yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] fonix232:
I'm not blaming your work, I just do not understand why you won't go with the Tablet layout for tablets (it's not been fcked up with other tabs on 800*480, although Ainol did bork it in their official 4.0.3 release).

About recovery, I meant exactly the new recovery.imgs. Your site had outdated info (and only the CPIO method), and I did not check the first page.

Nice work anyway, will try it on my Aura as soon as I can (touchscreen is broken so it's mostly unusable). CM9 seems promising here, and if you could check the released Ainol BSP, and see if you can back/forward port the sensor and hwlibs, it would make it easier to make camera and hw accel to get working. Also, just saying, some modules are missing (like, the RealTek USB Wireless driver, for one, or the mma7660, both used by not just the Aura, but some other A10 based tabs too)

Biggest problem here is the fragmentation of boards. There are many out, based on the A10, with mostly the same features, but some are a bit different, I can bring the Aura-Novo7A example: Aura has no vibrator, no back camera, different WiFi and g-sensor, etc etc. They need different boot.img (insmodding different services, like the csi0 interface, has different arguments to properly work with devices), and as such, they can not be supported with one generic image. As there are more A10 based tabs coming (namely the Ainol Novo 7 Aurora and Elf), and they have even more different HW (bigger screen, more RAM, more NAND, etc), the best would be to make a generic tree, a common build folder, what contains most of the common bits and things, and let all a10 based devices derive from that, so anyone can easily get a 100% working build of their own. I would be able to help out with that, given that the Ainol BSP contains 99% of all sources (but for GB, not ICS), and the remaining 1% are proprietary files like wifi firmware, and gles drivers.
[Miscellaneous Android Development] fun_:
"you won't go"?

I posted that Tablet UI can be used with 120dpi on 800x480 device several days ago and I also added description about it in post#3. then I posted about Tablet UI on 800x480 160dpi case.

no method is described on my site. both method for 2.3/4.0 ROM are described in post#2 here. what's outdated?

at this time my images are for ainol NOVO7 Advanced. there is message "DO NOT USE IF YOUR TABLET IS NOT LISTED BELOW" on my site and post#1 here. please read carefully.

I understand different A10 tablets are different. different kernels must be used for different tablets. different kernel modules must be used for different tablets. different sensor libs must be used for different tablets. it's very clear.

I can't understand why do you think "some modules are missing" in "CM9 for NOVO7A". it's for NOVO7A.

if you check CM7 for Telechips tablets page on my site, you can see I made CM7 for 40+ similar but different tablets. I know well there are a lot of "similar but different" chinese cheap tablets.

EDIT:

to make CM9 for other tablets, no source/BSP is necessary. it's not used in my CM9 for NOVO7A (and other CM for other tablets on my site). I need some info and some files from stock rom, and my free time.
[Miscellaneous Android Development] fonix232:
Please forgive me my inattention, I did not want to begin a hatewar, I was simply trying to help.

When I saw your page I only saw download for the CPIO recovery. That's what I was referring to.

I did read carefully this time ;)

Actually, no. Kernel and kernel modules can match, the exception is the init.rc files in the initramfs. It would be pretty easy to have a base system and a flashing script what determines the tablet itself, and creates a proper boot.img from zImage and one of the many initramfs'. For libs, Ainol releases have all the needed ones in them, but you only copied the used ones.

Actually, the Novo7A includes all the modules, you just didn't copy them.

Yes I get that. That's why I said to have a common device tree, and branch out devices from that.

Like if I didn't develop CM9 yet for some devices :rolleyes: I'm just saying, that BSP contains many things, including libcamera, libhardware, libhardware_legacy, and some more source codes, plus some device configs. And it would be great if we would have as much source code based things as possible, instead of pulling all the libs from an actual device. It is always better to work with source than to work with compiled libs, it gives us more freedom. And the only no-source proprietary libs are the egl libs, and the wifi firmwares (as I said before).

EDIT:

Was anyone able to find a way to boot into fastboot with the new layout? Maybe it's my Aura, maybe it's u-boot, but no luck :S
[Miscellaneous Android Development] fun_:
you may not know, I have some dev thread and I always got a lot of worthless messages. I'm trying to ignore them, but sometimes I'm very frustrated.

I'm sorry if I misunderstood your messages.

then there was no support for ICS ROM at that time but at this time it's supported. this is work-in-progress project. I feel nothing was wrong if something was not available. same for now and future.

if you are talking about ICS ROM, yes, there are a lot of modules which are not used on NOVO7A but can be used on other tablets. but I'm making CM for GB ROM too. if you check GB ROM, you can see there are a lot of "missing" modules. anyway it's not a problem at all. I can get necessary modules for some another tablet from that tablet.

there is no reason I have to add support for other tablets in my very first images for NOVO7A. and I never say I don't add support for other tablets in future. just saying "it must be easy ..." must be easy. if it's necessary I can say a lot of things which is not done yet. but time is needed to do it.

there is no reason to do it now and I never say I don't do it.

one more thing, anyone can fork my repo and can do it freely. I have no responsibility to do anything that people want. I just do my work for my fun.

I never said BSP is useless. it will be useful if we can use it. but at this time "pulling files from rom" is very easy and very usefull for me too. source may give us freedom but it must not give any free time to me.

I got a lot of help/advice/suggestion from people. but so far no one gives me free time.

at this time there is no reason not to use binary files from rom even if it gives bug or limitation.

I guess there is fastboot support code in u-boot in ICS ROM but I don't know how to enter fastboot mode.
[Miscellaneous Android Development] fonix232:
No problem at all, I understand that, as a developer :D

Actually, all the modules can be found in the Ainol Novo7A builds. Atleast so far that was the case.

Yes, I see that, I'm just saying that for further development, if further devices came in, it is easier to manage with a common tree, plus the sub-devices referring to common.

Sure, some guys from TabletRepublic began working on device trees too, but for AOSP (should be almost the same, except some CM-specific flags). And I did it too, but for the Aura. I think I might be able to create a common base, create some more new flags to be used with the sub-devices, and then we can easily work on different trees + common.

I have some (not too much) free time, but no ability to compile ICS (would take around 20 hours on my PC), so I can provide help with coding and testing, but not with building.

I am also saying the source usage for the future - while there is no reason yet, there will be soon, like calibrating sensors, etc etc.

Fastboot is supported, yes, there should be a way to boot into it but apparently that would need some u-boot interfacing (accessing the terminal through JTAG maybe?).
[Miscellaneous Android Development] fun_:
err, "if you see GB ROM, you'll notice a lot of modules are missing". if you are taking about compiling full NOVO7A kernel source from ainol, yes, I can make any modules for GB ROM from source. but there is no source for ICS ROM. I'm not sure currently supplied modules in ICS ROM are enough for any future unknown tablets.

anyway, it's not problem. if I try to add support for some tablet, I can get necessary modules from that tablet even if it's not available in current ICS ROM.

I think current my repo is very generic. I'm sure there are few N7A specific definitions and not enough for other tablet. but converting it to common should be easy.

I made common tree for telechips and rockchip. no reason not to do it for allwinner.
[Miscellaneous Android Development] fun_:
for ICS ROM works fine. but, for GB ROM, screen goes black after bootanim lol... I have to revert some change :(

EDIT:

a10gb_update.zip is replaced now. it works fine :)
[Miscellaneous Android Development] fonix232:
No, I'm saying that the actual firmware releases contain more modules that the one in your releases. We will need a newer kernel release, and that will not probably come in the near future.
[Miscellaneous Android Development] KillerKink:
Fun,

I have gotten stock 4.0.3 to work on p76ti. Yeah, its from N7A firmware since there does not seem to be one available from Teclast that I can find(only 4.0.1). :)

I am starting to work on your tree but notice that extract-files.sh is getting from /system/lib/modules while it should be from /system/vendor/modules?

I am using your master branch from cm_device_allwinner_a10 which should be for CM9?
[Miscellaneous Android Development] fun_:
cm_device_allwinner_a10 is for CM9. there is no rule to fix path to somewhere. you can change it freely.
[Miscellaneous Android Development] KillerKink:
Great! Thanks for the confirmation. Yes, its easily changed but I am just surprise that yours is not from /system/vendor/modules/ as that is where its from in N7A 4.0.3 firmware.
[Miscellaneous Android Development] zenitraM:
Hi!

First of all, thanks for your great work!

I've been fiddling with a few ICS firmwares for my N7A and found some strange things.

I read somewhere that the Ployer Momo9 Enhanced firmware worked better than the Ainol one, and flash worked out-of-the-box, so I went and flashed it expecting it to not even boot. To my surprise, it booted and it works quite well (only WiFi and HW buttons are missing, and rotation is inverted).

So I flashed the recovery on the Momo image and, to my surprise, the N7 can't boot the recovery by pressing any button while booting. So I booted manually, and then made a backup to try to use Ainol's boot.img (and then kernel modules) on Momo's firmware. But then the hardware buttons didn't work... on recovery :confused: Isn't recovery using its own kernel? Because in that case, there might be additional flags /something hidden on the firmware that set hardware features.

I tried flashing back Novo7 ICS and then restoring the complete backup of Momo's ICS (all partitions).. but it didn't boot then, which seems to confirm this.

EDIT: Nevermind, found it's something related with the script.bin file which contains device configuration as in: http://elinux.org/Hack_A10_devices. I'll investigate more.
[Miscellaneous Android Development] mghilardi3:
Compatibility on Ainol Novo 7 Paladin

I have the Novo 7 Paladin. I have been looking for a 'custom ROM' or AOSP build as the original software isn't great. I have been eyeing this thread with the highest of hopes as a CM9 build would be a dream come true on this thing.

Let me know if it would work, or if anyone happens to know of a ROM that would.

Update: Well strike that looks like the older Ainols use the Allwiner and the new ones use Igenic XBurst soooo. nevermind.
[Miscellaneous Android Development] Cooper 5150:
Hey Fun,

First. thanks for the info. everything on this thread is great info. I am still a lkittle new with tablets and flashing, and with your process. I am good with phones, but i just got am LY-F1 Tablet, and iv`e read a little in here for it , but nothing very definitive for that particular brand. Could you possibly help with that? I have the LY-F1 4 Gb of memory with basically all the same specs that I have read in here for the other people with an Allwinner LY f1 Tab. My market works, perfectly, actually better than with the original Firmware, and my camera works, and will now do video, the only thing that does not is my speaker, but it came that way when i pulled it out the box brand new (Any ideas how to fix that. LOL.) and I started this process with flashing the official/original from mfg. stock firmware, and then the ICS 4.0 from the MOMO9 and it worked perfectly with zero flaws, or issues with the drivers, or market. I know the capacitive buttons on the side don't work, but everything else did and actually runs good.

Thanks again for all of this work. If you have something for that particular, i would be quite greatfull, if you don't have the time, no worries man! I really want to be able to back everything up, I can get into the stock recovery (hld Power and Vol. + for 7 Sec. and let go and wait 3 sec. and it should pop up. Also if you hold Vol - instead i get some weird other language with about 18 options to click on but i am scared to touch anything because i cant read it) Is there more of a detailed, or step by step for CWM to work opn the LY-F1? I see that a few others have gotten it to work, but i am new to flashing tablets and i know a little but i am clearly not on the same level as everyone else, buut i am learning, and i am trying to get better. Any help woukld be greatly appreciated once again!!!!

Thanks you all are great.
[Miscellaneous Android Development] mystombox:
Ainol has 2 different branches of hardware

One with MIPS another with ARM cpus.

The paladin/basic unfortunately is MIPS

Aurora/elf/advance are using ARM
[Miscellaneous Android Development] FezzFest:
The Novo7 Basic also uses a MIPS SoC.
[Miscellaneous Android Development] KillerKink:
fun, hope you dont mind. I am branching out your original work for gingerbread for CM7 on p76ti on another thread.
[Miscellaneous Android Development] fun_:
of course no problem :) enjoy!
[Miscellaneous Android Development] fun_:
new CM9/CWM5 images are uploaded. my laptop was broken and I was busy so my changes are very few...

network location is now working. Google Maps/Earth work fine.

install-recovery.sh is added to "for ICS ROM" too. CWM5 install procedure is almost same as "for GB ROM".

a lot of changes are done by CM team so something may be changed. enjoy!

----

I noticed there is "CWM5 for ainol NOVO7 Aurora" in some chinese forum. I checked recovery.img in it and I confirmed it is "for Advanced".

I'm surprising that kernel for Advanced is working on Aurora. probably some parts don't work correctly but fortunately it's not important for CWM.

I'll make images for Aurora/Elf too. I don't recommend to use "for Advanced" on other tablets.

(at first I'll make images for bmorn V11 and Scroll Excel...)
[Miscellaneous Android Development] matt5039:
hi fun

androtab.info is down....do you have alternative link

Tq
[Miscellaneous Android Development] fun_:
someone tried to download files with 100+ connections :(

web server was restarted and should work now.

thank you for your notification.
[Miscellaneous Android Development] matt5039:
Fun,

yup now the link live..tq

im just bought netpad allwinner A10, can it work with this cm9 build? do you have an idea how to go to recovery for this device?

tq in advance
[Miscellaneous Android Development] kcthomlau:
Thanks! I will try this soon
[Miscellaneous Android Development] thedon1066:
EDIT:- Sorry posted in wrong thread, <mod - please remove, thanks>
[Miscellaneous Android Development] Charlie--:
Does this mean there might be a CM9 for the Scroll Excel, one day?

I'm a mod over at 'scroll tablet forum' - let me know if you need anything from an Excel tab, as I will get it for you.

Cheers

Charlie

P.S. Thank you for the CWM5 - Been using on my Excel and it works great.
[Miscellaneous Android Development] firstdvr:
Any idea if Momo9 can be flashed with this Mod?
[Miscellaneous Android Development] user589:
Hi!

Thank you for your work.

I've just got a Onda Vi30 Deluxe (1024x768) with Allwinner A10 CPU. I would like to help you add support for Onda Vi30 to your ROM (after all, the hardware is very similar). I've already installed official onda's android 4.0.3_v0.5.

What commands should I run, files from my current firmware upload to help you?

As I understand, the ROMs for Onda and Ainol might differ in kernels and a few configuration files, all core applications should be the same correct (and for the most other phones/tablets too)? If so, do cyanogen folks provide some kind of a base system with an option to drop the kernel and configuration there?

EDIT: added output of commands requested in one of the first posts. How do I get a dump of filesystem?

EDIT2: Some more information: Onda Vi30 Deluxe have only 4 hardware buttons: 1 power button on the bottom and 3 usual buttons on the front (HOME, MENU, BACK)

dump: mediafire . com/?s8h1bi8ih153gno or filedropper . com/dump_1
[Miscellaneous Android Development] Charlie--:
There is no CM9 for a Momo9 at the mo' AFAIK.

However you should be able to use the CWM5 for GB on the Momo9 - It also works fine on the Scroll Excel, that I have. There is a version of CWM5 for ICS, if you are not using GB on your tab.
[Miscellaneous Android Development] thaigir99:
Gemei G2

Fun, I have ported ployers 4.0.1 to my Gemei G2,. So It should also be able to run cwm like the other a10 machines
[Miscellaneous Android Development] firstdvr:
Can you point me to the correct thread to download the CWM5 firmware. TIA.
[Miscellaneous Android Development] D3LTA:
What about the 3.0.17 kernel ?

Also no source on GIT ?
[Miscellaneous Android Development] Vinnie1:
NOVO7 Advanced - Gapps?

I installed the CWM, then I installed the A10 rom (upgraded from the official NOVO7 advanced 4.03).

All looks good and works fine until I install the Gapps.

I have been on the official CM Gapps page, and all the versions on there are pre-ICS, and therrefore do not seem to be compatible, I did try the latest version on there.

I have downloaded gapps for various tablets, and in one way or another they will not work propery, specifically I get FC's on market, gamil and the browser.

Can anyone point me too a working gapps please?
[Miscellaneous Android Development] infamouskid:
here is a copy of the CWM install script package made for ICS.

to use just extract all files to a folder and double click CWM_Recovery_install_reboot.bat

http://www.mediafire.com/?t2v69wyrboccm9z

reboot works.

backup and restore works.

wipe data/factory reset works.
[Miscellaneous Android Development] Andy98:
This will work on AllDro Speed ??
[Miscellaneous Android Development] wolfsstolz:
I have search but dont found it ...

Work it for my Novo 7 Elf too !? Thanks for answer

FW: ICS 4.0.3
[Miscellaneous Android Development] fun_:
http://goo-inside.me/gapps/
[Miscellaneous Android Development] riorey:
Point OF View Protab 2XXL

Hi!

I've installed the clockworkmod from the first post as well as the ICS upgrade for GB, both are working to some degree.

My problems seem mostly to be with input, touch and keys.

First, the dump for this tablet can be found at

android.bluapp.net/android/protab_2xxl_gb_org-20120219.tgz .

The changed files and additional modules I've made to the ICS zip are here android.bluapp.net/android/pov_protab_2xxl_ics-20120219.tgz .

Ok, recovery first!

Clockwork starts fine, can be handled to do upgrades by using the extendedcommand file in /cache/recovery, the powerkey works but MENU and HOME keys are not.

Events sent by those keys are 102 for HOME and 115 for MENU. The tablet has MENU/HOME/POWER and a BACK key.

ICS:

After adding the modules from the original GB rom and adding them to the rc scripts in the second archive ICS boots, connects to the WIFI and everything works, as long as I use a mouse connected to the USB-host port. Touchscreen is active but acts like a 5 point touchpad and moves the mousepointer around the screen. The same keys as in the recovery doesn't work at all.

I can get the touchscreen to move the pointer in the correct directions and by using 2 fingers I can actually "click" when I'm in the correct position but I would like to get this working as a touchscreen.

My programming experience as well as hacking Android is very limited and I'm not sure I know where to find information (I do know how to use google as well as forum search functions) about specific settings most users won't ever tamper with.

If someone has an idea where or what I should look for I'll be happy to test/implement this and release more information about this.

Thanks in advance,

Ricky
[Miscellaneous Android Development] fonix232:
Ricky:

For touchscreen to work properly, you'll need an ICS firmware of your tab. Then simply go to /system/usr/idc, and copy out the IDC file of your touchscreen, and place it in this build.

Buttons are the same, you need the keylayouts from /usr/keylayout/, copy them over, and done. After this, and a reboot, everything should work fine.
[Miscellaneous Android Development] fun_:
do you have this one?

http://www.pointofview-online.com/showroom.php?shop_mode=product_detail&product_id=308

and probably only GB ROM is released, right?

(if you really need answer, please write detail about your tablet as much as possible)

EDIT: sorry, I can see detail in protab_2xxl_gb_org-20120219.tgz

probably you need to make idc file manually. at first get name of TS on your tablet by using getevent -p. (or logcat or something)

EDIT: "ft5x_ts" is the name

then, make /system/usr/idc/ft5x_ts.idc file with following 2 lines

touch.deviceType = touchScreen
touch.orientationAware = 1

on Android, key assign can be changed by kl files in keylayout directory.

EDIT: try /system/usr/keylayout/sun4i-keyboard.kl from your stock rom

on CWM, recompile is needed.
[Miscellaneous Android Development] riorey:
Fantastic,

thanks, I've created my own idc file and copied the original keylayouts from the GB rom. It works, now it's only the recovery that doesn't contain the keylayout directory and maybe the occational orientation of the screen that needs fixed...

I'll upload the files to my site tomorrow for other to use.

Ricky

---------- Post added at 01:26 AM ---------- Previous post was at 01:21 AM ----------

Haha, sorry, you were to late! ;) Fonix232 helped me going, I found out how to do it from his message! :)

Anyway, what aobut the keylayout inside the recovery?

Thanks in advance,

Ricky

---------- Post added at 01:44 AM ---------- Previous post was at 01:26 AM ----------

ok, didn't see this before, ok?

I don't have a build-system for cwm setup, is this something you could do?

That would be the last for now on the POV Protab 2XXL ICS porting... Well, there are probably gazillions of stuff that don't work but I need a working cwm to flash the gapps-stack.

Thanks in advance,

Ricky
[Miscellaneous Android Development] riorey:
mkfs.ext4

Hi!

My POV tab only has 200MB on the /system nand and that's not enough, there is an internal NAND which GB used for "internal SDCARD" but it's unused in ICS, I'd like to move /system there (shouldn't be to hard as many a2sd scripts do this) but I need to reformat it from vfat to ext4 and I can't find any mkfs.ext4 for doing this, do you have any ideas?

Thanks in advance,

Ricky
[Miscellaneous Android Development] riorey:
Hi,

I thought i'd give you a small screenshot of my protab.
[Miscellaneous Android Development] Lesicnik1:
So, I've got a question.

Will this work on the Novo7 Elf?

(Mine is at customs :))