Karoo 2 takes forever to start up

Comments

13 comments

  • Avatar
    Johnathan Freter

    I figured it's because of the Android OS but yes it is slow. Modern smart phones are also very slow to start so I just figured this is a heavy OS thing, that is probably a bit over kill for a unit like this. 

    1
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    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 )

    1
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    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
    0
    Comment actions Permalink
  • Avatar
    Steve

    49 seconds from pressing the power button to being ready to start a ride. It's taken this long for as long as I can remember.

    You could just turn it on earlier?

     

    0
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    49 != 150. Thanks for playing.

    0
    Comment actions Permalink
  • Avatar
    yen

    Think i had one slow startup, funny how many times ive said on here wahoo have this that and the other..

    0
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    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.

    0
    Comment actions Permalink
  • Avatar
    yen

    Anna, Hammerhead could do lots more with the k2 but for some reason they're leaving it as it is and tweaking bits and not taking advantage of expanding it

    0
    Comment actions Permalink
  • Avatar
    Johnathan Freter

    Do you think any of that has to do with the SRAM buyout?

    0
    Comment actions Permalink
  • Avatar
    yen

    Im waiting and seeing on this..

    0
    Comment actions Permalink
  • Avatar
    Andreas Boiselle

    some months later and the Karoo 2 is still performing like Lance Armstrong without doping... that means slow

    0
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    I for one at least am no longer having this problem since maybe a month or two ago (didn’t remove sideloaded apps or change anything else).

    0
    Comment actions Permalink
  • Avatar
    Richard Soltes

    At least they used to have amusing graphics to entertain you while you waited.

    Fortunately  there are no ads in the space.

    Good time to check tire pressure, lube chain, adjust straps, make coffee.

    0
    Comment actions Permalink

Please sign in to leave a comment.