yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] charlie_c:
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.
[Verizon Droid Charge] Scrappy1:
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
[Verizon Droid Charge] charlie_c:
Sorry, thought you were OP :-)
[Verizon Droid Charge] lonndoggie:
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.
[Verizon Droid Charge] letsgophillyingeneral:
I prefer "Format, reinstall."

I would listen to what everyone is telling you and flash a new ROM. That thing is outdated and probably buggy.
[Verizon Droid Charge] JihadSquad:
Factory reset worked for me, and I have never seen it since.
[Verizon Droid Charge] lonndoggie:
I did that already, but thanks (a previous post where I mentioned I was starting that process, I didn't relay that I completed it as well--my bad). And it came back.

Also note the other poster who's getting it with a 100% stock setup.

I listen to what everyone tells me and use my fantastic powers of deduction and reason to whittle the suggestions down to those with and without merit. imnuts' insight that this was related to level sensors was huge, and from a highly respected and knowledgeable source.

Now, as to what triggered this? There was a maps update today. I'd also update tiny flashlight when it got its shake feature, but that didn't seem to cause it.

Dunno. But I seem to now have a weapon to stop it, perhaps. I hope others try the sensor on/off trick to see if it helps them as well.

Data gathering, debugging, sleuthing--I'm happier when I know what the problem is, rather than painting over it.
[Verizon Droid Charge] lonndoggie:
Right, saw your post.

A simple reboot fixed it for me, many posts back. Which was followed by a wipe and fresh install of the current OTA GB release but rooted and with...ah...er...a slightly modded kernel, and yet it came back for me.

I hope yours never comes back--but if it does, please try the sensor on/off thing, see if that stops it, and report back.

Thanks.
[Verizon Droid Charge] nismology:
As an update to my original post, according to the battery history for GB app (the basis of my first post and found here http://xdaforums.com/showthread.php?p=13328125) maps, YouTube, and the camera app continue to register sensor usage even after they are closed in the task manager and even force stopped in the case of YouTube/maps. The usage time isn't steady or realtime either. It's almost as if they are polling the sensor periodically. I urge somebody else to try it and report their findings.

Perhaps this app is registering erroneous readings. It isn't outside the realm of possibility but I just thought I'd update my findings.
[Verizon Droid Charge] Scrappy1:
Thanks for the info on Elixir lonndoggie. I'll try it if I get stuck again.

My recent data point is that I disabled auto rotation and rebooted, never to turn it on again. I hoped I'd be free of k3g_wq forever.. but nope. After a couple days it came back. So leaving auto rotation off doest prevent it.
[Verizon Droid Charge] Scrappy1:
It's the gyroscope! I confirmed this on my phone and my wife's phone. Using Elixir 2 I toggled on/off all other sensors, and nothing killed k3g_wq except gyroscope.

Now how do we find the process that starts k3g_wq on it's downward spiral?
[Verizon Droid Charge] lonndoggie:
I found the same thing tonight!

And I've got a hunch what triggered it, and likely triggered the last one, too: Today I got an update of Tiny Flashlight (the one that recently added a "shake in lock screen to turn on flashlight" feature). It's been discussed as a possible culprit, but for whatever reason, I didn't think to check for k3g_wq right after--but later I happened to look, and and there it was, running away.

So, like you, I went into Elixir, and figured "hrm...level, must be gyroscope", toggled it, and k3g_wq stopped.

Did you and/or your wife get any market updates today? I don't know why an app update would trigger that, but it seems like it might be.
[Verizon Droid Charge] lonndoggie:
I installed the app you linked to (thanks for that), but it's not showing much in the sensor usage display--after having killed the gyroscope (see preceding post), it showed Elixir in the mix, but with no blue bar showing, since it had the 'scope in use for only a few seconds. Other than that, it showed Touchdown (my exchange client) and the Android System itself (which is what the installed battery history shows as using a lot of CPU when this problem shows up). Unfortunately, it doesn't say which sensor, but in my case anyway, it doesn't seem to be the map or camera.

However, an update to maps might do it, if the triggered-by-update theory is correct.
[Verizon Droid Charge] Scrappy1:
One more finding: I plugged my phone in at 11 pm last night and k3g_wq wasn't active. However in the morning it was again stuck at 40% cpu usage. I have SystemPanel running always so looking back in time at k3g_wq usage I see it spiked to about 40% usage at 3am and just stayed there. The important point is that when the problem started the phone was sleeping, no applications running, only stock background services. Something must be enabling gyroscope in the background and not disabling.
[Verizon Droid Charge] lonndoggie:
Yeah, k3g_wq kicked in for me again this morning, with no discernible reason as to why (and gyroscope on/off killed it, too).

Also, last night I tried restoring an old version of Tiny Flashlight I had in TIBU, then upgrading again in the market--no k3g_wq for that, so it appears that was a red herring.

I'm thinking I need to upgrade to the paid version of SystemPanel so I can start tracking CPU usage history as well.
[Verizon Droid Charge] Scrappy1:
The 3am starting of 40% k3g_wq happened on both my phone and my wife's phone. She has SystemPanel but not tiny flashlight, so I think we can rule out tiny flashlight. I'm starting to suspect the new version of Maps. I'll watch what happens tonight.
[Verizon Droid Charge] Scrappy1:
OK this is no coincidence... at exactly 3am again last night k3g_wq jumped to 40% CPU usage and stayed there. According to SystemPanel at exactly the same time the google maps NetworkLocationService showed a blip of activity, but was quiet everywhere else. Now I strongly suspect maps. I'm also guessing disabling Google location services in settings will prevent this issue, just as it prevented all kinds of weird battery drain on the Samsung Fascinate.
[Verizon Droid Charge] lonndoggie:
I got the paid version of SystemPanel and turned on logging as well. And, sure enough, at 3AM, Android OS's CPU usage went up, and drilling down, there is k3g_wq. Opened OSMonitor, and there it is, doing its thing. So it would appear we have the same trigger for the problem.

It took a few tries to kill it via the on-off gyro sensor thing in Elixir today. But at least it did work. BTW, did you notice that, if you go look at the info for the gyroscope sensor in Elixir, the proper name of it is K3G Gyroscope Sensor?

I was looking at what else got logged as far as activity, and hard to figure what it might have been. I did see that the Amazon App Store had a tiny blip at about that same time, so I froze it with TIBU; we'll see if that does anything.
[Verizon Droid Charge] Scrappy1:
Last night I disabled Google location services and had no issues with k3g_wq getting stuck at 40% CPU at 3am.

I'll test again tonight.
[Verizon Droid Charge] Cilraaz:
Thank you guys for your work in trying to figure this out. I've also been seeing k3g_wq using a bunch of CPU in the mornings, though I can't say exactly when it starts. Thanks also for mentioning Elixir. That's been much quicker of a temporary fix for the issue, rather than doing a full reboot. Keep any info you find coming, and if you need a third party to try anything, please let me know.
[Verizon Droid Charge] lonndoggie:
To follow up:

It appears that I'm getting k3g_wq firing up every morning at 3AM now.

Stopping Amazon App Store didn't help (I didn't think it would).

Scrappy1, nicely done with the auto-rotation off thing! I'll try that tonight.

In a somewhat related note, after seeing k3g_wq running again this AM, and after having had trouble getting it to stop with the sensor on/off in Elixir, I decided this time to just toggle thru it a couple of times in Elixir from the get-go. That worked...but auto-rotation was also turned off at that point. Odd.

I wish we could triangulate on what the common element is for all of us that's causing this. What's happening at 3AM?

Also, I wonder how many people are wondering why their Charge is sluggish and with such poor battery performance, having no idea that this is happening. Sad, that.
[Verizon Droid Charge] Scrappy1:
OK, its looking very strongly like the k3g_wq issue is being caused by Google location services. For the second night in a row I left Google location service disabled, and had no k3g_wq issues in the morning and no history of it in SystemPanel.

My wife's phone left Google location services enabled and did have k3g_wq stuck at 40% CPU both nights starting at 3am.

There were a couple Google maps updates in the last few weeks. I'm guessing one of these introduced the location services problem, because we never saw this issue in the past.
[Verizon Droid Charge] Cilraaz:
I woke up to k3g_wq run amok again this morning. I'll add to your sample size by disabling Google location services and see how it is tomorrow morning.
[Verizon Droid Charge] lonndoggie:
Today, k3g_wq was not running for me. Google location services were turned on, however; I did have auto rotation turned off, though.

Looking at the SystemPanel logs, I do see a tiny spike for k3g_wq at 3am--but only that. So it was invoked, but behaved properly and shut down as well.
[Verizon Droid Charge] Cilraaz:
I have not had k3g_wq go out of control since disabling Google Location Services. So far, so good!
[Verizon Droid Charge] bgorrell:
Same problem

I started noticing performance problems and severe battery drain in the last week as well. One day it dropped 60% in just a few hours at work, untouched. Most days it has to be on the charger. Not normal for me. So, I just found the k3g messages others had mentioned in OS Monitor today, which led me to this thread. I did not see a K3G_WQ process running, but Android System was taking up 40% of CPU time and I had the messages as mentioned.

Other similarities are that Google maps recently updated and I had Google Location Services turned on (always had been). So, I turned off Google Location Services and ran elixir to start and stop the gyroscope. That did not stop the messages immediately, but after a reboot they are gone. I did turn on Verizon Location Services in Google's place. Is it a viable substitute for Google's service? Never quite understood that. Anyways, I'll check in the morning to see if the K3G messages come back.

My initial impression is the Google Maps or some other update is using Google's Location Services differently than before, causing the sudden problem. I wonder how widespread this is. As others mentioned, people may be experiencing this and not even realize it. In fact, my wife's phone (completely stock), has had similar problems since I installed a bunch of app updates last week. I'll check tonight to see if it's the same issue. If we can nail down the root cause, maybe we can get a fix. Disabling Google Location Services is just a workaround.
[Verizon Droid Charge] kvswim:
Just to clarify things:

Standalone GPS: gets actual GPS signal from satellites to phone. Slowest and most powerful consumed, but also the most accurate

Google Location: gets position from wifi locations, aka "wardriving". Quick and accurate with little power draw, but only if you are in an area with high wifi density, like NYC. Otherwise kind of useless.

Verizon Location: triangulates location based on cell towers. Least power draw and quick to lock, but inaccurate.
[Verizon Droid Charge] bgorrell:
Thanks for the explanation kvswim. Makes sense.

Checked my phone this morning and the k3g messages have not come back. Looks like it is not an issue with Verizon location services.

Wifi is not dense in my area, so it seems Verizon location service is my best choice anyway.
[Verizon Droid Charge] Cilraaz:
2 weeks later. I still haven't had a single instance of k3g_wq eating CPU since disabling Google Location Services. Seems like that's the trick.
[Verizon Droid Charge] lonndoggie:
In the settings for OS Monitor, there is a checkbox to show system processes; by default, that's off. Check it and if it's k3g_wq, you'll see it.

I've found that I sometimes need to start and stop gyroscope a few times. What I evolved to is start gyroscope, wait about 5 seconds, and repeat--twice. That seemed to have always killed it. No reboot required. Note that it typically shows up in OS Monitor for a refresh or two, then goes away.

Disabling Google Location Services is just a workaround.[/QUOTE]

I hope you guys figure it out. I tried with all location services off, and it didn't seem to help. Then again, there are some mornings when k3g_wq wasn't running (regardless of location settings)--but in System Panel's monitoring output, I could see that little blip for it at 3AM, so it started, but shut down successfully.

I've moved on--got a Rezound. Sooooo much faster, and so far stable, but the Sense UI is...well, senseless.
[Verizon Droid Charge] psychic99:
Killing my battery again

Folks,

Well I have been killing items using my battery and even got the extended battery so that I can go an entire day without charging, and keeping it in 3G. I've installed TS 1.4 w/ PBJ kernel, no FS mods and while it is better than stock, the RAM in this beast is just not adequate. In any case I can't wait to get rid of this POS however until I can find a way to do that I need to actually use it.

So in the last week, I have been out and about and k3g_wq on three separate occasions has rampaged my phone. This AM I noticed it began AFTER Google Maps update to 3.6.0, and rebooted to clear.

I did have GLS on (I dont like that because they track my location) to help because the Charge GPS is so weak, but I toggle it only to use nav now.

I dont have any other Gyro programs running, so when my pocket got hot I pulled it it said Google Maps update complete, and BBS tells me this process is wiping out my battery.

So I have (on my phone) figured that Goog Maps is the bad actor and this is with GLS off, so it seems there is just some bug with that sensor on this phone and for some reason Goog Maps is triggering it. For me it only seems to be a problem when Google Maps is used, however I cannot be 100% sure.

I had flashed this clean (ODIN), as well as partitions so IMHO this is a problem. Now this Charge is a refurb from Verizon since I went through 3 Thunderbolts and they couldnt fix my 4G LTE issues.

Now my wifes OV using CM7-- this $100 phone is just ROCK SOLID, except for VM sucky network, I haven't rebooted the thing in a month and after all day the battery only goes down 20%. With stock the battery would last 7 hours.

So it would be interesting to know if you guys are seeing the issue w/ new phones or refurbed.
[Verizon Droid Charge] kynalvarus:
This thread has helped me figure out why I was having to reboot my Droid Charge so often in order to get reasonable performance back - thanks!

Just curious, has this issue been reported to Google and/or Samsung? Perhaps a fix in Google Location Services could be patched in?
[Verizon Droid Charge] kynalvarus:
I posted a link into the Google Maps product forum, but XDA has noob-filtered me, so I can't share it. Hopefully this can get turned into an official bug report.
[Verizon Droid Charge] psychic99:
Google Maps 3.6.0

With the new update of Google Maps this weekend, I have tried to coerce it into causing sensor runaway. I have tried it w/ GLS on and off, and done navigation and maps.

I unplugged my phone @ 7 AM today and it is 12PM, and the battery (extended) is a 95% which is great considering the alternatives.

I will check in if I see this pop up again, but so far so good. In the past doing any of these activities would cause the sensor to drain the battery.

GM says 6.4.0 on my about so maybe I got the version wrong.
[Verizon Droid Charge] Scrappy1:
It appears the new FP1 OTA ROM is a solid fix for the k3g_wq issue. After several nights of leaving Google location services on, I haven't had any runaway k3g_wq process usage.
[Verizon Droid Charge] psychic99:
since the goog maps update a week or so ago it hasnt come back once. Def a bug in maps. I can leave gls on no problem, but I dont due to google spying and battery drain. It was taking 20% of my partial wakelocks...

My gps.conf fix now gets me going in under 10 sec now, so gls may only be useful in a building...
[HTC Flyer, EVO View 4G] loni90:
I got my view just the otherday, but soon realised that there is no sim-card slot on this baby.. looked it up, and yes... Sprint doesent have sims..

Is there anyway I can use this baby gal as a phone? Or at lease connect to 3g?

The last one is more interesting...
[HTC Flyer, EVO View 4G] globatron:
No, no way.
[HTC Flyer, EVO View 4G] loni90:
Damn...was hoping to get it to work...

Another question then...

How do I make it more international? It's too much tailored to US. I can't even change to Swedish keyboard or time?!
[HTC Flyer, EVO View 4G] N_ine:
With a quick market search, I found this.

https://market.android.com/details?...guagepack.swedish&feature=search_result&hl=en

Supposed to be paired with this: https://market.android.com/details?...vbS5tZW5ueS5hbmRyb2lkLmFueXNvZnRrZXlib2FyZCJd

Oh and I also found this: https://market.android.com/details?...vbS5hbmRyb2lkLmlucHV0bWV0aG9kLm5vcndlZ2lhbiJd

Have your pick.
[HTC Flyer, EVO View 4G] loni90:
Thanks a lot. I was more thinking of a HTC stock keyboard, but hey... I guess its better than nothing ;)
[HTC Flyer, EVO View 4G] loni90:
I would thank you, but don't know how to thru the app. (For now I will use my browser to do that ;) )
[HTC Flyer, EVO View 4G] raed81:
U can use it as aphone if u r connected to wifi then use google voice with groove ip app to make calls... Or u can use viber with wifi too
[Desire HD Q&A, Help & Troubleshooting] Fain11:
Little question on ER3BUS XL2.2.5

To JSL, great job with this ROM.

Just one problem, I setup powersaving at 15%, and when the battery arrived at that point, the powersaving profile didn’t kick in.

No lower brightness, no animations off, no vibration off, no Wi-Fi off, yet they were checked in powersaving menu.

The ROM is clean, no TBKP restore, only tweaks applied are your contacts fix and the full GPU rendering explained by mike1981 and hamdir.

I posted here, as I’m a noob and I can’t post in developer thread.

Thanks
[Desire HD Q&A, Help & Troubleshooting] Wolf:
Check your power mode settings. They should be something like high performance, normal, economy. Switch this to economy and it should work.
[Desire HD Q&A, Help & Troubleshooting] Fain11:
Thanks Ronin_2 for the reply, there is no such option in this ROM. Yet, in the “power” menu the power saver option was checked (turn on to reduce power consumption), which should be the economy profile you mentioned.
[Desire HD Q&A, Help & Troubleshooting] Fain11:
Could someone mention this to JSL?

Thanks in advance!

And by the way Happy New Year to all XDA developers and members! :)
[Desire HD Q&A, Help & Troubleshooting] shithead:
Already did that. I think it's a bug indeed, but he will release a new rom tomorrow. The next version uses a new base. Maybe it's fixed
[Desire HD Q&A, Help & Troubleshooting] JSLEnterprises:
that was when still on 1.05 as a base, 1.11 doesnt have it.

@ OP: It should have popped up a notice. If you dismissed it, it'll continue as normal, if you clicked the button that allows it to go to power save mode, it will do this. I have mine set to 20% and it works fine.

But tomorrow (or later today, depending on where you are in the world) I'll be releasing v3.0 based on 1.22 which also will fix a few issues there was with 1.11, and because of the nature of 1.22, arabic is already present in the rom, and I've also included zh_tw, which I bleieve is Thai.

But as of right now, I'm off to get my new years party on. T-minus 3 hours and 14 minutes. Happy New Years Everyone! :)
[Desire HD Q&A, Help & Troubleshooting] Fain11:
Thank you all for the replys.

@ JSL – The notice popped up, I pressed ok, yet powersaving did not kicked in.

Now I installed ER3BUS XL3.0 :D, thank you for the release.

I will reply after my battery drains.
[Desire HD Q&A, Help & Troubleshooting] Fain11:
Well finally my battery arrived at 15 %, the notice popped up, I pressed ok, yet still nothing happened.

I tried flashing “Er3BuS_3.x_Stock_framework-res”, same result as above.
[Galaxy Tab 10.1 General] WebbyHRT:
I'm new to samsung and I'm not having much luck finding out about generic firmware. Is there a global generic or an australian generic firmware?

My model number is GT-P7500

Baseband P7500XXKI1

Build HMJ37 p7500CEKI1
[Galaxy Tab 10.1 General] SaneinOne:
The build indicated is your carrier's stock ROM.
[Galaxy Tab 10.1 General] WebbyHRT:
I was hoping that there were generic stock roms. Carrier firmware is full of bloatware and they lag on rolling out updates.
[Galaxy Tab 10.1 General] SaneinOne:
Root and then delete any unnecessary apk files from system/app directory. Latest is stock is KL3.