iRiver, please fix the bugs!!

greenapple · 06-23-2010, 10:12 PM

Why don't they fix the bad bugs on TXT and DOC formats?

I'm not asking for new features. Is it too much to ask that the basic formats, as specified in the product specs as being supported, be fixed ASAP?

Running out of patience.

greenapple · 07-01-2010, 01:23 AM

iRiver is trying to market the product even more widely without fixing the key formats:
http://iriverstory.blogspot.com/2010...ugendubel.html

MacEachaidh · 07-01-2010, 11:52 PM

Hi greenapple,
I noticed yesterday that the way the Story treats text (breaking words at the end of a line) also occurs on my iRiver B30 mp3 player -- both in displaying text files on-screen, and in the text-based selection menu in the B30's OS. It seems to just be iRiver's way of doing things, seeing text solely as a string of characters, not as discrete units called words. (It's like a 1970s terminal-based view of handling text, and really should be brought up to date.)

I've been watching out for updates to the "firmware" -- obviously, to no avail. Nothing's been forthcoming. And I suspect there won't be any update now, at least until iRiver has finished readying its new WiFi-enabled models and shipped them off to market.

If you look at iRiver's product history, none of its devices has enjoyed significant ongoing development -- they're generally superseded and replaced within less than a year of their release, and then become abandonware, with no further updates of their operating software. I understand the need for iRiver to maintain a revenue stream, but this is kinda hit-and-run.

I'm a little grumpy, because I discovered yesterday that the B30 (less than six months on the market, less than three months in my possession) has been discontinued, and its software is still in need of significant cleaning up. I anticipate the same thing happening to the Story. If I were a programmer I might try to get into the Story's interface through iRiver's open-source offering, but I don't have those skills. And I don't think I should have to develop them just to see a device I've paid for become fully functional.

06-23-2010, 10:12 PM	#1
greenapple Evangelist Posts: 404 Karma: 664 Join Date: Dec 2009 Device: Kindle Paperwhite, Kindle DX, Kobo Aura HD	iRiver, please fix the bugs!! Why don't they fix the bad bugs on TXT and DOC formats? I'm not asking for new features. Is it too much to ask that the basic formats, as specified in the product specs as being supported, be fixed ASAP? Running out of patience.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Classic Some bugs in 1.3	rfog	Barnes & Noble NOOK	23	06-21-2010 03:42 PM
What bugs you	SameOldStory	Reading Recommendations	28	05-24-2010 10:23 PM
Seriously thoughtful bugs	GeoffC	Lounge	5	11-21-2009 03:42 AM
Bugs on v5/PP	keng2000	Astak EZReader	2	11-02-2009 07:18 AM
Bugs ?	hannah	Calibre	4	06-15-2009 06:51 AM

07-01-2010, 01:23 AM	#2
greenapple Evangelist Posts: 404 Karma: 664 Join Date: Dec 2009 Device: Kindle Paperwhite, Kindle DX, Kobo Aura HD	iRiver is trying to market the product even more widely without fixing the key formats: http://iriverstory.blogspot.com/2010...ugendubel.html

07-01-2010, 11:52 PM	#3
MacEachaidh Browser Posts: 745 Karma: 578294 Join Date: Apr 2010 Location: Australia Device: Kobo Touch, Kobo Aura HD	Hi greenapple, I noticed yesterday that the way the Story treats text (breaking words at the end of a line) also occurs on my iRiver B30 mp3 player -- both in displaying text files on-screen, and in the text-based selection menu in the B30's OS. It seems to just be iRiver's way of doing things, seeing text solely as a string of characters, not as discrete units called words. (It's like a 1970s terminal-based view of handling text, and really should be brought up to date.) I've been watching out for updates to the "firmware" -- obviously, to no avail. Nothing's been forthcoming. And I suspect there won't be any update now, at least until iRiver has finished readying its new WiFi-enabled models and shipped them off to market. If you look at iRiver's product history, none of its devices has enjoyed significant ongoing development -- they're generally superseded and replaced within less than a year of their release, and then become abandonware, with no further updates of their operating software. I understand the need for iRiver to maintain a revenue stream, but this is kinda hit-and-run. I'm a little grumpy, because I discovered yesterday that the B30 (less than six months on the market, less than three months in my possession) has been discontinued, and its software is still in need of significant cleaning up. I anticipate the same thing happening to the Story. If I were a programmer I might try to get into the Story's interface through iRiver's open-source offering, but I don't have those skills. And I don't think I should have to develop them just to see a device I've paid for become fully functional.

Advert