If you're already using a Pixel, why base your custom image on LineageOS as opposed to GrapheneOS? (I might actually be interested in a GrapheneOS-based build.)
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.<p>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?
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?
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".
Compiled android once ~10 years ago, remember it taking at least half a day. Really helped me appreciate how many things go into it.
android-latest-release branch (Android 16 QPR2) for lunch target aosp_cf_x86_64_phone-trunk_staging-eng (Cuttlefish emulator):<p>> du -hs --exclude /aosp/android-latest-release/out /aosp/android-latest-release<p>132G /aosp/android-latest-release<p>> du -hs /aosp/android-latest-release/out<p>127G /aosp/android-latest-release/out<p>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.
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.
Android build system is a heavy Rube Goldberg machine, it's amazing it even works at all
Building Android is heavy, and so is Chrome.
Android uses like 7 build systems and repo is like 50 submodules deep.
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.<p><a href="https://medium.com/@jnebos/the-humble-android-calculator-4f139e8b1699" rel="nofollow">https://medium.com/@jnebos/the-humble-android-calculator-4f1...</a><p>Second, the kernel itself presents attack surfaces. It is important to accept updates, when they are offered.
> Create a stripped-down "dumbphone" version of LineageOS for your Google Pixel without giving up the camera quality and touchscreen of a smartphone.<p>Dumb interface for smartphones, unrelated to dumbphones. Not that it was likely to be anything else. Pretty neat.
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.
> What will not work when using a phone running this build?<p>> RCS messaging<p>> (The points above apply to any phone with an unlocked bootloader, including ones running official LineageOS builds)<p>RCS really depends on attestation now? What the fuck?
Unsure about details, but it must at least not require Google Play attestation because Graphene supports it now
RCS also goes through Google servers. I don't see much point in using it.