maemo.org - Talk - SailfishOS 2.0 Nexus5 based on CM13 alpha release

Page 1 of 17

Next >

Last »

Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)

- SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)

- - SailfishOS 2.0 Nexus5 based on CM13 alpha release (https://talk.maemo.org/showthread.php?t=99377)

mautz

2017-05-10 11:02

SailfishOS 2.0 Nexus5 based on CM13 alpha release

Hi!

So, i thought it would be a better idea to start a new thread instead of spamming the 12.1 thread with messages about cm13.

First of all, i want to thank all the people at #sailfishos-porters who helped me countless times, when i was stuck. Thank you guys!

Installation:

Installation is the same as on cm12.1:

Normal install

Multirom install

You need to use this multirom recovery or you won't be able to flash sensorsfix3.zip after installation.

Changelog

Code:

05/22/2019 released SFOS image 3.0.3.9

11/12/2018 released SFOS image 3.0.0.8

11/22/2017 released SFOS image 2.1.3.7

10/07/2017 added OTA instructions

10/07/2017 released SFOS image 2.1.2.3 



09/19/2017 released SFOS image 2.1.1.26 build 02

- fixed GPS issue



09/14/2017 released SFOS image 2.1.1.26



09/13/2017 released SFOS image 2.1.1.24



05/16/2017 Released SFOS image 0.3:

- fixed bluetooth sleep issue.



05/11/2017 Released SFOS image 0.2: 

- home and adaptation0 repo issues fixed, store works without user intervention.

Needed files:

Multirom recovery: http://www.mediafire.com/file/1cihx7...d_20150630.img

CyanogenMod 13 patched: http://www.mediafire.com/file/970u3n...13_release.zip

SFOS-3.0.3.9 image:
http://www.mediafire.com/file/9hkddf...0.3.9.zip/file

Things that don't work:

- Video recording
- BT calls have bad quality

I hope these things get fixed in the future.

Wifi tethering
See this post

OTA - Over the Air update

repos for updating to 3.2.1.20 can be found here.

Repos for updating to 3.0.3.9 can be found here.

Updating from 2.1.3.7 is a little bit more complicated...read here.

Best way to update SailfishOS is by using an ssh connection to the phone.
Disable all patches and Openrepos repositories before updating.

Before updating use

Code:

ssu lr

to check if "adaptation community"(not to be confused with "adaptation-community-common"!) repo is available. If it is please disable it by using

Code:

ssu dr adaptation-community

.

Add the new adaptation-community-hammerhead repository:

Code:

ssu ar adaptation-community-hammerhead http://repo.merproject.org/obs/home:/mautz:/sfos-latest/sailfishos/

Set desired release version, for example 2.1.2.3:

Code:

ssu release 2.1.2.3

Refresh the package cache:

Code:

pkcon refresh

Upgrade SailfishOS:

Code:

version --dup

Reboot the phone and enjoy the new release.

Known issues:

Mobile settings don't survive a reboot

Following command in terminal should fix this problem.

Code:

devel-su chown radio:radio /var/lib/ofono

UI freeze

This bug still occurs sometimes, mostly after ending a phone call. Most of the time a three finger touch get's the UI working again, but sometimes more fingers are needed. Once i had to do a eight finger touch to unfreeze the UI :D

Time can not be set manually in Settings

Fixed by reinstalling timed-qt5

Code:

devel-su zypper in --force timed-qt5

Hopefuly fixed issues:

GPS not working in 2.1.1.x build
Fixed in 2.1.1.26-build-0.2 image

Install the following rpm to get GPS working again.

MTP not working

Fixed in 2.1.1.26 image, do not flash this kernel on this image!
Flash this kernel with recovery and mtp should work.

Device suspend not working
Fixed in 2.1.0.10-build0.3 image

Seems lile i forgot to enable the script service. Plaese run

Code:

devel-su systemctl enable bt-sleep-monitor.timer

devel-su systemctl start bt-sleep-monitor.timer

in terminal.

Store not working
Fixed in 2.1.0.10-build0.2 image
Enter the following in terminal:

Code:

ssu dr home

ssu dr adaptation0

zypper refresh

Thanks mosen!

Enough for now, happy testing.

Sources are available at GitHub.

mautz

2017-05-10 11:02

Re: SFOS Nexus5 CM13 alpha

Custom kernel

http://www.mediafire.com/file/h27qp1...ld-01.zip/file

CPU Governors /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

ConservativeX
ElementalX
Lionheart
SmartMax
Wheatley
Intelliactive
Intellidemand
ZZMoove

CPU Hotplug governors

AutoSMP /sys/kernel/autosmp
BluPlug /sys/module/blu_plug/parameters
Intelliplug ???
MSM Hotplug /sys/module/msm_hotplug
ZZMoove Hotplug /sys/devices/system/cpu/cpufreq/zzmoove
Alucard /sys/kernel/alucard_hotplug
zen_decision /sys/kernel/zen_decision

FileSystem schedulers /sys/block/mmcblk0/queue/scheduler

TripnDroid
fifo
vio
zen
fiops
vr

Other things

Faux Sound Control /sys/kernel/sound_control_3
KCAL control /sys/devices/platform/kcal_ctrl.0/
Backlight mod /sys/block/mmcblk0/queue/scheduler
Powersuspend
Updated graphics drivers(Devfreq instead of KGSL) /sys/class/kgsl/kgsl-3d0/devfreq/
CAF patches and some backports
Neon crypto support
LZ4 image support
kexec-hardboot
Dynamic FSync
MSM thermal instead of original Qcom thermal /sys/kernel/msm_thermal/conf
Fast charge /sys/kernel/fast_charge
Undervolt /sys/devices/system/cpu/cpu0/cpufreq/Uv_mV_Table
Overclock /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Underclock /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

and some more...

BluesLee

2017-05-10 11:10

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Reserved.

Issue when taking photos (unsolved)
I observe a bigger lag between the release time with sound feedback (?) and the point in time when the photo is taken. Sound feedback should be at the point in time when the photo is taken.

Install keyboard prediction package from official Jolla device as root

Code:

zypper in --download-only --force jolla-xt9

Package can be found somewhere here

Code:

cd /var/cache/zypper/RPMS/xt9/

Installation:

Code:

pkcon install jolla-xt9*

Setting date manually (see post #1)

Code:

devel-su date -s HH:MM::SS

juiceme

2017-05-10 11:33

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1527857)

CyanogenMod 13 patched: http://www.mediafire.com/file/970u3n...13_release.zip

How is this different from the regular cm13? or is it just a storage place for the normal hammerhead cm13 release since https://download.cyanogenmod.org/ seems to be (permanently??) down?

Can you please share your .ks as I always build my own releases..?

mautz

2017-05-10 11:56

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by juiceme (Post 1527861)

It is the cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J2-hammerhead.zip with a modified updater script.
I removed the verifying part of the updater-script to get rid of some error messages when installing it via a custom recovery with a not up to date android.

I can post the ks file when i pushed all needed files to OBS.

mosen

2017-05-10 14:47

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

First observation, i had to manually fix Jolla Store by doing

Code:

ssu dr home

ssu dr adaptation0

zypper refresh

All Apps where shown but non was downloadable before.

mautz

2017-05-10 14:53

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mosen (Post 1527869)

First observation, i had to manually fix Jolla Store by doing

Code:

ssu dr home

ssu dr adaptation0

zypper refresh

All Apps where shown but non was downloadable before.

Another thing i forgot to mention in my first post, thanks, i'll add this.

tealc

2017-05-10 16:56

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

I want to install sudo from mer-tools but get authentication error:

Quote:

ssu ar mer-tools
pkcon refresh
Refreshing cache
Waiting in queue
Waiting for authentication
Fatal error: Failed to obtain authentication.

Quote:

devel-su
pkcon refresh
Refreshing cache
Waiting in queue
Waiting for authentication
Waiting in queue
Starting
Refreshing software list
Fatal error: Authentication failed (is SSU set up correctly?)

Quote:

ssu lr
WARNING: ssu.ini does not seem to be writable. Setting values might not work.
Enabled repositories (global):
- adaptation0 ... https://store-repository.jolla.com/r...rhead/armv7hl/
- apps ... https://releases.jolla.com/jolla-apps/2.1.0.10/armv7hl/
- hotfixes ... https://releases.jolla.com/releases/...fixes/armv7hl/
- jolla ... https://releases.jolla.com/releases/...jolla/armv7hl/

Enabled repositories (user):
- adaptation0 ... https://store-repository.jolla.com/r...rhead/armv7hl/
- mer-tools ... https://releases.jolla.com/releases/...v7hl/packages/
- store ... https://store-repository.jolla.com/h...rsion=2.1.0.10

Disabled repositories (global, might be overridden by user config):

Disabled repositories (user):
- home ... https://download.jollamobile.com/hom...atest_armv7hl/

Edit:
zypper refresh seems to work instead

mautz

2017-05-10 20:48

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

@tealc

Disabling adaptation0 repo should have also worked.

I'll upload a new image which doesn't has the adaptation0 issue.

m4r0v3r

2017-05-10 22:06

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

good job :)

deprecated

2017-05-10 23:12

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Holy crap! This is amazing news!

Edit: btw mautz, does this include any of the custom kernel stuff from your CM12 releases? e.g., undervolting/underclocking, governor selection etc?

mautz

2017-05-11 05:18

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by deprecated (Post 1527905)

Holy crap! This is amazing news!

Edit: btw mautz, does this include any of the custom kernel stuff from your CM12 releases? e.g., undervolting/underclocking, governor selection etc?

No, i didn't made a custom kernel for cm13 yet ;)

mautz

2017-05-11 05:20

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Released sailfishos-hammerhead-release-2.1.0.10-new-build_0.2, which fixes the repo issues of the previous image. Still no clue why timed-qt5 isn't able to change the clock via gui.

BluesLee

2017-05-11 06:06

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1527909)

Released sailfishos-hammerhead-release-2.1.0.10-new-build_0.2, which fixes the repo issues of the previous image. Still no clue why timed-qt5 isn't able to change the clock via gui.

Hello mautz,

how did you fix this repo issue permanently? Currently, every time i use zypper or pkcon i have to drop adaptation0. Thanks.

Blues

p.s.

Solution: See first post of mautz.

BluesLee

2017-05-11 06:08

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Did anyone fixed the missing word prediction? The package jolla-xt9 ot any xt9 package seems not be provided by any repo.

icyphox

2017-05-11 07:56

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

So I tried installing AlienDalvik, and followed the general procedure (at least, what it was for 2.0.x), but I get this:

Code:

# systemctl start aliendalvik

Job for aliendalvik.service failed. See 'systemctl status aliendalvik.service' and 'journalctl -xn' for details.

Here's the output of

Code:

systemctl status aliendalvik

Code:

 aliendalvik.service - Myriad Alien Dalvik

   Loaded: loaded (/lib/systemd/system/aliendalvik.service; enabled)

   Active: failed (Result: start-limit) since Thu 2017-05-11 13:31:51 IST; 2min 28s ago

  Process: 29162 ExecStopPost=/system/script/alien_ui_pid_reporter.sh stop (code=exited, status=0/SUCCESS)

  Process: 29150 ExecStopPost=/system/script/alien_notification_cleaner.sh (code=exited, status=0/SUCCESS)

  Process: 27520 ExecStart=/system/script/start_alien.sh (code=exited, status=0/SUCCESS)

  Process: 27517 ExecStartPre=/system/script/alien_start_guard.sh (code=exited, status=0/SUCCESS)

 Main PID: 27520 (code=exited, status=0/SUCCESS)



May 11 13:31:50 Sailfish systemd[1]: Failed to start Myriad Alien Dalvik.

May 11 13:31:50 Sailfish systemd[1]: Unit aliendalvik.service entered failed state.

May 11 13:31:51 Sailfish systemd[1]: aliendalvik.service holdoff time over, sche...t.

May 11 13:31:51 Sailfish systemd[1]: aliendalvik.service start request repeated ...t.

May 11 13:31:51 Sailfish systemd[1]: Unit aliendalvik.service entered failed state.

Hint: Some lines were ellipsized, use -l to show in full.

What's the issue here?

mautz

2017-05-11 08:54

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

@BluesLee

The xt9 packages are only available on official Jolla devices. So you need to download them with a jolaa device and copy them to the N5, the same applies to the Jolla Maps application.

@icyphox

I never got aliendalvik work with cm13. Maybe it's because of different kernels. Just be patient, nh1402 is trying to get get anbox working on sailfish :-)

mosen

2017-05-11 12:59

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Please, someone give some kind of management summary of the differences between sfdroid and anbox. I lost track...
Will docker make it easier to deploy anbox on different sfos devices?
How about sfos system integration? (android -> GPS, BT, sailfish -> Notifcations, contacts, etc.)

I heard Jolla hired a new android related guy.
Could they be working on replacing soon to be dead horse Alien Dalvik for good?
Sorry for starting rumors and shifting OT but it bothers me a lot.

nh1402

2017-05-11 16:55

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mosen (Post 1527931)

sfdroid modified the cm base that Sailfish was flashed on top of, in order for it to boot into it (so it runs in parallel), and render inside Sailfish. Device specific modifications were needed to each base of each device, in order for it to work. sfdroid was also limited to whatever the base the device used for the port, CM10.1, 11 or 12.1.

Anbox uses a separate emulator image which runs inside an LXC container, and renders to the host Linux OS. Because a seperate image is used, and that it's an emulator image, the same image can be booted to with different devices without modification (which was needed with sfdroid), so any modifications (ie. to get rendering, sensors, network stuff working) will apply to all devices.

mosen

2017-05-11 19:14

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Very cool!
Does that also mean it is possible to switch the emulator image when a new android is released and keep the work done to adapt anbox to sailfish?

nh1402

2017-05-11 19:21

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mosen (Post 1527943)

Very cool!
Does that also mean it is possible to switch the emulator image when a new android is released and keep the work done to adapt anbox to sailfish?

yes (but there is a very good chance you'll lose app data/installed apps when you do), and depends what has changed between versions.

tealc

2017-05-12 19:52

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

I have problems with Settings->Mobile network->Data access point->Access point name being reset to an incorrect value when restarting the handset resulting in mobile data stops working. Not sure if this problem is specific for nexus 5.

Besides this it seems to work well except for a little bit more battery drain than older versions (using default kernel).

mautz

2017-05-13 02:57

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by tealc (Post 1527964)

Could you please instal SystemDataScope from openpos and tell me if your device goes to sleep?

tealc

2017-05-13 19:26

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1527969)

Could you please instal SystemDataScope from openpos and tell me if your device goes to sleep?

It looks like it sleeps almost all the time. The battery level is down to 50% now after 12 hours of usage (not much usage) so there is not a massive drain but more than before.

BluesLee

2017-05-14 06:02

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by tealc (Post 1527986)

It looks like it sleeps almost all the time. The battery level is down to 50% now after 12 hours of usage (not much usage) so there is not a massive drain but more than before.

This does not hold for me?! I only get positve suspend time using

Code:

mcetool --get-suspend-stats

when turning off bluetooth completly as root with

Code:

systemctl stop hciattach.service

Unfortunately its not of any use as you cant activate it directly without a reboot. Otherwise a workaround with turn on / off bluetooth would be possible this way

Code:

systemctl start hciattach.service

Job for hciattach.service failed. See 'systemctl status hciattach.service' and 'journal

ctl -xn' for details.

tealc

2017-05-14 08:06

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by BluesLee (Post 1527991)

This does not hold for me?! I only get positve suspend time using

Code:

mcetool --get-suspend-stats

when turning off bluetooth completly
...

I guess I must have misinterpreted the graphs from SystemDataScope then because I get the following:

Code:

mcetool --get-suspend-stats

uptime:       145337.916 

suspend_time: 0.000

I have bluetooth disabled in the settings, but based on your explanation I assume bluetooth still can prevent the CPU from sleeping?

m4r0v3r

2017-05-14 10:59

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1527909)

Released sailfishos-hammerhead-release-2.1.0.10-new-build_0.2, which fixes the repo issues of the previous image. Still no clue why timed-qt5 isn't able to change the clock via gui.

thats happened to someone else porting to another device, akhil_surabhi but not to my bullhead port so not quite sure whats causing it. i did disable something that was conflicting with dsme in my .rc file so maybe thats it? but i doubt it

rinigus

2017-05-14 11:20

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by tealc (Post 1527992)

I guess I must have misinterpreted the graphs from SystemDataScope then because I get the following:

Code:

mcetool --get-suspend-stats

uptime:       145337.916 

suspend_time: 0.000

To be sure that its not a bug in SystemDataScope: did you follow "CPU sleep, %" graph? When device sleeps, it should get towards 90-100% (Average, Min, Max, Last shown below the graph). In your case, its probably 0%

tealc

2017-05-14 12:13

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by rinigus (Post 1527998)

I didn't find the CPU sleep graph until after running the mcetool command, but assumed that is was the "sleeping" value in Processes graph mautz was asking for. After stopping the hciattach service it does go to sleep and the CPU sleep graph went from 0% to 90-100%.

I have added a systemctl script which stops the hciattach service so hopefully I will get better battery time from now on.

mautz

2017-05-14 17:30

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Could you please post /dev/shm/bt-sleep-monitor.log ?

And the check if the service bt-sleep-monitor.service and bt-sleep-monitor.timer are running?

tealc

2017-05-14 18:26

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1528004)

Could you please post /dev/shm/bt-sleep-monitor.log ?

And the check if the service bt-sleep-monitor.service and bt-sleep-monitor.timer are running?

I don't have the /dev/shm/bt-sleep-monitor.log which may be related to the service/timer being inactive.

Code:

-bash-3.2$ systemctl status bt-sleep-monitor.service

bt-sleep-monitor.service - Start Minimecs bt-sleep-monitor script at startup

   Loaded: loaded (/lib/systemd/system/bt-sleep-monitor.service; static)

   Active: inactive (dead)



-bash-3.2$ systemctl status bt-sleep-monitor.timer  

bt-sleep-monitor.timer - Delay start of minimecs bt-sleep-monitor script to avoid getting wrong bluetooth value on startup

   Loaded: loaded (/lib/systemd/system/bt-sleep-monitor.timer; disabled)

   Active: inactive (dead)

mautz

2017-05-14 18:32

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

@tealc

could you please post the output of

Code:

ls -lha /proc/bluetooth/sleep/lpm

and check if the file bt-sleep-monitor.sh is present in /usr/bin?

tealc

2017-05-14 19:29

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1528006)

@tealc

could you please post the output of

Code:

ls -lha /proc/bluetooth/sleep/lpm

and check if the file bt-sleep-monitor.sh is present in /usr/bin?

Code:

-bash-3.2$ ls -l /usr/bin/bt-sleep-monitor.sh 

-rwxr-xr-x 1 root root 5560 May 10 09:42 /usr/bin/bt-sleep-monitor.sh

Code:

-bash-3.2$ ls -lha /proc/bluetooth/sleep/lpm

-rw-rw---- 1 bluetooth net_bt_stack 0 May 14 21:27 /proc/bluetooth/sleep/lpm

mautz

2017-05-14 19:41

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Seems like the script doesn't start at boot. Could you try starting it manually with devel-su systemctl start bt-sleep-monitor.timer or devel-su /usr/bin/bt-sleep-monitor.sh?

UPDATE: Seems like i forgot to enable the script service.

Code:

devel-su systemctl enable bt-sleep-monitor.timer

devel-su systemctl start bt-sleep-monitor.timer

should solve the problem.

I will correct this in the next build.

UPDATE: Thanks BluesLee for pointing out the missing systemctl command.

tealc

2017-05-15 15:25

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

That worked better! Now the /dev/shm/bt-sleep-monitor.log file indicates that bluetooth is disabled. Thanks!

BluesLee

2017-05-16 02:07

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1528008)

Code:

devel-su enable bt-sleep-monitor.timer

devel-su start bt-sleep-monitor.timer

should solve the problem.

I will correct this in the next build.

Typo. For those who are not familiar with those commands, it should be

Code:

devel-su systemctl enable bt-sleep-monitor.timer 

devel-su systemctl start bt-sleep-monitor.timer

maximilian1st

2017-05-16 06:22

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Just to be sure, this does not help with the bad Bluetooth hands free problem right?

mautz

2017-05-16 06:57

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by maximilian1st (Post 1528050)

Just to be sure, this does not help with the bad Bluetooth hands free problem right?

Nope, that's another problem.

BluesLee

2017-05-16 12:56

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Very good battery life behaviour so far with cm13 + sfos 2.1 + using workaround regarding bluetooth sleep issue, great.

mautz

2017-05-16 13:17

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Uploaded build 0.3 which fixes the bt sleep issue.

All times are GMT. The time now is 12:53.

Page 1 of 17

Next >

Last »

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8