Hi Bill,

First of all: you are the first to report running the x86 binary. I am
generating the binaries as part of my build process but I have no x86
device and the Android emulator does not support that platform. The
hostdefs_android.ijs and netdefs_android.ijs you are currently using
was NOT generated under an x86 environment and may pose some
surprises.  Would you mind if I emailed you the compiled hostdefs and
netdefs binaries to run on your device?  I can use the output and fix
systemdefs to seek on a per-abi basis.

The non-functioning of 2!:0 and 1 are documented in the readme along
with a few other issues I expect users will want to be appraised of.
The Android environment is very locked down on a non-rooted device and
I only recently learned how to launch a host command at all, although
few useful ones are available.  I will revisit that in light of some
things I have learned.

The user directory is indeed explicitly set to the path you indicated.
 The value of $HOME you are seeing in terminal I can only assume is
set by term itself on launch.  The android environment give me no
$HOME variable at all on launch and I am forced to assign one.

It had not occurred to me to set the user directory outside the
hierarchy the environment provides (which is rooted at app_jconsole)
but it is an interesting idea. I will explore the possibilities.

Thank you very much for the feedback. You can all expect a slightly
tighter product in the near future.

 - michael

On Sat, Mar 24, 2012 at 4:03 AM, bill lam <bbill....@gmail.com> wrote:
> I install the android port on android-x86, The jconsole work without
> problem. But I found the ~user is not directly under /data but
> several folders under app_jconsole. I think this is caused by
> 2!:5'HOME' being pointnig to app_jconsole.  However
> echo '$HOME' in terminal gives /data as expected. Why the $HOME
> reported differently?
>
> 2!:0 and 2:1 does not work.  on android 4.0 , the path of sh is at
> /system/bin/sh  but the android port of libj.so seems still use
> /bin/sh,  is this the reason of failure?  Or the real android
> behaves differently?
>
> Пнд, 19 Мар 2012, Michael Dykman писал(а):
>> Several practical complaints have been raised about androids tightness
>> around files permissions.
>>
>> In what I hope will be an effective hit-it-with-a-hammer solution, I
>> have added an option under Help, "Make Writable" which explicitly sets
>> 0777 world-writable permissions on each and every file and directory
>> in the j app directory.  I sincerely hope this improves visibility.
>> Please let me know if you still have issues after it' use.
>>
>> Here is a link to a mildly upgraded version, this link to the apk
>> itself rather than the web page containing it.
>>
>> https://github.com/mdykman/jconsole_for_android/blob/master/dist/j-console-1.0.1.apk?raw=true
>>
>> This installation will leave your user files undisturbed nor will it
>> overwrite your system files.  This will just update the Android
>> binaries, providing system files only if not already present.
>>
>>  - michael dykman
>> ----------------------------------------------------------------------
>> For information about J forums see http://www.jsoftware.com/forums.htm
>
> --
> regards,
> ====================================================
> GPG key 1024D/4434BAB3 2008-08-24
> gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm



-- 
 - michael dykman
 - mdyk...@gmail.com

 May the Source be with you.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to