upvote
GrapheneOS includes an encrypted backup system covering far more data than Google cloud backups. It backs up data for apps opting out of cloud backups with allowBackup="false" since it operates in the device-to-device transfer mode. The backup system supports arbitrary sync services with a compatible API. Backups are per-profile so you can test it by restoring to a secondary user.

We plan to entirely overhaul the backup system but it already works fine. It could be a lot simpler and cleaner both in terms of implementation and user experience. We're in the process of overhauling the other apps first but we'll get to it.

reply
One clarification:

> It backs up data for apps opting out of cloud backups with allowBackup="false"

This is untrue for older apps targeting API 30 (Android 11) and earlier. As I understand it, allowBackup is still respected for them, preventing their backup even in D2D mode. https://github.com/GrapheneOS/os-issue-tracker/issues/1112#i...

Those apps are slowly going extinct since the Play Store stopped accepting updates written against the older SDK in 2022, but I gather there are still a few floating around out there (including some niche favorites that have unfortunately abandoned development).

And one wish:

I'd love the ability to maintain a "hotspare" device that's identical to the original in every important way. So if your phone is chucked in the ocean, dropped down a cliff, etc. you can just grab the other one (checkpointed from a few hours or a day ago) and seamlessly keep on going.

I think this is impossible today because of the way the system protects secrets in the Android Keystore and how it's intertwined with the TEE / secure element / Titan M2 / etc. I wish there were a way to truly own my phone including the ability to perform perfect-fidelity backup and restore.

reply
thanks for chiming in.
reply
reply
> the project has been taken over by another group of people not sharing our goals or approach

> Seedvault which was originally written for use in GrapheneOS by a GrapheneOS user is a consequence of the 2018 takeover attempt on the project, which the people currently in defacto control of Seedvault were heavily involved in.

Seedvault is currently maintained by the CalyxOS team but I've never heard about this stuff. Does anybody know what happened?

reply
There has been a lot of conflict between Calyx and GrapheneOS a while ago.
reply
[flagged]
reply
Yeah, it's planned for years and years at this point.

Sure I know there are more urgent priorities but at the moment there is no backup for GOS phones. It only works for some people in some situations. For me it never reliably worked, ever.

reply
Neat, I didn't realize it was still included. I thought it had been abandonned.

So basically one needs a webdav server somewhere or an usb flash drive.

reply
The problem is that most apps opt out of backup, so it's effectively useless.
reply
Yeah I don't even understand why this is even a thing. It should be user's choice, not app vendor/developer's choice.
reply
Android 12 changed the meaning of allowBackup="false" to opting out of cloud backups. GrapheneOS encrypted backups use the device-to-device transfer mode which includes apps opted out of cloud backups. It's similar to the Google Play data transfer feature, not Google's backup system.
reply
Android 12 changed the meaning of allowBackup="false" to opting out of cloud backups. GrapheneOS encrypted backups use the device-to-device transfer mode which includes apps opted out of cloud backups. It's similar to the Google Play data transfer feature, not Google's backup system.
reply
That still doesn't prevent other means that developers have to thwart backups. Chrome and vanadium has a custom backup agent that only dumps out settings, so browsing history and bookmarks aren't backed up at all. I believe firefox is similar unless they changed something recently. Same goes for other apps like signal. Browsers, messengers, and camera are the top 3 categories of apps I use on my phone, and the built-in backup gets 1/3 of them (camera actually works because it's just regular internal storage). That's not very good coverage.
reply
Vanadium will add more data to the device-to-device backups but we haven't gotten to it yet.

For Signal, you can set up their own backups locally and they'll be included with backed up home directory data if that's enabled. Signal encrypts their database and encrypts the key used for it with the hardware keystore. A generic backup system can't back that up directly. The encrypted database is useless outside of the current app install since the hardware keystore key can't be exported.

reply
I use Seedvault to create a backup locally on my phone, and then sync it to my backup server with Syncthing
reply
I use local seedvault backup and then sync via round sync daily trigger to my Nextcloud WebDav Server (native seedvault was not able to use this, for some reason).
reply
It's been planned for years...
reply
TTS has also been planned for a while and they released it recently. Donating or helping out is going to do more than complaining on HN.
reply
TTS is also in the process of being massively improved. What we've included is only an initial bare minimum implementation. We also plan to add speech-to-text but we may only support using existing models for it since it's harder and a model doesn't need to be bundled with the OS for accessibility.
reply
[flagged]
reply
I think more useful would be to be able to boot into another data partition with a different password, which, in turn, would hide the other "daily" partition. I believe LUKS is capable of that. The storage dump looks like a random set of data and only a valid password can find and decrypt a matching hidden partition.

Ideally this should also work on lock screen, e.g. if you type in a non-standard PIN, it would boot from the "dummy" partition in the background, with a slight delay perhaps.

This way you don't have backup anything (I mean you should, but for normal purposes) and have a plausible deniability whenever you get randomly inspected, not just at border crossings that you anticipate.

reply
>I believe LUKS is capable of that

Booting into a 30 GB partition on a 128GB phone is going to be mega suspicious, even if the remaining data is random.

reply
A partition based on a sparse disk image might avoid that.

You'd have what appears to be a 128GB image (or some large fraction of that), which in reality is largely holes (typically: repeated blocks of ASCII 00 bytes).

Of course, you'd need to avoid actually trying to fill that filesystem.

reply
There are ways around it AFAIK.
reply
There really isn't. You can try avoid the "30GB volume on 128GB phone" problem by putting the hidden volume inside the free space of another volume, but since the outer volume doesn't know about the hidden, you have to be very careful not to overwrite the inner volume contents. The safest way would just be to not use the outer volume, but that's also suspicious. Who carriers around a phone that doesn't have any activity for months/years? Not to mention trim/discard means that free space will get wiped by default, and disabling it also makes you stick out like a sore thumb.

You're better off traveling with a wiped phone, and restoring from backup after you've crossed.

reply
Who carriers around a phone that doesn't have any activity for months/years?

An activity-generator might help address that.

reply
Well the activity generator is going to have to be very careful to not accidentally overwrite data on the hidden volume, and somehow able to hide itself from adb or forensic tools that it's enabled.
reply
Those are ... relatively minor concerns.

Firing off as part of a duress key entry, and removing itself (from the decoy partition) as its work is done, would suffice.

ADB / forensic tools would be ineffective if USB access is denied (as discussed elsewhere in this thread).

reply
>ADB / forensic tools would be ineffective if USB access is denied (as discussed elsewhere in this thread).

Well no, because if you gave the pin, you'd expect the phone to work normally, including enabling adb. If you gave the pin but adb doesn't work that would be massively suspicious. Same if adb worked but logs were scrubbed. Otherwise you're back at "border guards found out you gave a duress pin, now you're being prosecuted for tampering with evidence".

reply
Right, it would have to be 64/64 for everyone.
reply
Not possible to have a robust implementation with the current tech unfortunately.

https://veracrypt.io/en/Wear-Leveling.html

reply
Interesting, did not know that! They do say some hardware, though, is phone's solid state storage definitely affected?
reply
Based on what I read it seems it's the same whether an SSD or UFS (what Pixels use) because they both use Nand flash as the underlying storage technique which is where the metadata issues occur.

https://search.brave.com/ask?q=ssd+vs+pixel%27s+storage%3F&c...

reply
That isn't truly hidden and can be detected as a low level from the SSD.
reply
No it can't. The the thing, it's obfuscated.
reply
I'm gonna trust the grapheneos HN account on this one.
reply
Having different data partition forces you to hide stuff, which can be unlawful in some juridictions.

Not having the data in the first place in some specific contexts (like crossing borders) is easier.

reply
Fair.
reply
A complete backup is solution that can be stored on my own encrypted servers and restored with a click of a button is really needed.

I always dread the possibility of my GrapheneOS phone being damaged or stolen and having to spend hours reinstalling and reconfiguring everything that Seedvault missed, as well as losing access to accounts that are locked by the secure element keys.

reply
> I am wary that I could be targeted at a border just for having a google pixel with grapheneOS.

Is that likely to happen at all in a civilized (Western) country?

reply
Yes, see https://www.theguardian.com/us-news/2026/jul/23/cop-city-pro... . The OP is actually a response to this.
reply
Remind us what happened when you do cross.
reply
Honestly, I feel like I'd be more suspicious of someone who had little to nothing installed on their phone.
reply
A lot of people are still using their smartphone pretty much as a dumbphone with a web browser.
reply
Yeah but if you're a normal guy strolling through every time with a phone that has nothing- no pictures, no signed in email, no history of messages, 4 contacts. That's abnormal, no way of spinning it as "but I just don't use my phone much" will make that seem normal. The average person has their phone glued to their body 24/7 now. Implying that you don't is abnormal.
reply
"I only ever cross borders with a blank phone because I don’t want you invading my privacy" is a perfectly valid answer. You can also add that it is your employer’s policy and/or your government official recommendation.
reply
You can also point out that other countries want to search phones too.

"I have to do this because of country X, you know that they're like, amirite?"

reply
> a perfectly valid answer

Makes no difference at all in the real world. You don't have to give valid answers, you need to get the guy across from you to not find you suspicious. That phrase is going to put a red flag on you, valid or not.

reply
> you need to get the guy across from you to not find you suspicious.

What? No, who cares about that? Let him find you suspicious, what matters is that he doesn’t access your data. And it is not suspicious to cross borders (esp. US borders) with burner phones. As others have said, it is standard practice.

reply
He doesn't access your data. He confiscates your phone, then still doesn't access your data, then denies you entry, then still doesn't access your data, then holds you in immigration detention for a week while he tries to access your data, which he can't. Is that a success? Maybe, if your data really is that valuable and a successful border crossing isn't.
reply
> Is that a success?

Definitely.

> Maybe, if your data really is that valuable and a successful border crossing isn't.

Even if my data consisted entirely of cat pictures, it would be more valuable than successfuly crossing the border into a country that actively tries to invade my privacy.

reply
Well why are you showing up at a border crossing if you don't want to cross the border?
reply
You may wish to cross the border but not at all costs.
reply
[dead]
reply
It's one that will get you denied entry, or detained indefinitely.
reply
I have worked for employers that required taking a burner phone to certain countries without any accounts logged in, etc. (so mostly for calls, maps, and web browsing) and nobody has ever been detained or denied entry. Some countries know that this is just standard procedure when they are visited for business trips. Probably different for the US though.

(Not legal advise of course, just observation. Always check with the legal department of your employer, etc.)

reply
> Probably different for the US though.

After cornering themselves into being labeled an unsafe destination (long overdue imho), the US are gonna have to learn being treated as such.

reply
"I'm here for business and my employer requires it" is an acceptable excuse. "I don't like government surveillance" is not.
reply
"I'm self-employed and my SOC 2 compliance consultant requires it."
reply
Denied entry, why not. But detained?
reply
In the USA border they detain people they think are lying until they think they are not lying.
reply
Lying about what? "I only bring a burner phone to border checks because I don’t want people like you to access my data“ is not a lie, and I fail to see how it could be interpreted as such.
reply
deleted
reply
"I got on pickpocketed on my last vacation, so now I travel with an old backup phone instead"
reply
This may feel like a good idea as a “gotcha” justification but it just doesn’t matter. It’s still extremely abnormal and you will stick out. The only way to protect yourself is by blending in, not sticking out.
reply
i am familiar with a number of the security team personnel, so i can give you the inside perspective.

the reaction you provoke at a border crossing, or an LEO encounter is almost entirely based on what profile you fit.

the vehicle, the state/contents of the vehicle, what you say, even how you move, are being evaluated for consistency with a profile.

reply
I think it would work. It's plausible enough. It doesn't have to be the most common answer to be accepted.
reply
Well but the point goes beyond “do they let you through.” All of this goes past the here and now. It’s about getting flagged in some system that causes you to get picked out 3 stops down the line when these odd occurrences add up to you not being trustworthy based on your profile history.

That kind of history is already being collected about people. That’s what you should be worried about when it comes to engineering some scheme that sounds clever.

reply
Like how many ?
reply
Even more of a reason for good and easy backup and restore.

Before travel back up the real contents and restore a dummy travel backup with random games, stock photos etc. Then restore back to real contents.

reply
This is never going to happen for the same reason Apple and Google won’t let you use different backup/restore methods.
reply
I looked at snapseed a few hours ago and backup must be done per profile.

So you can totally have different profiles with different backup servers/credentials and decide to nuke one before flying or crossing a border.

Obviously you can't expect having 2 whatsapp or signal accounts on same number but you can always have several SIMs.

The good thing is with profiles you can totally seed a profile for a few weeks before travelling.

reply
Sure but there'd be nothing there.

If the regime is going to just start taking people then nothing will stop that, but the goal is to stop the usefulness of this sort of thing as an intimidation measure - or at least drag it to the forefront and overthrow the regime.

reply
The easiest way to avoid suspicion is to have a phone filled with cat and family pictures, dumb apps and games.

You don't avoid scrutiny by being wierd and hiding things, but by hiding in plain sight by being ultra boring.

reply
The easiest way to avoid suspicion is to have a phone filled with cat and family pictures, dumb apps and games.

Presumably they know quite a lot about you already outside your phone (yay, Palantir). I mean, the guy the recent post was about was an activist. An empty phone vs. a phone with just cat pictures and dumb games wouldn't really make a difference. They went on a fishing expedition, so anything that does not have contact information/messages of other activists or any information that they could use against the phone owner would be a win.

(F-you Palantir for reading this message and adding it to my online record.)

reply
> (F-you Palantir for reading this message and adding it to my online record.)

Hello Palantir. I orchestrated 9/11. Please come and arrest me.

reply
On the other hand, if everything about you is boring, that in itself may begin to seem suspicious. "I borrowed this old phone from my stepson because my own phone got run over by a steamroller at a vintage vehicle show" is the sort of thing an actual spy or criminal would never say.
reply
Add some dickpicks because who doesn't have something on their phone that they don't want others to see.
reply
Multiple decoy accounts, heh. First one: cat pics. Second one: dick pics. Third one: conversations with an imaginary mistress. Fourth one: porn that's illegal in Korea. Fifth one: ....

completely impractical obviously

reply
[flagged]
reply
> So you plan to (1) actively/proactively conceal your data/evidence

I am not concealing data/evidence as it doesn't exists. I don't know of any law in any country that force you to hand out the key of your home to a remote state so that they can enter your country and do a search.

> and then (3) constantly restore from cloud backups?

Why constantly? Only and only if I need to access specific data (that may be available remotely without restore anyway). Full restore only when going back in my own country.

reply
It's been normal operating procedure for many employees that travel to the US. You think they're all criminals?
reply
Border officials don't have the right to search all of your data.

You are also not under any obligation to have it on your phone at all times.

reply
Just like a regular cop, all they need is probable cause.
reply
[flagged]
reply
> Correct! Furthermore, border officials have no requirements to allow you into their country either, unless you’re a citizen there,

I'd rather have them tell me to turn back and go home than being jailed there only because I don't want them to fap at the picture of my daughters.

reply
Unfortunately, it'll most likely go something like this: https://www.theguardian.com/us-news/2026/jul/23/cop-city-pro...
reply
Being prosecuted because your smartphone has been setup yesterday is not the same as being prosecuted because you gave a password that wipe your phone in front of law enforcement.

In the past I have had my smartphone die a couple of days before travelling and quickly buying a smartphone so I could have a mobile line in case of emergency while travelling. This is not a totally uncommon case to have a smartphone with very little data. A lot of people never setup any cloud backup and lose all their data every so many years.

reply
Yeah, the lesson is: do not travel to countries that treat people such in a shitty way. This has always been true. Unfortunately, for many foreigners this also applies to the US nowadays.

I guess that you are out of luck if you are a US citizen and need to return to your own country.

reply
Do the requirement to put your social account public when applying for a US Visa still applies? I guess the USA do not have that many non US visitors these days because I don't know a lot of women who would agree to that. Almost all my female friends have been experiencing stalking from jealous ex, former colleagues/clients/patients so putting their social media account public would be a complete no-go for them.

How is the tourism industry going?

reply