Hi, guys
I have a Samsung i9008 which is specific for China Mobile 3G TD-SCDMA.
Kernel version: 2.6.29-zeus1
I have download samsung i9008 resource code and compiled a tun.ko file.
Installed successfully without any errors (insmod).
# insmod /system/tun.ko
insmod: setup_module '/system/tun.ko'
# dmesg | grep tun
<6>[ 7.047790] IPv4 over IPv4 tunneling driver
<6>[ 7.066741] IPv6 over IPv4 tunneling driver
<6>[ 174.259918] tun: Universal TUN/TAP device driver, 1.6
<6>[ 174.266601] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
# lsmod
tun 11036 0 - Live 0xbf283000g_serial_softmodem 18504 0 - Live 0xbf279000
tiwlan_drv 823192 0 - Live 0xbf1ab000
omaplfb 16584 0 - Live 0xbf1a1000
pvrsrvkm 149188 43 omaplfb, Live 0xbf177000
modem_relay 71096 0 - Live 0xbf160000
vibrator 4104 0 - Live 0xbf159000
gsd4t 6900 0 - Live 0xbf152000
accel 18012 1 - Live 0xbf148000
PL_sensor 20276 0 - Live 0xbf13e000
compass 16848 1 - Live 0xbf134000
samsung_battery 24823 0 - Live 0xbf128000
dpram_flashless 183768 4 - Live 0xbf0f6000
param 17376 0 - Live 0xbf0ef000
rfs_fat 233792 6 - Live 0xbf0b0000 (P)
rfs_glue 75052 1 rfs_fat, Live 0xbf098000 (P)
fsr_stl 250268 6 - Live 0xbf055000 (P)
fsr 324408 4 dpram_flashless,param,fsr_stl, Live 0xbf000000 (P)
I have installed BusyBox. I have tried many version of BusyBox.
But when I connect in VPNC or run vpnc's script, the phone reboot.
I think the procesure of setup tunnel cause phone crash.
I can't find the solution to resolve.
Related
Hi, guys
I have a Samsung i9008 which is specific for China Mobile 3G TD-SCDMA.
OS: OMS 2.0 (from Android 2.1?)
Kernel version: 2.6.29-zeus1
I have download Samsung i9008 resource code and compiled a tun.ko file.
Installed successfully without any errors (insmod).
# insmod /system/tun.ko
insmod: setup_module '/system/tun.ko'
# dmesg | grep tun
<6>[ 7.047790] IPv4 over IPv4 tunneling driver
<6>[ 7.066741] IPv6 over IPv4 tunneling driver
<6>[ 174.259918] tun: Universal TUN/TAP device driver, 1.6
<6>[ 174.266601] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
# lsmod
tun 11036 0 - Live 0xbf283000
g_serial_softmodem 18504 0 - Live 0xbf279000
tiwlan_drv 823192 0 - Live 0xbf1ab000
omaplfb 16584 0 - Live 0xbf1a1000
pvrsrvkm 149188 43 omaplfb, Live 0xbf177000
modem_relay 71096 0 - Live 0xbf160000
vibrator 4104 0 - Live 0xbf159000
gsd4t 6900 0 - Live 0xbf152000
accel 18012 1 - Live 0xbf148000
PL_sensor 20276 0 - Live 0xbf13e000
compass 16848 1 - Live 0xbf134000
samsung_battery 24823 0 - Live 0xbf128000
dpram_flashless 183768 4 - Live 0xbf0f6000
param 17376 0 - Live 0xbf0ef000
rfs_fat 233792 6 - Live 0xbf0b0000 (P)
rfs_glue 75052 1 rfs_fat, Live 0xbf098000 (P)
fsr_stl 250268 6 - Live 0xbf055000 (P)
fsr 324408 4 dpram_flashless,param,fsr_stl, Live 0xbf000000 (P)
I have installed BusyBox and VPNC. I have tried many version of BusyBox.
But when I connect in VPNC or run vpnc's script, the phone reboot.
I think the procesure of setup tunnel cause phone crash.
I changed some parameters in .config and re-compiled tun.ko. The phone reboot as before.
I can't find the solution to resolve.
New to android, but fairly good in linux so I can understand most technical stuff with these devices.
I have a chinese tablet, softwinners a13 clone. I rooted it the day I got it, and it was running fine until one day it booted into recovery, and wouldnt restore anything because it could not mount any folders. Long story short, I flashed the faastjb to it, and it booted up like a charm. I should also note no other images would succeed in livesuit, all gave error 162 except faaastjb.
As mentioned the TS would not work, so I cracked the tablet open and seen that the chip is a zet6251 chip??
Foolishly, I did not dump the factory rom, but I did do some sort of backup in which I was able to view the factory init.sun5i.rc file to see what drivers it had installed. Shows the zet6221 driver. Here I thought, awesome, theres a zet6221 driver in the thread. So I ran the batch file to insert the drivers, and still my touchscreen doesn't work. The gsensor works properly, but no touchscreen.
I tried to manually insmod the driver, but it gives me file already exists, and when I check lsmod, it shows zet6221 as loading, all other drivers are live.
insmod attempt :
Code:
[email protected]:/vendor # insmod zet6221.ko
insmod zet6221.ko
insmod : init_module 'zet6221.ko' failed (File exists)
dmesg output (snippet) :
Code:
page 127 [0] doesn't match! continue to download!
<4>[ 177.021251]
<4>[ 177.021254] write : 2c
<4>[ 177.040032] read : 3d 3d 3d page=123 offset[0]=113 offset[1]=116 offset[2]=119 offset[3]=122
<4>[ 177.404167] page=125 offset[4]=118 offset[5]=121 offset[6]=124 offset[7]=127
<4>[ 177.411239] page 127 [0] doesn't match! continue to download!
<4>[ 177.411247]
<4>[ 177.411250] write : 2c
<4>[ 177.430029] read : 3d 3d 3d page=123 offset[0]=113 offset[1]=116 offset[2]=119 offset[3]=122
<4>[ 177.794167] page=125 offset[4]=118 offset[5]=121 offset[6]=124 offset[7]=127
<4>[ 177.801243] page 127 [0] doesn't match! continue to download!
<4>[ 177.801252]
<4>[ 177.801255] write : 2c
<4>[ 177.820032] read : 3d 3d 3d page=123 offset[0]=113 offset[1]=116 offset[2]=119 offset[3]=122
<4>[ 178.184164] page=125 offset[4]=118 offset[5]=121 offset[6]=124 offset[7]=127
<4>[ 178.191233]
I didnt paste all of the dmesg output. It was pretty much all this over and over with varying offsets.
lsmod output :
Code:
zet6221 46023 1 - Loading 0x00000000
device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
camera 53105 0 - Live 0x00000000
videobuf_dma_contig 6243 0 - Live 0x00000000
videobuf_core 20242 1 videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 200007 21 - Live 0x00000000
ump 34213 9 mali, Live 0x00000000
mxc622x 6310 0 - Live 0x00000000
nand 225000 8 - Live 0x00000000
And finally the original init file that I fortunately had backed up. This was backed up after rooting, but the tablet was fully functioning.
Just the part that is relevant...
Code:
#insmod key & tp driver
# insmod /system/vendor/modules/sun4i-ts.ko
insmod /system/vendor/modules/sun4i-keyboard.ko
# insmod /system/vendor/modules/ft5x_ts.ko
# insmod /system/vendor/modules/gt811_ts.ko
insmod /system/vendor/modules/zet6221.ko
# touch key
insmod /system/vendor/modules/hv2605.ko
# insmod mali driver
insmod /system/vendor/modules/ump.ko
insmod /system/vendor/modules/mali.ko
#insmod video driver
insmod /system/vendor/modules/cedarx.ko
#insmod gsensor driver
insmod /system/vendor/modules/gsensor.ko
# insmod /system/vendor/modules/bma250.ko
# insmod /system/vendor/modules/mma7660.ko
# insmod /system/vendor/modules/dmard06.ko
I will be getting another tablet from the friend that got me this one sometime in the next week, and I will do a factory backup from it to extract drivers. I really don't want the factory firmware on it again... it seemed to run very slow in comparison to this. it was originally 4.1.1
Hi.
Did you manage to fix this? I have the exact same problem
same problem
Hello.
I have 2 identical A13 tablets. I wanted to install CWM for sdext --> ended with endless recovery mode. One is still with its original rom and working.
For the problematic one I've tried several roms - but touch was not working. I can't find the factory image.
At the moment I loaded FaaastJB 2.5. Tried every touch drivers stated in that topic but without success. Did managed to get the g-senzor working with one of the users driver pack (M3AT5O5_V1).
I also tried to import original .ko and modifying script.bin but without success (could be that I'm doing sth wrong).
Can someone please help me make my driver pack or help me by creating it.
Here are all the possible info about the tablet that i can think of. Msg me if something is missing
A13, 10 partitions.
Model name: TY_MID, android 4.2.2, TYnuclear-ococci-eng 4.2.2 JDQ39 20131120 test-keys
Code:
[email protected]:/ # lsmod
lsmod
8188eu 767523 0 - Live 0x00000000 - wifi
device 26958 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000 - usb/eth
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34042 0 - Live 0x00000000 - video
siv120d 18948 1 - Live 0x00000000 - camera
camera 59581 1 sun5i_csi0, Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
dmard06 11119 0 - Live 0x00000000 - G-sensor
mc32x0 14040 0 - Live 0x00000000 - G-sensor?
cedarx 11869 0 - Live 0x00000000 - video
mali 199863 80 - Live 0x00000000
ump 34137 17 mali, Live 0x00000000
A13_gslX680 119756 0 - Live 0x00000000 (F)
nand 225000 8 - Live 0x00000000
[email protected]:/ #
Can't share outside links, but I have uberizer backup and rom dump available. Can also upload to any file sharing service if needed.
After much searching, and flashing, I found a rom that gets the TS working again. It indeed has a zet6251 driver, and I flashed it to my tablet. now works like a charm. Be forewarned, its default is not english, and I couldn't tell you what language it is, but you can set it to english.
This is a factory ROM, not rooted, no bells and whistles, but it does have a working TS and Gsensor!!
I'm just syncing the compressed image on my google drive, and will share once completed.
Google drive link :
drive.google.com/file/d/0B5un_i3IN5ecclYzM2xDeXlWaVE/edit?usp=sharing
add https to the beginning... unable to post links.
Hope it helps
midnightmekanik said:
After much searching, and flashing, I found a rom that gets the TS working again. It indeed has a zet6251 driver, and I flashed it to my tablet. now works like a charm. Be forewarned, its default is not english, and I couldn't tell you what language it is, but you can set it to english.
This is a factory ROM, not rooted, no bells and whistles, but it does have a working TS and Gsensor!!
I'm just syncing the compressed image on my google drive, and will share once completed.
Google drive link :
drive.google.com/file/d/0B5un_i3IN5ecclYzM2xDeXlWaVE/edit?usp=sharing
add https to the beginning... unable to post links.
Hope it helps
Click to expand...
Click to collapse
Hi.
First of all, thanks a lot for answering this after such a long time. I completely forgot that I posted in here.
I suffered a lot with this issue, but I managed to get a module working to solve the problem after a few weeks working on it. I forgot about this post, or I would have replied to you with my solution.
If you still want to try FaaastJB rom, you can get the patch that I develop in reply #2038 in page 68 of the FaaastJB topic, and let me know the result.
Regards
Please, I need help!
I¨ve installed this rom http://forum.xda-developers.com/showthread.php?t=2343531&page=11 to my a13 tablet. I had some troubles to start because touch doesnt worked for me, so dont any patch posted there, anyway I used a CWM backup to take my working drivers and use them in this new rom. Finally I got ts working, but camera and gsensor still not working. So reading the replies to search a similar case solved, I looked the #108 post of the rom¨s thread, because I had a similar problem (my working camera drivers doesnt loaded), there the creator of the rom attached two zip files to flash in bootloader, so I downloaded the zip and I rebooted in bootloader mode (using the native option from the rom). When it restarted the environment was cwm, as I choosed reboot in bootloader mode I thought bootloader mode could be similar, and I installed the zip from sd card. After that my tablet¨s touch doesn¨t working anymore. I restored my rom created with CWM backup, it load as usually does, but touch does not respond. I¨ve restored my "CWM roms" before many times, and always worked. Now when I install a new rom, the ts just doesnt works, even applying the patches. So I think something in the bootloader is not working ok, by my fault. I just was wondering if there is a way to recover my touch again, maybe "flashing back" the zip file, or something like this. Please help me, I can do everything to fix that problem
Here is my lsmod when ts was working
127|[email protected]:/ # lsmod
8188eu 621056 0 - Live 0xbf188000c
8192cu 575431 0 - Live 0xbf0e0000
rtl8150 10305 0 - Live 0xbf0d9000
mcs7830 7581 0 - Live 0xbf0d3000
qf9700 9152 0 - Live 0xbf0cc000
asix 24601 0 - Live 0xbf0c0000
sun5i_csi0 33255 0 - Live 0xbf0b2000
gc0308 37173 1 - Live 0xbf0a2000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf09d000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf093000
dmard10 11532 0 - Live 0xbf08c000
dmard06 11119 0 - Live 0xbf085000
mma7660 9397 0 - Live 0xbf07e000
cedarx 9351 0 - Live 0xbf077000
mali 151532 8 - Live 0xbf045000
ump 49746 17 mali, Live 0xbf031000
A13_gslX680 92383 0 - Live 0xbf016000
ssd253x_ts 16247 0 - Live 0xbf00e000
zet6221_ts 19640 0 - Live 0xbf000000
Now that ts does work anymore my lsmod log is
[email protected]:/ $ lsmod
8188eu 621056 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
cedarx 11869 0 - Live 0x00000000
videobuf_dma_contig 6251 0 - Live 0x00000000
videobuf_core 20242 1 videobuf_dma_contig, Live 0x00000000
mali 150572 8 - Live 0x00000000
ump 48978 13 mali, Live 0x00000000
mxc622x 6088 0 - Live 0x00000000
mecs 4078 0 - Live 0x00000000
sp0838 20079 0 - Live 0x00000000
gc0308 37173 0 - Live 0x00000000
gc0329 18016 0 - Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
xpad 9358 0 - Live 0x00000000
Something particular in my case is that in my ts chip inside the tabet is gsl1680 (yes, I opened it, but some time before getting the problem)
And in the camera flex says gc0329, and in the lsmod, even when all was working ok said is gc0308. So please help me. The file I¨ve flashed is http://dl.xda-developers.com/attachdl/07afd34232d9f76b3afcda55fceeb2bd/52c669bd/2/1/3/6/4/6/5/bootloader-gc0308.zip (original link because I cant attach dont know why)
Hope you understand my bad english and help me, I know maybe you have a lot of solutions, but Im really starting using android, so I hope you can help me.
Already solved, I¨ve flashed with stock rom.
Q&A for [MOD] FaaastJB v2.5 A13 Allwinner with Jelly Bean 4.2.2 by Toxicro
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Rahul Dhobi said:
Rom needed for 4.3 allwinner a13,Is this rom work on 4.3 inch tablet??
Click to expand...
Click to collapse
I also have a 4.3
this screen 480 x 272 Pixel
touch screen driver is ssd253x-ts.ko
my problem is that I only see a quarter of the screen :crying:
How can modify the pixel of the screen?
lsmod stock rom
mxc622x 6310 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 33868 0 - Live 0x00000000
gt2005 36911 0 - Live 0x00000000
gc0308 16888 1 - Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 114191 4 - Live 0x00000000
ump 34206 5 mali, Live 0x00000000
ssd253x_ts 22661 0 - Live 0x00000000
goodix_touch 18266 0 - Live 0x00000000
ft5x_ts 51253 1 goodix_touch, Live 0x00000000
inet_ctp 2227 2 ssd253x_ts,goodix_touch, Live 0x00000000
nand 164126 6 - Live 0x00000000
Click to expand...
Click to collapse
Change DPI setting in build.prop
djd2o said:
I also have a 4.3
this screen 480 x 272 Pixel
touch screen driver is ssd253x-ts.ko
my problem is that I only see a quarter of the screen :crying:
How can modify the pixel of the screen?
lsmod stock rom
Click to expand...
Click to collapse
Just modify ro.sf.lcd_density value in /system/build.prop and check changes I think ro.sf.lcd_density=90 is best suited for 4.3 inch screen
Help!
Hello guys, i hope someone is still active on this tread
I need help to get my TS working, and gsensor too. I have tablet with allwinner 13 (name of the device: for-fun q3 main 1.4v) and i tryed to install faaaastJB 2.5 on it and i succeded but as i mentioned i can't get TS and gsensor working... I even extracted gsensor config and TS modules from old working device but i can't get them into new rom :S
Code:
[email protected]:/ # lsmod
lsmod
8188eu 581030 0 - Live 0xbf1b8000
rtl8150 10305 0 - Live 0xbf1b1000
mcs7830 7581 0 - Live 0xbf1ab000
qf9700 9152 0 - Live 0xbf1a4000
asix 24601 0 - Live 0xbf198000
sun5i_csi0_dual 36744 0 - Live 0xbf18a000
bg0328_b 14558 0 - Live 0xbf182000
gc2015_b 21402 0 - Live 0xbf177000
sp2518_b 18789 0 - Live 0xbf16d000
sp0a19_b 21692 0 - Live 0xbf162000
gt2005_b 20941 0 - Live 0xbf157000
sp0838_b 21620 0 - Live 0xbf14c000
siv121d_b 15443 0 - Live 0xbf143000
gc0329_b 19593 0 - Live 0xbf139000
gc0308_b 20055 1 - Live 0xbf12f000
bg0328 14554 0 - Live 0xbf127000
gc2015 21398 0 - Live 0xbf11c000
sp2518 18785 0 - Live 0xbf112000
sp0a19 21692 0 - Live 0xbf107000
hm5065 28571 0 - Live 0xbf0fb000
gt2005 20941 0 - Live 0xbf0f0000
gc0309 19830 0 - Live 0xbf0e6000
gc0329 19593 0 - Live 0xbf0dc000
siv121d 15443 0 - Live 0xbf0d3000
sp0838 21620 0 - Live 0xbf0c8000
gc0308 20051 1 - Live 0xbf0be000
videobuf_dma_contig 6251 1 sun5i_csi0_dual, Live 0xbf0b9000
videobuf_core 20242 2 sun5i_csi0_dual,videobuf_dma_contig, Live 0xbf0af000
mecs 4078 1 - Live 0xbf0ab000
mxc622x 6088 1 - Live 0xbf0a5000
cedarx 9351 0 - Live 0xbf09e000
mali 150892 8 - Live 0xbf06c000
ump 49238 13 mali, Live 0xbf058000
zet6221 20285 0 - Live 0xbf040000
nand 225000 10 - Live 0xbf000000
[email protected]:/ #
If is still someone active, please help me get this rom working! Thank you!
EDIT: Dont look at this post, next one is under this. I dont know how to delete this, so anyone from admins can delete this.
gsensor
Hello guys after 2 days of pain with my little friend, finnaly got working TS and x,y axes working! Now, only problem left is gsensor file.
Here you go lsmod file and please tell me which one is gsensor and which one i should edit. If needed i can link you the gsensor.cfg file.
Code:
[email protected]:/ # lsmod
lsmod
zet622x 15814 0 - Live 0x00000000
ssd253x_ts 21647 0 - Live 0x00000000
ft5x_ts 51435 2 zet622x,ssd253x_ts, Live 0x00000000
device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34042 0 - Live 0x00000000
gc0308 16888 1 - Live 0x00000000
camera 53105 1 sun5i_csi0, Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 200007 34 - Live 0x00000000
ump 34213 13 mali, Live 0x00000000
mxc622x 6310 0 - Live 0x00000000
nand 225000 8 - Live 0x00000000
[email protected]:/ #
Navcity NT1710 A13 TS ZET5233
My tablet is a Navcity NT-1710 A13 and touch the chip is ZET5233, I have the original ROM because it was bricked on the boot screen. Can you help me?
Hi,
Is toxicro always helping in this forum?
FastJB livesuit Error
Flashing fast jb on Allwinner A13 Q8_V12 but as other firmwares FAST JB stop and rollback when reach at 3%. Even livesuit fails to write the original rom provided by the reseller. Help needed.
not working
My Lsmod
[email protected]:/ # lsmod
lsmod
mma8452 6990 0 - Live 0xbf1b9000
sun4i_vibrator 1793 0 - Live 0xbf1b5000
rtl8150 10305 0 - Live 0xbf1ae000
mcs7830 7581 0 - Live 0xbf1a8000
qf9700 9152 0 - Live 0xbf1a1000
asix 24601 0 - Live 0xbf195000
sun5i_csi0 33256 0 - Live 0xbf187000
sp0838 19043 0 - Live 0xbf17e000
gc0328 18313 0 - Live 0xbf175000
sp0a19 20147 0 - Live 0xbf16c000
ov2655 16871 0 - Live 0xbf163000
gc2015 19711 0 - Live 0xbf15a000
hm2057 23023 0 - Live 0xbf150000
gt2005 20632 0 - Live 0xbf146000
sp2518 19274 0 - Live 0xbf134000
gc0308 23577 1 - Live 0xbf12a000
cedarx 9351 0 - Live 0xbf10d000
mali 150844 4 - Live 0xbf0db000
ump 49202 9 mali, Live 0xbf0c7000
gc0329 19169 1 - Live 0xbf0be000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf0b9000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf0af000
gslX680 432406 0 - Live 0xbf040000
nand 225000 8 - Live 0xbf000000
[email protected]:/ #
getevent
add device 1: /dev/input/event3
name: "mma8452"
add device 2: /dev/input/event2
name: "gslX680"
add device 3: /dev/input/event0
name: "sun4i-keyboard"
could not get driver version for /dev/input/mice, Not a typewriter
add device 4: /dev/input/event1
name: "axp20-supplyer"
My touch works
driver-gslx680
i backup my script.bin,gslx680.ko,gslx680.idc from stock rom
then backed up to faastjb then touch works
but no gsensor and Camera
And I can't even play angry birds,temple run 1
In stock rom i played Injustice without lag(using Ramexpander)
Please fix
hi i tied every TS module but still not working
can you plz help me
and thnx
You can make a rom with Android 4.4 to allwinner A13 tablets ?
tauch tps0649 ver1.0 plase tauch script.bin
how to access Ismod and edit it?
How To Disable "GPU RENDERING" in FaaastJB 4.2.2 ROM by TOXICO
hi guys this is my first thread i love this rom its working great on my a13 a13q8 v5.0 tablet but i cant use puffin browser it displays message disable force gpu rendering. i went in developers options and there it is unchecked i dont know what to do now dint found anything in build.prop and this rom dont got init.d folder dont know how to contact toxico as m a new member cnt even post there plz help or contact toxico plz tell him abt this problm i love his rom plz help me wd this thnks in advance
FaaastJB V2.5 hangs after about 20 sec
Hey. Finaly got my allwinner A13 to work with FaaastJB V2.5 with everything working. Only problem now is that it hangs after 20 sec or so. Any help is greatly appriciated.
A13 FaaastJB v2.5 touchscreen driver
Hei all. Any help at this point would be greatly appriciated. Been trying to get this working since the first Faaast JB version.
In the following lsmod I have working touch but not wifi, in FaaastJB 2.5 I have working wifi but no touch. Been trying every module in both this and other forums.
I dont think its far from true that I have been trying on and off for 2 year now.
Code:
lsmod
dmard06 11119 0 - Live 0xbf156000
mc32x0 13474 0 - Live 0xbf14e000
8188eu 581006 0 - Live 0xbf0a1000
mcs7830 7581 0 - Live 0xbf09b000
qf9700 9152 0 - Live 0xbf094000
asix 24601 0 - Live 0xbf088000
sun5i_csi0 33255 0 - Live 0xbf07a000
gc0308 32383 1 - Live 0xbf06c000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf067000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf05d000
cedarx 9351 0 - Live 0xbf056000
mali 150700 8 - Live 0xbf024000
ump 49082 11 mali, Live 0xbf011000
gsl1680 51394 0 - Live 0xbf000000
Thank you!
Rom works, TS works, g-sensor works.
Now only the camera has to work. Can someone help me with that?
update:
Ok I made it work
Hi,
I have successfully rooted my android led tv running with jellybean 4.3 using king root apk ,However after reboot my wi-fi is not working.
and now connected with Ethernet , to the TV. Neeed help to troubleshoot to identify the wi-fi issue.
did the android reset of TV,still wi-fi not working ,i don't have any stock TV rom.
below is the lsmod info
[email protected]_en_4k2k:/ # lsmod
bnep 10090 0 - Live 0x00000000
rfcomm 32694 0 - Live 0x00000000
hidp 12995 0 - Live 0x00000000
bluetooth 143532 5 bnep,rfcomm,hidp, Live 0x00000000
uhid 5463 0 - Live 0x00000000
ehci_hcd 45925 0 - Live 0x00000000
usb_storage 39931 1 - Live 0x00000000
cywee_virtual 4845 0 - Live 0x00000000
mdrv_ir 15259 0 - Live 0x00000000
rc_mstar_tv 1627 0 - Live 0x00000000
mali 275156 21 - Live 0x00000000
ump 48823 15 mali, Live 0x00000000
below is the supplicant file info /data/misc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=/data/system/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
netcfg output not showing in wireless device in the output
lo UP 127.0.0.1/8 0x00000049
eth0 UP 192.168.0.102/24 0x00001043
sit0 DOWN 0.0.0.0/0 0x00000080
ip6tnl0 DOWN 0.0.0.0/0 0x00000080
the directory /data/misc/wifi/wpa_supplicant.conf is empty.
attaching RT2870STA
and dmesg to the thred
sorry im unable to attach the files.
please let me any additional files it required to troubleshoot help...
please help to resolve the issue.
i too got same problem in my Noble 4k tv. Any help?