Il giorno sab, 16/01/2010 alle 20.06 -0800, Alberto ha scritto: > So how do we fix this? I'm pretty sure you guys have already thought > about this and I wouldn't be surprised if a solution was coming soon, > since it''s such an obvious problem. However, here's my two cents, the > solution is very simple, a desktop application for syncing/updating/ > media playback/android market/amazon mp3, lets call it Android HQ or > Android Home for the sake of argument. > > The updates would be available to consumers as soon as they're > released, instead of months, years, or never depending on carriers. > This way most users would've the latest version as well as the > developers would have the latest SDK, developers would be able to take > advantage of the new APIs each updates bring and innovate faster, > instead of spending time supporting older versions.
I quite like your idea (but please make it cross-platform, or at least for Windows, OSX and Linux, and open source), even if I prefer mounting the SD card as a mass storage and manage it myself. But I think the main problem today with manufacturers upgrades is with kernel drivers. If all the kernel drivers were open source, I think now we could have them integrated in the official kernel, and upgrades could be smooth. But a recent implementation of Android 2.0 for the Samsung Galaxy had to revert to "backport Android 2.0 to 2.6.27 kernel" because of missing driver sources. It is the same problem plaguing Linux on the desktop. We need hardware developers to release hardware tech specs. Bye.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
