[Grimlin]

Originally Posted by vzw8130audible

OK. Been using release version 68 for about 5 hours now. I tried to copy some books over via my SD card and they're not showing up in My Library. Funny thing is, a title I deleted from my SD card (added in the old version, before I could log in) still appears... Frustrating as heck.

Only thing i can guess that I am doing differently is that I am transferring the files to my SD card by placing it in a USB card reader, rather than by linking my BlackBerry to my PC. Does that make any difference?

That information is stored in the RMS database on the blackberry. If you go into options/advanced options/applications and remove audible, it will clear that cache. When you reinstall it from the beta download, it will rescan your local file store and be clean again.

I never transfer over USB. I always pull my card out and transfer with the Card reader in my laptop as it is faster. No problems doing either way in my experience though.

[vzw8130audible]

FYI: While for most files (pdf, txt, etc.) SD cards are just a portable storage device. When transferring audible media files to your BBerry, the SD card will need to be onboard or the files won't be recognized by your So, if you use a card reader and then eject the SD card and jack it in your , your doesn't see the media files. If you make the same transfer via the connected via USB to your PC with the SD inside the , everything is wonderful.

A bit counterintuitive for me, but now that I know how it works, not exactly what I'd call a Bug.

[Grimlin]

Originally Posted by vzw8130audible

FYI: While for most files (pdf, txt, etc.) SD cards are just a portable storage device. When transferring audible media files to your BBerry, the SD card will need to be onboard or the files won't be recognized by your So, if you use a card reader and then eject the SD card and jack it in your , your doesn't see the media files. If you make the same transfer via the connected via USB to your PC with the SD inside the , everything is wonderful.

A bit counterintuitive for me, but now that I know how it works, not exactly what I'd call a Bug.

Strange that you are experiencing it that way. Do you have Content Protection enabled under options/security/general settings?

[vzw8130audible]

does the audibleair server get "congested"?

ever since the first time I connected (successfully), It's been timing out on me. Is this Verizon's revenge once again?

[Grimlin]

Originally Posted by vzw8130audible

does the audibleair server get "congested"?

ever since the first time I connected (successfully), It's been timing out on me. Is this Verizon's revenge once again?

I have never had that happen to me, so unfortunately I can't comment on it. Anyone else not on Verizon getting that issue?

[vzw8130audible]

...the battery, that is. For us 8130 users, that's the reset button.

the path from not seeing my downloaded audio to seeing it again was a simple reset. Now, I just need to figure out if it is Audible that is putting me in the place where I need to reset my . If that's the case, this might be a bug.

more to come.

[Grimlin]

Originally Posted by vzw8130audible

...the battery, that is. For us 8130 users, that's the reset button.

the path from not seeing my downloaded audio to seeing it again was a simple reset. Now, I just need to figure out if it is Audible that is putting me in the place where I need to reset my . If that's the case, this might be a bug.

more to come.

There is a nice soft reset app as well. Just a big reset button when you launch it. I installed it on my daughter's 8100.

[gpc]

Have opportunity to chnage to cell south and the 8830 cdma phone they have. Would be nice as cell south has much better signal within my home. However have read where several have had media problems with 8830 and not sure if all are cdma phones. Anyone here testing or using audible on 8830 with cdma? Would appreciate your feedback very much.

Just now moving to 1.68 as I was so pleased with the improvements on 1.64 I hated to change. Popping has gotten worse on 1.64, may have just been by book. Going to listen to same book on 1.68 and see if it changes.

Really appreciate audibles efforts to upgrade and improve our software.

[ValB626]

Still on 1.0.66 here, requested access to 1.0.68 to try.

Discovered that my download problems were absolutely signal-strength related. In DC this week (vs rural PA), I had no problems with subscriptions updating on time or downloading books.

Looking forward to testing 1.0.68.

Anyone else finding themselves buying more content to support beta testing? (hehehe, a good excuse anyway)

[gpc]

It is great to finally hear the end of a book on audible. Also, the first hour seems to have far less popping noises on 1.68 than on 1.64.

By the way to upgrade, you are not required to ask each time, just go back to the original download address they gave you and reload it as they have upgraded it to the newest beta version. I also emailed and asked permission to upgrade the first time.

Words on my screen seem to be running together at time, maybe just the third and fourth line when buffering and on device is appearing in bottom of line that has title. Not a biggie as I don't normally wear my reading glass and can't normally see anyway.

[ValB626]

Thanks, GPC. Just installed it.

Download was quick, even with my weak signal here at home, and the app initially started up MUCH faster than with v. 1.0.66.

However, after closing the app and then re-starting it, it hung again at that last 3/4-7/8 point on the blue progress bar. Got the occasional red-arrow download icon and hour-glass icon. It eventually started and went to the player with a "No file loaded" message. The menu wouldn't come up using the button to the left of the trackball, but the "go to My Library" button (3) worked. Selected a book from my local playlist to play, but got the "too many threads" error and the app closed. Pulled the battery, and it's was as slow to start up as in the previous version.

After the initial installation (before closing and re-starting): the books and subscription issues on my media card showed up just fine and I no problem logging in to my account. The submenu for "issues", under subscriptions, was still doing a fast flicker (no biggy, just noting it). My bad signal is not permitting me to download new issues of my subscriptions or any books. Will try again where I have a better signal.

After the battery pull and re-start, it went to the player showing "no file loaded" again (which was accurate). The button to the left of the menu was working to "go to My Library" this time.

Have to say I don't like having the new trackball volume control either, but my hard volume buttons on the 8130 were working in v 1.0.66. They are still working.

Within the player, the 9 button (advance to next section) worked fine. Used the FF (6) button to try to find my previous location in the second section of the book I had been listening to before downloading the new version (no bookmark, of course, as it was lost during the upgrade). Got multiple hourglass icons, a relatively short buffering message, and didn't start playing at the new location, so when I hit 5, it reset itself to the beginning of section 1 of the book. Hit 9 to go to section 2 again, then FF(6) again to look for my place in that section. This time, after iconing and buffering, it started playing at the new location without me hitting 5. I was still too early in the book, so I hit FF(6) again, got some buffering, then it reset itself back to the beginning of section 1. Went through the navigation sequence for a third? fourth? time, it didn't start playing at the new location by itself this time, so I hit 5, it began playing and didn't reset to the beginning of the book.

Am listening now for the 4-minute pop, as well as the garbling/speed changes that occurred during extended listens (several hours) in v 1.0.66.

Getting slow flickering on the player menu in this version.

[ValB626]

Originally Posted by vzw8130audible

does the audibleair server get "congested"?

ever since the first time I connected (successfully), It's been timing out on me. Is this Verizon's revenge once again?

I'm also on VZW and have found that download errors and timeouts are dependent on my signal strength. Even though my BB usually shows it's on 1XEV with 3 bars in rural PA, I can't download any content from here (altho I could download the app and log in), but have no problems in other locations.

[DallasFlier]

I've used .68 a fair bit today, and Grimlin I concur with the 6 items you still have listed as "bugs" now in the first post. Actually, I believe the "popping" has regressed and is a bit worse in .68 than it had been in .66. My opinion about the 6 listed bugs - the first three are really problematic and really need to be addressed. The other 3, for me, are minor annoyances I'm not too worried about. As for buffering, there needs to be LESS calling of the buffering - to avoid the multiple calls I've documented before - and if there's ANY way, the abominably slowness of the "buffering" event (longer than 30 seconds each time) needs to be improved.

[Ripley 29]

Originally Posted by ValB626

Within the player, the 9 button (advance to next section) worked fine. Used the FF (6) button to try to find my previous location in the second section of the book I had been listening to before downloading the new version (no bookmark, of course, as it was lost during the upgrade). Got multiple hourglass icons, a relatively short buffering message, and didn't start playing at the new location, so when I hit 5, it reset itself to the beginning of section 1 of the book. Hit 9 to go to section 2 again, then FF(6) again to look for my place in that section. This time, after iconing and buffering, it started playing at the new location without me hitting 5. I was still too early in the book, so I hit FF(6) again, got some buffering, then it reset itself back to the beginning of section 1. Went through the navigation sequence for a third? fourth? time, it didn't start playing at the new location by itself this time, so I hit 5, it began playing and didn't reset to the beginning of the book.

Am listening now for the 4-minute pop, as well as the garbling/speed changes that occurred during extended listens (several hours) in v 1.0.66.

It sounds like you are experiencing similar issues to the ones that I am having.. FF sometimes resetting back to the beginning of Section 1.

Also, the speed changes during listening. Are we the only two experiencing these issues, or are these also documented somehwhere? I get the speed changes constantly on my 8830, somtimes for minutes at a time.

[ValB626]

Originally Posted by Ripley 29

Also, the speed changes during listening. Are we the only two experiencing these issues, or are these also documented somehwhere? I get the speed changes constantly on my 8830, somtimes for minutes at a time.

Haven't experienced speed changes yet with the new version, but at the end of the second section of the book I was listening to today, and during the beginning of the third, I began hearing “corrupted” media file sounds again (i.e., short, high-pitched skreetches in the background that don’t interfere with hearing the content but are annoying, like fingernails on a blackboard). I tried pause/play, which sometimes worked in 1.0.66 for the speed changes, but that didn’t stop it. So I bookmarked my place, closed the app, and restarted it. This solved the skreetching problem during that listen.

I email a request to audible to decrease the volume of the audio tone(s) that accompanies setting a bookmark, selecting one to play, or deleting one. Hurts my ears! My volume setting for the player doesn't affect the loudness of this tone.

Managed to find a different location at home where I was able to OTA DL 29:59 mins of a book (setting was for 30 mins) at 21 KB/sec. But it did work!

[Grimlin]

Originally Posted by DallasFlier

I've used .68 a fair bit today, and Grimlin I concur with the 6 items you still have listed as "bugs" now in the first post. Actually, I believe the "popping" has regressed and is a bit worse in .68 than it had been in .66. My opinion about the 6 listed bugs - the first three are really problematic and really need to be addressed. The other 3, for me, are minor annoyances I'm not too worried about. As for buffering, there needs to be LESS calling of the buffering - to avoid the multiple calls I've documented before - and if there's ANY way, the abominably slowness of the "buffering" event (longer than 30 seconds each time) needs to be improved.

I had a thought about the buffering. What if the first buffer was small 30sec of content? Would buffer in about 4sec. Then it increased to the 4min which it could buffer in the background during that 30sec of audio. This would also help when scanning through a book to find something. Opinion? Worth suggesting?

[Grimlin]

Originally Posted by ValB626

Managed to find a different location at home where I was able to OTA DL 29:59 mins of a book (setting was for 30 mins) at 21 KB/sec. But it did work!

Have heard that some setting changes are recommended for VZW users. I hope to have a write-up from Audible to share soon.

[Grimlin]

Originally Posted by Ripley 29

It sounds like you are experiencing similar issues to the ones that I am having.. FF sometimes resetting back to the beginning of Section 1.

Also, the speed changes during listening. Are we the only two experiencing these issues, or are these also documented somehwhere? I get the speed changes constantly on my 8830, somtimes for minutes at a time.

Is there a pattern to either of these? I haven't experienced them. Have you sent them to Audible? If not, I would like to add them to my list and submit them next time.

[DallasFlier]

Originally Posted by Grimlin

I had a thought about the buffering. What if the first buffer was small 30sec of content? Would buffer in about 4sec. Then it increased to the 4min which it could buffer in the background during that 30sec of audio. This would also help when scanning through a book to find something. Opinion? Worth suggesting?

If the second part could be done in the background, then your 2-part buffer idea is great and definitely worth suggesting, I'd say - but you better tell them to buffer 45 seconds in the first part to make sure there's enough.

[ValB626]

Originally Posted by Grimlin

Is there a pattern to either of these? I haven't experienced them. Have you sent them to Audible? If not, I would like to add them to my list and submit them next time.

No discernible pattern to the resetting to the beginning of the book. The only pattern I've identified with garbling/skreetching is related to extended periods of listening. I mentioned both problems briefly in an email to audible, but included additional information in my previous post on these, so I don't think there's a problem in forwarding the more detailed info.

I tried to OTA DL the next 60-minute portion of the book for which I'd been able to download the first 30-minute section, from the same part of the house where I had enough signal to DL the first section. It took awhile at 17 kb/sec, then claimed the DL was successful. However, when I tried to play the additional sections, they didn't show up in the player (showed only Section 1 of 1). I eventually tried another DL, but got the message that this book was already on the device and it wouldn't initiate another DL.

I'm not finding the downloaded files for the book in MM or explorer listed by the name of the book (which is how they are listed when I side-transfer a book part). I did find 2 files with the same file names, one with a "2" appended to the file extension (aatmp), on the media card in the media card/music/audible folder (the device/music/audible folder appears to be empty). The size of the files and times (date/time modified) were about when I'd done the downloads. I deleted the smaller, earlier one of these, to see if the player would pull up the second file presumably with the later sections in it. No luck. Got the error message that the file is no longer on the device. Tried an "update list" in the books menu and the book showed up as not being on the device. So, although the second, longer DL appears to have worked, the player somehow didn't recognize/associate the later file with the first 30-minute DL. I also tried a battery pull with no different result.

On another note, I added a bunch of music to my media card last evening. When I opened audible later on, the start-up was extremely long. Instead of hovering at the 3/4-7/8 position on the progress bar, however, the long hover occurred at about the 9/10 position. I'm thinking the app read through all the new files on the media card?