Wow, what's the deal w/ BMW? How are three cars around the same model year getting three different results? Does BMW really change their hardware that often?

Anyway below is a link to the 0.29 OBEXD binaries. I found that the MeeGo developers are using the "tracker" back-end as default, but I'm not sure why. In any case, just for this round of builds, I compiled both an "ebook" and "tracker" version. From now on, however, unless specifically requested, I will only be building the "ebook" versions (the "tracker" version did NOT work w/ my head unit).

Link: http://www.mediafire.com/?sharekey=f...953e47d6c516bd

As far as this Maemo update and unmet dependency business goes, it is VERY likely that the installation of the new openobex package was not completed...at what point of the installation this happens, I don't know. I also don't know if it causes any other issues (the people reporting the problem seem to be getting results, which means openobex working well enough to get PBAP up and running). The mp-fremantle-205-pr package appears to be a dummy package that describes ALL of Fremantle. The removal of this package MIGHT cause headaches down the road when PR1.3/4/2.0/whatever comes out (or any distribution upgrade for that matter). In any case, re-installation of that dummy package and the removal of openobex1.5 would fix the problem... I just checked on my phone and I HAVE removed mp-fremantle-205-pr (like I said before, I probably forgot to document it). I have not run into any issues regarding that package yet.

Finally, I haven't had any success with the CRLF binaries yet, they refuse to transmit the phone book altogether...




Drew