Related
My Charge has seen decreasing performance. I'm running 2.3.6, the last TBH leak, and I was initially getting Quadrant scores as high as the 1400's. Now, I'm down around 700! Needless to say, the phone has gotten laggy.
I'm using OSMonitor to look at what processes are busy, and I keep seeing k3g_wq running, using anywhere from 20% to just under 40%. Never used to see it before. I figure it's a system process, as if I kill it, it starts back right away and always has the PID of 54.
I've searched here and with Google and I can't find anything about what this process is. From the name, I might guess it has something to do with 3g access, but it's running like that even when I go into airplane mode.
Thanks for any info.
just a suggestion but since GB has officially been released i would wipe cashe,dalvik and data. Then flash infinity, tweak stock or danalo's stock debloated/deoxided rom. Then flash imoseyon's repacked voodoo kernel. you will get a quadrant score of around 2000. Im currently running infinity ext4 without tsm, imoseyon's kernel and v6 script. its been pretty good for me so far. i have no complaints.
But if anybody else has a better setup. I myself would like to know as well
Wow, that's quite a prescription! For now, I'd just like to know what that process is and why it's running, so I can try to get it to back down.
Thanks for the tips. BTW, I was running voodoo lagfix back in the day, and it got me quadrant scores similar to what I was getting with this GB ROM (not 2K, but 1600 wasn't unusual); I'd like to get back to that point. Without necessarily starting over.
You're basically going to have to. The TBH leak is really old.
Sent from my SCH-I510 using xda premium
The TBH leak isn't that old (I downloaded it on Nov 7th), and the age of it doesn't make kernel processes run away. It's GB 2.3.6, basically the same as the latest OTA. And it only started doing this recently.
I'm afraid either something I've installed recently is triggering this (the better option, as I can start uninstalling stuff until the problem goes away), or there is something gone wonky with the hardware itself that the kernel is reacting to (obviously the worst case). That wouldn't surprise me, as this is my 3rd Charge, the first two having had lost their minds, running really hot and then rebooting every few minutes (this on the stock OS, rooted with the voodoo lagfix kernel).
More data (if there's anyone out there who actually knows what that kernel process is): OS Monitor's "messages" list is flooded with this:
"k3g_work_func: fifo entries are less than we want"
I get dozens of these PER SECOND.
Again, if anyone has any insight on what that process is about, glad to hear from you. Those who say "Nuke and pave!", not so much.
Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
"Nuke and pave" still seems like the best option.
Sent from my SCH-I510 using xda premium
kvswim said:
Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
Click to expand...
Click to collapse
Fifo is a general term for a queue -- "first in/first out". Many kernel processes live their lives managing queues. This one is complaining about it's queue being shorter (fewer entries) than it thinks it should have.
Did I see your name attached to a thread about trying to compile a kernel? If so, would you do me a favor, so I don't have to get all into git so I can get to the AOSP code, and grep for "k3g" and/or "k3g_wq" (still sounds to me like like "kernel 3g worker queue") and see if you can see what it does? Nothing in depth, just in general what it handles.
kvswim said:
"Nuke and pave" still seems like the best option.
Click to expand...
Click to collapse
Funny thing happened today. It was getting worse and worse. Battery stats showed a shocking thing--for the first time ever, Display wasn't the biggest battery hog, it was Android OS!
So I decided to just reboot, to see if I could get it back to good enough to do backups and start the nuke-n-pave process. I had rebooted a few times over the last few days, and it didn't solve anything. Today it did! Back to normal, and I ran Quadrant twice and got a 16xx on the second run. Nice. A few hours later, and it's still good. Keeping my fingers crossed.
Oh, I had also uninstalled DropBox (which I wasn't using yet anyway) and this massive Gameloft game, "Tintin". Those didn't help, before reboot. But maybe those, coupled with the reboot, did.
I may still nuke and pave, but probably with the stock GB and just root after that. And keep hoping the CyanogenMod comes out with a ROM for it.
Thanks.
I'm gonna revive this thread because I have a similar problem. My dad's charge is fully stock. He has never messed with anything. It was fine the whole time he had it except today. He has not used it at all today (10m screen time in 12 hours, and half of that was me trying to fix it) and the battery drained down to 30% all by itself. Me being the tech guy, he gave it to me and I checked battery usage. Android OS was reported to be using 89%. Cell standby was at 3%, and display came in last at 2%.
Since "Android OS" is very generic, I used adb to put the xda version of betterbatterystats on his phone, and under process, there is this thing called "k3g_wq" with almost a full bar. Under other, it shows the phone being awake 98.2% of the time. This problem only arose today. As he has not used the phone at all, there would be no rogue apps unless something just turned up. I disabled automatic updates in the market since the stock tunewiki app updated its permissions to read SMS (spyware???).
Does anyone have a solution to this besides factory reset?
K3G is a sensor, specifically the level sensor. Not sure why it would take up system resources, but I would think turning off auto screen rotation may be one method to try and limit its use and battery drain.
See my posts on k3g_wq above. Note that I found error log message about it not having enough entries--thus my supposition that wq == worker queue. If imnuts says it's a level sensor, then that's got to be it; from the name, I figured k was for kernel and 3g was...well...3g.
In my case, I was able to see it using OS Monitor (free in the market), using consistently about 30% of the CPU, which resulted in the OS being the largest consumer of battery.
And, for me, it finally just stopped doing it, after one more reboot. Hasn't come back. But every time the phone gets a bit laggy, I go look at that process list.
On another note, we're using my Charge at work as a test phone for our Android app, as it makes it blow up like no other device we have.
I have noticed a sensor leak associated with google maps. Try opening maps in that phone, exit out of it and see if sensor usage persists. I hadn't mentioned it before assuming it was unique to my device.
Sent from my SCH-I510 using Tapatalk
I also notice runaway usage of k3g_wq in the last week. I have stock OTA EP4 and it had been running fine for many weeks with no issue. So there has to be something that changed recently. My guesses are the new version of Google Maps, or new version of Tiny Flashlight with the "shake on lockscreen" feature. I don't see Tiny Flashlight running any services, but since I disabled the shake on lockscreen feature my k3g_wq usage seems to be OK.
I factory reset the phone and the problem disappeared.
Sent from my pocket-sized, Linux-based computer using electromagnetic radiation.
Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Scrappy1 said:
Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?
xdadevnube said:
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?
Click to expand...
Click to collapse
If you're a geek and have time to flash and mod, that's great for you. I used to be in this camp. Now I just want my phone to work without contanstaintly modifying it, babysitting process and battery life. I want a phone I could recommended to ANY friend or parent without worrying. The Charge definately isn't it.
My brief history in Android:
Samsung Fascinate: got tired of poor battery life and runaway processes.
Samsung Charge: got tired of poor battery life and runaway processed. Also, voice quality is horrendous.
Samsung Galaxy Nexus: Tons of reviews of runaway "Android OS" proccessed during idle. Voice quality is bad and outbound audio drops.
With each generation, problems weren't fixed and Google/Samsung continue their careless ways. To me its just sloppy, sloppy, execution.
Scrappy1 said:
I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.
charlie_c said:
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.
Click to expand...
Click to collapse
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
Scrappy1 said:
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
Click to expand...
Click to collapse
Sorry, thought you were OP
Sent from my SCH-I510 using Tapatalk
k3g_wq ... it came back, and then I killed it, I think
OP here.
Today I was looking at my Charge and marveling at how I was getting pretty good performance but better battery life due to my latest tweaks in SetCPU, when I looked at battery usage: Android OS was creeping up on Display as juice-user No. 1.
Uh oh.
So back to OS Monitor, and sure enough, there's k3g_wq on a steady 25-30% of the CPU.
Opened and closed Maps--no luck.
Killed its process in the process list in OS Monitor (it appeared to be swapped out, but what the heck)--no luck.
Opened another cool app called Elixir that shows you sensors, and lets you enable/disable them. Hrm...gyroscope, rotation and orientation sensors. All were off; turned each on, then back off.
Looked in OS Monitor and...YES! k3g_wq is gone!
Wild guess time, but apparently the start-up/shut-down of whichever sensor it is doesn't always work right, and leaves that service looking for its momma (that's a highly technical description of the problem, sniff).
Anyway, if you're seeing k3g_wq running wild, give that a try. Next time I do, I'll try them one at a time, see which one does the trick (assuming it's only one).
LDog
PS -- Kudos again to imnuts for letting us know it's the level sensor. Or sensors.
Has anybody else had the issue of an out of control CPU?
Using the stock Task Manager, CPU usage is reported almost at 99% at times... but I get nothing to indicate usage out of the ordinary using Watchdog or other third party task managers. I am honestly at a loss for words at this point, as I can never pinpoint exactly what app is causing trouble. One minute my phone will be fine, and the next its 109 degrees with CPU being reported at 99% or 100%.
Has anybody else had luck in fixing issues like this? This is probably the second Atrix 2 I have received from AT&T, and it doesn't appear to be a hardware issue.
Sent from my MB865 using XDA
I was actually having a similar issue a while back, and keep in mind I never exchanged my original handset.
On stock rom, my phone would freeze up, and begin to get really hot. I would have to remove the battery to restart the phone. Now I'm a creeper user and I've been lurking the forums since I bought this phone. I've seen tons of posts about it. The strangest thing was that it was sporadic, it would happen twice in one day, then it wouldn't happen for a month, and would suddenly happen out of nowhere, completely random times of the day. Your problem sounds similar, pretty much exactly what was happening to me except mine would freeze, you're probably catching it before it freezes. I wouldn't notice it as I don't constantly handle my phone it usually sits for at least an hour or two at a time. The 'freezing' may have been a temperature failsafe. I had luck restoring the phone to factory, but would occasionally still occur, the last I had the factory rom on it, it didn't happen for 2 months, at which point I installed a custom rom.
I read lots of replies to saying that it was probably a hardware defect, but I can assure it is not. Definitely on the software side of things.
Anyways, way too long of a post I know, try restoring to factory from the recovery partition.
Tim-7967 said:
Has anybody else had the issue of an out of control CPU?
Using the stock Task Manager, CPU usage is reported almost at 99% at times... but I get nothing to indicate usage out of the ordinary using Watchdog or other third party task managers. I am honestly at a loss for words at this point, as I can never pinpoint exactly what app is causing trouble. One minute my phone will be fine, and the next its 109 degrees with CPU being reported at 99% or 100%.
Has anybody else had luck in fixing issues like this? This is probably the second Atrix 2 I have received from AT&T, and it doesn't appear to be a hardware issue.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Ok, now this is going to sound odd, and it is, it is also a real pain in the rear, but it is the ONLY way to figure it out.
Issue is that there is an app that you have installed, that you most likely always use, and install on your phone, that does not play nice.
How to fix this:
1) Trouble shooting:
remove ALL of your installed NON-stock apps, one at a time, and check your CPU usage and heat before and after each uninstalled app, when it goes away, it is most likely the last app that you uninstalled.
2) After finding that bad app, do NOT re-install it, report your issue to the developer.
3) Find an app that is similar, and does the same thing, and try a few out, but don't re-install the suspect app until the dev has fixed the issue.
Hi all...first time poster, long time reader. (Mostly because someone has usually solved my problem for me six months in advance.)
My Inspire has been rebooting at random for about the last six months. The rate varies from once every couple of days to once every couple of hourse. Most of the existing answers are "replace the battery." I think that makes sense in cases where phones reboot while under strain (watching a video, during a call, etc.) because higher current draw would pull down voltage if a battery is failing. Not in my case, though. About 80% of the time that I notice a reboot, the phone is either in a pocket or on the desk.
For a few days I thought that I had solved it by removing the Facebook app. I had noticed a correlation between using Facebook at the phone restarting, and not using Facebook really did seem to make a difference for about a week. (Upon further investigation, that seems to hold across different ROMS. This has been happening with the stock rom, Ice Cold Sandwitch, and JellyTime.) But it isn't 100% better. I currently get about one reset every two days that I notice, and probably more that I don't notice.
That leaves me wondering, what could be going on? Is my hardware borked? Should I try flashing a different radio? I have had this phone for about 22 months and it would be nice to hold onto it a little while longer. Otherwise it has been a reasonably decent device.
-Tim
ZircularLogic said:
Hi all...first time poster, long time reader. (Mostly because someone has usually solved my problem for me six months in advance.)
My Inspire has been rebooting at random for about the last six months. The rate varies from once every couple of days to once every couple of hourse. Most of the existing answers are "replace the battery." I think that makes sense in cases where phones reboot while under strain (watching a video, during a call, etc.) because higher current draw would pull down voltage if a battery is failing. Not in my case, though. About 80% of the time that I notice a reboot, the phone is either in a pocket or on the desk.
For a few days I thought that I had solved it by removing the Facebook app. I had noticed a correlation between using Facebook at the phone restarting, and not using Facebook really did seem to make a difference for about a week. (Upon further investigation, that seems to hold across different ROMS. This has been happening with the stock rom, Ice Cold Sandwitch, and JellyTime.) But it isn't 100% better. I currently get about one reset every two days that I notice, and probably more that I don't notice.
That leaves me wondering, what could be going on? Is my hardware borked? Should I try flashing a different radio? I have had this phone for about 22 months and it would be nice to hold onto it a little while longer. Otherwise it has been a reasonably decent device.
-Tim
Click to expand...
Click to collapse
Tim, random reboots can occur due to lack of memory. See if your internal memory is almost full. In that case, try deleting some apps or sending a couple to he sdcard. Take into consideration, that not all apps work fine from the sdcard, so just send the ones you like less...BTW, are you rooted or just stock?
glevitan said:
Tim, random reboots can occur due to lack of memory. See if your internal memory is almost full. In that case, try deleting some apps or sending a couple to he sdcard. Take into consideration, that not all apps work fine from the sdcard, so just send the ones you like less...BTW, are you rooted or just stock?
Click to expand...
Click to collapse
That's an explanation I had not found. Internal storage looks OK in my case, with 701MB currently available out of 1.13GB. If it matters, the SD card currently shows 3.86GB avaliable out of 7.39GB. (I have tried with and without the SD card, and it doesn't seem to matter.) Maybe I should increase the free memory setting?
To answer your question, the phone is currently rooted and running IceColdSandwich 8.8 AOKP. If anything it reboots less frequently in the current configuration than it did on the stock ROM. I have not tried any Jellybean ROMs for more than a day at a time, so I'm not sure if that would be better.
ZircularLogic said:
That's an explanation I had not found. Internal storage looks OK in my case, with 701MB currently available out of 1.13GB. If it matters, the SD card currently shows 3.86GB avaliable out of 7.39GB. (I have tried with and without the SD card, and it doesn't seem to matter.) Maybe I should increase the free memory setting?
To answer your question, the phone is currently rooted and running IceColdSandwich 8.8 AOKP. If anything it reboots less frequently in the current configuration than it did on the stock ROM. I have not tried any Jellybean ROMs for more than a day at a time, so I'm not sure if that would be better.
Click to expand...
Click to collapse
Sounds to me like your hardware is bad. I have had my Inspire 4g for two years and the only issues I have had was maybe three apps force closing. I have never had the phone its self freeze or reboot. I have tried all kinds of ROMS and right now I have 4 regulars I stay with and alternated monthly. I Use Energy, Revolution, Smart Droid Red venom edition, and JB 10.1. All those ROMS are stable and cause no issues as you have described.
So from a tech view if I had your issues and it happens with all ROMS then that leaves only the hardware to be at fault.
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.
I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.
hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again
What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.
ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.
Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.
hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x
I have the same frustrating issue
Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)
I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.
This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.
I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...
HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!
The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version
I know there are memory management issues with this phone; what I'm not sure though is if the behavior I'm experiencing is just a manifestation of this well-known problem or another issue.
Since I got the phone a month ago, after some period of use after rebooting, simple actions like switching between two apps can cause the phone to hang for a long time - usually 20 or 30 seconds. The phone isn't completely hung - I can still go back to the home screen, and do some things, but whatever app I tried to switch to will be non-responsive for this whole time. Eventually, it will just start working again.
Other times, typing using the google keyboard will get stuck - that is, I can still type, but nothing shows up in the field where the text should appear. After a while it will suddenly "catch up" and everything I typed appears.
These two issues both seem to start happening around the same time, so it seems memory use related, but the amount of time involved seems very excessive for swapping.
I can fix this just by rebooting, but it always comes back after a while. I suspect it's related to how many different apps I've loaded and not just time of use, though, since sometimes it won't happen for a day or two, but it always happens again at some point.
I removed a bunch of apps that were migrated from my old phone (a Motorola Z Force), too, to try to eliminate a badly-behaving app, but I never had any issues like this on that phone, and it didn't make any difference.
Is anyone else experiencing this? Or does it sound like a possible hardware problem? I don't want to swap the phone unless it's clear this is abnormal behavior. Thanks.
It's abnormal behavior. My first thought is it might be related to a balky network or intermittent connection. Just a wild guess. Do you see the same issue in airplane mode? Also, if you check battery or cpu usage is anything hogging resources?
samnada said:
It's abnormal behavior. My first thought is it might be related to a balky network or intermittent connection. Just a wild guess. Do you see the same issue in airplane mode? Also, if you check battery or cpu usage is anything hogging resources?
Click to expand...
Click to collapse
I've used the phone in exactly the same circumstances as my prior phone (and other devices) so I don't think it has to do with network connectivity; but next time it happens I'll try switching to airplane mode just to be sure. There's no visual indication of a network drop (e.g. wifi status icon). I haven't checked for anything hogging resources during these events, and generally I'm not having any battery life or performance problems. It's just switching apps that brings everything to a standstill for a while, and then it works fine again.
jamtre said:
I've used the phone in exactly the same circumstances as my prior phone (and other devices) so I don't think it has to do with network connectivity; but next time it happens I'll try switching to airplane mode just to be sure. There's no visual indication of a network drop (e.g. wifi status icon). I haven't checked for anything hogging resources during these events, and generally I'm not having any battery life or performance problems. It's just switching apps that brings everything to a standstill for a while, and then it works fine again.
Click to expand...
Click to collapse
Maybe check the temp when it's stalling. This app might show something: https://play.google.com/store/apps/details?id=com.glgjing.stark&hl=en_US
I have the exact same issue as OP describes.
Had a 64gb Pixel 3 when it was first released and it manifested the issue with the random hangs and freezes. I decided it was too buggy and returned it.
A month later got a 128gb Pixel 3 on the gift card promo and it is exhibiting the same issue as the OP and my original 64gb unit.
Doubtful it is a hardware issue since this is my second one with the same issue.
I have tried factory reset and removing any un-necessary programs on both, but the condition still persists.
Both phones were on Fi.
If the January patch does not fix the issue it will be time to switch back to iPhone.
mrchuckfl said:
I have the exact same issue as OP describes.
Had a 64gb Pixel 3 when it was first released and it manifested the issue with the random hangs and freezes. I decided it was too buggy and returned it.
A month later got a 128gb Pixel 3 on the gift card promo and it is exhibiting the same issue as the OP and my original 64gb unit.
Doubtful it is a hardware issue since this is my second one with the same issue.
I have tried factory reset and removing any un-necessary programs on both, but the condition still persists.
Both phones were on Fi.
If the January patch does not fix the issue it will be time to switch back to iPhone.
Click to expand...
Click to collapse
Mine's 128gb (Verizon). The January patch looks trivial so not expecting any change here...
Not going to switch to iPhone but troubling that you have had this with two different phones. At the same time, pp seemed to think this is not typical behavior, and if it's a common OS issue then wouldn't a lot of people be talking about it? I'm not a crazy power user or anything, I never play games, pretty much use Waze, whatsapp, camera, facebook (lite), spotify, etc... really pretty standard apps.
I wonder if there's something unique to us that could be involved here? I'm not using any apps I wasn't using on my old phone, but I also had Oreo before and not Pie, so not a direct comparison. When I first set up my phone, though, all my old apps were migrated, including some Verizon bloatware I couldn't delete from the old phone. Is it possible that apps that were automatically migrated (but later deleted) could have left something behind that's causing issues with PIe?
jamtre said:
Mine's 128gb (Verizon). The January patch looks trivial so not expecting any change here...
Not going to switch to iPhone but troubling that you have had this with two different phones. At the same time, pp seemed to think this is not typical behavior, and if it's a common OS issue then wouldn't a lot of people be talking about it? I'm not a crazy power user or anything, I never play games, pretty much use Waze, whatsapp, camera, facebook (lite), spotify, etc... really pretty standard apps.
I wonder if there's something unique to us that could be involved here? I'm not using any apps I wasn't using on my old phone, but I also had Oreo before and not Pie, so not a direct comparison. When I first set up my phone, though, all my old apps were migrated, including some Verizon bloatware I couldn't delete from the old phone. Is it possible that apps that were automatically migrated (but later deleted) could have left something behind that's causing issues with PIe?
Click to expand...
Click to collapse
I have have been on Google phones since Nexus 4 and upgrading like a good consumer every year.
Like yourself I am not doing anything crazy and have the run of the mill stuff like FB, Snap, kik, Whatsapp and IG. The only thing out of the ordinary I have on the phone is Cerberus and BlackBerry email.
Apps don't get migrated so that is not the issue. When you setup a new phone or transfer, some of the data is moved, but the app is re-downloaded from the app store.
mrchuckfl said:
I have the exact same issue as OP describes.
Apps don't get migrated so that is not the issue. When you setup a new phone or transfer, some of the data is moved, but the app is re-downloaded from the app store.
Click to expand...
Click to collapse
Right - but it installed -everything- I had on my old phone including some Motorola & Verizon apps, which I then uninstalled (but maybe even missed some). Just thinking it might be possible that something hardware-specific to my old phone got installed on the pixel. In theory shouldn't matter but there seem to be so many nuances to Android, particularly across major releases, that I wondered if this could have been involved in the problem.
Anecdotally, it seems like it's been happening less often over time. I haven't had it happen in a few days, though I installed the update yesterday so I'm within 24 hrs of a clean boot now.
jamtre said:
Right - but it installed -everything- I had on my old phone including some Motorola & Verizon apps, which I then uninstalled (but maybe even missed some). Just thinking it might be possible that something hardware-specific to my old phone got installed on the pixel. In theory shouldn't matter but there seem to be so many nuances to Android, particularly across major releases, that I wondered if this could have been involved in the problem.
Anecdotally, it seems like it's been happening less often over time. I haven't had it happen in a few days, though I installed the update yesterday so I'm within 24 hrs of a clean boot now.
Click to expand...
Click to collapse
I've been having exactly the same issues for the last couple of days. Have just done a factory reset but the problem persists. The biggest issue is that when the phone is locked it seems to freeze as well and takes about 15-20 secs to unlock. Also if you phone it while its locked (and frozen) the incoming call isn't acknowledged (no ringing !) until after its unfrozen. Looks like I may have to return it and get a different phone !
Mike
More than a few people have been having issues with their Pixel 3, but I've yet to experience a single issue with memory management or slowdowns. In fact, I've found the Pixel 3 to be a far smoother UI than the iPhone X on the newest versions of iOS. Maybe I got lucky, but I'm more inclined to think it's about use. Just like my desktop operating system, I start from scratch every time I do a reformat, reset, or upgrade of a device. I can see there being issues with migrating old data. I'm also a fairly light app user; I've got around 100 apps in my drawer, most of which are Google apps or banking apps. Are the people experiencing these slowdowns installing a lot of things or running more resource intensive apps like Facebook? Not to say you shouldn't be able to do that with your phone, but I'm curious how behavior differs in our situations.
Feb update?
OP here, so more than a week since the February update landed and I have not had this happen since then. I'm kind of shocked, honestly, and keep waiting for the other shoe to drop, but so far it looks like something they did fixed this.
The only other significant change I made was to uninstall the Facebook Lite app, a few days ago, but I've used that long before I had a Pixel 3 so doubt it's related. So... :fingers-crossed:!!
jamtre said:
OP here, so more than a week since the February update landed and I have not had this happen since then. I'm kind of shocked, honestly, and keep waiting for the other shoe to drop, but so far it looks like something they did fixed this.
The only other significant change I made was to uninstall the Facebook Lite app, a few days ago, but I've used that long before I had a Pixel 3 so doubt it's related. So... :fingers-crossed:!!
Click to expand...
Click to collapse
Maybe I should give Pixel 3 a try. Tried P3 twice since October and it was a phenomenal laggy mess specially under load ... My Pixel 2 had its ups and downs, specially with the Pie release. Took them 3-4 months to 'get it right' so I'd expect Pixel 3 to be no different.
I was experiencing some lag and short freeze (2 to 7/8 seconds) with my pixel after the latest update.
I tried a factory reset with little hope but it seems it did the trick for me. No issues ever since.