Related
Hi community - I updated to VP3G and now either the red button nor the end button finishes the call - this is bad - any idea what I can do ?
peter7 said:
Hi community - I updated to VP3G and now either the red button nor the end button finishes the call - this is bad - any idea what I can do ?
Click to expand...
Click to collapse
Tough to answer with any certainty without knowing more details. Could be your radio - I had that same problem with some radios. Since going with this ROM I have not had the problem. Also what apps do you have loaded?
Mark.
peter, it is something you have done as no one else has had this issue.
What radio? What software have you installed? Using a different Dialer? Hard reset?
We need more information besides "it doesn't work".
And as long as we're giving advice, this forum prefers possible concerns or issues be posted in the already available thread.
For example; if you're having problems with Black Majik, no need to start another thread, just post in the already available thread.
Thanks
Berd
Yes first I thought it is the radio so I switched to Radio 1.43 but the problem is still there. Now I found out it is more the case when I`m connected via GPRS that the button as well as the "end" software button dòn`t work ...
Applications which I use - no extra phon software, but magic button or the as follows: sk software, skype, sprite backup, webis etc.
It's your hardware controller card, gone bad. After some time all of your front button will stop responding. I had the same problem, sent to Dopod service center and got it fixed.
Its not any of ROM issues what so ever. Its a common defect of some earlier batch, as told by the techies at the Service Center.
berdinkerdickle said:
And as long as we're giving advice, this forum prefers possible concerns or issues be posted in the already available thread.
For example; if you're having problems with Black Majik, no need to start another thread, just post in the already available thread.
Click to expand...
Click to collapse
Heh, I made the same assertion once and was told on no uncertain terms that I was wrong.
It seems that it is not the hardware because it is wonderful working when I`m not online with GPRS or 3G !
So what elese can I do ? Should I try another ROM or can I just install an updated file for the GPRS issue ?
PLs help
please remember this is a Dev forum and I believe you answered your own question try flashing another ROM and see if that fixes it. I have no idea about updated GPRS software - you mean a radio ROM? just flash another OS and see if that works its not a problem with 3Gvp's rom but maybe you had a bad flash
vp3G said:
Heh, I made the same assertion once and was told on no uncertain terms that I was wrong.
Click to expand...
Click to collapse
LOCK:Enabled
EXEC:\xda-developers\HiJack.exe
Forum Rules:
http://forum.xda-developers.com/announcement.php?f=355
And Particularly this comment:
pof said:
post a comment to the relevant thread instead of starting a new one.
Click to expand...
Click to collapse
END: HiJack.exe
LOCK: Disabled
RST: Reset
@berdinkerdickle: Yep, at the time I cited that stuff too... and was told by a certain mod that I was still wrong!
peter7 said:
It seems that it is not the hardware because it is wonderful working when I`m not online with GPRS or 3G !
So what elese can I do ? Should I try another ROM or can I just install an updated file for the GPRS issue ?
Click to expand...
Click to collapse
Hmmm... that's an interesting twist on the problem I've never heard before. I would suggest a) hard reset b) reflash my ROM c) flash another ROM. I'd probably also go with a Cingular version of the radio for now ... 1.40 or 1.48.
VP - shouldn`t I start with a new radio rom version before I reinstall your ROM ??? At the moment I`m using the 1.43 version
Up to you, but I thought you said you'd already changed radios. I'd probably go for the hard reset and see if it works before installing anything else.
Hi VP, your advice worked - I changed to ROM 1.48 and now when I dial the online connection is stopped and reactivated after the phon call.
THANK you so much !!!!!!!!!!!!!!!
Best regards
from Germany
Active Sync Error
VP - it´s again me - pls can you look at my problem: My Tytn is telling me -in the meantime several times a day -that I have to resynchronize and after I got the warning to resynchronize there comes the next warning that there is no IP number !
Hi!
Does anyone know where to find ROMS for HKC G1000 (DUAL SIM WM6)?
Many thanks!
i have one. they sent it to me coz i complained about noise being picked up by phone1. tried reflashing, but still the same problem.
Hi I have a HKC G1000, and do not do as a HARD RESET, as you know, thanks
I've got the last (november 2008) English ROM for HKC G1000 when been in ShenZhen month ago. If you need - I can upload it somewhere.
THOMYROS said:
Hi I have a HKC G1000, and do not do as a HARD RESET, as you know, thanks
Click to expand...
Click to collapse
There is Icon with green tree in Settings menu - search for it!
Hkc G1000 hard reset
Hi,
i have the same problem, i have installed a program now the phone is blocked in the windows boot up screen.
Did you solve the problem?
Could you help me please?
Thanks
try this
3 key press together for re-start:
G2 (Dial sim card 2 key) + Camera key (on the right side, near the on/off key) + on/off key.
9rinder said:
I've got the last (november 2008) English ROM for HKC G1000 when been in ShenZhen month ago. If you need - I can upload it somewhere.
Click to expand...
Click to collapse
hi, can i have it? please provide a link for download. thanks... hopefully it will solve my noise problem on phone 1. thanks...
can you post your rom versions?
mine is Under Device Information: WM6_HKC_G1000_VER_07
Hkc G1000
Thank you very much Pranix,
it worked ,
but only after take off the battery for 15 min. and with G1 button at place of G2.
I'm also interested to have the Rom (just in case
If you can provide a link it will be much appreciated.
mine is:
ROM: WM6_HKC_G1000_VER_07
RADIO: PPC_DMDC_RIL_01.01
PROTOCOL: W8.5P8.4
DRAGONFLY: DV17-MODULE-VER-07.12.2
Just a curiosity: this pda it supposed to have 64 Mb of ram, but on "about" i read only 43,74 Mb,
it's your the same or not?
Thanks again
we have the same version.
http://uploading.com/files/G05UZJ16/HKC G1000.rar.html
hopefully someone here can modify and update it to wm 6.1
how's the sound quality of your phone?
i have a problem with phone 1, it picks up alot of ambience noise.
difficult to hear the other person you're talking to.
if you put your hand over the mouthpiece, and also the earpiece, it creates a feedback sound.
no problem on phone 2.
Hkc G1000
Hi Pranix,
thanks for the rom file after i'll ask you how to flash it.
My phone works good both sims, your, sounds to be an hardware
problem, since you told that you have flashed the rom.
The set of the microphone for the sim 1 is too sensible, and when you put the hand on the micro, it cause what is called "larsen effectc", that happend when the sensibility of the microphone is too high and trigger a feedback from the earphone that cause an annoying whistle .
In an italian forum, I heard about an engineering code to write down in the
china phones with WM6, that allow you to set some hardware features
of the phone including the sound level, I don't know if this is possible also with our phone. but it worth a try.
I'll go to ask in the forum and if pertinent, i'll post you the answer.
Bye
hi,
the procedure to flash is in the rar file that i have uploaded.
just open the text file.
hope you can find some way to minimize the sensitivity of microphone setting for phone 1.
regards,
pranix
Hi Pranix,
he say that the code "engineer mode" it is available only on the china phones with the RTOS operating system, and in some motorola and Nokias,
but he say that maybe it is possible to change the parameters set on the windows registry, with a pc program like CeRegEditor.
Connect the phone to the pc, start CeRegEditor, make it read the registry, click on unlock (if not you can't save the changes), after that you have to look where are located the keys regarding the audio, and see if modifiyng the key value you can solve the problem.
I will look further if i find some else solution
good luck
i already tried editing registry however still the same.
maybe i was editing the wrong registry. hehe
i just hope that 9rinder gets to post his rom here
Pranix said:
i just hope that 9rinder gets to post his rom here
Click to expand...
Click to collapse
Here is link, try it, guys:
http://rapidshare.com/files/195288870/HKC.ZIP.html
Hi Pranix,
take a look here, maybe help:
http://forum.xda-developers.com/showthread.php?t=256734
then search on the registry with the keyword "volume"
9rinder said:
Here is link, try it, guys:
http://rapidshare.com/files/195288870/HKC.ZIP.html
Click to expand...
Click to collapse
hi,
can you post your rom details?
i downloaded the rom, it seems your rom & my rom are the same.
i checked the date & time stamp, its identical.
i also asked my contact at hkc, still no new rom since i asked for it sometime june.
how's the audio quality on your phone 1 & phone 2?
can you hear the calling party clearly?
oxyjo said:
Hi Pranix,
take a look here, maybe help:
http://forum.xda-developers.com/showthread.php?t=256734
then search on the registry with the keyword "volume"
Click to expand...
Click to collapse
i've actually tried editing those registries before however still the same.
the question here is that do we have one or two mircrophones?
coz if only one, then there must be a setting somewhere to adjust phone 1 & phone 2. phone 2 sound is better than phone 1.
if two microphones, i cant find the settings as there is only one setting to tweak.
Hello. I have one of this PDa.
Mine has this ROM:
ROM version:WM6_SITRONICS_SD106_VER_05
Radio version: CYNTHIA850_DMDC_RIL_01.01
Protocol version: W8.5P8.4
Dragonfly Version:CYNTHIA850 TF-DV17-MODULE-VER-07.16 Feb 18 2008 13:02:06
Do you recommend me to update?
Is any way to "extract" its original ROM?
And is any way to "edit" any of your roms to change the language of the OS?
Thanks
This thread is to document MCUs found to be cross-compatible between MTCD units, which includes PX3 and PX5 variants, which share identical mainboard hardware and MCU Chip STM32F091.
The following MTCD & MTCE (as of v2.56) MCUs have been validated as cross compatible on 1024x600 units:
- MLT - 01/07/17 - caution - has resulted in issues for some @leonkernan
- JY
- KBT - 08/12/2017 - thanks @abagos
- KD (v2.40_2 - enables bluetooth hands free in both front speakers)
- KGL
- KSP thanks @Overmann
- GS - Note "version unmatch" error and fix below No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80 - March 2018
- GS compatible on MX (see post #513)
- HA (v2.56 06/07/17 - note v2.52 on enables "shutdown delay when acc off" menu) HA MTCE (30/09/17) V2.65 https://www.sendspace.com/pro/dl/ufie8k
See this thread for pics where MCU HA and KD has been applied on JY. https://forum.xda-developers.com/showpost.php?p=72737797&postcount=640
I initially upgraded to KD 2.40, then HA v2.52 after first exporting the MCU settings.
Note that I had to reapply MCU settings in [factory sertings] to configure radio, LED, bluetooth, hardware keys, volume levels between radio, bluetooth, system etc.
MCUs were previously thought to be manufacturer specific - e.g. HA, JY, GS, KD, however I have found that they are compatible and of interest where there is either a specific issue with your MCU (e.g. bluetooth out of one speaker, to enable PX5 sleep mode control) or the vendor has long ceased to support & release updates - such as JY.
MCU cross-compatibility became of interest to me when I upgraded my JY [MCU v2.06_2] PX3 with a HCT PX5 SOM and wanted to enable the MCU specific menu item [shutdown delay when ACC off] to control sleep as found on HA/Dasaita.
I first noted that from an XDA post listing JY an KD v2.06_2 being identical and on that assumption, upgraded to KDv2.40_2, which successfully applied - but had to reconfigure factory settings.
Following on, I found a post which has an image of a GS board & MCU chip - noted it was identical to the MTCD JY MCU chip [STM32F091] - then came across a post where a user had inadvertently applied a MTCD GS MCU to a MTCD JY without bricking it.
I then started comparing same version number firmware files from various manufacturer MCUs with a text compare tool. From this work, I had enough info to compare the latest HA v2.52 and conclude it 'should' be compatible. Indeed it is.
As always, check first (suggest confirming MTCD, MCU Chip part number, view/compare the fw files, ensure you have original MCU FW, backup MCU settings or document the settings to ensure your hardware controls, volume control, bluetooth, radio, canbus etc are setup correctly). Apply at your own risk.
Please post your results and I will update this thread.
Updates:
UPDATE: 26/06/2017 Users of 800x480 Users must also apply file[dmcu.ext], a text file containing:
For PX3 --> screen:3
For PX5 --> screen:1
01/07/17 - MLT
06/07/17 - KGL confirmed and new HA v2.56
30/09/17 - MTCE MCU confimed compatible
08/03/18 - MTCE JY/GS/HA compatible - No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80
GS Specific Notes:
Oberbergler said:
For all those with a GS: Our unit is compatible with the MTCE MCU but you have to restore your settings and maybe to manually reconfigure your touchscreen and buttons. There is a simple function to do this in the factory settings (126) which is called key study. My touchscreen was also swapped by the x axis. I had to go with the swapped touchscreen into the settings, configure it, reboot the unit and everything was fine. For the buttons you have also the possibility to use short press and long press buttons, which is great because our units (at least mine) has only five buttons and no return button. So I use now the power off button as return in short press mode and power off in long press
Click to expand...
Click to collapse
Version unmatch see this post where user resolved by reapplying MCU AND Software APK Fix Here
- Attached Version Unmatch APK fix to this post, thanks @Wadzio
GS Configuration Settings file:
Bose321 said:
Here it is: https://gerbenbol.com/android/dmcu.cfg.
Click to expand...
Click to collapse
Do not dilute this thread by posting "how-to" questions such as - how do I update the MCU, what unit do I have, can I do it, how do I find factory settings, etc. This thread is to document cross-compatible MCUs and the fixes they apply.
Hi! Confirmed, I've upgraded to PX5 (JY UL135). Flashed KD2.40 over JY 2.06_2 then flashed HA 2.52 and everything is working as it should be. Thanks for your work.
I can confirm a cross compatibility as well.
My Unit is a xtrons device with die MCU firmware GS 2.43 and yesterday i did flash the HA 2.52. But be sure to save your mcu config first. Otherwise the hardware buttons won't do what they were supposed to do. But after flashing the firmware and restoring the config, everything is back to normal.
To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.
Some time ago I tried to investigate what actually those abbrevations mean. In my understanding GS, JY, HA is related to the canbus profiles, not directly to the reseller. It seems to be reasonable because MCU has really tiny flash capacity and add all canbus configurations to one chip would be impossible.
f1x said:
Some time ago I tried to investigate what actually those abbrevations mean. In my understanding GS, JY, HA is related to the canbus profiles, not directly to the reseller. It seems to be reasonable because MCU has really tiny flash capacity and add all canbus configurations to one chip would be impossible.
Click to expand...
Click to collapse
No, you are wrong there - the letters very definitely relate to the manufacturer, NOT the CAN Bus profiles KLD = "Klyde" KGL, = "Kai Ge Le", JY = "Joyous" etc, this has been established for years.
The seller has NOTHING to do with the software at all.
The CAN Bus profiles are named in factory settings
On MTCB/C headunits there was a slight difference in the code between MCU types so they were not interchangeable (apart from BN and HA), it would seem that on MTCD units there is no such variation in the code.
Does this also apply to LM_ (Erisin) MCUs?
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv
SpeedyCarv said:
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv
Click to expand...
Click to collapse
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.
typos1 said:
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.
Click to expand...
Click to collapse
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..
SpeedyCarv said:
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..
Click to expand...
Click to collapse
Maybe read it again ?
Basically, you could risk trying it - MTCB/C units can be restored if the wrong MCU is flashed, maybe MTCD units could be restored if the wrong MCU is flashed also ? But maybe not, so that is your decision whether to try or not.
Otherwise stick to what @marchnz has said and do not try it.
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Cant make it any clearer than that.
typos1 said:
Maybe read it again ?
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Click to expand...
Click to collapse
Not necessary to read again. I already knew that. That's what i tried to express in typing "my level of knowledge has not grown" Sorry if i write misunderstandable, i'm not a native speaker (German).
Thank you again for your time and patience
typos1 said:
To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.
Click to expand...
Click to collapse
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?
Wout2426 said:
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?
Click to expand...
Click to collapse
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
Or, once mcu has been upgraded, you can remove the mcu update (.img) from the root of the gps card and apply the config (.cfg) on the root of the gps card separately - by running the 'upgrade MCU', it will see .cfg file and apply it.
Update for 800x480 users who update to the latest MCU - you must also apply a dmcu.ext
DMCU.EXT details
DMCU.EXT & screen resolution setting/howto/details
dmcu.ext details for PX5 800x480
That said - why is anyone purchasing a PX5 unit with 800x480?!?!
KD --> HA for 800x480 Screen
I have had quite an experience over the weekend, but am able to report successfully updating a PX3 MTCD_KD unit to a PX5 with the HA2.52 MCU Code.
For those of us with 800x480 screen sizes, as now noted in the main thread, we need to create the dmcu.ext file with the appropriate screen size to be flashed with the dmcu.img file.
Just a note that if you run across the issue of not having the appropriate resolution; don't freak out.
One interesting note I hadn't mentioned before is that after the PX5 started thinking it was 1024, I replaced it with the PX3. The PX3 booted thinking it was 1024 also. After reverting the PX3 to 800 (flashing with screen:3), I replaced the PX5. The PX5 however, did not revert back to 800, but remained at 1024. The PX5 did not revert back to 800 until after I reflashed the MCU, specifically stating it was to be 800 (screen:1).
So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.
typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.
Bose321 said:
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.
Click to expand...
Click to collapse
Yeah, thats right - the "d" is just there to show its an MTCD MCU not an MTCB or MTCC one.
1-2-Hak said:
So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.
Click to expand...
Click to collapse
The shutdown option is under System Settings --> extra settings. You wont find it in the factory settings. Just FYI.
Which dmcu.cfg did you use? I might be wrong, but it seems to me it might be dangerous to use different dmcu.cfg files with different versions of the MCU Code.
I can't seem to find where to post this appropriately, so I'll post it here and see how many people tell me where to post...
So, I have a Xtrons HU which was originally running MTCE_GS_V2.72_3. I incorrectly updated to MTCE_CHS_V2.75. The system generally worked fine, but the radio didn't work. So, I acquired MTCE_GS_V2.78_1 from the vendor and installed this. The radio works again, but now I have a message Version Unmatch -01 FD044B343EE7C1C08400 GS 00000000 and an annoying ping every few seconds.
I have looked through the forums trying to find a solution and am very confused about how to proceed. Do any good Samaritans care to help out an Android HU newbie?
Thanks in advance.
rwgau said:
So, I have a Xtrons HU which was originally running MTCE_GS_V2.72_3. I incorrectly updated to MTCE_CHS_V2.75. The system generally worked fine, but the radio didn't work. So, I acquired MTCE_GS_V2.78_1 from the vendor and installed this. The radio works again, but now I have a message Version Unmatch -01 FD044B343EE7C1C08400 GS 00000000 and an annoying ping every few seconds.
I have looked through the forums trying to find a solution (?) and am very confused about how to proceed. Do any good Samaritans care to help out an Android HU newbie?
Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/sitesearch.php?q=Version Unmatch
Hi, where did you get the v2.78 from? I also have xtrons MTCD 2.72 are you able to share a copy of it please? Is there much difference?
Thanks, Anthony
Anthony_99 said:
Hi, where did you get the v2.78 from? I also have xtrons MTCD 2.72 are you able to share a copy of it please? Is there much difference?
Thanks, Anthony
Click to expand...
Click to collapse
MTCE GS 2.78. Installed it on mine (although I do have a 2GB PX5) and not noticed any differences....
For Dasaita PX6
Updates on Dasaita website: https://www.dasaita.com/blogs/news/update-firmware
-----
Older versions:
Android 10:
HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q
HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ
MCU images - unzip and copy "img" file to flash (sd/usb):
v3.57: View attachment MTCE_HA_V3.57.zip
v3.60: View attachment MTCE_HA_V3.60.zip
v3.62: View attachment MTCE_HA_V3.62.ZIP
DMCU - unzip and copy to flash (sd/usb) together with MCU image:
for 1280x720 units: View attachment dmcu-1280x720.zip - use it if you got a wrong resolution after flashing MCU image and you need to restore your unit to 1280x720 resolution
All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)
orik13 said:
For Dasaita PX6
Android 10:
HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q
HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ
MCU images - unzip and copy "img" file to flash (sd/usb):
v3.57: View attachment 5111231
v3.60: View attachment 5111233
v3.62: View attachment 5111235
DMCU - unzip and copy to flash (sd/usb) together with MCU image:
for 1280x720 units: View attachment 5111237 - use it if your unit has 1280x720 resolution, otherwise you can get 1024x600 or lower instead (no worries in this case - just reprogram)
All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)
Click to expand...
Click to collapse
Before even considering this read in the other thread what happen to my unit. User name halloj,
orik13 said:
For Dasaita PX6
Android 10:
HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q
HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ
MCU images - unzip and copy "img" file to flash (sd/usb):
v3.57: View attachment 5111231
v3.60: View attachment 5111233
v3.62: View attachment 5111235
DMCU - unzip and copy to flash (sd/usb) together with MCU image:
for 1280x720 units: View attachment 5111237 - use it if your unit has 1280x720 resolution, otherwise you can get 1024x600 or lower instead (no worries in this case - just reprogram)
All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)
Click to expand...
Click to collapse
Anyone reading this
*** Do not flash the DMCU.ext listed here together with the MCU ***
OP please edit this post, there is NO reason to flash dmcu.ext when flashing the same vendor MCU.
Suggest expanding on the comment "no worries just reprogram", with clear examples if making this statement.
marchnz said:
Anyone reading this
*** Do not flash the DMCU.ext listed here together with the MCU ***
OP please edit this post, there is NO reason to flash dmcu.ext when flashing the same vendor MCU.
Suggest expanding on the comment "no worries just reprogram", with clear examples if making this statement.
Click to expand...
Click to collapse
I edited it to make it more clear. Your comment is not absolutely correct: it is based on my own experience. Similar issues can be found by googling and even here at xda
Hi all I am a bit confused by how many different downloads please excuse me as a noob and first time flashing my PX6
My question is can I just jump from 3.5.8-1 to the latest 3.6.2 I believe and what files exactly do I need to load onto a flash drive.
Your help in advance is much appreciated. Cheers J
I am running a MTCE HA running 3.5.9
ToyotaJay said:
Hi all I am a bit confused by how many different downloads please excuse me as a noob and first time flashing my PX6
My question is can I just jump from 3.5.8-1 to the latest 3.6.2 I believe and what files exactly do I need to load onto a flash drive.
Your help in advance is much appreciated. Cheers J
I am running a MTCE HA running 3.5.9
Click to expand...
Click to collapse
Suggest NOT changing your MCU unless resolving a known issue. Same for Android. This is a head unit, constantly updating isn't necessary.
Update for mic issue
Hi Experts! If I want to update my Dasaita PX6 Max10 is there any preferred order which update to do first OTA or MCU? In case of OTA update at starting is it necessary to click on WIPE AND FORMAT FLASH option? Somebody is doing this, somebody is doing that... When is it suggested?
The reason why I planning to switch to latest update because during calls my mic is working strange, sometimes the others cannot hear me properly. They are complaining about low volume and faded voice. (If they are calling back they says it is better...) Have you experienced the same thing?
halloj said:
Before even considering this read in the other thread what happen to my unit. User name halloj,
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=83671635&postcount=3655
gomoriz said:
Hi Experts! If I want to update my Dasaita PX6 Max10 is there any preferred order which update to do first OTA or MCU? In case of OTA update at starting is it necessary to click on WIPE AND FORMAT FLASH option? Somebody is doing this, somebody is doing that... When is it suggested?
The reason why I planning to switch to latest update because during calls my mic is working strange, sometimes the others cannot hear me properly. They are complaining about low volume and faded voice. (If they are calling back they says it is better...) Have you experienced the same thing?
Click to expand...
Click to collapse
Are you sure it is not a h/w issue? Did you try other mic?
orik13 said:
Are you sure it is not a h/w issue? Did you try other mic?
Click to expand...
Click to collapse
I use the internal microphone, not yet tried an external one. I checked the mic with apps, basically it is working however its volume seems to be a little bit low, but it is not faded. I feel it is rather a noise suppression issue (coming from sw side), therefore I hope that an update could help.
orik13 said:
I edited it to make it more clear. Your comment is not absolutely correct: it is based on my own experience. Similar issues can be found by googling and even here at xda
Click to expand...
Click to collapse
I respectfully disagree based on years of experience: there's no need to flash the MCU configuration file DMCU with an MCU that matches the manufacturer of your head unit. I.e. HA to HA, JY to JY etc.
Your well meaning advice resulted in a configuration not appropriate (which messed up the screen) for another members screen type/resolution.
The 'similar issues' stated are probably your misunderstanding of what the DMCU file is and possibly where others have installed a different vendor MCU. E.g. GS on HLA
Hello, with dasaita px6 android 10 1024/600 firmware HA3, the update "HA3_rk3399_10.0_ota (20200915) 升级 包" and MCU "MTCE_HA_V3.62": all is ok , thank you
A few questions...
1) Anybody able to modify steering wheel controls? I open the app and it is blank.
2) Also, can you summon siri/google via the steering wheel when in carplay/android auto?
3) I have an OBD dongle but am unable to get the headunit to connect to it. I see it in the available devices but nothing happens after i select "yes" to connect.
I have the max10 600p resolution version for highlander. A canbus was included and I am able to change vol/toggle modes.
h0va4life said:
A few questions...
1) Anybody able to modify steering wheel controls? I open the app and it is blank.
2) Also, can you summon siri/google via the steering wheel when in carplay/android auto?
3) I have an OBD dongle but am unable to get the headunit to connect to it. I see it in the available devices but nothing happens after i select "yes" to connect.
I have the max10 600p resolution version for highlander. A canbus was included and I am able to change vol/toggle modes.
Click to expand...
Click to collapse
When you install a harness with a CAN adapter the steering wheel signals a routed for you to the CAN decoder box. It worked for me to reroute them to my own circuit. It should be equally fine to connect them to the KEY1 and KEY2 inputs, that is if your car has resistive buttons and only one or two. Then you can program them as desired.
Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?
woggles said:
Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?
Click to expand...
Click to collapse
I noticed that the first time I installed that update, then I went back to the prior version I had, one more time I gave it a try and I started to try to remove that annoying notification, but then I thought why waste time on that, also I notice that saving a screenshot was giving me an error, so once again I went back to the prior version I had installed.
I can’t decide whether to put this up or Malayk’s ROM. I don't really need pre-installed programs, I know which launcher, music player, etc.. I want to use, but there may be settings in it that I can't solve on this ROM.
woggles said:
Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?
Click to expand...
Click to collapse
Try
https://forum.xda-developers.com/showpost.php?p=83767241&postcount=3694
bad for me
thienthanty said:
Try
https://forum.xda-developers.com/showpost.php?p=83767241&postcount=3694
Click to expand...
Click to collapse
hello, with this firmware "HA3_rk3399_10.0_ota (20201016) 升级 包", I can no longer make a call with "google voice".
thienthanty said:
Try
https://forum.xda-developers.com/showpost.php?p=83767241&postcount=3694
Click to expand...
Click to collapse
Thanks, the annoying pop up is gone but as another use mentioned using call x from Google Assistant doesn't work anymore!