You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just got my Xreal One to use it with phoenix head tracker however, it does not support ones as it has in built X1 chip for 3DOF. The Phoenix head tracker uses your DLL for getting sensor data, will you add support for Xreal ones?
I could perhaps contribute in this. @MSmithDev , @kawaharas where you guys did get reference for xreal devices? I can see Android xreal SDK only on their website.
I could perhaps contribute in this. @MSmithDev , @kawaharas where you guys did get reference for xreal devices? I can see Android xreal SDK only on their website.
So at first glance it seems like the glasses communicate over a USB Network connection and send packets for commands and i assume the imu data. I currently don't have a pair to mess around with and can't really justify the cost if it doesn't work.
The android sdk is the only thing xreal currently offers
I could perhaps contribute in this. @MSmithDev , @kawaharas where you guys did get reference for xreal devices? I can see Android xreal SDK only on their website.
So at first glance it seems like the glasses communicate over a USB Network connection and send packets for commands and i assume the imu data. I currently don't have a pair to mess around with and can't really justify the cost if it doesn't work.
The android sdk is the only thing xreal currently offers
Let's say, I've created a python script that appears to parse the accelerometer and gyroscope data from the "Xreal One Pro" TCP socket stream. Would this help, or is more information required to make this work?
From what I understand, this should enable 3DoF, right?
@SamiMitwalli have you started working on the script, or do you have any working proof of concept ?
Yes, I have a proof of concept, it's a python script, but should be easy to adapt.
connecting via tcp socket to the glasses (169.254.2.1) on port 52998, because of the usb-ethernet connection
parsing the data stream and identifying the Gyro and Accelerometer data (Gx, Gy, Gz and Ax, Ay, Az)
printing the data
(sadly no xreal eye data is streamed)
The data stream is not even encoded, so it should be quite easy for anyone to replicate this, with the knowledge above.
(I'm thinking about forking or contributing to this repo, when I have a little bit more time)
@SamiMitwalli have you started working on the script, or do you have any working proof of concept ?
Yes, I have a proof of concept, it's a python script, but should be easy to adapt.
connecting via tcp socket to the glasses (169.254.2.1) on port 52998, because of the usb-ethernet connection
parsing the data stream and identifying the Gyro and Accelerometer data (Gx, Gy, Gz and Ax, Ay, Az)
printing the data
(sadly no xreal eye data is streamed)
The data stream is not even encoded, so it should be quite easy for anyone to replicate this, with the knowledge above. (I'm thinking about forking or contributing to this repo, when I have a little bit more time)
I published the proof of concept demo here.
The demo and the sensor data handling is not perfect, but gives the idea, of what could be done.
I hope this helps you and I can soon use my One Pro for "PhoenixHeadTracker" or "SteamVR".
@SamiMitwalli , I also tried your script on my One Pro and it works nicely, both in console and 3D viewer versions. 3DOF but not 6DOF. One step closer to integrating with "PhoenixHeadTracker" or "SteamVR". Nice work.
Thanks for checking it out, guys. A few weeks ago, I also saw that there is more sensor information in the data stream, but I have not yet updated the project (magnetometer).
@kaomoneus I did not find the information you mentioned. I am quite certain that they currently compute such things on the X1 chip and leave it on there for performance reasons and their specific standalone application (viewing a screen in 3d space)... but this is just a wild guess.
They only seem to expose minimal information that is potentially relevant to their stuff, like Unity APIs, i.e. the sensor data.
@MSmithDev , with this new info from @SamiMitwalli , would it now be possible to update your DLL for the One Pro? We should then be able to use our One Pro with PhoenixHeadTracker and SteamVR hopefully!
@MSmithDev , with this new info from @SamiMitwalli , would it now be possible to update your DLL for the One Pro? We should then be able to use our One Pro with PhoenixHeadTracker and SteamVR hopefully!
Yes it should be possible its something I can try and work on this week if not this weekend. Will probably need someone to test it with since i don't have a pair of Pro's are you in the Project MakeReal discord?
The other thing is we have been talking to an xreal developer that is currently trying to bring lower level sdk to life. Nothing confirmed yet so its still up in the air but that would certainly be the way to go with these projects moving forward since solving the drift issues is going to be redundant with the X1 chips i assume.
@MSmithDev , with this new info from @SamiMitwalli , would it now be possible to update your DLL for the One Pro? We should then be able to use our One Pro with PhoenixHeadTracker and SteamVR hopefully!
Yes it should be possible its something I can try and work on this week if not this weekend. Will probably need someone to test it with since i don't have a pair of Pro's are you in the Project MakeReal discord?
The other thing is we have been talking to an xreal developer that is currently trying to bring lower level sdk to life. Nothing confirmed yet so its still up in the air but that would certainly be the way to go with these projects moving forward since solving the drift issues is going to be redundant with the X1 chips i assume.
That sounds promising. Might then also get 6DOF?
I can offer to test with my One Pro if it helps. Let me know what to do. I'm not in the Project MakeReal Discord, and a simple end user (my coding skills are generally geared for scientific purposes).
Activity
shiroledat commentedon Jun 3, 2025
Just got my Xreal One Pro and would really like an update for support too.
kaomoneus commentedon Jun 22, 2025
I could perhaps contribute in this. @MSmithDev , @kawaharas where you guys did get reference for xreal devices? I can see Android xreal SDK only on their website.
MSmithDev commentedon Jun 22, 2025
So at first glance it seems like the glasses communicate over a USB Network connection and send packets for commands and i assume the imu data. I currently don't have a pair to mess around with and can't really justify the cost if it doesn't work.
The android sdk is the only thing xreal currently offers
Fritomaster commentedon Jun 26, 2025
Do you happen to live in NM, USA?
kaomoneus commentedon Jun 27, 2025
@MSmithDev but where did you gen xreal air protocol? Perhaps that would be a good starting point to me to search for xreal one proto...
kaomoneus commentedon Jul 1, 2025
@MSmithDev just found the some origins of your story
https://jakedownsdev.substack.com/p/open-sourcing-nreal-air-development
Great job!
SamiMitwalli commentedon Jul 14, 2025
Let's say, I've created a python script that appears to parse the accelerometer and gyroscope data from the "Xreal One Pro" TCP socket stream. Would this help, or is more information required to make this work?
From what I understand, this should enable 3DoF, right?
MSmithDev commentedon Jul 15, 2025
Thanks! I only wish Xreal would have worked with us on this.
SamiMitwalli commentedon Jul 15, 2025
Yes, I have a proof of concept, it's a python script, but should be easy to adapt.
(sadly no xreal eye data is streamed)
The data stream is not even encoded, so it should be quite easy for anyone to replicate this, with the knowledge above.
(I'm thinking about forking or contributing to this repo, when I have a little bit more time)
MSmithDev commentedon Jul 16, 2025
I'm also interesting in this
kaomoneus commentedon Jul 17, 2025
+1
SamiMitwalli commentedon Jul 18, 2025
I published the proof of concept demo here.
The demo and the sensor data handling is not perfect, but gives the idea, of what could be done.
I hope this helps you and I can soon use my One Pro for "PhoenixHeadTracker" or "SteamVR".
https://github.com/SamiMitwalli/One-Pro-IMU-Retriever-Demo
kaomoneus commentedon Sep 1, 2025
@SamiMitwalli Just tried this app! Awesome! It just works! And it works for XREAL One (not pro).
shiroledat commentedon Sep 2, 2025
@SamiMitwalli , I also tried your script on my One Pro and it works nicely, both in console and 3D viewer versions. 3DOF but not 6DOF. One step closer to integrating with "PhoenixHeadTracker" or "SteamVR". Nice work.
kaomoneus commentedon Sep 8, 2025
@SamiMitwalli how did you reverse this protocol? Is it possible to get current display mode and virtual screen location?
SamiMitwalli commentedon Sep 8, 2025
Thanks for checking it out, guys. A few weeks ago, I also saw that there is more sensor information in the data stream, but I have not yet updated the project (magnetometer).
@kaomoneus I did not find the information you mentioned. I am quite certain that they currently compute such things on the X1 chip and leave it on there for performance reasons and their specific standalone application (viewing a screen in 3d space)... but this is just a wild guess.
They only seem to expose minimal information that is potentially relevant to their stuff, like Unity APIs, i.e. the sensor data.
shiroledat commentedon Sep 15, 2025
@MSmithDev , with this new info from @SamiMitwalli , would it now be possible to update your DLL for the One Pro? We should then be able to use our One Pro with PhoenixHeadTracker and SteamVR hopefully!
MSmithDev commentedon Sep 15, 2025
Yes it should be possible its something I can try and work on this week if not this weekend. Will probably need someone to test it with since i don't have a pair of Pro's are you in the Project MakeReal discord?
The other thing is we have been talking to an xreal developer that is currently trying to bring lower level sdk to life. Nothing confirmed yet so its still up in the air but that would certainly be the way to go with these projects moving forward since solving the drift issues is going to be redundant with the X1 chips i assume.
shiroledat commentedon Sep 16, 2025
That sounds promising. Might then also get 6DOF?
I can offer to test with my One Pro if it helps. Let me know what to do. I'm not in the Project MakeReal Discord, and a simple end user (my coding skills are generally geared for scientific purposes).
kaomoneus commentedon Sep 21, 2025
@MSmithDev there are no tests yet. Do you test it on physical devices only?
Heffalump73 commentedon May 25, 2026
Hi everyone
Is this problem still alive?
I have Xreal 1S
yoshiyoish commentedon Jun 17, 2026
Xreal One Pro user here... is this dead?.... I'm gonna consider reselling my One pro.... if this is dead.....
kaomoneus commentedon Jun 18, 2026
@Heffalump73 I'm still dwelling on idea to write a backend for Xreal One, but quite busy in these times.
Heffalump73 commentedon Jun 22, 2026
@kaomoneus Hi pal! Really looking forward for this. I get it, we all are busy, times are tough these days.
MSmithDev commentedon Jun 22, 2026
No support for Xreal One, I don't have a pair of them and i don't even know if it would be possible to reverse engineer like we did for the Air's.
It's a real shame after all these years Xreal refuses to give basic access to the imu.