When i flash any of the whyzor reloaded cm7 roms my triumph over heats, it's currently on a KANG build & dosen't ever over heat, anybody know why this happens ? Has this happened to anyone else ? Because i've tried the same setup on my wife's triumph and the same thing happens it starts to over heat. If anybody can help me with this that would be great, I love CM7 & would love to be running the newer release's, but not if there gonna over heat my phone, that's a deal breaker for me.
I'm using his newest build and have been using it since he posted it and haven't noticed it overheating... Are there any apps running?
no this happens from the moment i flash the rom, i even turned off the phone and let it cool down then just turned it on and thats all, and it still gets hot ? I haven't tried the 1-25 build that was just released but i would expect the same thing will happen, I'm tired of doing fresh install's of this rom just for it to start over heating again, well i'll probably flash it to find out but it's frustrating
Hmmm that is strange... But yea I would try a fresh install of his newest build and see if that stops it. I think I had problems with one of the builds overheating too... But I also had a bunch of apps installed...
Installed or running ? what's the point of a rom that overheats when apps are installed LOL
ok well i fashed the new one & this is weird i flashed fhe gapps to but no market ? And of course it started getting hot
Are you overclocking? Undervolting? If so, what are your settings? was it overclocked/undervolted from a previous install?
yes it's overclocked to 1.5gz on my current rom, but i format the system before i flash the rom & i don't overclock the new rom because it starts getting hot way before i can even get to that stage of the install ?
Were you undervolting at any point before?
no never undervolted ???
It's a very strange issue that you're reporting...
Try flashing the original theOC kernel right after you flash the rom. The kernel from here:
http://forum.xda-developers.com/showthread.php?t=1338825
So do the following in CWM:
1. Wipe/Factory reset.
2. Flash ROM.
3. Flash kernel.
4. Reboot and see what happens.
At least we can narrow it down to if it's something in the ROM causing it or if it's something in that changed in the kernel.
Do you want me to flash the 1-25 or the 1-26 build ? Then the kernel, what about the gapps ? Alright back in a flash LOL
Flash the 01-26 ROM, don't install any apps, see if it overheats, if so, flash theOC kernel, check again if it overheats, then if not, reinstall your usual apps. If it starts overheating, then it's an app you installed. 'Battery usage' should be able to point out what it is. Or settings - applications - running services will also help find it, uninstall it and let the developer of that app know.
i'm wondering if juice defender could be the suspect here ? what should i set my minimum to on my cpu settings ?
overheat
I had an overheating problem to but when I reflashed the rom it stopped.
jaaydogg said:
i'm wondering if juice defender could be the suspect here ? what should i set my minimum to on my cpu settings ?
Click to expand...
Click to collapse
To troubleshoot problems, disable ALL apps services to find a stable base, then start renabling each one individually until the problem comes back, then you know.
Related
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App
The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...
SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?
I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.
I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.
Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..
Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...
I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.
This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.
And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...
I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?
Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.
I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.
Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.
Hello android gurus/deities (too much?),
Just got my first smartphone, a Droid Charge. Great phone, especially for the price. The screen is freaking fantastic and of course Android is amazing as ever.
However, since first activating it, I seem to get random crashes. I can't replicate the problem, since it doesn't seem connected to anything visual. First time it happened when I decided to check out the camera, took a picture, and tried to view it. Other times have been the first time trying out netflix, first time sending a text. Seems to happen the first time I use some apps.
The crash basically consists of a short 5-10 second freeze followed by a reboot. Any ideas? Is this a hardware issue I need to have addressed or more likely a software issue that I just need to wait for updates to come along and fix it? Or is this a common occurence with Android and I just need to suck it up? lol
Edit: Has also happened 3 or 4 times while browsing the web, including this site...
charges hardware are pretty great for the price the software is a big issue for the charge whitch is why most of us myself included suggest rooting your device whitch literally a dummy could do using odin... i am running a stock based of a leak called infinity rom pretty amazing for a stockish rom for now so reboots are known at least for me but i really think the majority of the problem for this phone is the software gps loss signal going in and out as in data (this is a hit and miss) ..... hope this helped you iron things out...
Out of curiosity, what will rooting my device accomplish with respect to the reboots? Anything?
I rooted the device, then tried infinityROM but ran into so many problems I flashed back to the factory rom X(... Rooted again, but still get reboots, any ideas?
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
RevTorA said:
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
Click to expand...
Click to collapse
http://rootzwiki.com/topic/4847-guide-new-users-guide-everything-how-to-root-rom-kernels-radios-cwm/
Also depends what rom you are running.
If it keeps happening after you root and flash a new kernel (and maybe install a rom) upload a logcat to a filesharing place and hop on IRC to ask for help.
irc.andirc.net
#charge
Port 6666
Sent from my SCH-I510 using xda premium
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
RevTorA said:
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
Click to expand...
Click to collapse
PBJ is a Froyo kernel. It will only work with Froyo.
i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
76redrum said:
i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
Click to expand...
Click to collapse
Hi,
What version did you install?
3.6.8 or 4.1.8?
Did you do a MD5 checksum?
Did you super wipe?
Did you add any mods?
If you want help,you need to post more information...
Hi i had the same sort of problem with my ARHD but I find out that the faux kernel was causing for difficulties.
Installed a stock kernel and all problems solved.
Still respect all developers
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
76redrum said:
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
Click to expand...
Click to collapse
Hi,
It does sound like a kernel problem.
Try the kernel in my signature.
Absolutely no problems there.
ill try the stock kernel thanks to all
phone:htc senation
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any digestions would be very appreciated
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any sugestions would be very appreciated
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
seatown1two said:
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
Click to expand...
Click to collapse
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
---------- Post added at 03:15 PM ---------- Previous post was at 02:25 PM ----------
Hawke84 said:
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
Click to expand...
Click to collapse
Hi, i've been running the 3.6.x Roms for a while now and think they're great, but was getting interested in the sense 3.5 stuff. What in particular do you like about the 4.1.x roms? Just seeing if it's worth the full wipe effort .
Thanks
Mike
ArcticWolf91 said:
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Click to expand...
Click to collapse
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Hawke84 said:
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Click to expand...
Click to collapse
Lol yes, you are not the first to tell me that, and believe me lesson learned. Though I did mention that it was rooted and that it would be running this Rom. But yes now I am troubleshooting the phone with this person and I may have to give them a refund because they opened a case with eBay.
mrew42 said:
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
Click to expand...
Click to collapse
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
seatown1two said:
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
Click to expand...
Click to collapse
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
mrew42 said:
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
Click to expand...
Click to collapse
how do you up the speed for idle..silly question i know
Hey everyone,
After trying almost every single ICS ROM available for my O1 P500h, every ROM seems to have the same problem. Although they all run very good, the phone will just hang at random points, but mostly when installing apps. Then requires a hard reset battery pull, or will reset itself after about a minute. Does anybody know of a solution to this? It wouldn't really be that much of a problem if the phone didn't take so long to restart.
I've seen other users report this problem to ROM dev's as well however the problems seemed to be fixed for them by a newer update for the ROM, but even if I use the newest version I still get this problem.
It's not present on CM7, or Jelly Bean (4.1 or 4.2) ROM's as far as the ones that I've tried. I feel like I've tried every single ROM for this phone already. I wanted to move on from CM7 because of it's lack of new-ness compared to ICS and above, and on the other hand Jelly Bean ROM's don't have a lot of internal storage compared to ICS ones, which is a problem for me because I download lots of apps.
Any help would be greatly appreciated!
TheCrazyDirectioner said:
Hey everyone,
After trying almost every single ICS ROM available for my O1 P500h, every ROM seems to have the same problem. Although they all run very good, the phone will just hang at random points, but mostly when installing apps. Then requires a hard reset battery pull, or will reset itself after about a minute. Does anybody know of a solution to this? It wouldn't really be that much of a problem if the phone didn't take so long to restart.
I've seen other users report this problem to ROM dev's as well however the problems seemed to be fixed for them by a newer update for the ROM, but even if I use the newest version I still get this problem.
It's not present on CM7, or Jelly Bean (4.1 or 4.2) ROM's as far as the ones that I've tried. I feel like I've tried every single ROM for this phone already. I wanted to move on from CM7 because of it's lack of new-ness compared to ICS and above, and on the other hand Jelly Bean ROM's don't have a lot of internal storage compared to ICS ones, which is a problem for me because I download lots of apps.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
which recovery You are Using & How do you flash the Rom & what rom you flashed try CM9.2.0 By hephappy
umm
Amitosh said:
which recovery You are Using & How do you flash the Rom & what rom you flashed try CM9.2.0 By hephappy
Click to expand...
Click to collapse
I've tried TWRP, CWM 5.0.2.7 and CWM 6.0.2.7. I've been flashing by formatting everything but sdcard (so boot, system, data, cache, etc.) and then installing zip from sdcard. I tried flashing HepHappy's ROM, IcySnap, XperiaICS and Protos9.
TheCrazyDirectioner said:
I've tried TWRP, CWM 5.0.2.7 and CWM 6.0.2.7. I've been flashing by formatting everything but sdcard (so boot, system, data, cache, etc.) and then installing zip from sdcard. I tried flashing HepHappy's ROM, IcySnap, XperiaICS and Protos9.
Click to expand...
Click to collapse
Stock kernel..?
umm
Amitosh said:
Stock kernel..?
Click to expand...
Click to collapse
The stock kernels which come with the ROM's, which allow you to overclock the phone to 800-something MHz. I never use the overclock though and keeping it on 600MHz that comes out of the box still has the problem. With GB I'd overclock it to 729 for normal use, and on JB 748 for snappier performance with no bad things happening (well, besides battery life)
TheCrazyDirectioner said:
The stock kernels which come with the ROM's, which allow you to overclock the phone to 800-something MHz. I never use the overclock though and keeping it on 600MHz that comes out of the box still has the problem. With GB I'd overclock it to 729 for normal use, and on JB 748 for snappier performance with no bad things happening (well, besides battery life)
Click to expand...
Click to collapse
Do You Run Plenty Of apps at a time Because that cause Reboot..., The kernel candied(Ice) Give me problem like yours. if there is no solution switch to 4.1.2 AOKP it is stable.
Hello. I have the GS5. For over three months it overheats like hell. Why because I did the firmware update and it all started with this.
TL;DR: I need an app or program that shows detailed percentage of usage and temperatures of apps. It would be great if you can find a real-time monitoring one like on PCs. My phone is rooted so feel free to recommend any app that suit my needs.
It overheats so much that I can barely able to hold the phone because it slips through so easily from my hand (nope my hands are not dirty, I wash them with lots of soaps ).
I bought a case and it is still somewhat hard to hold the phone with one hand but the case surely helped. Can use it with two hands but was able to use with one hand without any problems so why should I accept this right?
The cpu is around 40 Celsius at idle to very low usage. The battery is around 28 Celsius at idle. The room temps is 26 Celsius.
After using my phone for about fifteen mins, the battery is going up to 36-38 Celsius. The cpu is around 50 Celsius. Not playing games at all, just surfing on the web and installing one to two apps from Android Market. Do you think it is normal or excessive? I fell the heat in my hands. It was not been like this before the firmware update.
Although I did all wipes and flash the whole rom from scratch (even ticked Nand Erase All), my problem still persists so I am out of ideas. Maybe I can buy a new battery and a charger but I would like to make sure that the problem is not causing by software. Thank you.
karasahin said:
Hello. I have the GS5. For over three months it overheats like hell. Why because I did the firmware update and it all started with this.
TL;DR: I need an app or program that shows detailed percentage of usage and temperatures of apps. It would be great if you can find a real-time monitoring one like on PCs. My phone is rooted so feel free to recommend any app that suit my needs.
It overheats so much that I can barely able to hold the phone because it slips through so easily from my hand (nope my hands are not dirty, I wash them with lots of soaps ).
I bought a case and it is still somewhat hard to hold the phone with one hand but the case surely helped. Can use it with two hands but was able to use with one hand without any problems so why should I accept this right?
The cpu is around 40 Celsius at idle to very low usage. The battery is around 28 Celsius at idle. The room temps is 26 Celsius.
After using my phone for about fifteen mins, the battery is going up to 36-38 Celsius. The cpu is around 50 Celsius. Not playing games at all, just surfing on the web and installing one to two apps from Android Market. Do you think it is normal or excessive? I fell the heat in my hands. It was not been like this before the firmware update.
Although I did all wipes and flash the whole rom from scratch (even ticked Nand Erase All), my problem still persists so I am out of ideas. Maybe I can buy a new battery and a charger but I would like to make sure that the problem is not causing by software. Thank you.
Click to expand...
Click to collapse
Please provide further information in regard to your device e.g. ROM, kernel etc.
noc.jfcbs said:
Please provide further information in regard to your device e.g. ROM, kernel etc.
Click to expand...
Click to collapse
Sure. I haven't touched to kernel yet but I have a custom rom installed. I just installed it yesterday. Was using stock rom of Lollipop 5.0 of my country before. I also tried the UK rom (BTU) but all the same.
karasahin said:
Sure. I haven't touched to kernel yet but I have a custom rom installed. I just installed it yesterday. Was using stock rom of Lollipop 5.0 of my country before. I also tried the UK rom (BTU) but all the same.
Click to expand...
Click to collapse
Despite only little information available, I assume the issue is kernel related. Had you e.g. overclocked and over-voltaged? Most likely not as you were on stock.
Your custom ROM certainly came with its own, new kernel. I suggest to monitor the overheating first as you just recently flashed the custom ROM. However, you can also play with the kernel settings (my current one has its own control-apk, or by using e.g. an apk called "Kernel Adiutor") to see what's best serves your requirements. If you're not happy with the custom ROM's kernel, you can flash a custom kernel but check compatibility first. And remember, when you're on a custom kernel every time you flash the custom ROM you'll have to re-flash the kernel.
Here's a real good guide regarding CPU governors, I/O schedulers and more:
http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
noc.jfcbs said:
Despite only little information available, I assume the issue is kernel related. Had you e.g. overclocked and over-voltaged? Most likely not as you were on stock.
Your custom ROM certainly came with its own, new kernel. I suggest to monitor the overheating first as you just recently flashed the custom ROM. However, you can also play with the kernel settings (my current one has its own control-apk, or by using e.g. an apk called "Kernel Adiutor") to see what's best serves your requirements. If you're not happy with the custom ROM's kernel, you can flash a custom kernel but check compatibility first. And remember, when you're on a custom kernel every time you flash the custom ROM you'll have to re-flash the kernel.
Here's a real good guide regarding CPU governors, I/O schedulers and more:
http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
Click to expand...
Click to collapse
So I think I should update kernel on this custom rom with a new one? Because the OP says that flash hispasian kernel after flashing his rom. I haven't do that yet, nor I have experience about it. I believe I have a custom rom with stock kernel right now. I don't think it is related to custom rom. It overheats like I was on stock rom. Could be kernel. Can kernel be updated through the firmware update? It may explain why it starts to overheating after that. No, I haven't overclocked and over-voltaged the cpu. Maybe it came overclocked or over-voltaged with this custom rom but it isn't described.
karasahin said:
So I think I should update kernel on this custom rom with a new one? Because the OP says that flash hispasian kernel after flashing his rom. I haven't do that yet, nor I have experience about it. I believe I have a custom rom with stock kernel right now. I don't think it is related to custom rom. It overheats like I was on stock rom. Could be kernel. Can kernel be updated through the firmware update? It may explain why it starts to overheating after that. No, I haven't overclocked and over-voltaged the cpu. Maybe it came overclocked or over-voltaged with this custom rom but it isn't described.
Click to expand...
Click to collapse
I suggest to surf your custom ROM's thread and to figure out, which kernels can go with this ROM and which are the experiences of other users with the respective kernel.
Firmware updates (I assume you mean now updates of your ROM) won't solve your problem because with the update comes its own kernel i.e. you need to flash afterwards the kernel you want again.
I always flash my custom kernel through recovery. As recovery, I personally recommend TWRP in its latest version (as you see in my signature block, I'm using TWRP v3.0.2). An in my opinion very good tool, to install (actually flash through your current recovery) TWRP is via an App (apk) called "Flashify".
After you've flash TWRP and rebooted, google how to flash a kernel or search XDA for my postings. I think I already describe somewhere how to do so.
noc.jfcbs said:
I suggest to surf your custom ROM's thread and to figure out, which kernels can go with this ROM and which are the experiences of other users with the respective kernel.
Firmware updates (I assume you mean now updates of your ROM) won't solve your problem because with the update comes its own kernel i.e. you need to flash afterwards the kernel you want again.
I always flash my custom kernel through recovery. As recovery, I personally recommend TWRP in its latest version (as you see in my signature block, I'm using TWRP v3.0.2). An in my opinion very good tool, to install (actually flash through your current recovery) TWRP is via an App (apk) called "Flashify".
After you've flash TWRP and rebooted, google how to flash a kernel or search XDA for my postings. I think I already describe somewhere how to do so.
Click to expand...
Click to collapse
I mentioned firmware updates because I was wondering if stock (Samsung) rom firmware update did break something in stock kernel. Is it possible? I'm %99 positive this happened after the latest firmware update. I mainly flashed this custom rom to get rid of overheating problem but the problem persists.
I just flashed HispAsian kernel, which the creator of this custom ROM recommended, through TWRP and works fine for now. But nothing's changed about overheating.
karasahin said:
I mentioned firmware updates because I was wondering if stock (Samsung) rom firmware update did break something in stock kernel. Is it possible? I'm %99 positive this happened after the latest firmware update. I mainly flashed this custom rom to get rid of overheating problem but the problem persists.
I just flashed HispAsian kernel, which the creator of this custom ROM recommended, through TWRP and works fine for now. But nothing's changed about overheating.
Click to expand...
Click to collapse
Look into the kernel settings as mentioned in post #4 (http://forum.xda-developers.com/showpost.php?p=67135599&postcount=4).
Before you change anything I suggest to educate yourself via the thread mentioned in that post, too.
noc.jfcbs said:
Look into the kernel settings as mentioned in post #4 (http://forum.xda-developers.com/showpost.php?p=67135599&postcount=4).
Before you change anything I suggest to educate yourself via the thread mentioned in that post, too.
Click to expand...
Click to collapse
I actually don't care about custom roms. As long as I can find a solution for stock roms I would return to them. Could you please give me your solution for stock roms?
karasahin said:
I actually don't care about custom roms. As long as I can find a solution for stock roms I would return to them. Could you please give me your solution for stock roms?
Click to expand...
Click to collapse
It's always your decision and desire. I think everything said also applies to stock ROM. Check your kernel settings and manipulate to your needs. Some tools were mentioned before.
noc.jfcbs said:
It's always your decision and desire. I think everything said also applies to stock ROM. Check your kernel settings and manipulate to your needs. Some tools were mentioned before.
Click to expand...
Click to collapse
It is too complicated for me. If you could just point how to downlock the CPU's clock speed then I can try and see if it works to prevent overheating.
Also let's say I decide to return to stock rom. Will current kernel replace with stock one?
karasahin said:
It is too complicated for me. If you could just point how to downlock the CPU's clock speed then I can try and see if it works to prevent overheating.
Also let's say I decide to return to stock rom. Will current kernel replace with stock one?
Click to expand...
Click to collapse
I'm not familiar with your phone (wasn't it a Samsung Galaxy S5) or your stock ROM (Lollipop?). I suggest that you address your questions in the GSG5 forum, where the gurus for your phone rest. Sorry for that.
Anyhow, I added two screenshots of the apk "Kernel Adiutor" (first two), and two of AGNi control, which came with my kernel. As you see both of them support manipulation of kernel settings.
IRT your last question: I'm convinced flashing stock ROM is also replacing current kernel. ...but as said: GSG5 forum.