Related
Just checked my system update and there is a new one available.
System Upgrade 1.132.405.6 (18.1MB)
-Update: Improve screen control and Youtube client performance connection.
I'm guessing the youtube part is perhaps a solution to the crash error in the latest youtube update when you try to go back from landscape mode viewing. Screen control improvement possibly a Proximity Sensor fix?
Yet to download it but will try tonight on WiFi and update on what else seems to have changed.
just checked my had and found same update,,,here goes hope it fixes things and dont break anything (battery should last 5 days with new update )
wishfull thinking
Same here!
I can confirm this fixes the Youtube bug! Don,t have the prox. sensor issue, so can't check this!
+1 Fingers crossed
If you can't see it in the update section of your phone I've uploaded this RUU and others to:
http://mcgh.ee/DHD
Have just installed it, has made a definite improvement to the proximity sensor. Not holding my breath for the next couple of days though.
trevfee said:
Have just installed it, has made a definite improvement to the proximity sensor. Not holding my breath for the next couple of days though.
Click to expand...
Click to collapse
+1 here
got it here and it fixes youtube, one thing you have to say about HTC is that they sort out software issues pretty quick .The phones been out about what 10/14 days and 2 updates already , while some say there should not be faults, i look at it that at least they get their finger out and sort them
I like this "bug solving speed" too, compared to 5 months of solving 2.1 bugs in case of Motorola Milestone (which was extremly annoying as one of the bugs was a random reboot bug).
Nice seeing some updates but the sync problems on Exchange 2010 are still the same. I cant use the phone without this feature.
Yes, the Exchange Server 2010 Problem is still unsolved :-(
update, same as all, you tube fixed. i didnt have any issue with sensor ever so...
Can confirm that this update has new radio version: 26.03.02.26_M, HBoot remains at version: 0.85.0007
VISIONary still working nicely. I guess we will see exactly what they mean by "SCREEN CONTROL" in the update as the days move on.
mousey_ said:
If you can't see it in the update section of your phone I've uploaded this RUU and others to:
http://mcgh.ee/DHD
Click to expand...
Click to collapse
But 1.32.405.6 is missing there..
Lame old tmobile.. I get kicked from my data connection if I try to download the update.
And by kicked I mean lost all data for least 10th mins.
Sent from my Desire HD using XDA App
would like to hear more thoughts on the proximity sensor. did this fix it for anyone else?
whulfcastle said:
Lame old tmobile.. I get kicked from my data connection if I try to download the update.
Click to expand...
Click to collapse
Me too, I thought it was my signal at first and restarted the phone twice, I'll wait until I get home and use the WiFi
Just out of interest are people doing hard resets of the phone after an update? I had to do it after updating when I first got the phone and it solved a lot of the problems I'd started getting since the update but it just seems like effort to do it each time without a decent whole phone backup and restore facility in place.
yes confirm the update did download and install normally....I don't have the prox snsr issue, but seems to fix the youtube bug....
all go here.....love my device....
;-)
Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.
Nikouy said:
Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.
Click to expand...
Click to collapse
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.
You_got_owned123 said:
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.
Click to expand...
Click to collapse
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Happy to know I am not the only one having this issue , good that we are on the same boat.
I'm travelling in a few days and can't go abroad with the phone in this "working" conditions so I will have to downgrade for sure. Any 5.0 ROM to recommend? A solution for 5.1 would be better
haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!
guih said:
haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!
Click to expand...
Click to collapse
I flashed Slim ROM, touches delay improved a bit but I was experiencing some lag on the hardware keys.
I just flashed last bacon firmware (from April 09) and RobbieL811 ROM and seems to be running smoothly, I wonder if it was a firmware issue. Thoughts?
Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..
Infinityyy said:
Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..
Click to expand...
Click to collapse
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?
gsmyth said:
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?
Click to expand...
Click to collapse
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.
guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Infinityyy said:
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.
Click to expand...
Click to collapse
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.
Nikouy said:
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.
Click to expand...
Click to collapse
we're not alone man, multiple threads are popping up with people suffering from similar issues, including on reddit: http://www.reddit.com/r/oneplus/comments/33ky0u/open_post_to_oneplus_with_all_our_love_and/
I am having the same severe issues as well.
The nightmare begun after the 05Q update.
Ever since that update, no matter what I've tried, the touch problem is here.
I've tried numerous Roms + kernels combinations with no use.
OP support was trying twice to reset my phone to full factory reset to both Oxygen & CM11s with no use.
That is so frustrating.
i have the same problem, but only when i go outside and the weather is nice
Hi there,
(Im opening a new thread as the old one was completely off the topic of the original post)
So on CM11S, my phone screen was working fine. After the CM12S update, my phones screen sometimes doesn't respond correctly when I go to unlock my phone with the unlock pattern. (The timing of the update and the problem occurring may just be coincidence) Its as if holding your finger on the screen isn't registered as staying on the screen, its like the phone thinks I am lifting my finger off and reapplying it very quickly, I cant draw my unlock pattern and unlock my phone. It also affects the 'swipe down' I must do to get the unlock pattern prompt.
If I restart my phone, it usually fixes the problem. Although in the past few days, it has started happening more frequently and sometimes restarting the phone doesn't solve the issue. It is becoming more of a frustration now because of how frequently I have to restart my phone just to unlock it.
I first believed that using a glass screen protector was the problem, I thought the glass was causing ghost touches, so I removed my glass protector and replaced it with a film protector, at first it seemed that this was the problem, but I have just encountered the problem again. I'm not sure if its a hardware or a software issue, because restarting the device is fixing the problem most of the time, but its also switching off all power to the digitizer during a reboot so I cant tell what is the culprit.
I've opened a support ticket with OnePlus but it says it can be up to 10 days before I get a reply, I figured I'd post here too to see if anyone else has had similar issues or even found a fix.
Thanks in advance!
I had the same problem
I was having the same issue, although I never updated to CM12S. Instead, this happened to me when running Exodus Lollipop ROM and the SlimLP ROM. Since then, I have switched to Paranoid Android Alpha2 and have not had the issue recur in the last few days running PA. So to me it seems like a software glitch in many of the Lollipop ROMs. Try PA if you like and see if it's fixed.
welcome to ghost touch
google "oneplus one ghost touch" and join the hundreds of other known cases
I had a feeling this was the ghost touch issue, but my phone hasn't really had actual ghost touches, its just that most of screen stops working. I've got a few videos of it happening. First the screen goes a bit unresponsive, then after a short while, about 1/3 of the screen is completely unresponsive, I switched on show touches in development options and you can see that from the middle to the bottom of the screen there is no response unless I use the very edge on the right side, then it works, its like it has a dead spot. If I reboot my phone, that usually fixes the problem for a while, sometimes up to a whole day, but the problem comes back with time.
I was given a patch by the OnePlus automated support message, and it says my case has been forwarded to a specialist. I have just applied the patch which has rolled me back to CM11, I'm guessing it did more than just that, but the patch and notes don't really explain what it does. Either way, I'm in the process of receiving OTA updates so I can get back on CO12 so I can hopefully restore my data with my ADB backup (never done this before, not rooted my One yet)
Has anyone had any success with this patch?
Thanks
EDIT: So my ADB Backup isn't restoring on my phone. I am using Holo Backup (formerly Simple ADB Backup) and when I chose restore and select the backup, it just show the output for the help command from ADB and then doesnt appear to do anything else. Are there any manual commands to restore my backup or have I done something wrong?
Try going back to cm11s and then check...
Sent from Android (a google product)
Hi there,
So heres an update, I applied the first patch and it rolled me back to CM11S and the issue was still present on CM11S, I then got OTA's back up to CO12 and the issue still happens. I have turned off the off screen gestures and the ambient wakeup thing. It doesn't happen as often but when it happens, 2 restarts are needed to get it running smooth again.
My support ticket with OnePlus has gone quiet and I don't really know what my next step is? I have heard there is a second patch but I couldn't backup properly last time with ADB so I don't know if I want to go through all of the wiping and reupdating again when people report the 2nd patch is also ineffective.
Does anyone have any suggestions? I feel a bit cheated now knowing that my phone has what I can tell to be a manufacturing defect / hardware issue.
Another update here.
So after a week of silence from the OnePlus tech support, I have a new person handling my ticket and he has told me that I need to apply another display patch. I'm guessing this is the 2nd patch and not this final patch which was mentioned by Carl on Facebook.
Either way, I ran into a problem applying the 1st patch, I couldn't make a proper backup of my phone before I did the patch. I used SimpleADBBackup which I thought would work well but it took a very long time to create the backup and then when I applied the backup back onto my newly flashed phone, It missed many apps, only did app data for a few apps and didn't take any of my pictures or SD storage, so all my SMS and Call log backups were also lost. I would like to take a proper backup this time but I don't know how to do it? I don't trust this ADB backup method, even on the Simple ADB Backup program, it admits that ADB backups are hacky and untested.
I have been trying to use Helium but for some reason, my phone wont get past connecting it to the computer companion app, I have all phone drivers and ADB drivers installed correctly, but helium on the android side cant seem to see the computer app, the computer side of the app says that helium is enabled, but on my phone it is stuck on "waiting for the helium desktop app".
I feel like I'm having the worst luck with this phone, and its frustrating because I really like this phone and this flaw is really getting in the way of using this phone, I counted 8 restarts in one day due to the screen not working.
I hope someone can help me out, I don't want to fully wipe my phone again and I cant seem to back anything up correctly!
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
naghtan said:
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
Click to expand...
Click to collapse
I'm not sure if a full solution has been found yet. I read on Facebook that they are working with Synaptics to make a final patch which should solve the issue.
I've given up on trying to backup my phone without root, it just seems impossible to do right. I've just applied the 2nd display patch and got my phone running again, I think I may stay on CM11 and just forget lollipop until this issue gets resolved. I'm pretty sure last time I was on KitKat, the issues were there still but it may be less frequent, who knows?!
Do I have a better chance of seeing this screen issue less on KitKat or should I just update to CO12 for the 3rd time?
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
donk165 said:
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
Click to expand...
Click to collapse
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
vickykolari said:
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
Click to expand...
Click to collapse
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
I write with the assistance for 10 posts at today and I declare them to STOP sending me those bug non fixing ROMS/ZIPS...
I will replace by myself the screen (they don't change it in warranty because I've on the frame some dents... )
It's a clear HW issue, on any software, if the display degrade to a "fail stage" you wan't come back never to a total solve situation.
I loved my Oneplus, but they buy some batches of too cheap display, and after some month, I see clearly the results.
donk165 said:
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
Click to expand...
Click to collapse
I wish you all the luck mate..
vickykolari said:
I wish you all the luck mate..
Click to expand...
Click to collapse
Thanks man,
It went well, I have been issued an RMA and will be sending it back soon. Just waiting on the postage label.
Ive just received my new OnePlus One today, very chuffed as it hasn't cost me anything. RMA and Support with OnePlus may be a bit slow but at least they do the right things!
To anyone facing screen issues, create a support ticket and persist with it, it should pay off!
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
anugrah n3xu5 said:
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
donk165 said:
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
Click to expand...
Click to collapse
Congrats! Enjoy the beast
Sent from my A0001 using Tapatalk
Got a notification this morning. Anyone upgraded?
@anewday, you got screenshot of the update notification? Is it ending with PL#, then it must be December security patch. What's the build no.?
Mmb29k.g920vvru4cpk2
Yes, it's been running smoothly since last night.
txtl said:
Yes, it's been running smoothly since last night.
Click to expand...
Click to collapse
Whats different?
I think it's the November security patch.
AsaSpades said:
Whats different?
Click to expand...
Click to collapse
Just Nov security patches ,and samsung music is removed. Feel a little bit smoother.
Anyone seeing battery issues after this latest update? I already used package diablerie pro to remove bloat and I am still seeing terrible battery life.
JCTechie said:
Anyone seeing battery issues after this latest update? I already used package diablerie pro to remove bloat and I am still seeing terrible battery life.
Click to expand...
Click to collapse
Usually takes a few days to settle down after an upgrade. Give it a little time and see how it goes.
Touch and performance issues with Verizon update G925VVRU4CPK2 Galaxy S6E 12/16/16
sometimes, as in for short periods throughout the day the phone detects touches as a jump from one letter to the next; consequently, not inputting the first character but the second. This impairs my typing, so I have to type significantly slower for it to understand I'm typing different letters. this also affects any touch movement and the phone's performance as it lags as well as misses certain touches. This only happened after this update on 12/16/16. Not only does did it affect my phone but my brother installed the update as well and his phone (same model) is experiencing the same issues. I had nova launcher as well which i uninstalled and I have deleted the cache multiple times, started the phone in safe mode and was not able to use the phone codes since Verizon blocked access to updating the touchscreen's firmware. It is not a constant issue but it happens at least a couple times as day which is extremely annoying when trying to type or move around.
If anyone has encountered a similar problem or has a possible solution I would greatly appreciate any help
My device is Unrooted
Does service mode still work? Go to dialer and input *#0011#
anewday said:
Does service mode still work? Go to dialer and input *#0011#
Click to expand...
Click to collapse
Could someone try and let me know. I wouldn't upgrade if service mode doesn't work. Much appreciated.
So since about 2 days ago the phone just start freezing. Sometimes it just restarted randomly, but mainly freezing at least every 5 minutes. The power button alone wouldn't turn it off no matter how long I held it. Always have to use Pwr+Vol Down to reboot.
I put up with it because I've been busy, but finally tried wiping cache - no profit. Tried safe mode - no profit. Factory reset- negative profit. After the reset it just seems to restart a bit more often but in general it freezes less, making the timing seem even more random.
This happened when I first got it (used). It was restarting due to the fresh 7.0 update. So a factory reset fixed it and it was smooth sailing for like 3 months or something. I know there was a minor system update a few days ago but those dont usually call for a factory reset. I tried it anyway and it just didnt work. I had actually even tried uninstalling all the app updates from the night before it started happening. but safe mode couldn't even fix the problem so I guess that was moot.
Software version: G920VVRS4DQE1
Stock everything - I dont hack my daily drivers at all
Android 7.0
Mainly I'd like to know if Im alone. A fix would be great but I'm hoping it's not specific to my device. If it's a hardware issue I'm gonna give it a swift toss down the stairs and maybe deliver a nasty curb stomp to it right afterward.
Any advice?
I'm running into the same exact issue. Same build, and am running out of ideas.
Lathorus said:
I'm running into the same exact issue. Same build, and am running out of ideas.
Click to expand...
Click to collapse
Good to know its not just me. Did it start after a recent update for you also? That would give me hope that its not faulty hardware. Maybe just a bad update.
sawyerbenjamin said:
Good to know its not just me. Did it start after a recent update for you also? That would give me hope that its not faulty hardware. Maybe just a bad update.
Click to expand...
Click to collapse
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Lathorus said:
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Click to expand...
Click to collapse
Same for Verizon. I guess I'll just hold out, using a backup phone, until a new update hopefully fixes it.
Lathorus said:
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Click to expand...
Click to collapse
Gonna go ahead and revive this. It seems to work fine when the sim card is out. I recommend you see if it's the same with you. I've charged it up before work multiple times before work days and come home from to see that it never restarted. I was able to test this using the fingerprint feature; it isn't asking me to use pattern like it does after boot.
No one else is chiming in but, since we're both on Verizon, I'm having a feeling that it's directly related to the SIM/carrier.