gonner11: yes, I have a google fi pixel 2. The only issue is trying to send or receive MMS text messages. Doesn't work.

I can't unlock my pixel 2. I'm in the bootloader, device state: locked

I followed the instructions and OEM unlock is on, USB debuging is on...

anyway has suggestions? This is a project fi phone

<i_am_your_device "I have a pixel 4a and would like"> we need people to help us test building GrapheneOS, this is step 0 to help us out grapheneos.org/build#development-branch

once you can do that, then you can up us test the kernel for the new version of Android for your specific device family

my other device is pixel4a btw

is this works on my pixel 2... I'd be happy to help

we dont have enough people to support moving the Pixel 2 family to Android 11

for GrapheneOS, its a lot of work and not enough people willing to pitch in

as per the website, GrapheneOS supports Pixel 3 and Pixel 4 family devices

is this a bot?

sandroteem: Auditor can give some guarantees. Guess it depends what you are worried about, what you want to prove & to who...

Someone here have experience with this: if the device says "device state: locked" in boot loader, does that mean the phone cannot be unlocked?

This is a porject fi pixel 2 phone

How big the threat is...

If you are really worried using a device, which you don't know the history of isn't great...

cant_unlock: check the website. Need to go into android settings on device, enable developer options, enable OEM unlocking

@dazinism thanks, I followed all of that. I'm after these steps. developer mode is one. OEM is unlocked.

and aeon isnt a bot!

...well if they are they are a very helpful one 😆

running the fastboot command just says it's waiting for a device to connect

Probably means you need to try a different usb lead or port

Or you have an ancient version of fastboot

dazinism did this too - this is a USB cable that is verified to work for data transfer when the phone is booted normally

fastboot --version

it is also my third USB cable attempted, the other two were power only

fastboot version 30.0.4-6686687

fastboot is a bit more demanding of good quality lead and/or port

Can fail when data transfer and adb don't

@dazinism - OK, and it has to be able to transfer data right?

asking because my good thick cable is power only.. anyway ok I am trying another cable

fastboot flashing unlock

You using a usb A - C lead?

Yes

<dazinism "and aeon isnt a bot!"> i might as well be to the drones lol

I don't need sudo right?

(I'm on Debian)

another cable, same result

dazinism: ♥️

trying another USB port

Depends if you've followed the instructions on the website properly

this instructions say no sudo... I tried both

If you've set PATH dont need sudo

it does not work with another port on the computer either

ah, but I didn't set path. I had an issue

I changed to dir and I'm doing ./fastboot

shoudl work just the same though

If you tried sudo, think probably might as well continue with that

sudo gives me a permission issue

"sudo ./fastboot flashing unlockFAILED (remote: 'Flashing Unlock is not allowed')fastboot: error: Command failed"

Think you need udev rules for debian

I've not had to set them up

udev?

Have you done that?

I don't know what udev rules is

so no, I guess I haven't :)

Its something to do with usb security

Opens things up so you can communicate down usb

hmmmm

Hang on I'll find something....

the ubuntu rules should work

for debian

gl cant_unlock

interesting. ok I'm cloning one sec

and thanks for the help

Actually, thinking about it, if you using sudo think you wont need udev...

they might not have sudo installed

its easier to get them to use the udev rules

its up to the user to get their distro to recognize their device

or use to arch 😛

Eh well I'm tryng to follow the instructions there I get some commands not found

some Path issues Debian has these damn

No need for the ./

Just

sudo fastboot flashing unlock

it won't find it but I'll try

yep. command not found

fastboot is not in my path

when you set the path following the instructions on the website

do not open up new windows

the path does not get carried over, because you only set it temporarily

<gonner11 "I turned on developer options as"> this assumes you have fastbooth on your path, source.android.com/setup/build/running#unlocking-the-bootloader

If I set the path it forgets what is on the path before and I lose other commands

doesn't matter ./ should work if it's not on the path. something else is off

you are doing it wrong if you losing your commands

dont edit any .profile or .bashrc files if you dont know what your doing

just follow the instructions on the website

I just did it. Same issue.

if you lost all your commands, restart your computer

"< waiting for any device >"

oh I see what I did wrong before with the path command. ok my bad. but I still have the same issue

yes, because your distro doesnt let you use the usb to connect your device as a local user

that is, fastboot is in my path now, still doesn't work

ah ha.

yes, that is another problem

that why you use android udev rules

to avoid having to use sudo

wouldn't sudo work...? I did try to clone and install udev rules

i cant help you troubleshoot that issue because i dont use a distro that makes me do that, i just install the udev rules

again, setup the rules github.com/M0Rf30/android-udev-rules

ok. I will look more into that, I ran into some issues installing (following their instructions) but that looks more promising

gl

one question. when I do run fastboot with sudo, I get "FAILED (remote: Flashing Unlock is not allowed)"

is that the same issue with the udev tools, or, something is wrong with the phone?

because of your distro rules

ok. got it.

Thanks aeonsolution[m] I'm going to work on this.

if you dont know how to fix that then there's is no point jumping down the system administration rabbit hole

just setup android udev rules

<aeonsolution[m] "just setup android udev rules"> I've been curious about that, is that only for some distros? Cause I didn't have to do that for manjaro. Just used this easy install script github.com/Peter-Easton/grapheneos-easy-installer

birdie: wiki.archlinux.org/index.php/Android

How does porting work? Is it, for the most part, cherry-picking GrapheneOS-related commits from the old `10` branch into the `11` branches and testing them?

I've noticed the site switched over to mention the 11 branch now: grapheneos.org/build#development-branch

high level overview yes

you have to checkout the kernel from google

what device do you have

3a

oh nice

each device has a kernel that is provided by google as a prebuilt

go here android.googlesource.com/kernel/msm

find your device

clone the project

and cherry-pick everything from GOS github for your corresponding device kernel

you start with commits that dont come from google, you get them from the project

Hey inthewaves nice to have you here!

Noticed on github all the stuff you've been doing

Some interesting things you been upto

anu and i have a kernel for the beta, anu may have a new one now. what you would do in that case, is instead of doing that manual work you would clone our projects and put the our kernel where the prebuilt one is put

here grapheneos.org/build#kernel

and then build out the os and see if it works on your device

here is an oldish kernel

<aeonsolution[m] "birdie: wiki.archlinux.o"> Thanks I'll read that

cdesai: the entire "guide" could be shortened quite a fair bit

Tbh I ignored the binary stage. Building without a vendor for now

oh nice, the kernel for the beta is the same as 11 🕶️

Does anyone know wot this is

<aeonsolution[m] "you start with commits that dont"> Thanks, I'll look into it

inthewaves: send me a message if you need help

glad to have you checking this out!

aeonsolution: you can invite him to that chat

ls

kryptonymous stop spamming reactions

didn't know that was spamming anupritaisno1:. Was just catching up on the thread and reacting. BTW, I appreciate all you do for the community. 🙂

Please, how can i works alarm on GOS?

use the standard alarm clock app?

strcat: do you happen to know off top of your head if we are going to run into our usual chromium webview incompatibility issue

otherwise i'll go take a look

<strcat[m] "use the standard alarm clock app"> yes, but not works

Works fine for me

Did u set it for correct AM/PM? 😂

strcat: look like v86+ has sdk set to R

dan-v: yes and current version is 85

so unless we use beta, similar issue

I'll just use stock WebView temporarily

save trouble

sounds good strcat - i'll probably do the same initially until things are working and then give beta a shot

cdesai: seedvault and setupwizard will need to be ported

setupwizard breaks the build atm

Vanadium itself (browser only) works

should be done with that for now

also doing the Vanadium update to the new release

so much to do

so tomorrow or in the next few days when they release the Android 10 security update

plan is to do a final release based on that for Android 10 branch

along with switching over to the Android 11 kernels

to get the kernels shipped / tested early as a starting point

goal is to get the kernels ready today

testing Android 11 Pixel 2 kernel atm

need help with Pixel 3/3a and 4 still

I might just do a release tonight if we get the kernels done

before they release security patch tags

we'll see

strcat: have you validated if prebuilt vendor works with stock 11 AOSP?

okay Pixel 2 kernel works

dan-v: no

I'm working on Android 11 kernels with the last Android 10 tag

along with porting very basic stuff to Android 11 via emulator

I'm not touching Android 11 device support, letting you and cdesai do that

and others

kernel stuff is not that bad so far

strcat: ok, sounds good

Pixel 2 doesn't have many changes, 3 and 4 do

one thing to note is for qcacld Google applied a similar change as what I did disabling build tag

they backported a ton of stuff so there may be issues with other changes

need to figure that all out

this android-10.0.0_r46 tag they pushed... really fucking weird

it's from 2019 lol

lol wtf

BTW

it's not going to impact many people

but if you installed GrapheneOS before the first stable release in 2019, there may be issues updating to Android 10

because I am not going to port the code for handling the old encryption format from before the first stable release

i.e. people who installed it when it was Android Hardening may be forced to factory reset

it would be too much work to continue supporting the old format especially since it's difficult to test

Deletion: 100

installations that were made at some point before the 2019.03.05.03 release of the Android Hardening project will be forced to factory reset after updating to GrapheneOS based on Android 10

2019.03.05.03 was the only tagged release under the Android Hardening name, so this only applies if you installed before there were even official releases

i.e. one of the early testing builds

if you've factory reset at any point since then it's already handled

I'm not willing to continue porting the backwards compatibility handling forwards and it would be far too much work to actually do a forced migration (which is why it was never done)

Thanks strcat (=

Hey I’m still having issues generating signed build. I get this « warning » pastebin.com/k22iYA2N

The signing process complete but it must be badly signed because auditor fail at verified boot

atasuke: Auditor just doesn'

* atasuke: Auditor just doesn't know about your keys

you need to fork Auditor and add your verified boot key to the database

and set the debug / release keys for Auditor (that it uses to verify Auditor on the other device) to the keys you use to sign Auditor

it won't be interoperable with the official Auditor and AttestationServer builds

they don't trust your keys for signing the OS or for signing Auditor

if you use a modified build of Auditor, it won't pass attestation, since it isn't signed with the correct keys

the whole point of it is that you can't trick it like that

you can try

it won't work

the hardware-based attestation includes the signing key of the app from the OS

and the signing key of the OS

(it gets signing key of the OS in early boot before the OS is booted up and reads persistent state)

Thanks you a lot for the detailed information. This should be added to the website

Is there any resources on how to run your own attestation service ?

I have tried building Vanadium trichrome before and renamed it in different package in args.gn

Despite doing so, I can't install the apk in an official GrapheneOS phone

@d64qoc8432li8p9ouijtv:matrix.org: the apk needs the library apk installed first

<cn3m[m] "@d64qoc8432li8p9ouijtv:matrix.or"> I did that

Even in adb

But some error came

Gotta check later

Library -> Chrome apk

testing Android 11 kernel for Pixel 3 atm

atasuke: it's covered in the attestation server README

atasuke: server needs the same adjustments: add your verified boot key and perhaps give the OS a name like GrapheneOS (atasuke's build) for the database

atasuke: and set the keysit checks for Auditor to your debug / release keys

* atasuke: and set the keys it checks for Auditor to your debug / release keys

then you can just launch it on the server - you only need to do setup to configure it being able to send emails

Iirc

The package name is there

But, not sure if I did something wrong in building process

Just followed the instructions and downloaded the dependencies.

strcat: thanks you but where do I add the keys in the app and server ? Where is the database ?

Guys, I'm looking for a developer that could port graphene to a device I'm working with. Will pay of course

I do have sources (AOSP) for that device, so shouldnt be too hard I Guess?

kmart: grapheneos.org/faq#future-devices The expectation is you buy a device for GrapheneOS. The issue is that other devices don't meet the standards of the project otherwise they likely would be supported or at least considered

if it doesn't meet the criteria it is not GrapheneOS

This device wont be used for any kind of media playback, deleted the TZ truslets for that, as they are full of bugs usually, No need BT or NFC, browser or google store to install crapware. I think I can be made secure

<strcat[m] "testing Android 11 kernel for Pi"> The hero we don't deserve, but the hero we need

atasuke: in AttestationProtocol.java

look at commits adding devices

strcat: ok thanks a lot

cn3m[m]: its why I said I would pay for this anyway, I understand that some devices are better targets for this, but I really want soemthing more secure than a basic AOSP code

<kmart "cn3m: its why I said I would pay"> you are better with a locked bootloader

the bootloader will be locked, I woen full license of the code, and will write my own root key to them

own*

kmart: Which device you got if you don't mind sharing?

and while I am busy rewriting the entire boot chain up to the point kernel is booted (scrapped the MTK code of that part), I would prefer to replace the upper part with something better than AOSP

its an unbranded ODM device manufactured in china of course :) but at least I have all the source

Why not just buy a supported device?

because then I wont be able to rewrite the bootchain, incl, WiFi FW and cellular modem fw?

I understand all Graphene devices use modem/wifi fw blobs as they are, with all the bugs

Okay. But I have not heard good things about the Mediatek SOCs.

the SoCs are fine honestly, its the code that has a backdoor within a backdoor

<kmart "I understand all Graphene device"> They are isolated.

isolated how?

I am going to have to ask you to switch to offtopic chat. This has nothing to do with GrapheneOS and I can't see this device being supported

lmfao

"unbranded ODM" :curi

* "unbranded ODM" :curious:

No stress cn3m[m], just noting the reason why not grapheneOS-device, because I cant upgrade other parts of the FW on those. And AFAIK, aside from one custom phone form kickstarter, no retail devices have the modem isolated in a real way, they all share some memory and are vulnerable to modem->kernel exploitations

inrdrna[m], yes, look it up, you have to order like 5000 units, pay source code fee and you can start your own phone project

yeah no

iPhones have been doing that for years very well

and lately Pixels have been doing just as well

IOMMU can and does work

also MTK is absolutely shit at handling security issues

remember the root exploit for the kindle?

that effected every MTK chip

after a year of not patching

Google said fuck it and mitigated it themselves

Google doesn't do that!

sure, I know those issues, and many many more, every piece of boot chain has tons of bugs that are still unpatched to this day

while preparing to this project I must have found like 10 different ways to bypass secure boot on MTK

incl. unpatchable romcode bugs

but that isnt an issue

Save yourself the time and effort and buy a device every few years and don't worry about upgrades

since I scrapped all that code and rewrite it from scratch

it is not worth anyone's time

cn3m[m], I'm making my own phone bruh :P I'm not here to upgrade my personal device or somthing

that is assuming your code is flawless which is a huge assumption. Again if this could be moved to the offtopic chat I would apperciate that

well, then back to the core issue at hand - I would like to swap the AOSP delivered within the deal, with soemthing else, preferably GrapheneOS

and I would pay for this -- thats about it

"/join #grapheneos-offtopic"

but thats on the graphene topic, isnt it ?

device porting topic

kmart: to supported devices

that is not a supported device

thx for the clarification :P

kmart: yeah if a device is going to meet the criteria of the project then it is on topic

well it would be hard to judge that, as in the end the device will be indeed on the MTK chip but will run little to none of actual MTK code

you have the criteria

make your case why it meets every point of it

anyone use m.uber.com on graphene?

As far as I can tell it doesn't allow one to add stops or change destination... Maybe there's a way to use the app without google services?

or another work around I don't see?

<derpy "anyone use m.uber.com on graphen"> Try using desktop mode?

Not sure

d64qoc8432li8p9o I made a support ticket with them... Doubt they'll be helpful though

No way to do using uber.com or m.uber.com

I really doubt Uber will work without Google MAps

Not sure about adding stops or changing destination but m.uber.com seems to work OK for requesting a ride.

(I'm on CalyxOS w/microG disabled so this might not be 100% comparable to Graphene, but it seems to work OK)

<derpy "anyone use m.uber.com on graphen"> adsfasf: so far i doesn't work at all. Same goes for most mobility apps of course

btw I would greatly appreciate if people could send more PayPal and GitHub Sponsors donations to help cover the costs of defending the project

legal fees for defending against the BS lawsuit filed against the project and for filing our own lawsuits are very expensive

I'm going to be primarily using Bitcoin donations for funding other developers

been using PayPal to cover legal fees and it's entirely out atm

it's ~2k/month, need more donations

atm Bitcoin -> being used to fund other developers and hardware for them, PayPal -> legal fees, server costs, domain registration costs, GitHub Sponsors -> my income

not 100% but that's approximately how it's used

this way I don't need to deal with handling the complexity of capital gains on Bitcoin as income since the project isn't for me atm, keeps things simpler

a site that had my credit card info was compromised and my bank hasn't sent the replacement yet so I have to use PayPal to pay for stuff atm which is really annoying, had to move over various recurring payments to it and deal with hassle beyond that

they gave me a new number but didn't send the card, they fucked up somehow, really annoying, been a month since I can conveniently pay for stuff

and I had a backup card that's unused but they never sent a replacement when it naturally expired, good stuff

and they aren't responding to my messages via their site atm, and they won't give me a number for calling them about this, the regular credit card number is 'disputes' and they won't deal with it

I only need it so I can easily pay for stuff, I don't run a balance on it

so like atm OVH payments for GrapheneOS, domain registration and all my personal bills had to be moved to paypal or getting someone else to pay for it with a credit card and sending them cash

super annoying

banks always causing me problems

how hard it is to just send something in the mail?

strcat lawsuit is in US or Canada?

Canada

PayPal is the easiest way to pay those invoices right now so I'd appreciate if people can donate via PayPal, I need a lot more than I'm getting right now

I can pay via eTransfers or a credit card - but I haven't received either of the new renewed credit cards in the mail due to some bureaucratic problem

and eTransfers are a real hassle

so I guess I could start withdrawing money from my bank account into PayPal

it would be nice if donations would cover these ongoing substantial costs though

in order to continue development I really need these costs covered

not getting enough donations recently

I also want to start paying other developers so they can spend more time on the project so the BTC will start being used up for that

Would you take venture capital money if someone could find a firm willing to 'invest'?

[(i.e. how Matrix.org raised some money last year)](matrix.org/blog/2019/10/10/new-vect…m-to-accelerate-matrix-riot-modular)

hello

Hello

after having found netflix.service, amazon.service amazon.apphandler facebook.manager and tons of analytics packages on my damned xiaomi, I decided to choose other. That's the short story why I am here

and I am pleased to find such a populated chan, wow

Welcome!

and, may I ask if the next release will support the pixel 4a ?

<Lallerz "and, may I ask if the next relea"> Yes. Yes you may ask.

Thanks

will the next release support the pixel 4a ?

you guys have an auto-updater for F-Droid? Or you always do them manually by clicking 'install' on each app?

<derpy "you guys have an auto-updater fo"> For auto update functionality you need the f-droid privileged extension (because that functionality requires system access). It s not included in GrapheneOS though.

Do people in this community generally use & trust it (the priviledged extension)?

* @strcat Would you take venture capital money if someone could find a firm willing to 'invest'?

<derpy "Do people in this community gene"> no it is not supported(due to blindly trusting 3rd party repos) and needing root

ok

will just click with the ol fingers for now :)

<Lallerz "will the next release support th"> That will probably take some time, since the phone is not even out yet and someone needs to step up to be the maintainer of the 4a

thanks for the reply

I've dug around a bit in the logs and didn't really find anything definitive, but: what are people's thoughts on using biometrics (particularly the fingerprint reader) ?

it seems like it's viewed favorably, but it seems like having that sort of data recorded would be a risk to the user

I assume that data is never transmitted at all, and should be hard to access by apps that aren't meant to access it?

lev[m]: The biometric data is stored in the Titan M security chip

stored fuzzy not evn google or grapheneos can reverse it

what about the hardware itself? would it be impossible to intercept data being reported from a 'read' ?

your camera would be a much easier method

I don't know if they are using encrypted memory or what(the SEP does for TouchID), but at some point the effort required to man in the middle the fingerprint sensor would be really high

is there a way to use only biometric and not have to use the pin or a password? Or can they only be used in tandem

just use a 4 digit PIN

if it is truly random it would take roughly 650 years to bruteforce

the fingerprint times out after 48 hours

good to know.

so making a fake in that time would prove challenging if it was stolen

or if you restart

sure

so if you're nabbed, restarting the phone is a good move

yes, especially for AFU avoid lockdown

Pixel 4 with IR scanner + a good length truly random PIN + practicing a fast restart is probably the ideal setup

shoulder surfing and CCTV are dead in the water since you don't enter your password often

it's also depends on when you restart though, to be fair

If my device is stolen and I couldn’t reboot. Is the data at risk ?

if you get picked up, and instantly restart, you'll probably turn your phone back on to look up a number unless you have your emergency contact memorized

at which point you'll definitely enter it in, while on camera

<atasuke[m] "If my device is stolen and I cou"> um, not really

the 48 hour timeout on biometrics is good enough

and AFU is tricky on GrapheneOS

Ok

people know they are going to have to deal with no usb attack vector and layers upon layers of hardening on iOS. On a Pixel that may come as a real shock to see you also have that here. Not to advocate security through obscurity at all, but yeah

emergency contact number on the lockscreen sounds like a wise move

Pixel with GrapheneOS is pretty tough

Dope

Just an idea, why isn’t there a way to wipe the phone after a number of failed password attempts ?

I really don't think that is a necessary

You can already junk a Pixel effectively by trying to unlock it too many times(a DOS basically) an iPhone has this feature since the timeouts are shorter(but the minimum PIN is far far longer)

so if you want for instance to use an iPhone with a 4 digit PIN

it is meant for a 6 digit PIN so it wouldn't be as strong as a Pixel 4 PIN vs 4 PIN

an iPhone with 4 digit PIN and the 10 tries makes some more sense there

there's a program on FDroid called Wrong PIN Shutdown which will turn off your device after X retries if that gives you some peace of mind

not recommended

oh no?

salbutamol: you have to register the app as a device admin which is not really good

device manager

and correction

the time out on Pixels is not as aggressive as I remember

it is pretty hard to disable the device

but still it is very strong

oic - what's the risk there, that the app could be shady / exploited?

Yes shady

yes

if it was exploited it would have full ownership of your profile

gotcha

huh, apparently pixel 4/xl are already out of stock, and not available from google any more

in general the iPhone system is not as refined. Requires 6 digit PINs(which are long, but less likely to be easily guessed), shorter timeouts(which can be nice), but the wipe after failed attempts only make sense if you have a bad PIN imo

it opens you up to more damage if someone wipes your phone

than expecting someone to guess your nigh unbreakable PIN(on either phone)

if someone did bypass the hardware timer

they would bypass the wipe limit too

Does Graphene have a pin scramble feature? I haven't seen this mentioned anywhere.

though a hardware timer bypass is extremely unlikely

<echotunnelriver[ "Does Graphene have a pin scrambl"> it does

basically if you PIN is 1234 iPhone will protect you by at least making it longer. People don't really carry 6 digit easily guessable combos in their head like SSN, birthday(you could add year though), and years like 1787. iPhones with the wipe after 10(optional) makes it way more appealing if you have a really bad PIN

Pixels on the other hand the 4 digit PIN makes more sense if you have it fully random it will be very strong and you don't need to worry about data loss and on top of it the PIN is shorter

> Does Graphene have a pin scramble feature? I haven't seen this mentioned anywhere.

Do you mean rearranging the keypad?

Yeah, it's in the settings, somewhere

<cn3m[m] "in general the iPhone system is "> iPhone doesn’t require 6 pin

I mean you can set it to 4 if you customize it

but the default PIN is set to 6

nickcalyx[m]: Under Security

Hey! I'm female 23 and I'm so horny right now. Wanna trade pics with cute man. Add me here >> NUDY.FUN << :

Lmao

I know there are no deadlines / don't want to pressure anyone but what's the current state for android 11

Not that I really care to be fair it hasn't added anything relevant to us

But still

Kernel is the current goal

Pixel 2 is done

Pixel 3 is development

then I believe after the kernels are done a release on Android 10 will be out to test the new kernels

Hey! I'm female 23 and I'm so horny right now. Wanna trade pics with cute man. Add me here >> NUDY.FUN << :

rofl

what minimal effort

(re: now deleted spam, not the comments about testing the new kernel)

bait 10/10

clap

I genuinely pity anyone who would click on that

Pity me pls

you poor sad man

davx5.com/tested-with jeez they should at least recommend some top ones they know function well... paradox of choice!

just spent over an hour trying to move a damn address book... I don't see how this could possibly be a recommended app; such a waste of time.

Is there an android function where you can import / export just the address book to grapheneOS?

DAVx5 is way overcomplicated

FastMail works flawlessly. It's not complicated. Anyways, is off topic, my man.

"best way to migrate contacts to GOS" is off topic?

ok

Type all the numbers in individually if you can't figure it out.

These sorts of questions shouldn't be asked here. It's an internet search away.

How difficult is it to just make a fucking csv file of your contacts and import them into Android?

Or a vCard

derpy: I like etesync.com

jpds tnx

Hey! I'm female 23 and I'm so horny right now. Wanna trade pics with cute man. Add me here >> NUDY.FUN << :

Yes, I'll add you.

Jesus Christ lol

Again

is she like the 23rd female in her line of genetically engineered chatbots?

or is her first name "female" and last name "23"

Is it offtopic to ask about the phone app... I have a SIM and also a SIP account. It is supposed to ask first, but it does not ask and just defaults to the SIM.

Also, every time bluetooth disconnected I have to repair - it never remembers... Is this a known issue?

got the call selecting working

nice

is this with the stock dialer? I was thinking about looking at others, for no particular reason

Hey I heard that the next update will force some people to do a factory reset ???

Please tell me it’s not true

adeus[m]: No

Last time I bought a device with the hopes of putting a custom OS on it, the bootloader was locked and the radio was not supported. I just want to buy something that will definitely work with GrapheneOS.

(I bought a Galaxy Nexus. Little did I know, it’s a different piece of hardware when you get it from Verizon, and few ROMs supported it.)

> Hey I heard that the next update will force some people to do a factory reset ???

Where did you hear that

It depends on what version you first flashed the OS and if you factory reset after some update

only people who installed GrapheneOS before it was called GrapheneOS

and before the first Android Hardening stable release

i.e. people who installed before grapheneos.org/releases#2019.03.05.03

I was very clear about that

KE0VVT: its still the same, dong buy a Verizon Pixel as the bootloader can not be unlocked

*dont buy a