Roopa,
For your questions the agentry.db, we take your database which normally is used to show a client bug. For example, if you have an issue clicking a button then it crashes or if you click on this functional location search and it should fire a rule but it does not. Client bugs are normally handled through dumping your Agentry.db (client dump). We then download the same version of the software in our own internal server. We then assign this data and hopefully the database does not require a sync. So when we force to run it (without synching) in the same software the customer is using, hopefully we can reproduce the client issue.
The key technique here is that the data dump should not make us transmit as this will be problematic as we have no access to the backend.
The Agentry.db is used differently between iOS and Android. In Android you have to brand this client (as mentioned by Bill) and create a new install APK file. We then use the APK file to install in our branded client (we normally would not transmit as this will fail).
This Agentry.db is only to be used to replicate a client bug. There is no easy way to force it to transmit the old saved data. In older clients like the WinCE you can try saving logs file but sometimes when you transmit it may corrupt the current data on the client but sometimes the data gets transmitted but for the most part it does not work flawlessly.
Best Regards,
Mark Pe
SAP Platinum Support Engineer