Kia Connect (the new app) do not work

MaZe

I dint know why, but the app works now. I am on app version 1.1.17 and have the latest grapheneos version. Maybe they listened to all the complaines or graphene did something since then.

whoami

MaZe Do you mean 1.0.17 ? I tried that yesterday and it didn't work.

MaZe

Yes, sorry for the typo. I reinstalled the app on November 30th where it didn't work. Out of curiosity I started it yesterday and it worked to my surprise, I can login and perform every control of the car. The app details show updated at December 3rd, 2025 and version 10.0.17

I didn't modify any settings or permissions, beside accepting most of them that the app asked for.

Those are my defaults:
Exploit protection compatibility mode: Disabled
Hardened memory allocator: Enabled
Native code debugging: allowed
WebView JIT: Enabled
Dynamic code loading via memory: allowed
Dynamic code loading via sotrage: allowed

I have a Pixel 7 Pro.

whoami

I just reinstalled version 1.0.17. Immediately after launching it, I get the warning:
Security risk detected on your device. The service cannot be used. For your security, the app will be closed if it is running on a rooted device or in an unusual app environment.
Confirm

My defaults are identical:

Exploit protection compatibility mode: Disabled
Hardened memory allocator: Enabled
Native code debugging: allowed
WebView JIT: Enabled
Dynamic code loading via memory: allowed
Dynamic code loading via sotrage: allowed

I have a Pixel 9 Pro and am using build number 2025112101.

Novalissoide

whoami No developer options enabled, no adb, no Shitzuku, root or prior root?

Novalissoide

whoami

whoami The device is not rooted.

Kia begs to differ;

"the app will be closed if it is running on a rooted device or in an unusual app environment".

whoami

I just switched off developer mode and reinstalled the app.
Same behavior.
The device is not rooted.

Novalissoide

whoami my point is, "just switching developer mode off", and "reinstall the app" might not be enough to fulfill your target apps demand for 'non bot-like behaviour'.

whoami

Ok. You mean the fact that I have enabled developer mode even once made my phone an unusual app environement?
What can I try to do?

Novalissoide

whoami In general this is my first suggestion;
If you want us to help you check your device, you should turn developer options off. No ADB, no Shitzuku. Bootloader must be relocked and your device should be auto-updated.

whoami

ok. Developer Mode is off as mentioned before.
ADB is off.
I do not use Shitzuku.
Bootloader is locked.

I installed shelter for handling the work profile. Kia App and Sandboxed Google are installed in the work profile.

ginnun

Same here with the Hyundai app (Also tried the Kia app without more success).

Is there a way to check if ADB is off and bootloader is locked from Graphene OS? Developer mode is already off (But was enabled in the past), and Shitzuku not used.

de0u

ginnun In Developer options, under the "Debugging" heading, there is a toggle for "USB debugging", and also a button to "Revoke USB debugging authorizations".

A great way to detect bad advice about USB debugging is checking whether or not a source that explains how to turn it on also explains about revoking authorizations and turning USB debugging off. Sadly, probably 99% of "helpful" sources cover only the dangerous part.

ginnun

So I revoked any previous authorization, and USB debugging was already disabled, and I redisabled developer mode.

But unfortunately, the app still shows the error.

de0u

ginnun Have you tried disabling secure app spawning? Some users earlier in the thread found it useful.

ginnun

de0u I disabled it, and the app started properly.

Is this setting only available at the global level? I don't find an app specific option for this setting.

ginnun

ginnun ...but now it's my bank app that previously worked properly that now sees my phone as "rooted". So I reverted to app spawning enabled.

Lucario1829

ginnun unfortunately yeah, its only global

Vincent96

I got the app working. I disabled developer mode and disabled secure spawning. Compatibility mode is not required.

I have Google Play Services but I don't know if that matters.

Roede

Vincent96
As you can read in my post, I also have GPS (Google Play Services) active - even with network. I have tried with and without Secure Spawning and also running the app in Compability mode. I don't have developer mode enabled.
Still, I cannot get it to work.
Im happy for you that you can get it to work. However, there is something else you have done, that you're telling here, since the rest of us cannot make it work. Im sure the rest of the community would appreciate any more hints you can give.

Thanks again

whoami

Disabling secure spawning has fixed the issue for me too but it would be nice to have this setting on the app level.
Maybe there is a workaround by installing the Kia App in the work profile and disabling the secure spawning just there.
I have not found a way to do that now.

« Previous Page Next Page »