I was wondering something, why there's no custom kernels for this device? (Not counting the ones made to fix the f2fs thing)
I mean, I came from Nexus devices and I remeber XDA being full of super custom kernels that would make my device four times faster, coulder, and battery friendly with CPU and GPU overclocks, optimized toolchains and a lot of buzzwords (I hope you see the irony here).
But really, just by curiosity, today there's no more interest in this kind of thing?
Maybe because stock is already very good but most probably because no developer interested to make it.
Sent from my XT1635-02 using Tapatalk
Related
Hey,
So sorry for what probably seems like a dumb question. I'm usually a Vibrant guy, but I'm helping a buddy out with a G2/looking at the feasibility of getting one myself. I know at least for the Vibrant our normal kernels don't play nice with our version of CyanogenMod 7. I was curious if the same held true here? Or can I flash any kernel? Also, I see that there are different types based on the type of ROM, which is a new thing to a Vibrant owner. So can anyone recommend me a kernel? I'm pretty decent on flashing and all that, and recovering a brick (at least with my Vibrant). Basically I want the best bottom-line performance. I don't need extra bells and whistles, just a nice high clock frequency. Thanks!
-MN_Vibrant
MN_Vibrant said:
Hey,
So sorry for what probably seems like a dumb question. I'm usually a Vibrant guy, but I'm helping a buddy out with a G2/looking at the feasibility of getting one myself. I know at least for the Vibrant our normal kernels don't play nice with our version of CyanogenMod 7. I was curious if the same held true here? Or can I flash any kernel? Also, I see that there are different types based on the type of ROM, which is a new thing to a Vibrant owner. So can anyone recommend me a kernel? I'm pretty decent on flashing and all that, and recovering a brick (at least with my Vibrant). Basically I want the best bottom-line performance. I don't need extra bells and whistles, just a nice high clock frequency. Thanks!
-MN_Vibrant
Click to expand...
Click to collapse
If you're looking for a kernel for CM7, the kernel included is quite snappy though I personally run pershoot's kernel as he undervolts and has some other tweaks which improves responsiveness *and* battery life, at least for me.
Sent from my HTC Vision using XDA App
CM7 already comes with its own custom kernel (which also supports some overclocking), so no need to flash a separate kernel if you don't want to. But as already mentioned, pershoot's works well too.
You can't flash any kernel. Some are Sense specific, and some are for non-Sense ROMs. Flashing the wrong one for your ROM can apparently brick the phone, so read thru the threads for the ROM and kernel you are interested in, to be sure. The ROM developer will usually have kernel recommendations, or you can see what kernels users of that ROM have tried.
Like stated above you will need to read the instructions and notes on the kernel thread. CM7 has special requirements. Other Roms don't need. but be very careful on what you flash!
Merry Christmas everyone! I hope everyone received all the tech goodies we wanted for Xmas!
I've noticed that most of the ROM's available in the development section already have an Overclocked Kernel and also UV options. I personally would rather use a stock kernel, or a custom kernel that is not overclocked. Right now I don't see that available from what I've searched for.
There are a couple ROMs I'm interested in running, but both install a new OC kernel. Is it possible to strip the kernel from the ROM before installing? And if so, does anyone know a tutorial for doing so, or is it as simple as opening the archive file, stripping the kernel out, and rezipping the file?
I know there are apps like SetCPU to change the clock speed on an OC ROM, but I really don't want to depend on software to keep the OC from occuring. I hope I was clear enough in my post to get the point across lol! Thanks for any assistance gents (and ladies).
Franco's kernels don't have OC
Sent from my Galaxy Nexus using xda premium
Thanks Josh! Appreciate your input. I am still interested in the other option as well, stripping the kernel from the ROM.
I am not sure how to repackage the from after you do that, but if you extract the rom the kernel is called "boot.img" and you can flash it in fastboot so you can basically flash any kernel you want on any rom
Sent from my Galaxy Nexus using xda premium
Just curious why you wouldn't want an OC/UV kernel, you're getting better performance and better battery life, no downside imo.
ikon8 said:
Just curious why you wouldn't want an OC/UV kernel, you're getting better performance and better battery life, no downside imo.
Click to expand...
Click to collapse
I honestly just don't like to OC my CPU's. In the long run it will decrease the life of the CPU.
Besides, if you have a great AOSP ROM to run, there really is no need to OC at all. Any performance boost from the OC comes at the cost of shortening the life of the CPU.
Sent from my Galaxy Nexus using Tapatalk
I've run Intel chips at 40% OC for a decade at a time, with little impact.
I don't expect my Nexus, with or without <20% OC, to last me nearly that long.
Just sayin'....
-bZj
Are there any advantages/disadvantages for using a stock kernel vs a custom kernel? Thanks for the responses.
Sent from my Modded Classic Evo... It's easier this way.
Stock kernel usually does'nt clock over 998MHz and you are'nt able to over or undervolt the kernel for better battery life.Also on custom kernels there are more governor options(smartass,etc.).Custom kernels can go up to 1118MHz sometimes higher,depends on the CPU.
Diablo67 said:
Stock kernel usually does'nt clock over 998MHz and you are'nt able to over or undervolt the kernel for better battery life.Also on custom kernels there are more governor options(smartass,etc.).Custom kernels can go up to 1118MHz sometimes higher,depends on the CPU.
Click to expand...
Click to collapse
I am aware of those differences. Basically, I'm wondering why I see so many people wanting to use a stock kernel (especially the one in the new OTA) and I was wondering why. Like what are the advantages of using the stock kernel over a custom kernel? Is it more stable? Are there any other things I may not be thinking of that would make a stock kernel a better choice? Thx again!
Sent from my Modded Classic Evo... It's easier this way.
I would think stock kernels to be smoother because they are designed for that particular rom/build,when a custom kernel is designed to run on different roms/builds,then when roms are updated or changed,the custom kernel does'nt,unless changed by the developer,hence the lag and FC's.I hope thats the answer you were looking for.
Custom kernels are made universal for several devices and roms. Although they yield benefits over stock, sometimes they can be unstable on certain setups. like mentioned above stock is made specifically for said device bout somewhat limited, though very stable
Sent from my OG Evo 4G via XDA app. Did I mention from inside my pocket?
Diablo67 said:
I would think stock kernels to be smoother because they are designed for that particular rom/build,when a custom kernel is designed to run on different roms/builds,then when roms are updated or changed,the custom kernel does'nt,unless changed by the developer,hence the lag and FC's.I hope thats the answer you were looking for.
Click to expand...
Click to collapse
Naturesretard said:
Custom kernels are made universal for several devices and roms. Although they yield benefits over stock, sometimes they can be unstable on certain setups. like mentioned above stock is made specifically for said device bout somewhat limited, though very stable
Sent from my OG Evo 4G via XDA app. Did I mention from inside my pocket?
Click to expand...
Click to collapse
Thanks clicked for both of you. Reason I ask is because I am running the new radios that were released with the newest OTA and wanted to know what to look for when I finally give the new kernel a try. Has anyone used the new kernel HTC released with the OTA yet? Has anyone a comparison they could share? Thanks.
Sent from my Modded MikG Evo... It's easier this way.
Thanks for the info.
Hello fellow XDA brethren!
I am reaching out to whomever may be able to give me an "advanced" type of explanation in regards to
modified kernels being applied to my phone.
T-Mobile Galaxy SIII (32Gb White)
I seem to be having issues with many of the kernels offered by some of the excellent developers in the t999 forum.
Namely, ktoonsez, and the other famous dev who's name escapes me right now.
When I flash kernels like those above, my main symptoms are:
Artifacting / Glitchyness in GUI.
Now... I know that some kernels are geared towards battery life and are undervolted to a point, I've tried everything,
volting back up. I've been flashing every one of them properly as well. I know that people say "all phones aren't created
equal", but i refuse to believe that mine is so whack that I cant even use anything other than stock kernels.
I firmly believe that these symptoms are from GPU overclocks that my phone simply cannot handle, (explains artifacts?).
I can use different roms with their respective kernels such as CM10, and a few of the other popular TW roms that are offered.
Here's what I was wondering:
Is there any application that I can use to control GPU overclock (to see if tweaking with this fixes it, to narrow it down
that my phones GPU is just very sensitive)
Are there any kernels out there for touchwiz that give me some nice benefits that dont have any GPU overclock?
What other methods can I fool around with to see exactly what part of my phone is weak?
Any suggestions are appreciated!
I get LOUSY batterylife / performance on tmo stock kernel.
If it were a PC, the first thing I would suspect of causing the artifacting issue is bad video memory. Combine that with the poor performance on stock, it stands to reason that you may have gotten a bad phone from the factory. I would suggest that you consider simply having it replaced under warranty, if you do have bad RAM in the phone the problems will only get worse.
So far i've tried both faux and flar2's elementalx kernels on CM10.2 nightlies, and they both produce the same result. lag and screen tearing after playing a GPU intensive game such as Asphalt 7 and 8. I've mentioned this before, but apparently nobody else has had the issue. I'm starting to think my Nexus 7 is again having issues. If so it's going back for good.
It does not behave this way on the stock CM 10.2 kernel, so I'm not yet 100% sure it is a hardware issue. All settings are on stock with no overclocking as part of my test to see if I can figure out why.
You can see what it does in the video posted below: It was taken after playing Asphalt 7 for around 20 minutes.
https://dl.dropboxusercontent.com/u/17013328/N7screentearing.mp4
Can someone confirm this as a problem on their nexus 7 with custom kernels as well?
bump, i wanna know if there is a kernel that has vsync enabled... and how to enable it if it is off
You need to add voltage. Most kernels come undervolted. Some handle it better than others. Raise your CPU or possibly GPU voltage slightly and see if it gets better. Small increments. If you need to add too much voltage then it is something else. That is the first thing I'd try, especially since its on multiple kernels.
Sent from my AOSP on Flo using Tapatalk 4
CM drops frames playing something basic like super hexagon, for me. I haven't tried custom kernels yet but the stock CM one is crap. CM in general has just gone off the rails recently, stupid jss/jwr confusion and **** performance on nexus devices.
darkrom said:
You need to add voltage. Most kernels come undervolted. Some handle it better than others. Raise your CPU or possibly GPU voltage slightly and see if it gets better. Small increments. If you need to add too much voltage then it is something else. That is the first thing I'd try, especially since its on multiple kernels.
Sent from my AOSP on Flo using Tapatalk 4
Click to expand...
Click to collapse
Over-volting! it worked! i just added one step to all the clock speeds, no more screen tear!
but i want to know why it happens on the default voltages, i mean technically, why the tearing appears on low voltages?
EDIT: nope... screen tearing is still there... i added 2 steps to all of the clockspeeds, it's not solving the issue.
Sent from my Nexus 4
freeza said:
So far i've tried both faux and flar2's elementalx kernels on CM10.2 nightlies, and they both produce the same result. lag and screen tearing after playing a GPU intensive game such as Asphalt 7 and 8. I've mentioned this before, but apparently nobody else has had the issue. I'm starting to think my Nexus 7 is again having issues. If so it's going back for good.
It does not behave this way on the stock CM 10.2 kernel, so I'm not yet 100% sure it is a hardware issue. All settings are on stock with no overclocking as part of my test to see if I can figure out why.
You can see what it does in the video posted below: It was taken after playing Asphalt 7 for around 20 minutes.
https://dl.dropboxusercontent.com/u/17013328/N7screentearing.mp4
Can someone confirm this as a problem on their nexus 7 with custom kernels as well?
Click to expand...
Click to collapse
I have not used CM in a while but doesn't it still use a CAF based kernel? If so I know Flar will not make a kernel that is CAF based he only supports AOSP. Most likely that is why you have tearing. You need a kernel that specifically states it works with CM.
Sent from my SM-P600 using XDA Premium HD app
nrage23 said:
I have not used CM in a while but doesn't it still use a CAF based kernel? If so I know Flar will not make a kernel that is CAF based he only supports AOSP. Most likely that is why you have tearing. You need a kernel that specifically states it works with CM.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
Honestly CM doesn't play nice with anyone/anything any more. They do their own thing and want to be separate and "special" so nothing works well if you try to change anything. Their stock kernel sucks, and their compatibility with other kernels is slim to none. Best bet is finding a rom that is less restrictive.
just to be clear here, i'm on stock 4.3.
i was on stock kernel when the tearing happened, i moved to a custom one with vsync... same issue. overvolted, same... i also changed governors too, but the tearing is always there.
a temporary solution is to lower the graphics, but the nexus 4 supports the highest graphics, so i want to fix this on high
nrage23 said:
I have not used CM in a while but doesn't it still use a CAF based kernel? If so I know Flar will not make a kernel that is CAF based he only supports AOSP. Most likely that is why you have tearing. You need a kernel that specifically states it works with CM.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
You nailed it. I figured that out a while ago but thanks for replying
just switched to stock JWR, and the screen tear disappeared!