@jnod4@lemmy.ca to Buy European@feddit.ukEnglish • 24 days agoGoogle will develop Android OS entirely behind closed doors starting next week9to5google.comexternal-linkmessage-square49fedilinkarrow-up1288arrow-down16file-textcross-posted to: technology@lemmy.worldandroid@lemmy.world
arrow-up1282arrow-down1external-linkGoogle will develop Android OS entirely behind closed doors starting next week9to5google.com@jnod4@lemmy.ca to Buy European@feddit.ukEnglish • 24 days agomessage-square49fedilinkfile-textcross-posted to: technology@lemmy.worldandroid@lemmy.world
minus-square@PortugueseFOSStechie@lemmy.mllinkfedilinkEnglish18•24 days agoI wonder what this will do to grapheneOS. I was just about to flash it on my phone this weekend. Yet another example of companies circling the wagons
minus-square@easily3667@lemmus.orglinkfedilinkEnglish6•24 days agoIt says in the article the code will still be released in the same way it’s been for ages.
minus-square@PortugueseFOSStechie@lemmy.mllinkfedilinkEnglish6•24 days agoI understand that. But the development will be in closed branches. That has a greater chance of causing pains when GOS devs are adjusting these new features right? Because now you, theoretically, have no upfront information about whatever bloatware google is about to inject in.
minus-square@epyon22@programming.devlinkfedilink14•24 days agoThey didn’t before this only affects code changes going from AOSP to Google’s private branch, which is going away. Code from Google’s private branch to AOSP is unaffected. Custom ROMs are all just down stream consumers of AOSP repository anyways.
minus-square@PortugueseFOSStechie@lemmy.mllinkfedilinkEnglish2•23 days agoThat’s a fair response and answers a lot of my doubts actually. Thanks!
I wonder what this will do to grapheneOS. I was just about to flash it on my phone this weekend.
Yet another example of companies circling the wagons
It says in the article the code will still be released in the same way it’s been for ages.
I understand that.
But the development will be in closed branches.
That has a greater chance of causing pains when GOS devs are adjusting these new features right?
Because now you, theoretically, have no upfront information about whatever bloatware google is about to inject in.
They didn’t before this only affects code changes going from AOSP to Google’s private branch, which is going away. Code from Google’s private branch to AOSP is unaffected. Custom ROMs are all just down stream consumers of AOSP repository anyways.
That’s a fair response and answers a lot of my doubts actually. Thanks!