@zacharias.maladroit please help check dis logs... Had a reboot while using the phone and was on Home was it rebooted.
Thanks.
Thanks.
@zacharias.maladroit please help check dis logs... Had a reboot while using the phone and was on Home was it rebooted.
Thanks.
Sorry folks,
I was originally planning to do some kind of "final" kernel but my Z5 is totally dead, broken (into pieces) and already gone
no Z5 or Z4/Z3+ development anymore.
Please refer to previous more stable kernel versions/releases
Sorry folks,
I was originally planning to do some kind of "final" kernel but my Z5 is totally dead, broken (into pieces) and already gone
no Z5 or Z4/Z3+ development anymore.
Please refer to previous more stable kernel versions/releases
you can flash it through fastboothello friends i am new to this z5 kernels and stuff could any one explain me how to flash it I have root access and unlocked bootloader thank you.:good:
you can flash it through fastboot
Download fastboot for Windows here:
https://forum.xda-developers.com/showthread.php?t=2588979
Make sure you install it system wide.
power off the device, hold volume down and plug it into the PC to enter fastboot
then, open command prompt in the folder with the downloaded kernel(make sure you unzip it to get the boot.img)
after that, type in fastboot flash boot boot.img
ALTERNATIVELY
you can flash recovery for the Z5
https://www.google.com/amp/s/forum....-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050/amp/
Same steps as above but
fastboot flash recovery <recovery image>
now, you can boot into recovery and flash the kernel zip
hello , is someone compatible whit RR Rom Nougat ? RR ver.5.8.5 2018-4-06 please answer my questionSince I've been getting requests lately due to Google's updated Google Drive policy - here's the updated share link for the Z5 kernels
Z5-Kernels - Google Drive
drive.google.com
hello , is someone compatible whit RR Rom Nougat ? RR ver.5.8.5 2018-4-06 please answer my question
1)
Choose your device from one of the 4 folders
Z5 + Z5 Dual:
- Stock Kernels: https://drive.google.com/open?id=0BykGGWB96CBQQy05VURLbzJTZlU
- Resurrection Remix: https://drive.google.com/open?id=0BykGGWB96CBQTnYzcGFURmhZbUk
- Carbon Rom 5.1:https://drive.google.com/open?id=0BykGGWB96CBQakJDRG03NTV0ZFU
- crDroid (3.7_HZ_4):https://drive.google.com/open?id=0BykGGWB96CBQdDVGNWxSR2ljdEk
Z5 Compact: https://drive.google.com/open?id=0BykGGWB96CBQVE0tb2dieTZMXzg
Z5 Prem + Z5 Prem Dual: https://drive.google.com/open?id=0BykGGWB96CBQaVZTdnF5QnVTMU0
Z4/Z3+ + Z4/Z3+ Dual: https://drive.google.com/open?id=0BykGGWB96CBQa2xBdHR5TzlrNUE
2)
At the upper right, click on "List View"
3)
At the top of the table, there are 3 labels (name, owner, [last] modified, File size)
click on "Last modified", the newest Kernels should be shown either at the top, or at the bottom
4)
Download the latest Kernel
5)
???
6)
Profit !
305_corona_III.1_9_12_5_2_ctl_X
- msm: thermal: load scaling was reverted (this should make thermal behavior less erratic and more predictable)
- much faster /proc/vmstat (mostly used in Kernel Adiutor first tab & others)
- random: 64 & 128 default values restored
- CVE-2016-5696 fix re-added since random depletion now seems to be avoided, no slower down anymore during longer usage (?)
- slim-msm: sleep while device-timeout (better battery savings, more reliable operation)
- GPU: disable POPP [Power Optimizer Push-Pop] - unfortunately too laggy
- GPU: re-add conversion of some workqueues to kthreads, now it doesn't cause micro-lags anymore
- revert: asynchronous resume threads (potentially unstable)
- TONs of fixes (i2c, ion, crypto, camera, sound processing, bluetooth [?], tcp, block, hid, ipa, mdss, evdev, memcg, memory-hotplug, ipv6, spmi, smd, cpuidle, usb)
- sps: fix kernel panic (fix hang/reboot/not waking up from sleep)
- block: make it possible to delete files again that previously were impossible to be deleted
- sched: fix task-priority when using SCHED_RESET_ON_FORK
- add branch instruction count (potentially significantly better performance)
- power: qpnp-fg: use powerefficient workqueues (potentially MUCH LESS battery consumption)
- soc: qcom: bam_dmux: fast-shutdown flag [supported ?], (potentially much faster shutdown of modem and MUCH more energy savings)
- arm64 optimized variant of crc32: 30-450% speed improvement [EXPERIMENTAL, might break encrypted phone function], could speed up the phone in certain areas A LOT
- input: make volume keys work while device is in sleep-mode since starting with MM that might not work anymore
253_corona_III.1_9_4_2
- 253_corona_III.1_9_4 based (supposedly more stable kernel)
- make Safetynet work
- fix DirtyCOW: preventing others (non-authorized users/apps) from obtaining root privileges
- fuse: fix infinite loop (mostly for (t)exfat microSD exfat driver and all others being bound/mounted via fuse)
- workqueue: allow rescuer thread to do more work
battery life said:This kernel is giving me horizontal standby lines after usage & while in Airplane mode,
this means: most of the kernel-side issues relating to battery efficiency and wakelocks should be fixed. (why wasn't it like that out of the box ?)
If your device doesn't go to sleep it's due to wakelocks, alarms and services keep it awake
If you cannot find the latest kernels change to List View and Sort by Date/Recently Changed
git log --pretty=oneline a1a44f5809da69a742f11d734b506d5928fddbad..HEAD
9ddbefd9f3deacf57fa18e7459a1106aafddb6a7 localversion
7eb6328eced607ea21d7c584120a7666fe3a4fbf Revert "cpuidle: don't disable cpuidle when entering suspend"
612e33421681b586be3ce1db9b2b4dc5eec474f6 Revert "msm: thermal: Use phandle to input the cluster cpu map"
5b37bef7b713ab0743a30546799b49b1d8a01624 Revert "msm: thermal: Use CPU phandles instead of cpu mask in KTM"
e9d3ef69478e5bc7b8c74d7572358fbd4f16f75f Revert "msm: thermal: Fix KTM code to check psm is enabled before handling it"
67142189e4a6c74f0caa5a402326d6a72dbdda46 Revert "msm: thermal: Update scm calls in KTM with non-atomic calls"
7d38d566cc6e150f79531b82d4aafafcfbe9501a Revert "msm: thermal: Retry on failure to hotplug"
35096150dc7152a172f15d458d7521c103c0069d Revert "msm: thermal: Fix sensor number printed during thermal WD bite"
5b2b2431b5b6678058d88decd207589d099406f0 Revert "msm: thermal: Add support to read KTM thermal configuration"
3fb901ba3ca1eb3448393b4d8fce77175b997a31 Revert "msm: thermal: Add support to disable KTM mitigation via debugfs"
57fdf696e27ccc661d656b7393cec4befdd4586b Revert "msm: thermal: Add kernel boot command to disable KTM"
d6bcad0c60eca12573623b1c41c24de159892b6a Revert "msm: thermal: Support new DT properties to disable KTM feature"
db05b93b8d99151942e93c8103b42ebba539243a Revert "msm: thermal: Fix zone id to tsens map lookup"
cba81424857e4e23af319b8fa17e482733be6e5b Revert "msm: thermal: Register for panic notifier on successful probe"
3a75678e662179d731a4120b247365c9be0febd0 Revert "msm: thermal: Add support for sending CPR temperature band"
d70e6d54846095dc2ce761d3d2ddf7598b573551 Revert "msm: thermal: Add support for Cx restriction at low temperature"
e86b2def1655028adcd89c77610ae3a0b179366e Revert "msm: thermal: Add support for bandwidth limit(BWLM) feature"
5aac40ff08fe27b64ed4d219a1166a2f8d3a2921 Revert "msm: thermal: Configure core sensor id on emergency frequency init"
Changes since 5.11_corona_III.1_9_12_8_ctl_X
update to 5.11_corona_III.1_9_12_8_2_ctl_X
Reverting "msm: thermal" ("thermal engine") changes that allowed userspace access to thermal engine behavior [might have caused instabilities]
Reverting "cpuidle: don't disable cpuidle when entering suspend"
1)
Choose your device from one of the 4 folders
Z5 + Z5 Dual: https://drive.google.com/open?id=0BykGGWB96CBQQy05VURLbzJTZlU
Z5 Compact: https://drive.google.com/open?id=0BykGGWB96CBQVE0tb2dieTZMXzg
Z5 Prem + Z5 Prem Dual: https://drive.google.com/open?id=0BykGGWB96CBQaVZTdnF5QnVTMU0
Z4/Z3+ + Z4/Z3+ Dual: https://drive.google.com/open?id=0BykGGWB96CBQa2xBdHR5TzlrNUE
2)
At the upper right, click on "List View"
3)
At the top of the table, there are 3 labels (name, owner, [last] modified, File size)
click on "Last modified", the newest Kernels should be shown either at the top, or at the bottom
4)
Download the latest Kernel
5)
???
6)
Profit !
224_I.1_2_12 Changelog said:Changelog:
- ramdisk change/bump to AndroPlus v33 (224 kernel)
- ramdisk change/bump to AndroPlus v33 (253 kernel)
- (due to unknown errors/reasons the process AndroPlus uses to create and modify his ramdisk appears to work better, thus using that)
- (thanks to @AndroPlus)
- .
- significant battery runtime improvements are to be expected
- during bootup ony the small core cluster is active == cooler bootup, but potentially also slower (it should however be fast enough)
- Overclocking: active after Boot for BIG core 2.0 GHz, little core 1.63 GHz , adjust with Kernel Adiutor, etc.
- <-- experimental, if it locks up during setup/bootup (e.g. wiping dalvik cache and re-creating cache), please let me know
- .
- "HOTFIX": reverted experimental bluedroid wakelock control - this should prevent lockup during bluetooth usage and accidental activation
- filesystem buffer increased LRU size
- task's adj rbtree for LMK (low memory killer - much more efficient during high memory load)
- usb-gadget functionality
- android keyboard support
- some smoothness tweaks for interactive governor/in general; kudos to @auras76
- fastcharge support (not sure if this has an actual effect, it seemed to have charged my phone faster ?, dunno)
- dynamic fsync
- optional input boost (input boost control), optimized input boost for little cores only (do not boost for big cores)
- setting to tweak throttling temperature
- .
If you have systemless root and systemless xposed on your system, you have to flash latest betaSU and latest systemless xposed framework immediatly after flashing a new Kernel. If you dont do this you will get a bootloop.
Changes: said:
- I.1_2_13
- enabled dynamic_fsync
- added SIO + FIOPS i/o scheduler (give it a testing and let me know how it works)
- interactive cpufreq governor: some tweaks
- leaving disabled LMK adj rbtree improvement (didn't work in the past and also failed compilation this time)
- Overclock BIG core 2.2 GHz, little core 1.63 GHz (down from 1.7 GHz)
- arm64 optimizations
- cpufreq handling fix for cpuboost
- .
- I.1_2_14 (14 + .15 were a combined test-kernel with CPUQUIET)
- .
- I.1_2_15 (14 + .15 were a combined test-kernel with CPUQUIET)
- .
- I.1_2_16 (skipping this kernel release)
- new SUNRISE3 optimization flags (should squeesh out some more performance and stability)
- charging LED cyan stuck fixed (thanks to @oshmoun )
- SLIMBUS improvements (natural sound amplitude),
- NVIDIA powerefficiency improvements rework ( thanks to @RyTekk )
- some (general) sound improvements
- .
- I.1_2_17
- frandom (increase security with encryption/security in Android in general, better overall smoothness of UI)
- more (specific) sound improvements (these should be really noticable),
- scheduler efficiency improvements (might be better / might not; peak performance is somewhat lower, since it doesn't clock up that quick, faster in idle)
- writeback optimizations (less stalls and latency spikes during heavy writes)
- a bunch of ext4 + kthread stability and reliability improvements
If you have systemless root and systemless xposed on your system, you have to flash latest betaSU and latest systemless xposed framework immediatly after flashing a new Kernel. If you dont do this you will get a bootloop.