#GrapheneOS installation was scaringly easy with a YouTube tutorial in the background.
Nostr #Amethyst was the easiest part of the migration, lol! An absolute non issue.
The worst part was my #threema backup, as always, but it worked in the end and had nothing to do with grapheneOS...
Workaround for invalid threema data backups:
I had to make sure the screen wouldn't turn off and the energy saving options were turned off for the app while threema was creating it's backup 🤬 All to make sure that Android wouldn't interfere with the backup process while trying to run threema in the background 🤷♂️ 🤦♂️
d0enakalle🐇⚡
npub1d0…9xlas
2023-07-22 07:52:44
Author Public Key
npub1d0enakaludyvruzdndcgl4glkcqyfpvp9tdtf8cawzkskekhcu2sq9xlasPublished at
2023-07-22 07:52:44Event JSON
{
"id": "952d41939ab8432a09a8791aa7f5c6f37c96160172ede5abe97a170f2ef9972a",
"pubkey": "6bf33edbbfe348c1f04d9b708fd51fb6004485812adab49f1d70ad0b66d7c715",
"created_at": 1690012364,
"kind": 1,
"tags": [
[
"t",
"GrapheneOS"
],
[
"t",
"grapheneos"
],
[
"t",
"Amethyst"
],
[
"t",
"amethyst"
],
[
"t",
"threema"
],
[
"t",
"threema"
]
],
"content": "#GrapheneOS installation was scaringly easy with a YouTube tutorial in the background.\n\nNostr #Amethyst was the easiest part of the migration, lol! An absolute non issue.\n\nThe worst part was my #threema backup, as always, but it worked in the end and had nothing to do with grapheneOS... \n\nWorkaround for invalid threema data backups:\n\nI had to make sure the screen wouldn't turn off and the energy saving options were turned off for the app while threema was creating it's backup 🤬 All to make sure that Android wouldn't interfere with the backup process while trying to run threema in the background 🤷♂️ 🤦♂️",
"sig": "85e3b321780a3d3d724e904660c82c5582795c82e34e8ce88efe259cb81692936bfecb81192132b865841b7603ca7a7d9a410d15d35f95f5f0d31d6ac7d44b54"
}