(not posting to the original thread, as it is locked…)
So, Zwift has decided to move forward with phasing out support for some platforms. Quoting from received mail: “Starting August 10th , we will begin deprecating certain operating systems based on industry standard minimums.”
Wherever the source for “industry standard minimums” is, seems I will no longer be able to use my existing Android setup running the Companion. Unfortunately, I don’t have another phone to repurpose - which means I will have to buy a new one:
My old phone will go to the landfill.
The price of a new mid-range Android phone is, say, $150?
Eventually, that new phone will also be phased out. Let’s assume 2 years (Zwift has not set a timeframe for the next OS update…)
This essentially adds $6.25 to the monthly subscription cost. This is not a trivial increase to the subscription cost.
Sustainability? Environmental impact? Forget it. New functionality resulting from moving to newer OS versions? None has been mentioned, so cannot comment.
2 years isn’t a reasonable assumption. The newest Android version that Zwift are deprecating is Android 8, which came out in 2017. So as long as you don’t buy a new phone that has a 3-year-old version of Android on it, you should get a lot more than 2 years out of it for Zwift support.
Whilst not speaking specifically for Zwift, I’ve worked for other software development firms who do not support older operating systems, browsers, etc. This is pretty normal.
you could buy a refurbished or used (read: unwanted store return), but essentially still new, mid range android phone instead. i don’t think the environment or preordained technological obsolescence by hardware conglomerates are zwift’s problems to solve, at any rate.
Supporting old OSes costs Zwift money which comes from all of us. Your desire to run old kit is putting your hand into our pockets, much happier you spend your money, not mine.
It takes longer to develop and test when you are having to do so on various different platforms.
It also potentially restricts game development when hardware restrictions prevent some features being built (thinking mainly around memory constraints of older hardware).
respectfully, you are the one who decided to blame everyone else and the world for your own consumption habits without thinking. for the record, if you’re tossing your phone into a landfill just because it can’t run zwift in the future, i recommend selling or giving it to someone who just wants a phone that works instead
I sympathise with the desire to keep old hardware in use, but mobile testing is relatively complex and expensive, taking resources that could be used to do better testing on fewer platforms. I suspect most users would be happier with better testing of features and more effort put into product development. If the phone is in good condition, consider donating it to charity and buying a recent-model used device to replace it.
As a developer who ends up with several older devices that used to be used for development, one way to continue using an old device is to update using a Android Open Source Project (AOSP) version such as Lineage. I use an old Nexus 6P with Lineage to run the Companion application for example.
Android Custom ROM - Lineage OS - HTC One M7, bought 2013.
Welcome to Android 11!
Not the easiest way, but (including reading manual) in 2 hours with 0 cost done.
Edit: I don’t know why this thread should be ignored (see title) instead of trying to point the people who want to use older devices in the right direction. I am using my old friend HTC One for Zwift Companion, with 0 issues.
Lineage? Really works? What build of lineage do you have? As far as I’m aware the Android 11 and up builds don’t support signature spoofing and have no playstore unless you are using GAPPS?
“(I think) a solution path exists” would’ve been a better description. Unfortunately, I am yet to reach the “solved” state: I was able to obtain an unofficial build of Android 10 (Lineage) for my model (slte), together with GApps, but failed updating TWRP to a version that will install it, half-bricking the device in the process.
As amusing as that may be, I am not sure this forum is the right place for Android custom ROM, TWRP, ODIN, FASTBOOT, bootloader unlocking, etc. discussion - But I haven’t given up on the solution (which, as I said, is yet to materialize…)
