Android Tablets Forum banner
1 - 20 of 20 Posts

·
Registered
Joined
·
16 Posts
Discussion Starter · #1 ·
Could somebody please help.
I lost touchscreen function on my new Eken M009s after flashing it with Vestinious ROM.
Even I tries to revert to the Eken ROM it has not returned
Please help.
 

·
Registered
Joined
·
10 Posts
Could somebody please help.
I lost touchscreen function on my new Eken M009s after flashing it with Vestinious ROM.
Even I tries to revert to the Eken ROM it has not returned
Please help.
Hi shomer,

seems you have the uor615 ts on your m009s, you can try the HYBRiD Uberoid HoneyCombMOD v2, there's a special script for this device.

Good luck upgrading.
 

·
Registered
Joined
·
146 Posts
Could somebody please help.
I lost touchscreen function on my new Eken M009s after flashing it with Vestinious ROM.
Even I tries to revert to the Eken ROM it has not returned
Please help.
Keep trying different custom roms, it should work with some firmware.

Hope this helps
 

·
Registered
Joined
·
8 Posts
It hapened to me after flashig with multitouch version.Mine is singletouch
http://www.eken.com/support/
none of the firmware on that support work, and the 1.5.5 they put up yesterday is a corrupt archive.

I swear they are terrible support.

1.5.2 single, doesnt work.
1.5.2 multi, doesnt work.
1.5.3 multi, doesnt work.
-- they claim the 1.5.3 up now is single... doesnt work.
1.5.5 cannot even download properly.

even the 1.5.5 for the m008s is corrupt.

so I've tried the vt1603, vt1609, uor615x and none of them work with this EKEN m009s - I've opened it to ensure it is a m009s and it is.

I wish there was a way to physically query the hardware to determine what touchscreen chip it has... if I were the only one who is stuck with this unbelievable problem, I'd have ditched this as a joke and faulty hardware... but others are in the exact same situation after trying everything.

EKEN support will not help at all... the supplier is as useful as tits on a bull and that leaves everyone else in the world who have not had the issue...

those of us in this spot, no help... those who are not in the spot, cant help..

not a bad way to make money is it, sell a device that fails and then give you the run around... nice one EKEN.
 

·
Registered
Joined
·
1 Posts
Can sombody plz help, i hav recently got an android tablet and cant seem to find a rom that works, it has a 7 inch screen, the led is green (red when charging), it says mid on the box. Android version 2.3, model no. WonderMedia WM8650, black audio output socket there are no markings on the back. The WiFi keeps dropping off and has problems connecting, the calender wont work, angry birds has disappeared from the tablet and the market and most other apps come up as incompatible. I just want a rom that will put a working calender, e-book reader, angry birds and keeps WiFi connection, fast would be good to!
 

·
Registered
Joined
·
1 Posts
I have the exact same tablet that Ubernoob describes except for I'm running Android 2.2, and mine is a 2 point multi touch. I've tried installing Modroid (versions 1.5.3 and 1.5.1) and altered the files as indicated for the 2 point touch screen, but got neither version to work. I understand that these versions sometimes just won't work with my device, so my question is: is there a previous version of Modroid that may be compatible for me? If not, can anyone make a good recommendation for another program to use? I'm a noob myself and am not exactly sure where to go from here.. but I've reinstalled the factory firmware for the time being so anything's worth a shot. Thanks!!
 

·
Registered
Joined
·
42 Posts
look on the last page in modroid thread and I have uploaded an envboot file that works with the 2point multitouch also the battery bug is fixed in that one.
if you need any other file let me know I have an M009s with 2point multitouch.
I also needed to change the wmt_scriptcmd. if you need that I can upload it for you.
but try with the one you have first.
 

·
Registered
Joined
·
1 Posts
¡¡¡LO LOGRÉ!!!

me puse a jugar con los parámetros que encontré en la red.

instalé el android 2.2
kernel 2.6.32.9
build froyo ver 1.5.3-20110819

hice algunos cambios en el env_uboot.

setenv memtotal 212M
setenv mmcid 0
setenv lpj AUTO
setenv ipaddr 192.168.0.2
setenv serverip 192.168.0.1
setenv gatewayip 192.168.0.1
setenv netmask 255.255.255.0
setenv kernelargs
setenv bootargs mem=${memtotal} root=${filesystem-NAND_mtd} noinitrd rootfstype=yaffs2
rw console=ttyS0,115200n8 lpj=${lpj} ${android_bootargs} ${platform_bootargs}
quiet

setenv bootcmd
nandrw r ${kernel-NAND_ofs} 0x1000000 ${kernel-NAND_len};
if iminfo 0x1000000; then
run kernelargs;
bootm 0x1000000;
fi;
echo No kernel found

setenv logocmd
nandrw r ${wmt.nfc.mtd.u-boot-logo} ${wmt.display.logoaddr} 10000;
nandrw r ${wmt.nfc.mtd.u-boot-logo2} ${wmt.display.logoaddr2} 40000;
nandrw r ${wmt.nfc.mtd.kernel-logo} ${wmt.kernel.animation.addr} 80000;
display init force;
decompanima -f ${wmt.display.logoaddr2} 0x3000000;
decompanima -f ${wmt.display.logoaddr} 0x3000000

setenv wmt.display.logoaddr 500000
setenv wmt.display.logoaddr2 550000
setenv wmt.kernel.animation.addr f600000
setenv wmt.audio.i2s vt1603:f1:f2:ff:ff:100
setenv wmt.io.pwbn 100:0:2000
setenv wmt.eth.param 1
setenv wmt.gpi.bat [0:0:00020000:d8110040:d8110080:d8110000:d8110480:d81104C0][1:0:00000020:d8110040:d8110080:d8110000:d8110480:d81104C0][2:1:00010000:d8110040:d8110080:d8110000: d8110480:d81104C0]
setenv wmt.gpo.camera1 1:0:78110040811008081100C0
setenv wmt.gpo.wifi 6:1:6:d8110040:d8110080:d81100C0
setenv wmt.gpt.gsensor 3:8:d8110040:d8110080:d8110000:d8110480:d81104c0:83000000:d8110300:8:d8110320:6
setenv wmt.io.bat 3:2:1000:db1:b8b:db1:d7a:d43:d0c:cd5:c9e:c67:c30:bf9:bc2:b8b
setenv wmt.io.gsensor 1:3:4:0:1:1:-1:2:-1
setenv wmt.sys.keypad commonboard:1:rc_1:4:c0_73:c1_72:r0_9e:r1_8b
setenv wmt.pwbn.param 100:0:500
setenv wmt.ui.storage 7
setenv touchic true
setenv touchirq gpio0
setenv touchcodec vt1603
setenv wmt.io.touch 1:vt1603:2:800:480
setenv wmt.bus.i2c i2c0:1:1:i2c1:1:1
setenv bootdelay 1
setenv wmt_ui_hibernation 1
setenv wmt_sys_powerhold 0
setenv wmt.gpo.vibrator 1:1:28110040811008081100C0:1
setenv wmt.camera.param 0:0:0
setenv android_bootargs init=/init
setenv platform_bootargs wmtvo=2:1:24:800:480:60
setenv wmt.display.param 2:0:16:0:0:0
setenv wmt.display.tmr 40000:0:10:46:800:20:10:23:480:10
setenv wmt.display.pwm 0:25:50:99
setenv wmt.io.mxcgsensor 1:3:4:0:1:1:1:2:-1
setenv wmt.io.d06sensor 1:3:4:1:-1:0:1:2:-1
setenv wmt.vt160x.bat 0:1:10:0
setenv panelres.x 800
setenv panelres.y 480
setenv wmt.model.no puzhi_7inch_vt1603
setenv wmt.io.ts.2dcal 592 -32615 124311591 22305 157 -11032910 147589

con ésto ya jaló el touch.
espero le ayude a alguien más.
 

·
Registered
Joined
·
24 Posts
Hi. You try this?

"If you have a GREEN LED unit and your touchscreen doesn’t work, or it wont boot, you can rename one of the GREEN_env_uboot files to env_uboot and
replace the original in \firmwareinstall\env and reflash. Or simply take the env_uboot file from your devices stock firmware."

Extracted from modroid_readme.txt

In my case, this work. In recent version of uberoid, the charger as a option 30. The option 1 is indicated to green led.

Downloa this document: http://www.mediafire.com/?ofbln2h9z76e60q Maybe help you.
 

·
Registered
Joined
·
4 Posts
Sorry I can't post yet but i have a question that i thinks really worth asking that i havent seen the answer for. Can you use a 30pin to hdmi adapter for hdmi output? It would be an adapter just like the usb one im guessing.
 

·
Registered
Joined
·
2 Posts
Accidentally i install the eken m001 rom on my M009S... I works but the touchscreen has lost. I tried several times, tryng to reinstall to one original rom M009S, but it can't read the original rom... When i view the structure of ROM M001 Vs M009S.

ROM M001 is on /script folder.

Rom M009s is on /FimwareInstall and have a wmt_scriptcmd on root microSD

How i can reflash to original rom.

Please Help....
 

·
Registered
Joined
·
24 Posts
Accidentally i install the eken m001 rom on my M009S... I works but the touchscreen has lost. I tried several times, tryng to reinstall to one original rom M009S, but it can't read the original rom... When i view the structure of ROM M001 Vs M009S.

ROM M001 is on /script folder.

Rom M009s is on /FimwareInstall and have a wmt_scriptcmd on root microSD

How i can reflash to original rom.

Please Help....
Hi. Try uberoid rom with switch 30 in charger.
 

·
Registered
Joined
·
1 Posts
Hi! I've experienced the same issue.

now I solved it,so let me say...

1)if you use 'Eken M009s' that of Uberoid config file number 1,
it will be 'm009sg'.
2)the touch sensor of 'm009sg' is 'uor615x' and is not 'vt1603'
or 'vt1609' either.
3)you need add a 1 line to config file(env_uboot) near 'setenv wmt.io.touch 1:uor615x:0:800:480'.
4)'setenv wmt.uor615x.param 20000:320:58:58:3:1:3:7:1200:32:3500:150:3950:150'
5)it means that initialize touch sensor when firmware install.
6)and successfully your touch sensor is alive again!

fundamentally config file lacks a bit of parameter.
this is the reason that a sensor was not able to initialize correctly.
 
1 - 20 of 20 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top