Joying JY-UQ130 still viable? - MTCB Android Head Units General

Hello everyone!
Are the Joying JY-UQ130 7" head units still viable? I know they are 1 GB/16 GB units, but I don't need much other than BT streaming and terrestrial radio with a customizable interface. I don't have the MCU version yet. My searches turned up nothing recent, but I did find some posts about having to upgrade/replace the screen to take 5.1.1. Is that still the case, or are these posts old info that no longer applies?
https://www.amazon.com/1024600-Reso...=UTF8&qid=1483567944&sr=1-1&keywords=jy-uq130

Related

Aftermarket Head Units - What's Coming?

I would assume that the Pioneer NEX units will be receiving Android Auto, but those are really bloated, expensive systems that do way more than I want, and almost all of them have resistive screens.
There is currently an Alpine CarPlay head unit that seems very nice, and has exactly what I would want (except it's CarPlay). I hope they make this sucker into an Android Auto head unit when it's available.
What would be even more awesome is if it enabled whatever system (CarPlay, Android Auto) based on what was plugged in, so you and your SO could have different phones.
Anyone know any other head units that may be on the way?
You might want to check out a chinese Android head unit. They aren't exactly android auto and have their drawbacks on both the hard- and software side but they are available to buy now and are often sold dirt cheap, compared to the prices established brands will probably charge for upcoming android auto devices
Parrot RNB
Check out the first description of the Parrot RNB posted over at the Connected Car forum here. Just announced at '15 CES. It is a double-DIN, Lollipop head unit that is compatible with both Apple and Android systems, gps, OBDII (!).
Here: http://forum.xda-developers.com/showthread.php?t=2449005
I have a Kenwood ddx9902S and could not be happier.
dcdttu said:
I would assume that the Pioneer NEX units will be receiving Android Auto, but those are really bloated, expensive systems that do way more than I want, and almost all of them have resistive screens.
There is currently an Alpine CarPlay head unit that seems very nice, and has exactly what I would want (except it's CarPlay). I hope they make this sucker into an Android Auto head unit when it's available.
What would be even more awesome is if it enabled whatever system (CarPlay, Android Auto) based on what was plugged in, so you and your SO could have different phones.
Anyone know any other head units that may be on the way?
Click to expand...
Click to collapse
BPryde said:
I have a Kenwood ddx9902S and could not be happier.
Click to expand...
Click to collapse
I had the 9702s and it had several issues. Ever since my phone updated to 6.0.1 (a Nexus 6P), the audio coming out of it (spotify or GPM) was very quiet. Nothing I did fixed it. Also, when using Android Auto, once an overlay sound (notification, Google Voice Search) happened, the audio would have this audible static in it during bassy notes, only fixed by rebooting the head unit.
I even got a replacement head unit and it had the same issues.
I ended up getting a Joying Android 4.4.4 head unit instead of Android Auto. So far I am really impressed. The screen is really good, the sound is great, and it's got full Android as the head unit's OS.

mtcb stock/maylay roms 6.0.1 bluetooth error

As soon as my phone updated to 6.0.1 the bluetooth for phone connection connects for a few seconds and then cuts off. It seems to be very repeatable across phones and radios as until a week ago I had 2 mtcb devices both running 4.4. I have not tried the maylay 5.1 for mtcb devices yet, as I would have to set up everything for the wifey again on hers.
This does not happen with the mtcd devices with 5.1.1. It connects fine. I may just have to put 5.1 on hers to make my phone connect.
I have the joying 10.1 universal. If anyone wants to know what I think of this unit because I saw some questions about it, it seems fine. The stock software sucks and is slow. It has no micro usb ports although the rom thinks it does. Guessing they are just not plugged in. The stock microphone is 1000% better than I have seen on any other unit. I have had GS KGL and now a joying. There is no reason for an external. Even google understands me.

Considering Android Auto and have some questions

I am thinking about replacing my car stereo with an android head unit.
I have been reading the forum but do have some open questions:
1. How good are these head units?
2. Most head units seem to run older versions of android so I am concerned that the playstore and apps are not going to be supported for much longer. Which headunits are somewhat modern (good specs) with good developer support. I assume there are no treble supported headunits yet?
3. My primary use case for an android headunit are:
- listen to podcasts (PocketCasts?)
- GPS navigations (Google Maps or Waze)
- see my reverse camera when backing up
- listen to music (Pandora, Spotify, youtube, or stored music)
- listen to the radio (probably nice to have)
4. I am planning to get a dashcam and I saw that some headunits integrate with dashcam + reversing camera
5. Would be nice to be able to use a Bluetooth or something remote on the steering wheel. Ideally something discreet/small that can be glued to the back of the steering wheel ...
6. I am not planning to install a separate SIM card in the head unit (thanks ridiculous carrier prices in the US). How successful have people been getting their headunit to rely on Wifi at home and tethering to the phone when driving.
7. I saw some threads about headunits "sleeping" when the car is off - I drive an electric car, so I definitely want the unit to be OFF when the car is off. Don't care if it takes 10-30 seconds to boot.
8. Any recommendations for single DIN headunits that match the above requirements/use case? Don't need or want a gigantic screen and certainly do not want a motorized screen ... there seem to be some nice headunits where a 7" screen is mounted to a single DIN unit and the screen can be moved up and down depending on where you need it in the car.
You are actually considering an Android head unit, not Android Auto.
This is Android Auto:
https://www.android.com/auto/
Android headunits have several dedicated sections here:
https://forum.xda-developers.com/android-auto/android-head-units
https://forum.xda-developers.com/android-auto/mtcb-android-head-units-qa - for older units running Android 4.4 or 5.1
https://forum.xda-developers.com/android-auto/mtcd-discussion-questions-development - for newer units
Since you do not seem familiar with Android headunits and their specifics I strongly advise against gambling on Chinese units. Getting an Android Auto/Car Play compatible unit from an established manufacturer (the Sony XAV AX-100 seems pretty popular) would be a much safer option at similar price.

Help identifying unit

In my other cars, I have simple 2 DIN Android units which are easily identifiable and I have flashed different ROMS and MCU firmware to those to get the desired interface and features that I needed..
But with the new unit I purchased for my 2003 Mazda 6, I am having trouble working out what type of unit it is.. I have no idea if there are other ROMs available, or different MCU versions. I would like to figure this out, so I can potentially work on fixing some of the little annoyances that this unit has.
The unit was purchased from AliExpress here.
I have attached screenshots of the details in the settings app, and the 'car settings' app also.
Overall, the unit is very responsive, and the software isn't too bad.. but it has a few issues i'd like to attempt to fix.
Any help identifying it, or links to any MCU firmware or Android ROMs for it would be appreciated.
Thanks
The main issue I want to resolve, is the 'cold boot' each time I start the car..
Now, I have noticed that when turning off the car, the stereo backlight is turned off (yet the LCD is still on, and can be seen if there is light from the correct angle, and the touchscreen still works) and the stereo doesnt actually 'shutdown' until around 8-10 seconds later. This leads me to believe that its possible to configure the unit to not shutdown, but instead 'sleep'.
Would I be correct in assuming that the MCU is in control of the unit being sent the shutdown signal? Therefore, I would need a different MCU firmware to be able to achieve my goal?
I've seen lots of different MCU and ROM versions for other units, so surely there is some for this unit also.
I cant help you I m afraid, apart from telling you that they are deffo not MTCB/C or MTCD/E units.
As Typos1 has said, it's not an MTCx unit.
I did find some info here: http://4pda.ru/forum/lofiversion/index.php?t877165.html
marchnz said:
As Typos1 has said, it's not an MTCx unit.
I did find some info here: http://4pda.ru/forum/lofiversion/index.php?t877165.html
Click to expand...
Click to collapse
Sorry for the late reply.. Im going through that post now (using Google Translate) but its hard to figure out what I need to do..

Looking for the Android Auto headunit Apk/protocol

Hi,
I have a 2015 Audi A3, which unfortunately didn't come with AA as an option (I think it was introduced in 2017). It's a real pain to install the 2017 MMI into an older car, but there are guys out there developing aftermarket Android-based headunits that basically put a whole android "phone" in the dash; which isn't a very eloquent solution and kind of overkill in my opinion. They've got their own SIM cards and you have to change the bluetooth devices the phone is paired to and whatnot. It's really not exactly what I'm looking for. I just want AA and that's it.
Anyway there's one guy who's kind of got what I'm looking for . Unfortunately because the car also didn't come with a touchscreen, I have to toggle through the menus with the knobs and steering wheel buttons, which is meh. I'd love to put a digitizer overlay on the screen and play around with it, maybe have a daughter board made up and inject the screen coordinates into the packets somehow before it's sent down to the phone. I'm more of an EE, don't really have a lot of Android dev experience but I've got a lot of microcontroller and firmware experience. Anyway that's my high level idea of how this might work, not sure if I'm going in the right direction. I did ask the guy at RSNAV (seems to be a one-man show) last night if I might have the source code after signing an NDA and I'm awaiting his response. In the meantime I want to get a plan of action going.
So I'm wondering how AA is integrated on the client-side. Obviously the manufacturer headunits aren't running Android, but they've gotta communicate somehow with the phone. I can't find this info anywhere, I'm guessing this is info Google only shares with Auto manufacturers and the Kentwoods and Pioneers of the world. But maybe I'm wrong. I'm assuming it's a protobuf-based protocol between the headunit and the phone, but I don't know.
Can anybody help me out here? Thanks.
All my android auto head units are running android operating system two Chevy and one Mitsubishi. Main reason why poplar cars get rooted head units and what not. But after market android auto head unit is probably your best choice.

Categories

Resources