yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy R i9103] kishoreinme:
The build completed and the generated cm zip is usable without a new recovery though.

I tried to flash the recovery.img generated during the same with heimdall.

After flashing I Couldnt get into recovery mode.

Is there any other special method to build/flash recovery from cm sources?

or if you can, post a working recovery image.

Sorry that I am bugging more here. This is my first time I try to build CM from sources to get something up on the phone
[Samsung Galaxy R i9103] Adam77Root:
You need to set TARGET_CPU_VARIANT to 'generic' in BoardConfig.mk.

Try to build an image with the online builder at builder.clockworkmod.com. The R can be found among existing devices, but I think it still uses cm-10.1 branch as the official repo isn't updated to 10.2+. Or you can alternatively use the manual mode. I would also prefer the latter.
[Samsung Galaxy R i9103] kishoreinme:
QUOTE=Adam77Root;47514517]You need to set TARGET_CPU_VARIANT to 'generic' in BoardConfig.mk.

Try to build an image with the online builder at builder.clockworkmod.com. The R can be found among existing devices, but I think it still uses cm-10.1 branch as the official repo isn't updated to 10.2+. Or you can alternatively use the manual mode. I would also prefer the latter.[/QUOTE]

Thanks Adam

I tried manually building at the online builder . Getting the error

bionic/libc/Android.mk:429: TARGET_CPU_VARIANT is not defined

Console goes here

http://jenkins.cyanogenmod.com/job/recovery/45774/console
[Samsung Galaxy R i9103] kishoreinme:
Also I had tried instructions to build recovery from sources with

build/tools/device/makerecoveries.sh cm_i9103-eng

It gives a ~7mb recovery.img at the end of the build

Which when i flash with heimdall gives SOS upload failed

Heimdall v1.4 RC1

Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.

Initialising protocol...
Protocol initialisation successful.

Beginning session...
Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading SOS
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SOS upload failed!

Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...

Thanks
[Samsung Galaxy R i9103] Adam77Root:
Use 'make recoveryimage', that's the standard.

Use Odin or flash recoveries from ADB.
[Samsung Galaxy R i9103] Tha TechnoCrat:
Any progress?

"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"
[Samsung Galaxy R i9103] kishoreinme:
Sorry I was out of station. Nothing much. I tried flashing the recovery in all ways Adam suggested but the recovery mode goes broken.

If I could could atleast flash and boot/see some logs, I will try to debug if any problem arises. Now stuck in flashing stage itself.
[Samsung Galaxy R i9103] kishoreinme:
Adam,

Could you post the recovery generated from omni 4.3.1 sources which i beleive has the set_metadata_recursive implementation or any other latest cwm for i9103 having this implementation?

Thanks
[Samsung Galaxy R i9103] kishoreinme:
I have flashed without new recovery using this fix

http://xdaforums.com/showpost.php?p=47692333&postcount=15&nocache=1&z=1484923475146786

Now bootloop

Any help on debugging the bootloop?

adb says

error: device unauthorized. Please check the confirmation dialog on your device.
[Samsung Galaxy R i9103] Grarak:
use my device tree

https://github.com/Grarak/android_device_samsung_i9103
[Samsung Galaxy R i9103] kishoreinme:
Thanks for that . I built again with your device tree and your kernel 4.4.

Same error

Surface flinger doesnt come up.

Log attached.

:(

On booting my working Equilibrium ROM from Adam I see

D/libEGL ( 239): loaded /system/lib/egl/libEGL_tegra.so
D/libEGL ( 239): loaded /system/lib/egl/libGLESv1_CM_tegra.so
D/libEGL ( 239): loaded /system/lib/egl/libGLESv2_tegra.so

But CM11 boot shows different libs loaded

D/libEGL ( 126): loaded /system/lib/egl/libEGL_perfhud.so
D/libEGL ( 126): loaded /system/lib/egl/libGLESv1_CM_perfhud.so
D/libEGL ( 126): loaded /system/lib/egl/libGLESv2_perfhud.so

I have taken /vendor directory fro build from https://github.com/tpruvot/proprietary_vendor_samsung/tree/cm-10.2/i9103

Am I going wrong in proprietary files?
[Samsung Galaxy R i9103] darkspr1te:
try replacing the blobs for egl/tegra from the nexus 7 grouper, worked on my acer iconia cm11 build.

Nexus 7 blobs

darkspr1te
[Samsung Galaxy R i9103] Grarak:
I doubt that this will work

There are huge difference between tegra 2 and 3
[Samsung Galaxy R i9103] karthik050782:
Upload your build and send me the link by pm.. I will try my best...
[Samsung Galaxy R i9103] kishoreinme:
'Build' I guess you mean the binary.

I had PM'ed the binary download link to you.
[Samsung Galaxy R i9103] Grarak:
with build he means the rom
[Samsung Galaxy R i9103] kishoreinme:
yeah, I have uploaded the rom zip
[Samsung Galaxy R i9103] karthik050782:
Downloading... Will check..
[Samsung Galaxy R i9103] karthik050782:
Sorry guys, very busy.. Too much pressure in office.. So cant spend any time...
[Samsung Galaxy R i9103] kishoreinme:
Tried getting into surfaceflinger sources. Seemed it got a major overhaul. Later found this in

http://developer.android.com/about/versions/kitkat.html#44-graphics

[B]Graphics[/B]
[B]GLES2.0 SurfaceFlinger[/B]

Android 4.4 upgrades its SurfaceFlinger from OpenGL ES 1.0 to OpenGL ES 2.0.

And we have the OpenGL ES 1.0 loading with our libs I believe.

Am new to the "Graphics" arena. If someone can give a basic brief how we go about this, I will try get into sources for modification/porting from somewhere.
[Samsung Galaxy R i9103] karthik050782:
I feel there are some patches for getting 1.0 to work... And as tegra 2 is not supported by CM, i doubt they will add... Will check AOSP source..

some changes required in frameworks_av and frameworks_native..
[Samsung Galaxy R i9103] fernan13malaga:
Hi guys,

Can anybody explain what is working (and what not) in this rom?

As I can understand, the rom have the same bugs from cm10.1, but not sure.

Thanks

Enviado desde mi GT-I9103 mediante Tapatalk
[Samsung Galaxy R i9103] karthik050782:
Its not even booting...
[Samsung Galaxy R i9103] kishoreinme:
Tried this patch for OpenGL ES 1.1 fall back. No luck.

https://gist.github.com/steven676/7276901
[Samsung Galaxy R i9103] kaushal.k:
see this even galaxy y can run on 4.4

http://www.sidhtech.com/news/android-44-kitkat-update-phones-list/10025433/
[Samsung Galaxy R i9103] kishoreinme:
More than having latest software running , its about extending life of the phone to be in our hands. It was a point where I was about to give up changing the phone when there was not even ICS for us. Things changed

Though we are a small community, there are great devs who brought it till 4.3 . Many have changed phones and still supporting without the hardware. Still no clear idea of whether it would happen or not. Lets try for 4.4.
[Samsung Galaxy R i9103] karthik050782:
Yep... I have very little free time but try to contribute to our little forum...

I am compiling omni 4.4...
[Samsung Galaxy R i9103] karthik050782:
Any tegra2 device got kitkat?
[Samsung Galaxy R i9103] fernan13malaga:
Maybe an unofficial port, but I don't think so. CyanogenMod stop supporting tegra devices since cm10.1

Enviado desde mi GT-I9103 mediante Tapatalk
[Samsung Galaxy R i9103] G@sh!sh:
http://xdaforums.com/showthread.php?t=2551925
[Samsung Galaxy R i9103] karthik050782:
[MENTION=4719724]Adam77Root[/MENTION] help me...
[Samsung Galaxy R i9103] Adam77Root:
These are EGL lib errors, there's not much I can do here. :(
[Samsung Galaxy R i9103] Grarak:
Try to use libs from samsung captivate glide
[Samsung Galaxy R i9103] tonyp:
That won't help as they're still tegra2 blobs - which aren't supported in frameworks/native anymore. The only way to fix the blobs would be an update by nvidia / the vendors - which isn't happening obviously.

So you need to workaround the limitations of the old EGL in the sources to re-add compatibility (which btw had to be done for Android 4.3 and partly Android 4.2 as well).

The reason that CM11 doesn't boot up for you is that CM hasn't merged the required patches.

The commits do exist on CMs gerrit though:

http://review.cyanogenmod.org/#/q/s.../android_frameworks_native+branch:cm-11.0,n,z

They're new implementations of the CM10.2 patches by arcee.

Note that in some first tests the new ones didn't work for me on my tegra2 phone anymore - somethings seems to be broken in them for the tegra2 architechture.

The OmniROM has (had? I think they partly reverted it here) used forwardports of the old CM10.2 patches - which the SlimROM has merged as well in a similiar manner.

But this only fixes booting, I still do have way to many hot reboots so some more stuff has changed in 4.4 - which I didn't manage to fix or workaround so far.

What we need is someone with that kind of deep hardware knowledge.

All in all: Blindly changing blobs or other libs won't help here at all. Just building against different framework/native trees won't either.

The surfaceflinger and probably some more stuff in frameworks/native needs to get worked on in code.

Currently there doesn't exist a tegra2 device which fully works to my knowledge - and I'm following a couple ones like the Galaxy R, the Xoom, the Transformer TF 101, the Atrix and the Galaxy Tab 10.1.

I'm working on the 2x, but have way too less time at the moment to dig any deeper into the code - while the current ROM boots (using my frameworks/native repo here) and has a working ril, wifi & storage it's nowhere near a daily driver thanks to frequent hot reboots.
[Samsung Galaxy R i9103] Grarak:
Thanks for the info

The weird thing is that the captivate glide boots up with omni rom

I don't know whether they used these commits which you posted

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy R i9103] tonyp:
With the correct patches at frameworks/native (you can try out the one I've been linking above) and a properly set up device tree yours should boot as well.

But that's not enough - the glide has the reboots on sleep as well which my 2x suffers from, too.

Thinking about it, we tegra2 users might need an updated kernel when some deep sleep stuff changed - that has been the case back at Android 4.1 (vs 4.0) as well.

Edit: I've linked all tegra2 development threads I am aware of here:

http://xdaforums.com/showthread.php?p=48243852#post48243852
[Samsung Galaxy R i9103] karthik050782:
[MENTION=3605868]tonyp[/MENTION] thanks alot, in omni 4.4 there is no error in surfacelinger it is getting started but screen is black because of the sigsev errorrs(i guess)..

I will add the deleted lines and will test.. thanks a lot..
[Samsung Galaxy R i9103] karthik050782:
TARGET_ARCH_VARIANT_CPU should be generic or cortex-a9

I tried cortex-a9 it stuck in the samsung galaxy r not event to the bootanim..

why it should be generic?
[Samsung Galaxy R i9103] Grarak:
It should be generic

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy R i9103] karthik050782:
but other tegra devices are using cortex-a9..
[Samsung Galaxy R i9103] Grarak:
What other tegra device?

optimus 2x is using generic

https://github.com/p990-slimrom/android_device_lge_p990/blob/kk4.4/BoardConfig.mk#L21
[Samsung Galaxy R i9103] Adam77Root:
Perviously there was a distinction between simple Cortex and NEON-capable Cortex. Since NEON support is dropped, this is no longer this way. Generic is probably the only one without NEON flags.

Sent from my LG Optimus 4X HD
[Samsung Galaxy R i9103] karthik050782:
[MENTION=4443334]Grarak[/MENTION]: Oops! I haven't seen it...

Thanks adam! I have compiled again the omni 4.4 will try to put the patches of tonyp, hope it will boot...

Do we have random reboot in omni 4.3?
[Samsung Galaxy R i9103] kishoreinme:
We now have a booting CM11 based on 4.4.1 (KOT49E build) on Galaxy R

Things working (I have checked only these)

Wifi

Audio ( played a youtube video in browser)

2G/3G data

BT scan and pair

ADB

Calls:

Screen goes black at times during call

Call audio is only on speakers

Could not end a call.

Storage:

Both internal EMMC and external SD cards are NOT getting mounted.

So could not play any music or gallery or screenshot doesnt get saved

Camera app is not there so I could not check it

Frequent Reboots and Data has to be wiped on reboot.

Lets Debug issues one by one and try to get them solved.

Photo attached.

Sources and credits:

*Device tree : Grarak's cm11 tree ( https://github.com/Grarak/android_device_samsung_i9103/)

*Kernel : Grarak's 4.4 (https://github.com/Grarak/grakernel-n1)

*CM11 sources

*Frameworks/native branch changes merged as TonyP had pointed (https://github.com/p990-dev/android_frameworks_native/tree/cm-11.0-dev)

*Recovery updater hack (http://xdaforums.com/showpost.php?p=47692333&postcount=15&nocache=1&z=1484923475146786)

Other Devs Who had given us a working device tree historically . Esp Adam, karthik for their patience to answer my newbie questions .
[Samsung Galaxy R i9103] kishoreinme:
Starting with the storage issue , I guess it to be some problem with mounting stuff with vold

Mount gives

ls -l gives

Fstab.n1 and logcat attached.

Any pointers to solve this?
[Samsung Galaxy R i9103] Nikhil:
you and karthik with help of other devs have managed to bring a new life to galaxy R. Thanks a lot for this. :)
[MENTION=4394639]kishoreinme[/MENTION] could you please update OP with sources, credits and other details!
[Samsung Galaxy R i9103] kishoreinme:
Hopefully a new life :)

Lot more to get resolved.

I just built the sources the devs had pointed out and I take no credits.

The build is not stable and more broken functionalities and reboots. OP can be updated later I guess.
[Samsung Galaxy R i9103] Grarak:
Storage problem should be easy to fix

I will update my sources asap
[Samsung Galaxy R i9103] kishoreinme:
Is the change a part of device tree?
[Samsung Galaxy R i9103] Adam77Root:
Nice work! I have the storage issues with 4.4.1 on p880 too.

Yes, the camera app sometimes doesn't show up, it gets hidden because probably there are native errors with the camera. We had this back on CM10.

Sent from my LG Optimus 4X HD
[Samsung Galaxy R i9103] kishoreinme:
Thanks Adam

Would like to know if all are previously faced issues.

Is Storage problem coz of some new vold changes? standard issue it sounds so

I remember call balck screen in early GB days

and the call audio on speaker I remember when you gave a fix for skype call.Some libs from a Tab which did not have a telephony mic and speaker, I guess so

How to go about camera then?
[Samsung Galaxy R i9103] karthik050782:
Great buddy! You got the booting kit kat for us.. Hope all other issue will get fixed slowly..

First, lets fix the storage, check the grouper one.. storagelist.xml also u have to check..
[Samsung Galaxy R i9103] kishoreinme:
How do I go about the grouper stuff? grouper is with tegra3 one right? If you can point me what to look for then I will go about digging in.
[Samsung Galaxy R i9103] kishoreinme:
Able to mount and do a media rescan manually with

//Mount phone storage

mount -t vfat /dev/block/vold/179:49 /storage/sdcard1
mount -t vfat /dev/block/vold/179:4 /storage/sdcard0

//Trigger media scan

am broadcast -a android.intent.action.MEDIA_MOUNTED -d file:///storage/sdcard0
am broadcast -a android.intent.action.MEDIA_MOUNTED -d file:///storage/sdcard1

Not sure why it does'nt happen on boot. On reboot, could see Vold scanning the /dev/vold/ entries but doesnt mount them.Says Boot mount failed.

E/MountService( 1650): Boot-time mount failed (-1)

Regarding calls taken after recieving an incoming call. Speaker only audio. Could not end call and logcat shows crashes. Audio is routed in Tiny ALSA to speaker coz of some exception. Similar issues have been posted on omni 4.3 thread. Something common?

/TinyALSA-Audio Hardware( 474): audio_hw_set_mode(0x4002d948, 2)++
D/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_set_modem_state(1)
D/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_set_state(direction=2, state=1)++
I/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_get_device(40000000): available device 0x1
I/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_get_device(40000000): available device 0x2
I/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_get_device(40000000): available device 0x8
I/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_get_device(40000000): available device 0x4
I/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_get_device(40000000): available device 0x20
W/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_get_device: device type 40000000 not found
D/TinyALSA-Audio Mixer( 474): Unable to find default device
D/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_set_state(direction=2, state=1)--
D/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_set_device(2)
D/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_set_route(card=0,device=2)++
I/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_get_device(2): available device 0x40000000
I/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_get_device(2): available device 0x1
I/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_get_device(2): available device 0x2
[B]D/TinyALSA-Audio Mixer( 474): Setting Playback Path to SPK
D/TinyALSA-Audio Mixer( 474): tinyalsa_mixer_set_route_ctrl: mixer_ctl_set_enum_by_string(0x40dd1308, SPK)[/B]
D/AccelerometerListener( 1240): enable(true)
.
.
.
I/InCall ( 1240): CallCommandClient - Set Audio Mode: SPEAKER
I/AudioRouter( 654): Audio mode changing to SPEAKER
I/CallHandlerServiceProxy( 654): Updating with new audio mode: SPEAKER with mute false
I/InCall ( 1240): CallHandlerService - onAudioModeChange : SPEAKER

Log attached
[Samsung Galaxy R i9103] Adam77Root:
Same issue here on p880. Internal storage doesn't get mounted. External works though.

Regarding audio: check SGS2 KK update for TinyALSA updates.

Sent from my LG Optimus 4X HD
[Samsung Galaxy R i9103] kishoreinme:
Thanks Adam. Lt me follow them

Did you face the storage issue in 4.4 Build. (Not 4.4.1)
[Samsung Galaxy R i9103] Adam77Root:
No, it was working fine in 4.4, only broke in 4.4.1, didn't check 4.4.2 yet.

Sent from my LG Optimus 4X HD
[Samsung Galaxy R i9103] kishoreinme:
Currently building 4.4.2.

Is there any way to switch to 4.4.0 sources with repo commands? I wanna try 4.4.0 once
[Samsung Galaxy R i9103] Adam77Root:
Only if you revert all those new commits in each repo it was merged in.
[Samsung Galaxy R i9103] Grarak:
I already cherry picked all tiny alsa commits
[Samsung Galaxy R i9103] kishoreinme:
Building with updated tree.
[Samsung Galaxy R i9103] kishoreinme:
Having the 3 perfhud .so files in /lib/egl/ causes this. Delete them and it boots
[Samsung Galaxy R i9103] kishoreinme:
The very first incoming call was proper with earpiece and all subsequent calls and even after flashing again, the behaviour is same routing to speakers

The phone app doesnt respond to any touch inputs during incoming call. Outgoing call doesnt show any Phone app UI. Black screen below status bar with audio in speakers

Log attached.

Also is the following OK? It occurs very frequent.

E/gralloc ( 126): NvGrAllocScratchSet: NvGrAllocInternal failed
[Samsung Galaxy R i9103] kishoreinme:
Storage doesnt mount in 4.4.2 as well I tried adding mounts to init.n1.rc. Doesnt help.
[Samsung Galaxy R i9103] kishoreinme:
OP updated and added link to whatever build I have right now :)
[Samsung Galaxy R i9103] karthik050782:
I think its too early..
[Samsung Galaxy R i9103] kishoreinme:
I have pulled few changes from p990. Currently building them and hoping it to fix atleast storage. Tiny alsa as I get to read and hear is that its going to be a task to resolve audio.

The moderator wanted to cleanup the thread and its purpose and a valid download link if it is development thread.

So added it. I shall add disclaimer.
[Samsung Galaxy R i9103] karthik050782:
Gr8! I can understand, can you please post the gapps link... And all the best, i am getting sometime now for development.. Hope this weekend i will give a usuable omni 4.2.2
[Samsung Galaxy R i9103] kishoreinme:
Thats great karthik . Nice to hear that. I can take help from your device tree.

Something usable is the priority. Your previous experiences should prove good.

This is my first time and I just started working with a thought that "Why not give a try?" attitude.

I just downloaded PA gapps from

http://fs1.d-h.st/download/00084/EWF/DroidAcid.com--PA-gapps-full-4.4-20131114-signed.zip

Not tested though.

If possible kindly post your development tree link. I nay get some fixes.
[Samsung Galaxy R i9103] Adam77Root:
That's good, but I found the full version to be too big for testing and bringup, so I recommend that you use the "Mini Modular Package" from this thread.
[Samsung Galaxy R i9103] karthik050782:
Storage is fixed in omni 4.4.2 but everytime reboot i have to do a factory reset and also can't capture the data.. Till now not installing gapps, will try after installing gapps..

Weekend i will upload the device tree in my github... But i feel CM11 needs more fixes as they stop supporting tegra2..
[Samsung Galaxy R i9103] kishoreinme:
I face the same but Galaxy R logo passes after 5 minutes are so on reboot. Try waitin for sometime. After boot I see it has recovered around a GB of unknown files and put in /data/lost+found/ . May be it runs fsck i guess.
[Samsung Galaxy R i9103] kishoreinme:
Storage fixed with the help of karthik's tree.

Calls not yet.

Karthik, CM tree has telephony ril header. Removing breaks build. How come omni manages without it?
[Samsung Galaxy R i9103] karthik050782:
gr8, check the commit of omnirom, i didn't do anything for RIL.. Instead of CM, you can try slimkat which supports tegra 2... Not sure about PA..
[Samsung Galaxy R i9103] happy008:
I have a way to fix the call bug .View attachment libsecril-client.zip open this file you can see a libsecril-client.so in this. and then put this file into system\lib and change permission to rw-r-r .
[Samsung Galaxy R i9103] kishoreinme:
Thanks. I shall try

Did you try this? Which build does this come from?
[Samsung Galaxy R i9103] happy008:
i have tried this file .this file really can make call work well .this file come from Epsylon3's cm10.2 rom in cm-10.2-20130807-NIGHTLY-i9103.zip Build this build's call is work well link :http://atrix.tk/i9103/

if you can get touch with he you well have a easier work because when he make cm10.2 also have same problem like screenshot not work ,call bug and so on

by the way i thing cm11 have a bug when i use this it always reboot ,three time an hour

come from my gt-i9103 use omni 4.4.2
[Samsung Galaxy R i9103] kishoreinme:
Thanks for the inputs. Am occupied with my daily work and could not spend long time on this now. Will be back on this soon.
[Samsung Galaxy R i9103] kishoreinme:
Sure Karthik, I started with CM coz I liked some of the features like DSP manager and many of our devs had worked on it and can have some suport. Happy that omni most features like CM and am lovin it.

Also the frequent crashes are not good. For now I am busy with my daily job and shall come back to this if I have quite some time

I have previously worked with camera framework. Shall look into omni camera if I have short breaks.
[JAM, MDA Compact, S100 General] vacis:
can enyone help me with this???i wont to change the photo how can i do this???i mean the photo with the sympol from i mate or qtek in the start.thanks. :oops:
[JAM, MDA Compact, S100 General] ostoer:
You can find a complete set of instructions at Pocket PC Dubai
[JAM, MDA Compact, S100 General] duke911:
this is a great guide made by BTT...

http://xdaforums.com/viewtopic.php?t=22305

cheers :wink:
[JAM, MDA Compact, S100 General] vacis:
THANK YOU ALL.