[QUOTE=crane3;3731362]
Quote:
Originally Posted by DNSB
Whatever. the colors of the flashing is immaterial & depends on one's visual perception & the lighting environment. I saw the colors as somewhat different than gray.
|
Sorry, no "whatever". You asked for help supplying very little information that could be used to diagnose the problem. You then described what you were doing and mentioned something that seems to be impossible. If what your report was accurate, then it isn't expected. But, the Aura ONE has coloured lighting, so you have the colour set to a fairly orange colour, a blank screen flashed would probably look like you described. Though it might depend on if an all white or all black screen was flashed.
Quote:
|
The main point is why the screen flashing into different screens/menus when removing books?
|
What you described shouldn't happen. If you remove a purchased book, it might ask you to connect to the WiFi, but I wouldn't expect it to. If the WiFi connection isn't available, it should remove the file and update the internal database. The next sync will do whatever is needed with the server.
For sideloaded books, it shouldn't do anything with the WiFi. It should just remove the files and the database entries. And that is what I see here.
One of the things here is the timing. When you did the remove, did you see the prompt for where to remove it from? How long until the screen flashed white or whatever? If it was a minute or so, then it probably means the software hung and it was a sickel triggered reboot. But, I don't know how sickel would interact with KSM.
What did the WiFi prompt look like? Was it by itself or over some other screen? Did it let you do anything, or display and then go away?
The fact you ended up as the KSM menu suggests that nickel crashed and either the device rebooted or it returned to the KSM menu as if you had exited from nickel. If nickel crashed, there might be a log file giving an indication of what happened. This will be named "stack_nn.log".
My assumption is that there is a problem with the internal database and that is blocking something. The fix for that is to restore a backup or sign out of the Kobo account. The latter will rebuild the database from scratch. If that doesn't work, then a factory reset will probably be needed. Or, if you are having consistent problems, removing KSM to ensure that isn't interfering with things. It shouldn't, but what you report shouldn't be happening, so reverting to the default setup is the thing to do until you know what is happening.
Quote:
|
Looks like I shouldn't even have posted any questions here.
|
No, you should ask questions. But, you need to remember that everyone here is doing this on their own time. You need to ask questions with enough information that we can help. For example, I still don't know what you are doing when deleted from "onboard". I know of one thing that name would refer to, but I have no idea how you are getting to see this or delete from it.