[OBSOLETE] unofficial CyanogenMod 9/ClockworkMod Recovery 5 for Allwinner A10 devices

[fun_]

Is there anything you need from us Mk802 ownders that will help?

output logs from the likes of Lumberjack, etc?

I really need more free time

 

[scorpio16v]

EDIT: can you use adb on stock rom or on my CWM?

Sorry, have no luck for ADB. Maybe wrong driver or so. Using Lifesuite " LiveSuitPack_version_1.07_2011026 " on 64-bit Windows 7.
"adb connect" via WLan, the same for me.
On CWM, Windows shows a missing driver, but after manual search for the driver it reports, that there isn't a newer one.
Damn thing :silly:

 

[t-bon3]

ADB working fine on the stock ROM using drivers from here:

http://chinamobiles.org/downloads/zap/Drivers_AllwinnerA10_32and64.zip

Dont bother with windows update it will not find the drivers, use the ones from the archive above and you are good to go.

Livesuite drivers will only enable the connection to the device in bootloader mode.

 

[fun_]

Sorry, have no luck for ADB. Maybe wrong driver or so. Using Lifesuite " LiveSuitPack_version_1.07_2011026 " on 64-bit Windows 7.
"adb connect" via WLan, the same for me.
On CWM, Windows shows a missing driver, but after manual search for the driver it reports, that there isn't a newer one.
Damn thing :silly:

LiveSuit is completely different thing. please forget about it while talking about adb.

on windows, generally any adb driver can be used... google's official one in sdk is enough. the problem is difference of vendor id/product id written in .inf and used in your rom. these ids can be changed. you may need to edit .inf to match ids used in your rom. there are a lot of howtos on the net.

adb can be configured as "disabled" at initial boot. in this case you need to enable debugging from Setting UI.

some kernel build from source may have bug around adb. in this case, adb will not work even with proper driver.

 

[fun_]

it seems Christian Troy did the work thank a lot!
for MK802 users who want CM9, please refer his thread!

 

[KillerKink]

http://files.androtab.info/allwinner/cm9/20120716/
CWM with touch screen control. (quick hack, it doesn't work with TS which needs calibration)

please imagine virtual joypad used in some games. touch the screen, there is center position. move your finger up/down/left/right, then one of KEY_UP/DOWN/LEFT/RIGHT event will be generated respectively. in my recovery, KEY_UP/DOWN are assigned to move up/down, KEY_LEFT is assigned to select item, and KEY_RIGHT is assigned to back.

you need to move your finger some amount of distance(for now, 1/4 of touch screen height for up/down, 1/8 of touch screen width for left/right).

if you lift your finger without moving(or less than "some amount of distance"), BTN_TOUCH event will be generated. in my recovery, currently it's just ignored. I tried to assign it to select item, then default "reboot system now" item was selected by mis-operation several times

----
generally, on A10 Android devices, touch screen driver is provided as a kernel module. if your kernel needs TS driver module, you need to add TS driver module as "/ts.ko" in ramdisk in recovery.img. otherwise you can't use TS to control recovery.

----
as usual, my changes will be pushed to github when I can get more time.

EDIT:
upstream CWM was updated to ver.6. my changes will be conflict but currently I have no time to update my changes for ver.6.

EDIT2:
well... maybe "disable TS control" knob should be prepared...? comments are welcome

EDIT3:
this should work on many single-touch and multi-touch device, but it will not work on multi-touch type B protocol device.

fun,

you can check out this touch recovery. work well on a10.

http://forum.xda-developers.com/showthread.php?t=1485829

too lazy, i will try and get the source for a10 out on github when i can.

 

[fun_]

fun,

you can check out this touch recovery. work well on a10.

http://forum.xda-developers.com/showthread.php?t=1485829

too lazy, i will try and get the source for a10 out on github when i can.

thank you for your infomation.

the problem is, my free time I can't rebase my changes to CWM6 yet...

 

[scorpio16v]

I see,you have made a new recovery for mk802. It boots, but I can't select something. Looks like the old version ( splited screen and wrong colors )

 

[fun_]

I see,you have made a new recovery for mk802. It boots, but I can't select something. Looks like the old version ( splited screen and wrong colors )

if you want to try test version, please make sure you are using rom in "FW 0710B.rar" w/o any modification. test with other rom may be helpful if necessary information is provided.

I don't say problems must be solved with it. it's just a test version which contains a change that I want to know.

please keep in mind short sentence like as "it's crap" "as bad as old version" etc doesn't have any new information. I need detail information even if it doesn't work, even if it looks like nothing is changed from old one, etc.

I heard my CWM shows strange screen with 0710 ROM. I also heard it can be controlled(menu items can be selected). I also heard USB keyboard can't be used with my CWM 0716. I can't confirm myself but at least screen issue should be true.
then, I can't read exact meaning of your "I can't select something". you may feel it's unusable for daily purpose, or you can't control with keyboard, or you really can't control with any input device, or something else.

thank you for your cooperation.

 

[fun_]

today I have a time to flash latest 4.0.4(allwinner v1.4) rom for NOVO7 Advanced. I tried my CWM 0716 on it, then I noticed side buttons don't work correctly and touch screen kernel modules can't be loaded.

I replaced kernel and TS module from 4.0.4 rom, then these 2 issues are fixed. (I'm not sure everything are fine)

I know some parameter related to TS is changed in 4.0.4 rom. TS issue may be fixed by modifying script.bin but I don't think it's good idea to mix bootloader/kernel/modules versions so at this time I didn't try script.bin.

then, unfortunately I can't reproduce screen issue happened on MK802 with 4.0.4 rom on my NOVO7. I have some ideas but all of them are not yet included in test CWM. I need to go step by step.

 

[scorpio16v]

Sorry, for my not so detailed report.
I've tested it on the latest CM9 nightly from Christian Troy (21/07/2012)

First of all it is a working and needfull tool. And even in this current state I would NEVER call it crap or bad.

Yes, as you're aware, the screen is splitted in 4 menues. I see in this version the background picture 4 times and above the menu 2 times.
On older versions of your recovery, there was even the menue 4 times to see.
If you go up and down in the menu, on every second option the screen went black. But you can select the option. It only is hard to navigate.
The CWM itself is technicaly full functional.

You can controll it with a mouse or keyboard. It depends on what is pluged in before you boot in recovery. It is only recognized 1 input device at the same time.
The only thing is, you must have a keyboard with mousebuttons, because you can only make a selection with left mousebutton. Enter didn't work.

The reason why I wrote it didn't reconize anything was, that I thought my new USB hub works like the old one I tested before.

They look both like the same, but maybe the hardware is different.

On my old one, I can use the input device plugged in on the hub. This new hub semms not be recognized. That is reported from other people too.
On my old hub, input on CWM even didn't work if i have my bt dongle plugged in on the same time with my mouse or keyboard. Maybe this dongle was mounted as input device.

So If people reports that no input works, you should make sure no other USB device is plugged in that caused this fault.

 

[fun_]

Sorry, for my not so detailed report.
I've tested it on the latest CM9 nightly from Christian Troy (21/07/2012)

thank you for your information.

I heard his CM9 uses(replaces) some files from 4.0.3 ROM, and my current(old one, not testing) CWM runs w/o screen issue after CM9 installation. is it true?
then, what you tried is new(testing) CWM on old 4.0.3 ROM. this combination will not be supported.

Yes, as you're aware, the screen is splitted in 4 menues. I see in this version the background picture 4 times and above the menu 2 times.
On older versions of your recovery, there was even the menue 4 times to see.
If you go up and down in the menu, on every second option the screen went black.

what happen must be clear. my CWM assumes 16bpp framebuffer but it seems frame buffer is 32bpp. solution already exists in original CWM. just enable it & recompile CWM fixes this problem.

but I want to know why/where is the problem.

You can controll it with a mouse or keyboard. It depends on what is pluged in before you boot in recovery. It is only recognized 1 input device at the same time.
The only thing is, you must have a keyboard with mousebuttons, because you can only make a selection with left mousebutton. Enter didn't work.

I see. keyboard can be used under some condition thanks.

any input device must be inserted before CWM is started.

original CWM should be able to use multiple input devices. I don't try it yet. it may have a bug in original CWM code, and/or my code.

you can control with cursor keys. up/down are up/down, left is select, right is back. I think enter is act as down.

The reason why I wrote it didn't reconize anything was, that I thought my new USB hub works like the old one I tested before.

if you tried same keyboard and mouse on my old CWM, and if it worked, then, something must be strange. but please use old CWM on old ROM, or new CWM on new ROM. otherwise problem may happen.

They look both like the same, but maybe the hardware is different.

how new hub works on CM9? it should be same on CWM. if different, something is wrong in CWM.

 

[douglasanpa]

Great news!

http://quarx2k.ru/cm10-nightly-novo7(aurora)/

Enviado do Defy+ com CM10 by Quarx2k

 

[scorpio16v]

I heard his CM9 uses(replaces) some files from 4.0.3 ROM, and my current(old one, not testing) CWM runs w/o screen issue after CM9 installation. is it true?
then, what you tried is new(testing) CWM on old 4.0.3 ROM. this combination will not be supported.

I've used your versions, dated from 2012-06-15 and 2012-07-16 before. Both looks fine on older firmware 4.0.3.
The firmware, you mentioned "FW 0710B.rar" is the first 4.0.4 version for the mk802 and has the same bugs on CWM like CM9 from Christian Troy.
His legacy_compatibility.zip is based on this ROM version.
Only difference, it seems, you can see on your recovery 4 screens and 4 menues, like in my first attached pix.

you can control with cursor keys. up/down are up/down, left is select, right is back. I think enter is act as down.

Yes, you're right. left/right works like you described.

how new hub works on CM9? it should be same on CWM. if different, something is wrong in CWM.

On CM9, it works without problems. That's why I didn't recognized the fault the first time.

At least, I tried your new test CWM with the "FW 0710B.rar" and have the same splitscreens.

But as I said, it's not realy a problem for me. Should be only a short feedback about the actual situation.

 

[fun_]

I've used your versions, dated from 2012-06-15 and 2012-07-16 before. Both looks fine on older firmware 4.0.3.

I don't say they will not supported, and/or they have a issue, etc. they are supported, they should work well.

The firmware, you mentioned "FW 0710B.rar" is the first 4.0.4 version for the mk802

I'm sure about it and its issues. or I may not be sure, but anyway, as I said this is what I wanted to test.

His legacy_compatibility.zip is based on this ROM version.

I don't think so. I checked mk802_legacy-compatibility_v1.zip just now, it contains (not only but) kernel, modules, etc from 20120524 4.0.3 rom(very 1st one).
I think he tried to use files from 4.0.4 rom at some point in his work, but he is not using files from 4.0.4 for now.

you may use another compat zip from him. but it's not clear what you're using.

it may not be true, but currently I don't have a time to care about his rom and your environment. sorry.

----
EDIT
I'm not sure files in compat zip are important for screen issue. important files may be come from 4.0.4 on CM9.
I'm not sure that compat zip can be installed with my CWM propery. probably no. (I don't say installation will not be finished. it may be finished even if something is wrong)

anyway, a lot of things are not clear and this is the reason I don't ask testing on CM9.
----

Only difference, it seems, you can see on your recovery 4 screens and 4 menues, like in my first attached pix.

well, what you compared? what is "difference"? "4 menus"? I'm confusing and if you are talking something about CM9, please forget about it for now.

On CM9, it works without problems. That's why I didn't recognized the fault the first time.

then new hub is not wrong. someting in CWM is wrong.

At least, I tried your new test CWM with the "FW 0710B.rar" and have the same splitscreens.

thank you. this is what I wanted to know. now I can go one more step.

But as I said, it's not realy a problem for me. Should be only a short feedback about the actual situation.

I think screen issue is the problem. this is what I'm trying to fix. thank you for your report.

I have no more free time for now. next work and answer will be delayed.

 

[Christian Troy]

i cant use stuff from 4.0.4 because they've changed something inside kernel for cedar libraries and updated android_framework_base (that contains cedar libs) is not public on allwinnerwk's official github
it will break every media playback

 

[fun_]

i cant use stuff from 4.0.4 because they've changed something inside kernel for cedar libraries and updated android_framework_base (that contains cedar libs) is not public on allwinnerwk's official github
it will break every media playback

thank you for clarification.

btw does your CWM work well on MK802 (and/or other TS-less A10 devices)?
my CWM doesn't make /bootloader dir so your compat zip can't be installed properly. it makes things unclear...

I'll add /bootloader line to my next CWM, but if your CWM already support MK802, please clarify for your users.

 

[Christian Troy]

i dont think it will work on mk802

for /bootloader i've replaced the /wimax entries inside nandroid.c and extendedcommands.c (or a similar name i dont have sources here)

 

[fun_]

i dont think it will work on mk802

for /bootloader i've replaced the /wimax entries inside nandroid.c and extendedcommands.c (or a similar name i dont have sources here)

I see. then I need to do some work for MK802 users.

for /bootloader I'm thinking just adding only "mkdir /bootloader" line for now. your updater-script mount /bootloader and extract bootloader dir to /bootloader. mkdir should be enough for it.

of course, adding nanda backup/restore function to my CWM will be good... I forgot why I didn't do it

 

[fun_]

i dont think it will work on mk802

for /bootloader i've replaced the /wimax entries inside nandroid.c and extendedcommands.c (or a similar name i dont have sources here)

btw did you try Quarx2k's JB branches?