Trinus Forum › Forums › Trinus AIOVR › New to AIOVR, Assistance will be appreciated
Tagged: AIOVR, Android Nibiru 2.10.000, Shinecon, V509, virtual reality
- This topic has 10 replies, 2 voices, and was last updated 3 years, 2 months ago by
MonTaGaTnoM.
-
AuthorPosts
-
January 26, 2018 at 2:30 pm #7458
MonTaGaTnoM
ParticipantHowdy there TrinusVR forums,
I am happy to be a part of a new, though recently exploited and famed hobby. A product of mass-manufacturing commercial era factories. I have recently become an owner(among many) of a VR Shinecon AIO-1 headset, the best headset I could find for cheap per research of required design features. Having a neat processor, 2GB of RAM, adequate storage space, having a 1080P display, having android, having IPD/Focus adjustment and decent facial comfort.However everything cheap has their cost-cutting drawbacks, some rather distracting and annoying defects in the product. A few of them, which are profoundly obstacles, high resolution video from 1080P to 4K at either 30 to 60FPS have decent quality, although the hardware periodically hiccups some polygon artifacts causing flinching during video playback at the aforementioned formats.
The second profound drawback is how poorly the NibiruOS 2.10.000 release of this Android variant was compiled. I can’t figure out how to get the doggone thing to USB tether to my laptop! I noticed that in this variant release of NibiruOS compiled for the Allwinner H8 Octacore Cortex A7 A83T, that they have conveniently omitted the most important feature from the expected vr experience. The USB Tethering option in the extra networking settings page… Is there any possible way to fix this overlooked factory defect? Any creative criticism, tips, and/or instruction for rectifying the problems I have noticed this far is very much welcomed..
So far I have tested the Play store releases of TrinusVR’s software, and am using the site described OS variant specific releases of the AIO software. This is as far as I have went with this software, not sure of what else to test. I have a slew of games that have been tested by many people to enjoy with this, hope a solution is presented soon.
I look forward to getting a little fun out of this headset for some enjoyment in cheap VR with this forum. If anyone may know of a replacement, or possible upgraded PCB board for these units (A great deal of them I’m sure are generic in design.) for sale at a cheaply affordable price, then by all means please share… I’m also keeping in consideration replacing the SoC with a replacement that I have not bought yet, so returning this thing is an option, only about a week after receiving the import. If you have made it this far, thank you for keeping up with my over-thought out and heavily seasoned thread. I very much look forward to the solutions that surely have cost a tear or two, if you may be obliged to share them.
January 26, 2018 at 2:38 pm #7459MonTaGaTnoM
ParticipantWho renamed the delete thread button as Edit?? That is a very cruel thing to do..
January 26, 2018 at 10:28 pm #7464MonTaGaTnoM
ParticipantI have also rooted the headset with KingoRoot, the only rooting program that would work..
Also have access to regular Android settings, including dev options. I believe that I have read through most of the available info for these head mounted ache machines.-
This reply was modified 3 years, 2 months ago by
MonTaGaTnoM.
January 27, 2018 at 1:18 am #7467MonTaGaTnoM
ParticipantI had hope that using a third party tethering app might help TrinusVR for AIO headsets, though I was mistaken. It seems that TrinusVR for AIO is only expecting the non existing system tethering option. Even attempting to toggle the program via adb shell with, “adb shell su -c service call connectivity 34 i32 1” the command recommended for KitKat 4.4.2, has no effect on TrinusVR.
January 28, 2018 at 6:46 pm #7470loxai
KeymasterIndeed, the USB tethering implementation seems to be problematic with AIO devices. My test device is the (discontinued) Magicsee M1 Pro.
Tethering worked fine on that model, although it had the advantage of hdmi input, which is the best option for fast video.
That said, Trinus AIOVR has the Video via USB-ADB option for when USB Tethering is not possible.January 29, 2018 at 3:01 am #7471MonTaGaTnoM
ParticipantThank you for sharing this with me.
How might I try using this Video via USB-ADB feature? Is it possible to use the HMD’s sensors via USB when using that aswell?-
This reply was modified 3 years, 2 months ago by
MonTaGaTnoM.
January 29, 2018 at 1:43 pm #7474loxai
KeymasterEnable the ‘Video via USB-ADB’ checkbox
January 31, 2018 at 12:01 pm #7478MonTaGaTnoM
ParticipantI see that it does work, with MPC-HC player, though when I try to run DukeVR, nothing displays, although the mouse use does work, only the trinusVR logo shows up. Using mouse only mode since DukeVR renders SBS automatically. Does your program support programs like eduke32?
January 31, 2018 at 1:09 pm #7482MonTaGaTnoM
ParticipantThis software is ignoring the games I’m running
January 31, 2018 at 2:40 pm #7484loxai
KeymasterMouse mode working depends on the game and hardware used. DukeVR is an Oculus port (not SteamVR), might work using Revive.
January 31, 2018 at 3:54 pm #7487MonTaGaTnoM
ParticipantI understand that, which is why I downloaded one of their older versions for custom HMD’s that are not Oculus. I don’t think I need Revive, as even Mirrors Edge won’t even get recognized by Trinus AIO VR Beta. As for SteamVR, I cannot run it. Might you add compatibility for Vireio Perception? Would be nice to have that feature in this version of your software meant for Android NibiruOS.
How exactly does your software interface with programs, and how am I supposed to get it working with other programs?
-
This reply was modified 3 years, 2 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.