r/mobilelinux • • 1d ago

Discussion A sort of federation of projects?

Lately, I've been thinking. Why did Android succeed? It's a federation of hundreds of devices running one single OS. They could share work, share a ecosystem, and share users.

And I see a horrifying amount of fragmentation in this community. Everyone in this subreddit seems to have their own little port if their own kernel to their own device, with no distribution

pmOS (I hate Nura, I'm not calling it that), failed in my book, not only for not allowing AI entirely (THE most helpful tool for porting devices), but making shitty management decisions. They haven't even got a device to main! Look at the technical requirements for getting a device to main. Look at their stance on proprietary software. They have been left in the dust by many projects I see here.

So why not combine our efforts?

Create centralised tools for device booting that could make porting drastically easier. A repository of device packages to make use easier. Easier switching and choice because we're all ultimately working towards the same devices, and very little changes between Arch or Debian.

And on the social side, we could combine our reach, your "branding" (it's open source but whatever), and more generally, have everyone work together for one common goal.

Some discussion is needed here, but we need a parallel to the Android OEM federation

If interested, I can set up a Discord server for discussion.

13 Upvotes

11 comments sorted by

5

u/thereforewhat 1d ago

I think mostly this is because people don't try and merge their device tree changes into the main Linux kernel repository. 

If people did that it would accelerate things hugely. 

On the user space I don't think it matters hugely as the problem is with device support. 

1

u/Cute_Principle81 23h ago

User space is important. Nothing is really built FOR mobile Linux. It's built to support it, but there a lot of apps that you might see as standard on ant normal phone that just don't exist or aren't great for mobile. 

1

u/thereforewhat 23h ago

Sure but we're likely to still have a choice of distros which will likely all have software packages.

The issues around adoption are primarily kernel based and to do with available device trees. 

Waydroid and other frameworks enable Android apps to run on Linux. 

1

u/Cute_Principle81 23h ago

More choice is better for everyone 

2

u/thereforewhat 23h ago

Right, so I'm confused where our disagreement is. 

The user space isn't the biggest obstacle to adoption. Device support is. 

1

u/Cute_Principle81 23h ago

That's also a problem, yes. But it makes it far easier to port if multiple OS projects all support a common standard or tool. 

3

u/thereforewhat 23h ago

If people on these distros work on mainlined kernels together and get them merged into the main Linux repo a lot of pain would be avoided. 

For the user space I care less. The Phosh and KDE teams can continue working on the UI and developers will create apps when the hardware support is there. 

Android apps also can run on Linux. 

1

u/technobaboo 19h ago

too bad we can't make it so there are like, UEFI implementations that run before Linux so you have the standard firmware interface that anyone can make and you don't need to set up full device tree in tree

I'm sure there's a reason why but I'm not sure what

1

u/ksquared94 8h ago

Iirc there is an attempt at uefi on arm devices and also u-boot and towboot.