Database Info

Security storage app? Consumes 98% battery

I have the app android booster to monitor battery use. When I go to applications everything is at 1% and 2% but the android process "security storage" is consuming 98% battery? Does anyone know what this is? Is there a way to minimize it or can I freeze it with Titanium Backup?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

I wish I knew as it's killing my battery also, I'm thinking I'll have to reflash or even odin back to stock before I'll get rd of the battery drain caused by secure storage, I found out it's com.android.providers.security that started secure storage but not much else

I see nobody is addressing this issue, or even explaining it. Too bad, as I'm having the same issue. The annoying part is, no matter what kernel I run, the same thing happens: The phone will sit sedately idle until I want to use it, then the minute I try to do something "Security Storage" starts running and the phone becomes non-responsive for 30 seconds to a minute or two while that stupid app is running.
Why can't this app do its maintenance while the phone is idle, rather than the minute the user wants to do something, or be forced into "nice" mode (don't know if Android has such a setting, but it's based on linux and linux does have such a setting) so that it's only allowed to hog the CPU when the phone is idling.

change build prop ro.securestorage to false

ElwOOd_CbGp said:
change build prop ro.securestorage to false
Click to expand...
Click to collapse
I just registered to say THANK YOU to this man. :good:

did it work?
mikim1 said:
I just registered to say THANK YOU to this man. :good:
Click to expand...
Click to collapse
I've noticed a lot of system resources get wasted even after removing the knox apps and enterprise and container agent stuff that comes on samsung phones. I mean, I guess its good as an option to have if you have use for it. Problem is tho, for ppl like me, its also built into the system in order to make those implementations effective and when you install a custom ROM and or kernel it causes errors. I think thats why some people dont like touchwiz ROMs and think theyre laggy. When the kernel and system are not synced anymore, crap goes on in the background that is just a waste. I still dont know much really, but I spent some time trying to fugure out how to disable some loggers and errors that were going on and were pissing me off. Here is a link to a post I ran across that helped shed some light on some stuff. Be careful tho, and if you don't know what your doing, spend some time to learn about what all that stuff does, because it's system stuff and you could find yourself in a bootloop or with an expensive azz brick http://forum.xda-developers.com/showthread.php?t=2599266

ElwOOd_CbGp said:
change build prop ro.securestorage to false
Click to expand...
Click to collapse
interestingly using icyfusion rom and terrasilent kernel, I cannot find this line in my build.prop. anyone else not seeing it there? secure storage is eating up at least 20% constantly of battery/cpu accord to elixir2. My battery drain continues to plague the device and I can only get about 1-2 hours of light use out of it while it continues to drain when screen is off. All I want to do is use it to listen to some tunes and I'm regretting rooting the device now. Refreshing to stock, wiping everything...formatting etc. has no effect. Has anyone solved this problem (presumably related to secure storage?) with another method?
(yp-g1 us version, currently on GB 2.3.5 stock, rooted with terrasilent kernel).

klemmaniac said:
interestingly using icyfusion rom and terrasilent kernel, I cannot find this line in my build.prop..... currently on GB 2.3.5 stock, rooted with terrasilent kernel).
Click to expand...
Click to collapse
have you tried any current builds?

ElwOOd_CbGp said:
have you tried any current builds?
Click to expand...
Click to collapse
I tried CM11 which worked fine for a week or so and then all of the sudden the battery drain problem appeared. I didn't check the build.prop when on that because I decided to reflash to stock and start from scratch trying different roms/kernels. I can't shake the battery drain now no matter what I do - factory reset full wipe, you name it. I guess I could try installing cm11 again and see if it is in the build.prop then?? I just don't know how to proceed at this point.

My suggestion would be to go into developer options and take a look at process stats to see if there are any rogue processes running that you don't need. You can also download and install BetterBatteryStats app from here on XDA or purchase the paid version from the play store so that you can specifically pinpoint what is causing your device problems. Also, older devices often need batteries replaced because they wear out. I don't think the secure storage bug affects AOSP based ROMs since it is related to Samsung's Knox. Another tip would be to use a build prop editor app that has a search function to make finding things easier.

ElwOOd_CbGp said:
My suggestion would be to go into developer options and take a look at process stats to see if there are any rogue processes running that you don't need. You can also download and install BetterBatteryStats app from here on XDA or purchase the paid version from the play store so that you can specifically pinpoint what is causing your device problems. Also, older devices often need batteries replaced because they wear out. I don't think the secure storage bug affects AOSP based ROMs since it is related to Samsung's Knox. Another tip would be to use a build prop editor app that has a search function to make finding things easier.
Click to expand...
Click to collapse
thanks for the suggestions, but it's all similar to what I've already tried. I did use Elixir2 and another battery status app to monitor things, and I have also gone through running process and disabled everything that I don't need. I did order a new battery just to check, but I don't think that's the problem. The top part of the case (where the CPU is running I presume, not the battery) is getting very hot, so there is some problem with a program or service overheating the CPU which in turn drains the battery. I just charged to full today and turned the screen off so that the device will sleep. 2 hours later, it is dead. I checked battery stats in settings and there is no indication that the device wakes while screen is off...I'm just totally at a loss. It's almost like it's a hardware issue maybe caused by a kernel or something like that, rather than an app or service. I just have no idea. Someone in another forum advised me to flash to stock and run a logcat app and post results..so I guess I'll do that. I'm worried though, because I was googling prices for ipod touches earlier today....I don't want to go back to the dark side...but I just want a device that works and I can listen to music for more than 30 minutes too.

klemmaniac said:
thanks for the suggestions, but it's all similar to what I've already tried. I did use Elixir2 and another battery status app to monitor things, and I have also gone through running process and disabled everything that I don't need. I did order a new battery just to check, but I don't think that's the problem. The top part of the case (where the CPU is running I presume, not the battery) is getting very hot, so there is some problem with a program or service overheating the CPU which in turn drains the battery. I just charged to full today and turned the screen off so that the device will sleep. 2 hours later, it is dead. I checked battery stats in settings and there is no indication that the device wakes while screen is off...I'm just totally at a loss. It's almost like it's a hardware issue maybe caused by a kernel or something like that, rather than an app or service. I just have no idea. Someone in another forum advised me to flash to stock and run a logcat app and post results..so I guess I'll do that. I'm worried though, because I was googling prices for ipod touches earlier today....I don't want to go back to the dark side...but I just want a device that works and I can listen to music for more than 30 minutes too.
Click to expand...
Click to collapse
turn gps off

ElwOOd_CbGp said:
turn gps off
Click to expand...
Click to collapse
thanks, but that was one of the first things I turned off. I only want to use the device for music listening and quick browsing/email. I shut off wifi when not using and leave it in airplane mode as well....definitely something internally wrong with the device somewhere that goes beyong changing the usual battery draining settings. Still have the logcat running and the device is making very strange noises I've never heard before...popping, screeching scratchy sounds....very strange...things just seem to be getting worse and I'm worried I'm quickly heading to an expensive paper weight situation... Battery continues to drain at 20% or more/hour with screen off. I think after this if no progress is made,...I may try to unroot the device, but I don't know if that will solve the problem and will undo the damage already done.

[Q] Performance: k3g_wq, what is it?

My Charge has seen decreasing performance. I'm running 2.3.6, the last TBH leak, and I was initially getting Quadrant scores as high as the 1400's. Now, I'm down around 700! Needless to say, the phone has gotten laggy.
I'm using OSMonitor to look at what processes are busy, and I keep seeing k3g_wq running, using anywhere from 20% to just under 40%. Never used to see it before. I figure it's a system process, as if I kill it, it starts back right away and always has the PID of 54.
I've searched here and with Google and I can't find anything about what this process is. From the name, I might guess it has something to do with 3g access, but it's running like that even when I go into airplane mode.
Thanks for any info.

just a suggestion but since GB has officially been released i would wipe cashe,dalvik and data. Then flash infinity, tweak stock or danalo's stock debloated/deoxided rom. Then flash imoseyon's repacked voodoo kernel. you will get a quadrant score of around 2000. Im currently running infinity ext4 without tsm, imoseyon's kernel and v6 script. its been pretty good for me so far. i have no complaints.
But if anybody else has a better setup. I myself would like to know as well

Wow, that's quite a prescription! For now, I'd just like to know what that process is and why it's running, so I can try to get it to back down.
Thanks for the tips. BTW, I was running voodoo lagfix back in the day, and it got me quadrant scores similar to what I was getting with this GB ROM (not 2K, but 1600 wasn't unusual); I'd like to get back to that point. Without necessarily starting over.

You're basically going to have to. The TBH leak is really old.
Sent from my SCH-I510 using xda premium

The TBH leak isn't that old (I downloaded it on Nov 7th), and the age of it doesn't make kernel processes run away. It's GB 2.3.6, basically the same as the latest OTA. And it only started doing this recently.
I'm afraid either something I've installed recently is triggering this (the better option, as I can start uninstalling stuff until the problem goes away), or there is something gone wonky with the hardware itself that the kernel is reacting to (obviously the worst case). That wouldn't surprise me, as this is my 3rd Charge, the first two having had lost their minds, running really hot and then rebooting every few minutes (this on the stock OS, rooted with the voodoo lagfix kernel).
More data (if there's anyone out there who actually knows what that kernel process is): OS Monitor's "messages" list is flooded with this:
"k3g_work_func: fifo entries are less than we want"
I get dozens of these PER SECOND.
Again, if anyone has any insight on what that process is about, glad to hear from you. Those who say "Nuke and pave!", not so much.

Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
"Nuke and pave" still seems like the best option.
Sent from my SCH-I510 using xda premium

kvswim said:
Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
Click to expand...
Click to collapse
Fifo is a general term for a queue -- "first in/first out". Many kernel processes live their lives managing queues. This one is complaining about it's queue being shorter (fewer entries) than it thinks it should have.
Did I see your name attached to a thread about trying to compile a kernel? If so, would you do me a favor, so I don't have to get all into git so I can get to the AOSP code, and grep for "k3g" and/or "k3g_wq" (still sounds to me like like "kernel 3g worker queue") and see if you can see what it does? Nothing in depth, just in general what it handles.
kvswim said:
"Nuke and pave" still seems like the best option.
Click to expand...
Click to collapse
Funny thing happened today. It was getting worse and worse. Battery stats showed a shocking thing--for the first time ever, Display wasn't the biggest battery hog, it was Android OS!
So I decided to just reboot, to see if I could get it back to good enough to do backups and start the nuke-n-pave process. I had rebooted a few times over the last few days, and it didn't solve anything. Today it did! Back to normal, and I ran Quadrant twice and got a 16xx on the second run. Nice. A few hours later, and it's still good. Keeping my fingers crossed.
Oh, I had also uninstalled DropBox (which I wasn't using yet anyway) and this massive Gameloft game, "Tintin". Those didn't help, before reboot. But maybe those, coupled with the reboot, did.
I may still nuke and pave, but probably with the stock GB and just root after that. And keep hoping the CyanogenMod comes out with a ROM for it.
Thanks.

I'm gonna revive this thread because I have a similar problem. My dad's charge is fully stock. He has never messed with anything. It was fine the whole time he had it except today. He has not used it at all today (10m screen time in 12 hours, and half of that was me trying to fix it) and the battery drained down to 30% all by itself. Me being the tech guy, he gave it to me and I checked battery usage. Android OS was reported to be using 89%. Cell standby was at 3%, and display came in last at 2%.
Since "Android OS" is very generic, I used adb to put the xda version of betterbatterystats on his phone, and under process, there is this thing called "k3g_wq" with almost a full bar. Under other, it shows the phone being awake 98.2% of the time. This problem only arose today. As he has not used the phone at all, there would be no rogue apps unless something just turned up. I disabled automatic updates in the market since the stock tunewiki app updated its permissions to read SMS (spyware???).
Does anyone have a solution to this besides factory reset?

K3G is a sensor, specifically the level sensor. Not sure why it would take up system resources, but I would think turning off auto screen rotation may be one method to try and limit its use and battery drain.

See my posts on k3g_wq above. Note that I found error log message about it not having enough entries--thus my supposition that wq == worker queue. If imnuts says it's a level sensor, then that's got to be it; from the name, I figured k was for kernel and 3g was...well...3g.
In my case, I was able to see it using OS Monitor (free in the market), using consistently about 30% of the CPU, which resulted in the OS being the largest consumer of battery.
And, for me, it finally just stopped doing it, after one more reboot. Hasn't come back. But every time the phone gets a bit laggy, I go look at that process list.
On another note, we're using my Charge at work as a test phone for our Android app, as it makes it blow up like no other device we have.

I have noticed a sensor leak associated with google maps. Try opening maps in that phone, exit out of it and see if sensor usage persists. I hadn't mentioned it before assuming it was unique to my device.
Sent from my SCH-I510 using Tapatalk

I also notice runaway usage of k3g_wq in the last week. I have stock OTA EP4 and it had been running fine for many weeks with no issue. So there has to be something that changed recently. My guesses are the new version of Google Maps, or new version of Tiny Flashlight with the "shake on lockscreen" feature. I don't see Tiny Flashlight running any services, but since I disabled the shake on lockscreen feature my k3g_wq usage seems to be OK.

I factory reset the phone and the problem disappeared.
Sent from my pocket-sized, Linux-based computer using electromagnetic radiation.

Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.

Scrappy1 said:
Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?

xdadevnube said:
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?
Click to expand...
Click to collapse
If you're a geek and have time to flash and mod, that's great for you. I used to be in this camp. Now I just want my phone to work without contanstaintly modifying it, babysitting process and battery life. I want a phone I could recommended to ANY friend or parent without worrying. The Charge definately isn't it.
My brief history in Android:
Samsung Fascinate: got tired of poor battery life and runaway processes.
Samsung Charge: got tired of poor battery life and runaway processed. Also, voice quality is horrendous.
Samsung Galaxy Nexus: Tons of reviews of runaway "Android OS" proccessed during idle. Voice quality is bad and outbound audio drops.
With each generation, problems weren't fixed and Google/Samsung continue their careless ways. To me its just sloppy, sloppy, execution.

Scrappy1 said:
I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.

charlie_c said:
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.
Click to expand...
Click to collapse
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.

Scrappy1 said:
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
Click to expand...
Click to collapse
Sorry, thought you were OP
Sent from my SCH-I510 using Tapatalk

k3g_wq ... it came back, and then I killed it, I think
OP here.
Today I was looking at my Charge and marveling at how I was getting pretty good performance but better battery life due to my latest tweaks in SetCPU, when I looked at battery usage: Android OS was creeping up on Display as juice-user No. 1.
Uh oh.
So back to OS Monitor, and sure enough, there's k3g_wq on a steady 25-30% of the CPU.
Opened and closed Maps--no luck.
Killed its process in the process list in OS Monitor (it appeared to be swapped out, but what the heck)--no luck.
Opened another cool app called Elixir that shows you sensors, and lets you enable/disable them. Hrm...gyroscope, rotation and orientation sensors. All were off; turned each on, then back off.
Looked in OS Monitor and...YES! k3g_wq is gone!
Wild guess time, but apparently the start-up/shut-down of whichever sensor it is doesn't always work right, and leaves that service looking for its momma (that's a highly technical description of the problem, sniff).
Anyway, if you're seeing k3g_wq running wild, give that a try. Next time I do, I'll try them one at a time, see which one does the trick (assuming it's only one).
LDog
PS -- Kudos again to imnuts for letting us know it's the level sensor. Or sensors.

Horrible Battery Life

Hello All,
I have (2) N5's (one white, one black). I've noticed that battery life on the black one is extremely bad. I'm almost always near a charger, so it was quite a shock when I noticed the black one down to 37% by noon. The next day I swapped phones and never saw the charge on the white one drop below 97%. I wiped both phones and configured each identically and was able to duplicate very similar results over the next few days. This morning I decided to see what happened when I did not connect to a charger. My use has been almost nothing (5 mins of screen time, 3 hrs off battery), yet my phone is already at 81%. I notice "Android OS" is using approx 50% of the battery. I do have a few apps that run in the background and I also leave GPS, BT, mobile and wifi on all of the time, however this is no different than how I used the white one or any previous phones. I suspect this is a hardware problem, however I would like to try to pinpoint the cause to satisfy my own curiosity. Can anyone recommend specific apps/tools that would provide more detailed information about what is going on with the different subsystems (battery, cpu, radios, storage, etc) that could help me find the problem? Thank you.

Do some searching and reading.

It's your apps. Not a hardware problem.
Sent from my Nexus 7 using Tapatalk

Do a complete factory restore on both, with full charge, Then don't touch them at all, the post results
Sent from my Nexus 5 using XDA Premium 4 mobile app

You have a wakelock obviously. My Android OS does the same thing, but it doesnt destroy the battery that bad. My wakelock is wlan_rx_wake, and its very annoying to get rid of. Still havent found a way to kill it yet.

I've noticed if you turn the location settings to "Device only" the Nexus 5 sips battery, while the screen is off, because it isn't always waking itself 1,000+ times a day to report your location.

caribouxda said:
Do some searching and reading.
Click to expand...
Click to collapse
Pretty sure that's what I'm doing?
It's your apps. Not a hardware problem.
Click to expand...
Click to collapse
I initially thought the same thing; however, I did not install any apps after wiping the phone, yet the problem remains. Also, I do not have this problem on my other N5 with all of my normal apps installed and configured for normal use.
Do a complete factory restore on both, with full charge, Then don't touch them at all, the post results
Click to expand...
Click to collapse
I did this... mostly. After wiping both phones (by reflashing the factory image) I did charge both to 100% before using them. Unfortunately, I am on-call 24/7 and have to use one phone at all times. I did keep usage as identical as possible. I did this by not installing any apps and charging at the same times for the same amount of time. Also, my commute and time at work/home/elsewhere was almost identical. Of course there are some things that are out of my control (call, sms, emails, etc received), however it was certainly not enough to account for the difference I am seeing. If I take the phones off the charger at 7A, and use as little as possible, the white one will be >90% where the black one with be <40% by noon.
You have a wakelock obviously. My Android OS does the same thing, but it doesnt destroy the battery that bad. My wakelock is wlan_rx_wake, and its very annoying to get rid of. Still havent found a way to kill it yet.
Click to expand...
Click to collapse
This very well may be. How did you find out that your wakelock is wlan_rx_wake? This is what I'm really seeking - app recommendations or other ways to acquire this in-depth information. I've done some googling, but many of the apps that I've seen recommended do not work with KitKat. What I find most odd is how the white N5 with a 100% identical configuration does not have this problem.
I've noticed if you turn the location settings to "Device only" the Nexus 5 sips battery, while the screen is off, because it isn't always waking itself 1,000+ times a day to report your location.
Click to expand...
Click to collapse
Thank you. I suspect this would make a difference, however I am basing my expected usage on what I get with the white N5 with the same configuration. I did not change any settings on either and would like to see them similar with the same configuration. Once the issue is worked out, I will definitely take your advice and change this setting to increase my battery life.
Thank you all.

Did you download the firmware from Google then flash it in bootloader? Also you need to flash both phones to stock, Then not install any apps or settings on both so there both the same. That's a fair test.
If you can't do this, Then this thread is pointless as far as I'm concerned.
Sent from my Nexus 5 using XDA Premium 4 mobile app

markdexter said:
Did you download the firmware from Google then flash it in bootloader? Also you need to flash both phones to stock, Then not install any apps or settings on both so there both the same. That's a fair test.
Click to expand...
Click to collapse
Yes, I downloaded and flashed the stock image from Google. I run stock on all of my Nexus devices. I did not install any apps, however I had to setup E-Mail and modify my APN settings.
If you can't do this, Then this thread is pointless as far as I'm concerned.
Click to expand...
Click to collapse
Why the attitude? You're clearly a helpful person, based on the time you spend helping others on here. If you're having a bad day or dealing with some personal issues, I sincerely hope things get better for you. If you really have a problem with my test constraints, then please move along. As a UNIX Administrator for the past 15 years, and a component-level electronics tech for 5 years before that, I can tell you from experience that the real world simply does not always provide for ideal conditions. While I agree that a 100% identical setup is preferred as a control, it's simply not an option. Even with my constraints, there is no way the number of emails and texts that I sent/received on a given day are the cause here. All that said, the point of this thread was to gain insight into how I can find more detailed information about what is going on with the various subsystems - either app recommendations or other tools. Much of the information I've found has been high-level - Settings > Battery or BetterBatteryStats (which doesn't work with KitKat AFAIK).
Thank you.

Without the 100% identical test, it's a guessing game.
I don't have an attitude, if I did, I would have told you my credentials, but I didn't think that had anything to do with this thread...
I'm not being a smart-ass buddy, and I do like to help on here as much as possible or as much as my knowledge can allow me.
Better battery stats, is for sure your best bet, that app is a must have for trouble shooting. I'm sure within a few days, there will be a update.
Sent from my Nexus 5 using XDA Premium 4 mobile app

[RANT] - Lollipop is not great, but tolerable

I was very excited to see this:
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
So, I pushed ahead thinking that Lollipop has already been in the wild long enough, surely the initial kinks like WiFi drops and battery hogging have been resolved. No such luck, and after doing it, it looks like I'm going to have to do this:
http://forum.xda-developers.com/showthread.php?t=2784880
Lollipop is horrible. My phone no longer does one of the most basic things that's been around since the G1: Go (the F) to sleep! Seriously?!?!
Here are my other problems:
-Phone doesn't sleep on its own if timeout set for longer than 30 seconds (and even then, it's not reliable)
-WiFi doesn't reconnect after sleep (when sleep even happens, which is only when I push the button to force it). I have to toggle WiFi off/on to reconnect.
-Battery drain is pretty bad. My first month with the S5 had me barely even thinking about charging. Now, with Lollipop, I feel like I'm back on my old HTC MyTouch!
-The silly way they implemented the lockscreen. Here's my problem: I can ONLY use Settings > Sound and Notification > While locked with the option "Do not show notifications". Why? Any other setting blocks the Owner Information (Settings > Lock screen > Owner Information). If I don't, and if I'm unfortunate enough to have lost my phone, yet fortunate enough to have it found by a good samaritan, I better hope I haven't miss any calls or received any messages in the meantime. This one REALLY GRINDS MY GEARS because it's a horribly-implemented Feature ... at least the others are unintended bugs, but somebody had to give this one the green light.
-I can't adjust the icon sizes anymore. There used to be a choice of large or small icons.
-Oh, and for some bonehead reason, Samsung decided their stock ROM wouldn't have the Lollipop built-in flashlight icon.
-Another intentional feature that I can't disable: the phone keeps a history of recent activity that persists through reboots. YUCK! Why can I not disable this?!?! Again, another bonehead call that somebody had to green-light, without even considering the possibility that I might want to turn it off!
-All the UI "polishing" and improvements don't mean a thing to me, I want it to work.
I found all of the above in less than 24 hours on Lollipop! I might lose my s**t entirely if I keep it for much longer.
Here is my take on why:
Google and Apple are in a heated race to the top. They wrongly assume that what will set each apart from one another is almost entirely dependent on what a few bloggers say about some hot new feature. The paradigm appears to be something like: "Who cares if millions of loyal subscribers lose functionality when we want 100 people to have this one obscure and half-baked feature?"
Latest != Greatest
-----
EDIT:
I've had a change of heart on this. It's not too bad, I just needed to adjust a few settings and live with the other issues.

I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app

Tldnr
Don't start a thread just to complain

Lmfao when I saw that link and clicked it, I actually had that same thread opened moments before opening this thread because I, too, am having to go back to KitKat. I laughed for a good 20 seconds. Lollipop is freaking terrible at the moment. Zero customization and Google + Samsung are forcing too much garbage on us without giving any bit of customization.

mygraine said:
I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Heart rate monitor thing was fixed in OC4 I think, but if it still goes off a factory reset will fix it.

Agree
OP, I agree with you. It probably is the first version without the definitely improvement overall for users. It is risky to upgrade and troublesome if it didn't work out well on your devices. Wish Android 5.1 could be better than Kitkat overall.

I have absolutely no problems with the lollipop. I always had it stock from the start and just let the OTAs take over on their own. Have you tried even rebooting into recovery and wipe cache? Even though it's not a custom recovery you can still do that, also even when you dirty flash nightlies that's something that's good practice. My wife's phone had similar issues that I wasn't experiencing, until I did that to her phone and now she's having no problems. Now the general annoyances of how Samsung implemented ****, I understand, it's stupid with not having native flashlight, tethering is annoying having to use foxfi, and the lockscreen.. bleh. But other than that, everything is actually working like it is supposed to

Chiming in, Yes it's bad.
I have two lines with Verizon, both with S5 phones on them. Great device, its actually the first Android phone I've had that I did not do anything with beyond the out of the box experience. That changed when Lollipop was pushed via OTA, the most prominent issue I experienced on both of my S5s is general responsiveness issues, simple things like switching apps or launching apps sometimes would leave me with a white screen for between 5-10 seconds, an eternity especially when the device was lighting fast on 4.4.4 Kitkat. I followed every suggestion from wiping the device in Android, Wiping in recovery, wiping cache, all of these with only marginal improvements. It really is a shame that Google / Samsung did not do a bit better quality assurance on this build before it was pushed out to carriers and ultimately peoples devices. It says something that other carriers skipped 5.0 and that very rapidly 5.1 surfaced on Newer devices / Nexus devices.
As of last night both of my phones are Odin'd back to 4.4.4 and its like having a brand new phone. Sure, there might not be as much polish, but there are no features I will die without having. The only one that I can say I do miss is the feature where the device will disable the lock screen when your smart watch or home WiFi is connected.
Here's to hoping that Google eventually gets Android 5 right in the optimization department and that Samsung picks it up for the S5, and that Verizon gets it ready for OTA before I am ready to move on to a new device. Not interested in the S6 at all for its sealed nature for storage and battery, but that's for another thread on a different day.
-Nate

I Have to agree. I've given it several chances to perform to expectations but it just fails.... ( insert sad puppy face here ) no matter what I have tried it just under-performs and the biggest thing is the horrible battery life. Sooooo yeah like most of the other commentators in this thread, I'm moving back to 4.4.4......

Unfortunately/fortunately, I have found most of my battery issues were solved with a factory reset. I'm more frustrated that Samsung seems to having issues with Android Auto.

ldeveraux said:
Tldnr
Don't start a thread just to complain
Click to expand...
Click to collapse
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.

CaptainRewind said:
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...

ldeveraux said:
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...
Click to expand...
Click to collapse
Yeah, I guess that was wishful thinking.
In any case, it seems this thread was a complete waste of time. It made me feel better at the time, but looking back on it and the purpose of this site, it doesn't add any value or help anyone modify their phone. Not only that, one of my primary reasons for the OP was the screen lock issues which turned out to be an app, not the Android version.
So, I stand corrected. Live and learn. Enough said.

My wife would never let me root her phone ever. After this update either I find a way to go back a few with root or it goes against the wall. Looks like I have to start reading and figure out how to do this.

Lol I love how you described it. Sometimes you have to vent. Lol

CaptainRewind said:
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Care to share where this app is?
Sent from my SM-G900V using XDA Free mobile app

dk-v1 said:
Care to share where this app is?
Click to expand...
Click to collapse
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.

CaptainRewind said:
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.
Click to expand...
Click to collapse
Ok, so it's not a stock app. I am still having poor battery life and overheating issues.
Sent from my SM-G900V using XDA Free mobile app

Phone is painfully slow, trying to troubleshoot

So I've had a T-Mo S7 for about a year and a half now. It's incredibly slow/unresponsive and I've spent a really long time troubleshooting.
I've done full factory resets, and direct ODIN OS installs with data wipes. Whenever I do this, the phone starts out, with all current apps installed, extremely fast/responsive. I have a somewhat limited app library, and I haven't added anything since the phone slowed down noticeably.
About two months ago, the Samsung Device Maintenance app, which until then only reported battery draining, said "Some apps or processes are overloading the system (CPU)" and the app it reported was something like com.android/google.searchbar" which I assume is the google search bar widget. I thought, "awesome, the device app is actually doing something." I told it to kill the app and my phone sprung to life. My phone was super fast for a long time, but is now back to being super slow again. I searched "Apps" in device settings and can't find any apps/processes that sound anything like search bar. Also, how is there not a system resource monitor in system settings!? Clearly, an app is hogging resources, because I've experienced periods of responsiveness. Is there no direct way to figure this out without doing the safe mode process of elimination?
Can someone help shed some light or suggest further troubleshooting steps? Thanks in advance.

I got mine on black friday 2 years ago and I've been having the same issue. Of course my battery doesn't last very long being it's over 2 years old. I'm guessing it may have some.thing to do with the battery voltage being so weak after so long. I'm due for an upgrade obviously but I'd be fine using my S7 for another year if a battery replacement did the trick. I believe I was told in chat that I could go into the store and they'd only charge me $5 but I assume they'd have to send the phone out unless they just swap it out for a refurbished one. I've had no other problems with mine at all so not really the route I want to take.
Anyone else familiar with this process? Has anyone else had their battery replaced or phone swapped and notice if the fresher battery helps or is it just a symptom of it "can't" handle the newer OS properly? Any feedback would be appreciated. Hopefully it helps us both out. Didn't mean to hijack the thread!

tony yayo said:
I got mine on black friday 2 years ago and I've been having the same issue. Of course my battery doesn't last very long being it's over 2 years old. I'm guessing it may have some.thing to do with the battery voltage being so weak after so long. I'm due for an upgrade obviously but I'd be fine using my S7 for another year if a battery replacement did the trick. I believe I was told in chat that I could go into the store and they'd only charge me $5 but I assume they'd have to send the phone out unless they just swap it out for a refurbished one. I've had no other problems with mine at all so not really the route I want to take.
Anyone else familiar with this process? Has anyone else had their battery replaced or phone swapped and notice if the fresher battery helps or is it just a symptom of it "can't" handle the newer OS properly? Any feedback would be appreciated. Hopefully it helps us both out. Didn't mean to hijack the thread!
Click to expand...
Click to collapse
So I promise it's not the battery because I had it factory replaced by Samsung. To answer your question, yeah you have to send it in. With the waterproofing they have to do it at a repair center. However, for me it was 100% worth it. I think I was without the phone for about 10 days. But having a brand new battery life was incredible.
Also, as I was working with the phone slow for a while, it immediately and dramatically became quick after device maintenance killed that process. But a few months later, I'm back to suuuuper slow.

The S7 is getting old. Old things slow down. It's planned obsolescence. I've gotten to the point of turning notifications off for all apps and only using badge numbers to tell me when to check something. I also use do not disturb a lot when gaming instead of game tools because game tools is another app but do not disturb is more of an internal process. As soon as my taxes come back I'm probably going to get a S8+