caolz
We re-checked the bug in item 3.
I tried switching after re-selecting the 5 apps and specifying the SWC mode,
but sometimes the mode switch still works normally and sometimes it doesn't.
When the conversion goes well, only some of the apps 1 to 5 are converted.
I checked the selected app and there is no problem with the app.

    caolz
    Please solve problem 4 as well.
    It's very inconvenient.

    Trouble
    Do you mean you chose five apps, but some of them can't be switched?
    Which app can't be switched?

      caolz
      Of the five selected apps, sometimes only apps 2 and 3 are switched.
      sometimes only apps 2 and 4 are switched, sometimes apps 3,4 and 5 are switched.
      in some cases, the conversion is not possible at all.
      I think it`s not a problem with the app, but a aproblem with the conversion logic.

        Trouble
        This should be related to the application. If an application cannot be switched out, then the application cannot be switched out in any position.
        For example, Yandex Navi.

        Please tell me specifically which APP will not appear when switching.

        5 days later

        Ошибка установки обновления DuduAuto Pro из магазина

          Trouble
          The Question 2 has been fixed.
          Update Media APP version to 21001066 or above.

          The phone number starting with 0 in issue 4 has been fixed. Please update your Bluetooth Phone APP.

            caolz
            Problem number 2 has been resolved. thank you.
            However, problem number 1, 4 is still not resolved.
            The Bluetooth phone app is not updated.
            After the cell phone is connected to the android device via bluetooth,
            the phonebook list synchronizes very well.
            However only if the first digit of the phone number
            in the synchronized and displayed phone book list is 0
            the first digit of 0 is not displayed.
            Also the sort order of the Korean phone book list is Korean
            "ㄱ, ㄴ, ㄷ, ㄹ, ㅁ, ㅂ, ㅅ, ㅇ, ㅈ, ㅊ, ㅋ, ㅌ, ㅍ, ㅎ"


            Additionally, issue 1 is still not resolved.

            duduos-crash.zip
            4kB

              Reversing screen, need to clear the data cache. UI Server

                Trouble
                If the first digit of the Bluetooth phone contact number is 0, it will not be displayed.
                This is a bug.
                The next update for Bluetooth phones will fix this issue.

                  DUDU-HUANG

                  DUDU-HUANG
                  Please tell me how to clear reverse cache

                    caolz
                    Are you saying it will be resolved in the next version?

                      Trouble
                      Bluetooth phones version 2.001038 or above.
                      You need to wait for the latest version of Bluetooth phone to be released by the app store.

                        caolz
                        All right. thank you Will the problem with the rear camera screen no. 1 be solved in the next version?
                        There is a problem where the UI server cannot be updated in the App Store.

                        Trouble
                        Setup>System>Applications, Click on the top right icon ︙, then click the Show system option.
                        Find UI Server, then click UI Server>Storage & cache>CLEAR STORAGE.

                          caolz
                          Ilook the steps ypu mentioned, but the problem is still not resolved.
                          Icleared the UI server`s cache and storage, but this problem is still not resolved.
                          Additionally, the App store UI server is not updated.







                            Trouble

                            1. Проверьте в заводских настройках какой режим камеры заднего хода у вас установлен.
                            2. Попробуйте переключить этот режим на противоположный (перезагрузка) и затем снова обратно в тот режим который вам нужен (перезагрузка)

                            This was resolved with the UI seuver update, which continued to not work. The problem occurred because the UI server was not updated. Please note.
                            It's worked out fine for now