GrapheneOS version 2023062300 released

treequell

siabadaba I have not seen any other reports of this issue.

Where are you looking exactly? In Settings > Security, Fingerprint Unlock should be the second option from the top, after Screen lock and before Auto reboot.

Is this in the system user or a secondary user?

https://source.android.com/docs/devices/admin/multi-user#categories_of_users

siabadaba

treequell It's the system user (I don't have multiple users toggled). That's exactly where I'm looking and the option is not there. Screen lock and then immediately Auto reboot. When I go into Screen lock settings the only available options are None, Swipe, PIN and Password.

Another issue I just discovered is that my phone started dropping calls after _30s. Had it with multiple callers, both when I called and received. Network coverage is good.

brambler

treequell Thanks for this! Was wondering where this new toggle was.

DeletedUser301

Do third party clock apps work nicely with GrapheneOS? Let say, I set an alarm on a third party click app (downloaded from Fdroid) and the device somehow restarts, will the alarm trigger on time or do I need to unlock the device once?

matchboxbananasynergy

DeletedUser301 It's up to the clock app in that case, which would need to support direct boot to be able to use part of its functionality while the phone is in BFU state. It's not up to GrapheneOS, but rather the app itself.

As an example of this, GrapheneOS actually contributed direct boot support to Florisboard, which means it can be used to unlock the phone while in BFU state where it otherwise wouldn't.

treequell

siabadaba That's strange! Could you do something for me to help investigate this further?

Enable multiple users, create a secondary user, and then switch to that secondary user. Then have a look in Settings > Security, and tell me if you have the same issue with Fingerprint Unlock being hidden. That will help to establish if it's a device-wide issue or a strange configuration in your system user. You can always delete the secondary user after.

siabadaba

treequell Same thing in the new user. Screen lock and then immediately Scramble PIN input. No fingerprint. Also in the initial setup that option was not present

[deleted]

siabadaba Just checking, do you have a pin or pw set? If not, you need to create one before adding your fingerprints. These are a prerequisite to decrypt the profile/device from rest and as a fallback to fingerprints for when they fail.

memyselfandi

''prevent adding guest user on lockscreen via adding new users on lockscreen is disabled (UI only appears on large screens such as the Pixel Tablet)''

This one is interesting. Not wanting to offend anyone, it is just an observation. Even if one tries to be as mindful in building secure systems, major flaws will always be present. Keep up the good work.

siabadaba

[deleted] Yes, I have a pw

TrustExecutor

siabadaba
I had the same issue with a Pixel 6 Pro. I rebooted and then the fingerprint unlock was there again.

siabadaba

TrustExecutor Lol, I didn't do the most basicest of things. A restart did it. Thanks and sorry for the alarm

aerosola

Does anybody have performance issues since the last week or so? My Pixel 7 has feels so sluggish out of nowhere. I already rebooted several times. I haven't changed anything substantial on the phone itself. I know this can literally be anything, but perhaps other people share the same issue which could verify my doubts regarding if this is caused by the updates.

[deleted]

aerosola That's most likely not the case. We need to look for issues in your setup. Could you give more information?

Could you also check which apps or processes use the most of your CPU resources and battery?

One more thing to check is if your phone is overheating or not.

aerosola

[deleted] nothing out of the ordinary. I also observed my RAM is more aggressive than normal with killing background processes. Even just two apps open, will more often than normal kill the other app.

[deleted]

aerosola How many user profiles do you have? Do you have Google Play Services installed?

aerosola

Yes I have gplay services, only one profile. My experience matches that of this Pixel user (trending topic, 20 confirms already) https://support.google.com/pixelphone/thread/221589285/battery-is-still-warming-and-draining-very-fast-after-the-june-2023-security-update-pixel-7?hl=en&sjid=5925492497984080460-EU

Skyway

aerosola
There have been recent threads about this issue but I don't think there have been any answers unfortunately.
Seeing as its been reported to google probably not going be much anyone at gos can do .

gosrox

Skyway there really needs to be downgrade option for botched updates. My phone has almost unusable for 2 weeks now (jun 14 update) with launcher crashing all day and no one seems to care or experience it. If gos team cannot fix issues introduced by quarterly patches then those should be optional or downgradable to a different version with just kernel or quarterly rolled back. If i needed my phone in an emergency now i would be screwed becausd the launcher is crashing and i wouldnot be able to bring up app quickly tryibg to work around it while panick emergency. This should have never gone to production. Fingerprint issue too but mainly launcher for me. Launcher crashing all the time broke app switching completely.

No one even acknowledged my log here and in previous update thread no one had idea lol gosrox

aerosola

Skyway What fixed it for me was to go cold turkey. Turned phone off, and let it off for 20 minutes and then boot again instead of reboot or instant boot after shutdown.

treequell

gosrox Hi there, I'm sorry to hear you've been experiencing launcher crashes. The OS issue tracker on GitHub is the place where you should submit the bug report for the development team to look at: https://github.com/GrapheneOS/os-issue-tracker.

In the meantime, is using a third-party launcher app a viable temporary workaround for you?

spiral

gosrox

The launcher crash bug seems to be an upstream AOSP problem, lots here have reported this problem, including me. It happens to me all the time since that recent update.

Perhaps this can help - when the launcher crashes, I switch profiles, then switch back to he profile where the crash happened, and the launcher bug is gone (for now). It's obviously not a fix for the problem but it's been an acceptable workaround for me.

« Previous Page Next Page »