Bought my One Plus 3t almost 14 days ago.
I am running latest freedom rom with xceed kernel.
This annoyance has kept going on intermittently. I noticed it when I'm on calls , but it still happens when I'm not.
I'll turn on the screen, use fingerprint, it unlocks phone, soft buttons work and UI responds, but the screen itself, won't respond to any of my touches. If i turn the screen off and on twice, it will begin responding.
WTH right?
Edit, def happens when i'm on a phone call way more, just happened twice while on the phone with OPO. could it be my glass screen protector?
anyone?
Never had that. You can't really do much warranty-wise unless you can replicate it with the stock ROM, as it could be a software issue (though it's unlikely).
Never had this. But I've only been running stock until 4.0.1 and from there clean Lineage OS with stock and Boeffla kernel.
Related
Im rooted, and oc at 1100. Havent done anything different lately except added Softlocker. Its kind of unresponsive. I have to hold down longer sometimes, but not by much. (just enough to dive me nuts lol). Any ideas why?
Not that i have an answer but.. mine is the same way for the first several minutes(i don't know how many) after i re-boot. It only started happening after i OC'd to 1100. Usually it gets to being normal after a while. Yes it is annoying..
Do you have soft locker installed? After I deleted it and rebooted it seems fine. So far at least lol.
This is a know issue if you use one of the OC kernels. Just turn your screen off and wait a few seconds and then turn it back on. Your screen will be back to normal.
No, I've had that. It's slightly different. Softlocker removal worked for me.
Sometimes my NC will start registering phantom touches, opening apps or links at random. If I sleep/wake it, it will again be OK for a few minutes. It seems to also appear if I use pinch zooming.
I first noticed it on Froyo, and now also on CM7 nightlies. I have tried the fix with ADB to recalibrate it, but it seems to always come back. I'm not sure if I'm not doing it right, or if it's because I flash a new ROM nearly every night.
Is the calibration setting something in firmware that stays set, or am I wiping it out every time I flash a new ROM?
claudius753 said:
Sometimes my NC will start registering phantom touches, opening apps or links at random. If I sleep/wake it, it will again be OK for a few minutes. It seems to also appear if I use pinch zooming.
I first noticed it on Froyo, and now also on CM7 nightlies. I have tried the fix with ADB to recalibrate it, but it seems to always come back. I'm not sure if I'm not doing it right, or if it's because I flash a new ROM nearly every night.
Is the calibration setting something in firmware that stays set, or am I wiping it out every time I flash a new ROM?
Click to expand...
Click to collapse
The Nook screen is incredibly sensitive to Moisture of any kind, Greasy Finger Prints, Water in the Air, Spit... Ect ect... Most People see a Huge leap in screen usability after installing a Good Screen Protector, many will recommend the Anti-Glare kit that B&N sells. I would also recommend it, as it has fixed 90% of my Screen problems.
Also there is a Known issue with Defective Chargers and you will see this type of Behavior while using the Charger on the Nook. Some have gotten replacements from B&N and say that it fixes the screen issues while charging.
I witnessed it today in my friend's office. Later found out that it only happened when he plugged in a different power source. The problem went away after he plugged it back to the B&N adapter.
Sent from my PC36100 using XDA App
My issue happens both when charging and when not charging. Though the moisture issue is a distinct possibility, I do notice that the screen gets very greasy compared to my phone's screen.
Have either of you tried the screen calibration through ADB? I'm still curious as to whether that setting is persistent or if it gets wiped with a rom flash.
I've never been one to use screen protectors, as I find they usually make the screen worse to use, and screw up the "feel" of the screen, if that makes sense. But it may be worth it to try one.
I'm having the same problems. Phantom touches and also the screen sometimes stops responding to touch. I just put it to sleep and then wake it up and all is fine. I'm definitely going to try a screen protector. I'm thinking it's related to moisture/etc.
I had the same problem. Made it next to impossible to get through a pdf on adobe. I had 1.0.1 stock, so I returned the nook color to factory default (the 8 failed boots + button/power on), upgraded to 1.1.0 through a sideloader, and then rooted. So far no more phantom touches after a day of use!
I think what might have been the cause was using 1.0.1 rooted stock NC and trying out HC. But I'm not sure. Mostly it's an educated guess that whomever did the custom rom made the screen more sensitive because they are running their unit with a screensaver.
I would try going back to factory default if you still have it or original rom, trying to update to 1.1.0 and then go from there.
Hello guys,
I've been testing all lolipop roms that had listed everything as working. Such as crDroid, CandyRom, SlimLP. On every of those lolipop roms pretty much most of the important stuff worked. There were stuff like equalizer not working or too dim notification LED, but from time to time I got touchscreen freezes. I mean I could use phone for a couple hours and then the touchscreen would freeze really often, sometimes it froze for couple of seconds and that was it and sometimes it could last for 10 minutes. This is really annoying and unacceptable if developer says that the touchscreen works.
I ended up contacting crDroid developer - davidteri81 and he said that the touchscreen works fine for him. I asked in the thread and I got only a single response saying he doesn't have this issue, but the sensivity is too high.
I've tried like literally 4 lolipop roms on my Z1 and each one of them had those touchscreen freezes. I even ended up flashing liquidsmooth in which I didn't had this issue, or it just didnt had the chance to happen since most stuff doesn't work there and it isn't usable as a daily driver so I quickly got rid of it.
My question here is:
Do you get touchscreen freezes? Please reply only after minimum 24h of usage. If you don't have any touchscreen freezes on lolipop rom on the Z1 then please, tell me what Lolipop rom do you use as I couldn't find any that wouldn't have a buggy touchscreen.
Please tell me if it works for you without issues or do you also have this issue on the Z1 as I'm puzzled because it couldn't be just me since I did a full phone wipe, flashed the phone clean, even wiping internal memory, but it still happens and I cant find a way to use any Lolipop rom everyday on my Z1. The more replies I get, the better.
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
schickel said:
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
Click to expand...
Click to collapse
Same for me, although, the touch screen did freeze once, but I locked it and unlocked it and it worked again. It's probably hardware since I got my Z1 replaced because of this issue that even happened on stock ROM occasionally.
using CandyRom 5.0.2
I never faced any touch freezes issue
@olokos: I'm on 20150214 and now I've got touchscreen freezes. This is the first time for me on Z1.
But I think that this could be a global Cm12 issue, because my Nexus 7 also get some freezes and I thought that something is wrong with my fingers or tempered glass.
The problem is how to debug this?
im on candy 5 and my screen dont freeze, but my screen percieves touches from nowhere... but only if i have earphone plugged in .. thats more than just annoying
anyone has the same prob?
sry for my really bad english
Touchscreen freezing issue definitely isn't hardware issue on custom roms. I haven't tried CM12 or any other apart from those listed on XDA, but I will propably build some lolipop rom from source by myself if I get enough reports that will be useful for me. If touchscreen works for you then please, tell me what rom you are using and for how long you use it, what't the way you flashed it.
I only need those 3 things. If touchscreen doesn't work just for me then I'll build my own stock based rom based on Sony sources. I just have to make sure that the touchscreen issue isn't just on my side.
All I need is:
Do you have touchscreen issues? Yes/no
What ROM/Kernel you are using? CandyRom 5.0
For how long? 5 weeks
Answer those 3 questions, legitimately and I'll consider that. I'm not sure If I'll have enough time to work on this, so please, be honest with your answers because I'm not going to fix the touchscreen, or maybe I will if it doesn't happen for everyone.
I experience dramatic touch screen freezes as well since the first time I installed Lollipop nightlies. (4 weeks now). Tried clearing cache, factory restores, de- and reinstalling apps. Reflash kernel, format SD, reinstalling gapps, puzzeling at logcat logs etc. Nothing helps. Random freezes from seconds till minutes. Only thing that 90% of the time will help is keep pressing powerbutton until screen becomes responsive. It happens more when I have a lot of (hangout or whatsapp) notifications, or when trying to type something (stock keyboard). Tried other keyboards: no luck. Tried every toggle: WiFi , Bluetooth etc. : no luck.
I experience dozens of freezes a day. Almost to the point that cm12 is completely unusable. Love this ROM, but this is a real showstopper.
1. No
2. AOSP Vanir 5.02
3. Since first availibility (12/14)
I experienced this issue on 2 roms in 2 forms
1. No (coming from Stock 14.4.A.0.108)
2. KitSlim_AMG [Evo 8.1] / iHackers advanced Stock Kernel
3. Since installing the Rom
This was the first time i experienced touch-issues. Not a freeze of the screen, but the screen sometimes started registering touch-events on the wrong places. This was temporarly fixed by locking/unlocking the display.
1. Yes (coming from KitSlim_AMG [Evo 8.1] )
2. crDroid-5.0.2-20150303-honami / 3.4.0-crDroid (packaged with rom)
3. Since installing the Rom a day ago
This time i get freezes. And they are much more frequent than those "ghost-inputs" from KitSlim_AMG. Unlocking the device also fixes it temporarly.
Hi all, lurker here.
I've been having an issue with my OP3T that hasn't really phased me until now. From time to time my phone would lock up and crash (phone shuts down unexpectedly). I would have to manually reboot the phone by holding the power down button.
I am running on OOS Beta 10, rooted with Magisk 13, EX Kernel and whatnot. This has happened prior to being on beta channel and root as well. I've read somewhere that this is a hardware issue that arises from SD821 clocking up to max Freq which causes the crash but I think even with the custom kernel and underclocking I am still experiencing lock ups.
If there is a log I can provide for you guys I can post it, just don't know which one.
Thanks.
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch ?
pitrus- said:
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch
Click to expand...
Click to collapse
I don't have Substratum installed
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
shivagajavelli said:
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
Click to expand...
Click to collapse
Damnn, i've got the same problem.. blank screen with white light notif then off, when 3T not get random shutdown they give me random restart every 2-3mins, aarrgggghhh really annoying!
same problem with my devices
And then whats the solution for these problem? Arrggghhh
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
Anyway which kernel?
I have the same with stock and beta OOS, stock and bluspark kernel. Never rooted. I though that maybe i just press power button in my pocket but then it happend on the desk as well.
Similar issue, sometimes black screen with unresponsive buttons (they do vibrate), sometimes I can unlock it via fingerprint to the home screen but touch is unresponsive, only appswitch via recents button works but can't exit the app with home button, sometimes it just reboots.
Never had these issues from dirty flashing from open betas but now when I started clean these things began lol. Seems more laggy too.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
I just clean flashed all stock, pure without UBL, root but still same. Then tried to UBL, MAGISK + Franco Kernel, and still the same condition...
Ahhh i hate this phone! Really sucks
Hmm yeah I've had another crash but this just happened during boot.
Still have no idea what the possible cause is. Not aure why it's just us few that are experiencing this.
Maybe faulty hardware? Who knows
I used to have this problem when running the open betas for the 3t, I moved over to RR and there hasn't been any problems especially after the latest update
Edit. Also when turning on the phone the bootanimation (the two dots spinning around the thingy) it would freeze constantly, also fixed after moving to RR
My phone was crashed few times when using cameraMX application. I do not know reason, maybe last update fault? I have simple question, why we have beta version? Where is stable
Yeh I've had it freeze on multiple accounts while booting up. It would crash while the two dots are spinning and would need a hard reset.
Many times it would crash when entering my PIN for smart lock or lock screen as well..
Issue seems to have popped up again., after flashing OOS OB 14.
Most frequent symptom is after entering pin or unlocking device, at random times it would lock up Android and crash (shut down, not reboot). So I have to boot my device again by holding down power button.
Hey, no long ago, about 2 weaks or so, I had to replace my broken screen. Everything is fine now, my screen isn't that great tho, but that's okay. But I've noticed something, before I used to have customs roms (mostly mokee os), but when I sent my device to a store to fix it, I reinstalled stock, when I receive it back, everything was great. But then, I got bored of stock, and reflashed Mokee (notice: I tried with LOS 14, MOS 15, MIUI) and then I realized that at random power ups my vibrations stops working. To make it work again, I have to reboot the device a few times. Anyone ever had any issues like that? What should I do? Remember: vibrations works fine on stock, only have this issue with customs roms.
warutzu said:
Hey, no long ago, about 2 weaks or so, I had to replace my broken screen. Everything is fine now, my screen isn't that great tho, but that's okay. But I've noticed something, before I used to have customs roms (mostly mokee os), but when I sent my device to a store to fix it, I reinstalled stock, when I receive it back, everything was great. But then, I got bored of stock, and reflashed Mokee (notice: I tried with LOS 14, MOS 15, MIUI) and then I realized that at random power ups my vibrations stops working. To make it work again, I have to reboot the device a few times. Anyone ever had any issues like that? What should I do? Remember: vibrations works fine on stock, only have this issue with customs roms.
Click to expand...
Click to collapse
I have had a similar problem, the "Vibrate on tap" didn't work with the replaced LCD and custom rom.
vhcolombo said:
I have had a similar problem, the "Vibrate on tap" didn't work with the replaced LCD and custom rom.
Click to expand...
Click to collapse
Did you fixed it?