Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. c4pp4
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 54
    • Best 12
    • Groups 0

    c4pp4

    @c4pp4

    22
    Reputation
    11
    Profile views
    54
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Location Prague, Czechia

    c4pp4 Follow

    Best posts made by c4pp4

    • [HowTo] Using Anbox manually to reduce battery drain

      I. Disable Anbox via anbox-tool:

      anbox-tool disable
      

      or make it disabled manually:

      rm /home/phablet/anbox-data/.enable
      stop anbox-session
      sudo stop anbox-container
      

      or alternatively configure Upstart to ignore the start on / stop on stanzas:

      sudo mount -o remount,rw /
      echo "manual" | sudo tee /etc/init/anbox-container.override
      echo "manual" | sudo tee /usr/share/upstart/sessions/anbox-session.override
      sudo sync
      sudo mount -o remount,ro /
      stop anbox-session
      sudo stop anbox-container
      

      II. Remove Anbox icons:

      rm /home/phablet/.local/share/applications/anbox-*
      

      III. Create start script:

      #!/bin/bash
      sudo start anbox-container
      start anbox-session
      

      and stop script:

      #!/bin/bash
      stop anbox-session
      sudo stop anbox-container
      rm /home/phablet/.local/share/applications/anbox-*
      

      IV. Start or stop Anbox:

      bash <nameofscript>
      
      posted in Support
      c4pp4
      c4pp4
    • RE: One method to encrypt /home/phablet

      @ernest said in One method to encrypt /home/phablet:

      Seems that lightdm doesn't restart with the latest OTA. Any tips ?

      Hi, I'm using the following script (tested on OTA-15 and OTA-16 devel):

      #!/bin/bash
      if ! dpkg-query -l cryptsetup | grep ^ii 1>/dev/null; then
      	mount -o remount,rw /
      	apt-get update && \
      	apt-get -y install cryptsetup
      	sync
      	mount -o remount,ro /
      fi
      
      cryptsetup luksOpen /home/phablet.img phablet
      e2fsck /dev/mapper/phablet
      mount /dev/mapper/phablet /home/phablet && \
      nohup /etc/init.d/lightdm force-reload </dev/null >/dev/null 2>&1 &
      

      run as root: sudo bash <nameofscript>

      posted in Support
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @japsi said in Sony Xperia X (suzu/F5121 & F5122):

      As I see that Anbox should work in X is there any instructions how to install it? It's not on "supported devices" list yet.

      Just follow http://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html and skip "flash a specific boot image" step.

      In my case (F5122) it works. I used UT Terminal app:

      sudo mount -o rw,remount /
      sudo apt update
      sudo apt install anbox-ubuntu-touch
      anbox-tool install
      sudo apt install android-tools-adb
      sudo mount -o ro,remount /
      cd /home/phablet/Downloads
      wget https://f-droid.org/FDroid.apk
      adb install FDroid.apk
      

      and reboot... (not sure if it's needed)

      There is no sound by default, see https://github.com/anbox/anbox/issues/904. You need to override system/etc/media_codecs.xml file. I was trying to figure it out via rootfs-overlay (https://docs.anbox.io/userguide/advanced/rootfs_overlay.html) with no luck. I repacked android.img with fixed media_codecs.xml file and now there is a sound and even choppy video via NewPipe app. I used this fixed media_codecs.xml file: http://dpaste.com/2H2CP58, it's all in one from these files: https://github.com/anbox/anbox/tree/master/android/media because "Include" and "Included" tags don't work yet.

      Is there a way to apply anbox rootfs-overlay?

      posted in Devices
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @henri2h You can't modify the file directly, it's Squashfs filesystem (see https://en.wikipedia.org/wiki/SquashFS). The best way to override it is via rootfs-overlay as I wrote.

      To repack the image, you need some linux distro. Download the right android filesystem image from https://cdimage.ubports.com/anbox-images/. According to https://cdimage.ubports.com/anbox-images/devices.json it's android-armhf-64binder.img. You also need to have installed squashfs-tools package.

      Uncompress the filesystem as root to keep uid and gid identities:

      sudo unsquashfs android-armhf-64binder.img
      

      you will see something like this:

      Parallel unsquashfs: Using 4 processors
      1429 inodes (5270 blocks) to write
      
      [=================================-] 5270/5270 100%
      
      created 1239 files
      created 274 directories
      created 190 symlinks
      created 0 devices
      created 0 fifos
      

      it creates squashfs-root folder, locate squashfs-root/system/etc/media_codecs.xml file, rewrite it (as root) by the fixed one (http://dpaste.com/2H2CP58) and set the right owner:

      sudo chown 100000:100000 media_codecs.xml
      

      compress the filesystem into android.img:

      sudo mksquashfs squashfs-root/ android.img -noappend -no-xattrs -comp xz
      

      you will see something like this:

      Parallel mksquashfs: Using 4 processors
      Creating 4.0 filesystem on android.img, block size 131072.
      [=================================] 5080/5080 100%
      
      Exportable Squashfs 4.0 filesystem, xz compressed, data block size 131072
      	compressed data, compressed metadata, compressed fragments,
      	no xattrs, compressed ids
      	duplicates are removed
      Filesystem size 212128.35 Kbytes (207.16 Mbytes)
      	39.95% of uncompressed filesystem size (531034.87 Kbytes)
      Inode table size 23934 bytes (23.37 Kbytes)
      	33.61% of uncompressed inode table size (71204 bytes)
      Directory table size 16322 bytes (15.94 Kbytes)
      	43.33% of uncompressed directory table size (37666 bytes)
      Number of duplicate files found 38
      Number of inodes 1703
      Number of files 1239
      Number of fragments 229
      Number of symbolic links  190
      Number of device nodes 0
      Number of fifo nodes 0
      Number of socket nodes 0
      Number of directories 274
      Number of ids (unique uids + gids) 4
      Number of uids 2
      	unknown (100000)
      	unknown (101000)
      Number of gids 4
      	unknown (100000)
      	unknown (102000)
      	unknown (101000)
      	unknown (101003)
      

      Copy the new created android.img file into the phone's home folder into anbox-data and rewrite the original one.

      posted in Devices
      c4pp4
      c4pp4
    • RE: Icon Library

      I have given a try (OSM Scout Server icon):

      osmscout-server.svg
      https://dpaste.com/DG5BG4GEX

      scout.png

      posted in Design
      c4pp4
      c4pp4
    • RE: App menu double entries w/Anbox

      Try to refresh the Drawer by pulling down and releasing.

      posted in Support
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @boriseto

      from https://github.com/Halium/projectmanagement/issues/98:

      Kernel Support
      This Halium abstraction uses a 4.4 kernel provided by Sony and CodeAurora,
      thus has the benefit of taking advantage of upstream kernel patches
      and follows Ubuntu's Xenial kernel series for AppArmor updates.
      This opens the door for potentially decade-long support of kernel patches.
      The Halium suzu device platform is determined to support Snap packages
      and is well positioned to do so long term.

      from https://developer.sony.com/develop/open-devices/get-started/supported-devices-and-functionality/:
      KernelSupport_OpenDevices_202001.jpg

      posted in Devices
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @wdehoog

      This commit brings back almost everything in that commit back, except
      modify it so that it actually respect suspend inhibitions when pressing
      power button.

      posted in Devices
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      Audio is crackling... speakers, headphones... doesn't matter. Is it only in my case?

      posted in Devices
      c4pp4
      c4pp4
    • RE: Icon Library

      Not sure if it's the right place to ask but can someone please rework OSM Scout Server icon to be a regular square? I think it's pretty ugly now.

      https://github.com/rinigus/osmscout-server/blob/master/icons/osmscout-server.svg

      scout.png

      posted in Design
      c4pp4
      c4pp4

    Latest posts made by c4pp4

    • RE: Installer fails

      I successfully went through the process from Android 10 -> 9 -> UT. I don't remember exact walkthrough but I think it was something like this:

      I was using Linux distribution.

      At first I unlocked the device and flashed TWRP 3.5.0_9-0. I followed the video from here:
      https://www.youtube.com/watch?v=sqmng9WQFkI.
      Instead of installing TWRP installer (time 10:02) I used Advanced -> ADB Sideload:

      adb sideload twrp-installer.zip
      

      I also sideloaded Magisk-v21-4.zip to check "jdi" LCD via app:
      https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw.

      After that I followed the video from here (the same @BristledKing linked):
      https://www.youtube.com/watch?v=0t4UE4SiEL8.
      I switched from slot A to B and sideloaded Android 9 from here: https://github.com/ubports-xiaomi-sdm660/artifacts/releases/download/v0.1/jasmine_sprout_stock_android9.zip (UBports installer recommends flash it to both slots to be safe but I didn't do that).

      UBports installer:
      I think the device was recognized as "jasmine" not "jasmine_sprout" so I chose the right one from the list.
      I chose devel channel.
      After the failure with downloaded vendor.img I think I made a copy into ~/snap/ubports-installer/334/.cache/ubports/jasmine_sprout/firmware/ folder.
      UBports installer told me UT was successfully installed but after that gave me an error. The device didn't boot. I tried the installation again and the second try was really succesful.

      posted in Xiaomi Mi A2
      c4pp4
      c4pp4
    • [HowTo] Using Anbox manually to reduce battery drain

      I. Disable Anbox via anbox-tool:

      anbox-tool disable
      

      or make it disabled manually:

      rm /home/phablet/anbox-data/.enable
      stop anbox-session
      sudo stop anbox-container
      

      or alternatively configure Upstart to ignore the start on / stop on stanzas:

      sudo mount -o remount,rw /
      echo "manual" | sudo tee /etc/init/anbox-container.override
      echo "manual" | sudo tee /usr/share/upstart/sessions/anbox-session.override
      sudo sync
      sudo mount -o remount,ro /
      stop anbox-session
      sudo stop anbox-container
      

      II. Remove Anbox icons:

      rm /home/phablet/.local/share/applications/anbox-*
      

      III. Create start script:

      #!/bin/bash
      sudo start anbox-container
      start anbox-session
      

      and stop script:

      #!/bin/bash
      stop anbox-session
      sudo stop anbox-container
      rm /home/phablet/.local/share/applications/anbox-*
      

      IV. Start or stop Anbox:

      bash <nameofscript>
      
      posted in Support
      c4pp4
      c4pp4
    • RE: One method to encrypt /home/phablet

      @ernest said in One method to encrypt /home/phablet:

      Seems that lightdm doesn't restart with the latest OTA. Any tips ?

      Hi, I'm using the following script (tested on OTA-15 and OTA-16 devel):

      #!/bin/bash
      if ! dpkg-query -l cryptsetup | grep ^ii 1>/dev/null; then
      	mount -o remount,rw /
      	apt-get update && \
      	apt-get -y install cryptsetup
      	sync
      	mount -o remount,ro /
      fi
      
      cryptsetup luksOpen /home/phablet.img phablet
      e2fsck /dev/mapper/phablet
      mount /dev/mapper/phablet /home/phablet && \
      nohup /etc/init.d/lightdm force-reload </dev/null >/dev/null 2>&1 &
      

      run as root: sudo bash <nameofscript>

      posted in Support
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @fredldotme said in Sony Xperia X (suzu/F5121 & F5122):

      Status:

      Working:

      • Calling
      • SMS

      Some incoming calls and notifications are ignored (mainly when Wi-Fi is Off). Just info for newcomers.

      posted in Devices
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @Giampy Yes I know 😞
      see: https://github.com/ubports/ubuntu-touch/issues/1556#issuecomment-691728879
      and more detailed: https://github.com/ubports/ubuntu-touch/issues/1556#issuecomment-693120572

      You can add your comment but I think they don't care about it. @UniSuperBox moved it from QA to Done regardless the problem.

      posted in Devices
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @wvi OK just for sure, when your device is booting, do you see the message "Your device has been unlocked"?
      You can try booting Ubuntu 20.04 live from flash drive and using snap ubports-installer to exclude some kind of your system environment problem.

      posted in Devices
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @wvi Have you made all pre-install steps from the first post?

      posted in Devices
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @wvi The issue 1052 is about "No space left on device" and your issue 1343 is about "write failed: Read-only file system".

      posted in Devices
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @hsce1 Sorry about that. In my case the openstore launched.

      posted in Devices
      c4pp4
      c4pp4
    • RE: Sony Xperia X (suzu/F5121 & F5122)

      @Giampy https://github.com/ubports/ubuntu-touch/issues/1556

      posted in Devices
      c4pp4
      c4pp4