15:30:52 #startmeeting Fedora Mobility SIG 15:30:52 Meeting started Mon May 10 15:30:52 2021 UTC. 15:30:52 This meeting is logged and archived in a public location. 15:30:52 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:30:52 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:30:52 The meeting name has been set to 'fedora_mobility_sig' 15:30:53 #meeting_name fedora_mobility_sig 15:30:53 #chair torbuntu pbrobinson _Yoda_ 15:30:53 Current chairs: _Yoda_ nirik pbrobinson torbuntu 15:30:53 #topic Init process 15:31:06 sorry for the slight late start. Was getting coffee. :) 15:31:18 An important delay for sure :) 15:32:00 who all is around today for a meeting? 15:32:07 * torbuntu is present 15:32:18 /raise 15:32:24 https://pagure.io/fedora-mobility/issue/8 meeting ticket 15:32:25 My messages are coming through yes? 15:32:32 yep. loud and clear 15:32:32 yo 15:32:38 hey Marius[m] 15:32:39 /raise 15:32:41 :D great, thanks. 15:32:50 hey hartan[m] welcome 15:33:49 so I thought we would do a remix status a fedora vanilla status and then go to the topic torbuntu had in the ticket then any other business? 15:34:17 Works for me. 15:34:27 #topic remix status 15:34:48 I've not had much time to play around... any exciting new improvements lately? 15:34:50 * pbrobinson is here now 15:35:07 hey pbrobinson, welcome 15:36:07 sounds like some good strides on suspend time/battery usage... 15:36:19 I can't think of any outstanding excitement in improvements. I have been poking around at a few different things though, such as switching the github scripts to using btrfs and then recently looking to disable the modem power driver in favor of using eg25-manager. But I haven't gotten too far yet on either. 15:36:44 fair enough. 15:36:55 the problem with the eg25-manager stuff is that it's doubtful that will go upstream 15:37:15 I have started looking at the LTE modem bits, I think I should have a patch to test for upstream to get it working 15:37:23 That is why I was looking into this, there is a user space driver that can be packaged separately. 15:37:24 oh? I thought that was the thing that was going to go upstream over the modem driver thats not upstream. 15:37:33 yes 15:37:38 oh, eg25 isn't the userspace one? 15:37:41 * nirik is confused 15:37:43 I also pushed the latest ModemManager bits which may have the GPS support 15:38:13 https://gitlab.com/mobian1/devices/eg25-manager 15:38:13 maybe I've confused, the megi kernel had a massive weird kernel thing 15:38:16 I meant to test that GPS thing, but never did. ;( Updating my phone now to try it. 15:38:22 This is the daemon to replace the kernel driver 15:38:38 But to make it work, I have to stop the kernel one from working. 15:38:48 ah yeah, that was the issue. 15:38:53 well, a issue 15:38:56 I did try to use this with vanilla fedora, but it didn't know where the modem was to try and manage it ;) 15:39:38 looking at that it looks like functionality that should be part of ModemManager 15:40:20 torbuntu: so I should have a patch in the next few days to find the modem using the way upstream deals with these modems, so it may then find it 15:40:30 seems like it should work without much poking, since it's it's own armv7 os there... 15:40:59 pbrobinson: Sounds good! I'll test whenever it is ready :) 15:41:04 I feel having a eg25-manager is very device specific and when the next device comes along with a different modem the work has to be done all over again 15:41:32 nirik: welcome to this stuff.... it's arm cores all the way down.... 15:41:39 yep. ;) 15:41:59 Which makes me think of the Librem 5, I haven't looked much at how they manage their modem choice. 15:42:01 the newer modems actually use PCIe rather than USB to interface and are basically a PCIe endpoint 15:42:17 Matryoshka doll of ever smaller arm socs 15:42:59 #topic Roadmap to official spin 15:43:26 so, my 2cents would be that we need the fedora kernel + some way to have network so you can update the thing at the very least. 15:43:34 yea, the radio control on the modem will be a Cortex-R or M series ;-) 15:44:06 nirik: yes, so that's basically what I've been looking at, also did start to dig into wifi but that's a much bigger job 15:44:06 I started looking into Fedora Remixes/Spins in general and am currently trying to tame either lorax or osbuild to generate images for the Pinephone. The end-result should be similar to what the current images are, but using somewhat "more official" tooling. 15:44:06 Some people already said they'd have interest in making a calamares config that works on smartphone-devices like the Pinephone so we can have a graphical installer. 15:44:30 hartan[m]: look at the kickstarts and ImageFactory 15:45:03 I have an initial .ks somewhere I can likely dig out 15:45:13 probinson: Yup, I have already been referred to the fedora-kickstarts repo on pagure. I'm currently trying to figure out how I'd use it to make an image. 15:45:48 yeah, we will need a working kickstart, but that should hopefully not be too bad. 15:46:16 hartan[m]: basically "imagefactory --debug base_image --parameter generate_icicle false tdl-aarch64.xml --file-parameter install_script fedora-mobility.ks" 15:46:30 That'd be great, thanks! 15:46:55 actually s/base_image/target_image 15:47:07 #info need vanilla kernel booting/working [x] 15:47:10 What about "livemedia-creator", is that still a thing? The Wiki isn't exactly clear on it. 15:47:29 #info need networking working of some kind: wifi, wan, or usb [ ] 15:47:52 hartan[m]: nope, you don't want to be booting .iso images on a device like that 15:48:04 Was there anything else userspace that should be added to that phosh DE group? 15:48:17 I don't remember if chatty has been added to that since it got into the main repo yet. 15:48:26 torbuntu: whats left in the copr repo besides rmegi kernel and uboot? 15:49:02 I think just a few managers I was working on packaging/testing. Nothing mission critical (outside the kernel) 15:49:18 mmsd and eg25-manager is mostly all. 15:49:47 What's with the custom patch for phosh? 15:49:50 ah yes, mms. :( 15:50:11 mms is coming soon to chatty :) mmsd already works, just need to plug it into Chatty as a front end. 15:50:32 freenode_hartan[m]: the patch is for making Phosh work with wlroots 0.12.0 15:50:40 wow, mms, don't remember the last time I used that 15:51:11 I really wish it wasn't used here anymore in the states. 15:51:17 But most group texting is done through mms and people still prefer it for media. 15:51:17 pbrobinson: sadly, it's used all the time in the US. ;( all group messages and anything with media. 15:51:17 :( 15:51:39 ^ 15:51:44 pbrobinson: how would I check the modem? gnome-maps isn't finding location, but that could be something with it... 15:51:51 german providers block mms to security reasons. 15:51:53 nirik: yea, most people elsewhere use non carrier like Signal, my provider has decommissioned mms 15:52:37 nirik: good question, TBH I'll have to check when I finish digging into that patch, it should be a ttyXX interface 15:53:13 nirik: once I can test my modem locally will probably be easier as I only have a vanilla Fedora minimal on mine ATM 15:53:15 If it is the same thing I saw with trying to hook up eg25-manager, it may not be able to be found... 15:53:24 May 10 08:47:29 localhost.localdomain ModemManager[327]: [modem0] modem couldn't be initialized: Couldn't check unlock status: QMI operation failed: GW primary session index unknown 15:53:41 megi's driver may be holding it hostage... 15:53:48 (I don't have a sim in mine, might be confusing it) 15:53:53 that could be too. 15:54:10 no sim, no gps 15:54:25 anyhow, torbuntu... did you want to start a wiki page or file or something for a roadmap? or do we think we know it enough from just discussing? 15:54:56 Since it seems like a small list I think the discussion is probably enough for now. 15:55:35 Getting a fedora kernel with networking and the Phosh environment group? 15:55:37 probably just add it as a section to the existing wiki page 15:55:38 Do you mean roadmap as in "what's not upstreamed yet"? 15:56:10 more a 'what needs to be working before we can start making a official fedora spin' 15:56:14 ^ 15:56:19 torbuntu: and a kickstart... 15:56:40 ah yes, that too. So those 3 things for a Spin? 15:56:47 we also need to put in a fedora 'change' about it and get it approved 15:57:01 but I can't imagne that would be too hard. 15:57:02 That is another thing I was wondering about yeah 15:57:21 but it does mean we need to target some fedora release... 35, 36, whatever 15:57:53 I'm not sure what a timeline looks like for getting the KS and Kernel ready. 15:58:11 I suppose step 1 is really what we need from kernel upstream, without a working phone/data it's pretty pointless 15:58:24 ^ 15:58:34 yeah, with no way to use the net/update... not worth it 15:59:02 Is something missing for getting the USB C port to work? 15:59:45 not sure there. I know it did not last time I checked in fedora kernel, but it's been a long while since then 16:00:40 drivers 16:01:13 I don't believe any of the usb side of that HW IP block is upstream, there is the DP bits 16:01:32 Ah, that explains that. 16:02:03 if we could get that working that would be another option for net. :) basically IMHO any net is good... 16:02:14 Exactly. 16:02:49 arm-image-installer doesnt let you do encryption does it? (thats another thing we need in the longer roadmap... the daily driver roadmap :) 16:03:21 If we had encryption, how would you enter the passwords? 16:03:26 some distris already have this in place, but you need a working installer to implement it 16:03:48 nope, arm-image-installer doesn't do the actual install 16:03:50 hartan[m]: on screen keyboard... ;) 16:03:59 they present an onscreendisplay when asked for the password. 16:04:09 anyhow, sorry, thats a sidetrack. :) 16:04:19 anything else on roadmap? 16:04:20 * they present an onscreenkeyboard when asked for the password. 16:04:20 Is the OSK squeekboard, or some custom implementation? 16:04:31 Plasma? 16:05:42 Marius[m]: plasmas on screen keyboard/encryption? or you meant for roadmap? 16:05:59 I think, in the long term, we need plasma mobile as desktop in fedora. 16:06:00 squeekboard is the osk used by Phosh. 16:06:49 Marius[m]: well, that would be great... but I think we should focus on phosh for now and get it in a state where it's a spin... then as people package plasma mobile we can more easily add it... 16:06:59 ^ 16:07:01 but I of course won't tell anyone how to spend their time. :) 16:07:10 thats why i wrote "long term" ;) 16:07:24 if it's all packaged up we could do it at the same time as phosh... just mostly it needs the packaging work. 16:07:50 and a way to switch to it. 16:08:11 yeah... 16:08:20 #topic Open Floor 16:08:37 Oh! Before I forget, for the "Official Spin" can we do an ostree image? Or is that being way too optimistic at this time? 16:09:02 so, I had one other thing I just thought of... I was thinking I might do a talk on pinephone with fedora at nest (the next fedora conference)... would love help/feedback on it tho... 16:09:22 torbuntu: I think we should do a normalish one first, then once thats working go to ostree. 16:09:38 As i made a talk about it for the LPD next saturday, contact me. 16:09:38 I'd be more than happy to assist with feedback and help. I don't know if my schedule permits me to attend live though 16:09:40 I agree that ostree would be a good thing, just don't want to aim too high 16:10:03 Marius[m]: cool! prerecorded? or slides/live? 16:10:07 nirik: normal first, then ostree, works for me :) 16:10:12 Makes sense yeah. 16:10:22 Prerecorded in german with slides .. 16:10:34 ah nice. 16:10:43 just contact me later. 16:10:49 will do. :) Thanks. 16:11:26 Oh, another side note, we should be really close to having aarch64 flatpaks... there's just some last indexing stuff to do I think. 16:11:51 Awesome! Will they be a part of the normal packaging workflow with other architectures? 16:11:53 flatpaks of what? 16:11:56 Flatpaks from the fedora registry? 16:12:35 torbuntu: well, they will be normal for all flatpaks 16:13:07 I am wondering for myself packaging applications, do I just do the `fedpkg build` as normal, or will I have to do something else to build the flatpaks? 16:13:54 I never can find the page with all the namespaces... but basically a bunch of fedora apps are published in the fedora registry as flatpaks 16:14:02 yes, it's differnt... 16:14:44 https://docs.fedoraproject.org/en-US/flatpak/ 16:15:38 but they work fine on the phone... and will be somewhat needed with ostree... 16:15:40 Maybe this helps? 16:15:41 https://docs.fedoraproject.org/en-US/flatpak/concepts/#_oci_images 16:15:41 Didn't know they're OCI images now in Fedora. But that explains how they implemented the "delta"-updates. 16:15:49 yep. 16:15:58 Excellent, I mostly use flatpacks on the phone now as it is :) 16:16:33 ok, if nothing else will close out in a minute... thanks for coming everyone. 16:16:52 Thanks! 16:18:10 #endmeeting