cycling
17. April, 11:19 Uhr
[1587113974917.jpg](https://postimg.cc/mhRrcm2D)
I thought I'd post about my experience with using a low-end mobile phone as a dedicated bike computer - for those who are interested.
I had been using a Garmin Forerunner 310XT for years. It was fine as a basic GPS-based computer, but obviously lacking in features and connectivity. Really, I knew I wanted a much better connected device but, let's face it, really top-end cycle GPS's are not cheap. The Garmin Edge 530 is over $500AU and the 1030 around $650AU. In my book, that's a lot for the technology involved.
I had considered using a dedicated mobile phone for a while. Like most people, I had switched to recording rides direct to Strava on my phone during a ride, but really wanted a few extra options 'on the handlebars':
1 - The ability to play and control music or podcasts
2 - Real-time connectivity so that I can share my location
3 - The ability to have turn-by-turn directions and a map if needed
4 - A device that was still a 'dedicated' bike computer, so that I could just keep it charged, grab it and go.
Hardware:
Basically, most modern Android-based mobiles are just a 'System on a chip' running the OS connected to a battery and a screen and they have a ton of power and features.
But, for me, the main advantage (and the thing that made this fit for an experiment) is the price. Carriers always have a bottom-of-the-line Android phone on clearance intended for the Pay-as-you-go market. With that in mind, I picked up a brand-new ZTE Blade for $39AUD on sale in a supermarket. That's 6% of the cost of a Garmin 1030 and 7.8% of the cost of a Garmin 530. For that you get 1 GB RAM, 8 GB max storage a Snapdragon 210 / Cortex-A7 chipset and a 1600 mAh battery. The device runs 'Android GO' version 8.
Now, of course this phone is locked to a network as it's supposed to be for 'Pay as you go' use. That's really no problem if you don't want it for calls though. I just wanted it as a portable computing platform, although usefully it will still make emergency calls (more on that later).
With a Garmin connector stuck to the back, the phone weighs 137g, which is comparable to a Garmin Edge 1030.
Mounting (10/10):
Alongside the phone you require a way to attach it to the bike. This is where we get to the point that had kept me away from doing this before - most bike mobile phone holders look really bad. The point here is to be a fit-for-purpose bike computer on a road bike, not a mobile phone in a dodgy holder. To deal with this and make it look right a simple plastic Garmin mount adaptor can be purchased from eBay for a whole $5.30AU - it comes with a strong sticky pad pre-attached and an out-front mount ($7AUD) rounds it off.
Software (8/10 due to needing some intervention to factory settings):
The disadvantage of 'Android Go' is that some applications are not available for it by default in the App Store. Strava in particular, which was the whole reason for the project. However, the APK file (basically the Android application) can be download from a number of generally low-risk sites and installed with a few changes to the phone's security settings.
I use:
* Strava in the background for logging
* Ride with GPS in the foreground for standard 'bike computer' features
* Google Play Music (for streaming music)
* Podcast Player (for podcasts)
* Google Maps (for directions)
Running this software, the phone is not fast. Starting and switching apps lacks the snap of a 'day-to-day phone'. For what the device is it's not unacceptable, but there's a definite 'press and wait' for applications to start or switch. Probably due to the small memory as much as the slow processor. Performance in the foreground app is certainly acceptable when you consider the cost of the device and what you're getting in functionality.
Connectivity (10/10):
So here's the amazing thing about modern SOC's - even basic SOC's have great connectivity. For $39AUD I have Bluetooth 4, Wifi, 4G LTE and ANT+ (yes, it has ANT+ built in).
On top of that, the handset will still make emergency calls with the supplied SIM card installed but not 'connected', which makes for a really good emergency option on the move via a homescreen contact shortcut!
To maintain connection, I just activate the hotspot feature on my main phone, slide it into my back pocket and they the little ZTE is my 'dashboard' for the ride. I can even set it up so that Google Maps shares my location whenever the ZTE is on, but not my location from my regular phone.
GPS performance (10/10):
In a word, excellent. The device has GPS, GLONASS and BEIDOU support and tracking is really excellent - like 'I can tell what side of the lane I was cycling in' excellent. If I ever get hit by a car who accuses me of 'coming out of nowhere' I'm confident that I have a good trace!
Screen (2/10):
So this is the downside and possibly a dealbreaker for some. The screen is very weak in direct sunlight. It does not do at all well and can be downright impossible to see. The thing is, that apparently major problem hasn't actually made me abandon my ZTE. The bottom line is that I very rarely look at speed or pace on my computer and, for me, the advantages of Strava on the device, media control etc make up for the screen issue. Now that Australia is coming into winter it's less of a problem too as the sun isn't overhead during prime riding time.
Environmental (1/10):
The other downside, the device is is no way weather proof. If the rain starts then it goes into my back pocket and I have already seen moisture under the screen at least once. My next project might be to take to the phone with silicone sealant and try to seal the speaker, headphone and around the screen, for $39 I don't have anything to loose but I live in a pretty dry climate. If you live somewhere where you ride in the rain a lot, this device at least isn't for you.
Battery (5/10):
As you might expect, battery life is also limited. However, you can use Android to manage the screen somewhat. I have a timeout set to 30 seconds screen off but 30 minutes screen lock setup, so I can just hit the power button to wake. I have mobile data turned off but have mobile networks on for the emergency coverage. I've played with proximity sensor on/off for gestures but not had any luck.
Basically, my current settings deliver: 2.5 hours with the screen on constantly (so makes it through a 'daily' ride. All day with the screen turning off after 30 seconds and on using the power button (for safety, lock screen is set to 30 minutes).
Conclusion:
Basically, this really worked out well for me. For a total of $AU52 (that's $33US) ( Phone plus garmin adapter and out-front mount) I have a fully connected bike computer with GPS, Bluetooth 4, Wifi, GSM and ANT+. There are some compromises that clearly a designed-for-purpose cycling GPS would not be making, most notably the screen which would be a deal-breaker for some. Yes, you can use Strava on your regular phone and a basic handlebar mounted computer, but for me though, the ability to have a device that just records my ride, controls media, has an emergency phone, transmits my location etc has been great. I've been using it for three months now and am so happy with the solution that I will probably take a look at a low cost IP68 rated phone for a couple of hundred dollars that should have a better screen, battery and environmental protections.
Photos are here:
[1587113974917.jpg](https://postimg.cc/mhRrcm2D)
TLDR; A cheap 'burner phone' actually makes for an amazing bike computer with some work,
[Appendum]
Wow, Thank you for the comments, positive and negative.
As an idea, I realize that it's not exactly rocket science! I just stuck a Garmin mount to a cheap phone. I'm not expecting any particular kudos, plenty of people responding have done the same thing or similar.
I just thought I'd capture the project as a write-up to help any future Redditor who might ask the question 'how would a really cheap mobile phone go as a bike computer'.
The answer is, 'fine, with some advantages and some disadvantages'.
Part of the appeal for me was to see just how cheaply I could do this and get a usable result. The level of technology in even a basic SOC is absolutely stunning. Yes, there are any number of ways to improve the result, using a better phone being an obvious one. Based on the write-up above and comments below anybody who wants to replicate/improve this should make that decision cognisant of the cost/benefit offset. A better phone would overcome the (significant) weaknesses of my little ZTE. It also would have been too expensive for me to do on a whim to answer my own question. The great thing about a $39 phone is that I had zero concerns about failure. If you want to do this, I wholeheartedly recommend you get a phone with a better screen at least, but it'll cost more than $39!
DC Rainmaker 
Zwift Insider 
pressedienst-fahrrad 
Bikerumor 
Radfahren in Stuttgart 
Bikepacking 
Besenwagen 
Speed-Ville 
MTB-News.de 
Cyclingmagazine 
Cycling Weekly 
CapoVelo.com 
Zukunft Mobilität 
LINES 
Velonews 
Fahrradportal 
Coffee & Chainrings 
RADELMÄDCHEN 
Born2.Bike 
Rund ums Rad 
St-Pedali 
Velomotion 
Spoony's Bike Blog 
Rennrad-News 
Crazy42wheels 
Velostrom 
RoadBIKE 
rockster.tv 
Radsport-News.com 
RADfahren.de 
Tausendkilometer 
Natenoms Blog 
FRAKTUR 
Warum ich Rad fahre 
eBikeNEWS mit Neuheiten, Kauftipps und Tests ru... 
Castellli Blog 
Singlespeed und Fixie Blog 
BIKE Magazin 
Strava Blog 
Swiss BikeBlog 
