Hey All
First time post here, but long time browser and reader of the forums ..
I have managed to to get a Gear 2 and Gears s to work on my own LG G2 phone which is bog standard, nothing done to it so running Android 4.4.2
So I'm using a version of Samsung Gear that will run on a non Samsung device, works well, a few things of course don't work but that is to be expected.
If a Developer could PM i can share the info with them so they can check it out, and maybe seed it from there.
You could always post up the info. here so we can take a look ! I am trying to get my Gear S working on a non-rooted Z3 at the moment and failing dismally, so I can look at what you have
Hello all,
I've been reading around this forum and found several guides for installing Cyanogen, but they seem to be made for you to install it on a previous installation, which is not my case, and I also have several questions.
First of all I have Samsung Galaxy SII (GT i9100)... i bouht it on Amazon, so I guess it's american. It still has the software it came from, I have never changed it. I've had several issues with this phone since it was new, like out of the blue I turn it on and it gets on a forever loop with the samsung logo. So everytime this hapens I have to wipe data and factory reset from the android system recovery.
Also about a year ago I got what I believe was a virus it took me a while to get rid of, but although I supposedly did, I feel like some issues are still around.
My question basically, what's the newest android version I could install in my phone? and how could I do it? what's a good guide for it or something?
Thank you so much for your help.
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
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!