Quote:
Originally Posted by Deobulakenyo
I did manual reset a few times already. The last one was when i updated to the latest fw. I just need help how to debug and generate log for nanoclock so i can send it the dev. I don't know how to.
|
Did you do a real factory reset (either from Settings => Device information => Developer options or using the manual factory reset (see:
Manual reset your Kobo Sage, Kobo Libra 2, Kobo Forma or Kobo Libra H2O? The factory reset from the Device information menu is not a full factory reset.
As for the debug setting for nanoclock? Take a look at the nanoclock.ini file. change debug to true. Possiblly set the dump_log option to true as well.
Code:
;
; To debug, set to true
;; NOTE: Everything is sent to the syslog, to look specifically for nanoclock entries, run
;; logread | grep '\(nanoclock\|nanoclock\.sh\)\[[[:digit:]]\+\]'
;; NOTE: Alternatively, you can find a NickelMenu config that will dump it in .adds/nanoclock/nanoclock.log
;; over here: https://github.com/NiLuJe/NanoClock/blob/master/config/nm_nanoclock
;
debug=false
;
; If this is enabled, the current log will be dumped to .adds/nanoclock/nanoclock.log
; every time this config file is reloaded.
; This is a poor man's hack to get at the logs when you truly have no other way...
;
dump_log=false
You can add the following lines to your NickelMenu config file as well.
Code:
# Dump NanoClock's log to a file, because Dev mode log dumps are now encrypted :/.
menu_item : main : NanoClock Log : cmd_spawn : quiet : /usr/local/NanoClock/bin/nanoclock-logdump.sh
chain_success : dbg_toast : Dumped NanoClock log in .adds/nanoclock/nanoclock.log
chain_failure : dbg_toast : Failed to dump NanoClock log!
This information was lifted from
NiLuJe's github page for nanoclock. Check the items in the config folder.