G800H Lollipop 5.1.1 battery drain / no deep sleep - Galaxy S5 Mini Q&A, Help & Troubleshooting

Hi, I am wondering if anyone else has experienced this issue... I have an S5 G800H which originally came with 4.4.2. I update it to 5.1.1 when the first ROM came out in... October or November. It was a Russian ROM, and I was having issues with a weird battery drain issue. I reverted back to 4.4.2, and came back to 5.1.1 weeks ago. I again tested a version meant for Caucasus countries, one for South Africa and another one for United Arab Emirates. All of them lead to the very same problem, regardless of root or Xposed.
Overnight, when it is charging, the phone will stop deep sleep. That means the lowest frequency the device will use is 300MHz. No more deep sleep, which means it starts sucking the battery the moment I unplug it.
I checked the wakelocks etc. and found an alarm called "com.google.android.gms" that comes up every minute. No wonder the device does not sleep.
I can reboot, but it will stay awake. Once I clear the cache, all is fine until the next night.
Does anyone have a clue how to resolve this issue? It's really troublesome and I don't want to go back to 4.4.2 - the built is from August 2015 - with security updates as old, too.

Still no Lollipop for your country? If yes, I would go back to factory stock ROM then apply OTA to update and check if everything is fine. Don't let Google restore your apps, do a test for a few days using only the minimum apps installed manually.

lfom said:
Still no Lollipop for your country? If yes, I would go back to factory stock ROM then apply OTA to update and check if everything is fine. Don't let Google restore your apps, do a test for a few days using only the minimum apps installed manually.
Click to expand...
Click to collapse
Well I am in the EU and Samsung does not sell the G800H in the EU; they don't want dual sim devices here (for obvious reasons).
I must admit I even don't know what the original firmware was, but I think it was for South Africa, built in July 2015. Guess I could track it down. But to my understanding the CSC should not matter when I do a full flash through Odin.

Related

Got some sort of Update today...not 5.0

My SM-T700 is rooted so I don't get OTA updates. But when I hooked it up to Kies a while ago it said there was an update available so I said OK to install. After it rebooted, it went through an "Android is upgrading" screen where it counted up my apps from 0 to 150. It looked like my phone did when I turned on ART so I was thinking could this be 5.0? But no, it is still showing 4.4.2 in About Device.
Also says
Kernel Version 3.4.9-3702705, [email protected] #1, Sat Dec 27 19:56:44 KST 2014
Build number KOT49H.T700xxU1ANL2
Kies says my firmware version is PDA:NL2 / CSC:NL2 (XAR)
I've only played with it a few minutes but nothing obvious changed
I'm not rooted, also got the update. Not sure what it did.
catman51 said:
I'm not rooted, also got the update. Not sure what it did.
Click to expand...
Click to collapse
Did you get the upgrading apps thing when it restarted? Unlike my phone which is on 4.4.4 my tablet does not seem to give me the ability to enable ART in the developer settings. Bu the way it was doing the upgrading apps it looked just like my phone did when I turned on ART. I'm wondering if this could be some kind of preparatory update to get the device ready for the Android 5.x update?
I don't see art listed.
catman51 said:
I don't see art listed.
Click to expand...
Click to collapse
It isn't. Bt I think theupdate may have been doing it anyway.
still rootable?
hey guys. i just grabbed this tablet a couple days ago and it to is running same build, NL2. question is, do you know if i can still root with cf-auto-root beanstown port? thx gents
ratman6161 said:
My SM-T700 is rooted so I don't get OTA updates. But when I hooked it up to Kies a while ago it said there was an update available so I said OK to install. After it rebooted, it went through an "Android is upgrading" screen where it counted up my apps from 0 to 150. It looked like my phone did when I turned on ART so I was thinking could this be 5.0? But no, it is still showing 4.4.2 in About Device.
Also says
Kernel Version 3.4.9-3702705, [email protected] #1, Sat Dec 27 19:56:44 KST 2014
Build number KOT49H.T700xxU1ANL2
Kies says my firmware version is PDA:NL2 / CSC:NL2 (XAR)
I've only played with it a few minutes but nothing obvious changed
Click to expand...
Click to collapse
What is the exact model number of your tab? If you check samobiles website there are many updates for our device in different countries which is all based still for 4.4.2. So bummer Lollipop after a few months
Got an update just know as well. UK Samsung Tab S 8.4 user. Took a screenshot:
Sent from my SM-T700 using XDA Free mobile app
I bought a UK Samsung Tab S 8.4 the other day and it had this update. I haven't updated yet as i didn't want to lose the ability to root.
Anyone know if you can still root with the updated firmware?
nutley said:
I bought a UK Samsung Tab S 8.4 the other day and it had this update. I haven't updated yet as i didn't want to lose the ability to root.
Anyone know if you can still root with the updated firmware?
Click to expand...
Click to collapse
I'm pretty sure you can. Although cfautoroot can fail. Just flash the new firmware with Odin, then flash twrp recovery and flash supersu. Zip with twrp. That guarantees root most times and that's how I do it on new firmware.
Logged into Kies and it told me I had the latest firmware.
I bought my tablet a few weeks ago on ebay, and this was the build number that my tablet had when I got it. Apparently my tablet was from the Canadian region originally and this update was pushed out to them first. The firmware for it has been floating around on a few sites as well.
I also rooted with cfautoroot on this firmware.

Offered software update to same version I'm already on

Something slightly odd happened just now - my Z3C popped up with a Xperia System Update telling me it was ready to install to 23.4.A.1.264 just now. This is slightly confusing as I'm already on that version and have been for some time (I flashed a pre-rooted rom via recovery weeks ago). I doubled checked to make sure my mind wasn't playing tricks on me and the phone reports it is definitely on 23.4.A.1264. The message came back after a reboot so I've just selected to postpone the update and set reminders to "never" but why is this happening?
Edit- meant to post this in Q&A - sorry, can a mod move it for me?
No idea. I've received the same update as well.
Same for me. Just got one a few hours ago.
I also got the notice. I have Xposed installed and have modified the kernel with dual recovery. Does everyone else have a similar setup? Maybe the OTA service has issues detecting the system version after some partitions have been modified.
I am fully stock and I got the same update. It did nothing but restart my phone.
At least it's not just me then. It's very persistent though, despite setting it to postpone forever it still keeps giving the message each day.
January Android bugfix, supposed to fully fix stagefright.
I haven't updated and I haven't seen the update recently. I guess Sony fixed it on their end.

No updates available, OTA or Kies?

I recently bought a factory unlocked N910T off eBay, and it is running Lollipop. Both the OTA update module and Kies say it has the most recent firmware. We all know that is not true! Any idea what's going on? Is there something fishy or wrong with this phone? All the T-Mobile stuff like wi-fi calling and visual voicemail work fine, and the S-Pen hovers and everything so I'm sure it's not counterfeit. I presume I can still flash a stock rom through Odin or something, but I'm really bothered that the proper channels aren't working. Thoughts?
PS: My old N910T (broke the screen) got the updates just fine.
Jake of All Trades said:
I recently bought a factory unlocked N910T off eBay, and it is running Lollipop. Both the OTA update module and Kies say it has the most recent firmware. We all know that is not true! Any idea what's going on? Is there something fishy or wrong with this phone? All the T-Mobile stuff like wi-fi calling and visual voicemail work fine, and the S-Pen hovers and everything so I'm sure it's not counterfeit. I presume I can still flash a stock rom through Odin or something, but I'm really bothered that the proper channels aren't working. Thoughts?
PS: My old N910T (broke the screen) got the updates just fine.
Click to expand...
Click to collapse
Hi, I face the same scenario you described, no updates available thru official channels.
Did you already tried flashing the latest firmware thru Odin?
UPDATE: Downloaded the latest firmware with SamFirm and installed it with ODIN. No issues, my phone now haves Marshmallow.

Marshmallow for the Vivo XL kind of sucks....

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)

Latest securty-firmware patch screws up battery

I did the update 2 or 3 weeks agao and my battery has very odd behavior.
I am not the only one. Found youtube video of same problem and folks on moto forums talking about this.
very frustrating. Anyone have ideas?
https://www.youtube.com/watch?v=I5NtLPK9m1c
I think I may try to go back and flash older android 9 Firmware for my XT1929-4. Is there a factory app/program to flash or do most people use RSD? thx
How strange, what could it be? it's not my case. even still, this improved my battery performance..more than 8 hours of active screen.
My version is XT1929-6
Thanks for the info. I'm on the one update before at PCWS29.85-36-10 Sprint Version. Looks like I'll be staying on this firmware, no issues anyway. Rooted with Magisk, so it's a pain to remove and update, the OTA won't work even after disabling Magisk anyway.

Categories

Resources