Power share with Huawei Gt2 Pro

[Bruno_s24u]

Hello all,

I have recently purchased a S24 Ultra phone. It is my first Samsung phone and was hoping to be able to use its wireless power share feature to charge my Huawei GT2 Pro watch. So far my attempts have been unsuccessful. The watch is showing as charging but then it gets disconnected after anything between 10 seconds and 1 minute of charging. The placement on the back of the phone is also very fiddly. I'm not using a phone cover when testing and the watch charges without issues with my old P30 Pro and a Pixel 7 I had tested it with. When I chose the S24 ultra the wireless power share was one of the features that was important to me. Unfortunately I cannot return the phone as I had it for over 14 days. When I received it, I tried charging the watch but very briefly (within the 10 seconds that it takes usually to disconnect) so didn't notice this issue. The watch is wireless QI charge compatible and the same is stated about the S24 ultra's power share.

Anyone else has this issue and is there a possible solution to it? Could it be a phone setting or additional software causing it? 

[BandOfBrothers]

Hi @Bruno_s24u 

The placement of the accessories to charge this way has to be pretty exact and can be a case of moving the accessory around until it hits the spot just right. 

From https://www.samsung.com/uk/support/mobile-devices/how-to-use-wireless-powershare/  

"  Not all devices with wireless charging capability are compatible with Wireless PowerShare. "

[TechZilla]

Also remember if your phone is not fully flat the watch will move as well as if your phone vibrates etc.

[Bruno_s24u]

Thank you for the suggestions and the link.

I've been trying to position the watch all over the center back of the phone with almost the same results. There are a couple of positions where it stays connected for a bit longer (up to a minute) but my P30 Pro isn't that picky - once I place the watch in a position that starts charging it doesn't disconnect. The watch does display a message when is not in a good contact position on either phone but on the Samsung it gets disconnected as above even after it starts charging. If I keep doing it the watch gets some charge (1%-2%) if I keep at it for about 10-15 minutes but obviously I don't want to keep turning on the power share and place the watch again and again as the power share turns off automatically when the connection is lost.

I am trying it on a flat surface and there is only the vibration when the watch gets connected so don't think that's an issue as the charging starts on the watch after that vibration. I even tried placing the phone on top of the watch as that way I can access easier the power share toggle.

Would have thought that the QI standard means that any 2 devices that adhere to it are compatible, hence why I posted here to see if I'm doing something wrong or if there are some settings or additional apps that would resolve this.

[Bruno_s24u]

Have just had the opportunity to test this with someone's S22 Ultra and it worked flawlessly - didn't even have to find the "sweet spot", just placed the watch in the center of the phone and it started charging. Left it for 5 minutes and no issues. Don't know anyone with a S24 Ultra to test it which would prove, if it works, that there might be an issue with my phone - might walk into a phone shop and see if I can test it with one of their display handsets.

[Bruno_s24u]

Just in case someone else is facing a similar issue, I have managed to track it down to the Good Guardians app. Once I uninstalled it, my watch is happily charging (even with a spigen phone case on) and I don't have to make minute adjustments to its position either - just place it somewhere in the middle of the phone and it starts charging.

Was about to reset the phone and try charging the watch before contacting Samsung support but then I thought to try uninstalling some apps before that. The Good Guardians was the second I uninstalled and is not enough to uninstall just its modules, I had to uninstall the app completely. To test it, I have reinstalled it without any modules and sure enough the issue was back.

Good Guardians are not so good after all, at least for me.