Database Users

DK28, The Good And Bad

Even though its certain this isn't the official release, I thought we should condense the topics and just post the your thoughts about the good and bad features this update provides.
Ill start..dk28 isn't that awful for me like others. The only problems I've noted was samsung widgets disappearing sometimes, home screen rotation lag, and a few checkers showing up in the browser when zooming in and out.
However, on the bright side, flash is very smooth, and there are better icons
Sent from my SPH-D700 using XDA App

GPS fubared?

No notification when charging usb

Hey guys i recently started having a problem with the back button.it will pick up half the time and then its unresponsive the time any ideas on what i can do?

Probably just lag. Which way did you flash dk28?
Btw, I came up with some other things.
1. Notfications are delayed (ex. Handcents icons in the top bar are sometimes delayed)
2. Keyboard delayed (its actually a bit worse than before)
Sent from my SPH-D700 using XDA App

*Keyboard/touchscreen/captivate button lag/failure to register action/press
*Streaming music skips (last.fm) while doing anything else; like browsing the web.
*Slow orientation change
*No lineout on multimedia dock yet
*None of the unicorns and rainbows flying out of the screen that were promised by the legion of unrelenting froyo fanboys littering this forum for the past month.
Sent from my SPH-D700 using Tapatalk

acer1096xxx said:
Even though its certain this isn't the official release, I thought we should condense the topics and just post the your thoughts about the good and bad features this update provides.
Ill start..dk28 isn't that awful for me like others. The only problems I've noted was samsung widgets disappearing sometimes, home screen rotation lag, and a few checkers showing up in the browser when zooming in and out.
However, on the bright side, flash is very smooth, and there are better icons
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here, I guess a few of us got lucky. Just very small things such as checker boarding. I don't have homescreen lagg though, or widgets that disappear.
Sent from my SPH-D700 using XDA App

hardrock121 said:
GPS fubared?
Click to expand...
Click to collapse
GPS actually finally works for me with the update, I'm getting signal indoors in places I hadn't previously and it has yet to time out and require me to reflush the agps data or reboot the phone (used it all day today for work).
dannyzen said:
No notification when charging usb
Click to expand...
Click to collapse
Not seeing this one either, lets me know right away though the notification bar as per usual.
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.

punzada said:
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
Click to expand...
Click to collapse
That's odd...maybe your phone is actually damaged then
Sent from my SPH-D700 using XDA App

I personally went back to 2.1, rock solid and stable.
On 2.2, Screen rotation is slow as molasses, GPS is stuck on my work location and would not work at all in updating. Browser was a bit slower compared to 2.1. Hated the scattered, non-alphabetical applications folder, wtf?!!
I enjoyed the 2.2 leak but the little niggles weren't enough to stay on it.
I did like the coloured menus, and the ability to turn off 3G when holding the power button for a few secs.

I keep getting errors when connecting to Wifi. I will look down at the phone and wifi will be off even though i never turned it off, and then the notification toggle wont do anything, and when I go into settings to enable it, it says "error" underneath the Wifi entry. Then it takes a few tries to get it connected again.
I do like where Froyo is headed, but this is absolutely no where near polished enough for final release.
Edit: Having a fully working GPS is awesome though. 2 meter accuracy = Awesome.

Does anyone else have lag when trying to adjust brightness on the notification bar?

LordLugard said:
Hated the scattered, non-alphabetical applications folder, wtf?!!
Click to expand...
Click to collapse
If you press menu > edit > menu again, there's an option for A-Z order.
Guess it doesn't matter now since you downgraded, but just thought id let you know.
Edit: lilxflip, yes. I'm getting the same problem but didn't notice that until now
Sent from my SPH-D700 using XDA App

I've noticed since 2.2 that when a caller hangs up, I get a single beep in my bluetooth earpiece confirming that the call has ended, which I like...didn't have any sound before that.

Anyone else having trouble hanging up during a phone call? I hit the damn End button at least 3-4 times before it decides to hang up.

I must be one of the lucky few, everything works great, and not only that it fixed all the issues I had with the previous 2.1 build. I've tried out just about everything I can think of wifi, gps, 4g, pandora, etc.
edit: Should add, I did a factory reset after I installed it, wiped everything the only bit I loaded back in was contacts.

muyoso said:
Anyone else having trouble hanging up during a phone call? I hit the damn End button at least 3-4 times before it decides to hang up.
Click to expand...
Click to collapse
Give the phone a few secs after the screen comes back on then press it. Works fine; if you immediately press it.. it doesn't hangup. Seems intentional..
Umm.. aside from no GPS now which I plan to fix by reflashing di18 then 2.2... I don't find any major problems. The keyboard does have a bit of a registration flaw but not too major..
The leds do light up whenever the screen is off.
And I don't think the brightness sensor likes my room light because it enjoys changing itself a bit.
Sent from my SPH-D700 using XDA App

I'm always weary about doing wipes, so to test if this is true, mid anyone else testing out this also to see if he's right? =P

punzada said:
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
Click to expand...
Click to collapse
I have noticed the Sammy widget thing and the slow screen rotations but I was intrigued by your bug. So I tried it. Definitely happened. I wouldn't say 'blinks constantly' though. At least not in my case. It flashed on for about 2-3 seconds every 30 or so seconds. Maybe even as long as a minute. Caught me off guard. I watched it for a bit then went back to reading this thread only to have it happen out of the corner of my eye.

kenvan19 said:
I have noticed the Sammy widget thing and the slow screen rotations but I was intrigued by your bug. So I tried it. Definitely happened. I wouldn't say 'blinks constantly' though. At least not in my case. It flashed on for about 2-3 seconds every 30 or so seconds. Maybe even as long as a minute. Caught me off guard. I watched it for a bit then went back to reading this thread only to have it happen out of the corner of my eye.
Click to expand...
Click to collapse
Woah, just tried it. I had similar results. However, I opened the keyboard, let the flash disappear, then 2-3 seconds later it came back. And stayed there too, for about a minute or so!
Not really a big deal in my opinion; I honestly don't use the keyboard often due to its laginess..

TouchScreen issue resolved in gingerbread?

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.

Notification light

Hi Nexus 10 owners,
Love my Nexus 10 but I have an issue with the notification light under the screen.
It was working fine when I first got it on Friday, with it dimming on and off when an email is received.
But since yesterday, it hasn't light up at all, for any notifications, and I do have the "Pulse Notification Light" checked in setting.
So I was wondering if anyone else have any problems with the notification light? Could it be a bug, or perhaps my light broke after the first day?
Thanks in advance for any response.

I might suggest trying https://play.google.com/store/apps/details?id=com.coolbeans.ledtester&hl=en to see if your light still works

espionage724 said:
I might suggest trying to see if your light still works
Click to expand...
Click to collapse
Thanks for the suggestion.
Just tried the app and there's no light.
However, could it be that this app doesn't work on the Nexus 10 yet?

imistw said:
Thanks for the suggestion.
Just tried the app and there's no light.
However, could it be that this app doesn't work on the Nexus 10 yet?
Click to expand...
Click to collapse
Yea it might be possible that app doesn't work; may want to see what an actual N10 owner has to report though

Works fine on my N10, only flashes white though, regardless what colour I pick.
Sent from my Nexus 10 using Tapatalk 2

alias_neo said:
Works fine on my N10, only flashes white though, regardless what colour I pick.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
So I guess it's really just my N10 then.
Thanks though.

No problem, try reflash with stock images and you might get lucky. My Nexus 10 is buggy as sh** and I put it down to 4.2. It'll all get sorted out soon enough, hopefully yours is just a bug too. Hope you solve it.
Sent from my Nexus 10 using Tapatalk 2

UPDATE
Just reset my N10 and now the notification light works again.:victory:
Guess it must have been one of the app interfering with the light.
BTW, when I tested it with a LED tester app, it can actually show green, red, blue and purple lights.:good:

alias_neo said:
No problem, try reflash with stock images and you might get lucky. My Nexus 10 is buggy as sh** and I put it down to 4.2. It'll all get sorted out soon enough, hopefully yours is just a bug too. Hope you solve it.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I actually just solved it so now I am happy. haha
BTW, what do you mean by reflash with stock image and put it down to 4.2?

imistw said:
Thanks, I actually just solved it so now I am happy. haha
BTW, what do you mean by reflash with stock image and put it down to 4.2?
Click to expand...
Click to collapse
If I understand right, he just flashed a factory 4.2 image from Google, without any OTA updates.

You can get the factory software from the Google developer site and you can download it to your nexus device in case anything gets messed up.
By "put it down to", I mean I blame 4.2 (Android version on the Nexus 10) for all the bugs I'm having. It's a new OS, and this multiuser stuff amongst others means some pretty major changes so I expect it to be a little unstable for a while. Still a better state than honeycomb was when I bought my XOOM on launch day, boy was that a mess.
You're right about the lights, I just got it to work with all the different colours, cyan and then purple look nice
Sent from my Nexus 10 using Tapatalk 2

alias_neo said:
You can get the factory software from the Google developer site and you can download it to your nexus device in case anything gets messed up.
By "put it down to", I mean I blame 4.2 (Android version on the Nexus 10) for all the bugs I'm having. It's a new OS, and this multiuser stuff amongst others means some pretty major changes so I expect it to be a little unstable for a while. Still a better state than honeycomb was when I bought my XOOM on launch day, boy was that a mess.
You're right about the lights, I just got it to work with all the different colours, cyan and then purple look nice
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Wow, I did not know about the factory software from the Google developer site. Guess i learned something new today. :laugh:

UPDATE #2
The notification light is not working again
Reset my N10 again, then performed a LED light test each time I install a new app.
Until the last app installed, the notification light was working, then after a few minutes it stops working again.
So I guess it's not really caused by 3rd party apps.
So I ask again, has anyone had problem with their N10's notification light?
Still hoping that it's a bug instead of just me having a defective unit.
Thanks again!

I'm having the same issues. Sometimes the LED seems to be working, others it's not. I installed LED tester and again, sometimes it works fine and others not at all. I have tried to spot a pattern to see what causes it to stop and start and have drawn a blank - no idea. I have since installed light flow but this has not helped. Seems to me that there is either a software bug and we haven't yet figured what the trigger is, or there is a dodgy hardware batch (I hope it's the former!)

hefferman said:
I'm having the same issues. Sometimes the LED seems to be working, others it's not. I installed LED tester and again, sometimes it works fine and others not at all. I have tried to spot a pattern to see what causes it to stop and start and have drawn a blank - no idea. I have since installed light flow but this has not helped. Seems to me that there is either a software bug and we haven't yet figured what the trigger is, or there is a dodgy hardware batch (I hope it's the former!)
Click to expand...
Click to collapse
I think I've found the trigger. If I turn the device completely off, and turn it back on with the charger plugged in, notifications work. If I turn it back on with the charger unplugged, notifications do not work.
Other things I have tried which made no difference included factory reset and factory reflash.
Can some other folks see if their behavior matches mine? I have a replacement device being shipped to me, but if this is a software problem I'd rather not swap hardware. I'm very curious to hear if there are any devices that have a working LED under both boot up scenarios.

I think you are right. LED notifications were working ok when I had a freeze in google now. I restarted (on battery) and tested the notifications - no LED. I plugged in the charger, restarted the system and retested - LED working again. Looks like we have a workaround and a confirmed software bug rather than a hardware fault.

I'll test when I get home, but, I've only ever noticed the light when my tablet is plugged in, so it could be the same for me too. Shouldn't be a major problem, will get fixed in the next update as long as Google are aware.

alias_neo said:
I'll test when I get home, but, I've only ever noticed the light when my tablet is plugged in, so it could be the same for me too. Shouldn't be a major problem, will get fixed in the next update as long as Google are aware.
Click to expand...
Click to collapse
I'm not entirely sure, there are people who are claiming that their LED works 100%.

kftrav said:
I think I've found the trigger. If I turn the device completely off, and turn it back on with the charger plugged in, notifications work. If I turn it back on with the charger unplugged, notifications do not work.
Other things I have tried which made no difference included factory reset and factory reflash.
Can some other folks see if their behavior matches mine? I have a replacement device being shipped to me, but if this is a software problem I'd rather not swap hardware. I'm very curious to hear if there are any devices that have a working LED under both boot up scenarios.
Click to expand...
Click to collapse
Just tried this but still nothing.
Called Google today and they are sending me a replacement.

Ok, this is ridiculous.
Just unplugged my N10 and now the notification light is working.
So apparently it's working randomly.
Hopefully my replacement device works 100% of the time.
BTW, are replacement devices new, or refurbished?

Touchscreen issues solved after 05Q update

I was one of the unlucky persons to deal with the dreaded touchscreen problem. When on the 44s build, it sometimes got so bad the phone was almost completely useless. The touch screen problems didn't go away in spite of flashing countless Rome with almost every possible combination of kernels.. But nothing seemed to help. The touchscreen got noticeably worse when the phone got hot..i was almost at the verge of giving up.. But that's when it happened.. The 05Q update solved all of my touchscreen problems. I've checked with touch Explorer and even multi touch works flawlessly.. I understand that this problem was identified as a grounding defect.. And I did buy it.. But since the 05Q update seems to have completely solved this issue, my faith in oneplus has been restored.. Did anyone else notice this? What could be the reason?

Nothing's changed for me :c
Sent via Telnet

I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?

alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..

my problems
onefanboy3556 said:
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
Click to expand...
Click to collapse
I've been facing touch issues after this update. The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Anyone have similar problems or with possible solutions ? Also for heavy battery drain

alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
I'm having some issues too with this! Sometimes, even the physical power button doesn't work and I have to press it multiple times!

I m also facing same issue
Any solutions to resolve this issue?

Glad to hear it is better for you. Unfortunately, I still am experiencing ghost touches... Double tap on the other hand is fine.

For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable

kewlstuffdudez said:
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
Click to expand...
Click to collapse
From my experience I could say that these 'gost touches' are related to a system slowness more than a touch problem. Sometime I feel I could type fast without any problem, sometime I had to type very slow. Also this is rom related. Some are really snappy others not so. Another thing to mention is that keyboard feels better after a reboot, so maybe a memory leak!?
Inviato dal mio A0001 utilizzando Tapatalk

I just hope it's not the hardware touchscreen / sensor. My observations are consistent with everything you mentioned above. Memory leak feels possible or some unoptimized code. I don't see any issue in ex Chrome. It's mostly Hangouts app that's super slow so perhaps Google also pushed some update to Hangouts that slowed things down enough to be noticeable.

anuradha1208 said:
The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Click to expand...
Click to collapse
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Steelpapi said:
Sometimes, even the physical power button doesn't work and I have to press it multiple times!
Click to expand...
Click to collapse
Yes, same here!
kewlstuffdudez said:
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Click to expand...
Click to collapse
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su

I went straighten to CM12 nighties. The touchscreen issues still does up but not as much. Makes me think is a hardware issue with the touchscreen independent of firmware perhaps just didn't notice before. When I went to CM12 I did a full wipe, so everything from scratch

Sumanji said:
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Yes, same here!
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
Click to expand...
Click to collapse
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!

I have not faced touch screen issue.
Even i have broken my display from top..
Sent from my A0001 using XDA Free mobile app

Steelpapi said:
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
Click to expand...
Click to collapse
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su

A thread i created in the oneplus one forum after a bit of research from my side
https://forums.oneplus.net/threads/major-touch-screen-issue.282231/

Sumanji said:
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
Click to expand...
Click to collapse
Crazy stuff.. Looking at the video, I have almost bought that it's a software problem..

Mine works fine if and only if you turn off all those double tap settings (wake/sleep) and turn off ambient display.

I've gone through all the settings menus and turned off everything gesture or touch related... also switched to onscreen buttons.
Still have the same problem
I emailed support to arrange an RMA, but they want me to wait for Lollipop... WTF?

Display driver issue? fixes?

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