After reading through the general Appradio Unchained thread for several hours, I've realized that Appradio in general is device specific in many ways. This became especially apparent after I tried using an Android device Pioneer lists as being compatible with Appradio to no avail. The Nexus 7, and the Nexus series in fact, is not listed as supported by Pioneer but the Nexus 5 and Nexus 7 have been confirmed compatbile by many users. Pioneer hasn't even updated their compatibility list in 27 months:
pioneerelectronics com/PUSA/Car/AppRadio/AppRadio+Compatible+Devices
My current hardware:
Pioneer 4000NEX, completely stock
Axxess ASWC-1
Nexus 7 (2013)
Analogix SlimPort adapter
Mediabridge ULTRA Series HDMI Cable (6 Feet) - High-Speed Supports Ethernet, 3D and Audio Return [Newest Standard]
OEM USB charging cable
N7 Software
PureROM-4.4.4-KTU84Q-7-28-14.zip
pa_gapps-stock-4.4.4-20140818-signed.zip
ES File Explorer from Play store
ARU 0.16
CarKeyboard from Play store
4000NEX Smartphone settings: Other, HDMI
ARU Settings:
General > all checked
Keyboard > Change Input Method > CarKeyboard checked, open keyboard settings screen > carKeyboard checked
ARU > Rotation Locker checked, Start GPS Injector checked
Region setting: United States
N7 Bluetooth settings: Connected via phone and media
I then plugged in SlimPort adapter. On the home screen on the 4000NEX, the App button no longer had an X and touching it brought me to a new window, the Appradio window. After the BT connection reestablished itself with the new protocol, the N7 screen appeared on the 4000NEX!
Problems: The screen is very distorted. The y axis is reduced, making the image appear squashed.
Rotation locker doesn't seem to work, as the native rotation on the N7 is carried over to the 4000NEX; if the N7 is upside down, the 4000NEX displays the image right side up but inverts the touch input! Here's a video showing the issue:
dropbox com/s/fqlyega9de22gj3/2014-08-21%2016.50.07.mp4
Does anyone else have any experience with ARU or Appradio in general?
Related
hi.
i'm using my nexus 4 (CM 10.1 nightly from last week) and an SlimPort to HDMI adapter (http://www.amazon.com/gp/product/B009UZBLSG) on my Samsung TV.
when i connect the phone, it switches to landscape but the screen is black. it is connected ("no signal" disappears on TV) but i have no picture.
if i open up YouTube and play a video, i see the video on BOTH (TV and phone) but i have NO CONTROLS on my TV.
any video i found showing SlimPort shows a direct mirroring of the mobiel screen on the TV.
when using miracast (samsung dongle) i have a perfect mirror with all the controls (and on youtube only the video) - thats fine.
how can i get simple screen mirroring with SlimPort?
is there any setting to disable "multi-monitor" and use "mirroring"?
tanks in advance.
It's the same for me.
I am using my Nexus4 with [ROM][JB 4.2.2][PA3.15][AOKP-MR1][CM10.1]P.A.C True All in 1 ROM[09/04][V22.0.2]
Slimport plugged in to Nexus+TV: Picture only on TV. Nexus 4 Screen is on but black.
After pluggin out the slimport: Picture back on Nexus 4.
This issue was fixed in M3 for CM ("experimental" build from the 11th), and the fix is in the most recent nightly as well.
Anyone running Official KitKat or Custom 4.4 based ROM seeing in Settings>Display>Cast Screen option?
Yes, it is for streaming your display to a Miracast compatible TV, etc.
From Nexus site:
Some of this information applies only to devices running Android 4.4.
Nexus 4, Nexus 5, Nexus 7 (2013), Nexus 10, and HTC One Google Play edition are compatible with devices that support the Wi-Fi Certified Miracast™ protocol for wireless display. To turn on the wireless display feature, go to SNP_BEE8810A5FCD80173673B4B15A1804EAEE99_3529219_en_v0Settings > Device > Display > Cast screen > SNP_2918040_en_v1 Menu, then check the box next to “Enable Wireless Display.”
You can cast the screen to wirelessly stream video and audio to a variety of displays and other devices that support Miracast - even when a standard Wi-Fi network isn’t available. For example, you can cast the screen to show your device’s screen on a TV equipped with a certified Miracast adapter.
For more information, see the documentation that comes with the Miracast-certified device you wish to use with your tablet or phone.
If one is lucky enough to have a rootled Google ChromeCast with the Team Eureka Custom ROM this feature is coming if you that option in your Display Settings. I'm not going back to stock just for that but just wondered if the N10 had it also.
I have a Nexus 10 running stock rom rooted. I can confirm it has this feature & working.
my nexus 7 not showing the option of enable wireless display
I have nexus7 and I have updated it to kitkat4.4.4 version on cast screen when I go to menu to select enable wireless display option so there is no option written enable wireless display but help option is coming
I've searched and searched and can't find out how to fix this problem...
I used to use a Samsung Galaxy Nexus as a dedicated device for my AppRadio 2 Headunit, and have recently wanted to step up to the Nexus 4 as my dedicated "AppRadio" device.
I used to have it so my Samsung Nexus would boot upon power detection, and shutdown w/ a tasker profile after power was no longer deteced. This worked great.
When I switched to a Nexus 4 and Slimport, I have no problem connecting to AppRadio if I unplug / replug the device. I'm trying to eliminate the need to do this.
So TL;DR...
Problem: Appradio & Nexus 4 don't detect Slimport upon bootup (if plugged in while booting)
Solution that I don't know how to reach: Either create a tasker command to mimic "unplugging" and "replugging" of the USB, or find a way for the Slimport to autoboot after initializing.
Any suggestions?
Roms: Tried Paranoid & Stock Rooted
Kernals: Tried Franco & Stock
App: Also tried ARL and ARU
Hi Guys,
I have mounted a Nexus 7 (rooted First gen) to my car dashboard. It was a outside mount using a magnetic CD mount. I have connected the usb cable to power up the tablet and using tasker to automate things. I'm using my Xperia Z2 wifi hotspot to tether internet to nexus and It's all working fine. I want to explore the possibility of adding a backup camera now. Done a lot of research but not much information. I want to forget about wifi cameras as I cant have them with my hotspot cause I can only do one device. I'm trying to see if I can use a wired connection. I want to power the camera at all times when the ignition/engine is on so I can wire it to rear lights no problem.
I saw this video and I'm quite intrigued by this;
watch?v=V-gLrqUHATQ
This is my plan;
- Get a cheap camera backup camera (seen in the above video)
- Buy a UVC video grabber to connect everything.
- Have the app installed.
The camera will power on as soon as car is ignited and will remain on all the time.
My questions;
1. Where can I get a UVC video grabber that will work with my nexus 7 (First gen) the one shown in the TY video is a second gen nexus?
2. How can I connect both my charging usb and UVC usb at the same time? Will it work with a OTG cable?
3. How can I make the app to launch the video window when my car goes into reverse? I was thinking about wiring the power to reverse lights first and then when it powers up somehow get the camera app to auto launch and then close when its powered off. But I think it will be difficult with 2 usb cables and there will be a lag? Any way to automate this with tasker?
Thanks for your advice :cyclops:
hi
i think your backup cam will be connected to the reverse gear lights. it will work when the gear is reverse. so you can use carcam app. it popups when it receives a video signal and closes when the signal ends.
or i think tasker has an option under profile/state/hardware/usb connected/video that detetcs usb video devices when connected. but i am not sure that it will detect the uvc video grabber.
Hey everyone! I bought an Onn. Streaming Box at Walmart a couple of days ago, intending to run Torque Pro on my car's preexisting Backup Screen w/ a Bluetooth OBD2 dongle (a tiny $25 self-contained Android box seemed to make a lot of sense for that application). I sideloaded the Torque apk onto the box and used a remote app w/ mouse cursor to set up the layout, but when I went to finally pair the OBD2 dongle, it wouldn't pick it up. Since the screen just says "Accessories", I'm guessing you can only pair things like headphones, controllers, keyboards, etc.
I also tried sideloading "Bluetooth Direct", and forcibly connecting to my phone's Bluetooth address (just to test), and it couldn't connect (it seems like that app doesn't work for a lot of people though).
Is there any way around this?
I'm waiting for a powered OTG cable to be delivered today, so I can root and hopefully figure something out that way. It seems weird if it's really a limitation built into the OS, since regular android is buried underneath there somewhere, and it isn't like the box has some special Bluetooth hardware that limits it to certain devices.
If all else fails, maybe I could just get an OBD2 to USB cord and plug into an OTG, but idk if that would work either (it should on other Android devices).
And for anyone wondering, yes, the Android TV UI optimized for giant 4k TV's does not work well on a 5" 480p HDMI -> RCA screen, LOL.
Figured this out if anybody wants to do something similar, I just sideloaded the app "Bluetooth Scanner - Bluetooth finder - pairing" (com.pzolee.bluetoothscanner), and was able to pair it right away. I am running LineageOS and rooted with Magisk, but I'd think this should work on stock too.