Okay, I am having issues with my Note 3. I can run my phone as hard as i want and no problem until i get to about 50-60%. Then, my phone screen will just go black like the battery just died. Now if i plug it in for 1 second and hit the power button it starts booting up and i can immediately unplug it and it returns to 50-60% battery and continues to run fine. But it will not power up without plugging it in for a second. I even have a friend that is having the same issue with his att&t note 3 that has never been rooted ever. Just weird. I am currently running Vision-x vpucnc5 rom with calm kernal. I have tried multiple other roms and the problem still persist. I have even purchased another battery thinking that was the problem. I will include a screen shot of my battery info screen and all you see is a black line when it happened. Please help! Thanks in advance. .
When you run the device hard, is the phone getting hot? Do you have a big case on it? It sounds like the overheating sensor is kicking off the device. On my note 3, when running WiFi Tether Router app and it is downloading a big file say a movie. On 4g LTE at a download speed of 2MB+ the phone has gotten to hot and shut down. My solution is to take it out of the case when downloading.
Maybe plugging the charger into the device resets the overheating sensor?
Here is what I would do, here is a link to the Galaxy tool app http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159 download and install. Now you test all the sensors, and check the logcats to see what happened at the black line. Your phone has record of it in the logcats, either in the IOTHIDDENMENU, or SYS_DUMP !!!
jimzweb1 said:
When you run the device hard, is the phone getting hot? Do you have a big case on it? It sounds like the overheating sensor is kicking off the device. On my note 3, when running WiFi Tether Router app and it is downloading a big file say a movie. On 4g LTE at a download speed of 2MB+ the phone has gotten to hot and shut down. My solution is to take it out of the case when downloading.
Maybe plugging the charger into the device resets the overheating sensor?
Here is what I would do, here is a link to the Galaxy tool app http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159 download and install. Now you test all the sensors, and check the logcats to see what happened at the black line. Your phone has record of it in the logcats, either in the IOTHIDDENMENU, or SYS_DUMP !!!
Click to expand...
Click to collapse
Not really sure how to test the temp sensor. It seems from that app that my phone was at about 29 deg Celsius.
MRBULLRED said:
Not really sure how to test the temp sensor. It seems from that app that my phone was at about 29 deg Celsius.
Click to expand...
Click to collapse
There is a free app in the Google play store called the "Cpu Temperature" it gives you CPU temp and Battery temp in C/F. You might install it and run the device hard up to 50-60% and see what your temp is.
Don't forget to scroll through those logcats to see what happened at the black line.
Also I noticed your Screen is using some Battery, what is the preset on display time? Mine is 2 minutes then shuts off, I know if you run the display constantly they get hot.
jimzweb1 said:
There is a free app in the Google play store called the "Cpu Temperature" it gives you CPU temp and Battery temp in C/F. You might install it and run the device hard up to 50-60% and see what your temp is.
Don't forget to scroll through those logcats to see what happened at the black line.
Also I noticed your Screen is using some Battery, what is the preset on display time? Mine is 2 minutes then shuts off, I know if you run the display constantly they get hot.
Click to expand...
Click to collapse
Mine is set to 1 minute. The cpu temperature seems to stay around 100°F most of the time. However, after a random shutdown I noticed the temp was 140°F while booting it up right after the shutdown. Also. I uprooted and went back to stock NC5 yesterday. Still had the same problem today.
MRBULLRED said:
Mine is set to 1 minute. The cpu temperature seems to stay around 100°F most of the time. However, after a random shutdown I noticed the temp was 140°F while booting it up right after the shutdown. Also. I uprooted and went back to stock NC5 yesterday. Still had the same problem today.
Click to expand...
Click to collapse
My CPU temp is about 115F with WiFi Tether Router running pretty much all day. My Battery temp is 86F. My device feels cool to the touch, except just under the camera flash where the CPU is. What is your Battery temp at 50-60% ? Maybe you have a short in your Battery that creates excessive temp at the half way discharge point? Do you have access to another Battery to swap out and see if that has any effect?
jimzweb1 said:
My CPU temp is about 115F with WiFi Tether Router running pretty much all day. My Battery temp is 86F. My device feels cool to the touch, except just under the camera flash where the CPU is. What is your Battery temp at 50-60% ? Maybe you have a short in your Battery that creates excessive temp at the half way discharge point? Do you have access to another Battery to swap out and see if that has any effect?
Click to expand...
Click to collapse
First of all thanks so much for all your help.
My device feels cool to the touch all the time. Running candy crush seems to make it run at about 120f. Still feels cool to the touch. It happened with the battery that came with the phone so I bought another one thinking that was the problem. Do I buy a third?
MRBULLRED said:
First of all thanks so much for all your help.
My device feels cool to the touch all the time. Running candy crush seems to make it run at about 120f. Still feels cool to the touch. It happened with the battery that came with the phone so I bought another one thinking that was the problem. Do I buy a third?
Click to expand...
Click to collapse
No, I think two is enough. Check out this video https://www.youtube.com/watch?v=fls4NIRJ1IQ maybe this is the fix.
If not here is Sprint.com's suggestion, here is the link http://support.sprint.com/support/a...expectedly/WTroubleshootingGuide_542_GKB59231
jimzweb1 said:
No, I think two is enough. Check out this video https://www.youtube.com/watch?v=fls4NIRJ1IQ maybe this is the fix.
If not here is Sprint.com's suggestion, here is the link http://support.sprint.com/support/a...expectedly/WTroubleshootingGuide_542_GKB59231
Click to expand...
Click to collapse
Do you think this looks normal?
MRBULLRED said:
Do you think this looks normal?
Click to expand...
Click to collapse
NO, anything with Kim Kardashian in it is not normal. Lol As for the device that temp seems a little high, right now I am running 114F CPU and the Battery is 84F. The deivce is running WiFi Tether Router, plus a half dozen other apps, and charging. Let me hunt up the specs on the average operating temp on your CPU.
Hey if you get a chance try this. Go to settings/device/call and uncheck " Turn off screen during calls" the screen will stay on during calls. But if it doesn't go black then its the proximity sensor. It may be defective or may not deactivating because of a case.
Related
Has there been any resolution to the 1 - 2 second wake up lag yet? I've seen several "fixes" like reducing the resolution of the lock screen wallpaper etc but none of these work for me. I've experienced the lag on KE7 stock ROM, Cognition ROM, Villain ROM and now on Lite'ning ROM.
Not sure if I agree that it's being caused by the CPU clocking down when the phone is asleep either. When I use SetCPU to set the minimum clock speed to 1.2Ghz the wake up lag is still there.
Also the lag does not occur when the phone is plugged in and SetCPU is telling me that the phone still clocks down to 200Mhz when asleep and plugged in.
Someone must have some idea what is causing this #$%$## lag.
I use Softlocker Free for this.. Works perfect for me, a bit reduced battery life but not enough to stop me from using it..
Thanks for the reply. I tried Softlocker a while back and found the battery drain pretty heavy. Might give it another go. I was thinking there must be a permanent fix for this lag problem though. Hopefully it's just a matter of someone finding it.
I also noticed the lag on my old i9000 as soon as I updated to GB so know this is across the different samsung models on GB in addition to SGS2. I really do think its the clock going down despite your setcpu settings. Use cpuspy free from market and you will see what I mean. Once its in standby it goes into deep sleep which I believe is lower than 200? But set it to 1200 min and see if cpuspy logs it as going below that just to see
It will happen on every rom right now since they are all based on the firmware. I really think it saves battery going into that clock mode and if someone comes up with a fix the cpu will have to run at a higher clock rate and battery loss will be significantly higher
Sent from my GT-I9100 using XDA App
Mines instant with No Lock.
Sent from my GT-I9100 using Tapatalk
Tell us what you did to stop the wake lock. Is it plugged in though?
Sent from my GT-I9100 using XDA App
I am using Lite'ning rom 1.4 right now, when I press the home button til the screen on take around 0.5 second, is it normally?
I've tried this app,and it did seem work. I'll try to see how about the drain of power.
I was using No Lock and it didn't make any difference. What is really annoying me about this is that some users are seeing the lag and others apparently aren't. The lag on my phone is probably about 1 second. This isn't a really big deal unless this sort of thing annoys you. My iPhone didn't have the lag, my Desire didn't have the lag and I feel a high end phone like this shouldn't have the lag either.
blue265 said:
Once its in standby it goes into deep sleep which I believe is lower than 200? But set it to 1200 min and see if cpuspy logs it as going below that just to see
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I'll have a play and see.
do you guys get lag when using the power button? I get a small lag when using the home button, but if use the power button its instant.
djsaad1 said:
do you guys get lag when using the power button? I get a small lag when using the home button, but if use the power button its instant.
Click to expand...
Click to collapse
There seems to be nearly as many combinations of symptoms as there are phones. Mine has the same 1s or so lag regardless of how I wake it up. I tried SoftLocker again. Not only does it chew the battery, it was randomly causing my phone not to wake up at all, which then required a reboot. Softlocker has since been uninstalled.
The lag definitely doesn't show itself if the phone is plugged in or if music is playing in the background. Also if the phone has only been asleep for 5 or 10 seconds the lag is generally not there.... but not always. This seems to be inconsistent.
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
appro77 said:
There seems to be nearly as many combinations of symptoms as there are phones. Mine has the same 1s or so lag regardless of how I wake it up. I tried SoftLocker again. Not only does it chew the battery, it was randomly causing my phone not to wake up at all, which then required a reboot. Softlocker has since been uninstalled.
The lag definitely doesn't show itself if the phone is plugged in or if music is playing in the background. Also if the phone has only been asleep for 5 or 10 seconds the lag is generally not there.... but not always. This seems to be inconsistent.
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
Click to expand...
Click to collapse
Don't want to fork/derail the thread, but are you guys experiencing only the "Wake Up Lag" or also the lag when pressing the Home button while unlocked. I see some lag when using the home button to go back to Homescreen 1 for example. In case you folks are seeing lag in both the cases like me, could it be that both have the same underlying cause.
There is this other theory about the bundled Voice Talk app from Vlingo having the shortcut of Home button double tap, which causes any Home button tap to wait until the double tap window before doing its thing. I don't see that mentioned in this thread, but it kind of makes sense for the Home button lag, but perhaps not so much for the Wake lag (at least I could not think of a reason for that to happen). What do you guys think about both these problems?
appro77 said:
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
Click to expand...
Click to collapse
Well well finally users are reporting this problem, good to see its not only me.
Anyway, I don't think the Phone goes to any underclocked frequency when it goes to sleep. Cause if you can test SetCPU by setting it to 200 MHz then you will notice that in 200 MHz the phone turns itself off, you have to turn it on manually. So the problem is related with firmware definitely. And there are no fortunate users, some users don't take this as a problem, some don't notice it and some notice but doesn't agree, but here or there everyone has the bug. I hope the issue will be fixed in future firmware upgrade.
Regards.
Sent from GT-I9100
It may seem crazy but...
The delay depends heavily on the lock image you choose for lock screen.
With stock image it's instant, with custom background it slows down significantly.
My theory is that custom image is being resized while low Cpu frequency, it takes a while.
Sent from my GT-I9100 using XDA Premium App
rdy2go said:
It may seem crazy but...
The delay depends heavily on the lock image you choose for lock screen.
With stock image it's instant, with custom background it slows down significantly.
My theory is that custom image is being resized while low Cpu frequency, it takes a while.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
I've just tested that, it's the same no matter what background I use.
Wow..
Seems like the thread I can finally count on! Lots of behavior that I experience as well. I have the home button lag and the wake up lag and it's bugging me.
One thing to note.. The wake up lag is worse when you have an SD card inserted -> This scenario was the same for the SGS1 too. Anyone can confirm this?
I'm using No Lock as personal preference but the lag is always there. All behavior you guys mention (abt headphones plugged in, charging, within 5-10secs) are all being observed.
Eagerly waiting for a fix!
I had lag on my first SGS2, but it was worse that yours, at about 9-10 seconds (that's no exaggeration) plus high battery drain (Only getting about 6-7 hours battery at normal use). Went and got a new S2, no lag, and battery lasts 36 hours now.
It may not be the case with yours that its faulty, but I think I fixed the first SGS2 by flashing a newer rom, then doing hard reset and clearing cache's. I now have 2 shiny new SGS2's working as normal.
TheBishopOfSoho said:
I had lag on my first SGS2, but it was worse that yours, at about 9-10 seconds (that's no exaggeration) plus high battery drain (Only getting about 6-7 hours battery at normal use). Went and got a new S2, no lag, and battery lasts 36 hours now.
It may not be the case with yours that its faulty, but I think I fixed the first SGS2 by flashing a newer rom, then doing hard reset and clearing cache's. I now have 2 shiny new SGS2's working as normal.
Click to expand...
Click to collapse
I did flash a newer ROM, but didn't do a hard reset.. all my apps were intact. Perhaps I will spend sometime on it this weekend. By the way, which ROM did you flash on your first SGS2 that fixed the problem?
Also, I tried SoftLocker and it works!! The only downside is the battery life. I loose about 4-5% per hour while I was asleep. That bring me to say that the delay is not caused by the voice input function, but rather due to the device going into deep sleep (which may be normal). But it's the waking up that's taking long.
Still seeking for more ideas...
MasK said:
Also, I tried SoftLocker and it works!! The only downside is the battery life. I loose about 4-5% per hour while I was asleep.
Click to expand...
Click to collapse
Yes, I found that SoftLocker is not really a solution because of the battery drain and some other bugs it introduced.
Anyone who is experiencing this lag should be contacting Samsung. I contacted Samsung Australia and they told me they had not heard of the problem. If everyone who is experiencing the problem reported it to Samsung, I think there may be a far better chance of a fix. Anyone who is annoyed by this bug, please email Samsung via the link on their website. If they are flooded with complaints they "may" act and provide a fix.
So this time when my TFP shut down I got white lines across the display.
I have a thought, maybe some of you can test.
ICS is supposed to use hardware to do screen draws.
What if what we are seeing is the GPU overheating?
It sure looks like it to me... also if the "update fix" is to slow down the GPU this would suck.
Any way to test this? aka have some external way to cool it and see if it still crashes?
fenturi said:
So this time when my TFP shut down I got white lines across the display.
I have a thought, maybe some of you can test.
ICS is supposed to use hardware to do screen draws.
What if what we are seeing is the GPU overheating?
It sure looks like it to me... also if the "update fix" is to slow down the GPU this would suck.
Any way to test this? aka have some external way to cool it and see if it still crashes?
Click to expand...
Click to collapse
I'm not so sure it's related to the GPU overheating. Sometimes it happens while the tab is booting up, before I've even had a chance to stress the GPU. Also, last night I got in a fairly long game of Shadow Gun, then exited out and was able to use the browser for a while and *then* it locked up.
It's definitely not overheating related mine does it once every 1 to 3 hours no matter what it's doing even idle overnight. The developer that took my log files said it looks like a Linux stability issue.......
jdbaker82 said:
It's definitely not overheating related mine does it once every 1 to 3 hours no matter what it's doing even idle overnight. The developer that took my log files said it looks like a Linux stability issue.......
Click to expand...
Click to collapse
Well software fix would be better than flawed hardware.
Humm..
http://stackoverflow.com/questions/8654424/ics-crashes-when-intent-getextras-is-called
I am having an issue with my MoPho severely overheating and shutting off. But strangely it only seems to happen when I am outside. The first time I noticed it was when I went fishing. My phone had about 80% charge, and when I picked it up maybe 30 mins later is was scorching hot. To the point that it burnt me. And it had shut off. I didn't have it in the sun or anything. It was in the shade inside a bag. I was not able to get it to turn on even with a battery pull even after it had cooled down. The battery completely drained in a matter of minutes. I couldn't even get it to charge in the truck on the car charger, either. It got too hot on the charger to the point it wouldn't even get a charge. This has happened about 3 or 4 times since. It will go from a full battery, get super hot, and completely drain within minutes. This never used to happen in the house, it was only an issue outside. until today. Went fishing, phone had full charge. It managed to hold the battery for a couple hours, unlike the other times, but eventually got hot and died. Then when I got home, plugged it into the charger and went to sleep, woke up a couple hours later and it was burning hot, and had no charge. Other things on it are acting weird now, as well. The screen keeps turning on and off every few seconds by itself. I don't know what the issue is, but I might have to switch back to stock if I can't find a solution. Because eventually this is going to fry my phone. And I don't want that to happen. It is also a huge inconvenience for your phone battery to drain in a matter of minutes and become a useless paperweight when you are in the middle of nowhere and need a form of communication in an emergency.
Has anyone else had this issue and found a solution?
Galaxy_S_ said:
I am having an issue with my MoPho severely overheating and shutting off. But strangely it only seems to happen when I am outside. The first time I noticed it was when I went fishing. My phone had about 80% charge, and when I picked it up maybe 30 mins later is was scorching hot. To the point that it burnt me. And it had shut off. I didn't have it in the sun or anything. It was in the shade inside a bag. I was not able to get it to turn on even with a battery pull even after it had cooled down. The battery completely drained in a matter of minutes. I couldn't even get it to charge in the truck on the car charger, either. It got too hot on the charger to the point it wouldn't even get a charge. This has happened about 3 or 4 times since. It will go from a full battery, get super hot, and completely drain within minutes. This never used to happen in the house, it was only an issue outside. until today. Went fishing, phone had full charge. It managed to hold the battery for a couple hours, unlike the other times, but eventually got hot and died. Then when I got home, plugged it into the charger and went to sleep, woke up a couple hours later and it was burning hot, and had no charge. Other things on it are acting weird now, as well. The screen keeps turning on and off every few seconds by itself. I don't know what the issue is, but I might have to switch back to stock if I can't find a solution. Because eventually this is going to fry my phone. And I don't want that to happen. It is also a huge inconvenience for your phone battery to drain in a matter of minutes and become a useless paperweight when you are in the middle of nowhere and need a form of communication in an emergency.
Has anyone else had this issue and found a solution?
Click to expand...
Click to collapse
Many people have experienced overheating problems on our cm9. Some people including self have fixed it by just doing a fresh install of cm9 as it seems like just a fluke. Im sure the fact that were running a gingerbread kernel on ics doesnt help. Also, try dropping the battery down to 1200 from the stock 1300, see if that helps.
Sent from my MB855 using XDA
Acvice said:
Many people have experienced overheating problems on our cm9. Some people including self have fixed it by just doing a fresh install of cm9 as it seems like just a fluke. Im sure the fact that were running a gingerbread kernel on ics doesnt help. Also, try dropping the battery down to 1200 from the stock 1300, see if that helps.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Someone mentioned changing the overclock from the stock 1300 down to 1000 in another thread. Is that the same thing as what you're talking about? Or is there a separate setting for the battery? I did try dropping it down to 1000 but that's when the screen started turning on and off by itself. And LWP's stopped working properly. They would get stuck and seizure. Even after I changed it back to the default 1300. So I went into CWM and just reflashed the ROM. No more screen turning on and off or LWP's acting weird. But as far as the overheating problem I can't be sure I guess until I go fishing again or put it in another situation in which it's done it previously.
Galaxy_S_ said:
Someone mentioned changing the overclock from the stock 1300 down to 1000 in another thread. Is that the same thing as what you're talking about? Or is there a separate setting for the battery? I did try dropping it down to 1000 but that's when the screen started turning on and off by itself. And LWP's stopped working properly. They would get stuck and seizure. Even after I changed it back to the default 1300. So I went into CWM and just reflashed the ROM. No more screen turning on and off or LWP's acting weird. But as far as the overheating problem I can't be sure I guess until I go fishing again or put it in another situation in which it's done it previously.
Click to expand...
Click to collapse
I work outside every day and its bout 100 degrees out consistantly now... I'm not running cm9 anymore but I've noticed I still get the occasional overheat while its in my pocket, it most definitely gets annoying sometimes having to pull the battery and let everything cool down but I think the benefits outweigh the annoyance level a million to one. I guess what I'm saying is you're not alone friend, it definitely happens to me as well. I have my CPU set to 1k though and messed around with undervolting as well and feel like I get a little better results this way. Keep playing with your settings until you find the one that works best for you is the advice I can give. Good luck!
Sent from my MoPho running MIUI.us official port!
Party Spock is in the house, everybody have a logical time!
Galaxy_S_ said:
Someone mentioned changing the overclock from the stock 1300 down to 1000 in another thread. Is that the same thing as what you're talking about? Or is there a separate setting for the battery? I did try dropping it down to 1000 but that's when the screen started turning on and off by itself. And LWP's stopped working properly. They would get stuck and seizure. Even after I changed it back to the default 1300. So I went into CWM and just reflashed the ROM. No more screen turning on and off or LWP's acting weird. But as far as the overheating problem I can't be sure I guess until I go fishing again or put it in another situation in which it's done it previously.
Click to expand...
Click to collapse
Yeah its the same thing. Remember, our processor is technicallynot supposed to be over 1000 per core for a reason. People just like to push things to the edge. The whole lwp problem is expected and everyone experiences this with the our ice roms. That also is due to lack of proper 2d libs. But I'm glad most of your problems have subsided. Run your processor at 1000 and I'm sure the overheating will lessen. On a powerful dualcore phone like the photon 1300 from 1000 is miniscule anyway.
Acvice said:
Yeah its the same thing. Remember, our processor is technicallynot supposed to be over 1000 per core for a reason. People just like to push things to the edge. The whole lwp problem is expected and everyone experiences this with the our ice roms. That also is due to lack of proper 2d libs. But I'm glad most of your problems have subsided. Run your processor at 1000 and I'm sure the overheating will lessen. On a powerful dualcore phone like the photon 1300 from 1000 is miniscule anyway.
Click to expand...
Click to collapse
Alright. I will try it again. But I just love my LWP's =[ I always have a lwp on. I have never experienced the problem with the lwps until I set the processor to 1000. But I guess it comes down to sacrificing my wallpaper to stop it from overheating. If that's what it takes to fix the problem. Hopefully once the stable version is released everything will work like it should without having to sacrifice anything.
It did overheat again the other day. I did have Watchdog on my phone and I was on facebook messenger the other morning and it started acting up, I had my phone in my hand and within a couple minutes it got burning hot, and then right after, Watchdog popped up with a notification that messenger was above threshhold. It was running at 49% CPU or something. And come to think of it I would always get notifications about fb messenger "misbehaving". So I came to the conclusion that it could be either messenger or watchdog causing most of my problems. I deleted watchdog to see if it fixes my problems. I'm hoping it isn't messenger. Because I need my FB. lol. But I haven't really used messenger on my phone since I deleted watchdog. So we'll see. If that didn't solve it, then I will sacfrifice my lwp and set the processor back to 1000.
Galaxy_S_ said:
Alright. I will try it again. But I just love my LWP's =[ I always have a lwp on. I have never experienced the problem with the lwps until I set the processor to 1000. But I guess it comes down to sacrificing my wallpaper to stop it from overheating. If that's what it takes to fix the problem. Hopefully once the stable version is released everything will work like it should without having to sacrifice anything.
It did overheat again the other day. I did have Watchdog on my phone and I was on facebook messenger the other morning and it started acting up, I had my phone in my hand and within a couple minutes it got burning hot, and then right after, Watchdog popped up with a notification that messenger was above threshhold. It was running at 49% CPU or something. And come to think of it I would always get notifications about fb messenger "misbehaving". So I came to the conclusion that it could be either messenger or watchdog causing most of my problems. I deleted watchdog to see if it fixes my problems. I'm hoping it isn't messenger. Because I need my FB. lol. But I haven't really used messenger on my phone since I deleted watchdog. So we'll see. If that didn't solve it, then I will sacfrifice my lwp and set the processor back to 1000.
Click to expand...
Click to collapse
Fb messenger gets a lot of hate, i cant say thats your problem but you never know. Try out a chat client called imo from the play store instead. It supports fb as well as others and is leaps and bounds better than fb messenger.
Sent from my MB855 using XDA
Acvice said:
Fb messenger gets a lot of hate, i cant say thats your problem but you never know. Try out a chat client called imo from the play store instead. It supports fb as well as others and is leaps and bounds better than fb messenger.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Thank you. I will definitely try that =] Thank you. I really hope it fixes the problem. I can't wait for the stable release. haha
Hi guys,
My Atrix 4G is acting weird for the past 2 days. I was running Nov 25 CM7 nightly with faux 1GHZ kernel when the issue first occurred. The phone got too hot suddenly, it shot up from 32C to 58C in a few seconds and the charge started decreasing from 38% to 15% in 2 to 3 seconds. Before I could realize what happened, the phone turned off. I plugged in my charger after letting it to chill, and the phone started charging.
After sometime, I saw that the phone had charged till 25%. So I booted into CM7. Within no time, the phone got extremely hot and turned off again. It did not start charging till it came to normal temperature.
I somehow managed to flash the stock CM7 kernel, assuming that the issue was with the Faux kernel. After that, the phone was operating at normal temperature for a couple of hours. I thought that the Faux kernel was the culprit and thought that my issue is resolved. But after a couple of hours, I again felt the phone getting too hot in my pocket and before I could react, it turned off.
Please help me. Is the battery dead and needs a replacement? Or is it with the ROM? I've been running CM7 with stock/Faux kernel for many months and never faced such an issue.
Note: The issue started happening some time after I installed two apps. One is the Koi Live Wallpaper and one is the Xperia S launcher. Now both are uninstalled but the issue still persists.
Thanks in advance for your help.
It does sound similar to how a PC would react to an overheating CPU/GPU. In that case, you want it to shut off before permanent damage. Heat does not play well with electronics.
See if you can go under Performance Settings and set it to "powersave" and lower the clock speed to the next lowest setting (912 or 800). If it continues, try to backup everything and do a clean install. If the problem persists, it's not related to software.
Are you having the same issue in recovery? It might prove to be a challenge if it does.
Other suggestions: Remove any case you have on there along with the backing to get more air flow. Try to use it in a cold area, or in front of a fan or something. People have tried linking busted display digitizers with excess heat, might want to be careful.
Sent from my MB860 using xda app-developers app
I have that problem but with ICS/JB roms, the phones gets hot because my cpu is stucked at 750 MHz for some reason i don't know
Normally i don't have those problems with cm7, but when i had it i solve it by just installing another faux kernel. right now i'm running v023 at 1Ghz and it's working properly.
Maybe you can try to fix the permissions under CMW, sometimes that correct some problems
Try CPU spy and see if your phone is running at high clock speed all the time.
Sent from my MB860 using xda app-developers app
Thanks guys for the ideas.
The issue doesn't seem to be related to the ROM or kernel. It is with the hardware, because the phone is heating up even while it is switched off. The battery needs to be removed and after it is cooled, the phone works normally for some hours before it starts heating up again.
If it is getting heated up even while switched off, the issue has to be with the battery or the phone's circuit. Not sure which one is affected and I dont have a replacement battery to test.
Any ideas?
gkarthik16 said:
Thanks guys for the ideas.
The issue doesn't seem to be related to the ROM or kernel. It is with the hardware, because the phone is heating up even while it is switched off. The battery needs to be removed and after it is cooled, the phone works normally for some hours before it starts heating up again.
If it is getting heated up even while switched off, the issue has to be with the battery or the phone's circuit. Not sure which one is affected and I dont have a replacement battery to test.
Any ideas?
Click to expand...
Click to collapse
Are you saying it's overheating while completely powered down or just when screen is off? Is it still under warranty?
エイトリックス から 送ります
thesummoner101 said:
Are you saying it's overheating while completely powered down or just when screen is off? Is it still under warranty?
エイトリックス から 送ります
Click to expand...
Click to collapse
It's overheating when the phone itself is off. It's weird. Looks like the battery is leaking charge. And it is not under warranty
gkarthik16 said:
It's overheating when the phone itself is off. It's weird. Looks like the battery is leaking charge. And it is not under warranty
Click to expand...
Click to collapse
That is weird. Sorry, I can't be further help. Good luck.
エイトリックス から 送ります
Today my stock phone with JB overheated. I got a message on the screen that said the phone was shutting down for my protection. I was in the process of installing apps from the Play store. Six hours later it will still not turn back on. My battery was around 25% or so.
If it is not plugged in then no combination of button presses will produce any result.
If it is plugged in then it boots to the first logo flash and then reboots.
If it is plugged in and I boot to download mode then it flashes the download mode screen and reboots.
If it is plugged in and I hold down the power button then the power button flashes rapidly.
I left off for a couple hours and then plugged it in for a couple hours just in case it did need to charge, but it did not produce any change in results.
I am fairly certain that the fix described in http://forum.xda-developers.com/showthread.php?t=2039707 will work. I can also just return my phone since it is only one day old.
However it looks like there might be a fair number of people having this issue so I would like to look into preventative measures so that it does not have to happen. Other than not using the phone if it starts to get hot, does anyone have any ideas of where to check? Are there any files that can be changed to help the phone not get stuck in the pre-boot phase? I know we can change the temp that the phone shuts down at, but given that my phone actually was pretty hot I doubt that is a good solution.
Get a new phone and immediately turn on eco mode. My phone has never gotten hot during heavy usage and you won't notice any difference performance wise. You may notice better battery life, although, I haven't seen much improvement.
Sent from my LG-E970 using xda premium
Joecascio2000 said:
Get a new phone and immediately turn on eco mode. My phone has never gotten hot during heavy usage and you won't notice any difference performance wise. You may notice better battery life, although, I haven't seen much improvement.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
That is what I did with my first phone (I have two). I didn't on this phone because I wanted to see if there was any performance difference I could notice. It didn't seem any faster, but I only got to use it about 45 minutes before it overheated.
I will most likely return it, but I really do want to see what I can do to help out the people that won't have that option. I like fixing things so it is a hard choice.
Stock with jellybean?
You're pulling my leg, aren't you citizen?
Sent from my LG-E970 using xda app-developers app
That's not good to hear. Hopefully you just got a bad batch and it won't affect too many people. Makes me kinda worry but luckily mine has never gotten that hot or too hot, like i heard around here.
jefffeely said:
Today my stock phone with JB overheated..
Click to expand...
Click to collapse
Are you sure you're in the right thread?
I'm assuming by "stock with jellybean" he means no N4 conversion was done on that device
MrZim4 said:
I'm assuming by "stock with jellybean" he means no N4 conversion was done on that device
Click to expand...
Click to collapse
This one. I sat and stared at my screen for 15 minutes trying to decide the best and shortest way to word that. I guess I failed.
I ended up returning my phone. I turned on Eco mode as soon as I could as was suggested. I noticed my phone was starting to get just as hot as before so I double checked and Eco mode had turned off. I am keeping an eye on it, but I have still had it get pretty hot a couple times. Mostly when I am downloading a lot and have the screen on. I'm staying safe by not using it for long periods of time, but that is going to get old pretty quick )= If it is a bad batch thing I suppose it would make sense that this one is bad too since I got it from the same store just two days apart.
I scared to see what is going to happen when I use LTE for the first time tomorrow lol.
My first LGOG did this. Within a week of purchase.
Sent from my Nexus G using Tapatalk 2
How hot are we talking here for it to over heat. I've been up to 71°c on the CPU and 46°c on the battery. It felt really hot to the touch. But it continued to work.
Sent from my LG-E970 using Tapatalk 2
I posted a mod in the dev section that should resolve this issue. Just choose optimized stock for a regular experience that'll appropriately throttle to maintain a reasonable temp.