Nostr notes by matchboxbananasynergy

They aren't, though, and note that their insinuation is that ...

2025-07-19T16:48:21Z

In reply to nevent1q…6x5w
_________________________

They aren't, though, and note that their insinuation is that **we're** sending them there.

It's just deflection, and it's not deflection of criticism coming from us. They're trying to use as to deflect criticism from their own community and users. It's wild.

When /e/OS users on their own forum criticize /e/OS for its many ...

2025-07-19T16:36:39Z

In reply to nevent1q…7tmw
_________________________

When /e/OS users on their own forum criticize /e/OS for its many issues, their strategy has become to start insinuating that we're sending people there to criticize their OS, so yes, you wouldn't be taken seriously.

https://community.e.foundation/t/voice-to-text-feature-using-open-ai/70509/28

>So either those people are coming from people in ordered service from the toxic community we know too well.

They are unable to respond to criticism, so they'd rather lie and say that we're brigading their forum while calling our community toxic and our project members crazy/delusional. It's quite sad.

Appreciate the additional details. Barring a hardware issue, the ...

2025-03-07T14:43:19Z

In reply to nevent1q…wm03
_________________________

Appreciate the additional details. Barring a hardware issue, the only other thing that would make sense is that there is a slight delay between you pressing the power and volume down button. There's a grace period of about 100ms. If the power button is pressed first and the volume button is pressed 100ms or more later, the result will be the volume being lowered, which seems consistent with what you previously mentioned.

It would be very interesting to know if the behavior changes on stock OS, because we have confirmed that there is no issue on our end, nor have we gotten any reports about this.

I understand - the reason for me reaching out is that this is not ...

2025-03-07T14:32:58Z

In reply to nevent1q…228u
_________________________

I understand - the reason for me reaching out is that this is not an issue that anyone else is happening, and we've confirmed that it's not an issue across any of our supported devices, so we're trying to understand what the cause may be. It would help if you let us know if you've installed any 3rd party launchers or any apps with accessibility services permissions granted etc. You mentioned that it was fine on stock OS and we want to rule out a hardware failure/glitch somehow occurring after that.

From our perspective, there doesn't seem to be an issue, and given that you seem to be aware of how to trigger a screenshot via power button + volume down, we're just trying to understand what's going on.

Edit: another possible cause - if you're using a case, could you try without it? Just trying to rule out everything.

I've reached out via DM - looking forward to your reply. :)

2025-03-07T14:00:37Z

In reply to nevent1q…27mc
_________________________

I've reached out via DM - looking forward to your reply. :)

The global location toggle only controls whether apps that have ...

2024-10-13T13:28:36Z

In reply to nevent1q…26mj
_________________________

The global location toggle only controls whether apps that have access to the location permission can use it. If you want to use that kind of functionality without toggling it on and off again, just leave it on and adjust location permissions you grant to apps accordingly. Apps can be granted location permission with various levels of granularity.

Nostr event nevent1qqsv0dk925nd9xjkh90h79ddgdy60l426kgdj52s8pf57gx47hwl52czyptu0y5snx62x8qknupufdlp4ffudrkct5u8878gr7m7c2pczj3h74j6hzw

2024-10-10T09:24:00Z

In reply to nevent1q…9fwt
_________________________

See https://infosec.exchange/@matchboxbananasynergy/113282397101936133

This is nothing specific to GrapheneOS. It was added in Android ...

2024-10-10T09:23:21Z

In reply to nevent1q…gct8
_________________________

This is nothing specific to GrapheneOS. It was added in Android 13. That message shows up when you sideload or install an app from a non-modern app store like F-Droid that doesn't use a session installer, and the app in question also includes sensitive permissions like accessibility or device notification permissions.

It's meant to discourage people to sideload potential malware and grant it access to these very sensitive permissions, as that's how a lot of scammers try to trick their victims into giving up control of their device to attackers.

There's nothing specific to GrapheneOS about this. If you search for "Google Android Restricted Setting", you'll get to a page from Google telling you how to bypass it:

https://support.google.com/android/answer/12623953?hl=en

The reason they don't make it obvious in the UI is so that it's not easy for the attacker to get the victim to bypass the restriction.

That requires an explicit action on part of the user. What makes ...

2024-09-17T14:27:24Z

In reply to nevent1q…hkk7
_________________________

That requires an explicit action on part of the user. What makes a hardware switch different, which could be switched by someone with physical access to the device?

You can't enable/disable airplane mode while the device is ...

2024-09-16T23:04:41Z

In reply to nevent1q…5hpk
_________________________

You can't enable/disable airplane mode while the device is locked on GrapheneOS. Give it a shot. You'll see it asks for authentication.

At that point, what would the "dumbphone" be used for? If ...

2024-06-13T18:29:29Z

In reply to nevent1q…w7td
_________________________

At that point, what would the "dumbphone" be used for? If you use it to communicate with people via carrier-based calls, that's a pretty significant downgrade vs using something like Signal on a modern smartphone, where you can utilize end-to-end encryption. Beyond that, those devices are pretty godawful when it comes to hardware and software security.