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?
My headunit (MTCB KLD6 with latest MCU 2.98 ) touchscreen is not more working properly, some upper and bottom part of the screeen is not responding to my finger touch, even tough I have managed to enter the factory settings to reset some setting such as the radio band (because I dont hear enything) it doesnt accept the "enter" comand when I press the OK button.
Also the "space" button and numbers/letter on the left bottom corner is not working when pressing the screen.
Is there anyway to make it work again??
I have also reinstalled another rom, resintalled it twice, maybe I should revert to an older MCU version?Currently I am running an MCC mcu version (kld6 2.98).
Is there any way to re-calibrate the screen??
I am so frustated.
Yes, it's really frustrating. I have the same problem with my Eunavi (MCU MTCD_LM_2.55_1, px5). Bottom of the screen (20%) doesn't respond. I also made factory reset of device, installed another ROM and changed MCU (from 2.55_1 to 2.52_1). All that things doesn't help. Because seller is not interested in helping me, in weekend i'm going to disassembly device and check connections between display and mainboard, eventually try to buy another display (digitizer ?) to replace it.
Has anyone ever suffered this problem?? Is there a way to re-calibrate the Head-Unit??
if I enter the code httouch into factory settings to check the unit resolution it says "1024*768" but my unit is a 800x480 native resolution.
I've never installed a wrong rom with incorrect resolution, I've changed serveral roms, reinstalled original MCU, but some part of the screen does not respond to finger touch...
Goaz said:
if I enter the code httouch into factory settings to check the unit resolution it says "1024*768" but my unit is a 800x480 native resolution.
I've never installed a wrong rom with incorrect resolution, I've changed serveral roms, reinstalled original MCU, but some part of the screen does not respond to finger touch...
Click to expand...
Click to collapse
If you want I have a MTCB 1024*600 touchscreen left. BTW I am from Italy too
Touchscreen change is great idea. I changed my digitizer after one month (1,5 week conversation witch seller and 2,5 week waiting on package). Now device working like new - I'm absolutely sure that was hardware failure. Changing is simple in my issue - 18 screws and 7 wiring tapes.
How did you know which to buy ?
Sent from my SM-N975F using Tapatalk
I just got mine installed and the top band of my screen is unresponsive as well.
I cannot touch My Apps in the play store or search in the play store due to the dead area being on that top portion.
I cannot even search in maps as that search bubble is at the top where the screen seems to be dead.
Time to contact Aliexpress.
Hi guys,
I bought andoid car system Wondefoo with PX5 (octacore) + 4GB/32GB with DSP chip for Ford.
I have serious trouble with this car system - after switch-off car radio went sleep, but sometime when I switch-on car and radio wake-up, system beeps are working, but player, or FM radio cannot work - I have to push reset button and after reset it works until radio going to sleep and wake-up.
Did anyone simillar problem with PX5 radio??
Hi, I have similar no sound problem with Wondefoo PX5 4GB/32GB DSP unit (for VAG). This problem happens only when system wakes up from sleep, never after a cold boot. In my case, system beeps are working but otherwise there is only increased amount of white noise from the speakers. I haven't found a solution, except for disabling sleep to force a cold boot every time.
Another annoying problem with my unit is that Wifi and Bluetooth are often unavailable after a cold boot. Wifi adapter MAC address is set to value 02:00:00:00:00:00 when this problem happens. Rebooting fixes also this problem, and after a successful boot Wifi and Bluetooth work fine unit next shutdown. So , I think it could be a software bug in initializing the radio chip. Have you seen this issue with your unit?
What is the software version on your unit? My radio has MTCE_XRC_V2.89_2 and px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180706.161540 test-keys.
have either of you guys found resolution to this problem? I don't have an issue with the audio, but after waking up from sleep my Wi-Fi and Bluetooth no longer are available. My unit is a seicane model, but it has exactly the same build number and MCU version. Their support or telling me that I should replace my Wi-Fi module, but seeing as others are having the same issue I would think this is a software problem. I have about 10 days remaining on my ability to return it to Amazon. And I'm leaning heavily towards doing that. Unfortunately I really like their custom faceplate match to my vehicle.
erkme73 said:
have either of you guys found resolution to this problem?
Click to expand...
Click to collapse
I haven't found a solution to the Wifi+BT problem. I tried upgrading system software to the newer version that is made available in this post but it did not fix it.
I have started thinking that perhaps the Wifi+BT issue could be related to bad electrical connection between the motherboard and the radio chip. Now that the weather is colder, Wifi and BT never work when starting the car in the morning. Anyways, this is pure speculation. If I have time, I will open the radio and have a look.
That's a very interesting observation. I live in Middle Tennessee and it's recently started getting colder, and I've noticed that I have to do a restart twice sometimes. there have been enough random post about Wi-Fi and Bluetooth not working after waking up on various threads at different forms that I thought for sure this was a software issue. The manufacturer has offered to send me a new Wi-Fi module, and I declined mainly because it wouldn't arrive before my return window closes
Did you have any issues with being able to sideload apks? I can't do that. No errors it just blinks and goes back to the directory screen. I also don't have contacts or calendars listed as sinkable items in my account sync settings. Each of these individual issues aren't enough for me to return the device, but when taken as a whole it's a bit too frustrating.
Set sleep timer in > SETTINGS > CAR > EXTRA SETTINGS >
Set it to 1HR
AndroidAutoShop said:
Set sleep timer in > SETTINGS > CAR > EXTRA SETTINGS >
Set it to 1HR
Click to expand...
Click to collapse
I can't speak for the original two posters, but that doesn't address the problem after sleep. The max time is 1 hour, but obviously by morning, it's been longer than that, and the problem arises again.
FWIW, I just initiated a return of my Siecane unit (thanks Amazon) and have ordered a replacement. If it's a hardware issue, this should put it to bed. If the problems remain, it's going back and I'm trying Joying or Pumpkin (or anything other than Siecane). Thank God I bought this on Amazon and not through AliExpress. Certainly worth the higher retail price to have that protection.
Have the exact same issue with my BT an WLAN and also the no sound Problem. Annoying. First few months the unit works great without the problem with WiFi and BT. Now the whole radio sucks like hell without any Connection. I will try order a new BT WiFi Module for a few bucks from AliExpress. Search WLAN px5 there.
I have the issue with white noise after wake-up from sleep mode on my Eonon unit PX5, Android 8. No sounds, just white noise and beeps when I touch the screen.
I installed Malaysk ROM but the problem persists. On cold starts, the sound is normal.
I'm having the exact same issues as described by you guys. PX5. Android 8. Hal9k Mod v3.1. Newest MCU flashed.
No sound after fast boot no matter what. Sound works perfectly after a cold boot. I will donate $10 to the whoever can fix this issue or find a good workaround via paypal.
Fredik said:
Hi guys,
I bought andoid car system Wondefoo with PX5 (octacore) + 4GB/32GB with DSP chip for Ford.
I have serious trouble with this car system - after switch-off car radio went sleep, but sometime when I switch-on car and radio wake-up, system beeps are working, but player, or FM radio cannot work - I have to push reset button and after reset it works until radio going to sleep and wake-up.
Did anyone simillar problem with PX5 radio??
Click to expand...
Click to collapse
mkuka said:
Hi, I have similar no sound problem with Wondefoo PX5 4GB/32GB DSP unit (for VAG). This problem happens only when system wakes up from sleep, never after a cold boot. In my case, system beeps are working but otherwise there is only increased amount of white noise from the speakers. I haven't found a solution, except for disabling sleep to force a cold boot every time.
Another annoying problem with my unit is that Wifi and Bluetooth are often unavailable after a cold boot. Wifi adapter MAC address is set to value 02:00:00:00:00:00 when this problem happens. Rebooting fixes also this problem, and after a successful boot Wifi and Bluetooth work fine unit next shutdown. So , I think it could be a software bug in initializing the radio chip. Have you seen this issue with your unit?
What is the software version on your unit? My radio has MTCE_XRC_V2.89_2 and px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180706.161540 test-keys.
Click to expand...
Click to collapse
AndroidAutoShop said:
Set sleep timer in > SETTINGS > CAR > EXTRA SETTINGS >
Set it to 1HR
Click to expand...
Click to collapse
erkme73 said:
I can't speak for the original two posters, but that doesn't address the problem after sleep. The max time is 1 hour, but obviously by morning, it's been longer than that, and the problem arises again.
FWIW, I just initiated a return of my Siecane unit (thanks Amazon) and have ordered a replacement. If it's a hardware issue, this should put it to bed. If the problems remain, it's going back and I'm trying Joying or Pumpkin (or anything other than Siecane). Thank God I bought this on Amazon and not through AliExpress. Certainly worth the higher retail price to have that protection.
Click to expand...
Click to collapse
sambadii said:
I have the issue with white noise after wake-up from sleep mode on my Eonon unit PX5, Android 8. No sounds, just white noise and beeps when I touch the screen.
I installed Malaysk ROM but the problem persists. On cold starts, the sound is normal.
Click to expand...
Click to collapse
foto55 said:
I'm having the exact same issues as described by you guys. PX5. Android 8. Hal9k Mod v3.1. Newest MCU flashed.
No sound after fast boot no matter what. Sound works perfectly after a cold boot. I will donate $10 to the whoever can fix this issue or find a good workaround via paypal.
Click to expand...
Click to collapse
Hello All
Here is the solution
I had the same problem since the beggining. The only solution was that i put the settings at SETTINGS > CAR > EXTRA SETTINGS > 30 sec
It did do the job but as you guys mentionned the radio was always starting after deep cold instead of sleep. It was still pretty fast but hey who doesn't want the screen to appear right away.
Like the last post, I did update to Hal9k Mod 3.0 . I did try again, same issue.
I was told to update the mcu. So I did to the mtce_gs_v1.94
And here is when everything was possible .
I know that the issue we have is because of the Amp of the bose system that for some reason is not starting after or something like that (don't remember exactly since i read that months ago)
So by updating the MCU, after restarting I had no sound but white noise (like when you listen to radio but there is no channel)
This is when you have to go to Hal9k mod settings.
then in manage applications. then you gotp applications that do not close when sleep and you choose ''amplifier''
and voila
hope it helps. I did try 6-7 times now and no problems anymore.
So have fun and thank you for the donations
Let me know if need some pictures
What you're saying makes sense to me but I don't have an "Amplifier" app to chose. I've even selected every possible app from the dropdown list and still nothing.
It might be because I have the MTCE patch form here https://forum.xda-developers.com/android-auto/mtcd-software-development/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
I'll try with another firmware to see if it works. I have the XRC system btw.
Just in case those of you that are on this thread haven't found the solution to the wifi/bt when cold, look here: https://forum.xda-developers.com/an...o-wifi-bluetooth-waking-t3852206/post78313081
It's a long thread, and the solution appears around page 7-10. It is a hardware issue - an incompatible IC that needs to be replaced (or main board needs to be swapped). Resellers have fixed this for some that are still under their year warranty.
Jkteam said:
Hello All
Here is the solution
I had the same problem since the beggining. The only solution was that i put the settings at SETTINGS > CAR > EXTRA SETTINGS > 30 sec
It did do the job but as you guys mentionned the radio was always starting after deep cold instead of sleep. It was still pretty fast but hey who doesn't want the screen to appear right away.
Like the last post, I did update to Hal9k Mod 3.0 . I did try again, same issue.
I was told to update the mcu. So I did to the mtce_gs_v1.94
And here is when everything was possible .
I know that the issue we have is because of the Amp of the bose system that for some reason is not starting after or something like that (don't remember exactly since i read that months ago)
So by updating the MCU, after restarting I had no sound but white noise (like when you listen to radio but there is no channel)
This is when you have to go to Hal9k mod settings.
then in manage applications. then you gotp applications that do not close when sleep and you choose ''amplifier''
and voila
hope it helps. I did try 6-7 times now and no problems anymore.
So have fun and thank you for the donations
Let me know if need some pictures
Click to expand...
Click to collapse
Try Hal9k mod settings and make not close when sleep and you choose ''amplifier" after few times hu go to sleep again no sound bug happened
Sent from my G8141 using Tapatalk
Still no solution to this problem found. Bump.
Hello guys. I bought px3 hu with Android 8.1 i have same issue with HU. After deep sleep wakeupno sound from HU only solution to get back sound is restart of HU. Who can says what is here a problem,software or hardwer. I have warranty for HU if i just get another its help?
rseke said:
Hello guys. I bought px3 hu with Android 8.1 i have same issue with HU. After deep sleep wakeupno sound from HU only solution to get back sound is restart of HU. Who can says what is here a problem,software or hardwer. I have warranty for HU if i just get another its help?
Click to expand...
Click to collapse
Hi, try putting the ACC shutdown timer on 30 minutes. see if it helps.
the setting is located in Settings > car > extra settings>