Hulk Is there a specific amount of donation that would noticeably support development of a more-robust backup solution? Obviously the GrapheneOS core developers aren't bounty hunters, but since this is an announced goal of the project, is there some amount that would help a bunch toward backups?

    I would actually like the idea of community funding.
    "Obviously the GrapheneOS core developers aren't bounty hunters"
    This is one way of looking at this. Flawed idea imo.

    Think of it like a Kickstarter. Donate 1 million and we will implement XYZ.
    Why can't it be the same? With a few sane adjustments of course.
    But for example, you want feature X, there is 10k amount for it, once it reaches
    this goal, it's implemented. Yeah, it makes the project trashy and pay-for-feature,
    like many games where you have to pay to win, but well, at least it's a thing to consider.
    I know this bare idea is bad, but it's possible to make goals that once reached, development
    time will be focused towards it. Better camera, backup, etc.

    • de0u replied to this.

      uid0gid0 I think when it comes to which model the GrapheneOS developers work according to, they are the ones who decide. For example: We're not contract workers, we're not accepting bounties, we're not doing something just because you keep on pinging us about it.

      Hopefully backups is different because it's a public goal. So I'm curious as to whether some specific volume of donations might be supportive of this existing goal.

          de0u

          I agree. They don't want to set a bad precedent though.
          IMO, they are leaving money on the table. GrapheneOS is certainly already worth a one time donation. But it's hard to justify recurring donations when they routinely make people feel like crap just for asking. It feels, and this is subjective, that non devs are looked down upon, because they aren't willing to learn how to code. As if they even would consider accepting code from novices anyway. So the masses must just accept the priorities or lack thereof, for any feature popular or not. It's fine, but not really inspiring of donations.

              2 months later

              I feel that manual backups are tricky and time-consuming - as far as I know you have to go to each app one-by-one and it depends on what the app offers. There are also various system settings. So I'd like to explore alternatives.

              What does anyone think about using adb for backups? It seems like it could be completely automated in a script.

              12 days later

              @WhiteKnight adb backup / restore is deprecated for anything other than debugging. It doesn't back up data for non-debug builds of apps targeting Android 12 and above. You're trying to use a development tool and are drawing wrong conclusions about the backup system based on it.

              allowBackup="false" only disables cloud backups for apps targeting Android 12 and above and the traditional backup file exclusion system also only applies to cloud backups. Targeting Android 12 and above is mandatory for apps in the Play Store. The new file exclusion system differentiates between cloud, end-to-end encrypted cloud and device-to-device backups. There's no option for apps to disable backups, but they could exclude all their files from them. The vast majority of apps do not exclude their files from device-to-device backups, which is what gets used by the backup system.

                Graphite

                Considered alone, yeah it's sucks that users who put their digital life and trust in GOS feel disempowered like this.

                On the other hand - how much of a voice do users have in the Google or Apple ecosystems?

                Can we find examples among other OSes who use a different funding / resource allocation / prioritization structure? (LineageOS, etc?)

                The Kickstarter model is not a good one for security and privacy minded OS in my opinion, many problems with the kickstarter funding model. I think there are good reasons why most creators on the KS platform move on to forming their own org independently of KS after their initial success, rather than stick around on KS long-term.

                  5 days later

                  Would be handy if there was a OS based backup system that creates a local backup file of like the settings, sms and call history, contact list, etc., which then can be either be stored on a computer or a cloud storage like Proton Drive, so I don't need to look for apps on the Play store that can do these things.

                    12 days later

                    GrapheneOS is fantastic and automated, reliable backup is the only critical part that I miss. I hope you'll build a great solution, you have my support guys.

                      WickedMouse

                      WickedMouse Would be handy if there was a OS based backup system that creates a local backup file of like the settings, sms and call history, contact list, etc.

                      I have used "SMS Import / Export", which covers SMS/MMS and contacts. The need to manually use airplane mode is a little clunky, but it's been useful.

                      A general backup solution would indeed be great, but we will need to wait.

                            Draknof Give them some time.

                            The Project is heavily underfunded in staff and financial terms.
                            Please keep that in mind and consider some form of support.

                            Either with financial donations or if you have the required skills contribute to the project.

                            Cheers.

                              de0u Yeah I've been using "SMS Backup & Restore", to save them all locally and then copy them to PC, so use the same app on the new/other phone to import them.

                                7 days later

                                As there is no good backup solution in sight, my strategy is to store data on /sdcard where possible and from there I back it up with another app. Obviously this does not work for all apps, but I have started to prefer apps that can store on /sdcard and will be changing code for apps that I compile myself.

                                IMO the best long-term solution would be too hook into the existing Android BackupAgent mechanism (link) and make it backup into a self-hosted network storage instead of Google cloud. But that requires development inside the OS and/or creating a shim that replaces the existing Google backend.

                                Where is Google's backup mechanism implemented; in the core OS or in GSF? If it is in GSF, one could create a shim like many other shims in GOS. It would be enough to support one backend, namely Rclone (link). Rclone itself supports many storage solutions, ranging from self-hosted SFTP to public cloud providers. So every user could chose his preferred backup storage.

                                I have tested backup. Perfect no it isn't. But pretty
                                damn good actually. I'm not seeing why people dislike it. At the end of tbr day I'm just so thankful for a non apple/google solution.

                                Thank you to the devs and community.

                                  James did you test restore to a new phone? From what I've read, about 40% of your phone is backed up.

                                      Yeah I've been trying seedvault the past few days it'll install all your apps , most settings are saved , contacts and call logs are saved .
                                      But no app data , texts or pictures .
                                      It doesn't save the important stuff
                                      It will install backup on pixel 6 but not on pixel 6 pro half the time.