Bit of a long explanation, but I thought I’d ask if anyone else has had this issue and has found a workable solution.
My TomTom rider 550 recently gave up the ghost and so I mounted an SP connect (square type) wireless adaptor on an anti-vibration mount, running TomTom Go navigation software on a Samsung S22 Ultra.
Originally, I had this plugged into a DIN-USB adaptor and the TT nav software worked fine, but the wireless charging was not keeping pace with the power consumption and the phone battery slowly discharged.
Enabling power saving mode and turning off adaptive brightness stabilised things and gave a very slow charge, about 1% per hour, but the screen was now very hard to read in bright conditions
Additionally, plugging anything ese into the spare USB port on the adaptor sent the wireless charge into freefall, and the phone discharged rapidly in use.
OK I though, let’s forget the adaptor, which in any case needs to be free to power gizmos in my tank bag and provide a dedicated power source to the wireless charger.
Now the can-bus system won’t power a wireless charger directly from the cockpit auxiliary connector, so I hooked up the Nippy Norman can-bus adaptor and fed the wireless charger from there.
With this arrangement, the DIN-USB adaptor works fine charging gizmos, but the wireless charger / Samsung phone has the same issues with running the nav and charging.
I’m beginning to think that high end smartphones and wireless chargers might be quite hit and miss, so’s not to be a reliable option, and I’ve not yet tried deleting the wireless element, but wondered if anyone else had come across these issues with a Samsung or similar smartphone.
Possibly back to a dedicated sat-nav?
All info gratefully received.
My TomTom rider 550 recently gave up the ghost and so I mounted an SP connect (square type) wireless adaptor on an anti-vibration mount, running TomTom Go navigation software on a Samsung S22 Ultra.
Originally, I had this plugged into a DIN-USB adaptor and the TT nav software worked fine, but the wireless charging was not keeping pace with the power consumption and the phone battery slowly discharged.
Enabling power saving mode and turning off adaptive brightness stabilised things and gave a very slow charge, about 1% per hour, but the screen was now very hard to read in bright conditions
Additionally, plugging anything ese into the spare USB port on the adaptor sent the wireless charge into freefall, and the phone discharged rapidly in use.
OK I though, let’s forget the adaptor, which in any case needs to be free to power gizmos in my tank bag and provide a dedicated power source to the wireless charger.
Now the can-bus system won’t power a wireless charger directly from the cockpit auxiliary connector, so I hooked up the Nippy Norman can-bus adaptor and fed the wireless charger from there.
With this arrangement, the DIN-USB adaptor works fine charging gizmos, but the wireless charger / Samsung phone has the same issues with running the nav and charging.
I’m beginning to think that high end smartphones and wireless chargers might be quite hit and miss, so’s not to be a reliable option, and I’ve not yet tried deleting the wireless element, but wondered if anyone else had come across these issues with a Samsung or similar smartphone.
Possibly back to a dedicated sat-nav?
All info gratefully received.