Quote:
Originally Posted by hieronymos
I'm not sure what you mean but
a) you could mean that Kobo was working against its customers on the market question. That isn't true. There simply was a bug somewhere deep down in the operating system that prevented communication between the Google Framework on the Vox and the Google servers. It is Google who prevents Kobo from distributing the market, not the other way around. What you find on XDA is mostly piracy - only the Cyanogen guys are officially tolerated (in a written statement) to distribute the copyrighted non-open-source Google Apps.
b) You could mean that after an update you'll have to install the Market again. That's true. In all updates we have received, Kobo has sent the whole firmware. That means that apart from your data (/data, /sdcard and /extsd), everything gets completely wiped and reapplied (yes, up to the bootloader). This means that rooting, deleting and whatever you do on /system is completely meaningless, because it will be overwritten anyway. It also means that doing such things do not affect in any way updates. Of course, nobody can guarantee that Kobo won't change for the 'patch method' where only punctual files get replaced - in which case all that rooting, moving, disabling and Google Apps installs could lead to a mess (although Kobo's recovery system is quite advanced and will most likely simply restore the Vox to pristine state - as long as you don't touch the bootloader, the kernel, the recovery partition and the cache).
If you want to be completely sure not to mess anything up in /system, don't touch it. Or disable ("freeze") system apps, rather than moving them around or deleting them. You can do that over adb without having rooted (pm disable). The data for what is allowed to run and what not is saved on /data so a settings-activated factory reset deletes these settings.
c) As for the time spent, Kobo knows about the MAC address issue (the one that prevents the Vox and Google to communicate). That is why nobody here actually dug in deep enough to decompile the GoogleFrameworkService, change it, recompile and sign it. I'm actually quite positive that the fix is on the way and when that is fixed we might just install all packages out of the Cyanogen zip. Chances are, when an update comes out, it will be way easier.
|
Yeah, I'm referring to your item b), but I wasn't aware of c). Sounds like c) would make us all happy. But I'm delighted with the progress made so far - it really improves my Vox user experience.
