Related
I have been experiencing a rather annoying bug on my S6. After unlocking the screen, sometimes the status bar will not pull down. This happens about 1/5 unlocks. I have to lock the screen again and then unlock for it to work again. Since the status bar is usually the first thing I use after unlocking, this becomes a real pain. I was hoping that the recent update would fix this, but it's still happening.
Is anyone else experiencing this issue? I couldn't find anything on the forums or Google.
gj13 said:
I have been experiencing a rather annoying bug on my S6. After unlocking the screen, sometimes the status bar will not pull down. This happens about 1/5 unlocks. I have to lock the screen again and then unlock for it to work again. Since the status bar is usually the first thing I use after unlocking, this becomes a real pain. I was hoping that the recent update would fix this, but it's still happening.
Is anyone else experiencing this issue? I couldn't find anything on the forums or Google.
Click to expand...
Click to collapse
Could you please provide additional information about your phone, such as the Base and or ROM?
Maybe try going into Recovery mode and clearing cache, that may resolve it.
Rayman360 said:
Could you please provide additional information about your phone, such as the Base and or ROM?
Click to expand...
Click to collapse
Baseband: G920AUCU1AOCE
ROM: Stock unrooted (G920AUCU1AOE2)
Rayman360 said:
Maybe try going into Recovery mode and clearing cache, that may resolve it.
Click to expand...
Click to collapse
No recovery, but the cache was cleared after I installed the G920AUCU1AOE2 update.
gj13 said:
Baseband: G920AUCU1AOCE
ROM: Stock unrooted (G920AUCU1AOE2)
No recovery, but the cache was cleared after I installed the G920AUCU1AOE2 update.
Click to expand...
Click to collapse
There is the issue right there, your base needs to be G920AUCU1AOE2, your on the older firmware but using the newer ROM. Use Odin to return to stock G920AUCU1AOCE, then do the OTA update from AT&T again. FYI The new PingPong Root still works on the new OTA, if you decide to go that route.
Return to Stock - http://forum.xda-developers.com/att-galaxy-s6/development/5-16-stock-odin-tar-g920aucu1aoce-t3110182
Rayman360 said:
There is the issue right there, your base needs to be G920AUCU1AOE2, your on the older firmware but using the newer ROM. Use Odin to return to stock G920AUCU1AOCE, then do the OTA update from AT&T again. FYI The new PingPong Root still works on the new OTA, if you decide to go that route.
Return to Stock - http://forum.xda-developers.com/att-galaxy-s6/development/5-16-stock-odin-tar-g920aucu1aoce-t3110182
Click to expand...
Click to collapse
That doesn't explain why it was happening when I was on the version that it shipped with. They matched at that point. Good suggestion though.
Rayman360 said:
There is the issue right there, your base needs to be G920AUCU1AOE2, your on the older firmware but using the newer ROM. Use Odin to return to stock G920AUCU1AOCE, then do the OTA update from AT&T again. FYI The new PingPong Root still works on the new OTA, if you decide to go that route.
Return to Stock - http://forum.xda-developers.com/att-galaxy-s6/development/5-16-stock-odin-tar-g920aucu1aoce-t3110182
Click to expand...
Click to collapse
I just updated the baseband to match the software. I'll report back after I use it a bit to see if it happens again. It just happened after I posted that. Ugh x.x
Looks like I'm going to have to factory reset. I was hoping more people would at least vote on the poll -.-
Wireless charging possible cause
It seems like this issue only happens if you use wireless charging. I did a factory reset on the phone and used it for a couple weeks with AC charging and I did not have this issue. As soon as I tried wireless charging again, the issue came right back.
gj13 said:
It seems like this issue only happens if you use wireless charging. I did a factory reset on the phone and used it for a couple weeks with AC charging and I did not have this issue. As soon as I tried wireless charging again, the issue came right back.
Click to expand...
Click to collapse
I strictly use wireless charging, so your blanket statement only applies to you. Never had an issue with three different charging pads.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Hi,
I'm French and I 'very got a stock nexus 6.
I have the 5.1.1 android (LMY48T) and as I noticed a notification about 6.0 I started the update.
After few minutes, the update was DLed and a rebootr was announced... But nothing.
I waited for a bit.
And tried to shut-off the phone for a manual reboot... Now I'm still in 5.1.1, and when I check the update it's says that my phone is up-to-date..
Any help?
Thanks for reading.
Greg
Happened to me too on my Nexus 6
Thanks for the contribution, did you find any piece of information anywhere else?
no not at all :/
Bummer...
hello gregaste
i can confirm the exact same problem downloaded the ota and pressed restart and install and nothing happened it its telling me ur device is up to date ! i hope somone can help us
Are you rooted? Not sure what "very stock" means. OTAs will fail if you are.
Had the same thing happen to me. Twice. Got a replacement N6 last week and I was letting all the OTAs go through before unlocking the bootloader and rooting. When I got the 6.0 update notification I let it download. After rebooting it didn't update and when I checked system update it saif I was up to date despite still being on 5.1.1. Then, for fun, after returning my original Nexus to stock I decided to let the 6.0 update download. After rebooting I was still on 5.1.1 and again it said I was up to date. Very weird. I got impatient and flashed the factory images.
I'm stock, and i'm not sure about my first message, but I'm positive that "very stock" is an auto-correct fail...
I phone to Google android help yesterday, and a guy told me something like "s-h1t happens" more polite though, and that I should wait for another notification... let's hope.
Happened to me as well. Once the ota is downloaded, give time to the phone to restart itself in recovery, it takes about 10 mintutes to go into recovery and dont interfere with soft reset.
Sent from my Nexus 6 using XDA Free mobile app
Semseddin said:
Happened to me as well. Once the ota is downloaded, give time to the phone to restart itself in recovery, it takes about 10 mintutes to go into recovery and dont interfere with soft reset.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
i restarted the phone my self and nothing happened but later i also cleared the cashe still it tells me ur system is up to date
phlimsh said:
i restarted the phone my self and nothing happened but later i also cleared the cashe still it tells me ur system is up to date
Click to expand...
Click to collapse
turn on your wifi, connect to wifi, then check if you are up to date.
gregaste said:
I'm stock, and i'm not sure about my first message, but I'm positive that "very stock" is an auto-correct fail...
I phone to Google android help yesterday, and a guy told me something like "s-h1t happens" more polite though, and that I should wait for another notification... let's hope.
Click to expand...
Click to collapse
let us hope it will show again soon !
Thank you for the tip. Maybe I didn't wait because no message told me to... Lesson learned.
So you had a second ota notification? How long after the first one who failed?
simms22 said:
turn on your wifi, connect to wifi, then check if you are up to date.
Click to expand...
Click to collapse
i ve done that like 100 times and nothing still says " your system is up to date " i guess i will wait for about a month maybe another ota will show up if not then i will flash although iam afraid something goes wrong and i will regret messing up my phone cause i have not done that before
phlimsh said:
i restarted the phone my self and nothing happened but later i also cleared the cashe still it tells me ur system is up to date
Click to expand...
Click to collapse
Go to Settings / About / Send feedback ; tell them you haven't recieved MArshallow OTA, that's how i got my 6.0 ota for the second time without waiting hours.
Semseddin said:
Go to Settings / About / Send feedback ; tell them you haven't recieved MArshallow OTA, that's how i got my 6.0 ota for the second time without waiting hours.
Click to expand...
Click to collapse
I followed your steps, but it feels like a coincidence to me... we'll see.
gregaste said:
Hi,
I'm French and I 'very got a stock nexus 6.
I have the 5.1.1 android (LMY48T) and as I noticed a notification about 6.0 I started the update.
After few minutes, the update was DLed and a rebootr was announced... But nothing.
I waited for a bit.
And tried to shut-off the phone for a manual reboot... Now I'm still in 5.1.1, and when I check the update it's says that my phone is up-to-date..
Any help?
Thanks for reading.
Greg
Click to expand...
Click to collapse
That may have been the October security download. After getting Marshmallow on my N5 and N9 weeks before, I got that update notice, downloaded it, rebooted and noticed the old Lollypop boot animation. I thought the update didn't get applied and never got another notification. I later ran Stagefright Detector and noticed that the two latest CVEs were remediated. So I'm still waiting for Android 6 for my Nexus 6.
stevemw said:
That may have been the October security download. After getting Marshmallow on my N5 and N9 weeks before, I got that update notice, downloaded it, rebooted and noticed the old Lollypop boot animation. I thought the update didn't get applied and never got another notification. I later ran Stagefright Detector and noticed that the two latest CVEs were remediated. So I'm still waiting for Android 6 for my Nexus 6.
Click to expand...
Click to collapse
Thank you for your input.
I'm not sure it's related to the secrity update though, because I was already up to date on this matter (LMY48T) , ain't I ?
gregaste said:
Thank you for your input.
I'm not sure it's related to the secrity update though, because I was already up to date on this matter (LMY48T) , ain't I ?
Click to expand...
Click to collapse
I went from LYZ28J to LYZ28K with that update. I believe T-Mobile and Sprint are on different forks of Lollypop.
Hi I have a problem from going to 5.1.1 from 5.0.2. I have tried clearing cache,
I have 9gb free,
made sure everything is up to date and enabled,
and have factory reset my phone.
Still doesn't work.
Says something about "dm- verity verification fail" if I go into that developer screen when you hold power, home and volume up right after it tries to update again while loading.
Never has been rooted and have had it for a few months now. Also I was wondering if I could root this phone and just manually update it with custom firmware and forget about Ota updates anymore and be able to run the latest and greatest firmware. I have read in a few places that the new bootloader is un-cracked though and can't be rooted? Thanks.
DaMonsterMonster said:
Hi I have a problem from going to 5.1.1 from 5.0.2. I have tried clearing cache,
I have 9gb free,
made sure everything is up to date and enabled,
and have factory reset my phone.
Still doesn't work.
Says something about "dm- verity verification fail" if I go into that developer screen when you hold power, home and volume up right after it tries to update again while loading.
Never has been rooted and have had it for a few months now. Also I was wondering if I could root this phone and just manually update it with custom firmware and forget about Ota updates anymore and be able to run the latest and greatest firmware. I have read in a few places that the new bootloader is un-cracked though and can't be rooted? Thanks.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the specific help you need, I'm going to move this thread to your device's Q&A forum. Good luck!
The_Merovingian said:
Greetings,
Thank you for using XDA Assist. To get you the specific help you need, I'm going to move this thread to your device's Q&A forum. Good luck!
Click to expand...
Click to collapse
Awesome thanks!
Hi there! Have you tried options 1 & 2 in this HOWTO guide?
DaMonsterMonster said:
Awesome thanks!
Click to expand...
Click to collapse
lirex said:
Hi there! Have you tried options 1 & 2 in this HOWTO guide?
Click to expand...
Click to collapse
#1 didn't show any update but I did go to the samsung kiosk in best buy. He said he has had this problem with phones on other carriers too and he flashed it! Still would like to know if anyone is working on rooting these...
DaMonsterMonster said:
#1 didn't show any update but I did go to the samsung kiosk in best buy. He said he has had this problem with phones on other carriers too and he flashed it! Still would like to know if anyone is working on rooting these...
Click to expand...
Click to collapse
Would love a root, but if the rumors are true, that a new S7 Active version will be announced in Jan and released in Mar, and the new S7 Active (still likely only an AT&T exclusive...) has noticeable improvements, perhaps a root solution for this phone may fall to the way-side.
I'm on the fence about getting an S6, kinda waiting to see if I can get any confirmed specs for a new S7.
Argh... tough...
This is by far my biggest issue with the phone right now.
I am constantly getting notifications and have to unlock the phone to see what they are.
I have gone in on and app-by-app basis and turned lock screen notifications on for textra, Facebook and gmail. But other apps that I use like Slack will not get anything other than "badges" notifications.
Is there a way to A) Set ALL apps to have lock screen notifications at once B) Force apps that wont even after manually setting to display
Performed another factory reset so I was able to get into settings
Build number I am on is MIUI 10.0.2.0(OEAMIFH)
viper98 said:
Performed another factory reset so I was able to get into settings
Build number I am on is MIUI 10.0.2.0(OEAMIFH)
Click to expand...
Click to collapse
Hello, do you have experience with adb/fastboot and access to a computer? If so, your best bet would be to flash the fastboot stock which should resolve the issue.
Crossvxm said:
Hello, do you have experience with adb/fastboot and access to a computer? If so, your best bet would be to flash the fastboot stock which should resolve the issue.
Click to expand...
Click to collapse
Will that void my warranty at all?
I was toying with the idea of trying to flash Android Pie, but since I've had the phone opened for less than 24 hours I didn't really want to unlock the bootloader and void warranties and whatnot already lol
viper98 said:
Performed another factory reset so I was able to get into settings
Build number I am on is MIUI 10.0.2.0(OEAMIFH)
Click to expand...
Click to collapse
viper98 said:
Will that void my warranty at all?
I was toying with the idea of trying to flash Android Pie, but since I've had the phone opened for less than 24 hours I didn't really want to unlock the bootloader and void warranties and whatnot already lol
Click to expand...
Click to collapse
Flashing stock? No. Flashing Pie? I'm not sure, but I'll tell you the same as I've told many others; wait for MIUI 10 Android 9 stable as it shouldn't be far off.
Thanks for the help.
Everything has been stable for about 19 hours now. Here's hoping it stays going!
New question added. Decided to just edit the thread instead of make a new one
So last night my face unlocked just stopped working. I deleted my face data and added it again and now it still doesn't work. It just says can't verify face. Anyone else experience this?
sruel3216 said:
So last night my face unlocked just stopped working. I deleted my face data and added it again and now it still doesn't work. It just says can't verify face. Anyone else experience this?
Click to expand...
Click to collapse
Not just spontaneously as you described. It's happened to many ppl but usually immediately after they updated, or tried a custom kernel. If you are unlocked try re-flashing the last image (or probably just boot.img). If not, you could try flashing the latest OTA image via recovery.
v12xke said:
Not just spontaneously as you described. It's happened to many ppl but usually immediately after they updated, or tried a custom kernel. If you are unlocked try re-flashing the last image (or probably just boot.img). If not, you could try flashing the latest OTA image via recovery.
Click to expand...
Click to collapse
Im locked. Never unlocked or rooted. It hasn't worked ever after it stopped last night. Multiple face deletes and re-adds. Also haven't updated since last ota 3 weeks ago.
sruel3216 said:
Im locked. Never unlocked or rooted. It hasn't worked ever after it stopped last night. Multiple face deletes and re-adds. Also haven't updated since last ota 3 weeks ago.
Click to expand...
Click to collapse
...If not, you could try flashing the latest OTA image via recovery. You can find the OTA's and instructions on how to perform a "rescue OTA" on Google's Dev Site. I know it sucks not having FR because it happened to me playing around with a kernel that wasn't updated for December. I got FR back by flashing a different, updated kernel. Let us know what you decide to do and how it turns out. No telling when you will get the next OTA!
v12xke said:
...If not, you could try flashing the latest OTA image via recovery. You can find the OTA's and instructions on how to perform a "rescue OTA" on Google's Dev Site. I know it sucks not having FR because it happened to me playing around with a kernel that wasn't updated for December. I got FR back by flashing a different, updated kernel. Let us know what you decide to do and how it turns out. No telling when you will get the next OTA!
Click to expand...
Click to collapse
Ok il try that thanks!
It's just annoyed cuz my phone has been the same for weeks and never rooted. It began with a notification saying I needed to re-registered my face or it might now work. So I deleted and added and then it's never worked since
v12xke said:
...If not, you could try flashing the latest OTA image via recovery. You can find the OTA's and instructions on how to perform a "rescue OTA" on Google's Dev Site. I know it sucks not having FR because it happened to me playing around with a kernel that wasn't updated for December. I got FR back by flashing a different, updated kernel. Let us know what you decide to do and how it turns out. No telling when you will get the next OTA!
Click to expand...
Click to collapse
I dont understand why i am getting this error:
PS C:\adb> adb sideload flame-ota-qq1b.191205.012.a1-59de0d4d
adb: failed to stat file flame-ota-qq1b.191205.012.a1-59de0d4d: No such file or directory
I have the file in the adb folder where i am launching cmd. adb devices shows my device ID and "sideload"
sruel3216 said:
I dont understand why i am getting this error:
PS C:\adb> adb sideload flame-ota-qq1b.191205.012.a1-59de0d4d
adb: failed to stat file flame-ota-qq1b.191205.012.a1-59de0d4d: No such file or directory
I have the file in the adb folder where i am launching cmd. adb devices shows my device ID and "sideload"
Click to expand...
Click to collapse
Make sure you have the correct image for your device. Flame is for the 4, not 4XL. If that is the correct image for you, most errors are caused by either 1) you are not using the latest adb/fastboot binaries. If you type adb version you should get a return of 29.0.5 (October 2019). or 2) you have multiple versions of adb on your machine and verifying the version as in #1 above will alert you to that. Even if you are in the same folder, if an older version is in your PATH statement it can/will cause issues. Good luck.:good:
PS.. or you forgot to add the ZIP extension in your command? The image is a zipfile and you have to include the entire filename including the file extension. eg. flame-ota-qq1b.191205.012.a1-59de0d4d.zip
v12xke said:
Make sure you have the correct image for your device. Flame is for the 4, not 4XL. If that is the correct image for you, most errors are caused by either 1) you are not using the latest adb/fastboot binaries. If you type adb version you should get a return of 29.0.5 (October 2019). or 2) you have multiple versions of adb on your machine and verifying the version as in #1 above will alert you to that. Even if you are in the same folder, if an older version is in your PATH statement it can/will cause issues. Good luck.:good:
Click to expand...
Click to collapse
Ahh it's prob 2). I have the 4 I just posted in XL cuz there is more activity.
sruel3216 said:
Ahh it's prob 2). I have the 4 I just posted in XL cuz there is more activity.
Click to expand...
Click to collapse
Ah, ok ... just remember the file extension too. Best of luck.
v12xke said:
Ah, ok ... just remember the file extension too. Best of luck.
Click to expand...
Click to collapse
got it to flash. i forgot to add the .zip part when sideloading.
now to see if faceunlock is fixed
Edit: Faceunlock still doesnt work...
is there an app in settings that controls faceunlock that i can clear data/cache and force stop?
sruel3216 said:
got it to flash. i forgot to add the .zip part when sideloading.
now to see if faceunlock is fixed
Edit: Faceunlock still doesnt work...
is there an app in settings that controls faceunlock that i can clear data/cache and force stop?
Click to expand...
Click to collapse
Not that I am aware of... it's the phone security so I'm sure it's encrypted and on the Titan M chip (but I don't know for sure). Some folks have had to do a factory reset to fix the issue, especially if BL locked. Highly unlikely next months OTA will fix your issue. Do you have the option of unlocking? If so, now would seem a good time because you're going to lose your data either way. Anyway, start backing your stuff up and it may be time for a FDR. :crying:
v12xke said:
Not that I am aware of... it's the phone security so I'm sure it's encrypted and on the Titan M chip (but I don't know for sure). Some folks have had to do a factory reset to fix the issue, especially if BL locked. Highly unlikely next months OTA will fix your issue. Do you have the option of unlocking? If so, now would seem a good time because you're going to lose your data either way. Anyway, start backing your stuff up and it may be time for a FDR. :crying:
Click to expand...
Click to collapse
damn it lol. yeah i have the option so i might as well unlock. Il do that tonight i guess. thanks for the help!
my phone wasnt ready for 2020
sruel3216 said:
...my phone wasnt ready for 2020
Click to expand...
Click to collapse
Live and learn. Next time unlock out of the box before setting up. Even if you have no intention of ever rooting, if the "fit hits the shan"- you have more tools (and options) being BL unlocked. Cheers! :good:
v12xke said:
Live and learn. Next time unlock out of the box before setting up. Even if you have no intention of ever rooting, if the "fit hits the shan"- you have more tools (and options) being BL unlocked. Cheers! :good:
Click to expand...
Click to collapse
unlocked and faceunlock works again...for now. hopefully that doesnt happen again. Thanks for the help!
Any idea what got it back going? Mine started repeatedly notifying me last night to update my face recognition data. As soon as I deleted the old data and enrolled again, it stopped working completely. Been broken 100% ever since. Tried reenrolling a couple more times. Reboot. So far no improvement. It just rhythmically flashes 'Can't verify face. Try again.'
fastpakr said:
Any idea what got it back going? Mine started repeatedly notifying me last night to update my face recognition data. As soon as I deleted the old data and enrolled again, it stopped working completely. Been broken 100% ever since. Tried reenrolling a couple more times. Reboot. So far no improvement. It just rhythmically flashes 'Can't verify face. Try again.'
Click to expand...
Click to collapse
This same exact thing happened to me last night. Message on the lockscreen saying to re-enroll my face or it may not unlock. What was funny was that it was able to unlock every time I tried. After re-enrolling, I get the same flashing "Can't verify face. Try again." message. Wonder if there was an A/B test that went out that messed things up. Do you happen to be rooted or have any other modifications?
Tried flashing a few different kernels to see if anything would change. I'm away from my computer for another week so I can't try reflashing images. Booting into safe mode did not work. Uninstalling Magisk did not work either.
sruel3216 said:
Im locked. Never unlocked or rooted. It hasn't worked ever after it stopped last night. Multiple face deletes and re-adds. Also haven't updated since last ota 3 weeks ago.
Click to expand...
Click to collapse
Same boat (locked and stock - Verizon....tried to BL unlock when first turning on phone (removed SIM as to not activate) but that didn't work so locked it is). 2 days ago got the android notification to update my face data so I deleted it and went to re add and nothing but the cannot verify face try again messages. I just deleted face data and use my fitbit to smart unlock for now until this gets fixed to avoid having to repeatedly type my PIN in. To note I did the December update back in early December so it's odd that this has now reared it's ugly head.
Seems to have happened to a lot of people after the new year. Y2K bug twenty years later perhaps? lol
tysj said:
This same exact thing happened to me last night. Message on the lockscreen saying to re-enroll my face or it may not unlock. What was funny was that it was able to unlock every time I tried. After re-enrolling, I get the same flashing "Can't verify face. Try again." message. Wonder if there was an A/B test that went out that messed things up. Do you happen to be rooted or have any other modifications?
Click to expand...
Click to collapse
Yep, that's precisely how mine is behaving. I'm 100% stock.
The same just happened to me the last evening. Suddenly that message popped in and when I tried to delete and re-add the face unlock it completely stopped working. Pretty sure there is some Google A/B testing going on.
People reported factory reset should be the only way to fix this, so I'm gonna wait till tomorrow for the new security patches.
bakemcbride21 said:
Same boat (locked and stock - Verizon....tried to BL unlock when first turning on phone (removed SIM as to not activate) but that didn't work so locked it is). 2 days ago got the android notification to update my face data so I deleted it and went to re add and nothing but the cannot verify face try again messages. I just deleted face data and use my fitbit to smart unlock for now until this gets fixed to avoid having to repeatedly type my PIN in. To note I did the December update back in early December so it's odd that this has now reared it's ugly head.
Seems to have happened to a lot of people after the new year. Y2K bug twenty years later perhaps? lol
Click to expand...
Click to collapse
fastpakr said:
Yep, that's precisely how mine is behaving. I'm 100% stock.
Click to expand...
Click to collapse
TENN3R said:
The same just happened to me the last evening. Suddenly that message popped in and when I tried to delete and re-add the face unlock it completely stopped working. Pretty sure there is some Google A/B testing going on.
People reported factory reset should be the only way to fix this, so I'm gonna wait till tomorrow for the new security patches.
Click to expand...
Click to collapse
yup pretty annoying. think factory reset is the only fix