Thanks for the speedy reply, Danny;
If you're pretty sure this one will be bombproof, I'd be glad to have one to play with again - I miss the little beast
On reflection, I reckon I must have used the HTC tablet to attempt both upgrades: Both times it failed at 30% & that seems unlikely (to me, anyway) to be coincidence. The reason I used the tablet is that Mercury would not upload any trip records to the Samsung Note: Although much of the trip data was missing & Graph view was not working properly, at least Mercury & Tablet were communicating!
I will be sure to use the Samsung Galaxy Note this time.
ok that information help a lot, let me summarize your 2 android device problems :
1. Samsung Note - like most of the samsung ROM issues we have encountered these days, it misuse google library that cause bluetooth initialize and reset problems, can you confirm your samsung note can connect mercury and live view data without any connection or lost bluetooth issues ?
if you have experienced samsung note connection issues, i think we have solved it on 1.0.6 mercury android client (i did it on my samsung ace with 4.1.2 custom rom already)
2. htc tablet - it has serious bluetooth packet lost or drop, it can explained why "Although much of the trip data was missing & Graph view was not working properly" and firmware upgrade failed. with such bluetooth package lost may cause package resent and arrive to mercury in wrong sequence even we have packet exchange with crc checked …
we have solution to tackle this package lost but need to have firmware upgrade, however using firmware to patch the firmware is not a proper solution with packet lost android device (user may have only one android device for firmware upgrade), in the mean time the mercury client 1.0.6 can prevent this kind of android device from perform firmware upgrade e.g. when you use your htc tablet to firmware upgrade, after some checking, it will prompt firmware upgrade failed before re-flash entire firmware.
now i have an idea !
i will send you 3 x speedict devices, 1 x speedict mercury and 2 x other speedicts (we use it for another project, but it support up to 45v only as venus) name it mercury lite, so …
1. we will upgrade all 3 speedicts with latest 1.0.3
2. upgrade your both htc and samsung with client 1.0.6
3. put your speedict mercury aside, just use 2 x speedict mercury lite for testing
4. with 1.0.6 client on samsung note, you can take one of the speedict mercury lite for live view, software activate test first and then try re-flash with firmware 1.0.3 AGAIN.
5. without any problem you can proceed next
6. use the mercury lite you just re-flashed above and htc tablet with 1.0.6 client installed, try to re-flash firmware 1.0.3 again, you may have firmware upgrade failed message because of bluetooth lost packet during firmware upgrade …
7. let me know the result
if we are luck, you can keep have the speedict mercury lite together with your speedict mercury !