yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] WLFung:
Hi, all the great guys here.

I've tested the CWM Recovery on my Ainol NOVO7 Aurora 8GB.

To mention firstly, I had installed NOVO7 Essential Clean ROM v0.3 By Android-kun from slatedroid.com

(http://www.slatedroid.com/topic/29280-rom-novo-7-essential-clean-rom-v03-for-aurora/)

Actually I can't push the recovery.img to the device at the beginning whereby the "CWM_Recovery_install_reboot.bat" file created from the origin.

It did finished upload, but it can't boot into the Recovery, which means the Recovery.img was not store successfully. It does a normal Android boot up even you boot into Recovery.

After few tests unsuccessful, I search another Mirror from the other forum.

(http://www.sendspace.com/file/edikkx)

It breaks down "Install" , "Boot to Recovery" and "Boot to normal" into different .bat files. I check the script, the command is almost same.

But it successfully upload the .img file and boot into the Recovery.

I can't find anything wrong from the .bat files, weird.

After all the success in Recovery, the Recovery brings another problem.

I can't shift the option by pressing "Volume+/-".

It did nothing with "Volume+/-", but "POWER" & "BACK" buttons do response to its function.

In order to move the cursor, I had to HOLD UP the "BACK" button and press the "Volume+/-". But after enter the 2nd level from the Options, if released the BACK button and doing the same way holding the BACK button, it would back to the 1st level.

Else I have to hold the BACK button all the ways. But I have to press the POWER button quickly to enter 2nd level then the "Volume+/-" to shift the cursor. If not, when released either "POWER" or "Volume+/-" will trigger the BACK function from the "BACK" button hold-up.

I am facing the difficulties in operate the Recovery.

Or someone can give me the solution?

Many Thanks to all of you.

=========================================================

SOLVED!

Hold the "Volume+/-" first that press the "BACK" to trigger the cursor move.
[Miscellaneous Android Development] riorey:
Point OF View Protab 2XXL

Hi!

I've got a simple question, sohuld we try and make 1 rom for all A10 tablets or should I go ahead and make a separate rom for the POV Protab?

I don't see a major problem of having a united rom as that would make more "hackers" involved instead of branching out. I'm aware of the differences between the different makers hardware but it seems the basics are the same so with a little innovative scripting we should be able to handle most cases anyway.

What do you say?

If you don't think it's a good idea I'll just start a new thread for the POV, which I really don't want to do.

Thanks in advance

Ricky
[Miscellaneous Android Development] fun_:
I'm always try to share things as much as possible among the A10 tablets. please read title of this thread carefully, here is not for specific product :)

I don't see major problem except lack of my free time(and real another hardware) to support other tablets. the reason that currently only files for NOVO7 Advanced are available, is very clear, I don't make other files yet :)

I don't think my files are only for hackers. this is ongoing development project so a lot of things are related to dev work, but final output should be provided for everyone.

I don't know people like which one, single specific file for his tablet, or a little innovative scripting. for some reasons, I'll make specific one for each tablets. but you can try your idea freely. you can post your file here for such kind of work.
[Miscellaneous Android Development] fun_:
please don't use files for other tablets.

I don't want to use my time to post this kind of message...
[Miscellaneous Android Development] fun_:
I want to make CWM for Elf but I can't promise when it will be done.
[Miscellaneous Android Development] telerian:
Do you guys have plans to support bluetooth USB ?

I am trying to find the kernel modules (for v3.0.8), btusb.ko and bluetooth.ko compiled for ARM and also bluetoothd and bluez tools

I have Onda Vi30 tablet running ICS 4.0.3
[Miscellaneous Android Development] fun_:
talking about CM9, it should be possible.

about modules for 3.0.8 kernel, no idea for now. (I don't say it must be impossible. I just say I don't know because I didn't try yet)
[Miscellaneous Android Development] fun_:
I noticed the way to fix flickering on dialogs etc on CM9 for NOVO8A. it seems it can be applied on NOVO7A(and other tablets with Mali) so I built new CM9 images with it & latest source.

then, 20120303 is uploaded. sorry, no other change is done. "for ICS" image still uses old(0.4?) kernel and proprietary files and not tested well.

----

I already downloaded ainol's 0.9 ROMs, but I have no time to try it for now. please don't ask about it ;)

I hope I can get more time in this month...
[Miscellaneous Android Development] the-razer:
Hi fun_,

Do you know if CWM Recovery you built for Novo 7 Advanced is, or could possibly be, compatible with Novo 7 Aurora? As these devices become available and quite popular, it would be really nice to have CWM Recovery on them. I'll receive mine in the next two days, so if you need someone to do some tests, then write me a PM.

Otherwise, if you don't plan or have time to support the Aurora, is there some kind of a guide how to dive into porting CWM Recovery? Would try then to do it on my own but never had any contact with it.

PS: hardwarewise they seem to be quite similar, except for the screen
[Miscellaneous Android Development] proximafc:
Has put CWM Recovery on Onda Vi40 all ok. to run the right button + reset, moving home+right, home+menu
[Miscellaneous Android Development] riorey:
fun_ what do you use for compiling cwm?

I've tried setting up my own toolchain and environment but I can't get it downloaded correctly. Do you have a good howto or some other info I can use?

Thanks in advance,

Ricky
[Miscellaneous Android Development] fun_:
sorry, no. I know there is "CWM for Aurora" on the net but it's just a copy of my old CWM for Adv1. I know it partially works but I don't recommend it at all.

I have a plan but don't have enough time. currently my free time is consumed to write message like as "sorry, no" "use google before asking" etc. lately I completely ignore PMs, sorry.

I got a lot of messages like as "I can help you so please email me how to help you asap". I really feel thanks for them but sadly I don't have a time to reply them.

anyone can learn how to build android things from the net. I provided some links on post#1 here.

yeah, all allwinner A10 tablets are quite similar.
[Miscellaneous Android Development] fun_:
personally I feel "home+" is not ok but thank you for your info.
[Miscellaneous Android Development] fun_:
if links on post#1 here were useless, sorry, no idea.
[Miscellaneous Android Development] fun_:
test CWM/CM9 for NOVO7 ICS 0.9 ROM series

http://files.androtab.info/allwinner/cm9/20120305/NOVO7A1/ Advanced1

http://files.androtab.info/allwinner/cm9/20120305/NOVO7A2/ Advanced2

http://files.androtab.info/allwinner/cm9/20120305/NOVO7AE/ Aurora/Elf

it seems key combination to boot recovery like as "VOL+ & POWER" doesn't work with bootloader in 0.9 ROM :( please use command described in post#2.

CM9 for Adv2/Aurora/Elf are not tested at all so it may not work.

on Adv1 it runs very fast but actually it seems cpufreq doesn't work correctly :(

EDIT:

HOME/MENU act as VOL+/VOL- on Adv2/Elf.
[Miscellaneous Android Development] metalboy94:
Installed on LY-F1, only volume buttons work for up/down and Power button for select. No Back button. :(
[Miscellaneous Android Development] Mitred:
Hi Fun

Scroll Excel

clockworkmod v5.0.2.7 this is the one from your CM9(ainol7) thread on XDA

volume down cycles up volume down cycles up but it only works in landscape so not noticed if you need it a link is on the OP i will mirror this post on your cm9 thread

Menu= key:115

v-up= key:139

v-Dn= key:217

Power=key:116

Home= key192

Back= key1
[Miscellaneous Android Development] fun_:
5.0.x (built with CM7) will not be updated anymore. you can use 5.5.x (built with CM9).

sorry, I couldn't understand this part. is there any problem on CWM?

I guess HOME is 102 but anyway thank you for your info.

I'll make CM9 for Excel soon.
[Miscellaneous Android Development] riorey:
Nope, they are fine, my 5 year old Fedora 16 Laptop is ****ty though, I'm using my sons 6 core Ubuntu instead... (He is 10!) :)

Thanks again,

Ricky
[Miscellaneous Android Development] Mitred:
Volume butons are wrong way round but causes no problem

I'm shure i read home as key:192

Will check when i get home sorry for mix up but i have been a bit lost

Lately.

Dave aka Fonefixer one of the other mods on scroll tabletforum died of heart attack on saturday night and it was a bit of a shock

Edit: yes you are right home key:102

look forward to testing Cm9 on the excel thanks
[Miscellaneous Android Development] fun_:
you said VOL+ goes down, VOL- goes up? (I talked about it here some weeks ago)

did you update CWM after I swapped VOL+/-? if no, it should be fixed.

I see, no problem. R.I.P. Fonefixer.

almost prepared. I need to build & test...
[Miscellaneous Android Development] fun_:
I got a report, CWM for Aurora works, CM9 for Aurora doesn't work(boot loop). any other reports?
[Miscellaneous Android Development] Syke42:
What keys do you hold to boot into CWM on the V99?
[Miscellaneous Android Development] the-razer:
I installed CWM Recovery on my Aurora and after rebooting it seems to have the wiped the data partition. Comparing "cat /dev/block/nandg > recovery.bak" with one I did before installing your CWMR is different as you CWMR has a diffrent checksum, too.

Probably the partition layout has changed, but when some reported it to be working, this is unlikely.

I'm using the 1st March official ROM. I will try this later with the newest ROM realesed today by Ainol. Downloading just takes >3h -.-
[Miscellaneous Android Development] fun_:
if you can help me, please tell me detail before starting random things. please keep in mind I don't have Aurora so I can't get any exact info e.g. partition layout unless someone tell me.

(I can read a lot of things from ROM image so it should be OK if my reading is OK...)

"after rebooting it seems to have the wiped the data partition", how did you "reboot"? what happened just after "reboot"?

you didn't mention "CWM worked fine" so I understand you couldn't see CWM screen, right?
[Miscellaneous Android Development] the-razer:
Sorry, that my post wasn't clear. So to start in the beginning:

First I backup up /dev/block/nandg, then installed your CWM. Turned the device off and on again holding VOL+ & Power. I know it wasn't supposed to work, but why not try? Nothing happend, booted into Android, but all usersettings where gone. Also my backup and your install files on /data. So I guess it got somehow wiped. I also made a backup of the "new" /dev/block/nandg and compared md5 checksums with your recovery.img and the backup I made before installing you CWM and all 3 have diffrent checksums. As this happend I didn't want to try "dding" boot-recovery into nandf, because I'll have to send my Aurora back (issue with the screen not being glued well), which get's a bit complicated sending back a bricked Aurora (warning in post #2).

Here's the partition layout and the corresponding mountpoints:

ROM: 1st March ROM, build-no: 20120301.162352

root@android:/ # cat /proc/partitions

major minor #blocks name

93 0 16384 nanda

93 8 2048 nandb

93 16 32768 nandc

93 24 524288 nandd

93 32 1048576 nande

93 40 1024 nandf

93 48 32768 nandg

93 56 524288 nandh

93 64 13381632 nandi

179 0 7761920 mmcblk0

179 1 6656000 mmcblk0p1

179 2 819200 mmcblk0p2

179 3 285696 mmcblk0p3

tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0

/dev/block/nandd /system ext4 ro,relatime,user_xattr,barrier=0,data=ordered 0 0

/dev/block/vold/93:64 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/93:64 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0

tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

/dev/block/vold/179:1 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
[Miscellaneous Android Development] fun_:
thanks. I can't understand why /data was wiped :(

new nandg backup must be different to recovery.img. if you want to compare them, you need to extract recovery.img from whole nandg image.

anyway, please send back your aurora at first.

----

actually "bricked" is difficult on this tablet. you can flash(restore/initialize) rom with livesuite if hardware is fine.
[Miscellaneous Android Development] the-razer:
I already suspected livesuit to use some kind of "JTAG mode", that is independant from bootloader, but thanks for the confirmation. Is this true for all A10 devices? And to be absolutely sure: no chance to destroy this function by manipulating anything in NAND? Then I'll try this again later, exams keeping me too busy atm -.-
[Miscellaneous Android Development] fun_:
I can't promise "absolutely sure" about anything because I'm not allwinner's person. I'm just a user. I just know everyone use it to "unbrick" tablet.

honestly speaking if you don't want to get a change to destroy your tablet, you shouldn't try CWM/CM9 or any unofficial thing. (even though you can get a change to destroy only with official things... please remember it's cheap chinese product)
[Miscellaneous Android Development] the-razer:
Sure ;) This was more a "did I understand correctly" than a "say nothing happens, and if it still get's bricked I'll send you the bill" :D

I know that there's always a risk, but if no one take's it, there would be no development like CWM. So already thank you for porting it. I'll give it a try in the evening and will report back.
[Miscellaneous Android Development] infamouskid:
would this work on the teclast a10t?

it's all winner based as well.

also reading a few pages i saw some boot, rootfs, recovery and other files.

what do these do?

also if no one has tried this on the a10t how can i port this to my tablet?

i would like to try.
[Miscellaneous Android Development] fun_:
thanks.

I have no idea why /data was wiped on your Aurora, and why CM9 doesn't work on some guy's Aurora :(

I want to hear about Adv2/Elf... anyone?
[Miscellaneous Android Development] theprisoner6:
CWM Recovery Aurora

Sorry, just got the Aurora... how do you install the CWM recovery? What is the key combo?

Also, after install, how do I boot into CWM recovery?
[Miscellaneous Android Development] the-razer:
I'm now on the official ROM released today by Ainol (which works like a charm btw).

Good news!

I installed CWM Recovery again and it worked! What I've tested and works:

- backup to SD card

- advance restore (I restored the cache partition)

- wiping cache partition

- manually formatting cache partition

- mounting/unmounting

- adb shell

When restoring only one partition it seems to check all md5 checksums, not just the one required, which is not necessary(?). I don't know if this is normal CWM behavior or not, but could be improved :D

Hardwarekeys are working as they should, back is "back", Vol +/- is "up" and "down", power is "ok"

Great work! :)

No /data wipe or other strange behavior. I think there was a problem with my ROM I had installed because the /data partition was mounted and after another reboot it was wiped again.

EDIT: cpufreq seems to work. I can change the governor and min/max frequency. Both working, but Recovery is lagging a bit at 60 Mhz ^^

EDIT: Powering up holding the back button enters recovery. Yay!
[Miscellaneous Android Development] riorey:
Point OF View Protab 2XXL

Hi fun_,

I'm a bit uncertain if I should spawn off a new thread or not?

My rom is heavily based on yours but at the same time they're not compatible anymore. I've recompiled CWM so it works on the Protab, it won't work on the other tablets if they don't use the same key-events and from what I've seen so far the required drivers are different. At the same time your fixes to build.prop works on the Protab as well.

Please, advise me what you think I should do?

Thanks in advance,

Rickard
[Miscellaneous Android Development] fun_:
thank you for your report.

I'll make new CWM image(with small change) soon and it will be available under "supported" list on my site.

build# on your old rom was same as 0.9 ROM...but probably something was wrong and it should be gone by flashing new rom. it's standard china quality ;)

lol. I just removed cpufreq settings(conservative, min 300MHz) from CM9 to speed up booting because I guessed default is "performance" governor(it's true on Adv1 0.9), but it isn't true on Aurora, right?

really good news! I hope it should work on Adv2/Elf too.

(there is no "BACK" (on side) on Adv1 so I can't confirm it lol)

I'll update description. thank you.
[Miscellaneous Android Development] the-razer:
Yes, default governor was "performance" in CWM Recovery. Are we talking about the same thing? :P I didn't try CM9. All I did was changing cpufreq govenor and min/max scaling freq in /sys/devices/system/cpu/cpu0/cpufreq via ADB shell because you mentioned that cpufreq might be broken. The default values were: min 60Mhz, max 1008Mhz and the govenor, as mentioned, "performance".

Glad that the Aurora will be "officially" supported. Thank you! :)
[Miscellaneous Android Development] fun_:
oops. I understood default is NOT "performance" because "performance" should set max freq(1008MHz) at any time...

EDIT:

oh, you just said "if I set freq to 60MHz on recovery, I felt lag" to check cpufreq functionality, right?
[Miscellaneous Android Development] fun_:
it depends on what do you want.

I just pushed my change to support other tablets that currently I'm working.

https://github.com/naobsd/cm_device_allwinner_a10/commit/2cc2837bff8d3edc4cd2d5e4d1da310ec08f1fff

8192cu wlan, mma7760 accelerometer, and ft5x_ts TS should be supported by this commit. update.zip with additional files will be uploaded when it will be made.

I know keylayout files are not good for some tablets so I'll replace it in update.zip as postprocessing after build. sensors.exDroid.so can't be shared on some tablets so it will be replaced too.

my recovery_keys.c should work on NOVO7 Adv1/Adv2/Elf/Aurora, Bmorn V11, and Scroll Excel.

I don't know it's enough for you. currently I don't know how "not compatible". (sorry, I have no time to learn about your rom for now)

I don't say I don't support other tablets not listed above. I just do things in turn. I can't do everything at once. I'll support other tablets after current work is done.

if you need your own changes for now, please keep your own repo. if you can use my repo in future, feel free to use my repo.

thank you for your cooperation.

EDIT:

sorry, you asked about thread.

if you want to merge your changes to my repo(even if it needs branch), or you can wait my work for your tablet, please use here. you can talk about dev things for your tablet here.

if you want to make your work independent, please make your own thread.

this thread is mainly for development work so you can use here for development and you can make another "users'" thread for your tablet/rom.
[Miscellaneous Android Development] the-razer:
exactly.

(It seems that a message here on XDA has to have at least 10 characters. So don't pay attention to this as it's only purpose is to lengthen my message :cool:)
[Miscellaneous Android Development] fun_:
thanks for clarification.

http://files.androtab.info/allwinner/cm9/20120308/

here is latest image (just uploaded, not yet tested). I'll test it and update my site to link them. CM9 for Aurora(and probably for Elf) will not work so they will not be linked yet.

descriptions on post#1-3 will be updated later.

----

about latest CWM,

install-recovery.sh now uses /sdcard/recovery.img(was /data/recovery.img). /sdcard may NOT be "SD card", make sure it's placed under "/sdcard".

reboot-recovery.sh can be used to reboot recovery.

these scripts can be used on rooted shell (adb or any other term apps), or gscript with "su".

other changes,

governor is set to "performance". if your kernel uses another governor, you may get better responsiveness ;)

SD card and internal NAND flash are exported by USB mass storage function in CWM. (it didn't work on ICS ROM and only SD card was exported on GB ROM)
[Miscellaneous Android Development] fun_:
http://files.androtab.info/allwinner/cm9/20120308/GBROM/

CWM & CM9 test image for Bmorn V11 and Scroll Excell.

(I think ICS ROM is not released yet for them, right? EDIT: I just noticed there is custom ICS ROM for Excell. my CWM/CM9 doesn't work with it)

at first please install & test CWM. please put recovery.cpio on /sdcard then run install-recovery.sh on rooted shell.

on Bmorn V11, keys on front aren't worked correctly, sorry!

on CM9, please check how it works. (at least accelerometer, key assign, touchscreen, and wlan)
[Miscellaneous Android Development] riorey:
I'd prefer if I wouldn't have to maintain a ROM all by myself, though some of the changes in for example default_recovery_keys.c seem to be incompatible.

This is needed for the Protab 2XXL:

case KEY_HOME:

return HIGHLIGHT_DOWN;

case KEY_VOLUMEUP:

return HIGHLIGHT_UP;

case KEY_POWER:

return SELECT_ITEM;

case KEY_ESC:

if (ui_menu_level > 0) {

return GO_BACK;

}

It's not a diff, just a copy and paste so you know what keys need to be added to the correct case.

I checked your source-code, if we change place for up and down the only thing you seem to have to do is add case KEY_VOLUMEUP: to HIGHLIGHT_DOWN and it should work, the keys are on the right side of the tab and CWM starts up in landscape anyway so it does not really matter which key is up or down.

The sun4i-keyboard.kl should also have these values added:

key 139	VOLUME_UP

key 217	VOLUME_DOWN

key 102 HOME WAKE

key 1 BACK WAKE

key 115	MENU	WAKE_DROPPED

Some of them are already there, some are missing.

That's it for now, maybe there isn't a big difference in the end, anyway. :)

Rickard
[Miscellaneous Android Development] fun_:
thanks for your info.

well, ProTab2 XXL has, HOME, MENU, and POWER on side, and BACK on front? no VOL+/-?
[Miscellaneous Android Development] riorey:
Coirrect, the home and menu buttons doubles as vol+/- with long press. It works with ICS without any other changes. If not there is an other file called axp20-supplyer.kl which I can provide that might fix that.

You're welcome.
[Miscellaneous Android Development] fun_:
http://www.guru3d.com/article/point-of-view-protab-xxl-tablet-review/6

hmm. I see. long-press feature is nice...but...

as you said I'll add KEY_VOLUMEUP(actually it acts as MENU in stock ROM) to HIGHLIGHT_DOWN. so you'll get MENU = down and HOME = up on CWM.

on CM9, I'm thinking to add 115 as VOLUME_DOWN so HOME/MENU will act as VOL+/- with common sun4i-keyboard.kl. (and long press will act as VOL+/- too...)

of course I can make & replace sun4i-keyboard.kl specifically for your tablet. which do you like, same key map as stock rom or not?

EDIT:

oh wait, I found your sun4i-keyboard.kl is same as one for Scroll Excel. I remembered your TS is ft5x_ts, same as Excel too. then, what's your accelerometer?

EDIT2:

sorry, I remembered I already downloaded files you uploaded. accelerometer is bma250, same as Excel.

then, CM9 for ProTab2 XXL is already available. try SCROLLEX_update.zip :)

EDIT3:

ProTab2 XXL is made by inet, as same as Excel. I guess this configuration is common for A10 tablets made by inet...
[Miscellaneous Android Development] riorey:
Yikes! :)

I didn't have time to check this until now, well, I'll try the rom.