I loaded it up and used it for about 3 mins or so (gpu force is on). I could feel the phone starting to get hot and about that time my screen went black (which has done this before) so I pulled the battery out which usually fixed previous issues. Well this time everything would boot up and once the launcher loaded my GPS icon appeared in the status bar and the device would crash and reboot again. After numerous battery pulls and booting into safe mode and everything else I could think of the problem never corrected, doing the same thing everytime. Eventually had to restore with factory image.
Just wanted to know if anyone else has experienced this? Also, it doesn't help that in new to android and was completely uneducated on a fix besides what I did and was a little turned off to the OS at that point.
On the other hand I love my Galaxy Nexus lol
Sent from my Galaxy Nexus using xda premium
i play around with it here & there but have never had that happen. also, i have gps/location turned off(always that way) so not sure if that has anything to do with it.
I'm playing around with it aswell and up to 30-40 min straight without it ever even getting tempered.. with gps location turned on and over wifi..
Sent from my Galaxy Nexus using xda premium
no issues here with earth over wifi. gps off. didn't get too hot either. also loaded faster and with less lag than my transformer.
I've also used it for more than 15 minutes without problems. It does heat up, but nowhere near the ungodly temperatures it reaches while playing games.
gps seems to heat up more when charging it seems. with any phone. but i wouldn't sweat it too much unless your phone is rebooting or melting.
crookone10 said:
Just wanted to know if anyone else has experienced this? Also, it doesn't help that in new to android and was completely uneducated on a fix besides what I did and was a little turned off to the OS at that point.
Click to expand...
Click to collapse
I had a few freezes (mostly in google maps) but they were resolved with a battery pull. Your expereince could have been just very bad luck.
Try this App to check your phones hardware: https://market.android.com/details?id=com.into.stability&feature=order_history
I had no problem running it for 20 min, no errors occurred. Phone gets really warm to the right of the camera when the App is active, which is to be expected.
Both mine loaded fine.
Related
Noticed an issue, thought I'd see if anyone else was seeing it. I don't know if it's isolated to Netflix or not, but it is the only time I've had my phone freeze up on me. I have had it happen twice so far. I don't know how to recreate it though. I'll play Netflix for a while, and then all of the sudden it freezes. I have to pull the battery and restart the phone. Once frozen, it won't accept any input.
Hey. I just had the same problem as you. I was watching netflix and within 10 minutes, the epic 4g touch froze and none of the button worked, not even the power button. I had to removed the battery to reset it. Then it happened again 1 hour into my movie on netflix so I decided to search and saw your post. This is the first time my phone has ever locked up like this.
I use netflix all the time and haven't had it happen to me.
If you look at the Netflix app I'm the market, you will see this started with the latest app update...its the app not the phone. Glad I didn't up date mine...still works great.
Sent from my SPH-D710 using XDA App
chazglenn3 said:
If you look at the Netflix app I'm the market, you will see this started with the latest app update...its the app not the phone. Glad I didn't up date mine...still works great.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I have the latest update, and it still works fine on my phone.
I did have this once in a while. Maybe once a week? Exact symptoms as you describe. I couldn't repeat the bug consistently. Although it seemed to happen when watching more than 45 mins on the phone.
As of the latest update (a week ago), I haven't seen the problem come up actually. It has something to do with the app, not the phone.
Since having the issue I have done an update or two on Netflix. I have been watching a significant amount of video using it too.. I think i'm over 10GB on my plan lol... Anyway, I haven't seen it since. Must just have been Netflix like many of you have noted.
glad to find this post. I've had the same issue on my AT&T GS2 and was about to return the phone.
It's odd to me that an app without root access can freeze the phone and all buttons so easily. Doesn't speak well for the phone's stability. Perhaps something's overheating...
Netflix locks up, no buttons or anything work. First time I pulled my battery to reset it. Didnt think anything about it. So I noticed my phone was getting low on battery so I hooked up my charger and went back to watching X-Files. After an episode and a half I had a little bit of a charge so I pulled the plug and moved to my desk to work while I watched. Couple mins later, blam...lockup. This time I held the power button down and the phone did reset itself, but then I noticed my battery was at 6% when it had been at 60ish before I unplugged it. Then oddly enough, it started climbing about 1% every ten minutes. Wtf?
So anyway. All that novel of a post us to say that i've tested and can recreate the lockup regularly while watching on battery, but haven't had it happen yet when connected to the charger. I'm running unnamed ROM with no other mods or themes. Is it possible this has something to do with CPU profiles changing as the battery drains?
I just wanted to add that the same thing happens to me as momentary.
I'll be watching Netflix while plugged in (USB in this case), phone locks, have to remove the battery, reboot and the battery reads almost dead. It'll go from like 70% to 7%.
This has happened 3-4x.
Anyone have a solution?
I have two sgs2's in the household, its happened on both phones.
Has happened to me on stock,midnight,and unnamed.
Netflix is a buggy app in general. I had to use an old version until recently because it would freeze on both my phone and my CM7 touchpad.
Calkulin 2.9.1 EL29. I have a hunch that this happens only while using Wifi. I've been testing Netflix on 3g and have yet to run across it. It sucks because I only use Netflix while at home and work, and at home I have a lousy 3g signal, especially while downstairs...
Anybody's phone locking up while using Netflix on 3g?
I have been having the same problem for the last few weeks, I usually use 4G on battery and it does freeze on me occasionally. When I am out of 4G, I use 3G with no issues so far. I have yet to use it with WIFI to see if that could be a problem as well.
I hook my phone up to my TV via MHL and run Netflix off my Wifi...
First episode of Deep Space Nine always plays flawless.
Second episode typically locks up the phone and stutters the last half-second of audio until I reset it.
Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.
My Galaxy Nexus is running CM11 since day one and before that I was running PlayfulGod's Unnofficial port.
Every couple of days the phone simply crashes/hangs. It happened at night few hours after I last touched it, it happened during the day while simply laying at sleep in the desk and even while using it. The phone simply stops responding.
If it crashes while sleeping the phone appears to be dead, while active, the screen will remain frozen until the battery is dead (guessing... didn't really wait until the battery ran out).
Removing the battery and re-inserting and the phone will work, typically showing a big hit on the battery level.
I assume there's some CPU activity going on because I can feel the area near the camera warmer (not hot) than the rest.
I opened this topic to follow the issue raised on this post:
VuDuCuRSe said:
I just had the same problem! (I'm using the official Jan05)
It happened a few times on the last days. The phone seems to be off, but in complete dark I can see a bit of back light. Once happened during sleep and it even registered screen on activity (weird).
Never really tried connecting it to the computer, always removed the battery right away. =(
Click to expand...
Click to collapse
At least amrs seems to be having this issue.
amrs said:
My phone had a hang yesterday and again today. Running 0104 nightly. Just a black screen with a faint backlight, no reaction to buttons or anything.
Today I managed to get some info finally as to what happens. Turns out the phone didn't crash, I was able to get in via adb, so dmesg and logcat attached. Also I noticed from the process list system_server was a zombie. As I understand it, system_server is a fairly major part of Android so that's probably a problem...
Click to expand...
Click to collapse
Maybe with more reports we may understand what is causing this crashes.
VuDuCuRSe said:
My Galaxy Nexus is running CM11 since day one and before that I was running PlayfulGod's Unnofficial port.
At least amrs seems to be having this issue.
Click to expand...
Click to collapse
I didn't have any problems for a few days, after installing 0112 nightly. Turns out I didn't have any deep sleep either according to Better Battery Stats. A reboot fixed that but then I got a crash quickly again. I realized weather info was odd in the lock screen so locked and tried to unlock and nothing. Couldn't even get in with adb shell this time.
So I guess deep sleep has something to do with this. I've been using the hotplug CPU governor most recently but I think this happened with interactive too.
I'm all stock... kernel, CPU/GPU settings and so on... so I guess that it shouldn't be related to that.
Do you know of any good debugging app to eventually save some sort of evidence of the crash?
I tried plugging the USB cable on the last crash but the computer/adb didn't detect the phone.
Let us know what your have found after the update. Good and bad.
Since the update my WiFi has dropped out on my home network twice. Have to restart or turn airplane mode on/off.
Also I don't think the battery has improved any....
Terra1 said:
Let us know what your have found after the update. Good and bad.
Since the update my WiFi has dropped out on my home network twice. Have to restart or turn airplane mode on/off.
Also I don't think the battery has improved any....
Click to expand...
Click to collapse
I just noticed a bit longer restart times. Thats it !:cyclops:
I've noticed darker video recording in low light l...
After the update, at the settings / power the scrolling is laggy. This module was updated, something is just not right at my device. I did a factory reset, no avail. It's lagging only over here, pretty annoying...
vistvan83 said:
After the update, at the settings / power the scrolling is laggy. This module was updated, something is just not right at my device. I did a factory reset, no avail. It's lagging only over here, pretty annoying...
Click to expand...
Click to collapse
Yeah, its true. It slipped my mind. Probably this particular portion of the software was developed at the last moment, and they didn't have enough time to test it thoroughly
I have narrowed my wifi drop outs to the beyond pod app.
My camera won't focus after updating. I had the problem prior, but did the alcohol microfiber run to get the coating off and it was working great. After I updated the camera now seems like it won't focus, only objects within 5 inches are in focus. I did a factory reset and made sure that the camera wasn't set to macro mode. Nothing is working to fix this problem. I think my camera might just be broken now.
Sent from my HTC One_M8 using XDA Free mobile app
Now after a few days i think that the battery cannot hold on so long as with 4.4.2. Previously i could run it two days with moderate use, now the battery level drops to 20% after 24 hours.
At the update the battery was not fully charged. Is this behavior normal after the update, did i make a mistake, or does anybody else have the same problem?
I'm on 19% after 13 hours. WTF is going on? I cannot see any suspicious app causing this. Can i revert to 4.4.2? LOL...
vistvan83 said:
Now after a few days i think that the battery cannot hold on so long as with 4.4.2. Previously i could run it two days with moderate use, now the battery level drops to 20% after 24 hours.
At the update the battery was not fully charged. Is this behavior normal after the update, did i make a mistake, or does anybody else have the same problem?
I'm on 19% after 13 hours. WTF is going on? I cannot see any suspicious app causing this. Can i revert to 4.4.2? LOL...
Click to expand...
Click to collapse
I have (or had) the same problem as you with the new update. Try clearing the cache partition (that's what I've been told). I'm still keeping my eye on the battery to see if it's fixed. The problem for me was that Android Kernel and Android System was using too much battery.
Here are some screenshots:
https://drive.google.com/file/d/0BzywJDML-7JkTkJwOV9mQk5ucG8/edit?usp=sharing
https://drive.google.com/file/d/0BzywJDML-7JkTlc3ODYzcUotQlE/edit?usp=sharing
These battery results are pretty bad compared to what I was getting prior to 4.4.3 (i got 2d5h once with 4h on screen and 7 hours awake).
Hi! I think i was able to fix it, the issue appeared on other devices which received 4.4.3. I cleared the cache for Google Play Store and for GP Services. Now i'm at 50% after 20 hours.
vistvan83 said:
Hi! I think i was able to fix it, the issue appeared on other devices which received 4.4.3. I cleared the cache for Google Play Store and for GP Services. Now i'm at 50% after 20 hours.
Click to expand...
Click to collapse
just tried that and hoping it works. I've tried turning off fast boot but having the same issues others are reporting also.
here is a post from another user:
Hi, everyone, this is my first time here, so bear with me. On Wednesday, August 28, I downloaded the new Kit Kat 4.4.3 update from AT&T onto my One M8. Right after and for a few hours after, everything was in great condition as always. I've had my M8 since launch and haven't had a problem since and hold it very dear to me. Then, after about four hours, I noticed the phone was getting hot, really hot. I had power saver on as always and I saw that the CPU was taxed at 97%, just having Instagram running and YouTube actively showing a video. So I restarted the phone, clearing the cache and making sure that nothing was working too hard. That's when the problems really started coming up. It was getting hot but I ignored it and went to the Play Store to update my banking app and download Reddit News. After seven minutes of a normally one minute (if that) update, I stopped the download, cleared the cache and tried again. Nothing. So Google Play won't download, update, or install apps, Google, or third-party. That's not all. Hangouts will not send messages. Even in full LTE connectivity and 5 GHz Wifi AC, message could not send both to Android users (one used messages, the other Hangouts) and to an iPhone. It was like deja vu with my old iPhone 4S. BUT THAT'S NOT ALL. YouTube was giving me hell, too. When I would type into the search bar to search for a video, the search bar would clear. For example, if I'm looking up and type into the search bar on YouTube "Linus Tech Tips," then it'll work. But if after that I backspace or "x" out "Linus Tech Tips," and type something else, say, "Build a Gaming PC," If I use Swype (Swiftkey, Google Keyboard, or HTC Sense), the first word shows up, but as I'm typing, the subsequent words are erased and "Linus Tech Tips" shows up in the search bar (check him out if you don't already). This is EXTREMELY frustrating and now I can't watch The Joy of Painting. Damn. Finally, the CPU and heat I mentioned before is crazy. The CPU is always between 79% and 99% at all times. the RAM is usually at about 75% as normal, but the CPU is running nuclear hot. It's going to 105-115 degrees Fahrenheit. This worries me, all of this, because I wonder if this is the fault of the new 4.4.3 update for the AT&T M8 model or maybe underlying causes. I've had Malwarebytes scan my phone and find nothing. That caches are cleared and nothing seems to work. If anyone can help I would be extremely grateful because my only option in my mind is to do a hard factory reset of the device. Thanks to anoye who can help, and if not, then, oh well. Thanks, and sorry I made an essay out of this, this is really a big problem for me.
another user just posted:
Well, I think that the factory reset fixed it. It's been over an hour now, and the phone isn't overheating anymore. Battery life has only dropped 2% in that hour instead of the 2% every five minutes after the update.
After the 4.4.3 update the camera's manual mode doesnt change the exposure the same way as it did in 4.4.2 so i cant see the pics in the viewfinder at night before i actually take the pic and look at it, and that really sucks.
So weird Issue.
Using Google Maps on MaximusHD 6 with the latest t-mo firmware (2.11) I get constant "GPS SIGNAL LOST" when obviously driving and using it as my nav since I got it. I'm in southern California with a pretty good LTE signal almost everywhere. The highways are pretty open so trees, mountains, buildings etc are ruled out as a probable cost.
Now today I noticed that I normally keep the phone locked/screen off when driving since it's connected over BT so there's no real need to look at it. During a normal 15-20min drive I would get the signal lost alert a lot. Upwards of 10 or so times on that single drive. While with my M8 it never happened especially when literally not 5min after getting out of the parking lot doing maybe 20mph down the street. I first I thought i messed something up since I took the phone apart to apply thermal paste to keep it from overheating.
However today on a drive back I kept the phone with the screen on. Never did it lose signal while the screen was on, but a minute after I locked the phone (screen off) did it lose GPS signal. I turned it back on and after driving 20min or so the signal wasn't lost.
So overall has anyone experience a similar issue? Full cellular coverage with frequent google maps alerts that the GPS signal was lost. Maybe a background gps process being killed or another coming up and hindering it.
Gonna wait for the Thanksgiving break to mess around with stock/custom roms and see if it's just something that can be fixed with a reflash.
I'm having the same issue, have you figured anything out? Have you tried using a different app besides google maps to see if it's the actual app doing it's power save feature, or the background powersaving process being started by the phone being screen off? Really interested because my phone starts burning up to extreme temps...
On the backup I had with the issue I narrowed It down to possibly a background process cutting it off once the screen turns back. Power saving was off and all that would stick while screen was off was maps, Google service, and social apps.
As for the cause I couldn't figure it out. I went with a stock from without issues. Then went back to custom roms and haven't had the issue again. Also I drastically lowered my app count. Barely use any apps not needed for basic functionality.
As for the temp issue you're having. I noticed gets warm just like any other device when using GPS. I have opened up the phone and applied a new thermal coat following off a thread around here.
I have another issue came up where the phone would seek out a GPS signal while battery saving was selected to even location turned off. Killed my battery in a heart beat. Hasn't happened again.
I would suggest you make a full backup and either flash a stock rom or redownload whatever custom rom your using. Do a trial run for a day or two with minimal apps and see if it improves.
Here's where it gets interesting..
I used to own a galaxy s3 i9300 and custom kernels caused exactly the same issue. Flashing a stock rom solved it and a few other issues, one in particular was gps inaccurate coordinates.
Now I have moved to an m9. This has in the past run great. It is completely stock and untouched by curious fingers.. However, recently my gps has been running at random intervals even though it is completely off in all accessable settings. I can't find the culprit and it sapped 40% in a few minutes. It was literally a short face to face conversation, jumped back in the car and went for my phone for waze.. Dead as a dodo..
Confuzzled completely as to whether this is the actual rom doing it or an app..
I wish I stole my HTC M9.
shivadow said:
Here's where it gets interesting..
I used to own a galaxy s3 i9300 and custom kernels caused exactly the same issue. Flashing a stock rom solved it and a few other issues, one in particular was gps inaccurate coordinates.
Now I have moved to an m9. This has in the past run great. It is completely stock and untouched by curious fingers.. However, recently my gps has been running at random intervals even though it is completely off in all accessable settings. I can't find the culprit and it sapped 40% in a few minutes. It was literally a short face to face conversation, jumped back in the car and went for my phone for waze.. Dead as a dodo..
Confuzzled completely as to whether this is the actual rom doing it or an app..
I wish I stole my HTC M9.
Click to expand...
Click to collapse
Android 6 should be released around here soon so maybe that'll improve/fix these issues. I wouldn't be surprised if Google services is causing this since it has in the past drained batteries and causes similar issues. If the kernel is involved then the issue has been seen on both stock and custom.
well it may be a setting from the maximums HD, try using other Rom and tell us if problem is solved, try HD Revolution or ViperOne.
Hi all, I got a Moto G3 and having issues with the gps no signal message, it is on and off, but more the time that have no signal. So have heard that Android 6 could be the guilty one.. Do any of you know if there is a fix yet? ?
Enviado desde mi Nexus 7 mediante Tapatalk