Great, well bye bye Pixel 6a, about time anyways I guess. I knew it was only a matter of time before they did something to make these devices completely unbearable, “AI” bullshit has done it.
I will definitely give it a shot, I’ve loaded an alternate OS on a phone before but it was more about customization then. Hopefully there will continue to be options like this for people who prefer to use their own brain and don’t mind pressing buttons instead of giving voice commands. I don’t want to talk to inanimate objects I talk to myself enough.
Well GrapheneOS is a a robust mobile OS built for security. It brings amazing privacy out-of-the-box and control features. You really own your phone! Not Google, not Big Techs and Government, YOU.
I will definitely give it a whirl, I also need to eventually switch my desktop to Linux as I’m still in W10, I used a lot of audio plugins (VST) that had no Linux versions but now I’m mostly hardware based. I just worry that there comes a time when it’s nigh on impossible to install an alternate OS on a phone but I suppose there will always be people trying to find a way.
Honestly I think that AlternativeOS will always be possible, the main issue is how compatible it will be with everyday apps that people rely on. We’ve started to see some compatibility issue with Play Integrity on GrapheneOS, with Revolut (has been fixed) and Alternate AppStore such as AuroraStore having some apps refusing to launch if not installed from PlayStore itself.
On the Linux side of thing you could see how your plugins performs on a VM and or see how Ardour plays with your hardware.
Yes.
Revolut prevented new users to login in a specific version of their app (the newer). Users that were already logged in could update the app without issue and users could use an older APK of Revolut to sign in. However the PlayIntegrity process that was banning their GrapheneOS users have been resolved and now the harden OS is whitelisted from Revolut.
At least that’s what I have followed/understood from the whole thing but I am not a Revolut user.
There’s more to it. It wasn’t Play Integrity blocking Graphene per se, but the fact that Revolut checked the build ID string, which was uniquely identifiable as Graphene for any build. This was then made more generic, so the block doesn’t work for now, but the workaround could break any moment and be made impossible by Revolut enforcing “strong” level of Play Integrity. Such bullshit.
RE: Audio stuff
I switched to bitwig long before I switched to Linux. Having familiarity with a DAW that ran natively was awesome; I also had a lot of plugins that ran as windows only VSTs. Yabridge + Wine was the answer.
You do have to downgrade wine to an older version (but this also helps you learn some Linux stuff) and works fairly well. I can even run omnisphere through yabridge (I do have a wild desktop tho so maybe not. the best point of comparison).
Mint is the first distro I used and most everything was really easy for getting audio stuff up and running quickly. I’m now using Garuda which I mostly like; there are issues that I’m still trying to work out.
Thanks, interestingly Garuda was at the top of my list but maybe I’ll just stick to Mint and not be fancy. Bitwig always interested me and if I decided to go back to a DAW I’m definitely taking a second look because I have a tracker background from way back and the modularity and easy hardware integration look great. I’m not too concerned about the plugins so much as the hardware now, there is no official support for the Black Lion audio interface I bought but I’m assured it should work fine under ALSA and as I’m currently only needing it to record a stereo pair it should be fine. The plugins I use now are mainly compressors and EQs for some final mixing and “mastering” and there seems to be a decent amount of choices now for native plugins in those areas but I do have some favs I might need to bring over so I will check Yabridge. Look forward to getting my hands dirty again, hacking windows has just becoming getting rid of nuisances instead of customizing my computing experience.
If you’d be interested in a tracker-like DAW, Renoise has a native Linux version.
For more traditional DAWS, Bitwig and Reaper are the two best Linux native options. Reaper is quite cheap, and also offers a trial version that just nags you like winrar.
I mean I like Garuda, but I would say it has taken a bit more to set up. I think if you’re running AMD you’ll be fine, it just depends on how much tinkering you want to do. Honestly the biggest reason I switched was that I had moved to Debian and games were not working too well for me - gaming has been much smoother but my desktop environment is a bit glitchy and buggy (likely due to my nvidia / Intel stuff)
Bitwig has better support on debian-ish distros, which mint kinda is (at least it is able to download and run .deb files).
Bitwig has been my favorite DAW since I began using it more in 2019, and as my only DAW fully but EoY '19; I enjoy all the flexibility I have with modules and the like.
I am unfamiliar with the Black Lion audio interface from what I’m reading it looks like they have class compliant interfaces so it should work with pipewire.
Ubuntu studio with the audio suite may be a good way to go too.
Depends on the total use case tho. I’m a newbie too in Linux but am happy to answer what I can
Only non-carrier-locked Google Pixel phones. They have been talking about potential partnership with other OEM but it’s not easy with Google ToS for Android OEM manufacturer to support other OS officially.
Also they have paranoid-level security model and beside a few company like Google, Apple and maybe Samsung few devices would meet their requierments… And you know, Samsung introduced Knox to prevent their users to flash other firmware or mod their hardware and the other one, Apple, is the company that killed the FOSS Cydia Store…
Phone carriers don’t want people “churning” (leaving their network for another) so they enforce the phone’s locking, especially if you buy the phone from the cell carrier, as they often advertise free phone or cheap phone on a payment plan, and use that to enforce people staying on their network.
I’m not a huge phone user to begin with so thats fine as long as I can change some colors here and there, I prefer less fancy tbh for instance I like the i386-dark theme here.
Well the chip is still capable of using some “AI cores” and you can install AI app on it but by default it’s gone. I would assume that there is some algorithme in Android that have been setup using Machine Learning and that you could market as AI since everything that is automated or made by computer gets the label AI as it’s the new buzzword of Silicon Valley and technology but I wouldn’t call them AI myself.
I really really want to but I can’t for another year because I’m still paying off my pixel. It’s still carrier locked and I can’t unlock it till it’s paid off.
It’s rough…I still have another 13 months I think. But to the article, I don’t have the options in my phone that they’re talking about. Do you? Or has it just not rolled out to me yet?
Fair. I think I had previously uninstalled Gemini when I first got my phone so maybe that’s why the app isn’t present? But the way that they are talking about it in the article, since Gemini seems to be replacing Assistant, maybe new settings will appear for me to mess around with…
I could be wrong, but I have a suspicion that you still won’t be able to once it’s paid off. I’ve run into the issue a few times in the past when buying an “unlocked” Pixel from Amazon that was carrier unlocked, but the bootloader was still not unlockable. A “carrier unlocked” phone allows you to use the phone on any carrier, but doesn’t always guarantee an unlockable bootloader.
That is a misleading claim right here, don’t blindly trust everything you read online. The core team of the project explained it very well why it’s not as dramatic as people made it seems too. It’s not an ideal position and Google is definitely going in a direction that doesn’t not benefit AOSP but no Android16 is comming to GrapheneOS and future version also should.
Did they explicitly say anywhere that future versions should be coming as well? I only see them mentioning Android 16, and devices still being “supported”, but that could also mean improvements in Android 16.
GrapheneOS will continue supporting the current devices we support until their end-of-life dates. We’ll also add support for new Pixels as long as they meet our requirements. We’ve tried to make that clear, but recent posts about changes to AOSP have been widely misrepresented.
Prior to Android 16, Pixels had first class support in the Android Open Source Project as the official reference devices. This was never one of our requirements and no other device provides it.
From my understanding yes but maybe not in this thread
These projects suffer from the same issues with how Google share new Android versions. This is not a solution. Also if you have a Pixel I would personnaly use a secure locked bootloader OS rather than an unsecure unlocked bootloader. I tend to privilege /e/OS on Fairphone and LineageOS on phone that have already dropped support.
Thanks for the report, I just got basically forced to install the new 16 update after a week of swiping it away so I’ll have to get going on that, I’m so tired of digging through the settings after every update to check every one to turn off all the tracking, suggestions, etc. If those even do anything. Whack a mole.
Great, well bye bye Pixel 6a, about time anyways I guess. I knew it was only a matter of time before they did something to make these devices completely unbearable, “AI” bullshit has done it.
Just install GrapheneOS on your device and AI is pretty much gone
Just about to say the same, since he has a pixel phone…
I will definitely give it a shot, I’ve loaded an alternate OS on a phone before but it was more about customization then. Hopefully there will continue to be options like this for people who prefer to use their own brain and don’t mind pressing buttons instead of giving voice commands. I don’t want to talk to inanimate objects I talk to myself enough.
Well GrapheneOS is a a robust mobile OS built for security. It brings amazing privacy out-of-the-box and control features. You really own your phone! Not Google, not Big Techs and Government, YOU.
I will definitely give it a whirl, I also need to eventually switch my desktop to Linux as I’m still in W10, I used a lot of audio plugins (VST) that had no Linux versions but now I’m mostly hardware based. I just worry that there comes a time when it’s nigh on impossible to install an alternate OS on a phone but I suppose there will always be people trying to find a way.
Honestly I think that AlternativeOS will always be possible, the main issue is how compatible it will be with everyday apps that people rely on. We’ve started to see some compatibility issue with Play Integrity on GrapheneOS, with Revolut (has been fixed) and Alternate AppStore such as AuroraStore having some apps refusing to launch if not installed from PlayStore itself.
On the Linux side of thing you could see how your plugins performs on a VM and or see how Ardour plays with your hardware.
Revolut is fixed on grapheneOS? I had to uninstall it because of that.
Yes. Revolut prevented new users to login in a specific version of their app (the newer). Users that were already logged in could update the app without issue and users could use an older APK of Revolut to sign in. However the PlayIntegrity process that was banning their GrapheneOS users have been resolved and now the harden OS is whitelisted from Revolut.
At least that’s what I have followed/understood from the whole thing but I am not a Revolut user.
There’s more to it. It wasn’t Play Integrity blocking Graphene per se, but the fact that Revolut checked the build ID string, which was uniquely identifiable as Graphene for any build. This was then made more generic, so the block doesn’t work for now, but the workaround could break any moment and be made impossible by Revolut enforcing “strong” level of Play Integrity. Such bullshit.
RE: Audio stuff I switched to bitwig long before I switched to Linux. Having familiarity with a DAW that ran natively was awesome; I also had a lot of plugins that ran as windows only VSTs. Yabridge + Wine was the answer.
You do have to downgrade wine to an older version (but this also helps you learn some Linux stuff) and works fairly well. I can even run omnisphere through yabridge (I do have a wild desktop tho so maybe not. the best point of comparison).
Mint is the first distro I used and most everything was really easy for getting audio stuff up and running quickly. I’m now using Garuda which I mostly like; there are issues that I’m still trying to work out.
Thanks, interestingly Garuda was at the top of my list but maybe I’ll just stick to Mint and not be fancy. Bitwig always interested me and if I decided to go back to a DAW I’m definitely taking a second look because I have a tracker background from way back and the modularity and easy hardware integration look great. I’m not too concerned about the plugins so much as the hardware now, there is no official support for the Black Lion audio interface I bought but I’m assured it should work fine under ALSA and as I’m currently only needing it to record a stereo pair it should be fine. The plugins I use now are mainly compressors and EQs for some final mixing and “mastering” and there seems to be a decent amount of choices now for native plugins in those areas but I do have some favs I might need to bring over so I will check Yabridge. Look forward to getting my hands dirty again, hacking windows has just becoming getting rid of nuisances instead of customizing my computing experience.
If you’d be interested in a tracker-like DAW, Renoise has a native Linux version.
For more traditional DAWS, Bitwig and Reaper are the two best Linux native options. Reaper is quite cheap, and also offers a trial version that just nags you like winrar.
I can totally relate to this! Perfectly sentenced.
I mean I like Garuda, but I would say it has taken a bit more to set up. I think if you’re running AMD you’ll be fine, it just depends on how much tinkering you want to do. Honestly the biggest reason I switched was that I had moved to Debian and games were not working too well for me - gaming has been much smoother but my desktop environment is a bit glitchy and buggy (likely due to my nvidia / Intel stuff)
Bitwig has better support on debian-ish distros, which mint kinda is (at least it is able to download and run .deb files).
Bitwig has been my favorite DAW since I began using it more in 2019, and as my only DAW fully but EoY '19; I enjoy all the flexibility I have with modules and the like.
I am unfamiliar with the Black Lion audio interface from what I’m reading it looks like they have class compliant interfaces so it should work with pipewire.
Ubuntu studio with the audio suite may be a good way to go too.
Depends on the total use case tho. I’m a newbie too in Linux but am happy to answer what I can
What phones can run graphene?
Ironically, only Pixels are supported at the moment.
Only non-carrier-locked Google Pixel phones. They have been talking about potential partnership with other OEM but it’s not easy with Google ToS for Android OEM manufacturer to support other OS officially. Also they have paranoid-level security model and beside a few company like Google, Apple and maybe Samsung few devices would meet their requierments… And you know, Samsung introduced Knox to prevent their users to flash other firmware or mod their hardware and the other one, Apple, is the company that killed the FOSS Cydia Store…
Phone carriers don’t want people “churning” (leaving their network for another) so they enforce the phone’s locking, especially if you buy the phone from the cell carrier, as they often advertise free phone or cheap phone on a payment plan, and use that to enforce people staying on their network.
GrapheneOS will feel very different, and quite a bit less of the “fun” customization options, since its goal is security.
I’m not a huge phone user to begin with so thats fine as long as I can change some colors here and there, I prefer less fancy tbh for instance I like the i386-dark theme here.
I am the same, so it wasn’t an issue for me either. I just wanted to confirm that you were not going to get the previous “fun” ROM experience.
Pretty much gone or fully gone?
Well the chip is still capable of using some “AI cores” and you can install AI app on it but by default it’s gone. I would assume that there is some algorithme in Android that have been setup using Machine Learning and that you could market as AI since everything that is automated or made by computer gets the label AI as it’s the new buzzword of Silicon Valley and technology but I wouldn’t call them AI myself.
I really really want to but I can’t for another year because I’m still paying off my pixel. It’s still carrier locked and I can’t unlock it till it’s paid off.
Yep you can’t flash carrier locked Pixels, I hope you don’t have much longer to wait or that the time will fly fast
It’s rough…I still have another 13 months I think. But to the article, I don’t have the options in my phone that they’re talking about. Do you? Or has it just not rolled out to me yet?
I avoid running Google software on my devices so I don’t have the Gemini App
Fair. I think I had previously uninstalled Gemini when I first got my phone so maybe that’s why the app isn’t present? But the way that they are talking about it in the article, since Gemini seems to be replacing Assistant, maybe new settings will appear for me to mess around with…
I could be wrong, but I have a suspicion that you still won’t be able to once it’s paid off. I’ve run into the issue a few times in the past when buying an “unlocked” Pixel from Amazon that was carrier unlocked, but the bootloader was still not unlockable. A “carrier unlocked” phone allows you to use the phone on any carrier, but doesn’t always guarantee an unlockable bootloader.
Any idea how I could check? It doesn’t say anything any that I’m my carrier account…
Sadly they might not be able to update GrapheneOS to new Android versions anymore :(
That is a misleading claim right here, don’t blindly trust everything you read online. The core team of the project explained it very well why it’s not as dramatic as people made it seems too. It’s not an ideal position and Google is definitely going in a direction that doesn’t not benefit AOSP but no Android16 is comming to GrapheneOS and future version also should.
Could you please link this explanation?
https://grapheneos.social/@GrapheneOS/114721666000552094
Did they explicitly say anywhere that future versions should be coming as well? I only see them mentioning Android 16, and devices still being “supported”, but that could also mean improvements in Android 16.
From my understanding yes but maybe not in this thread
Fair enough, I hope you’re correct.
Then LineageOS, /e/ or whatever.
These projects suffer from the same issues with how Google share new Android versions. This is not a solution. Also if you have a Pixel I would personnaly use a secure locked bootloader OS rather than an unsecure unlocked bootloader. I tend to privilege /e/OS on Fairphone and LineageOS on phone that have already dropped support.
I have a 6a, installed GrapheneOS though the web tool, very happy.
Thanks for the report, I just got basically forced to install the new 16 update after a week of swiping it away so I’ll have to get going on that, I’m so tired of digging through the settings after every update to check every one to turn off all the tracking, suggestions, etc. If those even do anything. Whack a mole.