App won't run on Android <12?

[Laserboy1054]

Hi! (First post after "hello")
Maybe this has already been discussed--forgive me if it's already trod ground!
I am in the process of ordering an R1T. I decided to go ahead and install the app--just to poke around. Then I discovered that the app requires at least Android 12! Sheesh! My phone is running Android 10. Do I really need to get a new phone? I really like my phone--it's an obscure brand, an Oukitel WP10 (if you like the Rivian Max battery pack, take a look at the batteries Oukitel is putting in its phones!). Getting my carrier to "see" it was quite an adventure when I got the phone two years ago and I'd rather not go through it again too soon. And it's working great!

Does anyone know a good workaround or do you think I should just bite the bullet and get a newer model?

Many thinks for any help!

Best wishes.

Sponsored

 

[VSG]

The Rivian app doesn't work on versions of Android < 12.
This is stated in the app store under requirements.

Version 10 has been unsupported by Android for more than a year. If your phone/carrier does not support more recent versions, then yes it's probably time for a new phone.

 

[Laserboy1054]

The Rivian app doesn't work on versions of Android < 12.
This is stated in the app store under requirements.

Version 10 has been unsupported by Android for more than a year. If your phone/carrier does not support more recent versions, then yes it's probably time for a new phone.

Thanks for the info! Yeah, I figured that was the case. I've ordered a replacement. It's not a huge expense: a ~$500.00 phone to enable an ~$80,000 truck. But I dislike waste as a general principle. I'll try to find a new home for the old phone (I can still get more than four days out of a single charge on it!).

Best wishes

 

[TollKeeper]

You could always try to download the APK file, and install it that way. I have to do this on some of my Amazon Tablets, and it works just fine.

https://apkpure.com/rivian/com.rivian.android.consumer

Thats for version 2.7.0 and they are on 2.8.0

This is for 2.8.0

https://www.apkmirror.com/apk/rivia...-0-release/rivian-2-8-0-android-apk-download/

Both downloads say they require Android OS 12.0

 

[Laserboy1054]

Hmmm...I'll look into it. Clearly a learning curve for me.

Thanks for the pointer!

 

[defcon888]

Hi! (First post after "hello")
Maybe this has already been discussed--forgive me if it's already trod ground!
I am in the process of ordering an R1T. I decided to go ahead and install the app--just to poke around. Then I discovered that the app requires at least Android 12! Sheesh! My phone is running Android 10. Do I really need to get a new phone? I really like my phone--it's an obscure brand, an Oukitel WP10 (if you like the Rivian Max battery pack, take a look at the batteries Oukitel is putting in its phones!). Getting my carrier to "see" it was quite an adventure when I got the phone two years ago and I'd rather not go through it again too soon. And it's working great!

Does anyone know a good workaround or do you think I should just bite the bullet and get a newer model?

Many thinks for any help!

Best wishes.

I moved to iPhone 5 years ago after swearing them off. I had all the Androids starting with Froyo, Gingerbread all the way up to Pie. I loved the fact that I could install my own version of the OS....but with that said....get a cheap Android that can run the latest OS and just use that for the Rivian only....use your phone you have now as your phone. Depending on your carrier, they probably have a deal for a cheap Android that you can add to your plan.

If you don't want to do that, look online for Android <12 software that you can load yourself onto your phone.

 

[Laserboy1054]

Yup, that strategy occurred to me as well. I might do it. Fortunately, a few weeks to go before I take delivery, so I have time to get prepared. Many thanks for the input!

 

[zymolysis]

Hi! (First post after "hello")
Maybe this has already been discussed--forgive me if it's already trod ground!
I am in the process of ordering an R1T. I decided to go ahead and install the app--just to poke around. Then I discovered that the app requires at least Android 12! Sheesh! My phone is running Android 10. Do I really need to get a new phone? I really like my phone--it's an obscure brand, an Oukitel WP10 (if you like the Rivian Max battery pack, take a look at the batteries Oukitel is putting in its phones!). Getting my carrier to "see" it was quite an adventure when I got the phone two years ago and I'd rather not go through it again too soon. And it's working great!

Does anyone know a good workaround or do you think I should just bite the bullet and get a newer model?

Many thinks for any help!

Best wishes.

I've got a Samsung Galaxy S10e with Android 12. My SO has a Galaxy S9 (with Android 11, I presume), which worked last year with the Rivian app (when I first got my R1T). But later in the year Rivian introduced a version of its app that requires Android 12. She is still able to use it as PAAK (phone as a key), but can't run the app. Now I am worried that Rivian will release an app version that will require a later version of Android, and force me to buy a different phone. Apparently the S10 Lite is eligible for Android 13, but none of the other S10 models.

 

[dfx]

I've got a Samsung Galaxy S10e with Android 12. My SO has a Galaxy S9 (with Android 11, I presume), which worked last year with the Rivian app (when I first got my R1T). But later in the year Rivian introduced a version of its app that requires Android 12. She is still able to use it as PAAK (phone as a key), but can't run the app. Now I am worried that Rivian will release an app version that will require a later version of Android, and force me to buy a different phone. Apparently the S10 Lite is eligible for Android 13, but none of the other S10 models.

I also have an S10e with Android 12 and while the app works fine with it, I can't get it to work as a phone key for the Gen 2 R1S. There never was a problem with the phone and the Gen 1 R1S but it's been a pain not having that functionality. Once I get a Key Fob it won't be much of an issue, but for now it's an inconvenience.
Has anyone else run into this issue with older phones and Gen 2?
They don't make phones as small as the S10e anymore and I'd rather not change to a larger new model

 

[usherlevy]

I also have an S10e with Android 12 and while the app works fine with it, I can't get it to work as a phone key for the Gen 2 R1S. There never was a problem with the phone and the Gen 1 R1S but it's been a pain not having that functionality. Once I get a Key Fob it won't be much of an issue, but for now it's an inconvenience.
Has anyone else run into this issue with older phones and Gen 2?
They don't make phones as small as the S10e anymore and I'd rather not change to a larger new model

Same issue. Note 10 + worked perfectly fine on Gen 1 R1S. Upgraded to gen 2 R1S and phone as a key will only work first time i pair it (or when i put the phone in and out of airplane mode. Then it will work one time again). Really annoying. Any fixes?

 

[kenyee]

The Bluetooth support on newer android phones is a lot better so it'll be more reliable.
Upgrading to something that has a snapdragon gen 2+ (S23 or better in Samsung land) will also get you much better battery life.
Google also forces developers to drop an older OS version every year so I wouldn't keep an older phone running anything less than android 13 at this point...

 

[dfx]

The Bluetooth support on newer android phones is a lot better so it'll be more reliable.
Upgrading to something that has a snapdragon gen 2+ (S23 or better in Samsung land) will also get you much better battery life.
Google also forces developers to drop an older OS version every year so I wouldn't keep an older phone running anything less than android 13 at this point...

Thanks for the input. Planned obsolescence embraced by tech companies is a pain and despite their posturing, it is not an environmentally responsible business practice.
I guess I'll have to upgrade

 

[Ceejay]

ya also frustrated that I have to upgrade my (otherwise) perfectly good phone, a Samsung Galaxy s10 running Android 12

 

[mkhuffman]

It is interesting I just discovered this problem when I wanted to install MFA on an old phone that is running Android 10. I just wanted a backup to handle the MFA process in case my primary phone is unavailable, but since that won't work, I purchased a cheap $80 phone off of eBay that is now on Android 15.

 

[kenyee]

Pick up a Pixel 8a or current Samsung phone ... 7 years of updates.

I'd be worried about security holes in older phones that no longer have security updates...

Sponsored