Related
As everyone knows, Swype isn't really that open source anymore and you have to go through a lot to get your hands on it (if you don't know what your doing) and it usually involves piracy.
However, there is a alternative!! (but not free )
It's called Ultra Keyboard and its available in the app store
I'll get some screenshots of it and the swype feature in action.
However, this makes your camera useless and if you try to open it, it will restart your phone. Why? Because it also has another feature which allows you to use the camera the view your surroundings while you type. Would be cool and all besides that fact that it doesn't work!!
mikurej95 said:
As everyone knows, Swype isn't really that open source anymore and you have to go through a lot to get your hands on it (if you don't know what your doing) and it usually involves piracy.
However, there is a alternative!! (but not free )
It's called Ultra Keyboard and its available in the app store
I'll get some screenshots of it and the swype feature in action.
However, this makes your camera useless and if you try to open it, it will restart your phone. Why? Because it also has another feature which allows you to use the camera the view your surroundings while you type. Would be cool and all besides that fact that it doesn't work!!
Click to expand...
Click to collapse
There's also Slide it. I even think that it's bit faster at finding words than swype.
I attach the patches I have created and that should be applied to stock AOSP 2.3.4_r1.
The patches enable card emulation mode on Nexus S (original credit goes to Nemik, who posted the first working patches on Android Developers Group). They are basically a rewrite of my own patches but allowing also SWP mode for UICC sporting a SE.
I modified the Settings application to add a pair of options related to NFC:
Card Emulation Only Mode. This disables reader function. Card emulation mode is always enabled. Be careful because P2P mode may not work (not tested)
Use External Secure Element if Available. This makes the phone to use the SE of the UICC if available instead of embedded one.
To test card emulation, just approach your Nexus S to a Mifare compatible card reader. Embedded element (SmartMX) has a 4K Mifare card with stock keys (all FF).
As a bonus I also modified Bluetooth settings so discoverable option makes phone discoverable without stupid time limits.
Important BUGFIX Update 01/05/2012
The patch was not well created, since NFC was not enabled in building process. You could see NFC Settings but options were not enabled. The corrected version has date of today.
I would love to test this, but it's a catch 22 situation for me... AFAIK the only place in the UK that accepts contactless payment is McDonalds, and the only time I go to McDonalds is after a night of heavy drinking, so with a hangover there is no chance that I would be able to operate my phone.
Sent from the future to put right what once went wrong.
i think i don't really get it...
with this patch i can "store" a NFC card at my phone and use the phone instead of the card??
eiabea said:
i think i don't really get it...
with this patch i can "store" a NFC card at my phone and use the phone instead of the card??
Click to expand...
Click to collapse
Yes and No. With this patch you can enable card emulation mode for experimental purposes. With an external reader you can read/write the Mifare memory area inside the embedded secure element. If you happen to use Mifare classic for a purpose (i.e. ticketing transport), you know the map, and you know the keys you can store a clone of the card you are using on your phone by means of a external reader.
You could load smartcard cardlets (to implement advanced smart card applications such as paywave/paypass, etc.) if you knew the smartcard access keys, but unfortunatelly they are only known by google.
This hack is only intentended for experimentation/research. Beware, do not use it if you do not know what card emulation is or what it is useful for.
This is great stuff. I've been waiting for something like this for a while. are you in the UK? If so do you have any idea about the oyster card? I have a visa paywave card as well. It is it possible to read these cards from the nexus s and then emulate them? Also, can the nfc chip in the nexus read 125khz cards? I know that's out of the nfc standard range, just curious. sorry for the number of questions, but if we could get this to work it would be the best use of this underused nfc chip! I'm on 2.3.6 though, I heard they enabled access to the secure element on this version.
Sent from my Nexus S using XDA App
grippa said:
This is great stuff. I've been waiting for something like this for a while. are you in the UK? If so do you have any idea about the oyster card? I have a visa paywave card as well. It is it possible to read these cards from the nexus s and then emulate them? Also, can the nfc chip in the nexus read 125khz cards? I know that's out of the nfc standard range, just curious. sorry for the number of questions, but if we could get this to work it would be the best use of this underused nfc chip! I'm on 2.3.6 though, I heard they enabled access to the secure element on this version.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Well, answering to your questions ... No I am not in UK, but I have heard about Oyster card. In fact I work developing ticketing systems. It used to be a plain Mifare Classic 1K but Wikipeda states it has been replaced by Mifare DESfire. The embedded secure element of the Nexus S sports a Mifare 4K, which is backwards compatible with Mifare Classic 1K. Mifare DESFire is a different story. Classic Mifare Cards are memory cards divided into sectors that requiere a key authentication against each sector. Every sector has two keys, one usually configured for reading and the other one configured for writing. Real world ticketing systems usually configure different keys for every card. These keys could be derived from CSN of the card using hardware encryption modules (such as SAMs). However I have seen real systems working with prefixed keys for all the cards (which is just insane).
All that being said, you could theoretically configure the embedded Mifare 4K card to work as a plain old Oyster card, which is nowadays useless. I said theoretically because you should know the map of the key (how to write the correct values in the correct blocks) and the matching keys for your card. If you knew how to get the matching keys (read and write keys) obviously the security of the system would be broken.
You said something about reading cards. Nexus S can act as a reader and in card emulation mode. To read cards you need to know the read keys, which usually are not public either.
I do not know how Visa Paywave works, but I guess it is a command (APDU) based card. The same happens here. You wont even have access to card application to copy it to other card. In fact card applications (cardlets) can not be extracted from cards, only replaced or deleted.
Paypass can work with Google's Wallet because Visa itself installs its cardlets on the embedded element of the Nexus S surely via some kind of TSM service provided by Google (who owns the access keys to load new cardlets)
Hi everyone,
I just found thie thread on another website (don't remember which one btw)... And I'm wondering something...
Here at work, we have RFID cards for opening the door, Mifare 4k I think.
We also have the writer so we can program cards when we need one or two...
So could I use our writer on my Nexus S so I could open the door with my phone ?
remi.serriere said:
Hi everyone,
I just found thie thread on another website (don't remember which one btw)... And I'm wondering something...
Here at work, we have RFID cards for opening the door, Mifare 4k I think.
We also have the writer so we can program cards when we need one or two...
So could I use our writer on my Nexus S so I could open the door with my phone ?
Click to expand...
Click to collapse
This is what i am after, would this ever be possible?
m0rtadelo said:
I attach the patches I have created and that should be applied to stock AOSP 2.3.4_r1.
The patches enable card emulation mode on Nexus S (original credit goes to Nemik, who posted the first working patches on Android Developers Group). They are basically a rewrite of my own patches but allowing also SWP mode for UICC sporting a SE.
I modified the Settings application to add a pair of options related to NFC:
Card Emulation Only Mode. This disables reader function. Card emulation mode is always enabled. Be careful because P2P mode may not work (not tested)
Use External Secure Element if Available. This makes the phone to use the SE of the UICC if available instead of embedded one.
To test card emulation, just approach your Nexus S to a Mifare compatible card reader. Embedded element (SmartMX) has a 4K Mifare card with stock keys (all FF).
As a bonus I also modified Bluetooth settings so discoverable option makes phone discoverable without stupid time limits.
Click to expand...
Click to collapse
Guess you used the SmartMX java applet to emulate?
Is this the part where UID is generated?
Code:
/*
+ * Utility to recover UID from target infos
+ */
static phNfc_sData_t get_target_uid(phLibNfc_sRemoteDevInformation_t *psRemoteDevInfo)
{
phNfc_sData_t uid;
switch(psRemoteDevInfo->RemDevType)
{
case phNfc_eISO14443_A_PICC:
case phNfc_eISO14443_4A_PICC:
case phNfc_eISO14443_3A_PICC:
case phNfc_eMifare_PICC:
uid.buffer = psRemoteDevInfo->RemoteDevInfo.Iso14443A_Info.Uid;
uid.length = psRemoteDevInfo->RemoteDevInfo.Iso14443A_Info.UidLength;
break;
case phNfc_eISO14443_B_PICC:
case phNfc_eISO14443_4B_PICC:
uid.buffer = psRemoteDevInfo->RemoteDevInfo.Iso14443B_Info.AtqB.AtqResInfo.Pupi;
uid.length = sizeof(psRemoteDevInfo->RemoteDevInfo.Iso14443B_Info.AtqB.AtqResInfo.Pupi);
break;
case phNfc_eFelica_PICC:
uid.buffer = psRemoteDevInfo->RemoteDevInfo.Felica_Info.IDm;
uid.length = psRemoteDevInfo->RemoteDevInfo.Felica_Info.IDmLength;
break;
case phNfc_eJewel_PICC:
uid.buffer = psRemoteDevInfo->RemoteDevInfo.Jewel_Info.Uid;
uid.length = psRemoteDevInfo->RemoteDevInfo.Jewel_Info.UidLength;
break;
case phNfc_eISO15693_PICC:
uid.buffer = psRemoteDevInfo->RemoteDevInfo.Iso15693_Info.Uid;
uid.length = psRemoteDevInfo->RemoteDevInfo.Iso15693_Info.UidLength;
break;
case phNfc_eNfcIP1_Target:
case phNfc_eNfcIP1_Initiator:
uid.buffer = psRemoteDevInfo->RemoteDevInfo.NfcIP_Info.NFCID;
uid.length = psRemoteDevInfo->RemoteDevInfo.NfcIP_Info.NFCID_Length;
break;
default:
uid.buffer = NULL;
uid.length = 0;
break;
}
return uid;
}
Is it possible to tell the app to emulate UID i.e. AA BB CC DD?
Kind regards
Jonas
I can see the NFC settings changed in teh application.Thanks.
See here for the steps for applying patches and buiding the Android and Flashign it on Nexus S.All credit goes to the patch writer.
Rgds,
Softy
anyone can give a link to the firmware for Nexus S compiled with this NFC-patch ?
please !
This is a real hacker method. I went though the patches. The main modifications are in the NFCService.java file.
Side question:
Why does the ID of the eSE (embedded Secure Element) change all the time with an unhacked phone?
With this hack, the Id of my eSE is 4246981811.
In the source code however, it appears that the ID is hard coded to 11259375. I used the patched provided here. Why do I get a different ID?
can we use on another phones
msm8260 etc. ???
anyone succed doing this ?
TNIxeye said:
anyone succed doing this ?
Click to expand...
Click to collapse
Would be nice to get this working on the 4.0.4...
im using ICS my NFC doesnt work...someone pls help me...pls pls pls pls
can this work with sony xperia s ICS? or any one can port this to xperia S?
shailentj said:
Why does the ID of the eSE (embedded Secure Element) change all the time with an unhacked phone?
Click to expand...
Click to collapse
I think thats for Privacy reasons, but don't know exactly. German identy card for example has every time another ID to make it impossible to track a user.
SamsungPisser said:
I think thats for Privacy reasons, but don't know exactly. German identy card for example has every time another ID to make it impossible to track a user.
Click to expand...
Click to collapse
Thats a security feature of SmartMX - Random UID.
Can be set on "normal" SmartMX to either fixed UID or random UID.
sooo...this has to be run on Ginger Bread? Any chance of even ICS?
I thought I'd order some smart tags to see what the first decent NFC apication I've come across can do.
Initially I was pretty impressed. Turn on NFC, wave the phone near a tag and Smart Connect pops up asking what you want the tag to trigger. Each event in Smart Connect has begin and end actions - begin is triggered by NFC detecting a tag and end is handled on the phone when you stop the event (there is Smart Connect item in the notification bar to make this really easy.)
So far so good, it's all really easy and slick to use.
The only problem is that the NFC detection only currently works if the phone screen is unlocked and on. This means if I want to leave a tag in the car to switch on my BT and start my navigation app, then I can't just get in and swipe the phone near it... I've got to unlock the phone first! Niggle!
For a first outing, this is still good so hopefully Sony will offer the ability to use tags without unlocking the phone at some point in the future.
Just thought I'd share in case anyone else is thinking of making a purchase.
On sgs3 it was the same as far as I remember and some custom roms had option in settings to work while screen off. Hopefully, for you, it will be ported/done for Xperia T also (aokp had that option and some other cm10 derivates)
Sent from my LT30p
If you want to take better advantage of NFC's potential, I'd recommend buying some generic tags and downloading NFC Task Launcher from the Play store. Generic tags are cheaper, has higher capacity, and NFC Task Launcher can do a lot more than Smart Connect. Combine it with Tasker and you can do some seriously cool ****.
yesyesimanoob said:
If you want to take better advantage of NFC's potential, I'd recommend buying some generic tags and downloading NFC Task Launcher from the Play store. Generic tags are cheaper, has higher capacity, and NFC Task Launcher can do a lot more than Smart Connect. Combine it with Tasker and you can do some seriously cool ****.
Click to expand...
Click to collapse
Where can you get generic tags, any link maybe?
If my phone could trigger actions without being "under my actual monitoring" (On and unlocked) in reaction to NFC tags, I 'd consider that quite unsafe.
At least, there should be some kind of restriction system, like : you can trigger actions only on this particular list of "declared secure by the user" tags.
Maybe the software Yesyesimanoob (what a funny user name, sorry) speaks of can do it, i don't know.
Nickola
yesyesimanoob said:
If you want to take better advantage of NFC's potential, I'd recommend buying some generic tags and downloading NFC Task Launcher from the Play store. Generic tags are cheaper, has higher capacity, and NFC Task Launcher can do a lot more than Smart Connect. Combine it with Tasker and you can do some seriously cool ****.
Click to expand...
Click to collapse
Had a bit of a scare when my mate who has an SGS3 swiped his phone near one of my tags and his NFC task launcher detected and reprogrammed my tag so I couldn't use it.
Luckily Smart Tag Maker on the Play Store can fix them but it's a bit crap if just anyone can reprogramme them.
vid200 said:
Where can you get generic tags, any link maybe?
Click to expand...
Click to collapse
I get mine from tagsfordroid.com (US). I don't really know international sources well enough to suggest a reliable one, sorry, but the tagsfordroid.com ones are just rebranded "Mifare Classic" tags, so you might want to look for that. They have about 700+ bytes of usable capacity, so you can put more on a single tag than the Sony ones (48 bytes).
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
emuX said:
Had a bit of a scare when my mate who has an SGS3 swiped his phone near one of my tags and his NFC task launcher detected and reprogrammed my tag so I couldn't use it.
Luckily Smart Tag Maker on the Play Store can fix them but it's a bit crap if just anyone can reprogramme them.
Click to expand...
Click to collapse
Not sure about the Smart Tags as I don't have one, but NFC Task Launcher can make a generic tag read-only, so once you've programmed it, no one (including yourself) can reprogram it ever again.
---------- Post added at 04:31 PM ---------- Previous post was at 04:27 PM ----------
nickola said:
If my phone could trigger actions without being "under my actual monitoring" (On and unlocked) in reaction to NFC tags, I 'd consider that quite unsafe.
At least, there should be some kind of restriction system, like : you can trigger actions only on this particular list of "declared secure by the user" tags.
Maybe the software Yesyesimanoob (what a funny user name, sorry) speaks of can do it, i don't know.
Nickola
Click to expand...
Click to collapse
You have to be rooted to get NFC to work while the screen is off, and that's only available for certain devices right now, with a custom APK. Maybe it will come to the Xperia T eventually, who knows.
nickola said:
If my phone could trigger actions without being "under my actual monitoring" (On and unlocked) in reaction to NFC tags, I 'd consider that quite unsafe.
Click to expand...
Click to collapse
Agreed that blanket access for all tags would be bad so some sort of control would be required (e.g. You can enable certain tags to work without unlocking the phone - such as the Blue (car) tag.)
It is really cool but I have no idea how can it be used to make me convenient because before you scan the nfc tag, you should open your screen and unlock it.
niuzhd said:
It is really cool but I have no idea how can it be used to make me convenient because before you scan the nfc tag, you should open your screen and unlock it.
Click to expand...
Click to collapse
Works best when you want to trigger multiple actions. For example, when I get into my car, I swipe a tag to activate in-car mode, which involves:
- Maximize media volume
- Lower notification volume
- Activate gesture media controls (via a Tasker profile, or alternatively you can try the app Wave Control for this)
- Activate SMS reader/auto-responder
Swipe the same tag again before exiting car to disable car mode.
yesyesimanoob said:
Works best when you want to trigger multiple actions. For example, when I get into my car, I swipe a tag to activate in-car mode, which involves:
- Maximize media volume
- Lower notification volume
- Activate gesture media controls (via a Tasker profile, or alternatively you can try the app Wave Control for this)
- Activate SMS reader/auto-responder
Swipe the same tag again before exiting car to disable car mode.
Click to expand...
Click to collapse
Are you using Smart Connect or NFC task launcher? (My smart connect doesn't switch the options off when you swipe a 2nd time.)
emuX said:
Are you using Smart Connect or NFC task launcher? (My smart connect doesn't switch the options off when you swipe a 2nd time.)
Click to expand...
Click to collapse
NFC Task Launcher. It has an option to create a "switch", which will alternate between two series of tasks each time you swipe it. Of course this means you're writing more data to the tag, which the Sony Smart Tags are probably too small to contain and hence Smart Connect doesn't provide the option.
I ordered these: http://www.amazon.com/NFC-Tag-Bundl...qid=1350520268&sr=8-1&keywords=tags+for+droid
They came quickly despite not being Prime Eligible. The quality is very nice and I look forward to testing them out when I get my phone later this month,
2 pices:
Ebay link
In case anyone is interested, I worked out how to write protect my Smart tags so they can't be hijacked by anyone who wants to write to them.
First, you need to read the existing content. (I used NFC Tag Writer by NXP, as it allows you to copy the content straight to the clipboard.) I then used NFC Writer by Tagstand to write the same content again but with the write protect option set. I had to write the content twice to be able to write protect - first in the normal way (no option to protect) then again via history with the option to lock in top right of the screen.
I've now locked all mine so they will always be the correct IDs for SmartConnect.
nickola said:
If my phone could trigger actions without being "under my actual monitoring" (On and unlocked) in reaction to NFC tags, I 'd consider that quite unsafe.
At least, there should be some kind of restriction system, like : you can trigger actions only on this particular list of "declared secure by the user" tags.
Maybe the software Yesyesimanoob (what a funny user name, sorry) speaks of can do it, i don't know.
Nickola
Click to expand...
Click to collapse
It's called "Turn NFC Off". It's built into every Android with NFC.
dragon_76 said:
It's called "Turn NFC Off". It's built into every Android with NFC.
Click to expand...
Click to collapse
Not exactly. If NFC is OFF (and it definitely is on my phone), there is no reaction to any smart tag.
What I meant is, that there should be a possibility to specify a list of "user tags", the same way you can declare a Mac Addresses list on your WiFi access point/ISP router.
Anyway I've given up on using NFC.
Nickola
Smart Tags are much more beautiful than general ones...But may I ask how much u spent on them?I found them very cheap in local stores and thought that they were not original ones.
nickola said:
Not exactly. If NFC is OFF (and it definitely is on my phone), there is no reaction to any smart tag.
What I meant is, that there should be a possibility to specify a list of "user tags", the same way you can declare a Mac Addresses list on your WiFi access point/ISP router.
Anyway I've given up on using NFC.
Nickola
Click to expand...
Click to collapse
NFC doesn't serialise chips. Any "user tag" could be cloned, passive devices being much more difficult than active. RFID, and NFC by extension, were designed to be simple. The fact that companies or individuals have chosen to use the technology in a way that may compromise security is irrelevant to the technology. Its biggest security feature is that it requires physical access within just a few centimetres, and it requires one device to be "smart" and know what to do with any information in a tag.
You can always put a little tinfoil hat on your phone to match your own...
To be honest, I never pay much attention to Smart Tag until I saw this thread, LOL
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.
Hello,
Galaxy series is wunderfull piece of hardware because of S-Pen. To use its full potential you need propper software for it.
Original S Note is great software, but has some reasonless limitations:
- password (max 10 chars, no chars like [email protected]#...)
- sounds (can't be turned off)
- pens (cannot rearange possition of user defined pen styles)
- can't easly insert space in memo...
(connected app --> "Action Memo", has too few editing options, formating options...)
I don't belive that it will be fixed in future versions. So the one and only solution seems to be create new S Note clone.
There was nice attempt "Write beta", you can find it on google play, but it is probably no more supported and developed.
So the foolish question is:
Is someone willing to start develop S Note clone?
Artichouke said:
Hello,
Galaxy series is wunderfull piece of hardware because of S-Pen. To use its full potential you need propper software for it.
Original S Note is great software, but has some reasonless limitations:
- password (max 10 chars, no chars like [email protected]#...)
- sounds (can't be turned off)
- pens (cannot rearange possition of user defined pen styles)
- can't easly insert space in memo...
(connected app --> "Action Memo", has too few editing options, formating options...)
I don't belive that it will be fixed in future versions. So the one and only solution seems to be create new S Note clone.
There was nice attempt "Write beta", you can find it on google play, but it is probably no more supported and developed.
So the foolish question is:
Is someone willing to start develop S Note clone?
Click to expand...
Click to collapse
Maybe I'm missing something important, but I just use Google keep. I use "S Pen Toolkit" to auto-launch Keep when I remove the S-Pen, and it seems to work well enough for what I use it for.
StevePritchard said:
Maybe I'm missing something important, but I just use Google keep. I use "S Pen Toolkit" to auto-launch Keep when I remove the S-Pen, and it seems to work well enough for what I use it for.
Click to expand...
Click to collapse
The point is that you cannot compare Google Keep or EverNote with S-Note. S-Note is very complex with many functions. But as I wrote, S-Note has pointless restrictions. Also it is written here:
http://forum.xda-developers.com/showthread.php?t=2551326
(Of course I know, recreate S-Note-clone is complicated, but it could be a challenge for someone )