@Exhort14 Thanks, I've cited your positive feedback. If you own a GitHub account please post directly in the respective issue next time, that makes it easier for everyone to keep track. If you don't have one that's fine too, in that case ping/message me or akc3n so we don't miss it.
spring-onion
- Joined Mar 30, 2023
Tasty!
Community moderator for GrapheneOS.
Matrix: @spring-onion:matrix.org
Discord: .spring.onion.
Please try following the instructions found in this comment.
[deleted] No worries I don't think anyone took it that way, including me.
- Edited
We've been going since 2014, plenty of our improvements have landed upstream, multiple high profile individuals endorse us and we have overcome a malicious takeover attempt that was aimed at selling you out.
Also, since we're on topic already: https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
Hi. Switch browsers, Firefox doesn't support web usb functionality.
- Edited
That's because you have at least one other instance of the web installer open, get rid of the extra ones.
Incognito tab perhaps? Does the hard drive of your computer have at least 32 GB free?
Hello!
Refresh the browser tab and on your phone, hold the volume down button while it's starting so you get into fastboot mode again. From there you can restart the installation. Skip the unlock bootloader step since you've done that already.
At what point did the installation go wrong? Connect the phone to your computer with the included usb-c to usb-c cable if possible, it's known to be compatible.
Viewpoint0232 Stupid question but if you enable "automatic reboot", will the alarm still go off in the morning?
grapheneos-enthusiast the alarm won't work if your phone is in BFU state (after reboot), that's why is not advisable to enable auto reboot if you rely on your phone for morning alarms
Yes it does, assuming you're using the included clock app and the owner profile to set it. Third party clocks can do it too, they just need to support direct boot. Secondary profiles are not suitable for this because they can't be started separately from the owner.
- In HELP
OEM unlocking can not be turned off while the bootloader is unlocked, that's working as intended.
You're on Ubuntu, check Brave isn't installed as a snap. Avoid flatpak too.
sir_brickalot do I understand you correctly, that security improvements != security patches?
Oh, no I used that synonymously.
sir_brickalot So the older version could be relatively safe but high value targets should probably instantly upgrade and get a big fat warning or something?
Important to note is that for pixels, there is only the one update path, and that is to the newest Android version. There is no sort of sidegrading here, you don't get these inferior backports. And we are obviously not interested in doing that for devices that are perfectly in support. So you would be immediately running an unsupported, end-of-life release. It won't kill you if you were to update 2 days later, but the only path is straight ahead. It's why Google has gone over to officially advertise that their now 7 years of support also include all Android releases; less work involved by not dealing with ugly backports and legacy branches. The pixel 6 and 7 line-up is very likely to get the same treatment for the same reason.
sir_brickalot I still think think it could be beneficial for users to have the option to choose the time of the upgrade on major upgrades
You can disable the updater if you wish, security wise the earlier you update the better. It is a delicate procedure, but we don't just throw it at you and have you deal with any major fallouts, this time around we had many consecutive releases to iron out the biggest flaws.
sir_brickalot I’m not aware of any major operating system that automatically upgrades from one major version to the next without user input.
Well, here we are.
sir_brickalot Syncthing for Android development has been discontinued
Holding onto it won't turn back the time, better find a replacement sooner than later.
- Edited
Hello!
By far not everything is backported to older Android releases. You must be on the very latest version to have all security improvements applied, that's why it's so crucial to port our features as quickly as possible. That is painful at times because upstream bugs get in your way too but not much you can do about that, it's necessary.
- Edited
Hello!
DinaricZoomer My banking app is activated by it sending an sms to my phone. It does not give me a code that I manually enter, but it activates itself upon receiving the message.
That should work if you give google play the sms permission.
Fully functional on my 7a.
custardbomb 3rd party launchers must first add support for it, but it's possible.
OEM unlocking does not unlock the bootloader, it allows the bootloader to be unlocked. So head back into fastboot, hit the unlock bootloader button, confirm that action on your phone, then you can remove the key and finally use Google's web installer.
You can try a factory reset, sometimes that helps. But chances are high the device was issued by a carrier, likely Verizon, who never allows OEM unlocking, even if the device is paid off. If you bought the device just now I suggest you return it. The pixel 4 XL is end of life by the way, you should get a more recent device.
- Edited
To what degree is your wife interested in changing the way she handles her digital life? The answer to that question will heavily weigh in on the setup deployed. If she's not all that invested the play store route is totally fine, that way you avoid unexpected outcomes like apps behaving differently than normal, etc. Things can always be moved around if she grows more keen as time goes on.
[deleted] Would there be any negatives/downsides to not updating to the latest firmware beforehand? Just to confirm.
Your phone won't behave any different once it's all done.
Welcome!
NFC functionality is supported on GrapheneOS, but unfortunately many banks rely on Google Pay for mobile payments, which will not work at this point of time because GrapheneOS isn't certified by Google. If your bank offers its own implementation, chances are high you won't face any issues.
We have a maintained compatibility list for banking and various authentication apps that gives you an idea which ones are expected to work and what workarounds you may need to apply. The government one you mentioned isn't on the list yet - maybe you could file a report for it in the future - but I did find you this forum post from march this year. Looks like getting it up and running isn't difficult.
RCS is a little flaky at the minute but can be successfully setup. Work is already underway to make this easier for everyone.