Related
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, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip
xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565
Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!
I've got a rooted XT926 with unlocked bootloader. I've flashed plenty of custom ROMs on the phone including ones running 4.1, 4.2 and 4.3. I'm gradually moving back to earlier stock-based ROMs because, while the extra features are cool, I grew tired of random main functions that didn't work properly and my battery life was getting progressively worse.
Now I'd like to know for sure I'm running the stock kernel. How do I determine this? My kernel version is 3.0.31-g101ca72. The date of "Thu May 30 18:22:06 CDT 2013" also appears in this subheading of Settings/About Phone.
If I'm not running the stock kernel, where do I find it? I've done plenty of searching but can't seem to find a downloadable stock kernel that I could simply flash from TWRP recovery. Most of the posts of this nature are about unrooting and restoring stock. I don't want to do that. I want my phone to remain rooted but I'd like to know that I'm either on the stock kernel or can find it and flash it.
Not really sure how to check, but if you fastbooted back to stock you have the stock kernel. If you found a stock based ROM and flashed via recovery, unless stated otherwise in the post it should have the stock kernel. And have you tried arrrghhh's kernel? It works really well. It's for all msm8960 (or whatever msm we are) devices so it will work as long as you download the stock version.
Sent from my MB886 using Tapatalk
What would be the point of using arrrghhh's kernel with a stock rom? Or, what does his kernel do differently than the stock one?
At the moment I'm running RageHD 2.3, a straight-forward stock-based ROM running 4.1.2. It's doing pretty much what I want -- everything works, smooth and solid, better battery life than I was getting with 4.2.2 and 4.3 ROMs and improved signal strength. Still, I read from time to time that custom ROMs tend to give improved functionality and lessened bloat but that they also shorten battery life, sometimes substantially. To test this myself I need to know that either I'm on a stock kernel now or that I can find and flash a stock kernel.
So after doing 4 full wipes trying various rom/kernel combos that get me root and deodex, only to find out a day later when on a longer call that my Note5 still can't handle a phone call without a random reboot, I really want to avoid going through this tedious several hour process again unless I know there's going to be phone call stability.
Does anyone have any recommendations for something? I don't care if it's barely modified, I just want a stable TW based Deodexed rom that gives me root so I can restore from Titanium backup and uninstall bloat.
apols said:
So after doing 4 full wipes trying various rom/kernel combos that get me root and deodex, only to find out a day later when on a longer call that my Note5 still can't handle a phone call without a random reboot, I really want to avoid going through this tedious several hour process again unless I know there's going to be phone call stability.
Does anyone have any recommendations for something? I don't care if it's barely modified, I just want a stable TW based Deodexed rom that gives me root so I can restore from Titanium backup and uninstall bloat.
Click to expand...
Click to collapse
Which kernels have you tried? Arter 4.0? Stock modified? Skyhigh?
Brava27 said:
Which kernels have you tried? Arter 4.0? Stock modified? Skyhigh?
Click to expand...
Click to collapse
I've tried:
Noble V2 (wifi broken) w/stock rom
Noble V3 (call reboots) w/stock rom
Then Complete wipe of absolutely everything and adb sideloaded the below:
Stock Deodexed N920TUVU1BOH4 Rom (http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270), which I assumed use a stock kernel, but came to find out used the crappy Noble V3 and had call reboots
Then I also tried flashing the "Stock" kernel linked here with TWR: http://forum.xda-developers.com/tmo...ernel-stock-modified-kernel-touchwiz-t3194148 on top of the above Rom, but still have the phone reboots during calls.
All I want is a stockish, rooted deodexed rom. I don't care about custom fonts, themes, boot animations or any of the other crap people put in their roms to try and make them special.
I heard Arter (located international) is the "best" combination for a "stockish" kernel with no reboot, and should work with Jovy's "stockish" deodexed rom.
But you will have to remember...perfection is in the eyes of the beholder, phone hardware, and the phone data / system components.
For you I will recommend pure none rooted stock [I know that is not what you want] given you do not want to go through the process of doing wipes.
@apols
Currently I'm using @arter97 kernel v4.1 with @jovy23 deodexed rom and have not had any reboots. Before I installed this stuff, I updated to the BOH4 firmware (and baseband) using the directions in post 2 of jovy23 Rom thread.... then I twrp flashed the Rom and kernel noted above using post 1 of the jovy23 rom thread. Then I flashed the arter97 kernel.
Go to this link... to find info on both of them.
http://forum.xda-developers.com/showthread.php?p=62608884
dandroid7 said:
@apols
Currently I'm using @arter97 kernel v4.1 with @jovy23 deodexed rom and have not had any reboots. Before I installed this stuff, I updated to the BOH4 firmware (and baseband) using the directions in post 2 of jovy23 Rom thread.... then I twrp flashed the Rom and kernel noted above using post 1 of the jovy23 rom thread. Then I flashed the arter97 kernel.
Go to this link... to find info on both of them.
http://forum.xda-developers.com/showthread.php?p=62608884
Click to expand...
Click to collapse
I've just installed Thrashrom 2.1 + Arter97 + BOH4 baseband and have now made two 20+ minute calls in a row, which is about 18 minutes longer than any previous call would work. That combo might be a winner.
apols said:
I've just installed Thrashrom 2.1 + Arter97 + BOH4 baseband and have now made two 20+ minute calls in a row, which is about 18 minutes longer than any previous call would work. That combo might be a winner.
Click to expand...
Click to collapse
been using arter97's kernels since i rooted my phone (almost 2 weeks?) and all 3 releases have worked on my T-Mo N5 on at&t without issue.
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.