FORUMS
Remove All Ads from XDA

Update the LG VR360 Goggles any phone.( GooglePlay App )

21 posts
Thanks Meter: 6
 
By Supportit, Junior Member on 15th April 2018, 10:37 AM
Post Reply Email Thread
Hi so i got the Samsung S8+ and want to use the goggles with my phone and not the LG G5.

I made this app,
https://play.google.com/store/apps/d...firmwareupdate

With this you can emulate the goggles on any phone so the VR Manager from Lg is recognising it and so you can start the firmware update.

In the future i want to make it possible to use the full goggles and not just the firmware update but we will see.
Edit: it is now possible to enable and use the goggles with the app
The Following 3 Users Say Thank You to Supportit For This Useful Post: [ View ] Gift Supportit Ad-Free
 
 
15th April 2018, 01:40 PM |#2  
Junior Member
Thanks Meter: 10
 
More
Cool!
I just somehow pulled some more Informations from the hidraw0 device than usual.

Unreadable Parts are replaced by ~
~
BSP_Init >> Init SPI_Init
MotionSensor_ReadID : BMI160 ID = 0xD1


Sensor Fusion start...

bmi160.dev_addr = 0xD0
p_bmi160->chip_id = 0xD1, v_data_u8r = 0xD1
bmi160 Chip ID: 0xD1
algo_get_version() major=3 minor=6 majorbugFix=1 minorbugFix=1
sensor switch list: 1 0 1
~
sensor switch list: 1 0 1
~
Accel back up 16 2 10, CRC 28
Accel Calibration Offset is Validation
~
Gyro back up 8 -5 -12, CRC -9
Gyro Calibration Offset is Validation
Calibration temperature = 30
Accel CRC = 28
Gyro CRC = -9
Accel X Cal State = 1, Axis offset = 16
Accel Y Cal State = 1, Axis offset = 2
Accel Z Cal State = 1, Axis offset = 10
Gyro X Cal State = 1, Axis offset = 8
Gyro Y Cal State = 1, Axis offset = -5
Gyro Z Cal State = 1, Axis offset = -12
BSP_Init >> Init BMI160_Init
~
Proximity Cal load!!
pas230.ps_th_far_low = 0, pas230.ps_th_far_high = 171
pas230.ps_th_near_low = 111, pas230.ps_th_near_high = 1023
pas230.ps_cross_talk = 41
~
BSP_Init >> Init PAS230_Init
~
BSP_TC358870XBG_Init_Reg : Waiting for HDMI signal reg=(1)
~
Proximity FAR
~
~
Proximity NEAR
~
Proximity FAR
~
BSP_TC358870XBG_Start_Video >> failed ~!! stop to wait HDMI s
~
MAX98091_Init >> IN
MAX98091_Reset >> IN
MAX98091_HEADSET_On >> IN_END!!!!!!
Set_Earjack_First
BSP_Init >> Init MAX98091_Init
SW : LGR100AT-00-V10a-310-XX-MAR-11-2016+0
Power_Task: event.value.signals (3), now sleep mode (0)
Power_Task: proxi_value = 5
BSP_SM5306_Sleep: already turn off b/L, is_backlight_on (0)
Power_SleepMode: now sleep mode (1)

INPUT_EVENT_EARJACK_REMOVE
~
Power_Task: event.value.signals (4), now sleep mode (1)
Set_Earjack_Remove
MAX98091_HEADSET_Off >> END
Power_SleepMode: now sleep mode (2)

INPUT_EVENT_EARJACK_REMOVE

seems like i have:
SW : LGR100AT-00-V10a-310-XX-MAR-11-2016+0

i will try you app and give feedback!
The Following User Says Thank You to marian_86 For This Useful Post: [ View ] Gift marian_86 Ad-Free
15th April 2018, 02:45 PM |#3  
Junior Member
Thanks Meter: 10
 
More
It worked (with kinda trouble)

Plugging in the 360vr directly via USB-C in my Huawei Nova did nothing.
(I think due to incompatibility with the DP-part)
But then i tried [LG306vr] -> [Usb-C to USB-A] -> [USB-A to USB-C] -> [Phone]
While doing this i followed the instructions in your app to the point.
It worked!
The "modelname" and "software version" buttons in the LG VR Manager app are not doing anything, but i could confirm Firmware Update by pulling raw Data.
sudo cat /dev/hidraw0
Far Threshold = 111
Cross talk = 41
BSP_Init >> Init PAS230_Init
BSP_TC358870XBG_Init_Reg : Waiting for HDMI signal reg=(1)
Proximity FAR
BSP_TC358870XBG_Start_Video >> failed ~!! stop to wait HDMI sMAX98091_Init >> IN
MAX98091_Reset >> IN
MAX98091_HEADSET_On >> IN_END!!!!!!
Set_Earjack_First
BSP_Init >> Init MAX98091_Init
SW : LGR100AT-00-V10d-310-XX-MAY-02-2016+0
Power_Task: event.value.signals (2), now sleep mode (0)
Power_Task: proxi_value = 5
BSP_SM5306_Sleep: already turn off b/L, is_backlight_on (0)
Power_SleepMode: now sleep mode (1)

INPUT_EVENT_EARJACK_REMOVE
Power_Task: event.value.signals (4), now sleep mode (1)
Set_Earjack_Remove
MAX98091_HEADSET_Off >> END
Power_SleepMode: now sleep mode (2)

INPUT_EVENT_EARJACK_REMOVE

Before Update: SW : LGR100AT-00-V10a-310-XX-MAR-11-2016+0
After Update: SW : LGR100AT-00-V10d-310-XX-MAY-02-2016+0

After the Update the raw-dumps look more clean (a lot of gibberish missing).

Keep on the good work!
The Following User Says Thank You to marian_86 For This Useful Post: [ View ] Gift marian_86 Ad-Free
15th April 2018, 03:48 PM |#4  
OP Junior Member
Thanks Meter: 6
 
More
Nice thank you for testing.

I had the same result that after the update all the junk is gone in my test app and when using cat /dev/hidraw0 too
Maybe i will try to edit the firmeware to be always in on mode so the goggles will work without any app after the update, but lets see.

I made another app out of the vr manager to update the goggles directly but after some playing the goggles where always in dfu mode so i had to find this solution.

Before the firmware update my goggles where not working on the vrplayer on my pc but after the update the headtracking does work. still without a picture but a good progress so far, i think my usb c port on the pc has not hdmi part in it.
I think thats why it will may help others too
15th April 2018, 04:11 PM |#5  
Junior Member
Thanks Meter: 10
 
More
Nice, after upgrading the Firmware VR-Player (Windows) is able to enable the LCDs and use the Headtracking. (Still black image due to missing USB-C Port, but with enabled backlight)
On my 9jr old Hardware videos and everything vr related is more like a slideshow or powerpoint-presentation, but the most important thing it the proof of concept!

keep on hacking this cool gadget
15th April 2018, 07:00 PM |#6  
OP Junior Member
Thanks Meter: 6
 
More
Ok good news i am able to send the right command to the googles to start the displays via my app.

i just want to tell it, later i will make an update

Just for the info the junk in the usb transfer is indeed the motion sensor, in the old firmware it was active the whole time and in the new firmware it is only active when the start command is send to the goggles.
15th April 2018, 11:12 PM |#7  
Junior Member
Thanks Meter: 10
 
More
Great to hear!
In my opinion modding the firmware would not be suitable for "everybody", and packing a modded version into a public custom app might be difficult due to some legal issues.

Btw, i don't want to go completely offtopic, but how did you decompile the dfu file?
I've never used dfu-stuff before.
I can see the strings you mention before using:
-> strings LGR100AT-00-V10d-310-XX-MAY-02-2016+0.dfu | more
But looking at some source code could make reverse engineering a bit more easy
I think i saw some other useful commands...
17th April 2018, 07:29 AM |#8  
OP Junior Member
Thanks Meter: 6
 
More
Yes you are right this would only be an option if the command sending didn't work but now as it works, the Firmware mod isn't needed anymore.
I do know the legal problems i wouldn't put the modded Firmware in the App you would have to download it somewhere else.


I did the firmware decompile with IDA but it did not decompile everything so many data is not readable and everything else is in Assambler.

What commands did you find ?
I am able to send commands to the goggles but unfortunatly every command bigger than 14 bytes dont get acceptet right now. But every command from the list in the other thread shorter than than 15bytes gets accepted.

I am now also able to read the head tracker junk data that is coming from the goggles and make it readable.
The protocoll goes like this: the first byte is the data indicator
4 is for Information like the readable text we saw earlier.
5 is the headtracker data then the next 6 blocks of 4 bytes are float numbers with gyro xyz and accel xyz data . And after that there is one 6byte int counter.
17th April 2018, 09:21 PM |#9  
OP Junior Member
Thanks Meter: 6
 
More
I just made an update in the app.

It is now possible to enable the goggles via the app.

Download it from the play store https://play.google.com/store/apps/d...firmwareupdate
29th April 2018, 02:10 AM |#10  
Junior Member
Thanks Meter: 0
 
More
Well, my device is the H850 but my LGVR seems to be the Chinese version It's not recognizable with my phone It's now recognizable by your software
However, there are still some problems, such as the opposite direction of the two display screens that prevent me from using it properly. In addition, the features on your VR like the XDA forums are incomplete. There is no head recognition. The VR button does not work. I hope you can succeed.
my brother:五指交叉:

---------- Post added at 01:10 AM ---------- Previous post was at 01:06 AM ----------

I don't know if all versions of VR are compatible with G5. Hope you can give me some help
5th May 2018, 09:47 AM |#11  
OP Junior Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by Boss.W

Well, my device is the H850 but my LGVR seems to be the Chinese version It's not recognizable with my phone It's now recognizable by your software
However, there are still some problems, such as the opposite direction of the two display screens that prevent me from using it properly. In addition, the features on your VR like the XDA forums are incomplete. There is no head recognition. The VR button does not work. I hope you can succeed.
my brother:五指交叉:

---------- Post added at 01:10 AM ---------- Previous post was at 01:06 AM ----------

I don't know if all versions of VR are compatible with G5. Hope you can give me some help


Hi. Yes thats how it works right now.
Maybe you can try flashing another kernel from europe to your h850 and than it will work.
I bought myself one lg g5 to test the goggles but i dont like it ,it is very buggy so i will not develope any further. I did send both off my goggles back to the supplyer
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes