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
I have a Pure Edition that I recently updated to the 5.1 OTA but I'm having problems with the screen never auto-sleeping.
Easy Stuff:
I have it set to sleep at 2 minutes and my dev setting for always-on-while-charging is turned off. This behavior happens whether it's charging or not.
History
Phone is Unlocked
It was running the first 5.1 Soak Test (i.e. the one that couldn't directly run this OTA)
I downgraded to the 5.0 factory image
After the downgrade, it immediately picked up the OTA and installed without a single visible problem.
I did a factory reset (via settings menu) just to start from a clean slate once on the 5.1 OTA image.
It is still unlocked but I have never rooted/modified this 5.1 OTA. I want it stable before I mod anything. I even still have stock Recovery.
So my assumption is that given that the 5.1 OTA image installed successfully, that's proof that I did a proper/complete downgrade to the 5.0 image. Is this correct?
Any other thoughts on what to look to before starting down the downgrade/wipe/etc. path again? I spoke to a friend who also has a Pure Edition that just went to the 5.1 OTA and he's not having no problem at all like this.
I'm really just guessing here but perhaps it could be an issue with attentive display. Maybe try turning it off to see if it will turn off.
Sent from my XT1095 using Tapatalk
Jaxidian said:
I have a Pure Edition that I recently updated to the 5.1 OTA but I'm having problems with the screen never auto-sleeping.
Easy Stuff:
I have it set to sleep at 2 minutes and my dev setting for always-on-while-charging is turned off. This behavior happens whether it's charging or not.
History
Phone is Unlocked
It was running the first 5.1 Soak Test (i.e. the one that couldn't directly run this OTA)
I downgraded to the 5.0 factory image
After the downgrade, it immediately picked up the OTA and installed without a single visible problem.
I did a factory reset (via settings menu) just to start from a clean slate once on the 5.1 OTA image.
It is still unlocked but I have never rooted/modified this 5.1 OTA. I want it stable before I mod anything. I even still have stock Recovery.
So my assumption is that given that the 5.1 OTA image installed successfully, that's proof that I did a proper/complete downgrade to the 5.0 image. Is this correct?
Any other thoughts on what to look to before starting down the downgrade/wipe/etc. path again? I spoke to a friend who also has a Pure Edition that just went to the 5.1 OTA and he's not having no problem at all like this.
Click to expand...
Click to collapse
Chill bro.. Its a usual bug.. Nothing to worry.. Clean the partition cache in recovery.. You are good to go...
One of my friend did a factory reset in 5. 1 and had this problem...
Sent from my XT1092 using XDA Free mobile app
So recently I flashed some Marshmallow roms and i missed my xposed so i went back to lollipop. After noticing some smoothness loss, I then flashed stock lollipop and still have issues.
Has anybody else had this problem? If so, do you have any solutions? Thanks!
TheGingerlyGamer said:
So recently I flashed some Marshmallow roms and i missed my xposed so i went back to lollipop. After noticing some smoothness loss, I then flashed stock lollipop and still have issues.
Has anybody else had this problem? If so, do you have any solutions? Thanks!
Click to expand...
Click to collapse
That happened to me too when I went back to Lollipop a few days ago for the exact same reason. I tried everything and nothing could match the smoothness and/or battery life of Marshmallow. I said screw it and flashed 6.0 a few hours ago. That's the only solution I found.
So can't check "allow OEM quick" on N.
Already opted out of developer preview thru the site, and 4 days later, still no ota back to MM. Suggestions?
I thought to just fastboot twrp and try to flash a stock rom to allow unlock then start from the beginning but wanted opinions first.
Sent from my Robin using XDA-Developers mobile app
sookieball said:
So can't check "allow OEM quick" on N.
Already opted out of developer preview thru the site, and 4 days later, still no it's back to MM. Suggestions?
I thought to just fastboot twrp and try to flash a stock rom to allow unlock then start from the beginning but wanted opinions first.
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
well, to flash stock, you dont use twrp, you use fastboot while youre in the bootloader. and in N, allow oem unlock is automatically enabled.
It isn't tho
It i tried OEM unlock and it didn't work. :-/
Sent from my Robin using XDA-Developers mobile app
sookieball said:
It isn't tho
It i tried OEM unlock and it didn't work. :-/
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
how? did you do fastboot oem unlock?
Maybe you've already tried this, and I don't know if it will work, but have you tried re-enrolling and unenrolling in the hope that it will jog the revert mechanism into life?
I have tried enrolling and unenrolling a few times....
No dice.
Sims,
In fastboot... fastboot OEM unlock. Then error.
Sent from my Robin using XDA-Developers mobile app
sookieball said:
I have tried enrolling and unenrolling a few times....
No dice.
Sims,
In fastboot... fastboot OEM unlock. Then error.
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
you pribably cant oem unlock while on N then. that probably why they made it unavailable. im not on N now, so cant test.
What about trying a sideload of the full OTA? I thought (I might be wrong) that it's independent of a locked bootloader.
https://developers.google.com/android/nexus/ota#instructions
It's worth a shot, especially as it doesn't overwrite your data.
On a related note, I'm on preview 3 - battery drain when idle is higher than what it was on stable M, so thinking about reverting back to M.
1. To avoid a factory wipe, can I just flash the img files from the stable M (skipping userdata) on top of the preview 3?
2. If so, to avoid getting the N preview update notification, I guess I will need to un-enroll from the beta program. Will that cause an OTA to be sent back to my phone (causing factory wipe as described on the beta page)? Or does it recognize that I'm already on 'M' and skip the OTA?
3. Before I do this, is it possible to flash the radio only from the latest "M" image on the "N" preview? (could that help with the drain when idle?)
Did you not like my previous answer...?
http://forum.xda-developers.com/showpost.php?p=66961421&postcount=104
dahawthorne said:
Did you not like my previous answer...?
http://forum.xda-developers.com/showpost.php?p=66961421&postcount=104
Click to expand...
Click to collapse
LOL! Yes, I did! And thank you for that as well - the part that I didn't understand (and unless I missed it in your response, I don't think we talked about in that post) was - since I'd still be enrolled in the preview/beta program, how do I get out of the program, without getting factory reset.
(I do have a nandroid backup as a last ditch option - trying to do this the 'clean' way first)
The preview is working well for me as well - skype is the only app giving me grief, but I can live with that. The battery drain on idle seems to be significantly higher than what I encountered with "M" stable. With barely any usage this morning (screen on for 11 minutes), my battery is at 77% (full charge and off the charger at 10 pm last night). Cell Standby is the the highest drain (6%). Phone idle and Android system tied for 2nd place at 3%.
With the latest M build, I'd be at over 90% battery remaining (with similar usage).
You're right on all counts...
I think the answer to your wipe question is that you'd have to agree to do it - if you unenrol and have already reverted manually to M, the downgrade OTA may be downloaded (though from my experience, as I said, I think the developers are smart enough to recognise that it's a waste of time and even that won't happen) but you would still have to push the button to accept it. They won't unceremoniously dump it on you without your permission.
And the battery drain... I was wondering if it was my imagination, or maybe just that my phone is a year old (I got a replacement last May) and the battery's a bit tired, but I've noticed that the percentage drops almost before my eyes. I have Battery Bot Pro showing my percentage figure on my status bar, and it seems to me that every time I unlock the phone another one or more percentage points have gone. It went from 97% this morning to 77% in a couple of hours, and I recharged it before I went out to work - it's now already down to 75% and falling. Like you, I'd expect it to be a clear 10% or more better than this over this period.
Looks like Google have a bit more work to do on their power management...
Edit: And in the 5 minutes since I wrote this, with the phone sitting beside me, screen off, nothing running, it's already down to 74%. Not at all impressive. Despite being relatively happy with it, I may have to renege on my previous comment that I can't see myself reverting to M.
And before you ask, I'll be reverting using my TWRP backup of M which I took immediately before I installed N...
Thank you
I'll wait for the June security update (factory image) and install that directly (skipping userdata). If that fails, I'll revert to the TWRP backup. (restoring TWRP on my old N5 has given me grief in the past, so going to avoid that if possible)
Edit: maybe I'll try flashing the radio from the May image onto "N" and see if that helps. The battery drain appears to be radio related.
Done. No problem at all. TWRP took about 12 minutes to restore 7GB of data, then a rather nerve-racking 5 minutes with the Google quad-icon swapping bits, and I'm back to MOB30I.
Seven updates waiting; BBC Radio, Skype, Google Drive, Sygic, all the broken apps working again, still have root.
Welcome back, old M world...
And if you're thinking of restoring M early next month, I'd give the OTA version a try. Just out of curiosity I sideloaded the MOB30H OTA on my Nexus 5 a few days ago, and it worked flawlessly without wiping any data. That's what I'll be doing on my N6 in June.
I've also just unenrolled from the Beta program, and checked for a system update. Exactly as I thought, "Your system is up to date" on MOB30I. I know that the OTAs have been slow for some people, but I don't expect to see the revert OTA - I'll post in this thread if I ever do.
dahawthorne said:
And if you're thinking of restoring M early next month, I'd give the OTA version a try. Just out of curiosity I sideloaded the MOB30H OTA on my Nexus 5 a few days ago, and it worked flawlessly without wiping any data. That's what I'll be doing on my N6 in June.
Click to expand...
Click to collapse
Would the fact that I'm rooted cause any issues with sideloading the OTA? (I realize the new OTA is essentially a full image, so it should just overwrite the system, and I'd have to reroot after that)
No problems at all, no. My N5 was rooted & encrypted, and the OTA slid in easily. As I said in another thread, it boots into TWRP but the OTA is designed to handle that. I installed TWRP again anyway, probably pointlessly but just to be on the safe side, and then used it to install SuperSU 2.74.
Easy as pie...
I unenrolled, got a prompt for system "update" back to MM, it downloaded, and now I am going on 30 minutes on the install part....been stuck on the reboot screen with 4 colorful circles....
How long does it take to re-install MM? TIA
EDIT: Decided to hold down power button for about 5 seconds and it rebooted to setup screen
dahawthorne said:
And the battery drain... I was wondering if it was my imagination, or maybe just that my phone is a year old (I got a replacement last May) and the battery's a bit tired, but I've noticed that the percentage drops almost before my eyes. I have Battery Bot Pro showing my percentage figure on my status bar, and it seems to me that every time I unlock the phone another one or more percentage points have gone. It went from 97% this morning to 77% in a couple of hours, and I recharged it before I went out to work - it's now already down to 75% and falling. Like you, I'd expect it to be a clear 10% or more better than this over this period.
Click to expand...
Click to collapse
I ended up flashing the radio (only) from MOB30I on to the N preview, and so far, the battery life on idle is back to how it was on M. I think I have a reason to stick on to the N preview a bit longer now
banditsw said:
How long does it take to re-install MM? TIA
Click to expand...
Click to collapse
Looks like you got it sorted out, but just for future reference, the reason it took long is because it essentially factory reset your phone - a factory reset with full wipe on the encrypted N6 cane take 20-30 minutes.
I'm impatient, me, so by the time I read this I was already back on MOB30I, but in any case I'm happier to have all working apps without the rash of library errors and force-closures. Interesting thread...
But we never heard back from sookieball after I suggested a sideload: http://forum.xda-developers.com/showpost.php?p=67013821&postcount=8
dahawthorne said:
But we never heard back from sookieball after I suggested a sideload: http://forum.xda-developers.com/showpost.php?p=67013821&postcount=8
Click to expand...
Click to collapse
I ended up reverting back to the "M" stable image yesterday (was waiting for the June image to be available). No issues with the "N" to report, except one custom app that I use was giving me some issues.
Anyway, thought I'd share my "downgrade" story
If you do the downgrade the right way (un-enroll from the Beta program), and get the OTA back to the latest "M", it will likely go well - because it performs a factory reset on your phone.
I however, didn't wait to set my phone up from scratch (lazy), so I flashed the factory image for the latest "M" (and skipped userdata.img). Bad idea. Flash went thru' successfully, but I ended up with pretty much an unusable phone because two system processes kept crashing in a loop after booting up. I then tried ADB sideload for the new OTA image file - same results. Wiped cache partition - no difference.
I then remembered that some apps (like Google Maps) had different versions for "N", and realized that the issue must be because of apps like that not being compatible with "M". Thankfully, I had a nandroid backup of the "M" (May security release) from before I installed "N", and I installed that - and then, updated to the June security release of "M".
Whew!
So, in summary, If you are rooted, take a nandroid backup in TWRP before you install "N" preview. If not, plan to factory reset your device after going back (or while going back) to "M" - no shortcuts.
So Blu finally released the Marshmallow update for the Vivo XL... and it kind of sucks. It's only 6.0 and not 6.0.1. The Gionee model of this phone has been running 6.0.1 since June. Updating via the OTA was a nightmare. It failed 3 times before it finally worked. Then I performed a factory reset, as always when performing a major update. It seems that you cannot format the memory card to use it as internal storage. It gives you the option but it ALWAYS fails. Also, the battery life blows. I lost 20% battery overnight while the phone was inactive and supposed to be dozing. Very disappointing so far. Anyone else have any problems?
My update failed several times but that was about he only problems I've faced. After a factory reset everything seems to be working fine. I am able to use my micro SD as internal as well. No other problems at all with what you mentioned. Everything seems to run smoother than it did on lollipop (but that could be as a result of the factory reset).
I'd love the upgrade if it didn't break compatibility with one crucial app. Until the issue of false root positives is addressed, I'm sticking to lollipop.
my wife's phone updated first try, didn't even feel the need to factory reset it after it came up, so far buttery smooth and better battery life, i think like 1 % over night sitting there and moderate use she got a few days out of her phone. so far i'm happy
My Vivo XL updated with no problems. However, i have noticed that it runs slower than before when viewing Netflix or listening to music, even though i only have 2 or 3 other apps opened at the same time. I usually have to free up more RAM to get it to work properly but i never had this problem when the phone was running Lollipop. Can be irritating at times because even some websites will lag or typing text messages can be slow because the lag time is ridiculous.
weatherdude35 said:
My Vivo XL updated with no problems. However, i have noticed that it runs slower than before when viewing Netflix or listening to music, even though i only have 2 or 3 other apps opened at the same time. I usually have to free up more RAM to get it to work properly but i never had this problem when the phone was running Lollipop. Can be irritating at times because even some websites will lag or typing text messages can be slow because the lag time is ridiculous.
Click to expand...
Click to collapse
Back up your things and try a factory reset. Had the same problems but this fixed it.
This was a good updated for me
WiddleyScudds said:
This was a good updated for me
Click to expand...
Click to collapse
Yeah. I'm the OP. After a couple days, the update settled in. Battery life went back to normal, which is to say, stellar. So basically, all good here.
xphyle1971 said:
Yeah. I'm the OP. After a couple days, the update settled in. Battery life went back to normal, which is to say, stellar. So basically, all good here.
Click to expand...
Click to collapse
Extreme mode is also impressive don't know if you've seen it. Do you know if there is root yet? I've attempted king root but it fails and I don't want to brick this phone trying to F with other methods
I'm also running 6.0 and it seems to be working great. Much smoother and better battery life. Does anyone know of a method to root the Vivo XL running 6.0 yet?
Good afternoon guys, I have a problem, to update mi Blu vivo XL to Marshmallow the official BLU site says that my version number should be : BLU_V0030UU_V10. I am a little confused about this version number. That is the number in the Wireless update? I have this Current number in Wireless update BLU_V0030UU_V07_GENERIC_5.1_20160126-1033, but when I have tried to check for updates I can't install nothing, this message appears " Your system was damaged, wireless update is disabled". I don't know what to do, I can't install the update via Wireless update, Is there any other method like manually transfer a file? If it is possible, where can I find the file and what is the file name?
adaeda said:
Good afternoon guys, I have a problem, to update mi Blu vivo XL to Marshmallow the official BLU site says that my version number should be : BLU_V0030UU_V10. I am a little confused about this version number. That is the number in the Wireless update? I have this Current number in Wireless update BLU_V0030UU_V07_GENERIC_5.1_20160126-1033, but when I have tried to check for updates I can't install nothing, this message appears " Your system was damaged, wireless update is disabled". I don't know what to do, I can't install the update via Wireless update, Is there any other method like manually transfer a file? If it is possible, where can I find the file and what is the file name?
Click to expand...
Click to collapse
I also have this issue. probably because of being rooted. However even I restored original ROM backup and original recovery, I still got such information and cannot do OTA update.
it works correctly , the system is smooth and everything is fine , maybe You a have a rooted device try reflashing and redownload the update
adaeda said:
Good afternoon guys, I have a problem, to update mi Blu vivo XL to Marshmallow the official BLU site says that my version number should be : BLU_V0030UU_V10. I am a little confused about this version number. That is the number in the Wireless update? I have this Current number in Wireless update BLU_V0030UU_V07_GENERIC_5.1_20160126-1033, but when I have tried to check for updates I can't install nothing, this message appears " Your system was damaged, wireless update is disabled". I don't know what to do, I can't install the update via Wireless update, Is there any other method like manually transfer a file? If it is possible, where can I find the file and what is the file name?
Click to expand...
Click to collapse
Same here, my android 6.0 version was v07. Oddly enough, the first OTA update is v10. But then the next OTA update took the label back to V07. I reverted back to android 5.1 stock rom, since that was the only way I could get TWRP to load.
How can I go back to the lollipop update ???
Pls I need you guys to help me
I'm using BLU vivo XL, I flashed my phone through stock recovery and I wiped cache & format the phone then rebooted the phone, ever since then its been writing invalid imei, I checked the baseband and it's not showing anymore, I've tried to fix this but no way, I later downloaded the stock ROM and reflashed the phone still its showing invalid imei, I wanted to download Gionee S plus stock firmware but dunno if it's gonna fix the problem, pls I need guys to guide me on how best to fix this issue, its been two weeks + now, God bless.
someone share marshmallow for vivo xl (blu vivo xl v0030uu)