Firmware 4.33.19608

[Deobulakenyo]

Originally Posted by tschucha

The bug where the led power light turns off after about 5 seconds is still there on the Kobo Sage.

To duplicate:

Plug USB3 power cable into Kobo Sage
White LED lights up
After a few seconds LED goes off
Device will continue to charge, just no LED indication

Same with my Libra 2. When you connect it to a charger, led lits up, then blinks a few times, then turns off. It still charges though without the led. And yes, the led when charging setting is turned to ON.

[MGlitch]

Originally Posted by NiLuJe

You might have been thinking of my comments about the Sage: essentially same board as the Elipsa, but with half the RAM (i.e., 512MB), but the same (roughly) large (ish) amount of reserved memory by the sunxi display driver.

The only thing I'd have to say about the Libra 2 is that it's probably the most finicky kernel we've seen, but the impact of that is hangs/crashes, nothing RAM related (almost all of the issues I've seen on that front are epdc related, and possibly power delivery adjacent). Then again, confirmation bias: the epdc is what I care about most, so I'm bound to notice those more than the average Joe ;p .

Yes, I believe it was you. I was torn between you and frostshultz though I don't believe he's got his hands on a libra 2 or the Sage for that matter.

I wonder if that could have been the root of the issue PetBest reported, though I'd stand by my previous comment of not wanting to spend too much time or mental energy until/unless the issue returns and is at least mildly repeatable. It'd be a bit like throwing pebbles down a well to try and measure the distance from the top of the well to the top of a barn, and down that path madness lies.

[koboy]

Originally Posted by MGlitch

I was torn between you and frostshultz though I don't believe he's got his hands on a libra 2 or the Sage for that matter.

the last post is rather interesting, if you like that sort of thing https://www.mobileread.com/forums/sh...342428&page=59

best wishes koboy

[snarkophilus]

I got a Libra 2 on Thursday, copied over my Aura setup from these great instructions, patched with geek1011's patchkit with about 14 patches enabled, and have read for about 3 or 4 hours without a glitch.

[windirt]

Originally Posted by Deobulakenyo

I read for about two hours last night and i have yet to experience a freeze/hang that i experienced in 4.32 fw.

I use 14 patches, nickelmenu and nanoclock.

I upgraded my Libra2 to 4.33 and applied a couple of space reduction patches. Heavy use for a day without the usual 4.32 freeze.

So I tried to install nanoclock, in a few hours of use encountered two crashes, the crash means no response when turning the page, the reader automatically restarted after a few seconds, I lost the progress of this reading.

Since you are not experiencing crashing problems with nanoclock, I wonder if some setting in my nanoclock is causing the crash, please refer to my nanoclock.ini which in the attachment. Maybe I have enabled a setting that you have not enabled.

[rcentros]

Installation of 4.33 seems to have gone well on my Clara HD. I was having problems with my side-loaded fonts and now I'm not. So it looks good so far.

[tschucha]

Originally Posted by Deobulakenyo

Same with my Libra 2. When you connect it to a charger, led lits up, then blinks a few times, then turns off. It still charges though without the led. And yes, the led when charging setting is turned to ON.

I wish they'd fix this damn thing - it worked with the stock firmware (4.28 or 4.29 I forget which) and has been broken since then.

[NiLuJe]

@windirt: There's a giant warning in NanoClock about the Libra 2 being a crashing mess, and NanoClock being the perfect way to make that worse .

So, yes, it's probably not helping .

(Hell, depending on the alignment of the planets, you might not even be able to successfully *boot* a Libra 2 with NanoClock enabled...).

[DrChiper]

Originally Posted by Deobulakenyo

Same with my Libra 2. When you connect it to a charger, led lits up, then blinks a few times, then turns off. It still charges though without the led. And yes, the led when charging setting is turned to ON.

On the Libra 2, and like the Wifi/Bluetooth entanglement, there seems to be also some connection between the Led and USB-C. When I have had the connection menu popup (for instance due to making a physical connection to my PC) and I then press Cancel, the Led remains on when putting the reader in sleep while charging. Thereafter, it remains on until charged 100%.

[NiLuJe]

That's because none of this is a bug, the new behavior is correct. The LED is powered down when the device itself is powered down or in a low power state (i.e., suspend to RAM). There was an issue where being plugged in could prevent the device from successfully entering a low power state, which, besides making your charge time longer, and potentially confusing Nickel's idea of how to suspend the device later on, caused the charging LED to stay on. *That* was a bug .

[DrChiper]

Originally Posted by NiLuJe

[...] or in a low power state (i.e., suspend to RAM).

So low powered state = "sleep" mode?
If so, what is then the state in "sleep" mode with an attached USB charging cable? Because in my case, then the led is continuously on.

[tschucha]

So this LED behavior is intentional? On my wife's Forma the LED light stays on when plugged into the power. Of course the Forma has a USB-B and not a USB-C.

By the way - the power required to keep the LED constantly on cannot be very much.

They should either make this an option or go back to the old way of leaving the light on so you can easily see if the power connection is solid.

[Deobulakenyo]

Originally Posted by NiLuJe

That's because none of this is a bug, the new behavior is correct. The LED is powered down when the device itself is powered down or in a low power state (i.e., suspend to RAM). There was an issue where being plugged in could prevent the device from successfully entering a low power state, which, besides making your charge time longer, and potentially confusing Nickel's idea of how to suspend the device later on, caused the charging LED to stay on. *That* was a bug .

So what then is the purspose of the setting to toggle "Indicator light while charging" if the indicator light won't be on while charging?

[Deobulakenyo]

Originally Posted by windirt

I upgraded my Libra2 to 4.33 and applied a couple of space reduction patches. Heavy use for a day without the usual 4.32 freeze.

So I tried to install nanoclock, in a few hours of use encountered two crashes, the crash means no response when turning the page, the reader automatically restarted after a few seconds, I lost the progress of this reading.

Since you are not experiencing crashing problems with nanoclock, I wonder if some setting in my nanoclock is causing the crash, please refer to my nanoclock.ini which in the attachment. Maybe I have enabled a setting that you have not enabled.

I have wrestled with nanoclock for a long time since i bought my Libra 2 (disappearing clock after connecting to PC and refreshing the database) until NiLuJe fixed it with the latest version. Make sure uou use the very latest one. If the problem persists, i will give you my config.ini and you can try that.

[windirt]

Originally Posted by Deobulakenyo

I have wrestled with nanoclock for a long time since i bought my Libra 2 (disappearing clock after connecting to PC and refreshing the database) until NiLuJe fixed it with the latest version. Make sure uou use the very latest one. If the problem persists, i will give you my config.ini and you can try that.

yes, I'm using the 0.11.3, but I saw the 0.11.4 just released.