Database Info

[Q] Gear 2 Neo and Samsung Galaxy S3 Trouble

I just bought a Gear 2 Neo and when Pairing it with my S3 the watch stays on the startup screen all the while my S3 shows they are paired. The phone never connects to download the software from the watch, i did however get it to work with my Galaxy Tab 3 but not with my S3. Does anyone know a way to get this to work.
P.S. I did a factory restart and tried it with no additional software on the phone except for the Gear Manager from Samsung. I thought there might be something conflicting. The S3 is running android 4.4.2.

if you are running a custom rom then put your phone back to stock and it'll work properly. someone here was having issues with their phone & the gear 2 and it was all because they were running the latest Jedi rom.

rlee008 said:
if you are running a custom rom then put your phone back to stock and it'll work properly. someone here was having issues with their phone & the gear 2 and it was all because they were running the latest Jedi rom.
Click to expand...
Click to collapse
I am currently running stock and have not rooted my phone. I did factory rest it and tried to install the gear manager but it wont run correctly on my S3. the interface just keeps flashing white and wont pair properly. All this time the phone is still on the startup screen.

Help getting the Gear Manager/Gear 2 running on AOSP Lollipop

Hey all, As I'm sure other people are I am trying to get my Samsung Gear 2 connected to my Galaxy S5 running the latest CM12 nightly. Unfortunately, Since Lollipop, as far as I'm aware nobody has been able to get the Gear Manager to function correctly on Non-Touchwiz roms.
I have tried just about every combination of installing, uninstalling and restoring from TW roms with Titanium backup that you could think of. Nothing will allow my device to function correctly. Upon pairing with the app, the most common crash is HostManager. The watch will pair but as soon as it does, You get repeated messages of 'Unfortunately, HostManager has stopped.' and the Gear manager app stays at 'Conneting to Gear'. The only way to stop the crash loop is to turn of Bluetooth or Freeze the HostManager app.
Surely there is some way to fix this? I haven't seen a lot of people looking in to it despite the fact that a number of people must want to run their Gear device with an AOSP-type rom?
Here is the logcat from the installation of the HostManager APK (I don't think this is useful, as it all installs correctly but added anyway just in case): pastebin<dot>com/eWp2AuHd
And here is the Logcat from the crash of HostManager: pastebin<dot>com/N0eWGZRL
Sorry about the links, The logcat is too long to fit in an XDA post and I'm below the post count required for posting links, and I don't want to meaninglessly post just in order to insert links.
As you can see I left a large buffer of the logcat around the crash in case there is any other important information about what is going on.
Any help here would be appreciated. If you can fix it and have a PayPal I'll buy you a beer or two

So sad...
I just installed Resurrection Remix 5.1 on my S5. It looks really better than the Samsung Lollipop (and works better)... but no way to link my Gear 2...
Did you find something helpful ?

Albadros said:
So sad...
I just installed Resurrection Remix 5.1 on my S5. It looks really better than the Samsung Lollipop (and works better)... but no way to link my Gear 2...
Did you find something helpful ?
Click to expand...
Click to collapse
Unfortunately I was unable to get it to work. I went and bought a Gear Live insead.

Did this with unrooted HTC m9 and unrooted Gear 2 with latest FW.
Deleted all the files installed on phone from gear manager.
Download latest GM files (extract/ed from APK)
Install every apk except Host Manager and install Gear Manager App as last
Open GM and connect your Gear 2. As soon as it tries to install Host Manager hit home button/go to your file explorer App on your Phone and install Host Manager 2.2.14100299
Open GM again and cancel Host Manager installation.
Have a little patience and it should show you the option to accept the terms.
Set Notifications in GM App on your phone.
If you prefer Root for Gear then you can root your Gear without problems and you don't have to do this all over again.
Sideloading APK's working fine, had S Voice running but coulndn't connect to watch yet.
Changed Bootscreen, sounds and more without problem.

Redmen What OS are you running? 5.0.2? or 5.0.1?

daroota said:
Redmen What OS are you running? 5.0.2? or 5.0.1?
Click to expand...
Click to collapse
5.0.2 with software: 1.32.401.15

Mmmm, I'm running 5.0.2 CM12S on my OnePlus One, and a friend and myself cannot get it to connect in Gear Manager and activate on the watch itself. My thought was since none of the Samsung Galaxies have 5.0.2 yet, Samsung hasn't build a apk for that version yet. I hope they will update it soon.

Wondering the same thing, love my nexus but rendered my gear 2 pretty much worthless. Any advancements towards this?
Sent from my Nexus 6

There is one way I know how, but it's a royal pain in the butt.
Do a nandroid restore to 4.4.4, install the old gear software like it once was installed. then update to Lollipop like normal, and install the latest gear manager. The problem is that the watch has to BE paired already to your phone, and without wiping (so you don't loose your bluetooth unique ID) update to keep the pair.
In my case, I took a nandroid backup before I updated to lollipop, so I restored it, paired it, used titanium backup to copy my programs and data for the watch and the bluetooth ID, then restored back to lollipop because it was a OTA update which didn't change my settings... updated to the latest Gear manager, and restored my Bluetooth settings= Profit...
However 2 problems I am having, is my watch doesn't want to answer the phone, and Saproviders keeps crashing, so I removed saproviders... everything else works fine.

daroota said:
There is one way I know how, but it's a royal pain in the butt.
Do a nandroid restore to 4.4.4, install the old gear software like it once was installed. then update to Lollipop like normal, and install the latest gear manager. The problem is that the watch has to BE paired already to your phone, and without wiping (so you don't loose your bluetooth unique ID) update to keep the pair.
In my case, I took a nandroid backup before I updated to lollipop, so I restored it, paired it, used titanium backup to copy my programs and data for the watch and the bluetooth ID, then restored back to lollipop because it was a OTA update which didn't change my settings... updated to the latest Gear manager, and restored my Bluetooth settings= Profit...
However 2 problems I am having, is my watch doesn't want to answer the phone, and Saproviders keeps crashing, so I removed saproviders... everything else works fine.
Click to expand...
Click to collapse
This isn't a viable option for those of us that want to swap to an AOSP based ROM. I've tried this, and while it will pair with the phone OK, the gear manager software doesn't work, therefore you can't receive notifications on the watch. The only function that works when you do this is answering phone calls on the watch, as this can be done without Gear 2, as it uses A2DP (I think) so will work with any bluetooth phone for hands-free.
There is also no way to OTA update from a TW ROM to a custom ROM, unless you are referring to an OTA update from a 4.4.4 based AOSP like CM11 to 5.X/CM12?

Correct. I went from cm11 to cm12 on my one plus via OTA.
Sent from my A0001 using XDA Free mobile app

Gear S2 and CM ROMS

Anyone get the Gear S2 watch working in a custom rom like CM? CM13?

Still trying to get my gear s2 working on my galaxy s5 running CyanogenMod 12.1

Worked fine for me with oneplus one. Just make sure you light reset the watch any time you try a new rom
Sent from my A0001 using Tapatalk

Yea tried that. Normally thr gear app would pop up and try to pair with the gear s2 but its not doing that. Ive manually downloaded the three Samsung gear APKs on the other thread...believe it was the gear plugin, Samsung accessories, and Samsung gear app. The app is giving the error saying Samsung gear cannot install due to custom ROM.

Hi!
I tried to install the Samsung Gear App and get the same Error that the OS has been modified unauthorised... :-/
My Question is: Did someone try this App after insalling the stock ROM again?
I don't want to backup and reinstall all apps and data...
Thank you for your help!

I have been through this rodeo, and I have noted a couple things.
1) Unlocked Bootloader: Doesn't matter, I am currently running Phils Recovery on my TW Official OK4 ROM, Gear and android pay work fine.
2) CM12.1 or CM13, not rooted or removed root: Doesn't work. Root is not the only thing both apps are looking for.
3) TW Custom ROM: Doesn't work. Could not get it working on my MOAR 7 rom which is based on TW.
4) STOCK ROM with Phils Recovery: Works fine if I don't root.
So obviously the check goes beyond root, and probably some combination of Software Version / Build Number or some other reference point to detect the ROM.
The reports of hiding the root on a custom ROM to get Android Pay to work, simply don't work. My hunch is that whatever Android Pay is using, is the same mechanism as the Gear Manager app from Samsung.
In the end, frustrating, because TW stock is completely slow, and kills my battery, and does stupid things like turns on my screen anytime I put it on an inductive charging station, or won't allow me to turn the volume to max over BT because of communism... or socialism... or whatever.

[email protected] said:
I have been through this rodeo, and I have noted a couple things.
1) Unlocked Bootloader: Doesn't matter, I am currently running Phils Recovery on my TW Official OK4 ROM, Gear and android pay work fine.
2) CM12.1 or CM13, not rooted or removed root: Doesn't work. Root is not the only thing both apps are looking for.
3) TW Custom ROM: Doesn't work. Could not get it working on my MOAR 7 rom which is based on TW.
4) STOCK ROM with Phils Recovery: Works fine if I don't root.
So obviously the check goes beyond root, and probably some combination of Software Version / Build Number or some other reference point to detect the ROM.
The reports of hiding the root on a custom ROM to get Android Pay to work, simply don't work. My hunch is that whatever Android Pay is using, is the same mechanism as the Gear Manager app from Samsung.
In the end, frustrating, because TW stock is completely slow, and kills my battery, and does stupid things like turns on my screen anytime I put it on an inductive charging station, or won't allow me to turn the volume to max over BT because of communism... or socialism... or whatever.
Click to expand...
Click to collapse
Thank you "eatmeimadanish"!
So, if i install the stock rom (recovery stays the same) the app will start without a problem and the connection to the gear s2 is fine?
The only thing is that i'll have the standard samsung tw-rom again...

scorp1on1899 said:
Thank you "eatmeimadanish"!
So, if i install the stock rom (recovery stays the same) the app will start without a problem and the connection to the gear s2 is fine?
The only thing is that i'll have the standard samsung tw-rom again...
Click to expand...
Click to collapse
Yes. Unfortunately the TW rom does suck, and has a bunch of built in stuff you can't turn off. If you are used to (like me) with a ROM that makes any kind of sense in it's design, then it's a beotch to switch back (kiss the battery life goodbye). On a good front, the Gear S2 is pretty awesome....

Hey!
I got my Samsung Gear S2 today and i'm installing my apps again.
Gear Manager started without a problem and the connection to the Gear S2 was established in a second!
Of course i'll install another launcher!
Best regards,
scorp

Found the Answer... CM13 working with Gear S2
http://forum.xda-developers.com/gea...gear-manager-samsung-accessory-t3216240/page7
Found the answer with the help above. I just did this on my Ressurection ROM and the app now looks for the watch... Don't have my watch but it got past the error message so I will try it tonight and report back.

Lineage OS
Tested on Lineage OS for Samsung S7 Edge. It worked perfectly thank you

[email protected] said:
http://forum.xda-developers.com/gea...gear-manager-samsung-accessory-t3216240/page7
Found the answer with the help above. I just did this on my Ressurection ROM and the app now looks for the watch... Don't have my watch but it got past the error message so I will try it tonight and report back.
Click to expand...
Click to collapse
Tested on my galaxy s4 gt-i9500 whit lineage os 14.1 and works perfect

I have followed instruction and after editing i could not install gear and required apps from google play. I had to find apk outside and it worked. I`m using lineage 14.1 and n910v -Note 4 Verizon. Does anyone know why i could not download from google play ? Should i use some other brand in build.props or change something additionally?

Gear 2 - Tizen - Error

Hi there,
I need assistance with a Gear 2 I bought secondhand. When I boot it I get the following error. "An unknown error has occured. If he problem persists, visit a customer service center."
On Tizen it gives Me the same error no matter what variant I Flash on to it. I even tried Lollipop which runs quite smoothly but then there is no connection whatsoever and the Gear 2 then seems undetectable.
h*t*t*p*s://drive.google.com/file/d/0Bzfs714pAXNNZDJaQ0xZTnJnS00/view?usp=sharing
Would appreciate any help.
Thanks Guys.

There are instructions in the "Porting Android to Gear 2" Development Thread with a very specific Tizen ROM to flash for returning to Tizen. I am wondering if whoever you bought your watch from went to Android and then didn't go back to Tizen through the right channel. You might try flashing that ROM.

I did Re Flash Android and Re Flashed that specific ROM and 10 others and 2 different versions of Lollipop. The Tizen keeps showing the error no matter what U Variant U flash. Lollipop seems to work fine but no connection. I tried various different thread instructions etc to get it connected to no avail.

Android Wear_511_LCA43__09_24_2015
Flashed this onto the watch for the 100th Time with different Gear Manager. Also about the 100th Gear Manager I have tried. And all of a sudden it works.

Images
Hitman1983 said:
Flashed this onto the watch for the 100th Time with different Gear Manager. Also about the 100th Gear Manager I have tried. And all of a sudden it works.
Click to expand...
Click to collapse
Sadly I would have loved to get it working with the Tizen and not Android but the Error seems to be Unknown Globally.

I know it sounds weird, but have you tried a different USB cable? I find that Odin is really touchy when it comes to which USB cable you use.

Bump
You guys want to tell Me no one has ever ran across this problem with Tizen?
And whats up with the connectivity on the Android Port?

Hitman1983 said:
Android Wear_511_LCA43__09_24_2015
Flashed this onto the watch for the 100th Time with different Gear Manager. Also about the 100th Gear Manager I have tried. And all of a sudden it works.
Click to expand...
Click to collapse
Hi,
I am in exactly the same situation you were in. Bought a 2nd hand gear2 and I got the unknown error message.
What exactly should I do please?
Thanks

are you guys still having issues ? the only thing you can do really is try flashing original firmwares, if that doesnt work there must be a read/write problem with the onboard memory

Question Have to Reconnect watch everytime my phone restarts.

I'm using a Galaxy watch 4 Classic for a month now and it has been working perfectly fine. But the only issue I'm facing is unable to quickly reconnect after my phone restarts. I have to repeat the long first-time connection procedure (which has got quite frustrating TBH). I even have to do this when I turn on Flight Mode on my phone. I know it is not how it is supposed to act normally but I believe there must be some solution to this.
It seems to be something wrong with my Samsung Wearables app. It does not seem to remember any device after a restart.
Also to mention, my phone is rooted if that is causing this.

It is indeed your root that's causing this problem
Install the Bluetooth Library patcher via Magisk or TWRP (whichever you prefer) from here:
https://github.com/3arthur6/BluetoothLibraryPatcher/releases/tag/v2.4.1
And this problem should go away. Reboot and re-pair your device. Should remember them afterwards.

I tried to install the Bluetooth patch file but, the root manager I have installed "EFTSU Manager", does not open any of the Bluetooth patch files I downloaded. I installed Magsik but it does not seem to work on this device. Also my device boots normally. No TWRP from where I can install packages.
Please guide me on how I should make this work... If any additional details are required, ask ill provide them.

If not Top Secret...
Why not tell Model Name of your Phone...
Samsung not Samsung?
For instance I fixed this ugly issue on my Samsung SM-A202F rooted with Magisk...
Best Regards

Here my "Diary"...
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
IMHO only fixed after FukKkKtory Reset Watch again.
Best Regards

Skipping f%$ing useless Intro by tap tap few times on Screen.
This is since Tizen totally stupid feature because in earlier Tizen firmware Intro asked for skip...
Seems Samsung loves to torture user by stupid tasks.
Best Regards

adfree said:
If not Top Secret...
Why not tell Model Name of your Phone...
Samsung not Samsung?
For instance I fixed this ugly issue on my Samsung SM-A202F rooted with Magisk...
Best Regards
Click to expand...
Click to collapse
My Device is Samsung Galaxy S9 SM-G960F. I guess it is not rooted with magisk because magisk app wont work on this device.

ShaDisNX255 said:
It is indeed your root that's causing this problem
Install the Bluetooth Library patcher via Magisk or TWRP (whichever you prefer)
Click to expand...
Click to collapse
As you told, i tried to install the patch file using Magisk for which i installed Magisk. But it did not seem to work. Have a look at the screenshots from the app and log.
What should i do now.