**** BEGIN LOGGING AT Mon Jun 01 02:59:57 2020 Jun 01 07:31:50 @erfanoabdi any plans for Halium-9 GSI OTA updates or incremental updates that doesn't format all previous data? Jun 01 07:41:16 Is it hard to implement it? Jun 01 07:42:29 For OTAs to work you'll probably have to end up working with the UBports community, getting your kernel built by the CI server. Jun 01 07:47:03 @Comrade_Nora [And I keep failing to compile the systemimage], keep removing Java crap like APKs and possibly mentioned JARs from the device repos & files and it'll pass at one point hopefully ;) if you're doing a Halium 9 port you could always use the GSI Jun 01 07:54:38 @fredldotme [For OTAs to work you'll probably have to end up working with the UBports communi …], Hm. But since the GSI uses a modified rootfs and system image, will it possible to set up OTA updates for different rootfs than the official rootfs? But ubports community u mean the UBports telegram group or some other group? Jun 01 07:56:52 The PinePhone also uses a slightly customized rootfs, so that shouldn't be too much of a problem. But yeah, when it's time to make system-image work with GSIs it would probably be best to ask in one of the UBports groups on Telegram, or the forum. Jun 01 08:11:48 @fredldotme [The PinePhone also uses a slightly customized rootfs, so that shouldn't be too m …], Understood. thanks👍 Jun 01 08:13:09 I think its more appropriate for Erfan to do it though. The rootfs and System image are his work for the most part. Only boot image various for devices. Let's see what Erfan has in mind too. Jun 01 08:18:49 Well, I'm sure we don't want to add yet another OTA mechanism other than what we already have in UT, so it has to integrate with system-image, which goes through CI for the most part. It'll also mean needing a proper recovery with system-image support, that means TWRP is out of the picture. But yeah, let's see what Erfan has to say too Jun 01 08:18:49 . Jun 01 08:27:02 @fredldotme [Well, I'm sure we don't want to add yet another OTA mechanism other than what we …], Hmm👍 Jun 01 08:27:25 omerready was added by: omerready Jun 01 10:09:27 I say don't release any ota until recovery of AB devices gets fixed Jun 01 10:10:00 Btw we can have a virtual AB method ane seamlessly updates Jun 01 10:10:26 @erfanoabdi erm maybe don't call it virtual a/b when it's already something else Jun 01 10:10:28 New rootfs and system will be placed to /data/image-new Jun 01 10:10:45 @phhusson [@erfanoabdi erm maybe don't call it virtual a/b when it's already something else], Ah yeah true Jun 01 10:11:20 @erfanoabdi [New rootfs and system will be placed to /data/image-new], And in reboot ramdisk will pick them as image Jun 01 10:13:09 @erfanoabdi [And in reboot ramdisk will pick them as image], Ok. But will the old userdata and packages will also be there and merged ? or it wont be available? Jun 01 10:14:22 @erfanoabdi [And in reboot ramdisk will pick them as image], you can even rename /userdata/system.img to /userdata/system-old.img and system will continue to run fine until reboot Jun 01 10:14:29 @joelselvaraj [Ok. But will the old userdata and packages will also be there and merged ? or it …], Will be lost on update … Users basically shouldn't remount rootfs afaik in legacy devices too Jun 01 10:14:46 but on fully ported devices we'd like to utilize /system partition not to waste space Jun 01 10:14:49 @NotKit [you can even rename /userdata/system.img to /userdata/system-old.img and system …], Yeah Jun 01 10:15:18 on recent devices it should fit whole rootfs Jun 01 10:15:45 @NotKit [but on fully ported devices we'd like to utilize /system partition not to waste …], Yeah that's our golden goal Jun 01 10:17:14 @erfanoabdi [Will be lost on update … Users basically shouldn't remount rootfs afaik in legacy …], So basically, we cannot incrementally update rootfs. Any updated will overwrite the existing changes to rootfs right? But we can atleast persist user data such as photos and videos and apps? or everything will be overwritten? Jun 01 10:18:24 Isnt it bad? If user apps and customizations is lost on each update? Jun 01 10:20:07 android has a patch system to update system and vendor image right? cant we have something similar for halium/ubuntu touch? Jun 01 10:20:12 apps are stored outside of rootfs Jun 01 10:21:29 @joelselvaraj [android has a patch system to update system and vendor image right? cant we have …], that system works only when you have unmodified system and vendor partitions, so same Jun 01 10:22:27 I think currently flashing Erfan's zips without wiping data will keep user data and apps Jun 01 10:22:31 Ah ok. The expected use case is, users should not modify the rootfs. All apps and files is stored outside rootfs and will still be present if rootfs updated. Jun 01 10:22:54 @NotKit [I think currently flashing Erfan's zips without wiping data will keep user data …], Hmm. Get it. Jun 01 10:23:51 you mean keeping the images as files around? Jun 01 10:25:51 @joelselvaraj [Ah ok. The expected use case is, users should not modify the rootfs. All apps an …], There's one method u can use … apt upgrade.. Jun 01 10:26:08 To keep rootfs updated Jun 01 10:26:50 Once we get halium9 rootfs to CI that should do the same Jun 01 10:28:11 Yeah Good then👍 looking forward for your GSI to be included in the CI. so we can get seamless updates. GSI starting look stable for more people to use. Jun 01 10:28:33 👍😉Yep Jun 01 10:28:43 We still have long way to go Jun 01 10:29:12 👍Sure. Good luck Jun 01 10:32:37 @NotKit How can we switch mobile data to sim?. I found one dbus command `dbus-send --session --print-reply --dest=com.ubuntu.connectivity1 /com/ubuntu/connectivity1/Private org.freedesktop.DBus.Properties.Set string:com.ubuntu.connectivity1.Private string:SimForMobileData variant:objpath:/` but dont know what to give for objpath. Is Jun 01 10:32:37 this right command? Jun 01 10:33:30 I didn't try it myself, so feel free to experiment Jun 01 10:34:17 is there a list of devices that work (-ish) with halium 9? Jun 01 10:50:32 @NotKit [I didn't try it myself, so feel free to experiment], ok 👍 Jun 01 10:50:40 @NotKit [I didn't try it myself, so feel free to experiment], [Edit] ok 👍 Thanks Jun 01 11:17:16 @erfanoabdi do you happen to know how to properly deploy a debos built rootfs.tar.gz with a custom-built system.img? I tried hacking the halium-install script but nothing (e.g. vendor, persist, ...) gets mounted on boot and it seems upstart doesn't start either Jun 01 11:17:34 for UBports on Halium 9 base Jun 01 11:24:51 https://github.com/erfanoabdi/ubport_GSI I presume I could hack on this too :p Jun 01 11:31:16 Make sure u push system with "android-rootfs.img" file Jun 01 11:33:37 Since we're talking about the OTA functonality: We'll need a fixed gpg and toybox for the recovery. Does anybody have a device capable of debugging the ecovery bootup? Jun 01 11:34:05 on Volla Phone we still have separate recovery partition Jun 01 11:34:13 and /proc/last_kmsg Jun 01 11:34:14 It'll need gpg and a fixed toybox: … https://github.com/fredldotme/android_external_toybox … https://github.com/fredldotme/android_external_gpg Jun 01 11:35:13 last_kmsg makes Mediatek look like the goody guy :) Jun 01 11:35:22 [Edit] last_kmsg makes Mediatek look like the good guy :) Jun 01 11:36:38 (Compared to non-functioning pstore on the Pixel 3a, that is) Jun 01 12:00:16 Genxster was added by: Genxster Jun 01 12:01:32 @erfanoabdi [Make sure u push system with "android-rootfs.img" file], so now I deployed using halium-install's `--system-as-root` arg as well as making the system image generate with `BOARD_BUILD_SYSTEM_ROOT_IMAGE := true`, rebooted -> no SSH, copied android-rootfs.img to system.img, rebooted -> ubports plymouth splash came up and d Jun 01 12:01:32 evice booted to setup :D Jun 01 12:03:54 @erfanoabdi [Make sure u push system with "android-rootfs.img" file], [Edit] so now I deployed using halium-install's `--system-as-root` arg as well as making the system image generate with `BOARD_BUILD_SYSTEM_ROOT_IMAGE := true`, rebooted -> no SSH / GUI, copied android-rootfs.img to system.img, rebooted -> ubports plymouth splash Jun 01 12:03:54 came up and device booted to setup :D Jun 01 12:06:30 (Photo, 800x1067) https://irc.ubports.com/uut1pTx8.png look promising already :) Jun 01 12:06:34 (Photo, 800x1067) https://irc.ubports.com/s5e2LGmM.png looking promising already :) Jun 01 12:07:05 @arnavbhatt288 [We tried to port Halium to kenzo], Have you build for Kenzo successfully ? Jun 01 12:08:00 @Deathmist1337 [], ril not crashing anymore? Jun 01 12:13:46 @erfanoabdi [ril not crashing anymore?], looks like it still does crash the device on shutdown anyway :/ SIM showed up on top bar when I inserted it though while the device was already running, no cellular network though Jun 01 12:13:51 I assume I need stub_netd? Jun 01 12:15:24 aaand it seems to have just crashed while booting too with SIM on slot 1, damn... Jun 01 12:15:32 yeah stub netd is needed on device tree, but that would be better if it wasn't crashing Jun 01 12:18:18 (Photo, 508x761) https://irc.ubports.com/UdyS5Vwq.png WOWW Jun 01 13:03:56 after testing I seem to need both `system.img` as well as `android-root.img` in `/data` for the GUI to show up; `system.img` alone gets me to SSH but no GUI and `android-root.img` alone doesn't even have SSH. I just tested a cheeky `ln -s system.img android-rootfs.img` and that seems to do the trick lol Jun 01 13:12:54 @erfanoabdi no luck with sub_netd btw, the service 100% is running, but all I get is this in `/var/log/syslog` after I toggled cellular data off & back on: https://pastebin.com/raw/AbKE08nN Jun 01 13:13:01 [Edit] @erfanoabdi no luck with stub_netd btw, the service 100% is running, but all I get is this in `/var/log/syslog` after I toggled cellular data off & back on: https://pastebin.com/raw/AbKE08nN Jun 01 13:19:19 https://pastebin.com/raw/7trTnJKB there's also my running `/proc/config.gz`, but everything relevant regarding IPA* seems to be already enabled Jun 01 13:29:23 @Deathmist1337 sorry no idea, I'll get op5t from work soon and will help to debug Jun 01 13:35:49 oh nice ^^ the GSI is actually working better than this systemimage currently, e.g. I still have broken vibration (hfd) & fingerprintd here Jun 01 13:36:22 [Edit] oh nice ^^ the GSI is actually working better than this systemimage currently, e.g. I still have broken vibration (hfd) & fingerprintd here among other issues like camera crashing on startup etc Jun 01 13:46:06 When I run this command on terminal … wget https://static.peat-network.xyz/junk/ubports/com.ubuntu.camera_3.1.2+gstdroid3_arm64.click … pkcon install-local --allow-untrusted com.ubuntu.camera_3.1.2+gstdroid3_arm64.click … It says this package for 'arm64' and this system architecture is 'armhf' … My device is arm64 … Error - https://del.dog Jun 01 13:46:06 /igrestastu … Source - https://github.com/Linux-On-X00TD/ Jun 01 13:46:31 [Edit] When I run this command on terminal … "wget https://static.peat-network.xyz/junk/ubports/com.ubuntu.camera_3.1.2+gstdroid3_arm64.click … pkcon install-local --allow-untrusted com.ubuntu.camera_3.1.2+gstdroid3_arm64.click" … It says this package for 'arm64' and this system architecture is 'armhf' … My device is arm64 … Error - https: Jun 01 13:46:31 //del.dog/igrestastu … Source - https://github.com/Linux-On-X00TD/ Jun 01 13:47:05 [Edit] When I run this command on terminal … "wget https://static.peat-network.xyz/junk/ubports/com.ubuntu.camera_3.1.2+gstdroid3_arm64.click … pkcon install-local --allow-untrusted com.ubuntu.camera_3.1.2+gstdroid3_arm64.click" … It says this package for 'arm64' and this system architecture is 'armhf' … My device is arm64 … Error - https: Jun 01 13:47:05 //del.dog/igrestastu … Source - https://github.com/Linux-On-X00TD/ … Used UbuntuTouch gsi v6 ubport Jun 01 13:47:14 @A_T_R the rootfs is `armhf` still even if your device is `arm64` I believe because there are ongoing issues with `arm64` packacing that are being solved Jun 01 13:48:16 @Deathmist1337 [@A_T_R the rootfs is armhf still even if your device is arm64 I believe because …], OK Jun 01 13:49:14 Thanks Jun 01 18:50:09 布淳奠 was added by: 布淳奠 Jun 01 18:52:26 If both possible is it reccomend to build halium9 or 7 Jun 01 19:04:01 Marie Sams was added by: Marie Sams Jun 01 19:16:58 (Photo, 559x800) https://irc.ubports.com/AmQkt0IS.png Cool Jun 01 19:17:13 @NotKit Jun 01 19:17:22 you need a captcha Jun 01 19:25:14 @Augustin94 [If both possible is it reccomend to build halium9 or 7], Halium 9 is still W.I.P currently but for a recent device a bunch of stuff will work out of the box with the GSI for example while Halium 7 is a much more manual process Jun 01 23:38:52 How can I change the device name in the about page? Jun 01 23:39:04 (In Erfan's GSI) Jun 01 23:45:23 @Deathmist1337 [Halium 9 is still W.I.P currently but for a recent device a bunch of stuff will …], I am on a non treble device. Jun 01 23:56:35 then probably 7 since we don't have experience with that on 9 Jun 02 02:35:35 @mintphin [How can I change the device name in the about page?], @erfanoabdi Jun 02 02:44:01 @mintphin [@erfanoabdi], There's no easy way to do it Jun 02 02:45:44 @erfanoabdi [There's no easy way to do it], Is there a way to do it even? Jun 02 02:46:19 @mintphin [Is there a way to do it even?], Yeah Jun 02 02:47:40 we can get device code via `getprop("ro.build.product")` or `getprop("ro.product.device")` Jun 02 02:48:25 @birdzhang [we can get device code via getprop("ro.build.product") or getprop("ro.product.de …], On halium9? Jun 02 02:48:37 @erfanoabdi [On halium9?], on twrp Jun 02 02:49:17 `ro.product.device` Jun 02 02:49:19 getprop returns some useful values, like `ro.product.brand` Jun 02 02:49:34 ```# getprop |grep 'ro.product' … [ro.product.board]: [MSM8953] … [ro.product.brand]: [Xiaomi] … [ro.product.cpu.abi]: [arm64-v8a] … [ro.product.cpu.abilist32]: [armeabi-v7a,armeabi] … [ro.product.cpu.abilist64]: [arm64-v8a] … [ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi] … [ro.product.device]: [vince] … [ro.product.locale]: Jun 02 02:49:34 [en-US] … [ro.product.manufacturer]: [Wingtech] … [ro.product.model]: [Redmi 5 Plus] … [ro.product.name]: [omni_vince]``` Jun 02 02:50:24 [ro.product.model] should be the property shown in the about page. Jun 02 02:51:35 Oh wait. Jun 02 02:51:38 I know why this happens. Jun 02 02:52:00 Instead of getting "ro.product.model", it should get "ro.product.vendor.model" Jun 02 02:54:57 @mintphin [Instead of getting "ro.product.model", it should get "ro.product.vendor.model"], on davinci, it returns `[ro.product.vendor.model]: [lineage_davinci]` Jun 02 02:55:16 `[ro.vendor.product.model]: [Redmi K20]` is the right value Jun 02 02:55:48 or `ro.product.model` is okay Jun 02 02:56:00 Yeah it should be ro.vendor.product Jun 02 02:56:08 wait Jun 02 02:56:08 no Jun 02 02:56:15 on my device it doesn't exist. Jun 02 02:56:31 getprop |grep model Jun 02 02:57:04 returns only ro.product.model which is "Ubuntu Touch" Jun 02 02:57:19 [Edit] returns ro.product.model which is "Ubuntu Touch" Jun 02 02:57:33 and also it returns ro.porduct.vendormodel which is Mi A3 Jun 02 02:57:39 it's better to run on recovery Jun 02 02:57:57 yeah. Jun 02 02:58:09 but i can't keep the recovery with ubuntu touch unfortunately. Jun 02 02:58:09 @birdzhang [it's better to run on recovery], Why lol Jun 02 02:58:35 The thing is he is running gsi Jun 02 02:58:56 @erfanoabdi [Why lol], so that we can get the right value when installing gsi Jun 02 02:58:58 And props with vendor prefix is the value he needs Jun 02 02:59:57 @birdzhang [so that we can get the right value when installing gsi], No we should change some ubports codes to check for vendor props first **** ENDING LOGGING AT Tue Jun 02 02:59:57 2020