Sailfish OS (officially) on Sony Xperia devices - Page 107 - maemo.org

lantern | # 1061 | 2017-09-17, 16:35 | Report

Ok, thanks to mal from #sailfish-porters we now have fully working dual-sim F5122

add these 3 lines to /default.prop

Originally Posted by

persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1

and these lines to the end of /etc/ofono/ril_subscription.conf

Originally Posted by

[ril_1]
socket=/dev/socket/rild2

and install jolla-settings-networking-multisim

Code:

nemo@Sailfish ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
rootfs                2.4G  1.1G  1.3G  46% /
/dev/sailfish/root    2.4G  1.1G  1.3G  46% /
/dev/sailfish/home     47G   25M   47G   1% /home
devtmpfs              1.3G   72K  1.3G   1% /dev
tmpfs                 1.4G  244K  1.4G   1% /dev/shm
tmpfs                 1.4G  9.4M  1.4G   1% /run
tmpfs                 1.4G     0  1.4G   0% /sys/fs/cgroup
tmpfs                 1.4G  4.0K  1.4G   1% /tmp
tmpfs                 1.4G     0  1.4G   0% /mnt
/dev/mmcblk0p13        12M  3.7M  7.8M  32% /dsp
/dev/mmcblk0p25        28M  204K   27M   1% /persist
/dev/mmcblk0p24       223M  167M   52M  77% /system/vendor
/dev/mmcblk0p3         84M   62M   23M  73% /firmware
/dev/mmcblk0p52       1.3G  488M  813M  38% /fimage
tmpfs                 280M  632K  280M   1% /run/user/100000

Last edited by lantern; 2017-09-17 at 16:59.

The Following 54 Users Say Thank You to lantern For This Useful Post:
243kof, ajalkane, alfmar, Amboss, aspergerguy, brunelli, Bundyo, chris_bavaria, corvinux, DA5, edgar2, eekkelund, ejjoman, elastic, explit, HtheB, imaginaryenemy, J4ZZ, Jordi, juiceme, klinglerware, lal, lkravovicz, Macros, mariusmssj, MartinK, maximilian1st, meemorph, MegaVolnutt, meloferz, mikecomputing, MINKIN2, mosen, mrsellout, n-mi, pacman, peterleinchen, rcolistete, rinigus, Robissimo, rogger888, rrunner64, santeira, sbock, seiichiro0185, sfbg, skvark, ste-phan, Sthocs, theonelaw, TMavica, Transcend, wallinniklas, wicozani

mariusmssj | # 1062 | 2017-09-17, 17:18 | Report

Originally Posted by lantern View Post

Ok, thanks to mal from #sailfish-porters we now have fully working dual-sim F5122

add these 3 lines to /default.prop

and these lines to the end of /etc/ofono/ril_subscription.conf

and install jolla-settings-networking-multisim

Code:

nemo@Sailfish ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
rootfs                2.4G  1.1G  1.3G  46% /
/dev/sailfish/root    2.4G  1.1G  1.3G  46% /
/dev/sailfish/home     47G   25M   47G   1% /home
devtmpfs              1.3G   72K  1.3G   1% /dev
tmpfs                 1.4G  244K  1.4G   1% /dev/shm
tmpfs                 1.4G  9.4M  1.4G   1% /run
tmpfs                 1.4G     0  1.4G   0% /sys/fs/cgroup
tmpfs                 1.4G  4.0K  1.4G   1% /tmp
tmpfs                 1.4G     0  1.4G   0% /mnt
/dev/mmcblk0p13        12M  3.7M  7.8M  32% /dsp
/dev/mmcblk0p25        28M  204K   27M   1% /persist
/dev/mmcblk0p24       223M  167M   52M  77% /system/vendor
/dev/mmcblk0p3         84M   62M   23M  73% /firmware
/dev/mmcblk0p52       1.3G  488M  813M  38% /fimage
tmpfs                 280M  632K  280M   1% /run/user/100000

The dual-sim F5122 allows to either have 2 sim cards or 1 sim and 1 Micro SD card. Will sailfishOS be able to handle this?

The Following 8 Users Say Thank You to mariusmssj For This Useful Post:
Amboss, explit, hhbbap, imaginaryenemy, juiceme, mosen, santeira, willi6868

alfmar | # 1063 | 2017-09-17, 19:50 | Report

51+ gibibytes seem quite less than 64 gigabytes.

Where are the remaining ~7 Gib?

The Following 2 Users Say Thank You to alfmar For This Useful Post:
Amboss, juiceme

lantern | # 1064 | 2017-09-17, 20:13 | Report

Originally Posted by alfmar View Post

51+ gibibytes seem quite less than 64 gigabytes.

Where are the remaining ~7 Gib?

wasted at /fimage

Code:

[nemo@Sailfish ~]$ lsblk
NAME              MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0rpmb       179:32   0    4M  0 disk 
mmcblk0           179:0    0 58.2G  0 disk 
|-mmcblk0p1       179:1    0    2M  0 part 
|-mmcblk0p2       179:2    0   16M  0 part 
|-mmcblk0p3       179:3    0   84M  0 part /firmware
|-mmcblk0p4       179:4    0    8K  0 part 
|-mmcblk0p5       179:5    0  512K  0 part 
|-mmcblk0p6       179:6    0  512K  0 part 
|-mmcblk0p7       179:7    0  512K  0 part 
|-mmcblk0p8       179:8    0  512K  0 part 
|-mmcblk0p9       179:9    0    2M  0 part 
|-mmcblk0p10      179:10   0    2M  0 part 
|-mmcblk0p11      179:11   0  512K  0 part 
|-mmcblk0p12      179:12   0  512K  0 part 
|-mmcblk0p13      179:13   0   16M  0 part /dsp
|-mmcblk0p14      179:14   0  1.5M  0 part 
|-mmcblk0p15      179:15   0  1.5M  0 part 
|-mmcblk0p16      179:16   0   32K  0 part 
|-mmcblk0p17      179:17   0  1.5M  0 part 
|-mmcblk0p18      179:18   0   16K  0 part 
|-mmcblk0p19      179:19   0   11M  0 part 
|-mmcblk0p20      179:20   0    1M  0 part 
|-mmcblk0p21      179:21   0    1M  0 part 
|-mmcblk0p22      179:22   0   64M  0 part 
|-mmcblk0p23      179:23   0    1M  0 part 
|-mmcblk0p24      179:24   0  256M  0 part /system/vendor
|-mmcblk0p25      179:25   0   32M  0 part /persist
|-mmcblk0p26      179:26   0  512K  0 part 
|-mmcblk0p27      179:27   0  512K  0 part 
|-mmcblk0p28      179:28   0  400M  0 part 
|-mmcblk0p29      179:29   0   32K  0 part 
|-mmcblk0p30      179:30   0  512K  0 part 
|-mmcblk0p31      179:31   0  256K  0 part 
|-mmcblk0p32      259:0    0    4M  0 part 
|-mmcblk0p33      259:1    0  256K  0 part 
|-mmcblk0p34      259:2    0  256K  0 part 
|-mmcblk0p35      259:3    0  256K  0 part 
|-mmcblk0p36      259:4    0  256K  0 part 
|-mmcblk0p37      259:5    0  256K  0 part 
|-mmcblk0p38      259:6    0  256K  0 part 
|-mmcblk0p39      259:7    0    8K  0 part 
|-mmcblk0p40      259:8    0   40M  0 part 
|-mmcblk0p41      259:9    0   40M  0 part 
|-mmcblk0p42      259:10   0   64M  0 part 
|-mmcblk0p43      259:11   0   32M  0 part 
|-mmcblk0p44      259:12   0   10M  0 part 
|-mmcblk0p45      259:13   0   16M  0 part 
|-mmcblk0p46      259:14   0   20M  0 part 
|-mmcblk0p47      259:15   0  100K  0 part 
|-mmcblk0p48      259:16   0  100K  0 part 
|-mmcblk0p49      259:17   0  512K  0 part 
|-mmcblk0p50      259:18   0  512K  0 part 
|-mmcblk0p51      259:19   0 49.8G  0 part 
| |-sailfish-root 253:0    0  2.5G  0 lvm  /
| `-sailfish-home 253:1    0 47.4G  0 lvm  /home
`-mmcblk0p52      259:20   0  7.3G  0 part /fimage

$ du -chs /fimage/
488M    /fimage/

Last edited by lantern; 2017-09-17 at 22:01.

The Following 5 Users Say Thank You to lantern For This Useful Post:
Amboss, juiceme, meemorph, mosen, taixzo

Zeta | # 1065 | 2017-09-17, 21:43 | Report

Originally Posted by mariusmssj View Post

The dual-sim F5122 allows to either have 2 sim cards or 1 sim and 1 Micro SD card. Will sailfishOS be able to handle this?

If it is like on other phones, there are two separate contacts rows for each type, one on middle, and one on side, and you can even have the 2 sims cards at the same time as the micro SD, if you are ready to glue them together like in this hack :
https://hackaday.com/2017/04/14/dual...m-slot-phones/ (title is misleading, as explained in the [update] part of the article)

The Following 8 Users Say Thank You to Zeta For This Useful Post:
explit, Feathers McGraw, J4ZZ, juiceme, mosen, peterleinchen, santeira, theonelaw

theonelaw | # 1066 | 2017-09-18, 02:54 | Report

Originally Posted by Zeta View Post

If it is like on other phones, there are two separate contacts rows for each type, one on middle, and one on side, and you can even have the 2 sims cards at the same time as the micro SD, if you are ready to glue them together like in this hack :
https://hackaday.com/2017/04/14/dual...m-slot-phones/ (title is misleading, as explained in the [update] part of the article)

Sounds like the 5122 is definitely the one to get, now !

Do you need to choose the makes very carefully ?

My first guess is that a lousy μSD card might kill a SIM card
(bad experiences with other devices heat buildup under SIM cards)

...or vice-versa...

The Following 3 Users Say Thank You to theonelaw For This Useful Post:
Amboss, Feathers McGraw, juiceme

deprecated | # 1067 | 2017-09-18, 04:07 | Report

I already bought a 5121, but that's OK. One SIM and an SD is fine by me.

I dunno when I'll get access to buy Sailfish X (I'm in the US), but my 5121 will be here Wednesday.

The Following 4 Users Say Thank You to deprecated For This Useful Post:
Amboss, juiceme, meloferz, santeira

MartinK | # 1068 | 2017-09-18, 15:19 | Report

Originally Posted by lantern View Post

wasted at /fimage

Code:

[nemo@Sailfish ~]$ lsblk
NAME              MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0rpmb       179:32   0    4M  0 disk 
mmcblk0           179:0    0 58.2G  0 disk 
|-mmcblk0p1       179:1    0    2M  0 part 
|-mmcblk0p2       179:2    0   16M  0 part 
|-mmcblk0p3       179:3    0   84M  0 part /firmware
|-mmcblk0p4       179:4    0    8K  0 part 
|-mmcblk0p5       179:5    0  512K  0 part 
|-mmcblk0p6       179:6    0  512K  0 part 
|-mmcblk0p7       179:7    0  512K  0 part 
|-mmcblk0p8       179:8    0  512K  0 part 
|-mmcblk0p9       179:9    0    2M  0 part 
|-mmcblk0p10      179:10   0    2M  0 part 
|-mmcblk0p11      179:11   0  512K  0 part 
|-mmcblk0p12      179:12   0  512K  0 part 
|-mmcblk0p13      179:13   0   16M  0 part /dsp
|-mmcblk0p14      179:14   0  1.5M  0 part 
|-mmcblk0p15      179:15   0  1.5M  0 part 
|-mmcblk0p16      179:16   0   32K  0 part 
|-mmcblk0p17      179:17   0  1.5M  0 part 
|-mmcblk0p18      179:18   0   16K  0 part 
|-mmcblk0p19      179:19   0   11M  0 part 
|-mmcblk0p20      179:20   0    1M  0 part 
|-mmcblk0p21      179:21   0    1M  0 part 
|-mmcblk0p22      179:22   0   64M  0 part 
|-mmcblk0p23      179:23   0    1M  0 part 
|-mmcblk0p24      179:24   0  256M  0 part /system/vendor
|-mmcblk0p25      179:25   0   32M  0 part /persist
|-mmcblk0p26      179:26   0  512K  0 part 
|-mmcblk0p27      179:27   0  512K  0 part 
|-mmcblk0p28      179:28   0  400M  0 part 
|-mmcblk0p29      179:29   0   32K  0 part 
|-mmcblk0p30      179:30   0  512K  0 part 
|-mmcblk0p31      179:31   0  256K  0 part 
|-mmcblk0p32      259:0    0    4M  0 part 
|-mmcblk0p33      259:1    0  256K  0 part 
|-mmcblk0p34      259:2    0  256K  0 part 
|-mmcblk0p35      259:3    0  256K  0 part 
|-mmcblk0p36      259:4    0  256K  0 part 
|-mmcblk0p37      259:5    0  256K  0 part 
|-mmcblk0p38      259:6    0  256K  0 part 
|-mmcblk0p39      259:7    0    8K  0 part 
|-mmcblk0p40      259:8    0   40M  0 part 
|-mmcblk0p41      259:9    0   40M  0 part 
|-mmcblk0p42      259:10   0   64M  0 part 
|-mmcblk0p43      259:11   0   32M  0 part 
|-mmcblk0p44      259:12   0   10M  0 part 
|-mmcblk0p45      259:13   0   16M  0 part 
|-mmcblk0p46      259:14   0   20M  0 part 
|-mmcblk0p47      259:15   0  100K  0 part 
|-mmcblk0p48      259:16   0  100K  0 part 
|-mmcblk0p49      259:17   0  512K  0 part 
|-mmcblk0p50      259:18   0  512K  0 part 
|-mmcblk0p51      259:19   0 49.8G  0 part 
| |-sailfish-root 253:0    0  2.5G  0 lvm  /
| `-sailfish-home 253:1    0 47.4G  0 lvm  /home
`-mmcblk0p52      259:20   0  7.3G  0 part /fimage

$ du -chs /fimage/
488M    /fimage/

Isn't that where the firmware recovery images are stored ? Since switching from btrfs to LVM+EXT4 Sailfish OS is no longer using snapshots for factory reset (which turned to be a really bad idea, specially as you can't really update the snapshots). Instead, there is a separate partition where rootfs & home recovery images are stored.

When user initiates a factory reset, the system will drop the current LVM + EXT4 layout, recreate it and then fill the empty volumes with content from the recovery images.

Like this factory reset is not dependent on the health of a complex CoW filesystem and the recovery images can be easily updated by just updating the recovery images sitting on a separate partition. A slight downside is that additional space is occupied by the partition holding the recovery images, but I think the certainly outweigh this.

The Following 9 Users Say Thank You to MartinK For This Useful Post:
Amboss, corvinux, explit, Feathers McGraw, hhbbap, imaginaryenemy, juiceme, meemorph, mosen

alfmar | # 1069 | 2017-09-18, 15:41 | Report

Did anyone yet build some counter to SF X events (Sep 27 and Oct 11)?

I would like to download from Play Store an Android counter app to "SFX" which will self-destroy (and possibly wreak havoc) on October 11...

The Following 2 Users Say Thank You to alfmar For This Useful Post:
Amboss, juiceme

mikecomputing | # 1070 | 2017-09-18, 16:12 | Report

Originally Posted by m4r0v3r View Post

isnt there a fix for it anyways?

Not AFAIK :/ Or yes there is a DRMfix but I must be sure I can rollback to locked phone. I am afraid bankid and similar must have crap applications stop work on unlocked Android phone.

So if I only can be ssure thats not the case I would not mind play with try some AOSP android version first and later on try play with SFOS+HADK stuff...

Because I really HATE android and all its pre installed bloatware.

Indeed I miss my fairphone wit SFOS except it's camera and battery time... Camera, Battery and Display is way better on XZs compared to Jolla1 and FP2.

Btw. If there is some from sweden using bankid on an unlocked X or XZs let me know. (Also with SFOS when released of course)

The Following 7 Users Say Thank You to mikecomputing For This Useful Post:
Amboss, explit, hhbbap, imaginaryenemy, juiceme, mosen, theonelaw