Just got firmware 3.3.0

[Gordo29]

Hi

Updated to 3.3.0 shortly after it became available via wifi on my Touch. Have noticed that the cover of the book I'm reading (epub, sideloaded with Calibre) shows when it goes to sleep, but disappears when it powers down. When reading a kobo book (downloaded from Kobo) the cover shows both when sleeping and when powered down. Is this a bug with 3.3.0? I never noticed this with 3.2.

My screensaver setting is "Show current read" checked but not show covers full screen.

Anyone else?

[Joques]

Originally Posted by vice-versa

I don't know if it's a known issue (I can't read all the threads and even in a threads, sometimes all the posts) but I wanted to set the font to kobo Nickel (with 3.2.0) and I had huge line spacing even if it was set to zero. With 3.3.0, it seems to be fixed but I became used to Malabar and now that it "works", I don't want it anymore

Very strange. On my HD, the line spacing is still way too wide in 3.3.0. I had to use the patcher to bring it down to the level of the other fonts.

[anacreon]

Originally Posted by samhy

Do you mean that you let the light on? Because an "open book" doesn't use much more battery than the sleep screen The main difference is whether the IR sensors are on or off, isn't it?

Yes, I practically always have the light on for a better contrast, though it is on a much lower level when I read at night, which is when I mostly forget that since 3.3 I must turn it off manually (I read until I drop asleep).

[speakingtohe]

Originally Posted by samhy

Do you mean that you let the light on? Because an "open book" doesn't use much more battery than the sleep screen The main difference is whether the IR sensors are on or off, isn't it?

Pretty sure the ir sensors stay on. My mini I carried in my backpack or pocket and the battery discharged very quickly at times. Sometimes in a day. Would last for weeks with far more usage when I was using it at home only. Sony 350 was the same. The sensors being on is probably not a problem but the fact that they are being interrupted a lot on occasion.

I poked and prodded my 30 for a day or so once when it was off and that seemed to make the battery deplete which is strange as using the touchscreen to turn pages when it is on does not seem to do this.

Helen

[robko]

Originally Posted by anacreon

Yes, I practically always have the light on for a better contrast, though it is on a much lower level when I read at night, which is when I mostly forget that since 3.3 I must turn it off manually (I read until I drop asleep).

You might want to try to manually patch to 3.3.1 again or do a factory reset. Not autosleeping isn't a common issue with 3.3.1 so something is likely corrupted in your firmware.

[samhy]

Originally Posted by speakingtohe

Pretty sure the ir sensors stay on. My mini I carried in my backpack or pocket and the battery discharged very quickly at times. Sometimes in a day. Would last for weeks with far more usage when I was using it at home only.

From experience, my Mini tends to "wake up" by itself in my bags. I'm pretty sure that something is pushing the slider ever so slightly but that's enough to exit the sleep screen. Sometimes several sentences are selected, waiting to be highlighted, or I find myself in a chapter different from the one I was reading before putting the Mini in my bag/pocket

Yet I believe that the IR sensors are off when the device is sleeping because when I put my finger on the screen nothing happens.

[speakingtohe]

Originally Posted by samhy

From experience, my Mini tends to "wake up" by itself in my bags. I'm pretty sure that something is pushing the slider ever so slightly but that's enough to exit the sleep screen. Sometimes several sentences are selected, waiting to be highlighted, or I find myself in a chapter different from the one I was reading before putting the Mini in my bag/pocket

Yet I believe that the IR sensors are off when the device is sleeping because when I put my finger on the screen nothing happens.

Nothing visible happens anyway. When my mini and 350 were in my backpack they were in a small fairly snug zippered pocket inside. Not much chance of anything activating the slider switch AFAICS. And the quick power drain happened fairly frequently but never happened on either at home.

Anyway who cares really except at that horrible moment when you are facing a long ride or a long wait with nothing to read and so far I have survived even that.

Helen

[BeeTee-Ess]

Originally Posted by davidfor

Here is what I know has changed in 3.3.0:
...
There is a very interesting hidden change. Add the following lines to the config file:

[FeatureSettings]
FullScreenReading=true

Then go to the "Reading settings" page of the settings. The screen is messed up on the Glo, but, there should be a new section titled "Page layout" with one option. The options is "Show header and footer". It works as advertised and for both epubs and kepubs. If you make the change from within a book, you might need to reopen the book for it to take affect.

Thanks David...

My Mini has spent a long time on the shelf. You have just turned it into my favourite eReader!

[Risto40]

just synced my Glo and got version v3.3.0. Now, when the light is on, then after every tap on the screen, the screen blinks/refreshes. Very annoying when playing some game.

[corroonb]

I'm getting fairly regular crashes on my Kobo Touch with this firmware. The touch screen suddenly becomes unresponsive and the home button fails to work also. I have to hold the power button down for a while and then I can use the power button to turn it on. I think maybe that the automatic sync is bugged because the front page show a sync was performed just when the crash occurred and the battery was depleted by about 10% which happens when I sync. I have automatic sync and Wi-Fi disabled.

[GeoffR]

There has been a change in the way the font weight/sharpness settings are stored in the .conf file, each now has a single numerical parameter, so easier to tweak by editing the file if you can't get the weight/sharpness setting you want from the slider.

3.2.0:

readingFontSharpness\Dark%20Courier="@Variant(\0\0\0\x87=\b\x88\x89)"
readingFontWeight\Dark%20Courier=@Variant(\0\0\0\x87>\x99\x99\x9a)

3.3.1

readingFontSharpness\Dark%20Courier=0.0466666666666667
readingFontWeight\Dark%20Courier=0.34

Edit: On my Glo the slider sets the font weight from -0.2 to 0.8 (default 0.1), and sharpness from -0.4 to 0.2 (default -0.0667)

[read a lot]

Hi, new to the forum.
Need help with Kobo Aura HD.
Have updated reader to 3.31 and can no longer play solitaire without the screen flashing unbearably each time touched.
After speaking to Kobo help they want me to reset the reader. Before I do that can anyone please tell me, with the new update does their Solitaire work as it should, or is everyone having the same problem with the flashing screen.
Answers and help appreciated.
June
Australia

[toddos]

Originally Posted by read a lot

Hi, new to the forum.
Need help with Kobo Aura HD.
Have updated reader to 3.31 and can no longer play solitaire without the screen flashing unbearably each time touched.
After speaking to Kobo help they want me to reset the reader. Before I do that can anyone please tell me, with the new update does their Solitaire work as it should, or is everyone having the same problem with the flashing screen.
Answers and help appreciated.
June
Australia

I haven't tried solitaire, but I frequently play Sudoku on my Aura 6" and have noticed worse flickering on 3.3.0. It only happens on certain actions (deleting pencil marks is guaranteed to flicker, for example), but it definitely happens. I didn't have significant flicker with 3.2.0, so it definitely looks like a regression.

[Linton]

Originally Posted by read a lot

Hi, new to the forum.
Need help with Kobo Aura HD.
Have updated reader to 3.31 and can no longer play solitaire without the screen flashing unbearably each time touched.
After speaking to Kobo help they want me to reset the reader. Before I do that can anyone please tell me, with the new update does their Solitaire work as it should, or is everyone having the same problem with the flashing screen.
Answers and help appreciated.
June
Australia

This is a known problem introduced with 3.3.0. The same thing happens I believe with the web browser. Kobo support have agreed it's a bug and have told me it will be fixed in the next version.

[Halvah]

Originally Posted by booklover6

Oh no, don't do that. It has to go in the .kobo folder. You can mess the device up, putting it in the main folder!

I'm also attempting to sideload FW v3.3.0 (the Mark 4 hardware version) onto my Kobo Glo for the first time. Using explorer, when I look into the main drive I see the .kobo directory. When I click on the .kobo directory it opens and I see various files like KoboReader sqlite, some .conf files and six directories including another one called Kobo.

Which Kobo directory do I copy the unzipped v.3.3.0 files to: .kobo or the Kobo directory within the .kobo directory?

Thanks for any advice.