[Q] Status bar stuck after screen unlock - AT&T Samsung Galaxy S6

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

Related

[Q] New System Update

I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
ace_case said:
I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
Click to expand...
Click to collapse
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
skeevydude said:
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
Click to expand...
Click to collapse
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
ace_case said:
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
Click to expand...
Click to collapse
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
palmbeach05 said:
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
Click to expand...
Click to collapse
I'd say it's more like posting on Craigslist that you're going on vacation and then leaving all the doors open with your debit/credit card on the coffee table. It's a pretty serious bug, and according to wikipedia, 1.5% of the most popular 800,000 websites are still vulnerable to the bug, not to mention running a sideloaded app or connecting to a malicious website.
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
Flashing back to completely stock may be the easiest way to get the update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
If you flash the OTA update manually using something like Philz recovery, you can see the progress on the screen and where it stops updating. For me, it kept hanging on updating the smartactions.apk, which was because I had previously (long time ago) merged updates of the app to my System partition (along with a few other apps that were updated). This will mess up any attempt to do an OTA update, because your "stock" ROM is no longer stock.
I ended up having to flash back to the real stock with Mythtools, then install the OTA zip manually.
If you can't find the zip in your cache, you can download it directly from this post (thanks @skeevydude): http://forum.xda-developers.com/showpost.php?p=52657363&postcount=13

Unable to use home button on 4.4.4

I just upgrade to 4.4.4 .
I don't know why the home button disable after I upgrade the software from play store.
Swipe to open the google is unable to use too.
Appreciate the help!
that is just not enough information. what software did you upgrade from the play store? 4.4.4 doesn't come from the play store, it comes as an OTA update. did you install a new launcher?
640k said:
that is just not enough information. what software did you upgrade from the play store? 4.4.4 doesn't come from the play store, it comes as an OTA update. did you install a new launcher?
Click to expand...
Click to collapse
Thank you for your reply.
I'm using sprint's latest rom.
I found that every time when I reboot my phone ,while starting the system it will says : starting services.
There is a little wheel is rolling, every time . It takes about 1 minute to Finnish,So I try to skip it then cause this problem, if I wait till it finnished the problem will disappear.
BTW, I have not sim insert my phone.maybe this is the reason?
Very appreciate your help!
myarms said:
Thank you for your reply.
I'm using sprint's latest rom.
I found that every time when I reboot my phone ,while starting the system it will says : starting services.
There is a little wheel is rolling, every time . It takes about 1 minute to Finnish,So I try to skip it then cause this problem, if I wait till it finnished the problem will disappear.
BTW, I have not sim insert my phone.maybe this is the reason?
Very appreciate your help!
Click to expand...
Click to collapse
Are you rooted/ have safestrap/ have bootloader unlocked??? You could fix the problem without too much difficulty if you do.
If not, a factory reset may be your only option. If that doesn't fix the issue, I'd say talk to verizon or moto about getting a new phone.
1ad_m12 said:
Are you rooted/ have safestrap/ have bootloader unlocked??? You could fix the problem without too much difficulty if you do.
If not, a factory reset may be your only option. If that doesn't fix the issue, I'd say talk to verizon or moto about getting a new phone.
Click to expand...
Click to collapse
Thank you 1ad,
I'm using unlock BL phone, I think It's software problem, maybe because I'm using OTA to upgrade to 4.4.4.
myarms said:
Thank you 1ad,
I'm using unlock BL phone, I think It's software problem, maybe because I'm using OTA to upgrade to 4.4.4.
Click to expand...
Click to collapse
Did you use sunshine? I had an issue with my ROM after I used it. I restored from a backup and it fixed my issue/ kept the phone unlocked.
Use this to flash back to stock. Should fix any problems you have. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
1ad_m12 said:
Did you use sunshine? I had an issue with my ROM after I used it. I restored from a backup and it fixed my issue/ kept the phone unlocked.
Use this to flash back to stock. Should fix any problems you have. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
I'm sorry, what's sunshine?
I'm already using stock rom before I'm using Verizon's rom have not kind of problem.
myarms said:
I'm sorry, what's sunshine?
I'm already using stock rom before I'm using Verizon's rom have not kind of problem.
Click to expand...
Click to collapse
Sunshine is a BL unlock exploit for phones with locked BL's.
What I mean by returning to stock rom is reinstalling the firmware. It is very possible that the OTA did not correctly download to your phone/ not install properly.
Thank you for your information, 1ad.
I may try the way you said next time.

Thinking about lollipop upgrade

im pretty happy with kk, but i do want to be on 5.0, so i just wanted to make a few thing clear first.
1. if anything goes wrong with flashing a captured ota, how to restore my kk as it is now? will simply restoring a twrp backup do the trick on any stock rom?
2. where can i find the stock rom? the motorola site links arent working for me.
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
5. are there any bugs that seriously affect most users?
i am planning to root immediately so root only mods are fine.
im on a rooted unlocked bootloader xt1063,
thanks for your time,!
1. Just flash the stock ROM via fastboot.
2. I guess are some links on the Development section.
3. in 5.0, unfortunately not.
4. I guess no :/
5. Only a bootloop that happens with the newest versions of SuperSU (the only versions that works with 5.0), no major bugs..
Sent from my XT1063 using XDA Free mobile app
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Kobro said:
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Click to expand...
Click to collapse
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Kobro said:
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Click to expand...
Click to collapse
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Kobro said:
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
Click to expand...
Click to collapse
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Flash custom rom and enjoy lollipop
pastorbob62 said:
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Click to expand...
Click to collapse
your right for stating everything clearly, my bad
anomalyconcept said:
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Click to expand...
Click to collapse
yes that works, and has been since 4.3, on my custom rom devices it just is not so comfortable on a 5" device i was thinking more of something like pull down from right.
these responses motorola about the model xt1068
Catherine: Hi, my name is Catherine. How may I help you?
ENRICO: good morning
are to hold model xt1068, I wanted to know when will the update to Android 5
Catherine: Hi, at the moment we do not have a release date for Lollipop in Europe. It is currently going through testing before release but we are working hard to get it out as soon as possible. You can find the latest information at http://www.motorola.com/updates
ENRICO: thanks
Catherine: No problem, is there anything else that I can help you with?
ENRICO: no thanks
Catherine: Ok, have a nice day!
ENRICO:
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Kobro said:
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Click to expand...
Click to collapse
Don't need it now, but good to know should I have to reflash in the future. Thanks for the info. :good:

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.

Should I downgrade my android version?

Hey, I am currently running 6.0.1 as my android version. Just asking but would it be suggested to downgrade the android version? If yes, than too which version?
Why do you want to downgrade?
The Nexus 6 came out with the 5.0, you can't go further back, even with custom roms. Actually I've head somebody trying to build KitKat for the shamu, but I don't know if he succeeded.
Also why would you like to downgrade, anyway?
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Why not upgrading to android 7 instead of downgrading?
php111 said:
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Click to expand...
Click to collapse
Why don't you try upgrading instead? Android 7.0 factory image has just been released.
Oh, has it been released? Does it causes those boot loop issues on Motorola branded phones just like it does with LG branded? And could I upgrade using the Wugs tool?
php111 said:
Oh, has it been released? Does it causes those boot loop issues on Motorola branded phones just like it does with LG branded? And could I upgrade using the Wugs tool?
Click to expand...
Click to collapse
If you want to flash the factory image then go here: https://developers.google.com/android/nexus/images#shamu
You will find the factory image for 7.0 there and also the instructions on how to flash it. If you are already on stock 6.0.1, you should bee recieving an OTA update soon. But since you say you have reboots and freezes I would take a backup of what every you need onto your computer and then start of fresh from the link above. That way you won't be haunted by old bugs that might be stuck because of previous versions.
php111 said:
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Click to expand...
Click to collapse
These freezing/slow/crashing issues look very unique to you. Why didn't you try a factory reset, then add your apps back one by one, and look for those that give you trouble. Also are you rooted, do you use xposed or anything that modifies the basic system? Because I'm runnin 6.0.1 myself, and never had the issues you do.
The instructions on the developer page to flash looks too confusing. Well, it jumps right into it when myself I never done it before.
Everybody on this site once knew nothing about Android. Your safest bet is to just wait for the OTA to be offered (or proactively check for it) and accept it. If you're as novice as your posts suggest, I'm guessing that you're running a pure stock device, so you won't run into any problems with the upgrade. And if you do, you know where we are...

Categories

Resources