Dark mode question/Bluetooth headphone issue/Encryption question
First of all thanks to Daniel and the other contributors for this amazing, stable and google-free ROM. I installed it yesterday on my newly acquired Pixel 3a XL and I'm immensly satisfied.
I have a question regarding dark mode: Why isn't it consistent throughout the UI? The settings look more greyish than black. On stock Android it looks different to me. Notifications for instance are truely black. If I want to open a link in a specific app then the colouring is also more a shade of grey similiar to the settings. Should the native AOSP apps like calendar, messages, contacts and phone also take dark mode into account when enabled? None of the above mentioned apps turn dark when enabled in the settings. This doesn't really bug me, but I just wanted to get some background info on that matter.
Another issue is that my bluetooth headphones from the brand Ausdom can't receive the media output from the device. The pairing is successful, but when audio is played the output gets redirected to the phone speakers rather than the bluetooth ones. I tried to conduct the pairing one more time, the result was the same though. How can I further troubleshoot this problem? I didn't try the headphones on stock Android, but they worked without a hitch on different Android versions and ROMs as well as Windows.
My third concern relates to encryption handling. Can I set a different passphrase when booting up the device versus when it is already booted and I want to unlock it? I didn't see this setting under security. I had the notion (at least on other custom ROMs and even stock ROMs) that you are able to set a different password for when booting and unlocking the phone, i.e. long password for booting up and a pin/pattern for unlocking the device after booting. Did Google change something regarding this aspect or did I miss something in the settings?
Posted Feb 9, 2020, 2:57 PM UTC
I guess the problem with design issue is that nobody help this project.
For bluetooth it exist some threads here and also on Github. You need to disable A2DP in dev options.
You can't set a different passwort for boot. Android use a long time file based encryption instead of old full disk encryption. The other ROMs you mean doesn't use the new one so that explain that.
Yeah I really wish we could get somebody to help with the project but it feels really underground.
Seems to be getting more attraction on YT tho.