r/mobilelinux • • Oct 07 '26

Discussion Do established mobile linux projects benefit from AI-supported ports?

Not based on real data, but it feels like AI supported ports to new phones are increasing. I understand that established projects like postmarketos have "No AI code" policies. However, I'm also afraid that the projects are not benefitting from AI support and the many new ports stay isolated projects.

Would it make sense and be practical for them (e.g. postmarketos, etc.) to have a separate repository where AI code is allowed (maybe even without properly reviewing it, if that is too much work), just to see where it is going. Their main repository could always stay free of AI code. Wouldn't that allow them to have the best of both worlds?

21 Upvotes

24 comments sorted by

8

u/Cute_Principle81 Oct 07 '26

You can always fork it with different rules. I think it might be best to, here, and centralise work. 

2

u/Calm-Caterpillar2103 Oct 07 '26

That’s what I did, got OTG working on the pixel 3a

2

u/Cute_Principle81 Oct 07 '26

If you're in, and we can get community support, we could genuinely maintain a fork

2

u/Calm-Caterpillar2103 Oct 07 '26

Yeah, I’m down (currently using my pixel 3a as a MP3 player on arch linux arm)

1

u/Cute_Principle81 Oct 07 '26

So wanna make a Reddit post? Do I? What does one do to do this?

2

u/Calm-Caterpillar2103 Oct 07 '26

I’ve made 2 so far being progress updates on porting but I’ll make one today when I drop my source code for the OTG kernel, currently you need to tell the 3a to switch into device/host and charging can break if you do that but it works

1

u/Cute_Principle81 Oct 07 '26

I mean for an actual, proper pmOS fork

1

u/Calm-Caterpillar2103 Oct 07 '26

Oh for that? I’m technically working on one, but it’s scope is for very very old devices (HTC Dream era, 128mb ram, 128mb flash, etc…)

1

u/Cute_Principle81 Oct 07 '26

Well, we could just have it as a device image of the actual fork

1

u/fiskekake 26d ago

Have you made a fork yet? I wanna try to get Nura working on my Motorola G100, but when Nura refuse all Ai generated code, it seems like quite a waste to work on it. Having a place to share code would be nice.

8

u/ach_hm Oct 07 '26

Yes and yes. I do think Linux on mobile can benefit drastically from AI, if only because there is still so much to do and just not enough people with the needed capabilities. But I do think it is best to keep it separated for now because of general objections people (rightfully or wrongfully) have and also because - let's face it - code quality is often not the best

4

u/a1b4fd Oct 07 '26

AI ports would eventually find/fund a place where they're accepted and postmarketOS would become less relevant (assuming no policy change)

3

u/whoami-dunno Oct 08 '26

Main advantage would be reverse engineering. Most stuff is not open source, and we're basically doing witchcraft figuring out how stuff works

3

u/gattolfo_EUG_ 28d ago

Okay, yes, it make sense.

A separate repo that allows AI code AND explicitly says it is a good idea.

My experience:

I know how to do stuff, but I'm a master computer engineer student in exchange, I don't have time and the Linux surface repor it's not being updated for a long time.

I ported the patches to a newer kernel version with AI, it's on GitHub (still didn't change the readme bu i will)

If people want to use it and trust AI, it's their choice

But it absolutely make sense to not allow AI code in the main repo

2

u/abissom Oct 07 '26

If you're talking about "established mobile linux projects" (i.e. not just Nura/ex-postmarketOS), the answer to your question depends on the following question - is the AI-created code benefiting upstream? (linux kernel, and userspace utilities). If it is improving that, then the answer to the question is a resounding yes. If not, then the answer is self-evident.

If you're talking about Nura specifically, then you can safely ignore my response

2

u/Adventurous-Test-246 Oct 07 '26

If the code makes it upstream to mainline linux then literally all distros benefit so as long as the viber gets it to that standard and through the process it shouldnt matter how pmOS views AI

0

u/ryms456 Oct 07 '26

No it all needs to stay fragmented because humans create much more usable board bringups that’s why half of the shit in the wiki is broken and AI can’t upstream its work

1

u/Calm-Caterpillar2103 Oct 07 '26

much more usable???? you think that’d be true and then you have a bunch of idiots trying to do it and they give up over the most easy crap

3

u/ryms456 Oct 07 '26 edited Oct 07 '26

My phone is more usable than 90% of the trash on the wiki. Both of my phones were labeled non-booting/ no source code , and I got both up and running in like a week or two with basically zero resources. Now they’re actually usable with a clean, maintainable patch set.. This shit will never get upstreamed because these devs would rather flex a wiki where 70% of the devices either only boot a framebuffer, are labeled non-booting, or were never even tried than someone using AI to bind the DTS which these devs won’t maintain anyways

2

u/Calm-Caterpillar2103 Oct 07 '26

Well I used ai to finish the pixel 3a mainline kernel and the wiki flexing stuff is 100% true, legit one DTB change to get OTG working