Kernel v6 has arrived.

Source still up on Github.

Changelog:
I/O scheduler is set at /sys/block/mmcblk0/queue/scheduler.
gives you a list of available schedulers and shows which scheduler is active.


The backlight can now be dimmed beyond the lowest setting.
Change /sys/module/lm3630_bl/parameters/backlight_dimmer to '1' to activate the feature and set your desired value in /sys/module/lm3630_bl/parameters/min_brightness (default is 5)
Change your brightness in settings to maximum and back to minimum to check your results.

Force fast charge can be enabled at /sys/kernel/fast_charge
'1' is the old behaviour(charging with usb up to 900mA)
'2' lets you choose your desired charge level. Available levels are:
500 900 1200 1500 2000 (change in fast_charge_level)

To enable doubletap2wake feature change /sys/android_touch//doubletap2wake to '1' for the bottom half of the screen and '2' for fullscreen.

How long dt2w is active can be changed in /sys/android_touch/wake_timeout (in minutes, 0 is always active).
dt2w is active again after unlocking the phone.

To stop doubletap2wake feature using the power button set /sys/module/qpnp_power_on/parameters/pwrkey_suspend to '1'.
dt2w is active again when you lock the screen with swipe to lock or using the lock button.

But since dt2w is not a native feature of the N5 it will cause battery drain, i haven't tested it long enough to say how much battery it costs, because i got used to the lpm screen unlocking.

Flashable ZIP can be downloaded here.

Sorry, i've uploaded a ZIP which was missing the westwood TCP congestion control, link is now fixed (11-16-2016 11:11 PM)

Happy testing...

@mautz: Let me tell you first, that you make me feel like a little boy, full of pleasure, testing new stuff almost every evening. Big Kudos to you!


So I wanted to share my current test settings with you, using v6 of the mautz kernel.

I recommend 2.0.4.* as sailfish version. In my opinion it is more stable than the proposed 2.0.1.11 at the first page of this thread. I upgraded my version with OTA to 2.0.4.14, but there is a new '2.0.4.13' image available here... http://images.devaamo.fi/sfe/hammerhead/beta5/

I had some very rare freezes/reboots with my old voltage table, so I went +5mV for the whole range. I might do some fine-tuning later. The device is rock stable now.

I use Alucard as hot-plug governor with default settings. I think I love that one. With the new v6 kernel I set [noop] as I/O scheduler. 'They' say, [noop] is good for battery life. Other option I might try is [fiops].

I did not touch the dimmer settings, neither 'doubletap2wake' or 'fastcharge'. 'Dt2w' might drain battery, and I see no need for 'fastcharge', using a QI charger.

Hi,
is it a very bad idea to try an OTA to 2.0.4.13 from the link above using the method from the link below?
https://wiki.merproject.org/wiki/Ada...for_hammerhead

I've OTA'ed from 2.0.1.11 to 2.0.4.13 and 2.0.4.14 with ease, installing 2.0.1.11 following the guide in the first post of this thread. I think you'll be just fine OTA'ing to 2.0.4.1x after installing following the guide you linked.

Edit: just make sure to back up anything of value, as this is all a,“beta” process.

Here is what I did to bring my Nexus 5 to version 2.0.4.13:
- Download the magic-device-tool from https://github.com/MariusQuabeck/magic-device-tool because I'm lazy
- Install Sailfish OS using the tool
- Update to 2.0.4.13 using the instructions on this page https://wiki.merproject.org/wiki/Ada...for_hammerhead by replacing the RELEASE number
Job done... but, the battery still drains at the same speed haha silly me ;-p
I guess the way to go is to flash and patch as advertised on the first page of this thread if you are looking for less battery drain.

Did you flash the new kernel by user 'mautz'? https://www.dropbox.com/s/u0r74xx8uy...el-v6.zip?dl=0
I would try that first and do some tuning. Would be cool to share your results... (see previous posts in this thread)

My guess is you overestimate my "tuning" abilities but here I go again with the flashing session . What I just did, between my previous post and your reply is flash and patch as on the first page. I will do that again now as I understand one should not flash over a system that booted already.
Do I flash the kernel after flashing sfos and leave out the sensors patch? I guess so.

As I had a spare multirom test image, I tried something. Basically I just flashed the 2.0.4.13 zip file over an existing 2.0.1.11 installation. It works, BUT it will reset your device. All your data will be gone!


Backup/Restore

So you need a backup of your data. That brings us to another problem with 2.0.4.X. With the new version, the backup routine has fundamentally changed! The software is looking for an sdcard, and as we don't have an sdcard slot on the Nexus5, you cannot use the 'backup/restore' routine in the 'settings' app, unless you work with a CloudService-Account.

I use a different way. I use 'rsync' and backup the whole '/home/nemo' folder to my computer over wifi. That works well for almost everything but 'contacts/calendar'.

For 'contacts/calendar' I found a way in the SailfishOS cheat sheet ( https://sailfishos.org/wiki/Sailfish...t_Sheet#People ). You can export the 'contacts/calendar' to a file...

You can then import the data by opening the files with the jolla-file-browser.

No. You need to apply the sensorsfix3.zip anyway, but just once. Afterwards you can just flash any new kernel zip file.

Ok thanks, will finish the install.
Just wanted to share that I use fruux.com for the contacts and calendar.