not 100% stable according to Adrian (in my case, it's working well)
v4.6
CPU underclocking
v4.5
smoother (finally!)
no underclocking (it will be readded very soon)
v4.3
CPU underclock to 281 MHz
experimental Android M support
earlysuspend removed
fixed slow speed & long boot after booting from offline charger
if you have slower performance, stick to v4.2
v4.2
interactive governor (use it at your own risk, will probably cause reboots)
CPU 1458 MHz bug fixed
v4.0
Motorola memcpy enhancements for Krait CPUs
some source updates [*]CPU 1458 MHz bug (only on certain devices)! Caution!
super smooth!
v3.4
a couple of source updates
yankactive (it's bugged and it will be removed) and smartmax CPU governors
memcpy optimizations and auto hotplug disabled for testing purposes
v3.3
latest source updates
NTFS read/write support
SELinux is enforcing
v3.2
latest touchscreen fixes by @AdrianDC
auto hotplug added
v3.1
incall touchscreen bug fixed (big thanks to @Adrian DC)
Motorola memcpy optimizations (faster copy to memory)
CPU frequency table finally fixed
msm_mpdecision fixed
dynamic fsync temporarily removed
other source updates
v3
CPU overclock up to 1,944 GHz
new CPU governor: impulse
greatly improved CPU-boost (now it has got more options & new features)
dynamic fsync v1.5
build with the latest UBER toolchain & GCC 5.2
v2.2
SELinux is permissive (for M)
source updates and f2fs updates (thanks to @Mrcl1450 and @Adrian DC)
clean frequency table
UKSM updated to v0.1.2.3
bricked hotplug
v2.1
all the TCP congestion control algorithms are available
WLAN source updates
initial build for M
v2
FauxSound v3.6
debugging info removed from modules (now they're smaller)
CPU governors: interactive removed, bioshock, wheatley, ondemandplus, intellidemand2 added
I/O schedulers: added fifo, vr, zen
intellithermal
intelliplug
ZRAM for now removed (it caused kernel panics)
UKSM 0.1.2.1
v1
Linux 3.4.110 + other device-specific tweaks (thanks to @Mrcl1450 & @Adrian DC)
built with GCC 5.2.1 and UBER Toolchain + various optimization flags
CPU undervolting
sioplus I/O scheduler
ZRAM & zsmalloc backported from Linux 3.14
KSM (kernel samepage merging)
inbuilt frandom support
swap support
USB fast charging
Debugging
/proc/kmsg is a file that stores all the kernel messages from the very first seconds of the boot process. A copy of that file isn't always needed to fix a bug, but since I've explained how to get one I don't even remember how many times, I'll write here the needed steps:
1. open a terminal on your phone
2. run the following commands:
Code:
su
dmesg > /sdcard/helium.log
3. the log will be stored in helium.log. If the issue caused a reboot, step number 2 changes:
Remember to always check the second post before installing, to see if there are warnings/known bugs!
Thanks to:
@Adrian DC
@daedroza
@Mrcl1450
@bbedward
@pec0ra
@DooMLoRD
@nosedive
@dorimanx
@faux123
@Sultanxda
@osm0sis
@GalaticStryder
@Andreus94
@neobuddy89
@nikhil18
@Unusual Man
@Onawt
and all the authors of the hundreds of github commits in Helium's repo!
XDA:DevDB Information Helium kernel, Kernel for the Sony Xperia SP
init.d script editing - not required as of v46 Important: your modifications to the script will be lost:
when you update the ROM, if you use an AOSP-based ROM;
never (changes are persistent), if you use a CM-based ROM.
the init.d script provided with the kernel (01helium) contains some lines that enable or disable certain features. Remember that the script is written in shell language, so the lines starting with # are ignored.
In the script you'll find useful tips to edit it correctly.
What goes wrong? At which point does the phone get stuck? I also got a booting problem once today, after the SONY logo I got a black screen and then the SONY logo again, but after a few seconds the phone booted. So wait a few minutes before stating that the phone doesn't boot and tell me what do you see.
On CM12.1 Official 20151116 with Helium v1 I can't use toggle buton to see my last used apps
With T10.2 this working.
I don't know how but this is strange.
It boots all the way up to the home screen, in the same second the screen goes fuzzy and the device reboots. It's also plagued with that weird 1.4 Ghz issue that affects so many X-SP devices, I didn't managed to boot into KA, but it's obvious because it takes ages to do the apps optimization after cache/dalvik cleanup.
Oh yes, that's true. The 1.4 Ghz issue it's a device issue, rather than a kernel or a ROM one. I've erase and format everything, including internal storage. Clean install with ROMs that were reported as working fine with Tangerine.... still not able to go above 1.4 Ghz.
Oh yes, that's true. The 1.4 Ghz issue it's a device issue, rather than a kernel or a ROM one. I've erase and format everything, including internal storage. Clean install with ROMs that were reported as working fine with Tangerine.... still not able to go above 1.4 Ghz.
It's weird, because I'm not the only one with this problem and it works just fine with stock kernel or Tangerine up to 9.2.
I'll go back to stock tonight and then return to LP, hope to report "fixed". Thanks, Tomoms.:highfive:
It's weird, because I'm not the only one with this problem and it works just fine with stock kernel or Tangerine up to 9.2.
I'll go back to stock tonight and then return to LP, hope to report "fixed". Thanks, Tomoms.:highfive:
A few advices: when you come back to LP, if the issue is fixed on stock ROM and stock kernel, flash the LP ROM you want, flash gapps/xposed/any other thing you need but non Tangerine nor Helium. Then boot, install Trickster MOD Kernel Settigs and check if frequencies are OK. If it's OK, do not install Kernel Adiutor. Then flash Helium, do not wipe anything. Reboot and check.
And... what's the reason for not able to go above 1674 Mhz on antutu? If I benchmark on 1674+++ phone resets itself while testing processor. Hardware issue? Normally can use 1900++ , but on antutu... damn...
A few advices: when you come back to LP, if the issue is fixed on stock ROM and stock kernel, flash the LP ROM you want, flash gapps/xposed/any other thing you need but non Tangerine nor Helium. Then boot, install Trickster MOD Kernel Settigs and check if frequencies are OK. If it's OK, do not install Kernel Adiutor. Then flash Helium, do not wipe anything. Reboot and check.
Installed stock 4.3, than erased and format everything, I even removed the SD-card. Flashed latest CM 12.1, no gapps. Trickster - everything OK, 1.7 Ghz. Then I've installed Tangerine 11.1 - max. 1458 Mhz :crying: Uninstalled 11.1 and installed 10.2 - still not going above 1.4 Ghz I rest my case, good luck with Helium.
not 100% stable according to Adrian (in my case, it's working well)
v4.6
CPU underclocking
v4.5
smoother (finally!)
no underclocking (it will be readded very soon)
v4.3
CPU underclock to 281 MHz
experimental Android M support
earlysuspend removed
fixed slow speed & long boot after booting from offline charger
if you have slower performance, stick to v4.2
v4.2
interactive governor (use it at your own risk, will probably cause reboots)
CPU 1458 MHz bug fixed
v4.0
Motorola memcpy enhancements for Krait CPUs
some source updates [*]CPU 1458 MHz bug (only on certain devices)! Caution!
super smooth!
v3.4
a couple of source updates
yankactive (it's bugged and it will be removed) and smartmax CPU governors
memcpy optimizations and auto hotplug disabled for testing purposes
v3.3
latest source updates
NTFS read/write support
SELinux is enforcing
v3.2
latest touchscreen fixes by @AdrianDC
auto hotplug added
v3.1
incall touchscreen bug fixed (big thanks to @Adrian DC)
Motorola memcpy optimizations (faster copy to memory)
CPU frequency table finally fixed
msm_mpdecision fixed
dynamic fsync temporarily removed
other source updates
v3
CPU overclock up to 1,944 GHz
new CPU governor: impulse
greatly improved CPU-boost (now it has got more options & new features)
dynamic fsync v1.5
build with the latest UBER toolchain & GCC 5.2
v2.2
SELinux is permissive (for M)
source updates and f2fs updates (thanks to @Mrcl1450 and @Adrian DC)
clean frequency table
UKSM updated to v0.1.2.3
bricked hotplug
v2.1
all the TCP congestion control algorithms are available
WLAN source updates
initial build for M
v2
FauxSound v3.6
debugging info removed from modules (now they're smaller)
CPU governors: interactive removed, bioshock, wheatley, ondemandplus, intellidemand2 added
I/O schedulers: added fifo, vr, zen
intellithermal
intelliplug
ZRAM for now removed (it caused kernel panics)
UKSM 0.1.2.1
v1
Linux 3.4.110 + other device-specific tweaks (thanks to @Mrcl1450 & @Adrian DC)
built with GCC 5.2.1 and UBER Toolchain + various optimization flags
CPU undervolting
sioplus I/O scheduler
ZRAM & zsmalloc backported from Linux 3.14
KSM (kernel samepage merging)
inbuilt frandom support
swap support
USB fast charging
Debugging
/proc/kmsg is a file that stores all the kernel messages from the very first seconds of the boot process. A copy of that file isn't always needed to fix a bug, but since I've explained how to get one I don't even remember how many times, I'll write here the needed steps:
1. open a terminal on your phone
2. run the following commands:
Code:
su
dmesg > /sdcard/helium.log
3. the log will be stored in helium.log. If the issue caused a reboot, step number 2 changes:
Remember to always check the second post before installing, to see if there are warnings/known bugs!
Thanks to:
@Adrian DC
@daedroza
@Mrcl1450
@bbedward
@pec0ra
@DooMLoRD
@nosedive
@dorimanx
@faux123
@Sultanxda
@osm0sis
@GalaticStryder
@Andreus94
@neobuddy89
@nikhil18
@Unusual Man
@Onawt
and all the authors of the hundreds of github commits in Helium's repo!
XDA:DevDB Information Helium kernel, Kernel for the Sony Xperia SP
Hurray, a new version of Helium is available! ONLY for Lollipop for now!
Ok, let's talk about the hot stuff you'll find in it.
powersuspend v1.7:
powersuspend is a replacement for the old earlysuspend. earlysuspend was a suspension manager that was removed by Adrian some months ago since it's really outdated. This replacement is more modern and provides better power management since it "talks" with the CPU hotplugs, for example, and tells them when to enter a "suspended state".
How does it work? At the beginning, it could be triggered either by the kernel itself, or by the LCD panel (when screen went off, it entered the suspended state). It could also be triggered manually by the user (pretty useless in my opinion). Since the "kernel trigger" doesn't work properly on Lollipop on many devices, I cleaned up the code a bit and now it can be triggered only by the LCD panel. This cleanup causes a sort of "bug" in Kernel Adiutor: KA will show that powersuspend uses the "Autosleep" trigger even though, actually, it's set on the LCD panel trigger. This however doesn't affect anything. It's only a visual bug and even if you set the powersuspend trigger method to something else, it will go back to "Autosleep". Don't worry, it's working properly. I've got proof.
powersuspend was developed by the great faux123, so thanks to him!
hotplug updates:
intelliplug by faux123 was updated to v5.0. msm_mpdecision (a.k.a. bricked hotplug) by showp1984 and neobuddy89 also got a massive update. A new hotplug has been added: msm_hotplug by Fluxi. All these hotplug are well integrated with powersuspend and they have many tunable parameters!
ZRAM, zsmalloc backported from Linux 3.17:
ZRAM and zsmalloc have been backported from Linux 3.17 by Adrian. He also fixed the old swap bug so he deserves a huge "thank you"!
MSM_Limiter:
msm_limiter is an interesting tool that allows to set a different max frequency for the CPUs when the screen goes off. It talks with powersuspend to work properly. Unfortunately I couldn't find an app to control this feature so the only option is to do so by using the sysfs interface (more details will follow).
It's developed by neobuddy89.
library updates:
some libraries were updated: lib/genalloc was backported from Linux 3.10; lib/memcopy and lib/string were also backported from their glibc versions (this leads to better performance).
built with GCC 5.3.1:
v5.0 has been built with GCC 5.3.1 and the very latest UBER toolchain. The header files used by the kernel to improve the build have been simplified and updated too.
power efficient workqueues:
These new workqueues are tied to the CPU core they were created on and they avoid onlining cores if it's not strictly necessary, and they improve the use of CPU cache.
new CPU governor:
smartmax has been added.
KSM replaced UKSM:
maybe temporarily, maybe forever. KSM now has better power management features than UKSM.
init.d support re-added
lighter installation zip (TWRP is not included anymore)
as usual, lots of source updates (especially for f2fs)
Important! How to enable msm_limiter:
For your convenience, I suggest you to edit the /system/etc/init.d/01helium script after flashing the kernel (or even before - you can find it in the "scripts/init.d" folder of Helium's zip).
The line above is an example of how to set a maximum frequency for all cores when the screen is off. 1026000 is 1026 MHz, that is 1,026 GHz. Change the first four digits to any other existing frequency (check them in Kernel Adiutor, for example), otherwise the limiter won't work.
I don't know why, but msm_limiter overwrites the general max CPU freq. when screen is on. So you really must edit this line in the script if you want to use msm_limiter. Change "1728000" with the max frequency you want the CPUs to use when the screen is on, for example I put "1832000".
If you want to change one of these values, just edit the script. The new values will be applied after a reboot. You should re-edit it whenever you reflash the kernel though.
You can also edit the single files once the phone has booted, but the script will overwrite them as soon as you reboot. If you want msm_limiter to be always on, from phone bootup to poweroff, the simplest way is to edit the 01helium script as I've just explained you.
If you want to keep msm_limiter disabled, simply don't touch the script. It will set the default values I've put in, but anyway, unless you change the first line I wrote about, the limiter will be disabled.
TL;DR:
you cheater! You really must read the long post!
Well, I hope I have mentioned all the changes! Enjoy the release
Thanks to:
all the users mentioned in the changelog, the Linaro team, dorimanx and Adrian, of course
Ok guys so I'm going to take a little "break" from kernel development. There are 2 reasons:
Helium as of now can be considered a complete kernel (I can't think at something big that hasn't been added yet)
I've got other things to do
This however doesn't mean that I'll stop releasing updates - on the contrary, as soon as Adrian finishes the new kernel updates I'm going to release v6 and I'll continue releasing fast minor updates when Adrian adds something - , it simply means that all the features I've been striving to implement lately are finally included, so there isn't much to do now.
And this doesn't either mean that I'll disappear from XDA: I'll follow ROM development and I'll be happy to answer your questions, discuss problems et cetera.
