Author |
Message |
![[Post New]](/jforum/templates/default/images/icon_minipost_new.gif) 07/09/2010 23:02:42
|
ronouel
Joined: 12/15/2009 05:41:53
Messages: 76
Offline
|
I flashed my JBL to release version 16 (not beta) obtained here
http://www.jetbook.net/update.php?refid=29532
I went to the middle of a couple of books, closed them, shut down and changed batteries, went back to same books and they were at page 1 (that's right, one). Checked settings, and 16 WAS installed.
Looks like 15G bug is back to me. Flashed back to 15D-B once again, and all works fine.
Could they have fixed this in 16 Beta, then reintroduced the same bug in 16 released?
|
|
 |
![[Post New]](/jforum/templates/default/images/icon_minipost_new.gif) 07/10/2010 18:14:10
|
Jerry
Joined: 06/28/2010 05:09:51
Messages: 908
Offline
|
ronouel wrote:I flashed my JBL to release version 16 (not beta) obtained here
http://www.jetbook.net/update.php?refid=29532
I went to the middle of a couple of books, closed them, shut down and changed batteries, went back to same books and they were at page 1 (that's right, one). Checked settings, and 16 WAS installed.
Looks like 15G bug is back to me. Flashed back to 15D-B once again, and all works fine.
Could they have fixed this in 16 Beta, then reintroduced the same bug in 16 released?
Hey ronouel,
0.16 beta and 0.16 is the same exact file so i'm not sure why the JBL could be having this problem. Maybe it is somehow isolated to your hardware. The only other thing i can think of is 0.16 didn't properly install. Maybe try installing it again directly from the beta thread https://www.ectaco.com/ectaco-posts/list/20002.page
Hope this helps.
|
|
 |
![[Post New]](/jforum/templates/default/images/icon_minipost_new.gif) 07/10/2010 23:18:34
|
ronouel
Joined: 12/15/2009 05:41:53
Messages: 76
Offline
|
Jerry- I never used 16 beta so I don't know what it did. We have another JBL I can try 16 on, but if it does what it did to mine, I'll have to flash back on that one too. Since I am getting weary of this, I may wait till someone else confirms or denies.
Are you saying that you have a JBL on your desk with v.16 firmware that is NOT doing this, or are you saying you have not even checked?
|
|
 |
![[Post New]](/jforum/templates/default/images/icon_minipost_new.gif) 07/11/2010 11:22:47
|
Jerry
Joined: 06/28/2010 05:09:51
Messages: 908
Offline
|
ronouel wrote:Jerry- I never used 16 beta so I don't know what it did. We have another JBL I can try 16 on, but if it does what it did to mine, I'll have to flash back on that one too. Since I am getting weary of this, I may wait till someone else confirms or denies.
Are you saying that you have a JBL on your desk with v.16 firmware that is NOT doing this, or are you saying you have not even checked?
Hey ronouel,
I think i am confused, by your first post i was under the impression that you downloaded v0.16 and still had this problem. Now in this post it seems you have not tried v0.16. (Again v0.16 and v0.16 beta are the same exact file, just different names).
In any case v0.16 should not have the problems described in the previous version (losing page after exiting a book and losing font size).
These bug fixes are described on the official jetbook firmware page here and on the beta testing thread [url=
This message was edited 1 time. Last update was at 07/11/2010 11:24:19
|
|
 |
![[Post New]](/jforum/templates/default/images/icon_minipost_new.gif) 07/11/2010 13:26:31
|
ronouel
Joined: 12/15/2009 05:41:53
Messages: 76
Offline
|
Flashed my wife's machine with released v. 16 and it works fine. Hers never had 15G on it.
Reflashed mine with beta 16, then released 16, and it now works fine also. The only thing I can postulate is that since mine had 15G on it at one time, the 15G bug may not have been purged with the reflash.
I think 16 beta and released are the same file anyway. Same bit count 54231040 and same date and time.
Another variation was that this time I did everything in Windows- extraction, format SD, and load folders on SD. The first time, some of it was done in Linux.
I'll never report a bug after this without attempting a second reflash first. The 15G bug was a good call, I'm not so sure about this one.
|
|
 |
|