Thanks for the explanation.
Bblinker_unsteady
- Joined Oct 23, 2022
I'm not exactly sure what is going on with the
2023110900release for the Pixel 4a.If I remember correctly, I received an over-the-air OS update for my Pixel 4a about 3-5 days ago, when I connected it to Wi-Fi. (I've already migrated away from the 4a, though there are some minor accounts that I still have on the 4a, which I haven't moved to my latest GOS phone yet.)
I thought it was curious that the Pixel 4a received an OS update, as I had believed it was going to be stuck on Android 13. (After the update, it turned out the 4a is still on Android 13.)
However, when I click on the
2023110900release to see its description for the Pixel 4a releases, I've discovered that the2023110900section/HTML fragment doesn't exist anywhere on the GOS Releases page.Could someone explain what is happening? Am I misunderstanding what I'm observing?
DeletedUser115 Originally I wanted to use the Pixel Tablet as a secondary Android device in Molly, but it's currently hampered by the fact that my YubiKey 5C still can't be used to unlock KeePassDX (in order to unlock the local Molly database).
blinker_unsteady Seems like I still can't use my YubiKey 5C to unlock KeePassDX...
- Edited
You can practically bypass this behavior on GrapheneOS (and stock Google Android, I think) by turning off the Pixel Tablet to charge it to 100%.
(In stock Google Android, there is a setting that allows users to temporarily override this, and charge to 100%; but this must be done each time the user wants this to happen. In GOS, this option doesn't exist - the last time I checked - in the Settings app; probably due to the lack of privileged Play Services installed for Pixel Tablet specific OS features.)
This method works with both the official Google 30W charger and the included Pixel Tablet stand base.
I also discovered the Pixel Tablet stand can only charge, if I use Ethernet (via the USB OTG adapter from my prior Pixel phones; USB-C male and USB-A female, with USB-A male and Ethernet female).
aleksm I wasn't aware that the YubiKey 5C (without NFC, if I'm reading the post correctly?) works. I was going to make a new thread about my experiences with the Pixel Tablet, regarding how I haven't really used the device because I had initially thought KeePassDX wouldn't work with USB OTG connections due to this Key Driver issue on smartphones with NFC.
Since Pixel Tablet has no NFC (as Pixel Tablet is Wi-Fi only and thus wouldn't be able to use NFC to make contactless payments "in the real world"), hopefully I can start using my YubiKey 5C again to unlock KeePassDX on Pixel Tablet.
- Edited
DeletedUser115 In the Settings app and with the keyboard plugged in, you can follow this path to at least see the keyboard shortcut list: Settings > System > Keyboard > Physical keyboard > [name of keyboard] System Control > Keyboard > Keyboard shortcuts.
You can only change the modifier keys, but those are keys such as "Ctrl" and "Alt". ("Super" or "Windows" is what is meant by the "Action" key.)
I tried filing an issue, but it was closed as "won't fix", because FCM is excluded in the F-Droid build of Bitwarden.
However, I do agree that a mention of the "log in with device" feature not working on the F-Droid version is appropriate when trying to activate this. I'll try to cordially bring it up, though I don't have too much expectations at this point.
unwat I don't know if there's a very clean way to figure that out. I just tried to update Bitwarden with Google Play, but it didn't work, which indicates to me that both the Google Play and non-Google Play versions use the same package name.
I actually think the Bitwarden app was the Google Play version on the Pixel 5a, now that I think about it.
(I think the Pixel 5a has Bitwarden installed from the F-Droid repo? I'm around 90% sure.)
BTW, how do I add the Solved tag to this thread?
- Edited
Disregard everything I've said - I've discovered that the Google Play version through Aurora allows me to toggle Notifications, but the F-Droid version via the Droid-ify repo doesn't. I will report this issue to Bitwarden and will use the Google Play version for the time being.
(However, I'll still keep my previous post for the sake of record keeping in the case anyone else has this same issue.)
Thank you for helping me work through this!
Regarding this:
unwat Also, just as a side note, I have set up log in with device on my own Bitwarden account, but I never get the notification. The only way I can get it to work is by launching the app and refreshing my vault.
I this this is somewhat expected, because Aurora Store says that Bitwarden requires GSF, so any push notification related activity more or less only works on GOS with Google Play Services (and I'm conjecturing YMMV even if you installed the sandboxed Google Play Services). I know this from experience with Keybase, Proton Mail, and Wire (before it was distributed directly on F-Droid, and I'm not sure now since I've basically stopped using Wire since 2021).
- Edited
Yes, so far Bitwarden's the only app that has this behavior. (However, there could be other apps with the same issue - I just wouldn't know right now; but for now I'm operating on a "if it ain't broke, don't fix" basis for this issue.)
This issue has persisted after uninstalling and reinstalling Bitwarden repeatedly - sorry I didn't mention this earlier. Not sure if this will make a difference, but I'm pretty sure I've tried installing the Google Play version from Aurora Store and the F-Droid repo via Droid-ify - but both still have the same issue after clearing Bitwarden's app cache and storage.
I use the default GOS launcher, and I've made sure that notification dots are allowed via: Settings app > Special app access > Device & app notifications > GrapheneOS Launcher (under Allowed) > See all apps > Apps shown on device> Bitwarden is checked on.
(I've even made sure Battery Saver is turned off, but I think the issue still persisted.)
(Although it's always an option, I'd like to avoid resetting my entire device and set up my Pixel 4a from scratch to fix this.)
- Edited
I need to enable Notifications on Bitwarden on my Pixel 4a, so that I can use the log in with device feature (and I made sure to follow everything listed there).
However, when I try to enable Notifications for Bitwarden (by going to its App Info menu > Notifications), I cannot toggle the switch from off to on for allowing "All Bitwarden notifications". The switch is basically greyed out, and it cannot move, no matter what I do. Here's a screenshot.
However, I also have a Pixel 5a with Bitwarden, and somehow the Pixel 5a lets me turn the Notifications toggle on/off perfectly fine. (This told me that the problem I'm having isn't only limited to the Bitwarden app.)
I have no idea what to do for my issue discussed above - I want to try my best before reporting this to the GOS Issue Tracker.
BTW, in Molly's settings, you can go into the settings (Vertical 3 dots > Settings > Help > Toggle the "Auto-update Molly" switch off and then on) to "manually" trigger a Molly update, if you know that there's a released update but the app hasn't checked yet.
IIRC, the Signal website APK doesn't have options/menus to trigger any form of update. You basically pray that the update will come when the website APK automatically checks for updates on its own.
