• Update Bulletin
  • DUDUOS 3.6 Beta Released Just in Time for Chinese New Year!

Hi,
I am currently using Dudu 3.5 (V241222), can I install Dudu 3.6?

    Dudu OS has become more responsive, it keeps applications in RAM better. Or maybe I'm making it up, but that's how I feel. Of course, I always restore factory settings.

      lockc No, it is not necessary. As long as you don't move the files from Factory Reset folder tot the root of USB (leave the file structure untouched) your settings will be preserved.

      Since day one i didn't do a factory reset with an update. Working nicely until now.
      Bought it in March 2024

      Is there any way to update to this beta release WITHOUT using USB? I have tried the on device (downloaded the .7z directly from Chrome to downloads directory) but I believe for Beta updates, this does not work. Reason being....the Dudu is in my kids car and it seems the USB (both the external cord and the OEM connection) has stopped working. Maybe a short? Dirt might have got into the USB extension. ugh.

        Спасибо за обновление. Скачал на флешку. Поставлю отпишусь. Приятного отдыха.

        Tswire I think I've heard that it is possible from the root dir of the head unit. I think you have to extract the .7z

          lockc I think it's worth doing this because sometimes minor bugs happen and something might not work as it should. Unless you notice minor errors, you do not need to perform a factory reset.

          JhonnyD

          thanks, will give it a try today. I have it extracted but in the downloads. Need to fix the USB port anyway but eager to try 3.6

          JhonnyD
          Tried that and didn’t work. Copied both the 7z and the extracted files to highest directory I could (Local) and then tried a local Update pointing to each. Neither worked. Hmm

          Edit. Rebooting head unit seemed to work. Found the update file and doing it now. Probably have to delete those files after

          Not sure what items 6 and 10 with respect to added car integration and more advanced integration entails? Like more brands of cars? If so Nissan is left i the dust again.

          Tswire i upload it to the screen with the share app. My usb do not work as well..

            Denny7

            Weird. I did just check the USB and it charges and works for other things. Hmmm. Ya as long as you extract the 7z and place all the files into Local (root) and reboot your unit it works. It also deletes the zip and other things after installing

            FM radio alternative frequencies work in one direction, it searches for an alternative stops and does not return to the previous one.In my opinion it does not work properly, alternative stations should not be saved as an additional FM station in memory.FM radio and alternative radio stations work on the principle that the radio virtually remembers an alternative FM station and switches automatically.That's why it doesn't go back to the previous radio station because it doesn't remember the FM stations virtually. Previously, radio stations received better reception, now they fade out more often and do not receive signal.

              wybitny2
              Well, I don't understand what do you mean that it woks only in one direction, I haven't experienced anything like that in this version. Actually, there is no need to store the alternative frequencies anyhow, because AF list of the surrounding transmitters should be transmitted in RDS on each of the station's frequecny, so after switching to new frequency, it shoul load AF list from that transmitter.
              Anyway, so far I didn't find any noticeable difference in AF behaviour between previous version 3.5 an now the 3.6 on my main unit installed in my car. I'm testing it also on my secondary test unit I have now on my desk in the office, I'll try to sum up my findings with the AF when I find some time to play with it....

                wybitny2
                RDS alternate frequencies (up to 25 according the standard) should be sent in the RDS metadata in the RDS stream transmitted by the station. The tuner doesn't need to "search". The tuner needs to check the alternate frequencies in the RDS metadata stream, while comparing it with the pi-code of that radio station. It can simply "jump" from one frequency to the next. So if it simply checks and encounters a stronger frequency, but having a different pi-code, it should not switch.

                RDS doesn' t work correctly at the moment. It is a hit and miss.
                Sometimes it works correct.
                But sometimes you have a perfectly strong signal and suddenly it switches to a completely different station on a completely different frequency with a completely different pi-code.

                  jamar It works like AF before but it works badly. The station should not be saved on the list but should be remembered virtually like in any FM radio. Switches to an alternative frequency but does not return to the previous correct frequency. The alternative frequency should not be saved in the list with all stations but should be changed virtually. This is the first Android radio application where alternative frequencies are saved in a list with all stations. Navradio has the ability to add alternative frequencies but they are not saved on the list with all fm stations. They are saved virtually.

                    surfer63
                    Exactly, well written. I'll just add that there are actually two methods of sending AF list in RDS, and with method B there can be sent multiple (max. 8) AF lists with up to 12 frequencies, so it can be used by stations which needs to send more than 25 alternative frequencies on single transmitter, or to differentiate between frequencies belonging to different regions, which can broadcast different regional programs at times. This is reffered as AF REG (or Regional) on OEM or big brands units. it is actually used by several multi-regional stations here, as I've observed... But, for now, correctly working simple AF without the B method would be huge improvement ;-)

                    By the way, as it seems by your description in the second paragraph, that you have similar experience with AF like I do, did you notice any difference with this in the 3.6 version? Since the AF optimalisations were listed in the changelog and after updating I'm experiencing still the same glitches, I thought maybe I need to do a full reflash with factory reset for the changes to apply corretly, but maybe there are not that significant changes and we simply need to wait a bit more for the devs to come back from holidays and look into this a bit more...