[KERNEL][Z3] 78Kernel v3

[tiliarou]

Can I flash it over a D6633 stock rom ?

 

[-Happy Feet-]

Has anyone try to undervolt?

 

[blackhawk_LA]

Has anyone try to undervolt?

Yes, - 75mV for all frequencies and is still stable. But it varies between phones so you may suffer reboots

Sent from my D6603 using Tapatalk

 

[-Happy Feet-]

Yes, - 75mV for all frequencies and is still stable. But it varies between phones so you may suffer reboots

Thanks for the info, I try it

 

[Dobsgw]

Has anyone try to undervolt?

This is where I'm at now.
Whenever I get free time I undervolt a frequency by 5mv at a time and run a stability test.
I found globally undervolting caused reboots because certain frequencies will require a jump in voltage.
So try globally undervolting and run stability tests.

Then when you get reboots and stuff add like +10mv globally
Then on each individual frequency lower it 5mv at a time.

Btw it's really just for fun. It won't save you battery. Screen pulls far more battery than CPU. But it supposedly makes the CPU run cooler. So have fun

 

[blackhawk_LA]

So to make it work you're gonna need to remove all the files associated with root and scripts that interfere with the kernel (Ie they both try and so the same thing)

So in the Krypton folder in the zip delete recovery, root, superSU

Then go through the updater script and anything to do with those folders and the files in them needs to be deleted. Just use your instinct. If you deleted it then don't let the updater script try and flash it or it'll throw an error

This way you remove all conflicts and it can boot after flashing.
Flash kernel directly after flashing ROM so you keep recovery.

I'm still trying to make the kernel work with ExistenZ. I've compared LB and UB versions of your ROM to look for the differences, and besides everything related to root and recovery, I realized that framework-res.apk are different in each ROM. Maybe is there any change needed here? I remember decompiling and compiling an apk some time ago, to do a very simple editing, but I really have no idea of this kind of things. So if you can suggest me anything, I would be grateful!

 

[Dobsgw]

I'm still trying to make the kernel work with ExistenZ. I've compared LB and UB versions of your ROM to look for the differences, and besides everything related to root and recovery, I realized that framework-res.apk are different in each ROM. Maybe is there any change needed here? I remember decompiling and compiling an apk some time ago, to do a very simple editing, but I really have no idea of this kind of things. So if you can suggest me anything, I would be grateful!

I doubt that framework-res.apk will have an effect on the kernel booting.
It's very strange that it doesn't work even after removing root related parts of system.
Idk what to suggest.

Ideally you need Niaboc to fix it but he might not have time for Z3 ROMs anymore

 

[blackhawk_LA]

I doubt that framework-res.apk will have an effect on the kernel booting.
It's very strange that it doesn't work even after removing root related parts of system.
Idk what to suggest.

Ideally you need Niaboc to fix it but he might not have time for Z3 ROMs anymore

Iasked him but he told me he can't help because he doesnt have Z3 files in his computer anymore.
I thought that framework-res could be related because the phone boots fine until launcher and lockscreen is loaded. but you surely know better than me :good:

 

[Dobsgw]

Iasked him but he told me he can't help because he doesnt have Z3 files in his computer anymore.
I thought that framework-res could be related because the phone boots fine until launcher and lockscreen is loaded. but you surely know better than me :good:

Oh actually then it is possible that it's the framework.

I highly doubt it though due to my own experience.
When i had the same issue with Fragment ROM the solution was to remove all recroot files.
Sometimes it wouldn't boot at all and sometimes i got to lock screen before the crash happened.

At least this kernel works everywhere else and it really is great

 

[blackhawk_LA]

Oh actually then it is possible that it's the framework.

I highly doubt it though due to my own experience.
When i had the same issue with Fragment ROM the solution was to remove all recroot files.
Sometimes it wouldn't boot at all and sometimes i got to lock screen before the crash happened.

At least this kernel works everywhere else and it really is great

FOUND! After some trial and error, the culprit is module wp_mod.ko. Deleted it and now ROM boots normal but I seem to have problems with remounting system; sometimes xposed is not recognized. Do you know how could I solve this?

@Gustavo RD78

 

[Gustavo RD78]

New build!

Note: Only for deodexed roms! (removed .sqsh executables)

Updated TWRP recovery 3.1.0-0 thanks @shoey63
Patched DRM for this method
Slightly Underclock
Slightly Overclock
LMK optimizations
Add 100mhz step for GPU

Check my github for all progress

78Kernel_v3.2

.

 

[yecomixer]

@Gustavo RD78

Can it be installed over the previous version or recommend a clean installation?

 

[Gustavo RD78]

@Gustavo RD78

Can it be installed over the previous version or recommend a clean installation?

Installation on the previous ?

 

[yecomixer]

I realize that after installing this version of kernek you have to reinstall superSU in this case I chose the version SuperSU 2.79 SR3, otherwise it will stay in a bootloop.

 

[Gustavo RD78]

I realize that after installing this version of kernek you have to reinstall superSU in this case I chose the version SuperSU 2.79 SR3, otherwise it will stay in a bootloop.

Exactly, every time you change the kernel you need to re-flash SuperSU.
I'm using 2.79 Stable

 

[yecomixer]

Exactly, every time you change the kernel you need to re-flash SuperSU.
I'm using 2.79 Stable

I have been testing the kernel v3.2 these days but I have an error every time I am in the Google+ application as the minute I reboot the mobile and go back to version 3 of the kernel and I do not get error

 

[juanpirulo]

I have been testing the kernel v3.2 these days but I have an error every time I am in the Google+ application as the minute I reboot the mobile and go back to version 3 of the kernel and I do not get error

I dont know what kind of error you ve got with google+. I havent got any problem. cheers

ok now google+ force closed so yes there is a problem

edit again. I ve open again and work with google+ a few minutes no more force closed. So I dont know if is kernel related. cheers

 

[yecomixer]

I dont know what kind of error you ve got with google+. I havent got any problem. cheers

ok now google+ force closed so yes there is a problem

edit again. I ve open again and work with google+ a few minutes no more force closed. So I dont know if is kernel related. cheers

To me it started to happen since Google+ was updated to the latest version 9.11.0 because in the previous version does not happen I will try a clean installation of the kernel to see if the problem persists

 

[MacSeoin]

78kernel v3.2 causes system mounting problems on fragment v5

 

[juanpirulo]

78kernel v3.2 causes system mounting problems on fragment v5

No Problem with linuxroom. Had you install supersu systemless right after updating the kernel? cheers