315
Native Linux is coming to our phones much more easily (Xiaomi Mi Max 2) (thelemmy.club)
submitted 2 days ago by to c/linux@lemmy.ml
77 comments fedilink hide all child comments
 

AI can speed up a lot of the manual labour needed to bring even an almost dead, 10-year-old device back to life. My Xiaomi Mi Max 2 (oxygen, MSM8953) was dead. With AI help and my own knowledge, I ported/rewrote the missing drivers, and it now runs Nura (postmarketOS) with working camera, torch, SIM, phone calls and SMS. Only the loudspeaker is still broken.

Everything is up for anyone who wants to install it, or to understand the changes and manually write the patches for mainline: https://github.com/sv1sjp/mi-max2-oxygen-msm8953-nura-drivers Testing, feedback and PRs welcome.

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 2 days ago* (last edited 2 days ago) (8 children)

It’s literally the first sentence of their policy.

Yes, but what about the 2nd sentence?

The following is not allowed in Nura:

  • Submitting contributions fully or in part created by generative AI tools to Nura.
  • Recommending generative AI tools to other community members for solving problems in the Nura space.

As you can see, it says nothing about researching, troubleshooting, reverse-engineering, etc. As long as you write and understand the code yourself AI is allowed for everything else. As long as you're not using generative AI it's fine.

Citation needed.

My personal experience working with AI over the past year. And if that's not enough, here's also Linus Torvalds himself.

The arguments regarding resource use and profiting off of theft are valid. The arguments regarding the nature and capabilities of the tech are not. Developers ARE responsible for the code they submit, regardless of how it was created.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 3 points 1 day ago* (1 child)

    As you can see, it says nothing about researching, troubleshooting, reverse-engineering, etc. As long as you write and understand the code yourself AI is allowed for everything else. As long as you’re not using generative AI it’s fine.

    I'm not sure if you're joking or legitimately confused, but, assuming the latter, fyi the "AI" that people use for "researching, troubleshooting, reverse-engineering, etc" is part of what is called "generative AI". Given this, it's not much a stretch to read it as saying that even posting in Nura forums about the existence of @sv1sjp@lemmy.world's github repo would actually be a violation of Nura's policy (as of today; I expect it will evolve in the not-too-distant future).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] -3 points 2 days ago* (last edited 2 days ago) (5 children)

    It's not a good tool for research, it will just generate a hallucination and you end up doing something which does not work or just works somehow, but is not done correctly and will break in the future.

    I talked to quite a few people recently at the postmarketOS and Alpine Linux conference, it definitely was noticed that more contributions are now coming in that do things wrong or in a subtly broken way and the submitting people have no clue.

    If you rely on a lying computer for research, then your code will lie to you.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 7 points 1 day ago

    I've used AI for low level debugging on things that are basically undocumented to fix my personal machines, doesn't eliminate the trial and error process but it's gotten me farther a lot faster than if I were to do it on my own.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 7 points 2 days ago* (3 children)

    I rely on it to scour the docs, the forums, the codebases for any and all potential solutions and neatly present them to me. I then validate and evaluate myself. Just going with the first thing the AI suggests is lunacy and is exactly what I meant by "people are still discovering best practices".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] -5 points 2 days ago* (last edited 1 day ago) (2 children)

    Or just use Ecosia or DuckDuckGo.

    A search engine finds you places to look at and doesn't hallucinate incorrect details.

    I know it's perfectly possible to do mainlining of a device and work on the kernel stuff simply by reading stuff, asking people and bouncing ideas while strengthening the community in the process and having fun with other phone hackers.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 2 days ago*

    Unless you're doing something extremely common with well-established patterns, search engines have sucked for the past 14 years and been unusable for the past 8. For most of that time I would just refer to official docs, and official code examples, avoiding stackoverflow and other forums since they were just filled with outdated or plain bad info.

    Search engines like Kagi might still be decent, but they are few.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 5 points 2 days ago

    Υes good luck finding solutions with closed source drivers by using only Search Engines and not at the end of the day...reverse engineering... I mean, technically feasible, but I cannot understand why we skip the HUGE AMOUNTS OF TIME that this kind of work needs to be done. And expertise.

    The repository is here with an auto-installer script for anyone interested, the research is here for anyone to study and try to manually implement them to main-line. That's the beauty of open source.

    All in all, The device is alive again, so I would need to consume less new electronic devices in the feature so I will protect more the planet with not needing a new phone/smallserver than some data centers that I do not control!

  • permalink
  • fedilink
  • source
  • parent