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

gismo I did a factory reset, I didn't notice any errors that would annoy me. I didn't do a reset before and there were more errors.

    • Edited

    wybitny2 good for you but you don't have a VW with canbus steering wheel, right? This is a definite error, newly introduced and definitely annoying https://forum.dudu-auto.com/d/923-v36-canbus-bug-skip-fwd-rwd-now-is-the-same

    I posted the error 6 days ago and nobody from DUDUAUTO reacts - probably the most annoying part of this.

    Others have BT issues (not me).

    I use DuduOS also because I want to overcome the need to do factory resets for each upgrade. Android as such can do this very well without factory resets. On previous FYT units it was just ill programming that triggered the need for factory resets. Don't ask me to go back to that 😉

    NTFS ouch, the worst file system known to man 🙂 but I do understand why

      piper

      I am both a linux and Unix user since 1989 running the very first Linux kernels, so I have nothing with Windows.
      When talking about FAT or derivatives (apart from exFat), you are right: They are not good..
      NTFS though is a very good file system. "worst file system known to man" is complete nonsense.

        Ich glaube, dass diese Version die bisher schlechteste ist.
        Ich habe ein downgrade auf 3.5 gemacht.
        Ich konnte nicht einmal die Helligkeit vom Bildschirm einstellen.

        Было бы неплохо. добавить приложение на фронтальную камеру, так как такси в России и Беларуси, требуют верификацию личности, и для этого нужно проходить фотоконтроль.

        YAOXILONG can you add service to Bluetooth cache cleanup ? import android.app.Service;
        import android.content.BroadcastReceiver;
        import android.content.Context;
        import android.content.Intent;
        import android.content.IntentFilter;
        import android.os.IBinder;
        import android.util.Log;

        import java.io.IOException;

        public class BluetoothCacheClearService extends Service {

        private static final String TAG = "BluetoothCacheClear";
        
        private BroadcastReceiver shutdownReceiver;
        private BroadcastReceiver rebootReceiver;
        
        
        @Override
        public void onCreate() {
            super.onCreate();
        
            // Shutdown receiver
            shutdownReceiver = new BroadcastReceiver() {
                @Override
                public void onReceive(Context context, Intent intent) {
                    if (Intent.ACTION_SHUTDOWN.equals(intent.getAction()) ||
                            Intent.ACTION_POWER_OFF.equals(intent.getAction())) {
        
                        Log.d(TAG, "Device is shutting down. Clearing Bluetooth cache.");
                        clearBluetoothCache();
                    }
                }
            };
        
            IntentFilter shutdownFilter = new IntentFilter();
            shutdownFilter.addAction(Intent.ACTION_SHUTDOWN);
            shutdownFilter.addAction(Intent.ACTION_POWER_OFF);  // Some devices use this.
            registerReceiver(shutdownReceiver, shutdownFilter);
        
        
        
            // Reboot finished receiver (for after a reboot)
            rebootReceiver = new BroadcastReceiver() {
                @Override
                public void onReceive(Context context, Intent intent) {
                    if (Intent.ACTION_BOOT_COMPLETED.equals(intent.getAction())) {
                        Log.d(TAG, "Device has booted. Clearing Bluetooth cache.");
                        clearBluetoothCache();
                    }
                }
            };
        
            IntentFilter rebootFilter = new IntentFilter(Intent.ACTION_BOOT_COMPLETED);
            registerReceiver(rebootReceiver, rebootFilter);
        
        
            Log.d(TAG, "Service created.");
        }
        
        
        
        private void clearBluetoothCache() {
            try {
                // This requires root privileges.  There is NO non-root way to reliably clear the Bluetooth cache.
                Process process = Runtime.getRuntime().exec("pm clear com.android.bluetooth"); // Or the specific package name for your device.
        
                int result = process.waitFor();
                if (result == 0) {
                    Log.i(TAG, "Bluetooth cache cleared successfully.");
                } else {
                    Log.e(TAG, "Failed to clear Bluetooth cache. Return code: " + result);
                }
            } catch (IOException | InterruptedException e) {
                Log.e(TAG, "Error clearing Bluetooth cache: ", e);
            }
        }
        
        
        @Override
        public IBinder onBind(Intent intent) {
            return null; // This is a started service, not a bound service.
        }
        
        
        
        @Override
        public void onDestroy() {
            super.onDestroy();
            if (shutdownReceiver != null) {
                unregisterReceiver(shutdownReceiver);
            }
            if (rebootReceiver != null) {
                unregisterReceiver(rebootReceiver);
            }
            Log.d(TAG, "Service destroyed.");
        }

        }

          anpandiyaraj

          Can you explain why this class is necessary according to you?

          And where did you get this class? It is a bit strange. The method (void) clearBluetoothCache mentions that it requires root permission, but that is not correct. It is allowed for system apps.

          And when using it in a system app, why use an external pm shell command and not an internal java method like clearApplicationUserData()?

          But most of all: Please explain why and when this bluetooth cache clearing should be used, according to you?

          surfer63

          Same here, I also quit debian for reasons I will not post here

          Now, retirement for the last 5 years have been awsome, yes, I knew and conversed with Ian Murdock.

          gismo

          I can confirm I have this same bug for VW PQ, I hope dudu engineers can fix this asap...

          When do the Chinese New Year holidays end so that support team and Devs look at their products and bugs again? It starts to feel like ignorance...

            gismo From what I know, holiday is ended and they are working. They are testing the firmwares internally.

            gismo This is not ignorance, this is impatience of society. Everyone has the right to rest. It clearly states that the software may contain errors. The software is for enthusiasts

              wybitny2 would be true for a one man show, not for a company where you'd plan absence. But good to see they're operational again.
              I would consider myself as an enthusiast - but enthusiasm suffers if nobody looks at your bug report for meanwhile 9 days...

                gismo The bug report is not written out of anger or any regret. I see dudu os developing, I see changes for the better. I fell in love with dudu os from the day I saw this software for the first time. I test and I realize there will be errors, I'm not mad at them, I know it helps in detecting problems that may occur. If someone downloads new software for an enthusiast and thinks that everything will be fine, then he is probably lost because this is not how it is supposed to look, it does not have such a function.

                  • Edited

                  wybitny2 you misinterpret me. I'm not angry or even mad about an error, I filed a neutral bug report about an error that didn't exist in v3.5 and just wondered why it's not being looked at.
                  But all good, it's being treated now 🙂

                  Update: It's been fixed (https://forum.dudu-auto.com/d/923-v36-canbus-bug-skip-fwd-rwd-now-is-the-same/4), so I'm happy again. I have not experienced any other bugs in v3.6.

                  12 days later

                  Dafior1 저도 3.6으로 업그레이드후 A/C 플로팅창 비활성화 했는데도 저도 팝업이 뜨네요 심플(XP)캔버스를 사용해서 비활성화하면 팝업이 뜨고 라이즈(RZC)캔버스를 사용해서 비활성화하면 팝업이 뜨질 않네요 심플(XP)캔버스를 사용해야해서 저는 3.5버전으로 저는 다운그레이드를 했습니다 A/C 플로팅창을 비활성화하면 이젠 정상적으로 팝업이 나타나질 않네요 3.6 버그인거 같습니다....

                  Today i have downloaded and install the latest beta version on my dudu7 device.
                  I,am very curious about the fact that i can use google assistant when i press the button at the left side of my steering wheel.
                  Everything which i tried so far with that works well, the only thing where i,am not happy about is that there is no option to set another navigation app as default app, so when you say "Hey Google Navigate To ...." he uses the one i would, in my case "Tom Tom Go" instead of the default google maps.
                  I hope that will be fixed then i and many with me would be very happy.

                  Regards, Arjen

                    acvdmolen Everything which i tried so far with that works well, the only thing where i,am not happy about is that there is no option to set another navigation app as default app, so when you say "Hey Google Navigate To ...." he uses the one i would, in my case "Tom Tom Go" instead of the default google maps.

                    That is because it is Google Assistant. If you try this on your Android phone, it would only use Google Maps. If you remove Google Maps, it will give an error even though another Nav app is installed.
                    It is not a short-coming of DuDu or whatever brand of car unit or phone. It is simply Google.

                    Believe me: I would also like it otherwise. Especially as it does work with other Nav Apps within Android Auto.