<jneplokh "As stated, use the Network permi"> I've been doing both, should I not be doing it that way?

I don't see why you should use both

I was doing it that way so I could use NetGuard to block system things/apps and NetGuard plus system permissions to block normal apps for double insurance that they were being blocked so to speak

If I shouldn't be doing it that way, like if it's an actual bad thing that I am or something, then I'd change it

devs, for the kernel patches are we still using R-Preview 4? <android.googlesource.com/kernel/msm…/android-msm-coral-4.14-r-preview-4>

entry1: they all are, but they need to be unlocked and that is beyond the scope of the project. the only model you should avoid, is buying an unlocked Verizon Pixel 3a

you can read more on <grapheneos.org/install#prerequisites>

here is the info on Verizon that you can browser in the logs <freenode.logbot.info/?ch=grapheneos&q=verizon>

the fullproof way to avoid that issue is getting the phone from google or retailer, by from the secondary market is a hit or miss

* the fullproof way to avoid that issue is getting the phone from google or retailer, buying from the secondary market is a hit or miss

carriers usually have a lot of restrictions on unlocking devices too

i know everyone doesn't have the luxury of buying a new device

but thats unforunately what it comes down too

you're welcome, happy hunting

<entry1[m] "Sorry to bump again. Would Googl"> You can do that yourself on the repair page.

0xC0ncord: the repair page tells you that?

<aeonsolution[m] "0xC0ncord: the repair page tells"> store.google.com/us/repair

IMEI or S/N in that box and it tells you the model.

it can tell you if a phone is carrier variant?

<aeonsolution[m] "it can tell you if a phone is ca"> Yes. Here's mine:

nice, i did not know that

thank you for the share

It will say "Unlocked" or "Verizon"

<entry1[m] "0x UnlockedC0ncord Unlocked is "> Correct

Just finished installing GOS on my Pixel 4. Given the information I've been seeing recently of faults with F-Droid, does anyone here have other package managers / app stores to recommend? I saw someone mentioned Aurora.

Aurora Droid is nice, gives you the option to use many non F-droid repositories

entry1: I would use the F-Droid app for some package management on my previous device. I only used the website to download the F-Droid apk.

entry1: My understanding is that they aren't very timely in publishing updates for apps in the store and have apps that are targeted for old versions of Android but can still be installed on a device that has newer software which can be a security risk. Is that different on the website? I would find that a bit odd.

I have a question guys...What the hell is a Windows secure core PC?

izymandias[m]: have you read the microsoft marketing material?

the laptops sold under this branding goes thru a vigorous certification program with Microsoft

renlord: is it just laptops?

izymandias[m]: yep, just laptops only

will this be coming to PC's?

izymandias[m]: no and my guess is that it would be impossible

unless you happy to buy integrated builds with PCs

hey renlord, are you helping with the kernel patches for Android 11 by any chance

aeonsolution[m]: no

kk thanks

anyone know if there are actually apps that break if sensors permission was revoked?

besides google maps

or other maps that provide navigational assitance.

renlord: will it be coming to PC's?

izymandias[m]: no

never desktop PCs

not in its current state/form

could possibly come to those dell workstations, but definitely not enthusiast builds

renlord: are they going to get more secure?

izymandias[m]: i dont want to speculate on desktop pc security and it is offtopic in this channel

lets end on the fact that is less secure than mobile OSes

renlord: that sucks

it is hard to secure flexibility.

Hello, I have previously been able to build Vanadium and GrapheneOS many times successfully but it appears for the last 1-2 weeks the Vanadium build is broken. I came here last week and was told the Vanadium build was broken but it's a problem with upstream. Today strcat told me Vanadium build is not broken and hasn't been.

I'm compiling with python 2.7.13 as it was suggested to make sure its python 2 . After running "ninja -C out/Default/ trichrome_webview_64_32_apk trichrome_chrome_64_32_bundle trichrome_library_64_32_apk " it gets to step 78838/82828... then crashes:

grindlefang[m]: logs?

ld.lld: error: undefined symbol: content::CrossOriginEmbedderPolicyReporter::CrossOriginEmbedderPolicyReporter(content::StoragePartition*, GURL const&, base::Optional<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > const&, base::Optional<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > const&)

I've posted a longer snippet of my log here: pastebin.com/mfxu10vV

renlord: another question. Is the game valorant safe to play?

izymandias[m]: dont know

<izymandias[m] "renlord: another question. Is th"> No, their anticheat is basically glorified spyware

TIL ^

lulz

It also broke a ton of people's computers because of how deeply embedded it is into the system and it had a few problems

i dont know how else can anticheat works besides spying on you

faxing: is it different from other epics and steams anticheat?

renlord I tried to take a look at build changes to Vanadium or the grapheneos build page but it didn't seem there was anything major and I am following the build guide commands

Anonymously collecting open processes and comparing them and their function to a list of known cheat software without keeping logs

That's how you build an anticheat that doesn't spy on you

fuck this matrix bridge

strcat: take a look at my above messages about Vanadium build problems when you have a chance cheers

<izymandias[m] "faxing: is it different from oth"> VAC is complicated and not something I'm familiar enough with, though from my knowledge it is much less invasive. Epic doesn't really have an antichat per say, but they do use EAC (Easy Anti Cheat) for their games like Fortnite

grindlefang: there isn't any problems with Vanadium builds

grindlefang[m]: what are your gn args configs

Sure all post my args.gn one sec

I'll*

But their isn't truly a platform wide anticheat developed in house for Epic like Steam has

* But theirs isn't truly a platform wide anticheat developed in house for Epic like Steam has

enable_remoting (or was it reporting, check vanadium args)

post the errors in the chat and let us help you out, no need to ping strcat for things the chat can help with

I did post the error in chat

faxing: so Epic games' anticheat is spyware too?

I changed enable_reporting = false

pls take the anticheat discussion offline

it is off-topic

Because I saw the comment in Vanadium args.gn about the build being broken and it was breaking with a different error before

I'm building on ubuntu . I can still build GrapheneOS just not Vanadium since a couple weeks ago

you're probably missing dependencies that aren't listed in the building instructions

can you show the error you're getting

Just to clarify... changing "enable_reporting = false" was a good move right? I can change it back and build again to show you the other error it was giving me when it was set to true, if that helps

either or should work, what is breaking ninja is probably missing dependencies

grindlefang[m]: when you changed enable_repoting = false

did some stuff rebuild?

or it proceeded to link anyways?

have you tried a clean build again when you changed

I just did a clean build no . Setup a fresh environment, synced the code from scratch, and built from scratch with enable_reporting = false

now*

faxing: valorant isnt on epic games. Its riot games

What OS / environments are you guys building on ?

Ubuntu 20.04

no problems

I just don't understand why a dependency issue would cause that specific error in the Chromium source to manifest itself

ninja uses python

<overheadscallop[ "Ubuntu 20.04"> you're building vanadium from source?

yes, clean build syncing to latest stable 84.0.4147.89

<izymandias[m] "faxing: valorant isnt on epic ga"> I didn't say Valorant was on Epic Games?

I'm aware that it's on Riot Games

grindlefang: can you try starting over, i'll be here if you have questions

faxing: sorry just confused. are you saying epic games' anticheat is spyware like valorants?

izymandias[m]: faxing[m]: pls take it offline

ffs

Sure.. I'm going to try on debian buster

is running

build/install-build-deps-android.sh

gclient runhooks

Still necessary to install chromium build dependencies? I've been doign that and it seems to be working fine but wondering if that could be interfering with things

yes, some of those tools are used to complete the build

its just safer to have it even if its not all used

Ok

because figuring out whats missing wastes so much time

it would be amazing if there was a grapheneos dockerfile. I think that could seriously help development

Anyways thanks for your help so far guys I'll tinker around and let you know if I have any other questions

One last question: is deleting the out/ directory enough for a new clean Vanadium build? Don't want to have to delete the whole src dir and download the source again

just delete the out/Default if your ninja build added stuff in there

everything else can stay

Cool, thanks

you didn't edit any other files or directs under src/ right?

Nope

* [correction] you didn't edit any other files or directories under src/ right?

yeah, just delete out/Default

i have a dockerfile

but i dislike using docker

im gonna use systemd nspawn instead

it does funny things with my network

its shit ass with ipv6

always causes intermittent network failures

👍️

renlord: are you able to post it? It could be helpful in setting up a build env for devs or sorting out dependencies issues like mine

im testing the latest version for vanadium

are you still having issues

Yeah just doing another build now on debian buster

<izymandias[m] "faxing: sorry just confused. are"> Epic Games doesn't really have an anticheat like I said. It's just that their top games (i.e. Fortnite) use EasyAntiCheat (EAC), but that is not "Epic Games' Anticheat" as much as it is just an anticheat that they make use of for some of their more popular titles

Also it's still very invasive but not to the extent of Valorant's

zzz

3-strikes, you have been asked to cease offtopic discussions.

faxing: stop talking about anti cheat man

it's off topic you got told

faxing: Just private message or take it to #freenode_#grapheneos-offtopic:matrix.org

are they still spamming the matrix side?

faxing: thanks for responding anyway. i didnt know either

how comes graphene doesnt use Face ID? is it lacking the camera or is Face ID insecure?

izymandias: we need more developers to work on these features, please feel to help out

<izymandias[m] "how comes graphene doesnt use Fa"> you mean it is not working on your Pixel 4?

With regards to US law, Face ID and fingerprinting is insecure as those can be subpoenaed, to the best of my knowledge.

<switchdominion[m "With regards to US law, Face ID "> on the other hand bio-metrics pretty much kill shoulder surfing and

From what I've read about Face ID and facial recognition software in general, there are false positives that could allow someone to access your device.

switchdominion: Oooo I see. so the technology itself isnt insecure, its just that the government can force you to unlock your device with your face

<cn3m[m] "on the other hand bio-metrics pr"> Agreed. It all depends on which attack vectors an individual is most susceptible.

yeah face is especially strong(with require attention)

since someone can't do it when you are sleeping

<izymandias[m] "switchdominion: Oooo I see. so t"> With fingerprinting, yes. But when I tested out Face ID, which was years ago, granted, I was able to access another persons device using my face.

switchdominion: o really. was that on an android or IOS?

<izymandias[m] "switchdominion: o really. was th"> It was on Android. LG Stylo 2 or 3, if I recall correctly.

Granted, my experience and research with Face ID is likely outdated.

Yeah FaceID is far far stronger

and Pixel 4 got a great patch

I think it is just as good now

does it work with a mask on?

hehe

does the Pixel 4's match IOS's ?

<cn3m[m] "Yeah FaceID is far far stronger"> That's good. Though I would still warn those in certain countries that allow a subpoena, such as the US, for biometrics to use them based on their need.

is it the same tech. infrared?

izymandias: Yeah, iirc you can even use the infrared camera for photos

at the data center where I have my servers, I have to do finger print and then later face scanning, as well as rfid, and talk to a person, then rfid again and rfid a third time and then a combination lock

its quite the security theater

Trusted Face in Android is not nearly as good

oh and I understand they now put another rfid check in the elevator, so it will be 4 rfid checks

nickcalyx: xD

This is why i don't even record biometrics

Knull: why?

The subpoenas. Id rather my device not even have that information in the first place

<Knull[m] "The subpoenas. Id rather my devi"> it is stored fuzzed in the Titan or SEP

they are fine

Access should strictly be what you know unless combined with what you have. Not just 'what you have '

cn3m:

Password or two factor

* cn3m: are there whitepages on the Titan?

* cn3m: Are there whitepages on the Titan?

<switchdominion[m "cn3m: "> reddit.com/r/GrapheneOS/comments/hf…he_titan_m_chip_actually_do/fw8kr29 this is all I found

someone who takes your phone can hold it up to your face or press it to your finger

Knull: why not just enable password in the moment if such a situation was to arise?

xkcd.com/538 nickcalyx:

<nickcalyx[m] "someone who takes your phone can"> Exactly. That's why you don't only use that if possible

cn3m: let me guess, that's the one about beating them with the $5 wrench ?

between this and shoulder surfing

:)

biometrics have some notable advantages

If face scan unlocked a pin screen that you still need to enter, great. Face alone, no

Is it possible to set two factor in grapheme rn?

Knull: can that not be enabled?

Knull: the goal is you never put in your password in public

<broda721[m] "Is it possible to set two factor"> not at this point

Or have a complex enough password that a simple shoulder surf cant remember

could be recorded

<cn3m[m] "reddit.com/r/Graphen"> I read a bit of that earlier and I'll take a closer look now. Mostly I was wondering what you meant by Face ID and/or biometrics being "stored fuzzed in the Titan or SEP."

Recorded though? Probably a little outside most ppl's threat models

grindlefang[m]: i have no issues building

if you must have a dockerfile -- this is a crude one i use. 0bin.net/paste/m+cgxaCcAOsSy4x8#fXN…YF3GQNiBp1wJr9CW7JWRs1fJJra-yYoypES

you need to update args.gn and resync

run the docker container interatively with a shell and then follow the instructions on grapheneos.org

<Knull[m] "Recorded though? Probably a litt"> switchdominion: Here is what Apple says(they say roughly the same on FaceID)

Anything iPhone/Pixel Finger/Face is good

That's great, paired with a pin/ password

In the two -factor model, even if recorded, they need your finger

it is very easy to lockdown the device to not accept biometrics

I just tried on debian buster again and its failing at the same spot complainging about CrossOriginEmbedderPolicyReporter

I think the advantages outweigh the drawbacks

they time out too

And the other way around.. maybe they got ur cold dead finger, but dont know your pin

Pixel is 48 hours for example

to fake biometrics it could take a while

<renlord "grindlefang: i have no issues bu"> renlord: your docker file is pointing to a much older version of chromium.

In general biometrics are very smartly designed on iPhone/Pixel

grindlefang[m]: ya, just do the gclient sync step iteractively

the container image is not bound to wtv chromium version you're building

<faxing[m] "I didn't know you could have it "> you can't

You cant that i know of, my point is biometric is only good paired with a password. If i had to choose 1, its a pin

`docker run -v vanadium-path:/vanadium -it image /bin/bash`

Sorry im confusing ppl

<Knull[m] "You cant that i know of, my poin"> alphanumeric password + face recognition is likely the best

Yes

can't easily be fooled(can't at all without preplanning). Easily locked

grindlefang[m]: you might just want to reclone depot tools

and try again

between my old chromium build and this most recent one, depot_tools was completely broken

I would recommend biometrics for most people. My password has been recorded a few times thinking back

Also that ubuntu 18 only ubuntu 20 is officially supported? I just tried from debian stretch and buster but no go... which is supposed to be officially supported. I'll try from ubuntu 18.04 now like the dockerfile

Maybe something that will come unique to graphene

I'm doing a clean build everytimerenlord:

depot_tools is separate

isnt law enforcement allowed to force you to give up your fingerprint though?

<cn3m[m] "I would recommend biometrics for"> between the long encryption password, reasonable timeouts, safe storage, and quicking locking out biometrics you have far less to worry about.

> <@cn3m:privacytools.io> I would recommend biometrics for most people. My password has been recorded a few times thinking back

* between the long encryption password, reasonable timeouts, safe storage, and quickly* locking out biometrics you have far less to worry about.

Yes, fresh build environment

grindlefang[m]: chromium.googlesource.com/chromium/…/docs/android_build_instructions.md

<LinusSexTips[m] "isnt law enforcement allowed to "> Depends. In the US that is a maybe, currently it is leaning no. That is not set in stone

Just lockdown your phone or ideally reboot

it is qucik

do it before bed and in any situation you might have your phone taken

No fingerprint reader on 4xl it seems though 😕

cn3m: that is a very bad recommendation. fingerprints do not have anywhere near the same level of security or legal rights as a password. You can clone artifical fingers that bypass fingerprint scanners using high-resolution photos of a hand

<grindlefang[m] "cn3m: that is a very bad recomme"> I said facial recognition. Fingerprinting is legacy tech at this point

ok just replace fingerprints with biometrics what i said still stands

fingerprint you can still lock out and it is very effective against recording or shoulder surfing

I've seen videos of people recording their interaction with police only for their phones to be snatched out of their hands suddenly. Then i wonder how many were actually snatched and the footage deleted. if graphene had a feature that could use video recording while the phone was in lock or is put lock once the phone is snatched would be awesome.

<grindlefang[m] "ok just replace fingerprints wit"> someone has to do it before the time out

that is some serious commitment

not really... in most emergency or high-stress situations people are often on their phones to call for help or let their loved ones know what is going on

you're basing your security on the hope your timer runs out... seems risky

Well they could just wait for an AFU exploit and see how long they can keep your phone alive

GrapheneOS and iOS both have very robust protections against this, but not perfect ofc

<izymandias[m] "I've seen videos of people recor"> Interesting idea for physical record button, once released, phone locks, recording keeps running

you really should reboot if you think you will lose access to your phone

again... you're deflecting the securtity of biometrics

<Knull[m] "Interesting idea for physical re"> this could be done from the lock screen with public key cryptography

depending on your threat model and environment, you can alter your op sec

<izymandias[m] "I've seen videos of people recor"> cant you access the camera from the lockscreen via a setting?

<grindlefang[m] "again... you're deflecting the s"> you are deflecting the insecurity of having your password recorded as you put it in

you are also taking longer to access your phone with that long password

or using a PIN and putting a lot of faith into the hardware timer(which yeah the device will brick more than likely)

there is no one answer

<cn3m[m] "or using a PIN and putting a lot"> Isn't the hardware timer for a 4-digit pin upwards to over a century?

<switchdominion[m "Isn't the hardware timer for a 4"> 650 years, though there could always be a flaw

Two factor is the answer, lol

it is very unlikely

<Knull[m] "Two factor is the answer, lol"> yes password with pin+bio as the 2fa is decent

but still doesn't account for AFU attacks so still just reboot

will graphene ever have the option for bio+pin?

> <@knull:matrix.org> Two factor is the answer, lol

* yes password with pin+bio as the 2fa is decently ideal

Hopes and prayers, Linus, hopes and payers

<LinusSexTips[m] "will graphene ever have the opti"> yes, probably. What I heard it might be ideal to wait until fingerprint dies

yeah rip no facial recog on 3a

someone just needs to add it

<LinusSexTips[m] "yeah rip no facial recog on 3a"> unfortunately 4a looks like it won't since holepunch

Knull: dont think you would even need a physical button. maybe have a mode in the camera that requires you to have your finger on the record button and is locked once released. and have a feature that allows you to start recording again if you were to accidently release the finger from the screen. dont know how it would be done

<cn3m[m] "650 years, though there could al"> Specifically, I'm referring to brute forcing a pin with a Titan M. What flaw might you be referring to?

<switchdominion[m "Specifically, I'm referring to b"> It is not outside the realm of possibility for their to be a flaw in the hardware timer

it is a hardware system that is designed to brick if tampered

youtube.com/watch?v=7UNeUT_sRos here is a good talk on an old version of the SEP. These are just systems they could have flaws of course

<cn3m[m] "It is not outside the realm of p"> Of course. That is probably why Google has a $1.5 million bounty for anyone that can find a bug in the Titan M.

isn't it $1 million?

it is 1mil

1.5mil are android RCE bugs

basically 1.5mil CAD by this point lol

paid by some security firm that i cant remember the name of

yeah, though this could be exploited any time after they obtain it

I've seen 1-1.5 from different articles

<renlord "paid by some security firm that "> gray market?

it is $250k to Google iirc

from*

for kernel control with POC

2.5mil for android fcp zero click

The top prize is for a “full chain remote code execution exploit with persistence” of the dedicated security chip. On top of that, there’s an additional 50 percent bonus if a security researcher is able to find an exploit on specific developer preview versions of Android, resulting in a potential prize of $1.5 million.

renlord: I rather take the $250k

the one i recall is not zerodium though

but man, so many people paying top dollars

to think so few people actually have a phone you need a zero day for

Any iPhone in the last 7 years, Samsung Galaxy S series for the past 3 years(the 4th doesn't count as it is quarterlies), Any Pixel in the past 3 years. Not even a quarter of phones

does anyone know the reasoning behind migrating the kernel patches to R-Preview-4 instead of R-Beta-2?

i got the answer everyone, thank you for reading my gripes lol

<aeonsolution[m] "i got the answer everyone, thank"> What is the answer if you don't mind?

since the commits can be rebased using git, it is not as important where you start because you can add missing commits later

but its not an excuse to be sloppy either

the order of the commits still need to make sense

renlord: do you have the full list of commands you're using for Vanadium? The build guide is a little ambiguous . I'm still getting the same error. Just to clarify as well... enable_reporting = true ? Because that is not mentioned in build guide but seems to be a necessary temporary workaround

Am i blind or there's really no headphone Jack on pixel?

<Knull[m] "Am i blind or there's really no "> Only on the pixel 3a

Whats this world coming to

digital world and the end of analog world

Long live the headphone jack

i love my focal headphone, i can use Bluetooth and Jack on it

but i get let output with jack because of impedance

g65434-2: for me the jack any day

Even LDAC for some of my files hardly comes close

but do you keep charging those old jack headsets or just don't use noise canceling?

I have a phone that still does analog

Noise cancelling not so much

grindlefang[m]: yeah you need to enable reporting check the vanadium args.gn

Need to file an upstream bug about this and check on master

I'm having an issue with the camera. Most of the time the button is greyed out and it won't take a picture. I can eventually take one if I close the app and reopen a bunch of times. Then sometimes I'll press the button and it will take up to 10 seconds to actually take the picture. Is this a known issue? I'm pretty sure it just started recently

Does anyone have experience using WhatsApp on GrapheneOS? I know it works, just wondering about notifications though

Reading some conflicting information. Some say you don't get notifications, some they're iffy and some say you do

grindlefang[m]: following the build guide verbatim is sufficient

with the docker image

didnt need `enable_reporting = true`, mine was set to false

and enable_remoting = false too

Good day all, could anybody give me some assistance in sorting out my remote verification ? I keep on getting emails stating that the attestation has failed

it work fine testingtesting12

<testingtesting12 "Does anyone have experience usin"> The only thing you dont get is google drive backups but you probably don't want those if youre considering installing grapheneos because theyre not encrypted.

Has anyone had any trouble with sending files over Bluetooth?

<dreth[m] "The only thing you dont get is g"> Don't the notifications on Whatsapp use Google's push notifications service?

I did see fosdem.org/2020/schedule/event/dip_openpush recently but I don't know the current status of the project.

I have WhatsApp in a separate user profile

And I still get notifications despite just getting it from the Aurora Atore.

* And I still get notifications despite just getting it from the Aurora Store

renlord: I'm not sure what you're building from then, the default args.gn has enable_reporting = true github.com/GrapheneOS/Vanadium/blob/10/args.gn#L27 t . I have built with enable_reporting = false and It's giving me the same error.

I'm following the vanadium build guide and chromium build guide verbatim and it's not working, I've tried on debian stretch, debian buster and ubuntu 18. Seems strange also it only suddenly happened about 1-2 weeks ago. I'll keep investigating...

The fact it is complaining about the same lines every time seems a little weird too.

ld.lld: error: undefined symbol: content::CrossOriginEmbedderPolicyReporter::CrossOriginEmbedderPolicyReporter(content::StoragePartition*, GURL const&, base::Optional<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > const&, base::Optional<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > const&

nick demonMachina

Close....Jake.

The grapheneos vanadium build instructions are really ambiguous as well.. it just links to chroimiums android build instructions for fetching dependencies, telling you to get dependecies before syncing.. but the chromium page says you should sync before fetching dependencies

renlord: your dockerfile had a lot of unnecessary steps in it as well for example calling install-build-deps.sh before calling install-build-deps-android.sh even tho install-build-deps-android.sh calls install-build-deps, and apt installing the same packages multiple times. However I'll try to use that as a base for an environment and hopefully I can guess the right commands needed to build Vanadium

<grindlefang[m] "The grapheneos vanadium build in"> Vanadium is just Chromium with hardening patches, strcat adapted the build rules for Vanadium development. In general, external links are for reference material. Not for steps to follow as part of the install.

There are a lot of steps it so it does feel overwhelming at first but I can gurantee you the steps there will help you succesfully build Vanadium.

Anything from the Chromium page is just for reference. If you want to dive into that and see how it relates to how Vanadium gets built for GrapheneOS, you should definitely jump in. It'll definitely help you with development.

Why is my terminal sayingfastboot is too old?

What instructions did you follow interceptingfist?

I'm on 30.0.3

Hated one

But he didn't explain the flash all part

He only mentioned how to flash all on windows

As a general rule, don't use instructions that aren't from the Official Website <grapheneos.org>.

I'm also using thosr

They are already pulled up

Right, but if someone else gives you directions that don't verbatim stick to these instructions. You'll get that error.

<aeonsolution[m] "Vanadium is just Chromium with h"> I have built Vanadium many many times. It's not that the instructions are overwhelming.. .it's that they are incomplete and ambiguous

No,sometimes it's easier to see the process

interceptingfist: freenode.logbot.info/?ch=grapheneos&q=fastboot

In the logs, you'll see that error you get is always from people watching videos.

renlord: Judging from what you said about enable_reporting seems you are building from QQ3A.200705.002.2020.07.06.20 and not the 10 branch which is the latest

Let's try to figure it outinterceptingfist. Close all your windows, and start from step 1.

You can see this is the previous version of chromium "83.0.4103.106" which was also building fine for me

We'll narrow down the issue from there.

I can see also there is a lot of active development under the 10 branch in the last week that is not in the tagged version

grindlefang: the issue are the packages with Ubuntu not so much that the instructions

if you have successfully built Vanadium and have suggestions to improve the install process, please make a pull request

<aeonsolution[m] "grindlefang: the issue are the p"> Yeah.. I have built on debian buster, sid and ubuntu and all are giving the same error. I used the same dependencies mentioned

I am, the build is broken

we don't have enough people building Vanadium on Ubuntu and Debian to lend their insight

most of us use Arch based OSes

Ubuntu and Debian are supposed to be officially supported

Arch is not

Arch gives us the packages to avoid the problems you are having with dependencies

Well then looks like the build instructions are incorrect

If they say to use debian and ubuntu not arch

who is they?

The build instructions friend

Arch is the first one

?

Right, and ubuntu and debian are next

the devs that work on GOS and Vanadium use Arch

if you have suggestions to improve Ubuntu and Debian development

please create a pull request

It doesn't build on officially supported environment and builds, I would suggest that is a problem with your build instructions not the developer ;)

Debian and Ubuntu are supported by Google to do Android testing

and development

I will setup a new environment in arch to build Vanadium and GrapheneOS, altho AOSP does not support arch

switchdominion: entry1 for apps and appstores (and even app repos) have a look at hub.libranet.de/wiki/graphene-os/wiki/Apps

you need to figure out the dependencies to build Vanadium and if you have suggestions to improve the process please make a pull request

Nothing mentions the error that see

Thanks though

Also.. I am starting to doubt it's a dependency issue as there are no complaints when installing the dependencies and it manages to get 95% build complete and complains about the same CrossOrigin error on all 3 OSes

If only grapheme could make a install video

interceptingfist: freenode.logbot.info/?q=fastboot+out+of+date&ch=grapheneos

<interceptingfist "If only grapheme could make a in"> What OS are you trying to install from?

I found one that worked perfectly for me

Using Ubuntu

Well that's a little dismissive, like I said your build guide is broken and I have "figured it out" many many times before with identical set of commands that built Vanadium. The 10 branch is broken and significantly different than the QQ3A.200705 version of Vanadium

Linux pop

I'm platform tools was downloaded from google lmao

It's not out of date

I also have a windows machine going to try it

That's what I used

Should be fine on Pop!_OS

grindlefang: I can't help diagnose and issue on a distro, I don't use. The advice I am offering is based on my previous experiences building Vanadium. I was trying to led you to that understanding. I'm not being dismissive.

interceptingfist: did you set up your environment variables correctly?

if you close powershell, the path to fastboot gets lost

I don't think I closed it

what command step are you on?

Where you do flash all

ok, lets start from the beginning, let me pull the instructions

open a new powershell window

Terminal is new

I'm on 3a

`cd .\Downloads\`

after that run the curl command

for windows

i know we are doing it all over, but its to help find the issue

working backwards from the last step doesn't always work

because i don't know what changes accidentally/intentionally were made

Ok

cool when that is done

we need to set the path the platform-tools so run `$env:Path = "$pwd\platform-tools;$env:Path"` afterwards

then run `fastboot --version afterwards` to check if your path is set to fastboot

* [correction] then run `fastboot --version afterwards` to check if your path is set to find fastboot

if your phone is OEM unlocked, you can then unlock the bootloader

by running: `fastboot flashing unlock`

using the same powershell window

make sure you are booted in the bootlader

Ok

since you already downloaded the images

I'm step by stepping the instructions for linux

?

aren't you on window

I'm trying to get either one to flash

thats a really important detail to leave out

Well neither does anything for the flash part

leaving your shell or powershell untouched

please move the factory images

I'm on the Linux right now 1 minute left on the dl

oh ok, you are downloading the images again

are you using a USB A to USB C cable?

C

Yea a to c

nice, did you download and unzip the images already

Unzipping

Yep

All that's left is flash command

cool run `./flash-all.sh` afterwards, make sure the phone is plugged in and that you are in the bootloader still

use the USB port closest to the motherboard

No such fi

is it flashing?

No

And this riot froze up on me lol

nice

ok, what are you trying to do now

Trying to make sure its all connected

And just try one more time I guess

you changed the directory to the sargo right

Ya

kk

yeah run the flash script

hopefully now you dont get fastboot error

Here's this for if you get other common errors related to Linux

if you close the shell, your path gets reset so the fastboot commands wont work until you update your path again just fyi

Redownloading it

When I do export path it doesn't show anything

why did you run export path again?

do you still have the shell we used for the initial steps active?

if you do, use that shell to run the commands

the steps are setup in a way where you can do everything in one shell

if you use different shells, the paths will not match up

I'm started over from scratch

kk

you're almost there

i think we figured out that issue

fastboot problems are usually path problems

or downloading third part stuff not in the instructions

party*

It still says nonsuch directoru

No such directory

I don't understand why it fails to try to flash

lets do this

cd $HOME/Downloads

then run ls

you should see platform-tools and the factory-images(unzipped) and the factory-images(zipped)

if you don't then you had the paths wrongs when you switched to Linux without mentioning it to me

if you do see all this

use the fastboot --version command

and see if you path is still up to date

if it is not

run `export PATH="$PWD/platform-tools:$PATH"`

and the try fastboot again

if you get the correct version as a response

now change into the unzipped directory

and run ls

you should see the flash-all scripts

if you directories you move into should be the sargo one

not the one in the examples on the website

* [correction] the directory you move into should be the sargo one for the pixel 3a

<aeonsolution[m] "cd $HOME/Downloads"> Nothing happens

Nvm

I hit wrong letter

progress is progress, you are almost there

I'm on downloads directory bit its waiting forna command

Its not showing me anything after downloads

thats because the files didnt get downloaded there

you downloaded them somewhere else

wait did you run `ls`

if there is nothing there

you need to do the steps all over again

and do all the commands using that shell you are using

dont open new ones

<LinusSexTips[m] "invidio.us/watch?v=o"> This video is the way the truth and the life

<aeonsolution[m] "thats because the files didnt ge"> Thanks for you help

did you get it up and running

Yea mann

:)

awesome, persistence pays off

Yea

Do you use a VPN?

i do, but im not using GOS as a personal phone right now, its just testing and development stuff for now; you can ask the group for specifics on that if you're curious

the logs might have gold in there too

<interceptingfist "Do you use a VPN?"> if you install f-droid there are a couple of free VPN's.. riseup VPN and calyx VPN

some people use orbot as a vpn too, to push traffic over Tor

the problem with Tor though is it only handles tcp but not udp

<nickcalyx[m] "the problem with Tor though is i"> Thanks

Did you know that getting the same app from @fdroidorg instead of Google Play can mean it won't track you? twitter.com/t_grote/status/1279779673128534016

Right, I've "fixed" the 90hz flickering on my device. I used adb.

I've basically forced the display to always be at 60hz

adb shell settings put system peak_refresh_rate 60

adb shell settings put system min_refresh_rate 60

I wonder if an app could be made for that? I know nothing about Android development (or any type of dev work for that matter), but it doesn't seem like too much of a "challenge" to make an app that could toggle those settings, using adb? I dunno. Just a thought!

Rebooted and the adb command is persistent, yay. I can't tell you how much this has made me happy lol

I never understood the 90hz thing, it seems silly IMO

It does look smoother when scrolling through the UI and whatnot, but it isn't a game changer

Well, maybe for games

<SchismXL[m] "It does look smoother when scrol"> A little smoother*

Good evening.

Brilliant project.

Might I ask: What difficulties prevent other ROMs from allowing the bootloader to be relocked, as is the case with GrapheneOS?

Secondly, if there were to be an implementation rootless theming along the lines of Android 8 (requiring ADB), would this pose any security risk?

<mrsenshi[m] "Might I ask: What difficulties p"> hardware and interest. Pixels and OnePlus(OP has had a rocky history at best) devices support it across the line. Most roms don't support it on Pixels or OP since lack of interest largely due to people wanting to root(which breaks it).

<mrsenshi[m] "Secondly, if there were to be an"> ADB is not recommended for security reasons

<SchismXL[m] "It does look smoother when scrol"> It reminds me of that scene in 'this is spinal tap'. . But this one.goes to 11 !!!

Hey im trying to install graphenos on my second pixel and i get this error:

I got this error with my first pixel and someone just told a code

and it fixed it

But i dont know any coding someone who might knows

I have the latest fastboot

Are you following the official guide?

and you should be using powershell

Mind private messaging me?

I'll pay u for helping me out im not that techy

helpimaloser: you are not flashing correctly

you have not installed fastboot yet

Sup guys

Got my first install of graphene on pixel 3 thru

theres lot under the surface in terms of features but wondering the similarity and lack of interactive privacy features

similarity to android 10

and some system apps remainin even though most removed