Database Develop

[Q] Status bar stuck after screen unlock

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

Nexus 6 Reboot/Optimize Apps after 5.X update

Hey there,
I got quite a serious problem. Since i updated to 5.1 my phone sometimes suddenly restarts, followed by a message which says "optimizing apps", which ranges from 30 to 150 apps. At first, it was no big problem, now it occures nearly every 10 minutes, so currently i can't really use my phone.
What i tried to do:
Factory reset, reflash 5.0 - 5.1.1 (every single image available)
The problem is still there.
Now my question, is it a Softwareproblem, which will be updated soon (should i try Android M (what about the warranty?))?
Or is it quite a serious hardwareproblem (i read somewhere that it could be because of overused RAM modules)?
I tried to use the searchengine, but i didnt find a specific thread in this subforum.

The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though

danarama said:
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
Click to expand...
Click to collapse
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.

Haabiii said:
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Click to expand...
Click to collapse
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.

Evolution_Tech said:
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
Click to expand...
Click to collapse
Thanks, I didn't know that.
Evolution_Tech said:
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Click to expand...
Click to collapse
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
Evolution_Tech said:
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Click to expand...
Click to collapse
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.

Haabiii said:
Thanks, I didn't know that.
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Click to expand...
Click to collapse
Personally, I'd boot to bootloader and do:
fastboot format cache

Evolution_Tech said:
Personally, I'd boot to bootloader and do:
fastboot format cache
Click to expand...
Click to collapse
Already done and i also reflashed the whole cache image. I hope the Android 6 Update will help solve my issues. The problem is, that i usually get really upset about little stuff like that just because i don't get why it's happening.

I updated monday evening to the Android M Preview, for now it only restarted once to, as it said, install a update (?), since then no reboot at all. It worked like a charm yesterday. I really hope the problem is fixed that way.
Just wanted to let you know if you have a same problem.

Missing "System Updates" button in about phone

Yesterday morning I noticed that the "System Updates" button in Settings/About Phone was missing. At the time I was on the LVY48F(Project Fi build) but have since flashed MRA48K without wiping ddata and it is still missing. Some Google searching found one thread regarding an N5 with the same issue but the resolution they found was a Factory Reset. I'm not opposed to wiping data to fix issues but since this is really more of an annoyance than a problem since I usually flash the images ADB sideloaded the OTAs I don't mind doing some research to see if I can fix . Anyone ever seen this before and know a way to fix it? When I get home from work I'm going to try to use ADB to run the Setup Wizard like you would if you had the broken home button and notification shade.

Did you try 'wiping cache'?

Cache wipe from stock recovery didn't help. I wiped data for the settings app as well with no change.

I would just back up your phone then factory reset everything

irontaco1 said:
I would just back up your phone then factory reset everything
Click to expand...
Click to collapse
Yeah, I mentioned that I don't mind doing a Factory Reset, just wanted to explore any options to fix it without wiping first.
Unfortunately, i dont think backing everything up would prevent me from having to reset my Android Wear watch to be able to pair with again which is the 1 and only thing that annoys me about resetting.

Did you find a solution to your problem yet?

irontaco1 said:
Did you find a solution to your problem yet?
Click to expand...
Click to collapse
Honestly haven't put a lot of time into it yet, hoping to get some time after work today.

For some other reason I ended up doing a factory reset and the button is back. I was sure wiping would bring it back but was really looking forward to digging through the phone and figuring it out.

Well its good that it's fixed I guess

face unlocked stopped working?

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

Somehow stuck at Secure start-up - How Hosed am I?

Hello and thanks for your help. Somehow, on a reboot of my new 405QA I am stuck at the secure startup screen as seen in the attached image. I have no idea what this is, what it means, or how to get past it. I do not use anything but a swipe lockscreen so there is no fingerprint, pin, or pattern if that is what it seeks. I do not think I even enabled this "feature" but maybe it was turned on by default?
Anyhow, what can I do? I would like to preserve my system and I believe that if I fail to come up with what it wants, it will factory reset the phone.
Thanks for your help!

I gave up and went through the 30 tries until the thing factory reset. What BS. I never enabled this.

whitedavidp said:
I gave up and went through the 30 tries until the thing factory reset. What BS. I never enabled this.
Click to expand...
Click to collapse
This same thing happened to me when I first tried to unlock the bootloader and root the device. It is not an easy thing to do. I, like you, ran into roadblocks along the way. Lucky for me, I was upgrading from a Nexus 6 (still love that phone) that was operating just fine. So I could take my time and get the LG40 up and running how I wanted it to be (bootloader unlocked, unencrypted and rooted with Magisk) before I began setting it up.
Just be patient, and you'll get there too.
[NG]Owner

NGOwner said:
This same thing happened to me when I first tried to unlock the bootloader and root the device. It is not an easy thing to do. I, like you, ran into roadblocks along the way. Lucky for me, I was upgrading from a Nexus 6 (still love that phone) that was operating just fine. So I could take my time and get the LG40 up and running how I wanted it to be (bootloader unlocked, unencrypted and rooted with Magisk) before I began setting it up.
Just be patient, and you'll get there too.
[NG]Owner
Click to expand...
Click to collapse
How did you guys fix it? Same roadblock too

minecraftuser1999 said:
How did you guys fix it? Same roadblock too
Click to expand...
Click to collapse
You could try resetting the device using the button combination