[Challenge] Why is "because X phone won't work with Gear Manager" acceptable?
I find this hard to believe and a slightly lazy answer to a common problem. There is obviously code in the APK that refuses to work on any non-Samsung device. Dozens of threads exist with people offering up the entire Gear APK catalog, some trying to get it to work on Nexus & and others.
fOmey and others have reverse engineered the entire ROM, but no one has figured out a way to "fix" one single app to allow it to work with all phones?
Is this not a work-in-progress somewhere? It's certainly not in any thread I have found.
What are the limitations to such a venture? Has it been tried? Is there a copyright issue? What reason has this not been attempted?
Our community has done some amazing things over the years and this site is the go-to place for rooting and hacking. There has to be one sole out there willing to give this a shot.
I am, by no means, a programmer or coder. I would take this up, but I do not have the skillset. Best I can do is go through XML files and the like hoping to find "if X=Z then A" and remove it.
Ultimately this would give us the missing companion to null_ that allows notifications and interactivity (i.e. Music player controls, etc)
So-- any takers?
I have a Nexus 5, even with the app fully running, I can only get the phone call part to work - talk/listen/incoming caller contact name
The way to get around unsupported device is with the GearManagerStub apk
I've had a bit of a search through most of the code, and from what I can tell all the apks are included so can only conclude there must be something in tw framework. Or I missed something...
http://forum.xda-developers.com/showthread.php?t=2549058
Brendo said:
even with the app fully running, I can only get the phone call part to work - talk/listen/incoming caller contact name
Click to expand...
Click to collapse
This is not helped by the app. I have mine tethered to an iPhone 3gs(not by choice) and it works fine with no software at all.
styz said:
This is not helped by the app. I have mine tethered to an iPhone 3gs(not by choice) and it works fine with no software at all.
Click to expand...
Click to collapse
To load the gear manager app, it is.. You simply connected your gear via bluetooth.
The gear manager app pushes notifications to the gear.
Without the GearManagerStub.apk it fails to load, its depends on this particular app.
It's pretty simple actually - and the same reason Sense doesn't run (well) on non-HTC devices. Samsung's got a huge proprietary framework on their phones that their proprietary apps expect to be in place and depend on. So plopping Gear Manager on a phone that doesn't have the expected underlying s/w causes it to fail or deliver bits and pieces of functionality. Someone could probably figure out which pieces of Samsung's framework need to be in place but if there are a ton of them adding useless bloat (outside the Gear functionality) wouldn't it be easier just to use the Gear with a Samsung phone? And the design point Samsung's chosen (dependency on proprietary Samsung code on the phone for the Gear to work) pretty much tells you that, at least for now, they are happy with restricting Gear sales to owners of Samsung devices. Hell, the SGS4 GPe doesn't even support the Gear.
Just a personal thought, at $299 (I know, it was 30% less at T-Mobile) the Gear's a questionable investment (AKA: a "play thing") as it is. Accepting that key features (of the few provided) are missing to get it to work on a non-Samsung phone seems like a great garage project but not a very good use of $299. Just my opinion of course.
BarryH_GEG said:
It's pretty simple actually - and the same reason Sense doesn't run (well) on non-HTC devices. Samsung's got a huge proprietary framework on their phones that their proprietary apps expect to be in place and depend on. So plopping Gear Manager on a phone that doesn't have the expected underlying s/w causes it to fail or deliver bits and pieces of functionality. Someone could probably figure out which pieces of Samsung's framework need to be in place but if there are a ton of them adding useless bloat (outside the Gear functionality) wouldn't it be easier just to use the Gear with a Samsung phone? And the design point Samsung's chosen (dependency on proprietary Samsung code on the phone for the Gear to work) pretty much tells you that, at least for now, they are happy with restricting Gear sales to owners of Samsung devices. Hell, the SGS4 GPe doesn't even support the Gear.
Just a personal thought, at $299 (I know, it was 30% less at T-Mobile) the Gear's a questionable investment (AKA: a "play thing") as it is. Accepting that key features (of the few provided) are missing to get it to work on a non-Samsung phone seems like a great garage project but not a very good use of $299. Just my opinion of course.
Click to expand...
Click to collapse
I am purchasing home automation items and bluetooth adaptors for my vehicle so I don't think of this as a toy. I consider it a great step forward.
fOmey said:
...Without the GearManagerStub.apk it fails to load, its depends on this particular app.
Click to expand...
Click to collapse
I installed the stub and the gearmanager apks and it still gave me a 'unsupported device' message. *sadface*
therealduckie said:
I am purchasing home automation items and bluetooth adaptors for my vehicle so I don't think of this as a toy. I consider it a great step forward.
Click to expand...
Click to collapse
Just because you can doesn't mean you should. Why would an underpowered device with a 315mAh battery, 512MB of RAM, and a 1.63" display be the best "tool for the job" you described? Especially when it requires a host in near-by proximity for the majority of its functions? It's great what people are doing with the Gear outside the mission Samsung released it for but, like I said before, you're talking about parlor tricks more for sport than serving a function unachievable by better means; some of which are more practical. And if you're trying to use the Gear while driving, especially if you've shrunk the DPI with a launcher, good luck. It's hard enough using the basic functions and S Voice while driving without ending up in another lane. I'm not criticizing everyone's ingenuity and cleverness just pointing out how impractical some things can appear when you take in to account what the Gear really is; a shamefully low-spec, low functionality Android "phone" with a tiny screen that happens to have a wrist band.
BarryH_GEG said:
It's pretty simple actually - and the same reason Sense doesn't run (well) on non-HTC devices. Samsung's got a huge proprietary framework on their phones that their proprietary apps expect to be in place and depend on. So plopping Gear Manager on a phone that doesn't have the expected underlying s/w causes it to fail or deliver bits and pieces of functionality. Someone could probably figure out which pieces of Samsung's framework need to be in place but if there are a ton of them adding useless bloat (outside the Gear functionality) wouldn't it be easier just to use the Gear with a Samsung phone? And the design point Samsung's chosen (dependency on proprietary Samsung code on the phone for the Gear to work) pretty much tells you that, at least for now, they are happy with restricting Gear sales to owners of Samsung devices. Hell, the SGS4 GPe doesn't even support the Gear.
Just a personal thought, at $299 (I know, it was 30% less at T-Mobile) the Gear's a questionable investment (AKA: a "play thing") as it is. Accepting that key features (of the few provided) are missing to get it to work on a non-Samsung phone seems like a great garage project but not a very good use of $299. Just my opinion of course.
Click to expand...
Click to collapse
That's why this is a challenge
Im intrigued.. I want to figure this out, I prefer to use AOSP. Iv been forced to go back to TouchWiz since owning a gear.
I might have to do some more digging around.
therealduckie said:
I installed the stub and the gearmanager apks and it still gave me a 'unsupported device' message. *sadface*
Click to expand...
Click to collapse
Depends how you do it? I moved the apk to system/app and then had to install it (so that it was in data/app as com.whatever as it looks for apk based on that name). May not need it in system app anymore
Which phone?
---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------
fOmey said:
That's why this is a challenge
Im intrigued.. I want to figure this out, I prefer to use AOSP. Iv been forced to go back to TouchWiz since owning a gear.
I might have to do some more digging around.
Click to expand...
Click to collapse
Do you know how much touchwiz is in google edition roms? Does gear fully work with ge roms?
Brendo said:
Depends how you do it? I moved the apk to system/app and then had to install it (so that it was in data/app as com.whatever as it looks for apk based on that name). May not need it in system app anymore
Which phone?
---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------
Do you know how much touchwiz is in google edition roms? Does gear fully work with ge roms?
Click to expand...
Click to collapse
Sadly I was able to test extensively using GE, although I did find all the initial APK's installed & completed successfully.
I didn't get a chance to pair up completely, the base keeps randomly rebooting (nothing related to the gear). This could be due a modified gearmanagerstub.apk on the GE base, I'm not entirely sure.
I could easily upload a version of the stub APK, you can give it a go on your nexus ?
EDIT: GearManagerStub.apk : From KitKat Google Edition (i9505) & (Uninstall existing GearManager.apk before testing).
BarryH_GEG said:
Just because you can doesn't mean you should. Why would an underpowered device with a 315mAh battery, 512MB of RAM, and a 1.63" display be the best "tool for the job" you described? Especially when it requires a host in near-by proximity for the majority of its functions? It's great what people are doing with the Gear outside the mission Samsung released it for but, like I said before, you're talking about parlor tricks more for sport than serving a function unachievable by better means; some of which are more practical. And if you're trying to use the Gear while driving, especially if you've shrunk the DPI with a launcher, good luck. It's hard enough using the basic functions and S Voice while driving without ending up in another lane. I'm not criticizing everyone's ingenuity and cleverness just pointing out how impractical some things can appear when you take in to account what the Gear really is; a shamefully low-spec, low functionality Android "phone" with a tiny screen that happens to have a wrist band.
Click to expand...
Click to collapse
Gear, with null_, requires no host. It can also connect to bluetooth enabled devices other than a phone.
I was motivated but this: http://daisyworks.net/btgarage.html
It's brilliant and exactly what i have needed for years.
Other interesting links:
http://www.smarthome.com/android_apps.html
http://www.instructables.com/id/Home-Automation-using-Arduino-Android-Phone/
Fact is, this is not a toy when something like null_ is used. It offers a great deal more functionality in a much smaller and more portable/handy package.
Your bias against the device is obvious so it begs the question: why are you here? Just to raise your post count and stir drama in an otherwise peaceful sub-group? Or, do you own it and you are so disappointed that you refuse to see its potential?
Either way, your negativity will not sway me or change my mind. I know it has potential and I plan to use it fully. The fact that it has a wristband is a feature and a plus.
Oh, and I don't consider something that has multiple times the computing power of the original Apollo moon landings "low specs". <3
fOmey said:
To load the gear manager app, it is.. You simply connected your gear via bluetooth.
The gear manager app pushes notifications to the gear.
Without the GearManagerStub.apk it fails to load, its depends on this particular app.
Click to expand...
Click to collapse
Maybe i wasn't clear in my post. I was responding to the phone call portion of the gear. Even without the software installed it still allows the phone calls to be taken and shows the contact information on the watch just like it did on the g4s with the app. All i was saying is that he commented that he was only able to get the phone portion working with the app and i was explaining that you can do that without the app.
fOmey said:
EDIT: GearManagerStub.apk : From KitKat Google Edition (i9505) & (Uninstall existing GearManager.apk before testing).
Click to expand...
Click to collapse
Tried it. Same result. 2 gear manager apps still refuse to install - music and weather (I believe because they reply on specific apps?). Nfc setup connection still works. App still works, but no details get sent to watch. Perhaps tw framework hooks in and serves data to gearmanagerstub, then stub sends to manager, which sends to watch?
---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------
styz said:
Maybe i wasn't clear in my post. I was responding to the phone call portion of the gear. Even without the software installed it still allows the phone calls to be taken and shows the contact information on the watch just like it did on the g4s with the app. All i was saying is that he commented that he was only able to get the phone portion working with the app and i was explaining that you can do that without the app.
Click to expand...
Click to collapse
Yes, from what I understand, the Bluetooth headset part is the only 'generic' part of the watch. It receives data just like a car headset when it displays contact info etc
Just installed that STUB with both the 1.5 and 1.2 GM and both still showed me a 'device not supported" error message.
I spent about 2 hours with Samsung one night and they told me it had to do with baseband version...or that mine was a 4.1 baseband (even though I am running CM 10.2 with 4.3 OS).
Perhaps there is a lockout on older baseband versions?
This is an SG3 phone, by the way.
therealduckie said:
Just installed that STUB with both the 1.5 and 1.2 GM and both still showed me a 'device not supported" error message.
I spent about 2 hours with Samsung one night and they told me it had to do with baseband version...or that mine was a 4.1 baseband (even though I am running CM 10.2 with 4.3 OS).
Perhaps there is a lockout on older baseband versions?
This is an SG3 phone, by the way.
Click to expand...
Click to collapse
How did you install? Try deleting; move to system/app; installing from system/app
Brendo said:
How did you install? Try deleting; move to system/app; installing from system/app
Click to expand...
Click to collapse
Sorry, I should have been more clear...
I installed them both fine. It's when i try to pair the Gear that I get that message.
therealduckie said:
Sorry, I should have been more clear...
I installed them both fine. It's when i try to pair the Gear that I get that message.
Click to expand...
Click to collapse
Did you delete the touchwiz launcher off your gear ? That will cause a unsupported device error also.. learnt this the hard way !
Brendo said:
Tried it. Same result. 2 gear manager apps still refuse to install - music and weather (I believe because they reply on specific apps?). Nfc setup connection still works. App still works, but no details get sent to watch. Perhaps tw framework hooks in and serves data to gearmanagerstub, then stub sends to manager, which sends to watch?
Click to expand...
Click to collapse
If you can narrow down which two of those APK's dont install, I can try figure out why.. First step on getting this working is simply identifying what exactly is not working and why.
Once we can get gearmanager running on other branded phones, I'm confident the notifications may work.. or atleast the "more notifications".
fOmey said:
Did you delete the touchwiz launcher off your gear ? That will cause a unsupported device error also.. learnt this the hard way !
Click to expand...
Click to collapse
I'm using Nova Launcher as my launcher on my phone. TouchWiz doesn't even load on boot, that I am aware of.
fOmey said:
Did you delete the touchwiz launcher off your gear ? That will cause a unsupported device error also.. learnt this the hard way !
Click to expand...
Click to collapse
Really? I still have tw on my gear :s
If you can narrow down which two of those APK's dont install, I can try figure out why.. First step on getting this working is simply identifying what exactly is not working and why.
Once we can get gearmanager running on other branded phones, I'm confident the notifications may work.. or atleast the "more notifications".
Click to expand...
Click to collapse
I still have to install all the extra apks manually
- SAMusicProvider_signed.apk
- SAWeatherProvider_signed.apk
I was wondering if there was any way to add MAP to the bluetooth profiles to add messaging support for receiving texts in the car. I see that Moto left out this profile for some reason and I kind of miss that feature. I wasn't sure if there was a way to add this and reflash the radio drivers to the phone.
My phone is an unlocked Dev Edition XT1060 on 4.4.
htmwrx said:
I was wondering if there was any way to add MAP to the bluetooth profiles to add messaging support for receiving texts in the car. I see that Moto left out this profile for some reason and I kind of miss that feature. I wasn't sure if there was a way to add this and reflash the radio drivers to the phone.
My phone is an unlocked Dev Edition XT1060 on 4.4.
Click to expand...
Click to collapse
I am not quite sure what you are asking. Do you want to have messages from other programs read out from Moto Assist?
Or do you want to have your texts read out over a different BT profile?
It might not be quite what you are looking for but this app (http://forum.xda-developers.com/showthread.php?t=2123493) was mentioned in this thread (http://forum.xda-developers.com/showthread.php?t=2599230) regarding bluetooth operation in Kitkat.
mechanical tool said:
I am not quite sure what you are asking. Do you want to have messages from other programs read out from Moto Assist?
Or do you want to have your texts read out over a different BT profile?
It might not be quite what you are looking for but this app (http://forum.xda-developers.com/showthread.php?t=2123493) was mentioned in this thread (http://forum.xda-developers.com/showthread.php?t=2599230) regarding bluetooth operation in Kitkat.
Click to expand...
Click to collapse
Not exactly. On my previous phone, when I received a text message, the message would be sent to the car via bluetooth and read aloud. The Bluetooth profile used is called MAP, or Message Access Profile. Motorola did not include this profile in their drivers, presumably to encourage users to use the moto assist feature . I was wondering if it was possible to add this profile and reflash the updated radio drivers. But this may also include adding lines of code to the rom itself. I was unsure if this was even probable to do.
Hey everyone,
I unlocked my boot loader, rooted, and flashed CM11 on my Moto X a couple days ago. I am only missing the Active Display feature from stock and wanted to replace it with something from the play store. I am running into a problem with both acDisplay and Dynamic Notifications apps. They both work when I get notifications, however do not work at all when set to "active mode". They should be using proximity and motion sensors to imitate how the Moto X normally operates. Does anyone know a way to get them to work similar to how they are "advertised" to work?
I'm sorry, I don't know the answer to your issue..
But I wanted to say, any app that mimics Active Display will take a great toll on your battery life. Active display is designed to use an extremely small amount of battery on the Moto X.... Any other app will not be so battery friendly.
This is why the majority of users stick to stock, with Xposed and Gravity Box for customization.... Or use stock based roms, that have the unique moto features in them.
i.Design said:
Hey everyone,
I unlocked my boot loader, rooted, and flashed CM11 on my Moto X a couple days ago. I am only missing the Active Display feature from stock and wanted to replace it with something from the play store. I am running into a problem with both acDisplay and Dynamic Notifications apps. They both work when I get notifications, however do not work at all when set to "active mode". They should be using proximity and motion sensors to imitate how the Moto X normally operates. Does anyone know a way to get them to work similar to how they are "advertised" to work?
Click to expand...
Click to collapse
In not seeing where either of those apps claim to use the sensors in a similar way as stock active display. Where do you see that they are advertised to do so?
Edit: scratch that. I do see that acdisplay claims to use the sensors.... Not sure why it isn't working for you.
@KJ is correct that they will use much more battery than stock AD, which takes advantage of the low voltage components of the X.
The Moto Hint page lists "advanced features" as follows:
http://www.motorola.com/us/accessories-bluetooth-headsets/Moto-Hint/moto-hint-pdp.html
"Pair with your Moto X and ask questions like, “What’s today’s forecast?” or “How do I get home?” and get answers directly in your ear. You can also hear notifications, make calls, and send messages without having to touch or look at your phone.*"
The asterisk on the bottom of the page says: "* Requires Moto Voice, only available on Moto X (2nd Gen.) and Droid Turbo."
Is this pre N6 dated information, or should the Always Listening Capabilities of the N6 allow this functionality with this device?
l_stevens said:
The Moto Hint page lists "advanced features" as follows:
http://www.motorola.com/us/accessories-bluetooth-headsets/Moto-Hint/moto-hint-pdp.html
"Pair with your Moto X and ask questions like, “What’s today’s forecast?” or “How do I get home?” and get answers directly in your ear. You can also hear notifications, make calls, and send messages without having to touch or look at your phone.*"
The asterisk on the bottom of the page says: "* Requires Moto Voice, only available on Moto X (2nd Gen.) and Droid Turbo."
Is this pre N6 dated information, or should the Always Listening Capabilities of the N6 allow this functionality with this device?
Click to expand...
Click to collapse
Moto Voice and always listening are different. Moto Voice is a seaparate API that calls on Google's Google Now Voice Commands so it's safe to say this won't work as described with the Nexus 6.
l_stevens said:
The Moto Hint page lists "advanced features" as follows:
http://www.motorola.com/us/accessories-bluetooth-headsets/Moto-Hint/moto-hint-pdp.html
"Pair with your Moto X and ask questions like, “What’s today’s forecast?” or “How do I get home?” and get answers directly in your ear. You can also hear notifications, make calls, and send messages without having to touch or look at your phone.*"
The asterisk on the bottom of the page says: "* Requires Moto Voice, only available on Moto X (2nd Gen.) and Droid Turbo."
Is this pre N6 dated information, or should the Always Listening Capabilities of the N6 allow this functionality with this device?
Click to expand...
Click to collapse
Donjuanal beat me to it. And don't you think it would be odd for it to be pre-N6 dated information, when the Droid Turbo was only just recently announced, well after the N6 was?
l_stevens said:
The Moto Hint page lists "advanced features" as follows:
http://www.motorola.com/us/accessories-bluetooth-headsets/Moto-Hint/moto-hint-pdp.html
"Pair with your Moto X and ask questions like, “What’s today’s forecast?” or “How do I get home?” and get answers directly in your ear. You can also hear notifications, make calls, and send messages without having to touch or look at your phone.*"
The asterisk on the bottom of the page says: "* Requires Moto Voice, only available on Moto X (2nd Gen.) and Droid Turbo."
Is this pre N6 dated information, or should the Always Listening Capabilities of the N6 allow this functionality with this device?
Click to expand...
Click to collapse
You can still use the Hint with the N6, it just won't have all the Moto Voice features that you get with the Moto X.
_MetalHead_ said:
You can still use the Hint with the N6, it just won't have all the Moto Voice features that you get with the Moto X.
Click to expand...
Click to collapse
Does that mean it will be always listening or no?
I also just bought the Moto hint and paired it with my N6. I sure would love for someone to port over the always listening feature from the Moto X to our Nexus 6. They are both made by Motorola and should work, theoretically anyway.
dmarco said:
I also just bought the Moto hint and paired it with my N6. I sure would love for someone to port over the always listening feature from the Moto X to our Nexus 6. They are both made by Motorola and should work, theoretically anyway.
Click to expand...
Click to collapse
The "always listening" feature in the Moto X relies on specialized features designed into the hardware; I don't think they incorporated that into the Nexus 6 though.
what do you mean by the always listening feature? google now listens and responds to me, on my nexus 6, with the screen off and not plugged in. isnt that the same thing?
edit.. never mind. i just realized that its an ear piece :angel:
The standby time with it on is only like 2-3 hours. I just got it because it was a nice looking device
I wonder if we have an alternative to this device that can use our Ok Google features.
EDIT: we can use this app with any bluetooth headset it seems. https://play.google.com/store/apps/details?id=com.vibaroo.btnow
Any updates on functionality of the hint with N6?
DespairFactor said:
I wonder if we have an alternative to this device that can use our Ok Google features.
EDIT: we can use this app with any bluetooth headset it seems. https://play.google.com/store/apps/details?id=com.vibaroo.btnow
Click to expand...
Click to collapse
I installed Swipeup Utility, so that swiping up would trigger a voice search instead of launching Google Now on my N6. It turns out that by remapping the action it also alters the behavior of a bluetooth play/pause button long-press -- it now launches the Google Voice Search interface! That's awesome, since I can give commands now just like I used to do when I had an iPhone. I switched to Android several years ago, but I've always missed the ability to control basically everything by voice.
Got the hint today. It works with voice commands. You just touch the side of it while in your ear and talk.
Pretty cool but I want a better fit. Not sure if I want to keep it or not.
Hi!
I've extensively googled, reddited and searched on XDA, but haven't found an answer.
Are there ROMs supporting the "voice anywhere"-feature (the sound processor of the Moto X) to be activated even with an activated lockscreen/handsfree?
I've setup my room with Philips Hue Lights and various interactions with other devices via tasker and all is controlled via the "Moto Voice/Auto Voice" feature.
I'm unrooted yet but would like to switch to a custom rom now, but haven't found anything conclusive whether the devs were able to implement the always-listening function.
Alas I think I can say for sure it doesn't exist ..there's one for the 1st gen so maybe there is hope
The ones for 2013 are only modified stock not aosp. Far as I know the moto specific features like touch less controls and active display or whatever they call them now are not open source this you will not find them on anything but stock
Sent from my XT1053 using Tapatalk 2