I’m just an ordinary human that loves learning, solving puzzles, and eating food!

  • 12 Posts
  • 7 Comments
Joined 2Y ago
cake
Cake day: Mar 12, 2021

help-circle
rss

Hey that’s pretty cool! I’ll give your app a try this evening when I’m off work. Thanks


**[2021121602](https://grapheneos.org/releases#2021121602)** Tags: - [SP1A.210812.015.2021121602](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.210812.015.2021121602) (Pixel 3, Pixel 3 XL) — extended support release for legacy devices with frozen 2021-11-01 patch level - [SQ1A.211205.008.2021121602](https://github.com/GrapheneOS/platform_manifest/releases/tag/SQ1A.211205.008.2021121602) (Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a, emulator, generic, other targets) Changes since the 2021121012 release: - Vanadium: update Chromium base to 96.0.4664.104 - skip reporting network connectivity to the OS from apps with the Network (INTERNET) permission revoked to avoid triggering a SecurityException - remove special case of throwing SecurityException for socket errors caused by EACCES/EPERM as a debugging aid since it causes compatibility issues when the Network (INTERNET) permission is revoked - kernel (Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a): fix incorrect alloc_size annotation (already fixed in older kernels and no real world impact) [Twitter](https://twitter.com/GrapheneOS/status/1471604086961315847) / [Nitter](https://nitter.net/GrapheneOS/status/1471604086961315847) | [Reddit](https://reddit.com/r/GrapheneOS/comments/ri1oj2/grapheneos_2021121602_release/) / [Teddit](https://teddit.net/r/GrapheneOS/comments/ri1oj2/grapheneos_2021121602_release/)
fedilink

**[2021120717](https://grapheneos.org/releases#2021120717)** Tags: - [SP1A.210812.015.2021120717](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.210812.015.2021120717) (Pixel 3, Pixel 3 XL) — extended support release for legacy devices with frozen 2021-11-01 patch level - [SQ1A.211205.008.2021120717](https://github.com/GrapheneOS/platform_manifest/releases/tag/SQ1A.211205.008.2021120717) (Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a, emulator, generic, other targets) Changes since the 2021112404 release: - full 2021-12-01 security patch level - full 2021-12-05 security patch level - rebased onto SQ1A.211205.008 release, the first quarterly maintenance/feature release for Android 12 - Sandboxed Play services compatibility layer: improve robustness of Play Store compatibility layer - Camera: update to [version 7](https://github.com/GrapheneOS/Camera/releases/tag/7) - TalkBack (screen reader): update dependencies - avoid per-network randomization mode (AOSP default) being displayed as per-connection randomization mode (GrapheneOS default not available in AOSP) after rebooting despite persisting and working properly (caused by an additional abstraction layer introduced in Android 12) [Twitter](https://twitter.com/GrapheneOS/status/1468387568672718852) / [Nitter](https://nitter.net/GrapheneOS/status/1468387568672718852) | [Reddit](https://www.reddit.com/r/GrapheneOS/comments/rbeo2g/grapheneos_2021120717_release/) / [Teddit](https://teddit.net/r/GrapheneOS/comments/rbeo2g/grapheneos_2021120717_release/)
fedilink

**[2021112404](https://grapheneos.org/releases#2021112404)** Tags: - [SP1A.210812.015.2021112404](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.210812.015.2021112404) (Pixel 3, Pixel 3 XL) — extended support release for legacy devices with frozen 2021-11-01 patch level - [SP1A.211105.002.2021112404](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.211105.002.2021112404) (Pixel 3a, Pixel 3a XL) - [SP1A.211105.003.2021112404](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.211105.003.2021112404) (Pixel 5a) - [SP1A.211105.004.2021112404](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.211105.004.2021112404) (Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, emulator, generic, other targets) - [SD1A.210817.037.2021112404](https://github.com/GrapheneOS/platform_manifest/releases/tag/SD1A.210817.037.2021112404) (Pixel 6, Pixel 6 Pro) — incomplete support for 6th generation Pixels (no official builds) Changes since the 2021112123 release: - Sandboxed Play services compatibility layer: add another UserManager shim to fix issue with FCM in secondary user profiles - Sandboxed Play services compatibility layer: mark Play Store confirmation notification as ongoing to avoid users dismissing the notification and then being unable to accept or reject the install/update/uninstall action - Camera: update to [version 6](https://github.com/GrapheneOS/Camera/releases/tag/6) [Twitter](https://twitter.com/GrapheneOS/status/1463690375164477440) / [Nitter](https://nitter.net/GrapheneOS/status/1463690375164477440) | [Reddit](https://www.reddit.com/r/GrapheneOS/comments/r1lb8j/grapheneos_2021112404_release/) / [Teddit](https://teddit.net/r/GrapheneOS/comments/r1lb8j/grapheneos_2021112404_release/)
fedilink

**[2021110617](https://grapheneos.org/releases#2021110617)** Tags: - [SP1A.210812.015.2021110617](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.211105.002.2021110617) (Pixel 3, Pixel 3 XL) — extended support release for legacy devices with frozen 2021-11-01 patch level - [SP1A.211105.002.2021110617](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.211105.002.2021110617) (Pixel 3a, Pixel 3a XL) - [SP1A.211105.003.2021110617](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.211105.003.2021110617) (Pixel 5a) - [SP1A.211105.004.2021110617](https://github.com/GrapheneOS/platform_manifest/releases/tag/SP1A.211105.004.2021110617) (Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, emulator, generic, other targets) Changes since the 2021110507 release: - GrapheneOS Camera: update to [version 3](https://github.com/GrapheneOS/Camera/releases/tag/3) - revert hard-wiring camera gesture handler as a workaround for AOSP 12 bug with the gesture on the lockscreen - Vanadium: add workaround for upstream bug with login when sandboxed Play services is present - android-prepare-vendor: overhaul Pixel 4a (5G), Pixel 5 and Pixel 5a support including building more AOSP modules
fedilink

> The Auditor app uses hardware security features on supported devices to validate the integrity of the operating system from another Android device. It will verify that the device is running the stock operating system with the bootloader locked and that no tampering with the operating system has occurred. It will also detect downgrades to a previous version. Auditor app version 34 released: https://github.com/GrapheneOS/Auditor/releases/tag/34 See the linked release notes for an overview of the improvements and a link to the full list of changes. See https://attestation.app/about and https://attestation.app/tutorial for info about the app and optional monitoring service.
fedilink

Auditor app version 34 released: https://github.com/GrapheneOS/Auditor/releases/tag/34 See the linked release notes for an overview of the improvements and a link to the full list of changes. See https://attestation.app/about and https://attestation.app/tutorial for info about the app and optional monitoring service.
fedilink

Auditor app version 34 released: https://github.com/GrapheneOS/Auditor/releases/tag/34 See the linked release notes for an overview of the improvements and a link to the full list of changes. See https://attestation.app/about and https://attestation.app/tutorial for info about the app and optional monitoring service.
fedilink

**Pixel Fall Launch** > On October 19, we’re officially introducing you to Pixel 6 and Pixel 6 Pro—the completely reimagined Google phones. Powered by Tensor, Google’s first custom mobile chip, they’re fast, smart and secure. And they adapt to you.
fedilink

Android Security Bulletins
**Android Security Bulletins** Monthly device updates are an important tool to keep Android users safe and protect their devices. This page contains the available Android Security Bulletins, which provide fixes for possible issues affecting devices running Android. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as: - [Google](https://source.android.com/security/bulletin/pixel) - [Huawei](https://consumer.huawei.com/en/support/bulletin/) - [LG](https://lgsecurity.lge.com/security_updates_mobile.html) - [Motorola](https://motorola-global-portal.custhelp.com/app/software-security-page/g_id/6806) - [Nokia](https://www.nokia.com/en_int/phones/security-updates) - [OnePlus](https://security.oneplus.com/mend.html) - [Oppo](https://security.oppo.com/en/mend) - [Samsung](https://security.samsungmobile.com/securityUpdate.smsb) Learn how to check and update your Android version [here](https://support.google.com/android/answer/7680439?hl=en). **Sources** Fixes listed in the public bulletin come from various different sources: the Android Open Source Project (AOSP), the upstream Linux kernel, and system-on-chip (SOC) manufacturers. For device manufacturers: - Android platform fixes are merged into AOSP 24–48 hours after the security bulletin is released and can be picked up directly from there. - Upstream Linux kernel fixes are linked to directly from the bulletin on release and can be picked up from there. - Fixes from SOC manufacturers are available directly from the manufacturers. **Bulletins** https://source.android.com/security/bulletin#bulletins
fedilink

**Hello and welcome to [!grapheneos@lemmy.ml](https://lemmy.ml/c/grapheneos) !** Our Lemmy GrapheneOS community is *currently* `unofficial`, `reserved`, and used for announcements/news. GrapheneOS is a privacy and security focused mobile OS with Android app compatibility. https://grapheneos.org/ https://attestation.app/ https://github.com/GrapheneOS Official chat rooms: [#grapheneos:grapheneos.org]( https://app.element.io/#/room/%23grapheneos:grapheneos.org) and [#offtopic:grapheneos.org](https://app.element.io/#/room/%23offtopic:grapheneos.org) This is a community based around the GrapheneOS projects including the hardened Android Open Source Project fork, Auditor, AttestationServer, the hardened malloc implementation and other projects. --- **All installs should follow the [Official Install Guide](https://grapheneos.org/install). No other guides are recommended or supported.** If your question is related to device support, please see the [Which devices will be supported in the future?](https://grapheneos.org/faq#future-devices) for criteria and the [Which devices are recommended?](https://grapheneos.org/faq#recommended-devices) for recommend devices from the [FAQ](https://grapheneos.org/faq) section of the official site. If your question is related to app support, please check the [Usage Guide](https://grapheneos.org/usage). Sections like [Bugs uncovered by security features](https://grapheneos.org/usage#bugs-uncovered-by-security-features) should help if you have a native app with a security issue uncovered by hardening. If you want to know what browser to use please reference [Web browsing](https://grapheneos.org/usage#web-browsing). In general, Vanadium is almost always the recommendation for security and privacy. If your question is related to a feature request, please check the issue trackers. [OS issue tracker](https://github.com/GrapheneOS/os_issue_tracker/issues), [Vanadium](https://github.com/GrapheneOS/Vanadium/issues) for other GrapheneOS project check the [Reporting issue](https://grapheneos.org/contact#reporting-issues). --- **GrapheneOS has a very active community primarily based around the official chat rooms on Matrix and where most of the core community, including contributors, to the project have discussions. Most of those people are not active here on Lemmy's [!grapheneos@lemmy.ml](https://lemmy.ml/c/grapheneos) community.** The official GrapheneOS space groups together all of the official rooms along with members of the community who join the space. You can join the space at [#community:grapheneos.org](https://app.element.io/#/room/%23community:grapheneos.org) Links to join our new official chat rooms via the Element web client: | Matrix Room | Description | | --------------------- | ------------------ | | [#grapheneos:grapheneos.org]( https://app.element.io/#/room/%23grapheneos:grapheneos.org) | Best place to request support, ask questions or get involved in the project | | [#offtopic:grapheneos.org](https://app.element.io/#/room/%23offtopic:grapheneos.org) | Discuss topics not strictly related to GrapheneOS | | [#dev:grapheneos.org](https://app.element.io/#/room/%23dev:grapheneos.org) | Discuss GrapheneOS app and OS development | | [#testing:grapheneos.org](https://app.element.io/#/room/%23testing:grapheneos.org) | Provide feedback on Beta channel releases | | [#releases:grapheneos.org](https://app.element.io/#/room/%23releases:grapheneos.org) | Release announcements | | [#infra:grapheneos.org](https://app.element.io/#/room/%23infra:grapheneos.org) | Infrastructure monitoring and discussion | You can use the client and home server of your choice. For new users, the Element web app or mobile app with matrix.org as your home server is a sensible choice. Please contact the moderators of this community if you have any questions or concerns.
fedilink

Requesting is not begging, hence the purpose of c/community_requests

You seem like an angry person replying out of hate. I’m sorry for whatever it is that happened to you to be this way. It doesn’t give you a right to attack, harass and bully people.

Edit: your behavior is very much like an abuser in real life that gets off on verbally insulting people for your own sick and twisted kicks.



AOSP Community
Coming soon.
fedilink

Ultrasonic Cross Device Tracking and how to prevent it using GrapheneOS.
fedilink

Libera.chat IRC network

From Libera.chat’s guide:

Creating Channels.
Choosing the correct namespace.
Before creating a new channel on Libera.Chat, please take a moment to read up on our namespaces policy and ensure that your channel is named appropriately from the beginning. This will avoid disruptions in the future.

How to create a new channel.
Be identified.
You must be registered and logged in to services to make channels. You can log in by doing /msg NickServ IDENTIFY YourNickname YourPassword

Joining the channel.
The next step of creating a channel is to /join it.

Pick a channel name without spaces and add the appropriate number of #’s to the beginning, according to our namespaces policy. Eg, /join #awesomeprojectname if it is for an official project channel or a community channel about a project, or /join ##yournickname-chats for an informal channel.

Check that it is available.
You can check that a channel is registered or not with /msg ChanServ info #wanted-channel-name

If it is not registered ChanServ will tell you, otherwise it will show you the public information for the existing channel.

The first person to join an unregistered channel is granted temporary operator status. If the channel is empty and unregistered, you should have operator status now. If not, you will need to talk to the people already in the channel, or if there is nobody there with Libera.Chat staff either in #libera or on /stats p.

If the channel is already registered and you are unable to claim it, you will need to choose a different channel name.

Registering the new channel.
Once you’re sure you can register the channel, you need to /msg ChanServ register #wanted-channel-name

https://libera.chat/guides/creatingchannels