#jbring34
1 messages · Page 1 of 1 (latest)
Hi 👋 I haven't personally heard of this. Are there any errors that are being encountered?
I do not believe there are any errors being reported.
They are trying to update to version 2.01.00.17-SZZZ_Prod_US_v5-480001
Hm, the only mention I'm finding so far of behavior similar to this was on iOS devices.
I am trying to get a video to show
It seems like now the reader won't even start the update
This is the code we use to get to the update screen
I'm not sure if it applies to all readers, but I believe at least some of them require their battery have a certain amount of charge before they will attempt an update.
What is the battery level on the reader?
The battery was 33%
Is it possible that the updated started and then stopped once the battery got below 50%?
I think that is a possibility, but I'm not sure whether that is expected behavior. I do see that the readers seem to require at least a 50% charge to begin the update process.
I am having the user charge their reader and then try again and video when they do so if it happens again we can see it. IT just seems weird to me that we've had multiple people say the update stops at 66.3%
Agreed, that feels like too much of a coincidence.
Do you know if there is anway to downgrade my reader? Mine has been updated for a while so I can't test with the actual update
I don't believe there is