Hi. Wich tools can be used to overclock a little the cpu, and/or gpu?
I've noticed some performance drop in 3d since sense 5, comparing with sense 4. Specially with WAZE app.
Thanks all.
You first need a custom kernel to OC. Then you can use apps like Trickster Mod, Kernel Tuner, and others to tune the kernel settings.
Sent from my Evita.
Can you give me some help to go with a custom kernel? Does they improve a lot over the default ones? I was looking at BEASTMODE rld 3.5...
There are only two available for Sense 5, Beastmode and Elemental. Asking for a suggestion isn't allowed so I can't do that. They're both pretty good though.
Sent from my Evita.
OC'ing HTC One X
Google and/or YouTube Beastmode. Plenty of info available.
FedericoUY said:
Can you give me some help to go with a custom kernel? Does they improve a lot over the default ones? I was looking at BEASTMODE rld 3.5...
Click to expand...
Click to collapse
If you are looking to overclock, then a custom kernel is a must, so in that way its an "improvement" (at least more features) than stock kernel. On a stock kernel, CPU frequencies over the "official" spec will not be available (not even appear) on overclocking tools/apps. Also, custom kernel will generally give more choice of governors, if you are into such things.
Ok, after I get a solution with the connectivity problem I'll try to switch kernel. But what about 3d performance loss with this now rom, particulary with sense 5 I guess? Is that normal?
I never noticed a performance loss with 3d on Sense 5, but you can OC both 2d and 3d with the Beastmode kernel.
Sent from my Evita.
Ok, the kernel installation is just from twrp like a rom choosing wich one to install right? Are there any noticeable gains with them? Whether it is beastmode or elemental x?
FedericoUY said:
Ok, the kernel installation is just from twrp like a rom choosing wich one to install right? Are there any noticeable gains with them? Whether it is beastmode or elemental x?
Click to expand...
Click to collapse
Yes, kernels are flashed in recovery. Beastmode is s-on friendly, but Elemental requires s-off according to the top post of that thread.
Whether you notice any gains will probably depend on how you use your phone and how you tweak, so I don't think there is any blanket response to that question. If you have given this much thought to it, just go ahead and flash. You can always dirty flash the ROM to go back to stock kernel, if you don't like the results. Or make a nandroid backup before you flash the kernel, which I recommend before flashing anything, anyway.
If I flash a kernel, whether elemental or beastmode, is there a way to return to orginal kernel only without flashing the entire rom?
You only need to dirty flash the ROM, that's flashing the ROM again without wiping anything except cache and dalvik. All of your settings, apps, and so on will remain, you'll actually not notice any changes at all. If for some reason you don't want to do that you can just flash the boot.img from the ROM zip to get the stock kernel back.
Sent from my Evita.
That's just what I needed to know. Thanks for the thousanth time timmaaaa. Cheers!
You're welcome, glad to help.
Sent from my Evita.
FedericoUY said:
If I flash a kernel, whether elemental or beastmode, is there a way to return to orginal kernel only without flashing the entire rom?
Click to expand...
Click to collapse
Dude, I already answer that question before you even asked it. Did you read my previous post?
Sent from my HTC One XL using xda app-developers app
redpoint73 said:
Dude, I already answer that question before you even asked it. Did you read my previous post?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I made a different question later, about just returning to previous kernel WITHOUT flashing the entire rom. I've read your post, and was helpful as well. Thank you.
Hi again. If I backup my current rom (system/data/boot) with the stock kernel, then I flash a moded kernel, and then I restore my backup (maybe because I'm not comfortable with the new flashed kernel for example), the kernel will be restored as it was on the moment of the backup right?
That's correct, but you don't necessarily need to restore the backup to get the stock kernel back. You can just flash the boot.img from the ROM zip, or dirty flash the ROM.
Sent from my Evita.
So flashing the boot.img will only flash the kernel.... Intresting. Thanks!
FedericoUY said:
I made a different question later, about just returning to previous kernel WITHOUT flashing the entire rom..
Click to expand...
Click to collapse
I don't think you understand what a "dirty flash" is. Flash without doing a factory reset (but wipe cache and Dalvik, which you shoud pretty much do with any significant system change). It retains all your settings, apps, etc. which are contained in the user data partition. It only touches the partitions where the ROM itself and kernel are located. It doesn't take any more time than flashing the stock boot.img.
---------- Post added at 10:17 AM ---------- Previous post was at 10:15 AM ----------
FedericoUY said:
So flashing the boot.img will only flash the kernel.... Intresting. Thanks!
Click to expand...
Click to collapse
Actually, there are other contents in boot.img besides just the kernel. But for practical purposes, nothing that significant.
Related
I just learned about the kernels for the XL and was interested in having the s2w feature. Can anyone advise the most stable build I can use with stable CM10 on the phone? I am new to kernel flashing and in a few threads, it appears the kernels are either CM10 nightly enabled (past the stable -- incompatible) or for Sense ROMs (also incompatible).
the kernels in the android development are sense only. since you want sleep2wake the only real option for you is rohan's kernel, its meant for aosp roms like cm10, and is the only kernel for jb roms that has s2w.
And for future references, if I am running on Rohan's kernel and flash a Sense ROM over it what would happen? Are you suppose to flash the kernel with a Sense kernel before going back to a Sense rom?
an_xda said:
And for future references, if I am running on Rohan's kernel and flash a Sense ROM over it what would happen? Are you suppose to flash the kernel with a Sense kernel before going back to a Sense rom?
Click to expand...
Click to collapse
Yes, non sense kernels will not work with sense roms. Reinstall stock or one of the other sense kernels when you switch roms.
Sent from my HTC One X using xda premium
Skeeterdrums said:
Yes, non sense kernels will not work with sense roms. Reinstall stock or one of the other sense kernels when you switch roms.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I should be more clear. If I had Rohan on my phone and went to a Sense ROM before flashing a Sense kernel, would I brick my device or would the kernel just 'not work/disable itself'?
an_xda said:
I should be more clear. If I had Rohan on my phone and went to a Sense ROM before flashing a Sense kernel, would I brick my device or would the kernel just 'not work/disable itself'?
Click to expand...
Click to collapse
You would just soft brick and the phone would be stuck in boot loop. Why would you even try?
Sent from my One X using xda premium
ChefAnt said:
You would just soft brick and the phone would be stuck in boot loop. Why would you even try?
Sent from my One X using xda premium
Click to expand...
Click to collapse
So if you are on CM10, how would you flash the Sense kernel and a Sense ROM? What would the order be?
an_xda said:
So if you are on CM10, how would you flash the Sense kernel and a Sense ROM? What would the order be?
Click to expand...
Click to collapse
First make a full wipe (factory reset, all that), then flash your rom using the typical procedures, then flash a sense kernel. Same goes for AOSP, make a full wipe if coming from another rom, flash the rom, then the kernel.
utkaar099 said:
First make a full wipe (factory reset, all that), then flash your rom using the typical procedures, then flash a sense kernel. Same goes for AOSP, make a full wipe if coming from another rom, flash the rom, then the kernel.
Click to expand...
Click to collapse
No this could be wrong. I am assuming OP is on 1.14 hboot. Older hboots allow you to flash kernels. With 1.14, kernels will not flash in recovery. Either use fastboot to flash kernels or use flash image GUI app found in the themes and apps section. After kernel is flashed then flash your ROM in recovery as normal.
Sent from my One X using xda premium
Thanks folks. Just what I needed to know for future references.
What the other guy said is true, but that was actually what I was hinting at when I said "typical procedure." I'll be more specific next time... Also, your very welcome!
Sent from my HTC One XL using xda app-developers app
ChefAnt said:
No this could be wrong. I am assuming OP is on 1.14 hboot. Older hboots allow you to flash kernels. With 1.14, kernels will not flash in recovery. Either use fastboot to flash kernels or use flash image GUI app found in the themes and apps section. After kernel is flashed then flash your ROM in recovery as normal.
Sent from my One X using xda premium
Click to expand...
Click to collapse
in this process, when should you do the full wipe? before or after flashing the new kernel using the fastboot method?
As title says, is there any way to lock the CPU frequency? Or do i have to flash a custom kernel? No matter i set the frequency to my desired max freq, the CPU just don't stick. I used several apps like setcpu, voltage control and kernel tuner with no luck.. i even turned on the power saving mode to lower the CPU clock, but still it bypasses it. The thing is, I still don't have the guts to try that since i'm still S-On and a total newbie when it comes to rooting, s-off, supercid, et al..
Btw, my phone is HTC One S with viperROM 2.2.0, but i'm still on stock kernel..
Sent from my Viper One S using xda premium
Stock kernel doesn't allow changes in clockspeed afaik. So I guess you would need a different kernel and also root to actually give apps the rights to change these values in the first place.
Sent from my HTC One S using xda app-developers app
Oxious119 said:
Stock kernel doesn't allow changes in clockspeed afaik. So I guess you would need a different kernel and also root to actually give apps the rights to change these values in the first place.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So i guess that was it. To install a custom kernel. I just don't want to mess up with the kernel stuff just yet since i'm still new at this. By any chance, do you know if i've installed a custom kernel, can i go back to the stock one if things go haywire? One more thing, i can't find in the dev section on how to revert to stock kernel and where can i download it..
Sent from my Viper One S using xda premium
The stock kernel is included in the respective RUUs. You can flash it just like all other kernels to revert to your stock kernel.
Edit: Once you are s-off with a custom recovery you can just create a mirror image of your whole system before trying a new kernel. So when things go wrong or you're just not satisfied you can use the image to recover your system.
There should be a couple of good tutorials and tools around the forums to explain everything in detail and help you with technical difficulties.
Sent from my HTC One S using xda app-developers app
Oxious119 said:
The stock kernel is included in the respective RUUs. You can flash it just like all other kernels to revert to your stock kernel.
Edit: Once you are s-off with a custom recovery you can just create a mirror image of your whole system before trying a new kernel. So when things go wrong or you're just not satisfied you can use the image to recover your system.
There should be a couple of good tutorials and tools around the forums to explain everything in detail and help you with technical difficulties.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
One last question, i just created a nandroid backup, if ever in the future that problems arise after flashing a custom kernel, and then i restore the nandroid i just made, would the custom kernel be replaced by the kernel included in the nandroid backup? Or kernels aren't included in the backup?
Sent from my Viper One S using xda premium
gelo01 said:
One last question, i just created a nandroid backup, if ever in the future that problems arise after flashing a custom kernel, and then i restore the nandroid i just made, would the custom kernel be replaced by the kernel included in the nandroid backup? Or kernels aren't included in the backup?
Sent from my Viper One S using xda premium
Click to expand...
Click to collapse
They are, not it won't flash unless you are s-off. You need to fastboot the kernel (boot.img).
http://www.youtube.com/watch?v=5xVl2dBTnmI&feature=youtube_gdata_player
hTConeS | SoFF | CharmAnDroiD | eleMeNtal
*INveRTeD sENsE 5 ROM+ThEmE+TwEAkS*
*CharmAnDroiD 3.0 FULL ROM UPDATE*
Hi, does anyone have a link to the bodivas repack kernel for the 6810? The link is missing from UTIA's second post in the thread for his kernel. I want to give his kernel a whirl. Thanks, Matt
Ignore this request. I flashed UITA's kernel but my hardware and his ROMs/kernels do not get along :'(
Reverting back to my backup...
Matt
mattbuffey said:
Ignore this request. I flashed UITA's kernel but my hardware and his ROMs/kernels do not get along :'(
Reverting back to my backup...
Matt
Click to expand...
Click to collapse
I'll upload it later today. Forgot all about it sorry.
Firstly, did you flash the SkyHigh kernel after first boot of any ROM? Don't flash directly after ROM flash. Otherwise boot loop. Only after ROM full boot.
Secondly, make sure that you have no tweaks or tweaking apps etc installed.
For the ROM, you need to follow the installation instructions EXACTLY, using correct recovery version and full wipe install.
Other than that, unfortunately, your hardware may not like some of the kernel tweaking or UV etc.
BTW, I'm working on a SkyHigh kernel update. Maybe try that in future "IF" I ever get to release stage.....
Sent from my GT-I9500 using XDA Premium 4 mobile app
It's weird, I had the same problem with your ROM on ICS. I was hoping JB would be different, but I got exactly the same stability problem. As you say, it must be something to do with the tweaks that upsets my tab. I can report that CIFS works fine with your kernel though!
I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex
alexm231 said:
I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex
Click to expand...
Click to collapse
1st option
Primokorn said:
1st option
Click to expand...
Click to collapse
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex
alexm231 said:
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex
Click to expand...
Click to collapse
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
Great. Thanks so much for the detailed answer, it clears up my confusion!
Now off to try Franco's kernel
Alex
Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
I actually have an additional question: do we need the same process even if we're talking about the newer version of the same kernel? Like going from an older version of Franco's to the newest
Alex
No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk
kufikugel said:
No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex
alexm231 said:
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex
Click to expand...
Click to collapse
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.
rootSU said:
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.
Click to expand...
Click to collapse
Yes, I consider your guideline (on your signature) very good advice indeed.
Thanks again to all
Alex
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
I know I had to do that when I flashed elemental. Otherwise some apps won't open. But now I want to find out was the the full correct way? Or was it the lazy way
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
Flash the stock boot.img and system.img and then flash the kernel you want to change to..
I have also tried just flashing the stock boot.img and then the custom kernel.. Sometimes it works, sometimes it doesn't. So I would reccomend flashing both! (boot and system)
also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.
simms22 said:
also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.
Click to expand...
Click to collapse
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.
akmsr said:
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.
Click to expand...
Click to collapse
yes. they arent located in either of those locations, so my advice applies, and is the only reason why i posted this. they are located in /etc/init.d/. you either dont have that location (best option), have it but an empty folder, or have an init.d folder with files in it. if there are files there, delete them.
Flashing a system.img will overwrite init.d scripts. /etc is a symbolic link to /system/etc so when you replace /system/etc with whatever is in a ROM.zip or a system.img, these changes apply to /etc too.
If you look in any ROM.zip or kernel.zip, they all flash their scripts to /system/etc/init.d
Sent from my Nexus 5 using Tapatalk
I have this question about kernel flashing, i tried google but no luck so xda is my last resort, anyway i want to flash a overclocked kernel of another rom, if i do so will it hard brick my device, as i cant try it not until i know that i can boot back into recovery even with incorrect kernel, i really hope someone can answer this. And oh yes i need to ask another question about camera not focusing correctly,i mean it focuses correctly then again becomes blur to take a shot, but when i do video calling in whatsapp, it works kinda ok that what my partner said but idk i have Grand 2 ms013g. Thnx
max gokue said:
I have this question about kernel flashing, i tried google but no luck so xda is my last resort, anyway i want to flash a overclocked kernel of another rom, if i do so will it hard brick my device, as i cant try it not until i know that i can boot back into recovery even with incorrect kernel, i really hope someone can answer this. And oh yes i need to ask another question about camera not focusing correctly,i mean it focuses correctly then again becomes blur to take a shot, but when i do video calling in whatsapp, it works kinda ok that what my partner said but idk i have Grand 2 ms013g. Thnx
Click to expand...
Click to collapse
It is impossible to answer that if we don't know what kernel you're trying to flash and what specific device model number you're trying to flash it on or what ROM you're using(i.e. custom ROM or Stock ROM, if custom ROM, what ROM?)
If the kernel was not made for your device, you can't use it. If it was made for your device, then it is a question of whether the kernel is compatible with the ROM you're using.
Sent from my SM-S767VL using Tapatalk
Ummm
This is the first time that someone replied to my post on xda i m lucky ig, and thnx a lot for the precious reply, so i have aokp 7.1.2 custom rom, and i think it has stock kernel, i want to flash deds kernel, infected kernel, and some others i need to check, which are compatible with my device but not this rom, it say touchwiz, 5.x, 6.x. and my device is Samsung Grand 2 G7102 with msm8226 i want to install overclock kernel as i m more into gamings even tho i still have some good gaming but not that good those kernel support overclocking upto 1.6ghz, if u need more info i m willing to give it to u.
Droidriven said:
It is impossible to answer that if we don't know what kernel you're trying to flash and what specific device model number you're trying to flash it on or what ROM you're using(i.e. custom ROM or Stock ROM, if custom ROM, what ROM?)
If the kernel was not made for your device, you can't use it. If it was made for your device, then it is a question of whether the kernel is compatible with the ROM you're using.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I mistakenly replied to this thread/post other than replying to ur comment, sorry i m newbie
max gokue said:
I mistakenly replied to this thread/post other than replying to ur comment, sorry i m newbie
Click to expand...
Click to collapse
TouchWIz stuff is stock only, you can't mix TouchWiz stuff with custom ROMs such as AOSP, AOKP, LOS, etc.
Touchwiz can use modified stock kernels that have overclock support built in but you can't use stock kernel or modified stock kernels with custom ROMs.
Likewise, you can't use stock with custom kernels either, stock can only use stock and modified stock kernel.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
TouchWIz stuff is stock only, you can't mix TouchWiz stuff with custom ROMs such as AOSP, AOKP, LOS, etc.
Touchwiz can use modified stock kernels that have overclock support built in but you can't use stock kernel or modified stock kernels with custom ROMs.
Likewise, you can't use stock with custom kernels either, stock can only use stock and modified stock kernel.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Ok so if i do flash one custom kernel what could happen if its not supported? Hard brick? Will i still be able to go to recovery?