Sailfish OS on Sony Xperia X (community build) - Page 19 - maemo.org

Active Topics

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (9)
to SailfishOS by biketool - 4 hrs, 12 mins ago
[Announce] coderus unrestricted system-ui (297)
to MeeGo / Harmattan by nieldk - 6 days, 9 hrs ago
more...

Page 19 of 36

Thread Tools

meemorph	2017-10-05 , 15:18
Posts: 204 \| Thanked: 443 times \| Joined on Jul 2012 @ Germany - Potsdam	#181

Originally Posted by jakibaki

Look at the top-answer of this post. Works perfectly on Xperia X too

Thank you, very nice hint. I can confirm that it works. I added 4GB to rootfs (btw: I have /home/nemo on the sd card).

what I did on my XperiaX (recovery shell):

Code:

lvm
lvm> lvscan
  ACTIVE            '/dev/sailfish/root' [2.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [18.25 GiB] inherit
lvm> exit

resize2fs /dev/sailfish/home 11G

lvm
lvm> lvresize -L -4096M /dev/sailfish/home
lvm> lvresize -l +100%FREE /dev/sailfish/root
lvm> lvscan
  ACTIVE            '/dev/sailfish/root' [6.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [14.25 GiB] inherit
lvm> exit

resize2fs /dev/sailfish/home
resize2fs /dev/sailfish/root
exit

Last edited by meemorph; 2017-10-06 at 15:04.

Quote & Reply |

The Following 12 Users Say Thank You to meemorph For This Useful Post:
acrux, carmenluci, deprecated, hhbbap, J4ZZ, jakibaki, juiceme, lal, maximilian1st, objectifnul, olf, speactra

meemorph	2017-10-06 , 15:01
Posts: 204 \| Thanked: 443 times \| Joined on Jul 2012 @ Germany - Potsdam	#182

Yesterday I put a sim card in the xperia first time. It was on for e very short time, because by mistake I deactivated it at settings->SIM_cards. Now it is gone forever.

reboot: not PIN asking, no gsm indicator at the top right, settings->SIM_cards says no SIM card inserted.

If I start the csd tool, the phone asks for the PIN. And on the second test csd shows PASS. But at settings->SIM_cards still no card inserted.

Any hints? Don't try the same!

Quote & Reply |

The Following 6 Users Say Thank You to meemorph For This Useful Post:
jakibaki, juiceme, lal, maximilian1st, pasko, santeira

taixzo	2017-10-06 , 16:21
Posts: 959 \| Thanked: 3,427 times \| Joined on Apr 2012	#183

I figured out why the wifi and cell signals weren't working. Apparently if the phone is in airplane mode in Android, and you flash Sailfish, the radios are completely disabled in SFOS. I flashed back to Android, disabled airplane mode, flashed back to Sailfish and the wifi works. Camera and lockscreen are also working now; no idea why airplane mode would affect those.

__________________
Saera: A Siri clone for the N900, N9(50) and Jolla

Follow me on Twitter: twitter.com/taixzo

Quote & Reply |

The Following 16 Users Say Thank You to taixzo For This Useful Post:
ajalkane, deprecated, edgar2, ezameht, jakibaki, jenix, Jordi, juiceme, lal, lantern, maximilian1st, meloferz, pasko, pycage, santeira, uber

oenone	2017-10-07 , 04:31
Posts: 84 \| Thanked: 146 times \| Joined on Feb 2015	#184

Originally Posted by meemorph

Thank you, very nice hint. I can confirm that it works. I added 4GB to rootfs (btw: I have /home/nemo on the sd card).

what I did on my XperiaX (recovery shell):

Code:

lvm
lvm> lvscan
  ACTIVE            '/dev/sailfish/root' [2.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [18.25 GiB] inherit
lvm> exit

resize2fs /dev/sailfish/home 11G

lvm
lvm> lvresize -L -4096M /dev/sailfish/home
lvm> lvresize -l +100%FREE /dev/sailfish/root
lvm> lvscan
  ACTIVE            '/dev/sailfish/root' [6.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [14.25 GiB] inherit
lvm> exit

resize2fs /dev/sailfish/home
resize2fs /dev/sailfish/root
exit

Thank you for the instructions.

I get this when running lvscan:

Code:

lvm> lvscan
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
  ACTIVE            '/dev/sailfish/root' [2.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [47.38 GiB] inherit

The Input/output errors, are they caused by anything in particular, and is there anything I can or should do about them?

And then. . .

Code:

resize2fs /dev/sailfish/home 11G
resize2fs 1.43.1 (08-Jun-2016)
Filesystem at /dev/sailfish/home is mounted on /home; on-line resizing required
resize2fs: On-line shrinking not supported

What is on-line resizing and how do I get past this issue of it not being supported?

Decided to carry on:

Code:

lvm> lvresize -L -4096M /dev/sailfish/home
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  WARNING: Reducing active and open logical volume to 43.38 GiB
  THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce home? [y/n]: y
  Size of logical volume sailfish/home changed from 47.38 GiB (12128 extents) to 43.38 GiB (11104 extents).
  Logical volume home successfully resized
lvm> lvresize -l +100%FREE /dev/sailfish/root
  Size of logical volume sailfish/root changed from 2.44 GiB (625 extents) to 6.44 GiB (1649 extents).
  Logical volume root successfully resized
lvm> lvscan
  ACTIVE            '/dev/sailfish/root' [6.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [43.38 GiB] inherit

Seems to have worked, or am I missing something?

EDIT: Yep, missing something. Device is stuck in a bootloop. This is the F5122.

Last edited by oenone; 2017-10-07 at 04:58.

Quote & Reply |

The Following 3 Users Say Thank You to oenone For This Useful Post:
juiceme, maximilian1st, meemorph

lantern	2017-10-07 , 05:42
Posts: 367 \| Thanked: 1,442 times \| Joined on Feb 2015	#185

oenone
lvscan on my F5122 output same errors on the same blocks on live system.

PS Make sure you resize in recovery.

Quote & Reply |

The Following 3 Users Say Thank You to lantern For This Useful Post:
juiceme, maximilian1st, meemorph

jenix	2017-10-07 , 05:53
Posts: 74 \| Thanked: 355 times \| Joined on Aug 2017	#186

Originally Posted by oenone

Thank you for the instructions.

I get this when running lvscan:

Code:

lvm> lvscan
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
  ACTIVE            '/dev/sailfish/root' [2.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [47.38 GiB] inherit

The Input/output errors, are they caused by anything in particular, and is there anything I can or should do about them?

Please don't just copy-paste any commands when you don't understand what they are doing. Especially don't just continue when they result in unexpected output, like the errors here!

And then. . .
Code:
resize2fs /dev/sailfish/home 11G
resize2fs 1.43.1 (08-Jun-2016)
Filesystem at /dev/sailfish/home is mounted on /home; on-line resizing required
resize2fs: On-line shrinking not supported
What is on-line resizing and how do I get past this issue of it not being supported?

Well, the device tells you in plaintext what's the problem:
"Filesystem at /dev/sailfish/home is mounted on /home; on-line resizing required"
Did you carried this out in recovery mode? Did you do something prior to this that left the partitions mounted?

Decided to carry on:

Code:

lvm> lvresize -L -4096M /dev/sailfish/home
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  WARNING: Reducing active and open logical volume to 43.38 GiB
  THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce home? [y/n]: y
  Size of logical volume sailfish/home changed from 47.38 GiB (12128 extents) to 43.38 GiB (11104 extents).
  Logical volume home successfully resized
lvm> lvresize -l +100%FREE /dev/sailfish/root
  Size of logical volume sailfish/root changed from 2.44 GiB (625 extents) to 6.44 GiB (1649 extents).
  Logical volume root successfully resized
lvm> lvscan
  ACTIVE            '/dev/sailfish/root' [6.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [43.38 GiB] inherit

Seems to have worked, or am I missing something?

EDIT: Yep, missing something. Device is stuck in a bootloop. This is the F5122.

You have obviously missed a lot of I/O errors which are never a good sign. And which probably is the reason you destroyed the LVMs.
Flash again and then make sure that the partitions are not mounted before trying to resize them.

Quote & Reply |

The Following 6 Users Say Thank You to jenix For This Useful Post:
brunelli, chris_bavaria, juiceme, lal, maximilian1st, meemorph

jakibaki	2017-10-07 , 06:25
Posts: 120 \| Thanked: 843 times \| Joined on Jul 2015 @ Berlin, Germany	#187

Originally Posted by oenone

Thank you for the instructions.

I get this when running lvscan:

Code:

lvm> lvscan
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
  ACTIVE            '/dev/sailfish/root' [2.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [47.38 GiB] inherit

The Input/output errors, are they caused by anything in particular, and is there anything I can or should do about them?

And then. . .

Code:

resize2fs /dev/sailfish/home 11G
resize2fs 1.43.1 (08-Jun-2016)
Filesystem at /dev/sailfish/home is mounted on /home; on-line resizing required
resize2fs: On-line shrinking not supported

What is on-line resizing and how do I get past this issue of it not being supported?

Decided to carry on:

Code:

lvm> lvresize -L -4096M /dev/sailfish/home
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  WARNING: Reducing active and open logical volume to 43.38 GiB
  THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce home? [y/n]: y
  Size of logical volume sailfish/home changed from 47.38 GiB (12128 extents) to 43.38 GiB (11104 extents).
  Logical volume home successfully resized
lvm> lvresize -l +100%FREE /dev/sailfish/root
  Size of logical volume sailfish/root changed from 2.44 GiB (625 extents) to 6.44 GiB (1649 extents).
  Logical volume root successfully resized
lvm> lvscan
  ACTIVE            '/dev/sailfish/root' [6.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [43.38 GiB] inherit

Seems to have worked, or am I missing something?

EDIT: Yep, missing something. Device is stuck in a bootloop. This is the F5122.

It looks like /home is mounted. Is it possible that you didn't do this from recovery?

Quote & Reply |

The Following 3 Users Say Thank You to jakibaki For This Useful Post:
juiceme, maximilian1st, meemorph

m4r0v3r	2017-10-07 , 17:24
Posts: 1,746 \| Thanked: 1,832 times \| Joined on Dec 2010	#188

switching between different ambiences should be working fine if you upgrade to 2.1.2.3

Quote & Reply |

The Following 3 Users Say Thank You to m4r0v3r For This Useful Post:
juiceme, maximilian1st, meloferz

deprecated	2017-10-07 , 17:31
Posts: 300 \| Thanked: 962 times \| Joined on Jun 2010 @ USA	#189

Originally Posted by m4r0v3r

switching between different ambiences should be working fine if you upgrade to 2.1.2.3

Switching between ambiences work, yes, but there are several of the baked-in ones that don't work at all. I replaced them all with random ambiences I created, and they switch just fine. I guess the baked-in ones are broken somehow.

__________________
Sony Xperia XA2 Ultra SFOS 3 + Sony Xperia X SFOS 3, Nokia N810

Quote & Reply |

The Following 2 Users Say Thank You to deprecated For This Useful Post:
juiceme, maximilian1st

m4r0v3r	2017-10-07 , 18:37
Posts: 1,746 \| Thanked: 1,832 times \| Joined on Dec 2010	#190

Originally Posted by deprecated

Switching between ambiences work, yes, but there are several of the baked-in ones that don't work at all. I replaced them all with random ambiences I created, and they switch just fine. I guess the baked-in ones are broken somehow.

which ones in particular?