TheGoogle Phonecould be aployto upset the wireless industriousness , or it could be an expensiveniche machine . Either way , it ’d be a bid to take Android back from the society that seem hell - dented on destroy it .
https://gizmodo.com/why-we-all-need-to-calm-down-about-the-google-phone-5426003
Android ’s most serious job right now is atomisation : with each new phone , it seems , come a unlike version of the o . In theory , these difference are trivial , and amount down to handset manufacturers ’ and attack aircraft carrier ’ custom interfaces , which sit atop a mostly unchanged Android core . In pattern , it ’s much worse .
Just search at the current top tier up of Android equipment . The Motorola Droid pass Android 2.0 . The HTC MyTouch 3 gigabyte and G1 on T - Mobile run Android 1.6 . The HTC Hero , a new phone than the MyTouch and the G1 , is still pose on 1.5 , along with the even unexampled Motorola Cliq , which shares one parent — Motorola — with the 2.0 - loaded Droid . Why is this something to worry about ? Remember Google Maps Navigation , the free turn - by - turn app for Android ? It only works on Android2.0 and 1.6 . An app write by Google does n’t even do work on every new Google telephone set . Imagine how affair are with third company apps . ( Spoiler : it ’s a shitshow . )
https://gizmodo.com/google-maps-navigation-hits-the-g1-mytouch-all-other-5411138
Google ’s been reasonably diligent about update the devoid , open - source heart of Android moving forrard at a steady pace , and append handset manufacturers with the tool they need to keep their handsets running the late computer software . That said , Google still deserves some of the incrimination here . That their software update let in new , exclusive functionality is fine on its own . And yeah , their avidity to earmark for Android to be bark and profoundly customize by handset manufacturers is fine on its own — in fact , it ’s implicit in the project ’s open reference ethos . But flux together , these ambitions create a gurgling software slurry of incompatibility , user experience inconsistency and general thwarting . ( See : Samsung Behold II ) So what hap ?
https://gizmodo.com/samsung-behold-ii-non-review-oh-god-the-ugly-5406912
The problem is in the model . Android updates seed out through carriers , over the air or with special installers . This is because the updates are their duty : once handset manufacturer ( and carrier , through handset manufacturers ) have make their own interpretation of Android , they ’ve efficaciously taken it out of the ontogeny flow . update it is their responsibility , which they have to pick out to uphold . Or not ! Who cares ? The phones are already sold . And there ’s very little to motivate a carrier or handset manufacturer to update their Android phones , because the consequences incline to fall on Google : If Android fragment , the App Market does n’t work . The public sours . Android starts to suck . This is where the Nexus One comes in .
sell without a aircraft carrier , package update for the Nexus One will be in Google ’s hands . They will be able-bodied to keep it up to date as Android develops , without hold to look on some other caller — or companies — not to drip the Lucille Ball . Users wo n’t have to bother learn Google ’s esoteric dessert - themed version codenames , and spirit will be better . This glide slope to software package updates already has a case work : the iPhone . There ’s a well intellect Apple did n’t trust AT&T with keep the iPhone up to particular date , and that they did n’t want the company that actually manufacturers the phone — Foxconn — to have any responsibility for its software package . Smartphone software is fussy and complicated , and so is the experience of using it . It needs to be tightly control to remain consistent , and because apps are the most authoritative part of a smartphone platform nowadays , consistency is life or end .
Without totally changing what the Android undertaking is , Google ca n’t put an absolute period to fragmentation . What they can do is provide an illustration of how an Android phone should be done . With the Nexus One , Google in all likelihood is n’t getting into the business of making hardware ; they ’re just hear , in their passive , Googly way , to retrieve restraint of a project that ’s spiraling toward chaos .
Update : Some input signal from someone who work in a major attack aircraft carrier ’s machine development group :
There is TONS of incentive for carriers to update their
software package . Take a look at Verizon hosting the only Android 2.0 equipment .
Are you perish to tell me that Sprint and T - Mobile would n’t love to
have their Android devices on 2.0 yesterday ?
The trueness is , there ’s very short incentive for the Handset Lord to
provide an update . All those telephone set are already sell and in the
carrier ’s inventory . Any investment in updating those models will
wreak them no additional cash flow . However concentrate on their next
model will .
He ’s partially correct : aircraft carrier have a need to keep their software up to date , in that they are the 1 who have to deal most with customers . French telephone manufacturers are the one ’s with the least motivation , since their cut-rate sale has already been made . But in branding a French telephone with their name , effectively selling it as their product , and assuming responsibleness for seeding updates , a postman becomes responsible for make certain their customers have up - to - date software , and exerting pressure on handset manufacturing business if they do n’t concur up their ending . — Thanks , David !
AndroidGoogleGoogle PhonesMotorolaSamsungSmartphonesT - Mobile
Daily Newsletter
Get the best technical school , scientific discipline , and culture news in your inbox day by day .
word from the future tense , deliver to your present .
You May Also Like
