WEBVTT 00:00.000 --> 00:12.680 Next up, I'm going to introduce it as a expo. 00:12.680 --> 00:20.840 Sorry, first little question, who here is a mobile Linux user, can you raise hands 00:20.840 --> 00:21.840 please? 00:21.840 --> 00:23.840 Who here is this? 00:23.840 --> 00:28.960 Who here is a so mobile Linux, is it an Intex user, no Android full-backs or a good to see? 00:28.960 --> 00:30.960 Who here is an Essex Mo user? 00:30.960 --> 00:35.960 Oh, I should raise my hand, okay, we have two, three hands and we had a bit more hands before. 00:35.960 --> 00:44.960 So, Essex Mo is a mobile user interface, it's added for hackers. 00:44.960 --> 00:53.200 We started in 2020 when Mars Alan founded our project and we shipped with postmarked 00:53.200 --> 00:59.360 the OS and also other distributions and there's been a lot of development since 2020 and our project 00:59.360 --> 01:02.160 yet is getting more and more interest. 01:02.160 --> 01:08.000 Our motto is minimal mobile hackbook, also featuring on my t-shirt here, so I'll go through 01:08.000 --> 01:14.000 each of these three motto keywords and explain and they'll be about the project. 01:14.000 --> 01:18.440 They won't take long, we only have 10 minutes, minimal. 01:18.440 --> 01:23.600 So what we do is we're minimal in reusing existing pre-opressor software components. 01:23.600 --> 01:28.040 We don't try to reinvent the wheel, we'll ever something already exists, we use it and we plug 01:28.040 --> 01:30.520 it into our infrastructure. 01:30.520 --> 01:37.760 At the heart of Essex Mo is a tiling window manager, we use sway on Wailons and we use DWN on 01:37.760 --> 01:45.680 XOR currently, so we support both Wailons and XOR and all these components are tied together 01:45.680 --> 01:53.200 using simple post-exile scripts, so that's the glue that holds everything together. 01:53.200 --> 02:00.400 We feature a menu-based interface, so we are kind of a non-traditional interface in that 02:00.400 --> 02:05.640 sense that we are menu-based and because menus are very versatile and you can very easily 02:05.640 --> 02:11.280 chuck things into a menu without having to design many user interface components. 02:11.280 --> 02:17.400 We use B-manue or Wofi on Wailons and on XOR, we use the plane or the D-manue from the 02:17.400 --> 02:21.600 Circles project. 02:21.600 --> 02:26.080 And then we have context menus for various applications, so when you open an application 02:26.080 --> 02:32.120 and you swipe open your menu, you get a menu that is dependent on the application you 02:32.120 --> 02:36.080 were in. 02:36.080 --> 02:40.760 So when needed we built new components or contribute to existing components, so one of 02:40.760 --> 02:47.760 the things that we contribute to a lot is the keyboard, virtual keyboards from Wailons, 02:47.760 --> 02:55.360 WVKBD, and SVKBD from Circles project, those are virtual keyboards and we have a touch 02:55.360 --> 03:00.000 demon that's already there since the inception of the project and there are all kinds 03:00.000 --> 03:02.040 of other small components. 03:02.040 --> 03:05.440 One of the latest additions is peanut butter which is a lock screen, which I will get 03:05.440 --> 03:09.080 back to in a later slide. 03:09.120 --> 03:16.080 So mobile, so the mobile aspect is of course, we run on phones, so we want things to be 03:16.080 --> 03:17.080 mobile. 03:17.080 --> 03:23.640 Our menus are optimized for talking to the mode manager, for talking to network manager, 03:23.640 --> 03:26.960 they have all kinds of entries to interact with that. 03:26.960 --> 03:31.960 You can just see your incoming texts in the menus and reply to that your normal editor 03:32.200 --> 03:38.480 or e-mexor, whatever you want, pops up or you could type your SMS in depth. 03:38.480 --> 03:44.120 We optimize for small touch screens, because it's a small form factor so that it has 03:44.120 --> 03:47.680 different demands, but of course we only control so much. 03:47.680 --> 03:51.240 One of the keys on mobile devices is of course to be fairly lightweight, and that's one 03:51.240 --> 03:58.240 of the things that we also focus on, because we take sex lightweight components, we have 03:58.240 --> 04:03.520 we can run easily on devices that are constrained by battery. 04:03.520 --> 04:07.480 So the most important part, of course, the hackable part is why we're all here, we want 04:07.480 --> 04:11.280 to own our phones, and we want to modify our phones to our liking, and that's why we 04:11.280 --> 04:16.280 run Linux on them, and that's one of the things that we excel at, because we try to make 04:16.280 --> 04:21.680 everything as hackable as possible, the post-exile scripts form the glue of the system, 04:21.680 --> 04:24.520 and you can add a DCL script through our hook system. 04:24.520 --> 04:28.840 We provide hooks for things like receiving an SMS, and you can add a debt hook, which is 04:28.840 --> 04:33.840 just a sales script, if you want, to inject your own functionality, whatever that may be 04:33.840 --> 04:38.080 forward, you do x-n-pp to matrix, or that's up to you. 04:38.080 --> 04:42.440 You can use your favorite editor, your favorite page here, as I mentioned. 04:42.440 --> 04:47.440 What we also have is SSH supports, which is the first-class thing, usually I don't have 04:47.440 --> 04:51.920 my phone just somewhere in the house, and I hesitate into it, that I use my phone 04:52.160 --> 04:56.920 as an SSH device, then that I really use it, and then you can just control your menus 04:56.920 --> 05:01.920 over SSH, you can send text over SSH, everything, everything, of course, not calling, 05:01.920 --> 05:06.240 that's another issue. 05:06.240 --> 05:10.480 We have device profiles, which are basically configurations for different devices, and 05:10.480 --> 05:15.560 more and more devices are being supported on post-market OS, so then also on 05:15.560 --> 05:20.200 SXMO, when people make these device profiles. 05:20.200 --> 05:28.040 What's new since the last release, it was January, but we have a lock screen now, and 05:28.040 --> 05:32.840 we're that we joined the 99.9% of people who already had a lock screen, we never had a 05:32.840 --> 05:37.400 lock screen, we didn't really mind not having a lock screen, because usually when people 05:37.400 --> 05:43.880 would find an SXMO phone, they wouldn't understand how to operate it anyway, but that's 05:43.960 --> 05:48.840 security practice, so now we do have a lock screen, it's called peanut butter, and it's 05:48.840 --> 05:53.800 a weight-in-base touch screen focused on unlocking by pushing the sequence of corners in 05:53.800 --> 05:57.480 your desired sequence. 05:57.480 --> 06:02.760 What we also have is a new menu back end wofi, our manual page has got a refresh, so 06:02.760 --> 06:05.880 with the documentation is more up to date now, and it's just a normal mum page, which 06:05.880 --> 06:11.080 you can read on your phone, very old scope, works well, and there are new hooks for 06:11.080 --> 06:17.560 things like blocking numbers, and things like that, so what's coming, that integration 06:17.560 --> 06:23.080 with system D, because we also want to run on systems that use system D, 06:23.080 --> 06:28.440 a post-marked OS is switching to system D, but for aseximult, there are also staying on 06:28.440 --> 06:33.240 open RC, so it's optional, you don't have to use system D, but when you use system D, 06:33.240 --> 06:37.800 we want to have good integration for it, there's i3 supports coming up by a contributor, 06:37.800 --> 06:41.160 so you can plug in another window manager if you want, a river supports also something 06:41.160 --> 06:46.840 I'm working on, improve power state handling, improve performance for the status bar, 06:47.960 --> 06:53.320 all these kind of small things, calling the asex and PPP is a project our other 06:53.320 --> 07:00.040 co-maintainers working on, and more device profiles, so that's it, you can find aseximult 07:00.040 --> 07:04.840 on the aseximult website, and you can contribute patches on a mailing list, and we have an 07:04.840 --> 07:10.040 ICT channel which is also a bridge to matrix, so you can join the discussion and join the community 07:10.040 --> 07:16.040 and help build aseximult and mobile in exchange for general, thanks for your attention 07:16.040 --> 07:27.480 We do have some time for questions, so if you want, now it's your chance 07:27.480 --> 07:31.480 Yes? 07:31.480 --> 07:45.880 Could you speak up a bit, because it's a bit hard to hear, yeah, the device, the question was what 07:45.880 --> 07:51.320 did the device profile, what's in them, right? It's basically a set of environment variables 07:51.320 --> 07:58.200 that defines all kinds of aspects of the system that are are are are variable like what specific 07:58.200 --> 08:04.120 device is, specific hardware path through a device or enabling or disabling specific functionality, 08:04.120 --> 08:09.640 so just the device has a modem, does it not have a modem, where is the modem, such kinds of 08:09.640 --> 08:16.760 basic things are in device profiles, so it's a shelf grip with basic environment variables for 08:16.760 --> 08:18.200 describing your device 08:19.160 --> 08:25.240 I think the time that the device will review will come out there 08:26.280 --> 08:31.400 Oh, which you are recommend, I'm running it on a OnePlus 6 currently, which is fairly decent, 08:31.400 --> 08:36.840 but one of the big problems is core audio, it's also in postmarked OS and in the next mobile 08:36.840 --> 08:42.680 in general, as Lukas talk, you mentioned it already, core audio sucks and doesn't really work well, 08:42.920 --> 08:48.200 but other than that, that's a good device, the Google Pixel 3A is also getting some prominence, 08:48.680 --> 08:53.320 yeah, you should look, you check the postmarked OS list for the best devices, and pick. 08:53.320 --> 08:55.560 Very quick, very quick. 08:55.560 --> 09:01.960 Yeah, how can I post, how can I post it? 09:03.560 --> 09:07.000 Port a new device, you can read that manual place that I've mentioned, and there's a section about 09:07.000 --> 09:11.880 this device profiles, and then you can read exactly how you get what kinds of variables are needed for 09:12.680 --> 09:18.680 for your device. And of course you have to first put it into postmark the way so that 09:18.680 --> 09:22.680 independent of as Eximao.