Demo mode as slideshow

[Nemo1984]

Originally Posted by GeoffR

That string is (part of) a mangled C++ function name. A disassembler can unmangle the name.

Mangled name: _ZN15DemoModeManager12exitDemoModeEv
Original name: DemoModeManager::exitDemoMode()

It won't do any good to change the name, but you can use it to locate the code for the named function, and it tells you what arguments the function takes (none in this case.)

What kind of disassembler do I need to do that?

[boriar]

Originally Posted by tshering

The location of nickel and some of the stuff it depends on is /usr/local/Kobo.
...

Ok! Many thanks for your answer and sorry for the

[tshering]

Originally Posted by Nemo1984

What kind of disassembler do I need to do that?

You would use c++filt. There are also online demanglers like http://demangler.com.

[Nemo1984]

Thank you!

[ItalianUruguayan]

Originally Posted by tshering

Certainly, an interesting experiment. However, by the use of an older libnickel.so.1.0.0 you might lose several of the improvements of the newer version. Therefore you could as well stay with the older FW and prevent it from updating. On a side note, I forgot whether the FW version is hardcoded into nickel or libnickel.so.1.0.0. But if it is in libnickel.so.1.0.0, you might be forced to upgrade to the current FW when you sync with the Kobo server, just because you have an older libnickel.so.1.0.0.
Apart from staying with an older FW, you could try modify advboot that it starts the demoloop.sh script without nickel. I have never used the demo mode in nickel, so may be there are some advantages like auto sleep or auto power off. I do not know.

I might also mention that it is possible to have two versions of the reading software installed at the same device. I have currently running 4.3.8842, and 4.2.8110. You would of course use only the newer version, when you connect to the Kobo server.

tshering, I'm really interested in this. I love the chess app, so I'm sticking to 3.15.0 on my Glo HD. I was wondering if it would be possible to use a newer libnickel.so on this? I tried replacing the libnickel.so.1.0.0 file with the one on the 3.19.5761 firmware, but as soon as I rebooted the device was bricked and I had to do a factory reset. Would this work if I replace the entire /usr/local/Kobo folder?

[tshering]

Originally Posted by ItalianUruguayan

Would this work if I replace the entire /usr/local/Kobo folder?

If you replace this folder, you can as well update to 3.19.5761. Or which advantage do you expect from replacing only the /usr/local/Kobo?