Hi guys
I recently bought an OnePlus 2. With the original firmware, I experienced a very strange and very annoying issue: My screen randomly turned off (e.g. during a chat in WhatsApp). The screen turns off and I have to turn it on again by pressing the power button. Then I enter my PIN to access my phone again and it locks AGAIN. This happens like 10 times in a row, then I have to reboot the phone and it was OK again. I seriously don't know what triggered this issue.
However, recently I got pissed of because I tried to call one of my customers and as soon as I entered my PIN and tried to open the phone app, the screen locked again and I almost threw away my phone. Damned troll.
So I decided to try another ROM as I thought it was an OS-related issue. Now I'm running Exodus Android 6.0.1. I did a clean install and guess what: The issue came back on this ROM...
In my opinion there's only something both installations (my previous 5.1.1 stock ROM and my current 6.0.1 ROM) have in common: I've been using XPosed with Amplify, Greenify and XPrivacy. Other than that, I have no idea what it might be.
Have you encountered the same or a similar issue? If so, were you able to solve it? How did you solve it?
I just uninstalled Amplify, as I think it stops somehow the Gyroscope service, that's why it locks randomly. I'll check if the issue appears again...
I think I have good news for you guys: I guess I was able to locate the issue.
I noticed it always happened when I was holding the phone in the hand I had a ring on my finger. Then I found out the phone has magnetic sensors (for flip covers).
I downloaded the Xposed module "Magnet Sensor Control", the bug hasn't appeared so far!
I hope I was able to help you guys with my findings. This thread may be closed now.
Related
I have a major problem with the slide lock function on the HD2. When the screen is locked, if the device is placed flat on a table (screen up), the screen lights every 30seconds, then dims, then goes off, then relights again.
This is killing my battery life. I haven't been able to find any other reports of this on this forum.
There are no notifications waiting on the phone while this is happening.
The only modification I have made to this device is to disable the HTC messaging app (using Zenyee's cab).
Anyone have any ideas?
Have you installed any other software at all?
Hmmm, now it has stopped doing it. Randomly. After doing it non-stop for 3 days, it suddenly stopped.
There's a lot of that kind of stuff going on with the HD2 ROM.
s0uthpaw said:
Hmmm, now it has stopped doing it. Randomly. After doing it non-stop for 3 days, it suddenly stopped.
There's a lot of that kind of stuff going on with the HD2 ROM.
Click to expand...
Click to collapse
It's not the "HD2 ROM". It's some buggy software that you installed on the phone yourself.
The phone does not do that out of the box (or with the official ROM updates.)
Try to think back to when it started happening, and what you'd recently installed. Uninstalling may not solve the problem, as you can't guarantee that all the changes will be backed out, but try to remember what you installed that caused this problem and uninstall it. If this doesn't work, a hard reset will probably be required.
This is my first post on this forum. I searched around here for a solution, didn't really find one matching my problem. I am not a phone wizard or anything like that either. So I'll try my best explaining my problem.
First things first:
Phone: Note 4
Model #: SM-N910T
Android Version: 5.1.1
Rom: Stock Rom
Rooted: Rooted Once and used a custom Stock T Mobile Rom Once.
Here's the ROM I used at the time: http://forum.xda-developers.com/not...10tuvu1cog2-debloated-deodexed-stock-t3175406
Recently I So recently my phone out of the blue started lagging, freezing, and restarting itself. I didn't download any applications or anything like that for it to freeze up. I was currently then on the custom ROM I have mentioned above and it was the updated version. I have tried everything to my knowledge to try and fix the problem. I have tried going back to stock T mobile ROM (currently on stock rom now) through odin and stuff. After all that, it was still lagging, freezing, and restarting etc... Ran it through safe mode and the only problem in safe mode is that the lag is gone, but the restart is still there. Running in safe mode, if I would turn the screen off and back on to unlock my phone, there would be like 40% chance that it would restart after unlocking the phone and the phone would just restart normally. Rarely, whenever my phone would attempt to restart.. I would get a "Could not boot normally" message along with couples codes below and the image of android guy. Then I would have to take my battery out and attempt to restart the phone once again.. I've wiped the cache and everything in recovery mode, nothing helps at all. Also, the phone is in perfect condition. Hasn't been dropped, cracked, no water damage, or anything like that.
This place is my only hope to fix my phone before I will go out to buy another phone from the carrier.
Thank you all for taking your time to help me
u r not alone
hi, huntitude. even i am experiencing similar issues. kindly follow this thread and update if u find any solution
http://forum.xda-developers.com/note-4/help/frustrating-problem-phone-lagging-t3336964
doctor geek said:
hi, huntitude. even i am experiencing similar issues. kindly follow this thread and update if u find any solution
http://forum.xda-developers.com/note-4/help/frustrating-problem-phone-lagging-t3336964
Click to expand...
Click to collapse
Well I already got rid of my note 4 unfortunately before anyone could help me here so I had to upgrade my phone to note 5 and return note 4. While I still had my note 4, I realized something weird. While the phone was lagging and crashing etc.. When I had it plugged in for charge it would work perfectly fine. No lag, it wouldn't freeze up or restart (had it running perfect for 7 hours). It was like my phone was brand new again. As soon as I unplugged it from the charger, few minutes in and it was back to restarting and all that. I never knew why it did that.
Anyone know why this mightve happened?
Might be the battery though
I thought that too. I tried my brothers note 4 battery for awhile and it worked for a little bit and then it started doing the same thing even on his battery. Shrugs.
Huntitude said:
I thought that too. I tried my brothers note 4 battery for awhile and it worked for a little bit and then it started doing the same thing even on his battery. Shrugs.
Click to expand...
Click to collapse
In the COH update iteration there is an annoying bug that affect fingerprint.
The bug causing the phone to restart, lagging & closing all apps randomly when the fingerprint is set.
May be this one is also the same.
Try to disable all fingerprint related settings.
d4rkkn16ht said:
In the COH update iteration there is an annoying bug that affect fingerprint.
The bug causing the phone to restart, lagging & closing all apps randomly when the fingerprint is set.
May be this one is also the same.
Try to disable all fingerprint related settings.
Click to expand...
Click to collapse
I never used finger print scanning on my Note 4. Always disabled.
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks!:crying: I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet and never had a flip cover or any sort of case so literally don't know why it happened.
Thanks in advance,
Max
Hi
I had the exact same issue with mine, I was on LineageOS and could access the logs so I was able to determine it was an hardware failure.
Went to a repair shop to replace the home button, and Bam it worked again.
If you didn't flash a custom ROM it is likely an hardware issue just like I had.
Hi, first of all I apologise if this question has been asked but I don't know how to search just this place.
I'm using everything stock, no root, stock launcher.
I have my phone set up to ask for the password on reboot. I have my fingerprint reader set up to unlock my phone. I also have the fingerprint reader set up to wake the screen.
However under certain circumstances the fingerprint reader does not unlock the phone. The most reliable way to trigger this behavior is to plug the phone in to charge.
I exclusively lock the screen with the power button.
The fingerprint reader is still responsive and it still wakes the screen but there's no vibration feedback and it does not unlock. After I unlocked the phone with my password and lock it again the reader works again.
So what's going on here? How should I debug this?
After reboot it is normal to ask for password first time. Sometimes i have also seen this but when i unlock with pattern (my backup way) and lock again it works fine. I can not trace this to be related with charging or something else and it happens rarely but i have seen it also. Maybe a software bug.
Looking back to the days when i have LG V10 i remember that i had the same problem with fingerprint sensor not working sometimes. It was more frequently related to heat buildup as it was hot phone anyway.
I had the same problem these days, I think the fingerprint reader won't work if your hands are really cold.
Hmm I don't think my U Ultra is getting particularly hot and, no, my hands are certainly not very cold either. This behavior happens indoors.
It's just extra security plan and simple
Sometimes, not very often though, my fingerprint reader refuses to respond. Not even a misread where you get haptic feedback and not a lot else.
Just using the power button and entering my back up security (pattern in my case) and it comes back to life.
I don't particularly worry about it, but I suppose it's nice to see that it's not just me
Will see if the upgrade to 8.0 fixes it.
I met this problem.The solution was very interesting.I use Yandex.disk app.This problem did occur after the Yandex.disk app is update.I hard reset my phone.The problem was not in my phone.But I setup Yandex.Disk app the problem repeat occur.İf you installed Yandex.Disk, uninstall the application.if you don't use Yandex.Disk,The last apps update uninstall to try.
Good Lord I have so many apps installed though...
Then go to a full factory reset and see if it helps, thats the 1st thing you do when you have problem.
After a bit of experimentation this behavior seems to have stopped after I disabled/removed all Smart Lock Trusted Places -- a feature that is already known to be buggy.
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Garkan said:
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Click to expand...
Click to collapse
8 fixed this bug for me but i found more bugs in oreo so i am thinking to roll back to 7.0 and meet fingerprint sensor bug again because oreo problems are disgusting - car bluetooth does not works as it should - i can't read addressbook in my car head unit - it shows error. i found that is some bluetooth software parts was not included in 8.0 but successfully fixed in 8.1. and i'am pretty sure we will never receive 8.1 for u ultra.
in russian 4pda forum i found some reports (unconfirmed yet) that fingerprint bug disappeared. maybe somebody here can confirmed it?
No i have android 8 and issue still occurs sadly did not found a fix.
I've suddenly had this issue a couple of days ago a couple of times. I didn't do anything (except a couple of reboots) and it was fixed again.
Now after updating to Oreo and again using leedroids ROM, i didn't experience theissue again..
I talked to a htc representative and said to clear credentials from security/encryption and credentials seems to be a conflict in security certificates. For the moment it works.
Hello XDA,
This is my very first community post so please don't judge if I do something wrong here
Let's cut to the chase. I am a happy owner of the OP6T 8/256gb phone and I am super happy with the device, however, I have been having an awkward issue. From time to time, couple of times a day, my phone would not recognize neither double tap nor the power button to wake the display up. Usually out of frustration I press the power button couple of more time, but nothing happens. Then after 3-4 seconds the display wakes up and even opens the camera (because I pressed the button couple of times, but not in a fast way...). Afterwards, the phone works without an issue until same thing happens hours later.
So my question is if anyone is experiencing anything similar and found the culprit of it?
If you need any additional info on my settings, please let me know!
It is not the worst thing that could be happening with a new phone, but you know, one expects the brand new phone to work 100% of the time
Looking forward to your replies and ideas!
Many thanks,
Donatas
It's happened to me only recently. I'm rooted with magisk 17.3 running a few modules such as dual speaker, Google dialer framework and viper. I was on stock kernel, but switched to Smurf kernel without any hiccups so far.
Well I am full stock, even with stock launcher... That's why it bothers me that it is happening:/ thanks for your reply
Donis.za said:
Hello XDA,
This is my very first community post so please don't judge if I do something wrong here
Let's cut to the chase. I am a happy owner of the OP6T 8/256gb phone and I am super happy with the device, however, I have been having an awkward issue. From time to time, couple of times a day, my phone would not recognize neither double tap nor the power button to wake the display up. Usually out of frustration I press the power button couple of more time, but nothing happens. Then after 3-4 seconds the display wakes up and even opens the camera (because I pressed the button couple of times, but not in a fast way...). Afterwards, the phone works without an issue until same thing happens hours later.
So my question is if anyone is experiencing anything similar and found the culprit of it?
If you need any additional info on my settings, please let me know!
It is not the worst thing that could be happening with a new phone, but you know, one expects the brand new phone to work 100% of the time
Looking forward to your replies and ideas!
Many thanks,
Donatas
Click to expand...
Click to collapse
Yes this has happened to me, glad to see I'm not alone.
It happeneds randomly, like few times a day, not too frequent to render the device unusable, but enough to be irritating - especially when it's a brand new device.
My setup;
*Rooted
*Magisk (viper & YouTube vanced module)
*Stock kernel
I'm at a loss as to what's the cause of this issue, it's very weird, it could just be an oxygen os bug that will be resolved by OnePlus. Who knows. Hopefully if more people comment about this here - we will eventually get to the bottom of it.
So far on 9.0.6 build the issue appears to have been fixed, I have not had any random temporary lock screen freeze.
Can anyone else confirm this?
krohme said:
So far on 9.0.6 build the issue appears to have been fixed, I have not had any random temporary lock screen freeze.
Can anyone else confirm this?
Click to expand...
Click to collapse
Glad to hear it is fixed for you!
Unfortunately, since the update, I already experienced it 4 times...
Even more so, sometimes now the phone would randomly stop playing music from Soundcloud (I dont know about other apps, i predominantly use Soundcloud).
I love the phone but it is a little shame that some of these features are failing
Hope 1+ will fix this and we all be happy!
Yeah, sometimes my device doesn't respond to double-tap. Usually I just have to double-tap again and it wakes up. I haven't noticed the issue with the power button, but I rarely use that to wake the device. I did have a situation recently where the device wouldn't wake from a screen tap no matter how many times I tried. I can't recall if using the power button woke it or if I had to force a reboot. But that's only happened that one time.
I just updated to 9.0.6 a day ago. I don't think I've experienced any non-wake issues since then. Really haven't been paying that close attention, I guess.
I believe I am having this issue. I just flashed 9.0.7 from TMO and I'm rooted with magisk v4a and vanced. I get random freezes where I can't tap anything on my screen. I have to turn it off and on with the power button.
I experience this as well. I thought it was just an isolated thing, and it's kinda annoying...
It's very irritating. I'm trying to pin point it and so far I notice it with Firefox and Spotify transitions.