Thank you! Whatever it is, the issue seems to be specific to GOS, not stock Pixel. nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug & nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qz9thwden5te0v35hgar09ec82c30wfjkcctexf34p3 need to talk. This has been wrecking havoc on battery life for too long.

Reply to this note

Please Login to reply.

Discussion

What happened to the keyboard bug in Amethyst? It was about a year ago? You couldnt use OpenBoard or similar keyboards with Amethyst. I don't remember how the bug was fixed.

OpenBoard like keyboards and Amethyst about a year ago. Vitor said there was nothing titWasnt it last year happen last year?

Non-amethyst users won't see the edit lol.

Yeah, it was an inclusive range on the visual transformations to write names when @ tagging. All keyboards were the usual until "< size". AOSP keyboard wanted <= size.

I know one thing for sure. Its not Amethyst I'll be getting rid of. It will be GrapheneOS. They need to get their crap together.

nostr:nevent1qqsv2q2cqh2ug0gcu79amzxrkdvppyhgvfku2035r3u3aagfyu5d8pqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8h7cxcx3madw5xr2rr9puy68cud6sd7tm6aczwt6mhv0ec9xcklypsgqqqqqqs76xh2x