View Single Post
Old 04-21-2022, 03:07 AM   #267
Deobulakenyo
Guru
Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.
 
Posts: 706
Karma: 2153490
Join Date: Aug 2021
Location: Stupid Philippines
Device: Kobo Libra 2, Boyue Likebook P78
Quote:
Originally Posted by DNSB View Post
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.

Thanks for the instruction on debugging. I followed the nanoclock log instruction before but all i get is the log that nanoclock started. But i will do it again and share the log.

For the nickelmenu, what does it do? Do i rnable it via nickelmenu and then disable it after?

As for the reset. I did manual reset by holding the volume up button while pressing the power button and waited until the screen flashed and reset the device to factory setting. Rolled back the fw as well after. Then i turned the device on and it updated via wifi to 4.30. I updated it again via wifi to 4.31. then i manually updated to 4.32 as the latest fw is not yet available in my location.

Last edited by Deobulakenyo; 04-21-2022 at 03:11 AM.
Deobulakenyo is offline   Reply With Quote