WEBVTT 00:00.000 --> 00:10.160 Okay, so welcome to this Foss on Mobile Devroom. 00:10.160 --> 00:14.880 It's great to see the room fill up so quickly, although I know that's kind of annoying 00:14.880 --> 00:19.280 for people who want to get in, but hey, everything is recorded. 00:19.280 --> 00:27.480 I'm just an important member before I jump into their presentation proper, but just to 00:27.480 --> 00:37.200 say that we're combining a range of open source software on mobile, so we are doing 00:37.200 --> 00:45.920 Linux on mobile, we're doing AUSP, Android open source, and we're also doing a bunch of 00:45.920 --> 00:50.760 stuff about ecosystem and apps and all that kind of stuff. 00:50.760 --> 00:55.800 So this is everything you could ever want to know about Foss on mobile. 00:56.760 --> 01:06.760 I haven't said that then, I'm going to kick off with the first presentation. 01:06.760 --> 01:11.880 So just to reiterate what I've just said in actual facts, this room is about Foss on 01:11.880 --> 01:15.640 mobile and Linux-based platforms. 01:15.640 --> 01:19.240 There are maybe other operating systems that are not Linux-based, but hey, we don't 01:19.240 --> 01:22.760 do them. 01:22.760 --> 01:29.080 So we're talking about all the things I've just mentioned, AUSP, custom ROMs, Linux mobile 01:29.080 --> 01:36.920 operating systems, free apps, free app stores, and also open source hardware and kernel 01:36.920 --> 01:41.080 enablement and all that kind of stuff. 01:41.080 --> 01:45.240 We like the idea of bringing everybody together from this range of disciplines, which 01:45.240 --> 01:50.800 have a lot of commonality, so we're looking for some, we're looking for some cross-pollination 01:50.800 --> 01:56.880 colonization here. 01:56.880 --> 02:02.000 So this presentation actually has three presenters, so I'm Chris Simmons. 02:02.000 --> 02:08.960 We also have David, you guys want to come on because you're on an element and remain lurking 02:08.960 --> 02:09.960 over their own corner. 02:09.960 --> 02:15.240 They will come on their appropriate times and just in case you can't remember what 02:15.320 --> 02:22.360 it looked like, this is what we all looked like. 02:22.360 --> 02:33.840 So I'm going to kick off with a quick chat about AUSP, the Android open source project. 02:33.840 --> 02:38.960 So I just want to emphasize a lot of people don't think of Android as being open source, 02:38.960 --> 02:44.760 but it kind of is, though the OS in AUSP is open source. 02:44.760 --> 02:50.040 And it's what every Android device is based on. 02:50.040 --> 02:57.120 The interesting thing then is that AUSP is used by thousands, tens of thousands have 02:57.120 --> 02:58.120 developed. 02:58.120 --> 03:03.440 So there is a big community of people using AUSP, developing it, porting it, modifying 03:03.440 --> 03:05.160 it. 03:05.160 --> 03:12.920 A lot of them are working in big companies, so phones, cars, TVs, all the big names are 03:12.920 --> 03:13.920 using Android. 03:13.920 --> 03:22.720 There's also the more direct community that we're addressing here today, so people working 03:22.720 --> 03:27.800 on custom ROMs, free apps, and so on. 03:27.800 --> 03:33.680 And there's also kind of the community I kind of started out with, actually, is the 03:33.680 --> 03:41.000 community of people developing small scale what we used to call embedded Android products. 03:41.000 --> 03:44.920 So you find Android in all kinds of interesting things. 03:44.920 --> 03:50.960 The bottom there it says, gym equipment, so Palatone use Android in there, in their machines, 03:50.960 --> 03:57.320 apparently, point of sale, digital advertising, tons and tons of stuff. 03:57.320 --> 04:02.960 So Android is everywhere. 04:02.960 --> 04:07.480 So I haven't said the scene, what about Android and Google? 04:08.040 --> 04:13.520 So the good news is, Google found the development of AUSP. 04:13.520 --> 04:17.240 Ooh, so that's a good thing. 04:17.240 --> 04:25.360 The bad news is that they have complete control of the repositories. 04:25.360 --> 04:32.040 So if you want to upstream a patch to AUSP, you have to do it through Garrett, and you 04:32.040 --> 04:39.480 need to do it through the Android dev team, and as kind of tricky. 04:39.480 --> 04:44.600 So it's fair to say, I think, that Google don't encourage patches from outside of the 04:44.600 --> 04:47.040 other company. 04:47.040 --> 04:49.520 And indeed, this actually is documented. 04:49.520 --> 04:56.440 And you Rubin, who is the founder of Android, has his quote, he says, open source is different 04:56.440 --> 04:59.040 from a community driven project. 04:59.040 --> 05:01.840 We're light on community. 05:01.840 --> 05:05.560 And that pretty much sums it up. 05:05.560 --> 05:11.320 So Palatone, what we're here for is to put the community back into AUSP, and we'll come 05:11.320 --> 05:19.040 back to that again in a couple of slides of time. 05:19.040 --> 05:25.440 I just want to document a couple of things that have been happening with AUSP over the last 05:25.440 --> 05:26.640 year. 05:26.640 --> 05:35.280 So it's fair to say that from a community aspect, 2025 was not a good year for AUSP. 05:35.280 --> 05:41.640 So I've highlighted a few things, and remain will also go into a couple of things as well. 05:41.640 --> 05:46.800 But the first thing that happened back in March, no more main branch. 05:46.800 --> 05:55.840 So there used to be a main branch for AUSP, and that had updates pushed to it throughout 05:55.840 --> 05:56.840 the year. 05:56.840 --> 06:02.840 And in particular, there were a bunch of projects that were AUSP first, in other words, 06:02.840 --> 06:06.960 they were developed on the main branch of AUSP. 06:06.960 --> 06:12.640 So Bionic, Bluetooth, cuttlefish, and a bunch of others. 06:12.640 --> 06:14.200 Unfortunately, that is all gone now. 06:14.200 --> 06:17.840 All of that is done now on the private branch. 06:17.840 --> 06:24.960 And it is then pushed to the public branches from time to time. 06:25.040 --> 06:30.440 We'll talk about exactly what times in the next slide. 06:30.440 --> 06:33.760 So that was a bit of a blow. 06:33.760 --> 06:43.200 June, when Android 16 was released, we noticed that the support for pixel devices was missing. 06:43.200 --> 06:48.880 So if you look in the devices directory of AUSP now, all the pixel stuff has gone, there 06:48.880 --> 06:56.760 was really just the emulators, cuttlefish and goldfish, and some dev boards, so the K-dass 06:56.760 --> 07:04.440 VIM, VIII, and a couple of corecom boards supported by Lenovo are still there. 07:04.440 --> 07:06.720 Apart from that, it's all gone. 07:06.720 --> 07:12.440 As a real pain, because even if you weren't developing directly to run on pixel, it was 07:12.440 --> 07:18.320 really nice to have the configuration that's a Google account with to see this is how 07:18.360 --> 07:22.960 you should configure Android for a real device. 07:22.960 --> 07:31.960 So we no longer have that. 07:31.960 --> 07:37.560 And then in July and in January, they clarified a little bit as to exactly when they're 07:37.560 --> 07:42.640 going to be pushing their internal branches to the public service. 07:42.640 --> 07:50.480 So initially they said it will be on every QPR, every quarterly platform release. 07:50.480 --> 07:53.520 They've rolled back a little bit on that. 07:53.520 --> 07:57.920 So at the start of this year, there's a banner appeared on all of the source to Android.com 07:57.920 --> 08:03.360 pages, which says effective in 2026. 08:03.360 --> 08:11.040 We will publish the source code to AUSP in QT and Q4, Q2 and Q4 only, in other words, with a major 08:11.040 --> 08:14.960 release and then with the QPR-2 release. 08:14.960 --> 08:18.960 So we only get two code drops per year now. 08:18.960 --> 08:25.600 That's a little bit sad. 08:25.600 --> 08:32.200 So this has taken a play, and we're going to come to the end of the presentation. 08:32.200 --> 08:38.960 We have some ideas as what we can do to come together as a community, and we can work 08:39.040 --> 08:47.360 with Google, but ultimately the basis that we're working on is the AUSP that we get from 08:47.360 --> 08:50.360 Google. 08:50.360 --> 08:52.160 OK, so this is what I want to say for the moment. 08:52.160 --> 09:03.720 I'm going to hand over now to remain, because you write microphones over, ignore the 09:03.720 --> 09:09.200 thing noise. 09:09.200 --> 09:14.200 We'll get better of this. 09:14.200 --> 09:21.720 Thank you, Chris. 09:21.720 --> 09:29.160 As Chris said, 2025 was not a good year for AUSP, and Android in general, in terms of open source 09:29.160 --> 09:40.160 I mean, and no less focus a bit more on application side. 09:40.160 --> 09:46.560 One of the major announcements of Google, the past year, was the Google developer registration 09:46.560 --> 09:54.440 or the silo-ding topic, or whatever we call it, so today, I mean until now you were a 09:54.440 --> 09:59.000 developer, anyone to develop an application, and to share it, or internet, and anyone 09:59.000 --> 10:03.640 was about to install, more and more with some warnings, but you were about to install, and over 10:03.640 --> 10:09.960 the past year, Google announced that from now, in order to install it easily, as a normal 10:09.960 --> 10:15.800 developer, you will have to show your identity to Google, so you'll be kind of a proof 10:15.800 --> 10:23.160 by Google to share your ATK over Android, so that's a measure shift, and kind of a bit 10:23.160 --> 10:31.000 against open source, and well, you will still be able to share an APK freely with our 10:31.000 --> 10:37.640 disregistration, but you will have even more warning than before, et cetera, so it's not 10:37.640 --> 10:43.040 so much, I will say a problem for custom homes, because custom on developer are probably 10:43.080 --> 10:49.200 can get rid of that, but if you want your application to be used by people on Google on 10:49.200 --> 10:55.400 Android, then it will become a problem. I think it's average, we made a very good blog post 10:55.400 --> 11:02.000 about this topic that you can find on the internet. The other topic, which is important 11:02.000 --> 11:11.400 about Android application in 2025, was the raise of plain integrity, plain integrity, 11:11.400 --> 11:17.160 as Chris said, AOSP is open source, but as you may know, to run your application, most of 11:17.160 --> 11:22.440 them rely on some Google components, and one of them is plain integrity, so plain integrity, 11:22.440 --> 11:29.400 the tool, as you case, at a low-app developer, to ensure the app will run only on a proved 11:29.400 --> 11:37.680 device by Google, so it works well for Google devices for sure, but it works a bit less 11:37.760 --> 11:44.000 well when it comes to run your application on a custom room. This is a problem, for example, 11:44.000 --> 11:49.120 of banking gap or some AI application, which are checking that you are running on an official 11:49.120 --> 11:56.000 Google Android. More and more developer are using plain integrity, and it becomes challenging 11:56.000 --> 12:02.800 for custom ROM to get those app working without all the Google services packages, which 12:02.880 --> 12:08.800 means that even if AOSP is open source, if you want to run all your application, becomes 12:08.800 --> 12:15.040 more and more difficult for run developer to claim that you are compatible with all applications. 12:15.760 --> 12:20.880 So that's one of the challenge, and well, at least at Mirina, the company I'm working with, 12:20.880 --> 12:26.000 we are working on this, and many others are working on this, but that's a challenge from last year. 12:26.080 --> 12:40.640 Well, time is ring, so other data for the major, I will say, custom ROM or AOSP based OS, 12:42.320 --> 12:49.200 the order is not the popularity of each, it's just in the alphabetical order. There are many 12:49.280 --> 12:55.120 others, I've put here what I feel out of both popular, there are police ROMs also, 12:55.120 --> 13:02.320 there are really many others, that's the most popular on the internet, and well, most of them 13:02.320 --> 13:07.840 over the past year moved to other with the 16, that was one of the major shift over the last year, 13:08.800 --> 13:17.760 and bring many, many other features. The good news, I spoke a bit about venues, 13:18.320 --> 13:24.880 the good news is we have way more, I will say, devices, and hardware which are compatible with 13:24.880 --> 13:31.200 non-google Android, which are released on the market. So again, I put the list here, probably 13:32.640 --> 13:39.200 there are probably many others, but at least the old brand are selling Google Android devices 13:39.200 --> 13:45.200 without Google, which is I think a good thing for open source, most of them are open source, 13:45.200 --> 13:50.960 not always, but most of them are, and at least we're not relying on Google, so that's what 13:50.960 --> 13:55.280 we can refer to, and that's only what was announced last year, and probably more to come this year. 13:59.600 --> 14:07.840 What's cooking for 26 now? We spoke about restriction from Google, they are also coming from 14:08.560 --> 14:16.880 other manufacturer, at first Samsung announced that they will kill, but they're unlocking, 14:16.880 --> 14:22.400 so but what they're unlocking is the features that allow you to unlock your device and install 14:22.400 --> 14:28.320 whatever you want. Samsung has announced that they mail my kill this feature, as well as other 14:28.320 --> 14:36.160 manufacturer did in the past, I think Xiaomi did a long ago. So well, for sure, for the community, 14:36.160 --> 14:40.320 it means that you will not be able to develop anymore and to install. There are always way to 14:40.320 --> 14:49.040 access such stuff, but it's way more complicated. Another challenge for the ecosystem is the 2G 3G 14:49.040 --> 14:57.280 shutdown. I'm not sure if you're aware of it, but most of the carrier will shut down such network 14:57.280 --> 15:04.160 in the next years. The point is if your device is not compatible today with the OLT, the voice 15:04.160 --> 15:13.120 of LTE, the voice of a 4G or 5G, you will not be able to pass a call anymore. So it means that for 15:14.560 --> 15:19.920 community developers who want to bring AOSP on the device, they have to ensure that 15:19.920 --> 15:24.880 the LTE is working otherwise in a couple of years, you will have an open source device, but you will not 15:24.880 --> 15:32.080 be able to make any call. So that's a challenge. It's well too important now, but for very 15:32.160 --> 15:36.000 old device that we are still supporting, I'm thinking for a good up all about some all some 15:36.000 --> 15:42.480 some devices at the LTE or AOSP. It will become a challenge in a broken. 15:44.080 --> 15:49.680 And that's where I will probably transition to David with the more upper hour and maybe 15:49.680 --> 15:56.480 the line driver's support, which is growing. And yes, I will switch to David for the next slide. 15:56.800 --> 15:59.840 Again, transition, sorry about the sound. 16:10.560 --> 16:17.280 Great, thank you very much for me. Thank you, Chris. Some of these challenges that we see for 16:17.280 --> 16:22.480 AOSP are also challenges for other Linux distributions, which I'm going to talk a little bit now. 16:23.440 --> 16:28.960 So so far we've talked, like, broadly speaking about AOSP, but although AOSP is, 16:29.760 --> 16:33.120 by far the most popular Linux distribution, I think it's probably fair to say, 16:33.120 --> 16:37.600 it is not the only Linux distribution that runs on mobile phones. And there are a bunch of others 16:37.600 --> 16:43.040 that you might call more, you might call mainline or mainline-esque type Linux that run on mobile 16:43.040 --> 16:46.320 phones. And that's what I'm going to talk about to the last section of this talk. 16:46.800 --> 16:53.520 And there are lots of districts, as with desktop Linux, there are lots of different distributions, 16:53.520 --> 16:57.040 desktop or laptop Linux. There are lots of distributions that run on mobile phones. 16:58.240 --> 17:02.800 It's a similar source of ecosystem in that it's there are all these different organizations that 17:02.800 --> 17:06.800 run them. And this slide captures some of those organizations. So on the left side, you can see 17:07.440 --> 17:12.080 a mixture of distributions. Some of you might be running distributions that are not in this list. 17:12.880 --> 17:15.680 Please give a shout out at the end of the questions. If you'd like to do that, 17:15.680 --> 17:20.000 but this is definitely some of them. And on the right hand side, there is a mixture between the 17:20.000 --> 17:24.720 distributions and the shells that you can run on the user interfaces. So the user interfaces might be 17:24.720 --> 17:34.480 things like Knome Shell Fosh, which are both Knome Shell and Fosh are known based user interfaces, 17:34.480 --> 17:41.120 or for example, Plasma Mobile, which is a KDE variant. And some of these distributions will work with 17:41.200 --> 17:45.120 some of the user interfaces. But some of the distributions essentially have their own user 17:45.120 --> 17:50.960 interface, which is TIE2, or semi-TIE2, the distribution, or encouraged for use. For example, 17:50.960 --> 17:56.160 with a BIN2, the user interface would be the mirroring for example. So I'm going to go through 17:56.160 --> 17:59.440 just for the last bit, some of these distributions are given up data on the sorts of things 17:59.440 --> 18:07.040 that's been happening with them over the last 12 months. So first up is Joy-Dion. Joy-Dion is a 18:07.680 --> 18:12.240 version of, as a name suggests, a version of Linux that is a mixture of both Android and 18:12.240 --> 18:18.080 Debian. So the way that works is that it is a GNOME-based Linux at the top layer. The user 18:18.080 --> 18:24.480 space is like, it's just like Linux. And the underlying parts are based on the Android drivers. 18:24.480 --> 18:29.280 So it benefits from using the Android drivers, using lip hybrid or helium, which means that it 18:29.280 --> 18:35.600 gets potentially better platform support, better support on the devices, but you still get the user 18:35.600 --> 18:40.160 experience of a Linux-based system on top. And over the last 12 months, the project has been 18:40.160 --> 18:45.280 doing well. It's had several releases. The latest one was in September, was one A1, 18:45.280 --> 18:52.640 based on Debian 4K, and GNOME 48. So it's been having a successful development year. They've introduced 18:52.640 --> 18:58.080 things like captive portal detection for when you're using Wi-Fi on a close network. 18:58.800 --> 19:03.520 M3 lock screen controls for controlling audio multimedia apps from the lock screen 19:03.840 --> 19:08.080 phone, which is a genuine quality of life improvement for end users, at least that's certainly my 19:08.080 --> 19:14.800 experience. And also updating way-droid, which allows the Android apps to run within the Linux environment 19:14.800 --> 19:21.520 to Android 13. So a good year for joining. I'm doing these in alphabetical order, but actually 19:21.520 --> 19:27.680 there's a bit of a link here. FuryLab is an organization that was set up to cell phones with Linux 19:27.840 --> 19:34.160 installed on them. And their version of Linux is called Furious, Furious, Furious. It's kind of neat. 19:35.280 --> 19:41.040 And their objective was to, they tie the hardware with the software. So you buy the hardware 19:41.040 --> 19:45.440 and you get the operating system with it. And their objective was to make one release per month during 19:45.440 --> 19:50.480 last 12 months. And there was your phone, the FLX-1 was released. Maybe about 18 months ago, 19:50.480 --> 19:55.280 it was a big deal at Boston last year, but it's a relatively new thing. And it has they have 19:55.280 --> 20:00.640 broadly speaking achieved to get a release out every month. So really, a really good result for Furious 20:00.640 --> 20:05.520 and Furry Labs. They've had some hardware issues. As I understand, at the FLX-1, they can no longer 20:06.240 --> 20:10.640 they can no longer source, so they are moving to the FLX-S, the slim version, which is slightly 20:10.640 --> 20:16.000 different hardware design. I've just had to look at it downstairs. They have a standard UD2. So if you 20:16.000 --> 20:19.920 want to have a look, don't do it today, because you're in here today, tomorrow, go to the stand 20:19.920 --> 20:24.720 and have a look at the Furious, the Furry Labs device. It's really nice. It has kill switches on the side, 20:24.720 --> 20:29.120 which is an upgrade from the original version, and it has more RAM, but it also has some 20:29.840 --> 20:34.480 aspects, which are not quite as good as the FLX-1. The screen is not quite as good, for example. 20:34.480 --> 20:38.640 So it's more recycled than an upgrade, but it's a really nice device and worth having a look at. 20:40.320 --> 20:45.360 Their user interface is based on Foch, which was the GNOME-based user interface that was developed 20:45.360 --> 20:51.680 by Purism and is a community effort and it's being developed quite extensively. So that's Furry Labs. 20:52.640 --> 20:59.680 Next up is Mobion. So Mobion is a dubion variant, so like-droidion, but it is a mainline-linx variant. 20:59.680 --> 21:04.720 So that means that it is designed, the changes that are required to get it running on the 21:04.720 --> 21:10.480 devices are pushed upstream to be used in the main-linx kernel. They do also have some releases that 21:10.480 --> 21:16.480 run on lipide-riss and hellium as well, but they've also had multiple releases during the 21:16.480 --> 21:22.800 year, so they recently moved to Mobion Tricksie in October that upgraded to Foch 46 and Plasma 21:22.800 --> 21:28.960 Mobile 63, so the product is bubbling along nicely and progressing. Hardware support, there are 21:28.960 --> 21:33.360 a few devices which it runs on, which are officially supported. If you want to give it a try, you can 21:33.360 --> 21:40.400 download it, and we do have some Mobion variants on the Linux or Mobile stand at UD2 again tomorrow, 21:40.400 --> 21:43.440 not today, and have a look at those, if you want to give them a try. 21:44.240 --> 21:49.120 Postmark it, OS is another Linux variant, which has had a really successful year this year, 21:49.120 --> 21:55.520 it's doing really successfully, and it is a mainline-linx variant again that has a biannual release, 21:55.520 --> 21:59.840 so it has two releases a year, the most recent one was in December, and they've had a really 21:59.840 --> 22:05.360 big year, they switched, it's now plain Linux variant, they switched to using system D this year, 22:05.360 --> 22:09.840 it was a really big shift, they've had a lot of really strong development, they have an improved 22:09.840 --> 22:14.320 Firefox and Thunderbird user interface that was released over the last 12 months, and they've also 22:14.320 --> 22:20.160 managed to secure funding from NLNet for their backhand infrastructure, so a really successful, 22:20.160 --> 22:25.680 and I think as it says there, they've also got a new code of conduct team introduced, so lots of 22:25.680 --> 22:32.160 really good stuff. Okay, just a couple more to go, self-push OS, which is the system developed by 22:32.160 --> 22:38.880 Yollas, it is a development of Mimo, the old N900 devices, has had a very successful year with a 22:38.880 --> 22:44.240 you may be aware of crowdfunded device that they are putting together to call the TID, the TID, 22:44.240 --> 22:50.160 so the DIT phone, the do it together phone, and they have five releases during the last year, 22:50.960 --> 22:55.040 including improvements to app support, which is their ability to run Android on the device, 22:55.040 --> 23:00.640 they've introduced wireguards, VPN support, landscape views on more of the official apps, 23:00.640 --> 23:05.920 and things like all blocking in a whole bunch of bug fixes as well, so lots of changes. 23:06.800 --> 23:11.040 And then finally, I've been to touch, so this is the development of the original 23:11.040 --> 23:15.440 Ubuntu touch released by Canonical, which can be called dropped, but the community picked up, 23:15.440 --> 23:19.360 and it has been developing very successfully, it's based on the Lumeree user interface, 23:19.360 --> 23:25.920 which you may be familiar with, as you may be familiar with it, when using the term Unity, 23:25.920 --> 23:30.720 so it was the original Unity interface that has become this, and they have been adding 23:30.720 --> 23:35.520 voltage support to various devices, we've heard about the 2D3D switch-off, and the voltage support 23:35.520 --> 23:40.240 is aimed to provide a solution to that, and they've also had other improvements like three 23:40.240 --> 23:45.040 theme improvements, improved personal data encryption and things like that. 23:45.040 --> 23:49.760 So all these projects, you can see there's a whole band of them, they're all charging along really 23:49.760 --> 23:53.600 well and developing very successfully. There are a whole load of others, which I'm not going to 23:53.600 --> 23:58.800 talk about, but which you can have a look at if you want too many to speak of, but maybe it's all 23:58.800 --> 24:03.440 Linux, so maybe you want to develop your own version or something for it, and you'll come back 24:03.440 --> 24:06.960 to the DevRum next year and do that, and we would welcome that very, very much. 24:08.160 --> 24:11.920 All right, so that's kind of landscape of mobile in it, so I'm just going to hand back 24:11.920 --> 24:15.600 now over to remain for, sorry, to Chris to wrap things up, I could pump. 24:16.160 --> 24:20.160 If I can get this off, there we go. 24:22.400 --> 24:28.000 Okay, so just to finish off then on what's, hopefully, some of the positive notes. 24:29.280 --> 24:35.440 So the thing we have here at particular FOS then, is a community. 24:36.240 --> 24:42.800 So if the corporates are not doing everything, then we can come together and we can make things happen. 24:42.800 --> 24:48.960 So three bullet points, share and coordinate, promote community efforts, pull resources. 24:49.840 --> 24:54.320 That is the essence of FOS then. And then finally, 24:57.760 --> 25:03.600 particularly what we're doing about creating communities, so I wanted to do a quick shout out for 25:03.600 --> 25:09.920 ASP Devs, which we are putting together a community for ASP developers, hence the name. 25:10.880 --> 25:16.240 There's also the Meetup, the ASP and the ASM Meetup that I run every two months. 25:18.640 --> 25:26.800 There's the Keep Android Open project page, which is, there's what it says. 25:26.800 --> 25:32.160 It is lobbying people to keep Android open source. 25:33.120 --> 25:43.600 And then Linux and Mobile, LinMob is a generic project, which aims to pull a lot of resource for all of the 25:44.400 --> 25:51.760 Linux-based mobile devices that David was just talking about. So take a picture of this, click on those links, 25:52.560 --> 26:00.000 this is how we create community. We're kind of at a time, I think if anybody has questions and I'm 26:00.000 --> 26:04.000 sure there's lots of questions raised from all of that, we're going to have to take this either 26:04.000 --> 26:12.400 offline in the corridor track or, of course, you can always put post questions on the chat for 26:12.400 --> 26:18.800 the FOS and Mobile Devs. But thank you very much and that's me down for the moment.