DUDU-Meng

  • 4 hours ago
  • Joined Apr 22, 2024
  • Mikescotland Thanks Mike. I appreciate the explanation. It, however, frustrates the living sh*t out of me that I've been misled by essentially fraudulent advertising. My selection of this damned unit was based on an essentially pure unaltered digital signal being delivered to my processor. If the unit is doing all of this BS conversions then there's no benefit in optical of standard RCA which is unsurprisingly what I've found to the case.

    @DUDU-Meng you guys need to resolve this ASAP and modify the lies in your product description. You are saying one thing and delivering something completely different.

    • Mikescotland
      and @DUDU-Meng
      Yes, Mike is correct.

      The 7z file only contains:
      2025-05-16 11:27:17 ....A 2592044 872659 lsec6318update
      2025-07-15 08:03:02 ....A 43253 Stm32ud.bin

      whereas the zip file contains:
      0 2025-07-15 08:33 DUDU7 MCU 20250715/
      144726 2025-07-15 08:03 DUDU7 MCU 20250715/N32F030x8_Flash.Hex
      43253 2025-07-15 08:03 DUDU7 MCU 20250715/Stm32ud.bin

      Please explain.

      • mohammadfadel1987 No. The DUDU OS is developed only for FYT based head units. As long as you don't have the word FYT in your MCU description, no chance. Sorry to tell you this, but also in the future I don't see other devices to be supported. Maybe @DUDU-Meng can explain you better. The best solution for you is to buy a DUDU device.

      • @DUDU-Meng @dudu-lai

        1. What's the point of these icons (tpms, gps, etc) if they don't do anything? Tpms alarm and icon doesn't change. In fact I can turn the icon on even if I don't have tpms connected at all. The icon just sits there.
        2. How to get these icons? They appear on your pictures however there is no way of showing them even if they are passed via canbus? False advertisement?
        • reg66

          I understand, but in another post (https://forum.dudu-auto.com/d/1880-urgent-need-help-restoring-aptx-hd-after-flashing-bluetooth-firmware-by-mistake/13), user @DUDU7Dubai upgraded the BT firmware to the latest (and still the latest) BT firmware of 20250705.7z and his issues were gone after flashing the 20241231.7z BT firmware.
          Now @acvdmolen had issues flashing the latest BT-firmware, which is that same BT firmware from @DUDU7Dubai and @acvdmolen could correct it by flashing the latest MCU firmware.

          There seems to be an incompatibility between the several firmwares.
          Dudu ( @DUDU-Meng ) should clearly state which combinations are working combinations.
          You should not make users try all kind of combinations untill you find a working one.
          For example:

          • Use the latest BT firmware (20250705) only with the latest MCU firmware (20250715).
          • If using older BT firmware and/or older MCU firmware: do not upgrade only one of them (or something alike).

          @DUDU-Meng : Please confirm or please explain.

          Edit: On my previous Joyings (2-5 units ago) and I know from Teyes, that sometimes when new hardware, functionality or "other changes" were done, the MCU firmware was part of the normal firmware upgrade. It almost seems here it is the same with the new MCU and BT firmware.

          • DUDU-Meng
            @DUDU-Meng Just in case anyone needs to, now or in the future, can they downgrade MCU if the updated version is worse or causes different issues?

            As in, try the updated MCU and if needed reflash the original MCU file...

            Cheers

            • acvdmolen
              You ask that to yourself?

              Anyway: The MCU embedded software is very specific software. It is not as simple as other software.
              It integrates the Android layer with the hardware normally not in Android, like the car itself, the canbus, FM-chip, etcetera.
              You can't compare that to a PC where the UEFI (previously BIOS) was only responsible for the starting up and checking the basic hardware and then start the OS. Everything else is driver based. Android works different. And in these units the MCU does much more than the UEFI.

              On the other hand: As there is only one DUDU7 model (and Dudu6 and 4/5), without differences, it should be fairly simple for FYT to do an upgrade of the MCU firmware.

              But why upgrade? You upgrade because there is a bug and something not working.
              In "software land" there are apps that are very stable and have not been updated for years. If that is the case for the MCU firmware, there is simply no reason to upgrade.

              @acvdmolen : What issues did you have with your Bluetooth. It clearly says NOT to upgrade if you do not experience issues.
              And for that Bluetooth firmware update: There is a down-grade which has nothing to do with the central MCU firmware. @DUDU-Meng already shared it in another post.

              • DUDU-Meng @DUDU-Meng Thank you for the reply

                Let me explain the situation more clearly to avoid any misunderstanding during translation

                Before I used the OTA firmware flashing option in the settings, aptX HD was working perfectly on my Nothing Phone 2. After flashing, aptX HD stopped working completely. The phone itself fully supports aptX HD and even higher codecs like LDAC, so this is not a limitation of the phone

                Right now I can still connect, stream music, and make phone calls without any issues. The only problem is that aptX HD is no longer available as a codec, which means I lost the ability to use HD music streaming. As far as I know, aptX HD is the highest audio codec supported by your unit

                I have already tried the following:

                Factory reset of the Android unit

                Deleted the Bluetooth pairing on the phone and repaired it again

                None of these steps fixed the issue. The only change that caused this was flashing the firmware

                So I am asking again — can you provide the original Bluetooth firmware that was shipped with the DUDU7 12GB 256 model, which supported aptX HD?

                Thank you

                • DUDU7Dubai You must understand that in order to get any help the most important piece is this "device info". And although this mandatory device info is on the first page of the forum, nobody reads it or attaches it to their posts. And sometimes this thing is annoying also for me. Believe me that I read this forum almost everyday. And the members of the DUDU team try to explain everything to everybody. The problem is that sometimes the translation makes a mess. I am more than sure that @DUDU-Meng didn't want to say waste of time.

                • Hi

                  I would like to check if there is CANBUS support for the 2011 Mazda Axela. The original head unit looks something like this:

                  The car did not come with the original unit installed but can confirm this was the unit installed previously. The unit currently installed is a JVC unit. The OEM wiring has not been altered in any way as the previous owner used a harness.

                  There are other units such as Eonon and Ainavi that support this car's CANBUS protocol using a Raise CAN box (unsure what box is provided exactly) so I'm thinking it should work with a DUDU unit as well, assuming there is a CAN profile for this and/or similar car.

                  The following features are known to work with a Raise CAN box and 2010-2012 Mazda 3 CAN profile:

                  • BOSE audio (this car does not have the BOSE package but the non-BOSE 6 speaker set up)
                  • A/C controls as long as the car has automatic climate control (this car has dual auto climate control)
                  • steering wheel controls (this car has OEM SWC installed)
                  • driver information screen (normally displays music such as track name, duration, FM/AM info)
                  • screen brightness dim/change to dark mode when headlights on

                  If someone has installed a DUDU unit in this (or a similar) car, please let me know if these features work.

                  @DUDU-Meng or @dudu-lai are you able to share the list of CAN profiles for Mazda vehicles available on the unit - both Raise and HiWorld. Also please confirm if these functions will work with DUDU.

                  If you need any more photos, please let me know and I will try to get them as soon as possible. I am installing this unit in a friend's car so do not have access to it right now so may take a few days.

                  Thanks

                  EDIT: The following are photos of the connectors from the actual car



                  • Jurka This is a long shot diagnosis but have you physically inspected the exterior housing of your antenna? In some cases the plastic housing on roof antennas starts to fail over time and you can see worse reception after a rainstorm. Again, its a long shot diagnosis but just trying to think of something for you. Maybe @DUDU-Meng has another suggestion.