<coomerhead:telegram> send graphene homeserver signup (re @GrapheneOSBridgeBot: <strcat:grapheneos.org> I strongly recommend using a different Matrix server than that)

<strcat:grapheneos.org> the grapheneos.org one is for mods/devs and former mods/devs

<madaidan:telegram> $100 CAD per message (re @coomerhead: send graphene homeserver signup)

<leeya:kde.org> > <@grapheneosbridge:grapheneos.org> <madaidan:telegram> $100 CAD per message (re @coomerhead: send graphene homeserver signup)

<leeya:kde.org>

<leeya:kde.org> Lol

<coomerhead:telegram> am poor

<coomerhead:telegram> will donate my $100 BTC

<coomerhead:telegram> Forwarded from pashkadurov: Can someone help me to set up Whonix to work fast on mac, I will send 100$ BTC

<varikvalefor:matrix.org> GrapheneOS has won over this former BlackBerry OS snob.

<jimmy_dean_sausage:matrix.org> Friends...no OTA update on Bramble (stable). Anyone else?

<matic_nick:matrix.org> What's the general preferred "desktop" OS here nowadays?

<matic_nick:matrix.org> I don't hang around here often but when I did it was the iPad OS. Apple M1 was barely just a rumor then though but it's pretty well vetted by now, is it safe buy? strcat

<jandroid:matrix.org> I flashed stock android and device was able to connect to my network. Why is the eSIM problem happening only on GrapheneOS?

<hypokeimenon:tchncs.de> matic_nick: #grapheneos-offtopic:matrix.org

<akc3n:tchncs.de> > <@jandroid:matrix.org> I flashed stock android and device was able to connect to my network. Why is the eSIM problem happening only on GrapheneOS?

<akc3n:tchncs.de>

<akc3n:tchncs.de> GrapheneOS/os-issue-tracker #159

<jandroid:matrix.org> Sorry, I wasn't clear in my question. This is a follow up question from today morning. I see some remnants of my old mobile service provider (visible) after I flash grapheneOS. strcat mentioned it has something to do with eSIM, which I never used. (visible doesn't yet support it on Android anyway)

<jandroid:matrix.org> When I flash stock, I am able to connect to my current provider Spectrum with no issues. But, on GrapheneOS, it doesn't work

<stonjjohn:matrix.org> > <@aa3b:matrix.org> I got it.

<stonjjohn:matrix.org>

<stonjjohn:matrix.org> This solved my bad USB driver/ports on my PC. I updated them to the latest drivers with no change. Flashing mobile to mobile worked like a charm! Thanks!

<an-individual:matrix.org> So i've been having trouble installing graphene OS to a google pixel 4. I've been using the web installer. Unlocking the bootloader goes okay. But when I got to flash the image after downloading it, the fastboot screen loads with the message "no valid slot to boot"

<an-individual:matrix.org> Is there anything anyone here can do to help me get up and running?

<akc3n:tchncs.de> > <@an-individual:matrix.org> Is there anything anyone here can do to help me get up and running?

<akc3n:tchncs.de>

<akc3n:tchncs.de> Hi, try to boot it and see if it retunrs to fastboot or it detects the correct slot.

<an-individual:matrix.org> booted to fastbootd after trying again from the beginning.

<go7d13z:matrix.org> Isn't there two ways of doing it

<an-individual:matrix.org> Options are Reboot system now, enter recovery, reboot to bootloader, power off

<go7d13z:matrix.org> ?

<akc3n:tchncs.de> an-individual: if it detects the correct slot, then return to fastboot and lock the bootloader to that it displays the "Your device is loading a different operating systtem" screen

<an-individual:matrix.org> It doesn't say anything about a slot

<an-individual:matrix.org> Should I take a picture of the screen I got?

<go7d13z:matrix.org> Does your computer screen show downloading? It took me there when I installed on boot loader

<akc3n:tchncs.de> an-individual: what os are you using?

<system> file image.png too big to download (3645745 > allowed size: 1000000)

<an-individual:matrix.org> image.png

<an-individual:matrix.org> Guy: Yes, it showed downloading and I waited for finish of download.

<go7d13z:matrix.org> Good it usually says not to mess with it until done

<an-individual:matrix.org> akc3n: flame-factory-2021.06.09.13.zip

<an-individual:matrix.org> I have pixel 4.

<akc3n:tchncs.de> > <@an-individual:matrix.org> akc3n: flame-factory-2021.06.09.13.zip

<akc3n:tchncs.de>

<akc3n:tchncs.de> no, what host os, are you on linux or windows

<an-individual:matrix.org> I gave up on the web installer and decided to try using the one from the zip...

<an-individual:matrix.org> Windows.

<an-individual:matrix.org> I did install the android fastloader

<akc3n:tchncs.de> an-individual: reboot to bootloader

<go7d13z:matrix.org> Now it should be virtually ready once you select reboot to bootloader

<akc3n:tchncs.de> then lock it grapheneos.org/install/web#locking-the-bootloader

<an-individual:matrix.org> But its hanging here on my command line

<an-individual:matrix.org> matrix.grapheneos.org/_matrix/media…matrix.org/QUwtVzXcFijONdGHIECGQyQB

<an-individual:matrix.org> Is this a problem?

<go7d13z:matrix.org> Anyone know any security implements for keeping my sim card separate from os

<leeya:kde.org> > <@an-individual:matrix.org> Is this a problem?

<leeya:kde.org>

<leeya:kde.org> It's a problem on port/cable it seems, try replugging

<go7d13z:matrix.org> Other than say airplane mode

<an-individual:matrix.org> Okay I'll try that.

<akc3n:tchncs.de> > <@an-individual:matrix.org> Windows.

<akc3n:tchncs.de>

<akc3n:tchncs.de> What that error means is that you have an outdate or incorrect version of fastboot android drivers on windows 10. You should plug the phone in and run windows update while it is plugged in.

<an-individual:matrix.org> Using windows 10

<akc3n:tchncs.de> Or as "iT'5 n0t c0nV1nCing b3c@u$E wE sAiD s0!" - "trustworthy" community members or "experts" said, cable/port problem. If you are using a desktop, then please make sure you plug the cable into the back of the computer's usb ports, as the front hub is no good for this. Also, please make sure you are using the original usb cable.

<go7d13z:matrix.org> Try restarting it

<go7d13z:matrix.org> The download buttons

<go7d13z:matrix.org> Reclick it it worked for me

<leeya:kde.org> > <@akc3n:tchncs.de> Or as "iT'5 n0t c0nV1nCing b3c@u$E wE sAiD s0!" - "trustworthy" community members or "experts" said, cable/port problem. If you are using a desktop, then please make sure you plug the cable into the back of the computer's usb ports, as the front hub is no good for this. Also, please make sure you are using the original usb cable.

<leeya:kde.org>

<leeya:kde.org> The flashing process has started

<leeya:kde.org> Most likely it's not the fastboot version that's the problem

<akc3n:tchncs.de> an-individual: freenode.logbot.info/grapheneos/20210407#c7542614

<an-individual:matrix.org> So I unplugged and replugged.

<akc3n:tchncs.de> > <@leeya:kde.org> The flashing process has started

<akc3n:tchncs.de>

<akc3n:tchncs.de> Thanks for correcting my mistake, appreciate it. Apologies an-individual

<an-individual:matrix.org> It still said waiting for device....

<an-individual:matrix.org> I went to back to fastboot mode using the option in the menu

<an-individual:matrix.org> Then the command line continued

<an-individual:matrix.org> And finished. Said press any key to exit.

<an-individual:matrix.org> I did that.

<an-individual:matrix.org> I went to start device from fastboot menu.

<an-individual:matrix.org> It shows google logo.

<leeya:kde.org> Try locking

<an-individual:matrix.org> Then it goes back to fastboot, saying "no valid slot to boot"

<an-individual:matrix.org> Okay I'll try locking

<leeya:kde.org> (Or was it done already (locking bootloader))

<go7d13z:matrix.org> Make sure you relock device before first boot

<leeya:kde.org> Nvm, thought it booted

<akc3n:tchncs.de> an-individual: freenode.logbot.info/grapheneos/20210407#c7542614

<go7d13z:matrix.org> Try whole download process one more time it does that sometimes

<go7d13z:matrix.org> At least for me it did

<an-individual:matrix.org> I tried locking, still saying "no valid slot to boot"

<an-individual:matrix.org> I'll try from the beginning again, but this time I'll lock the bootloader before trying to reboot

<strcat:grapheneos.org> Pixel 4a (5G) and Pixel 5 releases should be ready tomorrow

<strcat:grapheneos.org> temporarily enabling dynamic kernel modules like AOSP/stock until we figure out what goes wrong with them

<leeya:kde.org> > <@an-individual:matrix.org> I'll try from the beginning again, but this time I'll lock the bootloader before trying to reboot

<leeya:kde.org>

<leeya:kde.org> It should flash on b (?) slot this time, and when the flashing ends, it should indicate the active slot as b

<leeya:kde.org> > <@akc3n:tchncs.de> an-individual: freenode.logbot.info/grapheneos/20210407#c7542614

<leeya:kde.org>

<leeya:kde.org> (Based on this log)

<go7d13z:matrix.org> Nooice sunfish is mine

<an-individual:matrix.org> Okay I'll see what it says

<an-individual:matrix.org> So I unlocked by bootloader again it says "slot a"

<an-individual:matrix.org> How do I get it to slot b?

<an-individual:matrix.org> boot slot a

<an-individual:matrix.org> "iT'5 n0t c0nV1nCing b3c@u$E wE sAiD s0!" - "trustworthy" community members or "experts":

<crosschannel:tchncs.de> Is Google switching to the Fuchsia kernel a bad thing?

<leeya:kde.org> > <@an-individual:matrix.org> How do I get it to slot b?

<leeya:kde.org>

<leeya:kde.org> It's a question mark, you'd see when the flashing process starts

<an-individual:matrix.org> Ah okay Ill start flashing again.

<leeya:kde.org> On which slot will be used

<leeya:kde.org> > <@an-individual:matrix.org> sent an image.

<leeya:kde.org>

<leeya:kde.org> On the "setting current slot to..." part here

<an-individual:matrix.org> Sending 'bootloader_a' (8833 KB) OKAY [ 0.545s]

<an-individual:matrix.org> Writing 'bootloader_a' (bootloader) Flashing Pack version c2f2-0.3-7241749

<an-individual:matrix.org> matrix.grapheneos.org/_matrix/media…matrix.org/oekvrfTgPNqKanxTWlQnEoTT

<stonjjohn:matrix.org> > <@an-individual:matrix.org> sent an image.

<stonjjohn:matrix.org>

<stonjjohn:matrix.org> Did it install successfully?

<strcat:grapheneos.org> no

<an-individual:matrix.org> matrix.grapheneos.org/_matrix/media…matrix.org/McebCJuLAuXGrVfWKbHvIGZh

<an-individual:matrix.org> About to try locking again before booting now....

<an-individual:matrix.org> It says "error failed to boot into userspace, one or more components might be unbootable"

<strcat:grapheneos.org> don't boot

<strcat:grapheneos.org> you didn't finish installing

<strcat:grapheneos.org> it's a waste of time to boot something known to not be installed

<strcat:grapheneos.org> you need a reliable USB connection and drivers

<strcat:grapheneos.org> you can't install when it's dropping USB connection

<strcat:grapheneos.org> don't waste time trying to boot when it didn't install

<strcat:grapheneos.org> also just use web installer if you don't understand the CLI output

<an-individual:matrix.org> Yeah it didn't boot.....

<an-individual:matrix.org> Even after locking before the first boot.

<strcat:grapheneos.org> it's known it won't boot when you didn't install it

<strcat:grapheneos.org> locking after not actually installing the OS isn't going to change that

<an-individual:matrix.org> I installed adb from the official android download.

<strcat:grapheneos.org> you didn't actually install the OS

<an-individual:matrix.org> I don't understand what's wrong with my drivers.

<strcat:grapheneos.org> adb is not used for installation

<an-individual:matrix.org> what should I use? I tried windows update it has no suggestions.

<strcat:grapheneos.org> read what the guide says about USB please

<strcat:grapheneos.org> an-individual: you already have drivers so it's not going to show anything now

<an-individual:matrix.org> says everything's up to date.

<anupritaisno1:m.apex.to> an-individual: please verify your download once, make sure you're using the correct USB cable or a good quality connected directly to the motherboard and aren't following any unofficial guides

<strcat:grapheneos.org> an-individual: it's known it won't show drivers now you have them

<strcat:grapheneos.org> if you're using some random USB-A to USB-C cable, there you go

<strcat:grapheneos.org> that's why it's not working, the cable is broken

<anupritaisno1:m.apex.to> an-individual: please verify your download once, make sure you're using the correct USB cable or a good quality one connected directly to the motherboard and aren't following any unofficial guides

<an-individual:matrix.org> Its a cable that came with the phone

<strcat:grapheneos.org> most cables are not spec compliant and don't work for this

<an-individual:matrix.org> Its not random\

<strcat:grapheneos.org> anupritaisno1: then it's the USB-C port that's probably the issue

<strcat:grapheneos.org> an-individual: then it's the USB-C port that's probably the issue

<anupritaisno1:m.apex.to> an-individual: please restore a system restore point. You cannot "install" adb on windows. You're likely following an unofficial guide rn

<anupritaisno1:m.apex.to> Following unofficial guides will lead to bricked phones

<anupritaisno1:m.apex.to> Which is what you're experiencing rn

<an-individual:matrix.org> "On Windows, you may need to install a driver for fastboot now: In Windows Update, click Check for updates. After that there might be a link "View optional updates." Download and install any driver updates. If there are no optional updates, simply continue with the installation instructions."

<an-individual:matrix.org> I tried that and it doesn't say jack about optional updates.

<akc3n:tchncs.de> > <@strcat:grapheneos.org> locking after not actually installing the OS isn't going to change that

<akc3n:tchncs.de>

<akc3n:tchncs.de> That's my fault for giving incorrect information to an-individual and I apologize for that guys. As I was going of the freenode.logbot.info/grapheneos/20210407#c7542614

<strcat:grapheneos.org> an-individual: again, it's not going to show drivers you already have

<strcat:grapheneos.org> said that above

<strcat:grapheneos.org> an-individual: you don't have a reliable USB connection to the device, so your USB drivers (not the fastboot drivers) or USB port / internal hub are broken

<strcat:grapheneos.org> an-individual: you cannot install without a reliable USB connection, nothing you do with software will fix a hardware issue with your computer

<strcat:grapheneos.org> use a different computer or a phone to perform the install

<strcat:grapheneos.org> or figure out what is wrong with that

<anupritaisno1:m.apex.to> an-individual it seems you have followed some weird guide and it has installed weird drivers

<strcat:grapheneos.org> we can't really help you fix USB here

<anupritaisno1:m.apex.to> Get rid of those

<strcat:grapheneos.org> probably not going to help even if they did do that

<anupritaisno1:m.apex.to> System restore works

<anupritaisno1:m.apex.to> Kk

<strcat:grapheneos.org> they should just use a different computer or phone to perform the install

<an-individual:matrix.org> If I use a different computer

<an-individual:matrix.org> What drivers should I get?

<strcat:grapheneos.org> do it the way it says

<strcat:grapheneos.org> don't follow any unofficial guide

<an-individual:matrix.org> Okay

<strcat:grapheneos.org> if you use macOS or Android to perform the install you don't need any drivers / weird stuff

<an-individual:matrix.org> Don't have that

<an-individual:matrix.org> matrix.grapheneos.org/_matrix/media…matrix.org/ZICMCXmInmHOpxqWIaOsqRVm

<an-individual:matrix.org> If I do it this way, will it work on windows 10?

<an-individual:matrix.org> grapheneos.org/install/web#prerequisites

<an-individual:matrix.org> Using microsoft edge and its updated

<entry1:matrix.org> Yes, fully update Windows and use latest version of Chrome

<entry1:matrix.org> an-individual

<strcat:grapheneos.org> an-individual: you need a working USB connection

<strcat:grapheneos.org> nothing in software will fix not having that

<strcat:grapheneos.org> could be hardware issue, could be USB driver issue (unlikely to be anything to do with fastboot drivers)

<an-individual:matrix.org> It was using the ADB

<an-individual:matrix.org> I'm pretty sure.

<strcat:grapheneos.org> adb is not used

<an-individual:matrix.org> It would say "no device found"

<strcat:grapheneos.org> I don't know what you mean 'the ADB'

<an-individual:matrix.org> I would unplug, replug.

<strcat:grapheneos.org> adb isn't used for installation

<an-individual:matrix.org> Its something you aparently really don't wanna use.

<an-individual:matrix.org> Yeah.

<an-individual:matrix.org> I'm ditchin it, on another pc using the windows update now.

<an-individual:matrix.org> It mentioned something about a USB android driver in the optional updates.... went ahead and updated all drivers just to be sure.

<an-individual:matrix.org> Aparantly the guide I was following was total bogus

<an-individual:matrix.org> Had the wrong one.

<an-individual:matrix.org> It takes a minute to update windows and all the drivers

<an-individual:matrix.org> That's what I'm waiting on now for my laptop

<an-individual:matrix.org> Sadly my desktop pc won't be able to perform these installations now unless I completely whipe windows and start anew

<an-individual:matrix.org> Not prepared to do that, I have shit I really need to keep running here.

<an-individual:matrix.org> I have no valild restore points that would help me for this desktop\

<entry1:matrix.org> Like strcat mentioned, try using a different, high quality USB C to USB C cable and try some different ports

<an-individual:matrix.org> If using the propper drivers doesn't solve that, I will try a different cable.

<an-individual:matrix.org> RN this is what I got it came with the phone.

<an-individual:matrix.org> I did test the phone for MTP connection before starting this.

<an-individual:matrix.org> That much seemed to work, I could drag files between computer and phone no problem.

<strcat:grapheneos.org> the cable that comes with the phone is almost certainly fine

<strcat:grapheneos.org> it's the USB-C ports on many crappy Windows laptops, etc. that are not

<entry1:matrix.org> Cool. Keep us posted. Yeah even if the phone works for file transfer, it may not work for the flashing process. That cable should be good though. Most of us here have experienced that and learned that the hard way from having either a faulty cable or port

<an-individual:matrix.org> I have USB-A to USB-C cable that came with the phone... I think that's the right term for the usb port on most laptops?

<an-individual:matrix.org> I've performed a flash before but not with Graphene OS.

<clannad:telegram> My private DNS went down

<an-individual:matrix.org> It was some sort of root installation for a galaxy J3

<strcat:grapheneos.org> an-individual: no USB-A to USB-C cable comes with the phone

<entry1:matrix.org> > <@an-individual:matrix.org> I have USB-A to USB-C cable that came with the phone... I think that's the right term for the usb port on most laptops?

<entry1:matrix.org>

<entry1:matrix.org> USB C to USB C is the only cable that comes with Pixel phones

<clannad:telegram> Killed my entire network

<an-individual:matrix.org> Oh. Well I orderd this one on amazon

<strcat:grapheneos.org> the cable that comes with the phone is USB-C to USB-C

<an-individual:matrix.org> Maybe that's part of my fun? XD

<strcat:grapheneos.org> well that's really sketchy no such cable comes with the phone, was it not a new phone?

<entry1:matrix.org> > <@grapheneosbridge:grapheneos.org> <clannad:telegram> Killed my entire network

<entry1:matrix.org>

<entry1:matrix.org> Adguard DNS?

<strcat:grapheneos.org> an-individual: was it a used phone?

<strcat:grapheneos.org> you didn't get the original cable then

<an-individual:matrix.org> No not new man

<an-individual:matrix.org> I tried to be cheap

<strcat:grapheneos.org> that's your issue, they gave you some random broken cable

<strcat:grapheneos.org> the issue isn't the phone, it's the cable

<an-individual:matrix.org> Renewed phone.

<an-individual:matrix.org> Possibly.

<strcat:grapheneos.org> 99% chance the cable is broken

<an-individual:matrix.org> We'll find out here shortly.

<strcat:grapheneos.org> have a lot of experience resolving these issues for ppl

<an-individual:matrix.org> Computer restarting now with all updates.

<strcat:grapheneos.org> almost every random USB-A to USB-C cable is broken

<an-individual:matrix.org> Are there good A-to-C cables I can get?

<an-individual:matrix.org> That's kinda my option rn.

<entry1:matrix.org> Anker and Belkin have a good reputation

<entry1:matrix.org> You can always keep a costlier cable just for flashing, and use lower quality ones for everyday/spare use

<an-individual:matrix.org> SO far so good with the restart, the web interface from official graphene OS website actually detected my phone. Before it wasn't doing that until I did funky cable nonsense.

<anupritaisno1:m.apex.to> Edge works fine

<anupritaisno1:m.apex.to> No need to suggest chrome

<an-individual:matrix.org> That's good\

<an-individual:matrix.org> I hate chrome

<anupritaisno1:m.apex.to> Ignore these my connection went down due to a thunderstorm ^

<an-individual:matrix.org> Google spying on me...

<an-individual:matrix.org> Whole reason I'm even here.

<an-individual:matrix.org> It booted.

<an-individual:matrix.org> So yeah, the guide I followed was complete trash.

<an-individual:matrix.org> The cable turned out to be fine.

<an-individual:matrix.org> They sent me a good one.

<an-individual:matrix.org> So uh

<an-individual:matrix.org> It did boot

<an-individual:matrix.org> I connected to wifi

<entry1:matrix.org> Got it? an-individual

<an-individual:matrix.org> Ummm

<an-individual:matrix.org> I press next

<an-individual:matrix.org> And theres this black screen

<an-individual:matrix.org> I press back

<an-individual:matrix.org> Next again...

<an-individual:matrix.org> Its a loop

<entry1:matrix.org> I'm familiar with doing the CLI method (not recommended for first time users). There should be someone who can assist

<an-individual:matrix.org> Nevermind

<an-individual:matrix.org> I got out of it.

<an-individual:matrix.org> Sorry I was being foolish

<entry1:matrix.org> What's it on now?

<akc3n:tchncs.de> > <@entry1:matrix.org> What's it on now?

<akc3n:tchncs.de>

<akc3n:tchncs.de> Its all done. I'm just walking him through attestation.app / auditor for scheduling remote verification in pm chat.

<ss00:tchncs.de> strcat: is it possible making a donation and then after the donation is made make non-binding feature request for consideration only? If so, after donation is made to what email would I direct that feature request ?

<anupritaisno1:m.apex.to> ss00: please don't do it that way

<anupritaisno1:m.apex.to> Explain your feature on the issue tracker

<akc3n:tchncs.de> > <@ss00:tchncs.de> strcat: is it possible making a donation and then after the donation is made make non-binding feature request for consideration only? If so, after donation is made to what email would I direct that feature request ?

<akc3n:tchncs.de>

<akc3n:tchncs.de> github.com/GrapheneOS/os-issue-tracker/issues

<strcat:grapheneos.org> ss00: we don't take payments for features/work

<an-individual:matrix.org> I did run verify

<an-individual:matrix.org> I think it said its okay

<an-individual:matrix.org> I sent a DM to akc3n

<ss00:tchncs.de> strcat: "non-binding" feature "request"

<akc3n:tchncs.de> > <@an-individual:matrix.org> I sent a DM to akc3n

<akc3n:tchncs.de>

<akc3n:tchncs.de> Got it. replying now regarding auditor.

<ss00:tchncs.de> strcat: I'm asking if *after* donation I can make a request that is completely non-binding and again just a "request"

<leeya:kde.org> You can open an issue with or without donation in os-issue-tracker anyways

<leeya:kde.org> Doing it with donation will not make the development any faster

<renlord:matrix.org> you could fund a particular feature on bountyhunt or something along those lines

<renlord:matrix.org> whether it is accepted upstream or not it is a separate matter

<leeya:kde.org> Doing it with donation will not make the development any faster (on that requested feature)

<strcat:grapheneos.org> ss00: donations won't be taken into account for features

<strcat:grapheneos.org> they're donations not payments for a service

<strcat:grapheneos.org> we won't accept donations that are based on expecting something in return even "non-binding"

<renlord:matrix.org> google what a donation is lol

<strcat:grapheneos.org> the project only takes donations, it doesn't provide contract work

<strcat:grapheneos.org> there's no business associated with it

<ss00:tchncs.de> strcat: again not asking for any work or any expectation of any deliverable just that I can make a suggestion

<akc3n:tchncs.de> > <@ss00:tchncs.de> strcat: again not asking for any work or any expectation of any deliverable just that I can make a suggestion

<akc3n:tchncs.de>

<akc3n:tchncs.de> > github.com/GrapheneOS/os-issue-tracker/issues

<strcat:grapheneos.org> ss00: suggestions unrelated to donations

<strcat:grapheneos.org> donations will not impact prioritization of work or how a feature request is seen

<strcat:grapheneos.org> there is nothing provided in return for a donation, as required by law for it to not be considered payment for a service/product

<akc3n:tchncs.de> > github.com/GrapheneOS/os-issue-tracker/issues

<akc3n:tchncs.de> Submitting a suggestion and label it as a `Enhancement new feature or request`

<ss00:tchncs.de> strcat: For final time, I would like to make a donation to the project. The donation is as the name implies a donation and is zero expectation of any work in return. I only ask that consideration be given to a feature request and nothing more.

<renlord:matrix.org> consideration is always given to any feature request filed in the issue tracker

<renlord:matrix.org> whether or not a donation is made

<resist.berlin:matrix.org> > <@ss00:tchncs.de> strcat: For final time, I would like to make a donation to the project. The donation is as the name implies a donation and is zero expectation of any work in return. I only ask that consideration be given to a feature request and nothing more.

<resist.berlin:matrix.org>

<resist.berlin:matrix.org> Make two separate things

<resist.berlin:matrix.org> You can suggest anything right here, right now

<renlord:matrix.org> they are two separate and independent matters

<resist.berlin:matrix.org> For example: "I would like a pink unicorn theme". You can say it right here, it might get accepted or not. Lengthy discussions might follow or not. But this chat and the issue tracker are made for that.

<ss00:tchncs.de> What is the problem with a project donor making a request for consideration to the project administrator?

<strcat:grapheneos.org> ss00: donations don't come with anything in return

<strcat:grapheneos.org> that's not changing

<strcat:grapheneos.org> nothing will be considered or provided based on a donation

<strcat:grapheneos.org> people can file feature requests whether or not they donate

<resist.berlin:matrix.org> > <@ss00:tchncs.de> strcat: For final time, I would like to make a donation to the project. The donation is as the name implies a donation and is zero expectation of any work in return. I only ask that consideration be given to a feature request and nothing more.

<resist.berlin:matrix.org>

<resist.berlin:matrix.org> Make it two separate things

<strcat:grapheneos.org> feature requests will be considered on their merit

<strcat:grapheneos.org> if it's not wanted, it will be closed

<strcat:grapheneos.org> if it is wanted, it will be left open, and a volunteer can work on it

<strcat:grapheneos.org> if you want to pay a developer to implement something, do that

<strcat:grapheneos.org> doesn't imply we will take the changes

<strcat:grapheneos.org> paying the developer to do it doesn't involve us

<strcat:grapheneos.org> the project doesn't offer contract work

<strcat:grapheneos.org> the project internally pays developers, it is not a business and doesn't offer contract work, etc.

<anupritaisno1:m.apex.to> ss00: what is your feature exactly

<anupritaisno1:m.apex.to> Describe your feature, not the payment for it

<akc3n:tchncs.de> > <@ss00:tchncs.de> strcat: For final time, I would like to make a donation to the project. The donation is as the name implies a donation and is zero expectation of any work in return. I only ask that consideration be given to a feature request and nothing more.

<akc3n:tchncs.de>

<akc3n:tchncs.de> I understand where you are coming from, it may be difficult at times to explain oneself virtually via text, I too sometimes struggle with that and people understanding my intentions, and I can see you are quite adamant about and sincere. However, these are both seperate matters. And there is nothing wrong with making a feature request or suggestion. To be perfectly candor with you, it's all about how you may have per

<anupritaisno1:m.apex.to> If it's actually a good suggestion we will add it in ourselves

<akc3n:tchncs.de> I understand where you are coming from, it may be difficult at times to explain oneself virtually via text, I too sometimes struggle with that (not intended to mean that you are struggling with this by any means) and people understanding my intentions, and I can see you are quite adamant about and sincere. However, these are both seperate matters. And there is nothing wrong with making a feature request or suggestion

<akc3n:tchncs.de>

<akc3n:tchncs.de> Just my two cents on my own experiences and what helped me develop personal growth in communicating with others.

<ss00:tchncs.de> akc3n: here is a copy of my first message:

<ss00:tchncs.de>

<ss00:tchncs.de> *strcat: is it possible making a donation and then after the donation is made make non-binding feature request for consideration only? If so, after donation is made to what email would I direct that feature request ? *

<ss00:tchncs.de> Key words being "after donation" "non-binding" and "consideration only"

<strcat:grapheneos.org> no, it isn't

<strcat:grapheneos.org> it's possible to file a feature request

<strcat:grapheneos.org> it's possible to make a donation

<strcat:grapheneos.org> it isn't possible to make a feature request related in some way to a donation

<strcat:grapheneos.org> if you insist on it being related we can't take the donation

<akc3n:tchncs.de> > <@ss00:tchncs.de> akc3n: here is a copy of my first message:

<akc3n:tchncs.de> >

<akc3n:tchncs.de> > *strcat: is it possible making a donation and then after the donation is made make non-binding feature request for consideration only? If so, after donation is made to what email would I direct that feature request ? *

<akc3n:tchncs.de>

<akc3n:tchncs.de> I know.....

<strcat:grapheneos.org> not really interested in more of this have a lot to do

<ss00:tchncs.de> > <@strcat:grapheneos.org> it isn't possible to make a feature request related in some way to a donation

<ss00:tchncs.de>

<ss00:tchncs.de> Thank you. For whatever bizarre reasoning is at play here I respect that choice and this question has nownbeen answered. Thank you everyone. Have a nice weekend.

<resist.berlin:matrix.org> I doubt it's a "choice". It's a legal requirement

<akc3n:tchncs.de> > <@ss00:tchncs.de> Thank you. For whatever bizarre reasoning is at play here I respect that choice and this question has nownbeen answered. Thank you everyone. Have a nice weekend.

<akc3n:tchncs.de>

<akc3n:tchncs.de> Thanks, you as well.

<q22:matrix.org> I didn't mean to react. I was just curious if i could see who reacted, by clicking on the thumbs down. W/e

<akc3n:tchncs.de> > <@q22:matrix.org> I didn't mean to react. I was just curious if i could see who reacted, by clicking on the thumbs down. W/e

<akc3n:tchncs.de>

<akc3n:tchncs.de> Interesting. Hold that thought....

<anupritaisno1:m.apex.to> No offtopic here please

<Onkeldago:telegram> Hey Friends. Hope youre good ?

<Onkeldago:telegram> can someone help me find an MDM solution for graphene? I want to download and install apps automatically & I want to be able to wipe a device.

<akc3n:tchncs.de> > <@grapheneosbridge:grapheneos.org> <Onkeldago:telegram> Hey Friends. Hope youre good ?

<akc3n:tchncs.de> > can someone help me find an MDM solution for graphene? I want to download and install apps automatically & I want to be able to wipe a device.

<akc3n:tchncs.de>

<akc3n:tchncs.de> A third party MDM that doesn't use GSM. We do recommend against third party device administrators as they present a lot of attack surface.

<akc3n:tchncs.de> Also, this maybe better suited for #offtopic:grapheneos.org for further discussion.

<akc3n:tchncs.de> > <@grapheneosbridge:grapheneos.org> <Onkeldago:telegram> Hey Friends. Hope youre good ?

<akc3n:tchncs.de> > can someone help me find an MDM solution for graphene? I want to download and install apps automatically & I want to be able to wipe a device.

<akc3n:tchncs.de>

<akc3n:tchncs.de> A third party MDM that doesn't use GSM. However, we do recommend against third party device administrators as they present a lot of attack surface.

<akc3n:tchncs.de> Also, this maybe better suited for #offtopic:grapheneos.org for further discussion.

<akc3n:tchncs.de> @onkeldago:telegram on the telegram side, it's @grapheneosofftopic

<akc3n:tchncs.de> > <@grapheneosbridge:grapheneos.org> <Onkeldago:telegram> Hey Friends. Hope youre good ?

<akc3n:tchncs.de> > can someone help me find an MDM solution for graphene? I want to download and install apps automatically & I want to be able to wipe a device.

<akc3n:tchncs.de>

<akc3n:tchncs.de> As for remote wipe, please read this section entire section grapheneos.org/faq#encryption

<akc3n:tchncs.de>

<akc3n:tchncs.de> Also check out github.com/Peter-Easton/GrapheneOS-…en-incorrect-guesses-at-the-pincode

<stonjjohn:matrix.org> So based on the FAQ (grapheneos.org/faq#google-services) it reads as though unless the dev of the app builds their own notification and/or text-to-voice system/s such as in apps like OSMand via f-droid (navigation voice guidance) and Signal (notifications) those respective functions will not work, is that correct? And so, I can assume that if apps of similar functions are not working as expected then its

<stonjjohn:matrix.org> In my example, voice navigation in OSMand doesn't work in GrapheneOS therefore that is an indication of what I said previously and not a bug or an issue with the OS necessarily. Am I interpreting this correctly?

<eassen496:matrix.org> Ils it normal that I have g.co/ABH when i launch my phone ?

<eassen496:matrix.org> Is***

<akc3n:tchncs.de> > <@stonjjohn:matrix.org> In my example, voice navigation in OSMand doesn't work in GrapheneOS therefore that is an indication of what I said previously and not a bug or an issue with the OS necessarily. Am I interpreting this correctly?

<akc3n:tchncs.de>

<akc3n:tchncs.de> Apps are #offtopic:grapheneos.org in general.

<akc3n:tchncs.de> Apps that don't have a fallback for push notifications and relay on google services therefore it is definitely not a a bug more an issue with the OS.

<akc3n:tchncs.de> > <@eassen496:matrix.org> Ils it normal that I have g.co/ABH when i launch my phone ?

<akc3n:tchncs.de>

<akc3n:tchncs.de> Yes, it is.

<akc3n:tchncs.de> > <@stonjjohn:matrix.org> In my example, voice navigation in OSMand doesn't work in GrapheneOS therefore that is an indication of what I said previously and not a bug or an issue with the OS necessarily. Am I interpreting this correctly?

<akc3n:tchncs.de>

<akc3n:tchncs.de> Apps are #offtopic:grapheneos.org in general.

<akc3n:tchncs.de> Apps that don't have a fallback for push notifications and relay on google services therefore it is definitely not a a bug nor an issue with the OS.

<akc3n:tchncs.de> > <@stonjjohn:matrix.org> In my example, voice navigation in OSMand doesn't work in GrapheneOS therefore that is an indication of what I said previously and not a bug or an issue with the OS necessarily. Am I interpreting this correctly?

<akc3n:tchncs.de>

<akc3n:tchncs.de> Apps are #offtopic:grapheneos.org in general.

<akc3n:tchncs.de> Apps that don't have a fallback for push notifications and relay on google services therefore it is definitely not a a bug nor an issue with the OS.

<eassen496:matrix.org> Okay

<akc3n:tchncs.de> > <@eassen496:matrix.org> Ils it normal that I have g.co/ABH when i launch my phone ?

<akc3n:tchncs.de>

<akc3n:tchncs.de> freenode.logbot.info/grapheneos/20210319#c7323159

<akc3n:tchncs.de> eassen496: take a look at that explanation regarding your question about g.co/ABH

<sphinxcat:matrix.org> stonjjohn: the example of OSMand has more to do with not having a TTS app installed / configured

<sphinxcat:matrix.org> stonjjohn: the example of OSMand has more to do with not having a TTS app installed / configured, but yes you got it

<plok0099:matrix.org> Help ,Anyway to install graphene without unlocking bootloader?

<exfoliat:matrix.org> plok0099 no there isn't

<plok0099:matrix.org> okayy i see :(

<ss00:tchncs.de> > <@grapheneosbridge:grapheneos.org> <Onkeldago:telegram> Hey Friends. Hope youre good ?

<ss00:tchncs.de> > can someone help me find an MDM solution for graphene? I want to download and install apps automatically & I want to be able to wipe a device.

<ss00:tchncs.de>

<ss00:tchncs.de> Its possible to provision a GrapheneOS device as a *device owner* but it is *very very difficult*. All the support is already built into GrapheneOS but without the option during initial device configuration to scan the QR code thingy and provision the device into this mode the process becomes a serious headache!

<ss00:tchncs.de> > <@akc3n:tchncs.de> A third party MDM that doesn't use GSM. We do recommend against third party device administrators as they present a lot of attack surface.

<ss00:tchncs.de> > Also, this maybe better suited for #offtopic:grapheneos.org for further discussion.

<ss00:tchncs.de>

<ss00:tchncs.de> 1. Many third party MDM work fine without GSM.

<ss00:tchncs.de> 2. Regarding attack surface that is outrageously misguided assessment.

<ss00:tchncs.de> > <@akc3n:tchncs.de> As for remote wipe, please read this section entire section grapheneos.org/faq#encryption

<ss00:tchncs.de> >

<ss00:tchncs.de> > Also check out github.com/Peter-Easton/GrapheneOS-…en-incorrect-guesses-at-the-pincode

<ss00:tchncs.de>

<ss00:tchncs.de> Encryption is not a substitute for remote wipe capability. Indeed I can think of some circumstances in which an encrypted and locked device would be a problem and liability.

<ss00:tchncs.de> > <@akc3n:tchncs.de> As for remote wipe, please read this section entire section grapheneos.org/faq#encryption

<ss00:tchncs.de> >

<ss00:tchncs.de> > Also check out github.com/Peter-Easton/GrapheneOS-…en-incorrect-guesses-at-the-pincode

<ss00:tchncs.de>

<ss00:tchncs.de> Encryption is not a complete substitute for remote wipe capability. Indeed I can think of some circumstances in which an encrypted and locked device would be a problem and liability.

<ss00:tchncs.de> > <@akc3n:tchncs.de> As for remote wipe, please read this section entire section grapheneos.org/faq#encryption

<ss00:tchncs.de> >

<ss00:tchncs.de> > Also check out github.com/Peter-Easton/GrapheneOS-…en-incorrect-guesses-at-the-pincode

<ss00:tchncs.de>

<ss00:tchncs.de> Encryption is not a complete substitute for remote wipe capability. Indeed I can think of some circumstances in which an encrypted and locked device would be a problem or liability. Encryption is only good when your adversary does not pull out your fingernails.

<ss00:tchncs.de> I can think of many circumstances in which remote wipe would be by far better option it perhaps from US/Canadian perspective not relevant though so I might suggest to my friend that requires MDM for remote wipe functionality to consider a different project perhaps Calyx ?

<ss00:tchncs.de> I can think of many circumstances in which remote wipe would be by far better option it perhaps from US/Canadian perspective not relevant though so I might suggest to my friend that requires functionality to consider a different project perhaps Calyx ?

<akc3n:tchncs.de> > <@ss00:tchncs.de> 1. Many third party MDM work fine without GSM.

<akc3n:tchncs.de> > 2. Regarding attack surface that is outrageously misguided assessment.

<akc3n:tchncs.de>

<akc3n:tchncs.de> Fair enough, perhaps then you can provide that answer to the user asking about an MDM solution then (and educate me as well please, genuiely I would really like to know).

<akc3n:tchncs.de> As far #2 Encrochat would beg a differ, after all, that is part of reason as to why there network went down in the first place...

<akc3n:tchncs.de> Please have a read through logbot for more information about attack surface risk increase, and that we don't recommend, even though it works fine through device admin.

<ss00:tchncs.de> > <@akc3n:tchncs.de> Fair enough, perhaps then you can provide that answer to the user asking about an MDM solution then (and educate me as well please, genuiely I would really like to know).

<ss00:tchncs.de> > As far #2 Encrochat would beg a differ, after all, that is part of reason as to why there network went down in the first place...

<ss00:tchncs.de> > Please have a read through logbot for more information about attack surface risk increase, and that we don't recommend, even though it works fine through device admin.

<ss00:tchncs.de>

<ss00:tchncs.de> Drawing on the Encrochat saga is seriously misguided my friend. I am in bed but FYI several turnkey open source projects you can self host your own MDM.

<akc3n:tchncs.de> > <@ss00:tchncs.de> Drawing on the Encrochat saga is seriously misguided my friend. I am in bed but FYI several turnkey open source projects you can self host your own MDM.

<akc3n:tchncs.de>

<akc3n:tchncs.de> As the user whom initially asked the questoin, already tried self hosting and was looking for an alternative. Perhaps it may help you to read their message careful rathe then attacking me.

<ss00:tchncs.de> No attacks my friend just discussion

<ss00:tchncs.de> I will review again and respond I am tired and in bed and need put phone down lol if I don't respond tonight i will in the morning

<akc3n:tchncs.de> > <@ss00:tchncs.de> Drawing on the Encrochat saga is seriously misguided my friend. I am in bed but FYI several turnkey open source projects you can self host your own MDM.

<akc3n:tchncs.de>

<akc3n:tchncs.de> A real world example based on court record documents is a fact I decided to use to reference from recent history. I'm not sure what I did to you except defend you earlier when you were talking about making a donation and non-binding feature request.

<akc3n:tchncs.de> > <@ss00:tchncs.de> No attacks my friend just discussion

<akc3n:tchncs.de>

<akc3n:tchncs.de> I don't have any friends that speak to me the way you just did. Have a good night sir.

<coastguard:matrix.org> Hello, I saw that it is possible to install /e/ on the Fairphone and relock the bootloader. Do you think it is worth looking into building GrapheneOS for the Fairphone? I am talking about myself, doing the work.

<antoine62:halogen.city> It may not have the hardware features that graphene wants

<akc3n:tchncs.de> > <@coastguard:matrix.org> Hello, I saw that it is possible to install /e/ on the Fairphone and relock the bootloader. Do you think it is worth looking into building GrapheneOS for the Fairphone? I am talking about myself, doing the work.

<akc3n:tchncs.de>

<akc3n:tchncs.de> grapheneos.org/faq#future-devices explains about meeting the standards, however you can build for a generic target, however generic builds don't have vendor files like firmware.

<hmenke:matrix.org> strcat: The latest tag `RQ3A.210605.005.2021.06.09.13` of platform_manifest is missing from GitHub (and the repo doesn't exist on GitHub).

<penners:matrix.org> Hello everyone. I disabled the settings and vanadium app via adb shell, and now my phone won't boot - just stuck on the flashing GrapheneOS text. Do you think it's salvageable or do I need to reflash graphene?

<akc3n:tchncs.de> > <@hmenke:matrix.org> strcat: The latest tag `RQ3A.210605.005.2021.06.09.13` of platform_manifest is missing from GitHub (and the repo doesn't exist on GitHub).

<akc3n:tchncs.de>

<akc3n:tchncs.de> Current release was still being worked on yesterday.

<akc3n:tchncs.de>

<akc3n:tchncs.de>

<akc3n:tchncs.de> All repositories other than the Pixel 4a (5G), Pixel 5 kernels and the overall manifest are tagged, however not those until it's finished.

<akc3n:tchncs.de>

<akc3n:tchncs.de>

<akc3n:tchncs.de> Then the devs can push those out into Beta hopefully sometime today, and then tag release.

<akc3n:tchncs.de> > <@penners:matrix.org> Hello everyone. I disabled the settings and vanadium app via adb shell, and now my phone won't boot - just stuck on the flashing GrapheneOS text. Do you think it's salvageable or do I need to reflash graphene?

<akc3n:tchncs.de>

<akc3n:tchncs.de> Why would you disable the settings via adb shell?!!!?

<penners:matrix.org> > <@akc3n:tchncs.de> Why would you disable the settings via adb shell?!!!?

<penners:matrix.org>

<penners:matrix.org> Yeah not my smartest move. I wanted to lock down the phone to only a few apps as an anti-distraction strategy. Disabled settings so that it's not possible to add new users. Now it's the ultimate anti-distraction phone, because I can't do anything with it!

<st4rpixel:matrix.org> Which model will be supported longer

<st4rpixel:matrix.org> Pixel 3a XL

<st4rpixel:matrix.org> or

<st4rpixel:matrix.org> Pixel 3 XL?

<leeya:kde.org> 3a XL

<leeya:kde.org> based on endoflife.date/pixel

<st4rpixel:matrix.org> Thank you sir.

<hainslow:matrix.org> Good afternoon, is this the right place to get help at installing GrapheneOS?

<progfolk:matrix.org> Hey guys, hoping for some help with an install error message...

<progfolk:matrix.org>

<progfolk:matrix.org> Using the Web Installer on a Pixel4a, have unlocked bootloader, then get the following message after flashing factory image:

<progfolk:matrix.org> "The requested file could not be read, typically due to permission problems that have occurred after a reference to a file was acquired"

<progfolk:matrix.org>

<progfolk:matrix.org> Any suggestions?

<progfolk:matrix.org> Thanks

<st4rpixel:matrix.org> I heard in the last update is a function with "auto reboot".

<st4rpixel:matrix.org> Got the newest one but someone can explain what this function is and how I can configure it?

<Atlantistux:telegram> Hello all

<Atlantistux:telegram> I recently buy a pixel 4a, with Android 11 preinstalled, does anyone know of a method to find out if the phone has been used before?

<penners:matrix.org> > <@penners:matrix.org> Hello everyone. I disabled the settings and vanadium app via adb shell, and now my phone won't boot - just stuck on the flashing GrapheneOS text. Do you think it's salvageable or do I need to reflash graphene?

<penners:matrix.org>

<penners:matrix.org> Continuing on from this, I'm trying to reinstall Graphene. I can't unlock the bootloader because OEM unlocking was not turned on in settings, can't get into the OS to turn it on.

<hainslow:matrix.org> Pretty new to this and havin trouble installing. I'll try to keep this brief.

<hainslow:matrix.org>

<hainslow:matrix.org> I installed Lineage on my Pixel 3 and want to try Graphene now. I'm wondering what's the right way to install since the bootloader is already unlocked.

<hainslow:matrix.org>

<hainslow:matrix.org> Following the web installer instructions I'll get "timeout of 10000 ms exceeded" when I try to unlock or

<hainslow:matrix.org> obtain factory images.

<hainslow:matrix.org>

<hainslow:matrix.org> Do I need to skip that "unlock the bootloader to allow flashing the OS and firmware" part?

<hainslow:matrix.org>

<hainslow:matrix.org> Also tried command-line instructions (I'm on Manjaro Linux) to flash the images but the script (./flash-all.sh) won't do anything.

<hainslow:matrix.org>

<hainslow:matrix.org> Prequisites should be fine: I have enough memory and storage space, I've got a USB-C cable (not the original one, though - phone is refurbed and came with a new one, worked flawlessly with Lineage installation), my computer (Dell XPS 15) has an USB-C port, my OS is (Manjaro --> Arch), adb & fastboot (android-tools, android-udev, and up-to-date and I'm used Chromium Browser for the Web installer.

<hainslow:matrix.org>

<hainslow:matrix.org> Thanks a lot for helping! Have a great weekend!

<sb13x:matrix.org> > <@st4rpixel:matrix.org> I heard in the last update is a function with "auto reboot".

<sb13x:matrix.org> > Got the newest one but someone can explain what this function is and how I can configure it?

<sb13x:matrix.org>

<sb13x:matrix.org> Settings>Security>Auto Reboot and select how often you want your device to restart when left idle at the lockscreen for.

<dontneedheadaches:telegram> Hello everybody..

<dontneedheadaches:telegram> if I for any reason want delete all on my phone with graphenos offcourse and reinstall all again am I sure there is no info leaked to the phone itself? I mean pics or chats or whatever can be found hidden in the device?

<hainslow:matrix.org> Pretty new to this and havin trouble installing. I'll try to keep this brief.

<hainslow:matrix.org>

<hainslow:matrix.org> I installed Lineage on my Pixel 3 and want to try Graphene now. I'm wondering what's the right way to install since the bootloader is already unlocked.

<hainslow:matrix.org>

<hainslow:matrix.org> Following the web installer instructions I'll get "timeout of 10000 ms exceeded" when I try to unlock or

<hainslow:matrix.org> obtain factory images.

<hainslow:matrix.org>

<hainslow:matrix.org> Do I need to skip that "unlock the bootloader to allow flashing the OS and firmware" part?

<hainslow:matrix.org>

<hainslow:matrix.org> Also tried command-line instructions (I'm on Manjaro Linux) to flash the images but the script (./flash-all.sh) won't do anything.

<hainslow:matrix.org>

<hainslow:matrix.org> Prequisites should be fine: I have enough memory and storage space, I've got a USB-C cable (not the original one, though - phone is refurbed and came with a new one, worked flawlessly with Lineage installation), my computer (Dell XPS 15) has an USB-C port, my OS is (Manjaro --> Arch), adb, fastboot, android-udev are installed and up-to-date and I used Chromium Browser for the Web installer.

<hainslow:matrix.org>

<hainslow:matrix.org> Thanks a lot for helping! Have a great weekend!

<dontneedheadaches:telegram> Wats the best way to do so reinstall the apps again

<hooly:tchncs.de> > <@grapheneosbridge:grapheneos.org> <dontneedheadaches:telegram> Hello everybody..

<hooly:tchncs.de> > if I for any reason want delete all on my phone with graphenos offcourse and reinstall all again am I sure there is no info leaked to the phone itself? I mean pics or chats or whatever can be found hidden in the device?

<hooly:tchncs.de>

<hooly:tchncs.de> Even if some bits are not wiped, it is all encrypted. Good luck trying to restore any data without the key.

<hainslow:matrix.org> Pretty new to this and having trouble installing. I'll try to keep this brief.

<hainslow:matrix.org>

<hainslow:matrix.org> I installed Lineage on my Pixel 3 and want to try Graphene now. I'm wondering what's the right way to install since the bootloader is already unlocked.

<hainslow:matrix.org>

<hainslow:matrix.org> Following the web installer instructions I'll get "timeout of 10000 ms exceeded" when I try to unlock or

<hainslow:matrix.org> obtain factory images.

<hainslow:matrix.org>

<hainslow:matrix.org> Do I need to skip that "unlock the bootloader to allow flashing the OS and firmware" part?

<hainslow:matrix.org>

<hainslow:matrix.org> Also tried command-line instructions (I'm on Manjaro Linux) to flash the images but the script (./flash-all.sh) won't do anything.

<hainslow:matrix.org>

<hainslow:matrix.org> Prequisites should be fine: I have enough memory and storage space, I've got a USB-C cable (not the original one, though - phone is refurbed and came with a new one, worked flawlessly with Lineage installation), my computer (Dell XPS 15) has an USB-C port, my OS is (Manjaro --> Arch), adb, fastboot, android-udev are installed and up-to-date and I used Chromium Browser for the Web installer.

<hainslow:matrix.org>

<hainslow:matrix.org> Thanks a lot for helping! Have a great weekend!

<dontneedheadaches:telegram> Best and easiest way to wipe the phone? (re @GrapheneOSBridgeBot: <hooly:tchncs.de> > <@grapheneosbridge:grapheneos.org> <dontneedheadaches:telegram> Hello everybody..

<dontneedheadaches:telegram> > if I for any reason want delete all on my phone with graphenos offcourse and reinstall all again am I sure there is no info leaked to the phone itself? I mean pics or chats or whatever can be found hidden in the device?

<dontneedheadaches:telegram> Even if some bits are not wiped, it is all encrypted. Good luck trying to restore any data without the key.)

<hooly:tchncs.de> > <@hainslow:matrix.org> Pretty new to this and having trouble installing. I'll try to keep this brief.

<hooly:tchncs.de> >

<hooly:tchncs.de> > I installed Lineage on my Pixel 3 and want to try Graphene now. I'm wondering what's the right way to install since the bootloader is already unlocked.

<hooly:tchncs.de> >

<hooly:tchncs.de> > Following the web installer instructions I'll get "timeout of 10000 ms exceeded" when I try to unlock or

<hooly:tchncs.de> > obtain factory images.

<hooly:tchncs.de> >

<hooly:tchncs.de> > Do I need to skip that "unlock the bootloader to allow flashing the OS and firmware" part?

<hooly:tchncs.de> >

<hooly:tchncs.de> > Also tried command-line instructions (I'm on Manjaro Linux) to flash the images but the script (./flash-all.sh) won't do anything.

<hooly:tchncs.de> >

<hooly:tchncs.de> > Prequisites should be fine: I have enough memory and storage space, I've got a USB-C cable (not the original one, though - phone is refurbed and came with a new one, worked flawlessly with Lineage installation), my computer (Dell XPS 15) has an USB-C port, my OS is (Manjaro --> Arch), adb, fastboot, android-udev are installed and up-to-date and I used Chromium Browser for the Web installer.

<hooly:tchncs.de> >

<hooly:tchncs.de> > Thanks a lot for helping! Have a great weekend!

<hooly:tchncs.de>

<hooly:tchncs.de> Try flashing the stock ROM and installing updates, in case Lineage doesn't include some firmware updates.

<hooly:tchncs.de> > <@grapheneosbridge:grapheneos.org> <dontneedheadaches:telegram> Best and easiest way to wipe the phone? (re @GrapheneOSBridgeBot: <hooly:tchncs.de> > <@grapheneosbridge:grapheneos.org> <dontneedheadaches:telegram> Hello everybody..

<hooly:tchncs.de> > > if I for any reason want delete all on my phone with graphenos offcourse and reinstall all again am I sure there is no info leaked to the phone itself? I mean pics or chats or whatever can be found hidden in the device?

<hooly:tchncs.de> > Even if some bits are not wiped, it is all encrypted. Good luck trying to restore any data without the key.)

<hooly:tchncs.de>

<hooly:tchncs.de> Just re-install GrapheneOS.

<dontneedheadaches:telegram> Tks for the awnser but is there not a easier way to delete all but keep graphenos? (re @GrapheneOSBridgeBot: <hooly:tchncs.de> > <@grapheneosbridge:grapheneos.org> <dontneedheadaches:telegram> Best and easiest way to wipe the phone? (re @GrapheneOSBridgeBot: <hooly:tchncs.de> > <@grapheneosbridge:grapheneos.org> <dontneedheadaches:telegram> Hello everybody..

<dontneedheadaches:telegram> > > if I for any reason want delete all on my phone with graphenos offcourse and reinstall all again am I sure there is no info leaked to the phone itself? I mean pics or chats or whatever can be found hidden in the device?

<dontneedheadaches:telegram> > Even if some bits are not wiped, it is all encrypted. Good luck trying to restore any data without the key.)

<dontneedheadaches:telegram> Just re-install GrapheneOS.)

<hooly:tchncs.de> > <@grapheneosbridge:grapheneos.org> <dontneedheadaches:telegram> Tks for the awnser but is there not a easier way to delete all but keep graphenos? (re @GrapheneOSBridgeBot: <hooly:tchncs.de> > <@grapheneosbridge:grapheneos.org> <dontneedheadaches:telegram> Best and easiest way to wipe the phone? (re @GrapheneOSBridgeBot: <hooly:tchncs.de> > <@grapheneosbridge:grapheneos.org> <dontneedheadaches:telegram> Hello every

<hooly:tchncs.de> > > > if I for any reason want delete all on my phone with graphenos offcourse and reinstall all again am I sure there is no info leaked to the phone itself? I mean pics or chats or whatever can be found hidden in the device?

<hooly:tchncs.de> > > Even if some bits are not wiped, it is all encrypted. Good luck trying to restore any data without the key.)

<hooly:tchncs.de> > Just re-install GrapheneOS.)

<hooly:tchncs.de>

<hooly:tchncs.de> Factory-reset?

<dontneedheadaches:telegram> But factory reset will delete graphenos asswell I guess

<hooly:tchncs.de> Someone correct me if I'm wrong, but I'm pretty confident that it does not.

<hooly:tchncs.de> "When you do a factory reset, regardless of the ROM installed, it erases the /data and /cache partitions of the phone. If you modified the /system partition (remove bloat) it will not undo those modifications. To return to a true factory state, you would need to run an official OEM utilitity, such as an RUU for HTC devices."

<hooly:tchncs.de>

<hooly:tchncs.de> forum.xda-developers.com/t/q-factor…et-is-resetting-current-rom.1668623

<ghostsplintersix:matrix.org> What does the website say?

<hooly:tchncs.de> If you use factory-reset with a custom ROM, it is like you just flashed that custom ROM.

<dontneedheadaches:telegram> Ok thanks a Lott guys

<dontneedheadaches:telegram> But to be extra sure nothing will be left I can do it 2-3 times?

<dontneedheadaches:telegram> Lol

<dontneedheadaches:telegram> Like my nick Says I don’t like headaches

<dontneedheadaches:telegram> Hehe

<hainslow:matrix.org> > <@hooly:tchncs.de> Try flashing the stock ROM and installing updates, in case Lineage doesn't include some firmware updates.

<hainslow:matrix.org>

<hainslow:matrix.org> Is this the right guide for that: developers.google.com/android/images

<hooly:tchncs.de> > <@hainslow:matrix.org> Is this the right guide for that: developers.google.com/android/images

<hooly:tchncs.de>

<hooly:tchncs.de> Yes.

<hainslow:matrix.org> > <@hooly:tchncs.de> Yes.

<hainslow:matrix.org>

<hainslow:matrix.org> Thanks a lot!

<eisiem:matrix.org> Hi everyone! [PopOS (Ubuntu/Debian), Pixel 4a, Web installer]. I just enabled OEM unlocking and USB debugging, and installed android-sdk-platform-tools-common. However, when I reboot into the bootloader interface, it displays (among other things) "Device state: locked".

<qwertbert:matrix.org> That is to be expected, as the OEM unlocking toggle just allows you to unlock the bootloader and doesn't by itself do so.

<qwertbert:matrix.org> grapheneos.org/install

<eisiem:matrix.org> I see. But then when I click "Unlock bootloader" it says it can't find compatible devices. Also running lsblk doesn't show the phone. Could it be related to the "udev rules" thing? I didn't get what I have to do on that point.

<catfishes:matrix.org> eisiem: did you do this? On Debian and Ubuntu, install the android-sdk-platform-tools-common package.

<eisiem:matrix.org> Yes I did. Is there any problem if the web browser is on a flatpak?

<catfishes:matrix.org> I'm not sure. PopOS is not officially supported. Do you have another phone you could try the install usb-c to usb-c

<hainslow:matrix.org> I'm stuck at "Unlocking the boatloader" (web installer). Pressing the button results in --> Error: Timeout of 10000 ms exceeded. Can anyone help? Using a Pixel 3, USB-C to USB-C, Manjaro Linux

<eisiem:matrix.org> > <@catfishes:matrix.org> I'm not sure. PopOS is not officially supported. Do you have another phone you could try the install usb-c to usb-c

<eisiem:matrix.org>

<eisiem:matrix.org> Yeah, I'll try that

<hainslow:matrix.org> > <@hainslow:matrix.org> I'm stuck at "Unlocking the boatloader" (web installer). Pressing the button results in --> Error: Timeout of 10000 ms exceeded. Can anyone help? Using a Pixel 3, USB-C to USB-C, Manjaro Linux

<hainslow:matrix.org>

<hainslow:matrix.org> Nevermind, reconnection USB solved it.

<eisiem:matrix.org> > <@eisiem:matrix.org> Yeah, I'll try that

<eisiem:matrix.org>

<eisiem:matrix.org> Tried with a not contained web browser and now it works

<strcat:grapheneos.org> snap doesn't contain it just breaks WebUSB

<eisiem:matrix.org> Not snap, but flatpak

<strcat:grapheneos.org> even less "contained" then

<eisiem:matrix.org> But not broken. It would be nice to know what restriction is preventing the web browser from finding the device, and write it on the guide

<eisiem:matrix.org> (So you can disable that restriction)

<strcat:grapheneos.org> it's not an officially supported OS / browser

<strcat:grapheneos.org> we aren't going to be covering every random little Linux distribution / fork

<eisiem:matrix.org> Bro, it's chromium on ubuntu

<strcat:grapheneos.org> Chromium on Ubuntu does not use Flatpak

<strcat:grapheneos.org> and is already listed in the guide as not supported

<eisiem:matrix.org> > <@strcat:grapheneos.org> Chromium on Ubuntu does not use Flatpak

<eisiem:matrix.org>

<eisiem:matrix.org> It does if you want

<madaidan.:matrix.org> > <@strcat:grapheneos.org> even less "contained" then

<madaidan.:matrix.org>

<madaidan.:matrix.org> They disable Chromium's Layer-1 sandbox and replace it with Flatpak lol

<strcat:grapheneos.org> ...

<eisiem:matrix.org> It doesn't come by default on mainstream Ubuntu, but it's a flatpak, you can run it on almost every Linux distro. Including Arch, which is supported (I think).

<strcat:grapheneos.org> so it's the opposed of 'contained'

<strcat:grapheneos.org> they take a working sandbox and break it

<strcat:grapheneos.org> nice

<strcat:grapheneos.org> eisiem: we aren't supporting that

<madaidan.:matrix.org> github.com/flathub/org.chromium.Chr…k-Add-initial-sandbox-support.patch

<eisiem:matrix.org> It's okay if you don't want to support it. But if I find the way to do it with flatpaks, would you write on the guide as a tip or something?

<strcat:grapheneos.org> o

<strcat:grapheneos.org> no

<eisiem:matrix.org> :c

<thecannon:matrix.org> what's a layer 1 sandbox?

<madaidan.:matrix.org> > <@thecannon:matrix.org> what's a layer 1 sandbox?

<madaidan.:matrix.org>

<madaidan.:matrix.org> chromium.googlesource.com/chromium/…src/+/HEAD/docs/linux/sandboxing.md

<anupritaisno1:m.apex.to> thecannon: internal chromium stuff essentially

<lelmister101:matrix.org> >They disable Chromium's Layer-1 sandbox and replace it with Flatpak lol

<lelmister101:matrix.org>

<lelmister101:matrix.org> lol

<st4rpixel:matrix.org> > <@sb13x:matrix.org> Settings>Security>Auto Reboot and select how often you want your device to restart when left idle at the lockscreen for.

<st4rpixel:matrix.org>

<st4rpixel:matrix.org> Dont see it on my P4a recent update..

<st4rpixel:matrix.org> RQ3A.210605.005.2021.06.09.13

<leeya:kde.org> > <@st4rpixel:matrix.org> Dont see it on my P4a recent update..

<leeya:kde.org> > RQ3A.210605.005.2021.06.09.13

<leeya:kde.org>

<leeya:kde.org> Only on Owner User

<leeya:kde.org> (Maybe you're looking on secondary users, which neither deny USB nor Auto Reboot option is present there)

<hainslow:matrix.org> Hey, freshly installed and noticed that more than 100 weird Apps have permissions for sensors. Can anyone clarify why's that?

<strcat:grapheneos.org> there are no "weird apps" with sensors permission

<strcat:grapheneos.org> you're misunderstanding something

<strcat:grapheneos.org> I strongly recommend not disabling permissions for base OS components, they shouldn't be shown there but that's how the UI works right now

<strcat:grapheneos.org> Sensors and Network are permissions added by GrapheneOS

<strcat:grapheneos.org> apps don't declare if they need sensors access so it has to add the toggle for every app

<strcat:grapheneos.org> on the stock OS or on iOS you simply don't have the option available at all

<strcat:grapheneos.org> you're just looking at a list of every app-based component and app because it has to be assumed every app needs it right now

<strcat:grapheneos.org> base OS components shouldn't be shown there by default but that's what the standard Settings app does by default

<strcat:grapheneos.org> not our UI

<strcat:grapheneos.org> not our UI design

<hainslow:matrix.org> Thanks. I'm not disabling. It looked just weird in the permission manager/overview to have one entry with more than 100 permissions.

<strcat:grapheneos.org> because base OS components shouldn't be shown there (by default, at least)

<strcat:grapheneos.org> but they are

<strcat:grapheneos.org> you can see the same thing for other permissions including that you can break the permission manager and package manager by removing their "usage stats" permission

<hainslow:matrix.org> allright. thanks for clarifying!

<coastguard:matrix.org> When having a new pixel 4a and a new sim, do i need to activate it somehow with stock os before fladnshing grapheneos?

<strcat:grapheneos.org> no

<coastguard:matrix.org> Updating to latest stock before flashing is to make sure the processu goes well or are there things later on that aren't updated with grapheneos?

<strcat:grapheneos.org> covered in install guide

<strcat:grapheneos.org> everything is updated by GrapheneOS

<strcat:grapheneos.org> the reason we recommend updating stock first is to have the latest firmware with all the bug fixes / improvements for flashing via fastboot

<coastguard:matrix.org> Ok thanks

<strcat:grapheneos.org> this is what the install guides say

<strcat:grapheneos.org> > It's best practice to update the device before installing GrapheneOS to have the latest firmware for connecting the phone to the computer and performing the early flashing process. Either way, GrapheneOS flashes the latest firmware early in the installation process.

<strcat:grapheneos.org> I think it's clear

<auckland:matrix.org> Hi, I saw the official website statement regarding pixel 4 no longer being supported and updated.

<auckland:matrix.org> :(

<auckland:matrix.org> Why not though.

<strcat:grapheneos.org> that's untrue

<auckland:matrix.org> wait

<strcat:grapheneos.org> there is no such statement on the website

<auckland:matrix.org> One second.

<auckland:matrix.org> "The Pixel 4 and Pixel 4 XL have comparable security but won't be supported as long".

<auckland:matrix.org> grapheneos.org/faq#supported-devices

<auckland:matrix.org> :(

<strcat:grapheneos.org> obviously older devices won't be supported as long

<strcat:grapheneos.org> what you claimed above is not stated on the state

<strcat:grapheneos.org> what you claimed above is not stated on the site

<auckland:matrix.org> Can you put a figure or a number on how longer theyll be maintained.

<auckland:matrix.org> Can you put a figure or a number on how much longer theyll be maintained.

<strcat:grapheneos.org> 5th generation will be supported for at least around 1 year longer

<strcat:grapheneos.org> since it came out 1 year later and has the same guaranteed support time

<strcat:grapheneos.org> 6th generation may have an extra year of support, making that 3 years longer (2 years later + 1 year extra support potentially)

<strcat:grapheneos.org> that's how things work

<strcat:grapheneos.org> newer devices have a newer SoC generation / other hardware and better security

<strcat:grapheneos.org> nowhere on the site does it say that Pixel 4 is legacy or being dropped

<auckland:matrix.org> But maybe it's not as risky as some people like to put it when using unsupported graphene oses on older devices - Maybe it just means that some bugs may arise or hardware vulnerabilities, but that could be a stretch- and if it does maybe it will affect the next gen versions too anyways?

<auckland:matrix.org> But maybe it's not as risky as some people like to put it when using unsupported graphene oses on older devices? Maybe it just means that some bugs may arise or hardware vulnerabilities, but that could be a stretch? And if it does maybe it will affect the next gen versions too anyways?

<strcat:grapheneos.org> the Pixel 4 is not legacy or supported

<strcat:grapheneos.org> the Pixel 4 is not legacy or unsupported

<strcat:grapheneos.org> Pixel 3 is not unsupported

<auckland:matrix.org> Not yet.

<strcat:grapheneos.org> it's entirely insecure to use a Pixel 2 and there is no official GrapheneOS support for it, only extended support releases

<strcat:grapheneos.org> Mr. Aucklander.: every device will eventually be EOL at which point they become increasingly insecure to use until there is practically zero privacy and secure left like the Pixel 2

<strcat:grapheneos.org> Mr. Aucklander.: every device will eventually be EOL at which point they become increasingly insecure to use until there is practically zero privacy and security left like the Pixel 2

<auckland:matrix.org> darn

<strcat:grapheneos.org> most laptops stop receiving those updates within 1 year

<strcat:grapheneos.org> some marketed as 'secure' ship insecure from day 1

<auckland:matrix.org> I' probably should not buy pixel 4 as a gift, then.

<strcat:grapheneos.org> we suggest only buying 4a (5G) and 5 at this point

<strcat:grapheneos.org> potentially 4a

<ghostsplintersix:matrix.org> The 4a is a great device.

<fierybinary:matrix.org> either way, if your phone no longer receives updates, don't throw it away

<fierybinary:matrix.org> just give it to someone who needs it, maybe someone in a poor country, some poor kid in America, etc

<fierybinary:matrix.org> just give it to someone who needs it, maybe someone in a poor country, some poor kid in a developoed country too, etc

<auckland:matrix.org> Why though I can estimate my threat model in a controlled environment.

<adaptare:matrix.org> > <@strcat:grapheneos.org> we suggest only buying 4a (5G) and 5 at this point

<adaptare:matrix.org>

<adaptare:matrix.org> why? because they are newer and will receive longer support?

<strcat:grapheneos.org> grapheneos.org/faq#recommended-devices

<strcat:grapheneos.org> > The following devices offer the best hardware, firmware and software security along with the longest future support time and are strongly recommended:

<adaptare:matrix.org> but you wrote "potentially 4a"

<adaptare:matrix.org> looks like 4a is already bad ^^

<adaptare:matrix.org> looks like 4a is already bad choice to pick ^^

<strcat:grapheneos.org> 4a (5G) and 5 are a better choice

<adaptare:matrix.org> looks like 4a is already a bad choice to pick ^^

<auckland:matrix.org> > <@adaptare:matrix.org> looks like 4a is already a bad choice to pick ^^

<auckland:matrix.org>

<auckland:matrix.org> Based on what though? It still has years to go, roughly speaking, until it is out of support.

<Moof:telegram> You mean 2 years. I mean it's what, 3 months less as the 5 or 5g? (re @GrapheneOSBridgeBot: <auckland:matrix.org> > <@adaptare:matrix.org> looks like 4a is already a bad choice to pick ^^

<Moof:telegram> Based on what though? It still has years to go, roughly speaking, until it is out of support.)

<Moof:telegram> You mean 2 years. I mean it's what, 3 months less as the 5 or 4a 5g? (re @GrapheneOSBridgeBot: <auckland:matrix.org> > <@adaptare:matrix.org> looks like 4a is already a bad choice to pick ^^

<Moof:telegram> Based on what though? It still has years to go, roughly speaking, until it is out of support.)

<auckland:matrix.org> Although I would question Graphene OS's ability to disable some of the 5G notorious features.

<strcat:grapheneos.org> stop spreading misinformatiobn

<strcat:grapheneos.org> stop spreading misinformation

<strcat:grapheneos.org> Mr. Aucklander.: Pixel 4a (5G) and 5 offer the best security

<strcat:grapheneos.org> older devices are missing certain Spectre / other side channel protections among other things

<strcat:grapheneos.org> and other kernel hardening

<strcat:grapheneos.org> 4G -> 5G is comparable to 3G -> 4G and just like the other protocols even in the stock OS / AOSP you can choose the maximum protocol version

<strcat:grapheneos.org> all that GrapheneOS adds is 4G only mode to disable 2G/3G

<strcat:grapheneos.org> please do not post harmful misinformation in either channel that may result in at risk people being compromised / harmed, it's not a place for speculation

<stiffcliff:matrix.org> > <@strcat:grapheneos.org> older devices are missing certain Spectre / other side channel protections among other things

<stiffcliff:matrix.org>

<stiffcliff:matrix.org> So the pixel 4a (non 5g) falls under the older devices?

<strcat:grapheneos.org> yes, it's comparable to Pixel 4 / 4 XL security, just perhaps supported longer if those don't get extended to match it

<strcat:grapheneos.org> it's comparable to 4 / 4 XL not 4a (5G) / 5

<Atlantistux:telegram> If i install grapheneos, can i reinstall the standard Android Pixel rom ?

<strcat:grapheneos.org> just has longer guaranteed support based on launch date / slightly newer (but same generation) SoC

<strcat:grapheneos.org> @Atlantistux via their factory images

<strcat:grapheneos.org> our site explains how to remove the GrapheneOS signing key and then it's just the same thing as installing GrapheneOS but with their images

<Atlantistux:telegram> And where are the factory images ? (re @GrapheneOSBridgeBot: <strcat:grapheneos.org> @Atlantistux via their factory images)

<strcat:grapheneos.org> developers.google.com/android/images

<strcat:grapheneos.org> we're not able to provide support for stock OS or their docs / instructions here

<strcat:grapheneos.org> we're not able to provide support for stock OS or their docs / instructions / flasher here

<Atlantistux:telegram> Ok thanks (re @GrapheneOSBridgeBot: <strcat:grapheneos.org> developers.google.com/android/images)

<Atlantistux:telegram> I can backup with twrp ?

<strcat:grapheneos.org> no

<leeya:kde.org> GrapheneOS uses Seedvault as backup provider

<strcat:grapheneos.org> you can't use that with either GrapheneOS or the stock OS if you're actually fully using either

<strcat:grapheneos.org> please use the official install instructions and complete them or you aren't running GrapheneOS

<strcat:grapheneos.org> if Auditor doesn't pass and say you're running GrapheneOS, it isn't GrapheneOS

<Atlantistux:telegram> I can use twrp for save my pixel rom before the installation of grapheneos, no ??

<strcat:grapheneos.org> no

<strcat:grapheneos.org> don't know what you're talking about

<strcat:grapheneos.org> it's off-topic

<auckland:matrix.org> sure..

<strcat:grapheneos.org> you can't use that with GrapheneOS and you're not running the actual stock OS if you have it

<strcat:grapheneos.org> we're not able to provide support for the stock OS or modified variants of it here

<strcat:grapheneos.org> or modified variants / forks of GrapheneOS either

<Atlantistux:telegram> But if i sell my pixel, how reset with the standard default installation ?

<strcat:grapheneos.org> explained above

<strcat:grapheneos.org> when you first asked

<strcat:grapheneos.org> you remove the GrapheneOS signing key with our instructions on that, use their factory images to install their OS and lock it

<Atlantistux:telegram> Oh ok

<acronym:matrix.org> When using a USB stick to transfer files from one profile to another, is there a way to find the USB stick in files without having to unplug and reinsert USB when new profile opened?

<adaptare:matrix.org> seems very convenient (irony)... i use shelter for that, but I dunno if grapheneos endorses its use

<adaptare:matrix.org> you need to grand it system rights tho

<adaptare:matrix.org> and saving data on usb flash can be a weakness. you can't be sure if your data is /really/ deleted with usb drive flash memory (to my knowledge)

<leeya:kde.org> > <@adaptare:matrix.org> you need to grand it system rights tho

<leeya:kde.org>

<leeya:kde.org> Yeah, which is an issue on trusting an app to create a managed work profile

<leeya:kde.org> Recommendation is to use the AOSP Multiple Users option

<adaptare:matrix.org> > <@leeya:kde.org> Yeah, which is an issue on trusting an app to create a managed work profile

<adaptare:matrix.org>

<adaptare:matrix.org> hmmm i will check it out. thanks for the info :)

<strcat:grapheneos.org> acronym: you could just use an app to transfer between user profiles via localhost

<strcat:grapheneos.org> I don't have a particular recommendation but it works fine, ideally use something authenticated though

<strcat:grapheneos.org> USB is safer compared to doing it badly

<coffeehorrors:matrix.org> > <@strcat:grapheneos.org> all that GrapheneOS adds is 4G only mode to disable 2G/3G

<coffeehorrors:matrix.org>

<coffeehorrors:matrix.org> hi, probably a dumb question but is there any concern with using 5G? I'm using the LTE-only mode to lessen the legacy code used rn

<strcat:grapheneos.org> LTE only mode is LTE only so no 2G, 3G or 5G

<strcat:grapheneos.org> the only actual concern with 5G is added attack surface compared to only using 4G

<strcat:grapheneos.org> eventually 4G will be legacy code

<coffeehorrors:matrix.org> follow up to that then, if I switch from LTE-only to 5G then that would reallow the 2G/3G legacy code then yeah?

<strcat:grapheneos.org> yes because that means 5G and below

<strcat:grapheneos.org> like the 4G mode means 4G and below

<strcat:grapheneos.org> we don't have a 5G only mode atm

<strcat:grapheneos.org> and 5G coverage is generally not good enough for it to make sense

<strcat:grapheneos.org> also many people can't test it yet

<coffeehorrors:matrix.org> Ah, okay! Thank you! :D

<strcat:grapheneos.org> the only setting we add there is LTE (4G) only

<strcat:grapheneos.org> rest standard

<strcat:grapheneos.org> we also don't override carrier being able to say their network doesn't support changing the mode atm

<strcat:grapheneos.org> (few have that configuration)

<strcat:grapheneos.org> (it's hard-wired configuration the OS has to ship)

<strcat:grapheneos.org> Pixel 4a (5G) and Pixel 5 releases should be available and pushed out from beta to stable channel pretty quickly soon btw

<strcat:grapheneos.org> we just needed to address new upstream issues

<strcat:grapheneos.org> I have releases built which *could* be pushed already but we want to do cleaner workarounds in a way that doesn't screw people over trying to build from source with a really complex mess from AOSP

<acronym:matrix.org> > <@strcat:grapheneos.org> acronym: you could just use an app to transfer between user profiles via localhost

<acronym:matrix.org>

<acronym:matrix.org> I don't know how to do localhost, if you could give me a quick overview to point me in right direction to read and learn about how that works would appreciate it.

<acronym:matrix.org> If no time np, thanks.

<parisnice:matrix.org> Thanks for the new feature (reboot) much appreciated and a really useful feature. Now the only thing missing is a checkbox with the option to wipe the device.

<strcat:grapheneos.org> parisnice: extremely unlikely to add that

<strcat:grapheneos.org> parisnice: an adversary could turn off the device if they want to approach it that way (at rest)

<strcat:grapheneos.org> users will lose data including in ways that harms them

<strcat:grapheneos.org> users would lose data including in ways that harms them

<strcat:grapheneos.org> factory reset relies on the same encryption implementation to make data unrecoverable anyway

<strcat:grapheneos.org> the only risk of not wiping is brute forcing, and as long as your PIN or passphrase is random, it's either not possible (strong passphrase) or requires a very sophisticated attacker able to exploit secure element (even a 6+ digit random PIN is secure if they can't exploit secure element)

<parisnice:matrix.org> strcat: 👍

<strcat:grapheneos.org> factory reset just destroys material needed to derive key encryption key so data is totally unrecoverable regardless of what happens

<strcat:grapheneos.org> factory reset just destroys material needed to derive key encryption keys (for device as a whole and each profile) so data is totally unrecoverable regardless of what happens

<thecannon:matrix.org> cryptonuke

<st4rpixel:matrix.org> matrix.grapheneos.org/_matrix/media…matrix.org/spSgnpFfnNhTfKVSuNnMuEAJ

<st4rpixel:matrix.org> Anyone knows what "Wifi enhanced mac randomization does? And better to keep it on/off?

<st4rpixel:matrix.org> > <@strcat:grapheneos.org> factory reset just destroys material needed to derive key encryption keys (for device as a whole and each profile) so data is totally unrecoverable regardless of what happens

<st4rpixel:matrix.org>

<st4rpixel:matrix.org> Awesome!

<leeya:kde.org> WiFi MAC address already randomizes every time it reconnects by default on GrapheneOS

<leeya:kde.org> > <@st4rpixel:matrix.org> Anyone knows what "Wifi enhanced mac randomization does? And better to keep it on/off?

<leeya:kde.org>

<leeya:kde.org> There's no need to toggle that

<strcat:grapheneos.org> factory reset doesn't try to do some sketchy zeroing thing just wipes material needed for deriving key encryption keys (via secure element and TEE primarily) and makes a new partition

<strcat:grapheneos.org> so that data is truly gone even if you had a clone of the SSD

<strcat:grapheneos.org> you could clone the SSD, and know the PINs / passphrases

<flawedworld:matrix.org> > <@st4rpixel:matrix.org> sent an image.

<flawedworld:matrix.org>

<flawedworld:matrix.org> Developer options are for developers. Please bear this in mind. These options are not going to be supported and some can lead to additional attack surface.

<strcat:grapheneos.org> after factory reset, you can't get any useful data out of the cloned SSD image

<strcat:grapheneos.org> doesn't matter that you have the passphrases

<zanthed:eridan.me> > <@st4rpixel:matrix.org> Anyone knows what "Wifi enhanced mac randomization does? And better to keep it on/off?

<zanthed:eridan.me>

<zanthed:eridan.me> go by this general rule: if you don't think you need to enable or disable something in developer options, you probably don't need to touch it.

<strcat:grapheneos.org> the other stuff needed to derive keys is *gone*

<Jeremy:telegram> Is there any difference if i flash graphene from another graphene OS phone?

<strcat:grapheneos.org> st4rpixel: don't use that, it's an unsupported really weird thing

<strcat:grapheneos.org> st4rpixel: our default MAC rand is far better than what that does to the standard AOSP / stock MAC rand

<flawedworld:matrix.org> > <@grapheneosbridge:grapheneos.org> <Jeremy:telegram> Is there any difference if i flash graphene from another graphene OS phone?

<flawedworld:matrix.org>

<flawedworld:matrix.org> No it uses the same WebUSB installer as on the desktop.

<strcat:grapheneos.org> flashing from another Pixel with stock or GrapheneOS is definitely the most reliable way because it eliminates the possibility of broken drivers or software interfering with it

<strcat:grapheneos.org> and it's known it has proper USB-C

<strcat:grapheneos.org> if you buy 2 phones just flash one from the other via stock then the other one via GrapheneOS

<strcat:grapheneos.org> save yourself all the trouble of potential driver / USB port / USB-A to USB-C cable issues

<strcat:grapheneos.org> we could have an app included to flash phones with GrapheneOS with pinned keys for the download but it's not worth investing resources in that, far more important things to make

<zanthed:eridan.me> USB-A to USB-C is definitely a concerning thing for me 😅

<parisnice:matrix.org> Regarding the reboot feature, is it needed to log in to the owner profile with in the given hours? Or is it enough to log in to any profile?

<strcat:grapheneos.org> there are proper USB-A to USB-C cables

<strcat:grapheneos.org> but just assume random USB cables are broken, they usually are, and they're unsafe for charging

<strcat:grapheneos.org> don't use some random cable to charge via USB-C especially via wall charger

<strcat:grapheneos.org> and don't use a random wall charger ever

<strcat:grapheneos.org> if you don't want to burn down the building

<zanthed:eridan.me> don't plug your phone into random places period

<Hulk:telegram> afaik, logging into either of your profiles will reset the timer (re @GrapheneOSBridgeBot: <parisnice:matrix.org> Regarding the reboot feature, is it needed to log in to the owner profile with in the given hours? Or is it enough to log in to any profile?)

<Hulk:telegram> source: twitter.com/GrapheneOS/status/1402017381053079554

<stonjjohn:matrix.org> Does enabling ”Sensors Off" tile provide an benefit under Quick Setting Developer Tiles, say to block mic/camera access from questionable apps (not everyone has the skill set to determine if apps are nefarious or not?

<stonjjohn:matrix.org>

<stonjjohn:matrix.org> Also, can you shed some light on the security benefits of why the phone auto reboot was added in the last release...is this to mitigate against partial AFU attacks?

<stonjjohn:matrix.org> matrix.grapheneos.org/_matrix/media…matrix.org/PhdTfOpWuqFwbiRdVibzXSTK

<strcat:grapheneos.org> stonjjohn: apps don't have camera or microphone access without you granting it, and they never have access in the background

<strcat:grapheneos.org> stonjjohn: and you can use 'allow once' rather than granting 'allow while in use'

<strcat:grapheneos.org> which are the only 2 options

<strcat:grapheneos.org> we have a toggle for Sensors (the other types of sensors not covered by existing permissions) access and even in AOSP/stock, sensors access only works in foreground

<strcat:grapheneos.org> stonjjohn: Android 12 adds global toggles for Camera / Microphone similar to the one for Location, and to be clear, those only control whether the permission works

<linus:midov.pl> you also cant use auto brightness if sensors are disabled system wide, better to just do it on per-app basis

<strcat:grapheneos.org> there is already a permission

<strcat:grapheneos.org> you should just be using allow once most of the time

<strcat:grapheneos.org> for camera, microphone, location

<strcat:grapheneos.org> allows for that usage session of the app, goes away after

<strcat:grapheneos.org> the *only* other option for camera/microphone is to allow *while in use* (foreground)

<strcat:grapheneos.org> makes sense for the actual camera app

<strcat:grapheneos.org> apps can just open the camera app and have you take a picture for them (which is what gives the consent) without needing the permission if they aren't control freaks about the UI

<strcat:grapheneos.org> the only reason something actually needs Camera is if it's a camera app or they do something like filters, beyond that it's just them wanting to control the UI

<stonjjohn:matrix.org> Thank you for the insight!🙂

<stonjjohn:matrix.org> Can you shed some light on the security benefits of why the phone auto reboot was added in the last release...is this to mitigate against partial AFU attacks?

<Hulk:telegram> you can read about it here twitter.com/GrapheneOS/status/1402017381053079554 (re @GrapheneOSBridgeBot: <stonjjohn:matrix.org> Can you shed some light on the security benefits of why the phone auto reboot was added in the last release...is this to mitigate against partial AFU attacks?)

<stonjjohn:matrix.org> > <@grapheneosbridge:grapheneos.org> <Hulk:telegram> you can read about it here twitter.com/GrapheneOS/status/1402017381053079554 (re @GrapheneOSBridgeBot: <stonjjohn:matrix.org> Can you shed some light on the security benefits of why the phone auto reboot was added in the last release...is this to mitigate against partial AFU attacks?)

<stonjjohn:matrix.org>

<stonjjohn:matrix.org> Yup, that is what I suspected they were mitigating against! Thanks!

<hainslow:matrix.org> hi, is it possible to move the status bar clock to the center? I remember I had it centered on stock Android 11 or LOS18.1. thanks!

<sb13x:matrix.org> > <@hainslow:matrix.org> hi, is it possible to move the status bar clock to the center? I remember I had it centered on stock Android 11 or LOS18.1. thanks!

<sb13x:matrix.org>

<sb13x:matrix.org> Not possible as it stands AFAIK I'm afraid. You could open an issue however it will also likely be low priority.

<hainslow:matrix.org> > <@sb13x:matrix.org> Not possible as it stands AFAIK I'm afraid. You could open an issue however it will also likely be low priority.

<hainslow:matrix.org>

<hainslow:matrix.org> Thanks for clarifying!

<stonjjohn:matrix.org> Does enabling Developer Mode and leaving it enabled increase the attack surface?

<strcat:grapheneos.org> stonjjohn: well enabling it requires entering passphrase

<strcat:grapheneos.org> if it's already enabled someone who gets device unlocked can turn on adb and extract stuff with it

<strcat:grapheneos.org> you should ideally have it off on production device

<strcat:grapheneos.org> lot of risky / dangerous features in dev options too

<strcat:grapheneos.org> just enable it to disable oem unlocking then turn it off

<st4rpixel:matrix.org> > <@strcat:grapheneos.org> just enable it to disable oem unlocking then turn it off

<st4rpixel:matrix.org>

<st4rpixel:matrix.org> Then disable oem unlock before disabling dev tools, isnt?

<strcat:grapheneos.org> that's what I said

<hainslow:matrix.org> Hi, is it possible to customize what'll appear on the screen after booting up? Is there a way to get rid of the "you're starting a different OS" message and/or the Google logo? Thanks a lot!

<strcat:grapheneos.org> no

<strcat:grapheneos.org> it would be a security vulnerability if you could replace the verified boot UI

<strcat:grapheneos.org> on a device built to run GrapheneOS, it would display no message when booting the official GrapheneOS release

<strcat:grapheneos.org> and would display that when the device is locked + using a non-built-in key flashed to the secure element to verify the OS

<ghostsplintersix:matrix.org> I just bought my Dad a Pixel 4a for Father's Day and he'll be using GrapheneOS on it. 👍🏻

<hainslow:matrix.org> > <@strcat:grapheneos.org> and would display that when the device is locked + using a non-built-in key flashed to the secure element to verify the OS

<hainslow:matrix.org>

<hainslow:matrix.org> Thanks!

<fierybinary:matrix.org> > <@ghostsplintersix:matrix.org> I just bought my Dad a Pixel 4a for Father's Day and he'll be using GrapheneOS on it. 👍🏻

<fierybinary:matrix.org>

<fierybinary:matrix.org> nice!

<ghostsplintersix:matrix.org> My Dad wants to distance himself from Big Tech and I've been working on my Mom.

<jandroid:matrix.org> Hello, are the APN settings coming from the ROM? With my Spectrum SIM card, the APN settings are different between stock and Graphene

<jandroid:matrix.org> On stock, I see settings version as "spectrum_us-2500000000471.31" . On Graphene, I see it as "verizon_us-250000000096.45"

<jandroid:matrix.org> Also, the APN name is different: VZWINTERNET (stock) vs CHARTER.RSLR.VZWENTP

<strcat:grapheneos.org> GrapheneOS isn't a ROM, it's an OS

<strcat:grapheneos.org> the boot ROM isn't shipped with the OS

<strcat:grapheneos.org> it's a ROM, can't be updated

<strcat:grapheneos.org> APN database and carrier settings database are part of the OS

<strcat:grapheneos.org> based on the stock OS, but they probably update it via Play Store

<jandroid:matrix.org> I see, so the settings aren't carried over from the stock OS somehow.

<jandroid:matrix.org> Oh, I think I understand, so you think it is updated post install of the OS

<jandroid:matrix.org> As a side note, I tested CalyxOS and the behavior is the same as GrapheneOS. It doesn't connect to the network and APN settings are the same

<auckland:matrix.org> > <@ghostsplintersix:matrix.org> I just bought my Dad a Pixel 4a for Father's Day and he'll be using GrapheneOS on it. 👍🏻

<auckland:matrix.org>

<auckland:matrix.org> Im a lil convinced now.

<strcat:grapheneos.org> jandroid: zero stock OS data is kept from when you had that installed, nothing would be carried over

<strcat:grapheneos.org> jandroid: and please don't talk about that malicious project here

<strcat:grapheneos.org> jandroid: our APN / carrier config databases are from what's included in the stock OS *without* updates to those apps from Google Play (CarrierSettings, CarrierConfig)

<strcat:grapheneos.org> so they may lag behind what they have with updates from Play since they don't always keep the base OS ones very up-to-date

<strcat:grapheneos.org> not really unexpected

<strcat:grapheneos.org> carriers changing things in weird backwards compatible ways all the time is unfortunate

<strcat:grapheneos.org> and need all that non-standard hard-wired config at all

<jandroid:matrix.org> Ok, so, there's no way to make this work for now, I assume, other than to wait.

<auckland:matrix.org> It's true though. If I'd picked any device to gift to someone, while keeping in mind security and privacy, I'd choice to google pixel over the others. Even though it's probably true that at some point some of the late versions are going to get out of support, it is still possible to maintain them in some other means (myself for example), and possibly by other open source privacy and security focused OS/ Rom devel

<auckland:matrix.org> It's true though. If I'd picked any device to gift to someone, while keeping in mind security and privacy, I'd choice to google pixel over the others. Even though it's probably true that at some point some of the late versions are going to get out of support, it is still possible to maintain them in some other means (myself for example), and possibly by other open source privacy and security oriented OS/ Rom deve

<auckland:matrix.org> Oh and graphene OS is very inspiring.

<anon748283:matrix.org> Hello, the last update on the 3a ended in bootloop

<strcat:grapheneos.org> anon748283: unlikely to be caused by the update

<strcat:grapheneos.org> probably a hardware failure

<strcat:grapheneos.org> the update will automatically be rolled back if it doesn't boot N times

<auckland:matrix.org> - I think I would like to expand on the concept alil personally and see how other devices behave when booted onto different OSes (I'm looking straight into apple's devices that are lying uselessly around in my room).

<strcat:grapheneos.org> 3a has low quality storage with a high failure rate at this point

<anon748283:matrix.org> What do you recommend as a solution? Thank you

<strcat:grapheneos.org> anon748283: force it to reboot a few times

<strcat:grapheneos.org> it will roll back the update

<strcat:grapheneos.org> if it's not booting even after that then the device is dead from hardware failure as I said is likely

<strcat:grapheneos.org> even if the update does roll back, the reason it didn't work was probably hardware failure

<strcat:grapheneos.org> it's not like you have a different device than everyone else

<strcat:grapheneos.org> and every installation of the firmware + GrapheneOS is bit-for-bit identical

<strcat:grapheneos.org> you have exactly the same firmware/OS as other 3a users, exactly the same, every bit

<strcat:grapheneos.org> every bit in the images, not just file content

<strcat:grapheneos.org> it's not really possible that it doesn't boot to late userspace without there being a hardware issue due to that

<strcat:grapheneos.org> it could somehow kernel panic reading data, or whatever

<strcat:grapheneos.org> but if it's dying early in boot it's a hardware failure

<strcat:grapheneos.org> depends how far it gets

<strcat:grapheneos.org> anyway, either way, it would roll back the update if it's not dead and boot old version

<anon748283:matrix.org> Ok thank you very much for your answer

<strcat:grapheneos.org> anon748283: if it has boot looped already a dozen times then it should have already rolled back since it's a number like 1-5 failures (varies by device model)

<strcat:grapheneos.org> and then after it rolls back installing update again may work since the bad areas of the storage won't be reused

<strcat:grapheneos.org> still a really bad sign

<strcat:grapheneos.org> happens to maybe 1% of 3a at this point

<anon748283:matrix.org> I left the loop running for an hour last night and played it again this morning via adb, same problem.

<anon748283:matrix.org> At first, I thought I was getting hacked

<anon748283:matrix.org> I'm going to switch to pixel 5 anyway.

<anon748283:matrix.org> Thanks

<basedmeow:matrix.org> > <@anon748283:matrix.org> I left the loop running for an hour last night and played it again this morning via adb, same problem.

<basedmeow:matrix.org> > At first, I thought I was getting hacked

<basedmeow:matrix.org> > I'm going to switch to pixel 5 anyway.

<basedmeow:matrix.org> > Thanks

<basedmeow:matrix.org>

<basedmeow:matrix.org> Good choice

<kernel_forge:telegram> Hey guys

<kernel_forge:telegram> Do you know if the installation works well on Xiaomi devices?

<sb13x:matrix.org> > <@grapheneosbridge:grapheneos.org> <kernel_forge:telegram> Do you know if the installation works well on Xiaomi devices?

<sb13x:matrix.org>

<sb13x:matrix.org> Xiaomi devices are not supported.

<sb13x:matrix.org> grapheneos.org/faq#supported-devices

<sb13x:matrix.org> > <@grapheneosbridge:grapheneos.org> <kernel_forge:telegram> Do you know if the installation works well on Xiaomi devices?

<sb13x:matrix.org>

<sb13x:matrix.org> Unless you're referring to using a Xiaomi to install onto a Pixel?>

<nescientone:matrix.org> Is there any way to reset a PIN password on a user profile from the owner profile? I inexplicably am running into issues with a 4 digit code I've had for a profile that I've used for months and also use across various other low-risk profiles

<nescientone:matrix.org> Is there any way to reset a PIN password on a user profile from the owner profile?

<strcat:grapheneos.org> nescientone: no, read grapheneos.org/faq#encryption

<strcat:grapheneos.org> you have to delete it if you don't know the password

<strcat:grapheneos.org> file names and data are encrypted with a per-profile key tied to lock method

<strcat:grapheneos.org> don't have lock method -> don't have key to decrypt file names / data for the profile

<strcat:grapheneos.org> all the OS is inherently able to do without that is delete all the files since it does know how big the data / metadata is but not what's inside it (and it's padded out)

<strcat:grapheneos.org> all the OS is inherently able to do without that is delete all the files since it does know how big the data / file names are but not what's inside it (and it's padded out)

<nescientone:matrix.org> Got it, thank you