Firmware 3.18.0 discussion - Page 14

oren64 · 10-03-2015, 08:45 AM

Quote:

Originally Posted by Nick_1964

Changed my answer as you changed yours.

you ask me to.

Quote:

Originally Posted by Nick_1964

So it is not right saying that when you take out the card and place that in a reader that it wants to format it, it doesn't.

I did't the say reader i say computer.

Quote:

Originally Posted by Nick_1964

When I use the ext3 plugin for windows,I can access the card without no problems and can locate the .kobo directory, the internal card has two partitions, on partition two I can see everything what is in the book,the same as what I would see when connecting to it when it was still in the reader with a filemanager over USB.

Interesting... but i think you still need to connect and reconnect the usb cable so in can detect "KoboRoot.tgz" file.

Nick_1964 · 10-03-2015, 08:53 AM

Quote:

Originally Posted by oren64

you ask me to.

I did't the say reader i say computer.

I ment a card reader in the computer.. sorry i wasn't clear about that.

Quote:

Interesting... but i think you still need to connect and reconnect the usb cable so in can detect "KoboRoot.tgz" file.

No... when turning on the power once opened and placed the Koboroot.tgz file or the update files for a complete upgrade on the card directly it does update, I revived my old Glo this way.

cmolinap · 10-03-2015, 01:48 PM

Hi,
I installed 3.18.0 in two Mini, without the patch, and running at 100%.

I'm definitely out of date: ¿why should apply the "patch"?
My rule of thumb is: if it's not broken, not there to fix it.
¿What is the function of the patch?

GeoffR · 10-03-2015, 03:16 PM

Quote:

Originally Posted by cmolinap

Hi,
I installed 3.18.0 in two Mini, without the patch, and running at 100%.

I'm definitely out of date: ¿why should apply the "patch"?
My rule of thumb is: if it's not broken, not there to fix it.
¿What is the function of the patch?

If you are happy with the way the Mini is working for you then don't patch it.

If there was something that you were not happy with then this thread describes some of the things that can be changed py patching.

Nick_1964 · 10-03-2015, 05:24 PM

Quote:

Originally Posted by cmolinap

Hi,
I installed 3.18.0 in two Mini, without the patch, and running at 100%.

I'm definitely out of date: ¿why should apply the "patch"?
My rule of thumb is: if it's not broken, not there to fix it.
¿What is the function of the patch?

There is no "the patch", the patch is a whole collection of improvements.
If you are happy with your 100 % why would you patch and go to 300% ¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿ (hate those things.., they remind me when I was a todler... 50 years ago or so..) .. grumble.. who let the door of the kindergarten open ... again...

WolfBack · 10-03-2015, 06:38 PM

If you thing you're happy with the virgin formats of the firmware, then you have to stay that way...
If you thing to make a step forward that make you happier, then take a tour in the patch section...
The only you have to lose is some of your time. You like it, then you keep it.. If is not, then you're roll back on the factory/usual condition...
IMHO, my reading life changes with that patches on both of my readers (aura classic & aura H2O).

aceflor · 10-04-2015, 05:09 AM

Quote:

Originally Posted by Nick_1964

There is no "the patch", the patch is a whole collection of improvements.
If you are happy with your 100 % why would you patch and go to 300% ¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿ (hate those things.., they remind me when I was a todler... 50 years ago or so..) .. grumble.. who let the door of the kindergarten open ... again...

Do you mean those "¿" ? You do realize that if cmolinap is a spanish native speaker, then he or she is just using it to punctuate the sentence, right ? I know they are weird in english, but obligatory in spanish....

Nick_1964 · 10-04-2015, 07:19 AM

Quote:

Originally Posted by aceflor

Do you mean those "¿" ? You do realize that if cmolinap is a spanish native speaker, then he or she is just using it to punctuate the sentence, right ? I know they are weird in english, but obligatory in spanish....

I didn't knew that about "¿" , in our language only kids are (mis)using it,but I was reading some previous messages of him before reply and in most of them he uses the normal one.
Thanks for pointing it out to me,and if it is the case, my apologies.

Off topic but if I would use all common sence characters used in my language on a forum where the spoken language is english, i would be banned

It was more the whole message.. he is more then 2 years active with e-readers (also in firmware topics), then jump in over "a" patch, not even knowing that there isn't just one only patch, asking himself why he needs a patch (I have some troubles using search but in almost every firmware topic there is a link to the patch that belongs to the firmware explaining what they do).

Then tells if it aint broken,don't fix it.. I can "follow " that logic for a big part but then:
Why putting firmware not mentioned/intended to be used on your two mini's (latest release for the mini is version 3.4.1 released in may 2014) on them if you follow that kind of logic ?

It triggered some irritation to me,and the tone of that I can taste in more reply's.

GeoffR · 10-04-2015, 09:46 PM

This has happened twice since I updated my Glo to 3.18.0, but it doesn't happen every time so it might not be related to the firmware version. Has anyone else seen this?

I sideloaded one new ePub using Calibre and the processing screen appeared to get stuck at 6%, but when I tapped on the screen it displayed the homescreen and everything was normal, the book had been successfully loaded.

Another time I sideloaded two new ePubs at the same time and the processing screen stuck at 50%, but again when I tapped the screen it displayed the homescreen and everything was normal.

By 'stuck' I mean I waited a few minutes and nothing happened (processing a book usually takes a few seconds.)

anavin · 10-04-2015, 10:47 PM

Quote:

Originally Posted by GeoffR

This has happened twice since I updated my Glo to 3.18.0, but it doesn't happen every time so it might not be related to the firmware version. Has anyone else seen this?

I sideloaded one new ePub using Calibre and the processing screen appeared to get stuck at 6%, but when I tapped on the screen it displayed the homescreen and everything was normal, the book had been successfully loaded.

Another time I sideloaded two new ePubs at the same time and the processing screen stuck at 50%, but again when I tapped the screen it displayed the homescreen and everything was normal.

By 'stuck' I mean I waited a few minutes and nothing happened (processing a book usually takes a few seconds.)

It happens on my H2O too, with 3.15.0 and 3.18.0.

icallaci · 10-05-2015, 01:15 AM

It happened to my H20 with 3.17.3 but not (so far) with 3.18.0.

BeeTee-Ess · 10-05-2015, 01:26 AM

Quote:

Originally Posted by cmolinap

Hi,
I installed 3.18.0 in two Mini, without the patch, and running at 100%.

I'm definitely out of date: ¿why should apply the "patch"?
My rule of thumb is: if it's not broken, not there to fix it.
¿What is the function of the patch?

Fair enough too.

However, I did apply a couple of Geoff's patches, mainly to maximise my use of the Mini's somewhat limited screen space. So, minimise margins, do away with headers and footers. Just the text of my books filling up the screen.

You have to read through the patch files, and selectively change 'no' to 'yes' for those you think will be helpful.

Nick_1964 · 10-05-2015, 07:17 AM

I have several times, with 3.17 and following up, that the device doesn't go into sleep after I transferred books on or off it, when disconnected from usb.. it stays on for hours with full light on, while the normal sleep time is 15 minutes..

Ripplinger · 10-05-2015, 08:31 AM

Quote:

Originally Posted by Nick_1964

I have several times, with 3.17 and following up, that the device doesn't go into sleep after I transferred books on or off it, when disconnected from usb.. it stays on for hours with full light on, while the normal sleep time is 15 minutes..

I've reported that behavior in the past as well for quite awhile. It started happening when they changed the order of shutdown so the light is no longer turned off first. So it's annoying that now you have to wait and watch if the light goes out or not.

It was suggested I changed my sleep timer to 5 minutes, which I really don't like it that short for normal usage, but that's what I did. It does seem to shut off itself after 5 minutes though, at least the times I've caught it and decided to watch it and time it.

It would be more livable if the light went out instantly like it used to, so you immediately know if you need to open and reclose the cover again instead of having to wait and see. I'm not very hopeful that they'll ever fix the bug so wishing for the best way to detect it will make it easier to deal with.

Nick_1964 · 10-05-2015, 08:44 AM

It happened again Yesterday.. I didn't closed the cover,it was not on any usb device but stays on forever, I let it stay on,this morning it was still with the current page of the book displayed,light was off and the device was dead.. no battery warning,nothing,not responding anymore to the on/off button, it needed the adapter to recover and then it switched to the home page by itself.. I opened the same page and leave it on my desk and after 15 minutes it just went into sleep modus.
I have not patched the sleep modus to another level, I don't use that part of the patch.

Had it also once that the device wake up and the light was out, the light section of the pull down menu wasn't on zero but at the normal percentage,but the light was out and changing the level didn't turn it on.. (i was afraid that it was broken) just pushed the on and off button once and it came back on..

Until now I didn't managed to re-occur both events to find out if there is a sequence to trigger it..

10-04-2015, 09:46 PM	#204
GeoffR Wizard Posts: 3,821 Karma: 19162882 Join Date: Nov 2012 Location: Te Riu-a-Māui Device: Kobo Glo	Processing screen stuck, but completes normally after tapping the screen. This has happened twice since I updated my Glo to 3.18.0, but it doesn't happen every time so it might not be related to the firmware version. Has anyone else seen this? I sideloaded one new ePub using Calibre and the processing screen appeared to get stuck at 6%, but when I tapped on the screen it displayed the homescreen and everything was normal, the book had been successfully loaded. Another time I sideloaded two new ePubs at the same time and the processing screen stuck at 50%, but again when I tapped the screen it displayed the homescreen and everything was normal. By 'stuck' I mean I waited a few minutes and nothing happened (processing a book usually takes a few seconds.) Last edited by GeoffR; 10-04-2015 at 09:50 PM. Reason: spelling

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Firmware 3.17.3 Discussion	PeterT	Kobo Reader	258	09-16-2015 09:13 AM
Firmware 3.16.0 Discussion	davidfor	Kobo Reader	240	08-14-2015 12:52 PM
Firmware 3.16.10 Discussion	murg	Kobo Reader	35	08-12-2015 02:08 PM
Firmware 3.15 discussion thread	Lynx-lynx	Kobo Reader	276	07-04-2015 07:33 AM
New Firmware (1.4) Discussion	Stinger	Kobo Reader	103	07-22-2010 12:02 PM

10-03-2015, 01:48 PM	#198
cmolinap Enthusiast Posts: 36 Karma: 9792 Join Date: Mar 2013 Location: Guatemala City, Guatemala. Device: Kobo Touch/Mini	Hi, I installed 3.18.0 in two Mini, without the patch, and running at 100%. I'm definitely out of date: ¿why should apply the "patch"? My rule of thumb is: if it's not broken, not there to fix it. ¿What is the function of the patch?

10-03-2015, 06:38 PM	#201
WolfBack Zealot Posts: 122 Karma: 130628 Join Date: Aug 2015 Location: Athens, Greece Device: Kobo Aura 6'', Kobo Aura H2O, Kobo Glo HD	If you thing you're happy with the virgin formats of the firmware, then you have to stay that way... If you thing to make a step forward that make you happier, then take a tour in the patch section... The only you have to lose is some of your time. You like it, then you keep it.. If is not, then you're roll back on the factory/usual condition... IMHO, my reading life changes with that patches on both of my readers (aura classic & aura H2O).

10-05-2015, 01:15 AM	#206
icallaci Guru Posts: 820 Karma: 6528026 Join Date: Sep 2012 Device: Kobo Elipsa	It happened to my H20 with 3.17.3 but not (so far) with 3.18.0.

10-05-2015, 07:17 AM	#208
Nick_1964 Bookworm Posts: 975 Karma: 768585 Join Date: Aug 2010 Location: Netherlands Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo	I have several times, with 3.17 and following up, that the device doesn't go into sleep after I transferred books on or off it, when disconnected from usb.. it stays on for hours with full light on, while the normal sleep time is 15 minutes..

10-05-2015, 08:44 AM	#210
Nick_1964 Bookworm Posts: 975 Karma: 768585 Join Date: Aug 2010 Location: Netherlands Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo	It happened again Yesterday.. I didn't closed the cover,it was not on any usb device but stays on forever, I let it stay on,this morning it was still with the current page of the book displayed,light was off and the device was dead.. no battery warning,nothing,not responding anymore to the on/off button, it needed the adapter to recover and then it switched to the home page by itself.. I opened the same page and leave it on my desk and after 15 minutes it just went into sleep modus. I have not patched the sleep modus to another level, I don't use that part of the patch. Had it also once that the device wake up and the light was out, the light section of the pull down menu wasn't on zero but at the normal percentage,but the light was out and changing the level didn't turn it on.. (i was afraid that it was broken) just pushed the on and off button once and it came back on.. Until now I didn't managed to re-occur both events to find out if there is a sequence to trigger it..

Advert

Advert