Aside from budget and time overruns it looks like they overshot the target of “futuristic” and landed in the middle of dystopian…
Aside from budget and time overruns it looks like they overshot the target of “futuristic” and landed in the middle of dystopian…
Man könnte noch argumentieren, dass es in Sichtweite gilt und die Bewohner dieser Institution durchaus kurzsichtig sind.
Ah, you “work” in “marketing”?
In welcher Luxus-Ecke von Deutschland lebst du denn, dass es bei dir Videosprechstunden gibt?
Und die Gründe für Videosprechstunde nicht möglich reichen vermutlich von zu wenig Bandbreite über keine Kamera bis zu “machen wir nicht”.
Und was ist das Problem, mit Video ist ja auch ne AU möglich.
Hmpff, ich fand ihn ja schon immer latent unsympathisch. Dass er jetzt mit den “Christ”-“Demokraten” Politik machen will bestätigt das irgendwie.
I built a custom app to do it since I couldn’t manage to fire the relevant intents from an adb shell without root.
I lifted the code from AAAD
Specifically the InstallAPK method in MainActivity.java
Intent intent;
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) {
intent = new Intent(Intent.ACTION_INSTALL_PACKAGE);
intent.setData(getUri(file));
intent.setFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION | Intent.FLAG_ACTIVITY_NEW_TASK);
} else {
intent = new Intent(Intent.ACTION_VIEW);
intent.setDataAndTypeAndNormalize(Uri.fromFile(file), "application/vnd.android.package-archive");
intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
}
intent.putExtra(Intent.EXTRA_NOT_UNKNOWN_SOURCE, true);
intent.putExtra(Intent.EXTRA_INSTALLER_PACKAGE_NAME, "com.android.vending");
getApplicationContext().startActivity(intent);
}
Basically you construct an Intent ACTION_INSTALL_PACKAGE
with data pointing to the APK file and the extras EXTRA_NOT_UNKNOWN_SOURCE=true
and EXTRA_INSTALLER_PACKAGE_NAME="com.android.vending"
which tells the installer that this APK is not sideloaded and it’s the play store asking to install it.
You might still need to enable unknown sources in Android Auto developer settings (separate from phone developer settings).
If I remember, I’ll try to pull the code for my app from my PC and post it.
The problem is that android auto is restricted to apps installed from the play store.
The F-Droid Version supports Android Auto, but it’s blocked by Google.
I managed to enable it by spoofing the installer-package during installation.
For me, the navigation is near unusable. Location tends to lag behind by a few seconds when running on Android Auto. On my phone it’s fine.
I run a 2 node k3s cluster. There are a few small advantages over docker swarm, built-in network policies to lock down my VPN/Torrent pod being the main one.
Other than that writing kubernetes yaml files is a lot more verbose than docker-compose. Helm does make it bearable, though.
Due to real-life my migration to the cluster is real slow, but the goal is to move all my services over.
It’s not “better” than compose but I like it and it’s nice to have worked with it.
They should not be worried, they should be educated.
If you worry a new user enough they’ll go back to Windows or Apple because there’s less scary warnings there.
We need to make the transition as pain free as possible. Learning about the joys of kernel compilation and SELinux can come later.
The first step is "Hey, this is as usable as Windows, without stupid ads in the start menu.