Related
[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 hear the Gear S is now totally independent, built in wifi, 4g, etc... Anyways, This thing is a bluetooth device, I'm assuming it's got a built in generic bluetooth dongle and the tizen OS itself handles protocols such as a2dp for headphones, and communication thru their strange SAP protocol. (Samsung Accessory Protocol)
Is it at all possible to achieve internet access for apps with any APIs for the new Gear S? I figured my phone (actual samsung) along with other manufacturers have a Tethering option. I was hoping I could turn on my bluetooth tethering and get actual internet connectivity on the Gear 2 Neo, and start developing real web-oriented apps for the watch without some flaky form of polling using a background process on the phone itself to relay content to the gear 2 neo.
Once I heard you could code for this in as close to HTML/CSS/JavaScript as possible (there are some things that just don't translate to be as simple as it is in any browser) I was hooked, rushed out and bought one, but now I'm disappointed at my purchase realizing there is no way to achieve any content from the web without a back-end running on the phone, and I never liked java, nor do I care to learn it.
Could it be already possible just no way to reference the internet thru the js methods available in the Tizen SDK? This is a form of linux, what about possibly getting perl or node.js in there and maybe making your own interface to sockets? It'd be so awesome to actually have perl on a gear 2 neo.
found thread
I searched before posting this, couldn't find nothing, and an unrelated google search about gear 2 neo ringtones brought up a link... go figure. Anybody else looking can also see the solution I stumbled upon here
http://forum.xda-developers.com/gear-2/general/guide-internet-connection-gear2-5-steps-t2956328/post57140526#post57140526
while it's not perfect, it's a giant leap in the right direction I look forward to more in this thread!
Hi, to begin if this is not the subject my sincere apologies, as you will see, I am new.
I have two appointments.
1- What would happen if I put the firmware of the Samsung J120M in my J110M. I've searched everywhere for a rom for the J110M and I do not find it, it contains Android 5.1.1 lollipop (But **** haha, it's ugly) the J120M also contains 5.1.1 lollipop (very nice, updated apps, very smart.).
Like every member of the community (I suppose) I am very obsessive. I like that my android is extremely tidy and obviously I like it. So for this first point I want to know if at least the worst thing that could happen is that you have to install the J110M firmware via download mode. Because if I ***** I ****ed.
Now 2 !.
As I never found a rom for this cel, it took me to customize it on my own. I replaced the samsung browser (for a more recent version) I replaced the touchwiz launcher (for an s7 launcher with icons of this one) obviously replacing the apk of the system. I saw a subject right here, where a developer posted s6 apps for any samsung device with android 5.1 lollipop with touchwiz interfaces. But none served me !!. I replaced the default apk (obviously copying) from the gallery, added the samsung player, also from My files, etc. And each one when restarting the cell phone threw the error "Gallery has stopped" etc etc. I deleted the data and everything, even reset the cel several times and it did not work. So if someone tells me how I could make these applications compatible for this cell phone (j110m) I would be very grateful.
Hi,
I was wondering if anyone has any experience with the new Gear VR controller and a Note 4 ? I understand I may have to root my SM-N910C in order to temporarily modify the model version [to a Note 5] in order to pair/calibrate controller ?
If I have to choose this route [unless anyone knows a work around] I am having trouble finding recommended method on FW build MMB29K.N910CXXS2DQF2
Any help appreciated !
Solution !
I did find some info on this so here's how you fix this problem WITHOUT root.
Go find
com.samsung.android.app.vr.input.service_1.0.44-44_minAP121(nodpi)_apkmirror.com.apk
or just look for Samsung gear vr input apk
Side load apk, you are then able to pair and calibrate ! This loop problem is ether intentional or a genuine bug.
Tested for a number of hours and works fine !
I would have imagined that the Gear VR Controlller would have worked perfectly fine with the Note 4. As long as you have bluetooth enabled.
Hello friends,
I tried the apk : com.samsung.android.app.vr.input.service_1.0.44-44_minAPI21(nodpi)_apkmirror.com
however my samsung note 4 (not rooted) is able to the gear vr controller, it can't appair to it.
I tried several time after rebooting my phone, I'm in the same situation
Any idea ?
I think they have dropped the Gear VR Controller Support on the Note 4 completely. Now the "Controller" menu is completely missing from the Oculus VR settings "More" menu. I tried installing older versions of the input service "1.0.44" but that didn't bring the menu back.
Someone any idea how to fix this?
Theoretically the controller is compatible with the Note 4 so it is probably a commercial step why they removed it.
PS: I didn't try rooting my phone to change the ID to see if the "Controller" menu reappears.
I am rooted on a Sprint Note 4 (SM-N910P). A few months ago, I got it to work by doing the process https://www.reddit.com/r/GearVR/comments/67z5sd/will_the_controller_work_with_note_4/ It worked, but then one day the option for the controller was gone again and the controller would not work. Oculus app updates may have done it.
I just went in and changed back build.prop so that ro.product.model=SM-G935P so that it thinks it's a Sprint Galaxy S7 Edge. I rebooted, and now the Controller option in the menu is back. That is all I did. I'm not sure if I'll have any negative effects just leaving it as SM-G935P, but I'm going to try.
I tested VR and controller functionality after leaving it as SM-G935P, everything seems to work just fine.
preslin said:
I am rooted on a Sprint Note 4 (SM-N910P). A few months ago, I got it to work by doing the process https://www.reddit.com/r/GearVR/comments/67z5sd/will_the_controller_work_with_note_4/ It worked, but then one day the option for the controller was gone again and the controller would not work. Oculus app updates may have done it.
I just went in and changed by build.prop so that ro.product.model=SM-G935P so that it thinks it's a Sprint Galaxy S7 Edge. I rebooted, and now the Controller option in the menu is back. That is all I did. I'm not sure if I'll have any negative effects just leaving it as SM-G935P, but I'm going to try.
Click to expand...
Click to collapse
preslin said:
I tested VR and controller functionality after leaving it as SM-G935P, everything seems to work just fine.
Click to expand...
Click to collapse
Does charging work with this mod?
Thanks
nasinec said:
Does charging work with this mod?
Thanks
Click to expand...
Click to collapse
I don't charge my phone while it's in VR, but I have no reason to think it won't work.
preslin said:
I don't charge my phone while it's in VR, but I have no reason to think it won't work.
Click to expand...
Click to collapse
Note 4 did not charge in previous editions of Gear Vr.
Hi everyone! So glad I can contribute to XDA!
1st: size is key, sm325 note8 Gear VR is the only one I was able to use with space to fit the size of Note 4 & Note Edge (remember that one?).
Second, you want to use Nova launcher activities (google it) and something like Aptoide to download the following:
Oculus VR apks (Home, App framework, etc.) as many as possible
More important still : download apps of Samsung's "Gear VR" service, setup wizard, system, input service, etc.
No need to root.
Once downloaded, create activities in Nova launcher widget on touchwiz or direct on Nova or custom launcher. Create them esp for Input Service to pair that VR controller that's the best $30/30€ you'd ever spend...
Better news still, all this is DPI free so if like me you are using a low setting for extra space on your Note 4 screen esp with the docking station HDMI that gave us D'ex before Dex, it does not screw with your stock VR apps.
Hi roniboian
Could explain more precisely your trick?
it look excellent but don't understand how to get GEAR VR controller connected to note. 4
roniboian said:
Hi everyone! So glad I can contribute to XDA!
1st: size is key, sm325 note8 Gear VR is the only one I was able to use with space to fit the size of Note 4 & Note Edge (remember that one?).
Second, you want to use Nova launcher activities (google it) and something like Aptoide to download the following:
Oculus VR apks (Home, App framework, etc.) as many as possible
More important still : download apps of Samsung's "Gear VR" service, setup wizard, system, input service, etc.
No need to root.
Once downloaded, create activities in Nova launcher widget on touchwiz or direct on Nova or custom launcher. Create them esp for Input Service to pair that VR controller that's the best $30/30€ you'd ever spend...
Better news still, all this is DPI free so if like me you are using a low setting for extra space on your Note 4 screen esp with the docking station HDMI that gave us D'ex before Dex, it does not screw with your stock VR apps.
Click to expand...
Click to collapse
Hello, i joined just to ask you how to do what you describe above! You said you would be happy to contribute, that would be really great,.. What you have written is very vague, at XDA the best people tend to share complete info, Could you give actual steps by steps?
I can find any of the APKs at 'APKMirror' site, they have the gear vr service, oculus home, everything, for Many many back dates.
(but; any advice on which dates or which actual files? Ideally the most recent update where the motion controller still worked..)
Please explain this 'create activities in NOVA launcher widget' method. (I am hoping it means, the apk's will install without the 'automatic wifi method' which invariably gives the newest files...)
What do you mean by DPI free? Please explain the process.
Thanks for the hope!
Yes, please explain in more detail. I am somewhat familiar with these sort of things and moderately comfortable messing around with stuff. I currently don't have a PC or easy access to one so I'm sure rooting my Note 4 is out of the question. That's why I've restarted my seach for a workaround to get the gear vr controller working with my Note 4 and corresponding headset. When I bought the controller a few months ago, I couldn't find anything reliable without root. This was the first place I came to so my hope is that this thread was abandoned b/c some of your brilliant minds have come up simple and successful patch. I have my fingers crossed, I'm getting kinda tired of using my steel series controller. Thanks everyone
Hi I can help. I started this thread, but XDA Password recovery can takes hours, even days or infinity now, since the link they send for password recovery, opens a random page, that has nothing to do with password recovery... I have never once gotten any help here with anything, ever, so I don't care enough to bother logging in anymore... BUT:
I have the Motion Controller working on my Note 4 in a limited fashion. You need to go to APKMirror (just Google 'download Gear VR Apk'... As you should have to begin with.) Download all the early APKs, one in each category, uninstall your gear software, and such, reinstall each apk (about 8 I believe) until it works. I remember centering around the earliest 'APRIL' Updates. You can run a LOT of apps with the controller, but not any new or newer apps. Im at: NextWorldVR (@) gmail.com if you need more help. The guy above will never answer you, this place is a bit of an elitist joke, I just figure out everything on my own now rather than bolster their tiny weaning toddler egos...
Hi,
I've got 2 original Samsung Gear. One with Tizen and one with a rooted Null Rom 23 on.
But I can't make any of them work with my phone (Android 7).
Is there any way to make it work? (I mean, I can connect them via bluetooth... But that doesn't help me really use them as I was doing with my old Samsung phone ).
Thanks!!
Anyone ? Any pointers to how to try to make this watch work on a non-Samsung Android 7 phone would be really appreciated!!!
Use it with null 23 Rom, not flashing any Samsung related app (except pedometer, clock, timer and touchwiz settings). In this way you avoid completely the Samsung setup wizard. Do not flash gapps and limit the two cores frequency to 1ghz, use only Google voice.
Pair the watch with any phone normally from settings (even more than one)
Then use Watch Droid Phone 9 (not 10 because of Google new policy) and enjoy your new smartwatch with vocal answers to social apps, calls and multimedia controller
With Tizen no (or very very... difficult). Otherwise, easy with flashing Android Wear ROM (see post here)
EDIT : Sorry, just Gear 2 not Gear 1