Ever since updated to the Nov 1st update. When I turn my screen on there is a 1 in 3 chance that the screen will be at max brightness. The only way to fix it is to wait 5 seconds or turn the screen back on then on. Anyone else seeing this?
Yea it started happening to me about two weeks ago after I installed GravityBox , don't knowwhat to do it's very annoying .
Known issue. I've filed a bug, please star it. Here's the link where we discussed this in detail.
http://forum.xda-developers.com/showthread.php?t=3256165
Thanks @andr0idfreak. I was starting to worry I was alone. From the bug report seems a lot of people are seeing it.
Related
This is one I havent encountered before but apologies if its been reported already. I couldnt find an obvious thread.
I have noticed recently that my Kaiser is not keeping time - quite dramatically so!
When I turn my device on from standby, the clock is often 20, 30 mins or even hours behind.
I have tweaked the hell out of it recently so I am quite sure it is related to something ive done as it hasnt happened on previous builds.
I am using synchrotime almost everytime i turn it on just to make sure the clock is right (hope this doesnt clock up too much data :-( ).
Anyway just wondered if anyone else had come across this?
Try turning the auto time setting in the phone settings to OFF, early on we found this to cause random time problems as well as causing active sync to run all the time.
Thanks. I'll give it a go.
Mine did that last night - 40 minutes slow. Never had that problem since i first got it a couple of months ago. Once it got coverage again, it syn'd back up.
Did that fix your issue?
I've got another interesting one. My clocks are right, but my text-messages show as an hour ahead (received one at 3pm PST and it shows as 4pm PST in the list). I do have the 2007DST patch from Microsoft and everything else is configured right. Is there another setting somewhere for txt-msgs?
this happens for me too. i dont no what is causing the delay. when i have my phone on device lock, whatever time it was when i locked it, it stays like that until i unlock. i noticed it recently, almost missed an appointment because of it!
tried turning off that auto time thing that dont have any effect.
worked perfectly thanks
I am checking to see if other people see this on there Nexus 6.
I get random reboots, like once every 2-3days I would say. (Is this Memory Leak?)
Also sometimes I cannot unlock with power button, it will stay black screen. Here sometimes it reboots, sometimes if I wait 10-20secs it works again.
I am wondering whether to return it for another one.
Actually I never faced with my device. And currently my device's Up Time is about 180 hrs. Running last 7 days without any problem.
Go to this link and look near the bottom of the page. Paul, from Google, is reporting that 5.1 should "reduce unexpected reboots." Hope that means they have fixed it and they just used the word "reduce" instead of fix because of the fact that any phone might reboot given the right set of circumstances. Hopefully, persisting reboots will finally be fixed. If you read the entire thread (very long) you will see that many people have reported random reboots and they have experienced them under different circumstances. I'd like to know if they've found what is triggering the repeated reboots for everyone---only time will tell. Some have exchanged their phone for another and had success. Quite a few others have reported receiving 1, 2, or even 3 different replacements and still experiencing reboot problems. Don't know what the answer is. I'm just sitting back observing, waiting to see if it gets resolved before purchasing the N6. If I don't see a satisfactory resolution, then I probably won't get one, even though, before it was released, it sounded like the just the phone I wanted.
https://productforums.google.com/fo...c/nexus/other-discussions/nexus-6/9aVUBrwdUZU
I have the same problem on my T-Mobile Nexus 6. 2 reboots in the past 24 hours. It occurs randomly too. I just got the phone like 3 days ago so I'm hoping that 5.1 will fix this issue. Next to the reboots I haven't had any issues with the phone. It pretty badass actually. I switched from the Note 4.
Thanks for the feedback! I really like the phone no way I will get rid of it for this issue. Its just annoying as nexus 5 I didn't. Have any issue like this but I guess KitKat was a more stable than LP.
I will await 5.1 which sound imminent
Sent from my Nexus 6 using XDA Free mobile app
Hello,
I own the watch for about 1 year, and recently I faced issues with it,
The upper notification menu stays on the screen and start flashing in glow lightning, sometimes it's half screen, or just 2 lines from the top.
I think it's a burn-in but not sure, it appears only after leaving the watch without use (usually at night, and i can see the problem appearing in the morning).
It disappearing alone after playing with the watch for couple of minutes (turning off,on...)
*I'm running on LeeDrOiD latest rom
**can't post pictures cause i'm a new user....
Does anyone faced this issue, or have a solution for this ?
Thanks Ahead
Yes, a lot of post for this common issue.
it stop after a while and maybe related on the face used and on the time where the screen stay off.
Thanks, the problem seem to have been fixed after flashing the original stock rom.
I've got the maximum brightness bug. For people who don't know what this is, it causes the phone to shoot to maximum brightness for a short period upon unlocking. This is incredibly annoying when I'm waking up early in the morning, or checking an important notification in the middle of the night.
It's a known issue, and here is the AOSP Issue: https://code.google.com/p/android/i... Priority Owner Summary Stars Reporter Opened
I've done some searching on this forum, but I haven't seen anybody with a solution.
I've tried resetting to bone stock, I've tried multiple ROMs, and multiple kernels, and flashed questionable zips trying to fix this.
Does anybody know of any way to fix this? Any kernel, or ROM that has this bug fixed? My eyes are bleeding. Save me.
Bumping this because I still have this issue and still can't find any information on it.
Turn off Google location history
Anybody notice that tap to wake intermittently stops working? I'm thinking that it happens when the phone has been sitting untouched for some time but I'm not sure. Maybe it is designed like this to save battery?
When the tap to wake doesn't work does face unlock stop working too?
If so it's a known problem
Rotten Ross said:
When the tap to wake doesn't work does face unlock stop working too?
If so it's a known problem
Click to expand...
Click to collapse
My problem exactly! I'm new to the 4XL, has this been a long-standing problem? Has Google already acknowledged the problem, and are they going to patch it? I have been restarting my phone 2 or 3 times a day. I was beginning to think it was defective. So glad I saw this post.
Sent from my Pixel 4 XL using Tapatalk
xRogerxC said:
My problem exactly! I'm new to the 4XL, has this been a long-standing problem? Has Google already acknowledged the problem, and are they going to patch it? I have been restarting my phone 2 or 3 times a day. I was beginning to think it was defective. So glad I saw this post.
Click to expand...
Click to collapse
I have this problem but not as bad as you. I normally have to restart my phone every 2-3 days due to this problem. I've spoken to someone a Google, they said that I have to see if a factory reset fixes the issue, (but it is very unlikely as many users have reported that it doesn't), if the problem still persists then I will have to send it to them to get a replacement. The person told me they don't know what causes the problem and don't have a solution. I don't see how a replacement is a good option considering that will probably become faulty to if they don't have a fix for it.