The 0.18 version of Lemmy was announced. This will solve many issues.
But we can’t upgrade yet because the captcha was removed, and captcha relied on Websockets, which are removed in 0.18 so despite the devs agreeing on my request to add captcha back, this will not be until 0.18.1. Without captcha we will be overrun by bots.
Hopefully this 0.18.1 will be released soon, because another issue is that the newest version of the Jerboa app won’t work with servers older than 0.18. So if you’re on Lemmy.world, please (temporarily) use another app or the web version.
Jerboa also won’t work with Android older than 8.0 though that’s less of a problem for server ops. But it still seems like reliance on unnecessary shiny tech. My 5yo Android 7 phone still works perfectly well and I plan to keep using it a while longer, so I can’t use the official Lemmy app. I wonder how fundamental Jerboa’s dependence on Android 8 is. Anyone know?
The real crime here is that a 5yo android phone is running 7 which was released 8 years ago?
It actually came with Android 6, and the vendor shipped one upgrade, to Android 7. Hmm, it looks like the phone (Moto XT1625) was announced in 2016, so 7 years ago.
I don’t think it’s the responsibility of unpaid app developers to work around that, especially when you can probably install a somewhat recent custom ROM. I have an ancient Nexus 4 with LineageOS 18.1 (Android 11, the last version for 32bit CPUs) and that version of LineageOS is still getting updates every few months.
LineageOS doesn’t pass google’s SafetyNet, so it locks you out of a lot of banking apps, and also some other important apps.
It’s possible to run those by rooting the phone and doing some hackery to trick the app into bypassing the SafetyNet check, but that’s a race against google security features.
Besides, I gave up running LOS on my old phone and just bought a new phone with stock android 13, and Jerboa crashes on startup on it as well.
There are Magisk modules that help with those problems. Yes, it’s additional word but using ancient, unsupported, and insecure Android versions is definitively not the proper solution.
Asking users to install custom roms to browse Lemmy doesn’t seem sound a good strategy for Lemmy to beat Reddit. What I’m wondering is whether Android 8 development is somehow easier than Android 7 development. I have not looked at the source code of RedReader. Someone mentioned the existence of Reddit API emulation for Lemmy. Maybe the easiest thing is run that, and point a copy of RedReader at it.
Lineage does sound nice, but it doesn’t support my phone.
I don’t ask anything of you. You’re the one asking volunteer app developers to support your insecure ancient Android version. Installing a new version of Android is a good idea in any case but if you want to continue “resisting” just deal with apps becoming incompatible with time.
My phone came with Android 6, the vendor shipped an upgrade to Android 7, and I installed that. They didn’t release any more upgrades. The phone hardware itself is still perfectly good so I really don’t want to take part in a hardware upgrade treadmill just because the vendors like to play Wintel. I’m typing this on a laptop from 2011 (Thinkpad X220) that also still works (hasn’t fallen apart yet), running Debian 11. It won’t run the latest Windows but I don’t care.
I still haven’t heard any type of explanation what of what stops Jerboa from working with older Androids. If it would take a total rewrite then I can understand the devs not wanting to do that. If it means changing a #define then I’d say change the #define. As a general matter I find Lemmy’s web design to be bloatier and more annoying than old.reddit so I’m not sure I would like Jerboa anyway (I haven’t seen it). I appreciate the work that the devs and ops have put into Lemmy but Ifrankly prefer the user interfaces of 40 year old Usenet readers to these Javascript pages that squirm all over the screen. So I want to keep persuing text based viewers like RedReader and Gnus. I’d try Jerboa if it was convenient for me to do so, but I’m not going to buy a new phone to run a program that I have doubts about to begin with.
That’s impressive
Yes but it’s also not that uncommon for Google phones to get many years of updates thanks to community ROMs. Google actually supports old Android versions for a pretty long time, it’s just that suites at Google don’t want them to formally ship on their own phones and that’s how LineageOS and even smaller community ROMs get support those phones with “relatively little” effort (at least compared to phones by random Android OEMs).
That’s good to hear. I would be curious to get a Pixel 4a, put LineageOS on it and see how long it would last
I have a 4a right now, plan to replace the battery sometime and switch to a community ROM when Google’s formal support ends
FYI: You can’t just install LinreageOS on top. It’ll require a full wipe. Should you do cloud backups anyway, the step is not that bad. If you never dabbled with that, it’s a bit intimidating at first but actually it’s not that hard once you grasped the basics.
My 5yo phone is running Android 13. Get LineageOS.
By keeping backwards compatibility that far back you give up on a large set of features. My guess is that Jerboa needed some feature that only exists from Android 8 and above and they didn’t want to reinvent wheels.
Probably it would be best if you try to get a used phone with an more up to date Android version.
I’ve gotten to the point that I think that any new software release of something like Android or Firefox is likely to make it worse than before. Reddit was another example. So I resist. What feature could they possibly want from Android 8 that wasn’t in earlier versions? If it was the dev kit (Jetpack) then I can sort of understand, but Android 7 has plenty of user level features, and apps such as RedReader that work fine. I’d be delighted with a RedReader port for Lemmy.
The idea of buying another phone and making more e-waste just to deal with version churn is distasteful to me. I might get interested if I can find a phone that supports Lineage really well, but otherwise I’d rather keep using what I have until it falls apart (it is getting there).
Thanks though.
I guess it’s time for you to get into app development and find out firsthand.> I might get interested if I can find a phone that supports Lineage really well
Literally every single Google phone. Get a second hand last gen one if you’re actually about reducing e-waste and that’s not just an excuse.
Tbh just use a custom rom
If I get a new phone while my old one still works, I’ll perhaps try a custom rom in the old one. Otherwise it’s like messing with a production server.
Using Android 7 is a huge risk, it’s simply not safe, go grab a new phone if you got money
Meh, if Android 7 has so many bugs, the later versions must have even more bugs. I’m not sure quite what I’m supposed to be at risk of. I don’t run any Google Play apps, have mobile data turned off most of the time, don’t have much really private info on the phone though I do have some auth credentials there (TOTP app that uses some kind of hardware secret store, plus API key for email app). If I had to replace my phone right away it would probably be with another Android phone, but in the long run maybe I’d prefer a Raspberry Pi tablet or something like that, plus a separate voice-only phone or wifi hotspot. Unfortunately VOIP seems to suck badly, at least with the app I’ve tried (Linphone). And also unfortunately, 2G is dead so I can’t cobble together a DIY dumbphone using an ebay module. I don’t think they have those for 4G yet.
If you have any particular suggestions of a phone that is 1) cheap, 2) has a headphone jack, 3) has easy to replace battery (having to open the phone with a screwdriver is acceptable, but having to melt adhesives with a high chance of destroying the phone is not). A built-in e-compass for navigation would be nice to have, and a decent camera (the 5MP one that I have now is ok, but the one in the N900 was awful). I don’t need any high end features that I can think of. Lowish res screen is fine but it should be large. Wireless charging would be nice but that seems to conflict with easily replaceable battery. I am thinking of the Moto G Power which has some older versions on sale at Best Buy. But again, I’d rather postpone a new phone as long as I can.
No, because the latest Android has all of the bug fixes discovered in Android 8-14.
Also, when the developers discover a big in the latest Android, they fix it. When the developers discover a bug in an old version, they check if it is still there in the latest.
I do understand that newer Android versions incorporate the bug fixes that were found in older versions. But their main purpose as far as I can tell is introducing new features (i.e. bugs) of their own. Android 7 is also not that old as far as this stuff goes. I’m sure lots of people are running even older Android versions on their phone. I still have an Android 2.3 music player (Archos 43) though I don’t use it much.
I’m not a heavy user of Android so I tend not to pay too much attention. I’m on a 1GB/month data plan and I usually use less than 1/10th of it, checking email or (in the past) Reddit here or there. The only internet-connected Google app I use much is Maps, though that admittedly is one of the more invasive ones. Is there anything else I should watch out for? I get the impression most vulnerabilities are in apps rather than the OS. Most of my apps are from F-droid and I do keep those updated.