Related
So before the gingerbread update i was experiencing the nexus one touch screen issue. This issue would happen mostly when the phone would be charging or warm, and the y coordinate of the touch screen would be off by about an inch. (I would post a link to youtube but i can't yet... new member =/ ) So if you try to answer your phone while the defect was active, you couldnt, because touching the slider would be recognized as trying to touch the 'menu' key on the phone.
Anyway, after gingerbread got pushed to my device, i have yet to experience this issue!! i havent been able to find anyone reporting this resolution. i'm extremely please about this because it was becoming a deal breaker after i missed an important call because i couldnt answer my phone due to the issue!!
anyone else experiencing this resolution!?
In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS
Hollow.Droid said:
In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS
Click to expand...
Click to collapse
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
this is where I was at before the push, i was seriously considering the incredible s, but for now it seems to have completely disappeared from my device...
I've also heard its a hardware issue (I do believe it to be true, not questioning that), so i found it extremely odd that its not happening now on my device.
Guess I'll just keep my mouth shut and enjoy
Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.
NexusDro said:
Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.
Click to expand...
Click to collapse
*gasp* not my invisible shield!?
Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
I had it terribly after the GB OTA, I wiped cache & dalvik and it all but went away. One occurrence in a week and a half, and I've been using the crap out of the phone.
Slightly off topic question: On stock Android, is wiping cache the same as wiping the dalvik cache? The stock recovery doesn't have the "wipe dalvik" option, only "wipe cache".
No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/
Rusty! said:
No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/
Click to expand...
Click to collapse
Thanks. But every time you flash an official update, the cache gets wiped and rebuilt though, right? That's why after each update it takes a long time to boot.
I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.
I still have the prob but it's different with 2.3
Before 2.3, the touchscreen problem was unpredictable and could happen at almost anytime, whether charging or not. I replaced the handset but the problem persisted.
Since upgrading to GB, I've noticed a very clear pattern. If I'm charging my device and unplug it before it is fully charged, the touchscreen becomes extremely erratic to the point I must reboot the phone. If it's allowed to charge completely it's okay.
It never happens when it's is not charging.
Still annoying as hell but I've moved to Africa and having the device replaced is a real challenge. So I guess I'm stuck with until I replace it.
Still has issue
Stock, no modification at all. Today when I was rearranging icons in ADW Launcher, it seems that the screen registered click below where my finger actually was, same as the problem I saw previous to updating to 2.3.3. The phone was not hooked to a charger at the time.
Stock GRI40 here on my Nexus One...same issues that i've already had with Froyo. As it was posted before, it's a hardware issue; and the Nexus S is the new kid on Google's block, so i'm not expecting anything to improve our screens.
filippogiad said:
I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.
Click to expand...
Click to collapse
Theoretically, there is a chance they could fix a software workaround for the hardware problem. If the error happens in only specific circumstances, and ALWAYS happens in those circumstances, then just teach the phone to know when those circumstances are happening, and tell it what to do in those cases. However, I doubt anyone at Google is working too hard on this problem. I agree, it seems to be much less frequent than it ever was. Seems likely that they may have added a little something to help us out.
brettbellaire said:
Seems likely that they may have added a little something to help us out.
Click to expand...
Click to collapse
Or more likely, it could be unintentional.
So even with official OTA it's still here?
Remember me of the ''crazy'' screen problem we had before while charging,perhaps it's a hardware problem after all
This is a main reason why tomorrow i'm getting a new galaxy s.
I tried a lot of custom and stock roms, I sent my phone to HTC and they replaced hardware, but this issue still persist. And it cause me a lot of problems, especially while driving...
I also still get that glitch but not as frequently. I noticed that i didn't need to reboot the phone to fix it. All i need to do is tap the power button to shutoff the screen and then re-tap to turn it back on and it'll show the lock screen. Slide to unlock and the screen is precise once again.
The bug is still there for me also. However, I didn't seem to have it as bad as some did originally, and now I've noticed that it's happening even less frequently.
Firstly congrats. If you're seeing this post, you might have already done so or are trying to flash some custom ROM, which is absolutely ok.
Rather its fun and satisfaction that you keep your device up to date if not possible through official means. Also for some good changes.
Unfortunately, its not completely flawless. There might be some issues which are covered in the further updates of the ROMs.
Among oother small problems, one major problem I faceed when I flashed a custom ROM (actually three) is that the Android Market failed miserably when I initiated it. There were horrible search results. Also the categories were not showing the apps which would otherwise be placed under them.
Fortunately, the Android Market site was open for me which was the last option for me to go on with.
The only solution I could find to this problem was a bit of patience and some really basic info about market.
I tried to re install all the applications that were previously being shown as installed already. Though they showwed "Installed" status but you can install them again.
After a lapse of almost three days, I tried to access the Market app and it was actually accessible with all the search functionalities and EVERYTHING running smooth.
A thing I would like to advise on is try not to wipe out all the data (the 4 wipe out options while flashing) from your device. It might, might help you not to lose data and possibly, the Android Market too.
Have fun.
I've been on a custom rom for greater than a month now and have not experienced any market issues. The only problem that I've ever had was wifi stopped connecting for me. But it was an easy fix. Sorry you've had problems... Perhaps something else is to blame?
Sent from my PC36100 using Tapatalk
antjmon said:
I've been on a custom rom for greater than a month now and have not experienced any market issues. The only problem that I've ever had was wifi stopped connecting for me. But it was an easy fix. Sorry you've had problems... Perhaps something else is to blame?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yes, as I have solved the problem anyways.
DawoodMunir said:
Yes, as I have solved the problem anyways.
Click to expand...
Click to collapse
عزيزي منير
Please let me know how did you fixed this issue?
I really need to know because i have the same issue.
This poll is simply to help determine whether there are hardware variances out there which will resolve the GPS lock dropping out, after some period of usage, issue.
There are many "workarounds" to help alleviate the issue, including limiting your usage to just Google Maps, updating Google Play Services, wifi options, clearing AGPS, etc.
What I'm interested in is whether anybody was able to maintain their normal usage and just swap out a unit and have the GPS issues resolved.
I'd like to isolate out folks whose GPS works fine simply because their normal usage pattern doesn't trigger the issue. By focusing only on folks that are triggering the issue who have exchanged their units, we can see if there are potentially hardware variances.
If there are a very low percentage of cases where a replacement fixes GPS, then it doesn't make sense for folks to keep exchanging their unit(s) hoping the new one fixes the problem. In this case, if GPS is really important, either take a chance waiting for Google to fix it (if they can) or return the unit and wait until it is resolved.
This poll will not tell you whether this is ultimately a hardware, software, or some combination issue. That requires understanding the root cause, which cannot be determined in a poll.
If your exchanged unit resolved GPS for you, please post
first 9 digits of "KBC" SSN number
build date from the box label
16 or 32gb
Code:
[B][U]For example[/U][/B]
SSN: D60KBC265xxx
Date: 2013.06
16gb
This will help figure out if there are any build/manufacturing patterns.
I voted no to see The poll.... I dont have my nexus yet. I hope I don't have any GPS issue that's the Main reason I traded my iPad mini for, that and the fact that I can pocket my tablet now
adeon said:
I voted no to see The poll.... I dont have my nexus yet. I hope I don't have any GPS issue that's the Main reason I traded my iPad mini for, that and the fact that I can pocket my tablet now
Click to expand...
Click to collapse
There is a 'View poll results" button. No need to 'fake' results by voting when you are not giving any proper answer.
adeon said:
I voted no to see The poll.... I dont have my nexus yet. I hope I don't have any GPS issue that's the Main reason I traded my iPad mini for, that and the fact that I can pocket my tablet now
Click to expand...
Click to collapse
For many people if ALL you use is google maps, no navigation, no earth, no gps status, no waze, etc. then you can get many of the units to hold lock for a while, possibly indefinitely.
However, a lot of people use a couple of gps apps and that is where the issues come up.
I guess fewer people use GPS on the tablet versions than the phone/tablet-with-mobiledata versions because their gps apps require data connections, which they may not have access to on the go, but many people still do have apps that work without a data connection or they tether the device.
So only 9 folks have actually exchanged the unit for GPS problems and found this thread? I would have expected more people would have exchanged given how many people are experiencing the problem on the GPS lockup threads.
People aren't exchanging because Google has said they are working on a fix. This implies it's a software issue that will be patched.
Obveron said:
People aren't exchanging because Google has said they are working on a fix. This implies it's a software issue that will be patched.
Click to expand...
Click to collapse
I have never read they are working on a fix, just that they are looking into it. Please post where it says what you are suggesting.
To me "looking into it" and "working on a fix" are quite different levels of commitment from Google. Keep in mind if the problem is on the proprietary hardware side (likely Qualcomm) and/or with Asus who hooked everything up, Google would need to interface with them for a solution (if any) so it would be very hard for them to unilaterally say they are "working on a fix" without even knowing what the root cause is.
Here is the latest info from Google's "official" community manager Paul Wilcox
http://productforums.google.com/forum/m/#!category-topic/mobile/android-devices/prfUDZA7M2s
Jul 30 - Paul Wilcox
Thanks for the reports everyone, we're looking into it.Aug 2 - Paul Wilcox
Hi again everyone,
Could you please let me know a couple of things about your experience with GPS on your Nexus 7 tablets?
1. Do you still encounter this issue if you visit Settings > Location access > Access to my location = on as well as WiFi & mobile network location = checked?
2. If you visit Google Maps or another program that displays your location, is the app actually getting your location even if the GPS notification doesn't seem to show a tight GPS lock? Or is it unable to pinpoint your location?
Thanks!Aug 5 - Paul Wilcox
OK everyone, thanks for confirming my questions from a couple of pages ago, as well as the info that disabling Google Play Services seems to be a workaround. My Android engineering colleagues are investigating this issue.
By the way, in case you're not aware several components of Android use Google Play Services so disabling that can have some unintended consequences on the functionality/performance of your device. For example the Hangouts app won't work without enabling Google Play services.Aug 6 - Paul Wilcox
On Tuesday, August 6, 2013 8:18:48 AM UTC-7, Kenny Bateman wrote:
Also I'm wondering if anyone from Google ever responds on here. Some/any input would be great!
Yup Kenny, Googlers are present in this forum. See my response about this issue a couple of pages back on this thread.
No update for the community about this at this time, but the team is aware and investigating.
Aug 9 - ArsTechnica
Google's Paul Wilcox has been active in that thread telling users that Google was "looking into" the problem and asking some follow-up questions—it's unclear as of this writing whether the issue will be fixable in software with an update or if it's indicative of a deeper hardware problem. We've reached out to Google for further comment on the issue and will update this post if we get a response.
Update: Google's official response is that they're aware of the issue but not ready to comment further at this point. We'll continue to follow the story as it develops.
Since then complete radio silence.
When Asus last had GPS problems with the Transformer Prime, their "solution/fix" was to give people $17 and a free GPS dongle (they even claimed the Transformer Prime didn't include a "professional" GPS). This came after a class-action lawsuit and only residents of the US could officially file a claim:
Settlement: Asus to give GPS dongle and $17 to Transformer Prime users
http://www.androidauthority.com/asus-transformer-prime-settlement-183316/
http://event.asus.com/ASUSPad/TF201GPS/
I haven't returned mine...I mean what is the use? Also my screen is working excellently with no multitouch issues, I do not see any dead pixels and the screen bleed is fine. So what am I supposed to do? I don;t want to tempt getting a worse machine but the GPS not working sucks...kinda stuck...
AnarchoXen said:
I haven't returned mine...I mean what is the use? Also my screen is working excellently with no multitouch issues, I do not see any dead pixels and the screen bleed is fine. So what am I supposed to do? I don;t want to tempt getting a worse machine but the GPS not working sucks...kinda stuck...
Click to expand...
Click to collapse
Not suggesting you personally should exchange it, though based on your confidence level you'll get a resolution you are satisfied with (or you really don't need GPS), you may need to consider whether to return it or just take a risk.
Just trying to get feedback from those that already have, which of course there will be some.
So far from the polling it is looking like it is pointless to return it though. That could change if some people find units that work for them.
It does make you wonder if every unit has the same GPS problem and the people who report GPS works fine just have a usage pattern that doesn't trigger it (which may be perfectly fine for them)
How do you tell the build date?
dannycalgary said:
How do you tell the build date?
Click to expand...
Click to collapse
It is on the label on the top and bottom of edge of the white box.
It'll be something like 2013.06, 2013.07 (or in the future 2013.08)
sfhub said:
To me "looking into it" and "working on a fix" are quite different levels of commitment from Google.
Click to expand...
Click to collapse
Fair enough sfhub, I guess I interpreted Google's commitment differently. It seemed to me that "looking into it" implied they are troubleshooting, which appeared to me they were commited to fixing the issue.
They asked about google play services, and were interested to hear that it affects the stability of the GPS. That alone, seemed to imply (in my naive perception), that software has an intergral role in fault.
I interpreted the semantics differently than you, and basically deemed that I personally wouldn't return the Nexus as there is a good chance Google could patch the problem.
However, after reading your excellent breakdown of Google's communication, I see your point of view. I am therefore much more concerned that it is a hardware fault. I still remain blindly optimistic that it is a software problem. After all, the GPS can be stable under certain software circumstances (disabling google play, using only specific apps, and only one at a time).
Don't get me wrong, I would love the problem to be fixable in software and have a gut feeling that it can (because I can use just Google Maps and nothing else and it won't drop) but without any knowledge of the root cause that is purely a guess/gamble.
Paul Wilcox mentioning Google Play Services was actually in response to a couple of users posting they had disabled Google Play Services and it helped their GPS situation. It wasn't something Google determined on their own and was reaching out to the community.
I'm skeptical that is the issue as I have Google Play Services disabled and I still get the dropouts and other folks have mentioned upgrading Google Play Services helped their situation while others mentioned downgrading helped their situation.
If I were to guess, Google Play Services may have some effect on the issue, but isn't the root cause.
IMO "looking into it" just means you've gotten past the PEBKAC-meter.
D70KBC-155xxx
2013.07
32GB
I purchased this unit from the Google Store and received it this morning. I own a nexus 7 2012 and it has always worked fine. So I knew how to set up the GPS. After trying for an hour I phoned Google Support and and was sent on reams of useless apps that really did not have anything to do with the GPS. When she asked me if I could see my location on the google map I told her yes but only because I was hooked up on WIFI. The we went on a 15 minute discussion on the fact the tablet was not outside. I told her the other tablet which was more than 5 feet further to the window was working just fine with 11/12 SAT/FIX. This was a very painful part of the conversation. Finally she offered to have me download apps that would not need the GPS and make do without it.
At this point I told her I was getting somewhat upset and asked her to pass me to someone else. I basically went through the routine all over again and I finally told him I would send the unit back and have my credit card reverse the charge. That seem to wake him up. He then offered to send me a new unit and for me to hold to this one until the new one comes in. So that is where we are right now.
This was the first time dealing with google support and I sure was not impressed.
no problem so far
ive been using the gps for a good amount of time and i haven't had an issue yet
aptech said:
ive been using the gps for a good amount of time and i haven't had an issue yet
Click to expand...
Click to collapse
Don't take this the wrong way but the thread is looking for people who have a GPS problem and got a replacement unit to try and resolve.
It seems you never had a gps issue.
sfhub said:
Don't get me wrong, I would love the problem to be fixable in software and have a gut feeling that it can (because I can use just Google Maps and nothing else and it won't drop) but without any knowledge of the root cause that is purely a guess/gamble.
Paul Wilcox mentioning Google Play Services was actually in response to a couple of users posting they had disabled Google Play Services and it helped their GPS situation. It wasn't something Google determined on their own and was reaching out to the community.
I'm skeptical that is the issue as I have Google Play Services disabled and I still get the dropouts and other folks have mentioned upgrading Google Play Services helped their situation while others mentioned downgrading helped their situation.
If I were to guess, Google Play Services may have some effect on the issue, but isn't the root cause.
IMO "looking into it" just means you've gotten past the PEBKAC-meter.
Click to expand...
Click to collapse
Did you reboot after disabling Google play services? That was the only way I could get it to work.
Disable and delete updates
Reboot
GPS works in navigation now
You get a ton of notifications to enable it again, but most apps still work fine without it.
Sent from my Nexus 7 using Tapatalk 4
sleepnmojo said:
Did you reboot after disabling Google play services? That was the only way I could get it to work.
Disable and delete updates
Reboot
GPS works in navigation now
You get a ton of notifications to enable it again, but most apps still work fine without it.
Click to expand...
Click to collapse
Yes, I have no updates at the moment, just what came stock, froze play services, rebooted.
I can get GPS to work indefinitely if I only use Google maps.
Once I use other GPS apps, including Google nav, it will lose ability to lock anywhere from 5 to 40 minutes
Sounds like a driver issue. Anyone try CM and if you get better results?
CM use their own kernel and drivers so you should get different results. That should prove it would be fixable in software.
Sent from my Nexus 7 using XDA Premium 4 mobile app
The issue is very intermittent. Today I wasn't able to reproduce with 2hours of GPS on. I have tried both stock and CM and had the bug on both.
Yesterday I lost lock consistently after 15-25mins on but rebooting would return it to life which makes me strongly believe it's fixable with software so I'm not too worried.
My daughter has just been given a Nexus 4 phone - out of warranty - but in full working order. Not rooted. On switching on the phone, she recieved and installed the latest 4.3 update just yesterday. But she has experienced a number of problems since then. The phone is not a 'brick' but it has lost some of its functionality: camera not working, processing appears unduly slow for routine operation, apps such as Whatsapp not working and clearly something is amiss. She lives abroad and tried to resolve this direct, over the phone, with 'google support' but failed including hard resets etc. Assuming the hardware is fine, is it possible to 'flash' to an earlier version of android (4.2?) and if so, would someone kindly provide an idiots guide to doing this?
I did look for 'other solutions' to this problem (as many others, according to differing sites, appear to have experienced similar problems) but I couldn't find anything straightforward on here.
Grateful for any guidance or support.
Have you tried a factory reset?
Swyped from my Nexus 4 using Tapatalk 4
Lord Yurij said:
Have you tried a factory reset?
Swyped from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Will check.
Sandy379 said:
My daughter has just been given a Nexus 4 phone - out of warranty - but in full working order. Not rooted. On switching on the phone, she recieved and installed the latest 4.3 update just yesterday. But she has experienced a number of problems since then. The phone is not a 'brick' but it has lost some of its functionality: camera not working, processing appears unduly slow for routine operation, apps such as Whatsapp not working and clearly something is amiss. She lives abroad and tried to resolve this direct, over the phone, with 'google support' but failed including hard resets etc. Assuming the hardware is fine, is it possible to 'flash' to an earlier version of android (4.2?) and if so, would someone kindly provide an idiots guide to doing this?
I did look for 'other solutions' to this problem (as many others, according to differing sites, appear to have experienced similar problems) but I couldn't find anything straightforward on here.
Grateful for any guidance or support.
Click to expand...
Click to collapse
Root.. is needed to flash... and yes its possible... like you said.. its not totally straightforward.. but definately possible.. needs time.. and patience... which I am in short supply nearing the end of day in office.. hope someone gets you the links and guides to do it..
Does anyone know if there's some facility to log bugs with Samsung?
There's 2 bugs I've identified with the latest firmware (I9505XXUGNE5) and Samsung support is absolutely useless. Apart from the fact that there's no way to respond to support emails and their rather annoying default line of "book it in for a service" thereby losing your phone for weeks; they say there's no way to pass these bugs onto developers.
Bugs can be reported if you had agreed for sending errors to samsung
You can find this at the first time phone boot
RubbaBand said:
Bugs can be reported if you had agreed for sending errors to samsung
You can find this at the first time phone boot
Click to expand...
Click to collapse
I'm talking about sending a report about features of the phone software which are faulty/do not work. I think you're talking about a crash report/diagnosis.
I think they dont have one