Related
Hey guys. I'm a new T-Mobile customer with an HTC MyTouch4G Slide (or the Doubleshot if you prefer). I came from Sprint with a Samsung Epic 4G.
For the most part, I love my doubleshot (even if I miss the screen size of the Epic), but I've been experiencing something weird. Every couple of days my phone will just randomly reset of its own accord.
I exchange the phone after the first few times this happened, and the second few. This is my third straight Doubleshot now, and I thought I was in the clear until it hard reset last night without me asking it to.
Relevant info: this has occurred with phones that were both S-ON and S-OFF, rooted and unrooted, stock ROM and with ROMs made by both CK23 and Undead.
Is anyone else experiencing this with their Doubleshot, and do you have any suggestions on fixing it? It's not a major dilemma, more of an annoyance, but I figure it's a $600 phone - it shouldn't do crap like that.
Never had or even heard of anyone else with this issue. How do you carry your phone, in your pocket with other kinds of electrical devices?
Just throwing random stuff out there because I've never head of this (not saying it cant happen)
If I'm out and about it's in my pocket with absolutely nothing else. No keys, no coins, no other gadgets. I'm a bit paranoid about keeping my screen as scratch free as possible (yes, I have a screen protector).
If I'm not out, it sits on my desk near a couple of Acer monitors and two small Sony satellite speakers for my computer.
Do you think the magnets on those speakers could be affecting your phone? I remember on older TVs if you kept speakers next to it, it would distort colors and picture
Not likely. The magnetic drivers in these satellites are tiny to begin with. My phone isn't that close to them, and there are few, if any, parts inside a phone like this which are susceptible to weak magnetic interference.
Seeing as how this hasn't really happened to any others, here's some ideas:
Are you running modaco recovery 4.0.0.9?
Since it has happened to you on several phones, do you think it could be software related? Maybe there's something which is running process(es) in the background which are causing your phone to freeze up and become unresponsive at which point it simply resets itself.
Yes, as to MoDaCo Recovery 4.0.0.9. It's entirely possible the problem could be software related, but I can't think of anything that would be consistently running on my phone to cause the problem.
I have a rather strong addiction to the built in task killer and tend to open it and run a "kill all" any time I'm done using my phone to ensure memory is already free for whatever game/ap I intend to run when I start up again.
GoodKingNerdnor said:
Yes, as to MoDaCo Recovery 4.0.0.9. It's entirely possible the problem could be software related, but I can't think of anything that would be consistently running on my phone to cause the problem.
I have a rather strong addiction to the built in task killer and tend to open it and run a "kill all" any time I'm done using my phone to ensure memory is already free for whatever game/ap I intend to run when I start up again.
Click to expand...
Click to collapse
That might be the problem right there. Try not doing that.
Task killers are a no go.
Sent from my MyTouch 4G Slide using xda premium
That doesn't make a lot of sense though. One, this is the one built into Android, so I can't imagine it hurts anything. Two, why are the resets seemingly random? This particular phone has only done it once, that I've noticed. The previous phones did it damn near every hour in some instances, a few times a day in others.
They don't appear to have any correlation to task killing.
OP, maybe you're really pressing the phone's limits with intensive use. Have you noticed that the phone and battery becoming hot after even 10 min or so of gaming/surfing/texting,etc? Perhaps the battery is overheating, which causes these random reboots. It's only a guess though...
Oh and I hate how the battery gets so hot. Anyone else experiencing this dilemma? My previous Android phone's battery didn't become nearly as hot as the MT4GS's.
No the task killer is only to kill sense items and basic apps. HTC added it not Google.
Sent from my MyTouch 4G Slide using xda premium
I am having the hot battery issue too. Even with the Anker 19 mah battery... I swear it actually could cook something. My boyfriend has the same phone, and it doesn't happen to his.
Sent from my myTouch_4G_Slide using XDA App
Anthonayy, nope. Not really. I can go more than a day without needing to recharge with my usage pattern. I am not a heavy user.
Undeadk9, even if the task killer is only to kill sense items and basic apps, I'm not using it to kill anything besides that. Also, my use of the task killer has shown no apparent correlation to the rebooting. The reboots are seemingly random. Typically they occur when I am *not* using the phone. I'll look over and all of a sudden, boop! My phone is resetting itself. It might happen far more often than I think, but I've only witnessed it one time with the current phone.
I may have over-exagerated my use of it before. I typically just use the task killer before I open a memory intensive game (like Asphalt) because the games tend not to run right if I try to open them without enough available RAM (big shock).
Seconded.
I have not rooted and run a stock mt4gs and have had this happen once every 3-7 days. Again sometimes I am using it and sometimes not. No apparent cause.
I did just chalk it up to a bad out of memory error, and the device just resets as a failsafe.
In re: to hot batteries the Anker has been a big win in that area. It will heat up once in a while but not nearly as much. I have had the reset occur with both batteries (OEM and Anker). Also the reset is not a problem just a minor annoyance.
I haven't ever experienced a hot battery. On my G2 and wifes Glacier both got hot batteries big time.
Sent from my MyTouch 4G Slide using xda premium
rdrrlabs said:
Seconded.
I have not rooted and run a stock mt4gs and have had this happen once every 3-7 days. Again sometimes I am using it and sometimes not. No apparent cause.
I did just chalk it up to a bad out of memory error, and the device just resets as a failsafe.
In re: to hot batteries the Anker has been a big win in that area. It will heat up once in a while but not nearly as much. I have had the reset occur with both batteries (OEM and Anker). Also the reset is not a problem just a minor annoyance.
Click to expand...
Click to collapse
+1
@ first I thought it was a rom problem, then I remembered it happened once with stock.
To anyone having reset issues. You need to do a warranty exchange. That is not a known issue with this device. Rooted or not.
Sent from my MyTouch 4G Slide using xda premium
Sense has started to reset itself recently for me. Kinda sucks...
Sent from my myTouch_4G_Slide using XDA Premium App
jonathan3579 said:
Sense has started to reset itself recently for me. Kinda sucks...
Sent from my myTouch_4G_Slide using XDA Premium App
Click to expand...
Click to collapse
"Sense" as in HTC Sense or the actual phone?
We're talking about the phone resetting, if the Sense interface is rebooting, we got another issue. lol
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.
Allright, i've owned my Sensation for several weeks now. Today, i sent a text, and as soon as i went back to the home menu, the phone turned itself off, and rebooted. It was a pi**-off, for sure, and now im worried.
I've done some research, and apparently (correct me if im wrong) it's because of too much RAM usage. However, i set the phone to notify me when free RAM is less than 50MB, and it never did. It just pulled an auto-reboot on me.
Should i worry about this? Is it normal; basically 100% guaranteed that it is because of low RAM?
Which leads me to this: I ALWAYS questioned all the things i had running at the same time. That's probably the only thing i don't like about the phone. Things start automatically. I have an EQ program, Groove IP, and the Music Player running at the same time. I don't understand why the phone won't just close apps if they aren't in use... Or at least if there was a more streamlined way of closing apps. Not going into Settings,Apps,Manage Apps, Running... That's pretty stupid, if you ask me... If there are alternate/better methods, i'd like to know them.
Back to the point, though. Should i worry about this reboot? And, what exactly is the cause/is it RAM usage?
Do not worry unless it becomes a persistant problem.
And even then do not worry because it can probably be fixed as long as its a software issue and not a hardware problem.
And free ram isnt a big deal with android. If you use it, you will use up all your ram quickly. But android will kick things not in active use out of ram when apps in use need more ram. Having free ram is actually a waste.
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Oh, ok...If it's a one-time thing, then i won't worry about it. However, i'd still like to know the cause of it.
Why does this happen?
Did your phone feel warm or hot when it switched off?
Okay, this thing about RAM is one of the biggest misconceptions I think a lot of people have regarding Android. Android doesn't use RAM like Windows. On Android, RAM usage is a good thing. It means that when you want to reload an application, it does it quickly. In other words, RAM unused is just RAM wasted on Android. And the other thing is, apps running in the background do not consume resources unless they also have background processes running as well. The other thing is that Android will automatically kill off certain processes when your RAM is low. So yea. You don't have to worry about RAM.
If you're worried about the crap that comes preinstalled with the phone, you might want to consider rooting and removing all those apps though.
Prenihility said:
Oh, ok...If it's a one-time thing, then i won't worry about it. However, i'd still like to know the cause of it.
Why does this happen?
Click to expand...
Click to collapse
Are you using an app killer to monitor your free ram?
That could easily be the cause. Sometimes those app killers will kill the wrong things and force a reboot.
You're better off dumping apps killers altogether. They work counter productively to the way Linux operates.
Yeah, i kill processes/apps in the settings menu, don't use any downloaded/third party apps for that purpose.
I guess i'll stop doing that...
HOWEVER, i still don't like how, for example, once i sign into Groove IP for the first time, it will stay signed in. Every consecutive time i go to use the phone again, it signs in automatically... After it wakes up from sleep mode, it will sign into Groove IP, and load things like the EQ program i use. I won't worry too much about the EQ, but other apps like Groove IP that are connected to some sort of signal, i don't want automatically running... Is it really not safe to just terminate a process in task manager?
Finally, on to the subject of reboots...Since owning the phone for...I don't know...A few weeks now? I've only actually turned it off/rebooted once...
Did that contribute to the random reboot? Was that not a good move, on my part, to pretty much always keep the phone on (although in sleep mode when not in use, of course...) ?
Prenihility said:
Finally, on to the subject of reboots...Since owning the phone for...I don't know...A few weeks now? I've only actually turned it off/rebooted once...
Did that contribute to the random reboot? Was that not a good move, on my part, to pretty much always keep the phone on (although in sleep mode when not in use, of course...) ?
Click to expand...
Click to collapse
Yeah it could have. Try reboot the day every week at the bare minimum. Ideally, I'd suggest rebooting every 4 days or so.
Prenihility said:
Yeah, i kill processes/apps in the settings menu, don't use any downloaded/third party apps for that purpose.
I guess i'll stop doing that...
HOWEVER, i still don't like how, for example, once i sign into Groove IP for the first time, it will stay signed in. Every consecutive time i go to use the phone again, it signs in automatically... After it wakes up from sleep mode, it will sign into Groove IP, and load things like the EQ program i use. I won't worry too much about the EQ, but other apps like Groove IP that are connected to some sort of signal, i don't want automatically running... Is it really not safe to just terminate a process in task manager?
Click to expand...
Click to collapse
If you are manually killing an app that's causing problems / pissing you off / or because you just don't like it's face, then no. That's okay. It's the automated app killers that kill everything as soon as you close them and then keep killing and killing like battle droids gone berserk that you want to avoid. It's that constant killing, which means an app restart and power usage, that will drain battery. And being unmonitored they can kill the wrong things that cause system instability.
But if you have 1 app that's bothering you you can kill it through the apps menu. That's normal.
The bigger problem is an app that constantly turns itself on like that. I hate those. There should be an option in the app settings to prevent that from happening. If there isn't, it's a bad app no matter how well it does what it's supposed to do.
You can use gemini app manager to change autorun settings for each app individually and autokiller memory optimizer to change the preset android memory limits so your phone automatically closes apps itself a little bit sooner.
Both are free apps but require root.
Gemini is really good. Certain apps start just because you received a text or plugged your usb in. Or your signal changed. I put a stop to that straight away!! Just don't change the settings for system apps.
sent from my Sensation XE
Happened again... Alright, im being irritated by this restarting problem... My phone was just idle, i haven't touched it for hours. It was next to me on my desk, and i heard/felt the vibration upon restart.
Should i call my service provider for a replacement? This is ridiculous... I didn't get this thing expecting it to restart on me.
Prenihility said:
Happened again... Alright, im being irritated by this restarting problem... My phone was just idle, i haven't touched it for hours. It was next to me on my desk, and i heard/felt the vibration upon restart.
Should i call my service provider for a replacement? This is ridiculous... I didn't get this thing expecting it to restart on me.
Click to expand...
Click to collapse
They are going to make you go through a lot of TS steps that you can do prior to calling them.
Have you downloaded any apps recently, say just before you had the problem the first time. It could be the fault of a buggy app, (Usually not likely, but is possible). Are you rooted or fully stock?
As for the Groove ID - look in settings, there may be a way to stop the auto sign in. Just an idea, I don't use it.
I'm not having anymore problems with Groove IP auto sign in. The "lite" version of the app doesn't have the option to disable it, anyway. I just don't run it, unless i need to use it.
This is the second or third time it's restarted. I believe it's the second time, since the 23rd of April, when i created this thread.
As far as rooted or not rooted, i'm not sure what that means. I think it's in regards to the SD card. No, i haven't messed around with it. It's stock. Other than adding some music to the phone. Nothing has been messed around with.
I'm really annoyed by the fact that this happened AGAIN during idle/sleep mode. I wasn't even using the phone. It was just sitting there. It's quite irritating.
Anyhow. What are all the possibilities of the reboots? I'm starting to think it's not lack of memory. Supposedly the RAM-related issue is Sense restarting because of lack of RAM.
The phone vibrates, and the HTC logo comes up, and finally comes to the Home screen.
The only good news, really, in the end, is that it's only happened a couple of times in such a long span of time... I seriously hope i get this figured out, and it never happens again. Or else i'm getting a replacement, for piece of mind, and as a solution.
Prenihility said:
I'm not having anymore problems with Groove IP auto sign in. The "lite" version of the app doesn't have the option to disable it, anyway. I just don't run it, unless i need to use it.
This is the second or third time it's restarted. I believe it's the second time, since the 23rd of April, when i created this thread.
As far as rooted or not rooted, i'm not sure what that means. I think it's in regards to the SD card. No, i haven't messed around with it. It's stock. Other than adding some music to the phone. Nothing has been messed around with.
I'm really annoyed by the fact that this happened AGAIN during idle/sleep mode. I wasn't even using the phone. It was just sitting there. It's quite irritating.
Anyhow. What are all the possibilities of the reboots? I'm starting to think it's not lack of memory. Supposedly the RAM-related issue is Sense restarting because of lack of RAM.
The phone vibrates, and the HTC logo comes up, and finally comes to the Home screen.
The only good news, really, in the end, is that it's only happened a couple of times in such a long span of time... I seriously hope i get this figured out, and it never happens again. Or else i'm getting a replacement, for piece of mind, and as a solution.
Click to expand...
Click to collapse
Referring back to my previous question, did you install any apps prior to the first reboot?
l2icky said:
Referring back to my previous question, did you install any apps prior to the first reboot?
Click to expand...
Click to collapse
Oops. Forgot, sorry... Uuuummmm... Either the Equalizer App, or Groove IP. The only ones i've downloaded. Although im leaning more towards Groove IP (doesn't start up anymore though; because i don't want it to. Never launched it).
Regardless, are you saying i should uninstall it?
Also, one thing i want to add, that i find a bit strange. If i restart the phone, the display brightness will be noticeably brighter than what i actually set it to. It's almost as if i have to remind the phone of the brightness level i set in display options. All i have to do is go to the brightness setting, and touch the slider.
Is this normal behaviour? For it to be brighter upon startup? (even when reaching the home screen/whilst the main UI, past HTC logo screen)
Prenihility said:
Oops. Forgot, sorry... Uuuummmm... Either the Equalizer App, or Groove IP. The only ones i've downloaded. Although im leaning more towards Groove IP (doesn't start up anymore though; because i don't want it to. Never launched it).
Regardless, are you saying i should uninstall it?
Also, one thing i want to add, that i find a bit strange. If i restart the phone, the display brightness will be noticeably brighter than what i actually set it to. It's almost as if i have to remind the phone of the brightness level i set in display options. All i have to do is go to the brightness setting, and touch the slider.
Is this normal behaviour? For it to be brighter upon startup? (even when reaching the home screen/whilst the main UI, past HTC logo screen)
Click to expand...
Click to collapse
It's a possibility that the app is causing the problem, though it is a small one. You might uninstall it and try it for a while, see if the device continues to reboot.
As far as your quirky brightness issue... It's technology. No two devices are the same, even if they have the "same" hardware/software. That almost seems like a fluke happenstance. Just a minor bug in your software.
You might want to read into S-Offing your phone and rooting it. Do some research into it. There are a lot of perks of rooting your device and going with custom ROMs. And if you ever have issues and have to get a replacement, as long as you can turn the device on and it's functional, you can always set it back to S-On with no root.
I've learned over the years, and this is just my personal opinion, stock ROMs are more likely and it seems as if they are meant to have more problems, however it's like anything else in the tech world, it's bound to deteriorate over time. It's how they keep you buying their product.
There are some really good guides that lead through the process step for step if you decide to S-off and root. And there are a lot of helpful people on XDA that will answer any of your questions.
l2icky said:
It's a possibility that the app is causing the problem, though it is a small one. You might uninstall it and try it for a while, see if the device continues to reboot.
As far as your quirky brightness issue... It's technology. No two devices are the same, even if they have the "same" hardware/software. That almost seems like a fluke happenstance. Just a minor bug in your software.
You might want to read into S-Offing your phone and rooting it. Do some research into it. There are a lot of perks of rooting your device and going with custom ROMs. And if you ever have issues and have to get a replacement, as long as you can turn the device on and it's functional, you can always set it back to S-On with no root.
I've learned over the years, and this is just my personal opinion, stock ROMs are more likely and it seems as if they are meant to have more problems, however it's like anything else in the tech world, it's bound to deteriorate over time. It's how they keep you buying their product.
There are some really good guides that lead through the process step for step if you decide to S-off and root. And there are a lot of helpful people on XDA that will answer any of your questions.
Click to expand...
Click to collapse
Allright. Went to grab my phone just now, and saw the error notification. The old "abnormal reset" notification.
I'm going to assume it reset on its own once again. So....
Any insight into this? Why's is reseting itself? Hasn't happened in a while... but... still.
It was just sitting there, idling.
My phone is dropping the framerate on touching the screen occasionally, stuttering for a short time. It is fine again after rebooting, but I am facing this problem since I got the phone three weeks ago. Does anyone else experience this? Is there a solution? I am worried this could be a hardware defect.
Try to reinstall the ROM. You can install full ROM without losing data. If that doesn't help, try a clean install.
Yes I see it too. In fact I started a thread on this in Q&A section but nobody seems to be interested
Nothing I seem to do in terms of tweaking the performance parameters seems to help. It can be fine for half an hour and then out of nowhere a few frames are dropped and it looks awful
It's ok 98% of the time but those 2% are making it hard for me to love this phone.
Lownita said:
My phone is dropping the framerate on touching the screen occasionally, stuttering for a short time. It is fine again after rebooting, but I am facing this problem since I got the phone three weeks ago. Does anyone else experience this? Is there a solution? I am worried this could be a hardware defect.
Click to expand...
Click to collapse
It sounds like a rogue app is taking control of your phone. I checked your Profile GPU rendering screenshot against mine, and indeed, mine never goes much higher above one-half length of the green line, which I think may be the 120fps limit (the green line itself is 16ms or 60fps.)
Seems to me that you need to uninstall some custom/rare apps to troubleshoot this issue.
It is definitely not normal behavior.
carlos67 said:
Yes I see it too. In fact I started a thread on this in Q&A section but nobody seems to be interested
Nothing I seem to do in terms of tweaking the performance parameters seems to help. It can be fine for half an hour and then out of nowhere a few frames are dropped and it looks awful
It's ok 98% of the time but those 2% are making it hard for me to love this phone.
Click to expand...
Click to collapse
So my guess is that either people don't notice it, but I think that's quite impossible as even some kernel devs told me they wouldn't experience this. Or it's a fault in oos itself. Or we are using an app or some setting that's causing this. Or it's a kind of defect, which I think is unlikely but not impossible.
I am about to reset the phone completely to stock with msm download tool and start from scratch. Have you already done something similar?
Next idea would be flashing Omni ROM as I believe this is one of the most clean and fluid custom roms. If all of this fails, I would start to believe it's a hardware problem.
Lownita said:
I am about to reset the phone completely to stock with msm download tool and start from scratch. Have you already done something similar?
Click to expand...
Click to collapse
I would suggest you learn adb/ fastboot to do this so you learn to know what, how and why you doing this and that.
Not really difficult but extremly helpful if you face problems.
The large amount of applications and internet uses it may slow. Better cleared all caches and it's working properly.
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.