See this photo:
https://goo.gl/photos/Ns9nKJotNX7mZnhz6
It seems that the digit in the top right corner of notification stops updating, and always showing the old time.
It will only update if i try to switch the time format to 24h and switch back, and it stays there since then.
A reboot will fix it but the bug may appear randomly. So I may get the wrong time and be late...
Pixel XL using totally stock rom without root or unlock, build number NDE63X(manually updated through google's full ota link, i didn't recieve any ota update since bought with NDE63N)
Anyone has the same issue?
Same issue here this morning with my Pixel.
After an hour the time was up to date again.
Build number NDE63V
Haven't had this problem on the pixel yet, but used to get it once and a while on my Samsung phones. I always thought it had to do with the network feeding the phone the wrong information. After a while it would update and be back to normal
Related
The weirdest damn thing happened to me...I received a system update available notification (i.e. ICS) as I was going to bed. I thought I'd just do it in the morning. When I woke up, the notification was gone, and if i try to go to manually do a system update, it says device is up to date.
anyone experience such an issue, and how can I resolve this?
thanks
Same thing happened to me. I was on 3G and decided when I get home I'd use wifi to download and update. Now it says up to date.
so weird!! all other updates previously would remain for days... anyone find a solution to this yet?
Same happened to me to this morning, it disappeared
alizawi said:
The weirdest damn thing happened to me...I received a system update available notification (i.e. ICS) as I was going to bed. I thought I'd just do it in the morning. When I woke up, the notification was gone, and if i try to go to manually do a system update, it says device is up to date.
anyone experience such an issue, and how can I resolve this?
thanks
Click to expand...
Click to collapse
wait or
you can update ics by making manual promotion
I prefer to avoid manual for two reasons:
1- I still believe the actual OTA version varies slightly than what is claimed to be the official OTA release in zip format. Little touches are always done before pushing an OTA update.
2- I have a broken power button, so can't do much in bootloader, or even get into it.
Perhaps google took it back to do some more bug fixing. But I'd like to hear an official statement if that's the case
szk5230 said:
wait or
you can update ics by making manual promotion
Click to expand...
Click to collapse
Please explain. I've tried:
Checkin
System Updates
Resetting phone.
Seems like the update was pulled. No matter what I do it says the phone is up to date. With all these stories of people bricking their phones I want to stay relatively legit.
alizawi said:
The weirdest damn thing happened to me...I received a system update available notification (i.e. ICS) as I was going to bed. I thought I'd just do it in the morning. When I woke up, the notification was gone, and if i try to go to manually do a system update, it says device is up to date.
anyone experience such an issue, and how can I resolve this?
thanks
Click to expand...
Click to collapse
Same thing. When I heard google started pushing ICS, I flashed back my nandroid backup of my stock 2.3.4 to get the OTA update, Immediately I got 2.3.6 update and installed it, and few hours later when I wasn't home I got the 4.0.3 update, and I thought I'll do it when I get home, but then it disappeared and doesn't comes back no matter what I do.
I did backup to the corrent stock (2.3.6) and tried to flash back to 2.3.4, thought maybe it will push me again, but now it doesn't push me 2.3.6 either.
Are OTA updates one-time only ? or it supposed push me 2.3.6 again ?
anyways I restored 2.3.6 and I wait hopefully to 4.0.3 again.
Please update here if you know any solution. I know I can install it manually, but I prefer clean OTA version.
after I update to ICS manually, the VPN doesnot work, so I flashed back to 2.3.6 and want to update by OTA.
but till then, the 2.3.6 system says it's up to date...
looks like it's pulled by google...hopefully for some enhancements... still waiting for something official
we had it in our hands and we lost it
Same story.
Last night I saw the system update notification and after 30' (charging the battery) I lost it.
I suppose it's due to issues with ICS 4.0.3. For example I can't make outgoing calls (SMS, incomming calls and data - works fine). Had to revert back to 2.3.6. Now everything works. So for two days i saw update notification and today it dissapeared. So I hope they found a problem and will fix it soon.
yeah, I guess I'm glad I didn't install it then. I'm sure it was pulled for a valid reason, so it's best to wait...fingers crossed that it won't be too long of a wait.
In the mean time I think I need to get my power button fixed, or hope the widgetlocker works on ICS so I can use my volume locker to wake the screen!!
yeah, I guess I'm glad I didn't install it then. I'm sure it was pulled for a valid reason, so it's best to wait...fingers crossed that it won't be too long of a wait.
In the mean time I think I need to get my power button fixed, or hope the widgetlocker works on ICS so I can use my volume locker to wake the screen!!
Not an official story by any means but it looks like there is definitely something going on.
http://mobilesyrup.com/2011/12/20/g...te-for-nexus-s-over-purported-battery-issues/
EDIT: I just noticed one of his sources links back here.
has anyone run across this issue when you set a specific time out, the screen dims after the specified time but does not lock, it stays on?
my phone was working just fine, stock not rooted, took the latest update and after that i've been having nothing but weird issues, the other day the notification area at the top was not working, i had to basically check every app, messages etc manually to see updates, had to factory reset the damn thing, now this screen issue, the phones is only 1 month old.
any input?
thanks
I'm having very weird issues with screen lock. I'm be on the phone and the device will randomly lock and not let me unlock it without restarting the phone.
The new update is when it all started. I don't want to do a factory reset, but it's looking like I might have to?
So I SWEAR I saw this mentioned somewhere earlier today but after searching I can't seem to locate it.
As the title says. I have Automatic system updates turned OFF. Turned that off right after I got it unlocked and rooted.
Verizon Pixel XL NDE63P
Today I get a notification regarding Android 7.1 Update. I didn't tap on it, couldn't clear it. Was concerned that the update might auto install without my permission or something. Well that hasn't happened, and NOW the notification is gone. I don't want to update yet...
I was thinking that turning off automatic system updates would mean it wouldn't even check to know there was an update. Am I going to be living with a nag that comes back with a hair trigger update button. Had that on Samsungs in the past. Will make you crazy always having to tell it NO try tomorrow every day...
Just wanted to see if anyone had seen this behavior or if I was just loosing my marbles here.
Thanks!
Screwit, just sideloaded the update. Everything is good, unlocked, rooted, customer kernel etc...
new update available. says "security , new device features " , its the android june security patch and possibly a new feature
If your using the no root hotspot it still works through update!!
It installs weird too after rebooting it restarts then the screen will black out and say "installing applications"
then it will say software is custom until the update notification at the top stops. even though it already popped up a toast that said successfully upgraded yet that still has to fill up (in the notification) then it all goes to normal seems smoother than ever
I am applying it right now, will follow up if I run across any issues.
Whentheworldends said:
I am applying it right now, will follow up if I run across any issues.
Click to expand...
Click to collapse
How big was the download?
297.58 mb
Trueno22 said:
297.58 mb
Click to expand...
Click to collapse
Thanks. So there is more than just security patch in it at that size.
All I know is the last update(not this one) broke my phone, My system app crashed randomly, vibration would continue to vibrate after calls were answered, very slow response and frequent random resets. Notifications would either not appear or not disappear. One time I lost all my home screen apps. The problems were so severe I decided to upgrade to the S8.
After this update my phone runs like new.... too bad I already decided to buy the new S8.... although my 'excuse' for needing it apparently has been fixed by this update, Now I just want the S8.
Mardibob said:
All I know is the last update(not this one) broke my phone, My system app crashed randomly, vibration would continue to vibrate after calls were answered, very slow response and frequent random resets. Notifications would either not appear or not disappear. One time I lost all my home screen apps. The problems were so severe I decided to upgrade to the S8.
After this update my phone runs like new.... too bad I already decided to buy the new S8.... although my 'excuse' for needing it apparently has been fixed by this update, Now I just want the S8.
Click to expand...
Click to collapse
yeah mines running smooth as butter. Just a note if you have that problem again (vibration etc) go into Stock recovery and clear cache it fixes it
Pixel 2 XL on Android P DP2 since it was released at I/O. Yesterday my phone randomly reboot while using it and after I received the notification of DP3. I thought it was weird but whatever. Several times throughout the night it would shut down and go into a boot loop at the G screen. It would eventually correct itself and boot into the OS. At this point I had yet to even tap the notification that DP3 is available for download.
When I got home I attempted to update to DP3 to see if it would fix the issue. It did not. This morning I managed to get back into the phone and did a factory reset. That did not resolve the issue, so I decided to un-enroll from the beta program and waited an hour for the Android O OTA to appear, it never did and still hasn't.
I downloaded an Android O image and loaded it onto the device, it made everything worse. I couldn't even get past the lock screen. In all my troubleshooting I found out that my phone will last longer if it was plugged into a power source.
I contacted Google Support and the end result was because I didn't wait for the Android O OTA and side loaded it, that was the cause of the Android O Issues. I would need to re-enroll into Android P Beta and then wait for the Android O OTA.
So I'm here waiting for the Android O OTA to appear, in the mean time I've barely touched my phone except for a few texts.
I decided to pull a bootlog.txt from the device after the most recent reboot but have no idea how to decipher it, I'm not that technical if it would be helpful to share.
Any advice would be great.
Cerealbowl218 said:
Pixel 2 XL on Android P DP2 since it was released at I/O. Yesterday my phone randomly reboot while using it and after I received the notification of DP3. I thought it was weird but whatever. Several times throughout the night it would shut down and go into a boot loop at the G screen. It would eventually correct itself and boot into the OS. At this point I had yet to even tap the notification that DP3 is available for download.
When I got home I attempted to update to DP3 to see if it would fix the issue. It did not. This morning I managed to get back into the phone and did a factory reset. That did not resolve the issue, so I decided to un-enroll from the beta program and waited an hour for the Android O OTA to appear, it never did and still hasn't.
I downloaded an Android O image and loaded it onto the device, it made everything worse. I couldn't even get past the lock screen. In all my troubleshooting I found out that my phone will last longer if it was plugged into a power source.
I contacted Google Support and the end result was because I didn't wait for the Android O OTA and side loaded it, that was the cause of the Android O Issues. I would need to re-enroll into Android P Beta and then wait for the Android O OTA.
So I'm here waiting for the Android O OTA to appear, in the mean time I've barely touched my phone except for a few texts.
I decided to pull a bootlog.txt from the device after the most recent reboot but have no idea how to decipher it, I'm not that technical if it would be helpful to share.
Any advice would be great.
Click to expand...
Click to collapse
You won't get the OTA until you pull out of the Android beta program. You can pull out for any of your enrolled devices here:
https://www.google.com/android/beta#devices
Just opt out there and you should receive the OTA to go back to Oreo. You won't get any OTA otherwise
TCUofficial said:
You won't get the OTA until you pull out of the Android beta program. You can pull out for any of your enrolled devices here:
https://www.google.com/android/beta#devices
Just opt out there and you should receive the OTA to go back to Oreo. You won't get any OTA otherwise
Click to expand...
Click to collapse
Did that yesterday afternoon, still waiting on the OTA to come through. Ironically the reboots has lessoned considerably, only twice today so far. I've used it minimally though and 1 time was due to trying to open the camera.
Cerealbowl218 said:
Pixel 2 XL on Android P DP2 since it was released at I/O. Yesterday my phone randomly reboot while using it and after I received the notification of DP3. I thought it was weird but whatever. Several times throughout the night it would shut down and go into a boot loop at the G screen. It would eventually correct itself and boot into the OS. At this point I had yet to even tap the notification that DP3 is available for download.
When I got home I attempted to update to DP3 to see if it would fix the issue. It did not. This morning I managed to get back into the phone and did a factory reset. That did not resolve the issue, so I decided to un-enroll from the beta program and waited an hour for the Android O OTA to appear, it never did and still hasn't.
I downloaded an Android O image and loaded it onto the device, it made everything worse. I couldn't even get past the lock screen. In all my troubleshooting I found out that my phone will last longer if it was plugged into a power source.
I contacted Google Support and the end result was because I didn't wait for the Android O OTA and side loaded it, that was the cause of the Android O Issues. I would need to re-enroll into Android P Beta and then wait for the Android O OTA.
So I'm here waiting for the Android O OTA to appear, in the mean time I've barely touched my phone except for a few texts.
I decided to pull a bootlog.txt from the device after the most recent reboot but have no idea how to decipher it, I'm not that technical if it would be helpful to share.
Any advice would be great.
Click to expand...
Click to collapse
You really should post this in the XL forum. There seems to be a much larger userbase, and you'll get more device-specific information and help there.:good: