this post was submitted on 04 May 2024
289 points (95.6% liked)

Technology

59080 readers
4093 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
289
No, you don't need a 'very bespoke AOSP' to turn your phone into a Rabbit R1 — here's proof (www.androidauthority.com)
submitted 6 months ago by AnActOfCreation@programming.dev to c/technology@lemmy.world
51 comments fedilink hide all child comments
 
  • Rabbit R1, AI gadget, runs on Android app, not requiring "very bespoke AOSP" firmware as claimed by Rabbit.
  • Rabbit R1 launcher app can run on existing Android phones, not needing system-level permissions for core functionality.
  • Rabbit R1 firmware analysis shows minimal modifications to standard AOSP, contradicting claims of custom hardware necessity by Rabbit.
you are viewing a single comment's thread
view the rest of the comments
[–] MargotRobbie@lemmy.world 33 points 6 months ago (1 children)

Technically, every Android phone uses a "very bespoke AOSP", because the Android kernel is customized for the hardware of every single phone model, which can include things like hardware drivers and carrier services.

This is the reason that there is no universal Android ROM that works across every Android phone, unlike Windows or normal GNU/Linux distributions.

[–] Kolanaki@yiffit.net 3 points 6 months ago* (last edited 6 months ago) (2 children)

What about custom ROMs like Lineage? The only thing holding it back from working on every phone is that many phones have blocks to prevent installing a custom ROM in the first place. Could be just like windows in that it has every driver for every piece of hardware in the package, just bloating it unnecessarily.

[–] MargotRobbie@lemmy.world 13 points 6 months ago

The manufacturer has to release the phone's kernel source code before any custom ROM development can happen for the phone most of the time for that reason.

There is a reason that GrapheneOS only works on a couple of Pixel phones.

Could be just like windows in that it has every driver for every piece of hardware in the package, just bloating it unnecessarily.

Google specifically designed the Android kernel so that the driver are excluded, unlike the normal Linux or Windows kernel, because, long story short, Qualcomm did not want it to happen.

[–] madscience@lemmy.world 6 points 6 months ago (1 children)

Every device had it's own device tree and kernel with custom driver's, binary blinds, and system software. All of it runs beside the closed source modern os

[–] balder1991@lemmy.world 2 points 6 months ago* (last edited 6 months ago) (1 children)

I’m not entirely sure because I’m not very knowledgeable about CPUs, but it seems this is largely a problem with ARM architectures and their lack of standardization, isn’t it?

[–] madscience@lemmy.world 7 points 6 months ago

There's nothing like uefi between the os and the hardware