Because WifiConfiguration and WifiManager.addNetwork() (and all
related functions) were deprecated in Android Q.
Because we target Android Q, WifiManager.addNetwork() will always
fail and return -1.
On Android Q, we can only suggest the system (and user) a WiFi
network but cannot add it permanently ourselves.
Because, apparently, there are devices where this intent cannot
be resolved.
Also put the project URL into a resource so we can at least show
it in a Toast if there's no browser installed. Might as well put
it in the clipboard some day.
Just simply use `requestLegacyExternalStorage="true"` to opt out
of the new Scoped storage model for the time being.
As soon as we set Android 11 as target version, this will no longer
work!
Details on the issue:
https://developer.android.com/preview/privacy/storage
Closing the camera will also shut off the flash.
This fixes the bug that when you scan a barcode with the flash on and
immediately go back (to the previous instance of CameraActivity), the
flash flag will still be true when the flash is off.
Fix for https://github.com/markusfisch/BinaryEye/issues/101
In case there is a configuration (orientation) change later on.
And always return previously initialized window insets what is
required when Fragments change and the listener won't fire (again).
Also use an explicit variable to know when the window insets rect
has been initialized. `Rect.isEmpty()` doesn't cut the mustard.
Don't use the static `windowInsets` when `setWindowInsetListener()`
is called because this is just for pre-Lollipop devices where
`ViewCompat.setOnApplyWindowInsetsListener(view)` *never* fires.
Calling RenderScript.forceCompat() on a build that was made with the
new build tools (which are required to make RenderScript build again
on macOS Catalina), results in a RSRuntimeException (Loading of ScriptC
script failed).
RenderScript.forceCompat() was introduced to fix RenderScript for
Lineage 16.0. Maybe this is no longer required with those new build
tools?
Yes, this means this setup is producing platform independent builds
that have different features depending on what platform they were
built on. And yes, that's as bad as it sounds.
So, for the time being, it's probably better to _NOT_ use Catalina
to make release builds.
Since RenderScript can no longer be compiled on macOS Catalina
because Catalina cannot run 32bit binaries and Google failed
to provide a 64bit compiler in time. Now, as if that wasn't
bad enough, the new build tools that provide a 64bit compiler
don't work on any other system than macOS unfortunately.
For details on the issue see:
https://issuetracker.google.com/issues/142590626
This reverts commit cf4020c613.
Those new build tools don't work on other systems than macOS
Catalina and even there produce broken builds :(
Also, it looks like the only solution is to remove
`RenderScript.forceCompat()` what's probably no longer
required to support Lineage 16.0 with those new build tools.
Confirmation pending.
