Karoo 2 takes forever to start up
Since the software update about two weeks ago, my Karoo 2 takes f-o-r-e-v-e-r to start up. After the latest update it takes almost two and a half minutes to get to the profile selection screen, of which exactly two minutes are spent with the screen displaying only the Hammerhead text + logo. It is not consistent though, sometimes I do get a more normal startup time, but I have not been able to discern any kind of a pattern.
The SIM card PIN code input right after startup has been sluggish already earlier (for maybe 3 months or so), the key presses (except maybe the first one) take several seconds to register on screen, plus the wtf factor of inputting and deleting extra digits because of this.
Any ideas, and am I really the only one with this problem?
-
Yeah, I totally get that it does not start up instantly, but it didn’t use to take this long. Never thought about timing it but it was definitely less than 30 seconds. The PIN code input used to be more responsive as well, and it does become like that now as well if I let it wait for an extra minute or two, so clearly there is something going on in the background.
Just curious, is there a way to view all the messages from the Linux kernel at startup, either on-screen or download them via adb? (Oh no, I see myself installing a command prompt app and pairing a BT keyboard to my Karoo soon... :D )
-
Ok, so I had to try adb lol^Hgcat, and I got absolutely nothing at all for the first minute or so, and then what I presume was a pretty normal startup sequence. I guess this is the weird part right at the top, presuming the timestamps are consistent (it takes about 500 more lines for the real-time clock to realize that today is in fact not Apr 4):
04-10 06:36:45.278 269 269 I SELinux : SELinux: Loaded service_contexts from:
04-10 06:36:45.308 269 269 I SELinux : /system/etc/selinux/plat_service_contexts
04-10 06:35:01.984 268 268 W auditd : type=2000 audit(0.0:1): initialized
04-10 06:35:03.819 268 268 I auditd : type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295
04-10 06:35:03.819 268 268 W auditd : type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
04-10 06:36:45.377 272 272 I SELinux : SELinux: Loaded service_contexts from:
04-10 06:36:45.380 272 272 I SELinux : /vendor/etc/selinux/vndservice_contexts
04-10 06:36:45.387 271 271 E hwservicemanager: BINDER_SET_INHERIT_FIFO_PRIO failed with error -1 -
Another software update, this still keeps happening. However, I have noticed that I seem to get a normal startup time most of the time if I let the unit power itself off from idleness, but if I use the power off function, I get 2 minutes Hammerhead screen every time after that.
The ~100-second difference matches pretty well the time between the first (auditd) timestamps and the start of the actual boot procedure. I tried to run dmesg via adb but apparently it requires root privileges.
As for just turning the unit on a bit earlier, yeah, right. Starting from home, it’s not a problem, plus obviously I don’t need navigation and don’t care if I miss the first 100–500 m of the ride. However, I tend to start many of my longer rides by taking a train and only notice it is time to go when the train approaches my stop (plus the bike is often more than an arm’s length away from where I’m sitting). Add to this the time it takes the unit to crunch new routes (and maybe even open the dashboard and press the refresh button) and we’re easily at 5 mins total or more.
Please sign in to leave a comment.
Comments
13 comments