Closed GoogleCodeExporter closed 8 years ago
truecrypt team: Please try recompiling your app with Android NDK r8b or
greater. This will fix this bug.
Original comment by n...@google.com
on 27 Nov 2012 at 9:18
Thanks for the report, and thanks for suggesting a fix. Will rebuild with r8c.
Original comment by christoph.schmidthieber@gmail.com
on 27 Nov 2012 at 9:22
@anilkpatel: Could you test the encfs binary that ships with 0.7.6? It's been
built with r8c and shouldn't produce this error.
TrueCrypt had to be built with Crystax NDK 7 because of incomplete wchar
support in the official NDK. It's a known problem:
http://www.crystax.net/trac/ndk/ticket/112
If it can't be resolved on the Crystax side, we'll have to switch to the
official NDK and find a wchar workaround.
Original comment by christoph.schmidthieber@gmail.com
on 27 Nov 2012 at 9:38
On testing the encfs binary on 0.7.6, here is what I did:
1. Launch terminal with Expert->Start root terminal
2. Enter "encfs" at the terminal command prompt
RESULT:
Got the encfs usage message. In other words, the linker error that I saw using
the truecrypt binaries is not present with encfs.
Let me know if there are additional steps you want me to try.
I appreciate your help.
Original comment by anilkpa...@gmail.com
on 27 Nov 2012 at 9:43
Thanks for your quick test. We'll have to wait for a reply from the Crystax
team now.
Original comment by christoph.schmidthieber@gmail.com
on 27 Nov 2012 at 9:46
This issue was closed by revision 63b3b3366cde.
Original comment by christoph.schmidthieber@gmail.com
on 28 Nov 2012 at 2:40
Try the latest truecrypt binary, available from the downloads section:
https://code.google.com/p/cryptonite/downloads/list
Original comment by christoph.schmidthieber@gmail.com
on 28 Nov 2012 at 3:08
The new binary works. The linker error is gone. Thanks for the quick
turnaround!
Now I have a different error with the mounting, but I can open another issue
for that.
Original comment by anilkpa...@gmail.com
on 28 Nov 2012 at 3:59
Yes please.
Original comment by christoph.schmidthieber@gmail.com
on 28 Nov 2012 at 4:29
Do you have a "mount" command sitting in /system/xbin/mount? If not, try to
install BusyBox from the Play Store.
Original comment by christoph.schmidthieber@gmail.com
on 28 Nov 2012 at 2:11
Yes, I have a mount command in /system/xbin/mount. This is linked to my
busybox mount. The mount was failing because I had not created the target
mount directory first. Once I did that, the mount succeeds. However, there is
an issue with limited file accessibility. I've created issue #47 to describe
it.
Original comment by anilkpa...@gmail.com
on 28 Nov 2012 at 8:35
Issue 50 has been merged into this issue.
Original comment by christoph.schmidthieber@gmail.com
on 24 Feb 2013 at 9:25
Original issue reported on code.google.com by
anilkpa...@gmail.com
on 25 Nov 2012 at 12:42