MTCB 5.1 Hardware Decoding not Working? - MTCB Android Head Units General

I have an AutoTop (YINUO) KLG dash unit. When I had the stock ROM, I was able to move through Google Maps and Headunit Reloaded) with ease, but after changing to any other ROM these two apps become unusably slow. In the case of Headunit Reloaded, it simply will not work unless SW decoding is turned on. I should mention that overall the system to perform much more smoothly than they did with the stock ROM. The issue exists only with apps like Google Maps, Headunit Reloaded, and Android Auto. It seems like the issue will exist on anything that needs accelerated rendering.
I am currently using dsa8310's rk3188 1024x600 5.1.1 OpenGApps ROM. This issue has occurred on all other ROMs I have tried, including Boonroondook and Malaysk.
Any advice for troubleshooting would be appreciated.

Just tried to enable the developer setting that would flash the screen for elements rendered by the GPU. None of the previously mentioned apps caused any reaction. So presumably, these ROMs are making the GPU inaccessible to apps. I don't know how to proceed, but I'd really like to use ROMs other than the factory one.

Related

Android Auto is now available for all drivers and cars

The in-car software is available on Android 5.0 phones for every driver to access
http://www.wired.co.uk/article/android-auto-all-cars
What does this mean? Can we get this apk and install this in our android HU's and have true android auto?
I've installed this on my MTCD device via the apk (google android auto apk mirror for the apk, I cannot post links yet). Make sure to install the correct arm/arm64/x86 version for your device, the top 3 Android Auto 2.0 are the three versions.
It runs extremely slow on my unit, curious to know if others have a better experience. I think I will stick with automate for now, but hoping that there will be continued development in the android auto pipeline. I think in my case it is limited by the hardware (1GB ram, som), but I bet the newer intel units will run it well.
i have a Joying 2GB, intel unit, I will try it this weekend
Running nice on my Samsung J7 / Mazda 3 SGT
I've only played with the app on my phone but I don't think it's been designed to work in the way you think. The new app is designed so your phone displays the Android Auto UI. If you install on a MTC Headunit, it's likely that it will assume your Headunit is the phone and not link to your phone (note - I'm assuming this based on what I've read and have not tried). However... If you only install on your phone and screen mirror to your headunit, it should be close to an Android Auto experience... Let me know if this works or if anything in my post is not true...
Yup, it is essentially the Android Auto UI optimized for phones on the MTCD head unit. No link to the phone is required (which is what I expected), however the slower MTC units are just too slow to run it well enough imo.
Wouldn't screen mirroring just display the UI and you would still have to interact with the phone for selections? I feel like that defeats the purpose of Android Auto.
If they made it so any Android tablet/HU could just be the display and touchscreen for Android Auto (similar to Pioneer etc) running on your phone, that would be awesome. Would achieve the functionality at a MUCH lower price tag than the Pioneer/Sony etc units and have way more flexibility for other apps.
To be honest, I've not played with screen mirror but I thought it allowed you to control your phone from the head unit as well as display it's screen (or so the marketing talk for my head unit claimed).
I thought it was uni-directional, but I have not tried it myself either (only got it a few weeks ago). After looking at some of the information, I think you might be right (assuming it really is mirror link). Hoping that is the case!
I loaded it on my Joying 2GB Intel 8 inch Android 5.1 unit
Much better than expected, although you still can't make calls on it
More pics
CadillacMike said:
I loaded it on my Joying 2GB Intel 8 inch Android 5.1 unit
Much better than expected, although you still can't make calls on it
Click to expand...
Click to collapse
Of course not, it's expecting to be installed on a phone not a tablet.
Not one of these units have ever implemented the standard Android way of handling phone calls.
Bit of a disappointment, really. The "Your Places" and "Saved" menus from Google Maps do not seem to be available thru Android Auto.
Has anyone created a Xposed or root hack that will allow AA apps not approved by The Google to be ran using AA? For example I have been working on a update for K-9 mail that will read my mail and let me respond from AA. However there is no way to use it outside of the emulator and Google would never approve it.
when I try to make a call it tells me "Network not available". anybody getting the same error?
fopoku2k2 said:
when I try to make a call it tells me "Network not available". anybody getting the same error?
Click to expand...
Click to collapse
From your phone? Or from an Android head unit?
I out AA on my Android head unit and it gets that error. Which is to be expected, as noted earlier by another poster, it is common for these Android units to not talk to the phone properly

music lags while using Maps

In Android Auto, When I'm listening some music from my phone and having G. Maps on the screen, there's always some lags in music when the map's moving (like in an higwith exit road)
I have a rooted Pixel 3 and a Mazda 3 2018 (Android Auto from MZD AIO)
I've seen in developper's options many options about bluetooth, what should be the best parameters?
Thanks!
I see the same thing when using my Chinese dongle on my android head unit. I've played around with developer settings in Android auto and the settings on the dongle and nothing seemed to help. It seems to be something low level in the dongle (in your case the head unit or mod app) that causes this where moving the map seems to overwhelm to the system.
Using the same headunit and phone but instead using Emils' head unit reloaded application I do not get any sound issues, even when running in 720p mode.
It seems like the issue we're seeing is more to do with the Android auto implementation in hardware/software.
Ok, I'll try it and see how it's going. Thanks

Linux/Android to HU (Kenwood DMX8019DABS) - Remote screen and touchscreen

Hello,
I wanted to change the HU in my car, and gone for something mainstream (Kenwood DMX8019DABS). Although, I did want one of the Chinese Android screens for flexibility; but not want to deal with some of the reliability and sound quality issues.
As the new Kenwood HU has screen mirroring, and I was thinking if I could have some SBC running Linux or Android and use that for geeking on. That way, I have the daily stability of a stock HU.... but can still install any Android apps I want and maintain the display and touchscreen functionality.
I understand not many other people will have the same requirements, but I wondered if anybody had tried anything similar previously?
Would a stock version of Android be able to cast to the HU?
Many Thanks

Is it possible to make an app that simulates Android Auto?

I currently use Screen2Auto and while it is working overall I'm still having issues.
I'm not a developer or anything, just an end user.
I'm curious why no one has come up with an alternative to Android Auto. I.e., an app that will run on an unrooted phone, make the car's headunit think it is interfacing with Android Auto, and allow you to mirror any app that is on your phone.
Are unrooted phones just too locked down to operate an app like this?
Is there a special key or something that the car's headunit requires for communication?
Is it just too onerous of a job to make an app like this?
Just curious. Seems like there would be quite a demand for an app like this.
https://play.google.com/store/apps/details?id=com.bitspice.automate ... this was an awesome attempt to do exactly what you are looking for. It was intended to be an AA replacement, and I was an early adopter/beta tester. The biggest problem was they were never able to find a way to get it to the head unit *legitimately*.The next biggest problem was that everytime they came up with something better than AA, Google would make changes and break it. Several times functionality would have to be changed / removed because of changes to Google's Terms of Service.
Ultimately it becomes a battle between Google's unlimited (seemingly) resources and the developer writing the app.
I'm looking for something a little different than the above. I'm looking for something that mirrors your phone's apps on the car's touchscreen.

Question The good old Android Auto Vivo Problem

Hey Guys,
i searched the Web for a possibility to get AA running on my X70 Pro+ with Origin OS Ocean....
Unfortunately there are only Posts and Threads about the X60 and other Vivo Phones and so on .
The issue seems to be the same.
Has anyone found a workaround to get AA running on Origin OS....?
I was hoping for Android 12 to get the Phone going, but no Idea what time we will get Android 12 and if Vivo sets permissions for AA then.
Cheers and greetings from Germany
Hi,
Right now, there is unfortunately no way to get Android Auto working. After Android 10 Android Auto only trigger car installation of it is a system application. Since there is not the case with Vivo and you couldn't mount AA as a system, you are out of options to make it work.
There is a slight, but really a slight option that it might work with the new Coolwalk version which will be available later this year.
Otherwise, the head unit direct version is also in preparation.
If you want the working AA now, the only realistic option is to buy an Android CarPlay dongle, or using a spare phone with older Android version as a buffer triggered from your phone hotspot (or with a separate sim card).
piskr said:
Hi,
Right now, there is unfortunately no way to get Android Auto working. After Android 10 Android Auto only trigger car installation of it is a system application. Since there is not the case with Vivo and you couldn't mount AA as a system, you are out of options to make it work.
There is a slight, but really a slight option that it might work with the new Coolwalk version which will be available later this year.
Otherwise, the head unit direct version is also in preparation.
If you want the working AA now, the only realistic option is to buy an Android CarPlay dongle, or using a spare phone with older Android version as a buffer triggered from your phone hotspot (or with a separate sim card).
Click to expand...
Click to collapse
Thank you very much for the detailed explanation
Im looking for an EZ solution too
But from my knowledge the only work around right now is root the phone and make AA an system app
which is not EZ for vivo since it does not allow to unlock bootloader
There is simply no chance to run AA with x70 pro+ now. The only viable solution are android dongles running on past Android versions and triggering car AA. Or even better - if you have or can buy cheap an Android 8, 9 or 10 phone with full gps and at least 4g ram (could be with broken screen or scratches), you can use it as an interface.
The only way to have android auto to work on your vehicle is to have the one with Funtouch OS (which I have), other than that, you will waste your time in trying to find a way to make it work..
piskr said:
Hi,
Right now, there is unfortunately no way to get Android Auto working. After Android 10 Android Auto only trigger car installation of it is a system application. Since there is not the case with Vivo and you couldn't mount AA as a system, you are out of options to make it work.
There is a slight, but really a slight option that it might work with the new Coolwalk version which will be available later this year.
Otherwise, the head unit direct version is also in preparation.
If you want the working AA now, the only realistic option is to buy an Android CarPlay dongle, or using a spare phone with older Android version as a buffer triggered from your phone hotspot (or with a separate sim card).
Click to expand...
Click to collapse
Will a dongle fix the connection issue?
piskr said:
Hi,
Right now, there is unfortunately no way to get Android Auto working. After Android 10 Android Auto only trigger car installation of it is a system application. Since there is not the case with Vivo and you couldn't mount AA as a system, you are out of options to make it work.
There is a slight, but really a slight option that it might work with the new Coolwalk version which will be available later this year.
Otherwise, the head unit direct version is also in preparation.
If you want the working AA now, the only realistic option is to buy an Android CarPlay dongle, or using a spare phone with older Android version as a buffer triggered from your phone hotspot (or with a separate sim card).
Click to expand...
Click to collapse
My head unit is after market and supports wireless. I know that my x fold won't hook up. Are you saying if I get carplay dongle I can hook my vivo wifi to it and it will work?
Sonicsoul25 said:
My head unit is after market and supports wireless. I know that my x fold won't hook up. Are you saying if I get carplay dongle I can hook my vivo wifi to it and it will work?
Click to expand...
Click to collapse
The head unit has to support Android Auto. Then you can choose from a variety of dongles. Even though they have more or less the same chip, they are different. Each producer tries to squeeze the most from the device, and they have a different approach.
Basically, you must avoid those, which don't clearly stated that some version of Android is installed. Without Android you gain nothing, it's only wireless connection - for IOS.
Most of them have Android 9 or 10, though in the last time 11 appears as well. That is really interesting, because with Android 11 you must have AA as a system app in order to trigger it on a head unit. It looks like producers now solve that issue.
And surprisingly, the core you get on the head unit, if everything goes ok, is not Android, it's IOS. In that core you have android apps including Google Play.
Since, as I said, every unit has a unique configuration, it's not possible to recommend any. The device that I bought is not in the market anymore, for example.
The very piece that you buy must play well with your car head unit and everything what is behind. And behind is a lot, managing systems for settings, audio and other customization.
You must be aware, when you connect AA dongle, it cuts every other setting related to its management out.
Therefore, the biggest issue might be that you'll lose calling via Bluetooth functionality. Because callings (and old style sms) goes different way than other features. My dongle does support calling but in limited way, without Assistant support and with custom made phone app, where the contact selection is rather difficult. And the next flaw is that it doesn't get along with my car audio system, therefore woofers are not engaged. The dongle doesn't have an equalizer, and I can't remedy it.
There is noticeable lag when starting apps and with commands, but otherwise there is no lag when running. Music, video and Gmaps function without glitches. Yes, you have YouTube, Netflix and any other video app you might be subscribed to. And video runs well with a decent resolution. You can load apps from store or as a sideload. And you can play local files, stored either in the dongle memory or on USB.
That's my experience, others may have different. You don't have necessary to buy a dongle, you can use an old phone with Android from 8 to 10 as a driver. Because, as you may already guess, your actual phone serves only as a hot spot (wireless and if you're lucky bluetooth too - tethering) to provide a signal for AA dongle.
If you want to buy a dedicated device, select one which has reviews from the users with as much as possible similar circumstances and priorities as you have.
piskr said:
The head unit has to support Android Auto. Then you can choose from a variety of dongles. Even though they have more or less the same chip, they are different. Each producer tries to squeeze the most from the device, and they have a different approach.
Basically, you must avoid those, which don't clearly stated that some version of Android is installed. Without Android you gain nothing, it's only wireless connection - for IOS.
Most of them have Android 9 or 10, though in the last time 11 appears as well. That is really interesting, because with Android 11 you must have AA as a system app in order to trigger it on a head unit. It looks like producers now solve that issue.
And surprisingly, the core you get on the head unit, if everything goes ok, is not Android, it's IOS. In that core you have android apps including Google Play.
Since, as I said, every unit has a unique configuration, it's not possible to recommend any. The device that I bought is not in the market anymore, for example.
The very piece that you buy must play well with your car head unit and everything what is behind. And behind is a lot, managing systems for settings, audio and other customization.
You must be aware, when you connect AA dongle, it cuts every other setting related to its management out.
Therefore, the biggest issue might be that you'll lose calling via Bluetooth functionality. Because callings (and old style sms) goes different way than other features. My dongle does support calling but in limited way, without Assistant support and with custom made phone app, where the contact selection is rather difficult. And the next flaw is that it doesn't get along with my car audio system, therefore woofers are not engaged. The dongle doesn't have an equalizer, and I can't remedy it.
There is noticeable lag when starting apps and with commands, but otherwise there is no lag when running. Music, video and Gmaps function without glitches. Yes, you have YouTube, Netflix and any other video app you might be subscribed to. And video runs well with a decent resolution. You can load apps from store or as a sideload. And you can play local files, stored either in the dongle memory or on USB.
That's my experience, others may have different. You don't have necessary to buy a dongle, you can use an old phone with Android from 8 to 10 as a driver. Because, as you may already guess, your actual phone serves only as a hot spot (wireless and if you're lucky bluetooth too - tethering) to provide a signal for AA dongle.
If you want to buy a dedicated device, select one which has reviews from the users with as much as possible similar circumstances and priorities as you have.
Click to expand...
Click to collapse
Thank you for the wealth of information. I Think I will just use my spare phone to run it. Until another solution arises.

Categories

Resources