Related
Does anyone know which FM Radio chip the Note has ?
My guess is a Silicon Labs dedicated FM chip, as is in the Galaxy S and S2 models. Perhaps it's accessible via /dev/fmradio.
If you call 5" a tablet, I think this Note may be the first major manufacturer tablet with officially supported FM radio. There are some esoteric Chinese tabs that support FM, and the original Dell Streak 5" has FM, but was never officially supported.
Can someone try the FM TwoO app and report if it works ? : https://market.android.com/details?id=ca.gc.crc.fmtwoo
I am also very interested to know if my FM app runs on this device, rooted or not: https://market.android.com/details?id=com.mikersmicros.fm
Thanks !
Someone has sent me debug logs (Thanks !) so I don't need any more. This device does have a Silicon Labs FM chip, and it appears that my app is working, although the emailer didn't say. He set Menu->Settings->Audio->Method to "Samsung2". It's possible "Samsung" would also work on a stock device.
Other than my curiousity about FM TwoO working, my question is answered. I'm tempted to close this thread, since I'm not here to try and promote my app, but I'll leave it open for now at least, should anyone want to discuss FM on this device, as appropriate for a Q & A forum. (?)
BTW, I get the impression that the Samsung FM app is better than other stock FM apps. It supports RDS, and I think AF, and on this device at least it seems to support recording, which I'm not sure any other FM app does.
hello
as i was already searching for any alternative FM Radio app that does not stream from the internet as there are millions and millions of streaming apps out there it was impossible for me to find them in the android market.
I liked the alternative radio app for my old Windows Mobile Device.
Now i own a Galaxy Note and tried the two apps
FM TwoO and Spirit FM Free.
It finds Radio Stations etc. But i get no sound from both apps.
I think i tried every possible sound setting.
I have Root on my Device but everything else is stock.
Is it supposed to not work on the Stock rom or can i help you with something like a debug output so your app can work on this device?
Just tell me
beowulf6 said:
hello
as i was already searching for any alternative FM Radio app that does not stream from the internet as there are millions and millions of streaming apps out there it was impossible for me to find them in the android market
Click to expand...
Click to collapse
Hi. There are almost no alternative FM apps for Android because Google refused and still refuses to provide an API. Just about every phone and chip manufacturer does FM differently and keeps their methods secret so it requires reverse engineering, which is very difficult and time consuming.
The CyanogenMod and MIUI ROMs have their own FM apps (for some devices only). FM TwoO works on some Galaxy S/S2 stock ROMs. My app Spirit tries to work on as many ROMs and chips etc. as feasible.
Now i own a Galaxy Note and tried the two apps
FM TwoO and Spirit FM Free.
It finds Radio Stations etc. But i get no sound from both apps.
I think i tried every possible sound setting.
I have Root on my Device but everything else is stock.
Is it supposed to not work on the Stock rom or can i help you with something like a debug output so your app can work on this device?
Just tell me
Click to expand...
Click to collapse
Finding stations etc. is the first obstacle. I'm happy to hear this works OK.
Sound is always the second obstacle; so many phones do this differently, even otherwise somewhat similar phones as Galaxy S and S2.
If the Audio Methods Samsung and Samsung2 don't work, we need a new Samsung3 method I guess. I think the S2 has the same issue. If I examine the stock FM app, and perhaps some logs, I should be able to determine what needs to be done.
Can you do this ? :
- Start the stock FM app, run for a few seconds, then stop it.
- Start my app, then send me logs with Menu->Help->EM Logs. In the email text please put "Galaxy Note" before pressing Send.
BTW, the stock S2/Note FM app seems pretty good, so I don't think you are missing too much from alternative apps at this time.
Also, I think my app may "work", more or less, if you start it while the stock app is running. I think the apps can co-exist simultaneously, but there are probably a few issues.
hello and thanks for your response.
You are right. The stock radio app is a lot better then the stock radio app on my windows mobile phone was. But still i dont like for example the really short textfield where the RDS text is written when the phone is in portait mode because most of the text is missing. It is better in landscape mode.
And of course alternatives are always good.
Your app works good when i keep the original radio app running in the background. (but i think the reception quality seems to be a bit worse with your app even on the same frequence. But i should test this more)
But it crashes as soon as i press the headphone/speaker button. Only a restart helps then to get rid of the stock radio-app and to get the radio working again.
i have send you a log file. hope it helps and keep up your work.
From my thread here: http://forum.xda-developers.com/showpost.php?p=21233829&postcount=2043
For Samsung Galaxy S, S2, Note, S3 etc:
Very experimental support for stock and stock derived ROMs with the Samsung Proprietary API. Works OK on my Galaxy S with Darky ROM Extreme Edition 10.2.
- Enable Settings->Debug->SA Proprietary.
- Restart the app.
http://www.mediafire.com/file/a12sm7m13smbjub/Spirit_FM_Radio_v120110.apk
- The Audio->Method is best set to the default of CyanogenMod, but might also work on Samsung, or even None or GalaxyS ALSA as a last resort.
Next release I'll re-enable the recording code and I think it will work on the Note, but might also work on Galaxy S/S2 devices.
If it works or not, please send me a log, best with SU/root:
Select Menu->Help-EM Logs, wait a few seconds, enter "Note" in the email text and press send.
I wish I could afford one of these Notes...
New release posted here: http://forum.xda-developers.com/showpost.php?p=21353990&postcount=2057
Jan 13: http://www.mediafire.com/file/52jo7vwy63576da/Spirit_FM_Radio_v120113.apk
Another shot at Samsung Proprietary support for Galaxy S2 / Note class devices, in addition to Galaxy S devices w/ FM.
As before, enable Settings-Debug->SA Proprietary and restart. SU/Root should not be needed.
Regards,
Mike.
At least one person reports this working on a a Galaxy S2. Please let me know, positive or negative.
I could REALLY use some help testing my FM app on a Note or S2 with a stock or stock derived ROM on which the stock FM app works.
I can't afford one, US/Canada versions have no FM anyway, and Samsung's Remote Test Lab seems just about useless.
The Remote Note I tried started the Feb 26 Market version of my app in the Proprietary FM API mode OK, so I think it's close to working, but that API requires an earphone/antenna plugged in, and the test device doesn't have that. And I can't get the debug logs or shell access either.
There's a Feb 28 version linked here: http://forum.xda-developers.com/showpost.php?p=23059662&postcount=2357
For a few weeks now, my app works on my Galaxy S with stock derived Darky ROMs using the Samsung API, and un-rooted.
Thanks !
Hey i just installed Spirit UI on galaxy s2 i9100G
am running on Rom jellyBam
app opens fine , i selected S2 dig. all i hear is noise
i live in egypt its ont on reg list
what should i do ?
mikereidis said:
I could REALLY use some help testing my FM app on a Note or S2 with a stock or stock derived ROM on which the stock FM app works.
I can't afford one, US/Canada versions have no FM anyway, and Samsung's Remote Test Lab seems just about useless.
The Remote Note I tried started the Feb 26 Market version of my app in the Proprietary FM API mode OK, so I think it's close to working, but that API requires an earphone/antenna plugged in, and the test device doesn't have that. And I can't get the debug logs or shell access either.
There's a Feb 28 version linked here: http://forum.xda-developers.com/showpost.php?p=23059662&postcount=2357
For a few weeks now, my app works on my Galaxy S with stock derived Darky ROMs using the Samsung API, and un-rooted.
Thanks !
Click to expand...
Click to collapse
I just downloaded. Will report soon.
Sent from my revived Galaxy Note
The first results are positive. I just listened to fm radio for about 15 minutes. It works through headphones and the speaker. But as far as I can tell the.reception seems to be somewhat worse than with the stock fm radio.
Phone is a N-7000 with stock ICS , rooted, PhilZ kernel. Are there any specific tests I should conduct?
Sent from my revived Galaxy Note
Mikereidis's post has almost one year, looking at the Spirit FM thread OT, Galaxy Note is supported since (at least) november afaik.
Hitch3ns said:
Hey i just installed Spirit UI on galaxy s2 i9100G
am running on Rom jellyBam
app opens fine , i selected S2 dig. all i hear is noise
i live in egypt its ont on reg list
what should i do ?
Click to expand...
Click to collapse
9100g is off topic here.
If it's the Unlocked version and you're a customer, then email me or post on the Q&A thread in my sig for info.
If it's the Unlocked version and you're NOT a customer, then please go away, I don't help pirates.
This thread is ancient. I've had a Note for at least 7-8 months now and it's fully supported, and will be supported by the coming Spirit2.
Please see my main thread: http://forum.xda-developers.com/showthread.php?p=13379669
I will now close this thread, thanks...
I have been looking around and I have found a few other phones being able to connect to the samsung galaxy gear, but there hasn't been a complete list of phones or even links to forums to help get it to work, figured I would start a thread.
Also anyone know if the LG Optimus G Pro is capable of connecting?
Getting phones to connect with the gear is one thing. I managed to connect my gear to my nexus 5 but without gear manager there isn't much functionality.
Sent from my Nexus 5 using Xparent Cyan Tapatalk 2
andiathsen
I dont think it'll be possible as of now
I'm using GG on my Pantech IM-A890K.
Gear Manager crashes whenever I touch "Settings" so I cannot really get notifications on my gear. Plus, native Weather / Media Control / S-voice do not work either. Except them, it works well; I can send/receive text (using TabletTalk), take a photo with native transfer service and use 3rd party app for remote control (Media Remote).
The only problem is that you still need a Samsung phone to initially get the gear ready for another non-Samsung phone. Take a look at this:
http://forum.xda-developers.com/showthread.php?t=2517364
[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
Anybody know if NON-SAMSUNG Roms can support the vr gear and Oculus? Any rom in particular? Thanks very much.
I cannot even get it to work on me S7 active but then im sure they have actually properly blocked/filtered in some way, as when inserting there is NO activity atall on logcat
where there seem to be on other phones ive tried ! (HTC etc but just lacks the software etc)
but there is this thread
https://forum.xda-developers.com/android/software/mod-samsung-gear-vr-devices-t3588601
where it has all the apps to trial ..
if your ok with using adb, and locat then go for it
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...