Out of nowhere my DNA began to overheat like hell, can't seem to find the issue. Doesn't seem like any app is creating the problem, and the only recent apps I downloaded were a few games. I even tried doing a factory reset, yet the problem persists.
Phone temperature goes up to around 43.5 C, 110 F degrees.
My current installed ROM is Cynogenmod, and I tried updating it to a more recent version (10.2.0-RC1), yet the problem won't go away.
I really don't know what else to do. At this point it seems like a hardware problem, but has this happened to anyone else?
Same thing is happening to me since i flashed an updated Cyanogenmod 4.4 rom. I tried factory reset and flashing a different rom but no luck.
Related
No matter what ROM I try some where down the line (either 1 week, or 1 month etc) i always get the same result. Which is that htc sense stops loading. I have no idea what the problem is and its quite frustrating. i soft-reset, nothing, i turn off sense and turn it back on, nothing. always the same problem. has anyone encountered this before?
Can you give more information? Like what radio version do you use? Does a hard reset tempory help it? What things did you change before this occured?
Yes, I had this happen too. Ultimately, I put the stock ROM back on with the stock radio - kept happening. Sent it back and got a refurbed unit. Absolutely no problems now.
Im having tha same problem
Try Task 29 and then new ROM
Although there is not much of a description of the problem, I strongly believe you may have re-flashed custom ROMs without doing a Task29 which "cleans" the internal FLASH ROM. If this would happen to be the case you get these types of problems where suddenly the Phone just shuts down. Even after HardReset you will only be able to run for a limited time before the phone freezes again.
So give Task29 a shot and see if it helps.
Ps: Also try using a recommended RadioROM for a particular custom ROM.
jorgeni said:
Although there is not much of a description of the problem, I strongly believe you may have re-flashed custom ROMs without doing a Task29 which "cleans" the internal FLASH ROM. If this would happen to be the case you get these types of problems where suddenly the Phone just shuts down. Even after HardReset you will only be able to run for a limited time before the phone freezes again.
So give Task29 a shot and see if it helps.
Ps: Also try using a recommended RadioROM for a particular custom ROM.
Click to expand...
Click to collapse
ive used task 29 every time ive flashed over the months, so its not that... ive used every single reccomended for each radio rom but always the same outcome.
what could it be? ive got a little feeling its got something to do with CHT, as its only when i play around with it alot that it happens.
Same, here. Thought it was my energy ROM but have tasked 29, tried different ROMS from different chefs and radios, taken SD card out all together, only works for a matter of minutes before sense freezes and needs a battery reset, very frustrating - any other suggestions?
I did experience similar issues. In my case I've been using Artemis series of ROM v23, 25 and 28. In my case I did not use T29 the first couple of times. When using v28 of about couple of weeks sense would stop running. In my case it happened after receiving an MMS where I subsequently had to pull the battery to reboot. Ones on reboot I noticed in the file manager that the internal ROM was filled with strange symbols and unrecognizable file names. I did a HardReset to clean up (I thought). The filesystem looked okay, but after that HR Sense would run for a few minutes depending on whether I tried to re-install contacts and settings or left it be. After every freeze I had to do a HR to actually be able to reboot, otherwise it would stop at the orange screen.
What I've done is to upgrade to HSPL3 (2.08 HSPL), TASK 29 and install the latest V.30 (I reckon in a few days it is obsolete ones again ) Now everything is rosy-dandy and running like a clock (knock wood).
I'm using Radio 2.09.51.03_2 on Artemis 30 (NOR). Phone is about 8 months now, and I have not had any problems until a week ago where the above happened.
Fingers crossed!
Still running good...
just to follow up... phone is still working good so it seems Task 29 is indeed a necessary thing to do.
so this never happened to me until I flashed LPQ. I had lpq running for a couple hours. then my phone started saying charging paused voltage too high, but my phone isnt even plugged in, it also says its charging. when it wouldnt stop I decided to go back to my turkbey backup, that made the issue stop. the same thing happened when I flashed 3 different LPQ roms.
anyone have any clue why this is happening? I thought it was a charging port issue until it only happened on LPQ
No one?? 169 views and nothing?
Are you wiping everything in CWM before flashing?
many people reporting this issue but no reliable fix for now.only solution was getting back on GB
korado said:
many people reporting this issue but no reliable fix for now.only solution was getting back on GB
Click to expand...
Click to collapse
at least im not the only one lol hope it gets fixed soon!
I had this problem on stock ginger ya phones too hot i unpluged bat then put phone in my fridge for 5mins on an old post i made i said this the case is thin why because this phone gets too hot they need a lil fan but the battety is not there or to small as for being of charge mine to all ya issues.
Sent from my GT-I9100 using XDA
did you do a full wipe (including cache) before you flashing it ?
sinancetinkaya said:
did you do a full wipe (including cache) before you flashing it ?
Click to expand...
Click to collapse
yes I did a full wipe. its happened on every LPQ ive tried when I go back to GB no more problems
armyms25 said:
yes I did a full wipe. its happened on every LPQ ive tried when I go back to GB no more problems
Click to expand...
Click to collapse
this is so FRUSTRATING!!! I flashed turkbeys ICS full wiped did everything like im supposed to and having the exact same problem again!! Why doesnt my phone like LPQ?
A weird issue of mine as well...
armyms25 said:
so this never happened to me until I flashed LPQ. I had lpq running for a couple hours. then my phone started saying charging paused voltage too high, but my phone isnt even plugged in, it also says its charging. when it wouldnt stop I decided to go back to my turkbey backup, that made the issue stop. the same thing happened when I flashed 3 different LPQ roms.
Click to expand...
Click to collapse
The only thing I can think of to fix this issue is to reflash the phone. But make sure to clear the dalvic cache, the regular cache, and do a factory reset before you flash it.
On another note that would relate to this thread, my phone is running fine with this new ICS, except for the fact that my screen lock doesn't show up everytime I press the power button to put it into sleep mode. Not even when I leave it alone for the backlight to go off by itself. I've tried changing the security settings, changing the security feature to everything available (facelock, pin, pattern, etc.) It doesn't even show up when there is no security feature at all.
Any help or info about this is very much appreciated. Thanks in advance!
-Davin
Daaaavinnn said:
The only thing I can think of to fix this issue is to reflash the phone. But make sure to clear the dalvic cache, the regular cache, and do a factory reset before you flash it.
On another note that would relate to this thread, my phone is running fine with this new ICS, except for the fact that my screen lock doesn't show up everytime I press the power button to put it into sleep mode. Not even when I leave it alone for the backlight to go off by itself. I've tried changing the security settings, changing the security feature to everything available (facelock, pin, pattern, etc.) It doesn't even show up when there is no security feature at all.
Any help or info about this is very much appreciated. Thanks in advance!
-Davin
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=22645081#post22645081
I am going CRAZY!!!! so now I flashed LP7 through odin everything went fine. then after a couple minutes, the exact same issue I have no clue whats going on. I never ever had this issue before LPQ and LP7, I mean Never!!!! does anyone have any clue what i can do? i really want LPQ and LP7 on my GS2!!
anyone?? I came from turkbeys Gingerbread. I went to turkbeys ICS, i wiped everything in CWM flashed his ICS and still having this issue. i have no idea whats going on.
Hi, I'm having the same problem with my S2 since I've installed ICS....I gotta mention that I installed ICS on another S2 and everything went just fine...But this time, i just don't know what went wrong so that a notification about baterry voltage keeps beeping every 3 sec...How can I solve this problem? Should any other installation of another version of GB fix this problem? I just can't use my S2 normally...Pls help me!!!
Hello,
I got XPERIA Mini Pro a couple weeks ago. It was on stock firmware with android 4.0.4. It's warranty ended a long time ago but the phone was still in a very good shape. I really like trying custom ROMs from different developers as I did on my previous XPERIA X10i. So I chose Unofficial CM11 from LegacyXperia with KitKat for start. I unlocked bootloader without any problems. Flashed kernel with flashtool, then flashed ROM with kernel's build-in recovery. It worked fine although sometimes It hung when I wanted to wake my phone and I had to pull battery out. It happend occasionaly and I though I can live with that. But after a couple days proximity sensor as well as front camera gone. I tried whiping cache, factory reset, pulling battery out for about 20 seconds, flashing ROM again, even flashing stock firmware again. Nothing helped. I did research and it appeared that this is common problem with mango after android 4.2. I think. OK, I thought I can live with that. I returned to CM11 but after a while problem with hungs on wake up started to annoy me. I decided to try the highest cyanogenmod for mango on stable stage of development, not nightly like CM11. It was CM9.1. Again, it worked fine and in fact, it was stable. But after a while I noticed that not only front camera and proximity sensor are gone but ALL OF MY SENSORS died. I tried a couple of things like before (whipe, reset, flash etc.). Tried going back on stock. Tried apps from market which test and reset sensors. Every one I tried said my phone does not support sensors. Accelerometer is crucial for me as I use SleepAsDroid app every day. I flashed CRDROID (based on CM11 but much much more stable) which I use till now. Tried doing research on Internet but I found nothing. Tried hitting my phone and dropping It (that helped a lot of people), tried heating battery by overloading processor (that helped a lot of people too). Nothing helped. Tried repleacing files responsible for sensors with the ones from stock firmware. Now test programs show that I have working light sensor but it does not change it's values at all. I accepted the fact that I won't restore my sensors but I must ask:
Is there anything more I can do? Did I missed something?
Is the only way to fix my problem buying a new motherboard? It appears strict hardware problem, right?
Please help, any suggestion will be much appreciated.
Best regards
Xiaomi Note 3 Pro 2/16GB
Hi,
i am currently on a nightly cm13 build. before i had the same issue on the snapshot build.
Used also different kernels but with the same results.
Issue is shown in the video below.
https://www.youtube.com/watch?v=HI43XX0WIpY
This happens probably once a day and only when i am waking up the phone from deepsleep with the fingerprint sensor.
The screen keeps being black for a second when this happens. When i turn off the screen and wake it up again, everything is fine.
What do you think, hardware or software issue?
EDIT: Just found out, that it could be potentially a LiveScreen issue on cm13
EDIT2: No, LiveScreen is not the problem
I'm also facing this issue. Are you using any custom kernel?
I'm using the Blaze kernel.
Yes, was using Blaze kernel as well but i tried different others as well.
I am now on Exodus ROM without these issues.
Seems to be a cm bug.
I've had the issue also while charging my phone last night.
CM13 with Redon kernel.
Scared the sh*t out of me...
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
MiripRedmoon said:
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
Click to expand...
Click to collapse
i know its long time ago, but could you repair the device?
screen glitches
same problem, flickering and mistyping too. Please anyone resolve, this has happened after the latest update
I had this issue, rom and kernel reinstall solved the problem. Maybe something is cached/crashed or both (the phone acted weird other ways too, random apps crashed and so on), before reinstall wipe cache, dalvik, data and system, then install the latest versions of the rom and kernel you want to use. Don't forget to flash firmware.
Since I did this everything is fine.
Title says it all, made the mistake of upgrading to Oreo and now stuck with relentless battery drain issues. Tried everything short of reflashing so far and failed. Nearly everything is disabled even after full wipe and reset (hard) and its still pretty bad in terms of battery life. So I signed up here looking for ways to salvage the hardware, perhaps by downgrading back to Nougat if I still can or installing something better and different altogether. I've read folks having luck with the cell standby drain by installing a nougat/oreo mash but couldn't find specific details on how to do this. Also this doesn't seem to fix the android system drain issue but its at least a start. I have basic experience using Kies and Odin, helped a couple relatives with boot looping tabs in the past. Please advise on the best path forward to make use of my new phone.
Have you tried installing 7.0?
What version of Oreo did you install? I myself installed a TMO Ver G930TUVU4CRI2 but running on ATT network. I rooted and debloated and I am blown away how smooth this runs with fantastic battery life.
Read Here Link: https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-g930tuvu4cri2-t3864700
edwardmorris said:
Title says it all, made the mistake of upgrading to Oreo and now stuck with relentless battery drain issues. Tried everything short of reflashing so far and failed. Nearly everything is disabled even after full wipe and reset (hard) and its still pretty bad in terms of battery life. So I signed up here looking for ways to salvage the hardware, perhaps by downgrading back to Nougat if I still can or installing something better and different altogether. I've read folks having luck with the cell standby drain by installing a nougat/oreo mash but couldn't find specific details on how to do this. Also this doesn't seem to fix the android system drain issue but its at least a start. I have basic experience using Kies and Odin, helped a couple relatives with boot looping tabs in the past. Please advise on the best path forward to make use of my new phone.
Click to expand...
Click to collapse
I feel your pain. I was in the same situation, spending days to find a solution to these battery drain while stuck on this buggy version. And I tried everything...basic battery saving related stuff, disabling pretty much everything on the phone, monitoring everything, even changing the battery.
For now, the only thing that fix the problem for me was using a 3rd party app to force the phone to connect to none LTE network. I don't know where the bug lies: android, samsung or att side? or maybe it is because I'm out of US on another carrier who is using other freq but it is a shame. I don't think there will ever be a fix for that unfortunatly...