Related
i am having a strange issue. Running Virgin Rom Google Edition 4.4.4.
Every time I am on the phone, screen turns black as expected. Yet, when I hang up, the screen doesn't turn on. Very often I cannot wake up the phone by pressing any button. After about a minute or two, it becomes responsive again, and I am able to turn the phone on.
When looking at Better Battery Stats, ProximitySensor is the biggest battery hug. In fact it runs for as long as the accumulated time of the phone calls I have mad or received.
In other words, it doesn't turn itself off when I am on the phone.
I tried blowing the compressed air through the top speaker and headphone jack with no improvement.
Is this hardware related or software related?
i tried other roms on this phone and don't remember having this issue.
I like using the AOSP based rom. If this is software related, can someone recomend another AOSP rom that works well and stable, and is as quick as snappy as the virgin rom I am using?
Any help, suggestions would be highly appreciated.
Thanks
That's an issue with aosp/cm ROMs, only in touchwiz it works as it should. It's also normal for it to be on while you are in a call. You can try opening the phone and blowing in it instead of just from the outside
I am confused by what you write.
You are saying there is an issue with aosp/cm roms. . Yet, you are also saying that it is normal for the proximity sensor to be constantly on while on the phone. Then if it is normal, than what is the issue with aosp rom? Does the proximity sensor stay on as well in TW roms?
Please clarify what you mean.
Thanks.
serio22 said:
That's an issue with aosp/cm ROMs, only in touchwiz it works as it should. It's also normal for it to be on while you are in a call. You can try opening the phone and blowing in it instead of just from the outside
Click to expand...
Click to collapse
Sorry I meant the issue with it not waking the phone up is the problem with aosp/cm ROMs. Proximity sensor needs a wakelock to detect when you move the device away from your ear so it can wake the phone up.. Wakelocks are not always bad
serio22 said:
Sorry I meant the issue with it not waking the phone up is the problem with aosp/cm ROMs. Proximity sensor needs a wakelock to detect when you move the device away from your ear so it can wake the phone up.. Wakelocks are not always bad
Click to expand...
Click to collapse
I dont know about it being a wakelock problem. I used to have this problem with the google play edition rom on my s4, where the screen will not come back on during a phone call, I got a air duster can and blow out the speaker above the screen. Samsung put the proximity sensor right behind the speaker for when you hold the phone up to your head and it get dirty easily.
Could you recommend a good TW rom that is light on resources and quick in real use?
Those are the aspects that attracted me to aosp roms in the first place.
retfeg said:
Could you recommend a good TW rom that is light on resources and quick in real use?
Those are the aspects that attracted me to aosp roms in the first place.
Click to expand...
Click to collapse
I generally don't recommend ROMs but Warpdrive is the lightest tw ROM I have ever used, its super debloated and fast, but I found there was home button lag at first, but this is because s-voice was removed and you can't easily disable the 'open by double taping home button' feature which is what makes it lag, so I installed S-voice myself, disabled the feature and the lag was gone
I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.
jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.
I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.
After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop
Hey guys,
Was wondering if anyone has experienced their Tab 3 8'' not waking up from sleep at random times.
This happens to be about once every day or two where i have to hold the power button to reset the tab because it won't wake.
I'm on the latest stock firmware.
Sent from my GT-I9100 using XDA-Developers mobile app
I had this happen before, but not as often as you experienced this. I am not sure what happens, but holding the power button to reset always fixes it, even though it is a pain to always have to do that. Also, I am running the latest CM13 rom, but I have experienced it on other roms as well.
Rawb0Ss said:
I had this happen before, but not as often as you experienced this. I am not sure what happens, but holding the power button to reset always fixes it, even though it is a pain to always have to do that. Also, I am running the latest CM13 rom, but I have experienced it on other roms as well.
Click to expand...
Click to collapse
Thanks for the reply. It's interesting it happens on CM13 too. I played around with different governors and schedulers but it doesn't change anything unfortunately.
I thought it might have something to do with leandroid toggling WiFi off for me at certain times as well, but I disabled that and it still goes into a sleep of death.
Sent from my GT-I9100 using XDA-Developers mobile app
44hats said:
Thanks for the reply. It's interesting it happens on CM13 too. I played around with different governors and schedulers but it doesn't change anything unfortunately.
I thought it might have something to do with leandroid toggling WiFi off for me at certain times as well, but I disabled that and it still goes into a sleep of death.
Click to expand...
Click to collapse
This problem is common maybe,it's because of your kernel is buggy or something
I have encountered this bug where I'm unable to use ambient display or wake up the display without the use of power button. Everytime I lock the screen it becomes unresponsive even the quick gestures don't work.
I have performed a soft reset but the problem has persisted.
Many other users seem to be suffering from this issue.
My device is full stock, no root or 3rd party apps on it.
Can anyone help me this this issue?
All users are facing this... It's because of battery optimisation.
No issues here. I am able to use the gestures just fine. Even the tap to wake and pick up to wake is working fine. I am 10.0.3 build.
I'm also having issues on tap to wake.
Happens to everyone. It's a hit or miss. Battery optimization makes the phone go into deep sleep and cause this issue is what i too understand.
Ya i did happen couple of times for me hope this bug get ironed out soon.
Sent from my HD1901 using Tapatalk
Same issue here also
Started encountering the issue recently - 3 days into ownership of the phone ?
The only peculiar thing I can remember is changing the override force dark toggle yesterday. And now that I recall, I don't remember seeing the ambient display since then. ?
Confirming I also have this issue. Very frustrating
I can trigger a black screen by holding the phone in landscape and launching the stock camera app. Then I have to hold Vol+/- and Power to reboot and it works again.
Hi guys. Found a fix on the OnePlus forum. Give it a try!
https://forums.oneplus.com/threads/fix-oneplus-7t-ambient-display-not-working.1128194/
i am also facing the same issue, where the tap on wake is not working when not using it for like 2hrs.
piyush.bhandari said:
Hi guys. Found a fix on the OnePlus forum. Give it a try!
https://forums.oneplus.com/threads/fix-oneplus-7t-ambient-display-not-working.1128194/
Click to expand...
Click to collapse
This worked for me at the first attempt . Thanks for the solution.
charan_55 said:
i am also facing the same issue, where the tap on wake is not working when not using it for like 2hrs.
Click to expand...
Click to collapse
Wow! A use for my work-issued iPhone! Yay, seems like its working.
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
all good on ArrowOS, DT2W and sleep working great... i know it's possibly not what ur looking for... but it's a seriously good rom.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
Yes, this happens also for me
I'd assume this would also be an issue on the Global rom?
If so, we can bring it to Poco's attention via Poco community forum.
Otherwise, we'd have to bring it to Xiaomi's attention on the Mi community forum.
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
this any good? or there's others if you search playstore....
this one maybe
(as a possible temporary solution, i mean)
EDIT: sorry, i read ur post as a touch sensitivity issue. have re-read, don't think those apps are of much use
Interestingly, don't have problems with double tap to wake, it works always, only with tapping for always on display to quick check time or notifications. Works 1 in 10 times. It's funny, tap, nothing, double tap ok.
Morak75 said:
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
Click to expand...
Click to collapse
same issue
Same issue, probably the biggest annoyance for me since I'm almost unable to use 10 second AOD tapping to conserve standby power.
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
blackhawk said:
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
Click to expand...
Click to collapse
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Nemix77 said:
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Click to expand...
Click to collapse
You be amazed how many have no clue or just don't think using of it.
It may be a settings glitch or again some sort of power management running amuck in the background. Play with it...
I posted the issue on Mi Community and Poco Community forum.
Not many people seem to use the double tab to wake feature with AOD set to 10 seconds.
I tried searching on Xiaomi and Poco both forums with keyword double tap and not a single thread for the Poco F3/Redmi K40.
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
I think youre right bro. If i time my taps perfectly and dont move position between taps, it works most of the time. Same goes for the AOD. Single tap works but it takes almost 2 seconds for the AOD to pop up which is pretty slow imo.
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Nemix77 said:
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Click to expand...
Click to collapse
Bro did you try single tapping and waiting for ~2 seconds?
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Nemix77 said:
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Click to expand...
Click to collapse
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
colosocool said:
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
Click to expand...
Click to collapse
Might depend on the device. Doesn't use much at all on my Samsung Note 10+.
With AOD touch to view active and phone/text running I use less than .5% @HR.
Never tried deactivating Double Tap on though... it's too useful.
More than likely it's not the culprit. Cloud apps and trashware like WhatsApp, FB, Google system apks are prime suspects.
Easy enough to test...