Hello
when my head unit starts, it always opening Music app that I really don't like...
how can I prevent it from running? there no option to disable the app (via settings), the device is not rooted so I cannot uninstall it or freeze it...
please advise (info on my head unit is attached)
thanks
Also interested to know how to do this. In my case the radio app starts automatically, which is pretty annoying because it starting on a frequency that we do not have broadcast on (87.5 Mhz). Which gives you a really noicy start on your drive...
Thanks
I've know it's possible only with root, but it seems there's no way to connect the kit for a laptop for rooting...
Can tools like OneClickRoot or similar work perhaps? Tried to contact seller of head unit, but do not quite understand the more technial aspect of android or programming of it.
Oneclickroot supposed to work, but nothing is happening when I plug the unit to my laptop... I've ordered a male-to-male usb cable to try maybe the rear usb ports will work... Waiting for eBay package...
You can root the 4.4 units by just using a specific password, check the Wiki.
Also you can disable apps in 4.4 without root (not all apps can be disabled tho).
The headunit will start playing whatever source it was last playing when it was turned off, so you can exit the radio app if you'd like, also it shouldn't start at 87.5 unless you left it on that freq, make sure the acc and constant power wires are correct and you aren't resetting the unit.
@jakejm79 mine is 4.1.1 not 4.4...
Hey,
I've finally managed to root the device!!
Instructions
* On the device, download `Root Master 2.1.1` on this URL: Root_Master_2-1-1.apk
* Make sure internet connection is active, `Root Master` downloads instructions depending on the device you have
* Open `Root Master`, refuse the update (last version of root master will not work)
* Click the big button where it is written “ROOT”
* Wait, it will ask you to install an app, install it (otherwise it will keep you asking that)
* Wait again, at the end a message popup, click the purple left button, it will reboot the device and install SuperUser (right button is for rating)
* Your device is Rooted !
Pretty easy !
taken from from:
http://forum.xda-developers.com/showthread.php?t=2660662
So I did managed to freeze Music.apk using titanium backup.
now I'm searching for the best music player (any suggestions beside Poweramp?)
and also I need to find some player that can run automatically when unit is starting and resume from last playback...
and it seems the wheel control buttons are not working with any but the native music app (the one that I was freezing)
thanks
Sooo... I have had my unit installed in my Sonata for about a year and just stumbled upon a few little gems I didn't know about. I have seen some info indicating that you can control the climate controls of the vehicle, and even have the display show when a door is open. HOW do I do this?!?!?!?
I am not using a canbus decoder, and I believe that will be the answer I need to achieve the desired result.
I was monkeying with the canbus settings in the Factory Settings menu and it has "15 HYUNDAI & KIA" with nothing selected for canbus items. I select any of the 2 options in that menu and it makes "no" difference. The middle one added an app to the application tray, but it wouldn't open.
-----------------
I also tried the IX35 and KIA5 options from the canbus menu and each of the sub items listed, and still a no-go...
Any ideas @doctorman or @Malaysk?
matt1981m said:
Sooo... I have had my unit installed in my Sonata for about a year and just stumbled upon a few little gems I didn't know about. I have seen some info indicating that you can control the climate controls of the vehicle, and even have the display show when a door is open. HOW do I do this?!?!?!?
I am not using a canbus decoder, and I believe that will be the answer I need to achieve the desired result.
I was monkeying with the canbus settings in the Factory Settings menu and it has "15 HYUNDAI & KIA" with nothing selected for canbus items. I select any of the 2 options in that menu and it makes "no" difference. The middle one added an app to the application tray, but it wouldn't open.
-----------------
I also tried the IX35 and KIA5 options from the canbus menu and each of the sub items listed, and still a no-go...
Any ideas @doctorman or @Malaysk?
Click to expand...
Click to collapse
I'm not any of the guys you're asking, but I can give an answer.
I've been struggling with that for the past four years and I never had it working. I've tried various can-bus decoders
like the ones you mentioned. Never had anything displayed from the can-bus.
I'm sure this has to do with the hardware from the Chinese. It's not working. The SPDIF interface-box works, hence
I can use the factory amplifier. I even tried various apps I've found, but again, nada. I've at least 6 can-bus decoders for I40, IX35 and so on.
Reason being that I've requested can-bus function when I've been buying HU's. I also have complained several times, but silence is the word from
the Chinese sellers.
If you ever find a solution, please tell.
halloj said:
I'm not any of the guys you're asking, but I can give an answer.
I've been struggling with that for the past four years and I never had it working. I've tried various can-bus decoders
like the ones you mentioned. Never had anything displayed from the can-bus.
I'm sure this has to do with the hardware from the Chinese. It's not working. The SPDIF interface-box works, hence
I can use the factory amplifier. I even tried various apps I've found, but again, nada. I've at least 6 can-bus decoders for I40, IX35 and so on.
Reason being that I've requested can-bus function when I've been buying HU's. I also have complained several times, but silence is the word from
the Chinese sellers.
If you ever find a solution, please tell.
Click to expand...
Click to collapse
I don't like that answer....please try again :crying:
I want to be able to control the climate controls for the system because I want to design an application that would pass commands to the controls for weather related activity... For instance, remote start the car in the middle of winter w/ frost on the window (below ~34F normally), and it will switch to defroster, and activate the rear defrost. Or when it is hot out, it will turn on the A/C to full, and make sure econ and recirculate are off.
If it has access to manage the climate controls it should be able to access the onboard temperature sensor to have all of the info I would need...
matt1981m said:
I don't like that answer....please try again :crying:
I want to be able to control the climate controls for the system because I want to design an application that would pass commands to the controls for weather related activity... For instance, remote start the car in the middle of winter w/ frost on the window (below ~34F normally), and it will switch to defroster, and activate the rear defrost. Or when it is hot out, it will turn on the A/C to full, and make sure econ and recirculate are off.
If it has access to manage the climate controls it should be able to access the onboard temperature sensor to have all of the info I would need...
Click to expand...
Click to collapse
For that purpose you've dedicated stuff already working. e.g https://www.viper.com/car/remotestart/
halloj said:
For that purpose you've dedicated stuff already working. e.g https://www.viper.com/car/remotestart/
Click to expand...
Click to collapse
I currently use a Viper system for remote start/etc... It doesn't have that functionality... You can hard wire a pulsed signal or constant +/- signal over a couple extra channels to do things like roll up the windows, or turn on rear defrost. It does sense the temp using an onboard sensor, but will not adjust the temp or level of the fan without causing a wiring headache, even for the most advanced installers. That also includes units that have a dball or one of the other devices that uses canbus to communicate w/ the car, as I do with the SmartStart device I have installed.
I emailed Joying again yesterday to ask about UL128N2, and they responded by adding the unit to their webpages and accepting orders.
Canada website (Canadian $):
http://www.joying.ca/best-joying-ne...t-pip-sleep-model-bluetooth-4-0-dab-obd2.html
Global website (US $):
https://www.carjoying.com/new-andro...h-4-0-gps-navigation-professional-head-u.html
and the website is down. As usual.
If the website isn't down, it's their forum. Sigh.
morgish said:
and the website is down. As usual.
If the website isn't down, it's their forum. Sigh.
Click to expand...
Click to collapse
Well its back up now. Or at least its working for me.
Sometimes international routing through the great firewall can be a bit.... spotty.
Has anyone bought already?
Is it better than the ones with bezel and volume knob?
KamaL said:
Has anyone bought already?
Is it better than the ones with bezel and volume knob?
Click to expand...
Click to collapse
My two units arrived. Played with one of them on the kitchen table late last night.
The row of capacitive buttons are thoroughly pointless -- touches to them don't register at all if your finger doesn't touch it absolutely perfectly.
Having said that, I like them better than the one with the knobs, for the reason I've already mentioned to you -- the lack of deep bezels.
Better? It is definitely a matter of preference. I don't need the capacitive button row, so that doesn't bother me at all.
Note: they have this weird dot thing stuck in the UI as configured by default. Touching the dot brings up a set of buttons -- back, home, menu, etc. So.... CHINA. Obviously, unless you have AT LEAST three copies (SystemUI header bar, row of buttons, the weird dot thing, steering wheel controls) of every button, somebody is going to miss it. Fortunately, there is a control application in the application menu that allows you to disable the stupid dot.
doitright said:
My two units arrived. Played with one of them on the kitchen table late last night.
Click to expand...
Click to collapse
I am sitting on the fence with this purchase, any-chance you could do a video review with these units?
doitright said:
My two units arrived. Played with one of them on the kitchen table late last night.
The row of capacitive buttons are thoroughly pointless -- touches to them don't register at all if your finger doesn't touch it absolutely perfectly.
Having said that, I like them better than the one with the knobs, for the reason I've already mentioned to you -- the lack of deep bezels.
Better? It is definitely a matter of preference. I don't need the capacitive button row, so that doesn't bother me at all.
Note: they have this weird dot thing stuck in the UI as configured by default. Touching the dot brings up a set of buttons -- back, home, menu, etc. So.... CHINA. Obviously, unless you have AT LEAST three copies (SystemUI header bar, row of buttons, the weird dot thing, steering wheel controls) of every button, somebody is going to miss it. Fortunately, there is a control application in the application menu that allows you to disable the stupid dot.
Click to expand...
Click to collapse
That dot was terrible. I also disabled it immediately, thankfully they gave an easy option to turn it off, unlike many of the other things that are obfuscated(such as disclosing to owners the hardware keycombo to boot into recovery).
Upon receiving my unit the capacitive buttons weren't always responding even when pressed perfectly, but after holding down RST till reboot they haven't had the issue again.
When inquiring about a larger touch area for the capacitive buttons I got "Hi friend, Nice day Yes, you can choose the bigger or small touch area in below settings:" with this picture attached.
Increasing the delta values in Settings of the Key Study app doesn't seem to do a whole lot but I think the trigger area is a bit bigger. Unfortunately the border values are for the entire touch screen not per button area.
tally3tally said:
I am sitting on the fence with this purchase, any-chance you could do a video review with these units?
Click to expand...
Click to collapse
No. I don't do video.
rcll said:
That dot was terrible. I also disabled it immediately, thankfully they gave an easy option to turn it off, unlike many of the other things that are obfuscated(such as disclosing to owners the hardware keycombo to boot into recovery).
Upon receiving my unit the capacitive buttons weren't always responding even when pressed perfectly, but after holding down RST till reboot they haven't had the issue again.
When inquiring about a larger touch area for the capacitive buttons I got "Hi friend, Nice day Yes, you can choose the bigger or small touch area in below settings:" with this picture attached.
Increasing the delta values in Settings of the Key Study app doesn't seem to do a whole lot but I think the trigger area is a bit bigger. Unfortunately the border values are for the entire touch screen not per button area.
Click to expand...
Click to collapse
That one looks like the buttons (and their corresponding areas) are considerably larger than with the 7". They are surprisingly small on this! I might see if I can disable them altogether, since I suspect that it would likely interfere with "slide finger in from left" gestures.
Ok, so got the thing installed last night.
Well, sortof.
Seems that China can't make up its mind regarding how far the front of the radio sticks forward relative to the mounting holes. So my first attempt to mount it resulted in the radio's face sticking so far forward that my DDIN face plate wouldn't have been able to make it down to the dashboard.... assuming that the holes fit. More on that later.
Second attempt, I moved the radio back to the next set of holes on the mounting bracket, which are a bit more than 1/2" behind the holes that I had the UL135 mounted with. Ok, well depth is *better*, but now a bit too far back. Middle of the night, so as long as I can use the thing to route my way to work in the morning, I'm ok with that. Maybe on the weekend, I'll drill another set of holes about half way between the two sets I tried so far. That should line it up OK.
So the DDIN sizing. Another thing that China can't make up its mind on. The UL135 fit in the Toyota Tacoma Metra dash kit... very snugly in horizontal direction, roughly 1mm clearance in the vertical direction. This UL128N2 is about 2-3 mm too big to fit in that dash kit in BOTH directions. They *claimed* the UL135 to be 100mm x 178mm. They *claim* the UL128N2 to be 102mm x 178mm. I will tell you that the UL128N2 is WIDER than the UL135, despite the claimed equal width. And given the 2mm (actually more) increase in height and that I had at least 1mm of available vertical space, I *should* have been able to force it in. NOPE. The difference is much greater than that, and in both directions. If the UL135 really is 100mm x 178mm, then the UL128N2 is probably 104mm x 180mm. WHY? Oh, the reason is absolutely HILARIOUS, it is because they have a thin plastic ring around the glass digitizer. They ordered the GLASS to have dimensions matching the DDIN target, but didn't compensate for the thin (~1mm) plastic ring around it! Very typical of the way that China manufacturing works. Ok, so I was able to grab a file and open up the dash kit a little bit to make it fit, and now its ok.
So next up... actual functionality.
First observation; the AM radio frequency standard is set to something that is most decidedly NOT North American standard. The closest frequency I could get to my preferred station was off by 2 kHz. While it was adequate to get the station and understand, without TYPICALLY an overabundance of noise or added sound from the next station over, it definitely sounds bad. Thanks so much China, for giving me a well working AM radio tuner! With any luck, I'll be able to hack the program to tune the proper frequencies.
On the physical utility of the unit, when you look past the "size" issue, its not bad. As expected, the screen is much more convenient without the deep bezel around it as the UL135 had. In order to achieve this, they replaced the physical control buttons with a row of capacitive buttons. Those buttons are pretty well useless, you can't reliably press them without focusing carefully on them. That is what is often called "distracted driving". I would go so far as to say that this row of buttons is DANGEROUS to try to use. Not only that, but the row of buttons is ***COMPLETELY REDUNDANT***. After all, they are just duplicates of the home/back/volume buttons that are already present on the SystemUI upper panel anyway, and, of course, the STEERING WHEEL BUTTONS (for those who have them hooked up). Why did they even bother to include that row of buttons? Because.... CHINA! Oh well.
Next up; there are some serious bugs when it comes to AUDIO ROUTING. If the radio is playing, and GPS voice comes on; radio mutes. Oh, it STAYS muted until you go BACK into the radio application, which seems to trigger a reset of the audio routing. This improved once I set google maps as the default nav application, now it just volumes down the radio to "pretend" to play the GPS sounds, and volumes it back up after.
Well, starting with the "included" ancient version of google maps... while it does make sound, it gets clipped by about 3 seconds at the start of the sound. So you miss about the first 3 seconds of the instruction. Update google maps to the latest version, and no sound comes out at all. Ok, what is happening with the newer one is that it is trying to use an audio pathway that is obviously BROKEN on these units. So that means that there isn't going to be any voice nav from google maps until either (a) THEY fix the audio routing problems, or (b) WE fix the audio routing problems. I'm not sure yet if there is an audio routing policy file that we can configure, or if this is something hard baked in somewhere. That's very annoying, but something I can live with for now. I prefer the newer google maps enough to live with the lack of voice guidance, rather than to try to use the ancient version.
DPI: Obviously, Android believes that the screen is as large as a TELEVISION. The fonts are all incredibly small, even if you set it to HUGE font. Ok, so right angle triangle has H = root(1024*1024+600*600)=1186.83 pseudopixels. Divide that by 7, makes 170 DPI. Its set to 160 DPI, so Android thinks that the screen is 7.4 inches. Ok, that's not really too far off from reality, but it IS in the wrong direction, to make everything look SMALLER than it should be. The problem is that the screen is roughly 3 feet away from your face. Take a tablet and how far do you hold it away? Roughly 1.5 foot. So lets figure out how big Android should *THINK* the screen is, in order to blow things up to the same scale as a 7" tablet at 1.5 foot.
We're dealing with right triangles again, 7:3 = x:1.5, x = 3.5. Android should think that the screen is 3.5 inches. That puts it up at 338 DPI. Ok, so these numbers are pretty rough, since I'm just guessing the viewing distances, but you get the idea. Crank that DPI WAAAAAAAY UP! Only problem I see, however, is regarding how they coded the SystemUI. If they followed the Android design guidelines, then they coded it with DP's (density independent pixels), which means that when you crank the DPI far enough to make applications look proper, it will make the CHINA look HUGE. Think about it -- they designed their SystemUI panels to show at a "normal" size when the DPI is set way too low. I can see bad things happening.
I wonder if it would be practical to just SWAP OUT the chinese SystemUI for one built from source? That might actually be a practical way of repairing the UI. Might also be nice to rebuild the System Settings application from source. I'll have to go over it again, but I don't recall there being anything special about System Settings -- they just colorized it, broke the bluetooth part, and added a password to developer options. WHY???!?!
Like the American proverb says... "if it ain't broke, don't fix it!" That ESPECIALLY goes for China, since if it ain't broke, they're GOING to break it.
And now, to BLUETOOTH.
Well, knew going into it that they futzed up the bluetooth settings as badly as they possibly could. Why? Because... CHINA. The good news is that they tried so hard to break it as badly as they could, that it was EASY to fix.
In fact, I had written up the most important fix WELL before I even had these head units. I will refer to my fix thread HERE: http://forum.xda-developers.com/and...elopment/bluetooth-settings-launcher-t3504526
There are two obvious problems with bluetooth on these units;
1) They deleted the System Settings button that brought up the Bluetooth settings. That is what I fixed in above thread.
2) They BROKE the bluetooth pairing pin prompt. On a normal Android device, when you try to pair with something from it, it will first try one or two "standard" pairing pins, and they don't work, then it will pop up a dialog requesting that you enter the device's pin. This one does NOT do that. It JUST tries to pair using whatever pin is hardcoded in the CHINESE bluetooth application. So while I haven't "fixed" this, there is at least a reasonably easy (if not particularly convenient) workaround. When it doesn't pair, you go into the chinese bluetooth application, change the pin there, and try again.
So the good news is this; the REAL MEAT of the bluetooth stack, is the product of INTEL. Not China. That means that once you work around the severely broken UI (again, WHY BREAK it when you can just leave it be and have it ACTUALLY WORK?), it actually works WONDERFULLY! That means you can connect to AND USE multiple devices at the same time. I.e., torque + **ANY** OBD device, while simultaneously a voice call AND bluetooth data tethering.
Hmm, what else....
Bootup.... this is a very dramatic change from the UL135.
A full bootup takes about 20 seconds.
So when you get into your car in the morning to go to work, after it has been sitting all day, you turn the key, and it is IMMEDIATELY UP. Wait, what? Its wired correctly -- if the +12 and IGN were reversed, then it would lose power with the ignition switch off, which means that it would have to do a full bootup. If the IGN wasn't connected at all, then the screen will never turn on -- when the IGN turns off, the screen goes off, radio stops playing, and another thing I observe, is that bluetooth connections are lost. So, either the thing is only doing a partial shutdown and proceeding to "drain the battery" mode, or they have actually made it sleep *correctly*, switch off all the parts that suck down the power, put the CPU into deep sleep (clock off), and sit there draining negligible power until it receives a wakeup interrupt (IGN line powers up). If that is so, then I am VERY pleased, at least with this element.
On performance and stability;
Its better than the UL135 across the board here. This thing is no rocket, the CPU is actually quite a TURD, though definitely better than RK3188 (despite lower benchmarks). The increased RAM helps with keeping things in memory and responsive. The stability is a night and day improvement over the UL135, which I believe to be attributable to the INTEL element. eMMC performance is abysmal.
Summary so far;
1) The front panel is bigger than DDIN.
2) The front panel sticks out a different amount than UL135.
3) The audio routing policy is BORKED.
4) The UI is ALL CHINA.
5) The Bluetooth stack is INTEL
6) Performance is "OK". Nothing special.
7) Wakeup after sitting all night is INSTANTANEOUS.
More on the GMaps audio routing.
While I haven't yet tried out the latest system update, I HAVE found a way to make GMaps actually speak.
Unfortunately, the "way" is by being on a PHONE CALL.
Yep. When you're on a PHONE call, google maps is HAPPY to speak to you. In fact, the damned thing will NEVER SHUT UP. Obviously. When better to harass you then when you're trying to listen to someone else? Or when you're trying to speak, since it shuts off the microphone in order not to echo back the nav prompts.
(fortunately, there is a setting to tell it not to issue nav sounds during call).
Oh yeah, gmaps also speaks LOUDER than the phone call.
EDIT: people on the joying forum are indicating that the newest update will fix the gmaps voice.
Ok, on to the December 8th UPDATE.
First off, I have NOT really run the update yet. Supposedly, it fixes the GMaps sound problem.
I can confirm that they have NOT (yet) caught on to Blueballs.apk that I wrote (and shared) to regain access to the System Settings --> Bluetooth activity, so bluetooth functionality has not been degraded.
First the install process;
Take their install archive and EXTRACT it to a uSD or USB disk. Either is fine. I used USB.
msdos type partition table, ONE partition, formatted as fat32.
Power on the vehicle, stick in the card or USB, and wait until it prompts you to install the update.
Now is where things get scary....
Starts by updating the MCU, fine, then proceeds to update the Android image. The progress bar moves about a 3rd of the way across, and STOPS. And it just sits there. For about 10 minutes. The only indication that the device isn't completely crashed out is that the little websphere thing is still spinning in the little robot's hands. Ok, eventually it goes, then it says to yank out the disk and it will reboot itself. OK, no problem.
You do it. And it reboots. It plays the boot animation, right up to the last frame... and stops. It just sits there saying "ANDROID" across the screen. Now you're thinking to yourself that THIS THING IS JAMMED UP AND YET WE HAVE NO WAY TO GET INTO RECOVERY!!!!! Crap. Ok, lets just let it be. It sits, and it sits, and about 15 minutes later, the panel lights go out. Ok, at least something changed. Wait another minute and it finally boots. So WHAT THE BLOODY HELL CHINA? Obviously, it must have been optimizing application number 27 of 258, so WHY DID YOU DELETE THE PROGRESS DIALOG, CHINA? WHY?????
So it boots back up, and you notice something funny right off the bat. It has returned to the china launcher. Ok, that's minor. Keep on moving, we can reset it to google launcher momentarily. So now you go into something like k9mail, and it asks you to sign in.
HUH?
But the program remained installed.
THE BLOODY MORONS..... THEY DELETED EVERYTHING FROM /data/data/. They kept /data/app/, but they deleted /data/data/. So everything you've set up now has to be reset. GEE, THANKS SO BLOODY MUCH, CHINA.
So my suggestion... if you're going to update to the Dec8 system image, the sooner you do it, the less of your settings you will lose, because the less of your settings you will have actually SET.
Quick observations;
1) They have NOT fixed the frequency selection on the AM radio. I'm still stuck 2 kHz away from my target frequency.
2) There were THREE phases to the system install; MCU, Android, and "Allapp.pkg".
3) Allapp.pkg contains Settings.apk. Yet there was a Settings.apk in the Android update. Hmmmmm..... wonder if we could just force back the REAL Settings.apk and have a proper functioning system?
4) Allapp.pkg *also* has a SystemUI.apk. Could it be? Could the one in the Android update actually be... no, it couldn't. There's no way that they would actually *include* an AOSP SystemUI, is there?
This is the list of all of the apk files in Allapp.pkg:
Code:
EasyConnectedFY07.apk
assets/CarMan.apk
assets/CarManNotChinese.apk
assets/EasyConnServer.apk
Gmail2.apk
JY-1-C9-BT-V1.0.apk
JY-1-C9-Guide-V1.0.apk
JY-1-C9-Launcher-V1.0.apk
JY-1-C9-MUSIC-V1.0.apk
JY-1-C9-Radio-V1.0.apk
JY-1-C9-Video-V1.0.apk
JY-2-C9-Launcher-V1.0.apk
Maps.apk
PlatformServerSofia.apk
Settings.apk
SFY-1-C9-Steer-V1.0.apk
Sofia-1-C9-Aux-V1.0.apk
sofia-1-C9-CarMark-V1.0.apk
Sofia-1-C9-FileManager-V1.0.apk
Sofia-1-C9-Gallery-V1.0.apk
Sofia-1-C9-RightCamera-V1.0.apk
Sofia-1-C9-Server-V1.0.apk
Sofia-1-C9-TV-V1.0.apk
SystemUI.apk
SYU-1-5009-FloatBtn-V1.0.apk
SYU-1-C9-Calculator-V1.0.apk
SYU-1-C9-Caliration-V1.0.apk
SYU-1-C9-Canbus-V1.0.apk
SYU-1-C9-CarRadio-V1.0.apk
SYU-1-C9-CarUi-V1.0.apk
SYU-1-C9-Graphics-V1.0.apk
SYU-1-C9-Navi-V1.0.apk
SYU-1-C9-SubServer-V1.0.apk
SYU-1-C9-UIServer-V1.0.apk
SYU-1-C9-Update-V1.0.apk
SYU-1-C9-Widget-V1.0.apk
SYU-2-C9-CMSettings-V1.0.apk
SYU-2-C9-EQ-V1.0.apk
Notice... CarMan.apk and CarManNotChinese.apk, LOL.
Oh, and "SYU-1-C9-Caliration-V1.0.apk" is also pretty cool.... ***CALIRATION***
doitright said:
My two units arrived. Played with one of them on the kitchen table late last night.
The row of capacitive buttons are thoroughly pointless -- touches to them don't register at all if your finger doesn't touch it absolutely perfectly.
Having said that, I like them better than the one with the knobs, for the reason I've already mentioned to you -- the lack of deep bezels.
Better? It is definitely a matter of preference. I don't need the capacitive button row, so that doesn't bother me at all.
Note: they have this weird dot thing stuck in the UI as configured by default. Touching the dot brings up a set of buttons -- back, home, menu, etc. So.... CHINA. Obviously, unless you have AT LEAST three copies (SystemUI header bar, row of buttons, the weird dot thing, steering wheel controls) of every button, somebody is going to miss it. Fortunately, there is a control application in the application menu that allows you to disable the stupid dot.
Click to expand...
Click to collapse
I have the 10" version and I got the buttons to work 100% after relearning the touch keys. Open "carmediasettings" then click on Panel keys assignment. Hope that helps =)
xlinkx said:
I have the 10" version and I got the buttons to work 100% after relearning the touch keys. Open "carmediasettings" then click on Panel keys assignment. Hope that helps =)
Click to expand...
Click to collapse
The issue on the 7" isn't the button calibration, just the physical size of the touch areas.
Doesn't matter anyway, since the buttons are all available in other places -- systemui bar and steering wheel.
So today installed the second UL128N2 into the wife's Subaru Forester.
Popped out a parrot asteroid smart (obsolete). The dimensions of the parrot are about a full quarter of an inch in both horizontal and vertical directions. Really had to do a job on the ddin dash adapter on that one, but fortunately was able to avoid having to cut up the actual dashboard.
doitright said:
Summary so far;
1) The front panel is bigger than DDIN.
2) The front panel sticks out a different amount than UL135.
3) The audio routing policy is BORKED.
4) The UI is ALL CHINA.
5) The Bluetooth stack is INTEL
6) Performance is "OK". Nothing special.
7) Wakeup after sitting all night is INSTANTANEOUS.
Click to expand...
Click to collapse
Any news on the instantaneous wake up after a full night? No car battery issues after several nights? I would be very interested in measurements of power consumption when the car is switched off.
Regarding the small font settings, would you suggest to buy the 8" unit if it fits in the car? I guess that the UL138N2 has the same hardware as the UL128N2 only with an 8" screen? And I hope that it has also the instantaneous wake up?
Sent from my SM-N910F using XDA-Developers mobile app
nomailing said:
Any news on the instantaneous wake up after a full night? No car battery issues after several nights? I would be very interested in measurements of power consumption when the car is switched off.
Regarding the small font settings, would you suggest to buy the 8" unit if it fits in the car? I guess that the UL138N2 has the same hardware as the UL128N2 only with an 8" screen? And I hope that it has also the instantaneous wake up?
Sent from my SM-N910F using XDA-Developers mobile app
Click to expand...
Click to collapse
No, I wouldn't suggest that. I would just suggest changing the DPI setting on the 7" to something more suitable.
The UL138N2 WILL NOT fit in a DDIN dash adapter. Its basically a DDIN *box*, with a TABLET bolted out in front of it. Unless your car is an ugly beater, you probably won't want to install something that ugly into it.
As far as overnight power consumption, I have not had any opportunity to test more than a 24 hour stretch. No issues, nor, frankly, do I expect any. They appear to be sleeping the unit correctly, so all of the wireless signals are turned off, and CPU is in clock stopped mode, so like a good quality tablet with the wifi turned off, it'll go for months like that. On a battery as big as a car has, possibly years (assuming that the car battery didn't self discharge in that time, which it will).
doitright,
With your help I was able to get full system menu. Thank you! I was wondering if you were able to get "Ok Google" to work on any screen. It only works on the home screen for my 10" head unit.
xlinkx said:
doitright,
With your help I was able to get full system menu. Thank you! I was wondering if you were able to get "Ok Google" to work on any screen. It only works on the home screen for my 10" head unit.
Click to expand...
Click to collapse
I have no interest in retard mode, so no. I have not.
doitright said:
DPI: Obviously, Android believes that the screen is as large as a TELEVISION. The fonts are all incredibly small, even if you set it to HUGE font. Ok, so right angle triangle has H = root(1024*1024+600*600)=1186.83 pseudopixels. Divide that by 7, makes 170 DPI. Its set to 160 DPI, so Android thinks that the screen is 7.4 inches. Ok, that's not really too far off from reality, but it IS in the wrong direction, to make everything look SMALLER than it should be. The problem is that the screen is roughly 3 feet away from your face. Take a tablet and how far do you hold it away? Roughly 1.5 foot. So lets figure out how big Android should *THINK* the screen is, in order to blow things up to the same scale as a 7" tablet at 1.5 foot.
We're dealing with right triangles again, 7:3 = x:1.5, x = 3.5. Android should think that the screen is 3.5 inches. That puts it up at 338 DPI. Ok, so these numbers are pretty rough, since I'm just guessing the viewing distances, but you get the idea. Crank that DPI WAAAAAAAY UP! Only problem I see, however, is regarding how they coded the SystemUI. If they followed the Android design guidelines, then they coded it with DP's (density independent pixels), which means that when you crank the DPI far enough to make applications look proper, it will make the CHINA look HUGE. Think about it -- they designed their SystemUI panels to show at a "normal" size when the DPI is set way too low. I can see bad things happening.
Click to expand...
Click to collapse
I tried some changes to the dpi in build.prop. I went up to 180 and the ui looks alright still. Then I decided what the heck and went to 300 since my galaxy s5 is at 480...bad idea. The screen gets stuck on the kill apps screen and you can't open anything. Luckily I was able to open es file explorer using adb and edit the build.prop. After rebooting, all os well again.
Moral of the story, don't try anything over...maybe 200?
I thought it would be better if we consolidated all the discussion on the PX5 head units into a single thread and I will try my best to group all the useful information in the first few posts when more information becomes available. I think this will help with discussion on these head units and help improve everyone's experience
Post 2: Firmware
Post 3: Tips, Tricks and Fixes - Rooting instruction here
Post 4: Bugs/Issues
Post 5: Useful apps
Post 6: Useful links
For those not familiar with the PX5 Head unit, the specs are below:
OS: Android 6.0 Marshmallow
CPU: Rockchip PX5 A53 Octa-Core
RAM: 2GB DDR3
ROM: 32GB
Audio output: 4*45W
Features:
Built-in Radio Tuner (RDS Enabled) (18 FM and 12 AM stations Preset)
Built-in USB & SD Slot
Region Free DVD Player
Screen Mirroring
Steering wheel controls (SWC) and Canbus interface
Optional compatible accessories:
DAB+ USB Tuner
TPMS
4G/3G Dongle
OBD02 Module
Camera
DVR
External Mic
The head unit comprises of two parts:
a MicroController Unit(MCU) board, which controls physical buttons and A/V inputs/outputs to/from the headunit. This board interacts with Android OS.
ANDROID part. The main Operating System.
Both MCU and Android ROM interact together to achieve the functionality of the head unit.
Manufacturers/reseller:
GS - XTRONS
HA - HotAudio/Dasaita
KGL - Erisins
MX - Witson
LM - Erisins/Pumpkin
A comparison between PX3 and PX5 can be found posted here by @FauxDreams with some previous discussion on PX5 in that thread as well:
PX3 Vs. PX5 initial impressions, some issues/findings after a day of ownership etc
Some information I found on the CPU:
Rockchip PX5 Press Release
*Warning: Do not install 1024x600 fw on 800x480 HU*
It has been reported that it will not display properly once installed.
An update usually consist of two files:
The Android ROM (update.zip) and it is usually compatible with any head unit of the same model (MTCD) and CPU (PX5).
The MCU (dmcu.img) is specific for each manufacturer and it should never be updated on other manufacturer's MCU update file (unpredicted response from physical buttons - or CAN bus responses, or bricking the unit).
However, it has been tested and confirmed that JY, KD, GD and now HA MCU are cross-compatible Verified cross compatible MCU thread (thanks for info @marchnz(
Update at your own risk!
Installation instruction:
Unzip update.img to the root of the GPS SD Card.
Make sure you Don't include the dmcu.img if your MCU does not match the MCU of the firmware.
Latest Stock Firmware/Custom Firmware/MCU:
Please refer to this thread post by @ikerg for latest up to date firmware/mcu info:
https://forum.xda-developers.com/an...x5-headunits-repository-t3619906/post72622240
Will add more info here as more tips, tricks and fixes shows up.
Rooting:
Rooting has been achieved by using the app Kingoroot. Kingoroot APK
This will root the device and install Superuser app. Internet connection will be required during the root process. As I am not a fan of superuser and kingoroot staying on my device, I change superuser to supersu and uninstalled both app. Please see steps below.
Reported to not work on hotaudio devices. It gets stuck at 10%.
SuperSU:
Install SuperSU (I used SuperSU Pro) from the play store and grant it superuser access. When prompted, install updated su binary with the normal mode. Once installed successfully, uninstall Kingoroot and Superuser app. Reboot.
Factory Settings
Password: 126
More password codes on Post #11 (again, thanks to @drukhadze)
Xposed:
https://forum.xda-developers.com/an...-unit-discussion-thread-t3573881/post71770240
Screen DPI:
Some apps, does not display properly with the screen DPI set at 240. Spotify for example has the login button missing. I use a DPI changing app to change the DPI to 200 to make Spotify login button reappear. Check the useful app section for the app I use that allows for the DPI to be changed on the fly without a reboot, but DPI can also be changed by modifying the build.prop
DAB+:
Updated DAB+ v1.4 app:
https://drive.google.com/open?id=0BxORzE28l_E3U01XYS04R3FENmc
Fixes stutter issue etc. Thanks to @trap63
17/04/25: https://1drv.ms/u/s!AjrY0uqbW_kBgzJa4n7w88DQ1pz2 (thanks @zapedge)
Modified DAB+ apk by @realzoulou with less bugs and even more features:
https://forum.xda-developers.com/an...b-app-realzoulous-modded-version-com-t3609608
3rd party DAB+ option:
https://forum.xda-developers.com/an...-unit-discussion-thread-t3573881/post72134396
May be a better option as runs within Android and not dependent on MCU manufacturer. You need the following:
- a DAB + stick with an RTL2832 chip e.g.
(http://www.ebay.de/itm/USB2-0-DVB-T...0T-/262943378408?_trksid=p2385738.m2548.l4275)
- RTL2832 Driver from Playstore
(https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=en)
- Radioapp Wavesink Plus DAB + FM-RDS
(https://play.google.com/store/apps/details?id=en.ses.wavesinkplus&hl=en)
Developer Options:
Standard 7 tap on build no. does not work on these head unit. To enable Developer Option, install this one:
https://play.google.com/store/apps/details?id=com.singlebyte.devshortcut
App resume after standby:
This might be an option to test https://forum.xda-developers.com/an...-unit-discussion-thread-t3573881/post71950009
As bugs/issues are confirm by other members, I'll add to this list.
Bluetooth:
~ Same issue with most other MTCD head unit. The bluetooth is not able to communicate with the bluetooth devices besides the official optional accessories, or phones. I tried using my bluetooth TPMS with this and it did not work.
~ Echo during calls also reported. Might be related to both external Mic and internal mic working together.
WiFi:
~ WiFi on these units seems weak and unreliable. Issue seems to be a weak antenna, bad solder and/or no diversity soldered in. Some users have success in soldering diversity and getting better reception. Disabling bluetooth also helps as bluetooth usually use the same 2.4gHz chip and will reduce interference when disabled. A more powerful antenna also seems to help some.
Useful Apps:
Easy DPI Changer - This apps seems to allow for DPI changes to be made on the fly without reboot. I am not sure if this is because Marshmallow supports this or if the app does anything different. Have not tried other DPI app.
FM Radio Controller - Control FM radio from notifications and more features.
AnyAutoAndio - Allows more app to be controlled within Android Auto App, including FM Radio Controller above
Android Auto - Google's head unit interface/launcher
MTCD Tools - Allows you to customise all your buttons to launch custom apps or do custom actions
MTCDialer - Handsfree dialing
Graser's Dasaita Tool - Xposed module with tweaks for ODB, whitelist sleep app and speed volume
Useful Links
MTCD PX5 Headunits Repository & information (Stock & Custom) - Repository for roms and fixes. Updated more frequently by @ikerg than I do with this thread.
...
~reserved
Just had the Xtrons PX5 unit for around 3 days now and I am enjoying it. I originally had the MTCD RK3188 1GB unit that was slow and boots extremely slowly.
So far, experience been good. 2 small issues I have notice so far are that my WiFi isn't as strong as the previous unit and the station details aren't coming across to my centre display of my dash with the right info. I might try playing around with some of the factory settings and canbus options to see if it'll resolve it.
Love the fact that the HU doesn't shut down but goes to sleep and comes on instantaneously once I put the ignition key in.
Did you change HU or the motherboard?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
colostro said:
Did you change HU or the motherboard?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
head unit
I found out, there are follwing possible passwords on which factory settings has reaction
Static programmed passwords
Code:
126 - opens facotry settings app (Device customer name beginns with RM - parameter ro.product.customer).
m123456 - opens facotry settings app with bit other parameters...
adbon - enables ADB
adboff - disables ADB
keject - sets ctr_key to eject
kpower - sets ctr_key to power
hcttouch - display some touch info. probably touch panel area size in pixels
hctreboot - initiates device reboot
hctbtup - writes on screen "BT updata!" , Sends Android Intent
hctbtte + 3 digits - probably starts some tests with bluetooth adapter. but no information what this 3 digits meaning
logcls - clears logcat
logcat - executes logcat as follows [b]logcat -f <filename> -v time
filename = <external storage>/<current date+time>_android.txt
kmsg - excutes dmsg command and writes output to <filename>
filename = <external storage>/<current date+time>_kernel.txt
radio - executes logcat as follows [b]logcat -b radio -f <filename>
filename = <external storage>/<current date+time>_radio.txt
logcan - starts CAN bus logging app
1199 - enables/disables HZC_MENU . I don't know what it is
v5555 - Enables/disables Video while driving. Enable also removes "Watching video" under Car settings
hcttest + up to 3 digits - not tested yet.
There are also up to 2 passwords, which are stored on device. Action same like with password: 126 . Probably one of them set to 126.
EDIT:
On _GS Device in MCU stored passwords
Code:
126 - opens facotry settings app
3333 - opens facotry settings app, only logo change screen
Hey there
i noticed the changelog has a Kernel G sensor... can someone just help me verify if the unit comes with a G sensor/ accelerometer built in? would be fun to have that on with the OBD torque app.
Radio channel to my dash display is working now. Not sure what changes made it work. But I did turn off canbus and turn it back on.
EDIT: Issue comes and goes. Still ongoing.
New issue I found is that I'm not getting sound to the rear speakers. Might be just specific to my unit or model as I have an Audi specific xtrons model. Have emailed the seller. Anyone have similar experience?
Strange thing is that no sounds are coming through the rca cables. Even with all 4 unplugged, the front speakers still producing sound.
EDIT: RESOLVED, didn't realise the speakers are treated as amp and I needed to plug in the amp control cable.
Hello, I just updated the firmware to 20170304 and I can not get the HU to turn off completely when I turn off the car, I turn off the car and when I turn it on after several hours, the HU does not start a cold start Fast and I have the open applications of the previous session. What I can do to turn off the entire HU and when I start the car I make the cold start.
In the factory options I have here these parameters, I do not know if they will influence.
I do not know what the KNOB MODE ...
saz92 said:
Hello, I just updated the firmware to 20170304 and I can not get the HU to turn off completely when I turn off the car, I turn off the car and when I turn it on after several hours, the HU does not start a cold start Fast and I have the open applications of the previous session. What I can do to turn off the entire HU and when I start the car I make the cold start.
In the factory options I have here these parameters, I do not know if they will influence.
I do not know what the KNOB MODE ...
Click to expand...
Click to collapse
I don't have access to my head unit at the moment, but I remember seeing an option called Default power status or something like that. Maybe that will do what you want?
I prefer it staying always on but in standby.
I'm also curious about the knob mode and what that does?
Hi, received this update this morning if anyone's interested.. ?
https://1drv.ms/u/s!AjrY0uqbW_kBgxd715vm7ZcxK6yR
Ga73 said:
Hi, received this update this morning if anyone's interested..
https://1drv.ms/u/s!AjrY0uqbW_kBgxd715vm7ZcxK6yR
Click to expand...
Click to collapse
Hi mate, who is the people you are in contact to?
Can you forward a request to enable (accept) "ODB Link MX" naming in pairing? This BT is not so cheaper ($80) and therefore isn't "market destroyer" for their Xtrons ELM, they could avoid to lock BT in accordance to Google's rules for MMallow>+.
Yesterday i lost all data on both sd-cards. I think that was already second time. Have someone noticed such problem?
scubee said:
Hey there
i noticed the changelog has a Kernel G sensor... can someone just help me verify if the unit comes with a G sensor/ accelerometer built in? would be fun to have that on with the OBD torque app.
Click to expand...
Click to collapse
I don't have any G-Sensor. Elixir sees, that there is G-Sensor enabled, but no I don't get any reaction on it.
Probably hardware part is missing. Maybe some of unit versions have this sensor.
If some chip is built in, under "Extra settings" G-Sensor sensitivity setting will be displayed
aarick said:
I don't have access to my head unit at the moment, but I remember seeing an option called Default power status or something like that. Maybe that will do what you want?
Click to expand...
Click to collapse
This option has some other function. HU state while next power up
On - normal boot
Off - boot to standby mode. Display while boot disabled. No info about sound, while my HU still not installed
Memory the status of last - boot to last state
Ga73 said:
Hi, received this update this morning if anyone's interested..
https://1drv.ms/u/s!AjrY0uqbW_kBgxd715vm7ZcxK6yR
Click to expand...
Click to collapse
This is the update from ro.build.date=Sat Mar 4 09:13:37 CST 2017, same as linked in #2
Ga73 said:
Hi, received this update this morning if anyone's interested..
https://1drv.ms/u/s!AjrY0uqbW_kBgxd715vm7ZcxK6yR
Click to expand...
Click to collapse
I just downloaded and looks like update.img is the same as the 170304 one, but dmcu.img has a different date. I wonder what has changed as the change log is the same. I'll upload just the dmcu.img for anyone that doesn't want to download the whole file
Anyone can get MTCD tools working? Tried it, but it's not recognising my steering wheel buttons.
https://forum.xda-developers.com/android-auto/mtcd-discussion-questions-development/release-mtcdtools-control-music-players-t3436789
I'm assuming that it's probably written for android lollipop and doesn't work on marshmallow.