yashsingh1/xdaforums huggingface dataset:
[Android Software Development] scanno:
The link to my thread is here:

http://www.tabletroms.com/forums/showthread.php?t=4433

Thanks for the hints. Found the max_rows in ui.c. The advent vega is a 10" tab, so it is a landscape device. Will have a look at the kindle fire sources.

Verstuurd van mijn HTC Vision met Tapatalk
[Android Software Development] Hammerfest:
your not joking sadly... I keep hoping to see it all the time so it can be ported over to my Hero, my HD2 or my ASUS Transformer... but the devs for these great devices cannot do skit with no source provided... I hope they take a look at this and find a way... its sad to see no source...
[Android Software Development] Sblood86:
Kindle fire progression help

So I'm looking into 2 things; the first is correct is the 'reboot recovery' option in advanced for the Kindle Fire to cause it to actually reboot into recovery instead of doing a normal reboot. For the life of me I can't find where/how to actually make this change I will admit I'm relatively new to recovery, I tend to stick to the rom side of things.

The second thing is that I'm am wondering if you would mind if I merge a fork of this directly into the cm7 tree that I have for the kindle fire (for convenience and a more complete source tree).

Thanks in advanced.
[Android Software Development] DooMLoRD:
I have created reboot wrappers which get executed by my custom recovery...

/sbin/reboot_recovery

/sbin/reboot_system

/sbin/reboot_fastboot

These scripts in turn execute corresponding the bootmode setting binaries...

Sure u can merge the fork into ur repos, that's why the work is open-sourced ;)
[Android Software Development] nilse:
Touchrecovery for the Xperia X8

First I would like to thank Team UtterChaos for the touchrecovery

GREAT WORK

and then i can announce that the recovery is working on the X8

together with alfsamsung we managed to port it to the x8

for both screen types: cypress and synaptics

Here is the thread http://xdaforums.com/member.php?u=3081601

for now only the cm7 version has it, other version will come soon
[Android Software Development] scanno:
Touch Recovery for Advent Vega Tablet based on Kindle Fire Sources

Hi,

I have build a working recovery based on the Kindle Fire sources. My sources are on github: CWM-Recovery-Modded-Touch-Vega.git

Link to the tread: http://www.tabletroms.com/forums/vega-rom-development/4518-%5Brecovery%5D-vega-touch-recovery-previous.html
[Android Software Development] Napstar:
Glad to hear that.

Thanx
[Android Software Development] nilse:
Stock Kernel

hey after I implemented the recovery in a kernel

i tried it for stock kernel, since not every x8 user has unlocked bootloader

everything is right, exept the touch :(

I was compiling on gingerbread branch, but i just get:

[UI_WAIT_KEY] key code: 330

the recovery is started over the chargemon file

its a tar file with: etc,res,sbin,tmp,default.prop,init,init.rc

do someone have an idea why its not working ?
[Android Software Development] DooMLoRD:
when recovery starts connect device via adb and execute these commands:

adb shell
mount /system
/system/bin/getevent /dev/input/event0

the final command will wait, touch device screen and see if u get any results... sometimes the touch-panel is at different "eventX" so try event1, event2, etc to get exact touch-panel event recognition...

on some HTC devices a seperate touch daemon needs to be started "ntrig touch" for the touch-screen to work...
[Android Software Development] eoghan2t7:
Can't wait for the source release been waiting for this one since the video was published ;)
[Android Software Development] StalinShang:
That's awooooooosomeeeeee!!! Greeeeeeeeat works!!!!
[Android Software Development] MrHassell:
nice

I guess being open source, I can merge the functionality into xCharge?
[Android Software Development] hampsterblade:
Compiles and works great on Galaxy S 4G. Can't wait for that icon version source.
[Android Software Development] Shane:
wow i did n;t seen any type of graphical recovery
[Android Software Development] $aNek011:
compilation error:

out/target/product/u8500/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse: bootable / recovery / ui.c: 364: error: undefined reference to 'get_menu_icon_info'

out/target/product/u8500/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse: bootable / recovery / ui.c: 364: error: undefined reference to 'get_menu_icon_info'

out/target/product/u8500/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse: bootable / recovery / ui.c: 364: error: undefined reference to 'get_menu_icon_info'

out/target/product/u8500/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse: bootable / recovery / ui.c: 364: error: undefined reference to 'get_menu_icon_info'

out/target/product/u8500/obj/EXECUTABLES/recovery_intermediates/ui.o: in function ui_wait_key: bootable / recovery / ui.c: 874: error: undefined reference to 'TOUCH_CONTROL_DEBUG'

out/target/product/u8500/obj/EXECUTABLES/recovery_intermediates/ui.o: in function ui_handle_mouse_input: bootable / recovery / ui.c: 442: error: undefined reference to 'TOUCH_CONTROL_DEBUG'

out/target/product/u8500/obj/EXECUTABLES/recovery_intermediates/ui.o: in function input_thread: bootable / recovery / ui.c: 517: error: undefined reference to 'MT_X'

out/target/product/u8500/obj/EXECUTABLES/recovery_intermediates/ui.o: in function input_thread: bootable / recovery / ui.c: 519: error: undefined reference to 'MT_Y'

out/target/product/u8500/obj/STATIC_LIBRARIES/libbusybox_intermediates/libbusybox.a (mktemp.o): in function mktemp_main: external / busybox / debianutils / mktemp.c: 94: warning: warning: tempnam () possibly used unsafely; consider using mkstemp ()

collect2: ld returned 1 exit status

make: *** [out/target/product/u8500/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1

make: *** Ожидание завершения заданий...

alexander @ alexander-desktop: ~ / android / system $

Please tell me how to fix :(
[Android Software Development] Napstar:
we have provided these sources for cwm v5.0.2.7 repo.

which version have you used?

if that does not solve the problem then check if your toolchain is 4.3.3.
[Android Software Development] thomas1991_12:
Im trying to port this to GT540 (using 5.0.2.7).

I read earlier that someone had the problem with UI WAIT KEY key code 330. I have the same problem. When I try:

(its event1 in my case)

I get an ouput in my shell. This is a part of it:

Any suggestion?
[Android Software Development] apeelme:
Same error:

target StaticExecutable: recovery (out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery)

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse:bootable/Napstar-xda-android_bootable_recovery-1bb1903/ui.c:364: error: undefined reference to 'get_menu_icon_info'

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse:bootable/Napstar-xda-android_bootable_recovery-1bb1903/ui.c:364: error: undefined reference to 'get_menu_icon_info'

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse:bootable/Napstar-xda-android_bootable_recovery-1bb1903/ui.c:364: error: undefined reference to 'get_menu_icon_info'

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse:bootable/Napstar-xda-android_bootable_recovery-1bb1903/ui.c:364: error: undefined reference to 'get_menu_icon_info'

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/ui.o: in function ui_wait_key:bootable/Napstar-xda-android_bootable_recovery-1bb1903/ui.c:874: error: undefined reference to 'TOUCH_CONTROL_DEBUG'

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/ui.o: in function ui_handle_mouse_input:bootable/Napstar-xda-android_bootable_recovery-1bb1903/ui.c:442: error: undefined reference to 'TOUCH_CONTROL_DEBUG'

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/ui.o: in function input_thread:bootable/Napstar-xda-android_bootable_recovery-1bb1903/ui.c:517: error: undefined reference to 'MT_X'

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/ui.o: in function input_thread:bootable/Napstar-xda-android_bootable_recovery-1bb1903/ui.c:519: error: undefined reference to 'MT_Y'

collect2: ld returned 1 exit status

make: *** [out/target/product/blade/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1

make: Leaving directory `/home/apeelme/android/systemCM7'

this toolchain (4.4.3) is default, i tried 4.4.0, 4.3.1...similar errors :confused:
[Android Software Development] cj360:
I see no one's posted in here in a while. I was wondering what the status is for the ics branch.
[Android Software Development] Napstar:
Change your build directory name form napstar-xda-bootable recovery to just "recovery"

was busy with kernel development so was using GB rom.

Now shifted to cm9. Will start work soon.
[Android Software Development] thomas1991_12:
Does this recovery only support Multitouch devices??
[Android Software Development] Napstar:
I have not faced such errors before. can't say what is going wrong.

Have you built recovery before using same computer?

No, it supports all touch (single/multi) supported devices.
[Android Software Development] keb00:
Any chance to nexus s?:D
[Android Software Development] Napstar:
Ask your recovery / kernel developer to use our patches.

If he/she is very busy then direct us to your recovery sources. We will try to port it.
[Android Software Development] apeelme:
Yes of course...(CM7,CM9,AOSP GB and ICS)

I build whole ROM and use it on my phone(repo sync - about 2 weeks ago)...after the build delete the recovery directory (in bootable), copy the new touch recovery directory...make clean, and build same device with new Napstar recovery...and recieve this error messages.

i dont know what is wrong...:confused:

(I apologize for my english)
[Android Software Development] keb00:
Ok thanks!;)
[Android Software Development] Napstar:
Do one favor.

Install this software

http://www.teamviewer.com/en/download/index.aspx

So that I can control your PC remotely. It will be easy for me to track the problem. :)
[Android Software Development] Maroc-OS:
Done for Samsung Galaxy Y GT-S5360 :) and added some fixes to the sources from 5.8.x.x and other recoveries :) i will upload that when i have some time :)

added your name and link ;)

http://xdaforums.com/showthread.php?p=26683694#post26683694

---------- Post added at 01:32 AM ---------- Previous post was at 01:30 AM ----------

you need to add this informations from default_recovery.c to your device recovery.c file and customize them for the device :)
[Android Software Development] Napstar:
[Added] Guide for porting touch recovery support to any device in 3rd post

Great work mate! :)

Maroc-OS is right. It seems that you are using your own customised recovery_ui.c

You must have specified its path in BoardConfig.mk file from system/device directory.

Just include default_recovery_ui.c related changes from my sources to your recovery_ui.c file.

Follow this guide that I have just added to thread for porting our recovery to other devices for further necessary changes.

http://xdaforums.com/showthread.php?p=22283471#post22283471
[Android Software Development] thomas1991_12:
With GT 540 i still have the WAIT KEY 330 message. Nothing more.

Are you sure it supports single touch, because there are commands like ABS_MT_POSITION_X. Which is for MultiTouch. (MT). Or does this command work with single touch screens too?
[Android Software Development] Napstar:
Oh, I did not knew that your device is single-touch one.

I will add necessary changes for single touch devices.But, as I dont have a device with single touch panel, I want you to test these sources and report here.
[Android Software Development] thomas1991_12:
Great to here! Let me now when your first version for single touch finishes. Ill test it on my device (gt540). Thanks!
[Android Software Development] Napstar:
I have sent a pm with link to a gist with modified UI.c
[Android Software Development] eoghan2t7:
@napster any idea when this version is been released for developers to port to there devices?

[youtube]JVWqgGfV0SM[/youtube]
[Android Software Development] Sblood86:
Yeh I was actually wondering the same thing; assuming you guys still intend on open sourcing this? I saw where DooMLoRD had a version up for the xperia (x10 i think it was) but sadly no source :(

Either way thanks for everything you guys have done for open source touch recovery (I still have issues with Koush not open sourcing his touch bits but that's not for here lol)...
[Android Software Development] Napstar:
Hey guys,

I know its been a long time I have not updated my sources.

Yesterday only, I had finished the full touch support for ICS build of CWM as well.

And we (Team UtterChaos) wants to release it first on our supported devices.

In few days that should be done. And after that only we will make full-touch sources open for all.

Sorry for the delay!
[Android Software Development] Sblood86:
Dude, no worries at all regarding delays; we all understand how stuff goes. Thanks a ton for the update.
[Android Software Development] ngh55:
Hey man, does this support the Motorola xoom?
[Android Software Development] Napstar:
If your device has working CWM recovery installed already.

It will be easy to port this for your device.

If not then it will be a bit tricky but not impossible. ;)
[Android Software Development] Napstar:
Porting support for our touch recovery

Hey guys,

Since it will take time to port this recovery to all our development device, I would like to offer an opprtunity to all of you.

Since we won't be releasing our sources till we finish our afore mentioned task, if you guys want I can compile full-touch based CWM recovery binary for you on my workstation.

I will need your

android-system-device-#### (your device directory),

recovery.img/boot.img and instructions on how to pack/unpack it

your android-system-bootable-recovery sources (if they are modified)

DONT SEND ME P.M., Instead Post here.

P.S. It will be on first come, first serve basis. And please don't demand me with other things about recovery. I have other things on my hands as well. :P
[Android Software Development] eoghan2t7:
Thanks Napster ill wait to send you files because you will have alot of users asking for it ;)
[Android Software Development] ngh55:
Actually there are a few, team rogue made a touch recovery for the xoom and I was wondering if a more recent version could be made, thank you for the response.
[Android Software Development] nilse:
hey this is great,

could you do it for me ?

i'm a lil kernel developer for the x8

in the previous version a few changes of your code were suffisent to build it with the cm7 tree

in Android.mk, simply outcomment this to use the default_recover_ui.c from bootable/recovery:

+#ifeq ($(BOARD_CUSTOM_RECOVERY_KEYMAPPING),)

+# LOCAL_SRC_FILES += default_recovery_ui.c

+#else

+# LOCAL_SRC_FILES += $(BOARD_CUSTOM_RECOVERY_KEYMAPPING)

+#endif

in default_recovery_ui.c:

int resX=320;

int resY=480;

int maxX=1689; //values for the x8 synaptics

int maxY=2534;

if you have time you could build it for cypress touchpad, too

just the maxX and maxY are different (blame SE for it)

int maxX=320;

int maxY=480;

for building simply:

. build/envsetup.sh

lunch cyanogen_shakira-eng

make -j1,5xcores recovery , since i just need the recovery binary, other files will be replaced

and the res folder would be nice :)

i hope its ok this way, since the dont have a boot.img, but a kernel.sin file for ramdisk&kernel

thank you and keep up the great work :D
[Android Software Development] Napstar:
Check your PM.

Compiled binaries are uploaded for both X8 and cypress based panel. :cool:

Enjoy!
[Android Software Development] nilse:
great recovery

thank you really much

as far as i can say, everytime when i'm scrolling a bit it just hangs up, no virtual or physical button is working then

also the debug text is over the virual buttons, but thats easy to change

pressing virtual buttons on the bottom and in screen is working perfectly, just the scrolling thing

thx again, the recovery is awesome

(just realizing xda added new icons :p )
[Android Software Development] Napstar:
Post a video, so that I can make corrections.
[Android Software Development] eoghan2t7:
Napster any idea when the source code goes live?
[Android Software Development] nilse:
here you go, first use of the updated cwm touchrecovery

image is a bit blurry, sorry for that

see me trying removing the battery at the end :p

[YOUTUBE]N_zpoEphlOw[/YOUTUBE]
[Android Software Development] KillerKink:
Have ported this to Allwinner A10-based device on CWM v5.5.0.4(CM9.0.0 branch) if anyone is interested

https://github.com/killerkink/andro...mmit/a0ae47f97a88965a39cf325dec71044fcd3a7541
[Android Software Development] dany547:
any ideea where is the line in ui.c for recovery font size? or whats the syntax name...
[Android Software Development] plikmuny:
can i request you people to develope an english based CWM recovery for my SmartQ T30 android tab ?

because it comes preloaded with chinese version of CWM recovery...

atleast tell me how do i change the menu language from chinese to English ?

awaiting your inputs pls....
[Android Software Development] cj360:
Your recovery probably has to be remade with your language. Your better of looking in the development forums for your device for how to build recovery for your device. Unless there's a way to change the default language of your recovery.

Sent from my Xperia Play
[Android Software Development] PANCHOMATASANO:
mips support

Hello.

I am not a developer.

I wonder if you can make a version of this CWM recovery touch :

http://androtab.info/mips/ingenic/clockworkmod/

https://github.com/naobsd/cm_bootable_recovery/compare/ics...ics-mips-naobsd

https://github.com/naobsd/mips_build/compare/mips-ics-mr1...mips-ics-clockworkmod

Is currently working on my tablet
[Android Software Development] sgt. meow:
If I compile after applying your changes (the 4 commits from your repo) to the .zip file downloaded from the github link in the instructions post, I should get a full touch CWM recovery (like the one in djnilse's vid) right? Not just touch navigation buttons at the bottom, right?
[Android Software Development] Napstar:
Not now! I am busy with other work.

Find your device developer and have him look at this thread. Because every device is different and my patches will apply only if your cwm tree is perfectly staged to my CWM state.
[Android Software Development] sgt. meow:
I'm compiling for the X8. You did one for djnilse. Unfortuantely it was a bit...err.."faulty". So I'd like to do one myself. Would you help me, please?
[Android Software Development] Napstar:
For last few months I was unable to do any development..

I will start porting our sources for CWM v6 from next week onwards!

Also I will try to fix few bugs!!

Lets see... :)
[Android Software Development] pppppp:
Thanks, keep up the good work! Eagerly awaiting!
[Android Software Development] whitexp:
i can build for my ldpi device ?
[Android Software Development] Android-Andi:
i have compiled it for p3110 :D

anyone knows how to fix the text on left side? it´s a landscape device :p

maybe [MENTION=4224819]Napstar[/MENTION] ?
[Android Software Development] :
You can change in ui.c this value:

#define MENU_ITEM_LEFT_OFFSET [COLOR="Red"]0.05[/COLOR]*gr_fb_width()

I think 0.15 or 0.1 will do the trick.
[Android Software Development] Android-Andi:
Thanks [MENTION=5186178]carliv[/MENTION] (out of thanks today, i press it later) :) Worked!

There is another issue:

At the Top it should write "CWM-based Recovery v 6.0.4.5" but it only writes "CWM-based Recovery v 6" and "by Napstar" but it only writes "by"

Any Idea for that too?

Edit:

Added some spaces behind "Napstar" and now shown... but not "v6.0.4.5"
[Android Software Development] :
For that look in ui.c for "int ui_start_menu" and focuse at these lines:

if (text_rows > 0 && text_cols > 0) {
for (i = 0; i < text_rows; ++i) {
if (headers[i] == NULL) break;
remChar = (int)(resX - strlen(headers[i])*CHAR_WIDTH)/[COLOR="Red"](CHAR_WIDTH*2)[/COLOR]; //To centre align text from header
for (j = 0; j < remChar; j++) {
strcpy(menu[i]+j, " ");
}
strncpy(menu[i]+remChar, headers[i], text_cols- remChar);
menu[i][text_cols-remChar] = '\0';

Try a lower value for "(CHAR_WIDTH*2).
[Android Software Development] Android-Andi:
i will try next days again. thanks again for your help!

i am working now on omnirom :)
[Android Software Development] Napstar:
That won't help. (CHAR_WIDTH*2) helps in center aligning the header lines as is mentioned in comments.

Try playing around with

if (text_rows > 0 && text_cols > 0) {
for (i = 0; i < text_rows; ++i) {
if (headers[i] == NULL) break;
remChar = (int)(resX - strlen(headers[i])*CHAR_WIDTH)/(CHAR_WIDTH*2); //To centre align text from header
for (j = 0; j < remChar; j++) {
strcpy(menu[i]+j, " ");
}
strncpy(menu[i]+remChar, headers[i], [COLOR=Red]text_cols- remChar[/COLOR]);
menu[i][[COLOR=Red]text_cols-remChar[/COLOR]] = '\0';
}
menu_top = i;

In both the places shown i red colored text. I will need to figure out the reason. Till then try changing these values which should serve the purpose.

[EDIT] I guess, it was a mistake to use text_cols-remChar at that place. Replace it with strlen(headers) and let me know if that corrects.

Thanks!
[Android Software Development] Phil3759:
Congrats for this amazing work

You just TWRP-fied CWM GUI

You went into the GUI and touch handling far from all I've done till now

[MENTION=2784807]DooMLoRD[/MENTION] suggested that I contact you

I do to congratulate the work you've done

However, just watching through your code changes gives me some bad headache :D

It will be a huge effort on my side to follow with it

In any-case, feel free to ask if you need some info about parts of my code
[XPERIA X8 Q&A, Help & Troubleshooting] L_S:
I wonder if it is possible to change the color of "Battery status style" to blue (ICS). I'm using a theme CM7 ICS and not combined green.
[XPERIA X8 Q&A, Help & Troubleshooting] vislavskid:
yes you can, with uot citchen i menaged circle batery for mine gdx v0.22 http://uot.dakra.lt/ With root explorer copy framework-res.apk and SystemUI.apk to sd card and pot it on pc and upload to uot citchen and chose yours batery stile.
[XPERIA X8 Q&A, Help & Troubleshooting] L_S:
Do not want to put circle.

I want to change the color of the line (at the top of stats bar) to blue.
[HTC Sensation] redtech83:
What exactly is beats audio? Is it different hardware or just software? I have a sensation 4g and flashed numerous ROMs, some with and some without beats audio, and I can't tell any difference with the audio and I can't find any explanation and/or specs. Is there something I'm missing? I've just been assuming its hardware I don't have, so haven't much worried about it.