Develop Bugs

[Q] How to get OTA notification again?

Hi All,
Last week I received a system update for my Nexus 7 for Lollipop. At that time I didn't want to update so I dismissed the notification. The problem is that I can't get it to re-appear. I've already tried to check for updates 100 times over a couple of days. I've also cleared the Google Play Services and then check for updates, but didn't work.
Is there a simple way to get the update notification again?
Thank you for your help!

Yes, wait for the OTA to become available again. There's a possibility that the latest OTA (5.0.1) was pulled and is no longer available. If you really want the update, download the firmware from Google and flash it manually.
Edit: someone got the notification today. So who knows why you haven't received the notification.

I thought one you dismiss the notification and don't take the update you go back to the end of the queue - so it could be weeks before you get it again.

Happened to me as well. Got the notification last week for 5.0.1, didn't update but didn't dismiss it either. After a couple of days it just disappeared and so far hasn't shown again.

I'm still waiting on 5.0 here. Getting annoyed and was looking for sideload update options but if other people are still waiting on it I guess I'll hold off a bit longer.

If you're now running a modified stock rom, you will most likely have issues updating with the OTA. Here's a way to update without having problems or waiting for the OTA with no loss of data: Download the rooted rom from Scrosler found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , use Wugfresh's NRT 1.9.9 to update the bootloader that's also mentioned in Scrosler's thread, and then dirty flash (no wipes) the 5.0.1 rom with TWRP.

Phibernaut said:
I'm still waiting on 5.0 here. Getting annoyed and was looking for sideload update options but if other people are still waiting on it I guess I'll hold off a bit longer.
Click to expand...
Click to collapse
Stop waiting and do it manually. Why is everyone so consumed with sideloading? You can flash the latest firmware in fastboot without losing anything.

When I lost my update (long story) it took 3 days to come back. A little less than I was expecting but still a little more than I wanted. I'd expect you'll get it back in 2-3 days.

Same here! But will download it now instead. Tierd of waaiting

April update random restarts?

Hello, i have the phone around a month now and never have any problems until april update. The last couple days the phone restarted randomly twice - once while i was using it and the other while not. Both times it was connected to power.
When updated i also deleted the cache from the storage menu, i will also do it from system restore and hope it will fix it. Any other ideas?

Nothing wrong with April update.

April update has been quite stable for me.

[Q] Is there a new update?

Hi all. At 4:20 AM PDT (the notification sys 8:20AM for some reason) this morning (June 12) my Note 4 buzzed and woke up and let me know there was a software update available. Any idea what this is?
I didn't install the small security update last month yet, is this just that update trying to be more forceful (the notification will not go away)? Or is it a new update?

Try it, and let us know what it is !

I didn't install last month's security update myself for the fear of losing that slim chance of an unlocked bootloader and root..lol
I haven't received a notification about an update this month..would you happen to have a description of the update?

Well, the notification wasn't going away and I accidentally hit continue and it rebooted and installed whatever it was.
Took it's sweet time installing and then optimizing apps, and as far as I'm aware nothing changed. Same baseband, same kernel, same build number (LMY47X.N910AUCU2DOI3) according to About Device.
Also my phone is starting to show me the same annoying screen that started appearing when the security update came out saying to connect to wifi to download another update (whatever update was installed today, it downloaded itself via mobile, not wifi).
So I am rather confused as to what the 'update' I installed was.

7.0 to 7.1.1 is safe for update against bootlooping issue?

I bought 5x last week and already installed android 7.0 out of the box. I just wanna know if its safe to update my phone to 7.1.1 without bootlooping issue. I saw many post has a problem from android 6 to 7 update. Forgot to mention that my manufacturing date is Oct. 2016. TIA

tugs0109 said:
I bought 5x last week and already installed android 7.0 out of the box. I just wanna know if its safe to update my phone to 7.1.1 without bootlooping issue. I saw many post has a problem from android 6 to 7 update. Forgot to mention that my manufacturing date is Oct. 2016. TIA
Click to expand...
Click to collapse
its a rare hardware issue amd usually there won't be a problem ... so yeah, just go ahead and update,

I flashed the latest update on both of my devices, its a hardware issue.

Mine is November 2016. I ran the OTA update and everything runs fine more than a month now. No issues.
A friend of mine had some issues, tho. For some reason, after he applied the december update(i think) his phone started booting with a yellow or red triangle(don't remember the exact colour) and after few such boots he couldn't power on his phone anymore. He had his motherboard replaced and runs fine now. That's an August 2016 device.

I suggest you to downgrade to 6.0.1 august update, it seems more safe than updating to nougat.

7.1.1 is perfectly safe to run and upgrade to. If your does start bootlooping chances are your phone was dying anyway. The problem just manifests itself when the phone is stressed and/or runs hot, for instance during upgrading.
Downgrading to 6 just seems a bit useless to suggest imo.

peltus said:
7.1.1 is perfectly safe to run and upgrade to. If your does start bootlooping chances are your phone was dying anyway. The problem just manifests itself when the phone is stressed and/or runs hot, for instance during upgrading.
Downgrading to 6 just seems a bit useless to suggest imo.
Click to expand...
Click to collapse
And why is that? All the statistics showing that the bootlooping problems started after Android 7.0 (august to september) I'm not excluding a hardware I'm talking about software side.

I think the general consensus is just that most likely devices started failing after about a year. Unfortunately coinciding with 7.0 being rolled out which is why people originally started to think the bootlooping was due to the update.

khalifakk said:
And why is that? All the statistics showing that the bootlooping problems started after Android 7.0 (august to september) I'm not excluding a hardware I'm talking about software side.
Click to expand...
Click to collapse
Folks who stayed on 6.0.1 have seen boot loops as well.
People have always tried to associate Android updates with issues. When something comes up, its hard not to look back at a recent update and think of it as the likely cause.
Our phone has received updates each and every month so the opportunity to blame an update is even more prevalent.

Question March security patch not showing up?

I've been following the S22 release, and already knew there were a few updates dropped at this point. I just received my new S22 Ultra from AT&T, during setup I saw a popup that said I had an update available. Great. However immediately after setting it up I had to factory reset and start over, and when I finally got all set up again, it says there's no update available. I'm currently on an S908U running the January update, S908USQU1AVA6.