I've decided that it's finally time to retire my iPhone 6S, largely because it sometimes just decides not to vibrate when notifications come in. This has actually been happening for a long time but I had convinced myself I was just spacing out. Pretty sure it's actually broken.

I'm unhappy enough with Apple that I want out of their ecosystem, and it's not like Google is better. I've got a PinePhone but it's not gonna cut it, so I am looking into devices I can put LineageOS / microG on.

I have to try to divine:
* Which devices are well supported by LineageOS
* Which devices will continue to be well supported by LineageOS
* Which devices have strong enough specs that they will perform well as software inevitably gets more bloated over the years I will own the phone
* Which devices are actually attainable locally at reasonable cost

I'm in hell.

Finally pulled the trigger and bought a Samsung Galaxy S10, because they are plentiful, relatively inexpensive, reasonably powerful, and supported by LineageOS.

Went to follow the installation instructions and the button to unlock the bootloader just... isn't there.

Apparently the North American models are basically unhackable. But the wiki doesn't tell you that.

This fuckin' sucks.

There are a million videos and articles online that suggest that maybe, if you set your clock back 7 days or 3 months and wave a dead chicken over it, the button will magically appear. This has not worked for me.

Bought a OnePlus 8 Pro. Verified before paying that I was able to unlock the bootloader. Got it home, looked at the LineageOS instructions, and apparently my model is the IN2021 and only the IN2020, IN2023, and IN2025 are officially supported. I reiterate: I am in hell. Why am I doing this to myself.

A quick search suggests that people are definitely using LineageOS with this particular device anyway so it's probably only not listed because the maintainer can't test on it or something. But.

I installed LineageOS anyway. It went smoothly. The settings screen now claims my phone's model is IN2023. OK. Sure. IN2025 is the North American model number so who knows. Haven't run into any problems yet, everything seems to be running smoothly. This world of alternative Android is weird but I am acclimatizing.

Spent virtually the entire day yesterday setting up my new phone. I'm pretty pleased. There's a nice ecosystem of open source replacements for virtually everything I use that's not obviously a proprietary service. I can set up the rest with the Aurora Play Store client. The only thing that sucks is that my bank's app won't start. I assume this is because it relies on Google SafetyNet.

Feeling, for perhaps the first time, like if there was something about my phone that I didn't like, that I could do something about it. It feels really good.

I was honestly not expecting to feel that way. I spent like five years writing Android and iOS apps professionally. I never felt that way about my iPhone. I stopped jailbreaking my iPhones years and years ago because it didn't feel like there was any point.

Self-hosting my own UnifiedPush server was rather more work than I expected, but in the end I think I was able to setup NextPush. Configuring the Android end of things was really slick, as it talks to the NextCloud app to fetch my credentials, server URL, etc. Interact with this post so I can see if it's really working!

Surprised to discover that Android 11 doesn't support mDNS (automatic zero-configuration hostnames like raspberrypi.local). I thought that was table stakes these days. Sounds like Android 12 finally added support though.

oh. my bank app not working on an unlocked phone might be a pretty significant roadblock, because my bank does 2fa through their mobile app, and once you turn on 2fa, you cannot turn it off, ever. If you lose your phone you can temporarily turn it off but you still can't login to web banking until you've installed it on a new phone and logged in with it.

so uh.

gonna have to call someone to get that sorted out, it would seem.

@SpindleyQ what specific security threat exactly are they worried about from unlocked phones here?


@jplebreton who knows? I'm not even entirely certain that's why it doesn't work, the error message is just "Sorry, something went wrong. Please uninstall the Scotia app and visit Google Play to install it again."

I do know that Google provides an API called SafetyNet, where it does a bunch of checks to verify the program and the phone haven't been tampered with. Of course an unlocked bootloader running non-Googled Android flunks this test by definition.

Sign in to participate in the conversation

Hi! Game Making Social is a part of the Fediverse dedicated to being a well-moderated, cosy, friendly place to talk and share stuff about amateur videogame making, and everything surrounding that.