[Q] Overheating problems, cant switch back to 4.2.2 - T-Mobile Samsung Galaxy S 4

This is my first time posting in this, so please excuse me if I put this topic in the wrong place or anything.
Recently I have installed a Cyanogen rom to my phone, upgrading it to 4.4.4 kitkat. Wel, everything went well. Though, recently it has been getting really hot. I mean, before I installed the rom, I was on 4.2.2 and I never had a problem like this. I mainly use my phone for games and my phone has never gotten hot to where the screen is really hot.
I bought a new battery, didn't work. Calibrated it, didn't work. Tried a fresh install, again did not work.
I tried going back to 4.2.2 but no rom that I find works, only one to work is 4.4.2 and it still over heats.
Any advice?

If you have a micro sd card in it, turn the phone off, let everything cool down, remove the battery cover, now place your finger on the micro sd card slot and turn the phone on. If it gets really hot in about 10 seconds, remove the micro sd card. Try running the phone without the micro sd card to see if that is causing the heating issue. Could be an old micro sd card or a failing micro sd card. Be sure to use a decent speed Class 10.

mar11974 said:
If you have a micro sd card in it, turn the phone off, let everything cool down, remove the battery cover, now place your finger on the micro sd card slot and turn the phone on. If it gets really hot in about 10 seconds, remove the micro sd card. Try running the phone without the micro sd card to see if that is causing the heating issue. Could be an old micro sd card or a failing micro sd card. Be sure to use a decent speed Class 10.
Click to expand...
Click to collapse
I have done that before, still get hots without it. Thansk for the advice though

Are you using a kernel that is overclocking your phone? That would be one possible cause of overheating that starts as soon as you installed a different ROM. What kernel came with it?

lalec said:
Are you using a kernel that is overclocking your phone? That would be one possible cause of overheating that starts as soon as you installed a different ROM. What kernel came with it?
Click to expand...
Click to collapse
Sorry i'm new at this whole thing, how would i find what kernel it is?

lalec said:
Are you using a kernel that is overclocking your phone? That would be one possible cause of overheating that starts as soon as you installed a different ROM. What kernel came with it?
Click to expand...
Click to collapse
I believe this is the kernel?

You could try the last stable cm build. Although, I'm running the latest nightly and am not having your issues.
Or
You could Odin back to stock and start over.

Android_Monsters said:
You could try the last stable cm build. Although, I'm running the latest nightly and am not having your issues.
Or
You could Odin back to stock and start over.
Click to expand...
Click to collapse
I have countless times gets hot even when using original stock. Will. Or won't let me go back to 4.2.2, only 4.4.2

It could be a rough app running in the background.. Its happened to me a few times.. Check battery and CPU usage to make sure there are no misbehaving apps

serio22 said:
It could be a rough app running in the background.. Its happened to me a few times.. Check battery and CPU usage to make sure there are no misbehaving apps
Click to expand...
Click to collapse
How would i go about that? I only donwload a few, but it heats up even before i donwwload any

Related

Can internal memory be corrupted??????

Hey Guys,
I've been some flashing lately and I'm not sure what caused the problem. I've been using SprintLovers Rom with no issues since Feb. But when it stopped being supported, so I switched over to [ ROM / 5-3 ] Calkulin's EViO 3 v1.0 Beta 2 [ 4.12 l Gingerbread l Tweaked ] (which IO loved by the way)but I kept getting constant reboots. I would be using Navigation or watching a video with Rock Player and within one min , my phone would go into a boot loop and stay rebooting until and I flashed the rom again. It drove me nuts and I couldnt take it anymore.
So I reformatted everything (even deleted my card by accident) and installed [MikRoms] - [6/7/2011] - MikG v1.03 - Re-Engineered GB Sense 2.1 + 3.0 (which I also love) and the reboots are not as frequent but they are still happening. The difference is that with this rom, its getting stuck in a boot loop at the HTC EVO 4G screen that you see when it boots up. If it does boot up, the phone gets to the Sense screen and reboots again. So the only way I can get it to boot back up is to flash the rom again from recovery.
I have a 32GB Duracell Microsd Card I got off Amazon: http://www.amazon.com/gp/product/B004AM6SOG
It worked perfectly with Sprintlovers rom, But as soon as I reformatted and flashed Calkuns rom, the reboots started,. I even tried using Nandroind and going back to a Sprintlovers backup and the reboots were happening on that rom and I never had issues with that rom.
So basically I'm trying to narrow down what is causing the rebooting. I thought maybe the memory card was going bad, but how can I tell? So what I started thinking was maybe my bootloader needs to be refomattted or cleaned? But I dont know how. Then after talking to Nick1313, who helped me reformat and get my phone running again, we started thinking maybe the internal memory of the phone has gotten corrupted. I assume that Android looks to boot the OS from the internal memory and then looks to the SD card for apps and etc....
Is there a way to test my SD card to see if its ok? is there a way to see tell if my internal memory is corrupted and if so can it be reformatted and fixed?
I saw some people having a similar issue in the Galaxy S forums,but no one seemed to have a solution.
My last resort is unrooting and returning my phone to the store tomorrow. The only problem with that is , I know they are gonna have to order me one and it wont be in until Monday or whatever and the is annoying.
Any ideas would be greatly appreciated.
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
jesuspgt said:
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
Click to expand...
Click to collapse
Thanks for the reply. I actually Flashed back to Sprint Lovers Rom last night to after deleting everything again and reboots were still happening. I flashed back to MikG rom this morning. No reboots as of yet. But it rebooted on me 5 times last night before I flashed Sprintlovers.
GPS has been the main app I've busing when the rebooting starts. So I'm testing my phone right now with having it map to a far location and keeping my screen on to see how long it takes to make my phone reboot. Right now I'm 3mins into the test.
Turns out the processor in my phone is bad and Sprint has to order me a new one

MicroSD dead?

Running stock 4.1.1 rooted. My external micro SD has been taking awhile the last week to read the card. It eventually would see the card and all was good. Today the phone shut off and I had to take the battery out to reset the phone. When then phone booted back up the ext sd is not seen by the phone. I have tried the SD in my PC and it reads fine. I have also tried another SD card I have in the phone, no go. All else is working fine on the phone. Any other suggestions as to how to diagnose the issue. I am leaning to a hardware issue obviously. Would it per chance help to upgrade to 4.1.2?
gandalf21502 said:
Running stock 4.1.1 rooted. My external micro SD has been taking awhile the last week to read the card. It eventually would see the card and all was good. Today the phone shut off and I had to take the battery out to reset the phone. When then phone booted back up the ext sd is not seen by the phone. I have tried the SD in my PC and it reads fine. I have also tried another SD card I have in the phone, no go. All else is working fine on the phone. Any other suggestions as to how to diagnose the issue. I am leaning to a hardware issue obviously. Would it per chance help to upgrade to 4.1.2?
Click to expand...
Click to collapse
Hi,
If all doesn't go well, try a factory reset.
I had the same issue before on my HTC Sensation.
Strangely enough, not complaining, after a few hours the phone found the SD card. For now working again. I am sure this won't last. I believe I am going back up and do a factory reset...
MICRO SD's FAIL on Samsung OR Samsung Fails on Micro SD's
gandalf21502 said:
Running stock 4.1.1 rooted. My external micro SD has been taking awhile the last week to read the card. It eventually would see the card and all was good. Today the phone shut off and I had to take the battery out to reset the phone. When then phone booted back up the ext sd is not seen by the phone. I have tried the SD in my PC and it reads fine. I have also tried another SD card I have in the phone, no go. All else is working fine on the phone. Any other suggestions as to how to diagnose the issue. I am leaning to a hardware issue obviously. Would it per chance help to upgrade to 4.1.2?
Click to expand...
Click to collapse
Hi mate. i had the S3 and changed it to Note 2. All came with 16gb internal and had Sandisk 32gb on external. I recommended the same to my work colleagues here in China. Well in a couple of months the SD's in all of our phones got fried up. It started with errors, slow reading, then requesting to format. in the beginning phone couldn't read them, and finally PC's as well. Many people face the same.
In forums some people say that SD cards of 32Gb and 64GB due to high market demand have been copied therefor the problems. That could be a cover up for a Samsung problem, but my IT told me that those SD cards are series 4 which are outdated, but there are almost all of them series 4 here. So he recommended to go for the 8 or 16gb which are more stable. i Got 16gb and for a couple of weeks, so far so good. I don't know if the problem persists with series 10 though. Back up your files frequently so you will not cry over spilled milk till we'll see what happens.
I put a 8gb in my phone, same issue. So far still working...but I am backing up and updating...

[Q] SD card eating all free RAM

Hello,
I seem to have a problem where my SD card eats all of my RAM. I'm running AOKP JB 4.1.2 Milestone 1 ROM and I have a 32GB G.Skill class 6 SD card on my SGH-T999
I've been running the ROM for some time with this SD card and never had any issues until lately. My phone will get sluggish and eventually get to the point where it has trouble opening anything. I will go to open the dialer and it will force close back to desktop,rendering the phone practically useless. The phone just instantly kills any tasks to keep the system itself alive. If I restart, I have all my free RAM back but I can see it goes down a few MB every few seconds until there is only about 60 left.
I noticed when I remove the SD card, this stops completely. So at first, I tried reflashing said ROM above. As soon as I got back in, it was still doing it. So I reformatted the SD card, and left it blank, and inserted it, and it started this again.
So my question, why is this happening, and how can I fix it? Since it seems to be isolated to the SD card and not the OS, is it possible the SD card is going out? I've only had it for about 6 months and only ever kept music on it.
darksniper42 said:
Hello,
I seem to have a problem where my SD card eats all of my RAM. I'm running AOKP JB 4.1.2 Milestone 1 ROM and I have a 32GB G.Skill class 6 SD card on my SGH-T999
I've been running the ROM for some time with this SD card and never had any issues until lately. My phone will get sluggish and eventually get to the point where it has trouble opening anything. I will go to open the dialer and it will force close back to desktop,rendering the phone practically useless. The phone just instantly kills any tasks to keep the system itself alive. If I restart, I have all my free RAM back but I can see it goes down a few MB every few seconds until there is only about 60 left.
I noticed when I remove the SD card, this stops completely. So at first, I tried reflashing said ROM above. As soon as I got back in, it was still doing it. So I reformatted the SD card, and left it blank, and inserted it, and it started this again.
So my question, why is this happening, and how can I fix it? Since it seems to be isolated to the SD card and not the OS, is it possible the SD card is going out? I've only had it for about 6 months and only ever kept music on it.
Click to expand...
Click to collapse
A media scan running against it?
Did you try fix permissions in recovery?
Update your ROM to a newer aokp build.
Are you restoring data from backups?
Some offending app you have loaded?
I can't be sure so I threw out some things to try.
Try shawn157 aokp builds. Very smooth and compiled for speed with linaro tool chain.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Try shawn157 aokp builds. Very smooth and compiled for speed with linaro tool chain.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I agree, super smooth and stable ROM, definitely worth trying out.. You should really upgrade to a newer aokp build, there's 4.2.2 now
Sent from my SGH-T999 using Tapatalk 4 Beta
TomTcom said:
A media scan running against it?
Did you try fix permissions in recovery?
Update your ROM to a newer aokp build.
Are you restoring data from backups?
Some offending app you have loaded?
I can't be sure so I threw out some things to try.
Try shawn157 aokp builds. Very smooth and compiled for speed with linaro tool chain.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I've scanned the card for errors, and received none. I have tried fixing permissions as well. I only ever do clean installs, never backups.
Also when I cleaned installed last time trying to figure this issue out, there was no apps installed.
But I will try your suggestion and try said ROM above. I know mine is a little outdated, I've just never bothered to update since I cracked my phone screen some time ago, so I just don't have the love for this phone like I used to. I plan on an S4 soon.
On a side note, Windows has no problem with the SD card, reading or writing. And it's formatted FAT32. I just don't see the connection between the SD card and my RAM. Oh well....thanks for the info, appreciate it.
You can try the other Rom first of course, but if it doesn't help you should Odin flash the root66 firmware. Anytime you have issues you can't resolve, the best way to troubleshoot is from the official build.
It could be there is a corrupted block on the sd that the phone can't handle, but the computer can. Try formatting from the computer using the formatting utility from a sdcard.org.
Another option would be to partition it from the computer. (Try a 28-30GBP partition).
Another thing you can do is show cpu usage in developer options. It may help you see any process that might be getting hung up. Also check under Settings, Battery. (Charge full, then let it run to about 93%) (the media scanner was one thing that used to hang easily and eat resources, so watch for that or similar)
Borrow an sd from someone just to try it. It is very possible that even though it looks sdcard related, it may not be at all. (Stranger things have happened!) If it acts the same with another card, that means the card is not the source of the problem.
Sent from my SGH-T999V using xda premium

Need help regarding SD EXT

i've partitioned the card and stuff, am S-Off and on mildwild, i wanted to ask that does removing the battery corrupt apps? i was running vj's 4.1.2 rom and when i removed the battery and reinsterted it, it caused all the apps to malfunction, they were kinda greyed out, what's the theory of this?
Hard to know the exact 'theory', also depends on what you were doing when you removed the battery. Things just get corrupted sometimes, was it all your user apps?
On your previous thread you stated you used gparted to partition the sd card, so this shouldnt have caused any issues as long it was just a FAT32 and ext4 partition, no swap.
Anyway, try not to remove the battery unless there's no other option..
Probably wrong installation caused a misunderstanding between the phisical memory and mounting point for the OS. Another possibility is that the OS change, by a fail, the name of the SD card.
Try to no retire the battery unless it's completely necessary
KR
Enviado desde mi HTC Desire
eddiehk6 said:
Hard to know the exact 'theory', also depends on what you were doing when you removed the battery. Things just get corrupted sometimes, was it all your user apps?
On your previous thread you stated you used gparted to partition the sd card, so this shouldnt have caused any issues as long it was just a FAT32 and ext4 partition, no swap.
Anyway, try not to remove the battery unless there's no other option..
Click to expand...
Click to collapse
thank you guys, yes, i partitioned using 4ext this time, and i had to remove the battery to change my sim card, it corrupted all the apps, the ones which i installed myself like outlook, whatsapp and stuff, the ones in the phone's system were ok
jafferkhan said:
thank you guys, yes, i partitioned using 4ext this time, and i had to remove the battery to change my sim card, it corrupted all the apps, the ones which i installed myself like outlook, whatsapp and stuff, the ones in the phone's system were ok
Click to expand...
Click to collapse
As in you pulled the battery while the phone was on, just to change SIM?
Next time power off the phone properly before you do this (hold down power, select power off). If you did that probably wouldn't have caused any issues..
eddiehk6 said:
As in you pulled the battery while the phone was on, just to change SIM?
Next time power off the phone properly before you do this (hold down power, select power off). If you did that probably wouldn't have caused any issues..
Click to expand...
Click to collapse
Thanks for replying dude...I did turn off the phone before removing the sim card. I think it's just a faulty rom... can you suggest me a stable, fast daily driver ics rom? Tired of being on gingerbread now... need a fast and smooth ics rom that is stable, ics everything working and can be used as a daily driver
jafferkhan said:
Thanks for replying dude...I did turn off the phone before removing the sim card. I think it's just a faulty rom... can you suggest me a stable, fast daily driver ics rom? Tired of being on gingerbread now... need a fast and smooth ics rom that is stable, ics everything working and can be used as a daily driver
Click to expand...
Click to collapse
Not sure you can conclude it was definitely the ROM unless lots of other people have the same issue on reboot, but still does sound strange.
Never used an ICS ROM myself, though I don't think it ever reached fully 'stable' as development shifted more towards JB. People still swear by whichever ROM they settle on to be honest: what is "fast, stable, smooth, daily driver" requirements differ between people.
I'm still on GB ROM personally. Don't think all JB ROMs will have the same problem as you, and like I said may not have been due to your ROM. Read a few of the threads and try a few, is always the best way to find out yourself. Sorry can't give actual experience.
eddiehk6 said:
Not sure you can conclude it was definitely the ROM unless lots of other people have the same issue on reboot, but still does sound strange.
Never used an ICS ROM myself, though I don't think it ever reached fully 'stable' as development shifted more towards JB. People still swear by whichever ROM they settle on to be honest: what is "fast, stable, smooth, daily driver" requirements differ between people.
I'm still on GB ROM personally. Don't think all JB ROMs will have the same problem as you, and like I said may not have been due to your ROM. Read a few of the threads and try a few, is always the best way to find out yourself.
Understandable bro thanks
Click to expand...
Click to collapse

[Q] device reboots always

Hi xda folks.
in short:
Phone is s-off and rooted through revolutionary.
Lately I flashed a new rom [ROM][Android 2.3.7][Oxygen_r2 HBOOT]MIUI 2.3.7c modded by moss20.
I did run the a2sd+ installations scripts as documented on the rom thread.
One week after flashing, phone became slow and lagging.
Eventually one week later phone was down out of battery without me noticing.
Since then phone reboots after entering my pin code or later.
How can I figure out where the issue originates?
For those who wants more details here is the full history:
My phone is 3.5 years old. I never had problems. And succeeded for a long time to s-off, root and flash roms thanks to this forum.
I have a 8Gb class 4 sd card with 4Gb fat 32 partition followed by one 4Gb of ext4.
Latelly flashed that Miui based rom http://forum.xda-developers.com/showthread.php?t=1725629. I used the oxygen r2 Hboot, the little rom version and activate the a2sd+. After a week the phone became really slow and lagging. Then eventually I found my phone off, abnormally out of battery without noticing how it happened.
Since then it is rebooting from the moment I have entered my pin code.
I thought that flashing a new rom (sense rom) would help but the problem persits. I then used a bigger hboot from alpharev and flashed the sense rom again. It didn't help.
I had a little improvement when completely repartitionned the sd card with 6Gb fat32 partition followed by a 1 Gb ext4. Since then it do not always reboot after entering pin code. It somes times stays up for 10 minutes before rebooting. Using some apps on the phone most likely quickly trigger a reboot.
The last thing I did with no success is to reset stock Hboot and RUU following suggestion of http://forum.xda-developers.com/showthread.php?t=1103520. Behavior is the same as the last one.​
I have no backup.
Any help to spot or fix that reboot issue would be greatly appreciated I love this phone
75 view but no reply?
Is my post wrong? Too long?
I need at least some leads the find investigation paths.
I have the feeling it could be related to the access to the SD card. Because It is the 1st I executed manually the a2sd+ installation scripts. How can I check that?
Or is it possible that some tweaking in the MIUI based rom (see link in OP) brought instability (voltage, ...)?
AntoineWils said:
75 view but no reply?
Is my post wrong? Too long?
I need at least some leads the find investigation paths.
I have the feeling it could be related to the access to the SD card. Because It is the 1st I executed manually the a2sd+ installation scripts. How can I check that?
Or is it possible that some tweaking in the MIUI based rom (see link in OP) brought instability (voltage, ...)?
Click to expand...
Click to collapse
1st, don't be impatient
What recovery do you have installed?
If you have trouble just after installing/activating an a2sd script it could have something to do with your partitions.
The best known method to partition/format your sdcard is using 4ext recovery.
Another problem could be the sdcard itself, maybe try another if handy.
What could help in general is power off phone, remove battery and eject/insert sdcard a few times,
just in case there's a little contact problem.
You should always be aware of what hboot you use for your rom, so what rom do you actually use and what hboot have you flashed?
tom0769 said:
1st, don't be impatient
What recovery do you have installed?
If you have trouble just after installing/activating an a2sd script it could have something to do with your partitions.
The best known method to partition/format your sdcard is using 4ext recovery.
Another problem could be the sdcard itself, maybe try another if handy.
What could help in general is power off phone, remove battery and eject/insert sdcard a few times,
just in case there's a little contact problem.
You should always be aware of what hboot you use for your rom, so what rom do you actually use and what hboot have you flashed?
Click to expand...
Click to collapse
Recovery: the one installed via revolutionary.
The trouble did not come immediately after installing a2sd+ but 2 weeks after.
I am using GParted to partition my SD card (and repartionned several times since issue stared)
I did not try an other sd card but I will try.
I did eject/insert the sd card lots of time since the issue started.
When the problem occurred I had HBOOT oxygen r2 from alpharev.
currently I am back on stock (and issue persists):
HBOOT (0.75.0000, S-ON),
rom (RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U_4.05.00.11_release_121684),
radio 4.05.00.11
I can root and S-OFF + recovery whenever needed.
Today my phone stayed up for 12 hours.
It was charging almost all day long.
Could my issue be related to battery issue?
My problem started when I noticed the battery was completely uncharged. Until today I did not charge it more than necessary to be at 100%
I checked the contacts and they look ok (not bend and straight).
AntoineWils said:
Today my phone stayed up for 12 hours.
It was charging almost all day long.
Could my issue be related to battery issue?
My problem started when I noticed the battery was completely uncharged. Until today I did not charge it more than necessary to be at 100%
I checked the contacts and they look ok (not bend and straight).
Click to expand...
Click to collapse
If problems still occur on stock unrooted firmware then it is likely a hardware rather than software problem.
Your setup looked correct before things went wrong. You partitioned your sdcard correctly with gparted, and your hboot wouldn't have anything to do with it.
You could try swapping battery, no harm in trying, see if that makes a difference.
eddiehk6 said:
... You could try swapping battery, no harm in trying, see if that makes a difference.
Click to expand...
Click to collapse
Thank-you eddiehk6, I hope it is the battery. It is going better but the phone remains unstable by moments.
I was not aware a battery could be so cheap for 'old' devices.
eddiehk6 said:
If problems still occur on stock unrooted firmware then it is likely a hardware rather than software problem.
Your setup looked correct before things went wrong. You partitioned your sdcard correctly with gparted, and your hboot wouldn't have anything to do with it.
You could try swapping battery, no harm in trying, see if that makes a difference.
Click to expand...
Click to collapse
A strange thing I noticed is that the phone can stays forever without rebooting on the "enter pin code" screen.
When I enter the pin code it reboots between instantly 30 seconds.
Isn't this proving that it is not an hardware issue?
I swapped the battery but it did not change anything.
The only thing I noticed is that without a sim card the phone is more stable. It still reboots but only every few hours. With the sim card inserted it reboots every few minutes if I am lucky.
How can the presence of the sim have an influence on this behavior?
Think you've got a hardware issue if it's still rebooting on stock ROM and after changing battery.
The SIM card will make a difference as it's connecting to a network, or trying to connect. Somehow it's causing instability -> reboot.
Only last thing I can think of is to s-off and flash latest radio version through fastboot. No guarantees this will work or make any difference.
I've got mildwild 5 and sometime when I'm using it or I want to take a pic the screen goes blank and I have to reboot it so annoying, what do you think the problem is?
Sent from my HTC Desire using xda app-developers app
try Evervolv Turba 4.0.0p2 ROM btw here is solution if phone overheats http://forum.xda-developers.com/showthread.php?t=2277365
Mine is starting to reboot for no reason.
Sent from my HTC Desire HD A9191 using XDA Free mobile app

Categories

Resources