Добрый день. Вы на dudu 7 переднюю камеру сделали с большим разрешением. Которая сейчас стоит ужасно показывает.
DUDUOS 3.6 Beta Released Just in Time for Chinese New Year!
- Edited
How do I downgrade to v3.5? Beta v3.6 has too many annoying bugs and due to the holiday nobody looks at the bug reports... it's this one in particular: https://forum.dudu-auto.com/d/923-v36-canbus-bug-skip-fwd-rwd-now-is-the-same
This is what I tried: https://forum.dudu-auto.com/d/902-bluetooth-on-36/8
Status - downgraded but Dudu Launcher won't start. I deleted the cache of Dudu Launcher - still won't start. Should I delete the data of Dudu Launcher?
Can upgrade to v3.6 again but that has the bugs...
- 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
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.");
}
}
- Edited
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?
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...
- Edited
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.