Messages

1

Users / CM11A and GC100 - are that combination receives notifications from wall switch?

« on: October 02, 2012, 10:12:49 pm »

After review of CM11A driver code I wondering if I connect CM11A using GC100 to the core, the core will receive the notifications from e.g. wall switch.
I assume that GC100 do not send info from RING rs232 pin. Could someone check this? If it is true I have proposal of the fix for this issue.
I just would like to know if this will work before I will buy CM11A and GC100...

Cheers,
ppiszc

2

Users / Re: Android QOrbiter

« on: October 02, 2012, 09:54:33 pm »

Sorry for very very long delay but I unfortunately flashed device using wrong image and I had my device totally bricked..
I had to find proper flash image to make alive my china android tablet.
I found three issues connected with qOrbiter (Ticket #1585).
Let me know if somene would like to check apk with fixes (I have apk for droid based on armv5).

Cheers,
ppiszc

3

Users / Re: Android QOrbiter

« on: May 19, 2012, 10:00:46 pm »

golgoj4,

On my cheap tablet there are no directory Linuxmce and file config.xml on sdcard (qorbiter do not create such file and directory).
I've made copy the directory and file from HTC Desire S (where qorbiter works fine) but this do not change the behavior of qorbiter on the tablet - qorbiter do not remember IP nor device number and exits just after hit the "Go!" button.
So my conclusion is that qorbiter has probably problems with sdcard operations (reading and writing) on specific cheap tablets.
Is the source code of android qorbiter on svn ? I can try to dig in this area.

ppiszc.

4

Users / Re: Android QOrbiter

« on: March 27, 2012, 09:49:58 pm »

golgoj4

Please find below link to logcat from my droid made during QOrbiter starts.
h**p://pastebin.com/rP4MhBpn

If you need more logs just let me know.

ppiszc

5

Users / Re: Android QOrbiter

« on: March 25, 2012, 01:11:33 am »

Ok thanks guys i will be looking into this further. Quick question Are you on wifi?

I use wifi.

ppiszc

6

Users / Re: Android QOrbiter

« on: March 24, 2012, 11:05:04 pm »

golgoj4,

You are right - I installed app from lasmarthomes.com site.
After install app from market, now I can put the IP of core (I use 192.168.90.1) and #device, but after hit "Go!" the app exits (for the while on the screen there is message "Guessing android phone, Loading Phone skins").
After a few try I observe that app do not remember core IP nor device no. (in the device nomber there is usually some random data).   

Cheers,
ppiszc

7

Users / Re: Android QOrbiter

« on: March 24, 2012, 10:13:50 pm »

golgoj4,

I just installed (first time) qorbiter on my Android (cheap china device - "Leader TAB R70"*) and after "splash screen" qorbiter exits without any message. I can't even put IP of my core.
Is it possible to run qorbiter on my device or I have to buy something like Galaxy tab?.
I can run any app if you want to dig deep into my droid.

Cheers,
ppiszc

*Some info from Android system info app:
BuildInfos
Android version : 2.1-update1-1.0.0
Release Codename : REL
API LEVEL : 7
CPU ABI : armeabi
Manufacturer : unknown
Board : trout
Brand : rockchip
Device : sdkDemo
Display : V0.18.ECLAIR.FH_TONE_8188.20110114.102044
Fingerprint : rockchip/sdkDemo/sdkDemo/trout:2.1-update1/ECLAIR/eng.temp.20110114.102044:user/test-keys
Host : temp-desktop
ID : ECLAIR
Model : rk2818sdk
Memory
Download Cache Max: 112MB/ Free: 96.76MB
data Max: 248MB/ Free: 186MB
External storage Max: 7.39GB/ Free: 4.48GB
Total RAM: 200MB
Free RAM: 82.51MB
Threshold RAM: 16.00MB
Screen
Resolution: 800 x 480
Refresh Rate: 73726.48
X factor for DIP: 1.0
Density: 160 dpi
Pixel per inch X: 25.4 dpi Y: 25.4 dpi
OpenGL
OpenGL Version supported : 0.0
OpenGL Version supported : OpenGL ES-CM 1.0
Vendor : Android
Renderer : Android PixelFlinger 1.2
Extensions :
GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_OES_EGL_image GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap