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.
Related
Since i see there is another update in the developement section (EPE54B) when do you suppose ERE36B is gonna be out?
_-..zKiLLA..-_ said:
Since i see there is another update in the developement section (EPE54B) when do you suppose ERE36B is gonna be out?
Click to expand...
Click to collapse
Maybe never. Google will release an update once they have one with all the fixes and updates they want to include. These leaked updates could just be internal "updates" for testing a handful of the changes Google wants to make, etc.
Great question. as far as i can remember every update has left at least some issues that existed before it. So I doubt Google is fixing a whole lot with the next update. Meaning it will fix stuff but I can't imagine what they might be waiting for.its been a long time since I've heard or read an official statement by Google regarding fixes for Android. I wish they'd let us know at least a very rough idea of what to expect regarding fixes and what part of what year to expect it. Surely they can at least estimate which 3 month period might be blessed with some software fixes...there's so much to look forward to its like Christmas if nobody knew when Christmas was or if it was going to even happen
I completely agree maverick. I've been anticipating ere36b for a while as i myself have a problem still with my 3g staying on 3g. In phoenix even, which surprises me as i thought it was a strong 3g area for t-mobile.
DMaverick50 said:
Great question. as far as i can remember every update has left at least some issues that existed before it. So I doubt Google is fixing a whole lot with the next update. Meaning it will fix stuff but I can't imagine what they might be waiting for.its been a long time since I've heard or read an official statement by Google regarding fixes for Android. I wish they'd let us know at least a very rough idea of what to expect regarding fixes and what part of what year to expect it. Surely they can at least estimate which 3 month period might be blessed with some software fixes...there's so much to look forward to its like Christmas if nobody knew when Christmas was or if it was going to even happen
Click to expand...
Click to collapse
i think we should all be confident that the N1 is going to get its updates. i had the Hero before and THAT was a pain. you had to wait for Google to make the update, HTC to add/remove changes in their update and then finally Sprint had all the power of when we actually received it. having an updated phone is one of the main reasons i have the N1. there will be no greener grass for some time for N1 owners.
uansari1 said:
Maybe never.
Click to expand...
Click to collapse
Dude!!! You're being a killjoy there - don't spazz the gazm bro.
And on top of this, would any updates remove apps, data, messages, photos, browser info etc we already have on the phone...?
No, same as ERE27 didn't.
run a custom rom and your "waiting for updates" will drastically be reduced....Stay stock and "wait for the man".....Your choice
martin0285 said:
run a custom rom and your "waiting for updates" will drastically be reduced....Stay stock and "wait for the man".....Your choice
Click to expand...
Click to collapse
Or you can root it and lose you warranty...(What if something really decides to happen?) Why not wait until you've had the phone for awhile? Lol
First thing i lose when i get a new toy, is the warranty
I expect Google to release an update within the next month. If they don't expect alot of news site to be on there asses bout the two main problems most users are having..
ram130 said:
I expect Google to release an update within the next month. If they don't expect alot of news site to be on there asses bout the two main problems most users are having..
Click to expand...
Click to collapse
the next update will probably come when flash is available so who knows when that will be
ram130 said:
I expect Google to release an update within the next month. If they don't expect alot of news site to be on there asses bout the two main problems most users are having..
Click to expand...
Click to collapse
Touchscreen and 3G?
/nod
both are in pretty decent shape if you load the last leaked update.
Devastatin said:
/nod
both are in pretty decent shape if you load the last leaked update.
Click to expand...
Click to collapse
I still think the touchscreen issue that some describe is a hardware defect, and that the 3G issue is just a problem with weak 3G saturation on T-mobile. I don't have either problem, and I assume that's the norm.
uansari1 said:
I still think the touchscreen issue that some describe is a hardware defect, and that the 3G issue is just a problem with weak 3G saturation on T-mobile.
Click to expand...
Click to collapse
It's not a hardware defect, it's just the way the screen is... Lousy mistake on HTC/Google part to not have what should be considered "Standard" nowdays on what was deemed a "Superphone" or flagship phone.. And what I mean by standard is "true multitouch" not just "oh, it can do pinch to zoom, yes..."
Hogwash
It is multitouch by design. Just 2 fingers. The current iteration can not accurately discern more than 2 fingers.
uansari1 said:
I still think the touchscreen issue that some describe is a hardware defect, and that the 3G issue is just a problem with weak 3G saturation on T-mobile. I don't have either problem, and I assume that's the norm.
Click to expand...
Click to collapse
The touchscreen issue isn't a hardware defect, its a hardware limitation... supports just 2 touches at a time.... thats more than enough ....cant use more than two fingers at a time (unless u consider ur phone a psp )........ nexus one offers a very good hardware at 530 $$... so i'm satisfied ....
tropmonky said:
It's not a hardware defect, it's just the way the screen is... Lousy mistake on HTC/Google part to not have what should be considered "Standard" nowdays on what was deemed a "Superphone" or flagship phone.. And what I mean by standard is "true multitouch" not just "oh, it can do pinch to zoom, yes..."
Hogwash
Click to expand...
Click to collapse
faraz1992 said:
The touchscreen issue isn't a hardware defect, its a hardware limitation... supports just 2 touches at a time.... thats more than enough ....cant use more than two fingers at a time (unless u consider ur phone a psp )........ nexus one offers a very good hardware at 530 $$... so i'm satisfied ....
Click to expand...
Click to collapse
I was referring to the "touchscreen calibration" problems or the touchscreen freaking out, that people have mentioned in some instances. I've never had THOSE issues.
As for the MT "issue"... I see it as a limitation. If you don't like it, then return the phone and wait for the Nexus 2.
http://forum.xda-developers.com/showthread.php?t=751518&page=10
Good news, hopefully its legit and its software.....
Here's a video of proof. http://www.youtube.com/watch?v=FJ65sS8nbRE&feature=youtube_gdata_player
Update on compass: jhego says it works, also says compass view works in google maps... he also used gps navigation for 15 mind straight without losing the route .... some good looking stuff...
Originally Posted by smashpunks Awesome. Thanks again. This will put my mind at ease and I can sleep well.
Originally Posted by smashpunks Awesome thanks for this update.. one last thing if ya could... check google maps street view in compass mode... no hurry just wondering.. may be a seperate fix but still interesting to know.. Thanks again for your testing...
Man, that's sick! I haven't used that mode before. I can tell you that it works__________________(2007-2008) CID/SIM Unlocked ATT Tilt(2008-2010) Unlocked Blackberry Bold 5.0.0.681(2010- Current) Rooted Samsung Captivate
UPDATE 2: some people are reporting no fix or worse... hmmmm.. what's going on. Half say its getting great locks and others not... maybe its a location thing?
Farkkkkk
If the GPS is fixed in this rom, can we have some crow for the people saying it's not fixable via firmware?
heygrl said:
If the GPS is fixed in this rom, can we have some crow for the people saying it's not fixable via firmware?
Click to expand...
Click to collapse
Agreed. People getting 8 satellites locked..... awesome
http://www.youtube.com/watch?v=FJ65sS8nbRE
6/6 INSTANTLY! 7/7 shortly after... yep, I'd say it's fixed
heygrl said:
http://www.youtube.com/watch?v=FJ65sS8nbRE
6/6 INSTANTLY! 7/7 shortly after... yep, I'd say it's fixed
Click to expand...
Click to collapse
Yes. This makes me very very happy.. now IMO its a perfect device... (hope not speaking to soon but I'd say its fixed also)...
Neat.
Has anyone been able to test out the compass? Whoever is making these videos, could someone ask them to demo Google Sky Map / Street View?
but this isnt for the vibrant right? or can it be ported over since they are so close to each other?
Jon C said:
Neat.
Has anyone been able to test out the compass? Whoever is making these videos, could someone ask them to demo Google Sky Map / Street View?
Click to expand...
Click to collapse
I'm having the dude test the compass... also even if this exact thing don't work on vibrant.. its proof that its software and fixable
.. that's all I really wanna know...
Update on compass soon....
It's the firmware for the Captivate, which flashes for different radios and so forth. It could be ported, but it would be a lot of unnecessary work.
To be honest, I find the idea of flashing different ROMs to be stressful. I stopped using my jailbroken iPhone because I grew tired of keeping up with flashing and jumping through hoops. I just want Samsung to fix the phone with an OTA, so I can go back to my normal life.
So, we have no word on a fix for the Vibrant. But one can assume that a fix on AT&T will find itself on the T-Mobile device.
Jon C said:
Neat.
Has anyone been able to test out the compass? Whoever is making these videos, could someone ask them to demo Google Sky Map / Street View?
Click to expand...
Click to collapse
Your the dude wanting to bail on the vibrant right? Its cool I understand . Hopefully this changes your mind...
Jon C said:
Neat.
Has anyone been able to test out the compass? Whoever is making these videos, could someone ask them to demo Google Sky Map / Street View?
Click to expand...
Click to collapse
Jon C said:
It's the firmware for the Captivate, which flashes for different radios and so forth. It could be ported, but it would be a lot of unnecessary work.
To be honest, I find the idea of flashing different ROMs to be stressful. I stopped using my jailbroken iPhone because I grew tired of keeping up with flashing and jumping through hoops. I just want Samsung to fix the phone with an OTA, so I can go back to my normal life.
So, we have no word on a fix for the Vibrant. But one can assume that a fix on AT&T will find itself on the T-Mobile device.
Click to expand...
Click to collapse
The fix is leaked from samsung .. we will get one too. Point again is its fixable, we never knew this before till now.
Although its still not been said if its 100% working.. could be a start though
No, it's a great piece of encouragement. Still, unless something is said soon, I will probably return my phone until the official fix is out. I can always purchase it again at a later date. It's encouraging to see a leak from Samsung fix the problem, but I'm sure you can understand: $500+ is a lot to spend on a phone.
Keep delivering the good news. Hopefully the Compass has been fixed as well. I really love TouchWiz, and was dreading the possible jump to HTC Sense.
Jon C said:
No, it's a great piece of encouragement. Still, unless something is said soon, I will probably return my phone until the official fix is out. I can always purchase it again at a later date. It's encouraging to see a leak from Samsung fix the problem, but I'm sure you can understand: $500+ is a lot to spend on a phone.
Keep delivering the good news. Hopefully the Compass has been fixed as well. I really love TouchWiz, and was dreading the possible jump to HTC Sense.
Click to expand...
Click to collapse
I can understand your view.
For me it is also encouraging that samsung really is trying .
This is encouraging news. Hopefully it's true and I can quit obsessing with it
This gives me a damn hard-on.
My phone locked & rebooted* itself twice today, while trying to use GPS. And I was in Mountain View, even - buncha bull****.
-bZj
*when it does this routine, it resets the volume on the system (thus the startup sound) to maximu8m - makes me even angrier!
heygrl said:
If the GPS is fixed in this rom, can we have some crow for the people saying it's not fixable via firmware?
Click to expand...
Click to collapse
don't recall anyone saying it couldn't be fixed - can you point us at one?
the consensus opinion has been no one knew whether it was firmware or software
and btw, while this is good news, we're not totally certain this is a permanent "fix"
if it's still working in 2 or 3 weeks for the folks that installed it, then it might be considered a fix
larryccf said:
don't recall anyone saying it couldn't be fixed - can you point us at one?
the consensus opinion has been no one knew whether it was firmware or software
and btw, while this is good news, we're not totally certain this is a permanent "fix"
if it's still working in 2 or 3 weeks for the folks that installed it, then it might be considered a fix
Click to expand...
Click to collapse
Regardless its getting 8 satellite locks for a lot of people .. that's never happened before ... this is a leak so not even official. So official may even be better ....
I was very concerned about the compass as I wasn't convinced that could be fixed via firmware basd on what I saw in the GPS service screens (seemed laggy even straight from the device). Eugene373 posted a fix to GPS for rooted phones here ://to.ly/5TFy (add http to follow the link). I installed it and it fixed both GPS and compass for me personally. This for me was proof positive tha there will be an official Samsung fix released to solve this issue.
K
larryccf said:
don't recall anyone saying it couldn't be fixed - can you point us at one?
the consensus opinion has been no one knew whether it was firmware or software
and btw, while this is good news, we're not totally certain this is a permanent "fix"
if it's still working in 2 or 3 weeks for the folks that installed it, then it might be considered a fix
Click to expand...
Click to collapse
ignored
sfsdf
down8 said:
This gives me a damn hard-on.
My phone locked & rebooted* itself twice today, while trying to use GPS. And I was in Mountain View, even - buncha bull****.
-bZj
*when it does this routine, it resets the volume on the system (thus the startup sound) to maximu8m - makes me even angrier!
Click to expand...
Click to collapse
Mine has been doing it for a couple of weeks and I finally got fedup with this routine and called TMO and complained. I'm getting a replacement Vibrant in 3 days or so but I'm not holding my breath on it working any better really although I hope that it won't freeze and reboot at least. This official fix can't come fast enough because this GPS caused freezing and rebooting is really getting to me at this point.
I still could not get a GPS lock even with the new radio and the DK05 ROM was still to buggy for me. So I went back to stock then back to 4.2 release of Froyo. I needed the GPS so I flashed the radio to the DK05 release and got 12 Sats in just a few seconds. This was the only combination hat has worked for me. Maybe it's just a fluke but it works for me even after reboot. Just thought I would share. I don't know why the rom version would matter 4.2 and DK05 radio gives me orking GPS.
Hope this helps someone......
Sent from my SPH-D700 using XDA App
Well known fix for a well known bug. Don't use GPS for a few days, then try it and report back, please.
Sent from my SPH-D700 using XDA App
herzzreh said:
Well known fix for a well known bug. Don't use GPS for a few days, then try it and report back, please.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I feel like there should be a flashing red line at the top of every forum post
"If you reboot your phone and your gps works, ITS NOT FIXED!"
herzzreh said:
Well known fix for a well known bug. Don't use GPS for a few days, then try it and report back, please.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I understand where your coming from but that's not what I was referring to. My point was that I could barely EVER get a GPS lock until now. I tried the "leaked GPS fix" in the other thread and if it worked it wouldn't after I rebooted the phone. I was simply reporting that with this combination of Radio and ROM that it worked very well. Before it would stop working when I rebooted but it locks right on now.
I am very aware the "Well known fix for a well known issue". This was different for me and I thought it might work for someone else still having issues.
I wasn't trying to be a **** or anything. What you did just forced a complete cache wipe and then a download of new data. Unless you use it daily and unless you have it set to cold start, I guarantee you that your issues will be back.
Sent from my SPH-D700 using XDA App
herzzreh said:
I wasn't trying to be a **** or anything. What you did just forced a complete cache wipe and then a download of new data. Unless you use it daily and unless you have it set to cold start, I guarantee you that your issues will be back.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
No problem. I guess my whole point was I had done the cache wipes many times with no positive outcome. This was really the first time I was able to use the GPS on my phone. Maybe it was just coincidence but I tried the cache wipe and anything else I could find to get the GPS to lock and this was the only thing that ever worked for me.
No GPS satellites in view
I wanted to share since I have the same problem...
I am now on my third epic as the first two would not even see a satellite for anything. Not sure if anyone else may be this unlucky but the first two were definitely defective. Third one works like a charm.
I do work for Sprint, and I've seen how shoddy quality control can be for some of the devices, but it seems like they almost rushed these out of the factory. Only had two customers come in that actually required a replacement, as the others were just the standard GPS issues, but man is it frustrating for this kind of phone.
I remember when I got my original touch that didn't even have gps enabled yet! How many years old and even with froyo on it, gps works near instantly for all tests.
But anyway, just wanted to share as I don't know that everyone who has been having issues has verified if they are even seeing satellites available.
ramsestut said:
I wanted to share since I have the same problem...
I am now on my third epic as the first two would not even see a satellite for anything. Not sure if anyone else may be this unlucky but the first two were definitely defective. Third one works like a charm.
I do work for Sprint, and I've seen how shoddy quality control can be for some of the devices, but it seems like they almost rushed these out of the factory. Only had two customers come in that actually required a replacement, as the others were just the standard GPS issues, but man is it frustrating for this kind of phone.
I remember when I got my original touch that didn't even have gps enabled yet! How many years old and even with froyo on it, gps works near instantly for all tests.
But anyway, just wanted to share as I don't know that everyone who has been having issues has verified if they are even seeing satellites available.
Click to expand...
Click to collapse
Thanks. I was seeing 0/0 in GPS Status. No matter what I did I had nothing. I was swapped out a few times as well but for the capacitive buttons. I got it working pretty good now. Now I get 12/12 outside and like 7/7 inside. Stas seen/Sats locked
I'm unclear on which version is "froyo 4.2". Do you mean the DJ29 leak? NVM. I didn't put 2 + 2 together; you were referring to the 4.2 revision of leaked DJ29.
I'm basically in the same boat OP was, I'm flashed all the way up to the latest DK05 ROM and modem but GPS is still a crapshoot.
At least it's finally looking like the next OTA will for-sure fix the GPS problems. With Samsung supposedly never acknowledging the problem I was worried.
Poryhack said:
At least it's finally looking like the next OTA will for-sure fix the GPS problems. With Samsung supposedly never acknowledging the problem I was worried.
Click to expand...
Click to collapse
From reading the anecdotal reports of uncontrolled testing here, I've seen no evidence of that at all. Maybe it's fixed, and maybe it isn't. You should still be worrried.
People are overcoming the novel problem particular to installing the leaked version. This problem, apparently an artifact of the way the leaked firmware is installed, was breaking GPS completely at the outset.
But that is not the same thing as saying that Samsung has fixed the longstanding GPS bug on the Epic. In fact, having the GPS work initially is a symptom perfectly consistent with that bug. (You can get the same effect just by doing of factory reset of your stock Epic running Eclair DI18.)
The Epic's GPS bug occurs over time, as the GPS almanac and ephemeris cache becomes out of date or corrupt. As far as I can see, no one running the leaked firmware has tested the use cases that can replicate the bug on the stock Epic.
boomerbubba said:
The Epic's GPS bug occurs over time, as the GPS almanac and ephemeris cache becomes out of date or corrupt. As far as I can see, no one running the leaked firmware has tested the use cases that can replicate the bug on the stock Epic.
Click to expand...
Click to collapse
I'm not doubting that this is a bug, but my Epic has NEVER been able to get quick and accurate locks, and I have tried after countless wipes. Unless it's just bad hardware there is more then one bug in play here.
The OP's situation seems near-identical to mine so I'm hopeful that trying this might actually have results.
Poryhack said:
At least it's finally looking like the next OTA will for-sure fix the GPS problems. With Samsung supposedly never acknowledging the problem I was worried.
Click to expand...
Click to collapse
First the fact that samsung hasn't acknowledge the problem is not "supposed" it is a documented fact. They refuse 100% to acknowledge the problem and in fact say on the record all GPS issues on Epic were fixed at release.
Second there is zero evidence that the next OTA will do anything for GPS on Epic, where do you even get the slightest indication that is the case?
Poryhack said:
I'm not doubting that this is a bug, but my Epic has NEVER been able to get quick and accurate locks, and I have tried after countless wipes. Unless it's just bad hardware there is more then one bug in play here.
The OP's situation seems near-identical to mine so I'm hopeful that trying this might actually have results.
Click to expand...
Click to collapse
the OP situation is totally different an yours, it has to do with flashing, which killed the GPS on many Epics. IE not an issue with time to first fix, interrmtant falure to fix, or accuracy, but a total killing of GPS.
The fix implemented restores GPS to the same function state as the rest of ours, generally working with some number of failures to flush cache and thereby no fix locaiton on occassion
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
Should'nt we all start posting annoying threads on Facebook to Motorola and the MS2?.. I already started see here -> http://www.facebook.com/topic.php?uid=121867580498&topic=20102
If we all do that.. they maybe atleast see it.. and think 0,0001 second about it.. thats better than nothing..!!!!
I wist it'd be that simple. With the first Milestone they've proven that they don't know what support is.
I seriously doubt it will have any effect. We all know about the MP3 problems and wrong keyboard layout... The device has been on the market for about six months and there's still no sign of a fix for those problems. Kind of annoying, having a euro sign on the keyboard, but not being able te use it.
...and Motorola knows about those issues. They simply choose not to fix them.
these two bugs are not present in custom firmware argent2stone...
try it
I already fixed those problems in the stock ROM for now I actually quite like Blur, so I don't need it (partially) removed. Unless Argen2Stone performance is undeniably better than Stock. Furthermore I don't know if it fixes the AAC problems, so I don't feel like reinstalling it now...
Still, that isn't the point. It's about the fact Motorola should've pushed a fix for those issues. They're minor, highly annoying and not everybody wants to root their phone to fix such issues.
w0ndersp00n said:
Still, that isn't the point. It's about the fact Motorola should've pushed a fix for those issues. They're minor, highly annoying and not everybody wants to root their phone to fix such issues.
Click to expand...
Click to collapse
Absolutely. +1