Related
I am a big android fan and can accomplish most of what people report they can accomplish with their phones provided they can post a decent how-to, but this is my second semester in college for computer science and i am starting to get a base of understanding and i want to start to be more active in the community so now that you know that i know NOTHING but can flash roms and such i want to get the ATT Note, it will be subsidized and under warranty and the size doesnt bother me BUT coming from the atrix i am frustrated that it seems everybody has EVERYTHING before i had it, so i would love to get the Nexus to ensure being up to date, Can you nexus people tell me if it is imperative for me to be a nexus owner to learn the workings of my green robot or am chasing the best gear without yet being able to utilize any of it yet. I presume you all enjoy the nexus and this forum will be a bit biased but really my question is, if i am not a real developer but a tinker will the nexus be a help or should i just get hardware i enjoy and hope the developer community will be strong for that model? Thanks for reading such a long post and for your thoughtful replies
If you are interested in Android why are you worried about devices? Android OS is the same on all, like Gingerbread, ICS etc. I don't know why you are concerned about what device to choose. Sorry if I am misunderstanding your question.
well, that is part of the question, should i care so much about the device?
i am asking in the nexus forum because if the device mattered then the nexus i presume would be the one to get, i just didnt know if things were at all simpler on the nexus,
the droid razr maxx now has a developer edition with an unlocked bootloader, so apparently there is a razr that is exactly the same as another razr except it is better developing on so i guess not all phones are the same that run android.
http://www.engadget.com/2012/01/29/motorola-announces-razr-developer-edition-with-unlocked-bootload/
I have a used/rooted HTC Evo i'd happily sell you, if you simply need a wifi capable android device to code on
im looking to buy a new phone and wonder if i should consider the nexus to be the best phone to buy and be able to learn on or if any phone that has an unlocked bootloader will suffice, i have an unlocked atrix which does fine but i want some new tech!
Am I understanding you correctly, you want to know which phone you should get because you want to start developing apps for Android?
If this is the case then the Nexus might be a better choice than the Note as it's sort of a reference device, and a lot of the phones coming out will have the same sort of features. With the Note you'd be testing your apps on a really large screen and you might find later on that they don't work as well on other devices.
I'm no expert or anything, I could be completely wrong!
this is exactly the type of thing im looking to hear, i think my preference is the note but if the community in general feels similar to this i think i will get the nex
Bump? I'm so curious on your thoughts xda
Sent from my MB860 using xda premium
You can program and test with your Aitrix too. Honestly, you don't need a Galaxy Nexus or any Nexus device to do any Android app. development. If you really get into development, you might want one, so you can test your apps on Ice Cream Sandwich.
If you're in a hurry to get your hands dirty, might as well learn using the latest API, and as such there are only 2 devices with officially released ICS, the galaxy nexus and the nexus s. Sure, some devices have unofficial ports and leaks, but if you encounter a problem, you can't be too sure if it's the OS's fault or the app. Also, it would probably be a good idea to hold on to your Atrix, so you can test your app with gingerbread as well.
Well there are various points to consider...
Obviously it's useful to have a phone the can run ICS to develop with the newest API. But as almost nobody has ICS on the phone, for now it might be more interesting to test with an android version people really have in masses. Then again, this is nothing nexus specific.
The support of the galaxy nexus from the android open source project (AOSP) is the main feature of the google nexus phone. But for software development this only really gets interesting if you start to move from developing normal applications that everyone (without root) can install from the market to working on custom ROMs that have code changes in the core (google) android code. Or if you need debugging tools not available on normal end-user builds (engineering builds seem to have lots of more development features, debug symbols for native (JNI) libraries, etc).
If you just start out coding it's likely that you don't really end up doing that very soon (but i know someone who started working on really low-level x86 assembly just after learning to code, so YMMV).
And then again many of these features will be available also if CyanogenMod is available on the phone you're using (as they make the AOSP code work somehow on their devices).
And you should look at the hardware features too: e.g. Galaxy Nexus: NFC; Note: drawing tablet style digitizer.
I think there's no simple and fast answer, and i'm doing any really low-level android work to really know what's needed.
It really depends on what you intend to do and how much you can work around various roadblocks on the way.
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.
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
Earlier this week I looked through countless posts and information pertaining to 4.4 Kit Kat on my GNex. As I looked at post after post and did my trial and error trying to find the right ROM for me, finally settling on Beanstalk, I realized just how amazing the support can be around here. From KitKang to SlimKat it is nothing but help when someone has an issue. All issues discussed, all issues looked at.
Then you have Google. Supportive... for new models only. The GNex has a great following and continued support of Devs here on XDA yet Google considers it too old to mess with and just ignores it. Petitions, outcry, and begging for Kit Kat and yet they still ignore it.
As I look at all the development projects I wonder why Google doesn't utilize the community more. Yes, I understand legality behind it and the need to pay the devs to do what they do if they used them. Still, in situations like the GNex when people want it like they do why not just Utilize the dev community. If they really just don't want to waste time on development with a 2 yo phone why not just outsource. Give these amazing Devs a chance. Look through the independent builds find one that suits the specifications needed and give that Dev team some support.
How many Devs here wouldn't jump at a chance to create a build for what is considered a outdated unsupportable phone, like the GNex, for Google who just doesn't want to waste resources on it. Take $10,000 and say "Hey, you want this phone supported create a build and you could get this $10k and your build sent out as a non-carrier update" Sure that is a small amount for Google but an amazing boost for a Dev doing what he loves. Saves Google time and Resources and gives us, that either lack the time or the ability too create a build, a strong build to keep our phone going for those 6 months to a Year before our upgrade time.
You have people like me that bought the GNex 4 months before the Nexus 4 came out but I am on Verizon and can't get a newer Nexus. You also have people that bought it a knowing nothing about the phone that ended up loving it but are stuck in a 2 year contract but would love to keep it running like new but are afraid to do anything like we do here because of their contracts. I just think a program like that would be helpful
To all the Devs out there working hard, keep it up. I love the choices and I love to test the new builds no matter how buggy they may be. Many Thanks go to all of you and all your hard work.
check out my thread on the Google's 18 Month window policy for updated and how its compared to apple
and the Nexus S
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.