gonzalo
https://github.com/lukaspieper/Gcam-Services-Provider
Here's the relevant part:
The only reason to consider Gcam-Services-Provider on GrapheneOS is the ability to use the button in Gcam that opens the last taken photo without having Google Photos installed. If you can do without it, you don't need this app.
For this functionality there's "Photosonly" flavor of the app on github releases page.
gonzalo Consider trying out fcitx5i-android! It is great!
Synth There is a great FOSS keyboard called fcitx5-android which is the implementation of the open-source fcitx5 im. For JP support use the Anthy plugin.
This keyboard also supports pinyin, jyutping, hangul and etc.
gonzalo there is a way to disable these pop-up notification globally?
Short answer: it doesn't look like it.
The setting you want is "Pop on screen", which you would have to disable for each individual notification type.
Possible hack: Do Not Disturb mode disables this globally (by default, under Custom restrictions). Maybe you could disable most of the other features of Do Not Disturb mode, but keep this one. Doesn't seem like a great solution to me, but at least worth mentioning.
gonzalo
https://github.com/GrapheneOS/os-issue-tracker/issues/2540
TLDR its a bug, it disappears eventually.
gonzalo You'll need to wait for Molly to catch up to Signal and then yes, you can import your Signal backup into Molly.
The ability to save tickets in Google Wallet works fine on GrapheneOS. Other functionality like UFC payments in India is reported to work fine too. It's possible that the app might depend on having had Google Play Services installed and set up correctly before you installed the Google Pay app. For instructions see https://grapheneos.org/usage#sandboxed-google-play-installation. It sounds like you might need to have signed into a Google Account on your device too. Have you done that?
Note that you won't be able to make contactless NFC card payments with Google Pay, because GrapheneOS is not a Certified OS by Google.
Tryptamine seedvault is terrible. It fails 9 times out of 10, and it doesn't reliably even tell you whether its failed or what's going on. Even if it happens to work, its so far removed from the type of seamless security in back ups that iOS offers that it's laughable to even try to compare it.
gonzalo if I understand your question correctly, I guess the answer would be it wouldn't work with an unmodified GrapheneOS build.
I'd suggest skimming/reading through the storage access section of the website.
Apps have their own (as the website calls it) "app-private ('internal') storage". Unless a special backup app can access that storage without restriction, copying a full "home directory" won't work for backups. If a phone is running an unmodified version of GrapheneOS, then I don't believe it's possible for any app to access those directories, even a privileged app. If apps want to support users backing up and restoring data, there is a supported way to do that. See https://developer.android.com/guide/topics/data/backup
Not since HgLauncher do I recall an iteration with a similar, thumb-driven list of apps. Had a "minimalist" feel with just enough features. So naturally, the app was abandoned shortly after yours truly, here adopted it.
Features including custom icon packs within the nifty app list AAAND (this is important) the ability to pick an alternate logo if for when your chosen pack inevitably doesn't have dedicated icons created for any particlar apps. Launchers like Rooted Pixel Launcher (a dated example, tbf) that merely apply icons automatically to matching apps -- with no option to manually select them for others -- defeat the entire purpose of custom packs to begin with in most cases.
I mean, what kind of demented, tortured-soul of a monster would use, say...Arcticons White alongside random, colorful icons?!? I shudder to think, friends.
Really though, I mention this in case our mighty devs happen to upgrade the standard launcher down the road, themselves (understandably, prob not a priority atm). IMO, the aforementioned implementation along with the ability to simply hide apps from the drawer would satisfy most users.
For a while now, I've also been having various problems with this launcher, lags, freezes, buttons that don't really respond and so on with Pixel 7a.
Not annoying on a daily basis, it doesn't happen every day, but sometimes it can be annoying.
gonzalo Solokeys1 works with pixels?
Neither SoloKey1 nor SomuTiny. Pixel has a Titan Security Key built in. The link above explains how you can use it to log in to Google.
Although you can use an Onlykey-DUO on phones, I prefer OTP apps on Android.
andOTP (unfortunately discontinued, but can do OpenPGP-encrypted backups) Aegis can import the entries of andOTP & lots of other authenticators.
If you use 2FA you need an OTP app and hardware sec key(s) anyway.
Hi there,
first of all I want to say that I have been a happy user of GrapheneOS for two years now. I thank the developers for their efforts providing us with such a great OS.
Usage of my Pixel 6 has become cumbersome since GrapheneOS version 2023121200. Right now I am on 2024010400 and still the following problems persist.
The problems I am experiencing are:
Is this normal behaviour now or am I experiencing a bug? Is there any setting which controls this behaviour?
Thanks a lot for your help and support.
Best regards Daniel
gonzalo I've pretty much given up hope on SeedVault ever working correctly. It needs to be replaced but as the devs have stated it's a lot of work to do so.
I think it should be removed entirely until a replacement is written otherwise it gives a false sense of safety in backups that may never work.
gonzalo We are receiving reports that people can reproduce this on Stock OS. It's not GrapheneOS specific. It is either an AOSP bug, or a bug with Signal.
gonzalo no, not really. Of course it depends heavily on what you want to achieve and you ask tasker to do.
as far as i am aware, Tasker profiles/tasks are neglectable in terms of battery usage as long as you do not overstretch location based tasks (kind of: perform tasy "y" once you are in the area (GPS wise) of "z"...this will end up in much more battery consumption compared to usual tasks (e.g. switch to "do not disturb" mode once you have an active calender event). Even in this case, i am far away to say that there is a battery drain.
So, no worries, tasker knows how to deal with it and at the end of the day, you are not able to say if the 1% of battery usage comes from tasker or from 10x switching the display on/off.
In my opinion the benefits and advantages of using tasker automation outweighs the battery consumption by far
Icecube gonzalo For apps using FCM, you need Unrestricted battery mode for Play services. For apps using their own background push service, you need Unrestricted battery mode for the app. Many apps like Signal use FCM when available and their own push when it's not available. Apps doing their own push need to run a foreground service which must create a non-hidden persistent notification which the user can disable without breaking it. It will show up in active apps when the service is running, so you can see when it's running the push service.
Google Play services does not create the notifications for apps. FCM is not a push notification service but rather a push messaging service. It delivers messages to the apps and they handle the messages.
Icecube There's no indication of any GrapheneOS issue for any of this. It's almost certainly a configuration issue with your device. You haven't said anything about your battery optimization configuration for Play services or apps doing their own push. All the apps you listed likely using FCM via Play services for push when it's available, and some of them will do their own push when it's not available. Their decision about using their own push may be done statically on first launch after install or app data reset rather than dynamically at each app launch. It depends on how the app chose to do it.
