yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] brenobf:
hey, where do I get the information you need to port this mod to my tablet?

there's a single description of it in a previous post.
[Miscellaneous Android Development] fun_:
what you asked is "ShutdownThread->reboot()" and you should know where it's implemented. it's Android.

then your question is off-topic here. my obsolete CM9 has no relation to Allwinner ICS source code. another CM9 uses some parts of Allwinner ICS source code but author doesn't post message here.

why did you ignore my answer in previous post?

https://github.com/allwinner-ics/pl...blob/master/core/jni/android_os_Power.cpp#L78

https://github.com/allwinner-ics/platform_frameworks_base/blob/master/core/jni/misc_rw.cpp#L70

in Allwinner code, go_recovery() is always called if reason is not NULL.

can you explain about "latest version of the CM9" more specifically?

I, OP on here, made CM9 for A10 devices. all information except recent some pages were about my CM9. but currently I don't make any "latest CM9".

another person is making another CM9. other people except me on here are talking about it in recent some pages.

recently I can't decide which CM9 are people talking about if they use "this CM9" "latest CM9" etc.

if you need expert, here may not be right place. at least I'm not "talented developer" mentioned by other people in last some pages here.

EDIT:

OK, I understand reason "" should be same as null. I checked Allwinner code and it should be same too. hmm. then, I have no idea, sorry :(

EDIT2:

I don't know about java and jni. if reason in android_os_Power_reboot() can't be NULL, it should be a bug in allwinner code. what happen if you run "reboot" command on your Allwinner ICS ROM?
[Miscellaneous Android Development] KevlarTheGreat:
Thank you very much for taking the time to respond.

I realized that I missed your answer the first time and edited my post but you were probably writing this one while I was updating my post.

Take a look at what I wrote in EDIT2. Basically, if you use null ShutdownThread->Run() and the SystemServer->Run() will convert it to an empty string. I verified the smali code in my ROM matches the code in java that I posted above. I can try to override that code....

Thanks for posting links to that source. I'll take a look.

I'll try to read through a bunch of posts later to find which CM9 people are using. I just thought looking at some of that smali code could lead me to a solution, but I don't know if reboot is implemented in CM9 for Aurora either..

EDIT: Haha, we are really out of syc here. :) I see your edit. Thanks.
[Miscellaneous Android Development] fun_:
here is my EDITs :)
[Miscellaneous Android Development] KevlarTheGreat:
I assume you mean from the shell. It actually does reboot normally. I haven't tried to trace through all the shell code yet. I'm not very familiar with that part of the system.
[Miscellaneous Android Development] Microphone:
ainol aurora

Hey guys,

i have quarx' latest nightly installed. loving it!

Do you know how i can play flash Videos without problems? using opera mobile browser...
[Miscellaneous Android Development] fun_:
at first AOSP doesn't have the code to update misc partition for recovery.

CM9 has a hook to run command which can be specified at compile time and it can be used to update misc partition for recovery.

https://github.com/CyanogenMod/android_system_core/blob/ics/libcutils/android_reboot.c#L110

ANDROID_RB_RESTART2 is used if reason is specified.

EDIT:

my CM9 didn't enable RECOVERY_PRE_COMMAND. I misunderstood that part was not merged when I was working for my CM9.

correct implementation for CM9 is, make a command to update misc partition if argument is specified as "recovery"(=reason), and specify it as RECOVERY_PRE_COMMAND.
[Miscellaneous Android Development] fun_:
ah, sorry, yes it's command for shell. and I noticed it doesn't use JNI ;)

it just call android_reboot() and I guess "reboot recovery" doesn't update misc partiton(can't enter recovery mode with it). ;)
[Miscellaneous Android Development] KevlarTheGreat:
Would it likely work for me to call android_reboot() from ShutdownThread?

I'm not very familiar with the native portion of android. I notice in Power->Reboot() it calls rebootNative(). Is that the same as android_reboot()?

private static native void rebootNative(String reason) throws IOException ;

What file does android_os_Power.cpp get compiled into? Where is it located on the device?

What file does android_reboot.c get compiled into? Where is it located on the device?
[Miscellaneous Android Development] fun_:
I'm not familiar with JNI.

https://github.com/allwinner-ics/pl...blob/master/core/jni/android_os_Power.cpp#L98

I think rebootNative() should be same as android_os_Power_reboot(). android_os_Power_reboot() calls (go_recovery() and) android_reboot().

/system/lib/libandroid_runtime.so

/system/lib/libcutils.so

sorry, good night.

EDIT:

forgot to answer first line. you need to call a native function which calls go_recovery() before android_reboot(). (or external command which has same functionality)

EDIT2:

well, I guess android_os_Power_reboot() in allwinner has a bug. it always call go_recovery() and never pass reason to android_reboot(). you need to fix android_os_Power_reboot(), not (only) android_reboot() for normal reboot and recovery reboot.
[Miscellaneous Android Development] XdxH62:
I'm pretty sure it's a Ployer MOMO15 [1] also sold as AirpadXL [2]. FCCID:Z9UCM008 [3]

I think I've got a different one on my tablet, but there is an image provided by X10 [4]. The links are in the attachment as I'm not allowed to post them yet.

The output of dmesg and getevent ist in the attachment too, but find isn't installed on my device. Let me know if you need more information or want me to test something.

Thanks for all your work. XDA is a great place to be!
[Miscellaneous Android Development] ludeguy:
Please HELP!

I have to go a bit off-topic here because I'm really desperate to fix this. I rooted my D90W and then I tried to flash the new official firmware (1.2) using LiveSuit and now it enters a boot-loop and doesn't get into the main screen. What can I do???

Thanks in advance
[Miscellaneous Android Development] cherrytree:
If you can enter CWM, wipe everything,if this does not help reflash with format with Livesuite!

Gesendet von meinem GT-I9100 mit Tapatalk
[Miscellaneous Android Development] brenobf:
Why are you ignoring my posts?

I'm not pointing something offtopic.

I just want to help making this ROM supported to my tablet's model.

Is it possible?

My tab: http://www.aliexpress.com/snapshot/105387943.html

Thanks
[Miscellaneous Android Development] mornage:
I'm interested to see if I can get CM9 to run on my tablet. It's an A1CS 7" AWA10.... I cant post links yet :(

I've been able to get CMW (ainol NOVO7 Advanced from androtab.info) to run on it, although with no back button, and can make and restore backups. I have tried to flash a few different CM9 versions but the tablet either gets in a boot loop or the display is all messed up and I cant tell if it's doing anything or not. I'm not sure if that's because I have to hard power off instead of rebooting nicely though. But with livesuite I can always get back to stock.

I am no developer, but with some guidence I hope to be able to cook up something to run on it.

Firstly, I'd like to make CWM more usefull. On my GNEX I have go back listed under every submenu to substitute for the lack of back button, adding that would be good, or seeing if I can get it to use the physical back button on the front (none of the front buttons do anything).

Then, I have the stock .img if it can be used to gather anything useful and am in the process of setting up a linux VM.

I have only ever written a few VBS scripts so my knowledge of devloping is extremely limited. I follow instructions well though and learn quick if someone can help :)
[Miscellaneous Android Development] fun_:
I guess Quarx doesn't have interest to this thread. at least, he didn't post anything here last several days.

then, can I use this thread for my work? in other words, can you stop to ask something to Quarx on here?

(I'm OK to talk something about his work if it has any relation to my work. and of course you can ask anything to him on another place freely)
[Miscellaneous Android Development] mornage:
[

I thought this was your thread!!!

It's your work I'm interested in as you have been able to get CM9 running on some allwinner tablets already. I'm hoping the work you have done already will help me get something working on mine. I already have the CMW you tweaked to work on the ainol NOVO, and your first few posts suggest with some work we can get CM9 working on it it too. I just need some pointers on where to begin, exact commands to get the info you require and if possible, some guidance so I can actually do the porting myself. Once I learn I can maybe help getting common things working!?
[Miscellaneous Android Development] brenobf:
please, do it! :)
[Miscellaneous Android Development] fun_:
(sorry, it's not only for you)

generally speaking, CyanogenMod is Android. there are a lot of information to build Android on the net. I learned from them. CyanogenMod also provides some documents on their wiki. I don't want to do copy & paste all necessary steps from them to here. I put some links on post#1.

I also wrote some commands and wanted some information on post#4. but I think, this thread is for development work by community. I don't intend to say "just gives some information to fun_, then fun_ gives you something". (regardless of what I actually did)

if someone get problem while building android and/or making enhancement to android for A10 devices, I want to help you as much as possible. but I may not be able to answer request like as "give me something".

I hope I can continue this work(for A10 devices) on here. but please don't expect so much. my progress is slow. if you want Quarx's CM9, please ask him. I will not able to follow his development work.
[Miscellaneous Android Development] brenobf:
friend,

I don't really know why you keep ignoring my posts.

Yea, we know the progress is slow, it's a hard task, etc.

BUT, if you tell or give us a clue of what we can do to help you, it would be just great.

Something like "root your tablet, then collet some informations about the running modules or check in "/etc/blablabla" what daemons are starting with the OS".

Just tell us what you need from us, then it's gonna be a bit easy.

The progress may continue slow, ok, but it'll be at least a litle bit less hard.

Hope what I'm saying makes sense for you.

If it doesn't, or if what I'm asking is not possible to be done please let me know.

Thanks!
[Miscellaneous Android Development] fun_:
sorry, I think I don't ignore you. well... I searched your posts.

http://xdaforums.com/showthread.php?p=26751649#post26751649

I couldn't understand about "it", but I should say "thank you". really sorry.

http://xdaforums.com/showthread.php?p=26664733#post26664733

I couldn't understand what is "you" and "this ROM" because people were talking about Quarx's CM9.

http://xdaforums.com/showthread.php?p=26632491#post26632491

it's reply for boofman and I'm not sure what is "this mod" here too.

http://xdaforums.com/showthread.php?p=26573339#post26573339

I'm not sure about "the rom" sorry.

http://xdaforums.com/showthread.php?p=26561086#post26561086

"it is *not* listed as "supported"" it sounds like you mentioned my CM9, but "this new update" it sounds like Quarx's CM9 and I thought you have interest to Quarx's CM9 as like as other people.

please understand, here was my thread, but suddenly people start to talk about another thing and post request for another person. I was really confused.

well, as I wrote in previous post(it was not only for mornage), there are some commands in post#4. but actually these information doesn't help me.

mornage said my work will help him. he asked just pointers. it helps me.

really sorry, currently I don't know what you really want. Quarx's CM9? or my obsolete CM9?
[Miscellaneous Android Development] mornage:
OK, understood.

I am currently more interested in your CM9 than Quarx's which I know to work on A10 tabs. I also am not expecting to just give you info and for you to build it for me. I was just hoping I could use your help to build a version of your CM9 for my tab. Then I should be able to help others too.

I am currently following instructions on here to see if I can build pure working (well booting at least) AOSP to flash via livesuite. I will then try building CM9 from source to see if I can do the same with that. Although I'm sure just pulling some bits from my tab and adding them to your code might be quicker, easier and better (if possible). Once I know how to do this, I hope to contribute to your project to fix bugs and get more A10s supported.
[Miscellaneous Android Development] brenobf:
hey, you don't need to sorry.

thanks for answering ;)

look, I want to change my tablet's stock rom (android image OS).

any rom I could install on it would be just great.

so, if you're telling me you have your own rom, that's nice.

how can I help you (what kind of information I need to provide you) to make your "obsolete CM9" compatible to my tablet?

Thanks again!
[Miscellaneous Android Development] fun_:
I see. some parts of my post were general statement for everyone. sorry for confusion :)

that instructions should be ok but please keep in mind "build & run AOSP/CM" and "make rom image for livesuite" are independent.

for "build & run", my recommendation is,

1. try to build generic(emulator) image with AOSP. it will not work w/o modification on your device but it confirms your build environment and you'll understand basic procedure.

2. try to build CM9. you may use my a10 device tree as a reference, and you'll understand how to add files for new device.

3. when CM9 build is completed, generated image will boot on your device, but it will have some issues. then you need to modify some files one by one.

I can't answer question like "I built AOSP/CM and made livesuite image, but it doesn't boot. what's wrong?". you can try to make livesuite image after you confirm your image is surely working on your device.
[Miscellaneous Android Development] fun_:
well, I have my own rom for my tablet, but it's not nice for your tablet.

sorry, currently I don't have a plan to make new "obsolete CM9" image for any tablet. I think it's not good thing to do.

"I'm still working" it's true. "I'm working for CM9 for A10 devices" is also true.

I have few updates and I'll push it into my a10 tree for someone who have interest to my work. and also I will help someone who want to make own CM9.

----

one more general statement.

from the beginning, I'm working for myself. I answered some requests and I will answer some requests. but I don't promise anything even if I say "I'll do it". I mentioned about it several times.

lately I said, here is my thread, I'm OP, etc several times. but I don't think I have responsibility for all posts and all requests posted on here. I don't know how to answer some thing which I don't have answer. someone may give answer. no one gives answer. it's community I believe.

I'm busy. you may feel you're ignored if no answer within some days, but I may have no time for weeks, or months. I think, even if I have answer, I don't have responsibility to answer with days or hours.

I really don't want to use my time to write this kind of message. it's not fun. probably people feel tired by this kind of message.
[Miscellaneous Android Development] mornage:
Cool,

Step 1 is well in progress and AOSP is buiding quite happily so far(ignoring the hours of stress getting java6-jdk). I was doing this for both reasons you said, so was good to see this suggestion :)

I might need some help identifying exacting changes between cm9 and fun_cm9 if you can spare the time, but we'll cross that bridge when we come to it.

To be honest, I dont want a livesuite image. I want CMW and update zips. I was only going the livesuite way as it was one of the threads I had come accross when looking to see if I can get some custom roms on my tab! It hadn't even occured to me to look at how to build a CWM flashable zip! This is clearly something I need to look at ;)
[Miscellaneous Android Development] njaro:
I own a GoClever A103 tablet which is almost identical to Protab 2XXL thus I have installed your CM9 version for this tablet. The operation speed is incredible but unfortunately the touch screen is not working properly and I would like to ask You if You could advise me on how I could change the screen drivers.

My tablet has an official ROM in. images format on GoClever's official website, can the drivers be ported somehow?Can it help?

I really want that ROM. It's awesome!!

Greetings
[Miscellaneous Android Development] erickho0407:
it seems that there is also unoffical CM9 for Ainol Novo7 Advanced

http://www.slatedroid.com/topic/33820-ics-404-ivi-cm9-firmware-for-novo7-advanced-btgpsusb-audio/
[Miscellaneous Android Development] fun_:
thank you for your information. I'll remove obsolete info on page 1 here, and add links to new CM9 for Aurora and Adv1. if someone knows another new CM9, please tell me.
[Miscellaneous Android Development] Christian Troy:
there's mine too, covering some 9.7'' and 7'' devices through compatibility zips

http://www.slatedroid.com/topic/33373-rom-cm9-nightlies/
[Miscellaneous Android Development] fun_:
wow really great :)

thanks! I updated post#1 on here now.

EDIT:

and post#3,4 are removed.

thank you for everyone who gave me a lot of information and sorry for my laziness!
[Miscellaneous Android Development] Christian Troy:
fun, i speak for myself, but without your input i couldnt do anything ;)

i wasnt able to compile a simple recovery but searching on google i've learned... and when allwinner sources came out i started to merge code...

then i've started over and i've forked quarx's repository but too late (when i had deleted the old repo!!!) i've realized that i was a bit ahead since hdmi was already working on mine and i had to merge and merge again... silly me! i should had trusted more in my (limited) capabilities :rolleyes:
[Miscellaneous Android Development] fun_:
oh :(

I just started to learn about HDMI output on A10(oops, too late!). I understand default output can be changed via script.bin and I'm sure CWM can run on LCD-less A10 devices. I'll investigate how to change it on-the-fly (w/o Android code). :)
[Miscellaneous Android Development] Christian Troy:
i did it (changing resolution on the fly under android), i've added an entry option inside display settings and then with this code i fetch the requested value:

String str = Settings.System.getString(mContext.getContentResolver(), Settings.System.HDMI_RESOLUTION);
hdmimode = mDisplayManager.getMaxHdmiMode();
if (str!=null && str.equals("1080_60") ) {
hdmimode = DisplayManager.DISPLAY_TVFORMAT_1080P_60HZ;
}
if (str!=null && str.equals("1080_50") ) {
hdmimode = DisplayManager.DISPLAY_TVFORMAT_1080P_50HZ;
}
if (str!=null && str.equals("720_60") ) {
hdmimode = DisplayManager.DISPLAY_TVFORMAT_720P_60HZ;
}
if (str!=null && str.equals("720_50") ) {
hdmimode = DisplayManager.DISPLAY_TVFORMAT_720P_50HZ;
}
mDisplayManager.setDisplayParameter(1,DisplayManager.DISPLAY_OUTPUT_TYPE_HDMI,hdmimode);
[Miscellaneous Android Development] fun_:
I noticed "Electron Beam Animation" causes hard reset on sleep on latest CM9. if you get same problem on other CM9, try to disable "Screen-off animation" in Display settings.

EDIT:

"hard reset on sleep" -> "boot animation just after pressing power button(or expire idle timer for sleep)"
[Miscellaneous Android Development] fun_:
official 20120308 ROM for NOVO7 Advanced(1) doesn't have a way to enter recovery mode while power on. recompile script.bin in nanda with following values

[recovery_key]
key_min = 16
key_max = 20

then VOL+ & POWER can be used to enter recovery as same as old ROM.
[Miscellaneous Android Development] KillerKink:
thanks!!! I just experience that yesterday and was trying to figure out which changes that I made cause this.

In CM7, this was also causing issue.

UPDATE:

hmm...maybe its not. Mine is boot animation restarting when pressing the power button to sleep.
[Miscellaneous Android Development] Christian Troy:
you can disable it in overlay/frameworks/base/core/res/res/values/config.xml

adding

<!-- True will enable the electron beam screen-off animation. -->

<bool name="config_screenOffAnimation">false</bool>

this has scared me when i've updated cm9 sources yesterday... :) but luckilly it was an easy fix

but i'm wondering why hwcomposer.exdroid.so segfaults with that animation :confused:
[Miscellaneous Android Development] KillerKink:
Thanks, I know the fix as I did the same for CM7. Just that I didnt realised it was that was the cause yesterday as I did a number of changes before I notice the issue.

Must have been that our hwcomposer is not playing well with the opengl codes introduce or missing function.
[Miscellaneous Android Development] 79bass:
Great... how you know which value to put?

I have a d90w and I've never been able to hw boot into recovery... I might try those value as well..
[Miscellaneous Android Development] fun_:
I just picked values from working old rom. these values are device dependent.

you can try,

1. choose a key (e.g.) VOL+

2. find a line for (e.g.) VOLUME_UP from /system/usr/keylayout/sun4i-keyboard.kl in your rom. if there are multiple lines, then you need to find out correct one. (e.g.) "key 139 VOLUME_UP WAKE"

3. get a key code for (e.g.) VOLUME_UP from 2nd item in that line (e.g.) 139 (it will be different on your device. check yourself! you may use getevent or CWM to get key code)

4. find a key symbol for (e.g.) 139 from input.h (e.g.) KEY_MENU

5. get a index number for (e.g.) KEY_MENU from sun4i_scankeycodes[] in sun4i-keyboard.c (e.g.) 2

6. get a min-max values from keypad_mapindex[] in sun4i-keyboard.c (e.g.) "2,2,2,2,2,2,2, // 15-21"

7. add/edit [recovery_key] section in (decompiled) script.bin in nanda like as

[recovery_key]
key_min = [B]15[/B]
key_max = [B]21[/B]

----

http://xdaforums.com/showpost.php?p=25650774&postcount=541

actually min/max values should be calculated from ADC output on real device.

your device/kernel may use modified sun4i_scankeycodes[]/keypad_mapindex[], then above source code is useless. you may need to make sun4i-keyboard module with debug output to get correct values.
[Miscellaneous Android Development] 79bass:
@_fun

I got this some time ago...

But if it's depending of the kernel C code, should all CM9 (with a custom kernel) have the same settings? I'm using Christian Troy's build now, for instance.

sorry if it's a dumb question...

I didn't really understand that... anyway, alternatively I can systematically try all the min-max options on the link you posted... I saw it some time ago.. but I was lazy to read trough it... :)

EDIT, so let's say the keycode I got from CWM are correct, I want to use vol+ (28) to boot into recovery:

input.h -> define KEY_ENTER	28
sun4i-keyboard.c ->	[6 ] = KEY_ENTER,

Now looking at:

static unsigned char keypad_mapindex [64] =
{
0,0,0,0,0,0,0,0, / / ​​key 1, 8, 0-7
1,1,1,1,1,1,1, / / ​​key 2, 7, 8-14
2,2,2,2,2,2,2, / / ​​key 3, 7, 15-21
3,3,3,3,3,3, / / ​​key 4, 6, 22-27
4,4,4,4,4,4, / / ​​key 5, 6, 28-33
5,5,5,5,5,5, / / ​​key 6, 6, 34-39
6,6,6,6,6,6,6,6,6,6, / / ​​key 7, 10, 40 -49
7,7,7,7,7,7,7,7,7,7,7,7,7,7 / / key 8, 17, 50 -63
;}

I should try put:

[recovery_key]
key_min = 34
key_max = 39

in the system.fex, right?

EDIT2:

Cool it worked with the min max I said... however not Vol+ but back button... so the serie is

back, the back+power for 4/5 sec, then remove power and wait (with back pressed).

I put in attachment the modified script.bin