Steps to reproduce the solution:
0. Rooted my phone through adb using update.zip.
1. I bricked my phone later (not sure how).
2. Restored it to stock settings using ODIN3
3. GPS works with decent accuracy indoors and out.
I would say give it a few days to see if it actually works or not
GPS always works well after a hard reset / factory reset. At least for a little while...
jhannaman82 said:
GPS always works well after a hard reset / factory reset. At least for a little while...
Click to expand...
Click to collapse
maybe the agps is not auto updating??? I know on windows mobile there is and app to manually download agps data but there is no app for android
i also used the odin3 restorer just to see if it actually worked in the event i needed to return my phone to att. after i did the restore i noticed not only was my phone smoother but the gps DID work better. so out of curiosity i went into the gps settings and noticed the server that the gps was connecting to was not the factory suggest att server. dont know if this has anything to do with it, but i am happy with it now. re-rooted my phone after i restored and deleted all the bloatware and now i have a really smooth, gps functioning, battery life extended cappy. i love my phone
What server is it using now? Can we change it without restoring? Sorry, I'm an android noob, the captivate is my first one.
Sent from my SAMSUNG-SGH-I897 using XDA App
Id also like to know what server you are using @novajustin
you can view/change the server by typing in the Dialer *#1472365#
Wander73 said:
Id also like to know what server you are using @novajustin
you can view/change the server by typing in the Dialer *#1472365#
Click to expand...
Click to collapse
not sure if this is anecdotal or not but I just tested the gps after not using it for 2 days and the only thing i changed was that i enabled skyhook. With just enabling skyhook I got a fix in 59sec which is not great but better than i was getting
how skyhook works http://www.skyhookwireless.com/howitworks/
gps settings are as follows...
session type: tracking
test mode: s/w test
op mode: standalone
start mode: hot start
gps plus: on
dynamic accu: on
acc: 50
use skyhook: off
use pc tool: off
supl/cp settings...
custom config
server: ww.spirent-lcs.com
port 7275
supl secure socket: on
agps mode: supl
i havent touched any of the gps settings since using odin3 and so far i have been pretty happy with the gps performance. oh btw i did the restore a week ago today.
novajustin said:
i also used the odin3 restorer just to see if it actually worked in the event i needed to return my phone to att. after i did the restore i noticed not only was my phone smoother but the gps DID work better. so out of curiosity i went into the gps settings and noticed the server that the gps was connecting to was not the factory suggest att server. dont know if this has anything to do with it, but i am happy with it now. re-rooted my phone after i restored and deleted all the bloatware and now i have a really smooth, gps functioning, battery life extended cappy. i love my phone
Click to expand...
Click to collapse
What would you call a "battery life extended cappy"? What kind of battery life are you getting?
I'm a light to moderate user of my phone throughout the day. Mostly busy here at work, dont have time to **** around on the phone all day; and I get only about 15 hours on a charge. Take it off charger in the morning (7:30-8:00) and have to recharge it every night (10:30-11:00).
novajustin said:
gps settings are as follows...
session type: tracking
test mode: s/w test
op mode: standalone
start mode: hot start
gps plus: on
dynamic accu: on
acc: 50 mine is set to 60
use skyhook: off mine is set to ON
use pc tool: off
supl/cp settings...
custom config
server: www.spirent-lcs.com
port 7275
supl secure socket: on
agps mode: supl
i havent touched any of the gps settings since using odin3 and so far i have been pretty happy with the gps performance. oh btw i did the restore a week ago today.
Click to expand...
Click to collapse
This worked for me with a couple of mods. After a reboot, it took about 29 seconds to get a fix on the first try. The second try took about 10sec. The third, 10sec again. The fourth, 4sec. With the settings above, I conclude that the GPS will lock in about 10sec or better after getting its initial fix.
Well, I was hopeful, but my server settings are the exact same as yours, and it still takes forever to get a fix. Like do long I get tired of waiting and give up. Guess I may try the restore. Maybe there's something we're missing here.
Sent from my SAMSUNG-SGH-I897 using XDA App
coldfuzion76 said:
Well, I was hopeful, but my server settings are the exact same as yours, and it still takes forever to get a fix. Like do long I get tired of waiting and give up. Guess I may try the restore. Maybe there's something we're missing here.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I was sitting outside my office, with a clear view of the blue sky I had to walk out of my office building (9th floor) even though I have a large office window. I cannot get any satellites from my office. Of course not.
Pardon me, I'm a noob, but why does getting a GPS fix require a connection to a server?
It downloads the satellites locations if I remember correctly. It lets You get a faster lock since the phone doesn't have to blindly look for satellites.
Someone please correct me if I'm wrong.
Sent from my Samsung Captivate.
derek4484 said:
What would you call a "battery life extended cappy"? What kind of battery life are you getting?
I'm a light to moderate user of my phone throughout the day. Mostly busy here at work, dont have time to **** around on the phone all day; and I get only about 15 hours on a charge. Take it off charger in the morning (7:30-8:00) and have to recharge it every night (10:30-11:00).
Click to expand...
Click to collapse
well coming from an iphone i already expected the battery life to be pretty worthless. after all these are not your old school flip phones, this is a fully functioning kick ass smartphone. anything with a 1ghz processor is going to eat batteries so i dont know what everyone is complaining about.. ok /end rant.
i use my phone A LOT. pandora at work but mostly the snes emulator so after playing at work all day, i come home and my battery is at 20%. perfect for me. i get home, throw it on the charger, and move on with my life. i havent really monitored my battery usage on idle, maybe one of these days i'll actually be able to put my phone down and see how long i get out of a charge on idle. but i can say this, playing a game for an hour straight before would drain my battery like i drain a bottle of whiskey, now its more of a sipper. but i also have my brightness and all the auto stuff turned down and off. this probably has not helped you one iota but i sure feel good about it haha
forgot to mention, i know quite a few people with all different android phones. one with a hero. 2 with evo. 1 with droid original, and one with a samsung moment. all of them say their battery life is about 1 day. its a fact of life with an android phone. iphones are going to last longer because they are not constantly syncing with some type of service all day as we are with android. all day our phones are contacting google or whatever services you may use for widgets. i have just accepted the fact that i have to charge my phone every night as i did with my iphone 2g and 3gs.
Related
My phone turned off by itself today while it was in my pocket, here are some information. The phone is also not rooted, no launchers have been used, and is currently using TouchWiz.
Purchased from AT&T Premier website on August 27th 2010
Delivered to me September 1st 2010
Manufacturing Date - August 2nd 2010
Battery Manufacturing Date - Not checked
Apps installed before shutoff experience:
Dictionary.com
Fandango Movies
The Moron Test Lite
WordUp
Google Voice
Speedtest.net
Barcode Scanner
Ninja Kaka - Fruit Dojo
Drop Block DEMO
Hella Umbrella Beta
PapiJump
Jewels
Unblock Me FREE
Smooth Calendar
GPS Test
1 Day/Night before I experienced the shutoff, the following were installed:
- Used my own wallpaper jpeg instead of one from the Captivate's stock wallpaper folder
- Beautiful Widgets
- AppBrain App Market
- Fast Web Installer
- Angry Birds Lite Beta (APK FILE, USED ANDROID CENTRAL'S SIDELOADER MACHINE)
- Paper Toss
I've had my phone for exactly 1 week, and after reading all the horror stories of people experiencing the random shut offs, I thought I was lucky up until now. I love this phone a lot despite the obvious GPS issues. Does anyone have any idea on what may be causing this? Hardware or Software issue?
I would hate to exchange it for another with AT&T since I've become so attached to it.
My phone randomly shut down within the first couple of days I had it too. However, it doesn't happen anymore.
I'm still not exactly sure what caused it. Here is what I can remember having differently before and now:
- Used the Grass live wallpaper; now, I'm using a static wallpaper
- Had a corporate exchange account synced; now, only syncing a Google account
And of course, I've been charing the phone more ever since I got it, so maybe the battery needs to "learn" something so that it doesn't automatically shut down?
kevrocks said:
My phone randomly shut down within the first couple of days I had it too. However, it doesn't happen anymore.
I'm still not exactly sure what caused it. Here is what I can remember having differently before and now:
- Used the Grass live wallpaper; now, I'm using a static wallpaper
- Had a corporate exchange account synced; now, only syncing a Google account
And of course, I've been charing the phone more ever since I got it, so maybe the battery needs to "learn" something so that it doesn't automatically shut down?
Click to expand...
Click to collapse
thanks kevrocks, how long have you had your captivate btw?
There are a few threads here, including mine with the "Let's compare apps" theory http://forum.xda-developers.com/showthread.php?t=763956. No on has been able to figure it out. However, in my observation, I had my Use GPS Satellites turned off while I was away on vacation in Europe. In the 7 days I was away, my phone never turned off on me. That was last week. This week, it still hasn't turned off (knock on wood). Could that be the culprit?
Do your own test. Uncheck the "Use GPS Satellites" in the Location and Security menu. Check it when using Maps or Navigation but don't forget to Uncheck it when not in use. Observe for a week and see if you get the same results as I did.
Good luck.
mike_terror said:
thanks kevrocks, how long have you had your captivate btw?
Click to expand...
Click to collapse
It's been 1.5 weeks so far.
Mine did this also, when i called Samsung they explained to me that they don't know what the problem is that is causing this issue and that some users are experiecning it. They told me that I would need to send the phone in with Phone, Bat, and Bat Charger for a complete diagnostic overview. Unwilling to do this I just returned the phone for a different one. I'm thinking that if it happens it hardware and you are best off getting a replacement rather then messing with it.
RexEscape said:
There are a few threads here, including mine with the "Let's compare apps" theory http://forum.xda-developers.com/showthread.php?t=763956. No on has been able to figure it out. However, in my observation, I had my Use GPS Satellites turned off while I was away on vacation in Europe. In the 7 days I was away, my phone never turned off on me. That was last week. This week, it still hasn't turned off (knock on wood). Could that be the culprit?
Do your own test. Uncheck the "Use GPS Satellites" in the Location and Security menu. Check it when using Maps or Navigation but don't forget to Uncheck it when not in use. Observe for a week and see if you get the same results as I did.
Good luck.
Click to expand...
Click to collapse
Funny you mention location. I flashed jh2, latest sre, and tats lag fix yesterday. I was actually turning on my locations and my phone shutdown. I figured it was the oc kernel.
Had other random reboots/shutdowns after. Could have been the flash. Just fyi'ing.
Sent from my SAMSUNG-SGH-I897 using XDA App
mine shut off for the first time yesterday, this is my second, first returned for a loose battery cover and speaker issue. I'm hoping the phone doesnt continue to shut off. Ive spoken to ATT, and i'm kinda screwed right now if it ends up being a hardware issue with the phone. i'm past my 30 days.
Oh, I also performed a factory data reset, and I haven't gotten any random shutdowns ever since.
I also spoke with Samsung technical support, and the rep suggested to do a soft reset. This is where you remove the battery, clean the gold contacts on the phone and battery, and then reinsert the battery.
I've had mine since the first Thursday it was out. For the first week or two, it shut down about once a day. After that, I've never had a random shut down. Don't know why, I've played around with settings and apps since day one back and forth, so I don't believe its any certain setting or app. Maybe a part of the phone or build getting adjusted?
I remember read somewhere that this is actually a hardware flaw: the battery barely touches the PINs. So if there is any free play in the battery compartment, your phone will randomly loss contact with battery and hence shutdown. Exchange the phone seems to be the only solution. Or you can insert some paper on the other end of the battery to make sure it tightly presses against the PINs.
Mine never encounters this problem regardless how I mess with my phones (flashed firmware couple times and rooted, updated many many times).
It definitely reacts as if the power was removed from the phone. There is no power down screen or indication of rebooting. I have looked at the contacts on the battery, but my last phone made a perfect connection as far as I could tell.
If it is a hardware issue, then I'm perfectly okay with that. I could wire the battery directly to the phone and problem solved. I've also heard of people having a lot of luck buying the cheap chinese batteries for the phone off of ebay to correct their shut down issues. Maybe their connectors are pushed more toward the surface than the Samsung battery.
So I spent 3 hours on the phone with AT&T last week while their warranty department did everything they could to not just honor the warranty (I can go into detail of anyone cares). But after the long grueling battle I was finally able to get my 1008 replaced with a 1009. Now the gps on my 1008 was shotty at best. I received the new phone, fired up Srendipity 6.3 and installed the free TeleNav GPS program and received instant results. Before, I was getting 3-4 sats after 30 seconds and it would barely hold. Now, I instantly get 7 or more sats and was able to lock up to 11 and hold them. My gps works spot on and I couldn't be happier. Morale of the story.. if you have spotty GPS at best, try exchanging the phone.. but be for warned about AT&T honoring the Gps capability for the Captivate with out a lot of legwork.
Sent from my SAMSUNG-SGH-I897 using XDA App
I was having a GPS problem and the warranty people sent out a replacement with a 15 min phone call. got one that works ok, but with the right modem it gets 10-11 sats in under 5 seconds.
might be who you get and how willing they are to try and figure out your problem without just jumping to it being a hardware problem.
The captivate gps is way to random to guarantee a replacement will fix anything as no one knows all the details of the problem. Part of it is obviously software as several tweaks work wonders for most people. No one knows what the combination is for sure.
A standing lock shows nothing for actual driving navigation performance.
Your results will vary but do we really need a new thread from everyone who warranty replaces their phone for bad gps performance
Sent from my SAMSUNG-SGH-I897 using XDA App
Remember too, almost all "new" Captivates' GPS work great for a few weeks. Post back in about a month and let us know how your new Captivate is working. Also, it seems as though the GPS will work great for a few weeks after loading a new ROM, then it goes bad again. Tells me there is s file the GPS must process avery time you turn it on. As the file grows in size, the GPS program can't process the file in a timely manner resulting in the interpretation of the GPS data being slow and off-course.
I'll do that. I like using my GPS for looking things up (don't use navigation that much since I don't do much traveling) but I'll definitely keep an eye on it and see how it handles aftera week or so and then after that.
Sent from my SAMSUNG-SGH-I897 using XDA App
just got a 1007 replacement for the 1007 i have. The GPS works out of the box for stock froyo. it actually trasks every single turn and is able to catch up when i am driving 75-80 on the freeway. So ya... if anyone fail to get their gps working by software tweaks, you should go ahead and use the random shut down execuse to get a replacement phone. the 1007/8/9/... thing doesnt really matter i guess. The one I got works like a charm beside the sticker behind the battery look crappy without a SN number and the samsung logo.( oh well probably a refurb , but at least it works~)
It's like a gamble, but hey at least exchange it while u still can with warranty is better than hoping for a software fix that we are still not sure about if it's the real issue. Honestly it could be software for some people, but after u tried couple Roms and fixes, a bad gps is a bad gps.
The "batch number" on my phone is 1008. The phone came with Eclair, of course. The GPS was poor at best. I updated the phone to Froyo. The GPS was not perceptibly different; still darn poor. I remember one miserable night where I was forced to find my destination using the Biblical System. The GPS never did lock during my one-hour ordeal.
For a totally unrelated reason, I ending up doing a master clear and reset. After I got everything reloaded I "tested" the GPS. Wow! It locked, well, instantly, or so it seemed.
An app available in the Market called GPS Status has two nice features. You can set it to automatically download the A-GPS file at start up. And, it reports on screen how long it takes to get it's first lock. With GPS Test (and others) you can see when the phone locks but GPS Status reports the time-to-lock information in seconds, no stopwatch or counting required.
Fascinated at the new-found capability of my Captivate, I have repeatedly checked how long it takes to get a lock. I would say, under widely varying conditions, the lock time is almost always less than 20 - 25 seconds.
YMMV but you might try a master clear and reset if you have a phone you undated from 2.1 to 2.2. Except for the time it takes to rebuild your phone, you have little to loose and you might find, as I did, the Captivate's GPS is excellent. Had I not "discovered" this "solution" I would have abandoned my Captivate--even though I think it's great phone overall--as I routinely depend upon my PDA's GPS capability.
FWIW, I do a lot of Geocaching so I have an understanding of how a GPS should perform. I had an AT&T Tilt which I'd made usable with a Sakajati HyperDragon IV ROM. The GPS in that phone was excellent. The first few days with the Captivate was a real downer. But, the now-functioning GPS makes the Capitvate a keeper.
For those not wanting to try getting a replacement. Plumbobs gps fix worked great for me. Check it out.
Sent from my SGH-I897 Captivate cog 4.3 using Xda app
My Xoom locks on in 4 seconds, indoors, straight out of the box. This whole thing is stupid.
So I've been using my gps for a few days now and it's still working just as well when I got the replacement. IMO there may be 3 types of phones out there which is why we all get different results..
Captivate with working GPS right out of the box
Captivate with 'meh' GPS that is fixable with software tweaks
Captivate with GPS so bad that it doesn't work at all.
This could all be hardware related in just how the manufacturing process worked. Some could have just been bad apples.
Sent from my SAMSUNG-SGH-I897 using XDA App
10 meter lock inless than 20 seconds. Running JVE modem on Continuum v4, and I have a 1008 build number.
Sent from a place my wife doesn't know about
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.
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