u/TimSchumi

Just trying if you can install GMS now (after the fact) probably won't break more than what is already broken anyway.

Well, it's about 170 devices that get queued on one day, one build takes around one hour, and we have around 5 build servers I think (and I'm not sure if all of them are set up to build LineageOS 24). So for build time alone that's already 34 hours, more than one day.

It's "available" in the sense that it's not unsupported anymore, but you can't obtain any builds for that particular device yet because the build servers are churning through ~170 devices at the moment, and it will take a day or two to show up.

I don't think the updater will allow you to do a major upgrade, for exactly that reason.

Having a common kernel does not mean that someone immediately can or has put it to use.

No issues with eSIM here, other than that some carrier apps may refuse to run due to Play Integrity.

At most you could actually try to boot into safe mode (there is a key combination somewhere) and then try to undo as much as possible.

If that doesn't work, then it will probably be a factory reset (or, if you want to try that at first, the "delete app data" button), and I don't think the service center would be able to do anything else either.

App developers' discretion.

Find an external link to the app and click on it. It may be possible that they just don't want you to install the app on Waydroid, which would show as "app not compatible".

I took some time to get back to this, reddit decided that my account was not human and I needed to be home to verify it first.

I'll have to say upfront that a lot of the ports DNA is still from Immirs version of it, or at least the parts that ended up in the upstream Angband source tree. It featured a lot more customization than my version does (dual screen, runtime-editable screen keys, etc.), the "place custom buttons anywhere" was just a stopgap to have any kind of usable experience.

I currently don't have any plans to continue development of original NDS-specific features, unfortunately.

But regardless, I'm happy to hear that you have this much fun with the port as-is.

Generally, using the intended build system is very helpful when trying to debug the intended build system.

Ok, so let's play that game.

• Where is the setting stored?
• Does the settings app have access to it?
• Does the QS tile have access to it?
• Should the setting even be accessible in the settings app, or should it be somewhere else?
• Can we even skip the dialog without impacting functionality if we don't refactor the code first?
• Will that approach still work after Google inevitably decides to rework yet another UI component?
• Who makes sure that everything works when coming from an older minor version?
• Who makes sure that everything works when coming from an older major version?

Maybe it's too long because you blew everything up into full-page sections and then pasted everything twice at that.

Following the steps in the wiki is the only supported way of installing LineageOS.

Possible certainly, but someone still has to create a build matching the device.

Maybe.

Feel free to fix it.

What you are essentially asking is "Why does Android 13 run slower than Android 8?".

Dragonball: Trunks is a fucking dumbass - An edit of a dragon ball scene where the character Trunks tries to throw his sword in the air and have it land in his scabbard. In the original show, this succeeds. The more widely known edit makes him completely fuck it up (like a dumbass)

I feel like this applies to DBZA as well in general.

They have threatened in the past to relicense their code and to then go after anyone using it that they do not like, and we don't really want to play that game.

As long as they are not based on GrapheneOS code, and we don't have to do any more than reviewing incoming patches and merge them once they are fine, then sure?

Wat?

Obviously.

Can't just throw away all the other data, can you?

Because then you'd just be back asking "Why have LineageOS and Android so many files?".