Sorry if this has already been discussed, but has anyone come across the exact phone compatibility requirements for the phone to work as a fob? I went to update my Tesla app for M3 support this week and was prompted with a "Your device isn't compatible with this version" notice and not allowed to proceed with the download.
Even though my phone is a rather ancient Samsung S III Mini, this is the first time I've come across any sort of such issues. I guess I've stuck with this dinosaur mainly due to its compact size while waiting for the next compact Android model to be released since I'd prefer not to switch to iOS. So I've been waiting for Samsung to release its promised Mini S6 until the release got scrapped, then the S7 the following year until that got scrapped, and now (fingers still crossed) the S8 Mini release that is still scheduled for later this year.
Since the Samsung "Mini" model range traditionally consisted of watered down processors and fewer features, it'd be nice to know what version Bluetooth etc. is required for Model 3 access before committing to a phone upgrade ahead of taking delivery.
It's not necessarily what Bluetooth version but rather the app itself that isn't compatible with your device. I can tell you that Android is incredibly more difficult to handle from a compatibility standpoint than Apple due to the sheer volume of devices and variations of hardware/software out there.
On the Apple side, Apple controls hardware and software. There are only so many devices in existence as well.
On the Android side it's a crapshoot. The hardware and software that sits on top of basic Android becomes difficult to handle.
Aging devices will always become an issue (on both platforms) as modern technologies evolve the older devices begin to sunset.
When you go to https://play.google.com/store/apps/details?id=com.teslamotors.tesla&hl=en, you will only see a confirmation of whether or not the app is compatible with your device; but behind the scenes in the Android Developer area it shows exactly which devices are compatible and not compatible with your app.
For a fun fact, I am the Product Owner for a proprietary software platform that my company utilizes for a few thousand users. My app is compatible on 7,631 Android devices and there are a total of 14,217 Android devices.
Thanks! I've emailed the Tesla App developer about this. Also, I just checked the link you provided, and it looks like this version requires Android 5.0. while my phone is currently on 4.4.2.
Be a bit careful though. Even if you can run the App, you might not be able to use your phone as a key. My iPhone 4S can run the Tesla App but it cannot be a key for my Model 3. The iPhone 6S can do both.
If I’m not mistaken, it’s not only Bluetooth but also NFC which explains why you need to make contact with the pillar. It’s possible the older phones didn’t have that technology built in. Basically any phone that can do an Applepay/Samsungpay service should also work as the key for the M3
If I'm not mistaken, it's not only Bluetooth but also NFC which explains why you need to make contact with the pillar. It's possible the older phones didn't have that technology built in. Basically any phone that can do an Applepay/Samsungpay service should also work as the key for the M3
I don't think the NFC is a factor (on the phone) which I think is exclusively Bluetooth. Along your line of thinking though, it can also dependent on Bluetooth hardware as well and maybe the older devices are not up to snuff.
As I understand it, the old phones have a version of BT that does not have the LE module. Some say it's in 4.0 but others say it's 4.1, if your old phone doesn't have LE then it will not work afaik.
For the technical, BT LE has the cryptographic protocol that is used. Other products like Tile use this as LE is always on and will try to pair with the corresponding devices. So if Tile does not work on your phone then there is a good chance that the Model3 LE communication will not either. I have an iPhone 6S which does have the LE as it connects to my Tile once it is in range but I know my old Touch 5th gen (the one with a touch screen) does not work and that's BT 4.0 so it could also be down to the antenna's used.
BLE= Bluetooth Low Energy = the English name for Bluetooth 4.0 hardware and software stack. It's correct that older hardware does not support it. It is possible for Tesla to add older Bluetooth 3 support if they don't mind the extra energy use.
In addition to the possible lack of BLE, an older version of Android OS may lack the necessary API calls to use the hardware and support the phone-as-key functionality. Plus there may be other performance-related issues.
Looks like my not-nearly-as-old HTC One m9 is compatible, though since I don't have any Tesla products yet apparently I can't sign in (thought it would let me sign in then tell me nothing here).
I 99.9% sure that the Google Play Store is smart enough to only display apps for download that are compatible with your device, so if you can download it, it's compatible. Still doesn't mean the key works, though I'd bet your device works just fine as the key.
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Related Threads
?
?
?
?
?
Tesla Owners Online Forum
387.6K posts
55K members
Since 2016
A forum community dedicated to Tesla owners and enthusiasts. Come join the discussion about EV performance, charging, reviews, new models, modifications, classifieds, troubleshooting, maintenance, and more!