MobileRead Forums - View Single Post

anarcat · 06-14-2021, 09:21 AM

Hi!

I stil have my Kobo Glo HD (on which I tested, coded and deployed wallabako, for those who know about that project

, but it's showing signs of age. The device is now about 6 years old, if my count is right, and while that's a respectable age for a computing device, I still have high hopes that I can keep using it for another 6.

The problem I'm having is that it seems to have trouble returning from sleep. At first, I couldn't quite figure out what the problem was: it would just seem to hang randomly. But now I feel it just is that: when the device times out into sleep, when I reopen the lid to start reading again, nothing happens: the display is stuck into whatever it was when I last closed the lid and it doesn't resume.

Tapping the power button doesn't resume from sleep either. Holding the power button turns the LED on very briefly, but then it goes off and never returns. Normally, the power button can be used to force-reboot the machine, but somehow that doesn't work: I've tried to hold the power button up to 20 seconds, no luck.

Plugging in the USB cord somehow makes the machine boot again: it then starts up Nickel normally and everything looks fine. Battery says "98%" and seems to charge normally. If I unplug the USB cord, I can use the device normally until the next suspend. If I suspend by hand and return soon after, it seems to recover correctly, so it doesn't happen *all* the time.

I am using koreader on that device, and I have tried to reinstall that, no luck. I also use Nickelmenu and plato, and I have done extensive hacking on the device to make various parts of wallabako work, so it could also be me that broke something, naturally. I haven't worked on wallabako for a long time now, so I doubt it's related. This feels more like a hardware / firmware issue.

My question is: what should I do with this? I've fallen back on using my Onyx Boox Note Pro 2 to read ebooks right now, but that's not really convenient: the device is really big and I don't like the built-in ereader that much. (You can install koreader through android, that said, but somehow font rendering is all aliased and weird, something which I need to bring up with the koreader folks.)

Alternatively, should I just get a new Kobo reader to replace this one? Are they still as hackable as they were?

06-14-2021, 09:21 AM	#1
anarcat Connoisseur Posts: 83 Karma: 192 Join Date: Jul 2013 Location: Planet Ocean Device: Kobo Glo HD, Onyx Boox Note Pro 2, Samsung Galaxy Tab S5e, Pixel 4a	fails to resume intermittently Hi! I stil have my Kobo Glo HD (on which I tested, coded and deployed wallabako, for those who know about that project , but it's showing signs of age. The device is now about 6 years old, if my count is right, and while that's a respectable age for a computing device, I still have high hopes that I can keep using it for another 6. The problem I'm having is that it seems to have trouble returning from sleep. At first, I couldn't quite figure out what the problem was: it would just seem to hang randomly. But now I feel it just is that: when the device times out into sleep, when I reopen the lid to start reading again, nothing happens: the display is stuck into whatever it was when I last closed the lid and it doesn't resume. Tapping the power button doesn't resume from sleep either. Holding the power button turns the LED on very briefly, but then it goes off and never returns. Normally, the power button can be used to force-reboot the machine, but somehow that doesn't work: I've tried to hold the power button up to 20 seconds, no luck. Plugging in the USB cord somehow makes the machine boot again: it then starts up Nickel normally and everything looks fine. Battery says "98%" and seems to charge normally. If I unplug the USB cord, I can use the device normally until the next suspend. If I suspend by hand and return soon after, it seems to recover correctly, so it doesn't happen all the time. I am using koreader on that device, and I have tried to reinstall that, no luck. I also use Nickelmenu and plato, and I have done extensive hacking on the device to make various parts of wallabako work, so it could also be me that broke something, naturally. I haven't worked on wallabako for a long time now, so I doubt it's related. This feels more like a hardware / firmware issue. My question is: what should I do with this? I've fallen back on using my Onyx Boox Note Pro 2 to read ebooks right now, but that's not really convenient: the device is really big and I don't like the built-in ereader that much. (You can install koreader through android, that said, but somehow font rendering is all aliased and weird, something which I need to bring up with the koreader folks.) Alternatively, should I just get a new Kobo reader to replace this one? Are they still as hackable as they were?