Ok thanks for reply, I get it now. It IS laggy on the video side. So what do you recommend, how to switch it to the right dpi? Do you think this has sth to do for ex with gpu rendering available to turn on indeveloper options?
Not sure if changing the DPI will help, in my opinion the best bet is to try some other roms. For example you can give this one a go: http://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cyanogenmod-13-cm13-0-t3303798Ok thanks for reply, I get it now. It IS laggy on the video side. So what do you recommend, how to switch it to the right dpi? Do you think this has sth to do for ex with gpu rendering available to turn on indeveloper options?
Then try cm 12 or other version of cm 13, I'm using cm 12 on the tab 2 8.9I've already tested cm13 by Andi and I was getting this (attachement) when launched AA. On CM12.1 I at least got it running.
I'm afraid I'm not aware of any other way to forward the port. You can try to use the ADB approach but in my case it wasn't stable (aka it kept disconnecting).does any one know any other way of port forwarding? that sysctl command doesn't work for me on all roms i have tried
![]()
I can use the FWD Port forward app but it doens't start on startup, does any one know any other command line / shell binary i can use to port forward?
Also when i start self mode i have to press home then open HU again, is this normal? otherwise i get a black screen.
it's require android 5.0+Hi,
I downloaded January 17 release through XDA Labs app and installed it in my RK3188 Android 4.4.4 head unit. I am using a Nexus 6P running the latest version of android to connect to it. When i connect, i can see that my phone detects the HU and shifts to android auto screen, but the head unit shows a black screen (with the side bar appearing sometimes). I am unable to see android auto view on the head unit.
Also when i exit headunit app by either using the exit entry in the sidebar or the back button, it keeps on starting back without closing. Only way to exit is to click on exit drive mode option on the notification drawer in the head unit.
I haven't tried using a different OTG cable yet, but will try that soon. Meanwhile, any idea what could be wrong here ?
Thanks in advance
Thanks for the reply. Android 5+ requirement is for the Google Android Auto app isn't it ? For that i'm using a Nexus 6P phone with android 6 running on it. It is the head unit which runs the server (headunit app) that has android 4.4.4. Should this be a problem ?it's require android 5.0+
Hi,Thanks for the reply. Android 5+ requirement is for the Google Android Auto app isn't it ? For that i'm using a Nexus 6P phone with android 6 running on it. It is the head unit which runs the server (headunit app) that has android 4.4.4. Should this be a problem ?
My head unit is 5.1.1 and I have same problemHi,
I downloaded January 17 release through XDA Labs app and installed it in my RK3188 Android 4.4.4 head unit. I am using a Nexus 6P running the latest version of android to connect to it. When i connect, i can see that my phone detects the HU and shifts to android auto screen, but the head unit shows a black screen (with the side bar appearing sometimes). I am unable to see android auto view on the head unit.
Also when i exit headunit app by either using the exit entry in the sidebar or the back button, it keeps on starting back without closing. Only way to exit is to click on exit drive mode option on the notification drawer in the head unit.
I haven't tried using a different OTG cable yet, but will try that soon. Meanwhile, any idea what could be wrong here ?
Thanks in advance
Thanks for the reply. this should be the issue. I also read elsewhere in this forum that the h264 decoding capabilities of Chinese head units are not good enough for the headunit app. The one unit which got it to work had an 8 core CPU (hopefully with better hardware decoding of h264). Mine is just a quad code RK3188.Hi,
You are right, the phone need to be 5+ and the device running the head unit need to be 4.1+. However as it was mentioned quite a few times, till now we didn't saw any chinese head unit which was able to run the app properly. It looks like all of them have some ind of problem with the Hardware decoding part.
If I recall correctly there was 1 person who got it working on an android powered head unit, but that was a custom build rather than a chinese product.
Also I think your unit is able to do a so called "screen-mirroring" called EasyConnect or similar, so you might want to try to run a headunit app on your phone in SelfMode and mirror the screen to your car stereo.
Alternatively I have posted a convoluted way on how you can mirror the screen from your phone to your car by wifi (assuming the phone is rooted). Besides not being the most practical/easiest way to get it running, it does require a strong charger for the phone (it will use Wifi+GPS+Screen always on) so the power consumption and heat up will be significant. For details see: http://forum.xda-developers.com/showpost.php?p=64881737&postcount=1015
Hi,My head unit is 5.1.1 and I have same problem
Have you succeed to run Android auto?
Or self mode!? (If yes, How?)
Thanks