Database Info

Please advise. Captivate issues galore...

Hi all. I just got a Captivate after using Mattc on my HD2 and I used an Aria for a couple weeks as well. I used Mattc on the HD2 for a couple months and really liked it. I understood it was running from the SD and lived with the other issues like slow wake up and occasional goofiness.
So when I got my Captivate I was thinking, wow, I'll have one of(if not the) fastest Android phone on it's native hardware. Everything should rock. I should be blown away... Not.
HELP!
The brightness settings. WTF! Why did they implement like 10 ways the brightness screws with your day. On my HD2 w/Mattc I set the brightness in settings to where I wanted and it stayed. Forever. Also when it hits 10% it kicks the brightness all the way down. 10%? Com on maybe 5%. But what is worse is when it does kick it down I kick it back up but it dims again at every percent it goes down. ANNOYING. Please let me control my phone... Oh and don't get me started on the Browser brightness. Huh? Even with the browser brightness set at max it's still dimmer than my regular brightness setting. Noticably. I only keep my brightness at like 75-80% too.
Also what the hell is with the lame Calendar notification settings? Are there any?
My question is this. Is there any ROM out there that will strip all that Samsung ideology and give me a stock Android experience. Especially without the brightness issues. Why do I need to slide my notification bar to change brightness? All it does for me is just cause my brightness to vary accidentally when I don't want it to.
Why must I add on programs for my Calendar alerts to function normally? Why?
So again. Is there a ROM out there that will strip all the Samsung goofiness? If I can't get this phone to work like I want I'm going to sell it and look for a Telus HTC Desire to use on ATT. HTC phones are the best man. IMHO
Thanks.

juiceppc said:
The brightness settings. WTF! Why did they implement like 10 ways the brightness screws with your day. On my HD2 w/Mattc I set the brightness in settings to where I wanted and it stayed. Forever. Also when it hits 10% it kicks the brightness all the way down. 10%? Com on maybe 5%. But what is worse is when it does kick it down I kick it back up but it dims again at every percent it goes down. ANNOYING. Please let me control my phone... Oh and don't get me started on the Browser brightness. Huh? Even with the browser brightness set at max it's still dimmer than my regular brightness setting. Noticably. I only keep my brightness at like 75-80% too.
Click to expand...
Click to collapse
Turn off auto brightness and pick a setting you like. Done.
Also what the hell is with the lame Calendar notification settings? Are there any?
Click to expand...
Click to collapse
I don't know what lame is, but I use my Google calendar and I can set notifications. I get notified. Is there a specific problem you have?
My question is this. Is there any ROM out there that will strip all that Samsung ideology and give me a stock Android experience. Especially without the brightness issues. Why do I need to slide my notification bar to change brightness? All it does for me is just cause my brightness to vary accidentally when I don't want it to.
Click to expand...
Click to collapse
There is no stock Android experience. Android is just the core - Samsung, HTC, etc, they all add specific things in order for their specific hardware to function. If you don't want what comes on your AT&T Captivate, then you can root and uninstall the apps you don't like, flash one of the many, many cooked ROMs available on this forum (just look around - they are everywhere, and all with great pictures and descriptions and huge threads full of information), tweak settings to your heart's content, or anything else you want to do.
Why must I add on programs for my Calendar alerts to function normally? Why?
Click to expand...
Click to collapse
I don't have any add-ons and I get my alerts. What exactly isn't working for you?

Auto brightness has been off. First thing I do-
I do not get audible alerts when a Calendar reminder goes off-(and there is no where in settings to change/check this)
I had to install "Calendar Snooze" to play an audible alert for a Calendar reminder-
Phone is at 10% now fully dimmed. Nice... Considering how bad the battery life is for this phone(for me) I'll be spending a lot of time with the screen fully dimmed.

juiceppc said:
Auto brightness has been off. First thing I do-
I do not get audible alerts when a Calendar reminder goes off-(and there is no where in settings to change/check this)
I had to install "Calendar Snooze" to play an audible alert for a Calendar reminder-
Phone is at 10% now fully dimmed. Nice... Considering how bad the battery life is for this phone(for me) I'll be spending a lot of time with the screen fully dimmed.
Click to expand...
Click to collapse
Try reading a little and you will see you can set the brightness at where you want it by un-checking the automatic brightness setting..Then you can swipe along the status bar to raise and lower the brightness..It will stay where you had it set IF the automatic brightness is unchecked..Where you have the slider at will be the brightest it will swipe to..
Set your alerts to something you can hear and turn up the volume..They work fine.
Battery life is not a issue provided you follow some advise..Bump charge it 1 time and then use it till it drains down to single digits before recharging...also make sure you back out of all programs and turn off wi-fi and gps and syncing when you don't need them. Loose any task killer program you have and run it stock..you will find your battery life is excellent..if not you may or may not have a bad battery..Lastly..if you are really dissatisfied with it..take it back..
Good Luck
Mac

In regards to the brightness, turn off auto brightness and the 'power saving option.', that should solve your issue.
As far as removing the AT&T bloatware goes, try Unleash the beast.
If you want to run Froyo try flashing a rom, I used the latest version of Cognition.

Run far away from this phone if you still have the chance.

MikeyMike01 said:
Run far away from this phone if you still have the chance.
Click to expand...
Click to collapse
Broad-brush damnations do nothing to help anyone.

Mac11700 said:
Try reading a little and you will see you can set the brightness at where you want it by un-checking the automatic brightness setting..Then you can swipe along the status bar to raise and lower the brightness..It will stay where you had it set IF the automatic brightness is unchecked..Where you have the slider at will be the brightest it will swipe to..
Set your alerts to something you can hear and turn up the volume..They work fine.
Battery life is not a issue provided you follow some advise..Bump charge it 1 time and then use it till it drains down to single digits before recharging...also make sure you back out of all programs and turn off wi-fi and gps and syncing when you don't need them. Loose any task killer program you have and run it stock..you will find your battery life is excellent..if not you may or may not have a bad battery..Lastly..if you are really dissatisfied with it..take it back..
Good Luck
Mac
Click to expand...
Click to collapse
Thanks for the advice. Although I have done all of those things. I'm kind of coming to one real main pain point that I can't seem to solve. The screen dimming at 10%. Does anyone know how to disable that? Even if I kick the brightness back up after it dims at 10% it will redim at 9% and so on...

Bitter. But hopeful.
Picsman said:
Broad-brush damnations do nothing to help anyone.
Click to expand...
Click to collapse
Unfortunately, running away from this phone does seem to be good advise. It doesn't mater how slick it is in theory. Uber display and kickass hardware are useless if the basic functionality suffers due to glitches most of the other options don't seem to exibit.
I decided to play the "mod and wait" game with this thing, and I'm regretting it. Broad-brush damnations would have helped me. At this point, enough issues have came up about this hardware that a "broad-brush" sticky may be warranted. The alert issues found by the OP, may be related to his speaker begining to fail. I had a similar issue. Calander and alarm notifications began failing in some apps, but not others. The phone would still ring. Some apps could still use the speaker. Within a week, nothing could use the speaker, and I had to do the "push-on-it" fix.
It's a forum. Posts are opinions. I've been impressed occasionally by the raw performance of this phone. Yet, I've also spent hours, hours, researching problems, applying fixes, flashing, pushing on the speaker, etc. And I've spent hours "waiting" for the thing to do something simple like send an email when it did fine the day before. With as much time and effort as I've put into researching and working on this phone, I feel like I (and others) have not gotten enough stability out of it.
I propose a broad brush damnation for this phone: "slick but intermittent".

fshalor said:
Unfortunately, running away from this phone does seem to be good advise. It doesn't mater how slick it is in theory. Uber display and kickass hardware are useless if the basic functionality suffers due to glitches most of the other options don't seem to exibit.
I decided to play the "mod and wait" game with this thing, and I'm regretting it. Broad-brush damnations would have helped me. At this point, enough issues have came up about this hardware that a "broad-brush" sticky may be warranted. The alert issues found by the OP, may be related to his speaker begining to fail. I had a similar issue. Calander and alarm notifications began failing in some apps, but not others. The phone would still ring. Some apps could still use the speaker. Within a week, nothing could use the speaker, and I had to do the "push-on-it" fix.
It's a forum. Posts are opinions. I've been impressed occasionally by the raw performance of this phone. Yet, I've also spent hours, hours, researching problems, applying fixes, flashing, pushing on the speaker, etc. And I've spent hours "waiting" for the thing to do something simple like send an email when it did fine the day before. With as much time and effort as I've put into researching and working on this phone, I feel like I (and others) have not gotten enough stability out of it.
I propose a broad brush damnation for this phone: "slick but intermittent".
Click to expand...
Click to collapse
haha. Thanks for the ,.. opinion. I'm starting to feel the same way about this phone. I had super high hopes. But I'm really going to stick with HTC. They just get it. IMHO.

I think most people regret buying this phone. Or they will, when FroYo never arrives, the lag gets worse and worse, the phone dies on them, and the GPS never come close to working, the market decides not to intall your app, this, that, or the other thing force closes, etc. etc. etc.

MikeyMike01 said:
I think most people regret buying this phone. Or they will, when FroYo never arrives, the lag gets worse and worse, the phone dies on them, and the GPS never come close to working, the market decides not to intall your app, this, that, or the other thing force closes, etc. etc. etc.
Click to expand...
Click to collapse
Umm froyo is already leaked and OTA is on its way.
Lag has never been an issue.
And GPS is a software fix... proven on these boards over and over.
SHEESH... I'd say go tell somewhere else.
Sent from my SAMSUNG-SGH-I897 using XDA App

yeah, 5 million people are completely dissatisfied because one guy managed to not know how to operate his phone.....

MikeyMike01 said:
I think most people regret buying this phone. Or they will, when FroYo never arrives, the lag gets worse and worse, the phone dies on them, and the GPS never come close to working, the market decides not to intall your app, this, that, or the other thing force closes, etc. etc. etc.
Click to expand...
Click to collapse
I think your wrong. I think quite a few people got defective phones and haven't bothered returning them,thinking that if they root it and flash a different rom that would magically fix a broken phone. This is XDA and folks here mostly do this..thus the reason for most of the complaints. Problem is..it won't change much of anything to reflash if the phone is defective..If it is broken to begin with..it will be broken no matter what you do to it.. If yours is defective..quite *****ing about it and get one that isn't..or a different phone entirely. The working ones are great..just like they are supposed to be.
I have 2 of them built in September..both work and neither is defective.This tells me many of those built prior have some issues..perhaps not all of them..but some of them certainly. This certainly doesn't make it right by anyones account..just saying if yours is defective..return it and get one that isn't.
I honestly don't understand people who have the option of doing this,not doing it.The folks at my AT&T store opened 7 different boxes and checked every one of them for any blue tint on the screen and having the 3 button recovery option..for my second one bought at the same time,so I do know there are many out there that ain't working properly..The OP of this thread..is unhappy with it..damn..loose it and be done with it if you are that unhappy..or take that one back and get them to open up the boxes and show you one that works properly...If it was bought mail order..then you should just return it as defective and get your money back..and buy where you can see it first..It's your choice...and your money.
Mac

haptiClock get the time by tapping your phone

haptiClock vibrates you the time (haptic feedback) if you shake/bump/tap your phone. It works when your screen is off, doesn't use much battery. The pattern to decipher the time from the pulses is simple to learn.
Great for checking the time on the sly, or when you can't pull your phone out.
Free version for trial then limited, and then paid for full version. Send me feedback, I want to make this a useful app! QR code at ... well as a total newb here I can't post links even a barcode, but lookitup!
-Phil

Permission: Prevent phone from sleeping
Makes me very nervous about battery life.
Otherwise, very interesting idea, and I'll check it out.
EDIT: I'm getting constant force-closes just reading the tutorial. Galaxy S phone (Android 2.1)

"I'm getting constant force-closes just reading the tutorial. Galaxy S phone (Android 2.1) "
Wow thanks for the info, I'll look into it... been tested on Droid, Droid X, Nexus
edit:<strike>The battery use isn't as bad as I thought it would be</strike>!
apparently it is using more juice than I had seen during beta testing
Android is really challenging- lots of hardware (IMO this is a good thing) and versions make testing unreliable...

Version 1.1 just uploaded should fix problem Izkata had... THANKS FOR THE INFO!

Just a quick test this morning, and it does appear to be fixed.
I'll test it more thoroughly later today.

I just downloaded the free version of this and it looks really promising.
While the screen was on and the app still open it worked perfectly, but when I turned the screen off and activated it again, it did hours fine and the rounded min fine, but the 2nd activation didn't work.

OK, noted ADeadlySpoon... thanks.
There is a time window to second tap to get the exact minutes, it's 10 seconds, you can also just go into "one tap" mode and time to exact minute every time. Still, I'll try to re-create your issue.

Wont work if screen is off.. on my EVO

drummer2780 said:
Wont work if screen is off.. on my EVO
Click to expand...
Click to collapse
Same with Desire HD which makes it useless for me atm.
But it's a nice App, hope this will work soon.

Okay, so - I left it running with the screen off and phone unused for about an hour and a half, to check the battery usage.
(Phone: Samsung Captivate (Galaxy S on ATT))
Normally, on average, I lose just under 1% per hour when the phone is not in use. With haptiClock active, I lost right around 1% per 10 minutes, while the phone was not in use. So the drop isn't as bad as I was expecting (yay!), but it's not something I'd leave on all the time, either.
No force-closes, ether, so the fix earlier seems to have fixed it entirely.
I have a habit of discreet time-checking, so this'll be great. Best trigger for me seems to be about 13 or 14 - juuust enough that I don't have to whack my phone/make an obvious movement to trigger it.

I have to change the language on the help, because when it did appear in my battery use stats it was always about the same as Cell Standby, which didn't seem to make sense, I should have grabbed Izkata's app (and will now) to check battery usage. It is important to turn off when you don't anticipate needing it.
On the Desire HD & EVO, I have no idea why ATM, but will look into it over the next 24hrs. I did test it on an HTC myTouch 3G and it worked.
If either of you get a chance, could you post OS version / API level and any mods?
Thanks for checking it out.
-Phil

upperTriangle said:
I have to change the language on the help, because when it did appear in my battery use stats it was always about the same as Cell Standby, which didn't seem to make sense, I should have grabbed Izkata's app (and will now) to check battery usage. It is important to turn off when you don't anticipate needing it.
Click to expand...
Click to collapse
Yey, thanks
It's not the best thing for measuring usage like this, though. To get the numbers in my previous post, I just recorded the percent before and after, and manually divided. 'Tho you can see in the History graph when it drops faster, so that helps.
upperTriangle said:
If either of you get a chance, could you post OS version / API level and any mods?
Click to expand...
Click to collapse
Android 2.1-update1 / API 7, rooted, but with no mods.

When screen is on, it works alright. But when screen turned off, no response from the app. Great idea though. I'm using a wildfire btw..

To those of you for whom the app doesn't work when the screen is off, this is an Android bug affecting certain phones. I believe it is a problem (be it a feature whereby the manufacturer is trying improve battery usage profile, or a bug) with the firmware. The HTC phones with Sense UI seem to be among the more commonly afflicted devices.
I remember seeing this bug report I started working on the app:
http://code.google.com/p/android/issues/detail?id=3708
BUT by the time it was getting close to done, my impression was that this had basically been fixed, and I didn't mention it anywhere in the release, none of the phones I tested on had this problem.
Now, there is another newer Android bug report regarding this issue, please STAR it (upper left of page)
http://code.google.com/p/android/issues/detail?id=11028
and hopefully we will see more rapid resolution of this issue, I think the OS isn't the problem, but perhaps manufacturer firmware updates could help resolve it.
Please don't leave negative comments on the Market if the app doesn't work with the screen off. Because of users doing this (which I should have seen coming) my star rating is started to go down. I have included language on the Market entry which should prevent people from giving the app a low rating solely because of this issue.
Lastly, there is a workaround of sorts for this which will fix the problem on some phones. I will implement it, but am going to proceed very cautiously, because last thing I want to do is break the app for users for whom it is currently functioning appropriately.
As such, I would really appreciate it if people who are experiencing this issue would beta test a new release with the workaround prior to my releasing it on the market.
So drummer2780,Testuser_01,thunderskain, ADeadlySpoon(?) ... if any of you would be so kind as to receive an APK file from me for testing on your device, in return I'll try to somehow get you the full version gratis of course (how we'll do that I'm not sure as I don't want an APK with licensing disabled floating around out there!, perhaps you can buy it from the Market and I'll refund the payment)
Izkata, for your help I'd like to do the same (give you free version) so if you buy it I will refund. I don't *think* a refund will invalidate the licensing, but I'm not sure, it is unclear from the Google distribution agreement language.
Thanks for checking out my app, I'm hoping people are finding it useful!

Izkata said:
Best trigger for me seems to be about 13 or 14 - juuust enough that I don't have to whack my phone/make an obvious movement to trigger it.
Click to expand...
Click to collapse
Since you are using it at a pretty sensitive setting:
Go to settings->overall sensitivity and select "Make more sensitive" and you'll find you can be a little more in the middle of the range and will have better precision for where you'd like the trigger to be, of course set it back if you want to use it and you're being more active.
-Phil

upperTriangle said:
So drummer2780,Testuser_01,thunderskain, ADeadlySpoon(?) ... if any of you would be so kind as to receive an APK file from me for testing on your device, in return I'll try to somehow get you the full version gratis of course (how we'll do that I'm not sure as I don't want an APK with licensing disabled floating around out there!, perhaps you can buy it from the Market and I'll refund the payment)
Izkata, for your help I'd like to do the same (give you free version) so if you buy it I will refund. I don't *think* a refund will invalidate the licensing, but I'm not sure, it is unclear from the Google distribution agreement language.
Click to expand...
Click to collapse
Since we both have a paid version of an app out, we could just do a "trade" and buy each others' apps, assuming you haven't already. The difference in pricing is small enough that I wouldn't really worry about it. Or we could try out the refund idea, then have experience to advise others in the future (I haven't bought haptiClock yet, and might not for a while - various stuff going on IRL)
upperTriangle said:
Go to settings->overall sensitivity and select "Make more sensitive" and you'll find you can be a little more in the middle of the range and will have better precision for where you'd like the trigger to be, of course set it back if you want to use it and you're being more active.
Click to expand...
Click to collapse
I'll take another look at the setting(s) eventually, and try and remember to post my comparisons in this thread once I do. (However, I'm starting a new job this week and don't want to mess with stuff/might not have time to mess with stuff until next weekend)

Great app! I've been looking for an app that did this for a really long time.
I was thinking though. The vibrate system's a little confusing, and I don't really need to know the exact time. Usually I only need to know it to the closest 15 minutes. Perhaps you could set toggles for the 10/15 minute vibe, the 5 minute vibe, and the 1 minute vibe?

SamUserInterface said:
Uually I only need to know it to the closest 15 minutes. Perhaps you could set toggles for the 10/15 minute vibe, the 5 minute vibe, and the 1 minute vibe?
Click to expand...
Click to collapse
There is a setting which allows you to only receive the 10/15 vibe (at least it requires an add'l tap to get the exact minute)... but I do like your idea of being able to specifically set where to stop. It would be a fairly extensive task for me to implement, as I basically have it set up to do just to the minute, or require add'l tap. We'll see how it goes, I can't say I'm going to be spending a bunch more time on this thing unless it attracts more users.
Thanks for the feedback!

Doesn't work with the screen off on the dell streak running dj steves 1.6.0 froyo ROM. Would definetly be interested in buying when (if) it can.

Well, it looks like all workarounds I've tried for phones which don't respond to the sensor when the screen is off (in standby mode) have failed. This is likely a firmware issue which ought to be addressed by the manufacturer. The code should run the same on all devices, this is the point of Android!
Given that it works on most phones, it is a "bug" or "defect".
Please take a moment to star the issue at code.google:
Issue 11028
Also, contact your phones manufacturer rolleyes: HTC) regarding this issue.
I think there are lots of possibilities here and hopefully it will get fixed because there are similar apps I'm creating which rely on the accelerometer working in standby as I've implemented in haptiClock.
Thanks
Phil

[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.

Android 4.4.2 Improvements...?

Hi. I want to buy the new Nexus 5 from Google/LG and i want to ask about the Android 4.4.2 update.
I have read that there were issues (again similar to the Nexus 4) that there were occasional wifi signal dropouts, weak speakers, screen quality and the camera.
Has these problems been resolved with the update?
Please advice. Thanks.

The sound of the speaker is average! It's a hardware thing, no software update can change it.. If you want some boost, you will need to root it and install a sound mod like Viper4android...
No wifi signal dropouts here. Whaatttttt??? The screen on this beast is a real BEAUT!
The camera is pretty good and can manage decent shots.

gino_76ph said:
Hi. I want to buy the new Nexus 5 from Google/LG and i want to ask about the Android 4.4.2 update.
I have read that there were issues (again similar to the Nexus 4) that there were occasional wifi signal dropouts, weak speakers, screen quality and the camera.
Has these problems been resolved with the update?
Please advice. Thanks.
Click to expand...
Click to collapse
Never had wifi problem, speaker is easily fixed and they addressed it in 4.4.2, my screen is perfect, and my camera is perfect.
This nice man made a volume boost mod http://forum.xda-developers.com/showthread.php?t=2532788
and this nice man made a camera mod http://forum.xda-developers.com/showthread.php?t=2516061

As i have mentioned in my other thread i'm not into modding or rooting as for me its too technical and i would rather air my complaints (and suggestions) to Google et al and wait for the official updates be it minor or major.
This is my 2nd-ever Nexus phone. The other one being the Nexus 4 and i didn't like it as there were just too many issues and problems hardware-wide and also software.
I would like to give this phone a chance and i hope the unit i got from Carphone Warehouse is free from hardware "abnormalities" and problems as they don't offer refunds anymore and only just exchange.
I heard after the 4.4.2 update there were still issues with the camera like it tends to over compensate or over saturate in some instances. The contrast algorithim (or whatever they call it) was tweaked but somewhat of a hit n' miss depending on the time of the day. True?
Also, how's is the shutter lag? (i.e. in-between shots) Is it a lot faster now than the N4? My old Galaxy S3 and my current iPhone 5C has an almost zero shutter lag which will benefit me.

gino_76ph said:
As i have mentioned in my other thread i'm not into modding or rooting as for me its too technical and i would rather air my complaints (and suggestions) to Google et al and wait for the official updates be it minor or major.
This is my 2nd-ever Nexus phone. The other one being the Nexus 4 and i didn't like it as there were just too many issues and problems hardware-wide and also software.
I would like to give this phone a chance and i hope the unit i got from Carphone Warehouse is free from hardware "abnormalities" and problems as they don't offer refunds anymore and only just exchange.
I heard after the 4.4.2 update there were still issues with the camera like it tends to over compensate or over saturate in some instances. The contrast algorithim (or whatever they call it) was tweaked but somewhat of a hit n' miss depending on the time of the day. True?
Also, how's is the shutter lag? (i.e. in-between shots) Is it a lot faster now than the N4? My old Galaxy S3 and my current iPhone 5C has an almost zero shutter lag which will benefit me.
Click to expand...
Click to collapse
Rooting and stuff is not technical at all, it requires little to no knowledge. Just read the guide threads..

My belief is that if i mod or root a device the warranty will be void and that i cannot "un-root" it again. My other worry is the rooting procedure might introduce bugs or even viruses. That's my belief. Again, i could be wrong.
I still would go to the normal route i.e. waiting for official updates based on end-user comments/complaints/issues/suggestions which i do every now and again till Google and those other OEM's realise things.

gino_76ph said:
My belief is that if i mod or root a device the warranty will be void and that i cannot "un-root" it again. My other worry is the rooting procedure might introduce bugs or even viruses. That's my belief. Again, i could be wrong.
Click to expand...
Click to collapse
Hi,
You can unroot and go back to stock: http://forum.xda-developers.com/showthread.php?t=2513701.
As for viruses and bugs, it's not the root that can cause that but more what you will do after rooting your device... There is no bug, at least no more than a non rooted device, with only rooting your device. It's only if you modify some files system, flash something not stable, or the wrong file and so on. If you install a "crappy" or cracked app with root access (and allow it without know what it does), yes maybe you can encounter some bugs or viruses. It's on the user side...

I have not rooted my phone and it's perfect, i have no complaints whatsoever. I keep refraining myself from rooting tho because of gravitybox, my geeky side keeps telling me to root but i don't right now because i don't need it, but i will definitely do it after a year or something (knowing myself).

gino_76ph said:
My belief is that if i mod or root a device the warranty will be void and that i cannot "un-root" it again. My other worry is the rooting procedure might introduce bugs or even viruses. That's my belief. Again, i could be wrong.
I still would go to the normal route i.e. waiting for official updates based on end-user comments/complaints/issues/suggestions which i do every now and again till Google and those other OEM's realise things.
Click to expand...
Click to collapse
When using Fastboot and ADB its commands so there is no chance of bugs or viruses.modding is what XDA is all about.
Sent from my Nexus 5 using Tapatalk

I could maybe try rooting my device one day. But until then i'm happy with normal updates.
I have been reading about the "fiasco" of 4.4.1 and i just think that Google sometimes don't listen to end-user complaints too quickly and they would rather sit back and wait till the complaints are a mountain high (with the same issues attached to it) until they act.

I used my N5 for a week, stock and unrooted. I had absolutely no problems with it. I got used to the screen after a day and never really complained about it. I even think it's the best screen so far, especially outdoors. Zero wifi signal drops. My phone speakers wake me up using the alarm clock. Camera can produce excellent photos; take a look inside the picture thread. It's really just the feature-itch that kept me flashing custom roms.
Sent from my Nexus 5 using Tapatalk

ej8989 said:
I used my N5 for a week, stock and unrooted. I had absolutely no problems with it. I got used to the screen after a day and never really complained about it. I even think it's the best screen so far, especially outdoors. Zero wifi signal drops. My phone speakers wake me up using the alarm clock. Camera can produce excellent photos; take a look inside the picture thread. It's really just the feature-itch that kept me flashing custom roms.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry i can't find the picture thread.

gino_76ph said:
Sorry i can't find the picture thread.
Click to expand...
Click to collapse
Hi,
Here: [PHOTOS] Post Your Pictures and Videos...

ej8989 said:
I used my N5 for a week, stock and unrooted. I had absolutely no problems with it. I got used to the screen after a day and never really complained about it. I even think it's the best screen so far, especially outdoors. Zero wifi signal drops. My phone speakers wake me up using the alarm clock. Camera can produce excellent photos; take a look inside the picture thread. It's really just the feature-itch that kept me flashing custom roms.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have been hearing somewhat conflicting comments that the 4.4.2 camera still has more space for improvements. It can sometimes bring oversaturatedness, greyness, haziness and still weak in the low-light department.
Another issue i heard is the battery seems still not convincingly and dramatically improved from the last time. 3G & 4G signal seems also not perfect. What i mean is if the phone comes from a 3G to a 4G area the phone either reboots itself, turns itself off or would take time to "reconfigure" its software to know that its in a strong 4G signal. Am i making sense?
Is there any truth to this?

gino_76ph said:
Is there any truth to this?
Click to expand...
Click to collapse
Not with respect to my phone.

Still somewhat not convinced. There are still some known issues with 4.4.2 i heard. I'm not too worried about the camera as i believe it is much improved but my other main concern is the battery life.
Some are saying that the "Android system" (or the OS) is the culprit. I'm not an engineer but is it because of maybe the way the OS works or something. I also heard that there are random wifi crashes, phone just turns off by itself and when the phone is actually asleep it drains a lot and then the battery heats up, etc.
I'm sorry to be bringing this issues up buy you hear and read this online and it seems credible. If more than 1 person have been complaining the same thing surely there is truth to the issue.

5Hi,
In my opinion stop the "I heard someone" or "some are saying" and jump the train...
4.4.2 is way better than 4.4/4.4.1 (and yes I ran stock rom in the past ).
About Android usage in battery stats is already discussed here, I mean in this Q&A forum, I have not it, like almost 90% (or more) users, it's on the user side (whatever some other users tends to think). It can happen on 4.4/4.4.1 too... but since a minority of users are still on this version and the updates have been quick, nobody still speak about it.
Wi-Fi crashes, phone turn OFF by itself (on full stock?) it's also a very large minority on stock (I would say never), it could be due to the user too, no?
High battery drain in idle-> mostly user side (rogue app for example). Ans so on...
Don't mixe what your read about some problems between stock rom and custom rom/kernel/mods...., in my opinion (and I'm not alone) all you read is nothing, biased feedback due to some users who don't know how use their phones, install xx and xy apps and after that they are complaining about battery life, bugs and so on
Battery heat (or CPU?), what is heat for you or for the guy who said that? I any case there is thermal throttle to prevent any dammage and you are running a quadcore CPU (with a max CPU freq at 2,26 GHz ) enclosed without thermal cooling so in certain circumstances expect some heat...
If you are not still convinced, hum... don't do anything
Test and see by yourself, sometimes it will be better than read something here and there... . I'm not saying that you are "reported" is false but nonestly it's mostly ******, at least like I said it's not about 4.4.2 itself but user side.
That being said you seem a user easily influenced by some things read or heard here and there, maybe you'll be more influenced by the replies in your thread

gino_76ph said:
Still somewhat not convinced. There are still some known issues with 4.4.2 i heard. I'm not too worried about the camera as i believe it is much improved but my other main concern is the battery life.
Some are saying that the "Android system" (or the OS) is the culprit. I'm not an engineer but is it because of maybe the way the OS works or something. I also heard that there are random wifi crashes, phone just turns off by itself and when the phone is actually asleep it drains a lot and then the battery heats up, etc.
I'm sorry to be bringing this issues up buy you hear and read this online and it seems credible. If more than 1 person have been complaining the same thing surely there is truth to the issue.
Click to expand...
Click to collapse
I have not experienced any of these issues when I was on stock for a week. I suggest you go buy the nexus 5 and return it if you don't like it then try the G2 if you really want amazing battery life. But I assure you, once you experience Nexus, you'll go back to Nexus.

Well, for one thing i had a Nexus 4 and i had to return/sell it because of so many issues. And those same issues have again cropped-up in the stock Nexus 5 4.4/4.4.1/4.4.2. Sounds familiar?
Yes it's true it "could be" a minority who have the same issues but its STILL a minority and its STILL the same issues. It's either the users fault or the phone itself. Yes it could be malicious/battery-draining apps or a ROM that has some bugs, etc. But in the past 6 months i have not heard of a "minority" of HTC One or Galaxy S3/S4 users that have the same issues. Have you? It does tell you something about how the phone was made and how Google pushes its updates.
I know and i'm well aware that the only thing to do is to actually try one. But what if if i try one, got the same problems, do a factory reset, still same problems, have to return/sell the thing and so on. Its such a hassle. That is why i am looking for answers and reviews/comments here. And i truly appreciate all your insights. I really do.
Call me fuzzy or overly-careful. I'm not looking for a "perfect" Google Nexus phone. I just want a phone (and Android phone as such) that works.
Again, as i said i'm not overly worried about the camera because a phone camera can & will never replace a proper one.My other concern is the 4.4.2 battery life. My Nexus 4's battery life was near atrocious. Could not tell you how long (or short) it's battery life is thats is why i got rid of it. But if a number of issues come up with the same battery life issue and battery getting warmer then am i to worry?
My typical day is get up at 6AM, remove the charger on my phone (if it was charged overnight), turn it off or turn the wifi off whilst i have my shower, get on the bus and the train, turn on my mobile data then checking the morning news/weather/notes/Twitter, get on to my work and keep my mobile data (and everything else like wifi, bluetooth, NFC...you know) turned off, turn on my data again for my 30-minute lunch and turn it off when back to my afternoon shift, going back home i listen to some music (a typical journey lasts around 45 minutes) whilst at the same time checking out some tech news on Appy Geek, when i'm at home i turn off my mobile data and connect to my home wifi (kept On till until i wake up again the next morning) whilst in-between supper & shower & bed i check Twiiter again, Instagram, couple of Youtube videos, email, playing a game which would last maybe 30-60 minutes max and that's it. I sleep around 11PM and wake up again around 6AM.
My questions are:
1. Anything to worry about the battery life?
2. Is it wise to install a "battery saving" app on the Play store?
3. Will heat be a factor on my "typical" day on draining my battery life?
4. Is it true the battery life improves after a couple of charges?
The area where i live, where i travel and my work place hasn't got a strong 4G signal. I have no problems with my home broadband/wifi as i typically have a very fast and stable connection. So...
5. Will the phone picking up 3G & 4G signal (switching back & forth and re-initializing again and again) be a factor in a battery drain?
6. What tips can you advice me on how to save battery life on my Nexus 5?
Thanks peeps.

gino_76ph said:
Questions below
Click to expand...
Click to collapse
1. Anything to worry about the battery life?
Based on how you use your phone, not really. Unless there's a hardware defect.
2. Is it wise to install a "battery saving" app on the Play store?
For me, no. I once tried one and it didn't help at all. But there's no harm in trying.
3. Will heat be a factor on my "typical" day on draining my battery life?
A few weeks ago I did some heavy gaming for an hour and the phone was really warm, but I still got >5hrs SoT at the end of the day before charging again.
4. Is it true the battery life improves after a couple of charges?
Yes the battery life is somewhat improved; but what I experienced was that it improves when I stay in the same ROM for some days, and I charge it overnight when the battery is less than 5%.
5. Will the phone picking up 3G & 4G signal (switching back & forth and re-initializing again and again) be a factor in a battery drain?
In my opinion (and experience), yes.
6. What tips can you advice me on how to save battery life on my Nexus 5?
Here's a thread you can analyze: Nexus 5 Battery Results

So...my Droid Maxx eats 10% of battery in just 3 hours,,,

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