Issues with flasher and 2024 Kia Carnival

[spektor56]

Describe the bug

Just my experience after installing my C3X in a new vehicle (2024 Kia carnival SX) after it was previously working fine about 9 months ago in a different vehicle (TMOD 2017 Honda CRV).

Plugged in, boots up, nice, ill go for my first drive tomorrow.
Ok lets test this out on my way to get vday gifts, hmm, no panda... too bad. Guess i should have reflashed yesterday to make sure everything from my previous car was completely wiped
ok lets flash at flash.comma.ai, hmm, dont need power in the second port this time ok, lets follow the instructions completely.
failed half-way through using USB cable from a samsung 25 ultra, hmm ok, probably not enough power over USB? i'll just use the AC adapter in the other port then like before...
flash success! good, says fastboot mode not QDL but whatever.
unplug and replug, reset device... didn't i do that already? ok whatever go for it.
add wifi and stuff, hey, install openpilot option now, niiiice, not just custom software now.
do training, ok, "VEHICLE ONLINE", no more "NO PANDA", good.
ok lets switch to nightly-dev, asks to reset again? sure i guess.
AGNOS update, all good
ok lets test now.
yay it works, stopping for round about, re-engage, hey, didn't work, press again, oh there we go... Does it miss some button presses? Oh i see, every time i disengage with brakes i have to double press to get it to engage again, not ideal but ok...
k lets make some training data for firehose mode, one drive down, get some pizza, back to get more training data.
hmm, radar failure, please restart car. Well thats not great, now im losing all this driving data. Maybe it's because of comma powerless install?
hmm weird, when i press the brakes it doesn't disengage openpilot until i press them harder.

Which car does this affect?

2020 Kia Carnival SX

Provide a route where the issue occurs

4c28b31eb5a4f5de/00000003--056f87c9ae/0

openpilot version

nightly-dev - 0.9.8 - 9d377d2

Additional info

Radar issue route: 4c28b31eb5a4f5de/00000003--056f87c9ae/0
not immediately disengaging on brake press: 4c28b31eb5a4f5de/00000004--4a20e00143/1

[adeebshihadeh]

hmm, no panda... too bad

TODO

ok lets flash at flash.comma.ai, hmm, dont need power in the second port this time ok, lets follow the instructions completely. failed half-way through using USB cable from a samsung 25 ultra, hmm ok, probably not enough power over USB? i'll just use the AC adapter in the other port then like before... flash success!

Might be commaai/flash#71. We'll test this extensively once the flasher changes have been finalized.

good, says fastboot mode not QDL but whatever

This a quirk of flashing the release AGNOS over QDL; will be fixed once 0.9.8 is out.

unplug and replug, reset device... didn't i do that already?

commaai/flash#82 fixes this by flashing the userdata partition.

yay it works, stopping for round about, re-engage, hey, didn't work, press again, oh there we go... Does it miss some button presses? Oh i see, every time i disengage with brakes i have to double press to get it to engage again, not ideal but ok

This is just how the stock ACC works in new Kias. I agree, it's not great.

radar failure, please restart car. Well thats not great, now im losing all this driving data. Maybe it's because of comma powerless install?

This was a bug briefly on master.

hmm weird, when i press the brakes it doesn't disengage openpilot until i press them harder.

Again, this is a stock ACC thing. We get the cruise state from the car.