@RichFelker a warning to you, as we're running similar android setups (and i wonder if you have encountered this too)
-
-
Replying to @int10h @RichFelker
because i had microG installed as a system app, upgrading LineageOS effectively uninstalled it, and removed all settings
1 reply 0 retweets 0 likes -
Replying to @int10h @RichFelker
including the list of which apps were authorized to use Google Cloud Messaging
1 reply 0 retweets 0 likes -
Replying to @int10h @RichFelker
seems like Signal doesn't know how to ask permission _again_ after it's already been asked and granted a first time, so now it just crashes.
1 reply 0 retweets 0 likes -
Replying to @int10h @RichFelker
other apps that use GCM still work, but microG hasn't added them back to the list of apps authorized for GCM, so they must have a fallback
1 reply 0 retweets 0 likes -
Replying to @int10h @RichFelker
sorta speculative atm, needs more work before bug report. but if running microG as system app, don't update lineage if you rely on Signal
1 reply 0 retweets 0 likes -
Replying to @int10h
Indeed, the lack of proper infrastructure for managing system apps makes this all really broken. I think you need a working "mover" app...
1 reply 0 retweets 0 likes -
Replying to @RichFelker @int10h
...to move a live install (with state/data) back and forth, and move it to non-system before upgrading the OS.
1 reply 0 retweets 0 likes
None of this would be an issue if the OS had a proper pkg manager and individual pkg updates rather than wiping & reimaging whole partition.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.