problem with Havon N516

plutino · 10-25-2011, 05:37 PM

I have used OIP 2.2 for a while. Recently I tried to upgrade to a few daily build. After one upgrade (I don't know which one), the internal storage of the device can only be mounted read-only. I reflashed a few different versions, including the 2.2, but the problem is still there. I also tried to ssh to the device and manually mount the partition, but still it goes to read-only. I suspect that the memory chip is somehow broken. Is there any way to tell whether this is a hardware or software problem?

Thanks.

lunohod · 10-26-2011, 02:03 AM

You could try to format the storage manually:

Code:

mkfs.vfat -F32 -n @VOLUME@ -m /dev/null /dev/mtdblock_storage
mount /mnt/storage

And I would suggest to install the latest flashimage over USB.

plutino · 10-26-2011, 01:27 PM

Thanks lunohod. Formatting the internal storage doesn't work. I don't have access to a windows computer now, so I tried to flash the reinstall firmware for 0.2.2 (cannot find one for the daily build), and it worked! Now I can have my FBreader preference saved again.

I got another question, which is why I frequently reflash the daily build recently. When reading utf-8 coded txt files in FBreader, the non-ASCII characters are not rendered right (most noticeably the quotation marks). I tried nearly all the combinations for language/coding/font, but nothing works. They are rendered correctly in coolreader, though. Do you have any thoughts on this?

Quote:

Originally Posted by lunohod

You could try to format the storage manually:

Code:

mkfs.vfat -F32 -n @VOLUME@ -m /dev/null /dev/mtdblock_storage
mount /mnt/storage

And I would suggest to install the latest flashimage over USB.

lunohod · 10-28-2011, 04:55 AM

Quote:

Originally Posted by plutino

I got another question, which is why I frequently reflash the daily build recently. When reading utf-8 coded txt files in FBreader, the non-ASCII characters are not rendered right (most noticeably the quotation marks). I tried nearly all the combinations for language/coding/font, but nothing works. They are rendered correctly in coolreader, though. Do you have any thoughts on this?

Show me some screenshots with good and bad rendering.

plutino · 10-29-2011, 01:18 AM

I attached screenshots of the same text in FBreader and CoolReader.

Quote:

Originally Posted by lunohod

Show me some screenshots with good and bad rendering.

Jellby · 10-29-2011, 03:40 AM

That's clearly a problem with the encoding (the fact that a single character shows as a series of wrong ones means that a multi-byte encoding is being rendered as a 8-bit encoding). Either something's wrong with the file or FBreader is not doing the right thing.

Maybe FBreader defaults to an 8-bit encoding, and has no problem with HTML files where the encoding is explicit in the header, but with text files with no indication, it doesn't guess or guesses wrong. CoolReader probably has a different default or guesses right.

JSWolf · 10-29-2011, 03:52 AM

Quote:

Originally Posted by plutino

I attached screenshots of the same text in FBreader and CoolReader.

Nice downloaded illegal eBook.

plutino · 10-30-2011, 12:14 AM

The file was processed in Emacs and I've specified the coding to be utf-8. In desktop version of FBreader, it's rendered fine. How to force an encoding in OIP version of FBreader? I only see options to set default encoding (which is already utf-8).

Quote:

Originally Posted by Jellby

That's clearly a problem with the encoding (the fact that a single character shows as a series of wrong ones means that a multi-byte encoding is being rendered as a 8-bit encoding). Either something's wrong with the file or FBreader is not doing the right thing.

Maybe FBreader defaults to an 8-bit encoding, and has no problem with HTML files where the encoding is explicit in the header, but with text files with no indication, it doesn't guess or guesses wrong. CoolReader probably has a different default or guesses right.

10-25-2011, 05:37 PM	#1
plutino Junior Member Posts: 5 Karma: 10 Join Date: Nov 2009 Device: boox	problem with Havon N516 I have used OIP 2.2 for a while. Recently I tried to upgrade to a few daily build. After one upgrade (I don't know which one), the internal storage of the device can only be mounted read-only. I reflashed a few different versions, including the 2.2, but the problem is still there. I also tried to ssh to the device and manually mount the partition, but still it goes to read-only. I suspect that the memory chip is somehow broken. Is there any way to tell whether this is a hardware or software problem? Thanks.

10-26-2011, 02:03 AM	#2
lunohod OpenInkpot developer Posts: 207 Karma: 481 Join Date: Mar 2008 Location: Stuttgart, Germany Device: N516,V3,PRS505,iLiad,eSlick, E60,Kindle3,M90,PB912	You could try to format the storage manually: Code: mkfs.vfat -F32 -n @VOLUME@ -m /dev/null /dev/mtdblock_storage mount /mnt/storage And I would suggest to install the latest flashimage over USB.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Hanvon/Hexaglot Hanvon N516 Review	DocChip	Andere Lesegeräte	110	02-03-2011 03:42 PM
hanvon n516	kalioon	Which one should I buy?	0	12-05-2010 05:37 AM
Long review of Azbooka N516 (Hanvon n516)	igorsk	News	3	02-17-2010 07:25 AM
Applications for n516	azbooka	OpenInkpot	0	12-31-2009 02:38 PM
hanvon n516	jjim	Calibre	2	12-26-2009 10:07 AM

10-29-2011, 03:40 AM	#6
Jellby frumious Bandersnatch Posts: 5,196 Karma: 2508097 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon	That's clearly a problem with the encoding (the fact that a single character shows as a series of wrong ones means that a multi-byte encoding is being rendered as a 8-bit encoding). Either something's wrong with the file or FBreader is not doing the right thing. Maybe FBreader defaults to an 8-bit encoding, and has no problem with HTML files where the encoding is explicit in the header, but with text files with no indication, it doesn't guess or guesses wrong. CoolReader probably has a different default or guesses right.


Advertisement Enthusiast