Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Why don't you undervolt the frequencies independently? I can undervolt 300Mhz frequency down to 650mV rockstable. This is by far the most important frequency to undervolt, because the phone (should) stay the most time at this frequency.

Which powertop version did you use? With 2.7 i get errors about missing functions in the kernel and i*m not in the mood to compile a new one right now...

The blu_active governor needs alot of tweaking to be more battery-friendly than conservative. In its default configuration it goes way to fast to the highest frequency and stays there too long. So, a few tweaks are needed...

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Indeed I got this message too. Still I can use powertop and see no problem when the program is running. In addition I get that 'devfreq' message when stopping powertop.
If you cannot run powertop on your phone, maybe first try
I simply did not know how far I can go, so I just started with the values mentioned above by deprecated. Now I tried 650mV @ 300Mhz... and my phone crashed on me after some time.

I will continue to test some frequencies and also hope that others will post their values here.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Powertop problem is solved.

Here's my current voltage table:
But i'm not done yet. For testing the individual frequencies, just use the userspace governor an dset it to the desired cpu speed. Put load on the cpu and change the frequency. If the system crashes, you've gone too low, of course.

And you are right 'blu_active' uses more power than 'conservative'(around 250mw more). This was the governor i also always used.But it is less power hungry than the original 'interactive' governor(about 250mw less).

I'll try to add a another governor to the kernel which is based on conservative.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

I worked out some settings that I will test during the week on my 'daily runner' Nexus 5 (PVS 2 binned SoC.), using the new 'mautz-kernel'...

# Set CPU governor to 'conservative'
# Voltage table: -100mV (300mhz+422mhz), -70mV (652mhz-1267mhz), -60mV (1497mhz-1728mhz), -50mV (1958mhz+2265mhz)
# Set max GPU Clock from 450mhz to 320mhz
# Set Simple GPU Governor (default: 5, 6000)

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Kernel Update:

New features:
ZZmoove profiles
The governor profile can be changed by 'echoing' the corresponding number into /sys/devices/system/cpu/cpufreq/zzmoove/profile_number

This time i compiled two different flashable Zips.

This ZIP has blu_plug governor included and this one NOT.

Because i haven't found a way to disable the blu_plug governor, i made the ZIP without it, if you want to try out ZZmooves own hotplugging driver.
If you want to use ZZmoove with blu_plug, you should disable hotplugging in ZZmooves settings.

Sources have been updated.

Thanks to all the people whose original work i have added and of course all the people who made SFOS possible on the N5.

Have fun.

I'm going to add some more features to the kernel, if you have any wishes, please let me know.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Could it be, that you posted a wrong SFOS-custom.zip? It seems that the 'zzmove' governor is not included in the kernel just downloaded and tested.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

CPU or Hotplug governor, or both?

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

I would say both...

Here is what I tried:

I wanted to check the default settings of the "zzmoove" cpu governor, but '/sys/devices/system/cpu/cpufreq/zzmoove/' doesn't exist.

I then simply tried to set the governor with 'echo "zzmoove" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor'. That resulted in an error.

Last I tried 'find / -name "*zzmoove*' as root. Nothing is found.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Could you please download and flash it again? I downloaded tge zip, flashed it and zzmoove is working. If you still have problems we can sort them out on IRC later.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

I may have been distracted by the "update hell" I had, upgrading to 2.0.2.51 "Aurajoki". It took ages and I had to restart the upgrade process three times... ;)

Indeed the 'zzmoove' governor is available. The clue is, that you have to activate the governor first. Then, and only then the "/sys/devices/system/cpu/cpufreq/zzmoove/profile_number" file will be available.

Still... I prefer the "conservative" governor.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Hi all,

I've flashed the new SFOS-custom.zip four times now. The first time I was able to load zzmove once by:

[root@Nexus5 cpufreq]# echo "zzmoove" > scaling_governor

Now, I rebooted and tried again:

[root@Nexus5 cpufreq]# echo "zzmoove" > scaling_governor
bash: echo: write error: Invalid argument

I've reflashed the kernel several times, all with the same result. I can't get zzmoove to load. Any ideas? Thanks!

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Disregard my previous post. I fixed it by flashing the first revision back, then flashing the new one over it.

Probably just a permissions glitch on my end. Sorry!

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

I preffered the powersave governor(i don't know why, but it does scale and it is not fixed at the lowest frequency), everything was working well except the stuttering of the ring tone, when you get an incomming call..

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

This version has two more Conservative based governors included:

ConservativeX and Bioshock

ZIP with blu_plug
ZIP WITHOUT blu_plug

Happy testing.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

I'll be testing the new stuff with conservativex and bioshock soon.

Meanwhile, I made a fix to my intermittent call issues with the microphone on my Nexus 5. Not sure if it was due to a bug or a hardware fault, but every person I called reported a bad echo from my end. Not sure if this has been discussed here before, but my fix is as follows:

remount /system rw with: devel-su mount -o rw,remount,relatime,data=ordered /system

edit /system/build.prop (I used nano). Find the following strings and replace as indicated:

persist.audio.handset.mic.type=digital (replace digital with analog)
persist.audio.dualmic.config=endfire (replace endfire with false)

Save the file and reboot your device. Echo gone, call quality improved dramatically. Enjoy!

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Wow! This will be great. Yes. This has been discussed here before. This is the reason I stopped using Sailfish on my Nexus 5. I will do this and see if it fixes the issue.

Thanks a lot.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Or wait a few days, i'm going to release a new version next week.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

I'll wait a few days then. Thanks mautz, for your continued contributions to this wonderful community! :)

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

I don't know which version of SFOS adaptation do you use. On mako, we fixed the echo and bad call quality a while ago with @ballock by hunting down a bug in libhybris. Unfortunately, it took a long time to start using this bugfix due to relatively slow merge of the PR into the upstream libhybris. So, its possible that you are using SFOS with older version (@sledges suggests that the version with fix is 0.0.5.18). To test if you are hit by the bug, try to check whether properties are read in correctly:

getprop persist.audio.fluence.voicecall

(this can be run as nemo). If you see empty line as a response you are hit by the bug! Find an updated image for N5, or ask for an update, and enjoy noise-canceling digital microphone. If you get "true" as a response, you probably have a bug in hardware.

Similar issue was in onyx as well. There, it turned out that the bug was in the settings of underlying CM base. But, if I remember correctly, N5 was OK in terms of CM settings.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Hmm.. Looks like I have the buggy one. Do I need to remove and re-install SFOS with a newer image? Which image is the correct one? I am running under MultiROM.

Thanks for your help.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

@abyzthomas: you're welcome! just to be sure that its not due to the changes in property names (N4 vs N5): try to run also

getprop | grep audio

In this case, you should see the property that you checked and its value.

The bug was basically induced at long property names. If you don't have the property that you checked in |grep audio list, choose the one with the longest name and check that.

As for image, I don't know. Maybe @RealJohnGalt has a newer version somewhere around? Or ask on IRC... If I recall correctly, @sledges was fixing this bug on N5.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

A lot of people in Android-specific forums have cited the N5 noise cancelling microphone as a hardware fault, e.g. "cheap microphone". Disabling it and switching to analog was my best bet for being able to use it as a phone. My device adaptation is 0.0.1.3 and I'm running on SFOS 2.0.4.14. As of yesterday, my calls are clean with exceptional audio, even in wind and with background noise.

Perhaps we can find a later adaptation, but that suggests a huge road of work. For now, my fix works on Nexus 5 with our adaptation.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

/* Please note that the later assumes that you are on SFOS with getprop bug that I cited. Until its checked by getprop commands listed in earlier messages, this is an assumption */

So far, before the fix, the microphone that was loaded during voice call was actually analog microphone (at least on mako). It might have been misconfigured and what your properties do is probably fixing it with this regard. Situation before getprop bug fix was transmitting metallic and chopped voice, sometimes echo. When switching to Android (using multirom), the voice quality improved dramatically. After the fix, the voice calls in SFOS were the same as in Android, rather clear.

As for long road - since the bug is fixed and in hybris proper, its just a matter of bugging the developers to recompile the SFOS images. The long part of the road has been made ready in March ( https://github.com/libhybris/libhybris/pull/313 ). It just that it wasn't incorporated into mer-hybris for a long time. Now the patch is within, so its mainly a question of recompiling hybris. If you wish, you could probably do it yourself for N5.

Reminder: all text above assumes that you are hit by this bug. You could also test it by comparing voice call quality in Android vs SFOS on the same device. If Android can do better, its possible and rather simple to get the same voice call quality in SFOS.

Whether N5 is better suited for using analog or digital mic - that I don't know. It could be also a common hardware bug on N5.

Writing this up with a hope its of use for N5 users as well. :)

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

I applied your changes and will see if there is a change, although in my case people have not complained about sound quality during calls.

After a messy upgrade to sailfishos 2.0.2.51 (I was not patient enough), I pushed that multirom image to 2.0.4.14. I am very happy with the result... So yay... For the first time, I am 'bleeding edge' on my Nexus 5 when it comes to SailfishOS!

In general I am pretty optimistic when it comes to new 'hammerhead' images. We have come far with this device.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

For those who are testing the new 'mautz'-kernel, I can refer to a post I made some time ago. I wrote a systemd service that allows you to load all your settings @boot, and also toggle the settings.

Basically you can just follow this post http://talk.maemo.org/showpost.php?p...&postcount=672 and change the content of the '/usr/lib/systemd/scripts/cpu-governor' file to something like this...

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Freshly compiled kernels anyone?

First the changelog:
To get an idea what MDSS color control is you can get more infos on XDA.

The settings can be changed via Android app or sysfs:
There are many profiles available on XDA

The sound control hax lets you change the volume of the speaker/headphone/ringtone and so on. You could buy FuxSoundControl android app or use one of the many other kernel settings apps for android or configure it via sysfs:
But be carefull, for rising the audio above zero(default) up to 20 you can enter values 0-20, but for setting sound below twenty the values are 255(equals -1) down to 226(equals -30).

And NEVER echo "-10" while wearing headphones :eek:

To enable/disable one of the Hotplug governors use an app or take a look here:
Don't forget to only use one governor at a time and to disable mpdecision.

This page has some more information about governors.

Source is updated.

Compiled kernel can be downloaded here

Feedback welcome.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

Fantastic work, mautz. Doing a lot of testing! Thank you for the work you've put into these kernels, they just keep getting better!

I'll post my conclusions and results as soon as possible.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

@mautz, how do I go about disabling mpdecision to try one of the other hotplug drivers? I think I'm missing something obvious. :p

Edit: I'm looking at this strictly from an SFOS point of view. I don't use sfdroid as I like to avoid Google wherever possible, just on principle. Does SFOS use the same structure as Android as far as where the tunables are kept?

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

@deprecated: I'd suggest not to disable mpdecision. I played around custom kernels during summer on mako and it became clear very fast that kernels without mpdecision have a major problem on SFOS - many SFOS "boosters" communicate with mpdecision. As a result, kernels without mpdecision (Hells Core, for example) had issues with showing you GUI at the end of the boot. There were also plenty of complaining messages in journal regarding it.

I didn't look much further then into it since it seemed that, on ARM, SFOS does require mpdecision (some boosters are probably closed source, such like a silica one). So, if you guys can find the way around it that would be great. I ended up just using underclocking in the kernel for mako since it was actually very hard to find kernels with mpdecision enabled.

What you guys are doing with N5 kernel is very interesting and I hope that you could optimize this aspect of SFOS further. Good luck!

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

To disable mpdecision just rename mpdecision in /system/bin folder.
If you don't use another hotplugging governor the four cores of the cpu stay online at 300MHz when they are not used instead of going offline.

I haven't encountered any problems using another hotplugging governor for weeks now.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

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...

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

@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.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

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

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

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.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

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.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

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)

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

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.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

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.

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

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

Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 

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