World: r4wp

Hi Doc, congratulations for this new landmark. As the hello.apk generated 
in the past from Red/System was not running for my Galaxy tab 10.1 
was not running, I expected the new apk release not running too and 
it is effectively not running here opn this machine, even  if I upgraded 
to Android 4.0.4 recently - so the problem is located under the Android 
level - as I had expected it too. May be the op cpodes generated 
are not the ones expected on my machine - that is they are not currently 
compatioble with the ones you generated - but I have no time to test 
it. this was just to keep you informed so others know this too... 
Don't bother with this case as I plan to get another Android device 
in the next few months to compare the compatibility of the product. 
Probably the CPU codes are not athe level you deliver them (ARM v5 
if I remember correctly ?)  Best regards.

Gerard - Galaxy Tab is prestigious product, it should run imo ...

Gerard, thanks for reporting it. Galaxy Tab uses Tegra2 chipset, 
so an ARM Cortex-A9 CPU, I see no reason why it shouldn't work with 
ARMv5 code... Are you sure you've tested with hello.apk and not hello-x86.apk?

Gerard, can you install this app on your Galaxy Tab: https://play.google.com/store/apps/details?id=org.jtb.alogcat&hl=en


Once hello.apk has crashed, just switch to this app, and send me 
the logs by email.

Kaj, thanks for the example

OK Doc I'll try it later as I must go to work now and I'll send it 
back results to you later. Thanks

Congrats on the Android release Doc - very exciting!  (sorry, I've 
been away from AltMe for a while)

Thanks Nick, more to come soon. :-)

I just test hello.apk on Samsung S3 Galaxy Android 2.3.6, it works 
well. Great work Doc!

Hi Doc, I just sent you my log results to your red-lang.org email 
account - thanks - it seems the device is unable to locate the sdram 
card since there is no such sdcard on this device and no slot to 
put one too... may be there is another place to send files but I 
never looked at it and so I don't know where to send my files - the 
device is just using his own directories by itself and I never bothered 
about it until now ... I will have to look further to help you in 
this way.

@Doc : I just sent back my unfiltered log results for the Samsung 
Galaxy tab 10.1 machine - thanks and best regards

I am runing %red.r for %0MQ-request-client.red but failing on 
#include %../common/common.red
It looks like it would be from 
https://github.com/dockimbel/Red.git
but I don't find any common/ directory

I am probably mis-aligning my zmq directories but don't have anything 
but common.reds from clones.
Any hints to help me find my path?

I don't think that common.red is from the main Red repo. I suspect 
it's one of Kaj's libraries.

That's correct

All bindings follow the same naming. The common repository is here:

http://red.esperconsultancy.nl/Red-common

It's easier to download all bindings together with the download.r 
script:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip

On my Nexus 7, the hello.apk comes up with a main screen that has 
"hello" in the top bar. Is that correct? To exit it, you have to 
swipe the app away. It does not respond to a return/escape.

Thanks I will catch up soon.

@james_nak : this is exactly what I get on my Galaxy tab 10.1 and 
I suspected it was not correctly executing since I doubt it is doing 
what is expected - even if I don't really know about the app !

@Doc : Can you tell us what was really expected as the normal behaviour 
for this Hello.apk app ?

before Doc does so, I expect him to release some new improved version 
:-)

@Gerard, you make me very curious to what you expected Hello.apk 
should do. I think it plays a Lionel Richie song! ;)

@Arnold and Pekr : What is the current behaviour of the Hello.apk 
? I thought it was displaying some welcome msg and then askin for 
some input before disappearing gracefully. Now on my machine a while 
screen is displayed with a "Hello" as its window name and nothing 
else is going on.... For the previous Red/System Hello, something 
almost similar was going on too. So it's not for the Red part fault 
but it is due to the lower layer ... I knew this but I can't diagnose 
what ios coming myself as I'm missing some vital knowlwdge here to 
be really helpful to debug anything ... on my own - sorry for having 
acquired some product in the first pioneers just to test how this 
kind of product was running on Android. I required some Flash and 
my Apple products just could'nt do it - but my tablet Android tablet 
was much slower on display than my iDevices. Hope that under Red 
and Red/System there will be some products running at full speed 
- if not I plan to let it go at a real bargain price very soon ... 
to get some more powerful device ASAP.

When I talk about spped it's related to display and GUI ...

Gerard - don't know, my HTC phone is being in the repair centre (touch 
layer not working) - just today received sms, that is it ready. I 
will have it back over the weekend ...

Now on my machine a while screen is displayed with a 
Hello" as its window name and nothing else is going on...."


Gerard, that's exactly what the current hello.apk is supposed to 
do.

OK, thanks. That's all I needed to know.

Me too - thanks Andreas - So I regretfully missed the point basing 
my view on the previous Red/System Hello.apk. - Really Sorry Doc 
for this misconception. Just thinking that I should have looked at 
the source code instead of being like a blind - asking unuseful questions. 
I'll take note as to not disturbing anybody in this way in the future....

This is what you should get when running hello.apk: http://static.red-lang.org/hello-droid.png

Just in case: I don't see the "Hello Android World from Red!" text 
on a Nexus 4.

Only Hello on windows name on  Notus II too

Notus = Galaxy Note II

@Doc : So the text msg is really missing - only the Window's name 
is appearing on my device - Phew !!! I was not disrturbing you for 
nothing at least! Hope the last log results could help a bit - but 
don't stress too much if your time is limited (rare) and I suppose 
it is .... thanks for the screen capture you sent.

This fact seems to show that Samsung really is doing things in a 
non standard way ... at a very low level may be !!!

And for most of their devices based on Android - or may be the same 
chipset - but I don't really know about the specific internals... 
of their devices !

How hard would it be to have Red generate .SYS Windows drivers?

Gerard, it's most probably a faulty apk, we'll see with the next 
demo.

SYS: It seems that not much is required to add to the PE file itself, 
I see no additional sections needed. However, it requires a proper 
checksum in the header. That checksum is either calculated using 
Windows API or the algorithm could be implemented directly in Rebol. 
In the first case, it shouldn't take more than an hour to add support 
to it, in second case a day or two. The main issue would be to find 
a simple way to test it once generated? Any idea?

Andreas: was your Nexus4 running 4.2.2?

Nenad, I only had the window title as well, on the Galaxy Nexus with 
4.2.2 - thought that was all that was expected.

I just tested the hello.apk (downloading from the Red site) on an 
emulated 4.2.2 and it works fine. So, it looks like the Android emulator 
is not as reliable as it seems.

Gerard, found the native crash dump info in your log file, thanks! 
We'll give it another try with the new bridge version once ready 
(this week).

Thanks Doc.

I have an example Windows driver that would be interesting to port 
to Red/System, so that could be a test case

I guess a 32 bit driver wouldn't work on 64 bit Windows?

Hmm, I'm not sure.

It would be great if it would; then I could surely use the Red route

I wonder how do you make the testing process simple and straighforward 
for a Windows driver.