Hi Nathan, I'm the maintainer of MobileOrg for Android. Have you read the org-mode documentation for MobileOrg? http://orgmode.org/manual/MobileOrg.html#MobileOrg That's a good place to start in figuring out what MobileOrg expects of org-mode, and also what org-mode expects from MobileOrg. The synchronization modes refer mostly to where you stage your org-mode files. The outline mode will work in the upcoming version of the application. You should definitely read the org-mode documentation about MobileOrg and I think that will give you a pretty good idea of how synchronization is handled from both sides. On Sat, Jun 11, 2011 at 2:11 PM, Nathan Neff wrote: > I just joined the 21st century and got a smart phone. > > I downloaded the MobileOrg for Android application, and have some > questions, > most of them are probably dumb, because I have only played with the > phone for a bit. > > 1) Is there documentation regarding the various setups/syncing modes? > I would like to know how to get data off my phone, put .org files on my > phone. > I know how to use Dropsend, etc, but I would probably rather just use > rsync or git to > sync the phone's data. > > 2) The menu for MobileOrg Android has an "Outline" button, but it > doesn't do anything. > > 3) In "Configure Synchronization Settings" there's a setting where you > specify where index.org > is. What do I put in there? Is this setting affected by the other > Synchronization settings? > > 4) What does "Sync" actually mean? Is it like rsync where it copies > the latest file, or does it attempt > a merge? What happens if you have new stuff in each file? Does > DropSend asking you which one you want, or > provide a diff tool? > > > As you can see, I'm very new to Android and have no idea what I'm doing :-) > > I do plan (within the next few months) to start learning how to > develop on Android platform, > and I think that Mobile Org Android would be a good "Scratch your own > itch" program to start with. > > I'd be more than willing to start a FAQ on the Github Wiki with any > answers that I get from this post. > > Thanks, > --Nate > >