• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Custom kernel

There is EthanBanker2428's synthetic kernel with CPU and GPU over clock but it actually slows the phone down instead of speeding it up. Your best bet is to stick with the kernel that comes with the rom
 
Masterchief87 said:
There is EthanBanker2428's synthetic kernel with CPU and GPU over clock but it actually slows the phone down instead of speeding it up. Your best bet is to stick with the kernel that comes with the rom
Click to expand...

I tried BrokenOS for a bit. I needed to get to a Cyanogenmod based ROM. I guess I am spoiled by CM.
 
I like the pure Google experience. That is why I use Google Now Launcher. No bugginess yet, pretty smooth so far.
 
Are their any custom roms that have the build in proximity stuff as well as the build in thing so when you receive a call the screen doesn't go black and yes I was finally able to root zte zmax build 13
 
Masterchief87 said:
There is EthanBanker2428's synthetic kernel with CPU and GPU over clock but it actually slows the phone down instead of speeding it up. Your best bet is to stick with the kernel that comes with the rom
Click to expand...
You've told me this a few times. It was hard for me to believe, so I've been testing and timing operations, like compressing/decompressing files, loading large games, encoding media, running benchmarks, etc.
I don't agree that the Synthetic Kernel slows the phone down, but it doesn't speed it up either. At least not the CPU. I'm not sure how to test the GPU, but I've seen enough. I don't understand why, though. It doesn't make sense to me. What a let down.
 
Last edited:
arkansawdave74 said:
You've told me this a few times. It was hard for me to believe, so I've been testing and timing operations, like compressing/decompressing files, loading large games, encoding media, running benchmarks, etc.
I don't agree that the Synthetic Kernel slows the phone down, but it doesn't speed it up up either. At least not the CPU. I'm not sure how to test the GPU, but I've seen enough. I don't understand why, though. It doesn't make sense to me. What a let down.
Click to expand...
Were you testing these things while the phone was on the charger or off? I noticed the most lag when the phone was charging. Also, the smoothest ROM/kernel combination I know of is BrokenOS with the kernel it comes with. Unfortunately the kernel for BrokenOS is so optimized just for BrokenOS that it won't work with other ROMs. After switching from BrokenOS to synthetic for about half a day, I noticed just how much smoother and faster BrokenOS really is. This is because of it being a "one off" so to speak, It has been actively maintained and improved upon with each release.
 
Masterchief87 said:
Were you testing these things while the phone was on the charger or off? I noticed the most lag when the phone was charging. Also, the smoothest ROM/kernel combination I know of is BrokenOS with the kernel it comes with. Unfortunately the kernel for BrokenOS is so optimized just for BrokenOS that it won't work with other ROMs. After switching from BrokenOS to synthetic for about half a day, I noticed just how much smoother and faster BrokenOS really is. This is because of it being a "one off" so to speak, It has been actively maintained and improved upon with each release.
Click to expand...
not to mention the kernel has been optimize for the cortex a7 chip.
 
I hate to say this, but I just now left broken. Was soft rebooting every time I got a call and if they didn't leave a message, I would't even know I had a call. It did this before. I removed all my tweaks and it didn't help. I clean reflashed and it was fine. Reinstalled my tweaks and it was fine, too. Lasted about 2 weeks, and started again this morning. Since it was a soft reboot, I was able to see the crash in a log, but unfortunately I didn't pull the log. Even if I did, I couldn't have reported it because of Xposed. Back on RR, which I love its stability, but I'm like blah without all my dark Layers overlays. I guess RR is tough enough to theme with Xposed, but I want to use less Xposed, not more. I may install a Broken backup from before I Xposed it, see if I can replicate the crash and pull the log, but it was the 3.9 release ending in 007, not the latest because I removed my ext4 partition when they got Obb On SD working on Lollipop. I have to make a decision now, and its not an easy one. Xposed or Broken, where will I stand. By chance, have you heard of the soft reboot problem when receiving calls from anyone else, @Masterchief87 ? It was doing the same without Xposed, so maybe I'm not the only one. But, like I said, it's the 007 release.
 
arkansawdave74 said:
I hate to say this, but I just now left broken. Was soft rebooting every time I got a call and if they didn't leave a message, I would't even know I had a call. It did this before. I removed all my tweaks and it didn't help. I clean reflashed and it was fine. Reinstalled my tweaks and it was fine, too. Lasted about 2 weeks, and started again this morning. Since it was a soft reboot, I was able to see the crash in a log, but unfortunately I didn't pull the log. Even if I did, I couldn't have reported it because of Xposed. Back on RR, which I love its stability, but I'm like without all my dark Layers overlays. I guess RR is tough enough to theme with Xposed, but I want to use less Xposed, not more. I may install a Broken backup from before I Xposed it, see if I can replicate the crash and pull the log, but it was the 3.9 release ending in 007, not the latest because I removed my ext4 partition when they got Obb On SD working on Lollipop. I have to make a decision now, and its not an easy one. Xposed or Broken, where will I stand. By chance, have you heard of the soft reboot problem when receiving calls from anyone else, @Masterchief87 ? It was doing the same without Xposed, so maybe I'm not the only one. But, like I said, it's the 007 release.
Click to expand...
100% user error and expose!
 
Masterchief87 said:
Were you testing these things while the phone was on the charger or off? I noticed the most lag when the phone was charging. Also, the smoothest ROM/kernel combination I know of is BrokenOS with the kernel it comes with. Unfortunately the kernel for BrokenOS is so optimized just for BrokenOS that it won't work with other ROMs. After switching from BrokenOS to synthetic for about half a day, I noticed just how much smoother and faster BrokenOS really is. This is because of it being a "one off" so to speak, It has been actively maintained and improved upon with each release.
Click to expand...
I was unplugged BTW. Power's been out all day here....storming.
 
0k, but I'm already convinced Synthetic Kernel doesn't improve performance. Now I'm wondering if the overclocked Freedom Kernel really improved performance on my old F6. That was the only other time I've used an overclocked kernel. But, WTH? This may be a bad analogy, but if one automatic weapon fired with a higher frequency than another, it wouldn't make sense if, after one minute of firing, they had both fired the same number of rounds. I've read a few articles about overclocked kernels today, but haven't found an explanation yet. This is something I want to understand. My best guess is that the Snapdragon 400 is optimized for frequencies lower than 1.6 GHz. I can say that, and it may sound good, but I really don't understand, yet. How the heck can it cycle faster, yet not get more done in a given time frame? Grrrrr....
 
Last edited:
arkansawdave74 said:
0k, but I'm already convinced Synthetic Kernel doesn't improve performance. Now I'm wondering if the overclocked Freedom Kernel really improved performance on my old F6. That was the only other time I've used an overclocked kernel. But, WTH? This may be a bad analogy, but if one automatic weapon fired with a higher frequency than another, it wouldn't make sense if, after one minute of firing, they had both fired the same number of rounds. I've read a few articles about overclocked kernels today, but haven't found an explanation yet. This is something I want to understand. My best guess is that the Snapdragon 400 is optimized for frequencies lower than 1.6 GHz. I can say that, and it may sound good, but I really don't understand, yet. How the heck can it cycle faster, yet not get more done in a given time frame? Grrrrr....
Click to expand...
The overclocked kernels for the lg f6 really did increase performance. Everything was snappier, I was able to compress and extract archives faster, benchmark scores went through the roof. Sometimes there are variables that don't show up on the spec sheet for a device. Think of this analogy. You have a water pump that shoots out 1200 gallons per minute and you modify it so that it can pump 1600gpm. That's all well and good but if the hose or pipe it is hooked up to can't transport the water being pumped at speeds higher than 1200gpm then you are just wasting energy with your modified pump. Or if we go back to your automatic weapon analogy, keep in mind that with the same weapon, as rate of fire increases, accuracy also decreases. Is it beginning to make sense?
 
It sure is. There are other factors involved in performance than just the kernel and processor. Thank you, @Masterchief87. I hadn't considered that and probably wouldn't have found that in the type of articles I was searching. You've just saved my evening! Now I can get back to learning the more relevant Android things I should be learning... Lol....
 
Last edited:
For anyone who read my earlier posts in this thread, after testing Synthetic Kernel against the kernel in RC5 with a stopwatch in as close to identical conditions as I could, both plugged and unplugged, I'm sticking with Synthetic Kernel on CM based ROMs. It was around 10% faster on my device. Tested on Resurrection Remix. My first tests were done on Broken, and the dfuse kernel matched Synthetic Kernel on that ROM.
 
Last edited:
arkansawdave74 said:
For anyone who read my earlier posts in this thread, after testing Synthetic Kernel against the kernel in RC5 with a stopwatch in as close to identical conditions as I could, both plugged and unplugged, I'm sticking with Synthetic Kernel on CM based ROMs. It was around 10% faster on my device. Tested on Resurrection Remix. My first tests were done on Broken, and the dfuse kernel matched Synthetic Kernel on that ROM.
Click to expand...
And the best one is this one only I have [emoji23]
b543113eacf181cdcb7ec765589d29f3.jpg
 
dfuse06 said:
And the best one is this one only I have [emoji23]
b543113eacf181cdcb7ec765589d29f3.jpg
Click to expand...
I just tested the October 13th broken-fusebox 3.4.1 kernel against the Synthetic Kernel on the latest Broken 3.9 and it wasn't even close. Hell of a kernel you made there @dfuse06! I do realize that the Synthetic Kernel probably works better with a CM based ROM, but that's a tale for another day.
 
Oh yeah... I forgot to post my final results, not that anyone cares. But, I took the time to test it so I might as well post it.. Can't find my math, though.
Synthetic Kernel did perform a hell of a lot better in RR than it did in Broken, but still about 5% or so slower than Broken with its own kernel. All tests I did were done with the default settings and governors just like they are after a fresh flash. And anyone who's tired of reading my kernel test results will be happy to know, I tired of timing shit too, lol. I'll have no more reports unless anyone cares to toss me a new kernel or two... The End!​
 
You must log in or register to reply here.
Back
Top Bottom