Develop Bugs

Notification to Update to 5.0.1 is gone on Nexus 7 2013

HI,
I got a notification few days ago that 5.0.1 is now available for my Nexus 7 but when I finally decided to upgrade, the notification was gone and checking system updates show that my system is up-to-date. Anyone know how I can get it back? I don't want to use the zip file and sideloading. My device is a bit complicated because I have Multirom and Ubunut Touch.
Thanks.

Try it ? http://lifehacker.com/5946585/force-an-android-device-to-check-for-a-system-update

Calvin Gross said:
Try it ? http://lifehacker.com/5946585/force-an-android-device-to-check-for-a-system-update
Click to expand...
Click to collapse
I've tried that already even if they say it won't work anymore and it will introduce some problems but still no luck.
Maybe the update was rolled-back? The update was downloaded already and all I need to do is install it

javacookies said:
I've tried that already even if they say it won't work anymore and it will introduce some problems but still no luck.
Maybe the update was rolled-back? The update was downloaded already and all I need to do is install it
Click to expand...
Click to collapse
If the update was downloaded on your phone, it may be in /cache. Remove it then check again update it will be fine.

There are rumors that the update has been pulled. Many people from other sites claim the same thing.

Calvin Gross said:
If the update was downloaded on your phone, it may be in /cache. Remove it then check again update it will be fine.
Click to expand...
Click to collapse
It's not there anymore. Probably it was deleted when I restarted. Could it possibly true that it was pulled-out?
I was actually searching for articles about it but no one says that it is indeed.

No longer able to tap approve or deny to SU prompts

Hi, I just recently upgraded to BlissPop ROM, and everything was working, but suddenly when I'm prompted by something for root access, the popup occurs, but I'm unable to hit approve or deny....it just clocks out. I tried looking in PlayStore for an update to SU, but it seems to indicate I have the latest and greatest already. Anyone happen to know a cause and fix for this?

crackface said:
Hi, I just recently upgraded to BlissPop ROM, and everything was working, but suddenly when I'm prompted by something for root access, the popup occurs, but I'm unable to hit approve or deny....it just clocks out. I tried looking in PlayStore for an update to SU, but it seems to indicate I have the latest and greatest already. Anyone happen to know a cause and fix for this?
Click to expand...
Click to collapse
Just uninstall then reinstall the supersu app.

Do you have Lux installed? Cause that was the problem in my case . I've uninstalled it.

vibecatalin said:
Do you have Lux installed? Cause that was the problem in my case . I've uninstalled it.
Click to expand...
Click to collapse
Holy crap. Nice find!!!!!! This was exactly my issue. Guess no more Lux. Thank you sooooooo much for the help!!!!

crackface said:
Holy crap. Nice find!!!!!! This was exactly my issue. Guess no more Lux. Thank you sooooooo much for the help!!!!
Click to expand...
Click to collapse
Yeah I had to quit using lux. CF.lumen is the one I use without any problems.
-DUHA

Lol I use Twilight and I have to pause it in order to be able to hit install when sideloading an app. Can't recall if it happens with superuser or not.

Root is back because I uninstalled LUX
BINGO!, it was Lux. I did an uninstall and rebooted and had ROOT.........WOW, strange that this would be the answer, but it worked for me at this moment.
Works for me on Lollipop 5.0.2 IronROM v2.1

4.6.3 is up...

Just wondering if anybody has tried it since there are no posts. I wanted to see if anybody knew the changes.

They started rolling out, Amazon hasn't published download links yet (in case s#it hits the fan), so we will have to wait a little bit longer for qualified answers...
I have no intent to install on my device, but let's see what the changelog will tell us.
edit: BIN file download is available... Thanks to russy23 & wjchen0 for posting the updates. :good:
(Just got home from work and saw the links, nice work.)

I hope the update has a patch for the mms bug called Stagefright.

not sure about the changelog, but this page has the updates
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550

Well, after the update a warning symbol with the message "Error" appears to the screen.
Now if I try to turn on the device it boots in the recovery mode and nowhere else.
Thx Amazon -.-

JowyOMac said:
Well, after the update a warning symbol with the message "Error" appears to the screen.
Now if I try to turn on the device it boots in the recovery mode and nowhere else.
Thx Amazon -.-
Click to expand...
Click to collapse
I Fixed the problem, I've done the wipe and the factory reset from the recovery. After that i've sideload the update from the pc to the adb fire phone console.
It Works

Any noticible changes??

russy23 said:
Any noticible changes??
Click to expand...
Click to collapse
Haven't seen anything yet. I'm not rooted, just have Google sideloaded. Upgrade went smooth, no issues.

jack9955 said:
I hope the update has a patch for the mms bug called Stagefright.
Click to expand...
Click to collapse
The Bug is possible only with the processing of mms information by Hangouts.
The Fire Phone, doesn't have Hangouts, so it probably wont be infected by the malware.
:cyclops:

JowyOMac said:
The Bug is possible only with the processing of mms information by Hangouts.
The Fire Phone, doesn't have Hangouts, so it probably wont be infected by the malware.
:cyclops:
Click to expand...
Click to collapse
It's not just hangouts that was affected by stagefright. Stock messaging, Facebook Messenger and whatsapp could also trigger it. To my understanding.
Sent from my Fire Phone using the XDA premium app.

russy23 said:
not sure about the changelog, but this page has the updates
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
thanks for the link.
Updated the 461013820 rom to 463001420 without any problem. non-rooted device with google play store installed.

The latest software version includes bug fixes.
this is what Amazon said about the new update, well i have to say more:
They fixed the bug of the AID Mode during the call, FINALLY!
They improved battery life. I say this because i've noticed a little improvement on the battery life.
They didn't fixed the bug of the headphone (When you disconnect the headphone while you are listening something such as Youtube, Music etc. If you replug the jack, It doesn't work anymore until you restart the device )
Did someone find anything else?

4.6.3 just being installed on my UK O2-locked Fire Phone (463001420). Looks like the download link is already up on Amazon UK - http://fire-phone-updates.s3.amazon...update-fire-phone-33.4.6.3_user_463001420.bin

I guess my phone tried to update last night... I woke up with my phone stuck in recovery, just continues to boot there... factory reset did not fix.
Help!!

if you are rooted, do you just loose root? Re-root after the update? Thanks.

Just got the OTA update not a big file at all
Installed the google apps..and so far so good

So for those who are wondering, after sideloading through adb, I was able to reroot using kingsroot and was also able to install safetrap and use it.

Any noticible changes??
Sent from my SD4930UR using XDA Free mobile app

russy23 said:
not sure about the changelog, but this page has the updates
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
thanks for the link. I noticed the 4.6.3 update is only for the unlocked version, while the AT&T version is still 4.6.1. When Amazon released the previous 4.6.1 update, they released versions for both AT&T and unlocked. Weird.

Same issue as ediebol reported. Stuck in Recovery. I've done the wipe and reset with no luck. Attempting to sideload, I get the * cannot read update.bin * error in ADB. File is copied to the ADB directory so it shouldn't have any issues finding it.
Anyone have any other ideas?

Google Play system update problem

My Google Play system update was stuck on 1 July for several months now. And today I notice it turns red with no more updates available. Anyone have the same problem nor know how to fix it?
I'm on latest stock ROM with locked BL.

Same here, is there an update??

That is apparently the current version?

Same on my phone, but I could update it manually to Sept 1. now.
Weird that it was not done automatically.

Albertli said:
Same on my phone, but I could update it manually to Sept 1. now.
Weird that it was not done automatically.
Click to expand...
Click to collapse
Oh, mine had the update today. 6.3k, can't have been much in it.
I don't think it was automatic in the past either. But I have is updates set to manual so maybe that's why?

https://www.apkmirror.com/apk/googl...1-android-apk-download/download/?forcebaseapk
Download and install this Apk if you are on the Sept Patch

Same story on my other phone Samsung A30s. So I guess it's not A2 lite specific.

Aadil Gillani said:
https://www.apkmirror.com/apk/googl...1-android-apk-download/download/?forcebaseapk
Download and install this Apk if you are on the Sept Patch
Click to expand...
Click to collapse
thanks, that's fixed the system update problem.

schrickz said:
thanks, that's fixed the system update problem.
Click to expand...
Click to collapse
Np

This was a problem for me as well. My moto g 5g was stuck on that of 1 August 2020. I searched all over the internet but couldn't find anything that would work. I even did a factory reset but that too didn't work and the it was still showing that no updates were available. But yesterday while I was using the "Multiple User" option available under the "System" in settings (not as guest but new user) and tried checking Google Play system update and surprisingly there was an update available. I changed from new user to the original user (admin) and found that still there was no update available there. So I checked back to the new user and updated the phone. Why Google treated the new user differently is something that I want to know?

Question Notification window issues after June update

After the June update, I can't tap notifications that used to lead me to the message.
Anyone know a fix?

Just tested now with a what's app message and a txt and rcs app working for me

This is what happens regardless of the notification

I just re flashed the update and checked before I rooted, it was fine before I rooted.
Why would root affect reading my notifications?

vibrantliker said:
I just re flashed the update and checked before I rooted, it was fine before I rooted.
Why would root affect reading my notifications?
Click to expand...
Click to collapse
I have no clue sorry I don't root at all I think you might have that delayed notifications bug that I saw get reported on here but I have no clue
Edit to ad I hadn't watched your video before the reply have you tried a clean fresh install see of that fixes it

vibrantliker said:
I just re flashed the update and checked before I rooted, it was fine before I rooted.
Why would root affect reading my notifications?
Click to expand...
Click to collapse
I had the same issue and it turned out being a custom font magisk module. I updated the zip for June firmware and it works fine now.