You can, no flashing back and forth required, simply loading up the web installer and following the steps and instructions should do the trick.
### #Amethyst v0.76.1: Zap Splits
Adds support for Zap Split setup and payment via NWC and manually via individual wallet calls.
- Adds zap split setup
- Adds zap split display
- Adds zap split payment
- Fixes bug when verifying the checksum of LNURLs (bech32) in uppercase
- Allows playback to save any position in real-time and not only after 5 seconds
- Removes potential bugs when the list contains an e tag with an a reference
- Moves deletion and report to be the last item on the dropdown menu
- Moves broadcast up in the dropdown menu
- Updating dependencies
- Updated translations for cs/de/sv
- Forces valid hexes in p- and e- tags when receiving the event
- Stops accepting space as a Valid hex char and requires an even number of chars (padding)
- Forces the ZapRequest to exist when processing the LnZapEvent
- Fixes some long NIP-19 cutting off in notes
- Updates to Finnish, Swedish, Czech and German translations
- Adds Bengali, Bangladesh translations
- Adds Italian Translations
- Updates Chinese Translations
Download:
- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.76.1/amethyst-googleplay-universal-v0.76.1.apk)
- [F-Droid Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.76.1/amethyst-fdroid-universal-v0.76.1.apk)
Yeah yeah, that's all amazing and all but clearly this was the nost important for this new release /s 😉😆😂
- Moves deletion and report to be the last item on the dropdown menu
- Moves broadcast up in the dropdown menu
Need any support and assistance, just let me know...
This interpretation surprises me, curious to know what you determine we're defending against?
In real terms this is not an attempt to defend us but defend end users from misappropriated and redefined clear terminology used to mislead.
We would genuinely love to see any one of these OEMs provide a Pixel level device. We are always looking for an OEM to do so, in the effort of making GrapheneOS first party software. Ubfortunately like Obi-Wan with Anakin too many of them take the path to become Vader.
How am I only just discovering #DeathValleyKnights throne they're good. 🤘
Omnissiah be praised for this digital aural pleasure!
As much as I admire what a lot of these companies I believe genuinely want to achieve, they have a lot of serious drawbacks and concerns, especially around how they market themselves when not in a commanding enough position to access the most appropriate and properly supported chips.
See this note covering the main players in this field.
Yeah cant be used alongside with the same number, it's fine to replace Signal with it however if you want to restore a Signal backup you have to wait for a little for Molly to version match.
Signal doesn't publish APK releases via Github, just tags for building yourself.
Download via the Danger Zone here:
https://signal.org/android/apk/
This should update itself in future where Play Services isn't available and it uses websocket rather than Googles Firebase for push notifications.
That said I would recommend Molly too as listed above, some GOS staff and community use it also.
Signal doesn't publish APK releases via Github, just tags for building yourself.
Download via the Danger Zone here:
https://signal.org/android/apk/
This should update itself in future where Play Services isn't available and it uses websocket rather than Googles Firebase for push notifications.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z any chance of moving them apart in the menu? Save any future evidence of #FatiguedFatFingerSyndrome 😄
The past 2 major OS releases have taken a couple of weeks.
Android 13 was released August 15th and we had an initial release on the 21st. https://grapheneos.org/releases#2022082100
However there is no set timescale, we were able to do this despite large features like sandboxed Google Play and Storage/Contact Scopes etc is because of our focus on preparing for new releases throughout the whole year.
Regards security features these are added all the time as you'll see from the release cycle above the linked one.
Take how Lineage and by association those based on it handle a major OS release, they took until December to have an initial port ready. That means their Pixel users had months of missed critical security patches.
We're always working on making changes more minimal, less invasive and revising the commits implementing them by splitting them, squashing them, reordering them, etc. We always have everything maintained as a clean patch set on top of the latest stable. Our approach is different.
I may have accidentally in my fugue morning state tapped broadcast over block on a spam post please ignore.
My bad.
We wish non-Google hardware would match or beat Google hardware with full support of alternate OS having access to it. Therefore supporting us to support them.
nostr:npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c does grapheneos have an official nostr account? I see there's a Twitter and a mastodon but I can't find an npub, I'm only on nostr and it would be useful to have a stream of announcements/updates where possible :)
No I am the only presence/staff member on Nostr. However there are fediverse bridged accounts that post announcements from the main project account on Mastodon.
This being one: nostr:npub1yvrtxdh3dr62mkx6jfx6ayra9f4ecylmpgrxw27hwzpfthk8tknssgn50m
You can ensure you recieve them by using the mostr.pub relay, click the link for info.
Fantastic to hear, #Amethyst is awesome, thanks to the tireless effort of nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z giving us #Android #Nostritches a fully featured #Nostr client.
As mentioned below you have a few options to choose from.
The following note covers the differences between the most common that is worth consideration depending on your motivation for switching.
You also have this article from PrivSecdotdev too:
https://privsec.dev/posts/android/choosing-your-android-based-operating-system/
Beyond that, the same sentiment expressed in the quoted note applies here too, any questions, support etc regards GrapheneOS etc AMA.
Be pleased to work it out with you,
Be well and take care, enjoy your journey.
People keep getting this wrong, Samsung hardware does indeed come close to matching Pixels and could be supported, however, when you unlock the bootloaders knox trips and blows efuses that break that hardware indefinitely as well as hobbling other features, regardless of if their stock OS is reinstalled.
Also comes down to SoC choice etc and how well their firmware driver support works, level of updates, regularity and how fast each OEM is to push them.
Only Pixels as it stands provide regular monthly updates and even then only GrapheneOS is able to ensure those come at our desired time as we often ship them before Google such as this months (September Security Patch) which Google postponed to include in a broader OS update.
As and when other OEMs step up their level of alternate OS support, hardware choices based on longevity of firmware/driver support and meet the regularity of providing security updates could we do so and we WOULD be happy to do just that.
However security and privacy actually matter to us, and your security matters to GrapheneOS, these terms are more than marketing buzzwords to us. We're not going to lower that standard for broader device support. More complete explanation can be found here:
https://grapheneos.org/faq#device-support
For those who want that, DivestOS is likely the next best choice if their ideological position on Google devices requires compromise elsewhere.
https://privsec.dev/posts/android/choosing-your-android-based-operating-system/#divestos
For everything else while you may choose not to use Google hardware be aware that the OSes you use all use Google by default and also bake it back into the system regardless of if you opt in. The implementation maybe open source but what is being implemented isn't. It's still propreiatry Google code.
Such Google services are: microG as mentioned above, connectivity checks, network time, attestation key provisioning, SUPL, DNS fallback (LineageOS only), PSDS (Pixel 6 and 7), eSIM activation and more.
Hi Simple, I've noted a couple of issues you were having below to troubleshoot, you are using a Google Pixel phone that is compatible and supported yes?
Next are you using the official instructions or some third party youtube video?
Are you attempting to flash with the CLI or Web based installer method?
GrapheneOS has 99%+ app compatibility with the sandboxed Play Services and per app toggles to disable where necessary or desired our hardening on/off.
Banking apps rest in that 1% in some cases due to their reliance on deprecated safetynet or Play Integrity API. However as linked below we have a resource provided by the community for the community based on it's feedback.
Yes using other non stock cables can cause issues as not all USB C cables either C-C or A-C are fully standard compliant resulting in them not being usable for low level fastbootd (this is not the standard fastboot in the bootloader).
Use the stock cable, ideally with another Android device (no driver required), if using a laptop be aware some use a daughterboard acting as a hub internally for USB C dependent on how old it is, the same for front IO on desktops.
Also: