-
@ GrapheneOS
2025-06-12 19:28:53
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq6asw3ntxmecx5gtcr2r3y276qmx4d0ppug560ajvqy2sq3n9vlaqdcnnc8 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqul4xvark6lq9682t42vplghgu26kuq9tde0qum8wm04wt355aedsv33jyf nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqg4eea6fyf4cjsr4yzuucfux8r8wkprmn66l47x93qpzv487uj8jqu2jv24 The biggest issue will be with this Android 16 update because we were not expecting this to actually happen the way it did. We received early notice in April about AOSP dropping device support but didn't know exactly what that meant. It was a factor in us preparing for the port more than we ever have before combined with our lead developer likely being unavailable for the whole port due to being conscripted. That's why we have an initialAndroid 16 port done now.