View Single Post
Old 12-11-2014, 03:57 PM   #1956
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Since I misunderstood a question asked by libertango, I proposed here to use a slightly changed koreader.sh. The change did of course not solve libertango-s problem, but I think it is nevertheless useful to better distinguish whether koreader has been called by advboot or KSM. I replaced
Code:
    # if we were called from advboot then we must reboot to go to the menu
    if [ -d /mnt/onboard/.kobo/advboot ]; then
        reboot
    fi
by
Code:
    # if ksmhome.sh is not running, reboot
    [ $(ps | grep -c  ksmhome.sh) -le 1 ] && reboot
    
    # If it is for some reason necessary to reboot some models even thought KSM is active
    # please checke here with case "$PRODUCT" in ...
tshering is offline   Reply With Quote