Hello, sorry if there is already a thread for this, I looked a bit and found none with any similar issue.
I have the phone for one and a half years, tried dozens of custom roms with no errors, worked perfectly until now, never dropped it...
Recently I started to notice I have some troubles with the upper row of characters in the qwerty keyboard, and some games... looked like two characters are touched at the same time.
I enabled the view touches in the developers option and it seems there's an area where indeed there are two touches registered instead of one.
I'm not allowed yet to link to the youtube video I made but I attached a zip with it.
To rule out a rom error I tried several and it happened in all, ViperS 3.1.2, AOSP 4.3, and now also in Android Revolution HD 7.3
Also tried the different calibration tools with no luck, also tried the tips for the unresponsive touch screen from different threads...
The question is, have you guys seen this type of error? Do you think my touchscreen is broken?
Thank you for your time and help.
Related
Okay So I followed a video tutorial that said right now the Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid V2_1_65.14.06[CubeV2]
was the best rom out there. So i installed it. I like the rom alot except it has some bugs that I cannot overlook, was wondering if there was a fix or a recommended upgrade from this Rom.
The bug I hate the most is the keyboard. First it was mapped wrong, but I installed the Tilt fix cab, which fixed that. But now the keyboard spacebar lags. So if i type at a decent speed the spacebar doesnt register being pressed at the right time. For example if i typed : "Hello, how are you doing today? " it would come out as " Hello,h owa rey oud oingt oday"
At first i thought it was maybe my error, that I developed some sort of bad habit of pressing the spacebar at the wrong time. But i sat there and was careful and indeed its the phones fault.
The next bug which I just noticed recently since I havnt had a reason to use it since now, is the video on the camera. When I press record it only records for 9 seconds even though I have it set to no limit. If i keep trying some times it goes past 9 seconds but the video freezes at that point, the counter still goes up and I'm forced to soft reset the phone to get out of it. I tried installing the HTC camera cab , with no effect.
Should i change roms or Is there a fix for this?
thanks
I don't believe dutty has touched these ROMs in almost a year now, and he has moved onto the HD, I believe.
Better to look at some of the more recent ROMS, like Garmin, PDA Corner, etc. and forget working with the Dutty ones.
drtolson said:
I don't believe dutty has touched these ROMs in almost a year now, and he has moved onto the HD, I believe.
Better to look at some of the more recent ROMS, like Garmin, PDA Corner, etc. and forget working with the Dutty ones.
Click to expand...
Click to collapse
How do you personally like your G's SE TF3D rom?
bilago said:
Okay So I followed a video tutorial that said right now the Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid V2_1_65.14.06[CubeV2]
was the best rom out there. So i installed it. I like the rom alot except it has some bugs that I cannot overlook, was wondering if there was a fix or a recommended upgrade from this Rom.
The bug I hate the most is the keyboard. First it was mapped wrong, but I installed the Tilt fix cab, which fixed that. But now the keyboard spacebar lags. So if i type at a decent speed the spacebar doesnt register being pressed at the right time. For example if i typed : "Hello, how are you doing today? " it would come out as " Hello,h owa rey oud oingt oday"
At first i thought it was maybe my error, that I developed some sort of bad habit of pressing the spacebar at the wrong time. But i sat there and was careful and indeed its the phones fault.
The next bug which I just noticed recently since I havnt had a reason to use it since now, is the video on the camera. When I press record it only records for 9 seconds even though I have it set to no limit. If i keep trying some times it goes past 9 seconds but the video freezes at that point, the counter still goes up and I'm forced to soft reset the phone to get out of it. I tried installing the HTC camera cab , with no effect.
Should i change roms or Is there a fix for this?
thanks
Click to expand...
Click to collapse
Welcome to 2009 from 2008 , Dutty did so great work in this forum last year, but you need an updated YouTube video. Where did you get a video saying that was the best ?
As stated above, start exploring 2009 , you will love it here
I doubt you will find anyone with new information. Have a search/read through the Threads from dutty or try flashing one of the newer ROMs, a few have been suggested above.
Thanks
Dave
hi,
I'm not sure when exactly this issue started on my phone, but I updated my touch pro with the chevron updater and have quite a lot of apps installed.
after several seconds workling with the phone, the touch screen stops working while the phone acts perfectly normal. I can use the keyboard and tilt the phone but I cannot use the touch screen anymore.
By turning the phone off and on it works again.
has anyone experienced a behavior like this?
I noticed my touchscreen becoming unresponsive when loading particular websites. Even had it freeze once (only time it ever froze on me)
What were you doing when it does this? Do you have the multitasking reg edit on?
exilkubaner said:
hi,
I'm not sure when exactly this issue started on my phone, but I updated my touch pro with the chevron updater and have quite a lot of apps installed.
after several seconds workling with the phone, the touch screen stops working while the phone acts perfectly normal. I can use the keyboard and tilt the phone but I cannot use the touch screen anymore.
By turning the phone off and on it works again.
has anyone experienced a behavior like this?
Click to expand...
Click to collapse
I know this is an old thread but this is the only reference to the exact same problem that I'm having. I'm having difficulty putting this down to hardware as the screen becomes responsive again when locking and unlocking which might point to software.
It could be a hardware issue that is resolved by locking then unlocking the phone but I don't know enough about the construction of it to have an opinion.
The advice I've had from htc is to wipe the 'phone and start again but I don't expect that to solve it (especially as their call handling system refers to Window Mobile 7 - the second large commercial organisation I've seen that on in recent weeks without looking too hard!).
Has anyone else seen this since the original post or @exilkubaner was a solution found to your problem?
Hi,
I have exactly the same problem. I hard reset my HTC 7 Pro, but no success, my screen doesn't respond until i lock/unlock the device.
So, any one have resolved this issue since the first post ?
Regards
Had the same issue, but I didn't have any roms installed.
Brought it in to Sprint and they found that I had a fried ribbon connecting the screen to the phone. Replaced under warranty.
It happened again, I determined that it was caused by my click in belt clip/holster. When I pull the phone out, it pulls the screen away from the keyboard a bit.
^Wow. Nice find. I'll have to be careful with mine now as I could easily run in to the same problem pulling it out like that.
VERY strange touch screen behaviour
Device: LG P920 Australian Optus Model, was upgraded to 2.3.5 using LG tools, then rooted ( cant remember which guide I used but it installed a package and su, was not superone click, maybe VRoot? it was for 2.3.5 and it worked) .
- then updated to v28b- eur- xx ICS , 4.0.4, kernal 3.0.21 using guides from Drastic00 xda guide
I am a bit of a phone noob, just learning to root using old samsungs and did my first ics flash on the LG P920. All good so far and thanks to all the guide contributors.
So the problem I am having in that the touch screen has two dead sections, the bottom section exactly covering the area occupied by the phone , message ect icons, and half way up a similar size section right across the phone. I have searched every post and forum I can find and cant find any thing like this. The touch screen works, just not in those sections. To get around it I can some times flip the phone to access things on parts of the screen that work, but a lot of time not.
I believe this started after I rooted the phone, although its always had issues with touch lag. If I hadnt rooted the phone, and its was just some random section I would put it down to hardware, but using the developer touch screen tests i can see the dead parts are exactly rectangle over the main phone controls at the bottom, which seems to me to indicate software, and on the new ics home screen I have activated the touches to be visual, and there are quite often two touch points racing back and forth along the little white line just above the dialer, message ect icons. when this happen you cant activate anything else because it thinks you are using two touches on the screen already.
I have used the LG remote computer controls program and i can access all sections of the screen perfectly through it, so that rules out everything but the link between the screen and phone in terms of software/ hardware. Have pulled off the ribbon plug and reattached also. I was hoping after upgrade to ICS it would be resolved but no luck. Unfortunately I cant remember how I rooted it but it was working fine for a few days then i noticed the touch issue after I started killing bloatware with Titanium. Is it possible removing an app has somehow messed up the touch screen code and its somehow not being repaired by the ics upgrade? Anyone seen this type of thing before. Found one post with a dead section after removing an app, but wast the whole bottom section and no ghost touches running around. Possessed?
http://forum.xda-developers.com/showthread.php?t=2213727
actually this post is similar to my problem but no solution found, will contact poster to see if it was a screen failure or software. My screen is also periodically doing the flashing buttons, going beserk thing as described in this post.
Hi,
Is there already a thread for OnePlus One screen responsiveness issues running on 44S? I've had a look but haven't found any.
I'm experiencing screen issues:
Two separate taps are sometimes registered as a swipe
Sometimes a single tap is not detected (hard to reproduce, though)
I have made two videos in preparation for a warranty claim, but I want to see if there's anything I can do before having to send it in for a month. The first video is of me typing - not using swipe/glide gestures, only tapping normally. On several occasions it thinks I'm swiping, however.
Sorry! I really want to post links to my videos, but I'm a new user.
OnePlus have admitted that there is a problem, but I heard they completely fixed it with the 44S update. Could it be that there's still something wrong, or maybe I have defective hardware?
Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.