MCU problem on a HXD unit. - MTCD Android Head Units Q&A

Hello, I recently tried to change the MCU of my unit. I changed it directly for an HA MCU, but obviously I got an unmatched version.
I have reinstalled the HXD but now the unmatch version is not removed, a beep sounds every few seconds, the touch buttons and bluetooth do not work.
All this before reading the "verified cross compatible MCUs" thread (I know, my fault). I have read and understand that I have to export the mcu.cfg file, but now I don't have the file with the initial configuration, and I don't have the latest MCU either, since it came with version V3.71_1, and now I only find v3. 62e.
I would appreciate if someone can help me.
Thank you very much.

To remove the beeping, try Mcu Unmatch Unlock. Button calibration and bluetooth settings are in factory settings. Choose your bluetooth type, if you don't know what you have, you have to try. For example, I have bluetooth WQ-BC6 on my Isudar MCU GS.
Solution for 'Version unmatch' (I hope final)
I know that this topic has already been discussed many times in many threads (most in MTCD - Verified Cross compatible MCUs). I also know that there is a known solution to this problem. However, there are users who report that they still have a...
forum.xda-developers.com

Pavel-71 said:
To remove the beeping, try Mcu Unmatch Unlock. Button calibration and bluetooth settings are in factory settings. Choose your bluetooth type, if you don't know what you have, you have to try. For example, I have bluetooth WQ-BC6 on my Isudar MCU GS.
Solution for 'Version unmatch' (I hope final)
I know that this topic has already been discussed many times in many threads (most in MTCD - Verified Cross compatible MCUs). I also know that there is a known solution to this problem. However, there are users who report that they still have a...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the reply. I have already tried Mcu Unmatch Unlock and it doesn't work, it doesn't open the application, i have read that it doesn't work on android 10.
Button calibration and bluetooth settings I have already tried in factory settings, but it doesn't work either, the buttons don't even light up.

jack43 said:
Thanks for the reply. I have already tried Mcu Unmatch Unlock and it doesn't work, it doesn't open the application, i have read that it doesn't work on android 10.
Button calibration and bluetooth settings I have already tried in factory settings, but it doesn't work either, the buttons don't even light up.
Click to expand...
Click to collapse
It is possible that the update changed your customer version, if you originally had MCU 3.71_1, then the 1 at the end indicates that your subversion is 1. Check what your customer version number is. (Factory settings/ Other/ Customer version)
WARNING: If you change the initial values (up to 3) of this number in the factory settings, the buttons on the front panel may stop working normally, and above (more than 3) problems may begin until the absence of an image on the screen, respectively, I strongly recommend saving immediately after buying a new radio factory reset image to the dmcu.cfg file and additionally write / remember the native MCU firmware extension and subversion number. Source 4pda.

Pavel-71 said:
It is possible that the update changed your customer version, if you originally had MCU 3.71_1, then the 1 at the end indicates that your subversion is 1. Check what your customer version number is. (Factory settings/ Other/ Customer version)
WARNING: If you change the initial values (up to 3) of this number in the factory settings, the buttons on the front panel may stop working normally, and above (more than 3) problems may begin until the absence of an image on the screen, respectively, I strongly recommend saving immediately after buying a new radio factory reset image to the dmcu.cfg file and additionally write / remember the native MCU firmware extension and subversion number. Source 4pda.
Click to expand...
Click to collapse
I tried changing the customer version, I tried all 3 modes, but it still doesn't work. I do not know what else to do.
Thanks for your kindness anyway.

Related

General ROLL-UP -Joying 2GB - Sofia ( Non MTCB/MTCD )- Tips, tricks and mods

There is getting to be quite a bit of information to look through when looking for tip/solutions related to the new Joying 2GB / Sofia units. Since this is not a MTCB or MTCD unit, the threads seem to be scattered all over and very difficult to find in searching. I have seen roll-up threads for other units, that contain information such as ROMS available, tips, tricks and useful information. Kind of a "one stop shop" for the newer Joying HUs. If you have useful software, mod, tips, customization's, get something to work, etc please post here and I can include.
CPU Information - Rockchip Sofia x64 C3230RK / mali 450 GPU / Up to 1.2Ghz / 4 core / FYT5009 SoM - rated to run at up to 85C. My particular is unit clocked at 1.04Ghz.
Advanced Settings Password: 3368
Homescreen menu: 8086
Backlight Current menu: 5768
Android 6 Thread
https://forum.xda-developers.com/an...ing-intel-head-unit-android-6-update-t3597121
Android 6 specific tips:
ADB Access: https://forum.xda-developers.com/showpost.php?p=71616884&postcount=273 -OR-
https://forum.xda-developers.com/showpost.php?p=72057022&postcount=12
Viper4Android: https://forum.xda-developers.com/showpost.php?p=72064749&postcount=41
Latest ROM - Current ROM can be downloaded from link on the Joying blog site.
https://www.carjoying.com/Joying-blog/59.html
Android 5.1 Discussion about the Feb 22, 2017/March 5, 2017/March 15, 2017 updates:
https://forum.xda-developers.com/an...d-units/joying-intel-update-feb-22nd-t3561285
People have experienced issues with the Joying Launcher (UI3) after the update. This seems related to having other packages (google voice search ) installed prior to installing the ROM. Install time 25-35 minutes.
Recovery from non-bootable system - Without being able to access recovery, about the only solution is to reload the ROM package. Unzip ROM to SD card or USB stick, put in unit (GPS Maps slot, if using SD card ) and press the 'recessed' reset button. The unit should find the update and reload the ROM. This will wipe your data, but does leave the apps. If you use titanium backup, and have a backup, you can restore your data fairly easily. See blog article above for step by step instructions.
Root - Unit comes with root accessible in adb. SuperSU can be installed easily. There are 2 methods for installing superSU. The first method is an overwrite of the boot partition with a pre-rooted image. Problem here is if future upgrade makes boot partition changes, this method will overwrite with an older version. I recommend method 2, which modifies the existing boot partition ( need source so I can provide credit ).
https://forum.xda-developers.com/showpost.php?p=69648860&postcount=84&nocache=1&z=8361786322568856 (over-writes boot partition / may not work on Joying Feb update )
https://drive.google.com/file/d/0B4qmTV7N4JliSjZMdGg3Z18wbkU/view?usp=sharing ( modifies existing boot partition )
OS & Google Apps - Android 5.1.1 ASOP based w/ pico installation of google applications. Voice actions are supported with installation of 'Google App' from play store. No support for google search talk back.
Recovery- A recovery partition is present but does not have any type of graphical UI. It does look like a complete stock android ( command line ) recovery, but no access using USB is available. It maybe be possible using PC-PC OTG cable.
SD Cards - I have not heard of any sdcard size limitations, up to 200GB have been reported to work. Must be formatted as FAT32. NTFS, exFAT, and ext3/4 do not work. You can format a USB stick with ext4 and it will work fine.
Google Voice Calling - Stock BT dialer crashes when being called from google applications ( such as google voice search ). Workaround is available.
https://forum.xda-developers.com/an...oogle-voice-to-initiate-calls-joying-t3528923
Enable OK Google from any screen - https://forum.xda-developers.com/showpost.php?p=72447390&postcount=968
Bluetooth Tethering & BT Settings - Bluetooth tethering, connects instantly, very reliable connection, works great for streaming music, gps etc. Saves phone battery vs WIFI hotspot. Limited to ~2Mbs ( slower than WIFI sharing )
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
(also good discussion here on the effects of process killing when entering standby )
Difficult to pair BT devices - Forces device pairing into database - Device pairs normally once HU thinks it has connected previously. I was able to pair TPMS, keyboard, etc using this method(s).
https://play.google.com/store/apps/details?id=com.brachcon.btautopair&hl=en
Modified stock bluetooth app to allow connection to all devices
https://forum.xda-developers.com/showpost.php?p=71280945&postcount=88
Backup Cam guideline mods - Make your lines match your camera view
https://forum.xda-developers.com/showpost.php?p=70325711&postcount=403
Apps not working after resume - The joying code will kill most applications when going into standby. This is really bad for apps that are supposed to be run at boot and background process, as they are not restarted when exiting standby. Symptoms include, widgets not updating, apps not getting GPS lock, process show running but background services are no longer running. This can be fixed by installing an updated apk file in /system/app/Sofia-1-C9-Server-V1.0 which removes the task killer. Also the key/button mods V2+ (below) will remove the task killer.
https://forum.xda-developers.com/showpost.php?p=71047452&postcount=62
Key/Button Mods - Extend the usefulness of your steering wheel keys and on unit buttons- V2+ also removes app kill on standby.
https://forum.xda-developers.com/an...-units/joying-2gb-steering-wheel-key-t3543390
If you just want to change the SRC button to call up google voice search, go here. ( also removes task killer )
https://forum.xda-developers.com/showpost.php?p=70480258&postcount=549
Immersive Mode / removes top navigation bar - No app needed - Full Screen on apps you choose, can be set from adb w/ root. Argument is list of package names separated by "," or "*" for all apps. ( survives reboot )
Specific apps:
settings put global policy_control immersive.full="com.google.android.apps.maps,com.pandora.android,com.spotify.music"
All apps:
settings put global policy_control immersive.full="*"
Clear / back to default
settings put global policy_control immersive.full=
Change Overscan - problems touching the corners, changing overscan can help:
https://forum.xda-developers.com/showpost.php?p=71492575&postcount=169
Phone/Tablet view on apps - No app needed - Change from 160dpi -> 161dpi gives "phone" view of many apps instead of "tablet" with no noticeable size change to other things. Done via adb. Requires reboot to take effect.
> wm density 161 # ( phone mode apps )
> wm density 160 # ( original tablet mode apps )
Heatsink mod Unit can run hot at heavy cpu load (such as benchmark testing). Can slightly reduce performance by throttling. Some users opt to add additional heatsink/fan to reduce temperatures.
https://forum.xda-developers.com/an...inside-look-joying-android-head-unit-t3546872
Red Themed Radio - Re-theme of stock apps - Don't like the look, change it. Can be done easily by unzipping the apk file, change images, rezip and install.
https://forum.xda-developers.com/showpost.php?p=70367793&postcount=434
More Radio Mods ( Layout change, more colors )
https://forum.xda-developers.com/showpost.php?p=71625005&postcount=286
xposed / xposed framwork - At this time, I am not aware of any way to make this work with the new Joying units. I have tried several packages and all have resulted in a non-bootable system. Please let me know you go get it to work.
Viper4android - Installer script that works on these models
https://forum.xda-developers.com/showpost.php?p=71317345&postcount=101
Nova or other launcher - Need to freeze or remove stock Joying launcher(s) in some cases, for other launchers to work correctly.
Other very useful Joying 2gb/sofia threads:
Audio Discussion / DACs - https://forum.xda-developers.com/an...ts/joying-2gb-sofia-headunits-common-t3577217
https://forum.xda-developers.com/an...pment/joying-android-5-1-1-2gb-units-t3465561
https://forum.xda-developers.com/an...opment/2gb-ram-intel-cpu-heres-specs-t3468322
Yes this is really needed. A FAQ with overview links and tips in just one post
Some people mentioned it was possible to boot into a restore function from a memory card with the update zip. If true, do we know what the exact process is? Any keys need to be held down?
Update, verified this procedure works:
sonof said:
I did recover from endless Android logo (resulting from trying to root with Joying HU root.zip found in this thread).
I did the following:
Put latest Joying update files to microSD card and insert it to GPS slot. Press and hold both reset and power buttons. Once it boots continue holding reset button.
This lead to automatic install of Joying update files and my HU was back alive but I hate the Joying company for not providing means to enter recovery and a complete ROM.
Edit: For me it did not ask if I want to update or not. It just began updating automatically. In contradict to the post above. But I was unable to boot to Android when I tried this.
Click to expand...
Click to collapse
My VW has reverse parking sensors. Does it not support those?
Just installed this unit. Speedwise it's night and day compared to my old Erisin (1gb 3188). Display is nice and crisp. Bit of a fiddle getting it mounted because of all the crap that needs to be stuffed behind it, but after some swearing and elbow grease I got it secured.
From the instructions, I cut an orange wire because I don't have a backup camera. I do however have optical parking sensors. On my Erisin this was supported (it showed a car model and visual indicators on screen). This unit doesn't appear to have this function. Can anyone confirm? I still get the beep from the speakers, so it's not really a big issue, but would be nice to know.
---------- Post added at 10:49 PM ---------- Previous post was at 10:49 PM ----------
catu said:
My VW has reverse parking sensors. Does it not support those?
Click to expand...
Click to collapse
Didn't see your post before asking the same question
anotheruserx said:
I'd like to work on this one.
But I have two questions;
1) did you manage to get any logs of how it failed?
2) When you made it unbootable, what was the exact procedure you used to recover the unit?
Click to expand...
Click to collapse
I didn't get any logs, as I couldn't connect to it until I reloaded the ROM. If I was able to make a USB connection, at least I could have looked at the logcat.
Procedure to recover: Insert USB drive with ROM, push recessed reset button, wait 30m for ROM to install, set up apps again. I have this procedure down pretty good. - The joys of playing with the system partition without USB access or recovery tools.
catu said:
My VW has reverse parking sensors. Does it not support those?
Click to expand...
Click to collapse
Actually, it turns out it does, however only when there's an obstacle (hopefully we can change this). Yesterday I only tested while stationary. Today I used it while driving, and noticed that whenever the sensor picked something up, the unit does actually display the sensors. It feels next to useless for me when it only shows on beeps, but at least we know it's there.
Well, that is the way my discarded Newsmy worked. Takes getting used to, but you then again you don't really need confirmation that "nothing" is in your way
Will need to think about this then, thank you.. Cant make up if I want this or the Ownice C500.
catu said:
Well, that is the way my discarded Newsmy worked. Takes getting used to, but you then again you don't really need confirmation that "nothing" is in your way
Will need to think about this then, thank you.. Cant make up if I want this or the Ownice C500.
Click to expand...
Click to collapse
After updating to the January firmware parking sensors are gone completely.
edit: enabling "radar" is the solution
Installed supersu (like described in this thread) yesterday and updated it from the play store. Worked fine.
Then I installed Viper4android, also from the store. I didn't expect it to work, but it does! Driver installed, and after a reboot it does exactly what it's supposed to.
Also installed Nova Launcher and set as default home. No issues with that so far. I have not frozen or uninstalled any of the original launchers.
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold. We had minus 8 degrees centigrade here and it took more than 10 minutes before the backlight came on. The radio is playing music and it is actually possible to change channel as long as you know where to touch the monitor. Today it was 5 degrees and it took only about 3 seconds before the backlight came on. I wrote Joying about it and they confirmed to me that there was an issue with 8 inch models for VW. They told me that they were working on a completely new firmware that would fix the problem. I told them that to me it seemed to be a hardware problem and how they wanted to fix that with a software. Their answer of course "No worry my friend ......". I told them that I wanted to return the radio because a radio that doesn't work when it is cold is useless to me. They told me that I would have to send it to China so that their engineers could investigate the problem. I then told them that I had bought it from a German website and it was delivered to me from Germany so if their wanted it to be sent to China then they would have to pay me for it - in advance. They told me that their warehouse in Germany did not accept any returns so it was impossible for me to return it. Then I opened a case with Paypal for selling defective merchandise. Then suddenly their warehouse in Germany was accepting returns. I had put this text also on the Joying Forum, but of course they deleted it. So when dealing with Joying and in case you have problems my advice is to be very tough on them otherwise they will BS you.
Kurt Lund said:
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold.
Click to expand...
Click to collapse
I have the same problem on the same unit. With the car headlights off, backlight is dim when it's cold, but gets brighter when it has time to warm up. And when the headlights are on, the backlight isn't on at all until it warms up.
I thought about writing Joying about it but I expected the kind of response you got. Plus, I've had my unit for a few months already so a PayPal claim isn't an option. Please let us know if you hear anything else about it from Joying.
Hi Joshnat,
Yes we have the same problem. Sometimes I can get mine to light up by turning the headlights on and off a couple of times. Are you sure that you cant make a Paypal claim? As far as I know you have 180 days.
Anyway, you should write to them and let them know that you know that many others have this problem.
Regards
Kurt
Kurt Lund said:
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold. We had minus 8 degrees centigrade here and it took more than 10 minutes before the backlight came on. The radio is playing music and it is actually possible to change channel as long as you know where to touch the monitor. Today it was 5 degrees and it took only about 3 seconds before the backlight came on. I wrote Joying about it and they confirmed to me that there was an issue with 8 inch models for VW. They told me that they were working on a completely new firmware that would fix the problem. I told them that to me it seemed to be a hardware problem and how they wanted to fix that with a software. Their answer of course "No worry my friend ......". I told them that I wanted to return the radio because a radio that doesn't work when it is cold is useless to me. They told me that I would have to send it to China so that their engineers could investigate the problem. I then told them that I had bought it from a German website and it was delivered to me from Germany so if their wanted it to be sent to China then they would have to pay me for it - in advance. They told me that their warehouse in Germany did not accept any returns so it was impossible for me to return it. Then I opened a case with Paypal for selling defective merchandise. Then suddenly their warehouse in Germany was accepting returns. I had put this text also on the Joying Forum, but of course they deleted it. So when dealing with Joying and in case you have problems my advice is to be very tough on them otherwise they will BS you.
Click to expand...
Click to collapse
You may have a faulty screen, my first one did something similar and wasn't very responsive to touches. I returned and my second unit was like night and day with how much better it looked and worked.
Has anyone got a factory backup camera to work? I have a 2015 Camry and right now I have the older Pumpkin rk3066 and the place that installed it hooked up the factory backup camera. I got my new Joying hu yesterday and am going to install tomorrow myself. I'm really hoping I can use my factory camera with this head unit also.
Sent from my LG-H918 using Tapatalk
mad212 said:
Has anyone got a factory backup camera to work? I have a 2015 Camry and right now I have the older Pumpkin rk3066 and the place that installed it hooked up the factory backup camera. I got my new Joying hu yesterday and am going to install tomorrow myself. I'm really hoping I can use my factory camera with this head unit also.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
I have the same car and HU, my oem backup carmera works. I bought a harness on Amazon including backup camera, USB, and aux in.
https://www.amazon.com/gp/product/B01BM3QGCO/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
Quick tip:
You can adjust backup camera brightness, saturation and contrast by touching the screen while backup camera is on.
Is there a trick to putting in the sd cards? Mine won't click in so it won't mount.
Edit: Forget it i just had to get the edge of a screwdriver and push it in. Had me worried for a minute.
Sent from my LG-H918 using Tapatalk
Does anyone have a link or info on the dummy proof DIY on how to Root the joying unit? I want to install some of these enhancements so need to root the device and have never done it so was looking to see if anyone has a link or good write up for the slow like me. Appreciate it. I have a Joying 2gb 7 inch unit.
Looking to install this option
https://drive.google.com/file/d/0B4q...ew?usp=sharing ( modifies existing boot partition )
thedru13 said:
Does anyone have a link or info on the dummy proof DIY on how to Root the joying unit? I want to install some of these enhancements so need to root the device and have never done it so was looking to see if anyone has a link or good write up for the slow like me. Appreciate it. I have a Joying 2gb 7 inch unit.
Click to expand...
Click to collapse
Within the zip there is a file with instructions - HOWTO.txt
How-To install:
1. You need a Windows PC that is connected to the same WiFi network as your HU.
2. Unzip the attached file somewhere to your disk.
3. Run CMD.exe as Administrator
4. Change directory to the folder that you unzipped.
5. Run the install.bat script with an IP address of your HU as a parameter:
C:\Users\<username>\Downloads\Joying_JY-UL135N2_SuperSU> install.bat 192.168.123.137
6. Wait until script finishes and reboot your Head Unit.
7. DONE!
You should now have the SuperSU application working.

MTCD_MX for Opel Insignia (Does MCU update have any afect on key mapping?)

Hi,
I'm new to the forum, and I have searched for an answer but have not found anything.
Hopefully it's a no-brainer for u experts out here.
I'm very tempted to try an update available for MTCD_MX - later than my 1.97b.
I have 5.1.1 MTCD_MX built into my car, and it works great with the original buttons of the dashborad & steering Wheel etc.
Anyhow, at the moment I have no possibility to change the key-mapping in my unit (nothing happen when I open the Key-mapping tool that came with the unit) so I want to know if an update from 1.97b to 2.59 will have any effect on the key mapping at all?
Or maybe there are other reasons why I sohuld / should not do an update - if so, please let me know.
If anyone knows this, please let me know in advance of doing something I would regret
Thanks in advance
Hello, you must modify the car model in the setting factory. You can try GM RAISE
I am running a px5 in a 2010 Insignia and running MX_2.75 on it with all the key mapping running fine. From what I can tell (and I am open to correction here) the key mapping is all done through the canbus adapter - this is why you can't change the key assignments (so my supplier in the UK says).
Thanks both for your comment.
Are updates possible through USB or is mandatory with SD-card via GPS-slot necessary?
(I failed my attempt with USB - so everything was restored to factory, still 1.97b)
GotJsv said:
Thanks both for your comment.
Are updates possible through USB or is mandatory with SD-card via GPS-slot necessary?
(I failed my attempt with USB - so everything was restored to factory, still 1.97b)
Click to expand...
Click to collapse
I use USB without a problem. Are you sure that it is a suitable img?
You might also need to update to Android 6.
GotJsv said:
Hi,
I'm new to the forum, and I have searched for an answer but have not found anything.
Hopefully it's a no-brainer for u experts out here.
I'm very tempted to try an update available for MTCD_MX - later than my 1.97b.
I have 5.1.1 MTCD_MX built into my car, and it works great with the original buttons of the dashborad & steering Wheel etc.
Anyhow, at the moment I have no possibility to change the key-mapping in my unit (nothing happen when I open the Key-mapping tool that came with the unit) so I want to know if an update from 1.97b to 2.59 will have any effect on the key mapping at all?
Or maybe there are other reasons why I sohuld / should not do an update - if so, please let me know.
If anyone knows this, please let me know in advance of doing something I would regret
Thanks in advance
Click to expand...
Click to collapse
You cant use key mapping because it's CANBUS buttons. Updates won't fix this. You can use the app in the development section to address this issue.
I just upgraded to a px5 with 4gb - it's quicker, but remapping is not an option.

Hizpo Head unit with inverted screen

Hello everyone. I’ve got a hizpo stereo that a friend of mine give me a few weeks back. The numbers on the side of the radio is ADY17009. It’s running Android 7.1.2. The problem I’m having with it is the screen is inverted. I’ve tried the reset button tried erasing everything no luck. I tried accessing developer mode pressing build number 7 times and it didn’t let me access it. Anyone know where I can get a copy of the stock firmware and operating system on this thing or can I upgrade it to the latest and hopefully it will fix the issue. I can’t sign up on hizpo website. Every time I try to I get a connection timed out error. I had posted in the general forum so please delete that. That’s what I get for not reading lol.
robert6983 said:
Hello everyone. I’ve got a hizpo stereo that a friend of mine give me a few weeks back. The numbers on the side of the radio is ADY17009. It’s running Android 7.1.2. The problem I’m having with it is the screen is inverted. I’ve tried the reset button tried erasing everything no luck. I tried accessing developer mode pressing build number 7 times and it didn’t let me access it. Anyone know where I can get a copy of the stock firmware and operating system on this thing or can I upgrade it to the latest and hopefully it will fix the issue. I can’t sign up on hizpo website. Every time I try to I get a connection timed out error. I had posted in the general forum so please delete that. That’s what I get for not reading lol.
Click to expand...
Click to collapse
This is usually a symptom of a loose connection in the hardware(believe it or not, a good shake, tap or bump this way or that way has been known to solve this) or a symptom of the sensor needing to be recalibrated(also solved by shaking/bumping or even lightly dropping on a soft surface from about 12 inches, but doing it while the device is powered off)
Or, if the device still functions correctly, there are apps that can recalibrate the sensors for you.
As for finding the stock firmware...
If a Google search for:
"Return to stock (your model number)"
Is not finding anything, then it probably isn't available. These cheap, off brand devices usually do not get any software support of any kind from the manufacturers, they do not release the stock source or the stock firmware to the public.
If it came down to really needing to flash the device, you'd have to look for a firmware from a device that uses the exact same hardware as the device you own. That can be very difficult, it requires opening the device to look at the numbers on the hardware components, then using those to compare to other devices. If one of those devices is the same as yours and has a firmware available, you can use it.
Sent from my LGL84VL using Tapatalk

Nokia 5.3 doesn't vibrate

Hi, I can't find any thread about this topic, I hope I didn't miss anything.
The problem:
In October, I've bought Nokia 5.3 with Android 10 in Czech Republic (Europe, probably German or UK distribution) and I found out it doesn't vibrate. I tried an app that's dedicated to vibrating but it doesn't do anything and switching to vibrate-only mode using the menu invoked by volume keys switches the phone basically to a full DND mode.
I searched the Internet and found a few reports of other users of Android 10 phones with a similar problem. (None of them, however, with a Nokia phone, at least not concretely Nokia 5.3). I hence assume it's not a defect of my phone but rather a software bug in Android. I'm of course rather reluctant to test this by returning the phone and getting a new one thru warranty because I did put some time into setting this one up. I reached out to the Nokia support but they were unable to help me further than advising me to check a few settings (which were OK) and told me I probably need to wait for an OS update.
The question:
Do you have Nokia 5.3 and do you or do you not have the same problem?
Thank you very much for your experience and suggestions.
Hi,
I have Nokia 5.3, bought it recently. However I hate vibrations so that was the first thing I disabled in the settings. It was vibrating like hell . Check your phone settings, there is an option to turn it on and off.
Cheers!
Hi toppicks,
thanks for confirming that it's obviously not a software issue. I checked all the settings I could, none of them change anything.
edison23 said:
Hi toppicks,
thanks for confirming that it's obviously not a software issue. I checked all the settings I could, none of them change anything.
Click to expand...
Click to collapse
do a factory reset
T.Y.M.SAI said:
do a factory reset
Click to expand...
Click to collapse
Finally, I found time to do the factory reset, it didn't help. I tried with the SIM card and also without it, the phone still doesn't vibrate. I'll go return it to the vendor on Monday, hopefully, I'll get it resolved that way.

Pumpkin brand PX30 MTCE HT - seeking MCU update

Hi,
I have a PX30 head unit with Pumpkin branding.
I've updated the ROM to Hal9k which is great but the unit often fails to boot sitting on a black screen. Repeated attempts to reset the unit, and it eventually turns on.
Auto sleep is not working either so its always cold boot, even if the unit has only been turned off a few seconds.
I would like to try updating the MCU software but cannot find a file.
The version info is: MTCE_HT_V3.60_1, Aug 14 2020 10:19:07
I have tried to register for manufacturer forum to ask there but didn't get a response for account approval.
If there is a newer version that would be great, equally the same version or an older version that is known to be stable could also help me.
Thanks!
Looks like I managed to answer my own question, I found version 3.71 on a German forum, here is a link to it.
210.4 KB file on MEGA
mega.nz
Still don't have the sleep working, if I change it to delay shutdown or sleep it makes no difference and its a cold boot every time. I've checked my wiring and I'm sure the unit is still getting +12v from the car when ignition is switched off.
Anything else I can try or check?
Hello, try if you don't have Default power status - OFF: Factory settings/126/Other/Default power status - set ON or if the radio does not remember saved stations, then set: remember last state.
Pavel-71 said:
Hello, try if you don't have Default power status - OFF: Factory settings/126/Other/Default power status - set ON or if the radio does not remember saved stations, then set: remember last state.
Click to expand...
Click to collapse
Hi, I tried this, the power settings don't make any difference.
If the unit is only off for less than say 1 hour, it will boot up again OK. It's not instant on like some youtube videos, maybe 10-20 seconds. I guess this is still standby mode?
If the vehicle is parked overnight, unit will not boot, just get a black screen. It takes several (usually 10+) attempts to reset it before it eventually boots.
This is really annoying, is there anything else I can check? The only thing I didn't change yet is the "customer type" number, would this make any difference?
Changing the customer version is not recommended, serious control errors and sometimes a black screen may occur, but it is up to you if you take that risk. Sometimes a new MCU update will make this change. The last number after the underscore indicates the customer version, MTCE_HT_V3.60_1, the last one is 1 so the customer version will be 1. If you have updated the MCU this may have changed. It is best if you have saved the factory settings in the dmcu.cfg file, with this file the MCU will be updated and all settings will be returned to the original settings. Factory settings - EXPORT button and save the dmcu.cfg file to external storage, if you do not specify a path, it is saved to the root directory by default. If the error was caused by the update to Hal9k, then the problem may be with this update, try to update again with wipe data or reinstall the original ROM. If that doesn't solve the problem, try a different car type in the canbus factory settings. Or the canbus adapter may be faulty.
Thank you, that is helpful. The unit was already doing this before any updates, I was hoping that updating the ROM and MCU would help but it seems to have made no difference.
I don't have a canbus adaptor.

Categories

Resources