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

Root [Virgin Mobile] [MK5][4.3][WIP] Working Custom Kernels (Sprint, TW, etc)

I took it off the charger around 8 am today, i have done some facebooking, snapchatting, a few texts, 35ish min phone call and some internet browsing and I have 70% battery left so i would say it's much better but i haven't done any stressful tasks yet to see any benefits/ or lack thereof in that aspect. I have the governor set to conservative unless i plan on any gaming. the min is set to 216 mhz and i haven't messed with any voltages yet, i am a little nervous on messing with those lol

oh and im using the kernel designed for the bootloader without knox.
And would it be a good idea to under volt? I noticed you talked about going -75, should i give that a try?
 
Warrior94 said:
I took it off the charger around 8 am today, i have done some facebooking, snapchatting, a few texts, 35ish min phone call and some internet browsing and I have 70% battery left so i would say it's much better but i haven't done any stressful tasks yet to see any benefits/ or lack thereof in that aspect. I have the governor set to conservative unless i plan on any gaming. the min is set to 216 mhz and i haven't messed with any voltages yet, i am a little nervous on messing with those lol

oh and im using the kernel designed for the bootloader without knox.
And would it be a good idea to under volt? I noticed you talked about going -75, should i give that a try?
Click to expand...

Undervolting is going to be key in helping extend battery life. Give it a shot in increments of 25. Also, decimalman has another zip in the op of his thread called dkpvmin (if I recall correctly on the name, I'm at work on Tapatalk), that will restore original voltage values if you decrease too far and phone doesn't have enough juice to reboot, you flash that from recovery. Put it on your SD card for a safety valve.
 
For anyone who doesn't follow the thread on XDA for the dkp kernel, he has created a minor bug in the latest TW 4.3 kernel that sets the minimum frequency to 1512, just like the max frequency, so your phone won't scale down if that happens but instead always run at max frequency. Very easy to change, but not if you don't know it's there in the first place! That would probably be some horrible battery life. It may or may not even show up, but he did put out the warning. Additionally, new test build for 4.4.x is up, running it for the last couple of hours myself with no issues, unlike the first 4.4.x test build which was rather buggy.
 
struckn said:
For anyone who doesn't follow the thread on XDA for the dkp kernel, he has created a minor bug in the latest TW 4.3 kernel that sets the minimum frequency to 1512, just like the max frequency, so your phone won't scale down if that happens but instead always run at max frequency. Very easy to change, but not if you don't know it's there in the first place! That would probably be some horrible battery life. It may or may not even show up, but he did put out the warning. Additionally, new test build for 4.4.x is up, running it for the last couple of hours myself with no issues, unlike the first 4.4.x test build which was rather buggy.
Click to expand...

Is there much difference between the kernels for 4.3 and the kernels for 4.4?

Edit: That is, if you're using them on TW 4.3 aka MK5?
 
TheBritton said:
Is there much difference between the kernels for 4.3 and the kernels for 4.4?

Edit: That is, if you're using them on TW 4.3 aka MK5?
Click to expand...

There are kernel builds specific to Android build number as well as to TouchWiz specifically. Flashing a 4.4 AOSP kernel on a 4.3 TW build won't even boot I would assume but just hang on the splash screen. I think there is nothing preventing the flash in recovery however, not in the way that GApps packages check for compatibility. Just like GApps, though, you do need to choose compatible builds. My understanding is that decimalman will release a very solid final build of each version once several test builds have gone up, and I know he is really close on 4.3 TW. Latest 4.4 AOSP is only the second test build, as he has been focusing on TW first.
 
struckn said:
There are kernel builds specific to Android build number as well as to TouchWiz specifically. Flashing a 4.4 AOSP kernel on a 4.3 TW build won't even boot I would assume but just hang on the splash screen. I think there is nothing preventing the flash in recovery however, not in the way that GApps packages check for compatibility. Just like GApps, though, you do need to choose compatible builds. My understanding is that decimalman will release a very solid final build of each version once several test builds have gone up, and I know he is really close on 4.3 TW. Latest 4.4 AOSP is only the second test build, as he has been focusing on TW first.
Click to expand...

Okay cool. I was under the impression you were on stock 4.3
That makes sense now.
Looks like he's taking a break from TW for a bit after the latest build and will be focusing on AOSP.
 
I go back and forth. Currently with the explosion of KitKat builds I am running more of that than anything else, but I switch back to my backup of JD's ROM when I need to answer specific questions that involve actually seeing what my phone is doing with that ROM running.
 
Was just able to flash the newest version of dkp tw kernel that came out on 12-09 and it works even better than the 12-02 I had running. :thumbup: It's much "snappier" and faster than the other build. Makes it feel brand new haha.

To upgrade, all I did was clear cache and dalvik cache.

Just wanted to give an update so that people know that he updates his kernel often.
 
Agreed, decimalman is freaking awesome and a tireless developer of his kernel, all branches of it, until a stable build emerges victorious.
 
tavisc said:
I'm on the MG2 bootloader. Is there any reason why I can't flash DKP?
Click to expand...

Are you saying you've tried and it won't work or are you asking theoretically if it's ok to flash? Kernels, like modems, are independent of bootloader. However, if you have Knox (it always comes back to Knox, doesn't it?), a custom kernel is the "trigger" that causes it to set the flag to 0x1, since even a custom ROM with its own kernel is considered to be a custom kernel as far as Knox cares. Moot point for most of us, whether or not we even have Knox, because root users have always known about the voided warranty possibilities.
 
struckn said:
Are you saying you've tried and it won't work or are you asking theoretically if it's ok to flash? Kernels, like modems, are independent of bootloader. However, if you have Knox (it always comes back to Knox, doesn't it?), a custom kernel is the "trigger" that causes it to set the flag to 0x1, since even a custom ROM with its own kernel is considered to be a custom kernel as far as Knox cares. Moot point for most of us, whether or not we even have Knox, because root users have always known about the voided warranty possibilities.
Click to expand...

Thanks struck I just woke up and misunderstood his question :) I was thinking MG2 ROM not bootloader.
 
TheBritton said:
Thanks struck I just woke up and misunderstood his question :) I was thinking MG2 ROM not bootloader.
Click to expand...

Just got up myself, had to squeeze in some forum time before getting ready for work! I think I read his question correctly, although there are two possible interpretations, which is why I asked for clarification.
 
struckn said:
Are you saying you've tried and it won't work or are you asking theoretically if it's ok to flash? Kernels, like modems, are independent of bootloader. However, if you have Knox (it always comes back to Knox, doesn't it?), a custom kernel is the "trigger" that causes it to set the flag to 0x1, since even a custom ROM with its own kernel is considered to be a custom kernel as far as Knox cares. Moot point for most of us, whether or not we even have Knox, because root users have always known about the voided warranty possibilities.
Click to expand...

Thanks, I'm just always worried about bricking. I'm not sure why, since I've had various kernels on others phones, and its never been a problem. Its most likely because this phone is so much more expensive compared to my older ones.

I don't believe I have knox. I haven't noticed anything about it when in download mode.
 
tavisc said:
Thanks, I'm just always worried about bricking. I'm not sure why, since I've had various kernels on others phones, and its never been a problem. Its most likely because this phone is so much more expensive compared to my older ones.

I don't believe I have knox. I haven't noticed anything about it when in download mode.
Click to expand...

I hear you on the expensive part there buddy! Just backup in recovery first and you'll be fine. Even if you had Knox, I just put that part in for some added info, not an actual concern.
 
Currently running the latest version of BMS on my CM11 12.27.2013 nightly. Seems to be running even quicker than the latest DKP currently. I'll update you guys tomorrow late afternoon or so, so that I can fully test it out for longer than 5mins haha. Data seems to be working fine as well. I have been "Booped by BMS".

yjajysup.jpg
 
ajnycguy said:
Currently running the latest version of BMS on my CM11 12.27.2013 nightly. Seems to be running even quicker than the latest DKP currently. I'll update you guys tomorrow late afternoon or so, so that I can fully test it out for longer than 5mins haha. Data seems to be working fine as well. I have been "Booped by BMS".

yjajysup.jpg
Click to expand...

Hows 4g lte and mms ?
 
You must log in or register to reply here.
Back
Top Bottom