Related
Ok so yesterday was ridiculous. Me and my friends were going to a Sonics cuz we've never been to one. Long story short, whenever we get into a jam, I use Sprint nav. I couldn't use it yesterday because the gps wouldn't lock.
I thought DI18 fixedthe issues
Sent from my SPH-D700 using XDA App
A_Flying_Fox said:
I thought DI18 fixedthe issues
Click to expand...
Click to collapse
DI18 was not even supposed to fix the GPS issues on the Epic. We are still awaiting a final fix from Sprint and Samsung. (For that matter, we are still waiting for them to publicly acknowledge the problem.)
One workaround for the worst of the bugs, caused by bad handling of GPS cache data, is documented here. (It's also documented somewhere on xda, but it is harder to find.) Another workaround is just to reboot the phone.
ive never had problems with gps
Rebooting the phone and using the workaround doesnt fix the issue with the phone lagging like **** when you're actually driving. Sometimes it wont update for 30 seconds.... which can totally screw you over. When my EVO locks on, it doesn't go half a second without updating.
even before the fix i haven't noticed a problem with my GPS. Now with the fix it updates faster. Maybe you are holding yours wrong.
boomerbubba said:
DI18 was not even supposed to fix the GPS issues on the Epic. We are still awaiting a final fix from Sprint and Samsung. (For that matter, we are still waiting for them to publicly acknowledge the problem.)
One workaround for the worst of the bugs, caused by bad handling of GPS cache data, is documented here. (It's also documented somewhere on xda, but it is harder to find.) Another workaround is just to reboot the phone.
Click to expand...
Click to collapse
Reboot is not the answer. Change the setting in GPS to cold start. Fixed the prob for me completly andim on DI18 stock.
ZenInsight said:
Reboot is not the answer. Change the setting in GPS to cold start. Fixed the prob for me completly andim on DI18 stock.
Click to expand...
Click to collapse
If you follow the link I posted you would understand that I agree about recommending cold start. But some folks might be more comfortable just rebooting as needed. Both methods reset the cache, and both can take a little time to get a fresh fix when the GPS starts. After that, the performance is quite decent.
hydralisk said:
Rebooting the phone and using the workaround doesnt fix the issue with the phone lagging like **** when you're actually driving. Sometimes it wont update for 30 seconds.... which can totally screw you over. When my EVO locks on, it doesn't go half a second without updating.
Click to expand...
Click to collapse
The GPS has other issues, frankly I think some of which can't be fixed and some of which can be fixed.
boomerbubba said:
If you follow the link I posted you would understand that I agree about recommending cold start. But some folks might be more comfortable just rebooting as needed. Both methods reset the cache, and both can take a little time to get a fresh fix when the GPS starts. After that, the performance is quite decent.
Click to expand...
Click to collapse
Boomer is correct. There are half a dozen ad hoc ways to clear the cache. Cold start does it every time, which means the problem never shows up, but has a drawback of harming Standalone GPS operation (outside of data coverage) area.
KaiserLinux said:
even before the fix i haven't noticed a problem with my GPS. Now with the fix it updates faster. Maybe you are holding yours wrong.
Click to expand...
Click to collapse
There is no fix in the latest firmware, there is a user developed workaround which address one of several issues.
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.
Hey everyone -
I originally posted about this in the Extreme Syndicate thread, but wanted to also ask here. I'm not sure if this is an issue wit my phone, the ROM, or the S5 in general. I'm on Extreme Syndicate L v2, and did a clean flash of it yesterday.
This morning, I noticed that placing the phone on it's back on a white surface while the screen is on caused a red light to appear. I think it's the heart rate sensor, but I'm not sure.
Is anyone else experiencing this? And could whatever-sensor-this-is-that-is-apparently-always-going be causing some people's battery drain on Lollipop?
Here's a short video.
https://www.youtube.com/watch?v=3iSN7WW8Axk
Please post below whether or not you have this issue and which ROM you are on. Thanks!!
btonetbone said:
Hey everyone -
I originally posted about this in the Extreme Syndicate thread, but wanted to also ask here. I'm not sure if this is an issue wit my phone, the ROM, or the S5 in general. I'm on Extreme Syndicate L v2, and did a clean flash of it yesterday.
This morning, I noticed that placing the phone on it's back on a white surface while the screen is on caused a red light to appear. I think it's the heart rate sensor, but I'm not sure.
Is anyone else experiencing this? And could whatever-sensor-this-is-that-is-apparently-always-going be causing some people's battery drain on Lollipop?
Here's a short video.
https://www.youtube.com/watch?v=3iSN7WW8Axk
Please post below whether or not you have this issue and which ROM you are on. Thanks!!
Click to expand...
Click to collapse
This is not very wide spread from what i know, its not related to the ROM, i was stock unrooted android. Its an error in the Update process. Verizon is unable to fix it besides a wipe to the phone, Just factory reset the Phone and the red light will stop. Sorry I cant explain any more.
luckytrek said:
This is not very wide spread from what i know, its not related to the ROM, i was stock unrooted android. Its an error in the Update process. Verizon is unable to fix it besides a wipe to the phone, Just factory reset the Phone and the red light will stop. Sorry I cant explain any more.
Click to expand...
Click to collapse
Are you saying you experienced this problem and have fixed it with a factory reset? Since I just wiped and re-set everything yesterday, I'd really only want to go this route if it's a proven fix... Thanks!
Sent from my SM-G900V using XDA Free mobile app
OK, I think I have it narrowed down to Google Fit. I went into the app's settings and told it to not monitor my activity. After a reset of the phone, the light isn't turning back on. I'm going to monitor it for the next hour or so to confirm that it's really off for good.
EDIT - The light is still staying off, so Google Fit appears to have been the culprit!
btonetbone said:
OK, I think I have it narrowed down to Google Fit. I went into the app's settings and told it to not monitor my activity. After a reset of the phone, the light isn't turning back on. I'm going to monitor it for the next hour or so to confirm that it's really off for good.
EDIT - The light is still staying off, so Google Fit appears to have been the culprit!
Click to expand...
Click to collapse
This Would make sense since when i would run S-health it would be off for as much as a day before returning. Google fit is a good idea, if that solves it try uninstalling the app and re installing I'm interested in know why a reset of my phone solved this.
Just as a quick heads up to anyone still watching this form, the red light error with google fit has been repaired. You can now use google fit properly and you will not get the heart rate monitor always being active.
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
steveindajeep said:
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
Click to expand...
Click to collapse
I haven't heard of any display issues in this regard since the X's initial release, and that was fixed pretty quickly with an OTA. None sense then... The "display driver" is built into the kernel, and if this was an issue I'm sure we would have heard more about it.
Sorry to hear, but this sure sounds like a hardware problem.
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
_arxn said:
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
Click to expand...
Click to collapse
Later on the same day: So I fell asleep for about 4 hours with brightness on low. (damn I sleep a lot) woke up and the issue returned. But I had the brightness on full for a while and it seems to have resolved again when I put it back to low brightness.
That's all so far. Still monitoring
I'm glad someone else noticed that when you slide the brightness bar it effects the way this display issue behaves. I was starting to think I was alone on this. Now this is just my experience on my phone of course. It seems to be around 2/3 way to full bright that it starts to flash the white lines on and off and then 3/4 + it is pretty much acts as it should, they go away! So I took a screenshot as acejavelin suggested and the screenshot was clear. So this would explain why updates don't seem to change anything since it does seem to be a certain batch with bad hardware. Can this hardware be solder changed? Guess I will keep an eye out for sale of xpure with busted digitizer/good lcd to test and possible mb swap.
Yes 1575 definitely has a display driver issue, i've noticed this too. I don't think there is a way to fix this, unless it would be fixed in Nougat.
But how sure are you that it's a driver issue and not hardware? That's why I'm waiting for nougat. If it doesn't fix the issue then I'm just going to have to retire the phone.
Sorry bro
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Mine has the same issues now and then but a restart fixes it always.
Bill720 said:
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Click to expand...
Click to collapse
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
But the Op!
onupirat said:
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
Click to expand...
Click to collapse
steveindajeep said:
I've already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
Click to expand...
Click to collapse
Oh. I just read this and assumed that we were all talking about the same thing. In your case, I'd perform some experimentation to make absolute certain that your findings aren't just coincidence.
Question re: hardware vs software
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
Hi ~ just read your msg, and tried your "screenshot test." The grayish area on my screen (which over time, comes & goes - haven't detected a pattern as to why/when) DOES show up on the screenshot.
If I understand correctly, that would tend to indicate that I am experiencing a software issue? (Not hardware)
I did do a Factory Data Reset, and am experiencing the same issue. I had not added any apps for an extended period of time, prior to this gray-area occuring. I did, however, drop the phone. I don't recall for certain, but I don't think the problem occurred immediately, rather, it started very shortly thereafter (1 -3 days).
And I am waiting for delivery of a battery, since that's shot (runs down very quickly, & shuts down with anywhere from 30% - 60%+ battery level).
Any suggestions for resolving this? I hope this post makes sense... And thank you for any ideas or assistance you can offer!
Hello everybody. I have the same problem.
And who ever changed the display? Do you want to understand this is the problem of the display, motherboard or drivers?
I think it's a software problem, a hardware will not stop glitches when you flash a different software until and unless you fix it. In my experience, after my phone break because of downgrade to marshmallow stock firmware, and with an unlock bootloader i update my phone using OTA update, suddenly it stop working. blank screen and i tried try to recovery it with xt1575 IMG file to boot it again, mine it was xt1572(India) then I start facing a lot of problem, glitches, can go back to marshmallow stock firmware so and so... Now I'm trying to find a solution !!!! Custom ROM, CM13 work better and no glitches till now... I will Report soon
Moto x style/pure display problem
steveindajeep said:
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
Click to expand...
Click to collapse
I think maybe due to brightness control problem, could be the software or hardware problem
I have 2 PH-1s one of them has this random issue that Essential support says is software related.
Would appreciate input from fellow owners
https://youtu.be/61TOTt7iERk
Sent from my PH-1 using Tapatalk
I had this happen to me today after the Oreo update, but it was perfectly fine with stock 7.1.1
Anyone else seeing this?
I have noticed ghost touches as well following 8.1 official update. They now happen about 1-2 times per day. Nothing changed from before except OS version. Didn't have this issue on the beta either.
Turning the screen off and back on fixes it temporarily, but it comes back.
FYI
I got in touch with Essential Support the second time, and they got the phone replaced with in warranty service.
I also got in touch with Essential support a few days ago for the second time. I can tell their support is from the US which I appreciate in a company, but this phone is agitating and their troubleshooting makes it worse. All manufacturers from Apple to Samsung may make you jump through these hurdles but it's same issues with this phone. I believe they know it. So why waste my time asking about water damage and drops? Come on. I'm going to do a hard reset since I took the latest update but have already switched back to my s8 as my DD. I'll check if turning the screen off and back on again fixes it. Even if it's briefly I could maybe live with doing that. I couldn't get any letters to register when typing a text in the standard messaging app.
I bet the issue has something to do with the hardware. Ceramic and titantium? I know my reception is so much worse when Sprint's network is being put to the test on the highways with the Essential when compared to the s8. It may just end up being the perfect media player in the car. 128GB of music and use it as the Waze/Google Maps device...
coolmaster121 said:
FYI
I got in touch with Essential Support the second time, and they got the phone replaced with in warranty service.
Click to expand...
Click to collapse
Good to hear. In Canada we don't have that option. Let us know when f the problem is fixed or if it happens again. Like I said in my case the issue really started on Oreo 8.1.
Could grip detection have something to do with this?
sam2c said:
Could grip detection have something to do with this?
Click to expand...
Click to collapse
No, literally you don't touch the screen and this issue happens. Turning the screen off and back on fixes it.
dhorgas said:
No, literally you don't touch the screen and this issue happens. Turning the screen off and back on fixes it.
Click to expand...
Click to collapse
Exactly... It keeps occuring more often than not.