What Android needs to do in order to control/remove the fragmentation, is have it MANDATORY that all handsets run VANILLA ANDROID as the base, BUT allow system overlays (Samsung/Moto/HTC/LG etc.) to be installed as SYSTEM APPS or perhaps even user apps.
With this in place, the code would not have to be modified heavily by individual manufactures prior to reaching each handset, each update could in fact roll-out DIRECTLY from GOOGLE to the phone and THEN the manufactures can update their system apps via another route or perhaps have a "system app update section" available through the Play Store.
The major change currently being integrated into Android on KitKat+ to reduce fragmentation is the moving of as much of the Android content to Apps on the Play Store anyway, so that handsets running older versions of Android can still have access to the new UI with up-to-date apps.
Apply this SAME technique to the Overlays produced by each manufacture and almost every handset could be on a Vanilla Android Base, with system/user apps over top.
Is fragmentation all that bad?
Its really just another word to describe the diversity in the android ecosystem. This freedom of diversity leads to innovation.
Lack of updates and unfixed bugs? I wouldn't call that diversity. Many Android users never get to experience Android at its best because they choose a 3rd party handset and get stuck back in time. This is a major major flaw IMO.
Sent from my Nexus 4 using Tapatalk 4
Related
Guys,
I think everyone nowadays is quick to judge Android and Google for fragmenting the OS with multiple (4) versions but I think it was a necessary for success side effect. Without the humongous push that Google has done with Android, it wouldn't have been where it is now.
If you haven't heard, Google shared its plans to battle fragmentation which I mentioned as well.
What do you think? Do you think if Google slowed down back then (1.5/1.6), they would have ended up with Android that is as awesome as today?
Right now, Google has set up Android with a low-end version (1.5/1.6) and a high-end version (2.0, 2.1) and the market is sorting itself out. I think the two options were to fragment or be unsuccessful. With the fragmentation comes some issues, but it also comes with a wider range of devices that are capable of running it, which pushed it's popularity. Fragmentation can be easily solved farther down the line when Google takes the updating into it's own hands and stops letting carriers and manufacturers screw with everything.
In the end, we'll see Android itself being updated via the Market, I'd bet.
thats why google is releasing separate packages for the awesomeness theyre releasing from now on. the browser, ui kits, etc will come in separate apk's on the android market so you can have fun with whatever kernel and not be binded to the manufacturers limits. at least thats what the article today from engadget said.
I couldn't fit the concept completely in the title, but here it is:
Would it be a good idea for Google to redesign Android in such a way that it allows for OEMs as HTC and Samsung to more easily add their layers Sense and TouchWiz upon it - perhaps even in the form of a single apk?
Considering the fact updates take extremely long because the newly released Android versions, in this case Jelly Bean, need to be altered by HTC and Samsung and others before Jelly Bean can be even released onto the brand devices, not to mention an even longer delay for those who decide to purchase their phone by the major source of destruction of innovation, that is, the carrier. If Key Lime Pie, the next Android version, is designed in such way that the OEM skins and Android itself remain seperate, would it be possible to update to a newer revision of Android without having to be dependent on the OEM and carrier? It would then be the OEMs responsibility to update their skin as soon as possible to maintain a proper experience, as obviously a new Android revision has new elements that could possibly remain unskinned yet at release.
I personally think a strategy in this way forces OEMs more to bring out updates as soon as possible, thereby driving competition up - which is ALWAYS a good thing, while Android updates remain independent of OEM and carrier.
Of course, there will be issues with such strategy, such as required updates to drivers. Skin updates are non-essential, while it would still be nice to at least have a functioning device after an update. How would that work out for devices by HTC automatically receiving updates to Android? Remember, the whole point of this idea is to bypass the need for OEMs and carriers altogether. While I even doubt thát is possible, I'd like to hear a discussion trying to achieve this point as closely as possible.
I even believe this thread, if it does result in great ideas, could be forwarded to Google to look at - but I might just be completely wrong with such idea and as such, I'd also like to hear why.
Discuss away.
They're already working on it.
[Note: This information is ~18 months old, probably. I haven't kept up to date on the projects.]
T-Mobile built a theme engine, which is included in CyanogenMod. However, there are aspects of it that Google does not quite like. Sony-Ericson is also putting forth an alternative approach, which Google likes better. So, T-Mobile is working to merge the best of both worlds.
The "big difference" between the approaches is:
- T-Mobile's themes are user selectable at run-time.
- SE's themes are set by OEM (need to flash a new ROM to change)... but they are more deeply/cleanly/??? integrated with the Android core.
It's both a technical and political matter.
Thought i would post this for other world wider users to give opinions,sky is our version of HBO or ESPN,they android support has been shocking,they don't even support jellybean 4.1 yet and no tablet support etc while all IOS devices are supported .We thought we were getting some where with them and they promised to be more open after stringing us along for months with false claims why they could not bring sky go out on android etc so here it what we got
http://helpforum.sky.com/t5/Sky-Go/Sky-Go-on-Android-Forum-response/ta-p/763976
and here is the thread with all the input and waffle we are getting
http://helpforum.sky.com/t5/Sky-Go/Sky-is-in-breach-of-its-customer-code/td-p/749576/page/20
whats the views of other countries users of the likes of HBO which runs on 4.2,netflix which does the same
Sent from my Transformer using XDA Premium HD app
it gets better after a barrage of question after the last staement this is what they come back with, to give you an idea how far behind they are, they dont support a single android tablet yet, no jellybean support yet, not support for HTC one seris yet not even on ICS
"Android Q & A
Why is it taking so long to test for JellyBean?
We have been testing the Jellybean operating system across the range of handsets we currently support (and new unsupported devices) and have run into a few challenges around media playback. These are all being worked through by our Android development team and we hope to release before Christmas along with support for the HTC One series. We’re unable to go into further details around these challenges as this is sensitive information. As soon as we have a confirmed date for the next release we will announce it here.
Why are devices blocked?
The main reason why some Android devices are blocked is due to rooting; we are not able to support rooted devices because of the risk to our security measures. All unsupported devices are unable to download the official Sky Go app.
How come Sky is the only company which seems to have such a problem with TV rights issues?
Unlike some other content providers we have a lot of 3rd party content available on Sky Go, we have multiple contracts with varying obligations in order to protect this content. For example, Sky has rights to content in the first pay TV window (following DVD release) whereas some other Movie services do not, therefore our security requirements are different. We have a very sophisticated Digital Rights Management system which we which we work hard to protect. It means we are unable to release one generic app that will work across all Android handsets, and to ensure each handset adheres to our content protection requirements, they do need to be Q/A and tested individually.
How long does it take to test a device?
Generally speaking testing takes a minimum of two weeks, if we run into compatibility issues on any variant of the Android operating system for that device we need to investigate, implement fixes and test them. In addition our suite of services spans many platforms (Mobile, Web, Xbox) and a variety of apps which all tie in to the same backend system and therefore utilise the same working environments, bringing in inter-team dependencies. Releases are scheduled so that multiple updates can be delivered simultaneously.
No other legitimate TV app has these problems, why?
We’re not able to comment on the rights deals other comparable services have with third party content providers
Why can other companies who have the same issues with content/licensing/contractual obligations provide apps that work across the android ecosystem almost immediately?
We cannot confirm if they do have the same challenges we have. Some companies in the UK have third party content and some don’t which may affect the level of protection required.
Why is HDMI out supported on PC / Laptop but not mobile or tablet?
HDMI out on a laptop is not something we are able to control; where HDMI blocking is within our control we must make every effort to block it as this is a contractual studio requirement
Why isn't your Sky Go director leading the push to get Sky Go on all platforms?
Our Director and the team here are all pushing to get Sky Go on as many platforms as we can. We have two equally resourced teams that work on app development for Sky Go, one for Apple development and one for Android. We are platform agnostic and do not have exclusive relationships with any manufacturers. We are well aware of the level of Android penetration in the UK and as such have been working as quickly as we can to develop support for the ever growing number of handsets and operating systems. We are hoping to release support for the HTC One Series before Christmas along with JellyBean. We have every intention of continuing to develop versions of Sky Go for new handsets and new operating systems; the fact of the matter is that we face significant challenges in Android development so unfortunately this will not happen overnight.
So its about time that Google make a new version of Android which requires OEM's to have a Launcher which is treated more like a 3rd party launcher, so Google can throw out new updates to the OS via a Windows update style updater...
if the OEM's wish to adjust the OS's deeper code, then they lose Google's Auto OS Updater support for that device.
And if the main reason for not implementing this is US carriers, then make it available in the parts of the world where carriers care more about user experience, and just disable it in the states and if any carriers request that Google enables it on their network, then they can go ahead and do so...
and to be honest I think that after so long, most US carriers will have to add their support for this in order to avoid customers from switching to a different carrier for a better experience...
if US carriers ever try to stop innovation, then innovate everywhere else to put pressure on US carriers to implement these innovations... don't let them stop us from moving forward.
Also, if Google don't implement an Auto OS updates system (ie: to update from 4.4 to 4.5, or for security updates) then we may see Ubuntu phone becoming the better platform over time...
Edit:
Also I'd like to mention that as a developer myself, it really does my head in when I'm developing an app which uses all of the latest Android features, but I have to consider work arounds or removing those features all together because of the fact that most users devices wont be updated to the newer version of Android containing these extra features for developers to take advantage of...
Hi I'm new to XDA, and I've been pondering these questions for a while now especially after Android 4.4/KitKat was officially announced. But regarding Google's new policies about the Play Store and the Android platform how is going to impact developers particularly indie and small developers? From what I understand Google's going to lock in pretty much all developers to the app store, is this true that Google will close developers account if they upload apps to another app store like Amazon for example?
By the way is Google also going to retire the Android Package installer tool and replace it with the Google verify and install tool?
Also I'm a bit concern about any devices updating to Android KitKat because supposedly Android KitKat will no longer allow manufacturers to install third party firmware mods as well as a lack of support for SD card storage. Although I can understand restricting the manufacturer firmware modifications such as UI mods, which more often then not regardless of the OS leads to fragmentation bugs and that's definitely not a good thing.:laugh: Now if its true Google's going to restrict driver support for SD storage then I'm very disappointed with Google. I mean come on it's way too early for them to ditch SD all together, well at the very most once the standard ROM size is at least 32-64 GB in size. And after all as Android advances so does the .apk file size for certain high end apps such as games will continue increase overtime.