upvote
MiniageOS: "Dumbphone" Version of LineageOS

(github.com)

33 points

by ashenke2 days ago |
19 comments
upvoteby dwedge1 hours ago|
next
[-]
This is an interesting concept but I think the dumbphone aspect will make people expect something different. It seems like it's more a static digital minimalism setup that you cannot easily undo. I saw someone doing similar by setting up MDM for their iPhone so you couldn't install anything without sending updates from a laptop.

I prefer the MiniageOS method if it's quick enough to refresh when needed. When you say banking isn't supported, I have a couple of banking apps that work on my two phones (AOSP and Graphene), would those still work? There are also a lot of apps that kind of rely on a browser being available even if not accessible (Uber is one but that doesn't work without Google play so whatever, but WiFi captive portals are another). Is there support for that?

reply
upvoteby 4thguy2 days ago|
prev|
next
[-]
As I read down the readme, I kept saying to myself "ok, that's reasonable," right up until I saw the 300GB free space requirement to build the image. Is that really what is needed to build an image for a phone or is this a one-off?
reply
upvoteby yjftsjthsd-h3 hours ago|
parent|
next
[-]
My understanding is that yes Android build requirements are... significant. Given that a gentoo system can self-host in like <10% of that space, I am somewhat mystified how it got here, but yes that's "normal".
reply
upvoteby tripdout2 hours ago|
parent|
prev|
next
[-]
android-latest-release branch (Android 16 QPR2) for lunch target aosp_cf_x86_64_phone-trunk_staging-eng (Cuttlefish emulator):

> du -hs --exclude /aosp/android-latest-release/out /aosp/android-latest-release

132G /aosp/android-latest-release

> du -hs /aosp/android-latest-release/out

127G /aosp/android-latest-release/out

So ~130GB each for the compiled artifacts and the source code. It's heavy, and at times can easily fill 64GB of RAM during the build.

reply
upvoteby nrclark3 hours ago|
parent|
prev|
next
[-]
Yes, that's normal for an Android build. Maybe even on the lightweight side as far as build requirements. I agree that it's an absurd about of space.
reply
upvoteby em3rgent0rdr1 hours ago|
parent|
prev|
next
[-]
Compiled android once ~10 years ago, remember it taking at least half a day. Really helped me appreciate how many things go into it.
reply
upvoteby 1 hours ago|
parent|
prev|
next
[-]
deleted
reply
upvoteby realusername2 hours ago|
parent|
prev|
next
[-]
Android build system is a heavy Rube Goldberg machine, it's amazing it even works at all
reply
upvoteby trollbridge3 hours ago|
parent|
prev|
next
[-]
Building Android is heavy, and so is Chrome.
reply
upvoteby exe342 hours ago|
parent|
prev|
[-]
Android uses like 7 build systems and repo is like 50 submodules deep.
reply
upvoteby chasil2 hours ago|
prev|
next
[-]
First of all, did you disable the calculator? This app is an amazing feat of intellect, and should be retained due to its fundamental worth of ingenuity.

https://medium.com/@jnebos/the-humble-android-calculator-4f1...

Second, the kernel itself presents attack surfaces. It is important to accept updates, when they are offered.

reply
upvoteby codethief1 hours ago|
prev|
next
[-]
If you're already using a Pixel, why base your custom, very much stripped down version of Android on LineageOS as opposed to GrapheneOS? From a security perspective, that's insanity.

(I would actually love to see a GrapheneOS-based version of this!)

reply
upvoteby a962 days ago|
prev|
next
[-]
> Create a stripped-down "dumbphone" version of LineageOS for your Google Pixel without giving up the camera quality and touchscreen of a smartphone.

Dumb interface for smartphones, unrelated to dumbphones. Not that it was likely to be anything else. Pretty neat.

reply
upvoteby iAMkenough3 hours ago|
parent|
[-]
What in your mind makes a dumbphone a dumbphone? I see many for sale with cameras and touchscreens, even app support.
reply
upvoteby dwedge1 hours ago|
parent|
[-]
Do you mean the ones running KaiOS? I'm not sure I'd count those as dumbphones they're only dumb because they have limited apps due to popularity (WhatsApp was there but left) and they often have the nokia style design (some with t7). In my opinion a dumb phone is one that might support internet but can't do anything with it except potentially hotspot
reply
upvoteby iAMkenough1 hours ago|
parent|
[-]
I’m not sure. From the few articles I’ve now read today, I see there’s a LightOS and WiseOS too.
reply
upvoteby tomashubelbauer2 hours ago|
prev|
next
[-]
I thought this was going to be an OS for actual dumbphones. Had me hoping I would have a reason to dig out my childhood Sony Ericsson W810.
reply
upvoteby LoganDark2 days ago|
prev|
[-]
> What will not work when using a phone running this build?

> RCS messaging

> (The points above apply to any phone with an unlocked bootloader, including ones running official LineageOS builds)

RCS really depends on attestation now? What the fuck?

reply
upvoteby cspeterson2 days ago|
parent|
next
[-]
Unsure about details, but it must at least not require Google Play attestation because Graphene supports it now
reply
upvoteby GreenVulpine3 hours ago|
parent|
prev|
[-]
RCS also goes through Google servers. I don't see much point in using it.
reply