Develop Bugs

my two cents about wp7 and nodo update

I've been sitting on the sidelines not being vocal, but I think there's something we need to consider...
When we got our wp7 phones we need what features were lacking. If you didn't you should have done some research before you bought the phone. Wp7 is still in its infancy and expect there to be bugs and problems. If you wanted something more concrete should have stick with your iphone or Android. For what we do have everything seems to run pretty smooth.
Im not going to lie, but I curious about the nodo update. But im glad I haven't received it. Because then our phones will be locked and the homebrew segment and actual limited customization will be gone. Until someone of course finds a work around. And someone always does. And honestly, on your old phones how many of you even knew it had a copy.paste feature? Instead of focusing on nodo update which doesn't really do much, except speed up our phones, why no concentrate more on mango! Mango is the update that we all should want! Just my two cents. Btw i use a HTC hd7 on tmobile USA and its done everything i wanted without any problems!

I think people are focusing on Nodo because it's the 1st update and it will give us an idea about how Microsoft will handle the platform.
If they can't even handle a small update with almost nothing in it, this is worrying for the future. If they need 5 months to release such a small update, when will we get Mango? it's nice to make big promises about Mango but I'm starting to believe Thurrott when he says 2012 when you consider Microsoft's pace. I couldn't care less about Nodo, I don't use C&P that much and it doesn't fix the bugs people really care about like Live Tiles and push notifications not working. It only fixes one bug and that's the marketplace one.
And how long until we stop saying "they've just started, give them time"? After 6 months they should be about to deliver their 2nd update and be talking about the next one. Even if it's in 3 months, at least talk about it! They act like they don't give a sh*t and I'm sure soon people will start trading their phones and go back to Android/iOS.

That's true too. But considering this is their first update we can't assume things will be perfect. Now if the next major update rolls out and there's still issues with updating I for would question Microsoft. But I see your point of view. Perhaps Microsoft was releasing this small update to see how their update system would work? Dunno, but don't give up on Microsoft just yet. Trust me, I miss my android G2, but my wp7 phone hasn't let me done yet. And I was just thinking, do we really need multitasking? That could open up a whole new can of worms.

A can of good worms. Especially in the Modding scene.

vetvito said:
A can of good worms. Especially in the Modding scene.
Click to expand...
Click to collapse
I've been the first to defend WP7 and Microsoft all over XDA for months now but with official announcements starting to be pushed back while devices in other countries and even some here are running the update Microsoft is really starting to look bad.

z33dev33l said:
I've been the first to defend WP7 and Microsoft all over XDA for months now but with official announcements starting to be pushed back while devices in other countries and even some here are running the update Microsoft is really starting to look bad.
Click to expand...
Click to collapse
Same here. I'm really starting to get worried that it'll be like everyone feared.
Oh well, I really thought they would up their game with this.
Still a great phone, just now I know it won't be supported.

I'm still not quite sure what carriers have to do with updating the phone. The update comes through Zune. C&P can't screw up a network, neither can the marketplace not crashing all the time.
In other words, this update fiasco is purely MS's fault.
Be it that they didn't make a better deal with carriers, they underestimated logistics, they haven't been forthright with customers, it is the fault of MS.
On the other hand. If you bought the phone because some said someone at MS said an update was coming out soon that would add C&P, I can see how you'd be pissed off, but you'd still be silly for buying a phone based on a rumor as opposed to its merits, which are plentiful.
My problem with this whole thing is:
1/. If MS was gonna stay mum and not update us on the delays, they should've STFU all the way until they announced a concrete date for the update.
2/. If MS was gonna talk about updates, they should've kept us posted all the way instead of tidbits here and there.
The way their going about it making it so some can't even recommend WP7 because of this update fiasco. I mean, since when couldn't MS send out bug fixes? I get one almost every week for my PC and that OS is way more complicated than a phone OS.

That's so true. They shouldn't make promises they can't keep. And if they say something and it dont go right atleast keep us in the loop. I also agree its hard to reccomend a phone where the support from Microsoft seems to be very spotty. So my question is, is it still too early to tell the future of wp7? I guess now I can understand why some people are asking about trying to dual boot on our phones. So is it the carriers fault, Microsoft fault, or the OEMs hardware fault we're not getting updates? And since we have to update through Zune, what do the carriers have anything to do with the updates?

I think what is forgotten here is that XDA is a geek forum. Most people do not have a clue about copy and paste. They want to hear music surf the web and take pictures. We easily forget that we are not normal consumers.

hassia said:
I think what is forgotten here is that XDA is a geek forum. Most people do not have a clue about copy and paste. They want to hear music surf the web and take pictures. We easily forget that we are not normal consumers.
Click to expand...
Click to collapse
Normal customers want their push notifications to work properly, that should have been fixed within a month and Microsoft haven't even talked about it.

Peew971 said:
Normal customers want their push notifications to work properly, that should have been fixed within a month and Microsoft haven't even talked about it.
Click to expand...
Click to collapse
Hear, hear! Allowing a maximum of 15 apps with notifications was a huge oversight on their part, and afaik there are still no plans to fix this.
As for the marketplace bugs, from what I can tell not even all of those are fixed in the No[Can]Do upgrade. Probably because this particular update has been sitting on the MS servers since January waiting for an actual release.

emigrating said:
Hear, hear! Allowing a maximum of 15 apps with notifications was a huge oversight on their part, and afaik there are still no plans to fix this.
As for the marketplace bugs, from what I can tell not even all of those are fixed in the No[Can]Do upgrade. Probably because this particular update has been sitting on the MS servers since January waiting for an actual release.
Click to expand...
Click to collapse
The messed up part is that this is an advantage.
While they were ironing out whatever back-alley deals they had to iron out with the carriers, they could've been taking notes on what actual people in the know on forums like these had to ***** about.
They could've then slipped a few of the fixes, swapped a few 1s with 0s in the code, tweaked it around just a bit to make the OS even better.
Instead, we're going to get the update verbatim, the geek world is going to laugh and MS is gonna wonder where it all went wrong for the umpteenth time.

Probably just a reiteration of what others have said, but nonetheless my opinion. Microsoft first said that the NoDo update would be coming early next year so most people assumed January, than they said late February (I think they did), then it was early March, and now its late March. This update merely adds copy + paste (along with a few bugfixes, one of which ISN'T for the camera) and that is a very basic feature! Apple just released iOS 4.3 (which updated the Safari javascript engine and some other stuff) AHEAD of schedule by 2 days and Microsoft keeps pushing back a minor update by weeks.
I'm pissed because I want WP7 to succeed. I used the device and I loved the device, but it's not nearly as good as its competitors as a whole. If Microsoft doesn't figure out what their doing WP7 will fail.

The general rule is you NEVER buy a phone based on what is "coming". You always buy based on what is in the phone when you bought it. I went through the same crap with blackberry, promising an os update to the storm 2 series. When OS6 came out they were like nope, not supporting that handset. Go buy a the touch.
I'm very satisfied with the Samsung Focus I have now, any future updates is just icing on the cake. You'll be sorely disappointed if you buy things based on promises

Sorry I will have to reiterate my post 'normal consumers' want to play music,surf the web play youtube and games most will not use copy and paste that is just a fact. I work in a theater with a varied range of people most do not even know they have copy and paste capabilities.

Official: NoDo postponed to 2nd half of March

Of course, should we even be surprised at this point?
If you can read French, link:
http://windowsphone.frogz.fr/post/2011/03/09/Officiel-Mise-a-jour-NoDo-en-video-et-date-de-disponibilite.aspx

http://forum.xda-developers.com/showthread.php?t=985084&page=12

Well the other thread is about the update coming anytime soon. With a new thread it's quite clear that won't be the case.

Damnn !
http://wmpoweruser.com/nodo-update-pushed-back-to-second-half-of-march
I'll say like comment 1 in the million time.

Pathetic.
If it's the carriers: f*ck you carriers
If it's Microsoft: f*ck you Microsoft
If it's because of troubles with Samsung, please just push it out those of us who were smart enough not to get a Samsung wp7.

This is just a joke, If no update by the end of this month time for a new device

These kind of comments really get my goat! Apple didn't release anything or communicate things for ages - yet their fan boys didn't go mad about it! For gods sake the WP7 devices area few months old, MS has arranged an update to fix some issues (of which WP7 is not alone in having when new) and yet you are moaning because it will be a few weeks late?

adamelphick said:
These kind of comments really get my goat! Apple didn't release anything or communicate things for ages - yet their fan boys didn't go mad about it! For gods sake the WP7 devices area few months old, MS has arranged an update to fix some issues (of which WP7 is not alone in having when new) and yet you are moaning because it will be a few weeks late?
Click to expand...
Click to collapse
I'm pretty sure their fanboys were mad as well. It's just that we didn't go to their forums to check as no one realized that POS was actually going to be a contender.

adamelphick said:
These kind of comments really get my goat! Apple didn't release anything or communicate things for ages - yet their fan boys didn't go mad about it! For gods sake the WP7 devices area few months old, MS has arranged an update to fix some issues (of which WP7 is not alone in having when new) and yet you are moaning because it will be a few weeks late?
Click to expand...
Click to collapse
Then again at least Apple had 4 updates out given the same time span.
Microsoft is just **** at handling updates it seems. I'm really disappointed.
Like the other guy said, if no update by end of month, welp, iPhone 5 here I come.

adamelphick said:
These kind of comments really get my goat! Apple didn't release anything or communicate things for ages - yet their fan boys didn't go mad about it! For gods sake the WP7 devices area few months old, MS has arranged an update to fix some issues (of which WP7 is not alone in having when new) and yet you are moaning because it will be a few weeks late?
Click to expand...
Click to collapse
The update fixes 2 issues: Copy and Paste and the marketplace app. That's it!
If Apple had issues with broken notifications, they wouldn't wait 6 months to address these. Microsoft hasn't even acknowledged that issue.
People would moan less about missing features if everything already there was working properly.

sorta happy with the news
it doesn't fix the panoply of dell issues
it removes chevron
so wtf is the point of it again?
I say it gives xda more time to integrate a proper solution for sideloading

The problem is that M$ is attempting to play in the consumer space. They don't do that well. After their core OS/Office business, they got lucky with XBOX and everyone thinks they are good with the consumer. They aren't! They are great at the enterprise and that's it. And I'm not a fanboi. I bought into WHS, WMC, WP7 AND ZUNE. I know, I know. I feel taken each time. Great ideas but not follow through on those folks parts. Management must really get in the way.

Apple has pushed out 4 updates (1 big one today) since release off WP7. Shame on you Microsoft!

mrTablet said:
Apple has pushed out 4 updates (1 big one today) since release off WP7. Shame on you Microsoft!
Click to expand...
Click to collapse
Holy freakin' hell! There was an update waiting for my new iPhone! Damn! That's some gadget love
My poor HD7 never sees any update love.

The delay of NoDo saddens me simply because I am a verizon customer and with that delay there will inevitably be another delay of the trophy, which means I have to wait LONGER still to get my WP7....sigh

sure haven't said:
If it's because of troubles with Samsung, please just push it out those of us who were smart enough not to get a Samsung wp7.
Click to expand...
Click to collapse
While I agree that if it really is Samsung devices holding it up, that they should push the update out to everyone else, I must defend what I think is easily the best WP7 device on the market. The Samsung takes the best pictures, uses fast NAND memory, has a superb screen, and a sleek form-factor. If that means that I have to wait a few extra weeks for an update, so be it. My phone works great as is. I knew that it wasn't as fully featured as Android or iOS when I bought it, and I knew that the first year or two would likely be bumpy. I was ok with that then, and still am.
Sorry if my having the best Windows Phone causes a delay to updates for your phone.

Seriously guys, how are you that upset because of a delay in the copy and paste update? How much do you even use copy and paste on a smartphone? The only useful thing coming in NoDo is the Marketplace search fix and the speed increase in loading games.
I don't even think I'm going to update mine until Mango, or at least until they have a Homebrew solution. I can deal with the extra 10 seconds to load Fruit Ninja if that means keeping my Homebrew apps and Twin Blades (which will likely go away after the update).
I'd do the update if they included the few annoying features I don't like, like saving the camera settings, pause playback when disconnecting headphones on an incoming call, etc. but not for copy and paste. You lose more updating than you gain.
Apple was able to do updates easily and quickly within months because there was 1 piece of hardware. Obviously all WP7s are not created equal with the Samsung update situation. Microsoft is going to work out the kinks during the first couple updates. It will be smoother and there will be less time between updates as time progresses.
Anyone saying they're going to get rid of their WP7 to get an iPhone or Android is ridiculous. For copy and paste? Really? WP7 outshines those phones by far.

Something about the update stinks.
I really do hope MS makes whatever OEM screwed up pay if that is the case (Samsung).
If it's the carriers, go Apple on them when WP7 gets big, which they will by the way, update fiasco or not.
I guess the main problem is, when we think update, we think easy bug fix. Not this complicated mess we have on our hands.

The whole reason I bought into WP7 was because MS said they'd be handling regular, incremental updates. It looks like NoDo will take seven months to reach end users (assuming it doesn't brick your phone, Samsung users) and adds functionality that was expected in early january.
And apparently the Mango update won't be ready this year.
I remember counselling patience to users about four months ago who were mad there wasn't an update already available, telling them to give it time. I think it's fair to say we've given it time. Maybe WP7 in a year or so, after Mango, but at the moment it's just moving too slowly.

zukа said:
The whole reason I bought into WP7 was because MS said they'd be handling regular, incremental updates. It looks like NoDo will take seven months to reach end users (assuming it doesn't brick your phone, Samsung users) and adds functionality that was expected in early january.
And apparently the Mango update won't be ready this year.
I remember counselling patience to users about four months ago who were mad there wasn't an update already available, telling them to give it time. I think it's fair to say we've given it time. Maybe WP7 in a year or so, after Mango, but at the moment it's just moving too slowly.
Click to expand...
Click to collapse
If MS can rearrange its WP7 business model to focus on just one supreme quality handset, and keep complete control over every aspect of it from design and functionality to updates, I could see WP7 having a chance. With Nokia on board, MS has access to quality hardware. MS has it's "Foxconn" in Nokia that would allow it to have the supreme quality. If they will just do it...

You know what, this is exactly what microsoft needs to do with WP

one sided promise from microsoft (re:updates) is pure fail. all parties should be brought onboard and each held accountable
http://www.engadget.com/2011/05/10/google-partners-with-oems-and-carriers-to-guarantee-android-upda/

Wow, I saw AT&T on the picture, I must relook at it.

It will never happen because all the OEM's and carriers involved seem to want Microsoft and WP7 to fail.

Look at the Zune hardware. My brother had a Zune since Day 1 and he got every update and new release from Microsoft, no problem. I don't think it's a Microsoft issue, I think it's a carrier issue.

Well, that announcement says Android phones will be supported for 18 months. It doesn't say updates will be instant, OEMs won't take weeks to develop ROMs and carriers won't take weeks "testing" them.

vangrieg said:
It doesn't say updates will be instant, OEMs won't take weeks to develop ROMs and carriers won't take weeks "testing" them.
Click to expand...
Click to collapse
if you read the live update, it says:
"12:34PM New guidelines! Man, this is going to be huge. Google's laying out a timeline for how long it'll take a device to get updated once a new build is let loose, as well as how long it'll be updated beyond that."

Google and Apple are both more powerful and influential in the mobile space than Microsoft right now. I don't think Microsoft is really in the position to dictate anything to anyone right now.

And what exactly are these guidelines? Three days for a new ROM from HTC with a new Sense on it?
I mean, this is great news for Android, but there's nothing so far that says anything real about what the update experience will be.
I know it's trendy to bash MS, but WP7 has seen four updates already. And the last one was cumulative, by the way.

I don't know, I have been receiving my updates when MS release them; other than the first one that took one or two weeks every other have been the same day (but I’m not in USA).

http://www.engadget.com/2011/05/10/google-clarifies-18-month-android-upgrade-program-details-far-f/
When pressed about how long it'd take updates to flow to phones after given the thumbs-up by Google itself, there's no hard news to report. In fact, the details there are still being hashed out.
To quote Google, "It's a logistics problem." We can only imagine. Trying to get every Android partner to follow a timeline for releases has to be a complete and utter nightmare, but the company seems certain that these stipulations won't cripple anyone's ability to innovate on their skins (or have too little time to make the needed changes).
We would've loved to hear a specific figure that we could start holding phone manufacturers to, but alas, it isn't to be. The only hard number thrown out today is 18 months. That's how long future hardware will be in the support cycle (at least, anyway), so you'll "soon" be able to count on your next Android device receiving all applicable updates for 1.5 years after purchase.

The guideline is yet to be hashed out. That's why they practically included everyone in the group to come up with a guide line. The only reason AT&T is included is because AT&T wants to make sure the final guideline doesn't put it in the spotlight again, like must release updates within 6 months of Google release That will never happen. I'm pretty sure the final guide line will be 12-month (from Google release the code and you see it on your phone), i.e. totally worthless and waste of time. Android is an open source platform, Google has no say about who can use the code and when they need to release the updates. The only thing Google can do is withheld Android market support.

And if they take longer than the set time frame? What happens?
Sent from my SGH-i917 using XDA Windows Phone 7 App

Nothing would happen. It is called guide line, not rules.

Well then, that'll really be a game changer then... /sarcasm
Where is the news in this?
Sent from my SGH-i917 using XDA Windows Phone 7 App

munkeyphyst said:
Well then, that'll really be a game changer then... /sarcasm
Where is the news in this?
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
There is none. FWIW MS has "guidelines" on updates as well, i.e. that carriers cannot block two consecutive updates.
-R

I smell a publicity fail from Google.

Well I have a wp7 and an android phone, I have to say there is no reason the OEMs cannot make their addtions such as the sense UI to be a replacement, that can be removed and updated seperately from the core OS. If they did that then it would allow for quicker updates.
In the past there were almost no updates done to phone other than small ones that were carrier specific (ie settings or patches) but major upgrades did not really happen. I would not be surprised if eventually updates to the phones to start costing money, much like a new version of OS X or a new version of windows does on a PC.

It's not a timeline.
It's just enforcing devices to be supported for 18 months.
It doesn't mean the manufacturers/carriers will have x amount of days after an android update to release said update. They can still release a phone with FroYo, and take 17 months to release gingerbread for that phone.
Also, it depends on whether the device's hardware supports the update and knowing Andorid manufacturers like HTC they'll just put a ROM chip too small to take any major updates in the phone, etc. Your Evo 4.0 can't support Sense 3.0? Good luck getting that update! HTC will not "downgrade" an Evo 4G from Sense 2 to Stock Android...
They are still trying to get the details panned out, but I'm not getting my hopes up. There are still phones out there sending SMS/MMS to the wrong contacts because the manufacturers don't even prioritize security updates for their phones (which, IMO, is a MUCH bigger issues than even large feature updates...). Android is a huge, hot mess when it comes to updates.

bill.g said:
Well I have a wp7 and an android phone, I have to say there is no reason the OEMs cannot make their addtions such as the sense UI to be a replacement, that can be removed and updated seperately from the core OS. If they did that then it would allow for quicker updates.
In the past there were almost no updates done to phone other than small ones that were carrier specific (ie settings or patches) but major upgrades did not really happen. I would not be surprised if eventually updates to the phones to start costing money, much like a new version of OS X or a new version of windows does on a PC.
Click to expand...
Click to collapse
Are you a developer?
Those aren't themes. They're deep customizations many of which have access to parts of the system that would require a "normal" app to run with Super User permissions. You can't release much of that as an App in the marketplace... Not to mention, they would just end up getting pirated by everyone and at worse breaking a bunch of phones that weren't designed to run the software (freezing them, reboot loops, making them unbootable, etc.).
There's also the issue of drivers, because different manufacturers use dispirate hardware configurations with screens, SoCs, cameras, etc. from dispirate sources. Getting all of that to work on an update is MUCH harder than getting the skins functional.
You people (generally speaking) really think the skins are the issue? They are not. Android (specifically, Linux) is the issue. The skins are easy as hell. The latest Epic 4G Gingerbread Leak has a working TouchWiz, but most of the phone/smartphone functionality is broken. That's a great example on just how easy porting the skins form version to version is. Skins typically aren't that sensitive to kernal ABI changes - device drivers ARE.
The fact that Android is based on Linux by default ensures that updates will have issues because it inherits many of Linux's issues. A Windows Mobile 6.0 update could in many cases just reuse drivers developed for Windows Mobile 5.0the same way Windows 7 can use many Windows XP drivers without any issues.
Linux doesn't have this type of backward/forward compatibility. That's why those leaked updates often have close to nothing working on them (No Wifi, no calls, no this, no that, etc.). Linux doesn't have a stable ABI for driver developers. Kernel updates can break any and/or everything. This means that the turnaround for updates is much longer than it will be for something like WP7.
The biggest issue with Android is the fact that Manufacturers and Carriers do not even prioritize critical security updates, and Google seems intent on not patching and quickly propagating patches for exploits used to root devices. Which is nice for tinkerers, but can be an issue when a malware uses that exploit on someone's device to perform malicious actions...

N8ter said:
It's not a timeline.
It's just enforcing devices to be supported for 18 months.
It doesn't mean the manufacturers/carriers will have x amount of days after an android update to release said update. They can still release a phone with FroYo, and take 17 months to release gingerbread for that phone.
Click to expand...
Click to collapse
I'm pretty sure they said timely updates. Which means they are going to work out some sort of guidelines on how long it takes for the updates to get pushed out. What that actually is remains to be seen though.

[Q] Android 5.0 Jelly Bean

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.

An news on 4.0.4 upgrade for gsm

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