Some of the user's here, myself included, have been having issues installing any ROMs/ kernels built by Faux. What I'm trying to do is pinpoint the exact cause of this and hopefully rectify the issue.
I'm currently downloading all available ROMs and will install each to determine which are flashable and which are not.
Flashing Procedures
0. Boot into CMW Recovery: External with EXT 4 support using volume down + power method
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Format /System
5. Flash ROM
6. Select Power Down from CMW Menu
7. Power on phone without wall charger plugged in
ROM List:
Bionix- Confirmed as working
EagleBlood GB- Confirmed as working
EagleBlood FR- Confirmed as working
Ultimate- Confirmed as working
Light&Sinister- Confirmed as working
Dark&Sinister- Confirmed as working
Faux AOSP-NOW WORKING!!
CM7- Confirmed as working
LG Stock- Confirmed as working
Observations:
Bionix converts /system and /data to ext3. I figured that if the issue we were having with Faux was due to format errors then I could just flash Faux over Bionix and it would boot. In testing, it seems like Faux gets further when flashed this way but still refuses to boot. Before I would only get the initial LG screen and then it would black out. Now I can get to the second LG screen with blue background but it hangs there. Will run logcat to see what is causing the freeze once I get logcat running again.
My current theory is that there is a difference in the boot.img that Faux has built for his ROM that will not boot correctly. I have the same issue with his kernels as well. They boot to the first LG splash screen and then the screen shuts off. Still struggling with my logcat issue so I'm at a standstill until that is fixed.
Development:
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Morfic's CM7 kernel. I personally believe this definitely proves that there is something in Faux's boot.img that doesn't function properly on all devices.
At Faux's suggestion, I flashed his Stock Voltage kernels in order to see if I could get the phone to boot.
Kernel:
[ Start @ 1.0 GHz, Stock Voltage, Max @ 1.2 GHz ]
(Official LGE/Tegra Voltage Values, Same as STOCK LGE Kernel)
CM7 Kernel Version 0.1.9- Boots to second LG splash screen then freezes.
CM7 Kernel Version 0.1.9 With EXT4-Booted fine but still displayed Morfic boot animation for some reason. Kernel version shows as Faux's in about phone, though.
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Mikeglongo said:
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Click to expand...
Click to collapse
I didn't test any of the ROMs for quality but I would personally stick with a Froyo based ROM for now. Gingerbread is simply too buggy and missing a lot of features.
[B][U]SUCCESS!!![/U][/B]
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Trinity's CM7 kernel. I personally believe this definitely prooves that there is something in Faux's boot.img that doesn't function properly on all devices. That would explain why I am unable to flash any of his kernels, either.
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
faux123 said:
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
Click to expand...
Click to collapse
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
hiko36 said:
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
Click to expand...
Click to collapse
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
faux123 said:
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
Click to expand...
Click to collapse
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
hiko36 said:
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
Click to expand...
Click to collapse
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
faux123 said:
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
Click to expand...
Click to collapse
Glad I could help and especially glad I finally figured out a way to boot your ROM. I was feeling left out haha.
Doh! He said rectify lol
Sent from my Xoom using XDA Premium App
Related
Ive flashed the trinity kernel...and although it boasted high speeds.....My wifi would not work....... I then flashed the netarchy kernel and that seemed fine at first but after starting an intensive memory app it kept rebooting phone.....I seem to be having no luck with any kernels...can someone maybe suggest a kernel that just works with CM7 Rc2 and just gives me slightly better gains to make NS run a bit smoother......
Netarchy is fine. I'm using it with the latest nightly build #25. Never encountered reboots, its something else.
1. Wipe Cache & Dalvik-Cache
2. Fix Permissions
3. Flash Netarchy 1.3.0-CFS (CM7 Compatiable)
Should cause the best possible performance with the kernel.
zephiK said:
Netarchy is fine. I'm using it with the latest nightly build #25. Never encountered reboots, its something else.
1. Wipe Cache & Dalvik-Cache
2. Fix Permissions
3. Flash Netarchy 1.3.0-CFS (CM7 Compatiable)
Should cause the best possible performance with the kernel.
Click to expand...
Click to collapse
Ditto to this.
Try the CFS version (if you haven't) IIRC it *seems* to work slightly more reliably than the BFS version.
Also I assume you're not trying to OC the CPU - if you are, just leave at default if you're getting stability issues.
try ogdobbers kernel for cm7. I have version 1.3.1.5 and its smooth as butter. I have tried others but they seem unstable and I also am not a fan of overclocking my phone. Its a stock kernel with the ext4 hack that makes your phone run very fast and smooth without risks of overclocking. I haven't had a single problem with it and have been running it for about a month now.
mattdub1 said:
try ogdobbers kernel for cm7. I have version 1.3.1.5 and its smooth as butter. I have tried others but they seem unstable and I also am not a fan of overclocking my phone. Its a stock kernel with the ext4 hack that makes your phone run very fast and smooth without risks of overclocking. I haven't had a single problem with it and have been running it for about a month now.
Click to expand...
Click to collapse
All of netarchy's kernels are not OC'd by default. To OC it you have to manually do it. So what you said about kernels being OC'd is wrong. This thread has only mentioned Netarchy's kernel so I'm assuming that you thought Netarchy's kernel OC'd by default. It's automatically set at stock speeds. It includes ext4 hack as well.
Ogdoober's modified stock is just too plain for me.
What's this app that you're talking about? Was it a game?
I've only used Netarchy's so far and never had a problem. Make sure to at least try the CFS version. My phone doesn't like 1.4 ghz, but I've used it without any problems at 1.2 ghz. Right now I'm back to stock speed since I don't see any benefits to overclocking it for my usages.
zephiK said:
All of netarchy's kernels are not OC'd by default. To OC it you have to manually do it. So what you said about kernels being OC'd is wrong. This thread has only mentioned Netarchy's kernel so I'm assuming that you thought Netarchy's kernel OC'd by default. It's automatically set at stock speeds. It includes ext4 hack as well.
Ogdoober's modified stock is just too plain for me.
Click to expand...
Click to collapse
Correct. My builds enable the ability to over clock, but run at stock speeds by default. It's always your choice.
For what it's worth, I usually run at stock myself ;D
Thanks too all of you...much appreciated....coming over from the DHD and incredible S Forums was a bit daunting....but you guys are really helpful.....
After surfing the forums for a couple days and not finding a completely precise answer to my problem, and due to being limited by posts, I have to ask a question here. I have rooted my phone, installed a number of different roms, but the only issue I have run into is flashing faux123's kernel and the Trinity kernels. No matter what kernel I attempt to flash I receive the wonderful black screen. The touch buttons light up when the screen is pressed, but the rom does not seem to load in the background. I am doing something wrong when I flash the kernel, or is there another problem that I have not found?
I have flashed UV and normal voltage kernels, along with going to advanced under CWM and formatting each part of the phone.
EDIT: Resolved the issue. It appears the only rom that works with these kernels on my phone is the nightlies. Thanks everyone though.
Jakkumn said:
After surfing the forums for a couple days and not finding a completely precise answer to my problem, and due to being limited by posts, I have to ask a question here. I have rooted my phone, installed a number of different roms, but the only issue I have run into is flashing faux123's kernel and the Trinity kernels. No matter what kernel I attempt to flash I receive the wonderful black screen. The touch buttons light up when the screen is pressed, but the rom does not seem to load in the background. I am doing something wrong when I flash the kernel, or is there another problem that I have not found?
I have flashed UV and normal voltage kernels, along with going to advanced under CWM and formatting each part of the phone.
EDIT: Resolved the issue. It appears the only rom that works with these kernels on my phone is the nightlies. Thanks everyone though.
Click to expand...
Click to collapse
if i was me after reading what I've found online i think i would look for a more reputable dev when it comes to kernels.
Reputable? Faux and morfic are among the elite devs for our device. They don't get any more reputable than them.
-custom sig.
CM7 should work, whether nightlies or stable. Trinity requires ext 4 support, meaning CWM touch won't work. Previous version 5.0.2.0 (I believe) should be used to install trinity. Faux should have worked so not sure why it failed on other than nightlies.
All CM7 based ROM should work with these kernels.
-- The noob says:
Three in the morning I woke up... it was hot... the g2x had SODd!
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
stompysan said:
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
Click to expand...
Click to collapse
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
sidneyk said:
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
Click to expand...
Click to collapse
Just tried Antutu CPU Master. Same issues. It says that my max frequency is 1000MHz.
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Tekfrog said:
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Click to expand...
Click to collapse
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
stompysan said:
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
Click to expand...
Click to collapse
Which kernel are you running now?
Tekfrog said:
Which kernel are you running now?
Click to expand...
Click to collapse
Thanks for trying to help, but I have found my problem. My recovery was still borked from when I tried flashing the official one in Rom Manager. Wiped my recovery, installed the roach recovery, reflashed all of my files, and now I am good to go. I feel like a derp now. LOL
Same issue w/ OC...but wipe recovery?
Your issue sounds exactly like the one I am currently having.
I would like to try your fix...but I am not understanding how the "wipe recovery" process goes. Would you mind please explaining that in more detail? Im pretty sure it IS NOT as simple as just doing a complete cache/data wipe then flashing the recovery over itself is it?
I am:
ViperMOD Prime rooted
ClockworkRecoveryMOD installed (but I think I may have fubar'd it doing the same thing you did trying to recover stock recovery)
FROZN 1.0.9 rom w/ included Guevor kernel and NoFrills CPU app
...but none of the CPU apps will let me OC...wether I flash the kernel seperate from the ROM or use the one included w/ the ROM.
Hope you can help me.
UPDATE: apparently this inability to OC the kernel in any way is happening to those of us experiencing the CWM bootloop issue...so since the loader goes immediately to CWM it never runs the flashed kernel.
So in these forums is a thread to fix the CWM bootloop and if you follow the instructions carefully, you fix the bootloop and thus allowing the flashed kernels a chance to actually install. I chose the Roach method which you can install the code using Terminal Emulator pretty intuitively. I didnt choose the other method because I didnt want to mess w/ setting up an ADB terminal on my PC, which seemed MUCH more difficult.
So...now FINALLY
ViperMOD Prime rooted
ClockworkMOD Touch Recovery 5.8.8
FROZN 1.0.9 ROM (w/ built-in Guevor kernel @ 1.2 default) and am OCd @ 1.54 (np's at all so far, lightning fast, havent even tried 1.6 or 1.7).
Only issue so far is File Manager app crashes on startup...which isnt good because now the other file manager app I tried doesnt see my ext_SDcard...the stock File Manager did.
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
When you flash the kernel go to the about section in android and make sure the flash was actually successful.
fwbflash said:
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
Click to expand...
Click to collapse
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
WU55 said:
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
Click to expand...
Click to collapse
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
horndroid said:
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
Click to expand...
Click to collapse
Thanks, this was it, I didn't see it, because I was a noob and didn't look for it.
so I, for the first time, flashed that new kernel on the front page of this discussion which overclocks the cpu. I have the newest version of jellybean installed so I considered that a stock based rom and thought it would work. in power svae mode the screen would go all crazy, balanced mode it was aalright except it would crash after a while. peformance mode would crash even sooner. so I found a stock based kernel and flashed that. Everything is fine now except the previous kernel changed some settings on the screen rresolution or something with the gpu which increased screen size I guess cause now my custom Hubs GUI is all spaced out which I had previously and meticulously spaced before hand. it caused smaller screen titles and smaller widgets basically making things look out of proportion. is there a way to revert those settings? it seems since the stock kernel doesnt innately change gpu settings that it didnt revert the settings initially set by the first kernel. the kernel I flashed to fix it was a stock kernel slightly modified from cleanrom to do something dpi and some other unimportant thing so it isnt the completely stock kernel but it is stock based. does anyone think If I flash a true stock kernel it will get fixed? if so can I get a link to said kernel or will I have to extract it myself from a stock rom
spidasense said:
so I, for the first time, flashed that new kernel on the front page of this discussion which overclocks the cpu. I have the newest version of jellybean installed so I considered that a stock based rom and thought it would work. in power svae mode the screen would go all crazy, balanced mode it was aalright except it would crash after a while. peformance mode would crash even sooner. so I found a stock based kernel and flashed that. Everything is fine now except the previous kernel changed some settings on the screen rresolution or something with the gpu which increased screen size I guess cause now my custom Hubs GUI is all spaced out which I had previously and meticulously spaced before hand. it caused smaller screen titles and smaller widgets basically making things look out of proportion. is there a way to revert those settings? it seems since the stock kernel doesnt innately change gpu settings that it didnt revert the settings initially set by the first kernel. the kernel I flashed to fix it was a stock kernel slightly modified from cleanrom to do something dpi and some other unimportant thing so it isnt the completely stock kernel but it is stock based. does anyone think If I flash a true stock kernel it will get fixed? if so can I get a link to said kernel or will I have to extract it myself from a stock rom
Click to expand...
Click to collapse
You can't use custom OC kernel with stock rom. You need to flash custom rom like Cleanrom and you can flash what ever kernel you want that designed for CleanRom.
buhohitr said:
You can't use custom OC kernel with stock rom. You need to flash custom rom like Cleanrom and you can flash what ever kernel you want that designed for CleanRom.
Click to expand...
Click to collapse
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
p.s. can I flash roms on my tablet without losing app data or settings or my hub UI settings? im on 4.1.1
spidasense said:
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
p.s. can I flash roms on my tablet without losing app data or settings or my hub UI settings? im on 4.1.1
Click to expand...
Click to collapse
You should able to flash cleanrom without losing any data, during the install there're options for many kernels, I suggest try the "_that stock kernel" first
spidasense said:
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
Click to expand...
Click to collapse
Anyone else with an unlocked bootloader uses a custom ROM that sets the display dpi. This has nothing to do with the GPU, it's just a setting that tells Android the display resolution so that it can scale UI elements accordingly.
To get your 240 dpi back, either install CleanROM Inheritance, or the first kernel in this thread:
http://forum.xda-developers.com/showthread.php?t=2106689
that is actually the kernel Iflashed to ttry and fix the dpi. thanks for informing me on that, I had a hunch dpi had something t odo with the problem I was having. I only tried one of them I guess theother one (ill have to check my sd card to find out which one ) will fix it.
and to be clear, I can flash clear rom inheritince and not lose app data or settings?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
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.