[Q] YFTECH ME-12 Development Help - General Questions and Answers

Hello everyone!
I have been trying to compile a cyanogenmod kernel and rom for a cheap chinese tablet: yftech-me12. A clone of that tablet is Arnova 7h G3.
Tablet specs:
Capacity • Flash memory: 4 GB*
• Expandable via micro SDHC Slot up to 32 GB
Operating system • ANDROID™ 4.0 “Ice Cream Sandwich”
Processor • ARM Cortex A8 @ 1 GHz
RAM • 512 MB
Display characteristics • 7 inch - Capacitive points MultiTouch Screen 16 million colors
• 800 x 480 screen resolution
Video Playback1 • H.264, MPEG-42 up to 1080p resolution
With the above codecs, the device can play video files with the following extensions: .avi .mp4 and mkv
Audio Playback1 • MP3, WAV, APE, OGG, FLAC
Photo viewer3 • JPEG, BMP, GIF, PNG
Interfaces • Micro USB slave 2.0
• Audio Jack 3.5mm
• Micro SD slot
Communication protocols • WiFi
Miscellaneous • Front camera
• Built-in speaker
• Microphone
• G-sensor
I have downloaded the kernel source code from arnova.. Compiled the stock kernel to make sure it works and it does..
My problem is that i cannot compile a cyanogenmod kernel for my device! errors i cannot even understand!!
I've tried to install cyanogenmod for allwinner a13 tablets from here: http://forum.xda-developers.com/showthread.php?p=43072957
but the kernel will not boot! Plus i had to delete a few apks because my system partition is approx. 260mb and it would not copy the /system since there was not enough free space!
some other details about my device such as lsmod output:
8188eu 621096 0 - Live 0xbf103000
YFdecrypt 22118 0 - Live 0xbf0f8000
kt080x 5983 0 - Live 0xbf0f3000
mc32x0 7726 0 - Live 0xbf0ed000
dmt0567 10125 0 - Live 0xbf0e6000
bma250 7521 0 - Live 0xbf0e0000
byd693x_ts 9491 0 - Live 0xbf0d9000
pixcir_jc 13381 0 - Live 0xbf0d1000
sitronix_ts 23687 0 - Live 0xbf0c6000
goodix_gt82x 21242 0 - Live 0xbf0bc000
rtl8150 10305 0 - Live 0xbf0ab000
mcs7830 7589 0 - Live 0xbf0a5000
qf9700 9152 0 - Live 0xbf09e000
asix 24601 0 - Live 0xbf092000
usbnet 26253 3 mcs7830,qf9700,asix, Live 0xbf085000
sun5i_csi0 33604 0 - Live 0xbf077000
hi704 19664 1 - Live 0xbf06e000
hi253 21036 0 - Live 0xbf064000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf05f000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf055000
cedarx 9479 0 - Live 0xbf04e000
mali 151198 10 - Live 0xbf01c000
ump 48898 19 mali, Live 0xbf009000
sw_ts 18329 0 - Live 0xbf000000
cat /proc/partitions output:
ajor minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 262144 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 261120 nandh
93 64 1024 nandi
93 72 2232320 nandj
93 73 2231296 nandj1
179 0 3872256 mmcblk0
179 1 3122070 mmcblk0p1
179 2 500000 mmcblk0p2
179 3 249007 mmcblk0p3
dumps of my partitions /system /boot etc. : http://www69.zippyshare.com/v/97403369/file.html
Could someone PLEASE help me out.. I used a13_nuclear_defconfig from my stock kernel's source code to compile cm kernel and i get errors that it can not find certain files in the /drivers section.. copied files from stock source code and then some other errors occured.. so it fails..
Could someone give me some pointers? How do you guys start porting a rom to a new device without ANY previous support? Do you rewrite the modules source code to fit the cm kernel? how do you configure/find ramdisks to pack with your zlimage? can i use stock ramdisk with cyanogenmods lzimage to boot my device?
I'm not a developer and i just started learning about compiling kernels and modules etc..
STOCK ICS 4.03 is VERY SLOW even with nothing installed..
I hoped that Cyanogenmod 10 would run better on my device that's why i started all this but i'm seriously stuck...
Thanks in advance!!

Related

[Q] Xoom video/media player capabilities (curious)

Nvidia lists the following specs on their website for the Tegra2 :
Video decode
H.264
VC-1 AP
MPEG2
MPEG-4
DivX 4/5
XviD HT
H.263
Theora
VP8
WMV
Sorenson Spark
Real Video
VP6
Audio decode
AAC-LC
AAC+
eAAC+
MP3
MP3 VBR
WAV/PCM
AMR-NB
AMR-WB
BSAC
MPEG-2 Audio
Vorbis
WMA 9
WMA Lossless
WMA Pro
Can anyone confirm that the xoom can decode these?
Can the Xoom/honeycomb media player read subtitles (in) .mkv or .srt, sub/idx files?
The xoom can handle those, but only very specific versions of those. For example, don't try playing a 720p high profile h.264 video, because it won't play. So if you torrented a 720p video for example and it was an mkv file, not gonna play since they are almost all high profile h.264. You can convert them to baseline h.264 and it will play up to 1080p, but converting is annoying and takes time.
I am not sure what is out there on torrents, but I have some MKVs that I encoded and they have a bitrate of around 3mbit. According to this general tips section:
http://forum.xda-developers.com/showthread.php?t=969029&highlight=720p
The Xoom is supposed to be able to play video as long as the bitrate is under 20Mbit. The post references this:
https://supportforums.motorola.com/message/330326#330326
which says that realistically as long as the bitrate is under 4Mbit you should be fine.
The MKVs that I am trying to play, which are well under 20mbit and under 4mbit, skips like crazy and is unwatchable.
If I look at vmstat (via adb shell) while I am playing a movie using rock player in software decoding mode, the CPU goes to 100% (presumably in the kernel that android is using each core gets 100%, so there is a total of 200% available -- half ends up in system and half in user land):
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
2 0 74440 58584 254928 30112 158 1005 0 99 0 30 99 0 0
1 0 74564 58588 255036 30124 466 2263 0 99 0 22 99 0 0
1 0 68392 58880 261072 30128 367 2742 0 99 0 32 99 0 0
1 0 67136 58968 262216 30180 684 3604 0 99 0 32 99 0 0
2 0 67004 58976 262456 30180 224 1635 0 99 0 13 99 0 0
3 0 66632 58912 262756 30180 272 1721 0 99 0 10 99 0 0
3 0 60564 59724 266896 30160 414 2212 3 99 0 19 99 1 0
3 0 25136 60136 294812 30196 603 3372 0 99 0 76 9 0 0
4 0 25012 60128 294512 30184 472 2458 0 99 0 88 6 0 0
5 0 25020 60128 294448 30184 390 2121 0 99 0 99 3 0 0
3 0 24540 60128 294440 30164 265 1631 0 99 0 99 1 0 0
4 0 24416 60128 294576 30164 353 1768 0 99 0 93 6 0 0
4 0 24912 60128 293108 30140 332 1747 0 99 0 99 5 0 0
3 0 24788 60128 293076 30140 300 1604 0 99 0 99 3 0 0
While looking at hardware decoding mode, the system usage drops way down:
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
2 0 54116 58928 262524 30140 170 933 0 99 0 10 99 0 0
3 1 63780 58932 262520 30276 1119 4809 0 99 0 24 99 6 0
7 0 50184 59544 264332 31072 3493 19967 6 99 0 99 98 14 0
4 0 5620 59852 311776 31124 455 4765 2 99 0 61 18 0 0
3 0 5124 59868 311872 31064 368 4590 0 99 0 33 23 0 0
4 0 5124 59860 313024 30952 322 4625 0 99 0 39 44 0 0
3 0 4760 59860 313060 30936 390 5172 0 99 0 45 25 0 0
3 0 5256 59860 313032 30900 358 5475 0 99 0 38 30 0 0
3 0 4884 59868 312992 30876 336 5202 0 99 0 31 35 0 0
4 0 4636 59868 312856 30816 307 5036 0 99 0 34 36 0 0
3 0 5504 59904 312876 30816 378 5095 0 99 0 36 37 0 0
4 0 5504 59912 312884 30664 363 5046 0 99 0 33 44 0 0
3 0 4512 59924 312808 30656 288 4796 0 99 0 27 29 0 0
4 0 5256 59928 312908 30408 287 4927 0 99 0 32 38 2 0
3 0 5008 59928 312808 30404 367 5779 0 99 0 44 28 0 0
1 0 5132 59944 312820 30224 490 3432 0 99 0 36 74 0 0
But the playback remains fairly choppy. So all we need is the great devs at Rockplayer to stick the right code in for hardware decoding.
Presumably the native player uses hardware decoding which is why it is able to play video with framerates around 4mbit.
http://mediainfo.sourceforge.net/en
Download that and after installing, open it up and drag your mkv file into the window. Bet you that those videos are high profile h.264 which is the reason for the choppiness.
The reasons your processor max out in software mode is that its using the CPU to play the file. It drops down using hardware acceleration because its the GPU playing the file.
I used mediainfo to get the bitrate, which is under 4Mbit, which is under the limit that is quoted on the Motorola website. The fact that they may be a specific "media profile" in whatever converter you are using makes no difference -- only the bitrate is important.
Also, as mentioned in my post, I understand that the CPU drop is due to the use of hardware rendering. We still have to wait for either specific Xoom GPU support in Rockplayer or optimized code changes in Rockplayer.
Also, it appears that the native movies app is able to play my MKV files. It plays them much smoother, but they are still too choppy and the sound doesn't come through. The audio track on this is an AC-3 48KHz, 384Kbps audio stream.
No. You dont understand. The profile is everything. Bitrate means nothing. Tegra 2 is not capable of playing high profile hd h.264. The video you are trying to play is probably a high profile h.264 mkv file. There are various profiles for h.264 video. The Tegra 2 can play baseline profile. Almost all media is in high profile.
Do this for me, drag the media file you are trying to play into MediaInfo, and then go to View>Text. Then select the entire Video section and copy it and then paste it in here.
Thanks guys.
The sad thing is a cheap single core tablet with limited memory like the Archos 101 can play any video I throw at it without needing to convert them. The Archos 101 even plays DTS and AC-3 audio. Most of my videos are 720p HD and the only thing it doesn't play is 1080p. However, the Archos 101 is not perfect.
I was really hoping that the Xoom (or one of these other tablets) could at least come close to performing as well. How is it a company like Archos can make a cheap tablet perform so well (media wise) and these higher end tablets fall short?
kmd1970 said:
Thanks guys.
The sad thing is a cheap single core tablet with limited memory like the Archos 101 can play any video I throw at it without needing to convert them. The Archos 101 even plays DTS and AC-3 audio. Most of my videos are 720p HD and the only thing it doesn't play is 1080p. However, the Archos 101 is not perfect.
I was really hoping that the Xoom (or one of these other tablets) could at least come close to performing as well. How is it a company like Archos can make a cheap tablet perform so well (media wise) and these higher end tablets fall short?
Click to expand...
Click to collapse
software, honeycomb is buggy, its hardly optimized. no one really knows what the tegra 2 is capable of yet.
the facts are simple, there no tegra 2 device capable of playing high profile h264 right now.
tegra 2 devices are just now making it to market and its new untested unproven hardware.
secondly there are only two devices released or pseudo released(in the case of the adam) that even use this hardware. not alot of info to go on here.
at this point ask anyone here and they can't give you any 100% accurate answer, because we simply don't know. its ALL speculation at this point.
you have two camps on this issue. one camp, the hardware people claim that because both the adam and xoom use tegra 2 and can't play h264 high profile that its a hardware limitation.
the second camp takes the side that because this is new hardware, it needs proper software and drivers to handle the decoding and that this is the reason for the poor playback. this camp believes it will be fixed down the line with an update.
the second camp is the more feasible scenario. anyone that knows anything about hardware and software understands that hardware is worthless without good software.
let me give a prime example everyone knows video encoding takes time. if you want to encode a 20 minute video lets say you use handbrake and encode the video using your cpu in 14 minutes. but wait, whats this? you have a $500 nvidia graphics card in your system? its a big arse paper weight right now ain't it?
lets fix that, lets get the proper software and drivers and encode that same 20 min video by offloading to this powerful gpu. done in 5 minutes.(*actually times vary based off settings and actually hardware)
get the picture?
however, this does NOT mean that the tegra 2 is without fault. it could be the hardware and its simply not capable of high profile and never will be. we simply don't know, because we don't have any good information from nvidia or motorola or notion ink. we don't know what its true capabilities are.
all we know is that the tegra 2 with the current available devices and software cannot play high profile h264.
all the rest is speculation.
..........
From an XBMC developer:
http://forum.xbmc.org/showpost.php?p=735285&postcount=41
Tegra2 can't hw decode h264 [email protected] or above. I know because I have one (Tegra2 dev kit). That really limits the video content to SD. Too bad, it's a nice chip except for that.
Click to expand...
Click to collapse
This guy worked on porting XBMC to iOS and has videos like this:
Code:
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 9 frames
Muxing mode : Header stripping
Codec ID : V_MPEG4/ISO/AVC
Duration : 1mn 52s
Bit rate : 6 478 Kbps
Nominal bit rate : 5 660 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
playing like this:
http://vimeo.com/20636064
on the ipad.
Same file playing on two different Tegra 2 tablets:
http://www.youtube.com/watch?v=lXWu6m33EP0&feature=player_detailpage#t=231s
... with the amount of Tegra2 for the next month,
i think we could download all videos in tegra2 useable formats (720p/1080p) and nvidea will also adress this topic, so i am not worried about ...
muyoso said:
From an XBMC developer:
http://forum.xbmc.org/showpost.php?p=735285&postcount=41
This guy worked on porting XBMC to iOS and has videos like this:
Code:
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 9 frames
Muxing mode : Header stripping
Codec ID : V_MPEG4/ISO/AVC
Duration : 1mn 52s
Bit rate : 6 478 Kbps
Nominal bit rate : 5 660 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
playing like this:
http://vimeo.com/20636064
on the ipad.
Same file playing on two different Tegra 2 tablets:
http://www.youtube.com/watch?v=lXWu6m33EP0&feature=player_detailpage#t=231s
Click to expand...
Click to collapse
take his with a grain of salt. all he said was i have a tegra 2 dev kit and tegra 2 can't do the high profile h264.
whats this even mean? is there something in this dev kit that actually lists what the tegra 2 is capable of hardware wise? whats in this dev kit, whats the real reason it won't play.
ill take him for his word when pigs fly out of his ass.
http://developer.nvidia.com/tegra/tegra-devkit-features
its just hardware, no magical software to be had there. which means what? hes got the same software we do.
also id like to point out that there is a VAST difference between making android support another codec so it can play a video and making android offload to the gpu using drivers. key word there folks, drivers.
back to the cuda example, two things are needed to tango. first you need the proper nvidia drivers. and secondly, you need an application designed to work with those drivers in order to have it successfully utilize the gpu. xbmc can only proved the app to interface with what exists, they can't do anything else.
ps:
al gore invented the internet.
Is there like a cut off date for peoples denial about tegra 2's shortcomings? Like a year from now when it still can't play video [email protected] h.264, will people still be claiming its a lack of software?
Davilla did massive testing of the tegra 2. You think there were drivers from apple for the ipad? No.
Look, there may be a software solution if the tegra 2's cpu is powerful enough to decode hd h.264, but there is massive evidence that it will never hardware decode that video. I think its an important enough shortcoming to inform people about and not lead them on with some promise of future software.
Sent from my SPH-D700 using XDA App
Any official info from NVidia about this H.264 high profile hardware decoding capability?
Anyone reached NVidia?
e.mote said:
Most Honeycomb tablets announced will have a Tegra2 in it, and video playback is an important component, so I'm confident the issue will be addressed, if not from Nvidia, then from a 3rd-party commercial media player like Coreplayer.
Click to expand...
Click to collapse
Please, not that Coreplayer for Android rumor again. (I've been waiting for too long)
It's not really CoreCodec's fault. Android has been a pretty fast moving target, and my guess is that Nvidia hasn't been exactly timely with software support for the Tegra2, else the VS G-Tab would've had decent playback by now.
My reading of the tea leaves is that we'll probably see CP either around the Honeycomb mass launch or a bit after. Anyway, it'll come when it'll come.
Now, VLC, I think will be a fair bit longer in coming,
http://ivoire.dinauz.org/blog/index.php?post/2011/02/02/VLC-on-Android
muyoso said:
The xoom can handle those, but only very specific versions of those. For example, don't try playing a 720p high profile h.264 video, because it won't play. So if you torrented a 720p video for example and it was an mkv file, not gonna play since they are almost all high profile h.264. You can convert them to baseline h.264 and it will play up to 1080p, but converting is annoying and takes time.
Click to expand...
Click to collapse
From Xoom office website, we know that Xoom supports AAC, H.263, H.264, MP3, MPEG-4, ACC+ Enhanced, OGG, MIDI, AMR NB, AAC+. If u want to play video on Xoom, the video format and video coding must be correct.
So I suggest u convert your MKV files to Mp4 H.264 1280*720 for playing.
I did a test, and I can't find any diffirence between 1080P and 720P, SO I recomend convert video to 720P, and the converted file size is small. therefore, u can transfer more video to Xoom.
For those use HandBrake, attachment is the [email protected] preset for playback in Tegra2
muyoso said:
The xoom can handle those, but only very specific versions of those. For example, don't try playing a 720p high profile h.264 video, because it won't play. So if you torrented a 720p video for example and it was an mkv file, not gonna play since they are almost all high profile h.264. You can convert them to baseline h.264 and it will play up to 1080p, but converting is annoying and takes time.
Click to expand...
Click to collapse
MKV is a container format, which supports holding unlimited number of video, audio, picture or subtitle tracks inside a single file, can’t be played on the Motorola Xoom. only the video format and video encoding are right, Xoom can be play it.
So, not because Xoom can't play 720P high profile h.264 video, but the video format is wrong. I suggest u convert MKV 720p h.264 video to MP4 720P H.264 for playing on Xoom.

[Q] Allwinner A13 nuclear_evb touch screen driver

I have tried to get my touch screen working after completely bricking my china tablet. Managed to get stable ROM+kernel running, but the touch screen isn't working.
http://forum.xda-developers.com/showthread.php?t=2343531
that is what I am running, but none of those screen drivers worked. It gave error;
Verifying update package...
E:signature verification failed
Installation aborted.
My device is black on the screen side and the backplate is white and it has metal stripe on the back. Also it has 760 written inside the backplate.
It is Wi-Fi only model with front camera.
I may be able to give you further info if I can get my mouse plugged and working to the tablet.
Thanks in advance. :highfive:
Here is my lsmod data
[email protected]:/ $ su
[email protected]:/ # lsmod
8192cu 575431 0 - Live 0x00000000
8188eu 581006 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 33255 0 - Live 0x00000000
cedarx 11869 0 - Live 0x00000000
ov5640 31583 0 - Live 0x00000000
mt9m112 15359 0 - Live 0x00000000
gt2005 19412 0 - Live 0x00000000
gc0308 18408 1 - Live 0x00000000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
mma7660 6857 0 - Live 0x00000000
mxc622x 6088 1 - Live 0x00000000
mecs 4078 1 - Live 0x00000000
bma250 7545 0 - Live 0x00000000
dmard06 7987 0 - Live 0x00000000
ft5x_ts 44577 0 - Live 0x00000000
mali 150572 12 - Live 0x00000000
ump 48978 23 mali, Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
xpad 9358 0 - Live 0x00000000
murmeli said:
Here is my lsmod data
[email protected]:/ $ su
[email protected]:/ # lsmod
8192cu 575431 0 - Live 0x00000000
8188eu 581006 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 33255 0 - Live 0x00000000
cedarx 11869 0 - Live 0x00000000
ov5640 31583 0 - Live 0x00000000
mt9m112 15359 0 - Live 0x00000000
gt2005 19412 0 - Live 0x00000000
gc0308 18408 1 - Live 0x00000000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
mma7660 6857 0 - Live 0x00000000
mxc622x 6088 1 - Live 0x00000000
mecs 4078 1 - Live 0x00000000
bma250 7545 0 - Live 0x00000000
dmard06 7987 0 - Live 0x00000000
ft5x_ts 44577 0 - Live 0x00000000
mali 150572 12 - Live 0x00000000
ump 48978 23 mali, Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
xpad 9358 0 - Live 0x00000000
Click to expand...
Click to collapse
hi the lsmod wont be any good unless it was run on a firmware with a working touchscreen... as this this only shows loaded modules etc... so if your ts was not working it wont tell us the name of the correct driver for your TS..
so was this run on a firmware with a working TS??
Inside 4ndroid said:
so was this run on a firmware with a working TS??
Click to expand...
Click to collapse
No I used mouse & keyboard, the device is nuclear_evb, but I can't find drivers for that exact model
murmeli said:
No I used mouse & keyboard, the device is nuclear_evb, but I can't find drivers for that exact model
Click to expand...
Click to collapse
right i need to explain something before we carry on basically the nuclear_evb is just a name there are 1000's of tablets with same name but different hardware as they are clones.. (cheap chinese knock offs)
now because you do not have a firmware with a working touchscreen when you run lsmod it doesnt actually tell us your TS driver because the correct driver is not a loaded module..
the only way to find a working driver is to test every driver you can out there or go through all firmwares one by one until you find one where the TS works and then run lsmod on that firmware to find out your TS driver..
i hope this makes sense...
if you need access to a full range of firmwares for these tablets you could visit my support forum and sign up for a free account..
www.insideforums.tk

how install touch driver

hi
i have tablet t98 now install custom rom but now not working touch
and read this post http://forum.xda-developers.com/showthread.php?t=2189569
but i do not know how install touch driver and which one use touch driver
check with 1smod
Code:
[email protected]:/ # lsmod
lsmod
8188eu 581006 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
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 11468 0 - Live 0x00000000
mali 114383 4 - Live 0x00000000
ump 34310 9 mali, Live 0x00000000
nand 126290 8 - Live 0x00000000
[email protected]:/ #
thanks

inject touch screen modules (compability patch)

Hello everyone,
I has a Chinese tablet "luxya MID702-sc" with the base android 4.0.4.
I find many rom cyanogenmod 4.2.2,4.1.2 but the modules are not the same results the touch screen does not respond.
I adb install and uberizer to retrieve the list of modules, I have to recover the original rom but I still can not inject a properly ...
Here are the modules loaded in the original version:
Modules:
mxc622x 6326 1 - Live 0xbf153000
mecs 4078 2 - Live 0xbf14f000
rtl8150 10305 0 - Live 0xbf148000
mcs7830 7581 0 - Live 0xbf142000
qf9700 9152 0 - Live 0xbf13b000
asix 24601 0 - Live 0xbf12f000
sun5i_csi0 33271 0 - Live 0xbf121000
gt2005 36907 0 - Live 0xbf111000
gc0308 22312 1 - Live 0xbf107000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf102000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf0f8000
cedarx 9351 0 - Live 0xbf0f1000
mali 115122 8 - Live 0xbf0c7000
ump 34209 11 mali, Live 0xbf0b8000
byd693x_ts 9094 0 - Live 0xbf043000
zet622x 19182 0 - Live 0xbf035000
ssd253x_ts 21452 0 - Live 0xbf02b000
ft5x_ts 93593 0 - Live 0xbf004000
inet_ctp 2227 4 byd693x_ts,zet622x,ssd253x_ts,ft5x_ts, Live 0xbf000000
_________________________________________
cyanogenmod 10 release:
Modules:
8188eu 581006 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 11 mali, Live 0x00000000
mxc622x 6088 0 - Live 0x00000000
mecs 4078 1 - Live 0x00000000
sp0838 20079 0 - Live 0x00000000
gc0329 18016 0 - Live 0x00000000
gc0308 18408 0 - Live 0x00000000
ft5x_ts 44577 0 - Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
xpad 9358 0 - Live 0x00000000
I need some help to find out what drivers ts is used and created a patch with these modules for injection, I tested many patch and its still not working I think there are missing modules. ..
here is the rom I try to install:
http://forum.xda-developers.com/showthread.php?t=2343531
sorry for my english :android-displeased:

Need help with A13 tablet Android 4.0.4

Hi guys
I have a A13 7 inch chinese tablet which got stuck on the logo and wont boot. Looking around forums I learned I need to know the kind of G sensor, camera, and TS my tablet has. Typing a couple of commands I got this. I'd like someone to tell me which are the sensors appropriate for my tablet so I can look for the right firmware. Any help would be very appreciated
export PATH=/data/local/bin:$PATH
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ lsmod
cdc_subset 1588 0 - Live 0xbf0e9000
cdc_eem 2915 0 - Live 0xbf0e5000
cdc_ether 7651 0 - Live 0xbf0df000
rtl8150 10305 0 - Live 0xbf0d8000
mcs7830 7581 0 - Live 0xbf0d2000
qf9700 9152 0 - Live 0xbf0cb000
asix 24601 0 - Live 0xbf0bf000
usbnet 26229 6 cdc_subset,cdc_eem,cdc_ether,mcs7830,qf9700,asix, Live 0xbf0b2000
sun5i_csi0 30803 0 - Live 0xbf0a5000
gt2005 20634 1 - Live 0xbf09b000
gc0308 18408 1 - Live 0xbf092000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf08d000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf083000
cedarx 9351 0 - Live 0xbf07c000
mali 150902 4 - Live 0xbf04a000
ump 49026 15 mali, Live 0xbf037000
mma7660 7219 0 - Live 0xbf031000
ssd2533_ts 9832 0 - Live 0xbf02a000
nt11003 50228 0 - Live 0xbf019000
goodix_ts 13732 0 - Live 0xbf011000
ft5x_ts 45793 0 - Live 0xbf000000
[email protected]:/ $
---------------------------
[email protected]:/ # getevent
getevent
add device 1: /dev/input/even
name: "mma7660"
add device 2: /dev/input/even
name: "ssd253x_ts"
add device 3: /dev/input/even
name: "sun4i-keyboard"
could not get driver version
add device 4: /dev/input/even
name: "axp20-supplyer"

Categories

Resources