Related
Hi,
I was wondering if I can change the functionality of the buttons which are placed on the unit. It would be great if I could change the NAV button to open not the iGo navigation but Google Maps.
Can you help me?
Kind regards
airchicken said:
Hi,
I was wondering if I can change the functionality of the buttons which are placed on the unit. It would be great if I could change the NAV button to open not the iGo navigation but Google Maps.
Can you help me?
Kind regards
Click to expand...
Click to collapse
Do you tried to enter the Settings, then GPS section, and changing there the associated application?
Which settings do you mean? Android Settings or Device Settings (which are secured by the code)
airchicken said:
Which settings do you mean? Android Settings or Device Settings (which are secured by the code)
Click to expand...
Click to collapse
Android settings and then GPS section
Okay, that might be a possible solution to change the NAV button. But how to change the other buttons?
airchicken said:
Okay, that might be a possible solution to change the NAV button. But how to change the other buttons?
Click to expand...
Click to collapse
On my unit I have the following buttons: MENU, DISC, NAVI, DIMM and BAND. I don't know which button can be still redefined, but the only solution (if there is any) I think it could be using a custom ROM.
In my opinion, there should be a configuration file anywhere. But I could not yet find it...
BTW: I have MENU, SETUP, >>|, RADIO, DVD, GPS
airchicken said:
In my opinion, there should be a configuration file anywhere. But I could not yet find it...
BTW: I have MENU, SETUP, >>|, RADIO, DVD, GPS
Click to expand...
Click to collapse
So, which other buttons would you like to redefine and with which other features?
I'd like to put a music player on the DVD Button, as I never watch a DVD in my car...
airchicken said:
I'd like to put a music player on the DVD Button, as I never watch a DVD in my car...
Click to expand...
Click to collapse
Do you have already installed a custom ROM on your unit? Take a look also in the device's Factory settings with the secure code. Such a redefining should be possible.
No, it's still stock...
I couldn't find anything in factory settings...
airchicken said:
No, it's still stock...
I couldn't find anything in factory settings...
Click to expand...
Click to collapse
OK, then I think that it could be possible only with the custom ROM or by root access.
I'm still on stock ROM too, and I would like to make a complete backup of the original ROM before installing the custom one.
That would be good. But as I'm on root, I should be able to change the necessary configuration files...
How do you managed yo get root access without custom ROM? Which is the exact type of your unit and the MCU version?
I had to sideload some things and install an app to root it - don't know exactly anymore.
Will tell you the MCU later this afternoon
Use MTC-Keys to remap buttons
Read links for install and setup
http://forum.xda-developers.com/android-auto/mtcb-software-development/xposed-modules-units-t3263966
http://forum.xda-developers.com/showthread.php?p=60941619#post60941619
Anyone that have installed 5.1.1 ( malaysk, boo, DSA or any other) has success with Bluetooth on KGL MTCB. Please been trying all available fix for it but can't get it to work it connects to MCU but does not show up in Bluetooth app. People with KDL have no problem with that its just KGL I'm thinking. Tried with DSA and typos a while back to solve it but all they said was change BT in setting and change apk to KGL BT apk, but did not worked. So please anyone has a solution help.
Thanks
Sent from my A0001 using XDA-Developers mobile app
No one has KGL with 5.1.1 installed ?
Sent from my A0001 using XDA-Developers mobile app
Luv-Kush said:
No one has KGL with 5.1.1 installed ?
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
I didn't dare to risk as I read lot of ppl complaining on all LP ROMs beside DSAs only on KLD. So I believe it is not only type (KGL or KLD) but also my version that wil/mayl make problems with KLD based MTCC ROMs.
So I will wait and see if devs will realise how complex this mixture of types, versions and tom bases is and will start to deal with it in manageable way which will incorporate adequate testing and true understanding what is going on under the surface. Mal is too amateurish and focused on cosmetics (and lacking even good will to support users in trouble), DSA is dealing with his KLD unit and his target is to fix his own problem (with great good will to enable everyone else to use his work but not ensuring that it will work 100% as he cannot test each and every combination) while booroondook is not even active here on XDA at all.
So, as for me is most important to have robust basic functions as I drive a car and not play with gadget, I decided to stick with KK which works 100%. Yes I would like to have LP (even I don't see any concrete benefits as all basic functions are same!) but I don't want to risk reliability.
Thanks for answer nobody seems to figure out what's causing this. Well I'm on 4.4.4 booroondook for now. Same I think malaysk is too much to deal with, I like small and simple close to OEM but with more app space. So what u think is good 4.4.4 ROM and what r u using. Thanks again I guess we have to wait for 5.1.1.
Sent from my A0001 using XDA-Developers mobile app
Luv-Kush said:
Thanks for answer nobody seems to figure out what's causing this. Well I'm on 4.4.4 booroondook for now. Same I think malaysk is too much to deal with, I like small and simple close to OEM but with more app space. So what u think is good 4.4.4 ROM and what r u using. Thanks again I guess we have to wait for 5.1.1.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm also on booroondook LP as it is FUSE with minimal bloatware. Then I installed few customised apps and closed modules and I'm very happy. Everything works 100% stable and performances are as good as possible on these units (you have to be realistic what you pay is what you get).
I'll wait and see how LP will progress and if it gets performance and stability same as KK then I will upgrade. No other reasons. Nothing new, nothing better currently.
---------- Post added at 06:02 AM ---------- Previous post was at 05:58 AM ----------
Luv-Kush said:
Anyone that have installed 5.1.1 ( malaysk, boo, DSA or any other) has success with Bluetooth on KGL MTCB. Please been trying all available fix for it but can't get it to work it connects to MCU but does not show up in Bluetooth app. People with KDL have no problem with that its just KGL I'm thinking. Tried with DSA and typos a while back to solve it but all they said was change BT in setting and change apk to KGL BT apk, but did not worked. So please anyone has a solution help.
Thanks
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
BTW which MCU version of KGL you have? Is it higher than 2.83? I would like to know if anybody has later KGL MCU.
Same MCU 2.83. So you said "I'm also on booroondook LP as it is FUSE with minimal bloatware. Then I installed few customised apps and closed modules and I'm very happy. Everything works 100% stable and performances are as good as possible on these units (you have to be realistic what you pay is what you get)." how is your Bluetooth works fine ?
Sent from my A0001 using XDA-Developers mobile app
pa.ko said:
I'm also on booroondook LP as it is FUSE with minimal bloatware. Then I installed few customised apps and closed modules and I'm very happy. Everything works 100% stable and performances are as good as possible on these units (you have to be realistic what you pay is what you get).
So the Bluetooth works fine for you on boo LP.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Luv-Kush said:
pa.ko said:
I'm also on booroondook LP as it is FUSE with minimal bloatware. Then I installed few customised apps and closed modules and I'm very happy. Everything works 100% stable and performances are as good as possible on these units (you have to be realistic what you pay is what you get).
So the Bluetooth works fine for you on boo LP.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. Both phone and OBD2. Phone is with CM 13 custom ROM and my obd2 is chiepest Chinese elm 1.5
I'm stating my phone and obd2 as I believe that problems are not only caused by HU and it's ROM but also by the other side. Yes tgese HU have very rudimentary BT support and thus it is important to have other side which is compatible. If your phone works fine with some other device, it is possible that both phone and that other device support higher version of BT stack which is higher than supported by our HU.
Click to expand...
Click to collapse
Luv-Kush said:
Anyone that have installed 5.1.1 ( malaysk, boo, DSA or any other) has success with Bluetooth on KGL MTCB. Please been trying all available fix for it but can't get it to work it connects to MCU but does not show up in Bluetooth app. People with KDL have no problem with that its just KGL I'm thinking. Tried with DSA and typos a while back to solve it but all they said was change BT in setting and change apk to KGL BT apk, but did not worked. So please anyone has a solution help.
Thanks
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hi,
I have a KGL MTCB unit with MCU KGL-2.83 installed on Opel Astra J.
I upgraded my unit (original KK ) to DSA 5.1.1 and I dont have any problem related with Bluetooth. I have tested the DSA roms based on MTCB fw and the newest based on MTCC fw. The bluetooth works in both versions so.. i think it is not a KGL problem at least in my unit.
vch88 said:
Hi,
I have a KGL MTCB unit with MCU KGL-2.83 installed on Opel Astra J.
I upgraded my unit (original KK ) to DSA 5.1.1 and I dont have any problem related with Bluetooth. I have tested the DSA roms based on MTCB fw and the newest based on MTCC fw. The bluetooth works in both versions so.. i think it is not a KGL problem at least in my unit.
Click to expand...
Click to collapse
I don't know what I'm doing wrong but my phone is connected but cannot see in Bluetooth app nor in setting Bluetooth. My MCU kgl 2.83 Bluetooth in factory setting is on SD_BT. Can you please tell me what can be the problem. I put 4.4.4 and I see it in both app and setting. Also can you tell me what Bluetooth in setting you have.
Sent from my A0001 using XDA-Developers mobile app
Luv-Kush said:
I don't know what I'm doing wrong but my phone is connected but cannot see in Bluetooth app nor in setting Bluetooth. My MCU kgl 2.83 Bluetooth in factory setting is on SD_BT. Can you please tell me what can be the problem. I put 4.4.4 and I see it in both app and setting. Also can you tell me what Bluetooth in setting you have.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Its very rare ...
My BT is different in factory setting i have WQ_BC6. You could try changing the BT to the one that i have in factory settings.
Just a stupid question maybe...but... i never have synced my phone with the BT stock option, i dont know if you sync first the phone in the BT stock option later it is shown in the BT app.
I always setup my phone following these steps :
-> I open the BT app (not the BT stock option inside of settings ) and in the phone section (i dont remember the icon), press the button that search phones. Have you try this way?
Luv-Kush said:
I don't know what I'm doing wrong but my phone is connected but cannot see in Bluetooth app nor in setting Bluetooth. My MCU kgl 2.83 Bluetooth in factory setting is on SD_BT. Can you please tell me what can be the problem. I put 4.4.4 and I see it in both app and setting. Also can you tell me what Bluetooth in setting you have.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Try other BT options - Im not sure that each and every unit even it is KGL uses the same BT module!
Also be sure that you enable Address/Phone book sharing on your phone when you pair, as if you don't then BT will not work even it shows as paired (happened to me).
Link just in case the embedding doesn't work.
Youtube Link: https://youtu.be/SzP-soM7cqA
TOP: PX3
5.1.1
MTCD_GS_V1.49_1 Apr28 2016
RK 3188
Mali400
4x1.6ghz
1GB RAM
16GB ROM
1024x600
Bottom: PX5]
6.0.1
MTCD_GS_V2.11_1 Jan7 2017
RK 3368
PowerVR G6110
4x1.2-1.5ghz
2GB RAM
32GB ROM
1024x600
First time shooting a video like this, I can post an update but I'll throw all my findings here.
Some if my initial issues;
With the MTCD PX3 5.1.1 RK3188 You could change the ACC timeout so that the unit would stay on for a specified time, that is no longer in the menu. (Car was off for 3hours and it still fast started so drawing current constantly)
Radio constantly resets after turning the key off even though the Headunit only goes into sleep it's still resetting all radio stations.
Some applications in the Google play store report they are not compatible with this unit ie: iGO Navigation. I had to side load it but that's causing issues with the sys.txt file.
The launcher is damn ugly...
Always says failed to download license when coming out of sleep even with WIFI & 4G connectivity.
(Will update as I use it more)
Positives;
Unable to make it slowdown with Spotify & iGO Navigation running at the same time like it used to.
Audio quality is a LOT better and having subwoofer control on the EQ is great.
No longer have engine whine/hiss either.
(Will update as I use it more)
Antutu benchmark comparison:
PX3:
Overall: 27808
3d: 1220
UX: 13079
CPU: 10293
RAM: 3216
PX5:
Overall: 39047
3d: 9019
UX: 13397
CPU: 12768
RAM: 3863
Please feel free to ask any questions etc.
Cheers
Mat
You should measure the power draw when it has been off for an hour or more. The Intel head units basically goes to a deep hibernation, drawing next to nothing (no more than a normal head unit) while the system is sleeping, and then it comes instantly back on and is ready to use within a second or two from turning on the ignition. It may be that the new PX5 has a similar or the same feature, which is why you don't set the ACC timeout anymore. On the Joying Intel units you can change it between what they call "dormancy" or "shut off" in the special settings app they have, allowing you to turn it all the way off when ACC is removed if you wish to do so.
Hilari0 said:
You should measure the power draw when it has been off for an hour or more. The Intel head units basically goes to a deep hibernation, drawing next to nothing (no more than a normal head unit) while the system is sleeping, and then it comes instantly back on and is ready to use within a second or two from turning on the ignition. It may be that the new PX5 has a similar or the same feature, which is why you don't set the ACC timeout anymore. On the Joying Intel units you can change it between what they call "dormancy" or "shut off" in the special settings app they have, allowing you to turn it all the way off when ACC is removed if you wish to do so.
Click to expand...
Click to collapse
Thanks for the idea, I have a DC clamp meter I'll use tomorrow to double check.
Just tried the ignition again after getting home from being out with friends. So the car was off for 6 1/2hours this time, hit the key & it instantly started.
Still not happy about it resetting the radio stations every time however.
Cheers
Mat
Edit: also showing an issue I'm receiving, PX3 top, PX5 bottom.
The 6.0.1 Octacore has a lot of apps that it's not "compatible" with.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On Intel MTCD devices, they removed the option to set ACC off timer.... due to the power consumption during deep sleep is negligible. I think some ROM update is neccessary to fix that small errors
It is strange that lots of apps were not compatible with the device as it is a RK3368 (two years old chip). Perhaps is sending a wrong device information to Google play ?
good review. Sound like a fellow kiwi? note that other resellers offer MCU and ROM upgrade on rk3188 to enable sub control. e.g. jy1.90
Hi,
About..
=> and having subwoofer control on the EQ is great. <=
Mine Xtrons pic..
(Never.. Buy an Xtrons hu again.. Bad support and to slow communication via email too.. excuses after excuses received!!)
Anyway: have fun with it
BrGd
Madyen
I like that new launcher!
ikerg said:
On Intel MTCD devices, they removed the option to set ACC off timer.... due to the power consumption during deep sleep is negligible. I think some ROM update is neccessary to fix that small errors
It is strange that lots of apps were not compatible with the device as it is a RK3368 (two years old chip). Perhaps is sending a wrong device information to Google play ?
Click to expand...
Click to collapse
Ok did some clamp DC current tests,
Headunit unplugged. vehicle left for an hour. 37-55mA current draw tested 3 times in 15minute period.
Headunit plugged in, sleeping 3hours then clamped. 97-130mA. That's a noticeable drain increase, that's enough to make a vehicle not start if it hasn't been driven in a week.
An ACC timeout adjustment would be great again. Lets say the unit locks up? My older unit would lockup every now and then and just be the wallpaper on screen (launcher crash) and I'd have to turn ignition off the ACC timeout time to reboot the headunit properly.
What happens now? Do I have to go pulling fuses.
And for the device information all it does is report as PX5, Where as the PX3 reports at RK3188. So I have a feeling that's an issue?
Hopefully updates get dropped soon through various vendors as at the end of the day they're all the same generic core board.
Cheers
Mat
hi.
have you managed to gain root access on the unit
Soo...
I think difference too small to upgrade PX3 to PX5.
On PX3 we can turn off all google services and enjoy fast HU
RazGame said:
Soo...
I think difference too small to upgrade PX3 to PX5.
On PX3 we can turn off all google services and enjoy fast HU
Click to expand...
Click to collapse
PX5 aside, the upgraded memory to 2gb is a major factor and provides an out of the box experience without feature limiting mods that may be difficult for some.
Note that I have upgraded my rk3188 to 2gb which improves the unit from boot to opening multiple apps and do not see the cpu as a bottleneck at all.
Seems to me the PX5 isn't ready for prime time as of yet, I'll stick to recommending the Intel for the time being. The power usage when sleeping is disconcerting, the Intel units draw something like 12-13 mA when in sleep mode, which is really great! That is actually a major feature for me, as I'd be annoyed waiting a minute or so for the thing to boot up in the morning.
Bit of an update, Had a few scenarios where radio has not reset now. I can't figure out what aspect causes it to reset but it does happen occasionally between a key cycle.
Apart from the launcher look which I hate I've warmed up to the unit. App switching, Spotify buttons are already linked to << >> > || etc. Haven't been able to lag the volume control, or GPS/Spotify/Pandora switching etc.
Appears With my usage It hovers around 900Mb Ram usage, so there is a chance the biggest change I'm noticing is the memory being 2GB now vs 1GB.
But does anyone have info about the DSP on these units? It sounds a lot clearer and less muddy now which is odd, I wasn't sure that was a change. But It's a welcomed one.
Any questions feel free to ask.
Cheers
Mat
Thanks for all the info
Is there any reference to the voltage on the RCA outputs on the unit? Is it too much to hope that with an improved DSP they can put out a bit more than the old 2V?
Sound quality wise does the unit seem more inline with more established aftermarket units now like Alpine etc (if you have any experience with them), Whats the main difference here?
Okay, I have some info on the MTCD 6.X.X MCU/Software Updates etc.
I also have the update.img & dmcu.img for 12th Jan 2017 for the PX5 unit. (According to Xtrons support, I haven't used yet.)
Link: https://dl.dropboxusercontent.com/u/876493/XDA/PB系列 Android 6.0 软件 (20170112 ).rar
If someone can host? I can temporarily dropbox them.
Cheers
Mat
The following is a Google translate of the .txt doc
2016-12-26
----------
**- Fixed "occlusion" of the weather application search box text
**- Repair Media DVD, up and down keys function
**- Adds interface hints for system high temperature testing
2016-12-27
----------
**- Update the text strong blue BC6, BC8 sdk, optimize the startup speed;
2016-12-29
----------
**- Update the text of strong Bluetooth BC6, BC8 sdk, handle Bluetooth music software reported information error is mistaken for A2DP service disconnected;
2016-12-30
----------
**- Update the exception of APP external device VOL
2017-1-3
----------
**- Repair the radio boot, fast access to non-frequency display problem
2017-1-4
----------
**- Fixes the problem of getting the third-party interface part to get the wrong state
**- Update the kernel CVBS system switch bug
2017-1-5
----------
**- Update the kernel OTG USB bug
**- Update the text strong Bluetooth BC6, to solve the problem of ringtones and dial-up crosstalk;
**- Update the drive recorder watermark display
**- Update the kernel touch screen GT911 bug
2017-1-6
----------
**- Synchronize RK code,
**- Repair USB recovery part of the upgrade can not, the version number changes to V6.0.7
**- Remove the RK's own watermark, making MJPEG and H264 USB display the same way
2017-1-7
----------
**- KERNEL update, repair the boot screen darkening and then restore the issue, G-SENSOR support (yet to be perfect)
2017-1-9
**Music to DVD crosstalk problem
**- Delete the recorder
**- Undo deleted google voice in previous version
**- KERNEL, G-sendor and 4g version of the conflict bug
**- KERNEL, Config for TPMS & BACKSCREEN
**- Release the Bluetooth phone, HOME, BACK, and other key restrictions
2017-1-10
**- Added ZTE MF833V 4G dangle support
**- modify the Bluetooth call state can operate the machine other applications (public version of the Bluetooth application)
In this case,
2017-1-11
**- Update Wenqiang MD725 Bluetooth OBD;
**- Update recovery V6.0.7, fix manually selected MCU upgrade unsuccessful BUG
**- Update Settings application to detect MCU upgrade file error
2017-1-12
**- Tire pressure built-in according to factory factory settings
**- Update billion even USB crash problem
**- Update the network video playback problem
**- Fixed "open the radio in the rear view, close the ACC, will re-open ACC, exit the rear view as the radio, the radio did not sound" problem
Click to expand...
Click to collapse
Hi,
(((excuse me)))
I have not previously responded to your "review" between these 2 hu because I felt it unfair to compare them both like the way you already did.. is not an honestly comparing -and maybe you knew it?- mate!!
Prove it.. you gonna or I hear you say.. right?
Ok here we go..
How it is possible in the Xtrons name that you compare both hu while you did not even have updated your old 5.1 hu at all?
Your 5.1 hu with an very old fw and mcu version while the newer 6.1 hu one is with the most newer fw and mcu come? now is that comparing you called fair
I don't know why you did it that? But maybe.. I may have my own thought of kind of conspiracy but I will keep it for myself and I don't tell it ofcourse
If you are really wanted to comparing both of them honestly then you should first of all update your old hu one first and then compare it with the newer one.. right?
TOP: PX3
5.1.1
MTCD_GS_V1.49_1 Apr28 2016
Bottom: PX5
6.0.1
MTCD_GS_V2.11_1 Jan7 2017
Long live the Xtrons king :laugh:
Have fun mate.
BrGd
Madyen
Madyen said:
Hi,
(((excuse me)))
I have not previously responded to your "review" between these 2 hu because I felt it unfair to compare them both like the way you already did.. is not an honestly comparing -and maybe you knew it?- mate!!
Prove it.. you gonna or I hear you say.. right?
Ok here we go..
How it is possible in the Xtrons name that you compare both hu while you did not even have updated your old 5.1 hu at all?
Your 5.1 hu with an very old fw and mcu version while the newer 6.1 hu one is with the most newer fw and mcu come? now is that comparing you called fair
I don't know why you did it that? But maybe.. I may have my own thought of kind of conspiracy but I will keep it for myself and I don't tell it ofcourse
If you are really wanted to comparing both of them honestly then you should first of all update your old hu one first and then compare it with the newer one.. right?
TOP: PX3
5.1.1
MTCD_GS_V1.49_1 Apr28 2016
Bottom: PX5
6.0.1
MTCD_GS_V2.11_1 Jan7 2017
Long live the Xtrons king :laugh:
Have fun mate.
BrGd
Madyen
Click to expand...
Click to collapse
I was comparing my 2 units, What I removed and what I was installing.
I think you care a little too much.
Cheers
Mat
Madyen said:
Indeed, if you say so, you knew about this and that but never know about an update of an new fw for your own hu and you keep it working and used with an very old fw?.. come on mate.. is that a joke?
As I said, Long live the Xtrons king
BrGd
Madyen
Click to expand...
Click to collapse
You're still making no sense. It's a vehicle specific fit unit, if another manufacturer did a PX5 version to suit I'd of purchased that.
I got my PX3 unit In September, Car didn't get driven between Early December-Mid January due to me breaking my wrist and having it pinned.
I still don't see what you're getting at, but okay. Take your salt elsewhere bud.
Cheers
Mat
FauxDreams said:
You're still making no sense. It's a vehicle specific fit unit, if another manufacturer did a PX5 version to suit I'd of purchased that.
I got my PX3 unit In September, Car didn't get driven between Early December-Mid January due to me breaking my wrist and having it pinned.
I still don't see what you're getting at, but okay. Take your salt elsewhere bud.
Cheers
Mat
Click to expand...
Click to collapse
It is better comparison by having both units completely updated to the last versions of mcu and firmware.
Lots of issues are related to mcu and the one for ypur px3 is very old
if I did help you, please hit "thanks" button
ikerg said:
It is better comparison by having both units completely updated to the last versions of mcu and firmware.
Lots of issues are related to mcu and the one for ypur px3 is very old
if I did help you, please hit "thanks" button
Click to expand...
Click to collapse
The PX3 is already sold, It's why I bought the PX5. I had about an hour with the PX3 after removing it before it got picked up.
Cheers
Mat
I hope someone can help. I restored it with an official rom but for some reason there is no sound as it boots up. Is there any way to enable this? Thanks for any help.
dinkmack said:
I hope someone can help. I restored it with an official rom but for some reason there is no sound as it boots up. Is there any way to enable this? Thanks for any help.
Click to expand...
Click to collapse
Hello dinkmack,
Indeed, at least two issues so far are related to sound in 3 last Android 6.0 OTA updates for M2-801L model (EU versions) :
- No boot sound anymore, even with all sound options activated (only a small vibration is emitted during starting logo screen
- Touch sound / keyboard typing sound remains active even though all related options have been deactivated.
For both of the above at least, I'm still looking for (official) solutions / workarounds, but none found so far.
If found, I'll provide another feedback here.
Hope this helps anyhow.
Have a nice day.
Kind Regards.
mas_tech99 said:
Hello dinkmack,
Indeed, at least two issues so far are related to sound in 3 last Android 6.0 OTA updates for M2-801L model (EU versions) :
- No boot sound anymore, even with all sound options activated (only a small vibration is emitted during starting logo screen
- Touch sound / keyboard typing sound remains active even though all related options have been deactivated.
For both of the above at least, I'm still looking for (official) solutions / workarounds, but none found so far.
If found, I'll provide another feedback here.
Hope this helps anyhow.
Have a nice day.
Kind Regards.
Click to expand...
Click to collapse
What keyboard are u using? I use the huawei swiftkey the stock in the rom, and if I remember right you must go to the keyboard settings to inactive the sound.
RE : MediaPad M2 8.0 No Boot Sound
omaga said:
What keyboard are u using? I use the huawei swiftkey the stock in the rom, and if I remember right you must go to the keyboard settings to inactive the sound.
Click to expand...
Click to collapse
Hello Omaga,
All options checked several times but without success so far.
Check the pic : https://ibb.co/m2QxLp
Any other place I might check those options?
Have a nice day.
Kind Regards.
Some time ago I ordered a px6 Max10 with 720p screen. The lcd screen somehow broke in the mail (I think they knowingly sent it to me broken... but that's just my opinion), and I sent them pictures of this. Dasaita sent me a new screen... or at least they were SUPPOSED to. A month and a half later (today) the WRONG part arrived in my mailbox. They sent me the outer glass instead of a new 720p screen. So here I am more than 2 months after I ordered this thing, it is STILL not in my vehicle. I am sooo friggin angry!
Anyway, I sent them an email but we're probably talking yet another 6 to 8 weeks... and that's if they get it right this time, which I doubt. I am fast coming to the conclusion these people are slightly less than honest.... but that's another thread.
I was thinking....
I do have a Dasaita px5 with a 1024x600 screen. Would it be possible just to take the screen off the px5 and stick it on the px6? This might be far easier than expecting much more from Dasaita at this point. After seeing what I saw today in the mail that they sent me, I don't think I am ever going to see a working 720p screen out of them. I have a feeling they are just going to jerk me around until I get tired of trying.
if they are thesame dimension...the only thing really is just flash the right file for the specific resolution
ojuniour said:
if they are thesame dimension...the only thing really is just flash the right file for the specific resolution
Click to expand...
Click to collapse
Yeah that's what I thought. I'm pretty sure the two screens are the same physical dimensions, and I believe the connections are all the same so its just a matter of flashing with the correct resolution.
Bob_Sanders said:
Yeah that's what I thought. I'm pretty sure the two screens are the same physical dimensions, and I believe the connections are all the same so its just a matter of flashing with the correct resolution.
Click to expand...
Click to collapse
Then just flash the 1024x600 update file (including the MCU if necessary )
May be useful to have a 2nd screen handy that you can connect over HDMI to see what you are doing when you try to flash different screen resolutions. For 1024x600 I think you need to flash a dmcu.ext file with "screen:2" in it.
Noway
woggles said:
May be useful to have a 2nd screen handy that you can connect over HDMI to see what you are doing when you try to flash different screen resolutions. For 1024x600 I think you need to flash a dmcu.ext file with "screen:2" in it.
Click to expand...
Click to collapse
Hi woggles,
I am new here, so please excuse me , if my question is stupid.
First, seems I have the same issue. I have PX6 , and the seller recently send me an update containing dmcu and update. files.
I did the upgrade and this almost brick my head unit. So, my display stop working, it have vertical lines , and flicking. My hardware buttons has lost its orders , for example home button become "power" button, and so on. Touch positions on the screen also are displaced. The screen constantly scrolling itself. Error message appear shows Version Unmatch -01.
I plug external HDMI monitor , and there all looks fine. So the issue is in the LCD display .
Then I update dmcu with newest version , and this error message disappear , but I still have issue with the LCD. Tried several update versions, but so far without success. Attaching pictures.
I think that the issue is in the screen resolution do not match , or LCD hardware issue, that is why I would ask you - how to flash dmcu with screen option ? My screen resolution should be 1280*720
Many thanks !
ps. unfortunately I cant attach an image, as new member
HighWay7777 said:
Hi woggles,
I am new here, so please excuse me , if my question is stupid.
First, seems I have the same issue. I have PX6 , and the seller recently send me an update containing dmcu and update. files.
I did the upgrade and this almost brick my head unit. So, my display stop working, it have vertical lines , and flicking. My hardware buttons has lost its orders , for example home button become "power" button, and so on. Touch positions on the screen also are displaced. The screen constantly scrolling itself. Error message appear shows Version Unmatch -01.
I plug external HDMI monitor , and there all looks fine. So the issue is in the LCD display .
Then I update dmcu with newest version , and this error message disappear , but I still have issue with the LCD. Tried several update versions, but so far without success. Attaching pictures.
I think that the issue is in the screen resolution do not match , or LCD hardware issue, that is why I would ask you - how to flash dmcu with screen option ? My screen resolution should be 1280*720
Many thanks !
ps. unfortunately I cant attach an image, as new member
Click to expand...
Click to collapse
To update the screen configuration you need to flash the dmcu.img along with a dmcu.ext file. You need to put both files on a FAT32 USB flash disk and you can upgrade MCU through the system settings menu or in recovery. The dmcu.ext file can contain the screen configuration and is simply a plain text file containing "screen:x".
For 1280x720 try the following screen values (upgrading MCU each time).
"screen:12" this resulted in blank screen for me
"screen:13" this works for me in all roms but I get one half line that flickers on the top left.
"screen:16" I never tried this, support mentioned it to me
"screen:18" only works for HA firmware 20190915 or newer but has the best results.
I would try 13 first, but I'm not sure if you have same display as me.
Good luck!
woggles said:
To update the screen configuration you need to flash the dmcu.img along with a dmcu.ext file. You need to put both files on a FAT32 USB flash disk and you can upgrade MCU through the system settings menu or in recovery. The dmcu.ext file can contain the screen configuration and is simply a plain text file containing "screen:x".
For 1280x720 try the following screen values (upgrading MCU each time).
"screen:12" this resulted in blank screen for me
"screen:13" this works for me in all roms but I get one half line that flickers on the top left.
"screen:16" I never tried this, support mentioned it to me
"screen:18" only works for HA firmware 20190915 or newer but has the best results.
I would try 13 first, but I'm not sure if you have same display as me.
Good luck!
Click to expand...
Click to collapse
May thanks ! I was able to recover screen settings !
For me "screen:12" working fine
Regards,
woggles said:
To update the screen configuration you need to flash the dmcu.img along with a dmcu.ext file. You need to put both files on a FAT32 USB flash disk and you can upgrade MCU through the system settings menu or in recovery. The dmcu.ext file can contain the screen configuration and is simply a plain text file containing "screen:x".
For 1280x720 try the following screen values (upgrading MCU each time).
"screen:12" this resulted in blank screen for me
"screen:13" this works for me in all roms but I get one half line that flickers on the top left.
"screen:16" I never tried this, support mentioned it to me
"screen:18" only works for HA firmware 20190915 or newer but has the best results.
I would try 13 first, but I'm not sure if you have same display as me.
Good luck!
Click to expand...
Click to collapse
Great post.
Some time ago I received a replacement screen panel and apparently it has a resolution of 1280x720, so I installed it ,but the image doesn't fit the screen. I have tried that dmcu ext file ,but the only value that works is screen:12,,,,,any ideas?
Al Ferro said:
Some time ago I received a replacement screen panel and apparently it has a resolution of 1280x720, so I installed it ,but the image doesn't fit the screen. I have tried that dmcu ext file ,but the only value that works is screen:12,,,,,any ideas?
Click to expand...
Click to collapse
Just using reverse thinking on this.....
Wouldn't a bigger image indicate a SMALLER screen? Are you sure the screen resolution is 1280x720 and not 1024x600?
Screen:2 I think is the 1024x600 if you want to try that. Just make sure you can get out of it without the screen just in case it goes blank.
Bob_Sanders said:
Just using reverse thinking on this.....
Wouldn't a bigger image indicate a SMALLER screen? Are you sure the screen resolution is 1280x720 and not 1024x600?
Screen:2 I think is the 1024x600 if you want to try that. Just make sure you can get out of it without the screen just in case it goes blank.
Click to expand...
Click to collapse
When they sent me the new screen they said it was 1280x720, and when I installed it I checked and it showed 1280x720 in settings. There is a setting in factory settings by the name of "Customer Version" and it's referred to the screen version or resolution , Version 1 and Version 2,,,,,,,,I saw somewhere to never change it to version 2 or it will be a blank screen . I did not try to flash the mcu with dmcu ext screen:1, I will try that later.:good:
.
.
Al Ferro said:
When they sent me the new screen they said it was 1280x720, and when I installed it I checked and it showed 1280x720 in settings. There is a setting in factory settings by the name of "Customer Version" and it's referred to the screen version or resolution , Version 1 and Version 2,,,,,,,,I saw somewhere to never change it to version 2 or it will be a blank screen . I did not try to flash the mcu with dmcu ext screen:1, I will try that later.:good:
Click to expand...
Click to collapse
Here is my experience with this similar issue. After figuring out the the dmcu.ext is basically a text file and the only thing in it is screen:x x being a number. The number representing a resolution in relation to what MCU and OS. The default of 1280x720 is 12 on all of the dmcu.ext I could download. I read in most people changing it to 18 depending on which MCU you have installed is what i read. I also was not doing a factory reset erase all before I did an install. So I did the factory reset and the dmcu.ext with screen 12. nothing happened. I did it again with 18 nothing. The 3rd factory reset with screen:0 and on all of these I was using MTCE_HA_V3.62 for dmcu.img. When this one rebooted it had a black screen. I plugged a monitor to the hdmi output and I could see through the monitor just fime but I had to touch my head unit screen where I think it should be according to the monitor so I factory reset again with screen:13 in the dmcu.ext and when the head unit rebooted after installing it was the correct resolution..
sitealpha said:
Here is my experience with this similar issue. After figuring out the the dmcu.ext is basically a text file and the only thing in it is screen:x x being a number. The number representing a resolution in relation to what MCU and OS. The default of 1280x720 is 12 on all of the dmcu.ext I could download. I read in most people changing it to 18 depending on which MCU you have installed is what i read. I also was not doing a factory reset erase all before I did an install. So I did the factory reset and the dmcu.ext with screen 12. nothing happened. I did it again with 18 nothing. The 3rd factory reset with screen:0 and on all of these I was using MTCE_HA_V3.62 for dmcu.img. When this one rebooted it had a black screen. I plugged a monitor to the hdmi output and I could see through the monitor just fime but I had to touch my head unit screen where I think it should be according to the monitor so I factory reset again with screen:13 in the dmcu.ext and when the head unit rebooted after installing it was the correct resolution..
Click to expand...
Click to collapse
Did you use one of the pre-made display fix files on the Russian yandisk repository?
HighWay7777 said:
May thanks ! I was able to recover screen settings !
For me "screen:12" working fine
Regards,
Click to expand...
Click to collapse
Where did u get the .ext and .IMG files from?
My screen is 1024x600
Thanks for the help
kiwibird said:
Where did u get the .ext and .IMG files from?
My screen is 1024x600
Thanks for the help
Click to expand...
Click to collapse
From reading the forums and contributing, probably FFS.
marchnz said:
From reading the forums and contributing, probably FFS.
Click to expand...
Click to collapse
I tried to look for the right files but wasn't successful. But what do you mean by probably FFS??
kiwibird said:
Where did u get the .ext and .IMG files from?
My screen is 1024x600
Thanks for the help
Click to expand...
Click to collapse
I had the same issue and it took forever finding it. Just rename either dmcu.ext. I tried editing the other, the depository I used no longer existed and any Google search came here.
The new place were I got the dmcu.ext file.
Yandex
Finds everything
disk.yandex.com