Has anyone had their phone screen just turn on when it was in standby for no apparent reason, My G5 just received a message placed next to the XP, then the XP screen just came on, there was no message, email or even phone call.
I haven't experienced this yet.
Sent from my F8132 using XDA-Developers mobile app
augie7107 said:
I haven't experienced this yet.
Sent from my F8132 using XDA-Developers mobile app
Click to expand...
Click to collapse
Not really a big problem, but was just wondering what triggered the screen to wake from standby.
kms108 said:
Has anyone had their phone screen just turn on when it was in standby for no apparent reason, My G5 just received a message placed next to the XP, then the XP screen just came on, there was no message, email or even phone call.
Click to expand...
Click to collapse
I have not experienced this yet either, but my touch screen sometimes glitch... Maybe related in a way
Sent from my F8131 using XDA-Developers mobile app
HellRoot said:
I have not experienced this yet either, but my touch screen sometimes glitch... Maybe related in a way
Sent from my F8131 using XDA-Developers mobile app
Click to expand...
Click to collapse
could be something in the background that triggered it, may be the reception or something.
kms108 said:
Has anyone had their phone screen just turn on when it was in standby for no apparent reason, My G5 just received a message placed next to the XP, then the XP screen just came on, there was no message, email or even phone call.
Click to expand...
Click to collapse
Yes, my XP wakes up several times per day just as you described, but the touch screen still works fine.
I enabled the double-tap wakup function and I usually keep charging it while working. I don't know whether these matter or not.
chrisyuhc said:
Yes, my XP wakes up several times per day just as you described, but the touch screen still works fine.
I enabled the double-tap wakup function and I usually keep charging it while working. I don't know whether these matter or not.
Click to expand...
Click to collapse
it has nothing to do with the touch, I think its something in The back ground or just a bug.
if I were you only charge the phone if needed to prolong the battery life.
i normal charge the phone when it reach about 10-15% and disconnect about 90%.
I haven't had any of these problems.
I did a master reset to check something out, not that it had a problem, but the display wake up hasn't shown up yet after the hard master reset, but a local LG rep and sony rep did say that some previous phone (Sony and other phones) did have this problem, it was something about apps running in the background.
well it isn't really a big problem, as said could be a app, or just a minor bug.
Related
I think I have the weirdest problem with my Sensation XL.
It works fine and sometimes, when I unlock it, the touch screen goes into super frenzy mode and starts doing things on its own. When it's stuck in that mode, I cannot use it, and it clicks buttons around randomly and very fast.
I have seen it open my messages, swipe a long gibberish text and send it (!) or this morning it just opened contacts and deleted one!
I am pretty sure it's all in random because on the keyboard I can see it swiping very randomly around the screen and in a very fast speed.
What on earth is this and how do I stop it? It almost looks like a virus or some sort of spyware but I checked and see nothing malicious installed.
The phone is about 8 months old and is not rooted. Latest firmware installed.(4.0.3 Android version).
The crazy behaviour did not coincide with any updates in software. Just started 3 weeks ago randomly and happened maybe 5 times till now.
The only way to stop your phone going mad and doing something you don't want it to do is to quickly rip the battery off, because you are unable to restart it from the touch screen.
It only happens after you unlock it, not while you're using it and I noticed it happens after a long period of inactivity.
Has anyone had that? Any help is very appreciated!
Thank you
nkomp18 said:
I think I have the weirdest problem with my Sensation XL.
It works fine and sometimes, when I unlock it, the touch screen goes into super frenzy mode and starts doing things on its own. When it's stuck in that mode, I cannot use it, and it clicks buttons around randomly and very fast.
I have seen it open my messages, swipe a long gibberish text and send it (!) or this morning it just opened contacts and deleted one!
I am pretty sure it's all in random because on the keyboard I can see it swiping very randomly around the screen and in a very fast speed.
What on earth is this and how do I stop it? It almost looks like a virus or some sort of spyware but I checked and see nothing malicious installed.
The phone is about 8 months old and is not rooted. Latest firmware installed.(4.0.3 Android version).
The crazy behaviour did not coincide with any updates in software. Just started 3 weeks ago randomly and happened maybe 5 times till now.
The only way to stop your phone going mad and doing something you don't want it to do is to quickly rip the battery off, because you are unable to restart it from the touch screen.
It only happens after you unlock it, not while you're using it and I noticed it happens after a long period of inactivity.
Has anyone had that? Any help is very appreciated!
Thank you
Click to expand...
Click to collapse
Lock the screen and open it again. If this doesn't stop it could be a Hardware problem
I also had some problems like this on the original firmware, but rarely, it got fixed when i flashed Incredibly Cool Sense v3. You should lock the screen not to rip the battery off, as it's faster and it should work
Lexmazter said:
Lock the screen and open it again. If this doesn't stop it could be a Hardware problem
I also had some problems like this on the original firmware, but rarely, it got fixed when i flashed Incredibly Cool Sense v3. You should lock the screen not to rip the battery off, as it's faster and it should work
Click to expand...
Click to collapse
I don't think it's a hardware issue cause the phone works well most of the time. If it was hardware the problem would be permanent, not intermittent and especially so occasional.
Must be something software related, I did add a lot of games to the phone recently but the problem happens even when these processes aren't running in the background which is puzzling.
Locking and unlocking the screen postpones the problem, it doesn't solve it. As soon as the screen is unlocked, it immediately goes crazy again.
I can only solve it by pulling the battery out, and FAST, before it sends crazy messages to my contacts
nkomp18 said:
I don't think it's a hardware issue cause the phone works well most of the time. If it was hardware the problem would be permanent, not intermittent and especially so occasional.
Must be something software related, I did add a lot of games to the phone recently but the problem happens even when these processes aren't running in the background which is puzzling.
Locking and unlocking the screen postpones the problem, it doesn't solve it. As soon as the screen is unlocked, it immediately goes crazy again.
I can only solve it by pulling the battery out, and FAST, before it sends crazy messages to my contacts
Click to expand...
Click to collapse
Welcome to the club. I had that same issue. But after a hard reset everything is fine with mine.
I assume that there was an app causing all that. If after a hard reset still does that you should send it for repair
If you have a screen protector its can be a main reason for this. To stop this behavior you can use power button and wake up it again. Some htc devices have the problem with multi touch screen
Issues of production. Clear the screen products with some alcohol and see than.
Sent from my HTC One X using xda premium
I don't have a screen protector actually and the screen is usually clean.
Must be some app, I wonder there was some way to find out which without having to do a hard reset and lose everything
stona175 said:
If you have a screen protector its can be a main reason for this. To stop this behavior you can use power button and wake up it again. Some htc devices have the problem with multi touch screen
Issues of production. Clear the screen products with some alcohol and see than.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
nkomp18 said:
I don't have a screen protector actually and the screen is usually clean.
Must be some app, I wonder there was some way to find out which without having to do a hard reset and lose everything
Click to expand...
Click to collapse
You can't! There is no way you can find out which one is causing that. Maybe it's some update from something that is causing the freezing.
Last night i did notice something else though. My battery was almost empty and i took my gf charger. She has S2 and after i charged my phone it has started to act strange......... Even today after i pluged the phone to install something from the PC it didn't even notice that i have connected it to the PC. Took me about 20 min in/out to get it running I clean the usb slot every week so it is not a dirt issue....
it happens with me when there's water on the screen
Send from my lovely Sensation XL, from a little town in france with a very very slow internet connection.
Mine was also weird when it rains but then I installed android 4.0 Rom and it was much much better it still has the music app problem but I has installed rocket music player and now I don't have any errors at all at with the minfree low memory killer enabled it has high free ram.. still without its holds battery long time and is very smooth defenly try that great Rom
Sent from my HTC Runnymede using xda premium
Be careful from contiouas pressure on screen it may drive it to behave strangely .
Try to use lock code before putting the phone into pocket
Sent from my HTC Runnymede using xda app-developers app
Definitely on to something.
It has happened a few times when it was drizzling and there were tiny droplets on the screen (not proper rain).
It started acting up when I was swiping the screen against the tiny droplets. After locking it, it would stop responding...
Most of the times I find it either non reponsive or acting weird after I take it out of my back pocket and try to unlock it.
Maybe being in my pocket, even locked, affects it somehow.
Is it easy to put another Rom? Do I lose all my apps?
rawadlayous said:
Be careful from contiouas pressure on screen it may drive it to behave strangely .
Try to use lock code before putting the phone into pocket
Sent from my HTC Runnymede using xda app-developers app
Click to expand...
Click to collapse
nkomp18 said:
Is it easy to put another Rom? Do I lose all my apps?
Click to expand...
Click to collapse
Yes you will lose all your apps.
Yes I have the same behaviour, its usually moisture from my hand, greasy buildup, water droplets and or being in my pocket the pressure on the screen makes it act up too, wouldnr worry bout it, not every screen design can be perfect ; )
Sent from my HTC Desire S using xda app-developers app
onejay09 said:
Yes I have the same behaviour, its usually moisture from my hand, greasy buildup, water droplets and or being in my pocket the pressure on the screen makes it act up too, wouldnr worry bout it, not every screen design can be perfect ; )
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
sorry to bump an old thread.
I have this problem on a bashed up screen. however... I don't think it can be hardware because if I hard reset its then OK on the next boot...
we need to learn more about touchscreens - how are they calibrated? I think it is reset on boot and also on each lock
Its the LCD ribbon touching the metal housing, short circuiting the screen, easy fix with a piece of tape over the ribbon
Edit
Also, once the phone heats up resistance builds up with it causing the issue
Sent from my cm9 using xda app-developers app
I had that same issue.
You won't loose any of your data if you made a back up before instaling the new rom
if I was of any help Just hit the thanks button
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Any one else have the problem of not getting notifications until you unlock the phone? I notice it also with facebook messenger, facebook, and not getting email either. Is this just me or someone else having this problem?
allergic2idiots said:
Any one else have the problem of not getting notifications until you unlock the phone? I notice it also with facebook messenger, facebook, and not getting email either. Is this just me or someone else having this problem?
Click to expand...
Click to collapse
Are you completely stock or rooted on a custom ROM?
Sent from my SM-N900A using XDA Premium 4 mobile app
ReggieSmith said:
Are you completely stock or rooted on a custom ROM?
Sent from my SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am completely stock. I do not want to root the device.
allergic2idiots said:
I am completely stock. I do not want to root the device.
Click to expand...
Click to collapse
Mine does/did the same thing. Never figured out what it was. Now it is up for sell and I am using my newer HTC One. I think it might be the power saver but never got around to testing it. In PS mode it is supposed to turn data off when the phone is sleeping.
Solarenemy68 said:
Mine does/did the same thing. Never figured out what it was. Now it is up for sell and I am using my newer HTC One. I think it might be the power saver but never got around to testing it. In PS mode it is supposed to turn data off when the phone is sleeping.
Click to expand...
Click to collapse
messing around with the settings and found it has something to do with the lock screen security. When its set to "none" the notifications works fine. I have tried a couple of the apps for screen locks and are not satisfied with them as far as thier looks. I am really hoping when ATT finally released the kit kat update it will fix this problem. I just sold my LG G2 to get this phone. Kinda disappointed now that ATT released its update today.
I used to have the HTC one but didnt like not having the sd card. I found I like the bigger screens.
Did you finally figure out the solution? I am completely stock, not rooted and have the same issue since last 6 months. I never had any lock screen, so thats not the issue, I always have my phone unlocked.
The problem is not app specific. The delay in notification happens all across the board. When my phone is sleeping, i dont get any notification. As soon as I wake it up, all notification come at the same time, including Yahoo mail, Gmail, hangout messages, whatsapp, Google voice, twitter and others.
It seems like the wifi/data is disabled when phone is sleeping. I double checked in the Advanced Wifi option that wifi is always on. Some people said that the push notification heartbeat might be the issue but why only few of us are seeing this issue and not everyone?
Anyone have any solution?
I have always had my Note 3 on PIN, and I always wake up to at least 2 or 3 emails (sometimes many more), and at least 2 or 3 days I wake up to a new text (I don't text people normally, but Amazon texts me to let me know an order has shipped, etc.)
So it's not the email or text app and it's not the lock screen "as a rule on all devices". It could be a few different things, like allowing wifi to be turned off when the screen is off (that saves so little battery it doesn't make any practical difference - turn it off and keep wifi on all the time). I don't normally run with 3G/4G on, but that shouldn't turn off during sleep, so it wouldn't cause the problem.
Hello
Ive had numerous problems while i was on KK 4.4.2 .681 and .757 with freezeing phone, random reboots(usually once a day) and touch screen issues.
I have asked alot here and over at Sonys support forum and ppl began to point out that i could very well have a hardware problem. Although the problems i have had on KK wasnt that odd. Since ive read about others having theese problems.
But early monday morning i thought that hmm why not try what a dude here suggested. Wipe the phone completley with cache, dalvik cache and all that and flash the latest 4.3 firmware with JB. Hmm oki well i did that, and so far i havent had any reboots, or any freezes. Camera is QUICK and takes better pictures. At some point i thought the touch was acting weird but that could just be the app itself freaking out, it was only for a few seconds and after that everything was working like it should. Battery time is better aswell(although it goes down to 75% quite fast but after that its slooooow).
So do you still think i might have hardware issues ? I was about to ship my phone back to China but now it feels like it is pure software issues. And i have had big troubles with the retailer to accept this as a warranty matter since he belives its a software issue.
But then again, my phone aint operating good at all with KK 4.4.2
So far everything is fine with the phone, missing some stuff from KK but not the end of the world. But im still testing. If it will remain on without a freeze until the end of the week i could be quite certain that it is KK that ****s up my phone totally.
Please respond with thoughts.
Who told you to wipe your phone? ..lol..
Just my thoughts about touch screen, I replaced 2 days ago my "lucid" classic transparent screen protector with one Anti-Glare, which is not lucid glass like many but is rough and it influence a little little bit on the visualization of the screen, tiny, tiny thing but the touch screen is much much more responsive.
Classic issue with touch screen, unlock with patterns, with the lucid screen protector sometimes it skipped the touch and I had to try 2 times to unlock the phone if the phone was put on the table without hold it. With the new screen protector it not skip anything.
Sometime a stupid thing can be the issue.
Could be the screen protector, remember the first one I had was a antiglare, and as far as I remember I didn't have those issues then. Now I have ultraclear one. Could be that, you never know. I do have tempered glass one wich I haven't used.
Just before the phone actually froze for a few seconds just when I took a picture, but it came back with no reboot. And I got a msg on WhatsApp and messenger at the same time so that could be what was causing the lag this time. Hopefully
Sent from my C6903 using XDA Free mobile app
Still no reboot! Used camera alot and done all sorts of stuff.
And today I changed my screenprotector to see if that would rectify the touchscreen issue. I used a tempered glass screen protector. O my god how much better that protector feels! But still testing for any issues
Sent from my C6903 using XDA Free mobile app
Some updates.
No random reboots!
But two other odd things occurred and one of them is known.
1. Touchscreen went crazy, it didn't press what I wanted and so on. I noticed it actually swiped on the keyboard. Turned that function off and unistalled the app "Color notes". Touch screen bugs are known and Sony even admitted it so.
2. I couldn't send sms today, tried to several but got error. Data and so on still worked. Restarted the phone and then it worked again (might just be coincidence). Although I noticed that it at some point it had trouble sending data, took forever to get connection even though I had 3-4 pins reception. Also noticed when that sms bug occurred that it switched from 2 pins to full every time I opened the sms to send.
But still no reboots. These things maybe would trigger reboots with kitkat, I dunno.
Sent from my C6903 using XDA Free mobile app
Jonas740 said:
1. Touchscreen went crazy, it didn't press what I wanted and so on. I noticed it actually swiped on the keyboard. Turned that function off and unistalled the app "Color notes". Touch screen bugs are known and Sony even admitted it so.
Click to expand...
Click to collapse
I have it all the time, I mean not the touch screen going crazy but the swipe one on keyboard, it happen always when I click on the letter A on left side, it really piss me off.
I think I have to turn off the swipe thing too.
Ye I've read about ppl having issues like we do and they just turned it off and then it works. Sony said they would fix the touchscreen issues in updates but still not fixed.
Btw, have you noticed that the "swipe" to turn off the alarm clock is less sensitive? It takes some trys to swipe to turn it off. Although it is a good thing because it makes me pissed and I have to concentrate to turn it off wich makes me to get up Might be an intended "bug".
Sent from my C6903 using XDA Free mobile app
Jonas740 said:
Ye I've read about ppl having issues like we do and they just turned it off and then it works. Sony said they would fix the touchscreen issues in updates but still not fixed.
Click to expand...
Click to collapse
Yeah, they are very lazy to fix this issues but they are not to put on the market a "new" device and forgot about Z1.
Jonas740 said:
Btw, have you noticed that the "swipe" to turn off the alarm clock is less sensitive? It takes some trys to swipe to turn it off. Although it is a good thing because it makes me pissed and I have to concentrate to turn it off wich makes me to get up Might be an intended "bug".
Click to expand...
Click to collapse
Yes, Yes, I am glad that I am not alone. It was less sensitive even before I turned off the "keyboard swipe" thing. So not really know if it's related to that features, it shouldn't, but you confirmed a "bug" which was keeping me thinking. O Lord, I dream about a Z1 bugs free! (dream only)
might not be
eclyptos said:
Yes, Yes, I am glad that I am not alone. It was less sensitive even before I turned off the "keyboard swipe" thing. So not really know if it's related to that features, it shouldn't, but you confirmed a "bug" which was keeping me thinking. O Lord, I dream about a Z1 bugs free! (dream only)
Click to expand...
Click to collapse
Well that Alarm swipe might not be a bug actually, ive tried it back and forth and if you "lazy" swipe it fast like you would when it rings in the morning it wont turn off. But if you do apply pressure and swipe slow it will turn off. Not a huge problem for me since it actually help me getting out of bed
Jonas740 said:
Well that Alarm swipe might not be a bug actually, ive tried it back and forth and if you "lazy" swipe it fast like you would when it rings in the morning it wont turn off. But if you do apply pressure and swipe slow it will turn off. Not a huge problem for me since it actually help me getting out of bed
Click to expand...
Click to collapse
Of curse, it help me too, I get angry because of that so I have to leave my bed ..LOL..
The thing is, who know if it was meant to be like that? It was made with that purpose? Because if it isn't then it's a "bug".
OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?
I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.
I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification
disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...
Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.
I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.
Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Aruarian said:
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Click to expand...
Click to collapse
Sounds like a different issue.
Mine was a complete one of, switch made me suspect software asop issue.
Monitoring.....
Sent from my Nexus 6
Happened again, dead power button, woke by volume buttons, reboot, works fine again.
So this isn't intermittent, in that when it fails it won't work again until restart, which says to me software.
I'm now using this thread as log. To see if RMA necessary.
Chroma 5.1 22/03/2015
Sent from my Nexus 6
Happened again later in the day.
Sent from my Nexus 6
ben_pyett said:
Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Click to expand...
Click to collapse
Do you have a screen protector covering the sensor? If so that's probably the issue, disable ambient display and see if you can reproduce the problem.
Sent from my Nexus 6 using XDA Free mobile app
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
ben_pyett said:
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
Click to expand...
Click to collapse
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Feature is disabled. ?
Sent from my Nexus 6
ben_pyett said:
Feature is disabled. ?
Sent from my Nexus 6
Click to expand...
Click to collapse
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
ben_pyett said:
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
Click to expand...
Click to collapse
Then short of backing up and doing a clean install I am out of ideas, sorry.
Sent from my Nexus 6 using XDA Free mobile app
Cheers. Literally only just did that for stable Chroma 22/03 version... Will wait until further versions come out and will consider doing that. Cheers anyway
Sent from my Nexus 6
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
happened to me today, like it was in a deep sleep and took ages for the power button to work.
Im on stock 5.1
Happened once 31/01 soft reboot resolved it
Still believe this is software.
ben_pyett said:
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
Click to expand...
Click to collapse
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I would get this issue on Chroma if I had enabled the option Display--Ambient Display--Overwrite Value.
See if thats enabled, and if so, try with it disabled for awhile.
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I was clean install on 5.1 but not since, although did import apps and data from TB not that it should impact it at all. Only ever run Chroma, jumped straight to it after initial unlock.
Fortunately volume keys always wake - so far.
Let me know how you get on - in this thread.
If I find it continues to happen then I'll consider clean install and then maybe even a replacement device.
Everything was fine after last reboot.
Immediately after plug in into charger, the power button stop working. First time experiencing this. Able to try this to guys?
Edit: I toggled 2 things.. Enabled / disabled ambient display overwrite defaults and screen on when plug / unplug charger..
Power button is working again without any restart.. @githyanki @ben_pyett