@thekit said in Gemini PDA:

It's not ready for daily use, but what currently works

That list sounds rather complete. What's missing in your opinion for daily use?

@flohack said in Porting Halium to Nexus 7 deb:

@doniks maybe @UniSuperBox can comment a bit on the manual tweaks you had to do for rootstocking the device, actually all should come out of the box somehow.

Well, in a way he did :) The PR for the update of docs.ubports is in, which means both ubports-boot and rootstock-install can take their bugs with them to the grave.

Then, if plasma mobile shows a screen, we should be able to do this, too right?

One would hope so. However, even with halium-boot (and a bunch more kernel configs it wanted) I managed just now to build and boot it, but I end up with the same segfaults :(

I spoke to @UniSuperBox and @bshah earlier today on telegram. There was a theory about something with libhybris and "N linker" but I didn't really get it and atm still just google logo.

what can I expect to happen if it works? I don't have a UT device around just now, so I tried with Android. I get:

$ sudo miracle-sinkctl 
[ADD] Link: 3
[miraclectl] # run 3
now running on link 3
[ADD] Peer: b2:72:bf:3b:28:c8@3
[PROV] Peer: b2:72:bf:3b:28:c8@3 Type: pbc PIN: 
[GO NEG] Peer: b2:72:bf:3b:28:c8@3 Type: pbc PIN: 
[CONNECT] Peer: b2:72:bf:3b:28:c8@3
now running on peer b2:72:bf:3b:28:c8@3
NOTICE: SINK connected
SINK set resolution 1920x1080

but other than the console output I never see anything. I was expecting to see the screen of my Android.

Edit: Ah found something:

On Laptop:

• git clone https://github.com/albfan/miraclecast
• follow the "How - Linux" steps in @Flohack's post above

On Android:

• install "Miracast Shorcut" (from fdroid)
• run it
• see your laptop show up

On Laptop:

• see "SINK connected"
• open new terminal
• cd miraclecast/res
• ./gstplayer
• see a live stream playing from your Android

Of course it misses some of the miracle of convergence .... it's just a video, you can't interact with it

Thanks! I do know :) And I did get invaluable help from there! I would be no where without it.

However, after piling up a couple of hacks I find it helpful to take a step back and summarize the status quo again which is hard in irc/telegram.

And also, I like to mix the different styles of working: Specific tips for a specific problem in the more ad-hoc irc and the long haul, asynchronous conversation of a forum/mailing list.

Oh wait ... ubports porting. No I didn't know that one! I was talking about the #halium channel. I'll have a look. Thanks.

Gave it another spin.

The general steps to get deb working are much simplified since it's all in github now: https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/asus_deb.xml - just follow the halium documentation. However, I'm wondering whether I should leave the OP as is, some people have expressed that it helped them in their ports to see the journey ...

Plasma mobile hasn't been sleeping. I can tell that the newer images work much better than previously.

For ubports, I made another attempt, but no GUI so far. Any tipps appreciated!

What I did in detail:

• Follow the steps on https://docs.ubports.com/en/latest/porting/introduction.html
• in rootstock-touch-install
  • insert the line do_shell "rm -f /data/system.img" as the first line in prepare_ubuntu_system, otherwise we have that thing left over from halium
  • insert the line IMAGE_SIZE=$(( $IMAGE_SIZE * 2 ))right after that variable is set, otherwise the image is too small, so I just double it
  • delete the line do_shell "ln /data/ubuntu.img /data/system.img", otherwise I end up with an empty system.img on the device ... Not sure what the problem was exactly, I think something goes wrong with the loop devices stepping on each others toes .. not sure
• now I can install using the latest ubports xenial root fs: build 298 form https://ci.ubports.com/job/xenial-rootfs-armhf/
• at first that wouldn't boot, so ...
• I make ubports boot a bit more verbose halium/ubports-boot
  • append quite=n debug=y to the UBPORTS_BOOTIMG_COMMANDLINE in Android.mk
  • insert [ -f /dev/kmsg ] || mknod -m 600 /dev/kmsg c 1 11 in initramfs/init right before the mkdir -p /var/lock line
  • change the line in initramfs/scripts/functions : _log_msg() from printf "$@" to printf "$@" | tee /dev/kmsg
  • now I could sprinkle around log_warning_msg blabla in initramfs/init and see everything nicely in last_kmsg.
  • eventually I found that it panics at the line: mount -n -o move /proc ${rootmnt}/proc ... I have simply commented this line for the moment, that avoids the panic and
• now it boots into the ubports rootfs
• however, no GUI comes up
• in /var/log/lightdm/lightdm.log I see

Launching process 2998: /usr/share/ubuntu-touch-session/usc-wrapper --file '/run/mir_socket' --from-dm-fd 11 --to-dm-fd 14 --vt 1
[...]
DisplayServer: Unity system compositor stopped

• usc-wrapper is a script. when I run the command inside: unity-system-compositor --disable-overlays=false --spinner=$SNAP/usr/bin/unity-system-compositor-spinner --file '/run/mir_socket' --from-dm-fd 11 --to-dm-fd 14 --vt 1
• I get a Segmentation fault (core dumped)
• when I run at the same time /system/bin/logcat | grep -Eve "NetlinkListener|rmt_storage" I don't see anything logged at the time of the segfault

logcat: http://paste.ubuntu.com/p/kz7JSTfgTR/
syslog: http://paste.ubuntu.com/p/JVQJ2mg98G/
dmesg: http://paste.ubuntu.com/p/MPvwKtYhsS/

Not sure what to do next. Maybe try halium-boot, maybe check the

lxc-checkconfig: http://paste.ubuntu.com/p/5Z6w8Kwcm6/

it still flags some things. Also, mabye related, I get

# lxc-attach -n android
lxc-attach: cgroups/cgfs.c: lxc_cgroupfs_attach: 2538 could not move attached process 10995 to cgroup of container
lxc-attach: attach.c: lxc_attach: 992 Expected to receive sequence number 0: No such file or directory.

However,

# lxc-info -n android
Name:           android
State:          RUNNING
PID:            1116
IP:             10.15.19.82
IP:             192.168.179.127

and it's all seemingly good enough for plasma mobile, so not sure.

Again, tips welcome!

I'm pretty sure that the installer does not touch the partition layout.

Remember

1. Android is weird. I wouldn't be surprised if some devices/bootloaders have specific expectations about the partition layout
2. these are embedded devices. If the bootprocess is severly messed up, you can't exactly put the hard disk into that other device and fix the partitions

So, while I guess it is possible to make cache smaller, I am not gonna try on my device and I'd caution you to do so!

Now to the aspect of "I'm running out of space" due to tinkering with libertine, ... well you still have some 6GB to through around, not huge, but not nothing either. If you run out of space, rather than doing acrobatics with partition sizes you want to look into acrobatics with bind mounting ;)

You could try and if it works document it here

https://docs.ubports.com/en/latest/userguide/dailyuse/libertine.html

I'd also try first with a symlink, but if that gives any problems, I would assume a bind mount should work. but then you have the additional challenge of having to reestablish the mount after every reboot. maybe it can be automated with upstart.

10, Initial Developer Documentation for the Librem 5 Phone Platform

Please change the post such that the urls become actual hyperlinks that can be clicked.

Enjoy your real lives guys. Well deserved. And thanks for the continuous updates!