Iv'e sucessfully managed to connect my Gear 2 Neo with alot of custom roms including CM11 / Slimkat with notifications/samsung apps working.
I currently got a samsung GT-I9195 (S4 Mini LTE) running latest NIGHTLY CM11 4.4.4 and got gearmanager and apps 100% working.
1: Download the attached files.
2: First you wanna edit your build.prop to: (I'M NOT RESPONSIBLE FOR ANY BRICKED DEVICES DUE TO EDITING YOU'R BUILD.PROP)
ro.product.brand=samsung
ro.product.manufacturer=samsung
ro.product.model=GT-I9195
reboot...
3: Install the apps in this order:
GR.GearManagerStub.apk
GearManager1_2.apk (I Couldn't upload APK's bigger than 20MB so please see to THIS thread about the actual Gear manager APK)
goproviders.apk (v. 2.0.27)
SAccessoryService_signed.apk (v. 2.14.41)
SAFotaProvider.apk (v. 2.140442.2011)
SAFTCore_signed.apk (2.0.18.4.1)
SANotiProvider_signed.apk (v.1.0.9.42)
saproviders.apk (v. 2.0.87)
TextTemplateProvider_signed.apk (v.2.3.0)
ConnectionManager_signed.apk (v. 1.1.10)
Gear2Plugin.apk (v. 2.1.14052101)
Here's the tricky part, Install either one of the Hostmanager apk's ive uploaded (either v.2.1.14052101 or v.2.0.14031004) and try to launch the Gear manager app from your desktop link.
if it force closes and says Hostmanager have stopped or Gear manager have stopped, just uninstall the current Hostmanager APK and install the other version of Hostmanager and it should open up and connect.
if it connects just install O_signed_SamsungGALAXYApps_14093005.02.008.1_HHP_GED_oldkey.apk that you just downloaded and try run samsung gear apps from your gearmanager.
NOTE: I have got it working with alot of different roms and different Android versions on my samsung by mixing different versions of the Gearmanager APK's , i have also got it to fully work but without samsung apps on my Sony Xperia L (C2105) Using this method.
i do not guarantee this will work for you, this is the way iv'e done it tho and i just wanna share how I did it.
Will this work on cm 12?
jondeponde said:
Will this work on cm 12?
Click to expand...
Click to collapse
No CM12 runs on ART not DALVIK, and gearmanager is not compatible with ART yet. but it will work on most 4.*.*. ROMS on any phone
Admire1991 said:
No CM12 runs on ART not DALVIK, and gearmanager is not compatible with ART yet. but it will work on most 4.*.*. ROMS on any phone
Click to expand...
Click to collapse
But my sgs5 is on stock lollipop rom. And gear manager is working fine with art. Of course, the GM i use is v2.1, above that version gives notification bugs (saprovider fc's) on me even when i was on 4.4.2.
Sent from my SGS5 SM-G900F (0x1) using Tapatalk.
annson08 said:
But my sgs5 is on stock lollipop rom. And gear manager is working fine with art. Of course, the GM i use is v2.1, above that version gives notification bugs (saprovider fc's) on me even when i was on 4.4.2.
Click to expand...
Click to collapse
Oh i actually didnt know that,sorr for beeing misleading then , my saprovider also fc but i use 3rd party apps lile textra instead of original and ALL 3rd party apps notifications work , but none of the "original" apps notifications working ... Tryed 3rd party apps out?
Sent from my SGS5 SM-G900F (0x1) using Tapatalk.
annson08 said:
But my sgs5 is on stock lollipop rom. And gear manager is working fine with art. Of course, the GM i use is v2.1, above that version gives notification bugs (saprovider fc's) on me even when i was on 4.4.2.
Sent from my SGS5 SM-G900F (0x1) using Tapatalk.
Click to expand...
Click to collapse
Hi!
How did you manage this to work? Do you have a guide? Which version of GearManager (2.1.14071502?) are you using?
EDIT: Nvm, I saw that you are using Stock ROM.
Yeah gear 2 works with stock 5.0 on my galaxy s5 and tizen mod 3 but only with gear manager 2.1. 2.2 does not seem to work for anybody. I don't know why it has not been fixed or why it was even released. As far as I can tell it literally does not work with galaxy s5 which is pretty much Samsung's flagship. Silly.
Anyways, was wondering If anybody got ANY custom 5.0 ROMs working with gear manager. I'm on pacman 5.0 right now and was thinking of trying the method posted above but I guess I'll just go back to stock until its easier seeing as I want to stay on 5.0 and the custom ROMs for 5.0 are pretty bare bones right now anyways. If anybody has a more simple method please post it!
Is this a solution to my problem with gear manager at S4 with lollipop (gpe ROM)? It's not working for me at all...
Galaxy S IV @ GE 5.0
Gear Manager sits at "Connecting to Gear" screen
I'm able to pair my Note 2 running CM11 with my Gear (running Tizen), but Gear manager is never able to connect. It just sits there spinning at "Connecting to Gear."
Running Android 4.4.4.
Any tips?
TIA,
Dingo
I have followed your guide and say thank you.
It is working with CM11 and a galaxy note 2 lte model.
My only issues no notification work at all upon the neo 2. Even the chinese cheap watches work very well.
I can not believe samsung have hamstrung these watches only to work with samsung android only.
I have a gear 1, gear 2 neo and gear fit. None work with CM11 it seems.
Hi,
Thanks for this wonderful thread.
I'm running on CM11 (KitKat) on my HP Touchpad tablet and changed the build.prop to be the "Samsung Galaxy 10.1 2014 Wifi tablet". Was able to install all the apks in the order suggested. Ran Gear Manager and it is able to see my Gear 2 Neo smartwatch (yay!). Clicking on the device from the Gear Manager, says "Connecting to Gear" and after a 30-40 seconds, the bluetooth is getting disconnected on the watch. My next step was to reset the watch and start fresh. After the reset, I'm still seeing "Connecting to Gear" for a long time but bluetooth is not getting disconnected. Btw, the Samsung App store app is working pretty good and updating to the newer Gear Manager is still worse where it is not even seeing my paired watch.
I'm running on the stock ROM on the watch and didn't flash it with the Tizen 3.0 ROM yet.
What are my options here? Is there any other way to make the Gear Manager to work?
The main purpose of buying this watch is to pair with my iPhone (for which I think I need to install custom ROM on the watch) and also use "Endomondo" app to transfer fitness data from the watch to the tablet. To use the "Endomondo" app and make it work with the watch, is there a way to bypass the Gear Manager completely and install the Endomondo companion app on the watch?
I'm almost close to getting this work and really hope for a good solution.
Thanks.
Test on cm12.1 note 3 n9005 gear s?
Inviato dal mio SM-N9005 utilizzando Tapatalk
Related
Modded version of Fitbit Mobile to allow sync on all devices with Bluetooth 4.0 Low Energy.
Minumum Android 4.3 version required!
NB Please read official report Android device compatibility
It's recommended to disable background updates or manually turn on/off Bluetooth when sync needed.
Here are reset device instructions: How do I restart my tracker?
Reported as working on devices:
- Google Nexus 4, 5
- Google Nexus 7
- Galaxy Nexus (some ROMs require additional BTLE libraries)
- Samsung Note 2, Note 3
- Samsung Galaxy S3, S4
- LG Optimus G, G2
- LG optimus 4X HD (starting from 4.4.2 (omni rom tested))
- HTC One
- HTC Evo 4G
- HTC DNA
- Motorola Atrix HD
- Motorola Moto X, Droid Maxx (some 4.2.2 ROMs with BTLE are also compatible)
- Sony Xperia Z, Xperia Z Ultra
- Oppo Find 5
Download Mega | AndroidFileHost
can support sony z ultra? if so,i will buy fitbit flex.
adx_x said:
can support sony z ultra? if so,i will buy fitbit flex.
Click to expand...
Click to collapse
It should support this device - it has Bluetooth 4.0 with LE and you can find Android 4.3 firmwares.
I don't have sony z - so ask people in your device thread to be 100% sure.
dimfish said:
It should support this device - it has Bluetooth 4.0 with LE and you can find Android 4.3 firmwares.
I don't have sony z - so ask people in your device thread to be 100% sure.
Click to expand...
Click to collapse
thanks,i have buy it,tomorrow report if can support z ultra...
Hi,
works perfectly with a rooted Galaxy S4, thank you!
Great, it works on my Nexus 7 running CM!
Not working on my Galaxy Nexus though, running stock. Do I need to switch to Cyanogenmod for proper BTLE support with that device?
JeremyNT said:
Not working on my Galaxy Nexus though, running stock.
Click to expand...
Click to collapse
Please read bold red text in 1 post - Android 4.3 minimum required. Also visit thread for your device with BTLE Drivers.
dimfish said:
Please read bold red text in 1 post - Android 4.3 minimum required. Also visit thread for your device with BTLE Drivers.
Click to expand...
Click to collapse
Well the device is running 4.3, but I guess Google disabled BTLE on the Galaxy Nexus for some reason. BTLE works in CM, and I only recently switched back to stock, so I didn't know it was missing.
The needed modifications to stock GNex are on this thread if anybody else encounters this situation:
http://forum.xda-developers.com/showthread.php?t=2387107
JeremyNT said:
Well the device is running 4.3
Click to expand...
Click to collapse
I see I'm sorry I thought you have 'toro' or 'toroplus' - they don't have stock 4.3 like 'maguro'
dimfish said:
I see I'm sorry I thought you have 'toro' or 'toroplus' - they don't have stock 4.3 like 'maguro'
Click to expand...
Click to collapse
I should have been more specific! Fitbit sync seems to work fine for me now that I have applied the modifications to re-enable BTLE, thank you for posting this apk
Thanks a lot dimfish, it's work for me on my s3 with slimbean 4.3. :good:
Awesome work!
Thanks dimfish, this is fantastic!
What does this mean for BLE functionality with other apps, Endomondo for example? Is this a possibility?
Thank you for this app... Just replaced the one already installed and I can now sync with my phone...
Sent from my SM-N900 with Tapatalk
Since you've made this modification, maybe you'll be able to enlighten me to the situation with 4.3 and Bluetooth Low Energy.
Did google push out the BLE spec in such a way that we theoretically shouldn't have to have a hacked app to sync with BLE devices on any 4.3 device, or is it far more complicated in that each device must be custom tailored in the code of the application to sync properly?
If the former is true, I can't really wrap my head around why the Galaxy S4 GPe 4.3 device would have syncing working perfectly with the stock fitbit app, but not the HTC One running a GPe 4.3 rom.
If the latter is true, google didn't fix anything with regards to BLE.
dimfish said:
Modded version of Fitbit Mobile to allow sync on all devices with Bluetooth 4.0 Low Energy.
Minumum Android 4.3 version required!
NB Please read official report Android device compatibility
It's recommended to disable background updates or manually turn on/off Bluetooth when sync needed.
Here are reset device instructions: How do I restart my tracker?
Reported as working on devices:
- Google Nexus 4
- Google Nexus 7
- Galaxy Nexus (some firmwares require additional BTLE drivers)
- LG G2
- HTC One
- Samsung Note 3
- Samsung Galaxy S3, S4 (custom ROMs)
Click to expand...
Click to collapse
Daman09 said:
Since you've made this modification, maybe you'll be able to enlighten me to the situation with 4.3 and Bluetooth Low Energy.
Click to expand...
Click to collapse
Actually I didn't read Google specs, however I don't see any reason why Fitbit should lie about 48 hours problem described here
So trying to avoid this problem they hardcoded supported devices (so you were able to fool it with modified build.prop).
But lets be realistic - this problem right now affects only Fitbit trackers, while android is still working and bluetooth is working - and when Google decide to help fix this specific problem - who knows...
You sir, are my hero! thanks man
Just tried this on my Sprint HTC Evo 4G LTE running CM10.2 (2013-10-11 nightly). I can confirm that it works perfectly with my Fitbit One! Thanks dimfish!
Working on Motorola Atrix HD
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
A few questions, pardon my n00bness:
-Does my HTC One have to be rooted for this to work?
-Does this modified apk modify my build.prop file?
-If so, does the app reverse this change once uninstalled?
Thanks!
I love you.
Working great on my cm10.2 for sg3
[App] Srlabs releases "SnoopSnitch" for detecting IMSI-Catchers, silent SMS...
unfortunetely it only works with some qualcom based devices, you can find a list of working devices under:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
new version is out: 0.9.3
Version 0.9.3
Support Android 5
Fix initialization issue on newer devices
Translation to German and Dutch
Click to expand...
Click to collapse
SnoopSnitch is an Android app that collects and analyzes mobile radio data to make you aware of your mobile network security and to warn
you about threats like fake base stations (IMSI catchers), user tracking and over-the-air updates. With SnoopSnitch you can use the data collected in the GSM Security Map at gsmmap.org and contribute your own data to GSM Map.
This application currently only works on Android phones with a Qualcomm chipset and a stock Android ROM. It requires root priviliges to capture mobile network data.
Requirements:
Qualcomm-based Android phone (see list below)
Stock Android ROM, version 4.1 or later
Note: Unfortunately, custom Android ROMs like CyanogenMod are not supported, as they lack the drivers necessary to collect radio data.
Root privileges on phone
Tested Devices:
The following devices have been verified to work:
Samsung S3 Neo (GT-I9301I)
LG G2 (LG-D802)
Sony Xperia Z1 (C6903)
Samsung S5 (SM-G900F)
Motorola Moto E (Moto E)
Samsung S4 (Qualcomm variant)
It is very likely that other Qualcomm-based Android phones also work, if they are rooted and have a stock firmware.
Incompatible Devices:
The following devices have been found to be incompatible and can not be used with SnoopSnitch:
UNSUPPORTED: Every device without a Qualcomm chipset
UNSUPPORTED: Every device with custom ROM
UNSUPPORTED: Samsung Galaxy S2 & S3
UNSUPPORTED: Nexus 5
UNSUPPORTED: Huawei Ascend Y300
Click to expand...
Click to collapse
from https://opensource.srlabs.de/projects/snoopsnitch (project site)
or google play link:
https://play.google.com/store/apps/details?id=de.srlabs.snoopsnitch
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
geminga said:
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
Click to expand...
Click to collapse
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
xd.bx said:
About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Well, Carsten Nohl, one of the developers, said yesterday on 31C3, that on CustomROMS like CM certain proprietary drivers are missing, which are needed for getting certain debugging information. Later yesterday in a workshop on 31C3 participants found out, that on some CM11 Phones the app is working.
There the app worked on:
Samsung S3 Neo
Samsung S5
LG G2
Sony Xperia Z1
Motorola Moto E
and dind't work on
Samsung S2, S3, S4 and S5 Exynos
Nexus 5
Fairphone
you can watch the presentation from Nohl on 31C3 here:
http://media.ccc.de/browse/congress...830_-_mobile_self-defense_-_karsten_nohl.html
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
About the compatible devices - I can confirm the app works on on Xperia V with the stock 4.3 Android. It gives no errors, but I have not yet encountered malicious GSM cells to verify the detection works ok.
Why do we have to make long distance calls and send sms to use this app?
http://forum.xda-developers.com/showthread.php?t=1422969
Celestial Fury said:
Why do we have to make long distance calls and send sms to use this app?
Click to expand...
Click to collapse
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
rudolfm said:
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
Click to expand...
Click to collapse
Sure I did. It doesn't say why we have to call/sms a specific number and why we data can't be gathered from our every day call/sms and why data can't be sent to the test site through the internet rather than call/sms.
XsheldorX said:
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
Click to expand...
Click to collapse
You need to flash a compatible kernel. http://d-h.st/mmb
Works on my SONY Xperia Z1 with CM11.
Though, when doing the test call my device was banned, for whatever reason....
Yeah I can (probably) confirm this with Z1 compact with CM 11. Works since day one I guess. The test works (around the first days incoming calls and sms did not, probably because of overload of the callingserver), but never had any sort of attacks. Now I'm in doubt if radio-part does not work with cm 11, as mentioned in the description, or there were zero attacks.
Another thing I observed. The software sometimes produces many wake-locks. But I guess thats normal if backgroundservice is active.
@ papperlapapp: Did you monitor any attacks (SS7 or silent sms)? Or even IMSI-catchers?
Installed the app without problems on my S5 with Phoenix ROM (Stock Based). However, when I start the active test, the app stops responding and android asks me several times if I want to close it. I chose no every time. Now I'm wondering if the tests are still running in the background or if the app just hang. Started the tests about 35 min ago, still waiting, absoluteley nothing happened yet.
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Works on Samsung Note 3 SM-N9005
Sent fra min SM-N9005 via Tapatalk
xperia E1 seemingly working
E1 seems to work.
but now what ? where are the logfiles where I see stuff live?
google 31c3 "mobile self defense" for the thrilling background story
let's all hope the CCC talkers have learnt better English by 2016 (Mr Nohl being one of the best still) !
https://media.ccc.de/browse/congres...self-defense_-_karsten_nohl.html#video&t=3838
xd.bx said:
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
MForce22 said:
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
Click to expand...
Click to collapse
I don't know. Just try, at worst you'll have to reflash the old kernel back.
itman-ch said:
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Click to expand...
Click to collapse
it is on play store too ^^
srlabs posted a device list:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
and a new version is out:
Version history
Version 0.9.2
Fixed app lock-up issues
Improved device compatibility check
Handled unsupported LTE gracefully
Version 0.9.1
Fix problem where SnoopSnitch would leave the phone muted after a test
Remove issue with disappearing (Skype) dialing dialogs
Resolved performance issue in analysis
Version 0.9.0
Initial public release
Click to expand...
Click to collapse
Game tuner for any S6 based lolipop Rom
Tested on Aurora rom s6 v3.0
Let me know if it works for you
Install Guide
1)Install the files in the zip as normal apks
(The zip is not flashable)
Video Guide And be sure to be subscribed to this channel for more tech videos for galaxy s4 and other stuff
https://youtu.be/Cgq-mZMj99Y
Download link:https://www.dropbox.com/s/ck27dc47nnib5fm/%5BLL%5DNon%20flashable%20game%20tuner%20for%20s6%20based%20rom.zip?dl=0
Disclamer: I am not responsible if your device gets bricked or anything like that
click the thanks button if it worked for you
Doesnt work. It says "gameservice" needs to be updated on galaxy store
BraianV said:
Doesnt work. It says "gameservice" needs to be updated on galaxy store
Click to expand...
Click to collapse
After updating from galaxy apps you will be able to use it
I dont have that store because of my debloated rom. Can you upload the updated apk?
Hey guys,
So I got a Gear S2 and I tried to install the gear app. However, when I try to run it it says that my phone is modified in an unauthorized way and that the gear app won't run on my os. So, I know that my phone is modified because I've installed CM12.1 and a recovery on it. Now, I do not want to stop using cm and revert to stock so how can I make the gear app work with my phone? Oh, probably should've mentioned this earlier, I have a Samsung Galaxy S3 Neo.
Fixed it. Open build.prop with an editor of your choice and replace everything that says "samsung" with "htc" (LOWER case). After that install the accessory and gear plugin and launch the app
Yeah had the same problem on my S5 with CmM13, just easy change at build.prop in /system like SpeederT12 already said to HTC or some other manufractor that work with it (I write htc in it and that reboot your phone and install the gear plugin and the accesory app as a apk and everything works fine
I have a oneplus 2 on cm13, root xposed, and I stuck on connecting. I installed the three recommend apps.
Someone can help me please?
I have the same problem with a galaxy s3 mini on CM. Gear App starts but does not find the clock. I can see it as a Bluetooth device however.
Urbiman said:
I have the same problem with a galaxy s3 mini on CM. Gear App starts but does not find the clock. I can see it as a Bluetooth device however.
Click to expand...
Click to collapse
hi, it works with s3 mini on cm12.1. :good:
look this thread: http://forum.xda-developers.com/gear-s2/help/pair-gear-s2-moto-g-t3323385
posts: #12, #19
best regards
Hi there, any help please ?
I tried to download Samsung's Wearable App from Google's Playstore to my S3 mini (I8190). It was refused, because my S3 had still Android 4.1.2. I installed CyanogenMod 11 successfully, hoping it should work. Download of the Wearable App worked well, however, installation failed because of OS mismatch. Then I tweeked the file /System/build.prop like:
ro.product.model=GT-I8190
ro.product.brand=Samsung
ro.product.name=GT-I8190
ro.product.device=GT-I8190
However, no change, Samsung's Wearable app does not accept CM11. I'm lost ...:crying:
Any idea ?
Thanks for help !
LikemyS3