Power consumption is getting normal if i disable cellular internet. Yes 3G and LTE were working fine.
wake_lock output:
dsme_iphb_wakeup mce_cpu_keepalive mce_display_on
Last edited:
[beta] [SFOS] SailfishOS 2.1.3.7 for cancro
- Thread starter saidinesh5
- Start date
wake_lock output:
dsme_iphb_wakeup mce_cpu_keepalive mce_display_on
Anyway, I won't back to android or anything looks like an os. I don't care any of them, sfos on mi4 is great and thank you very much for making it possible.
Btw. these wakelocks are to be checked when you expect the device to be in sleep mode.. and not when your device is connected to the the PC/charger or something.
You probably need to write some script / little app to keep track of these wakelocks. Will definitely have to optimize this.
http://ruleoftech.com/2014/debugging-sailfish-os-application-power-consumption is a useful read on this topic btw.
Right now my real life is a little hectic till this 14th. After that, I will be back to this project - with SFDroid (Android app support) being the priority. There is a 2.1.0 version coming up quite soon too.
Hi,
thank you for porting sailfish OS.
I use it since 3 weeks 27/7.
( Before I used the BQ Aquaris E5 HD Ubuntu edition, but they stop the development, so I choose the Mi3 with sailfish OS )
I love it. Sometimes when it is switched out, it start from alone. And rebooting sometimes take long. Once my bluetooth was on, and the screen freezes.
But I do not have more issues.
I hope you continue the porting . Cant wait for 2.1.0 version and SFDroid .
Greetings
thank you for porting sailfish OS.
I use it since 3 weeks 27/7.
( Before I used the BQ Aquaris E5 HD Ubuntu edition, but they stop the development, so I choose the Mi3 with sailfish OS )
I love it. Sometimes when it is switched out, it start from alone. And rebooting sometimes take long. Once my bluetooth was on, and the screen freezes.
But I do not have more issues.
I hope you continue the porting . Cant wait for 2.1.0 version and SFDroid .
Greetings
Last edited:
Thanks a lot for your support!
The screen freezing issue should be considerably minimized with the next version, if not completely fixed. Could you add this file to your device and reboot it to see if you still have the ocassional screen issues? https://github.com/CancroSailors/droid-config-cancro/commit/3ada749c98e98edcbb1f8e9ddfdb29fd9ce277b5 .
The rebooting taking longer than usual is a boot loop that's happening because some partitions not mounting in time. I will have to look into this bit again though. Could be a systemd issue too.
And yep, I will have to look into 2.1.0 porting earlier than I thought as I have been told there were some issues with the droplet browser on it.
Hi @saidinesh5
How proceed your good work on sailfish for cancel devices?
Thanks for your good work!!!
How proceed your good work on sailfish for cancel devices?
Thanks for your good work!!!
Hi,
I have compiled a 2.1 Early Access version for cancro 2 days ago. Right now testing it out and fixing bugs - So if all goes well, the 2.1 version should be available to general public once Sailfish OS 2.1 is released for general public. (We are not allowed to make a release until Jolla releases 2.1 to general public).
As for SFDroid, my packaging script ( https://gist.github.com/saidinesh5/3262c31c88776445544c8b2804ee02df ) for SFDroid was used to get a basic version up and running on Xiaomi Redmi 2. But I am working on a different approach - to get SFDroid working inside a chroot. I think it will take a little longer to get it up and running this way, but it should let us start/stop sfdroid on demand, and also let SFDroid not mess up your phone's data partition. (So far I have corrupted my phone's data a bunch of times when trying to get SFdroid up and running!).
P.S Right now I would really appreciate if the Android devs in here to help me debug the issues with SFdroid - where zygote is crashing with: F/art ( 9925): art/runtime/jni_internal.cc:769] JNI FatalError called: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...
@saidinesh5 thank you! Good news! I would have the copy and paste function that SF 2.1 have! 
Last edited:
THX for the great work porting sfos to the cancro.
I installed the CM12.1 without problems and it is running well on my mi4.
But when i try to install sailfishos i got these output:
Deleting the assert-line in the updater-script doesn't change anything.
What is with this partition issue on the mi, is that the problem?
How can i check if the partitions are correct?
Thanks in advance.
I installed the CM12.1 without problems and it is running well on my mi4.
But when i try to install sailfishos i got these output:
Code:
Device check succeeded, mounting filesystems ...
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
Copying filesystem archive ...
Copying installation script ...
Running installation script ...
Failed to extract filesystem!
E: Error in /data/media/sailfishos-cancro-release-2.0.5.6-alpha2.zip
(Status 7)
installation aborted.
E:replace_device_node: could not delete node!
E:replace_device_node: could not delete node!
E:replace_device_node: could not delete node!What is with this partition issue on the mi, is that the problem?
How can i check if the partitions are correct?
Thanks in advance.
The /sdcard of android should also be available in /data/media/0
Code:
$ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2017-03-11 23:40 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-03-11 23:40 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-03-11 23:40 bk1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-03-11 23:40 bk2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-03-11 23:40 bk3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2017-03-11 23:40 bk4 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2017-03-11 23:40 bk5 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2017-03-11 23:40 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2017-03-11 23:40 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2017-03-11 23:40 dbi -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-03-11 23:40 fsc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-03-11 23:40 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2017-03-11 23:40 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-03-11 23:40 misc -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-03-11 23:40 modem -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2017-03-11 23:40 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-03-11 23:40 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-03-11 23:40 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2017-03-11 23:40 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2017-03-11 23:40 rpm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-03-11 23:40 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-03-11 23:40 ssd -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-03-11 23:40 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2017-03-11 23:40 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-03-11 23:40 userdata -> /dev/block/mmcblk0p25THX for your fast reply.
It looks like the same:
Any idea?
It looks like the same:
Code:
./adb shell ls -l /dev/block/platform/msm_sdcc.1/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx 1 root root 20 Mar 16 17:23 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Mar 16 17:23 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Mar 16 17:23 bk1 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Mar 16 17:23 bk2 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Mar 16 17:23 bk3 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Mar 16 17:23 bk4 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Mar 16 17:23 bk5 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Mar 16 17:23 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Mar 16 17:23 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Mar 16 17:23 dbi -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Mar 16 17:23 fsc -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Mar 16 17:23 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Mar 16 17:23 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Mar 16 17:23 misc -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Mar 16 17:23 modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Mar 16 17:23 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Mar 16 17:23 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Mar 16 17:23 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Mar 16 17:23 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Mar 16 17:23 rpm -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Mar 16 17:23 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Mar 16 17:23 ssd -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Mar 16 17:23 system -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Mar 16 17:23 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Mar 16 17:23 userdata -> /dev/block/mmcblk0p25How much free space do you have?
Are these "errors"/"warnings" okay to ignore? Could you confirm by manually trying to mount /data in recovery and see if it is actually your data partition?
Code:
#mount /dev/block/platform/msm_sdcc.1/by-name/userdata /dataNot sure what's causing the issue: "E:replace_device_node: could not delete node!",
P.S If too impatient to wrestle with TWRP, you can
1) manually extract the rootfs in tar.bz2 inside the zip to /data/.stowaways/sailfishos/ (as shown in the updater-unpack.sh inside the zip)
2) manually flash the hybris-boot.img to your boot partition.
Code:
#fastboot flash boot hybris-boot.imgManually mounting in recovery mode does the same:
The userdata refers to /dev/block/mmcblk0p25 and when I look into /dev/block:
There is no mmcblk0p25!
But I have a mounting from /dev/userdata_moved to /data_root
Inside the /data_root it looks like this:
Is this the place i should copy sfos?
Code:
./adb shell mount /dev/block/platform/msm_sdcc.1/by-name/userdata /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: No such file or directory
Code:
./adb shell ls -l /dev/block
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- 1 root root 7, 0 Mar 21 20:04 loop0
brw------- 1 root root 7, 1 Mar 21 20:04 loop1
brw------- 1 root root 7, 2 Mar 21 20:04 loop2
brw------- 1 root root 7, 3 Mar 21 20:04 loop3
brw------- 1 root root 7, 4 Mar 21 20:04 loop4
brw------- 1 root root 7, 5 Mar 21 20:04 loop5
brw------- 1 root root 7, 6 Mar 21 20:04 loop6
brw------- 1 root root 7, 7 Mar 21 20:04 loop7
brw------- 1 root root 179, 0 Mar 21 20:04 mmcblk0
brw------- 1 root root 179, 1 Mar 21 20:04 mmcblk0p1
brw------- 1 root root 179, 10 Mar 21 20:04 mmcblk0p10
brw------- 1 root root 179, 11 Mar 21 20:04 mmcblk0p11
brw-rw---- 1 system system 179, 12 Mar 21 20:04 mmcblk0p12
brw-rw---- 1 system system 179, 13 Mar 21 20:04 mmcblk0p13
brw------- 1 root root 179, 14 Mar 21 20:04 mmcblk0p14
brw------- 1 root root 179, 15 Mar 21 20:04 mmcblk0p15
brw------- 1 root root 179, 16 Mar 21 20:04 mmcblk0p16
brw------- 1 root root 179, 17 Mar 21 20:04 mmcblk0p17
brw------- 1 root root 179, 18 Mar 21 20:04 mmcblk0p18
brw------- 1 root root 179, 19 Mar 21 20:04 mmcblk0p19
brw------- 1 root root 179, 2 Mar 21 20:04 mmcblk0p2
brw------- 1 root root 179, 20 Mar 21 20:04 mmcblk0p20
brw------- 1 root root 179, 21 Mar 21 20:04 mmcblk0p21
brw------- 1 root root 179, 22 Mar 21 20:04 mmcblk0p22
brw------- 1 root root 179, 23 Mar 21 20:04 mmcblk0p23
brw------- 1 root root 179, 24 Mar 21 20:04 mmcblk0p24
brw------- 1 root root 179, 3 Mar 21 20:04 mmcblk0p3
brw------- 1 root root 179, 4 Mar 21 20:04 mmcblk0p4
brw------- 1 root root 179, 5 Mar 21 20:04 mmcblk0p5
brw------- 1 root root 179, 6 Mar 21 20:04 mmcblk0p6
brw------- 1 root root 179, 7 Mar 21 20:04 mmcblk0p7
brw------- 1 root root 179, 8 Mar 21 20:04 mmcblk0p8
brw------- 1 root root 179, 9 Mar 21 20:04 mmcblk0p9
brw------- 1 root root 179, 32 Mar 21 20:04 mmcblk0rpmb
drwxr-xr-x 3 root root 60 Mar 21 20:04 platform
brw------- 1 root root 1, 0 Mar 21 20:04 ram0
brw------- 1 root root 1, 1 Mar 21 20:04 ram1
brw------- 1 root root 1, 10 Mar 21 20:04 ram10
brw------- 1 root root 1, 11 Mar 21 20:04 ram11
brw------- 1 root root 1, 12 Mar 21 20:04 ram12
brw------- 1 root root 1, 13 Mar 21 20:04 ram13
brw------- 1 root root 1, 14 Mar 21 20:04 ram14
brw------- 1 root root 1, 15 Mar 21 20:04 ram15
brw------- 1 root root 1, 2 Mar 21 20:04 ram2
brw------- 1 root root 1, 3 Mar 21 20:04 ram3
brw------- 1 root root 1, 4 Mar 21 20:04 ram4
brw------- 1 root root 1, 5 Mar 21 20:04 ram5
brw------- 1 root root 1, 6 Mar 21 20:04 ram6
brw------- 1 root root 1, 7 Mar 21 20:04 ram7
brw------- 1 root root 1, 8 Mar 21 20:04 ram8
brw------- 1 root root 1, 9 Mar 21 20:04 ram9
brw------- 1 root root 253, 0 Mar 21 20:04 zram0
brw------- 1 root root 253, 1 Mar 21 20:04 zram1
brw------- 1 root root 253, 2 Mar 21 20:04 zram2
brw------- 1 root root 253, 3 Mar 21 20:04 zram3But I have a mounting from /dev/userdata_moved to /data_root
Code:
./adb shell mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=931552k,nr_inodes=175218,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=931552k,nr_inodes=175218)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=931552k,nr_inodes=175218,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,size=931552k,nr_inodes=175218,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,size=931552k,nr_inodes=175218,mode=775,gid=1000)
/dev/userdata_moved on /data_root type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)
Code:
./adb shell ls -l /data_root
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwx------ 2 root root 4096 Mar 8 16:03 adb
drwxrwx--x 2 system system 4096 Mar 8 16:03 app
drwx------ 2 root root 4096 Mar 8 16:03 app-asec
drwxrwx--x 2 system system 4096 Mar 8 16:03 app-lib
drwxrwx--x 2 system system 4096 Mar 8 16:03 app-private
drwxrwx--- 2 media audio 4096 Mar 8 16:03 audio
drwx------ 4 system system 4096 Mar 8 16:05 backup
lrwxrwxrwx 1 root root 45 Mar 8 16:03 bugreports -> /data/data/com.android.shell/files/bugreports
srwxrwx--- 1 camera camera 0 Mar 17 17:11 cam_socket1
srwxrwx--- 1 camera camera 0 Mar 17 17:11 cam_socket2
drwxrwx--x 3 system system 4096 Mar 8 16:03 connectivity
drwxrwx--x 4 root root 4096 Mar 8 16:03 dalvik-cache
drwxrwx--x 82 system system 4096 Mar 8 16:04 data
drwxr-x--- 2 root log 4096 Mar 8 16:03 dontpanic
drwxrwx--- 2 drm drm 4096 Mar 8 16:03 drm
-rw-rw---- 1 camera camera 1780 Mar 8 16:08 fdAlbum
drwxrwx--x 2 system system 4096 Mar 8 16:03 fota
drwxrwx--- 2 system wifi 4096 Mar 8 16:03 hostapd
drwxr-x--x 3 root root 4096 Mar 8 16:03 local
drwxrwx--- 2 root root 4096 Mar 8 16:03 lost+found
drwxrwx--- 6 media_rw media_rw 4096 Mar 13 20:05 media
drwxrwx--- 2 mediadrm mediadrm 4096 Mar 8 16:03 mediadrm
drwxrwx--t 28 system misc 4096 Mar 8 16:03 misc
drwxrwx--- 3 nfc nfc 4096 Mar 8 16:03 nfc
drwx------ 2 root root 4096 Mar 17 17:11 property
drwxrwx--x 2 system system 4096 Mar 8 16:03 resource-cache
drwx--x--x 2 system system 4096 Mar 8 16:03 security
drwxr-xr-x 2 system system 4096 Mar 8 16:03 shared
drwxrwxr-x 20 system system 4096 Mar 21 19:41 system
drwx------ 2 system system 4096 Mar 8 23:03 time
drwxrwx--x 6 system system 4096 Mar 8 16:07 tombstones
drwx--x--x 2 system system 4096 Mar 8 16:03 userIt looks like this is the right path. Out of curiosity, do you have a multirom based TWRP or something? Not sure what's hiding the /dev/block/mmcblk0p25.
First back up your boot.img and then extract Sailfish to this path, and then flash hybris-boot.img
You can use https://www.androidfilehost.com/?fid=457095661767125252 image for Sailfish. It has telnet enabled at the boot time, to help you debug things. You can access telnet by : telnet 192.168.2.15 2323 or telnet 192.168.2.15 23 . The phone should give your PC an IP address in the 192.168.2.X subnet. If not, feel free to give your PC a static IP.
Good Luck!
Thank for your excellent job，I flashed this rom and now the Chinese input cannot work，would you fix this issue on next version？
Hi,
I think the Chinesse input methods were Jolla proprietary packages that are not available for the ports.
Could you try out Dolphin keyboard instead?
I think we have to sit down and port the QtVirtual Keyboard or something else for proper chinese input and even T9 input.
Cheers,
D
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone