Multi touch bug ftl and slow multitasking.
Was really hoping Google would solve these problems earler
Sent from my Galaxy Nexus using XDA App
hurricurry said:
Multi touch bug ftl and slow multitasking.
Was really hoping Google would solve these problems earler
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Multi touch bug is a complete killer. Really can't wait for 4.0.4 AOSP hopefully soon
The news is that not everyone is on 4.0.2 yet. If you can't wait then grab a custom rom, otherwise a whole lot of patience may be necessary.
virtualcertainty said:
The news is that not everyone is on 4.0.2 yet. If you can't wait then grab a custom rom, otherwise a whole lot of patience may be necessary.
Click to expand...
Click to collapse
Totally true.
Google is not really considering Galaxy Nexus a Nexus device it seems. Some other systems have gotten newer version of Android already.
At least my Galaxy Nexus runs bloatware-free official Android, even if the build is totally outdated by now. The only real benefit of having a Galaxy Nexus it seems.
Well, I actually don't think it is all that bad. The oldest ISC version out there is still only around 3 months old and better than 99% of Android's entire installation base.
The fact that a few manufacturers jumped on AOSP so soon is great and I'm happy for those users. I don't see the need to be 'first' and it doesn't sour my experience any. Google obviously thought the GN would re-fork with 4.0.3 by now but sometimes bugs get in the way of developer's best intentions.
virtualcertainty said:
Well, I actually don't think it is all that bad. The oldest ISC version out there is still only around 3 months old and better than 99% of Android's entire installation base.
The fact that a few manufacturers jumped on AOSP so soon is great and I'm happy for those users. I don't see the need to be 'first' and it doesn't sour my experience any. Google obviously thought the GN would re-fork with 4.0.3 by now but sometimes bugs get in the way of developer's best intentions.
Click to expand...
Click to collapse
Well yeah, but the things that annoy me are the bugs that are present in 4.0.2 and have been fixed in 4.0.4. And not only that, but also the API features of 4.0.3+ that was supposed to be the 'base' version of Android 4.0.
I don't mind how long major releases would take, but this is a small incremental update. I am just surprised that it takes so long to serve it to 'Google phone'.
kristovaher said:
Totally true.
Google is not really considering Galaxy Nexus a Nexus device it seems. Some other systems have gotten newer version of Android already.
At least my Galaxy Nexus runs bloatware-free official Android, even if the build is totally outdated by now. The only real benefit of having a Galaxy Nexus it seems.
Click to expand...
Click to collapse
Newer versions such as what? The latest aosp is 4.0.3 and not 4.0.4. It's quite obvious that 4.0.4 is not ready.
The Galaxy nexus is a Google supported device and is a nexus.
Sent from my Galaxy Nexus using xda premium
Well, if you look from it from the other side. Google might actually spare us from the still-bugged 4.0.3 version wich is AOSP. Also, JBQ already confirmed that the 4.0.4 version contained a "nasty bug" and wasn't ready for release.
If you look at it that way, new devices with 4.0.3 is still bugged in a way. And Google wants to keep those versions away from their current Nexus.
Just my way of being patient
Oddly enough, some of the tablets shown at MWC (on 4.0.3) had multi touch issues. This brings in a whole new strand of questions...
Sent from my Galaxy Nexus using xda premium
In regards to the latest os .... can anyone tell me what phone has ics update already???? And I've said phone ohh and it has to be released now announced
Sent from my Galaxy Nexus using xda premium
hurricurry said:
Multi touch bug ftl and slow multitasking.
Was really hoping Google would solve these problems earler
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I was really hoping people would stop *****ing about OTAs.
Sorry, but you all sound like a bunch of whiney kids. You'll never be satisfied because the OTAs will never be quick enough to satisfy people. Google is not going to give you nightly builds of ICS. So just calm down and wait for it to be finished and pushed out.
martonikaj said:
I was really hoping people would stop *****ing about OTAs.
Sorry, but you all sound like a bunch of whiney kids. You'll never be satisfied because the OTAs will never be quick enough to satisfy people. Google is not going to give you nightly builds of ICS. So just calm down and wait for it to be finished and pushed out.
Click to expand...
Click to collapse
You just love calling everyone whiney kids don't you?
People are pissed because we have a Nexus that for the first time, is NOT leading the way in terms of OS version. We are pissed because of the overwhelming silence from Google.
It would take them 15 minutes to post a blog on where things are at.
Scottatron said:
You just love calling everyone whiney kids don't you?
People are pissed because we have a Nexus that for the first time, is NOT leading the way in terms of OS version.
Click to expand...
Click to collapse
Yes I do. And people deserve to be given some perspective.
What do you mean? ~1% of Android devices have ICS. How is that not leading the way in terms of OS version when we're the only phone with it? Nothing has a higher OS (and don't say "omg the NS has 4.0.3!"). The Galaxy Nexus launched Android 4.
Why are you crying about not having 4.0.3/4.0.4 over 4.0.2. If its not ready, its not ready. That's why we don't have it officially yet. For all you know Google is holding off till 4.0.5, 4.0.6, or 4.1... no one knows.
Like your phone for what it is. You're like a dog chasing his tail when you get something great and always look for the next best thing. You'll spend your entire time with the device wanting more, and you'll never enjoy what you have.
Like I said in the other thread: OTA's will never come fast enough for people. If Google started pushing one every month (regardless of how what it did or didn't include/fix), it still wouldn't be fast enough because people would prefer it was 3 weeks instead, then 2 weeks, then 1 week, then nightlies. And guess what? Google isn't going to do nightly OTAs of ICS (not even close!). If you want nightlies, go build a ROM from CM source and change things for yourself. Or better yet, build straight from AOSP source and fix the bugs yourself. Make a thread for it and let people ***** at you for not fixing them faster.
maybe this is why apple is having better success in the mobile world then google and all the others.
while all i have is an old ipod touch from apple, and have GN and ACER tablet, the fact is that google ANNOUNCED 4.0.3 as THE LASTEST STABLE release, however, even on the official supported hardware i still have 4.0.2
this is why i personally compare android to the old windows mobile system.
on the old windows mobile system, if you wanted to upgrade to the latest, you had to hack the device and upgrade yourself, and even then not all devices could be upgraded to all OSs. when i talk to people about android, i still find mayself telling them that even on the official hardware you need to hack the device to get the official upgrade.
if google and all the open source will learn a little from old mistake they will build a better test environments and stop calling any buggy version an official release, or make sure that all devices be able to get the latest version when it is announced (ipod/iphone 3rd gen can still be updated to ios5 even if it can barely work with it) .
the simple fact is, the android is repeating all of the mistakes that even microsoft with WP7 have learned, and am not showing even the slightest inclinations to make a change to this inadequate system of multiversioning....
PCHelper said:
maybe this is why apple is having better success in the mobile world then google and all the others.
while all i have is an old ipod touch from apple, and have GN and ACER tablet, the fact is that google ANNOUNCED 4.0.3 as THE LASTEST STABLE release, however, even on the official supported hardware i still have 4.0.2
this is why i personally compare android to the old windows mobile system.
on the old windows mobile system, if you wanted to upgrade to the latest, you had to hack the device and upgrade yourself, and even then not all devices could be upgraded to all OSs. when i talk to people about android, i still find mayself telling them that even on the official hardware you need to hack the device to get the official upgrade.
if google and all the open source will learn a little from old mistake they will build a better test environments and stop calling any buggy version an official release, or make sure that all devices be able to get the latest version when it is announced (ipod/iphone 3rd gen can still be updated to ios5 even if it can barely work with it) .
the simple fact is, the android is repeating all of the mistakes that even microsoft with WP7 have learned, and am not showing even the slightest inclinations to make a change to this inadequate system of multiversioning....
Click to expand...
Click to collapse
I'll tend to agree with most of what you said.... Apple has this down to a T with releasing OS versions. Everyone with the previous 2 versions of the hardware is completely guaranteed to get the update the day that it comes out. Models 3 years ago may or may not get a full update, but they'll at least get a partial update (with some features pulled). You know what you're getting and you know when you're getting it. You'll never be in limbo. When Apple announces a new iOS version, they explicitly say which models will get it. The consistency is good.
WP7 is a bit better analogy of what Android has to strive for IMO. Android covers tons of carriers, devices, etc. but still needs to be able to handle pushing OTAs to everyone in a timely matter. This is a huge logistical hurdle for MS (or Google) to try jump. MS is handling it by putting very strict guidelines on what hardware can be used and what you can/can't do to the software (which is pretty much nothing). This makes the OTA process a 1000 times easier for MS to implement. What it leads to is basically knowing that the OTA update will work on all of these different devices because they're about 90% identical in hardware, and 99% identical in software. The only hurdle for them is pretty much getting carriers to accept the terms of pushing the OTA.
While Google could implement a system like this, it'd be at least a year out. Because in order for this MS-style system to work, Android would have to have specific hardware and software guidelines. The problem being that Android is open source and free, and manufacturers can really do whatever they want. They only have to follow some very relaxed "guidelines" to get GAPPS. Even if Google wanted to push OTAs to all of these phones in their current state they couldn't. Google doesn't hold the code from Samsung, HTC, LG, Huawei, and others because they're each doing it in house. There is no unifying OTA that can be pushed. Ultimately Google has no say in what happens after they certify it for GAPPS support. At that point, its between the manufacturers and carriers what is going to happen.
Google needs to start hitting manufacturers where they can, with GAPPS. Its the only closed-source part of Android and its a really really important one. They need to start forcing UI guidelines and skinning policies that let OTAs flow smoother. On the carrier side, they need to start pushing carriers to allow manufacturers to push them when its ready. Google can only do so much to carriers though. At that point they can threaten, but again its not up to Google what happens with those devices once the licenses go out. Its not a Google sale to the carrier, its a manufacturer sale. Until every phone Google sells is a Nexus, they won't be able to tell carriers what to do. Although the market share is huge for Android, it doesn't have the same unified push to bully carriers like Apple has.
....but I've got a couple other points as well on your post. You're making it sound like the Galaxy Nexus is running 4.0.2, and the rest of devices are running/being sold with 4.0.3 (the "stable" build). This is not the case. Whether its running the most "stable" build or not, the GNex is the most up to date of all Android phones out there right now. And we'll be getting stock 4.0.3 before anyone, and all of those phones being sold from this point w/ 4.0.3 will have skins attached as well.
martonikaj said:
the GNex is the most up to date of all Android phones out there right now. And we'll be getting stock 4.0.3 before anyone
Click to expand...
Click to collapse
Why doesn't the Nexus S factor into your argument?
Evangelion01 said:
Why doesn't the Nexus S factor into your argument?
Click to expand...
Click to collapse
First off, the Nexus S update has yet to be pushed to everyone. Its still halted because of bugs (and the NS4G doesn't have it officially, either). Second, simply because it's 4.0.3 doesn't mean that it's "better" than 4.0.2 on the Galaxy Nexus. For all intents and purposes, it's the same update... look at the NS4G and NS on Gingerbread. One was on 2.3.5, the other on 2.3.7... doesn't mean one was better than the other, but simply the NS4G needed specific build # because its a different device.
If you're splitting hairs of 4.0.3 vs. 4.0.2 to try and win this argument, it's not going to work.
now here is where we can start the argument... 4.0.3 is better then 4.0.2 if only due to the codex hardware fix.
But that is not the question. The issue is it was officially released as latest stable, however only after official release somehow all of a sudden the official Google phones are full of bugs and it is not good for them. If it is not developed and tested on the official hardware, then why put the official stamp on everything? Where is Google QA? Why buy Google official devices if we cannot even get the minimum we expect from the name? Pay attention, I am not talking about vendor devices, only on official stamped device/software....
Sent from my Galaxy Nexus using xda premium
Scottatron said:
You just love calling everyone whiney kids don't you?
People are pissed because we have a Nexus that for the first time, is NOT leading the way in terms of OS version. We are pissed because of the overwhelming silence from Google.
It would take them 15 minutes to post a blog on where things are at.
Click to expand...
Click to collapse
+1
Couldn't have put it better myself. Google really needs to pull its **** together and give us some of that 4.0.4 goodness!
Thank god for unlockable bootloaders and XDA devs, huh. Oh, wait......
From my point of view (and mine only) I knew the nexus would have an unlockable boot loader, I knew there would be a root exploit before I even brought the device and I knew the devs here would provide better then Google themselves, that's why I personally, brought the phone. Fortunately you didn't choose HTC. The delays are longer and the devices more secure. What I'm trying to say is, make the most the the nexus and this community and get a custom ROM or makesure you choose devices in the future for the right reasons. Let's face it, very few of us brought it for the specs....
Sent from my Galaxy Nexus using XDA App
Related
Okay, so I saw a bunch of the tech news sites running with the story about 5.0 coming out in Q2 (Google I/O?). Anybody have any GOOD info on this? I can't imagine it will be anywhere near as big an update as 4.0 was, but I am curious as to what it will have, who will get it first (GNex makes the most sense), and how far behind that release 6.0 and the next Nexus device are.
The next version will be 4.1
Sent from my Galaxy Nexus using XDA App
Hemlocke said:
Okay, so I saw a bunch of the tech news sites running with the story about 5.0 coming out in Q2 (Google I/O?). Anybody have any GOOD info on this? I can't imagine it will be anywhere near as big an update as 4.0 was, but I am curious as to what it will have, who will get it first (GNex makes the most sense), and how far behind that release 6.0 and the next Nexus device are.
Click to expand...
Click to collapse
We won't be seeing 5.0 for at least until Q4.
We may not get it until Q4 but it is extreamley probable that is will be announced in Q2 due to that's when google i|o is
cordell507 said:
We may not get it until Q4 but it is extreamley probable that is will be announced in Q2 due to that's when google i|o is
Click to expand...
Click to collapse
Doubt it. THey haven't even polished ICS. They would just stir up **** talking about 5.
if anything, Android 5 would probably be more of a minor update like it was from froyo to gingerbread than gingerbread to ICS. more behind the scene changes
This just further proves to the tech blog community that 'android fragmentation' will always exist.
kfirms said:
This just further proves to the tech blog community that 'android fragmentation' will always exist.
Click to expand...
Click to collapse
If thats the price of having a 'latest and greatest' style community I'm fine with that. I think went you have fast paced development and your always looking at the next big thing theres always gonna be a lack of consistency.
Troll... troll and more troll...
Enviado desde mi Galaxy Nexus usando Tapatalk
If it duel boot chromium then it will be a PC build
Sent from my Galaxy Nexus using xda premium
Why has the word RUMOR been left out of this entire thread!?
Okay continue the speculation..
Have to love Rumors, I think 4.1 is more logical than 5.0 and I would think we would see it on the gnex fairly quick. But again this is all speculation and rumors at this point.
Sent from my Galaxy Nexus using Tapatalk
I don't really see versioning == fragmentation. Having developed with and seen the android SDK grow, it looks like natural evolution to me.
Most people don't really get it. From 2.3 to 4.0 isn't like they rewrote "android", the changes are not that drastic. Its still essentially the same basic API and framework, with additions and deprecations as needed. In fact the increase of a "major" version number (2->4) was completely a farce, and entirely marketing spin.
So, 5.0 will be much of the same, and 4.0 is so good now, I can't say I'm all that worried about when its coming out. My main concerns are with manufactures optimization of the drivers that interface with the ICS HAL. Get that ironed out first, and let ICS be ICS.
Only real direction for growth is for Android to start having the ability to become a desktop computer + tablet in one, basically like W8 is trying to do.
ICS basically bridged phone + tablet, so only remaining path is to add desktop to it, to be able to replace most office computers (that aren't needing high powered gear)
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Deofol said:
I don't really see versioning == fragmentation. Having developed with and seen the android SDK grow, it looks like natural evolution to me.
Most people don't really get it. From 2.3 to 4.0 isn't like they rewrote "android", the changes are not that drastic. Its still essentially the same basic API and framework, with additions and deprecations as needed. In fact the increase of a "major" version number (2->4) was completely a farce, and entirely marketing spin.
So, 5.0 will be much of the same, and 4.0 is so good now, I can't say I'm all that worried about when its coming out. My main concerns are with manufactures optimization of the drivers that interface with the ICS HAL. Get that ironed out first, and let ICS be ICS.
Click to expand...
Click to collapse
Anti-android people just like to throw out the word fragmentation, don't feed trolls.
kfirms said:
This just further proves to the tech blog community that 'android fragmentation' will always exist.
Click to expand...
Click to collapse
Hey you, get back under your bridge until we say you can come out.
Damnit I accidentally hit thanks.
I don't know why people keep shooting this down as a rumor?
It's almost certain that we will see a major announcement in Q2, since google has been updating android 2 times a year almost since its release. The only uncertainty is whether they'll upgrade the name and how much they'll upgrade the version number.
So yes we will see an announcement at Google I/O and it'll be likely to hit our gn's first, just as we will see another one in Q3/4 along with another device release.
mortenmhp said:
I don't know why people keep shooting this down as a rumor?
It's almost certain that we will see a major announcement in Q2, since google has been updating android 2 times a year almost since its release. The only uncertainty is whether they'll upgrade the name and how much they'll upgrade the version number.
So yes we will see an announcement at Google I/O and it'll be likely to hit our gn's first, just as we will see another one in Q3/4 along with another device release.
Click to expand...
Click to collapse
You must have missed the announcement where Google said they will only give one update a year from here on out. With all the clamoring on how ICS is a "huge" update you will NOT see 5.0 in Q2 AND something in Q4.
Sent from my Galaxy Nexus using xda premium
I think we'll see a 4.1 update fairly soon, but JellyBean probably not until next year during the annual release and it will probably be just back end code like stated. We'll probably start seeing information on it around the end of Q2 but I don't see anything dramatic coming to light.
ICS was the BIG change over everyone was waiting for that brings tons of features to the table. I can't see them doing anything dramatic for a while. I think the CORE Android is where they want it to be now where Tablets and Phones are merged into one single version.
someone swing by google and see if the statue is up or not
mortenmhp said:
I don't know why people keep shooting this down as a rumor?
Click to expand...
Click to collapse
Because everywhere this is found on the internet it is tagged with a big ass RUMOR in the title!! And the original source is known for pulling **** out of their ass.
Im here at work and got me thinking bout the rumoured news bout Google releasing the JB 5.0 sometime this fall or workingnto release Q1 2013. News from AndroidPolice...too lazy to link it.
Im just thinking that these updates are happening way to fast. Some phones are yet to receive their ICS and yet JB is just around the corner. Also, new phones with quad will be released early/late spring..? with ICS and for some they will have to wait for another good amount of time for JB. We know that Samsung etc are never on the dot when releasing updates.
I kinda miss the days of Windows OS when they actually make you wait 2/3yrs for a new OS release. Just kinda makes it worthwhile.
All im saying is, that Google should wait until the supported phones have been updated to ICS and give them time to enjoy it. For others they will have to spend an extra money to buy the latest phone with ICS. Not really fair.
Ok im goin back to working...lol...sorta
Until we start seeing apps that don't work on somewhat new OS's I don't see it as a problem. For the most part, apps being put out now are still compatible with Froyo so why should people on Froyo care? Yes it sucks to get a new phone and not have the newest OS but what do you expect Google to do? With apple releasing yearly releases as well they need to keep up.
Google has been releasing yearly OS updates for a while now. Why the concern all of a sudden? Also, probably not worth getting worked up over unreliable rumors.
Sent from my Galaxy Nexus
I think one release a year is fair. With all thats evolving in the mobile landscape, an update interval any more than that will risk falling behind the competition.
A yearly update is not just to change things around for the heck of it, but to aim to improve the user experience. If the Android team has good work ready to be released, I don't see why they should hold it back because manufacturers can't get their act together. This is why we have the Nexus phones.
I completely disagree. Google's yearly release cycle means that they are always working on making Android better. Since a new major OS release comes every year, I am guaranteed to have a modern phone with a modern OS every year if I continue buying Nexii.
In my opinion it is certainly a good thing.
I dont agree with this. Wait 2-3 years for new features and fixes while other OS's (iOS and Windows Mobile) continue to have yearly updates? No thank you.
For the majority of people, whatever current Android they are on is more than enough for them. If you want to stay on the bleeding edge, you get a Nexus device.
JB probably will not be as big as an upgrade as it was from GB to Honeycomb or ICS.
How is Fall of 2012 or Q1 of 2013 too fast? It's not even spring yet. ICS was announced and released in November, I think. That is a full year, at least, in between OS changes. I think that 1 year in between OS updates is perfect. Why would you want to be stuck on an old OS when new, better features are always a good thing?
You're pretty much saying that you wouldn't mind still being on Eclair or Froyo right now. I don't know about you, but I think ICS is light years ahead of both of those OS's.
Hardware obsolescence will eventually halt fragmentation on its own. Most consumers roll over their device at the end of a contract anyway, that's just 2 years or 3 in some markets. Anyone that holds on to a phone for over three years either doesn't care about bleeding edge updates, they're happy with an old device anyway, or they've extended their device's life via custom roms. In other words, If it is January 2013 and you're still on Eclair then a) you probably don't know what 'Eclair's is and b) you're not losing any sleep over being excluded from updates.
I don't see a huge problem with the android market being 'fragmented' over 2-3 versions. It's all just optics: Android haters trumpet the fragmented platform while advocates brush it off. It shouldn't halt or slow down progress, and if it does then Google risks stagnation.
Its not that Google is going too fast, its that the other manufacturers are going too slow. 1 OS release a year shouldn't be a crazy schedule.
Am I reading this right - so you think technology advances too fast and wants it to slow down because YOU can't catch up?!
OP, please tell me that you are kidding.
Edit: I'm not flaming but simply shocked by the logic and argument.
Yes please get back to work already, sorry but I don't agree with your opinion, blame the carrier's and manufacturers as well.
Sent from my Galaxy Nexus using XDA App
ragnarokx said:
Google has been releasing yearly OS updates for a while now. Why the concern all of a sudden? Also, probably not worth getting worked up over unreliable rumors.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
The problem with these "hard and fast" Android updates is that is accelerates device obsolescence. Of the hundreds of Android handsets out there, only a dozen or two actually get these new OS'.
This isn't a problem you see in iOS devices, but it's certainly an issue with android.
Sent from my Transformer TF101 using Tapatalk
EP2008 said:
The problem with these "hard and fast" Android updates is that is accelerates device obsolescence.
Click to expand...
Click to collapse
Obsolescence? So which Gingerbread device can't make calls/text/access the market/use apps after ICS is released?
Just because some other devices do things faster/different doesn't make your device obsolete. And please, look up the word 'obsolete' first before tossing it around.
I think I partially understand and agree with OP's point.
It is not the yearly update that causes concerns, but it is the rate that creates so much hardware junk that counts.
For example, Apple's 3GS still can use recent iOS, at least it is upgradable, though you wont enjoy the speed or new features etc, but you still can use your old hardware with new iOS.
For Android, one year later you phone/tablet may already be "NOT ABLE TO UPGRADE TO NEW OS" , ICS, in this case.
Too many Device Spamming there. I think it is not Google's issue, it is , somewhat the Manufacturer's issue.
Because Nexus S still able to upgrade to ICS, Nexus One , sorts of (please correct me if I am wrong!)
But thanks to million android phone manufacturers, they locked down the system and make it proprietary in certain sense. and not upgradable to future OS because they don't know their current "Feature" will or will not be shoot down by Google's future updates.
Im actually coming from the Atrix which had an announcement from Motorola that ICS release would be sometime Q3 but that would depends if there is a delay or not. I decided to put myself into a contract and decided to get the Gnex since it had the latest offering of ICS. The Atrix ICS is still running on beta.
I agree that yearly updates will improve the user experience/fixes but then again we are but a small community here on XDA that are keen into rom/mod our phones. That is even if we have Devs willing to give time and effort in regards to leak updates. If ever we dont then we are sol. Im just thinking more about the general public who has no idea or would careless bout having a modified rom but are just interested in receiving the updates in a timely manner. Also, wat if ur current phone will not be included for any more OS release? the easiest way would be to purchase the latest and up to date phones.
If lets say that my collegues are getting the ICS for their SGS2 this Q2/Q3. Then JB will be released Q4/Q1 2013. The Google phones will be updated by either official or leak. Also i cant find the link but there was a stat released i few weeks ago stating that there are only 1% or 2% of phones that are currently running ICS.
Its frustrating for an average user having to sit next to a person with the latest OS release and wondering when they will get theirs.
For me, since im on ICS i dont care but when i was using my Atrix i had to settle for a mediocre beta ICS. :banghead:
@jiwengang - Thank you! Im glad someone here at least partially gets my point.
...now to get back to doin some real work.
I agree with others in that it's the hardware manufactures that are the problem, not Google.
1 year OS updates are fine. We just don't need 20 damn variations of the same phone from the same manufacture within that same year. The manufactures can't support all the different hardware configurations they are spewing out in a timely manner, so it takes ages to get updates, if you get them at all.
Dang manufactures need to focus more, stop trying to one up each other every 2 weeks. And support what they release more timely.
MilkPudding said:
Am I reading this right - so you think technology advances too fast and wants it to slow down because YOU can't catch up?!
OP, please tell me that you are kidding.
Edit: I'm not flaming but simply shocked by the logic and argument.
Click to expand...
Click to collapse
Not everyone has either the same knowledge or bottomless pocket that they can sport the latest and greatest phones. I still have a friend who I recently just flashed his SE X10 with GB 2.3.5. Though SE mentioned bout an ICS upgrade sometime in the future of who knows when.
Similar to the PC industry. A gamer will build a pc gamer rig with i9/FX with crossfire/sli etc...If you look at it now, the hardware has reached its peak. You can pretty much play any games these software companies throw at you. It is now the software ie: Games, trying to play catch up and entice gamers with more 'extra' dazzling features or effects to maximize ur hardwares potential. Back then, it was the other way around
If u use a console then its a different story.
Yes, it is shocking. Not everything works as smoothly as butter like ICS.
Yearly release / change of Android OS makes really senses to me.
I don't think I can wait for 2-3 years for an update / release.
that's why I got a nexus!
sent from my Nexus Prime
You are really losing focus as to what Jellybean actually is. All it is is an updated Ice Cream Sandwich. Yes, ICS was a huge jump from Gingerbread, because of the tablet/phone unification so there were major changes with the UI. That probably won't be the case with the next update. But if you remember the jump from froyo to gingerbread that wasn't a big deal huh? Googles cute little names cause too much confusion with consumers that don't understand software updates. 4.0.1, 4.0.2, 4.0.3...just updates.
Before you all scream heresy, hear me out.
Today marked Verizon officially announcing 4.2.2 for the Galaxy Nexus, thus marking the end of the VZW model being 4 updates behind the GSM models. Here's the thing...every time there's been an update in testing, El Madhatter has informed us because of his testing phone. He never got a 4.1.2, 4.2, or 4.2.1 build. His device went straight from 4.1.1/JRO03O to 4.2.2/JDQ39. Because of that, one can logically deduce that Google never actually released a 4.1.2, 4.2, or 4.2.1 build to Verizon for testing on the device.
There is historical precedent for this. Let's go back to December, 2011 when Android 4.0.3/Ice Cream Sandwich was released to the Nexus S and Motorola Xoom. Only two variants ever got Android 4.0.3:
1. The 900 MHz carrier-unlocked Nexus S (I9020T/I9023 - Got build IML74K)
2. The Wi-Fi Motorola Xoom (MZ604 - Got build IML77)
Here's a list of devices that never saw an update until Android 4.0.4/IMM76(X) was released in late March, 2012:
1. The 850 MHz carrier-unlocked Nexus S (I9020A - Updated directly by Google with no carrier approvals just like I9020T)
2. The Sprint Nexus S 4G (D720)
3. The Korean Nexus S (M200)
4. The Verizon Motorola Xoom (MZ600/MZ602)
5. The carrier-unlocked Galaxy Nexus running yakju firmware (I9250)
6. The Verizon Galaxy Nexus (I515)
The I9250 Play Store (running takju) model was not available yet.
So as you can see, clearly Google picks and chooses which devices get which updates in the event of brand new Android versions sometimes. Some builds (like 4.0.3) were clearly designed to be limited rollouts to test on a more limited scale. Then once they fix bugs, they do a more massive rollout (like they did with 4.0.4). Something tells me that 4.2 was the same thing.
4.2 and 4.2.1 had exactly one difference...the fixing of the December event bug. So, I think it's clear that Google probably intended the 4.2/4.2.1 JOP40(X) builds to be the test builds that they used to gauge the major problems. Now that the major issues with those builds are fixed, 4.2.2 is their "mass rollout" build that they're releasing to absolutely everything.
I think this is actually smart on Google's part, given that Verizon requires testing and approval of all updates to phones they sell.
Also, within that parameter, 4.2.2/JDQ39 hit GSM Galaxy Nexus models on February 12. We on Verizon got the official OTA rollout beginning March 19. That's a little over a month. That's the fastest update the VZW Galaxy Nexus has ever received.
Discuss.
i think its a little of both.
verizon does slow down the update process, but google is the one that releases the update itself.
Good thoughts. I also think it is likely that Verizon started testing and rejected those builds. 4.2 and 4.2.1 had some serious issues and I'm sure big red didn't want to support them.
A buddy of mine from high school works for Verizon corporate. I've asked him why VzW always seems to lag on updates. A lot of it comes down to VzW: It's not that Google never sent the updates to VzW, it's that VzW tests everything and what they don't like doesn't get pushed out to VzW customers.
Makes since to me, but I think Vzw miss handled the public relations aspects of it. I'm mean with all those jelly bean builds being released. They could've let their customers know that they're not interested in those builds but will update our phones with a build that meets their standards
I for one was ready you shout heresy at the top of my lungs, but then I saw it was written by Oldblue and had to give it a chance. I'm halfway convinced. Another peculiarity is the build numbers of late - in the past, each AOSP device typically had a slightly different build number (IMM76K, D, Q, JRO03C, R, O) due to small changes made to the final build for each unique piece of hardware. With 4.1.2 the build was JZO54K across all AOSP platforms, which continued with JOP40C,D and JDQ39. Something has changed in the build process to make Android more universal, and in the case of JDQ39 made it through Verizon testing in record time.
Now, do I believe that Google didn't send 4.2 or 4.2.1 to Verizon? Not sure, but it's worth pondering in absence of knowing what internal conversations occurred.
Sent from my Xoom using xda premium
It just wasn't a good idea for Verizon to take on the nexus. Nexus devices shouldn't be controlled by a carrier at all. Carrier's don't want to deal with the problems that the nexus devices bring.
Google doesn't release perfect builds to the nexus because that isn't the purpose of nexus phones. In order to be on the cutting edge of android development you have to deal with some things not working perfectly. I think everyone can agree that 4.2 and 4.2.1 had some pretty significant issues and Verizon customer support may not know what to do if a customer calls in needing help with something not working.
Winesnob said:
I for one was ready you shout heresy at the top of my lungs, but then I saw it was written by Oldblue and had to give it a chance. I'm halfway convinced. Another peculiarity is the build numbers of late - in the past, each AOSP device typically had a slightly different build number (IMM76K, D, Q, JRO03C, R, O) due to small changes made to the final build for each unique piece of hardware. With 4.1.2 the build was JZO54K across all AOSP platforms, which continued with JOP40C,D and JDQ39. Something has changed in the build process to make Android more universal, and in the case of JDQ39 made it through Verizon testing in record time.
Now, do I believe that Google didn't send 4.2 or 4.2.1 to Verizon? Not sure, but it's worth pondering in absence of knowing what internal conversations occurred.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Well there were past examples of all platforms having the same build number. All Galaxy Nexus devices launched with 4.0.1/ITL41D and 4.0.2 was ICL53F across the board.
On the Xoom, the Wi-Fi and Verizon models shared build numbers sometimes.
For the Nexus S, all variants ran 2.3.4/GRJ22. All except Sprint ran 2.3.6/GRK39F. Also, the Nexus One's Gingerbread builds always matched the GSM Nexus S variants...GRI40, GRJ22 and GRK39F.
Sent from my Nexus 7 using Tapatalk HD
oldblue910 said:
Well there were past examples of all platforms having the same build number. All Galaxy Nexus devices launched with 4.0.1/ITL41D and 4.0.2 was ICL53F across the board.
On the Xoom, the Wi-Fi and Verizon models shared build numbers sometimes.
For the Nexus S, all variants ran 2.3.4/GRJ22. All except Sprint ran 2.3.6/GRK39F. Also, the Nexus One's Gingerbread builds always matched the GSM Nexus S variants...GRI40, GRJ22 and GRK39F.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
True, but the most striking thing to me is that JDQ39 is on the N4,N7,N10, and GNex. Crossing that many platforms with the same AOSP core seems a bit unusual.
Sent from my Xoom using xda premium
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
iLeopard said:
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
Click to expand...
Click to collapse
In the case of the Verizon Galaxy Nexus variant, Verizon's only role is testing of any update. Beyond that, updates for that device come direct from Google. So Google submits the updates to Verizon, Verizon signs off, Google rolls it out. My point was, I don't think step one (Google submitting the update for testing) ever happened for 4.1.2, 4.2, or 4.2.1.
Sent from my Nexus 7 using Tapatalk HD
iLeopard said:
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
Click to expand...
Click to collapse
You are confusing carriers with manufacturers. TouchWiz is Samsung, Motoblur is Motorola, Sense is HTC. Carriers don't request these features, they come from the makers as a branding mark on top of the Android API. Carriers do on frqeuent occasion have the manufacturers presinstall bloatware from which the carrier receives advertising revenue or promotes its own services. The Nexus (despite being on Verizon) is a Google device, does not come with bloatware, and has no manufacturer skin stuck on top of Android. The vast majority of proprietary drivers for Nexus devices are posted on Googles open source pages as they have licensed them for distribution as intact binary files, aiding third party developers in building AOSP for Nexus devices. The Galaxy Nexus software update battle is between Google and Verizon - Verizon doesn't continue developing the platform, they simply test and decide if they are going to push it out. If not, they notify Google with specific issues and move forward from there.
Sent from my Xoom using xda premium
Winesnob said:
You are confusing carriers with manufacturers. TouchWiz is Samsung, Motoblur is Motorola, Sense is HTC. Carriers don't request these features, they come from the makers as a branding mark on top of the Android API. Carriers do on frqeuent occasion have the manufacturers presinstall bloatware from which the carrier receives advertising revenue or promotes its own services. The Nexus (despite being on Verizon) is a Google device, does not come with bloatware, and has no manufacturer skin stuck on top of Android. The vast majority of proprietary drivers for Nexus devices are posted on Googles open source pages as they have licensed them for distribution as intact binary files, aiding third party developers in building AOSP for Nexus devices. The Galaxy Nexus software update battle is between Google and Verizon - Verizon doesn't continue developing the platform, they simply test and decide if they are going to push it out. If not, they notify Google with specific issues and move forward from there.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Right, I did in fact confuse those two. Thank you.
The VZ variant complies with LTE standards though which does imply driver differences between the GSM and CDMA version?
iLeopard said:
Right, I did in fact confuse those two. Thank you.
The VZ variant complies with LTE standards though which does imply driver differences between the GSM and CDMA version?
Click to expand...
Click to collapse
Yes but Google and Samsung control that. The CDMA and LTE drivers for the VZW Galaxy Nexus are available on the AOSP driver page on Google's developer site.
Sent from my Nexus 7 using Tapatalk HD
Didn't the Sprint Galaxy Nexus get more updates though?
Sent from my Galaxy Nexus using xda premium
Yuhfhrh said:
Didn't the Sprint Galaxy Nexus get more updates though?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Toroplus (mysidspr) is maintained by Samsung, and that device bumped from 4.1.1 to 4.2.1. So no, it didn't get more updates and is actually an update behind the Google maintained Galaxy Nexi (takju, takju, mysid)
Sent from my Xoom using xda premium
My curse is that every thing reminds me of South Park, so I immediately thought "What's important right now, is figuring out whose fault this is."
Maybe you're right, but that answer only welcomes more questions. Could be Google thinks of VZW users as helpless children that can't handle the potential bugs present in the newest firmware. Maybe the opposite: Google thinks of VZW users as elitists who only deserve stable updates?. Or maybe they think, "We are VZW/Google, you know those AT&T jokers don't have service in the more rural areas of the country, you'll pay for it and then wait longer for updates. F you." Or maybe, VZW and/or Google were actually genuinely testing the firmware on the VZW LTE device before releasing it. I imagine it takes a while for the can-you-hear-me-now guy to make his rounds.
If anyone is to blame for lagging updates it's people like you who create threads like these. There has been a whacked sense of entitlement going on these past years and it's easier to find someone to blame rather than demonstrate patience. I would wager people are already asking when the next update is coming out. People call and harass Verizon or whoever and then tell the whole internet about how no one at Verizon knows anything or they are giving you conflicting dates. You're not forced to sign a contract with a particular cell phone carrier...are you? Oh and then the update finally comes and people rush to find and post the latest bugs and then call and harass Verizon or google again and ask them when the next update is coming. Has anyone ever called Verizon after an update and thanked them? Hmmm probably not, too busy asking for more and more. Android updates have become like crack for people and it's time to step away from the white mountains and just relax. They are just phones people!! Call your grandmothers instead of checking for updates everyday!
The op shows no sense of entitlement nor is requesting another update. Simply pondering on why various versions of nexus have updated differently. Fact is, to an extent your right, a lot of people are constantly crying for updates, but this thread is not one of those situations.
I, for one, bought a nexus for the purpose of being at the forefront of updates, but I'm not crying for any. As long as googles follows through with the promise of keeping my bought from Google devices up to date with the latest release I'm happy. That's not a sense of entitlement, its called buying a nexus for a specific reason.
Sent from my Nexus 7 using xda premium
hlaalu said:
If anyone is to blame for lagging updates it's people like you who create threads like these. There has been a whacked sense of entitlement going on these past years and it's easier to find someone to blame rather than demonstrate patience. I would wager people are already asking when the next update is coming out. People call and harass Verizon or whoever and then tell the whole internet about how no one at Verizon knows anything or they are giving you conflicting dates. You're not forced to sign a contract with a particular cell phone carrier...are you? Oh and then the update finally comes and people rush to find and post the latest bugs and then call and harass Verizon or google again and ask them when the next update is coming. Has anyone ever called Verizon after an update and thanked them? Hmmm probably not, too busy asking for more and more. Android updates have become like crack for people and it's time to step away from the white mountains and just relax. They are just phones people!! Call your grandmothers instead of checking for updates everyday!
Click to expand...
Click to collapse
Seriously? Wow. I never EVER hinted at a sense of entitlement. I agree with you that there is definitely a lot of that in this community, but that was not the point of this thread. If you look at any of the work I do around here, my entire purpose on XDA is to catalog stock OTA updates for Nexus devices and help the community with reverting to stock if necessary. Thus, a thread like this would be logical for me to start as this topic is basically at the crux of what I do here.
I should tell you, sir, to go back under your rock and stay there.
The title explains everything..personally, i hoped to see something better than some apps updates and a game playable in chrome. Even if someone says that google is working on a great, big update, a minor update to increase performance,battery and some bug fixes (like system ui memory leak?) would have been very appreciated by me.
(P.S. Worthless to say that the "fused location" update doesn't bring any noticeable battery saving and also that to get rid off memory leak i have to install a custom rom)
Yeah. I was kinda expecting them to talk about 4.3 and then give us a date when to expect it.
I dont think anyone is happy about it (we all love new features)
but i understand why they did what they did.
Google I/O is a DEVELOPER conference. so they did a bunch of stuff for DEVELOPERS so they would be able to make better applications.
and 4.3 is rumored to come June 10th...hopefully that will help you out a little bit with your problems.
i like multiple threads about i/o
Id say google nailed it with this io. This wasnt just for developers. They pushed updates to the whole android eco system. Yes they could've just released a new android version and some neat features to go with it. But that wouldnt move the ecosystem forward. This way the whole android family from 2.2 is affected. And ofcourse the developers knew their being heard , which is in every way VERY VERY good for us users.
Sent from my Galaxy Nexus using Tapatalk 2
Everything suggests, that a 4.3 release is close by, but it was probably supposed to be at I/O but got delayed. In my opinion they actually made up for it by pushing all the play features, which may not seem like an upgrade to the user, but which greatly increases general userexperience in a subtle way.
I agree with ferozfero. What they did unveil at I/O may not be what everyone wanted but looking at the big picture, it paves the way for some good stuff down the road. Google has a lot of other services that arent directly related to Android, which all got major updates. Complaining that we didnt get one little update to Android is pretty ungrateful. 4.3 doesnt need a big event to be released so we should all just be patient and see if the june rumor is true.
On a side note, Android will be celebrating its 5th birthday this september. I find that to be a good time to release version 5.0 if any.
Wrong thread. Thanks for failing Tapatalk. :banghead:
Actually i'm not complaining and i can sleep as every night even if my android version is still 4.2.2, but 2013 i/o was just out of my expectations and i wanted to share with everyone my thought. Another guy created a thread about google i/o, but he was simply disappointed about a "stock-android galaxy s4" instead of a nexus 5 or what ever it could be. This thread deals with android update and i/o no one spoke about it during the conference. I'm sorry if you think that i'm ungrateful, but developers at google are paid for their jobs and i deserve to expect always the top from a such rich and great brand like google.
Angelakaro said:
Actually i'm not complaining and i can sleep as every night even if my android version is still 4.2.2, but 2013 i/o was just out of my expectations and i wanted to share with everyone my thought. Another guy created a thread about google i/o, but he was simply disappointed about a "stock-android galaxy s4" instead of a nexus 5 or what ever it could be. This thread deals with android update and i/o no one spoke about it during the conference. I'm sorry if you think that i'm ungrateful, but developers at google are paid for their jobs and i deserve to expect always the top from a such rich and great brand like google.
Click to expand...
Click to collapse
Yes you can expect top stuff. But you should know that google has not disappointed anyone here. Actually they wer taking a step back for the good of the company and us. Yes they couldv just released a new version and everyone would be like yeeeee we got a new android version with cool features everyone but nexus users wont see for a year. But instead they released a slew of that will be available right then and would affect ALL end users much sooner tha a new android version. This us not to say theyr not gonna release one very soon. That way we would get all these awesome features and also a new android update. Everyone's happy.
Sent from my Galaxy Nexus using Tapatalk 2
I'm just excited for gcm (google cloud messaging).
Api sync notifications is going to be epic. I have two phones work and personal along with a tablet and to be able to sign in, delete notifications, etc from one device to all the others is going to be so nice.
I was satisfied with the io
Sent from my Nexus 10
Angelakaro said:
Actually i'm not complaining and i can sleep as every night even if my android version is still 4.2.2, but 2013 i/o was just out of my expectations and i wanted to share with everyone my thought. Another guy created a thread about google i/o, but he was simply disappointed about a "stock-android galaxy s4" instead of a nexus 5 or what ever it could be. This thread deals with android update and i/o no one spoke about it during the conference. I'm sorry if you think that i'm ungrateful, but developers at google are paid for their jobs and i deserve to expect always the top from a such rich and great brand like google.
Click to expand...
Click to collapse
Sorry if you thought I was soloing you out. I wasn't. I was talking about people who complain in general. A lot of people EXPECTED certain things at Google I/O and all I can say is I blame the rumors. Thats what rumors do to people.
jsgraphicart said:
Sorry if you thought I was soloing you out. I wasn't. I was talking about people who complain in general. A lot of people EXPECTED certain things at Google I/O and all I can say is I blame the rumors. Thats what rumors do to people.
Click to expand...
Click to collapse
Hehe you got that right. And this time the rumors wer so believable it had me going fr a while too.
Sent from my Galaxy Nexus using Tapatalk 2
Hopefully they're working on the #1 feature android lacks. Battery life.
Sent from my Galaxy Nexus using xda app-developers app
ferozfero said:
Yes you can expect top stuff. But you should know that google has not disappointed anyone here. Actually they wer taking a step back for the good of the company and us. Yes they couldv just released a new version and everyone would be like yeeeee we got a new android version with cool features everyone but nexus users wont see for a year. But instead they released a slew of that will be available right then and would affect ALL end users much sooner tha a new android version. This us not to say theyr not gonna release one very soon. That way we would get all these awesome features and also a new android update. Everyone's happy.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I respect your point of view because, actually, you're right. I think the same (that an update will be released soon)...my real disappointment was because they didn't talk about it.
jsgraphicart said:
Sorry if you thought I was soloing you out. I wasn't. I was talking about people who complain in general. A lot of people EXPECTED certain things at Google I/O and all I can say is I blame the rumors. Thats what rumors do to people.
Click to expand...
Click to collapse
Never mind Actually i'm really ANGRY because i thought that they would have released a major update and i reflashed factory 4.2.2 image and relocked the bootloader some days before the i/o, to get ready for the update! (LOL,just joking)
People are acting like if the OTAs come out on the day of I/O...I guess it helps to be prepared.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Let's get this out of the way first, nobody here is stupid, we know the L Release is never going to come to the Galaxy Nexus officially. So let's talk about the community. I just have one basic question for our talented devs, what are the odds that a port of L will be able to come to the Gnex and if so, what kind of time frame are we looking at here?
Does the Cyanogenmod team do developers previews like this one? We might see it from them.
I'm sorry, but this post is exactly what I expected to see today.
so lets get it out of the way.
SURE
we COULD see some 5.0 aosp love(via custom development)
MAYBE.
time frame?
when.source drops, give it a few months at most I'd say
source isn't even CLOSE to ready yet though.
SOOO
let's ALSO look at the past.
which nexus devices, after Google officially dropped support, are STILL ABLE AND ARE running LATEST android version?
ALL of them right?
stability and such isn't a factor for this question, it's IF IT CAN/DOES run newest aosp in SOME FORM.
so I'd say YES gnex WILL see 5.0 in SOME usable form. but asking for ANY "time frame"at THIS POINT since SOURCE ISN'T AVAILABLE YET is kinda pointless.
maybe though, just maybe, there are ALREADY some people at work on getting those "preview" things ported. no matter WHAT, patience and not asking for timeframe/eta is key here
I don't normally do +1 style posts, but I am also greatly interested in knowing this as well.
I imagine it is largely going to depend on how much of the underlying kernel and driver interaction changes. I remember on my prior phone, a Droid X which has been and is still locked down, it was generally impossible to get past ICS because of the major underlying changes in JB and not being able to get those on the DX. Granted the Nexus doesn't have this limitation but drivers aren't likely to be further updated and if the kernel goes too far forward it is unlikely to see compatible driver versions for GNex hardware.
EDIT: I should probably say modules instead of drivers. I'm primarily a Windows person PC-side.
Put it this way my 4 year old HTC Desire can run Kitkat then i would be amazed if we didn't end up with some pretty good builds of "L".
ashclepdia said:
I'm sorry, but this post is exactly what I expected to see today.
so lets get it out of the way.
SURE
we COULD see some 5.0 aosp love(via custom development)
MAYBE.
time frame?
when.source drops, give it a few months at most I'd say
source isn't even CLOSE to ready yet though.
SOOO
let's ALSO look at the past.
which nexus devices, after Google officially dropped support, are STILL ABLE AND ARE running LATEST android version?
ALL of them right?
stability and such isn't a factor for this question, it's IF IT CAN/DOES run newest aosp in SOME FORM.
so I'd say YES gnex WILL see 5.0 in SOME usable form. but asking for ANY "time frame"at THIS POINT since SOURCE ISN'T AVAILABLE YET is kinda pointless.
maybe though, just maybe, there are ALREADY some people at work on getting those "preview" things ported. no matter WHAT, patience and not asking for timeframe/eta is key here
Click to expand...
Click to collapse
Thanks for replying! I figured since I looked pretty thoroughly and didn't see a thread for it and thought that having at least one place for Gnex owners to talk about the L release for us wouldn't be a bad thing. I in no way meant to be one of those people who constantly bugs the devs about ETA's, I just meant what were could be expecting in the general sense. Thanks for the reassurance about us getting it, I've just been burned before about support with previous devices when they got past official support. But those weren't Nexii so I didn't know what to expect.
Brettbesa said:
Thanks for replying! I figured since I looked pretty thoroughly and didn't see a thread for it and thought that having at least one place for Gnex owners to talk about the L release for us wouldn't be a bad thing. I in no way meant to be one of those people who constantly bugs the devs about ETA's, I just meant what were could be expecting in the general sense. Thanks for the reassurance about us getting it, I've just been burned before about support with previous devices when they got past official support. But those weren't Nexii so I didn't know what to expect.
Click to expand...
Click to collapse
yea sorry about my tone in that reply mostly too
I'm usually not the one to fly off ranting towards other users actions, at least not on xda(i do #AshRants elsewhere lol)
your question was a valid one, and I know where you coming from when it comes to nom nexus devices and their lack of support, I had a droid x2 that was ORIGINALLY SCHEDULED BY MOTOROLA to have ICS update. which for some reason they just didn't follow through on. Their REASON they said was that "android 4.0+ would not improve functionality of this device"...aka "we don't feel like fixing all the bugs we gave you already with shotty gingerbread releases, and we aren't going to allow you to unlock the device or give you usable kernel source so screw off",...back when moto didn't gaf about the dev communities. they have made huge strides towards mending that relationship. just couldn't believe they had the gall to say 4.0 wouldn't improve the first dual core android device running a tegra2 chipset. bah. ramblings now again from ash.
but yea reason I kinda went off in that reply was mostly cuz I hoped all the other people who were already drooling at the chance to post the exact same things would slow down and think instead first it wasnt intended as a personal attack towards you or to start any flamewar on the subject. and judging by your reply you didn't take offense to it anyways, so :thumbsup: :good: we all on the same page anyways.
personally, I haven't seen much of the IO stuff about L, I saw mostly design changes, and would like to know more details about it's new features so I'll be digging around YouTube today for recaps and such.
but I'm almost certain that if we don't get some kinda official rom like CM, OMNI, SHINY, PA, etc... building L based.roms for us, then some of our awesomely talented devs will at LEAST get us able to look like we have it, along with SOME if not z MOST functionality of L.
ashclepdia said:
I'm sorry, but this post is exactly what I expected to see today.
Click to expand...
Click to collapse
I also think you guys should be patient. Your life won't be (that limited if there won't be a port of the coming up Android L to our Galaxy Nexus. Just relax.
As some have already pointed out, we're unlikely to see Android 5 "officially" ported to our GNex, for pretty much the same reason that we don't have an official 4.4 release for our phone. From ArsTechnica:
"Our talk with Burke shed some light on some more obscure topics too, including the lack of an Android 4.4 update for the Galaxy Nexus. Google's official line was that the company only supports hardware for 18 months after release, which it still mentions in its official Nexus update support document. As was speculated at the time, though, the decision was tied to Texas Instruments' exit from the consumer SoC market (TI's OMAP chip powered the Galaxy Nexus as well as other prominent Android-based hardware like the first Kindle Fires).
"It was a really extraordinary event," he said. "You had a silicon company exit the market, there was nobody left in the building to talk to."
Click to expand...
Click to collapse
TI stopped development for the GNex SoC at Android 4.1. Google and others worked hard to support it for 4.2 and 4.3, but the official TI software was broken by 4.4. The reason that we even have 4.4 custom ROMs is because some kind-hearted person, perhaps a TI insider, released beta or engineering sample software for the SoC. But as we've found, it's not the most stable
have a great weekend,
john
You could all complain about TI stopping development and blaming them. The Google Glass uses a not to different TI SOC compared to the GNex has a 3.4 kernel and runs 4.4.2
Now please understand that Google simply ditched us for reasons other than TI stopped developing SOC bla bla bla.
akash3656 said:
You could all complain about TI stopping development and blaming them. The Google Glass uses a not to different TI SOC compared to the GNex has a 3.4 kernel and runs 4.4.2
Now please understand that Google simply ditched us for reasons other than TI stopped developing SOC bla bla bla.
Click to expand...
Click to collapse
Plus if they didn't drop support after two years android would have alot more bugs in general.
DR3W5K1 said:
Plus if they didn't drop support after two years android would have alot more bugs in general.
Click to expand...
Click to collapse
I don't get your logic. And its not like 4.3 is flawless. HD video playback on this device (GNex) lags.
+ if Google themselves show a bad example to OEMs on how long to update devices, expect OEMs to not update devices older than a year. And this makes the whole "android doesn't get timely updates" into a new issue where "android doesn't get updates after a year+ at best".
GNex will never die!
(3.5 yrs going strong bby, and thanks to vanir+dirtyv f2fs running better than ever)
latenightchameleon said:
GNex will never die!
(3.5 yrs going strong bby, and thanks to vanir+dirtyv f2fs running better than ever)
Click to expand...
Click to collapse
Indeed. There will likely be somebody out there building from the latest source for this device as long as it's possible to do so, and possibly even if it isn't.
akash3656 said:
Now please understand that Google simply ditched us for reasons other than TI stopped developing SOC
Click to expand...
Click to collapse
Out of curiosity, what would those reasons be?
jsage said:
Out of curiosity, what would those reasons be?
Click to expand...
Click to collapse
That's up for you to imagine....
Money, profit, greed? You pick which one. Or make your own reasons.
akash3656 said:
That's up for you to imagine....
Money, profit, greed? You pick which one. Or make your own reasons.
Click to expand...
Click to collapse
Well, I guess when simple facts aren't sufficient then fantasy must be more believable.
wow
some of these replies were brutal, sheesh
gray bishop said:
some of these replies were brutal, sheesh
Click to expand...
Click to collapse
Honest perhaps. It's pretty simple really. The new OS (4.4) has a new kernel. The new kernel requires new drivers. Neither TI (OMAP SoC) nor ImgTec (PowerVR GPU) will supply those drivers.
Yes, an engineer at TI "released" a blob last fall. But it was not release-quality, it was beta-quality. Not everything is a conspiracy; we've just reached the end of the official support road.
On the other hand if one is inclined to run on the bleeding edge and stability is not their primary concern, there are any number of KitKat custom ROMs in which one can indulge.
have a great evening,
john
jsage said:
Honest perhaps. It's pretty simple really. The new OS (4.4) has a new kernel. The new kernel requires new drivers. Neither TI (OMAP SoC) nor ImgTec (PowerVR GPU) will supply those drivers.
Yes, an engineer at TI "released" a blob last fall. But it was not release-quality, it was beta-quality. Not everything is a conspiracy; we've just reached the end of the official support road.
On the other hand if one is inclined to run on the bleeding edge and stability is not their primary concern, there are any number of KitKat custom ROMs in which one can indulge.
have a great evening,
john
Click to expand...
Click to collapse
Ah crap I didn't mean to thank you. Anyway, yea sure remember all those OEMs you blame and all have given everything you've said to a certain product. GOOGLE GLASS. And go and check what SOC Google Glass uses.
Now have fun.