[Xperia Z5 Premium General] zacharias.maladroit:
[MENTION=6126659]PDesire[/MENTION] I wonder how long Sony will now take to release the kernel source for their 32.4.A.1.54 update,

it's not exactly because the delay, rather the limitations, roadblocks for the Z5 that exist which aren't seemingly there for the Z5 Compact, Z5 Premium, Z4/Z3+

e.g. you simply cannot disable e.g. SYSVIPC (which isn't needed for Android) but out of a strange reason the kernel doesn't boot without it,

then there's the dependence on a specific behavior of the kernel scheduler otherwise the ROM wouldn't enter into Android (to be fair, that also seems to happen to AOSP under certain circumstances

but the rate and occurrence this has happened for me on the Z5 is staggering),

also what is up with MHL ? When compiling the driver INTO the kernel the device also doesn't even boot !

That driver is bundled separately in the kernel source tarballs - so we don't have a reliable way (or know for sure) how to build it into the kernel and configure it,

which itself is a violation of the GPL since the whole kernel is under GPL v2 and after publishing the source we, the community ("we the people" :confused: ) should

be able to reproduce that work to have a booting kernel.

Perhaps the MHL driver isn't meant to be built INTO the kernel ? Well, the "stock" kernel is using a different MHL driver (outside of the kernel as a module),

why then offer that MHL driver in the first place ?

This is all pretty weird, then there's the case that the kernel doesn't boot at all when certain drivers are built INTO the kernel (well, it has happened before)

but in essence that defeats the whole purpose of security if you don't have a monolithic, closed kernel which is complete in itself which cannot be attacked in some way (sooner or later)

by loading foreign modules into kernel space and manipulation memory, rooting, crashing, etc.

[MENTION=6276304]DarkSilentSC[/MENTION]

One thing sure: Stock ROM is VERY bloated, it takes ages to load (would be interesting to know, why it takes that long - have you seen how quick e.g. LineageOS boots ? And that's with the same kernel !)

Then there's the DRM drama (certain ROM variants, regions on the world) when the DRM would cause excessive drain [it did for me on Lollipop] at pristine state (locked bootloader, no root),

the only fix was to flash tobias.waldvogel's patched kernel with the DRM emulation to get rid of the drain [wow - the community fixes a big corporates bugs again - awesome - NOT :eek:]

I've read somewhere that the SnapDragon 810 consumes 5 W peak compared to 1.5 W of the Snapdragon 820 (or 835 ?), in any case that processor [ARM stock design] was a really bad release without optimizations, probably rushed (against Samsung, Kirin, Apple, etc.) and the worst throw in Qualcomm's history.

In addition to that support has been dropped for it, which is kinda ridiculous since the SoC can hold its own against the competition, the chip has great performance - the issue is the small battery in relation to the high battery consumption ... [Sony bad decision, well - luckily we don't get another Note 7 :p But bigger battery or at least a battery pack as compensation would have been nice ]

Anyway ... that's all for now