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

35
rediii123•

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.

3
Chronic_Media•

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.

2
WasteFruit3•

There's a solution for the bluetooth issue in a previous reddit post

1
[deleted]•

[deleted]

1
[deleted]•

[deleted]

1
DanielMicayMODLead developer / project owner•

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.

AOSP doesn't use the same themes as the stock OS on Pixels. Dark mode also needs to be supported by each app, including targeting the most recent API level.

The AOSP Calendar app is a sample app for testing purposes and isn't intended for usage by end users.

Those other apps only receive major updates with major AOSP releases, so you need to be patient and wait for the next major release to get the changes from the past year (other than security / bug fixes). You're free to use other apps instead.

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.

Search for the problem. Other people have encountered it and there's a common workaround that seems to work for most people.

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?

Encryption is granular and uses per-profile keys, so what you're asking for doesn't fit how it works and isn't possible. It was a past GrapheneOS feature before it was called GrapheneOS, but the project lacked developers to implement a replacement for the improved encryption system. It hasn't used a global key for the entirety of the storage for years. The OS does support the concept of secondary unlock mechanisms. You can use a long passphrase as the main unlock method used to derive the profile's primary encryption keys and then a secondary unlock mechanism like fingerprint unlock. Secondary unlock mechanisms are still tied to more than a user interface screen lock because they also have to unlock the hardware-backed keystore as keys as be set to become at rest when the screen is locked.

Supporting an alternate PIN / passphrase as an extra factor for secondary unlock has been planned for years, but the community has not stepped up to get features like this implemented:

https://github.com/GrapheneOS/os_issue_tracker/issues/28 https://github.com/AndroidHardeningArchive/legacy_bugtracker/issues/451

If people want this implemented, they need to work on it or find/pay someone to work on it. People asking for it or stating that they consider it important won't make it happen. It will only get implemented when people finally step up and get it done. After that, it will also need to be maintained and ported to new versions, like other features. Many past features have been lost due to lack of support for the project, and this is essentially one of them, since the old approach became obsolete and the project has lacked the support to get a replacement implemented.

1
hackerman_XYOP•

Thank you for taking time to answer my questions, I appreciate it.

2