How to completely move the app and the messages to new Phone

[pyler]

And anyway, he can build stable version with "backup enabled" and share it via his website. Is it ok, no?
You will be able to install it as any normal APK.

[pyler]

definitely not a fork. I believe Kostya's can do a magic script to do it (release stable version with that flag)

[Kostya Vasilyev]

Yes, it's not a "fork" it's just a different build config.

Well, to a user, it's still a different .apk to install, in order to backup / restore. So it *is* an inconvenience.

On the other hand, there has been only one or two cases like this, very low compared to all the other discussion here.

[pyler]

http://android-developers.blogspot.sk/2015/07/auto-backup-for-apps-made-simple.html?linkId=15932577&m=1

You *can* exclude login/password info from backup and you are ready to go.

[Kostya Vasilyev]

That's M only.

[pyler]

But you will support M, right? 

[Kostya Vasilyev]

1.5.9 already runs on M, which 1.5.7 did not, remember the Apache HTTP debacle?

So yes, I support M already, have it on a Nexus 5 in front of me.

[mikeone]

Google walks us through Android M’s promising Auto Backup for Apps feature:
http://www.androidauthority.com/android-m-auto-backup-for-apps-630094/

They call it “Auto Backup for Apps” and according to them, developers come implement this with “zero lines of application code.” Awesome. They do mention that developers will first need to update the targetSdkVersion to 23 in order to enable it and test in the latest Android M Developer Preview. Of course, opting out is also possible and developers can exclude specific app data.

Watch "Android Auto Backup for Apps" on YouTube:
 https://youtu.be/HXacyy0HSW0

[Kostya Vasilyev]

This jumped at me right away:

"Apps are limited to 25MB of backup data"

May be enough for a lot of users, but there a certainly enough whose message DB is going to be larger.

"Zero lines of application code.” Awesome.

Yes, "awesome". They always say things like that.

[mikeone]

This jumped at me right away:

"Apps are limited to 25MB of backup data"

Yes, this "limitation" I've also noticed...  CAAARL!!!l
 

[pyler]

25 MB seems enough for me. Why we have to flood servers? Can't be some compression used in DBs?

[Kostya Vasilyev]

It quite amazes me how much attention this thread is getting.

Given that I pretty much know (or assume) that most people here -- keep their messages on the servers, so the app re-syncs just fine, and also use the app's own backup / restore feature.

[Midori]

It quite amazes me how much attention this thread is getting.

Given that I pretty much know (or assume) that most people here -- keep their messages on the servers, so the app re-syncs just fine, and also use the app's own backup / restore feature.

Here I am now 4.5 years later, fretting how to transfer my wife's aquamail to a new device. I read all of this thread and hate negative'ism. So easy surely to fix it for the masses like me who have severe server-storage limitations.    Can I not dump the database on an sd card somehow? 

[ring]

Yes, but it's just a file, and the user can store it anywhere they wish, it's their decision.

I'm talking about the agreement between me and Google, necessary to use Android's built-in "back up your apps, settings and WiFi passwords".

Apparently backing up passwords is a no-no there.

There is also a requirement to notify the user before backing anything up -- seems intrusive, I mean someone just installed the app, and gets prompted for "Allow back up data to Google cloud?" -- I'm sure it's going to scare a certain percentage of new users.

But now that backup & restore support Google Drive, it should cover more people.

---

But back to backing up actual messages -- that's different, it's something that would need time before it works, and I still think (even though the OP's case is different) -- that these days,  most people's emails are there on the servers, including older ones.

You need update android the last version.

[Midori]

You need update android the last version.

The new (destination) phone IS latest Android update.  The old (source data) phone is no longer updateable to same f/w current s/w, which is why I have to migrate to a new phone !