Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
They must also fix
1)Choppy browser with and without flash.....
2)Random freeze of the gingerbread launcher...
slateac said:
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
Click to expand...
Click to collapse
I think it was posted that the reboot fix was coming, but not the loss of data.
Maybe I am just a lucky one, but I have had Nexus S since release and have only had a "random reboot" once; and no data signal loss issue AFAIK like Engadget has described. I have owned three Nexus Ss.
There are other issues, though, making it clear 2.3 is not bug free.
fchipm said:
Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Click to expand...
Click to collapse
and they didn't even give us XDA credits
Perhaps 2.4 is coming sooner than planned and the fixes will be implemented in that? Just a wild guess.
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
i'm hoping they fix the quirky back button as well. that thing is driving me crazy!
I recommended the nexus s to my girlfriend, but seeing all these issues are making me regret it :\ there are no fixes/workarounds?
Sent from my SPH-D700 using XDA App
aaaaaand... 10char
Update: Huzzah! Just got a note from Google saying: "All of the issues described in the post are resolved and will be fixed with an OTA that will go out soon." Feel free to start mashing that "system updates" menu item.
Click to expand...
Click to collapse
that was fast.
Weird. I haven't had a single one of the issues described in any form. However, the browser issues do make me angry.
Glad there is a hotfix on the way (for the issues mentioned, that is, not necessarily the browser issues)!
The only issue that regularly bothers me is the vanishing ringtone one. It's not exactly critical from a utilitarian standpoint, but I think it's stupid that I should have to root and move files around my phone in order to set a custom ringtone. Still, I'm far too happy with pretty much everything else to switch.
I think one major sticking point with the Nexus S is that we have a fairly lengthy list of at least semi-common issues, but in several cases it's not clear whether those are hardware- or software-related. This is troublesome because the latter may be reasonably expected to get fixed in OTAs, while the former will probably only ever be resolved through workarounds, if at all.
I would be very pleased if Google were more transparent about what it's working on, or at least aware of, even if they (understandably) don't want to commit to fix dates. As a user, just knowing the basic nature of these problems and that they are being acknowledged would go a long way towards improving customer satisfaction in my book.
SooSpecial said:
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i read that there will be an ota update, but (maybe its a noob question) if your rooted will you still receive the update, and if so will it unroot the phone??
Fix the GPS!!!!!
Fix the keyboard: http://www.youtube.com/watch?v=RUZdvr6Pdjk
Discussed more in depth at this thread: http://forum.xda-developers.com/showthread.php?t=932838&page=13
Related
Anyone having issues after installing the leaked OTA update? I've noticed my alarms are no where near reliable anymore. I thought maybe the issue was the stock clock app, but I'm seeing the same thing with "Alarmed Lite". While this isn't a huge problem, I'm interested in seeing if anyone else has noticed anything similar. Right now at a cross roads. I love the updated camera, but I do rely on my phone for alarms.
My only other issue right now is my Karnivor (MQ2'ed, midblocked, Yakuza'ed) is extremely inefficient, and the Yak doesn't seem to recognize a normal trigger pull. Guess that's a topic for another forum though....
the ota has given countless problems. thats why i stayed away, and thats why.vzw never released it.
Sent from my Incredible using XDA App
jdkoreclipse said:
the ota has given countless problems. thats why i stayed away, and thats why.vzw never released it.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Countless problems like what? What is your source for that?
btpowers said:
Anyone having issues after installing the leaked OTA update? I've noticed my alarms are no where near reliable anymore. I thought maybe the issue was the stock clock app, but I'm seeing the same thing with "Alarmed Lite". While this isn't a huge problem, I'm interested in seeing if anyone else has noticed anything similar. Right now at a cross roads. I love the updated camera, but I do rely on my phone for alarms.
My only other issue right now is my Karnivor (MQ2'ed, midblocked, Yakuza'ed) is extremely inefficient, and the Yak doesn't seem to recognize a normal trigger pull. Guess that's a topic for another forum though....
Click to expand...
Click to collapse
stop using a task killer if you are, or check to see if you are killing anything that could be affecting your alarm. I used to use taskiller until I did some reading and I must say the system runs with less quirks now that I don't use one...
If you do not use a task killer, it may just be an issue with the ota, can't say for sure... as per the post above mine, I did read that the ota may not have been released because it may be incorporated into a following ota (possibly froyo) not because of "countless" issues...
BossMafia2 said:
Countless problems like what? What is your source for that?
Click to expand...
Click to collapse
look at all the threads about "my phone wont work after the ota"
Sent from my Incredible using XDA App
jdkoreclipse said:
look at all the threads about "my phone wont work after the ota"
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I see no threads like that. I do, however, see some threads about getting it to work 100%. I also know from personal experience that any issues are user error, as I had/have the ota installed and have no issues with it whatsoever.
I use my alarm for morning wake ups everyday and it has been flawless. The update gave me no issues that I can see and I've been running it at least a week.
BossMafia2 said:
I see no threads like that. I do, however, see some threads about getting it to work 100%. I also know from personal experience that any issues are user error, as I had/have the ota installed and have no issues with it whatsoever.
Click to expand...
Click to collapse
my bad.
Sent from my Incredible using XDA App
I haven't had a single problem with my OTA update either. But the hit or miss must be why they haulted the release. Can't wait for Froyo as is the same with everyone though.
If what's been going around the internet about 2.2 being released around the end of the month, that could also be why they pulled it. Changed their minds about the update and decided to just go full froyo. Or it could be a test ota meant only for devs to test out the new radio and drivers. At this point it's all speculation...but anyway this is getting offtopic.
To the OP, it almost sounds like you have some kind of auto task killer installed or something...
BossMafia2 said:
If what's been going around the internet about 2.2 being released around the end of the month, that could also be why they pulled it. Changed their minds about the update and decided to just go full froyo. Or it could be a test ota meant only for devs to test out the new radio and drivers. At this point it's all speculation...but anyway this is getting offtopic.
To the OP, it almost sounds like you have some kind of auto task killer installed or something...
Click to expand...
Click to collapse
I actually don't run a task killer, and when I did (pre ota update) I excluded the clock. I use SystemPanel now. Wonder if it's worth it to roll back and try again. Anyone know if it's safe to go back to the previous hboot and then reapply the patch?
My alarms work just fine, have had absolutely no issues with ota update.
Anyone else have problem with FM radio after OTA?
I've rooted 4 incredibles with this ota and only one had a problem of not being able to hear when on a phone call but if you turn speaker on it would work and you could hear it was pretty weird
I had constant reboots with the leaked OTA so I went back to stock. I'll wait for the 2.2 OTA to come out and for Unrevoked to hack it up.
Yay. I can confirm the following bugs after using OTA ED01 for a couple hours:
1) 50% time w/o signal bug still there. Still need airplane toggle after boot.
2) Browser scrolling choppy as ever.
3) Pop email client still snaps to top of list after reading each email.
4) battery issues / wakelock needs more testing
Now then, we know Samsung and VZW were not working on fixing any bugs in the last several months that they have been sitting on this code. All bugs from froyo leaks 2.5 months ago are still in there.
Seems to me there was 0 priority put on this update, since it was delivered extremely late and still chock full of bugs. My assessment is Samsung is way understaffed AND integrating bing caused some negative interactions between the companies involved. I won't buy another Samsung... and probably should move off of VZW.
Scrappy1 said:
Yay. I can confirm the following bugs after using OTA ED01 for a couple hours:
1) 50% time w/o signal bug still there. Still need airplane toggle after boot.
2) Browser scrolling choppy as ever.
3) Pop email client still snaps to top of list after reading each email.
4) battery issues / wakelock needs more testing
Now then, we know Samsung and VZW were not working on fixing any bugs in the last several months that they have been sitting on this code. All bugs from froyo leaks 2.5 months ago are still in there.
Seems to me there was 0 priority put on this update, since it was delivered extremely late and still chock full of bugs. My assessment is Samsung is way understaffed AND integrating bing caused some negative interactions between the companies involved. I won't buy another Samsung... and probably should move off of VZW.
Click to expand...
Click to collapse
What's a better option in your opinion besides Samsung? Are you more pissed at Samsung or Verizon?
Sent from my SCH-I500 using XDA App
My frustration is primarily with vzw on this... But I've known, or accepted, that one chooses a wireless service provider by asking "who sucks less?".
Sent from my SCH-I500 using XDA Premium App
Weird, I don't use the email client, but I have not experienced any of those issues. My battery does not drain while sleeping (with bt, gps and data all on) everything is smooth as can be. And I have never had to toggle airplane mode. All these bugs I had in dl30 and eb01, but none at all in this release. Also I have had no screen response issues anymore either. Not saying your wrong just posting my experience as well.
Sent from my SCH-I500 using XDA App
Legato525 said:
Weird, I don't use the email client, but I have not experienced any of those issues. My battery does not drain while sleeping (with bt, gps and data all on) everything is smooth as can be. And I have never had to toggle airplane mode. All these bugs I had in dl30 and eb01, but none at all in this release. Also I have had no screen response issues anymore either. Not saying your wrong just posting my experience as well.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yeah, I have been playing around with it a little, and have found the save thing. No bugs so far.
Sent from my SCH-I500 using XDA App
The only thing that wonders me is new radio. Is is the the same as EC01? It's too soon to ask probably but maybe somebody had missed calls issue with it yet?
SotYPL said:
The only thing that wonders me is new radio. Is is the the same as EC01? It's too soon to ask probably but maybe somebody had missed calls issue with it yet?
Click to expand...
Click to collapse
We'll have to see how it goes fellow chicagoland resident. I odin'd and ota'd to get the new radio and frameworks and files were compared lastnight and there is some differences in the frameworks between EC01 and ED01 so I'm gonna run themeless until I have time to port my theme over to the new frameworks. Initial impression I have is my data speeds are a little higher and more constant. But I'll give it a go traveling about the city today.
Oh, @OP the tws bug is not limited to our device. It's a froyo thing that many devices suffer from. Google it.
good day.
Everything looks good here... Besides battery life. I just did the ota at 9:30 this morning after about an hour **** has drained 30%. Oh well. I was using heavily, im gonna flash the debloated one and wipe bstats and what not to see if I get some improvement.
Sent from my SCH-I500 using XDA App
ajd88 said:
Everything looks good here... Besides battery life. I just did the ota at 9:30 this morning after about an hour **** has drained 30%. Oh well. I was using heavily, im gonna flash the debloated one and wipe bstats and what not to see if I get some improvement.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
If you had display on for an hour 30% drain is normal I think.
I just read the release notes for ed01 posted by kaus... It lists some added bloat, but in many cases contradicts the op of this thread (subject to verification I guess ;-).
Sent from my SCH-I500 using XDA Premium App
Scrappy1 said:
Yay. I can confirm the following bugs after using OTA ED01 for a couple hours:
1) 50% time w/o signal bug still there. Still need airplane toggle after boot.
2) Browser scrolling choppy as ever.
3) Pop email client still snaps to top of list after reading each email.
4) battery issues / wakelock needs more testing
Now then, we know Samsung and VZW were not working on fixing any bugs in the last several months that they have been sitting on this code. All bugs from froyo leaks 2.5 months ago are still in there.
Seems to me there was 0 priority put on this update, since it was delivered extremely late and still chock full of bugs. My assessment is Samsung is way understaffed AND integrating bing caused some negative interactions between the companies involved. I won't buy another Samsung... and probably should move off of VZW.
Click to expand...
Click to collapse
My wife and I have this phone. I am running EB01 Superclean and I just odin'd her phone to stock last night and upgraded to OTA ED01. So far, no time without signal bug, browser does not seem choppy, no wakelocks so far. Maybe you should odin to stock and start fresh if you have not done so already. I think that this can fix a lot of issues. No doubt that after brief testing my Superclean w/ -100 imnuts kernel is kicking the snot out of a stock ED01 froyo so far. But I always give it a week for the battery to calibrate and settle so I will report back.
i also have superclean 2.9.2 (nv). i'm not sure if i want to go back to stock and do the official ota because I finally LIKE my phone for the first time since... November? I really liked it for the first month (Oct) when I thought the OTA was due any day... but since then, not so much. but after installing superclean a week or so ago, suddenly i don't care about the ota. unless i hear from one of you more experienced gurus that it's the way to go, that is. I love that I don't have all that bloat on my phone. If i do the ota, I presume the bloat will come with it, and I've heard of people then cleaning up the phone... how is that different from what I already have? should I stay put or is there a distinct advantage to doing the ota and then cleaning it up? any advice and logic behind it would be appreciated. thanks.
Wife and I both have fasc I odin'd her back to stock took ota she so far has not been able to make calls out off and on all day she could answer tho...?? However.. What pisses me off the most is vzw dropping price and trying to sell this to everyone for mothers day like my mom needs this f/%ked up unsupported phone swindled to her."why yes madam this has the very latest software it has always been our best phone and now your kids can make you the coolest mom ever" scam scam scam or should I say spin spin spin the greatest company on the planet can you hear me now.. Ahh no cause my froyo won't make a call
Sent from my SCH-I500 using XDA App
ilprobu2 said:
Wife and I both have fasc I odin'd her back to stock took ota she so far has not been able to make calls out off and on all day she could answer tho...?? However.. What pisses me off the most is vzw dropping price and trying to sell this to everyone for mothers day like my mom needs this f/%ked up unsupported phone swindled to her."why yes madam this has the very latest software it has always been our best phone and now your kids can make you the coolest mom ever" scam scam scam or should I say spin spin spin the greatest company on the planet can you hear me now.. Ahh no cause my froyo won't make a call
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Well maybe you can do the mature thing and call Verizon instead of *****ing about a problem that ONLY you are having. Or maybe you can try factory resetting it.
Don't *****, that only gets you flamed.
Avelnan said:
Well maybe you can do the mature thing and call Verizon instead of *****ing about a problem that ONLY you are having. Or maybe you can try factory resetting it.
Don't *****, that only gets you flamed.
Click to expand...
Click to collapse
when you pay my bills you can tell me when I can shut up or just read and carrying on with your day.
Sent from my SCH-I500 using XDA App
Avelnan said:
Well maybe you can do the mature thing and call Verizon instead of *****ing about a problem that ONLY you are having. Or maybe you can try factory resetting it.
Don't *****, that only gets you flamed.
Click to expand...
Click to collapse
If you read what he said, he did do a factory reset, he said he odin'ed back to stock..........
jazzyjames said:
If you read what he said, he did do a factory reset, he said he odin'ed back to stock..........
Click to expand...
Click to collapse
I did read, but after that he updated did an OTA. If he already Odined I don't see the pain in doing a reset. Doesn't hurt.
What's up with not being able to download tapatalk either?? I upgraded ota and its still in my purchased list but won't let me install..and when I search it the market doesn't find it.
Sent from my SCH-I500 using XDA App
Has anyone else noticed that you can't delete gmail emails after the update? I delete them and they come right back. This is even with having full 3g service and excellent reception.
Sent from my SCH-I500 using XDA App
Don't worry superclean in my opinion is still better. It has all the great sbrissen mods and its only got a couple very tiny bugs (even though I can't think of one)
Plus all the themes you could ever want AND ec01 themes are fine on super clean... I think I'll just chill with what I got.
rweed said:
i also have superclean 2.9.2 (nv). i'm not sure if i want to go back to stock and do the official ota because I finally LIKE my phone for the first time since... November? I really liked it for the first month (Oct) when I thought the OTA was due any day... but since then, not so much. but after installing superclean a week or so ago, suddenly i don't care about the ota. unless i hear from one of you more experienced gurus that it's the way to go, that is. I love that I don't have all that bloat on my phone. If i do the ota, I presume the bloat will come with it, and I've heard of people then cleaning up the phone... how is that different from what I already have? should I stay put or is there a distinct advantage to doing the ota and then cleaning it up? any advice and logic behind it would be appreciated. thanks.
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
got this from a "sprint rep" on their forums
TiNy-2nz -
I apologize for the frustrations associated with the current issues with the GB release... Please know that we are aware of many of the issues people are experiencing and are working with HTC to resolve them. Although I don't have a time frame now, they will be sending out a patch to resolve issues associated with your device.
SOOO take it for what its worth and maybe there is a hair of hope .....
TInY
hope this is true.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk
I had a prompt to download an update today. I skipped cuz I'm still holding out for root on this update that I'm on. I'm not actually having issues other than I can't root...
sent from my 2.3.3 unrooted piece o ****....
I was also prompted for an update today, after just being prompted for the GB update the other day. I was hoping maybe they were being true to their word and unlocking the bootloader.
It was a rather lengthy update process with two reboots involved.
tiny2nz said:
got this from a "sprint rep" on their forums
TiNy-2nz -
I apologize for the frustrations associated with the current issues with the GB release... Please know that we are aware of many of the issues people are experiencing and are working with HTC to resolve them. Although I don't have a time frame now, they will be sending out a patch to resolve issues associated with your device.
SOOO take it for what its worth and maybe there is a hair of hope .....
TInY
Click to expand...
Click to collapse
Kiduno99 said:
hope this is true.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Not to sound like a douche, but I think it's pretty obvious that Sprint & HTC plan on releasing an update that would fix the problems presented with the GB update.
There was the 4.22 update,GB
Then the 4.24 update,GB fix,
Are you guys saying there is a 3rd update being pushed?
Sent from my PC36100 using XDA App
I'm wondering the same thing...I've already had two updates. I took both of them because I like my evolution stock, only reason I ever rooted my hero is because Sence made it sluggish.
Sent from my SPH-P100 using Tapatalk
at this point in time....i am not confident that we will have any sort of solution in the near future, we will simply have to deal with this horrible android version of gingershitbread, i never tought id hate the awsomeness that is an EVO , but currently...i kind of do, clearing user data, resetting,done it all, it still sucks arse and glitches half the dam time,its horrible, if id have known i would have stayed with stock 2.2 (not because of root but because it actually friggin functioned better)
I waited a couple weeks and did the rooted stock rom, 4.24
Have had no issues after a full week of use.
Sent from my PC36100 using XDA App
the more i think about it you think he said that just to shut me up and so the sprint forums dont get filled up with posts about it ??? I dunno; like the corp store told me; "as long as you can make and recieve calls there is nothing wrong with your handset"
IT suxx to be stock its like having a maseratti that only goes 55MPH
http://androidcommunity.com/asus-confirms-eee-pad-transformer-power-fix-incoming-20110713/
Wonderful news! Still I don't see how this bug was missed. It was one of the first things I noticed when playing with it on the first day I bought it... and it's so widespread... did they not even play around with them first?
This is GREAT news! I was going to send my dock for RMA today! Guess I will wait a little more. If anyone has more news don't hesitate to post: timelines, firmware or hardware fix...
Joël.
So this means that it not the dock itself so people can stop trying to find b60s
Sent from my SCH-I500 using Tapatalk
Me too. I have the RMA package all wrapped up to go. Now I'll wait and see.
This reinforces the value of forums like XDA. Sufficient data has been presented in various threads here to assist ASUS in narrowing down the issue and hopefully fix it. In addition the pressure from members kept the issue in their sights. Hopefully the fix will improve the overall experience and not just fix one issue at the expense of creating another.
w00t!
Hopefully its just a firmware update.
Has this been released yet?
veritas2884 said:
Has this been released yet?
Click to expand...
Click to collapse
No
10 char
I haven't noticed any power/draining problems personally. In fact, I am amazed at the battery life of the tab while docked. But glad that a fix is in the works for those that need it.
Dorkington said:
w00t!
Hopefully its just a firmware update.
Click to expand...
Click to collapse
i believe the article mentions it as a firmware update, but we'll have to see...that and other possible fixes on the horizon in 3.2 are just what is needed in a prod introduction. Sure there's bugs but it only becomes an issue if you don't address them.
teegunn said:
I haven't noticed any power/draining problems personally. In fact, I am amazed at the battery life of the tab while docked. But glad that a fix is in the works for those that need it.
Click to expand...
Click to collapse
I get excellent battery life if I put my ÁT in airplane mode when I'm done. I don't mind waiting 15 seconds for a few emails to download when I take it out of airplane mode.
Dorkington said:
Hopefully its just a firmware update.
Click to expand...
Click to collapse
My dock has already been shipped off for RMA, but I also hope that at least a portion of the issue may be correctable via firmware update. However, there are several reports in this thread (specifically here and here) that indicate that a hardware fix may be required.
In the main thread on dock battery drain, many with the B60 docks are reporting much small drain during standby and power off. So Asus is likely doing something different to the is newest batch of docks, and that means they have a 'fix' already.
So what are they waiting? Unless whatever they did to the B60 batch is hardware, and they need to figure out a software fix to patch the problem in older docks...
The fix is probably rolled into the 3.2 update.
kaylord84 said:
So this means that it not the dock itself so people can stop trying to find b60s
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I wouldn't assume too soon. I got a B60 dock 2 days ago. I also have had a B50 for about 2 weeks. There are noticable battery usage differences between the two in regular use, standy and when the tablet is turned off.
When I assume I make an a.....well you know
Lets wait and see what Asus says and does...
"We will shortly be announcing details on how this will be resolved for our customers."
If it was just a firmware update, they'd probably have said so. As in "We will shortly be releasing firmware to resolve this for our customers."
The only reason I can see for phrasing it in this manner is because they're expecting a hardware update -- which means "details" will be needed to tell customers in each market how to return their docks, what the expected turnaround time is, who pays for shipping, which serial number ranges are included, etc.
I hope I'm wrong, but I deal with decoding public relations-speke every day, and this doesn't read like a simple firmware update to me.
Dorkington said:
w00t!
Hopefully its just a firmware update.
Click to expand...
Click to collapse
Yep, same here! Got my dock from TD...
can anyone confirm if last minor 3.1 update fixed that?
Sent from my Transformer TF101 using XDA Premium App
It does not, from what I see in other posts
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?
Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.
Try flashing a different kernel as that is what bridges hardware and software.
Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium
uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.
I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.
I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.