[bookport] Re: Interesting Behavior During Update
- From: "Grant Hardy" <grant_r_hardy@xxxxxxxx>
- To: <bookport@xxxxxxxxxxxxx>
- Date: Sat, 5 Mar 2005 16:16:28 -0800
I agree with you, that process of checking the battery level just isn't
happening soon eough.
----- Original Message -----
From: "ptorpey" <ptorpey@xxxxxxxxxxxxxxxx>
To: <bookport@xxxxxxxxxxxxx>
Sent: Saturday, March 05, 2005 2:27 PM
Subject: [bookport] Interesting Behavior During Update
> Here is what I experienced during the latest update to the BP Transfer
> and BP firmware updates which I performed on Friday, March 4.
> Fortunately, everything worked out okay, but I know APH has been
> experiencing trouble with some of the newest betas and thought this
> might help shed light on some of the problems people have been
> encountering.
> 1. When I plugged my BP into the USB port, Windows reported that a
> new beta firmware was available.
> 2. I accepted the update in the usual manner and unplugged the
> Bookport when prompted to do so.
> 3. I didn't have earphones plugged into the BP, so didn't hear any
> status info.
> 4. After waiting for a minute or two, I plugged in the BP again and
> downloaded a new book onto the BP.
> 5. I did not use the BP again until today.
> 6. Today, when I started to use the BP, I noticed that, as is usual
> after a firmware update, all of my personalized settings (voice speed,
> pitch, sensitivity, etc.), were blown away. So, I got into the settings
> menu and started to select my usual settings.
> 7. The first few settings (for volume, pitch, sensitivity, sleep
> timer, etc.) went well.
> 8. The problem occurred when I got to the Date and Time Settings.
> The first indication that something was wrong was when the BP spoke
> gibberish like (bre", "thday", and sometimes nothing as I tried to cycle
> through the months with the 4 and 6 keys. A similar thing happened when
> I tried to set the day using the 4 and 6 keys - just gibberish, and
> sometimes nothing. Date and Year seemed to work okay.
> 9. Then I hit the 5 key to have the BP accept the new date and time
> settings. At this point, the BP stopped talking/functioning altogether.
> 10. To recover funtionality, I took out the batteries and put them
> in again. At this point, the BP said something like "batteries low,
> update aborted".
> 11. I checked the battery level - it was between 40 and 50 percent.
> I also tried to re-set my settings again, but the same gibberish
> happened. I should point out, that this brave soul is using alkaline
> rechargeable batteries (and always have!).
> 12. So, I put in a fully charged set of rechargeable batteries
> (which report between 70 and 80 percent as usual). The BP told me to
> standby while it was performing the firmware update.
> 13. After the update with the fully charged batteries was complete,
> I was able to customize all of my settings as usual, and everything now
> works as it should - no problems.
> 14. Summary - I know that the software is now checking the battery
> level before performing firmware upgrades in order to ensure that the
> update process will not be aborted prematurely and thus crash the unit.
> However, it seems that this checking process is not working correctly.
> The reason I say this is that my unit and settings were working fine
> before I attempted the update with( what the update process must have
> considered to be batteries which were too low. Instead of not doing the
> update at all, at least part of the update process was done since a) my
> settings were all changed to their defaults, and b) some of the settings
> had gibberish and were obviously not working correctly. Thus, it seems
> like the update process was at least started, and then prematurely
> aborted. Maybe there is something about the timing of the check for low
> batteries and the actual initiation of the update process that needs to
> be ironed out yet.
>
> I hope this feedback is helpful.
>
> -- Pete
>
>
>
>
>
>
Other related posts:
