Open GoogleCodeExporter opened 8 years ago
I have this problem as well. In my case, I found I was able to work around it
by creating a "mileage" directory on the sd card.
I am a (novice) android developer, and I would not expect the typical user to
know how to do this (or have a file management app to do it). So it would seem
that the fix would be for the mileage app to create this directory, if it
doesn't exist.
Thanks!
Original comment by pjbou...@gmail.com
on 18 Feb 2012 at 8:00
I do not know how to create a "mileage directory on the Sd card so I can
transfer my data to my new phone. Can you please elaborate.
Sincerely,
Original comment by michael....@gmail.com
on 3 Jun 2012 at 7:30
Could you try installing the latest update? It should create the directory
automatically for you. If you're already on the latest update let me know and I
can debug this further.
Thanks!
Original comment by evancharlton
on 3 Jun 2012 at 11:07
Hello tried to do export and nothing happend, i am using galaxy nexus with
android 4.1.1 and Mileage 3.1.1
Original comment by mishk...@gmail.com
on 20 Feb 2013 at 7:16
Backups do not work on Galaxy Nexus on Verizon. Perhaps the internal only
storage is causing problems? Is the backup/export looking for an external
storage drive?
Original comment by suprarx7...@gmail.com
on 14 Mar 2013 at 4:42
I am experiencing a similar issue. I have two Android 4.3 phones, the Galaxy
Nexus and the Nexus 4. Both are running the latest Mileage v. 3.1.1
I am unable to locate the named export on the Galaxy, and there is currently no
named folder appearing in the file explorer on the 4 called mileage even though
I have entered some dummy data into the software. Nor am I able to create that
folder. I am able, on both phones, to import the named export files, so they
are getting placed somewhere, but I am otherwise unable to locate them.
I have sent an email to Evan this evening, so I hope to hear back regarding a
solution soon.
Original comment by travis.g...@gmail.com
on 16 Sep 2013 at 4:29
It seems that this issue has been taken over from the original poster who had
an actual error not being able to export.
For the others, I wanted to add some information that this issues isn't
specific to the Milage App.
It appears that the issue may be involved with Android OS itself and the
connection type you attempt to use.
https://code.google.com/p/android/issues/detail?id=38282
Seems a reboot may reset the database that MTP uses. I was struggling with
this myself and decided to use Astro File manager to see what was going on with
the filesystem. I had deleted the mileage folder and attempted to do an
export, which worked, but I couldn't see the mileage folder. Astro could and I
created a new folder which I copied the exported file out to. After seeing the
information on the android issue I linked, I rebooted the phone and was able to
see the folder and the file in it.
hope that helps others with the same issue as many of us in here.
Original comment by granvill...@ruralsourcing.com
on 22 Nov 2013 at 9:06
Original issue reported on code.google.com by
gase...@gmail.com
on 20 Dec 2011 at 6:37