How to get work the Gear S3 on unsupported android devices with Gear App ->SOLVED!
I've thougt of this thread as a guide collection for anyone who has problems with the setup of his android phone by using a Gear S3
I had even pre-ordered the Gear S3, but it did not work with my Huawei MediPad / Honor X2, so I've already sent it back.
Also the Gear App is not shown in the Playstore, but I managed this by installing the .apk
(I think this is caused by the incorrect assignment as a tablet, but it's actually only a very large phone)
Bluetooth of the watch is recognized, however the Gear App crashes, when the watch will setup
But I can't accept this.
I would buy it a second time, if there is a way to make the Gear App work on the X2
(and other, not supported android devices, like the HTC 10)
So the behavior is identical to that described here:
http://forum.xda-developers.com/gear-s3/help/setup-gear-s3-frontier-htc-10-t3505529
or here
http://forum.xda-developers.com/showpost.php?p=69944929&postcount=54
or here
http://forum.xda-developers.com/showpost.php?p=69691127&postcount=25
SOLUTIONS
by @j to the 4n thankyou for this!
https://forum.xda-developers.com/showpost.php?p=70782233&postcount=41
https://forum.xda-developers.com/an...d-samsung-gear-app-android-n-samsung-t3547035
https://forum.xda-developers.com/showpost.php?p=70860684&postcount=36
https://forum.xda-developers.com/showpost.php?p=70681504&postcount=34
kajos said:
I've thougt of this thread as a guide collection for anyone who has problems with the setup of his android phone by using a Gear S3
I had even pre-ordered the Gear S3, but it did not work with my Huawei MediPad / Honor X2, so I've already sent it back.
Also the Gear App is not shown in the Playstore, but I managed this by installing the .apk
(I think, this caused by the wrong allocation as a tablet, it's actually only a very large phone)
Bluetooth of the watch is recognized, however the Gear App crashes, when the watch will setup
But I can't accept this.
I would buy it a second time, if there is a way to make the Gear App work on the X2 (and other, not supported android devices, like the HTC 10)
So the behavior is identical to that described here:
http://forum.xda-developers.com/gear-s3/help/setup-gear-s3-frontier-htc-10-t3505529
or here
http://forum.xda-developers.com/showpost.php?p=69944929&postcount=54
or here
http://forum.xda-developers.com/showpost.php?p=69691127&postcount=25
I now have a small idea, but I cant test it without the watch
In this video is shown, how to setup (Gear S2 ->S3 would be the same...):
?t=527
When Gear App crashed for me, here will be shown, that the app stops, while opening the Playstore for the Gear Plugin App
My suggestion, I havend tried:
I've installed the Gear Plugin App, before I setup the watch, along with the Gear App, but this was perhaps a mistake in this context.
Maybe setup will work, when Gear Plugin App is not already on the phone, when starting setup...
An other idea is to manipulate the build.prop, but I don't know the conditions of the Gear App ...
Has someone already found a solution and can be described here?
Click to expand...
Click to collapse
I have Gear S3
It was having exactly the same issue as you described of gear app force closes, I tried all different sequences whatever you thinking of as you mentioned.
My m8 custom rom is heavily tweaked to give most of HTC 10, so here is the similarity with HTC 10 people
So I restored my original unrooted backup and waooo it connect to gear S3, I'm enjoying now but no root no custom roms, may be will try another rom later.
It would be interesting, what kind of differences the build.prop shows between the m8 custom and the original.
Maybe, the key is buried there...
I read now, that a rooted phone prevented to connect the watch, especially also at the HTC10
Can someone confirm this?
And if so, how could you handle this?
Because of Samsung Pay I guess, it's not unlikely that root is undesirable
Yes, can confirm. HTC10 Viper 10.3
App crashes, when the watch will setup. Tried any installation sequences, but wasn't able to setup the Gear S3.
NOVodkA said:
Yes, can confirm. HTC10 Viper 10.3
App crashes, when the watch will setup. Tried any installation sequences, but wasn't able to setup the Gear S3.
Click to expand...
Click to collapse
I also had issues getting the Samsung Gear app installed on my HTC10 running Viper 3.5 (Android 6.0.1). I thought it was just because of Root, but I installed the Samsung Gear app on my Stock Rooted M8 and it worked perfect. So I then installed a stock port of rooted Android 7.0 and the Gear app installed fine. So it seems something in the custom ROM caused the app to not install.
For comparison I have a Verizon HTC 10, with a Dev Port of 7.0 rooted and the Samsung Gear app installed. I also have S Health and Samsung Pay working perfectly.
Ahowe125 said:
I also had issues getting the Samsung Gear app installed on my HTC10 running Viper 3.5 (Android 6.0.1). I thought it was just because of Root, but I installed the Samsung Gear app on my Stock Rooted M8 and it worked perfect. So I then installed a stock port of rooted Android 7.0 and the Gear app installed fine. So it seems something in the custom ROM caused the app to not install.
For comparison I have a Verizon HTC 10, with a Dev Port of 7.0 rooted and the Samsung Gear app installed. I also have S Health and Samsung Pay working perfectly.
Click to expand...
Click to collapse
Hi everyone, I can confirm that, It has nothing to do with root.
The connection of the Gear s3 works fine with the htc 10 and htc Stock installation.
Tested with Marshmallo and Nougat.
Maybe there are models and brands where the connection with the Gear s3 does not work even under stock installation, but that is different story.
There is something missing in custom roms.
I have now given up my favorite custom ROM, so I can use my watch with the phone.
Hopefully someone finds the solution, so it also works with custom roms.
I have logcats from both connection attempts, Custom rom and stock.
But I'm not an expert to read the logcat and find the Problem.
If someone has interest I can upload it .
There are obvious misunderstandings here!
I'm by no means concerned with identifying root as the main cause!
My only concern is to find the reason, or the concret causes for incompatibilitis or misbehavior of the gear app.
So my MediaPadX2 phone is completely stock, and it's only rooted, but Gear App crashes like described.
I would like to get the reason for this and find a solution.
If the issue is not caused by root, so all better (for me first)
Now we can summerize:
it is not necessarily to root, and does not occur only with some custom roms
So we are unfortunately not a step further.
But I'm still guessing that an unsatisfied query condition of the build.prop is the cause...
Toni10 said:
I have logcats from both connection attempts, Custom rom and stock.
But I'm not an expert to read the logcat and find the Problem.
If someone has interest I can upload it .
Click to expand...
Click to collapse
Unfortunately, I am also no expert
Hi guys,
I am new in this forum and hello to everyone
I have a xiaomi MI5 with the new rom nougat 6.12.15 from xiaomi.eu, it is impossible to connect a samsung gear S3 to a MI5 ?? when i open the gear app on the phone, it crashes and FC
Do you have a solution to make it work with the phone ??
Thank you
And merry christmas to all !!!
You had the Mi5 and the watch connected before the rom update?
Or did you buy the MI5 with nougat 6.12.15 so that it is all stock
You've problems with the pairing, too?
Maybe you have the possibility to compare with a working version on the same phone?
Please look, if there are differences of those parameters in the build.prop
http://ausdroid.net/howto/use-samsung-gear-fit-rooted-android-device/
I guess, that there would be a key to solve the pairing problems
https://forum.xda-developers.com/ht...tweaks-hub-t3379151/post69825479#post69825479
another log for anyone reading logs
Does someone get solution? I'm using HTC10 Android 7.0 Rooted (Viper 4.4 rom), the Samsung Gear app is forced close when pairing to S3.
According to this post by Leedroid, the Problem is the deodexed System.
Since he is a very experienced developer, I am sure he is right.
https://forum.xda-developers.com/showpost.php?p=70259624&postcount=646
From the first day I operated my phone with the Leedroid ROM and was very happy with it.
Now I reverted back to Stock ROM, to use the watch with the phone.
I don't think there is any other solution at the moment.
i don't think so!
My X2 has a odex stock rom 5.0, also some other stock shows the same issue
I guess that this idea a dead end, like some say the issue is caused by 7.. nougat...
kajos said:
i don't think so!
My X2 has a odex stock rom 5.0, also some other stock shows the same issue
I guess that this idea a dead end, like some say that has to be 7.. nougat...
Click to expand...
Click to collapse
Not entirely true.. I have the watch working on a Dev port of Android N for my HTC 10. Like others have stated, it would not work on a custom ROM like Viper. And that was when it was still on MM.
Sent from my HTC6545LVW using Tapatalk
And what does that prove?
kajos said:
And what does that prove?
Click to expand...
Click to collapse
In my situation I think it proves a few things. First, it doesn't seem like Root is an issue (as discussed earlier). Second, (in my situation) that something in a custom ROM causes issues. Either something with the build.prop as you have suggested, or something with the odex as others have said, but I have another theory.
What if it all boils down to which phones Samsung has deemed "compatible"? My HTC 10 is listed as compatible on the Samsung website, but maybe the identity of the phone is modified with the custom ROM?
I used this link related to the S2 to determine compatibility.
http://www.samsung.com/global/galaxy/gear-s2/device-compatibility/
I'm not a Dev, only a user who has basic understanding of how these things work, and can only report my situations in order to help others troubleshoot and hopefully find a way to enjoy this amazing watch.
Sent from my HTC6545LVW using Tapatalk
Every few weeks when I go to pay with my watch I hold the back button entered my pin, and then am greeted with the wonderful message that all of my card info has been deleted. I never had this problem when I had a Note 8 or an LG V30 or an S9 but with my LG G7, I do have this problem. I notice that in the Samsung Gear app, I don't have Samsung Pay in the list but when my card is deleted on my watch and I have to set it up again and it tells me to check my phone, it launches it just fine to add my card but just doesn't show it in the Gear list. I have seen that others have had issues with their cards being randomly deleted and having to be set back up again. It is a good thing I know my bank card number by memory and doesn't take long to set back up but it is a bit annoying. I'm worried US Bank may start to think someone is messing with my card.
Anyone else had any issues with Samsung Pay deleting their cards? This was one of the biggest reasons I got this watch.
Happening every few weeks. I read that hard resetting the watch helps. We should contact Samsung about this, they don't read this forum.
klau1 said:
Happening every few weeks. I read that hard resetting the watch helps. We should contact Samsung about this, they don't read this forum.
Click to expand...
Click to collapse
Been there, done that. No luck. I think part of the issue has to do with Samsung Pay not showing in my Gear app like it did with my previous phones. I did download the most recent apk and keep it on my SD card in case I need it, but when my card gets deleted from my watch and it makes me set up Samsung Pay again, it opens fine on my phone just don't know why it doesn't show up in the list.
Another possible reason could be when people do clean up of memory for the watch from the Gear app it could be deleting the cards since Samsung Pay isn't listed in the Gear app. Maybe not but it could be possible.
Its a known bug which samsung knows as well but they hardly do anything to fix it...its more frequent on non samsung phones...only hope is near gear watch launching with a better samsung pay app and we, the gear s3 owners also getting the update...
My Gear app updated today and now Samsung Pay is showing in the list on the Gear app now so maybe that will help. It was showing before on my current phone which is an LG G7 ThinQ but when I had the LG V30, it did show in the list on the Gear app. Perhaps Samsung updated compatibility with more phones even if they already worked with it despite the previously mentioned issue.
My credit cards have been deleted twice since I updated to the latest Gear App a couple days ago so that didn't fix the problem for me at least. I already called their support and they said it is a known issue with non-Samsung phones although I've read on multiple posts that Samsung phones have the same issue. They had me delete the cache on the Gear app, but that didn't help.
Gear S3 Frontier and Pixel 2 XL
Strange its happening now after over a year of perfection just a few weeks before Gear 4 releases
The CRG3 update seems to have fixed the problem at least for the past couple weeks, although my cards got deleted after I upgraded to Android Pie.
I spoke too soon. I received the CRH1 update a few days ago and all my credit cards were deleted once again today. I contacted Samsung Pay support and they acknowledged there is a known issue with Pixel 2 phones, but also blamed it in the Android Pie update. I had to remind him that this issue has been going on months before Pie was released and it's not exclusive to non-Samsung phones. My friend has a Samsung Note 8 and has the same recurring problem. He just asked me to be patient while they work on a fix. At least he didn't try to waste my time re-installing software or doing a factory reset
I havent seen too many threads about the Gear S2s randomly stopping working and not being able to take updates on here, but the forums on Samsungs site is awash with them, so i figured id throw this out there for those who might stumble upon it.
For the last few months my sons Gear S2 hasnt been able to pair with any phone properly. It would initially connect, then say that a firmware updates was required in order to continue using the device and wouldnt let you just continue with the current firmware. I tried pairing it with my U1 S9, my fiancees 100% stock Cricket S9, my old A8, 2 old S5's, S7 and S7 edge both, S4 and finally a S3. All of them failed to update the firmware and there was a bevvy of Android OS versions that i tried, so that was effectively ruled out. No amount of facory resetting via the OS itself nor recovery changed it. I then went to the Samsung forums as a last hope and there were "certified Samsung tech"s replying stating that they were working on it.
Fast forward to yesterday (i have been dealing wit this since before Christmas) and th ekiddo asked if there was any progress. It had been about a week since i tried it, so i tried it with my U1 S9 again and to my UTTER SHOCK AND DELIGHT, it actually took the update this time! It installed, rebooted twice (as per normal) and paired 100% with my phone! I unpaired it and had the kiddo pair it to the A8. That worked too!
Moral of the story, if you have a Gear S2 sitting in a drawer that suffered teh same fate, try the update again. Its worth a shot!
Ok Guys, This goes out to all us S3 Frontier (R760) users who have found that their Sensors no longer function after updating to the latest Tizen I found it annoying that Samsung would release a OTA not knowing it would cause Us too lose functionality of our watch, and despite numerous reports from Users across the world nothing has been done....Apart from of courser Samsung releasing OTAs that didn't fix S**T.
Despite losing that functionality I kept using my watch in the hope that Samsung would came too their Sensors and do something about it but NO!!!! just more OTAs so I decided that I would Roll back my device and roll back I did. Not to last years FUD1 Tizen 4.0.0.7 nor the year before that (2020) with the FTD4 firmware another Tizen 4.0.0.7 O.S but all the way back to Tizen 3.0.0.1 CQL1.
Now before rolling back to Tizen 3.0 I first tired with Tizen 4.0.0.2 DSA1 and there was a spark of hope when the HR sensor came to life but nothing else (Sensor) wise and it was short lived, with the HR sensor soon stopping shortly after. I did perform a Factory reset to see if that would correct it but unfortunately not and is probably where the issues started with Samsung releasing subsequent OTAs making things worse.
So with the Tizen 3.0.0.1 firmware on hand, I flashed it using Netodin and with the Watch passing the Flashing process all I could do was wait for it too Boot. Sure enough once reconnected to my phone and setup I went through and Tested the Sensors and found that ALL were working as they should including the Wake up gestures.....YAY!!!!!
So you too if you want can regain what you lost by flashing this firmware *******AT YOUR RISK ******* I DO NOT TAKE RESPONSIBILTY IF YOU BRISK YOUR DEVICE *********
I have provided the required File below, Extract and you'll be greeted with 4 files BL, AP, CSC and a Pit File. Place these files into their corresponding positions within Netodin including the Pit File ******** There will be a Warning Message pop up when adding the Pit File just press OK and it ( I DID ) then press Start and wait for the Watch to reboot. DONE!!!
******** This could also work for other S3 Frontier watches as long as you have the appropriate Firmware for your device. ****************
********* If your unfamiliar in using Netodin, I suggest YOUTUBE.****** If you find your having Connection issues Check the watches Wifi properties in your PC and change it from Public to Private that should do the trick.
SAME issue I am on R760XXU2FVG1
Sensors not working.
First will flash the 4.0.0.2 DSA1 one that's given in the forum. If that doesn't work will flash the CQL1. Will update soon
So out of curiosity I decided to update the firmware mainly because Galaxy Wearable informed me of the update. Little did I know
hemanthDroids said:
SAME issue I am on R760XXU2FVG1
Sensors not working.
First will flash the 4.0.0.2 DSA1 one that's given in the forum. If that doesn't work will flash the CQL1. Will update soon
Click to expand...
Click to collapse
Yeah keep us updated, would be interesting to see how everything turns out for you.
Installed Tizen 4.0.0.2 DSA1 didn't work. @jays note 2
Installed Tizen 3 given above by you along with Pit. Still it says fail. None of the sensors are working HRM, Gyro, accelerometer.
Software version, Tizen version matches with your screenshots.
But the attached screenshot only MCU Version differs with what you have posted.
I made sure my phone is disconnected from WiFi so that it wouldn't download any updates..
Am I missing something?
[Edit] Done using 2.3.2 firmware version also. No use. Still same issue with sensorhub
Hmmm that's interesting I would have thought rolling back to tizen 2.0 would have sparked at least 1 or more of the sensors too work.
Have you tried factory resetting after each flash, through recovery? I know sometimes things get a bit messed up after flashing. Worth a try, if not there maybe a chance your MB might be stuffed
Yes I hard reset before every flash. I even tried the combination firmware posted on other thread. Still nothing. I think it might be a hardware issue. For now I'll consider this as a fancy watch without any fitness features
PS: Thank you for this post. I think it helps many people who faced similar issues. Take care
One thing I could make out of this fiasco is that Samsung isn't as premium as a brand.
Their smartphones batteries swell after few years. This watch software is made so haphazardly. Build quality is bad - My watch strap feels very bad on skin.
They launch ton of products but doesn't give enough attention to each of them.
There is no longevity to their products. I like to keep things for long like 5+ years.
This is why I feel like moving to apple ecosystem.