Direct Stylus launcher - Shield Tablet Themes and Apps

Is there any way to pull out direct stylus launcher and gamepad mapper from stock firmeware and past it in any custome firmeware?

I'm not quite sure what you mean by this, but I'd imagine you'd find the APK for this in /system/app. The firmware itself is proprietary so don't expect anything there... I wouldn't expect this capability to work with anything besides the Shield. You may be able to get the APK working with Note devices, but outside of that, you're on your own.

I have used the APK for Direct Stylus. I'm trying to sort out how to get the stylus removal trigger.

Related

Bad Digitizer - Turning Phone into PDA

Note: I'm still working on this, and this guide may miss a few things/be incomplete. I'll subscribe to this thread but if I don't reply you can PM me.
I had a Droid 3 but the ribbon cable developed a nice hearty tear. I haven't taken the money to buy a new one to put it together, and since my wife's Droid 3 has a busted glass screen but everything else works, she'll probably assemble it herself. So that left me phoneless. To save a buck, I got a cheap wireless plan locally ($19.99 unlimited talk/text), but I am on a dumb phone. I really only wanted a MP3 player and the ability to surf the web casually without getting on the computer.
The biggest problem is that Android is too dependent on touch interface, which I didn't have due to the infamous bad digitizer ghost issues. So that left me a little irritated, since it was sitting in my drawer and collecting dust. So after much research, tweaking, and playing, here is what I got so far:
1) Download your ROM of your choice. I wanted Jellybean since we had it and I think ICS/JB look prettier than GB anyway. So I chose CM10.
2) The biggest problem will be the lack of touch input. This causes three problems: setting up the phone, using the back/home/menu/search buttons, and unlocking the screen. I got past this by first using a data cable and connecting via ADB. I can't find the app since I'm at work but it's on Google Groups and a bit of searching should help you find it. If you scroll down a bit someone updated it for JB. You just need Java and ADB.
3) The next problem was the keys. In /system/usr/keylayout/sholes-keypad.kl edit this file (adb pull /system/usr/keylayout/sholes-keypad.kl is your friend then adb push). Remap key 100 (right alt) to home wake_dropped, key 54 (right shift) to back wake_dropped, and 139 to menu wake_dropped (menu key don't work on JB on keyboard until this).
4) Install v6 Supercharger (easy to find and plenty of guides so I'm not going to hash that out). In there is a section of Bulletproof apps. Download from the Play Store the app Argus Touch Blocker and add it to the Bulletproof list. Then Enable the service and block the screen on any shaking.
5) The only browser that seems to work (have to use remote control over ADB to accept EULA) is Opera Classic.
If anyone else has suggestions/tips I'm open as well.

Gear VR Development Tips & Tricks

If you've been to the official forums, you may know it's mostly questions about when updates are coming or how to fix a specific crash. There is a lot of useful information floating around, but very little open development on / for it. These are some of the tips and tricks that have either been posted and updated, forced out of Oculus, or generated through personal testing.
Adding your own oculussig file to an apk:
Obtain your device ID by connecting the Note 4 and using "adb devices"
Enter the number into the form at https://developer.oculus.com/tools/debug/
Download https://mega.co.nz/#!ssB0ALwR!dLKy0OUv7H7aGZQ1YiqXKfDgUc3fnOIghCiEFAFtt4g
Extract the zip and copy the game and signature file into the extracted folder
Run the command to repack for your computer platform (available in USAGE.txt)
Running any app as vr_dual (without Oculus Home):
Install any Gear VR app with your device signature (app can downloaded, compiled, or backed up from an official install)
Go to your device Settings -> Application manager -> Gear VR Service (usually in the "Downloaded" section but could also be in the "All" section).
Tap on "Manage storage"
Tap the "VR Service Version" number six times.
Wait for scan process to complete and you should now see the Developer Mode toggle on this screen.
You should now be able to launch your app without the headset and also dock the headset at any time without having Home launch.
Don't forget to disable developer mode to restore regular functionality after you're done playing the game and enable it again before returning.
Unity game development shortcuts:
So you need a bunch of characters and environments, but the Unity asset store is expensive and you haven't had enough experience in 3DSMax to make your own. There is another way to get tons of content both fast and cheap:
MMD4Mecanim : http://stereoarts.jp/
mmd-for-unity: https://github.com/mmd-for-unity-proj/mmd-for-unity
UnityXNA: https://github.com/mvi/UnityXNA
MMD4Mecanim and mmd-for-unity are extremely similar. The difference between them is that MMD4Mecanim adds the necessary plugins to Unity (and the platforms you build against) to allow you to use models and motions that it converts, while mmd-for-unity performs a fairly complete conversion that allows you to use the items as Unity components with minimal scripts to control some of the aspects that don't fully convert. It is personal preference which is used. When building a scene that is mostly MMD, it is probably better to use MMD4Mecanim. When attempting to mix MMD into a scene built primarily with Unity, mmd-for-unity is probably a better choice.
There is a quick overview of how mmd-for-unity works available at https://www.youtube.com/watch?v=zSC2hKaG5AA
Many developers using the Gear VR favor MMD4Mecanim because of the other plugins that have been built on top of it, such as lip sync. In terms of game performance, mmd-for-unity may have a slight advantage due to decreased overhead. It is unnoticeable, though.
4 more days
I need a noob proof setup guide lol
friedrich420 said:
4 more days
I need a noob proof setup guide lol
Click to expand...
Click to collapse
Don't worry, I am bringing over all of the stuff I put together from the Oculus forums and personal testing.
I am going to put together a small folder on Mega with tools and some samples.
Thank you so much for starting this thread. Great idea and hopefully I'll learn a lot. One question when i try and enable developer mode after the scan I get the message "you are not a developer" and it closes
sawdoctor said:
Thank you so much for starting this thread. Great idea and hopefully I'll learn a lot. One question when i try and enable developer mode after the scan I get the message "you are not a developer" and it closes
Click to expand...
Click to collapse
My professor had the same issue. He had to reboot and wait a minute, then go in and try it again. It could also be how fast the clicks are. I know he wasn't rooted and didn't do anything other than reboot. When I did it, I tapped fast.
twistedumbrella said:
My professor had the same issue. He had to reboot and wait a minute, then go in and try it again. It could also be how fast the clicks are. I know he wasn't rooted and didn't do anything other than reboot. When I did it, I tapped fast.
Click to expand...
Click to collapse
I've tried it twice but will keep trying. You obviously know which kernel i'm using but I'll keep at it
sawdoctor said:
I've tried it twice but will keep trying. You obviously know which kernel i'm using but I'll keep at it
Click to expand...
Click to collapse
You could also try clearing data for the service, then open Home, then try. When they were setting up, they clicked around but didn't really say what they did. I was in a video conference with like 7 people trying to tell one lol.
What I know for sure was it didn't require root or any additional apps.
I just found a Miku archive with some 1,000 models... Looks like it's time to make a Unity orgy. Speaking of, I should post the Miku to Unity stuff. It's a cheap way to get models and they work with the new animations.
Moved to post 2
Same issue for me, keeps telling me I'm not a developer. Tried multiple data clears and restarts.
Jstylen said:
Same issue for me, keeps telling me I'm not a developer. Tried multiple data clears and restarts.
Click to expand...
Click to collapse
That's odd. I just noticed mine was cleared out after doing the last update and I activated and enabled it just now.
Edit: I think I figured out what's happening. It works for me because I have my own game with my signature installed. It didn't take any special app for the other tests because their copy of my game had their signature and I bet they installed it between attempts.
I think you have to have any VR app that contains your own signature installed to "qualify" as a developer. I updated the instructions to include that step.
This is what I was suspecting but hoped I was wrong. I don't have the money for the gear VR right now and hoped to try some things out with an stm32fdiscovery board instead. I suppose now I'll have to compile something with my signature in it.
I didn't realize there actually was a small section for the Gear VR, so we moved over there.
There are some video conversion tips on the official forums. I haven't tried them, but I'll try to gather up what I can and add it here.
We need more positive, productive threads in this section....
I am moving all of the content from a few other threads here, since the Gear VR section has a bit of a troll problem.
One possible way to improve the range of focus / clarity when using the Gear VR:
I found this trick while trying to figure out why no adjustment to the Durovis Dive (moveable lenses) seemed as clear as I expected. The solution was to move where the headset sat on my face, despite it not feeling like that was the "intended placement"
Whether or not you use the nose piece is up to you. I honestly never took the time to compare the two foam blobs, so whichever is the default is the one I use. Most of the trick involves using the tension of the top headband, so adjust the one that wraps around your head to wherever it is tight, but still comfortable.
The next part is where it varies by user. You will want to put the headset on and adjust the focus wheel to get as clear as possible for you. After you are comfortable with the view and about to come back here and say WTF, hold the headset by both sides and move it slightly higher on your face. If the view gets clearer, adjust the top band to keep it locked in place. If there is no change, try moving it lower on your face, and again adjust as needed.
While this may not fit into a scientific explanation of pixel depth, it is a rather simple concept. By moving the headset up or down, you actually slightly alter the angle in relation to your eyes. Most games and apps are intended for a view "level to the eye" and when the headset is too low, your nose can cause it to angle slightly downward. When it is too high, the upward tilt can cause your eyes to strain a bit more.
Hopefully that can help some to solve their issue with clarity before running off to cut up or pack in any additional parts.
I have been meaning to bring over a lot of other stuff from the Oculus forums, but I got wrapped up in having them delete my account.
It appears that some people feel the need to respond to every single thread with public service announcements. Whether or not that is the reason this section has all of 5 active threads and if that led to the Oculus Gear VR section being flooded with the same nonsense cannot be proven without a massive survey. All I can say for sure is that the development sections are safe and hopefully this being a development thread means it is, as well.
Anyway, as for that stuff I was going to bring over:
Controller Mapping by Drash (https://forums.oculus.com/viewtopic.php?f=67&t=20070)
In my Unity apps I use an input layer that requires me to map from an HID to a set of button mappings, and then the rest of my app just deals with with the device-agnostic things like Left Bumper, Start Button, etc. I know a lot of developers out there do something similar, and a few of the third-party input solutions do this as well. There's only one gotcha -- developers are responsible for ensuring setting up button mappings (or profiles) for a reasonable variety of controllers.
As far as I can tell, the most-used controller on Gear VR is the Samsung EI-GP20 Gamepad that optionally comes bundled with the Gear VR. That's good news for the developers that so far aimed to support that at a minimum, but as far as I can tell is a variety of other semi-popular gamepads in use as well:
Moga Pro Power
Moga Hero
PS3 Controller
Gamestop Gamepad
Moga Pro
Steelseries Free
ipega (I think there's a few different versions, not sure which ones people actually use)
So far, I've ordered and tested 6 different controllers now for both the desktop and for Android, and this helps because most of their mappings vary, but this is clearly not a future-proof way to go. Am I going to have to keep buying every controller to find out their HID and mappings? So until I take a different approach, at the very least I would like to throw out there some of the button mappings I've picked up from testing physical controllers, and perhaps others could do the same?
----
1.
"Gamestop Gamepad" aka "Red Samurai Wireless Controller for Android Tablets". I heard this cheap gamepad mentioned several times lately. Dirt cheap. And yet it feels great in the hand and all buttons feel very usable. Solid choice. It has two modes, one that seems to send keyboard commands, and one that actually acts as a normal bluetooth gamepad (Mode G).
Here are the button mappings for Mode G.
HID: "GS gamepad"
Button 1 - Button 0
Button 2 - Button 1
Button 3 - Button 2
Button 4 - Button 3
Left Bumper - Button 4
Right Bumper - Button 5
Left Trigger - Button 6
Right Trigger - Button 7
Left Stick Button - Button 8
Right Stick Button - Button 9
Start - Button 10 (says "Enter" on the controller)
Select/Back - Button 11 (says "Escape" on the controller)
Left Stick X - Analog 0
Left Stick Y - Analog 1
Right Stick X - Analog 2
Right Stick Y - Analog 3
Dpad Left/Right - Analog 4
Dpad Up/Down - Analog 5
----
2.
Moga Pro Power - This one holds a charge that you can use to recharge your Android device. Very nice controller, quality is top-notch, but pretty expensive. Also has two modes, one that is specific to Moga games, and one where it acts as a normal gamepad (Mode B).
Here are the button mappings for Mode B:
HID: "Moga Pro 2 HID"
The button mappings are exactly the same as the Gamestop Gamepad, except that the visual labels for the Start/Select buttons actually say Start and Select, and it doesn't seem like the Select button works in HID mode. Not 100% sure about this.
----
NOTE: The Samsung Gamepad does not have triggers, nor does it have stick buttons (pushing in the thumbsticks), so you may want to keep that in mind when designing a control scheme with wide gamepad support.
Click to expand...
Click to collapse
Gear VR Input Diagrams (download includes the Samsung controller and headset button images):
https://forums.oculus.com/viewtopic.php?f=67&t=17926
Streaming video (using Kodi / XBMC)
Nevermind, this should probably be a thread...
Hi! Thanks for posting this! I followed the instructions here, successfully installed a signed apk (one that wasn't on the phone previously), then turned on dev mode as described through the tapping and switch. Nothing seemed to have changed. I then toggled dev mode on and off (via the switch) and restarted the phone several times each. However, I still get the Oculus Home launching every time I insert the phone into the Gear VR as if nothing changed. I'm on the T-mobile US ROM and device, and I don't have the 5.0 upgrade yet. No root.
Does anyone have any ideas? I want to run cardboard apps in my Gear ! Thanks!
TriOptimum said:
Hi! Thanks for posting this! I followed the instructions here, successfully installed a signed apk (one that wasn't on the phone previously), then turned on dev mode as described through the tapping and switch. Nothing seemed to have changed. I then toggled dev mode on and off (via the switch) and restarted the phone several times each. However, I still get the Oculus Home launching every time I insert the phone into the Gear VR as if nothing changed. I'm on the T-mobile US ROM and device, and I don't have the 5.0 upgrade yet. No root.
Does anyone have any ideas? I want to run cardboard apps in my Gear ! Thanks!
Click to expand...
Click to collapse
If nothing is running, it will launch home.
There is also a possibility it only works for Gear VR apps. In that case, you could just disable the whole Gear VR service temporarily.
Either way, you don't really need to quote the OP to ask. It's implied.
twistedumbrella said:
If nothing is running, it will launch home.
There is also a possibility it only works for Gear VR apps. In that case, you could just disable the whole Gear VR service temporarily.
Either way, you don't really need to quote the OP to ask. It's implied.
Click to expand...
Click to collapse
Thanks for the reply. Sorry to violate posting etiquette, I didn't realize I had quoted that entire post - I will trim it down if I can find edit (I am new to posting here, so forgive me).
I have FPSE or any other cardboard app running, and gear home still pops up over it when docked to the usb port of the gear vr. I can't freeze Gear VR service without root, which I'm looking in to as the next best option I suppose. Force stopping it doesn't seem to work either. Reports on Reddit threads indicate this works with Cardboard apps, allowing them to run without home launching, but not for me.

[Q] Does anyone know of a gamepad/remote app?

Hi,
Been googleing for a while on this one, not found anything yet.
I'm looking for an app that can emulate a gamepad for my phone.
If all it does is emulate a single screen tap that would be fine.
The thinking is that I have a plastic Google Cardboard rig that doesn't have the magnet button thing. The idea being that the watch could replace this functionality.
If it could act as an analog stick/dpad that would be a huge bonus.
If nobody knows of an app for this, any input to deving one would be helpful. I don't currently have a Tizen dev suite set up but could get one going this weekend.
I've done some remote control stuff in java before but never on android. If anyone has experience in this your help would be appreciated.
I don't want to replicate something if it already exists.

Advice before I root

Hi All,
It's been quite a few years since I last rerooted a phone - I've found I just didn't really need to with Nexus devices, but since the next Nexuses don't have wireless charging, I've decided to pick up a Note 5.
It's a good phone, I really like it so far, but there are enough things niggling me about it, I think I will root this time. If anyone can provide advice on any of the following list I'd really appreciate it!
1. I see Dr Ketan's thread on the matter (http://forum.xda-developers.com/note5/general/how-to-root-note-5-t3205073) which seems doable, and as complex as I remember. Has anyone tried one-click rooting and can comment on reliability? I'm all for just getting easy root access... For reference I have the SM-N920I. I also see "tripping Knox" a lot, but I have no idea what the means. Last person I asked said "I can't say if that is a good or bad for your specific situation" which makes me think they didn't understand my question.
2. I don't like TouchWiz. It's OK, but I much prefer stock, or, what I'm doing at the moment: Action Launcher 3. I prefer the stock dialer, and the stock quick menu (when you pull-down notification bar). Can I flash a stock ROM onto the Note 5? I mean, not stock-like like the popular MODs (Cyanogen for example) but something that is practically stock? I may end up going with something like Cyanogen, but I'd just like to know what's out there along those lines.
3. Having said that I don't like TouchWiz, and might install a new ROM, there are many things I do like about this device's interface: The SPen's overlay/menu is handy. The fact it brings up a notepad-like app if you pop the SPen out when the screen is off, one-hand mode (note: I have found an XPosed Module for this), the fingerprint scanner, the camera app, the S Planner app, the Home button shortcuts (single click->home; double-click->camera; triple-click->one handed mode) ... all things I assume I'll lose if I flash away Touch Wiz. However, perhaps I can get some (or all) of these things back? If so ... how? e.g. It looks like one-handed mode could be acheived with an XPosed module, and the home-button shortcuts with a launcher (I think Action Launcher can over ride this...)
4. Always listening Google Now. At the moment I have fingerprint scanner lockscreen security, always listening S Voice, and Google Now "from any screen." It... kinda works. But I can't see any reason why Google Now shouldn't just be always listening, and using a Trusted Voice allow me to throw voice commands at my device at any time. At the moment only S Voice is always listening... and even if I have the screen on, trusted voice doesn't seem to be able to get through the fingerprint security anyway. Ironically if I ask S Voice to launch Google Voice Search... it ploughs through in that scenario. Ultimate goal: Have Google Now always listening, and use Trusted Voice to get past the lockscreen, which would typically be secured with a fingerprint scanner.
If you can answer, or provide feedback on any of these queries, it'd be much appreciated!
dakuth said:
Hi All,
It's been quite a few years since I last rerooted a phone - I've found I just didn't really need to with Nexus devices, but since the next Nexuses don't have wireless charging, I've decided to pick up a Note 5.
It's a good phone, I really like it so far, but there are enough things niggling me about it, I think I will root this time. If anyone can provide advice on any of the following list I'd really appreciate it!
1. I see Dr Ketan's thread on the matter (http://forum.xda-developers.com/note5/general/how-to-root-note-5-t3205073) which seems doable, and as complex as I remember. Has anyone tried one-click rooting and can comment on reliability? I'm all for just getting easy root access... For reference I have the SM-N920I. I also see "tripping Knox" a lot, but I have no idea what the means. Last person I asked said "I can't say if that is a good or bad for your specific situation" which makes me think they didn't understand my question.
2. I don't like TouchWiz. It's OK, but I much prefer stock, or, what I'm doing at the moment: Action Launcher 3. I prefer the stock dialer, and the stock quick menu (when you pull-down notification bar). Can I flash a stock ROM onto the Note 5? I mean, not stock-like like the popular MODs (Cyanogen for example) but something that is practically stock? I may end up going with something like Cyanogen, but I'd just like to know what's out there along those lines.
3. Having said that I don't like TouchWiz, and might install a new ROM, there are many things I do like about this device's interface: The SPen's overlay/menu is handy. The fact it brings up a notepad-like app if you pop the SPen out when the screen is off, one-hand mode (note: I have found an XPosed Module for this), the fingerprint scanner, the camera app, the S Planner app, the Home button shortcuts (single click->home; double-click->camera; triple-click->one handed mode) ... all things I assume I'll lose if I flash away Touch Wiz. However, perhaps I can get some (or all) of these things back? If so ... how? e.g. It looks like one-handed mode could be acheived with an XPosed module, and the home-button shortcuts with a launcher (I think Action Launcher can over ride this...)
4. Always listening Google Now. At the moment I have fingerprint scanner lockscreen security, always listening S Voice, and Google Now "from any screen." It... kinda works. But I can't see any reason why Google Now shouldn't just be always listening, and using a Trusted Voice allow me to throw voice commands at my device at any time. At the moment only S Voice is always listening... and even if I have the screen on, trusted voice doesn't seem to be able to get through the fingerprint security anyway. Ironically if I ask S Voice to launch Google Voice Search... it ploughs through in that scenario. Ultimate goal: Have Google Now always listening, and use Trusted Voice to get past the lockscreen, which would typically be secured with a fingerprint scanner.
If you can answer, or provide feedback on any of these queries, it'd be much appreciated!
Click to expand...
Click to collapse
1. Rooting is easy on the 920I. Just follow the instructions. As for tripping Knox, Knox is a security system which you may or may not use. Many don't but some people and enterprises do. Knox is also required for Samsung Pay which is currently rolling out. As soon as you root Knox will be disabled and a flag will be tripped which cannot be reset - thus once you root, that is that. Whoever said that they don't know whether you use Knox was absolutely right. The most obvious case is that if you want to use Samsung Pay, don't root.
Two things: when you root, make sure you backup your EFS. Also have a look around for which kernel you are going to install. I use arter 7.0 at the moment.
2 and 3. Experiment with other launchers and see what you like. I don't like touchwiz but I do like the spen integration. Same for ROMs - have a good look around before you root to see what you like. I prefer Dr ketan L3 but it's all personal choice.

Note 4 and Gear VR controller

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...

Categories

Resources