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

Active Topics

The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 2 hrs ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 15 hrs ago
n770 youtube video (0)
to General by nmdv - 5 days, 14 hrs ago
more...

Page 21 of 22

« First

< Prev

Next >

Thread Tools

wolke	2020-04-29 , 06:29
Posts: 986 \| Thanked: 1,526 times \| Joined on Jul 2010	#201

previous problem had an easy solution (just install readline rpm).

now ive got another problem. inner patch seems to apply correctly in chroot, but repacking the image files fails.

(note that the zip file is built, but is only half the size of the source zip file)

Code:

I: Syncing back the patched tree
I: Repacking
/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25
0+0 records in
0+0 records out
0 bytes copied, 0.000164125 s, 0.0 kB/s
  Physical volume "/dev/loop0" successfully created.
  Volume group "sailfish" successfully created
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/loop1: 25063/116640 files (0.1% non-contiguous), 264442/466176 blocks
We got ourselves root blocks _ 398289 _
after maths size _ 1631391744 _
  Rounding up size to full physical extent 1.52 GiB
  Logical volume "root" created.
  1 logical volume(s) in volume group "sailfish" now active
398289+0 records in
398289+0 records out
1631391744 bytes (1.6 GB, 1.5 GiB) copied, 7.78859 s, 209 MB/s
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
home: 83/7328 files (3.6% non-contiguous), 13285/16198 blocks
We got ourselves home size _ 13290 _
  Rounding up size to full physical extent 52.00 MiB
  Logical volume "home" created.
  2 logical volume(s) in volume group "sailfish" now active
13290+0 records in
13290+0 records out
54435840 bytes (54 MB, 52 MiB) copied, 0.163591 s, 333 MB/s
  0 logical volume(s) in volume group "sailfish" now active
1+0 records in
1+0 records out
1 byte copied, 0.00015447 s, 6.5 kB/s
Usage: mkfs.ext4 [-c|-l filename] [-b block-size] [-C cluster-size]
	[-i bytes-per-inode] [-I inode-size] [-J journal-options]
	[-G flex-group-size] [-N number-of-inodes] [-d root-directory]
	[-m reserved-blocks-percentage] [-o creator-os]
	[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
	[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
	[-t fs-type] [-T usage-type ] [-U UUID] [-e errors_behavior][-z undo_file]
	[-jnqvDFSV] device [blocks-count]
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open fimage.img

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

resize2fs 1.43.4 (31-Jan-2017)
resize2fs: Bad magic number in super-block while trying to open fimage.img
Couldn't find valid filesystem superblock.
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
umount: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work/tmp.Y3VaMPjpIX: not mounted
rmdir: failed to remove '/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work/tmp.Y3VaMPjpIX': Directory not empty
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open fimage.img

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

resize2fs 1.43.4 (31-Jan-2017)
resize2fs: Bad magic number in super-block while trying to open fimage.img
Couldn't find valid filesystem superblock.

__________________
~ teleshoes ~

Quote & Reply |

The Following User Says Thank You to wolke For This Useful Post:
juiceme

wolke	2020-04-29 , 19:20
Posts: 986 \| Thanked: 1,526 times \| Joined on Jul 2010	#202

ok fixed it, see https://github.com/g7/sailfishx-patcher-f5321/pull/14

__________________
~ teleshoes ~

Quote & Reply |

The Following User Says Thank You to wolke For This Useful Post:
juiceme

N77	2020-05-27 , 04:25
Posts: 13 \| Thanked: 40 times \| Joined on May 2020	#203

Hey guys I need some help if possible.

I am not a software coder but I managed to follow g7 guide from here:
https://github.com/g7/sailfishx-patcher-f5321
and install Sailfish on the X compact.

Now, I was looking at what Vknecht posted on:
http://merproject.org/logs/%23sailfi...05-02.log.html
respectively:

https://build.merproject.org/project...qualcomm:f5121

also a pie based port which works better, but only boots correctly sometimes:
https://build.merproject.org/project...:hw:sony:loire

because of:
https://github.com/sonyxperiadev/dev...6c494ecad6875e

I would like to try any of these ports but I need some guidance like step by step sequence of actions. I have Ubuntu machine which I think is needed (Windows 7 as well). Any help would be appreciated.

Quote & Reply |

The Following 3 Users Say Thank You to N77 For This Useful Post:
juiceme, santeira, Sheigorath

Sheigorath	2020-09-21 , 20:02
Posts: 1 \| Thanked: 2 times \| Joined on Mar 2020	#204

Originally Posted by N77

Hey guys I need some help if possible.

I am not a software coder but I managed to follow g7 guide from here:
https://github.com/g7/sailfishx-patcher-f5321
and install Sailfish on the X compact.

Now, I was looking at what Vknecht posted on:
http://merproject.org/logs/%23sailfi...05-02.log.html
respectively:

https://build.merproject.org/project...qualcomm:f5121

also a pie based port which works better, but only boots correctly sometimes:
https://build.merproject.org/project...:hw:sony:loire

because of:
https://github.com/sonyxperiadev/dev...6c494ecad6875e

I would like to try any of these ports but I need some guidance like step by step sequence of actions. I have Ubuntu machine which I think is needed (Windows 7 as well). Any help would be appreciated.

Is there any news about new ports for Compact?

Quote & Reply |

The Following 2 Users Say Thank You to Sheigorath For This Useful Post:
juiceme, wolke

Manatus	2020-10-01 , 12:06
Posts: 334 \| Thanked: 616 times \| Joined on Sep 2010	#205

I updated Eugenio's (g7) port to 3.4.0.22 on X Compact. No issues spotted.

Quote & Reply |

The Following 3 Users Say Thank You to Manatus For This Useful Post:
juiceme, Sheigorath, wolke

smatkovi	2020-10-21 , 19:50
Posts: 169 \| Thanked: 194 times \| Joined on Apr 2012 @ Austria	#206

this should be the solution, at least it helped on my mothers xperia x compact https://together.jolla.com/question/...post-id-199698

Originally Posted by eugenio

What's the output of
Code:
systemctl --user status pulseaudio
Have you tried running the upgrade again via command line?
Code:
devel-su
ssu re 3.3.0.14
version --dup
FWIW my X Compact works fine, even though the upgrade failed mid-way (but it doesn't seem related to the patch).
I also have encryption enabled, but since 3.2.0.

========================
EDIT: Now that I remember, I had to mask pulseaudio's system wide service after enabling encryption back then. Pulseaudio is normally started in the user session, but after encryption is enabled is started system-wide so that it's possible to route audio when taking emergency calls from the encryption unlock screen (I guess).

Not sure what is wrong, I thought it was due to encryption being a work in progress on 3.2.0 so I haven't complained But it seems to be an issue on 3.3.0 too, then.

You can mask pulseaudio using this command:
Code:
systemctl mask pulseaudio

Quote & Reply |

The Following User Says Thank You to smatkovi For This Useful Post:
juiceme

aspergerguy	2021-05-31 , 13:21
Posts: 807 \| Thanked: 1,589 times \| Joined on Aug 2014	#207

I updated Eugenio's (g7) port to 4.1.0.24 on Xperia X Compact. Have not encrypted as a backup device and yet to check notification LED and audio.

Attached Images

Quote & Reply |

The Following User Says Thank You to aspergerguy For This Useful Post:
juiceme

maximilian1st	2021-05-31 , 18:36
Posts: 127 \| Thanked: 203 times \| Joined on Sep 2010 @ Switzerland	#208

I have the Xperia X Compact as a daily driver since quite some time and did the patch thing before version 3.4. Since then, I just update OTA and it still works the same as it did with the first flashed patched version.

I don't care about the android layer anymore, not really using it. Only for Ankidroid ;-p But I would miss the text prediction as presage has no French version or Dutch. And honestly I read the howto make it yourself and I still don't know where to start

Funny thing is the Xperia 10 II is about the same width as the X Compact but way too tall. Small phones are not trendy these days.

https://www.phonearena.com/phones/si...es/10217,11367

I remember Casio or Panasonic had a 2G credit card size phone at some point. thought that was a very cool device at the time.

Smartwatches will probably be the future of phones with a mini tablet as second device.

That was way off topic, sorry ;-p

Quote & Reply |

The Following User Says Thank You to maximilian1st For This Useful Post:
juiceme

aspergerguy	2021-06-01 , 06:30
Posts: 807 \| Thanked: 1,589 times \| Joined on Aug 2014	#209

Originally Posted by maximilian1st

Funny thing is the Xperia 10 II is about the same width as the X Compact but way too tall. Small phones are not trendy these days.

Although running community port by rinigus the XZ2 Compact is very similar in size to Xperia X Compact.

Attached Images

Last edited by aspergerguy; 2021-06-01 at 06:40. Reason: Addition

Quote & Reply |

The Following 2 Users Say Thank You to aspergerguy For This Useful Post:
juiceme, wolke

aspergerguy	2022-03-17 , 19:24
Posts: 807 \| Thanked: 1,589 times \| Joined on Aug 2014	#210

Originally Posted by maximilian1st

I have the Xperia X Compact as a daily driver since quite some time and did the patch thing before version 3.4. Since then, I just update OTA and it still works the same as it did with the first flashed patched version.

And honestly I read the howto make it yourself and I still don't know where to start

Just to say that with g7 patch still updates to 4.2.0.21 (using terminal and sfos-upgrade) and can still build latest Sailfish_OS-patched-for-f5321-4.3.0.15-f5321-0.2.3.9 with one caveat. Whilst I am essentially a Mac user OSX Monterey doesn't sit happy with VirtualBox without a bit of tinkering, but got there eventually.

Attached Images