From: Árpád G. <arp...@gm...> - 2011-08-01 17:09:13
|
Hello, Thank you very much for pointing this out. As I've stated, my device is an iPhone 3G. I think I'll try the old DBVersion trick and let's see whether it works. AFAIK, the postprocess works fine, at least the logs show that a) the database is written to, and b) the checksum is correct, because iPod doesn't delete the entries from the database, just doesn't show them. When I tried to implement SQL insertions by hand (i. e., without the checksum), the app (or MusicLibrary.framework???) removed the tracks. Sent from my iPhone On 2011.08.01., at 11:41, Christophe Fergeau <cfe...@gm...> wrote: > Hi, > > 2011/7/31 Árpád Goretity <arp...@gm...>: > Which is >> the essential part of libimobiledevice which causes the iPod.app to properly >> read and reload the library? I'd like to implement this by hand in my iPhone >> app. > > There are 2 things that are needed, first of all, libgpod uses some > information it got from the iPod through libimobiledevice to > automatically identify the ipod model that is connected. This is > needed to know how the ipod database should be checksummed, and > whether sqlite files should be written or not. I think this is the > part that is missing in your case. > Then, for iOS devices, a series of commands needs to be run on the > sqlite databases as a postprocessing step (otherwise you get a long > "updating database" screen on the device), and once again libgpod uses > libimobiledevice to get these commands. I'm not sure either how to get > them from the ipod directly. > > Last but not least, recent iOS devices are read-only as far as libgpod > is concerned, that is everything that went out after the > iPhone4/iTouch4/iPad > > Hope that helps, > > Christophe |