[Kernel][Sony5.x][Z5C]Zombie[12.11.16]

[Marco20]

You were able to on lollipop? The only way I can get to recovery from this is to hot boot it in flash tool.

Same to me

Gesendet von meinem E5823

 

[gled]

You were able to on lollipop? The only way I can get to recovery from this is to hot boot it in flash tool.

I was able too in Lollipop to hot boot it, but not anymore since MM :/

 

[Momogs]

Hi

I am on Lollipop (bootloader unlocked) and downloaded the Zombie-B6 zip file. I used Fastboot to flash the boot.img file. Upon restarting the phone, I am stuck in a bootloop. Can you assist please.

Thanks

 

[ninestarkoko]

Hi

I am on Lollipop (bootloader unlocked) and downloaded the Zombie-B6 zip file. I used Fastboot to flash the boot.img file. Upon restarting the phone, I am stuck in a bootloop. Can you assist please.

Thanks

you can't use B6 as it's based on Marshmallow. Flash B5

 

[Momogs]

you can't use B6 as it's based on Marshmallow. Flash B5

Thanks. I figured as much and found a Lollipop based kernel. What is the URL for Zombie-B5?

 

[Gecc]

Thanks. I figured as much and found a Lollipop based kernel. What is the URL for Zombie-B5?

https://www.androidfilehost.com/?fid=24369303960683186

 

[Joeisgood99]

I managed to get my build booting. Sony really messed up the Readme. MM brought big changes, it will take some time to get everything correctly running.

So is it :
export DIFFCONFIG=common_diffconfig
export KBUILD_DIFFCONFIG=suzuran_diffconfig
make msm8994-perf_defconfig ???

I'm reading the Readme as:
expert KBUILD_DIFFCONFIG=suzuran_diffconfig
make msm8994-perf_defconfig

Looking at the output the common_diffconfig is referenced automatically. However the later results in a build that doesn't boot for me, sticks at the screen where the apps normally load without fully booting.

 

[amadib]

can we use this kernel with 32.1.A.1.185?

 

[civicsr2cool]

can we use this kernel with 32.1.A.1.185?

It's a lollipop kernel but probably

 

[Tommy-Geenexus]

So is it :
export DIFFCONFIG=common_diffconfig
export KBUILD_DIFFCONFIG=suzuran_diffconfig
make msm8994-perf_defconfig ???

I'm reading the Readme as:
expert KBUILD_DIFFCONFIG=suzuran_diffconfig
make msm8994-perf_defconfig

Looking at the output the common_diffconfig is referenced automatically. However the later results in a build that doesn't boot for me, sticks at the screen where the apps normally load without fully booting.

I use the former, not sure if the common diffconfig is automatically invoked.
Sorry for the late answer btw.

 

[Joeisgood99]

Hey @Tommy-Geenexus
Can you please link me to the commit that adds this feature??

Turquoise LED when EOC is reached (when battery is fully charged)

For some reason I cant find it....
EDIT: Found it!
Many thanks.

 

[Tommy-Geenexus]

New build is up!

Everything has changed about this kernel, the main focus lies on security and stability now.
Beware: Limited root support (/system not writeable); proprietary Exfat-module potentially broken (and i wont fix it)

 

[mindyabiznis]

Can I request FauxSound compatibility? As apposed to tomtom audio control which is command line based and irritating?

 

[Tommy-Geenexus]

Can I request FauxSound compatibility? As apposed to tomtom audio control which is command line based and irritating?

You can, but i am not going to add anything like that. You cant write to anything in /system either way.

 

[Tommy-Geenexus]

New build is up!

Changelog:

* Mitigated DirtyCow vulnerability (You can test vulnerability with the test suite)

Additionally i attached an App to the OP which displays your devices panel manufacturer!

 

[Tommy-Geenexus]

New Build is up!

Changelog:
* Added in November security patches

 

[don_pipo]

Has anyone a backup of Zombie b4 by any chance? :angel:
Rising a zombie from the dead back again...

 

[florstat]

New buils is up!

For exact details on improvements look at the OP.
I decided to release it now, as i may be busy over the next weeks.

As mentioned earlier, many improvements are included, i suggest checking my git repo to track all changes.

Important: Both Cluster are underclocked now!
Why? To keep it short, the energy usage of the SoC increases almost exponentially with increasing freqs (assuming all Cluster/CPUs are online).
Also, the manufacturing process is not optimal for high freqs because of high leakage, resulting in excessive heating.

The tradeoff of underclocking is marginally worse singlethreaded performance, however you will notice improvements both in battery-life and heat-emission.
F.e., i was able to play a demanding game without throttling for 20 minutes, while by default the throttling would hit in after less than 10 minutes.

Notice: This build does not allow any changes to the /system partition. A build with RIC disabled will follow later.
This is my personal (security-orientated) build i'm sharing here.

Hi, hope you'll read this.
I'm trying to build a custom underclocked kernel for the latest lineage available ( 14.1 ) as I noticed overheating/battery drain issues.
Do you think that just applying your patches would be enough in order to get overclock or do I need some extra step?
Are these ones those involved?
https://github.com/Sony-Kernels/and...c2417b4#diff-10e10dc2e2418a6d2d24c1a6696b8f24

 

[Tommy-Geenexus]

Hi, hope you'll read this.
I'm trying to build a custom underclocked kernel for the latest lineage available ( 14.1 ) as I noticed overheating/battery drain issues.
Do you think that just applying your patches would be enough in order to get overclock or do I need some extra step?
Are these ones those involved?
https://github.com/Sony-Kernels/and...c2417b4#diff-10e10dc2e2418a6d2d24c1a6696b8f24

If you want to underclock, apply the proper clk in the boot image's ramdisk init.
Overclocking is not advised, and the linked patch will not help with that.

This patch is needed for underclocking on stock Sony firmware.

This is all i can help you with, as i have retired from kernel development.

 

[florstat]

Thanks for you answer.
( for future reference:
I ended up applying this patch:
https://github.com/zachariasmaladro...mmit/1bd4d7bb5408283cbcc3d0ecfb6bdb83792acf57
It works well with little cores, but sometimes BIG ignore limits.
In my case that's not really important though, as I decided to set parameters in ramdisk init to disable them completely. )