It's dead, bros.
>>107099946with google killing sideloading on anything else, it seems destined to win at this point
>Dead It just graduated from being dependent on Google. They are working on a deal with a major phone manufacturer. If anything this is the best time for it. It also is getting more and more mainstream.
>>107099973This>>107099957And ThisBeing a gainfully employed white man Ii will of course buy their GrapheneOS native device on day one even though I already own a Pixel 9a.
>>107099973Yeah, i hope they make it as premium as they can. There is a market out there for sure that is bigger than the one of people installing custom roms.
>>107099973i cant wait for an0m phone 2.0!>>107100655youre brown
>>107100745My parents still got both my granddads Aryan certificate still in their documents at home. But the prove is in my ability to afford the new grapheneos phone as a toy.
>>107100745You're a faggot
new grapheneos phone drops:>no camera and no mic (it can be used to spy on you)>no wifi (you can use it to see through walls and shit)>no bluetooth (it's insecure)>no sms (also insecure)>no speakers (they can be used as a mic)>5G only
>>107100763To close to the truth
>>107099973Is there any chance that the OEM is not OnePlus? I hope it isn't because I don't want to use some heavy phablet trash. Considering they revealed the SoC will be the latest Snapdragon 8 Elite, it's not Sony and there aren't much more options.
>>107100759enjoy your honeypot phone retard
Can I get decent security features on LineageOS?
>>107100794Sorry you're so upset
>>107100825no
>>107100846Okay, so when is GrapheneOS coming to Samsungs?
>>107100854neverhttps://grapheneos.org/faq#future-devices>Which devices will be supported in the future?>Devices are carefully chosen based on their merits rather than the project aiming to have broad device support. Broad device support is counter to the aims of the project, and the project will eventually be engaging in hardware and firmware level improvements rather than only offering suggestions and bug reports upstream for those areas. Much of the work on the project involves changes that are specific to different devices, and officially supported devices are the ones targeted by most of this ongoing work.>Hardware, firmware and software specific to devices like drivers play a huge role in the overall security of a device. The goal of the project is not to slightly improve some aspects of insecure devices and supporting a broad set of devices would be directly counter to the values of the project. A lot of the low-level work also ends up being fairly tied to the hardware.
>>107099973Yup, google killing side loading apps is going to force me to buy an android phone not controlled by google
>>107100854Samsung supports most of the security features GrapheneOS needs, but they make them all inaccessible for alternate operating systems. So as long as Samsung doesn't change that it won't come to their phones. It will come to some Motorola phones in 2026 or 2027 though, since GrapheneOS is working with them to make that possible.
>>107101084you have no source that it's motorolla. No one knows the OEM except the graphene guys themselves
>>107100763this is why I have no hopethere was some possibility they might choose xperiabut they consider microsd and headphone jacks a security problem
>>107101095>they consider microsd and headphone jacks a security problemlmao really?
Next oemone plus or nothing phone
>>107101092please just no camera bump..
>>107101095>they consider microsd and headphone jacks a security problemsource?
>>107101256They did with the flashlight too I believe
>>107099946How exactly is it dead? They posted an update 13 hours ago.>I can't use it on the Pixel 10! I need the latest device to browse 4chan and goon!No, you don't.
>>107099973>It just graduated from being dependent on Google.This statement is so fucking retarded I don't even know where to begin with mocking you.
>>107101757posted what? why cant these troons fucking post on their website instead of constantly blathering on twitter threads
>>107099946Google needs to hurry the fuck up and publish the source for QPR 1.
>>107101928The autistic graphene devs seem convinced that it will eventually get published, even going as far as to chastise anyone who suggests otherwise.Not sure if they know something we don't or if they're just on some heavy copium.
>>107101960they really need someone else handling their social media
>>107101958>Not sure if they know something we don't or if they're just on some heavy copium.Judging by how they've behaved in the past when it comes to these trust me bro two more weeks things I'd say they're high off of something, god knows what, and are heavily hallucinating.
>>107101979Do you have examples of things they've been wrong about before? I've only recently started paying attention to the project so I don't know much about their track record.
>>107101985Out of hand? Honestly no. I've been half heartedly following the project for a few years so I'm just regurgitating shit I randomly picked up here. Not that it's a bad rom, I actually quite like graphene, but the devs have a tendency to overpromise and they often just get into bizzare twitter feuds.
Do you guys think there's sufficient interest in grapheneOS/android security for a general on this board?
>>107102107No fuck off. Shit up reddit with your generals.
>>107101757graphene is dying because google locked down latest pixels. pixel 10 was released months ago but no support.
>>107102608Did you not read my post? I'm well aware of that. You don't need the newest model, many of the prior Pixels still have years of support.
>>107100782I hope it's Motorola, they make honorable design decisions. I remember my moto z with cool attachments, and a gorilla glass screen that couldn't break
>>107103141prior pixels won't have years of support either. google is removing pixel support completely from aosp.graphene as-is cannot continue.
>>107103358Considering that my first ever smartphone was a Motorola, this would be amazing
Cashapp and venmo don't even work on graphene. LineageOS solved this problem ages ago. I don't know why the graphene devs just don't adapt to other phones and perhaps tablets. A focus on tablet/gaming/emulation like redmagic and the lenovo legion snapdragon elite would boost grapheneos in popularity. Being able to control your charging speeds, no thermal throttling for those of us who use magnetic phone coolers, etc.
>>107105267Muh identifing security chip though.
What are the downsides of Graphene? What apps don't work?Mostly worried about stuff like Maps and Venmo.
>>107105267>Cashapp and venmo don't even work on graphene.I use both of them just fine on graphene. Maybe him skill issue?
>>107105766I don't know where I heard it but I remember some video where the head developer goes on this 30 minute actual pure fucking reddit i love science tier rant.>DUDE THEY SHOT LE LAZOOOOOOOOOOORS AT IT IT MUST BE SECURE!
>>107099946The real reason google is fucking up graphene on new pixel phones is because cellebrite cannot break into grapheneos pixel phones and Nazi in chief trump doesn't like that
>>107105892>Mostly worried about stuff like Maps and Venmo.Jewgle Maps work and there's other Map Apps that are privacy preserving.Anything banking is a skill issue with very few exceptions. Look up here: https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
>>107099957kys
>>107103412thanks god I waited. I was about to buy a pixel 9 a week ago
>>107105933doesn't this mean I am forced to install via adb instead of just downloading an apk from my mobile browser and running it in the package installer?
>>107105986you have to use adb, yes. but you can use adb from your phone itself with local adb via apps like LADB/shizuku/termux
>>107105933Read the entire thing idiot; "developers" can install with apks. Guess how you become a developer. By uploading your id.
>>107106072I can't believe they are making me install an app to install apps
>>107106083Even if it wasn't (which it is) you have to be actually clinically brain dead or a paid shill to pretend they won't close any remaining loopholes. There are only those two options and I'm pretty sure I would have heard of a clinically brain dead potato continuing to type on their keyboard.
>>107106093>what is an appstore
>>107106083>Guess how you become a developerby tapping the build number 7 times in the settings, is this your first time on android?
>>107106318that's a repository. it's like installing a second package installer because the built-in one doesn't work
>>107099973But they rely on AOSP though?Google could just stop giving them the AOSP code and then they'd be fucked
>>107103358I always considered motorola but their lack of constant upgrades always bothered me, guess it wont matter if graphene actually does a better job with them than on google desu
>>107105267Venmo works for me and I don't even have the compatibility mode turned on.
>>107099946>skill issueWorks on my device.
>>107100825if you root, probably.>>107100846Better than stock OS, and if you dont got a pixel its not like its really a choice. hes right about daily driver-ness though, ive got Graphene and I dont know shit about fuck and its been fine. If you gave it to me without telling me it was Graphene I would not have known.
>>107105267I have cashapp, latest graphene version on a pixel 8. It works completely fine. capital one does too.
I dont know jack shit. Just got a pixel 8 and installed graphene. im liking it so far. what does all this hubbub mean for me
>>107108724Nothing really.There's some concern over Google no longer publishing their source code which would make it impossible for the devs to continue developing GOS, but they so far are convinced that it's simply a delay on Google's part. In any case, they claim they're working with a major OEM and will be ready to launch a device with official GOS support in the next 2 years, so any issues with Google would likely be resolved at that point with the support of an OEM.
>>107107599holy GPL violation
>>107108935The kernel patches are like 5% of AOSP, and most of that stuff has been upstreamed already. The rest is in vendor kmods which doesn't have to be open sourced.
>>107106982It's like installing an App Store, which is what I just said.
>>107099946>It's dead!>Use an iPoop Poogle.SAAAAARRRRR
We just need a powerful Linux mobile distro with an emphasis on web support so you can use banking sites on their mobile equivalents instead of apps and other """essential""" crap
>>107110224The problem is this has been tried a billion times, And it's unusable every single time.
>>107099946What google is doing to their Android will help other phones get market share, I will be buying a FairPhone for Christmas of 2025
welp it was fun while it lasted. I ran GrapheneOS on my Pixel 8 without too many issues. But the 8 had a loose usb-c port that was driving me nuts so I upgraded to a Pixel 10 Pro. Now I'm back in the land of raw dogging Android straight from Google. At least I get a reliable device that runs everything I need. It's also nice having Google's account and device security and things like "Find My" again.
>>107111861You know that there are a bunch of other ROMs you can use besides graphene, right?
>>107100913>on their meritsas in phoning (heh) home to mossad
>>107101960>just sell out to jewgle like we did!
>>107112071The only other ROM I'd consider using is LineageOS and last I checked it doesn't support the Pixel 10 yet either. I'm pretty sure that Google not opening up the entire Android 16 device tree or whatever has affected all of the custom ROM developers the same way.
>>107109191Nonfree firmware is OEM specific.It does not matter if Google withholds nonfree Pixel firmware because GrapheneOS is working directly with OEMs now, and would have direct control of the hardware supply chain, and may not even use Pixel hardware at all.
