[Xperia Z1 Compact Android Development] GNUDroid:
Back to where I started from! - Nearly. ;) But I'm really back to the quite old DU roms from august. Unfortunately this is the only really working one. And the only for on which a good custom kernel is avialable.

I have a question at you [MENTION=6927050]maz-1[/MENTION]: Are you still active on the Z1C? Basically this is a personal question, but I post here because maybe also other users are bothered by the same situation as me.

[the bad need: always to be up to date]

As for all device connected with the internet: The need for regular software updates is given by security. This exp specially for mobile phones: Compare: All people spending a lot of effort in hardening their router firewalls using anti virus on PC + updating their software. - But the device your carry with you? All your personal things. Often much more sensitive (emails, PMs, contacts, positions, camera) as on most users PCs.

[the main problems of Z1C: A the ROMs]

There is no ROM/kernel combination except yours which is working in satisfy way.

Meanwhile I switched in September aways from you build. I using the AICP build (last mostly worrking 20160919 build). I had to life with a not really working camera on concerts, in time critical situation at work (photos of experiments).

ACIP 20160919 Marshmallow (the last date where mostly all was working):

Everything is mostly working. Camera crashes laggy as hell. No chance at work, on concerts. And it is battery drainy. Even if xposed+greenify+build.prop tweaks + anplify + AICP build in wakelock blocker.

Jaguar (lollipop but security updates):

Camera: Wow as fast as in old lollipop roms! Quite a nice rom. But I had again many problems with the storage: Accessing SD card often makes trouble (important for my titanium backup + photos)

Android 7.0 and 7.1 builds: All drainy or a not working camera or even mobile data.

[the main problem of Z1C: B the kernel]

I was on an old android samsung device in 2009, then swithed for some years to the SII, then to the S4 mini, then to the Z1C: I'm really convinced for the need for a custom kernel:

Battery: A little bit undervolting + underclocking and 2 days life time instead of 1 as stock CM, AOSP, AICP, Omni,… roms. At same performance! The user can choose the right governor for his own needs (quick gui response, constant fps if some one plays games).

Speed: Many ROM developers neglect the influence of a custom kernel: Just the slim roms developers partly implement more than a the interactive or ondemand gov (performance + powersafe are useless).

[need for a custom kernel: NOW the really Important shock: S4 mini VS Z1C]

This Week I made a comparison which impressed myself: I found my old samsung S4 mini. A big developer community. Flashed a recent rom and tested the battery lifetime + performance.

S4/Z1C Lifetime: At the moments it was turned on with wifi always running since 5 days and showing 4 days left. 9 days! -Haha I never had this at the Z1C even everything on, even highly tuned to deep sleeps (Amplyify+greenify+frozen apps+wakelock blocker). Never ever longer as 4 days (not touching anything + no wifi)

S4/Z1C Performance: I started heavy apps like google maps on the two (2) core S4 mini + the four (4) core Z1C: They start in the same time. Sometimes the s4 is faster, sometimes the z1c. Similar. This is crazy. The Z1C is crappy without a tuned kernel.

This is really a demonstration, that the whole code base of the amami kernel seems to suck compared to to other phones.. Unfortunately our z1c has no big developer base, therefore I'm very glad that you provided once a good tuning. Since my speed/standby comparisons I even consider to revamp my old S4 mini.

@ Maz-1: What are your plans will you some-when continue on Z1C or are you already out of the amami development?