Android OS and sensors.qcom - Nexus 5 Q&A, Help & Troubleshooting

In the last weeks, I started to have an issue with "android os" going crazy without reason.
It's happening on WIFI or HPSA+
I noticed that sensors.qcom is always in my list when it is happening. I'm on stock (rooted) and I made a clean reinstallation of the OS a few days ago , and I installed only half of my apps... and the bug is already back ! so I'm trying to find what app is starting this issue (Don't get me wrong, the bug is probably on the google side , however, I'm sure there is an app starting it). Yesterday I uninstalled Greenify (I only had 2 apps greenified) and so far so good ... not sure if it is linked yet.
btw, BBS is no help with this issue.
anyone has the same problem here ?
on this thread, a few people are talking about sensors.qcom : https://productforums.google.com/forum/m/#!msg/nexus/HV2TICIjX9U/WbZ8yOfNBbsJ

Hopefully you figured it out but I just had this issue starting today. BBS didn't help either but for me the fix came when I switched off Lens blur in the camera. I took a picture yesterday and didn't finish editing in after doing a lens blur. Switching it back to regular camera mode fixed my issue. My guess is some app is using one of the physical sensors so try looking there.

Matrix_19 said:
In the last weeks, I started to have an issue with "android os" going crazy without reason.
It's happening on WIFI or HPSA+
I noticed that sensors.qcom is always in my list when it is happening. I'm on stock (rooted) and I made a clean reinstallation of the OS a few days ago , and I installed only half of my apps... and the bug is already back ! so I'm trying to find what app is starting this issue (Don't get me wrong, the bug is probably on the google side , however, I'm sure there is an app starting it). Yesterday I uninstalled Greenify (I only had 2 apps greenified) and so far so good ... not sure if it is linked yet.
btw, BBS is no help with this issue.
anyone has the same problem here ?
on this thread, a few people are talking about sensors.qcom : https://productforums.google.com/forum/m/#!msg/nexus/HV2TICIjX9U/WbZ8yOfNBbsJ
Click to expand...
Click to collapse
This is a big issue on alot of phones with Qualcomm cpus. My suspicion is its a hardware fault more common than people think.. Most people don't notice it especially heavy phone users, it will blend in well with other usage. Another reason is because it can stop by itself sometimes and doesn't happen nonstop. It is random.
Facts I know.
Whenever sensors.qcom shows up in battery stats, it will also be accompanied by high Android OS usage. Battery stats is not accurate, this bug could consume 50% of battery and it might just say 2%.
Check Cpu-z you will see all sensor information is missing.
CPU is constantly running near full speed.
It appears to be completely random, happening mid standby.
It is not caused by any app. I have tried on a completely stock rom.
Check wakelock detector kernel tab, you will see the wakelocks that cause this (there is millions)
You can fix it by restarting phone or enabling/disabling some sensors. Last time I had this happen (yesterday) my phone had lost 25% in 4 hours standby. I stopped it by enabling autobrightness and all sensors information returned in cpu-z along with cpu speed going back to normal. It is not caused by having auto brightness off however, just the toggling of sensors seems to stop it.
See my threads here
http://en.miui.com/thread-87409-1-1.html
http://en.miui.com/thread-63939-1-1.html

Related

Security storage app? Consumes 98% battery

I have the app android booster to monitor battery use. When I go to applications everything is at 1% and 2% but the android process "security storage" is consuming 98% battery? Does anyone know what this is? Is there a way to minimize it or can I freeze it with Titanium Backup?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
I wish I knew as it's killing my battery also, I'm thinking I'll have to reflash or even odin back to stock before I'll get rd of the battery drain caused by secure storage, I found out it's com.android.providers.security that started secure storage but not much else
I see nobody is addressing this issue, or even explaining it. Too bad, as I'm having the same issue. The annoying part is, no matter what kernel I run, the same thing happens: The phone will sit sedately idle until I want to use it, then the minute I try to do something "Security Storage" starts running and the phone becomes non-responsive for 30 seconds to a minute or two while that stupid app is running.
Why can't this app do its maintenance while the phone is idle, rather than the minute the user wants to do something, or be forced into "nice" mode (don't know if Android has such a setting, but it's based on linux and linux does have such a setting) so that it's only allowed to hog the CPU when the phone is idling.
change build prop ro.securestorage to false
ElwOOd_CbGp said:
change build prop ro.securestorage to false
Click to expand...
Click to collapse
I just registered to say THANK YOU to this man. :good:
did it work?
mikim1 said:
I just registered to say THANK YOU to this man. :good:
Click to expand...
Click to collapse
I've noticed a lot of system resources get wasted even after removing the knox apps and enterprise and container agent stuff that comes on samsung phones. I mean, I guess its good as an option to have if you have use for it. Problem is tho, for ppl like me, its also built into the system in order to make those implementations effective and when you install a custom ROM and or kernel it causes errors. I think thats why some people dont like touchwiz ROMs and think theyre laggy. When the kernel and system are not synced anymore, crap goes on in the background that is just a waste. I still dont know much really, but I spent some time trying to fugure out how to disable some loggers and errors that were going on and were pissing me off. Here is a link to a post I ran across that helped shed some light on some stuff. Be careful tho, and if you don't know what your doing, spend some time to learn about what all that stuff does, because it's system stuff and you could find yourself in a bootloop or with an expensive azz brick http://forum.xda-developers.com/showthread.php?t=2599266
ElwOOd_CbGp said:
change build prop ro.securestorage to false
Click to expand...
Click to collapse
interestingly using icyfusion rom and terrasilent kernel, I cannot find this line in my build.prop. anyone else not seeing it there? secure storage is eating up at least 20% constantly of battery/cpu accord to elixir2. My battery drain continues to plague the device and I can only get about 1-2 hours of light use out of it while it continues to drain when screen is off. All I want to do is use it to listen to some tunes and I'm regretting rooting the device now. Refreshing to stock, wiping everything...formatting etc. has no effect. Has anyone solved this problem (presumably related to secure storage?) with another method?
(yp-g1 us version, currently on GB 2.3.5 stock, rooted with terrasilent kernel).
klemmaniac said:
interestingly using icyfusion rom and terrasilent kernel, I cannot find this line in my build.prop..... currently on GB 2.3.5 stock, rooted with terrasilent kernel).
Click to expand...
Click to collapse
have you tried any current builds?
ElwOOd_CbGp said:
have you tried any current builds?
Click to expand...
Click to collapse
I tried CM11 which worked fine for a week or so and then all of the sudden the battery drain problem appeared. I didn't check the build.prop when on that because I decided to reflash to stock and start from scratch trying different roms/kernels. I can't shake the battery drain now no matter what I do - factory reset full wipe, you name it. I guess I could try installing cm11 again and see if it is in the build.prop then?? I just don't know how to proceed at this point.
My suggestion would be to go into developer options and take a look at process stats to see if there are any rogue processes running that you don't need. You can also download and install BetterBatteryStats app from here on XDA or purchase the paid version from the play store so that you can specifically pinpoint what is causing your device problems. Also, older devices often need batteries replaced because they wear out. I don't think the secure storage bug affects AOSP based ROMs since it is related to Samsung's Knox. Another tip would be to use a build prop editor app that has a search function to make finding things easier.
ElwOOd_CbGp said:
My suggestion would be to go into developer options and take a look at process stats to see if there are any rogue processes running that you don't need. You can also download and install BetterBatteryStats app from here on XDA or purchase the paid version from the play store so that you can specifically pinpoint what is causing your device problems. Also, older devices often need batteries replaced because they wear out. I don't think the secure storage bug affects AOSP based ROMs since it is related to Samsung's Knox. Another tip would be to use a build prop editor app that has a search function to make finding things easier.
Click to expand...
Click to collapse
thanks for the suggestions, but it's all similar to what I've already tried. I did use Elixir2 and another battery status app to monitor things, and I have also gone through running process and disabled everything that I don't need. I did order a new battery just to check, but I don't think that's the problem. The top part of the case (where the CPU is running I presume, not the battery) is getting very hot, so there is some problem with a program or service overheating the CPU which in turn drains the battery. I just charged to full today and turned the screen off so that the device will sleep. 2 hours later, it is dead. I checked battery stats in settings and there is no indication that the device wakes while screen is off...I'm just totally at a loss. It's almost like it's a hardware issue maybe caused by a kernel or something like that, rather than an app or service. I just have no idea. Someone in another forum advised me to flash to stock and run a logcat app and post results..so I guess I'll do that. I'm worried though, because I was googling prices for ipod touches earlier today....I don't want to go back to the dark side...but I just want a device that works and I can listen to music for more than 30 minutes too.
klemmaniac said:
thanks for the suggestions, but it's all similar to what I've already tried. I did use Elixir2 and another battery status app to monitor things, and I have also gone through running process and disabled everything that I don't need. I did order a new battery just to check, but I don't think that's the problem. The top part of the case (where the CPU is running I presume, not the battery) is getting very hot, so there is some problem with a program or service overheating the CPU which in turn drains the battery. I just charged to full today and turned the screen off so that the device will sleep. 2 hours later, it is dead. I checked battery stats in settings and there is no indication that the device wakes while screen is off...I'm just totally at a loss. It's almost like it's a hardware issue maybe caused by a kernel or something like that, rather than an app or service. I just have no idea. Someone in another forum advised me to flash to stock and run a logcat app and post results..so I guess I'll do that. I'm worried though, because I was googling prices for ipod touches earlier today....I don't want to go back to the dark side...but I just want a device that works and I can listen to music for more than 30 minutes too.
Click to expand...
Click to collapse
turn gps off
ElwOOd_CbGp said:
turn gps off
Click to expand...
Click to collapse
thanks, but that was one of the first things I turned off. I only want to use the device for music listening and quick browsing/email. I shut off wifi when not using and leave it in airplane mode as well....definitely something internally wrong with the device somewhere that goes beyong changing the usual battery draining settings. Still have the logcat running and the device is making very strange noises I've never heard before...popping, screeching scratchy sounds....very strange...things just seem to be getting worse and I'm worried I'm quickly heading to an expensive paper weight situation... Battery continues to drain at 20% or more/hour with screen off. I think after this if no progress is made,...I may try to unroot the device, but I don't know if that will solve the problem and will undo the damage already done.

[Q] Performance: k3g_wq, what is it?

My Charge has seen decreasing performance. I'm running 2.3.6, the last TBH leak, and I was initially getting Quadrant scores as high as the 1400's. Now, I'm down around 700! Needless to say, the phone has gotten laggy.
I'm using OSMonitor to look at what processes are busy, and I keep seeing k3g_wq running, using anywhere from 20% to just under 40%. Never used to see it before. I figure it's a system process, as if I kill it, it starts back right away and always has the PID of 54.
I've searched here and with Google and I can't find anything about what this process is. From the name, I might guess it has something to do with 3g access, but it's running like that even when I go into airplane mode.
Thanks for any info.
just a suggestion but since GB has officially been released i would wipe cashe,dalvik and data. Then flash infinity, tweak stock or danalo's stock debloated/deoxided rom. Then flash imoseyon's repacked voodoo kernel. you will get a quadrant score of around 2000. Im currently running infinity ext4 without tsm, imoseyon's kernel and v6 script. its been pretty good for me so far. i have no complaints.
But if anybody else has a better setup. I myself would like to know as well
Wow, that's quite a prescription! For now, I'd just like to know what that process is and why it's running, so I can try to get it to back down.
Thanks for the tips. BTW, I was running voodoo lagfix back in the day, and it got me quadrant scores similar to what I was getting with this GB ROM (not 2K, but 1600 wasn't unusual); I'd like to get back to that point. Without necessarily starting over.
You're basically going to have to. The TBH leak is really old.
Sent from my SCH-I510 using xda premium
The TBH leak isn't that old (I downloaded it on Nov 7th), and the age of it doesn't make kernel processes run away. It's GB 2.3.6, basically the same as the latest OTA. And it only started doing this recently.
I'm afraid either something I've installed recently is triggering this (the better option, as I can start uninstalling stuff until the problem goes away), or there is something gone wonky with the hardware itself that the kernel is reacting to (obviously the worst case). That wouldn't surprise me, as this is my 3rd Charge, the first two having had lost their minds, running really hot and then rebooting every few minutes (this on the stock OS, rooted with the voodoo lagfix kernel).
More data (if there's anyone out there who actually knows what that kernel process is): OS Monitor's "messages" list is flooded with this:
"k3g_work_func: fifo entries are less than we want"
I get dozens of these PER SECOND.
Again, if anyone has any insight on what that process is about, glad to hear from you. Those who say "Nuke and pave!", not so much.
Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
"Nuke and pave" still seems like the best option.
Sent from my SCH-I510 using xda premium
kvswim said:
Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
Click to expand...
Click to collapse
Fifo is a general term for a queue -- "first in/first out". Many kernel processes live their lives managing queues. This one is complaining about it's queue being shorter (fewer entries) than it thinks it should have.
Did I see your name attached to a thread about trying to compile a kernel? If so, would you do me a favor, so I don't have to get all into git so I can get to the AOSP code, and grep for "k3g" and/or "k3g_wq" (still sounds to me like like "kernel 3g worker queue") and see if you can see what it does? Nothing in depth, just in general what it handles.
kvswim said:
"Nuke and pave" still seems like the best option.
Click to expand...
Click to collapse
Funny thing happened today. It was getting worse and worse. Battery stats showed a shocking thing--for the first time ever, Display wasn't the biggest battery hog, it was Android OS!
So I decided to just reboot, to see if I could get it back to good enough to do backups and start the nuke-n-pave process. I had rebooted a few times over the last few days, and it didn't solve anything. Today it did! Back to normal, and I ran Quadrant twice and got a 16xx on the second run. Nice. A few hours later, and it's still good. Keeping my fingers crossed.
Oh, I had also uninstalled DropBox (which I wasn't using yet anyway) and this massive Gameloft game, "Tintin". Those didn't help, before reboot. But maybe those, coupled with the reboot, did.
I may still nuke and pave, but probably with the stock GB and just root after that. And keep hoping the CyanogenMod comes out with a ROM for it.
Thanks.
I'm gonna revive this thread because I have a similar problem. My dad's charge is fully stock. He has never messed with anything. It was fine the whole time he had it except today. He has not used it at all today (10m screen time in 12 hours, and half of that was me trying to fix it) and the battery drained down to 30% all by itself. Me being the tech guy, he gave it to me and I checked battery usage. Android OS was reported to be using 89%. Cell standby was at 3%, and display came in last at 2%.
Since "Android OS" is very generic, I used adb to put the xda version of betterbatterystats on his phone, and under process, there is this thing called "k3g_wq" with almost a full bar. Under other, it shows the phone being awake 98.2% of the time. This problem only arose today. As he has not used the phone at all, there would be no rogue apps unless something just turned up. I disabled automatic updates in the market since the stock tunewiki app updated its permissions to read SMS (spyware???).
Does anyone have a solution to this besides factory reset?
K3G is a sensor, specifically the level sensor. Not sure why it would take up system resources, but I would think turning off auto screen rotation may be one method to try and limit its use and battery drain.
See my posts on k3g_wq above. Note that I found error log message about it not having enough entries--thus my supposition that wq == worker queue. If imnuts says it's a level sensor, then that's got to be it; from the name, I figured k was for kernel and 3g was...well...3g.
In my case, I was able to see it using OS Monitor (free in the market), using consistently about 30% of the CPU, which resulted in the OS being the largest consumer of battery.
And, for me, it finally just stopped doing it, after one more reboot. Hasn't come back. But every time the phone gets a bit laggy, I go look at that process list.
On another note, we're using my Charge at work as a test phone for our Android app, as it makes it blow up like no other device we have.
I have noticed a sensor leak associated with google maps. Try opening maps in that phone, exit out of it and see if sensor usage persists. I hadn't mentioned it before assuming it was unique to my device.
Sent from my SCH-I510 using Tapatalk
I also notice runaway usage of k3g_wq in the last week. I have stock OTA EP4 and it had been running fine for many weeks with no issue. So there has to be something that changed recently. My guesses are the new version of Google Maps, or new version of Tiny Flashlight with the "shake on lockscreen" feature. I don't see Tiny Flashlight running any services, but since I disabled the shake on lockscreen feature my k3g_wq usage seems to be OK.
I factory reset the phone and the problem disappeared.
Sent from my pocket-sized, Linux-based computer using electromagnetic radiation.
Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Scrappy1 said:
Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?
xdadevnube said:
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?
Click to expand...
Click to collapse
If you're a geek and have time to flash and mod, that's great for you. I used to be in this camp. Now I just want my phone to work without contanstaintly modifying it, babysitting process and battery life. I want a phone I could recommended to ANY friend or parent without worrying. The Charge definately isn't it.
My brief history in Android:
Samsung Fascinate: got tired of poor battery life and runaway processes.
Samsung Charge: got tired of poor battery life and runaway processed. Also, voice quality is horrendous.
Samsung Galaxy Nexus: Tons of reviews of runaway "Android OS" proccessed during idle. Voice quality is bad and outbound audio drops.
With each generation, problems weren't fixed and Google/Samsung continue their careless ways. To me its just sloppy, sloppy, execution.
Scrappy1 said:
I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.
charlie_c said:
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.
Click to expand...
Click to collapse
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
Scrappy1 said:
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
Click to expand...
Click to collapse
Sorry, thought you were OP
Sent from my SCH-I510 using Tapatalk
k3g_wq ... it came back, and then I killed it, I think
OP here.
Today I was looking at my Charge and marveling at how I was getting pretty good performance but better battery life due to my latest tweaks in SetCPU, when I looked at battery usage: Android OS was creeping up on Display as juice-user No. 1.
Uh oh.
So back to OS Monitor, and sure enough, there's k3g_wq on a steady 25-30% of the CPU.
Opened and closed Maps--no luck.
Killed its process in the process list in OS Monitor (it appeared to be swapped out, but what the heck)--no luck.
Opened another cool app called Elixir that shows you sensors, and lets you enable/disable them. Hrm...gyroscope, rotation and orientation sensors. All were off; turned each on, then back off.
Looked in OS Monitor and...YES! k3g_wq is gone!
Wild guess time, but apparently the start-up/shut-down of whichever sensor it is doesn't always work right, and leaves that service looking for its momma (that's a highly technical description of the problem, sniff).
Anyway, if you're seeing k3g_wq running wild, give that a try. Next time I do, I'll try them one at a time, see which one does the trick (assuming it's only one).
LDog
PS -- Kudos again to imnuts for letting us know it's the level sensor. Or sensors.

MB865 CPU Out of control and Excess Heat

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.

Pixel 3 hangs for 15-30 seconds when switching apps, typing

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.

Android 10 issues/bugs

Since Android 10 dropped, if anyone notices any bugs or issues I figured it would be good to make a thread about them. Been using Android 10 since it dropped, and one issue that I have noticed is my signal is more sloppy and inconsistent which may be a radio issue. I am using Sprint, but the signal has been more spotty and the reception overall has declined.
Biggest issue, battery drained so fast after update. Standby mode eat up more juice compare to Android 9. 9 was giving me 6-7 hrs SOT now it's just about 3-4 hrs SOT. Few apps which were using battery percentage half of it's usage time now using double battery.look like apps are not yet optimized for Android 10.
omky_b4u said:
Biggest issue, battery drained so fast after update. Standby mode eat up more juice compare to Android 9. 9 was giving me 6-7 hrs SOT now it's just about 3-4 hrs SOT. Few apps which were using battery percentage half of it's usage time now using double battery.look like apps are not yet optimized for Android 10.
Click to expand...
Click to collapse
I've had that too, but it's not too significant, and i wouldn't worry about it for the first few days while things optimize but i also noticed slight battery drain.
Been trying to update the signals. The radio is definitely having issues for my carrier.
Pixel 3 in the Call Application, my screen goes black after call in connected and I can't seem to get the screen to become active again until call is over and I hit the power button twice. This just started after an OTA update to 10...
I updated to 10 OTA and since updating my wifi calling isn't working. Whenever I try to toggle it, it just says that it's unavailable and to try again later. I haven't performed a factory reset because it's always such a pain to do that (especially with all the accounts I have using 2FA w/ Google Authenticator).
My cell/data reception has also been significantly decreased, according to my little indicator in the notifications.
Anybody else having these issues?
My reception has always been poor with this phone so I cannot confirm our deny that it's worse on Android 10 stable.
However I ota updated from final beta to stable 10 and my phone randomly goes home while I'm using it. Really annoying when having an app open to have the home screen constantly appear.
Personally I'm having between 2 and 3 hours of SOT, and always had those stats on Android 9 too, for very basic using (no calls, no gaming, no videos, slight browsing, few SMS, etc). Hope battery will be much better for the Pixel 4...
I forgot about this. My phone initially also got stuck on the boot screen. I was like oh great here we go. Apparently it's an issue. Android 10 appears to still be in beta mode despite being released as stable.
https://bgr.com/2019/09/05/android-10-update-for-pixel-phones-sensors-bug-explained/amp/
Unbeliavable, how google tries to force you towards its search engine!! I could probably get used to thr new gestures, but not to that notorious search bar!! There is no reason to block all Launchers from working with gestures. I hope somebody will soon hack that!
you are furthering probably biggest bug of Q (not affecting everyone though, but many people)
https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
As I said in another thread, I have not been able to flash the factory image of either the .019 or .020 firmware. I've been doing the method of running the flash.bat file minus "-w" to prevent it from wiping my phone, using the latest SDK Platform Tools and after trying both they both cause a bootloop. My phone will attempt to boot up 2 different times and fail (assuming once for each partition, A & B?) then go back to fastboot mode.
Considering this other major bug with the sensors now not working, I guess holding off may actually a good thing for me for now.
Toronadian said:
.
Considering this other major bug with the sensors now not working, I guess holding off may actually a good thing for me for now.
Click to expand...
Click to collapse
i would definitively if i were you. not everyone is affected but some are so...
Sensors bug fixed thanks to great teamwork of many members in this forum! Solution available in sensors bug thread!!
Had no issue with sensors but am stock unrooted since the phone was purchased. From that link it appears it may be a rooting issue. I'm surprised that that it didn't go away though after wiping and reflashing stock images and relocking the bootloader
mikeprius said:
Had no issue with sensors but am stock unrooted since the phone was purchased. From that link it appears it may be a rooting issue. I'm surprised that that it didn't go away though after wiping and reflashing stock images and relocking the bootloader
Click to expand...
Click to collapse
still nobody knows what caused it but according to some users it seems it happened also for people who never modified their phones (people with not unlockable bl)
It's weird, this sensor bug everyone is having i never once had sth like that, flashed the official q factory image from beta 6 via the tool-all-in-one app. What i was thinking is, does the phone have different hardware revisions ? I am with the initial rev and can't tell
Gotten at least 3 random reboots since taking. Anyone else getting periodic recent app switching freezing or random reboots?
Hello.
I have the freeze too. Random freezing from the notification. Freezing with the recent app. Sometime black wallpaper with Nova Launcher.
The Q is with bug who don't have the beta or Android 9....
mikeprius said:
Gotten at least 3 random reboots since taking. Anyone else getting periodic recent app switching freezing or random reboots?
Click to expand...
Click to collapse
Yes, I've had a few random reboots since updating. It's been happening randomly in Google maps, YouTube, etc. I don't really want to factory reset unless I have to though.
Hey guys here is an android 10 bug on my Verizon pixel 3, when I goto the recent apps and try to clear them they will all get cleared and then when I go back to it they are all still there. Anyone else having this problem?
Im using google Launcher, and when I change the gestures sometime they all clear for good but sometimes they still won't until I restart the phone.

Categories

Resources