Related
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.
Allright, i've owned my Sensation for several weeks now. Today, i sent a text, and as soon as i went back to the home menu, the phone turned itself off, and rebooted. It was a pi**-off, for sure, and now im worried.
I've done some research, and apparently (correct me if im wrong) it's because of too much RAM usage. However, i set the phone to notify me when free RAM is less than 50MB, and it never did. It just pulled an auto-reboot on me.
Should i worry about this? Is it normal; basically 100% guaranteed that it is because of low RAM?
Which leads me to this: I ALWAYS questioned all the things i had running at the same time. That's probably the only thing i don't like about the phone. Things start automatically. I have an EQ program, Groove IP, and the Music Player running at the same time. I don't understand why the phone won't just close apps if they aren't in use... Or at least if there was a more streamlined way of closing apps. Not going into Settings,Apps,Manage Apps, Running... That's pretty stupid, if you ask me... If there are alternate/better methods, i'd like to know them.
Back to the point, though. Should i worry about this reboot? And, what exactly is the cause/is it RAM usage?
Do not worry unless it becomes a persistant problem.
And even then do not worry because it can probably be fixed as long as its a software issue and not a hardware problem.
And free ram isnt a big deal with android. If you use it, you will use up all your ram quickly. But android will kick things not in active use out of ram when apps in use need more ram. Having free ram is actually a waste.
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Oh, ok...If it's a one-time thing, then i won't worry about it. However, i'd still like to know the cause of it.
Why does this happen?
Did your phone feel warm or hot when it switched off?
Okay, this thing about RAM is one of the biggest misconceptions I think a lot of people have regarding Android. Android doesn't use RAM like Windows. On Android, RAM usage is a good thing. It means that when you want to reload an application, it does it quickly. In other words, RAM unused is just RAM wasted on Android. And the other thing is, apps running in the background do not consume resources unless they also have background processes running as well. The other thing is that Android will automatically kill off certain processes when your RAM is low. So yea. You don't have to worry about RAM.
If you're worried about the crap that comes preinstalled with the phone, you might want to consider rooting and removing all those apps though.
Prenihility said:
Oh, ok...If it's a one-time thing, then i won't worry about it. However, i'd still like to know the cause of it.
Why does this happen?
Click to expand...
Click to collapse
Are you using an app killer to monitor your free ram?
That could easily be the cause. Sometimes those app killers will kill the wrong things and force a reboot.
You're better off dumping apps killers altogether. They work counter productively to the way Linux operates.
Yeah, i kill processes/apps in the settings menu, don't use any downloaded/third party apps for that purpose.
I guess i'll stop doing that...
HOWEVER, i still don't like how, for example, once i sign into Groove IP for the first time, it will stay signed in. Every consecutive time i go to use the phone again, it signs in automatically... After it wakes up from sleep mode, it will sign into Groove IP, and load things like the EQ program i use. I won't worry too much about the EQ, but other apps like Groove IP that are connected to some sort of signal, i don't want automatically running... Is it really not safe to just terminate a process in task manager?
Finally, on to the subject of reboots...Since owning the phone for...I don't know...A few weeks now? I've only actually turned it off/rebooted once...
Did that contribute to the random reboot? Was that not a good move, on my part, to pretty much always keep the phone on (although in sleep mode when not in use, of course...) ?
Prenihility said:
Finally, on to the subject of reboots...Since owning the phone for...I don't know...A few weeks now? I've only actually turned it off/rebooted once...
Did that contribute to the random reboot? Was that not a good move, on my part, to pretty much always keep the phone on (although in sleep mode when not in use, of course...) ?
Click to expand...
Click to collapse
Yeah it could have. Try reboot the day every week at the bare minimum. Ideally, I'd suggest rebooting every 4 days or so.
Prenihility said:
Yeah, i kill processes/apps in the settings menu, don't use any downloaded/third party apps for that purpose.
I guess i'll stop doing that...
HOWEVER, i still don't like how, for example, once i sign into Groove IP for the first time, it will stay signed in. Every consecutive time i go to use the phone again, it signs in automatically... After it wakes up from sleep mode, it will sign into Groove IP, and load things like the EQ program i use. I won't worry too much about the EQ, but other apps like Groove IP that are connected to some sort of signal, i don't want automatically running... Is it really not safe to just terminate a process in task manager?
Click to expand...
Click to collapse
If you are manually killing an app that's causing problems / pissing you off / or because you just don't like it's face, then no. That's okay. It's the automated app killers that kill everything as soon as you close them and then keep killing and killing like battle droids gone berserk that you want to avoid. It's that constant killing, which means an app restart and power usage, that will drain battery. And being unmonitored they can kill the wrong things that cause system instability.
But if you have 1 app that's bothering you you can kill it through the apps menu. That's normal.
The bigger problem is an app that constantly turns itself on like that. I hate those. There should be an option in the app settings to prevent that from happening. If there isn't, it's a bad app no matter how well it does what it's supposed to do.
You can use gemini app manager to change autorun settings for each app individually and autokiller memory optimizer to change the preset android memory limits so your phone automatically closes apps itself a little bit sooner.
Both are free apps but require root.
Gemini is really good. Certain apps start just because you received a text or plugged your usb in. Or your signal changed. I put a stop to that straight away!! Just don't change the settings for system apps.
sent from my Sensation XE
Happened again... Alright, im being irritated by this restarting problem... My phone was just idle, i haven't touched it for hours. It was next to me on my desk, and i heard/felt the vibration upon restart.
Should i call my service provider for a replacement? This is ridiculous... I didn't get this thing expecting it to restart on me.
Prenihility said:
Happened again... Alright, im being irritated by this restarting problem... My phone was just idle, i haven't touched it for hours. It was next to me on my desk, and i heard/felt the vibration upon restart.
Should i call my service provider for a replacement? This is ridiculous... I didn't get this thing expecting it to restart on me.
Click to expand...
Click to collapse
They are going to make you go through a lot of TS steps that you can do prior to calling them.
Have you downloaded any apps recently, say just before you had the problem the first time. It could be the fault of a buggy app, (Usually not likely, but is possible). Are you rooted or fully stock?
As for the Groove ID - look in settings, there may be a way to stop the auto sign in. Just an idea, I don't use it.
I'm not having anymore problems with Groove IP auto sign in. The "lite" version of the app doesn't have the option to disable it, anyway. I just don't run it, unless i need to use it.
This is the second or third time it's restarted. I believe it's the second time, since the 23rd of April, when i created this thread.
As far as rooted or not rooted, i'm not sure what that means. I think it's in regards to the SD card. No, i haven't messed around with it. It's stock. Other than adding some music to the phone. Nothing has been messed around with.
I'm really annoyed by the fact that this happened AGAIN during idle/sleep mode. I wasn't even using the phone. It was just sitting there. It's quite irritating.
Anyhow. What are all the possibilities of the reboots? I'm starting to think it's not lack of memory. Supposedly the RAM-related issue is Sense restarting because of lack of RAM.
The phone vibrates, and the HTC logo comes up, and finally comes to the Home screen.
The only good news, really, in the end, is that it's only happened a couple of times in such a long span of time... I seriously hope i get this figured out, and it never happens again. Or else i'm getting a replacement, for piece of mind, and as a solution.
Prenihility said:
I'm not having anymore problems with Groove IP auto sign in. The "lite" version of the app doesn't have the option to disable it, anyway. I just don't run it, unless i need to use it.
This is the second or third time it's restarted. I believe it's the second time, since the 23rd of April, when i created this thread.
As far as rooted or not rooted, i'm not sure what that means. I think it's in regards to the SD card. No, i haven't messed around with it. It's stock. Other than adding some music to the phone. Nothing has been messed around with.
I'm really annoyed by the fact that this happened AGAIN during idle/sleep mode. I wasn't even using the phone. It was just sitting there. It's quite irritating.
Anyhow. What are all the possibilities of the reboots? I'm starting to think it's not lack of memory. Supposedly the RAM-related issue is Sense restarting because of lack of RAM.
The phone vibrates, and the HTC logo comes up, and finally comes to the Home screen.
The only good news, really, in the end, is that it's only happened a couple of times in such a long span of time... I seriously hope i get this figured out, and it never happens again. Or else i'm getting a replacement, for piece of mind, and as a solution.
Click to expand...
Click to collapse
Referring back to my previous question, did you install any apps prior to the first reboot?
l2icky said:
Referring back to my previous question, did you install any apps prior to the first reboot?
Click to expand...
Click to collapse
Oops. Forgot, sorry... Uuuummmm... Either the Equalizer App, or Groove IP. The only ones i've downloaded. Although im leaning more towards Groove IP (doesn't start up anymore though; because i don't want it to. Never launched it).
Regardless, are you saying i should uninstall it?
Also, one thing i want to add, that i find a bit strange. If i restart the phone, the display brightness will be noticeably brighter than what i actually set it to. It's almost as if i have to remind the phone of the brightness level i set in display options. All i have to do is go to the brightness setting, and touch the slider.
Is this normal behaviour? For it to be brighter upon startup? (even when reaching the home screen/whilst the main UI, past HTC logo screen)
Prenihility said:
Oops. Forgot, sorry... Uuuummmm... Either the Equalizer App, or Groove IP. The only ones i've downloaded. Although im leaning more towards Groove IP (doesn't start up anymore though; because i don't want it to. Never launched it).
Regardless, are you saying i should uninstall it?
Also, one thing i want to add, that i find a bit strange. If i restart the phone, the display brightness will be noticeably brighter than what i actually set it to. It's almost as if i have to remind the phone of the brightness level i set in display options. All i have to do is go to the brightness setting, and touch the slider.
Is this normal behaviour? For it to be brighter upon startup? (even when reaching the home screen/whilst the main UI, past HTC logo screen)
Click to expand...
Click to collapse
It's a possibility that the app is causing the problem, though it is a small one. You might uninstall it and try it for a while, see if the device continues to reboot.
As far as your quirky brightness issue... It's technology. No two devices are the same, even if they have the "same" hardware/software. That almost seems like a fluke happenstance. Just a minor bug in your software.
You might want to read into S-Offing your phone and rooting it. Do some research into it. There are a lot of perks of rooting your device and going with custom ROMs. And if you ever have issues and have to get a replacement, as long as you can turn the device on and it's functional, you can always set it back to S-On with no root.
I've learned over the years, and this is just my personal opinion, stock ROMs are more likely and it seems as if they are meant to have more problems, however it's like anything else in the tech world, it's bound to deteriorate over time. It's how they keep you buying their product.
There are some really good guides that lead through the process step for step if you decide to S-off and root. And there are a lot of helpful people on XDA that will answer any of your questions.
l2icky said:
It's a possibility that the app is causing the problem, though it is a small one. You might uninstall it and try it for a while, see if the device continues to reboot.
As far as your quirky brightness issue... It's technology. No two devices are the same, even if they have the "same" hardware/software. That almost seems like a fluke happenstance. Just a minor bug in your software.
You might want to read into S-Offing your phone and rooting it. Do some research into it. There are a lot of perks of rooting your device and going with custom ROMs. And if you ever have issues and have to get a replacement, as long as you can turn the device on and it's functional, you can always set it back to S-On with no root.
I've learned over the years, and this is just my personal opinion, stock ROMs are more likely and it seems as if they are meant to have more problems, however it's like anything else in the tech world, it's bound to deteriorate over time. It's how they keep you buying their product.
There are some really good guides that lead through the process step for step if you decide to S-off and root. And there are a lot of helpful people on XDA that will answer any of your questions.
Click to expand...
Click to collapse
Allright. Went to grab my phone just now, and saw the error notification. The old "abnormal reset" notification.
I'm going to assume it reset on its own once again. So....
Any insight into this? Why's is reseting itself? Hasn't happened in a while... but... still.
It was just sitting there, idling.
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
Well, this is not why I bought this phone for. SOT is only 25 minutes, and it is worse than my Xperia Z Ultra.
zllovesuki said:
Well, this is not why I bought this phone for. SOT is only 25 minutes, and it is worse than my Xperia Z Ultra.
Click to expand...
Click to collapse
I dont get it.....???????
Sent From Droid Ultra
caseyk621 said:
i dont get it.....???????
Sent from droid ultra
Click to expand...
Click to collapse
battery sucks for some reasons, solutions please?
zllovesuki said:
battery sucks for some reasons, solutions please?
Click to expand...
Click to collapse
Assuming you started from %100?
I found after some app updates that my play services cache was rather high and I had some unnusual battery drain. So I went to manage apps and cleared the cache on play services. Seemed to correct itself after that.
If you just got it then cycle it a couple times, it gets better after a week or so.
If you've had it awhile then a rogue app is causing it. BetterBatteryStats or gsam from play store will do better at helping figure it out.
5hrs 36mins SOT
Sent from my XT1080
KitKat and Jelly Bean have both had battery drains related to location services. I'm keeping location turned off until the next release. I'm not happy about it, but it does seem to make a difference.
cpurick said:
KitKat and Jelly Bean have both had battery drains related to location services. I'm keeping location turned off until the next release. I'm not happy about it, but it does seem to make a difference.
Click to expand...
Click to collapse
I don't have an issue with location services unless I have google now enabled then it is a battery hog.
I had a massive battery drain because of WiFi even when off. Go to WiFi settings advanced turn off scanning always on.
you need to use better battery stats. just research xda for it. and follow the posts directions. you will find out what exactly is eating your battery.
zllovesuki said:
Well, this is not why I bought this phone for. SOT is only 25 minutes, and it is worse than my Xperia Z Ultra.
Click to expand...
Click to collapse
Battery drain has been a relatively common experience after the KitKat 4.4 update. I have a Droid Mini, not a Maxx, but I've been seeing a lot of reports for all three of last years Droid line (Mini, Ultra and Maxx). Troubleshooting battery life is typically done through looking at events called wakelocks. Wakelocks are created by apps on your phone to prevent it from going into "deep sleep"--basically, they allow the CPU to stay on when the screen on your phone seems off. BetterBatteryStats or WakelockDetector are two apps that can be used to gain a little more insight into what wakelocks you are experiencing and what might be causing them.
However, wakelocks are broken down into two categories--those run by the Android kernel itself (kernal wakelocks) and those created by apps running in the background (partial wakelocks). Unfortunately, the 4.4 update made it impossible to view the partial wakelocks directly without root permissions. If you did as I did and naively updated to 4.4 without root, you won't be able to root your phone (as of now) to see the partial wakelocks. Instead, the wakelocks will show up under the kernal wakelocks that can be viewed--but instead of an app by app breakdown, they are visible only in the aggregate, so figuring out which app in particular is causing your problem can be a real trick.
One way to do so is to look at the apps running in the background of under the "Apps">"Running" in settings and see which apps you have actually been using and are supposed to appear and which apps are not. Then select the apps that you didn't start and force close them in sequence, checking Wakelock Detector or BetterBatteryStats after each to see if they have fixed your issue at all. The best way IMHO to see if they had an immediate effect is to look for increases in the "Deep Sleep" stat--if the app had been keeping your phone awake, and you force closed it, the Deep Sleep time should go up after you shut off your phone.
All that being said, troubleshooting is a real *****. There is an abundance of non-app-related issues with 4.4, or so it would appear. I have seen posts attributing fixes to turning location services to "GPS only". Others recommend clearing the Google Play Services cache in the Apps menu, clearing the cache in phone more generally, and using every other more conventional battery conservation trick in the book. Still others reported the only fix as a factor reset. These things had little to no benefit to me--although I never had to resort to a factory reset since I found a fix this morning. For me, all it took was going into Wifi>Advanced>Wi-Fi frequency band and changing from "Auto" to the 2.4GHz setting. This seems to have nailed the persistent wakelock issue that had been showing up as "Android OS" under the stock battery life in the settings, which showed up as a kernel wakelock under "suspend_backoff" in BetterBatteryStats. Hope that something out of all of this can help you--I'm immensely frustrated with how poorly my phone performed for the last month after the KitKat upgrade. It appears, however, that the fix I just found has restored my battery life from the 3-6 hours I have been getting lately to 12-14 hours. I'll update in a couple days after I see how things go. Best of luck!
Update, after a real short period of time:
Somehow doing this appears to have broken my Touchless Control. I can't get Google to recognize the "Ok, Google Now" bit, which it had done in the past nearly flawlessly, nor will Google Search transcribe voice searches, period. Going into the Settings>Touchless Control shows Touchless Control to be unchecked, but tapping the button to enable Touchless Control doesn't do anything. The button dims slightly, as if the press is registered, but the box doesn't check and the Voice Search and continues not to work. Interestingly, putting the Wifi back on "Auto" as opposed to 2.4GHz doesn't seem to fix this; rebooting into Safe Mode makes it work fine though. I've tried uninstalling and reinstalling my Touchless Control app, but I'm hoping this isn't a persistent issue for me. Ugh. In any case, I'll take battery life over Touchless Control for the time being.
EDIT: Voice input doesn't work anywhere on my phone--I can't press the microphone button on the keyboard and speak, for example, to dictate a text message. Potentially this is unrelated to the battery life issue, but I'm going to do some more digging and see what I can find.
Jumnhy said:
Update, after a real short period of time:
Somehow doing this appears to have broken my Touchless Control. I can't get Google to recognize the "Ok, Google Now" bit, which it had done in the past nearly flawlessly, nor will Google Search transcribe voice searches, period. Going into the Settings>Touchless Control shows Touchless Control to be unchecked, but tapping the button to enable Touchless Control doesn't do anything. The button dims slightly, as if the press is registered, but the box doesn't check and the Voice Search and continues not to work. Interestingly, putting the Wifi back on "Auto" as opposed to 2.4GHz doesn't seem to fix this; rebooting into Safe Mode makes it work fine though. I've tried uninstalling and reinstalling my Touchless Control app, but I'm hoping this isn't a persistent issue for me. Ugh. In any case, I'll take battery life over Touchless Control for the time being.
EDIT: Voice input doesn't work anywhere on my phone--I can't press the microphone button on the keyboard and speak, for example, to dictate a text message. Potentially this is unrelated to the battery life issue, but I'm going to do some more digging and see what I can find.
Click to expand...
Click to collapse
What do you have checked under settings, language and input?
Do you have any third party keyboards installed?
Have you done or considered doing a factory data reset?
Sent from my Nexus 7 using Tapatalk
jfriend33 said:
What do you have checked under settings, language and input?
Do you have any third party keyboards installed?
Have you done or considered doing a factory data reset?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No third party keyboards whatsoever. Up until now I had been really happy with Google's stock keyboard. Under Settings>Language and Input I have Google (English) checked, as well as Google Pinyin Input, and Google voice typing, which is set to English (US).
Been thinking about doing a factory data reset but would like to avoid it if possible because I've been horribly disorganized about curating my contacts across a variety of Google accounts--I know that if I had to, I have all my information backed up, but it'd be a big pain getting it sorted again afterward. I've heard others say that an FDR has fixed the battery all on its own. I don't know if I mentioned, but booting into safe mode restores the voice input functionality.
Got a Droid Mini now myself for a few days, it's at 4.4 and obviously unrooted and there apparently is no hope for the Chinese unlock nowadays either, sadly, so that means doing whatever possible to ensure the best battery life on mine as well. I hadn't considered forcing the 2.4 GHz Wi-Fi operation so I set it that way just now and then immediately attempted to use touchless control and it's working fine for mine with only that one change from Auto to 2.4 made.
I was using GSam Battery Monitor to get some idea of what's going on with this device but recently decided to just give the Snapdragon BatteryGuru a shot and see what happens (got another 1.5 days of monitoring before it does whatever it's supposed to do).
On complete idle it does lose about 1.2% per hour (with Wi-Fi off) but I might redo that test now with the 2.4 GHz manual setting and see if anything is changed.
It's not anywhere near the battery life of the Droid MAXX I had and sold, obviously, but so far it's doing ok. I ordered an Incipio Ghost 100 Qi-charging base a few days ago, hopefully it'll be here by the weekend so I can stop wearing and tearing the microUSB port.
Will see what happens...
br0adband said:
Got a Droid Mini now myself for a few days, it's at 4.4 and obviously unrooted and there apparently is no hope for the Chinese unlock nowadays either, sadly, so that means doing whatever possible to ensure the best battery life on mine as well. I hadn't considered forcing the 2.4 GHz Wi-Fi operation so I set it that way just now and then immediately attempted to use touchless control and it's working fine for mine with only that one change from Auto to 2.4 made.
I was using GSam Battery Monitor to get some idea of what's going on with this device but recently decided to just give the Snapdragon BatteryGuru a shot and see what happens (got another 1.5 days of monitoring before it does whatever it's supposed to do).
On complete idle it does lose about 1.2% per hour (with Wi-Fi off) but I might redo that test now with the 2.4 GHz manual setting and see if anything is changed.
It's not anywhere near the battery life of the Droid MAXX I had and sold, obviously, but so far it's doing ok. I ordered an Incipio Ghost 100 Qi-charging base a few days ago, hopefully it'll be here by the weekend so I can stop wearing and tearing the microUSB port.
Will see what happens...
Click to expand...
Click to collapse
Glad to know that the Wi-Fi settings aren't the likely culprit of my ****ed voice input. I tried the Snapdragon BatteryGuru for a while--for me the effect was negligible over a period of about two weeks. What was the wakelock keeping your phone up?
Jumnhy said:
Glad to know that the Wi-Fi settings aren't the likely culprit of my ****ed voice input. I tried the Snapdragon BatteryGuru for a while--for me the effect was negligible over a period of about two weeks. What was the wakelock keeping your phone up?
Click to expand...
Click to collapse
I have no idea, haven't bothered to look at the wakelocks presently. I got used to using TricksterMod to monitor everything but of course I can't do anything with it because of no root access.
Really wish a miracle would come along at some point, we could use a working root definitely.
Hell, we could use 4.4.2 AND a working root to be honest, hopefully whenever 4.4.2 comes along it'll fix a lot of crap in 4.4 that Motorola and Verizon just broke for whatever reason. Bleh.
Come on, Motorola, make it happen.
<and offer the option for us end users to purchase an unlock code direct from you, too...>
br0adband said:
I have no idea, haven't bothered to look at the wakelocks presently. I got used to using TricksterMod to monitor everything but of course I can't do anything with it because of no root access.
Really wish a miracle would come along at some point, we could use a working root definitely.
Hell, we could use 4.4.2 AND a working root to be honest, hopefully whenever 4.4.2 comes along it'll fix a lot of crap in 4.4 that Motorola and Verizon just broke for whatever reason. Bleh.
Come on, Motorola, make it happen.
<and offer the option for us end users to purchase an unlock code direct from you, too...>
Click to expand...
Click to collapse
Yeah, I'm with you there. I'm hoping we get 4.4.2 by mid/end of the summer, and in the meantime sitting here kicking myself for not jumping on top of buying an unlock code while they were available. $40 would have been cheap compared to putting up with this broken ****. I've been hugely disappointed in Motorola for failing to address the bugs in 4.4 in any sort of official capacity for the Droid lineup. It's funny--I didn't really care about having root so long as my phone was working. But trying to fix everything that has gone wrong has gotten my just drooling for root. Hopefully we get it eventually, and I know that the next phone I buy will DEFINITELY have an unlocked bootloader. Ugh.
I swore I'd never purchase another Motorola product and I suppose technically I haven't meaning I will never directly buy one from Motorola or from a carrier with their products (not even Google) - I got this Droid Mini for a decent price from someone off craigslist after selling the Droid MAXX for a very nice profit indeed so, in the long run I got the Droid MAXX free of charge to begin with, made profit from that then bought the Mini which is basically the same device in a smaller package more or less and still no money has gone directly to Motorola (or Verizon for that matter since I use T-Mobile just fine).
Gave up on Motorola when they pooched all of us Atrix and Photon owners so to hell with Motorola for that fiasco. Now it seems like they're doing it again by being slow and stupid for whatever reason.
I cannot for the life of me understand why it takes these companies so damned long to release a fix or update for a device - consider that the Moto X, the Droid Ultra, the Droid MAXX, and the Droid Mini all have the same X8 custom chipset and are basically the same devices in almost every respect and yet it still just doesn't get done like it should.
It's pathetic but I'm ranting now... my intolerance for stupid people (and companies) is well known so, Motorola, I can see not much has changed and so neither will my opinion.
I like the Droid Mini, it's a nice device, works fine given the limitations (no root yet, no 4.4.2) and the rather meager 2000 mAh battery. I could sell this I suppose, get me another Atrix HD (and still be mostly locked down I guess) but then slap that RAZR MAXX battery in it and get near-Droid MAXX battery life once again.
Nah, I think I'll keep the Mini unless someone makes me another offer I can't refuse. I see them listed on craigslist for rather low prices - exactly why I got this one a few days ago - and I honestly think there are a lot of people that just don't realize this is basically a "Moto X Jr" model that does effectively the same things including Active Display and "OK Google Now" touchless control.
You'd think most consumers were stupid or something for not noticing just what a fine device this Mini actually is. </sarcasm>
br0adband said:
I was using GSam Battery Monitor to get some idea of what's going on with this device but recently decided to just give the Snapdragon BatteryGuru a shot and see what happens (got another 1.5 days of monitoring before it does whatever it's supposed to do).
Click to expand...
Click to collapse
I tried that a week or so ago. I didn't let it control WiFi for me, but otherwise let it do its thing. (I also wouldn't let it turn off GMail syncing unless the phone was on - having GMail come to me close to push is one of the reasons I carry the thing with me.) It didn't make a damned bit of difference for me; it's off the phone now.
I've done the 2.4 GHz only thing. We'll see if it helps.
My ultra was doing the same thing. I back up my phone and factory reset it. For the first couple days I was killing the battery quickly from setting up my phone again and with in a week or so my battery life seemed to come back as it was in 4.2.
Sent from my XT1080 using Tapatalk
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