Database Develop

[Q] That screen...

I've scoured the internet in attempt to resolve this issue, and I know it's been talked about many a time before, but this just doesn't have an answer yet afaik.
Does anybody have any experience with fixing the inaccuracy of the touch screen after prolonged use? I love the nexus one, it's by far the best phone I've owned; but this little bug makes the phone completely unrealistic in real-world use.
If this isn't a software issue, it has to be something with the digitizer being powered off and back on to remove the accuracy bug. In that case, is there any low-level way to turn the digitizer off and back on as fast as possible every X seconds? That would mean losing touch capability for a few milliseconds, but is much better than locking and unlocking the phone each time it "goes wild."

I had given up all hope that this issue could be resolved in any fashion as dodgy hardware is, well...dodgy. Nothing can be done about it right?
I haven't had a screen wonk since starting in on the CM7 nightlies many moons ago!
IN YOUR FACE WONK!

Is there an FAQ about this digitizer issue?

JoeSchmoe007 said:
Is there an FAQ about this digitizer issue?
Click to expand...
Click to collapse
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once

DirkGently1 said:
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
Click to expand...
Click to collapse
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.

JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.

Hollow.Droid said:
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Click to expand...
Click to collapse
When accuracy goes berserk - does powering phone off/on help?

JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Well, the touchscreen issue is nothing more than a bad digitizer that was released with the phone and never improved during manufacture of the device. All Nexii have the same one, although people suffered the problem in varying degrees. What would happen is every so often your touch on the screen would register in the wrong place so you may be selecting a shortcut on your homescreen to launch an app, but it might register the touch as being an inch higher/lower/somewhere random. the solution has always been to simply press the power button to turn the screen off/on again. This would fix the issue... until it occurred again.
The call wonk is really in two parts. Stock GB ROMs had a habit of introducing a slight delay in one party being able to hear the other during the start of a call. On CM7 ROMs it was a more significant issue of black screens and freezes during the start of a call. These didn't affect affect everyone though, and even Cyanogen himself didn't have it on on his own device.
EDIT: The other issue affecting the N1 was a weak, and often failing, power button. With the need to keep using it to fix the screen wonk the problem was made worse. That's why you might often see mentions of Trackball wake as it reduced the need to use the power button, therefore extending it's life. Trackball wake is only available on custom ROMs so bear that in mind too!
The phone isn't perfect but with the custom ROM devs doing there thing it's pretty decent for me

Hollow.Droid and DirkGently1 - I appreciate your responses.
Can I bring your attention to my other question to which nobody responded yet?
http://forum.xda-developers.com/showthread.php?t=1077733

JoeSchmoe007 said:
When accuracy goes berserk - does powering phone off/on help?
Click to expand...
Click to collapse
When the issue happens you just lock and unlock the screen to fix it. No need for a reboot.
This issue isn't really such a big deal. It happens once a week or so, and it takes a few seconds to black out the screen then unlock, problem gone.

screen responsiveness problem

Every couple of days I have a problem with the screen becoming VERY unresponsive. It seems to affect the whole screen and requires touching characters on the keyboard, web buttons, app icons, etc. multiple times before the touch is registered. The problem persists until I reboot the device.
I haven't rooted yet or otherwise modded it at all, but maybe I have a poorly optimized app running? Haven't tried to capture a logcat yet either (and frankly wouldn't know what I was looking at).
Has anyone else experienced something like this?
Thanks!
_john

Looks like mine is suffering something similar to the problems discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1779652

I also have this issue. Was able to reproduce with multi touch tester apps. When I cross axis the touch points freak out. I think it's a grounding issue. If I touch the headphone jack or have headphones in the issue goes away. Called in a RMA request yesterday. Hope this issue isn't present in the next device.
Sent from my Nexus 7 using xda premium

[Q] Occasionally no response lower right screenside CM9 and CM10

I have experienced a really strange phenomenon. Just got a new Galaxy S GT-I9000 and decided to give CM10 a shot.
The main problem I am facing is some sort of a lag or better no response at all randomly. Problems are visible when:
1. I type on my keyboard
2. I scroll down long lists
The Problem.
Sometimes the device doesnt respond to my "tap" at all. The bug just occurs on the right half of the keyboard so you could say lower right half of the screen in a certain area around [k, i, l , j] buttons. When scrolling down lists my thumb is normally in that area so even when scrolling down the screen simply does not react from time to time and when I lift my thumb up and tap again everything works as normal.
This problem is extremely frustrating because I am not able to type properly anymore. First i was afraid its not the Firmware BUT my phone. But on stock rom I dont experience any of this at all.
Does anyone have an idea? Why can't I find something about this problem in the Forums. CM9 should be stable and nobody seems to experience this problem but doesnt the fact that it works on a stock rom prove, that its can't be the hardware?
Greetings

[Q] Status on CM Based ROM Screen Rotation Issues?

Hey guys, I've been off the forums for about a week or so now...can anybody briefy bring me up to speed regarding the issues of the wifi bug, and the auto rotation bug? From what I very hastily just skimmed, I didn't see anything indicating there has been a fix yet. Is there at least any news regarding the status of these issues, and when they may possibly be fixed?
I'm quite fond of ROM flashing, and we all know our small Droid 4 following is pretty limited in the amount of dev support it recieves, compared to several other phones; and continue to appreciate the few devs that have remained faithful to providing the Droid 4 with the few ROMs it does have. So, the not being able to use any custom ROMs because of these few critical glitches has been horrible.
Any insight from anyone on the status of these issues would be much appreciated. Thanks.

Hello,
Sorry to but in, but I'm also experiencing an issue with the Accelerometer not producing any data. I can only switch to landscape mode by sliding the phone open, but I have to turn the screen off and back on to restore back to portrait. Not a huge problem, but one I'd love to see a fix to. Any updates on this would be appreciated. Thanks.

if your on CM10 download his latest version. This should have a fix

Do you also face touch problem in your K3 note

I'm facing a very annoying problem in my k3 note, that some areas of screen randomly stop responding. In my phone its mostly limited to bottom right part of my screen where backspace on keyboard is located. Rest of phone is responsive except this region. Restarting the phone fixes it temporarily.
But strange part is it doesn't happen on all ROMs, I first noticed it in some AOSP MM ROM, then i think it was Andronium VUI ROM (based on dev 1628) and now on s433 rom which leads to believe its some software thing not hardware thing.
Are there others also which face similar issue ? Any possible solution except switching to different rom ?

Mafioso said:
I'm facing a very annoying problem in my k3 note, that some areas of screen randomly stop responding. In my phone its mostly limited to bottom right part of my screen where backspace on keyboard is located. Rest of phone is responsive except this region. Restarting the phone fixes it temporarily.
But strange part is it doesn't happen on all ROMs, I first noticed it in some AOSP MM ROM, then i think it was Andronium VUI ROM (based on dev 1628) and now on s433 rom which leads to believe its some software thing not hardware thing.
Are there others also which face similar issue ? Any possible solution except switching to different rom ?
Click to expand...
Click to collapse
Yes, I have this problem with the screen also. I've heard from others with similar issues on other forums. It seems it is a hardware fault or possibly an issue with the way software interacts with the screen controller. In my case the screen is periodically unresponsive around the letter E or R on the keyboard and I have to tap the area with greater pressure. Sometimes it gets very buggy and very frustrating.
There is another possibly related problem when scrolling a web page or dragging - larger areas of the screen become unresponsive. Turning the screen off and then back on fixes the problem for the next 2 or 3 minutes. This issue has also been fixed for me with the kernel from daniel_hk here http://forum.xda-developers.com/k3-...rnel-dc-mtk-m1-kernel-vibeuiv3-51631-t3483573 - the only proviso is you apply it to Vibeui 1631. So while the scrolling issue seems to be fixed, the unresponsive areas around letters E and R on the keyboard remain.
I've noted the problems above would temporarily go away after flashing a new ROM however they eventually return. I've considered buying a new screen but not really sure if its a hardware or software issue - possibly both!

EpicSauce said:
Yes, I have this problem with the screen also. I've heard from others with similar issues on other forums. It seems it is a hardware fault or possibly an issue with the way software interacts with the screen controller. In my case the screen is periodically unresponsive around the letter E or R on the keyboard and I have to tap the area with greater pressure. Sometimes it gets very buggy and very frustrating.
There is another possibly related problem when scrolling a web page or dragging - larger areas of the screen become unresponsive. Turning the screen off and then back on fixes the problem for the next 2 or 3 minutes. This issue has also been fixed for me with the kernel from daniel_hk here http://forum.xda-developers.com/k3-...rnel-dc-mtk-m1-kernel-vibeuiv3-51631-t3483573 - the only proviso is you apply it to Vibeui 1631. So while the scrolling issue seems to be fixed, the unresponsive areas around letters E and R on the keyboard remain.
I've noted the problems above would temporarily go away after flashing a new ROM however they eventually return. I've considered buying a new screen but not really sure if its a hardware or software issue - possibly both!
Click to expand...
Click to collapse
hmmm it's interesting that different people have different areas of unresponsive screen. It seems more like software issue to me, as I started noticing this issue more on newer dev roms only. Today, I've reverted to dev ui 3.1 1622st as I remembered it didn't have it. Will report in couple of days of how it goes, so far haven't noticed it.

I have been facing touch problems for quite some time on the ROW version of the ROM s433. The touch starts acting weirdly, i.e random things start getting touched automatically and this happens mostly in the lower half of the screen. I turned on the show pointer location option from developer settings and it shows the pointer stuck at one point on the screen showing erratic behaviour. Turning the screen off and then back on solves the problem but very temporarily. Restarting solves for a longer time but the problem pops back up.