Hello, I am running a Note II with jedi master x2 4.3 and purchased a Gear 2 neo, running latest firmware version.
http://forum.xda-developers.com/showthread.php?t=2568537
I cannot remember if I uninstalled S-Voice or it is not included, either way after trying to get it to work I donwloaded and installed an APK for the s4's s voice, it starts up and seems to work on the phone, but the watch is not recognizing it (and I did restart the watch, at which point it asked me (again) to accept the terms and conditions for S-Voice and again told me it needed to be installed.
Any thoughts? And thanks for taking the time to read this!
stonechitlin said:
Hello, I am running a Note II with jedi master x2 4.3 and purchased a Gear 2 neo, running latest firmware version.
http://forum.xda-developers.com/showthread.php?t=2568537
I cannot remember if I uninstalled S-Voice or it is not included, either way after trying to get it to work I donwloaded and installed an APK for the s4's s voice, it starts up and seems to work on the phone, but the watch is not recognizing it (and I did restart the watch, at which point it asked me (again) to accept the terms and conditions for S-Voice and again told me it needed to be installed.
Any thoughts? And thanks for taking the time to read this!
Click to expand...
Click to collapse
It seems the problem is with your phone setup, not the Gear 2. You should ask this question in a thread that is dedicated to discussing your Note 2 ROM.
BlackZenith said:
It seems the problem is with your phone setup, not the Gear 2. You should ask this question in a thread that is dedicated to discussing your Note 2 ROM.
Click to expand...
Click to collapse
Thanks for the input, I will give that a shot.
Edit: I fixed it using these instructions as if my phone was a non samsung
Hi everyone,
I have a Nexus 5 that was purchased from TELUS (in a rush since I couldn't wait for a google play store version to make it here). Is there any way for me to flash or change my phone to get it's updates from google directly, and thus removing TELUS from the equation? EG my update to 4.4.3 was way behind google's push, and since it is a Nexus 5 there's no customizations that I can think of that TELUS would actually do to this phone.
I'd really like to have this device as if it came from the play store.
Thanks!
There is no such thing as carrier branded software on a nexus (with exception of Verizon on the Gnex... but different story).
Updates aren't always going to be on time; you just have to wait.
korockinout13 said:
There is no such thing as carrier branded software on a nexus (with exception of Verizon on the Gnex... but different story).
Updates aren't always going to be on time; you just have to wait.
Click to expand...
Click to collapse
So to state the obvious then, my phone doesn't communicate with TELUS update servers, it's straight to google? Is there a way I can check this in developer options or anything?
froek said:
So to state the obvious then, my phone doesn't communicate with TELUS update servers, it's straight to google? Is there a way I can check this in developer options or anything?
Click to expand...
Click to collapse
every single current nexus gets its update from google(or gets updated manually). updates are promised to go to everyone within a 3 week period. if you somehow changed any system files, you wont get an ota. just update your phone manually, its easy and faster.
simms22 said:
every single current nexus gets its update from google(or gets updated manually). updates are promised to go to everyone within a 3 week period. if you somehow changed any system files, you wont get an ota. just update your phone manually, its easy and faster.
Click to expand...
Click to collapse
Where's the best place to locate all OTA files? Is there a place to browse to select, or is it always like in this post where they mention the link only:
http://forum.xda-developers.com/showpost.php?p=53135171
froek said:
Where's the best place to locate all OTA files? Is there a place to browse to select, or is it always like in this post where they mention the link only:
http://forum.xda-developers.com/showpost.php?p=53135171
Click to expand...
Click to collapse
http://www.randomphantasmagoria.com/firmware/nexus-5/hammerhead/
all official nexus factory images https://developers.google.com/android/nexus/images
but there isnt a page with all official otas.
Great! Thanks very much everyone
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
To make a long story short:
I'm a diabetic and used to use my old phones (Note 3, Galaxy s6) to read my glucose level with an app called LibreLink. This made being a diabetic so much easier - no need to carry an extra reader with me all the time.
Appearently Samsung S8 and S8+ (and S7) worked fine with the Libre sensors at first - but an OTA update changed *something* and suddenly S7/S8/S8+ no longer worked. And they still don't. Some users have reverted back to an older official firmware to get the sensor readings back, but I'd rather stay on a newer fw because of.. well, deodex, debloat, tweaks... (Currently using Batman rom 1.0 and loving it).
Do we have any developers here that could check if it would be possible to replace/revert the new NFC-files/settings with the ones from the oldest 955F firmware? I really wouldn't know where to start with this...
efex said:
To make a long story short:
I'm a diabetic and used to use my old phones (Note 3, Galaxy s6) to read my glucose level with an app called LibreLink. This made being a diabetic so much easier - no need to carry an extra reader with me all the time.
Appearently Samsung S8 and S8+ (and S7) worked fine with the Libre sensors at first - but an OTA update changed *something* and suddenly S7/S8/S8+ no longer worked. And they still don't. Some users have reverted back to an older official firmware to get the sensor readings back, but I'd rather stay on a newer fw because of.. well, deodex, debloat, tweaks... (Currently using Batman rom 1.0 and loving it).
Do we have any developers here that could check if it would be possible to replace/revert the new NFC-files/settings with the ones from the oldest 955F firmware? I really wouldn't know where to start with this...
Click to expand...
Click to collapse
I noticed that you used your LibreLink. My son is a T1 Diabetic, and we REALLY would like to use the LibreLink, however here in the USA it will not allow me to download the program. Do you or anyone else know how to get this program? PLEASE help.
Following this thread.
aspag said:
I noticed that you used your LibreLink. My son is a T1 Diabetic, and we REALLY would like to use the LibreLink, however here in the USA it will not allow me to download the program. Do you or anyone else know how to get this program? PLEASE help.
Click to expand...
Click to collapse
sure, here ya go!
https://drive.google.com/file/d/1O0-aLWYuyrCGev8fS_G_hxng7EFlvqcW/view?usp=sharing
I'm not sure if it's the current version, as my phone isn't officially supported.. But it works great
Thank you! So I downloaded it and it installed fine. However, when I tried to open it it tells me to download it from Google Play. Must be some sort of security. So anyhow something is blocking it... Any thoughts?
I've just gotten myself onto a Galaxy S7 for my carrier with Nougat installed. I happen to like the looks of this version and have no consideration to update to Android Oreo (8.0). But this looks to be a forced update. I have merely avoided this by just not connecting to wifi, however this makes me unable to use the samsung cloud without using mobile data to backup pictures and content. The only way I could perform disabling the update was through rooting the device, which I did not like having to do at all. It only brought complications to the devices run patterns etc.
As well I have also searched everywhere to find a way to disable the update service without rooting, even as far as Package Disabler Pro however it seems the developer was forced by samsung to disable this capability during the Note 7 Era. Even trying to use an Older Version of PDP failed because of the License Verification.
So I have come here to ask, Has anyone at all ever found a way to stop the update service from forcibly downloading the update when connected to wifi and forcing the device to update whatsoever, without Rooting the Device. Your knowledge and advice would be highly appreciated
ben70190 said:
I've just gotten myself onto a Galaxy S7 for my carrier with Nougat installed. I happen to like the looks of this version and have no consideration to update to Android Oreo (8.0). But this looks to be a forced update. I have merely avoided this by just not connecting to wifi, however this makes me unable to use the samsung cloud without using mobile data to backup pictures and content. The only way I could perform disabling the update was through rooting the device, which I did not like having to do at all. It only brought complications to the devices run patterns etc.
As well I have also searched everywhere to find a way to disable the update service without rooting, even as far as Package Disabler Pro however it seems the developer was forced by samsung to disable this capability during the Note 7 Era. Even trying to use an Older Version of PDP failed because of the License Verification.
So I have come here to ask, Has anyone at all ever found a way to stop the update service from forcibly downloading the update when connected to wifi and forcing the device to update whatsoever, without Rooting the Device. Your knowledge and advice would be highly appreciated
Click to expand...
Click to collapse
Wow this is disappointing. I'm in the same position. I unintentionally tapped update vs, wait and now it asks me several times a day.
I didn't have any of these issues with my S5. Since when does samsung force their customers to update? Seems to me samsung still owns my phone after I paid for it. If I wanted this crap, I would have bought an apple. i can't believe everyone is ok with this? Not even a data toggle switch anymore. I had to use ADB to put this back. My S5 was able to multi-task and my S7 can't. Further my 5 can get on wifi faster. None of this should be possible.
Forced to Root
ADB my S7 said:
Wow this is disappointing. I'm in the same position. I unintentionally tapped update vs, wait and now it asks me several times a day.
I didn't have any of these issues with my S5. Since when does samsung force their customers to update? Seems to me samsung still owns my phone after I paid for it. If I wanted this crap, I would have bought an apple. i can't believe everyone is ok with this? Not even a data toggle switch anymore. I had to use ADB to put this back. My S5 was able to multi-task and my S7 can't. Further my 5 can get on wifi faster. None of this should be possible.
Click to expand...
Click to collapse
I guess theres no solution to this then other than rooting the device sadly. I was forced to root it and I used the root method that requires no having to tweak the kernel so its been going pretty good for now. But yes indeed even my Galaxy S4 is faster than my s7 now in some cases. But the only thing I can see the issue with is now I hate having to restart my S7 when im using it because it takes like a minute or two to fully load up everything. Feels like im using a PC and not a phone
any luck ?