Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Sailfish OS on Sony Xperia X Compact (community build)

    Reply
    Page 20 of 21 | Prev | 10   18     19   20   21   | Next
    Manatus | # 191 | 2019-12-12, 11:55 | Report

    SFOS 3.2.1.19 updated with OTA, no issues.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to Manatus For This Useful Post:
    juiceme

     
    aspergerguy | # 192 | 2019-12-26, 18:55 | Report

    Just to mention no problems using g7 patcher with latest Sailfish_OS-Jolla-3.2.1.20-f5121-0.2.1.27.zip

    HTML Code:
    I: Creating an empty root image
    1821+0 records in
    1821+0 records out
    1909456896 bytes (1.9 GB, 1.8 GiB) copied, 1.26998 s, 1.5 GB/s
    mke2fs 1.43.4 (31-Jan-2017)
    Discarding device blocks: done                            
    Creating filesystem with 466176 4k blocks and 116640 inodes
    Filesystem UUID: 8a9da342-263a-40ee-9483-daae54cc36df
    Superblock backups stored on blocks: 
    	32768, 98304, 163840, 229376, 294912
    
    Allocating group tables: done                            
    Writing inode tables: done                            
    Creating journal (8192 blocks): done
    Writing superblocks and filesystem accounting information: done 
    
    I: Syncing back the patched tree
    I: Repacking
    /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.1.20-f5121-0.2.1.27/patcher-tmp/work /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.1.20-f5121-0.2.1.27
    0+0 records in
    0+0 records out
    0 bytes copied, 0.000848465 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: 24286/116640 files (0.1% non-contiguous), 264455/466176 blocks
    We got ourselves root blocks _ 398302 _
    after maths size _ 1631444992 _
      Rounding up size to full physical extent 1.52 GiB
      Logical volume "root" created.
      1 logical volume(s) in volume group "sailfish" now active
    398302+0 records in
    398302+0 records out
    1631444992 bytes (1.6 GB, 1.5 GiB) copied, 12.8736 s, 127 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 (7.2% non-contiguous), 13309/16222 blocks
    We got ourselves home size _ 13314 _
      Rounding up size to full physical extent 56.00 MiB
      Logical volume "home" created.
      2 logical volume(s) in volume group "sailfish" now active
    13314+0 records in
    13314+0 records out
    54534144 bytes (55 MB, 52 MiB) copied, 0.320027 s, 170 MB/s
      0 logical volume(s) in volume group "sailfish" now active
    1+0 records in
    1+0 records out
    1 byte copied, 0.000580506 s, 1.7 kB/s
    mke2fs 1.43.4 (31-Jan-2017)
    Discarding device blocks: done                            
    Creating filesystem with 341796 4k blocks and 85536 inodes
    Filesystem UUID: 00435d11-5b24-4102-b290-ab612c05807c
    Superblock backups stored on blocks: 
    	32768, 98304, 163840, 229376, 294912
    
    Allocating group tables: done                            
    Writing inode tables: done                            
    Creating journal (8192 blocks): done
    Writing superblocks and filesystem accounting information: done 
    
    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
    fimage.img: 11/85536 files (0.0% non-contiguous), 14574/341796 blocks
    resize2fs 1.43.4 (31-Jan-2017)
    The filesystem is already 341796 (4k) blocks long.  Nothing to do!
    
    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
    fimage.img: 16/85536 files (6.3% non-contiguous), 130960/341796 blocks
    resize2fs 1.43.4 (31-Jan-2017)
    Resizing the filesystem on fimage.img to 197441 (4k) blocks.
    The filesystem on fimage.img is now 197441 (4k) blocks long.
    
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/ (stored 0%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/sailfish.img001 (deflated 55%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/hybris-recovery.img (deflated 2%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/fastboot.img (deflated 3%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/AdbWinUsbApi.dll (deflated 49%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/fastboot.exe (deflated 67%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/fimage.img001 (deflated 2%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/Jolla-3.2.1.20-f5121-armv7hl.urls (deflated 92%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/flash-on-windows.bat (deflated 63%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/hybris-boot.img (deflated 2%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/md5.lst (deflated 35%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/flashing-README.txt (deflated 59%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/AdbWinApi.dll (deflated 49%)
      adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/flash.sh (deflated 57%)
    /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.1.20-f5121-0.2.1.27
    I: Done! Enjoy!
    I: Cleaning up...
    Connection to 127.0.0.1 closed.
    iMac:sailfishx-patcher-f5321 adrian$ 

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by aspergerguy; 2019-12-26 at 19:15. Reason: Correction
    The Following User Says Thank You to aspergerguy For This Useful Post:
    juiceme

     
    willi.liebig | # 193 | 2020-02-04, 15:36 | Report

    hi, I have the same trouble as post 106 ... after cloning of the git repository (git clone https://github.com/g7/sailfishx-patcher-f5321.git) the folder "droid-config-f5121" is still empty, even when I manually download the patcher. Is this a bug or how can I manage to get all files downloaded?
    Will

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to willi.liebig For This Useful Post:
    juiceme

     
    wolke | # 194 | 2020-02-04, 15:40 | Report

    its a submodule. from the readme:
    git clone https://github.com/g7/sailfishx-patcher-f5321.git
    cd sailfishx-patcher-f5321
    git submodule init
    git submodule update

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to wolke For This Useful Post:
    juiceme, olf

     
    willi.liebig | # 195 | 2020-02-04, 19:17 | Report

    hi, mh, there are still some errors. Is there a possiblity to download the patched zip-file anywhere?

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to willi.liebig For This Useful Post:
    juiceme

     
    Manatus | # 196 | 2020-04-04, 08:53 | Report

    SFOS 3.3.0.14 updated without issues on g7's hack image.
    Also enabling the encryption worked. I had all kinds of issues in restoring existing data from the GUI based backup after the encryption, so prepare well with external backups if you do this.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to Manatus For This Useful Post:
    juiceme

     
    Manatus | # 197 | 2020-04-04, 12:36 | Report

    Scratch that what I said above. Either after the upgrade _or_ after doing the encryption, leds and sound stopped working. So upgrade only if you dare.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to Manatus For This Useful Post:
    juiceme

     
    eugenio | # 198 | 2020-04-04, 12:45 | Report

    Originally Posted by Manatus View Post
    Scratch that what I said above. Either after the upgrade _or_ after doing the encryption, leds and sound stopped working. So upgrade only if you dare.
    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

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by eugenio; 2020-04-04 at 13:21.
    The Following 2 Users Say Thank You to eugenio For This Useful Post:
    juiceme, Manatus

     
    Manatus | # 199 | 2020-04-04, 17:37 | Report

    Thanks Eugenio! I was bit too fast...

    I got the issue fixed by doing a factory reset, and upgrading from there back to latest. After enabling encryption again I didn't have issues anymore.

    I tried 'version --dup' just before resulting to factory reset, but all packages were up to date.

    In addition to sound I also had issues with the LED. Csd tests showed that the led still worked, just it did not get triggered in the events with text messages, calls etc.
    I also noticed also that any pull menus that normally would have sound to them didn't trigger haptic feedback (haptic was fine with virtual keyboards). Both of these issues may be connected to pulseaudio and order in which SFOS expects things to happen.
    So I think your suggestion would have worked.

    Well, at least the factory reset has now been tested and working!

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by Manatus; 2020-04-04 at 17:54.
    The Following User Says Thank You to Manatus For This Useful Post:
    juiceme

     
    wolke | # 200 | 2020-04-29, 05:57 | Report

    hmm, cant create a g7 image for rokua

    keep getting:
    error: Failed dependencies: libreadline.so.8 is needed by zypper-1.14.6+git4-1.5.1.jolla.armv7hl

    trying to messing with the inner chroot patch file and not having much luck

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to wolke For This Useful Post:
    juiceme

     
    Page 20 of 21 | Prev | 10   18     19   20   21   | Next
vBulletin® Version 3.8.8
Normal Logout