Related
Hi, I have a Pumpkin, this one specifically:
Pumpkin Quad Core 7 inch 2 DIN Universal Android 4.4 Car Stereo Radio HD 1024*600 Muti-touch Screen GPS Navigation Without DVD Player Support WIFI/3G/Bluetooth/OBD2/DVR/Mirror Link/SWC https://www.amazon.com/dp/B016B4IY60/ref=cm_sw_r_other_awd_BNbkxb27QAKDQ
The only issue I'm having is that the volume knob will stop working after a few minutes of running. This has happened on two separate head units (same model). I've seen a couple posts with the same problem but no one really talks about it.
Disabling Wheel3 won't do anything because the option is already disabled.
Is this a major problem across all these units or did I just get two problematic units? Anyone have a fix better than the statusbar volume control?
This is known bug on XDA, faced by many of us. I have this issue with my RK3188 HU (Joying JY-UQ130, 99% the same HU than yours).
The most frequent issue is due to Waze v4.x. To avoid knob issue, just reinstall older Waze version (3.9 and before).
Actually, no hardware nor software fix. This problem doesn't occur with SWC.
Lwysiwyg said:
This is known bug on XDA, faced by many of us. I have this issue with my RK3188 HU (Joying JY-UQ130, 99% the same HU than yours).
The most frequent issue is due to Waze v4.x. To avoid knob issue, just reinstall older Waze version (3.9 and before).
Actually, no hardware nor software fix. This problem doesn't occur with SWC.
Click to expand...
Click to collapse
Waze is currently not installed.
Damn ! Try to update your ROM and MCU with the latest versions. It solved issue for a few of us.
Next step should be to have stock ROM with no app and test if problem occurs again. Issue is not clearly identified right now
Same issue on my Joying sometimes. It also seems to be caused by particular apps such as Waze as mentioned.
If I don't use those apps, it usually works fine.
BTW, when that happens as an emergency "this has to be turned down/up" solution, you can PULL DOWN the main menu bar and click "volume" on the settings toolbar and you will get the volume on screen display that you can click for a few seconds before it goes away to change the volume.
I have it on my Pumpkin 3188 SD (which is a KLD2 unit) too.
It has nothing to do with Waze 4. Sure, Waze 4 makes it happen more often, but it will happen with older Waze (probably less often but still happens) and all other audio apps.
It happens often when you get a call via blutooth (which interrupts your current audio) and so on.
Seems it is a bug in the firmware in all these units.
No one has found a fix yet so you'll have to learn to live without a volume knob for now.
---------- Post added at 11:30 PM ---------- Previous post was at 11:01 PM ----------
Lwysiwyg said:
Damn ! Try to update your ROM and MCU with the latest versions. It solved issue for a few of us.
Next step should be to have stock ROM with no app and test if problem occurs again. Issue is not clearly identified right now
Click to expand...
Click to collapse
Happens with the stock ROM too. I tried latest firmware (KLD2 2.81) on mine and it still happens.
Some have "solved" it by using a single audio app at a time, not using bluetooth with their phone, etc. but that's just trying to avoid the problem and not fixing it.
Same here with original ROM (I didn't change the ROM at all nor rooted the device actually) and latest waze installed...
Does anyone know if updating to Android 5.1 (e.g. Malays) solves the issue?
Upgrading the MCU software won't help since on my KLD2 I've tried flashing firmware up to KLD6 2.97 (that's what I am running now) and the volume knob issue remains. I suspect the issue is somewhere in the KitKat flash. Wondering if the problem is still there with the Lollipop flashes.
Sorry to resurrect a dead thread, but has there ever been a solution to this? Even a widget that could do volume control on these head units would be fine. All of the available widgets for Android to control volume do not work with this head unit.
Also, is this still a problem with the new Intel units?
I'm still having this problem occasionally too, usually when waze is open.
thintin said:
I'm still having this problem occasionally too, usually when waze is open.
Click to expand...
Click to collapse
Always Waze, no idea why. On a bright note, I switched to Malaysk ROMs Lollipop 5.1.1 yesterday and did not have the issue at all today (although the ROM itself is SLOOOOWWWW). Will continue to run it for a few days and report back.
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.
Hello all,
I hope you can help me with an issue I have with my PX5 MTCE head unit for a Toyota Corolla E12.
MCU: MTCW-XRC_V2.79k_1
ROM: Stock px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180126.092422 test-keys (this was installed after Malaysk Rom did not work as expected for me)
So here comes the problem:
I have installed an after market backup camera. It gets +12V and GND from the reverse light. I used a wired setup and also a wireless transmitter with a reverse trigger line to test were the problem is. The reverse trigger line from the wireless receiver or the reverse trigger line (which was connected to the +12V from the backup light) is connected to the reverse line of the head unit. At first it works very well and the HU switch to backup camera when the reverse gear is in. But after a couple of tries the picture of the camera freezes. The HU will switch off the picture when another gear is chosen but when the reverse gear is again selected the same frozen picture is shown. After a couple of tries the HU will start to not even switch to the backup camera even if the reverse gear is selected. It only works again if the HU will be disconnected from the car power supply. Then the whole problem starts again.
What is here the problem? Is it a hardware issue?
Kind regards,
Volcano666
Volcano666 said:
Hello all,
I hope you can help me with an issue I have with my PX5 MTCE head unit for a Toyota Corolla E12.
MCU: MTCW-XRC_V2.79k_1
ROM: Stock px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180126.092422 test-keys (this was installed after Malaysk Rom did not work as expected for me)
So here comes the problem:
I have installed an after market backup camera. It gets +12V and GND from the reverse light. I used a wired setup and also a wireless transmitter with a reverse trigger line to test were the problem is. The reverse trigger line from the wireless receiver or the reverse trigger line (which was connected to the +12V from the backup light) is connected to the reverse line of the head unit. At first it works very well and the HU switch to backup camera when the reverse gear is in. But after a couple of tries the picture of the camera freezes. The HU will switch off the picture when another gear is chosen but when the reverse gear is again selected the same frozen picture is shown. After a couple of tries the HU will start to not even switch to the backup camera even if the reverse gear is selected. It only works again if the HU will be disconnected from the car power supply. Then the whole problem starts again.
What is here the problem? Is it a hardware issue?
Kind regards,
Volcano666
Click to expand...
Click to collapse
Hello Volcano, try to use a 12v filter or change the 12v input.
I have this exact same issue with my Eonon PX5 in a Toyota FJ Cruiser using the stock reverse camera. No idea what is causing it, but will see if I can find some sort of filter for the reverse input. Anyone else experienced this one?
Hey not sure if this applies to everyone but for me, I had this same issue and it seemed to go away after I noticed my unit wasn't grounded very securely with the cars ground.
I just connected a wire to the metal case of the unit and ran it to an unpainted metal part of my car and I haven't had this issue since.
There's probably other reasons why this issue could happen though.
Good luck!
Have the same problem with my px5 MTCE head unit (MCU KLD v2. 87) with installed hal9k rom. When I put my car into reverse before the android system is started completely. My whole unit sometimes freezes in boot logo. When I switch to reverse and back to forward and back again to reverse to quickly my reverse camera freezes with the last picture seen. I read in another post that it could be fixed by updating the MCU version but I first have to try this myself.
DonnerPlays said:
Have the same problem with my px5 MTCE head unit (MCU KLD v2. 87) with installed hal9k rom. When I put my car into reverse before the android system is started completely. My whole unit sometimes freezes in boot logo. When I switch to reverse and back to forward and back again to reverse to quickly my reverse camera freezes with the last picture seen. I read in another post that it could be fixed by updating the MCU version but I first have to try this myself.
Click to expand...
Click to collapse
You might be onto something there! Last night I upgraded my MCU from WWW v2.88 to KLD v2.94 and i haven't had the problem reoccur. Granted I haven't driven much since last night but I will keep you all informed!
So I installed a new MCU version on my px5 MTCE head unit. I used the BD375xx Sound Processor Mod from Wadzio, MCU: MTCE_KLD_294bd.zip and as far as I can tell the problem with the reverse camera freezing is now gone. Thanks to the MCU mod my sound is now also way better than before so If someone has the same problem you should try a newer MCU version and maybe even use the modded version to get better Sound.
Great! Mine is going fine now too, so I think we have this one solved!
Thanks everyone!
I have had this problem reoccur once since updating the MCU. I'm pretty sure it is due to interference. While I was reversing, my partner turned off the climate control fan and at that exact moment the reverse display froze again. I had to reset the unit and it has been fine ever since.
i can confirm i upgraded the MCU from MTCE_LM_v2.88_1 to MTCE_HA_v2.99 and initial indications are, my problems is gone.
Problems;
- putting in reverse the camera worked for between 30s - 2min during daytime before screen went blank
- putting in reverse the camera worked for up to 30s at night time when infrared was used before going blank.
Will do further testing, but so far so good, seems to hold the reverse pic for extended periods. (picture flickers more than on previous wince unit thought)
Can confirm, i was getting the same issue, reverse camera image getting frozen, i updated my stock MCU from MTCE_HA_2.75 to the the latest 2.99 i could find, the problem seems to be happen less frequently but still does from time to time, usually when i turn it on first in the morning. Any further help would be appreciated.
I have se same problem, sudendly the screen frozen on reverse. on V2.99
Updated to 3.06 MCU, and turn off the parking lines on de PX5. Problem seems solved.
Seems that in this 3.06 MCU version, the reverse camera try to delay the reverse image signal, but no problems till now.
uberlisk said:
Can confirm, i was getting the same issue, reverse camera image getting frozen, i updated my stock MCU from MTCE_HA_2.75 to the the latest 2.99 i could find, the problem seems to be happen less frequently but still does from time to time, usually when i turn it on first in the morning. Any further help would be appreciated.
Click to expand...
Click to collapse
Did you try to turn off de parking lines image on the unit? Try to update to 3.06 also.
jerrymh said:
Did you try to turn off de parking lines image on the unit? Try to update to 3.06 also.
Click to expand...
Click to collapse
Parking lines were already off, gonna try and update to 3.06 later today, will post any findings, thanks for the help.
After some days of testing i can confirm that the problem still persists even after i upgraded to MCU 3.06, i wonder if my rom version could have something to do with it, currently using
ROM: Stock px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180809.101522 test-keys, maybe try hal9k or malaysk.
Can anyone that has solved the issue by upgrading the MCU, tell me your ROM version?
Thanks.
uberlisk said:
After some days of testing i can confirm that the problem still persists even after i upgraded to MCU 3.06, i wonder if my rom version could have something to do with it, currently using
ROM: Stock px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180809.101522 test-keys, maybe try hal9k or malaysk.
Can anyone that has solved the issue by upgrading the MCU, tell me your ROM version?
Thanks.
Click to expand...
Click to collapse
Did you try 20181210 using a full wipe info. on the update?
This is my case, first used 2.99 and de november update, then installer de wadzio mod 2.99 and all were fine,
Then installer the 20181210 version and the freeze problems starts.
Now updated to 3.06 and seems solved. but is has a 5 seg delay from parking to reverse, and passing from drive to reverse has no delay.
Yea sadly upgrading to 20181210 with v3.06 didnt fix the issue. Running out of ideas.
uberlisk said:
Yea sadly upgrading to 20181210 with v3.06 didnt fix the issue. Running out of ideas.
Click to expand...
Click to collapse
Try this version - it's solved my issue completely (root required)
1) Browse to directory /system/app/MTCBackView/
2) Rename MTCBackView.apk to MTCBackView.apk.old
2) Rename oat directory to oat.old
3) Copy the attached apk to /system/app/MTCBackView/
4) Rename the new APK to MTCBackView.apk
5) Set permission on new apk to 644 (rw-r--r--) or 666 (rw-rw-rw-)
6) Put car into reverse and check that the app loads correctly.
With this apk and MCU KLD v2.94 I haven't had a single freeze for 2 weeks. I got it from a ROM image that Eonon sent me to attempt to fix this issue. They stated " our technician replied that there is the system error or conflict"
millab said:
Try this version - it's solved my issue completely (root required)
1) Browse to directory /system/app/MTCBackView/
2) Rename MTCBackView.apk to MTCBackView.apk.old
2) Rename oat directory to oat.old
3) Copy the attached apk to /system/app/MTCBackView/
4) Rename the new APK to MTCBackView.apk
5) Set permission on new apk to 644 (rw-r--r--) or 666 (rw-rw-rw-)
6) Put car into reverse and check that the app loads correctly.
With this apk and MCU KLD v2.94 I haven't had a single freeze for 2 weeks. I got it from a ROM image that Eonon sent me to attempt to fix this issue. They stated " our technician replied that there is the system error or conflict"
Click to expand...
Click to collapse
Excuse, how can you Root the Dasaita head unit?
jerrymh said:
Excuse, how can you Root the Dasaita head unit?
Click to expand...
Click to collapse
Easiest way is to install Hal9K 3.1 - it is pre-rooted
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>
Hi guys,
I'm having a weird problem that I am unable to resolve. It drives me crazy since I have a very long drive daily and rely on bluetooth audio.
When playing music over bluetooth, there will be stuttering after 20-30mins of playback. The stutter will occur sporadically every x seconds. Sometimes it goes away sometimes it doesn't.
A quick fix I found is disabling/enabling bluetooth, which resets everything and gives another ~20-30 mins without stuttering.
Since I use the phone as a work device, I bought another one so that I could run some tests. Both phones are unlocked.
I tried Pi Experience (Pi) and Lineage 15.1 (Oreo). Both were ran without any apps other than the built-in ones and Play Music.
A few troubleshooting steps I did:
- Since this is occurring on 2+ devices, I strongly doubt it's a hardware issue
- My previous LG V20 (Android 6-7) and friends Iphone have zero issues (so the car isn't the problem)
- This stutter occurs on any BT device the phone connects to
- Disabling/enabling bluetooth resets the issue
- Pi and oreo are affected
- Disabling BT/Wifi scanning in location does not resolve the issue.
- Stopping every service related to BT besides a2dp while the problem occurs does not resolve the issue.
- Restarting Play Music or stopping Play store does not resolve the issue.
- Disabling battery Manager on Pi does not resolve the problem
What I think the problem could be:
- Memory leak in the A2dp service? (I have no idea how to check for that)
- Power saving features that are applied to the BT service after being active for so long (since resetting the service works)?
I'm running out of ideas. Does anyone have any suggestions/tips/story on what the culprit could be and how to fix it?
I can provide a logcat of when the problem occurs if that can be of help
Thanks
Phil
Bumping this up in case someone can chime in!
I have tried all the firmwares as they become available and still face this issue! I know for a fact I am not alone with this problem since I have 2 Redmi Note 5 pros with this problem, and had the exact same issue with a Samsung Galaxy S9+ (snapdragon) that was returned!
If someone can answer these questions, that would be greatly appreciated:
- Do the Firmwares available contain the actual android drivers for bluetooth? Or it's the literal firmware for the SOC (the driver would then be a different file inside the /system partition)?
- When you disable/enable bluetooth, what happens in android? Is the driver unloaded/loaded? or maybe disabled/enabled? Since this step resets the the problem, i'd be interested to know!
Thanks
Maybe Doze-related, but I use audio over Bluetooth for like 2hs almost every single day in my main device (Is not whyred) without problems, so I'm not sure about that.
1- No, the Bluetooth blobs are located in /vendor partition.
1- The operation of bluetooth is complex, many things happen when it's switched on/off, but simplifying: some processes and services are started/stopped.
Anyways, the best way to find the problem is taking logs and send it to the rom developer.
onliner said:
Maybe Doze-related, but I use audio over Bluetooth for like 2hs almost every single day in my main device (Is not whyred) without problems, so I'm not sure about that.
1- No, the Bluetooth blobs are located in /vendor partition.
1- The operation of bluetooth is complex, many things happen when it's switched on/off, but simplifying: some processes and services are started/stopped.
Anyways, the best way to find the problem is taking logs and send it to the rom developer.
Click to expand...
Click to collapse
Thanks for the reply.
This occurs on every rom that is loaded on the devices. I have a strong feeling it's related to the drivers.
I tried looking at the logcat while it glitches, and no errors seem to be shown. I will attach one within the next few days.