So I got the Pioneer 8100NEX setup last night. After flashing OxygenOS on my phone (BlissPop wouldn't work due to the DPI issue) I am up and running with Android Auto. However, when going through the music app option all I have is Google Music. The other main app I use for tunes and general listening is TuneIn which, while installed and apparently should work, is not showing up. I searched the settings for TuneIn and didn't notice anything obvious. Is this a Pioneer setting I am going to wait for or am I missing something obvious? Thanks!
I realize this is a dusty post, but did you ever get TuneIn to appear in AA? I'm having the same issue on my Nexus 6P.
Allow me to spray some Pledge/Endust on this topic as well. I have a Moto X Pure Edition running TruPureXMM 2.6 and I just purchased a 2016 Honda Civic EX with Android Auto built-in. Everything about it works great: Maps, Hangouts, Play Music with voice search, the whole thing. EXCEPT: similar to the posters above, when touching the Audio button to see other apps, the only app listed is Google Play Music. I should also note that I have multiple Auto-compatible audio apps in addition to TuneIn Radio Pro; I also have BeyondPod, Pandora, and iHeartRadio. None of them appear. Google support is non-existent at this point, which is a little unsettling as more and more carmakers are offering stock options with Android Auto.
I'm not any kind of expert, but I'm wondering if this is a side effect of having a rooted and/or custom ROM installed. Mine is stock based for my phone but it is rooted and I see that the OP had a custom ROM as well. I don't know what you are running @monorailmedic. Any information or assistance from someone who has experienced this would be greatly appreciated. Thanks.
Do you have any adblock app running on your phone?
johannvonperfect said:
Allow me to spray some Pledge/Endust on this topic as well...
...I should also note that I have multiple Auto-compatible audio apps in addition to TuneIn Radio Pro; I also have BeyondPod, Pandora, and iHeartRadio. None of them appear. Google support is non-existent at this point, which is a little unsettling as more and more carmakers are offering stock options with Android Auto.
I'm not any kind of expert, but I'm wondering if this is a side effect of having a rooted and/or custom ROM installed. Mine is stock based for my phone but it is rooted and I see that the OP had a custom ROM as well. I don't know what you are running @monorailmedic. Any information or assistance from someone who has experienced this would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
I am running the stock ROM on a Nexus 6P. All of my other audio apps appear (BeyondPod, DoggCatcher, NPR One, Google Play Music...)
themissionimpossible said:
Do you have any adblock app running on your phone?
Click to expand...
Click to collapse
I have none.
themissionimpossible said:
Do you have any adblock app running on your phone?
Click to expand...
Click to collapse
I do have AdAway. I will try disabling it the next time I am in my car. However...
monorailmedic said:
I am running the stock ROM on a Nexus 6P. All of my other audio apps appear (BeyondPod, DoggCatcher, NPR One, Google Play Music...)
...
I have none.
Click to expand...
Click to collapse
Curiouser and curiouser. I will mention that I tried disabling USB Debugging and that did not have any effect.
johannvonperfect said:
I do have AdAway. I will try disabling it the next time I am in my car.
Click to expand...
Click to collapse
Disabling AdAway had no effect. However, I believe I have resolved the issue.
I mentioned that I have TuneIn Radio Pro, but I did not mention that I got it through the Amazon App Store rather than Google Play. (It was a free app of the day many moons ago.) I installed the regular version of TuneIn from the Play Store and...voila, it appeared in Auto. Same thing with the other apps - I had installed them outside of Google Play, and apparently Auto doesn't like that. Reinstalling through the Play Store got me up and running.
I don't know if that scenario is also your issue @monorailmedic, but mine has been resolved this way.
johannvonperfect said:
...
I mentioned that I have TuneIn Radio Pro, but I did not mention that I got it through the Amazon App Store rather than Google Play. (It was a free app of the day many moons ago.) I installed the regular version of TuneIn from the Play Store and...voila, it appeared in Auto. Same thing with the other apps - I had installed them outside of Google Play, and apparently Auto doesn't like that. Reinstalling through the Play Store got me up and running.
I don't know if that scenario is also your issue @monorailmedic, but mine has been resolved this way.
Click to expand...
Click to collapse
I too got the Pro version from Amazon years ago when it was a freebie. I'll try downloading the version from the Play Store in the morning. I wrote to TuneIn today, so if this is the issue, it'd be swell if they provided me the key to the newer pro version via the Play Store.
johannvonperfect said:
Disabling AdAway had no effect. However, I believe I have resolved the issue.
I mentioned that I have TuneIn Radio Pro, but I did not mention that I got it through the Amazon App Store rather than Google Play.
Click to expand...
Click to collapse
In fact, I mentioned a possible block because IMHO the apps for Android Auto can't work if they aren't able to contact the Google Play store for license activation.
johannvonperfect said:
I believe I have resolved the issue.
I mentioned that I have TuneIn Radio Pro, but I did not mention that I got it through the Amazon App Store rather than Google Play. (It was a free app of the day many moons ago.) I installed the regular version of TuneIn from the Play Store and...voila, it appeared in Auto. Same thing with the other apps - I had installed them outside of Google Play, and apparently Auto doesn't like that. Reinstalling through the Play Store got me up and running.
Click to expand...
Click to collapse
Interesting... Besides license validation of protected apps (which the dev controls) this is the first instance I recall hearing where sideloaded apps won't work.
Developers of AA compatible apps can't just sideload either, even just for testing. App has to go through Google Play as a special AA beta test.
Google requires that all AA compatible apps (and their updates) be tested by them and approved for not being distracting. This is part of their protection for that. Sideloaded or Amazon etc. apps can't be guaranteed to have gone through this testing. (Actually an MD5 of the APK or similar could be done, but that could be abused on rooted devices and Google prefers everything goes through Play anyway.)
So, how are you all using TuneIn? I've been immensely disappointed that there's no favorites/presets list available via AA. Nor is there even the recent stations list available. So, how in the world do you access the stations you want? The lists that are available seem really truncated and have only strange channels I've never heard of. I was able to use voice commands once but now that isn't working and one of my stations wasn't accessible that way either. So, the whole app seems to be essentially useless to me via the AA interface. Bluetooth streaming still works, but defeats the purpose and of course then there's no access to any of the other aspects of AA.
monorailmedic said:
I too got the Pro version from Amazon years ago when it was a freebie. I'll try downloading the version from the Play Store in the morning. I wrote to TuneIn today, so if this is the issue, it'd be swell if they provided me the key to the newer pro version via the Play Store.
Click to expand...
Click to collapse
I too have the pro version from Amazon, which i got for free. In order to get it to work with Android Auto you have to install it using google play as the vendor. Same goes with other apps that you sideload
1. Install Tunein Pro from Amazon Store.
2. Save the apk installer file using es Explorer. hxxp://android.stackexchange.com/questions/75360/is-it-possible-to-backup-apk-from-an-installed-application
3. Uninstall Tunein Pro
4. Reinstall using ADB hxxps://pixplicity.com/setting-install-vendor-debug-app/
I tested it and it works
You can also "unblock" non-play store apps in AA. Open AA on your phone, then go to "information" then tap many times on the upper bar... it will reveal "developer options". Now tap on 3-dot menu and set developer mode. You should see more apps through car headunit.
Hi, I just received my new Mi VR headset. I have a Mi5 32g running the official LineageOS 14.1 build.
The companion app for the headset requires the MIUI China ROM 8.3 or newer to run:
(note: XDA forum does not let me post the link to the apk since I m a new user. You can google app.xiaomi and 431493 to find it)
The headset seems rather useless without that app.
I managed to make Google Daydream app work, but the Mi VR controller is not recognized by it, as expected. Furthermore, the Mi VR controller doesn't even connect to Bluetooth - it is supposed to only work within that VR app.
My first question is: ideas on how to hack the app so that it works in LineageOS? Build.prop mods? Apk editions? I tried a few things without luck so far.
Do you guys think there are actual drivers etc in the China ROM that are required for the app to run? If so could they be extracted from the China ROM and installed into the LineageOS?
Finally, what are the chances of making the MI VR controller emulate a daydream controller?
The build quality of this headset is excellent. Best in its class. If we can make it work with our Xiaomi phones it will be a home run.
Thanks!
Federico
To work on making the Mi VR controller work with Google Daydream App, here are two hints:
The emulator apk that allows any phone to emulate a Daydream controller:
Google: daydream + controller + emulator
User that reverse-engineered the Daydream View controller to make it work on an iPhone:
Google: hackernoon + daydream controller + Pisani
(again I can't post urls yet - too new in the forum)
If someone could reverse engineer the Mi VR controller in the same way -which is pretty identical- then we could envision to make it work using parts of the code of the controller-emulator app.
plz
I really, really need this. please tell me if you can get it to work.
when you got daydream to work with the headset do you know if it was using the phone sensors or the built in headset sensors? was daydream working with the phone plugged into the headset or do you have to leave it unconnected?
cheers
PushStartVR said:
I really, really need this. please tell me if you can get it to work.
when you got daydream to work with the headset do you know if it was using the phone sensors or the built in headset sensors? was daydream working with the phone plugged into the headset or do you have to leave it unconnected?
cheers
Click to expand...
Click to collapse
Update: Daydream app is working great using another phone with the daydream controller emulator app. Daydream uses the phone sensors, not the headset's. The MI VR controller is not recognized.
I still can't make the MI VR app work.
I got to download from the Xiaomi website the SDK for the MI VR. I wonder if someone could use it to make a "driver" to use the MI VR controller and sensors in Daydream.
Also making the MI VR app work on LineageOS is key!!
A very cool project
Perhaps I should start giving more background here for catching more people's interest.
So first: going to geekbuying (.com), you can get the new Mi VR headset (white, with controller) shipped everywhere for about 70 dollars. You might say "That's more expensive / equally expensive than the Google Daydream View". Yes. But it is about 10 times better, too.
For starters: the Mi VR headset is more or less a copy of the design of the Playstation VR headset. Everything in it cries high quality, and you can use it (personal experience) for long sessions of 20+ minutes without feeling any fatigue or discomfort. It's pretty awesome.
Second: it has a controller just like the Daydream View, but it's a little better thought through (in Daydream View you need to press a button for 2 seconds for the VR experience to center; in the Mi VR it does that with double click which is easier; also, the Mi VR controller has a magnetometer, I'm not sure the Daydream controller has it, and I suspect it can be used to calculate distance from the phone and thus have some sense of movement, which in theory could offer one more degree of freedom - I might be wrong and this might be also available in the Daydream controller, I haven't checked).
But the aspect where the Mi VR headset excels is in its inclusion of native sensors in the headset that have a much higher refresh rate than those typically found in phones. In theory, they provide a much more fluid movement experience in VR.
All that said, the product has officially only launched in China. When you buy it from Geekbuying or similar sites, you will get a box wherein everything is in Chinese, including the manual etc.
As far as I can tell, the Mi VR app, not to be confused with the Mi VR PLAY app, is sort of the epicenter for the use of the headset/controller as they can only be paired through that app. In fact the controller cannot even pair directly through Bluetooth without the app.
The app is not in Google Play Store, it can be downloaded from the Mi Store but it refuses to work on LineageOS and I think it might also don't work in MIUI global ROM (not sure of that). It is made to work on MIUI China Rom.
Last but not least: apps like vRidge and Trinus allow to stream SteamVR games from your computer to your telephone to use it in headsets (it transmits sensor data back to the computer), by simulating a Rift headset.
I've tried this on the Mi5 phone with the Mi VR headset and it is AMAZING (you need to have a direct connection using the phone as hotspot for reducing delay).
And there are a few programmers that have made the Daydream Controller Emulator app on a phone as an emulator of HTC Vibe controllers in SteamVR.
So...we are close to be able to use the actual hardware controllers (Daydream controller, possibly Mi VR controller) and the headsets to play VR games designed originally for Rift or HTC Vibe and have an acceptable experience of them at a fraction of the investment.
To recapitulate, the roadmap to be able to fully enjoy the Mi VR with a Mi phone (like Mi5) is:
1) to somehow make the Mi VR app work with LineageOS (this might simply entail obtaining a proper build.prop file for the China rom, or perhaps is more complex than that and it might entail obtaining some files from the China ROM to be included in the LineageOS system)
2) to manage to build a driver for Windows for the Mi VR controller, so that it can interact with things like SteamVR
3) to manage to somehow make Daydream app recognize the Mi VR controller
4) maybe: to manage to make Daydream app recognize / use the headset's sensors (as opposed to the phone's). Same for vRidge/Trinus
Let me know if anyone would like to collaborate on this.
best!
Federico
how hard is it to get the SDK?
im no dev but I have some skills to follow whats going on.
---------- Post added at 01:11 PM ---------- Previous post was at 12:27 PM ----------
Federico.parra said:
Perhaps I should start giving more background here for catching more people's interest.
So first: going to geekbuying (.com), you can get the new Mi VR headset (white, with controller) shipped everywhere for about 70 dollars. You might say "That's more expensive / equally expensive than the Google Daydream View". Yes. But it is about 10 times better, too.
For starters: the Mi VR headset is more or less a copy of the design of the Playstation VR headset. Everything in it cries high quality, and you can use it (personal experience) for long sessions of 20+ minutes without feeling any fatigue or discomfort. It's pretty awesome.
Second: it has a controller just like the Daydream View, but it's a little better thought through (in Daydream View you need to press a button for 2 seconds for the VR experience to center; in the Mi VR it does that with double click which is easier; also, the Mi VR controller has a magnetometer, I'm not sure the Daydream controller has it, and I suspect it can be used to calculate distance from the phone and thus have some sense of movement, which in theory could offer one more degree of freedom - I might be wrong and this might be also available in the Daydream controller, I haven't checked).
But the aspect where the Mi VR headset excels is in its inclusion of native sensors in the headset that have a much higher refresh rate than those typically found in phones. In theory, they provide a much more fluid movement experience in VR.
All that said, the product has officially only launched in China. When you buy it from Geekbuying or similar sites, you will get a box wherein everything is in Chinese, including the manual etc.
As far as I can tell, the Mi VR app, not to be confused with the Mi VR PLAY app, is sort of the epicenter for the use of the headset/controller as they can only be paired through that app. In fact the controller cannot even pair directly through Bluetooth without the app.
The app is not in Google Play Store, it can be downloaded from the Mi Store but it refuses to work on LineageOS and I think it might also don't work in MIUI global ROM (not sure of that). It is made to work on MIUI China Rom.
Last but not least: apps like vRidge and Trinus allow to stream SteamVR games from your computer to your telephone to use it in headsets (it transmits sensor data back to the computer), by simulating a Rift headset.
I've tried this on the Mi5 phone with the Mi VR headset and it is AMAZING (you need to have a direct connection using the phone as hotspot for reducing delay).
And there are a few programmers that have made the Daydream Controller Emulator app on a phone as an emulator of HTC Vibe controllers in SteamVR.
So...we are close to be able to use the actual hardware controllers (Daydream controller, possibly Mi VR controller) and the headsets to play VR games designed originally for Rift or HTC Vibe and have an acceptable experience of them at a fraction of the investment.
To recapitulate, the roadmap to be able to fully enjoy the Mi VR with a Mi phone (like Mi5) is:
1) to somehow make the Mi VR app work with LineageOS (this might simply entail obtaining a proper build.prop file for the China rom, or perhaps is more complex than that and it might entail obtaining some files from the China ROM to be included in the LineageOS system)
2) to manage to build a driver for Windows for the Mi VR controller, so that it can interact with things like SteamVR
3) to manage to somehow make Daydream app recognize the Mi VR controller
4) maybe: to manage to make Daydream app recognize / use the headset's sensors (as opposed to the phone's). Same for vRidge/Trinus
Let me know if anyone would like to collaborate on this.
best!
Federico
Click to expand...
Click to collapse
Awesome, didnt know about the steam vr thing. When you were using steamVR did it use the headset sensors?
PushStartVR said:
how hard is it to get the SDK?
im no dev but I have some skills to follow whats going on. [...]
Awesome, didnt know about the steam vr thing. When you were using steamVR did it use the headset sensors?
Click to expand...
Click to collapse
Hi! I can't post links here yet (too new a member in the forum) but you can google "dev.xiaomi.com mi vr" and you'll find it/them. There is a generic SDK and then a Unity plugin SDK that apparently is very easy to implement in the personal free version of unity.
There seems to be a procedure involving a Google Form one needs to fill in in order to get a code that, I assume, is necessary to get your apk published within their specific Mi VR market - but I understand that code would not be necessary for testing in a phone.
The website is fully in Chinese - I found that using Google Translator gave me a decent enough translation to follow through.
About SteamVR: both Trinus and vRidge (Riftcat) used the phone sensors, none of them appear to "see" the headset's. There should be a way to expose them on the Android device, and also I would assume there should be some modification made to the Trinus/vRidge client Android apps so that they send that sensor data as opposed to the Mi5 sensor data. Not that easy but perhaps not that difficult, I don't know.
Same applies for Daydream app.
Let me know if you get anything to work, the headset is really awesome - even the rudimentary experience of using it with Daydream app with another phone as controller (emulator) has been really cool!
Hey there!
I´m using the Mi Vr app, and everything its in chinnese, so I´m willing to use the daydream apk.
I´ve already installed it, but when I open it I need the controller, but the problem is; I can´t connect the controller through bluetooth, it just appears to be connected when I open the MiVR app.
I´m thinking that maybe, I could open the MiVR app, so the controller gets connected, and then frezze it and open the DayDream app, and see if it works, although I dont think so.
Have you get anything new on how to use it??
best regards
@Federico.parra How did you manage installing the daydream app on lineage?
Hi, maybe this interest you, some open source software and APIs unlike xiaomi's
http://openhmd.net
Received my mi VR today. Flashed xiaomi.eu MIUI 8 to test. In MIUI you can use the headset only with miVR app. There appears a screen in the phone even when you are in another app and even if miVR app ist not Installed. Also app translator doesn't work when using the miVR app. Too sad there is only the chinese app
QR code
Federico.parra said:
Update: Daydream app is working great using another phone with the daydream controller emulator app. Daydream uses the phone sensors, not the headset's. The MI VR controller is not recognized.
I still can't make the MI VR app work.
I got to download from the Xiaomi website the SDK for the MI VR. I wonder if someone could use it to make a "driver" to use the MI VR controller and sensors in Daydream.
Also making the MI VR app work on LineageOS is key!!
Click to expand...
Click to collapse
Which QR code do you use to calibrate the MIVR for daydream?
Mi VR is not working on my Mi 5 with MIUI 8 Global ROM
unicycler said:
Received my mi VR today. Flashed xiaomi.eu MIUI 8 to test. In MIUI you can use the headset only with miVR app. There appears a screen in the phone even when you are in another app and even if miVR app ist not Installed. Also app translator doesn't work when using the miVR app. Too sad there is only the chinese app
Click to expand...
Click to collapse
Were you able to use the Mi VR headset? I have a Mi5 with Global ROM MIUI 8.1.4.0 but when I plug the phone to the VR I got a black screen saying that I have to unplug the phone.
I tried to install the Chinese ROM but I couldn't.
rodry15 said:
Were you able to use the Mi VR headset? I have a Mi5 with Global ROM MIUI 8.1.4.0 but when I plug the phone to the VR I got a black screen saying that I have to unplug the phone.
I tried to install the Chinese ROM but I couldn't.
Click to expand...
Click to collapse
Habe you installed the app?
On xiaomi.eu ROM I've been able to run the app and use Mi VR, yes.
unicycler said:
Habe you installed the app?
On xiaomi.eu ROM I've been able to run the app and use Mi VR, yes.
Click to expand...
Click to collapse
I've download the apk and ran the installation but I don't see the app logo. I'll try with that rom you mentioned, probably does not work with the global rom (it's the official one)
rodry15 said:
I've download the apk and ran the installation but I don't see the app logo. I'll try with that rom you mentioned, probably does not work with the global rom (it's the official one)
Click to expand...
Click to collapse
Thats weird. Where did you get the apk from?
I've also installed it on lineage, it won't run, but app symbol is there and also should be there on global miui.
I installed last MIUI Global dev ROM and installed the App (downloaded directly from Xiaomi market) and it works fine, EXCEPT that the controller does not work properly: its buttons work fine, but the pointer does not move when I move the controller around. It's not a pairing issue, as in one particular game (a paper airplane flying through the mountains) moving the controller does move the plane...it seems like a weird software issue that makes me think that only China version of the ROM has been thoroughly tested with Mi VR and that support in the Global dev ROM is untested / limited.
Does anybody else had the same experience with the controller not moving the pointer in menus etc?
Also, for those that have it working with Global Dev ROM, any clues on how to make this work on LineageOS, perhaps moving a few folder from MIUI DEV GLOBAL to the LineageOS system files?
Yes, same here. Didn't try the paper game yet, but it doesn't react to the moves of the controller. Does it have to outside from games? I'm on latest xiaomi.eu ROM (MIUI 8.3)
unicycler said:
Habe you installed the app?
On xiaomi.eu ROM I've been able to run the app and use Mi VR, yes.
Click to expand...
Click to collapse
Did remote and headset button worked for you?
_PePeL said:
Did remote and headset button worked for you?
Click to expand...
Click to collapse
Yes it did.
My phone was working fine until few months back, I started to notice headset not working properly, not sure if the problem was caused by system update or apps I've installed. Is there a way to troubleshoot the problem? I'm not that familiar with Android, working mostly with PC (Linux/Windows).
Here's what I've noticed:
1) Skype audio test stopped working (I can't hear through earphone).
2) Tried using Whatsapp, the same result
3) Installed Earphones Test+ 2.8 and Mic Test 5.2 (both apps installed from Google Play store and developer is Laureano) and both reported back that the mic and earphone are working fine.
ps: I haven't updated for some time the following services: Android Accessibility Suite, Android System Webview, Clock, from Google: Carrier Services, Gboard, Google, Google Calendar, Google Duo, Google Maps, Google Photos, Speech Services. I'd like to avoid installing unnecessary apps/services, and use as much as I can opensource apps.
Hi. I've been trying to run CarStream and Fermata Player on my Hyundai Santa Fe with my rooted Pixel 6 Pro but everytime I try to start these apps on my car, the apps keep force closing on my phone. If I patch using AA Phenotype Patcher and reboot, the apps work fine. But I have to do this every time. Can anyone suggest a way that I don't have to do this everytime I connect my phone to the car? I have tried cloning the apps using Lucky Patcher, tried using an older version of Android Auto, King Installer, AAAD, etc. But everytime I need to patch or clear data of AA in order to get 3rd party apps running in my car.
I have the same problem but haven't found a solution. All third party apps keep force closing on the latest AA 7.1 and even 6.9. and 6.8 refuses to run without updating itself to 7.1
Let me know if you find a solution
I did discover a fix by accident. So this is how my 3rd party apps run without any patching or clearing data again and again:
1. Fully updated AA on my phone using Play Store.
2. Downloaded CarStream and Fermata Player using AAAD.
3. Cloned the apps using Lucky Patcher and uninstalled CarStream and Fermata Player.
4. Installed patched versions of CarStream and Fermata Player using King Installer.
5. Patched CarStream and Fermata Player using AA Phenotype Patcher.
6. Uninstalled all the updates to AA from Play Store.
7. Connected my phone to car and updated AA when prompted.
That's it. From that time Carstream and Fermata Player stopped force closing and are running on every drive without me having to run the patches and rebooting the phone again and again. Let me know if it helps you too.