Show HN: A Mashup to find LineageOS supported phones that are repairable
sustaphones.com
sustaphones.com
There's many issues with this.
The primary one is that if I select battery replacement "easy", I also want to see "very easy". I consider it easy+. This is the expectation.
Having said that, I need to be able to filter by screen size range, by screen time (e.g. oled) and by presence of headphone jack.
If they can't do this much, the filters are of very limited usefulness.
I really like and appreciate your site!
I have been trying to decide on which Android device that I need to buy that supports official versions of Lineage and it would be nice if it could be easily repaired as well.
My favorite phone so far has been a six year old Motorola.
The battery lasts for several days without a charge and doesn’t send any data out that isn’t necessary according to tcpdump and my PiHole.
(Which is probably why the battery lasts so long)
Google Android is an absolute dumpster fire and cheap devices often come with preinstalled malware and rootkits abd even expensive Samsung devices are loaded with too much bloat.
But my old Moto is not on the approved list so I have to compile a new OS which was fun but gets old real quick.
I watched a teardown video for the phone on YouTube and it appears the battery is replaceable, just not easily, whereas its given an "x" on this list (is this true of all phones?). Fortunately I don't seem to be suffering any battery-related problems at the moment, but I will be attempting to replace the screen, which does not seem to be easy on this dwvice.
So, the listing for the Moto X 2014 is saying exactly that. A swappable battery means that you can just take off the cover and change the battery, without needing any tool. That's not the case here (at least it's not marked as having that feature). Instead an iFixit guide is linked with 'moderate' difficulty (unlike others that are very difficult, then I wouldn't even try). Maybe that definition of a swappable battery is not universal and should be explained on the page?
What do you mean? I keep Pixel 4A on my buy-list, if/when my old trusty Nexus5X with zero Google services breaks down.
I do enjoy the 4a very much however, it's a great device.
I'm not aware of a good source for "supports VoLTE natively / with hacks / not at all" data, though.
I still haven't found a good VOIP client for desktop linux/pinephone.
You can't call to and receive calls from normal numbers through it, can you?
Also, it seems that my phone supports VoLTE even though I use Lineage OS without gapps. At least it shows LTE being set up for voice too in the settings app as well when I dial that 4636 number.
https://www.androidpolice.com/2020/07/24/how-to-find-out-if-...
Repairable for now means "battery swappable or easy to change". Lineage is only one of two Roms listed, MoKee is the other one.
It does support the second screen as an extension of the main one. The IR glitches, and voLTE does not work like in many lineageos models.
The biggest issue is battery and camera. Which the custom ROMs on XDA will solve.
Also you can buy on aliexpress a 4100mah, or even 10000mah with an extended case.
It supports usb to hdmi. You can install the gcam app.
It lg v20/g5 are still very good phones but you do need to invest some time on them.
So far i used geizhals (https://geizhals.eu/?cat=umtsover&xf=162_LineageOS+Support%7...), but this is so much better since you implemented filters for version and release date.
Good job, i'll stop raving now, promise.
(edit: formatting)
> Further, it appears that only official LineageOS versions are taken into account
That's correct. There are of course many more roms available on xda, unofficial lineage roms and other projects, but for one I do not know a structured way to list them, and second I think that if one decides on a device it should be based on official support by a bigger project.
If there are more of those bigger projects that should be listed (and that have a list of devices they support published somewhere) I'm happy to add them to the list. It does not have to be only MoKee and LineageOS.
When fixing things it doesn't matter where you find the guide so I'm saying that if there are other videos available they should be linked. Obviously using iFixit only is easier to implement, but maybe there can be a way for the users to upvote arbitrary links?
> but maybe there can be a way for the users to upvote arbitrary links?
Maybe if the foundation would be a bit different :) But this is a completely static site. One ruby script per data source creates a central .yml file, another custom ruby script creates the HTML based on that data and some .erb files, netlify is then serving those HTML files (pulls them directly from a gitlab repo). And after the holidays my time will be too limited to change that, especially for a noncommercial project. But if there is serious interest to create a fork with more features and data I would open source this.
Edit: As someone on Reddit was asking for a repo and this comment planted the idea to open source it anyway, here is the repo: https://gitlab.com/onli/sustaphones
Make (example "Samsung")
ModelNum (example "i9300")
ModelName (example "Galaxy S III (International)")
Year
Codename
LineageOS (example "17.1", link to site)
MoKee ROM (example "7.1", link to site)
Battery (example "Easy", link to iFixit)Another good resource to find phones with removable battery is this chart:
Edit: The Lineage link now goes to the device wiki entry, where the installation instructions are also linked.
For the removable battery, the idea here really is to go one step further. When almost all modern phones have no removable battery the next best thing is having a battery that is easy to replace, even if it is not directly swappable.
I have found the best way to see what lineage options looks like for a particular device (and root, recovery, install requirements) is to check the XDA device forums for specific devices before phone purchase.
It would be nice to be able to link to specific queries and individual results.
With other devices it could be that the parser needs improvements. The guides can have flags and there are maybe some that need to be respected or displayed. You did stumble over another example?