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 there,
I have my One Plus since a few month ago, this holiday (NYE) I went to the beach, and I realized the phone was getting slower over the time.
As I returned to my city, I made some test and it's definitely slower, the keyboard is lagging a lot, it can't even keep with my writing speed, some letters are misspressed without me touching them, etc.
I did a factory reset, but the problem persisted.
I booted up in CM Recovery, deleted media, cache and data, and installed everything again, and the problem is still there, keyboard is lagging as hell and the phone is not as fast as it was.
I tried using Antutu Benchmark but it runs normally and the score is the same as it was before.
I used the performance profile but it keeps lagging.
Is there a way in which my phone could have been damaged by the heat or the sun in the beach? Or maybe some sand? It is really annoying that I cant even type fast because it will miss like 10% of letters I use.
Need some advice.
Regards,
DCastro555
Try changing the keyboard
See what the temperature of CPU or GPU is. It might have been throttling due to high thermal temperature
Sent From Lollipopified Bacon Goodness!
Aayush_goel said:
Try changing the keyboard
Click to expand...
Click to collapse
Tried it, its a bit better but still slow. The weird thing is that it sometimes works good for a few minutes, and then slows again. Its random... But most of time is useless...
Try flashing a custom rom
Hi everyone,
I was thrilled last night when my X3 Pro showed an upgrade to Android 12-based MIUI 13 was available. I downloaded the thing (all 3.1 GB of it...), install went without a hitch, ditto reboot, but I'm severely disappointed so far.
Everything feels slow and sluggish, even with the power slider set to Performance and the screen refresh rate pegged at 120 Hz.
Navigation in the Settings menu is OK, but all the other applications are slow to react. Scrolling up and down my Twitter timeline doesn't feel as snappy as it did before, when I was still on MIUI 12.x and Android 11.
Have any of you noticed the same thing? Did Xiaomi jump the gun with this update? I know Android must rebuild some system and application caches after each upgrade and all, but still, this doesn't quite feel right.
The only good thing is the battery life, which seems to have improved a bit, but that's all. DevCheck shows CPU peaks at 2.4 GHz under strain, but the Kryo core that's supposed to clock at 2.9 GHz never seems to wake up.
Did Xiaomi underclock the CPU the way Samsung does sometimes, to preserve battery life? Like I said, something's not right here...
Why do you even MIUI in the first place ?
I had the same. Only the factory reset showed the miui13 claw on Android 12. Tetaz everything runs smoothly. The battery holds up better.
I'm not inclined to do that just now. I've got tons of music and stuff on my phone and I really don't have the time at the moment, but push come to shove, maybe I'll have to do it.
jarco1 said:
Should i factory reset broh my miui updater was not working and everytime it was downloading corrupted zip so i downloaded it from the web with exact same name of the zip file from xiaomi server and updated in miui additional update.
Click to expand...
Click to collapse
Just updated my X3 Pro about an hour ago and I'm totally disappointed. It feels heavier and slower to respond overall. Apps like Twitter, Telegram, and Instagram seem much slower and laggy and stutter when scrolling. Twitter in particular runs like disaster. My phone was buttery smooth and did not have any lagging issue even when I tried to create one before this stupid update!!! Should I factory reset or wait for another update or something guys?
omidsr said:
Just updated my X3 Pro about an hour ago and I'm totally disappointed. It feels heavier and slower to respond overall. Apps like Twitter, Telegram, and Instagram seem much slower and laggy and stutter when scrolling. Twitter in particular runs like disaster. My phone was buttery smooth and did not have any lagging issue even when I tried to create one before this stupid update!!! Should I factory reset or wait for another update or something guys?
Click to expand...
Click to collapse
Mine is slowly getting there, in terms of ease of use and overall smoothness, so I suppose it's a matter of Android reconstructing apps and system caches after all. It's not quite as smooth as it was under 12.5.9, though, and some "features" are mildly annoying, like the fact that I have to tap the Return to home button twice to actually close some apps (but not all of them). It's hard to tell if the app itself is causing this or if it's an Android 12 trait.
UglyStuff said:
Mine is slowly getting there, in terms of ease of use and overall smoothness, so I suppose it's a matter of Android reconstructing apps and system caches after all. It's not quite as smooth as it was under 12.5.9, though, and some "features" are mildly annoying, like the fact that I have to tap the Return to home button twice to actually close some apps (but not all of them). It's hard to tell if the app itself is causing this or if it's an Android 12 trait.
Click to expand...
Click to collapse
I'm also seeing some improvements over time! Totally agree with you! It's getting better as things get reconstructed and stuff but STILL it feels slower than the snappy phone it was before the update. Seems we need to be patient! I don't think a factory reset is worth the time and hassle now that things are showing signs of getting back to normal.
I totally agree. I resort to factory reset only when necessary, with a gun to my head and a knife to my throat...
Let's give it a week or so and we'll see; After all, it's a big upgrade: new MIUI version + moving from Android 11 to Android 12.
Time will tell, but I'm relieved to see it's not my imagination if the phone feels slower!
UglyStuff said:
I totally agree. I resort to factory reset only when necessary, with a gun to my head and a knife to my throat...
Let's give it a week or so and we'll see; After all, it's a big upgrade: new MIUI version + moving from Android 11 to Android 12.
Time will tell, but I'm relieved to see it's not my imagination if the phone feels slower!
Click to expand...
Click to collapse
Agreed! Yup, it definitely is slower to my eyes too. It's no imagination. Sure, it's a BIG update and many enhancements and fixes are to follow in the near future!
Everyone decides for himself what he wants to do. I just wrote that after the update, the phone was stuttering and restoring the factory settings made it run faster and smoother as on miui 12.5.9.0 and it heats up less
Its 2022 and people still dont get that its good to do any major updates on clean phone or do factory reset to remove any issues, official or not, its just how android work really :/
People always had such issues and they probably will have them in the future.
Its not like your life depend on getting new software, so just update later when you have some free time to do clean install or do factory reset.
It remind me of installing custom ROMs when you get feeling that its smoother. Well most of that speed came from having clean system, and after month or two you loose some of it. Here you have clooged system with your stuff and app cache, and you throw on top new OS... you will get some issues...
You guys should know that it is highly recommended to reset during a major Android update if you don't then don't be surprised by weird bugs.
its the common rule,when you are updating any rom on any device,its proper to factory reset and built from then.....i believe its a dirty installation even if you factory reset-install rom-restore data from recovery....even that it will give you some errors....noticed last time with a11,restored from backup ,and the time between restarts,is way to more.....
I have the same problem. I updated it on March 16 (Wednesday) and it's obviously buggy and slow. Google discover on the home screen was so unstable I had to remove it altogether. Phone lags in being unlocked by fingerprint, and locking it with two taps is done without any animation. Gallery is un-usable too as it's become to slow and it stutters. The game boost slider in games is un-usable as it interferes with the game so I've disabled it. I am NOT happy with this upgrade.
Battery might've improved but I suspect they've sacrificed the performance.
just install a custom rom
John1337 said:
I have the same problem. I updated it on March 16 (Wednesday) and it's obviously buggy and slow. Google discover on the home screen was so unstable I had to remove it altogether. Phone lags in being unlocked by fingerprint, and locking it with two taps is done without any animation. Gallery is un-usable too as it's become to slow and it stutters. The game boost slider in games is un-usable as it interferes with the game so I've disabled it. I am NOT happy with this upgrade.
Battery might've improved but I suspect they've sacrificed the performance.
Click to expand...
Click to collapse
You can read. After all, many people wrote that after such a large update, and even more so, switching from android 11 to 12, it is advisable to do a factory reset and you will not have any problems. The fluidity will increase significantly and the battery will hold better. It's so hard to understand. The same is done when installing a custom rom.
jarco1 said:
You can read. After all, many people wrote that after such a large update, and even more so, switching from android 11 to 12, it is advisable to do a factory reset and you will not have any problems. The fluidity will increase significantly and the battery will hold better. It's so hard to understand. The same is done when installing a custom rom.
Click to expand...
Click to collapse
Maybe work on your grammar and semantics first, and then talk about things being difficult to understand. It's common knowledge that a factory-reset is advisable after an upgrade, and it's not like you're imparting arcane knowledge by saying a factory-reset should be done. What is being discussed here are bugs encountered after an upgrade, and since it's android 12 it's expected that a factory reset shouldn't be needed.
Check your attitude, no one asked for help.
In my opinion, Miui's overall optimization on this phone is a disaster. In one year they haven't been able to correct the Google Discover's tremendous lag yet (I think they haven't even tried to). I have done a totally clean installation of Miui 13 Android 12 via fastboot (using miflash). I must say that the optimization now is even worse than it was before the update. The phone just feels slower. Of course we can use custom roms, but it is Xiaomi's responsability to do a much better work with their software.
I hid the notification and I will not update for a long time until I know that there are improvements to something, since the beta I read that the version has problems :/