yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] shumo:
anyone ?

someone must know if it's ok to replace the modem.bin file from a cwm flash-able zip
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
Try it it will work or it will fail .

But make a note of your existing German modem first .

jje
[Galaxy S II Q&A, Help & Troubleshooting] javefang:
have you tried to flash via ODIN? afaik CWM can only flash .zip files
[Galaxy S II Q&A, Help & Troubleshooting] umarian:
Man try this link:http://xdaforums.com/showthread.php?t=1277593
[Motorola Atrix 2] seraphielx:
I have the screen time out (settings->display->Screen Timeout) set at 15 seconds and the stay awake (settings -> appications -> development -> stay awake) checked but it will not stay on.

Anyone else have this issue after update to 5.3.6?
[Motorola Atrix 2] JRW 28:
Sets the screen timeout.... AKA SCREEN TIMEOUT ,if you want it to never timeout, set it to never... 15 sec = 15 sec timeout, 30 sec =30 sec timeout and so on...

STAY AWAKE

Screen will never sleep WHILE CHARGING

this will be the only time the screen never sleeps
[Motorola Atrix 2] seraphielx:
I am aware of the WHILE CHARGING part of it.

I plug it in and it will not stay awake....

I am seeing if anyone else has this issue to see if something went bad in flashing from stock to supercharged to stock to update to stock to update or if they messed something up in the update.

I plug it into my charger to keep it awake while I have it mounted in my car for Google music and it would stay awake with the screen time out option selected and even shut the screen off when I would turn the car off before I updated to 5.3.6

So if someone can give a simple it is working on my phone or a hey you ****ed something up that would be great.....
[Motorola Atrix 2] kirkgbr:
It's working for me. When I am charging it stays awake.

Not sure what "5.3.6" is but I am on the new 2.3.6
[Motorola Atrix 2] seraphielx:
It is 2.3.6 but I just had someone else in the office check it and they have the same issue after the update...
[Samsung Galaxy Player 4.0, 5.0] dbearsfootball:
Will there be a custom rom for the yp-g1 U.S. model?
[Samsung Galaxy Player 4.0, 5.0] Zyxxeil:
Im wondering the same exact thing all the love is going towards the YP-G70
[Samsung Galaxy Player 4.0, 5.0] dunca123:
I am sure there will be eventually. I have the 5.0 US, so I already have access to one custom ROM. Check www.cyanogenmod.com every so often to see if they release a custom ROM. Also keep an eye on the development page. You are bound to get one soon enough.
[HTC Desire S] spymare:
Hi. Today I rooted my Desire S using this tool: http://www.unlockroot.com/

So I enabled usb debugging and clicked root, and it also got rooted.

Then I rebooted into recovery mode and clockworkmod, and wiped everything, now no matter what rom I install, it is stocked at the HTC boot screen.

The problem is now, I can't get it unrooted, because the tool unlockroot requires usb debugging to be on, but that can't be done in recovery mode, and I got no os installed.

I tried to go into fastboot, and then click unroot using the unlockroot tool, but it still won't work without usb debugging :S

does someone got any suggestions?
[HTC Desire S] doghous:
Is your phone S-Off or you unlocked the bootloader from HTCdev.com?

If you've unlocked your bootloader from HTCdev.com then, once you have installed the custom rom you have to do the following:

- extract the boot.img from the rom zip file that you installed and I suggest you place it in your android-sdk platform-tools folder.

- reboot your phone in fastboot

- open a command line window and go in your android-sdk platform-tools folder and flash the boot.img with the following command:

fastboot flash boot boot.img

That's what I need to do on my phone (HTCdev unlocked) when I flash any custom ROM.
[HTC Desire S] spymare:
it is S-on.

After I rooted it with the unlockroot tool I tried to unlock the bootloader, but I can't because when you have to enter the code on htcdev, that it generates, it fails, since the unlockroot tool changed something.

I'm trying your suggestion now, does it need to be S-off?
[HTC Desire S] Rostwildch:
Can you reach the recovery? I suposse you have the clockworkmod installed, if so: can you boot into bootloader using fastboot?

We need more info :)

---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------

Thats it, you need it S-OFFed in order to work. Anyways, if I were you I would revert it to stock and start from the beginning.
[HTC Desire S] spymare:
yeah, I got clockworkmod recovery, and can boot into fastboot

I got hboot 2.00 0002

I just tried with S-on, and it got further than just booting to the HTC logo, it showed a boot screen from the room, but now it shows HTC quality briliant and is stocked there, before it was stocked at only the HTC logo.

It would maybe solve it if I get S-off :)?

I clicked back button and it was into android, but as soon as i unlocked the screen, it went back to the HTC logo :S
[HTC Desire S] Rostwildch:
I think flashing roms won't work with hboot 2.00.0002, you have to downgrade and s-off the phone.

Read this: http://xdaforums.com/showpost.php?p=21733356&postcount=1

and search for other threads in the forum, there are many that explains how to do that.
[HTC Desire S] spymare:
finally I got it working :) thanks alot!!! you just saved me from selling my htc desire s that i bought today :)))
[Samsung Epic 4G Touch] digweed4me:
Update

Cm9 next batch Samsung exynos

http://www.cyanogenmod.com/blog/progress-on-cm9
[Samsung Epic 4G Touch] iSaint:
Made my nipples warm hmmm
[Samsung Epic 4G Touch] Dchibro:
That's pretty encouraging. I do hope our E4GT doesn't take too big a back seat to its GSM brothers though. We all know how that tends to go.
[Samsung Epic 4G Touch] phatmanxxl:
Christmas hell yea! I can't wait.
[Samsung Epic 4G Touch] AntikytheraTech:
Ha! Awesome picture. Good work. Cannot wait for CM9. Does anyone know how the capacitive touch buttons will work for the SGSIIE4GT once we get ICS? Will they light up, be functional at all? Inquiring minds would like to know.
[Samsung Epic 4G Touch] globalninja:
They will work as they do now. The on screen home, back, and search buttons are for devices that don't have capacitive buttons.

Sent from my Epic™ 4G Touch
[Samsung Epic 4G Touch] skndeep102:
the onscreen buttons can be disabled I believe so you can use your hardware capacitive buttons

Sent from my E4GT
[Samsung Epic 4G Touch] AntikytheraTech:
Nice, good to know. As much as I want those soft buttons, it's just too much of a waist a screen real estate when I have perfectly good capacitive touch buttons available. Thanks
[Android Software Development] Napstar:
[ info ]

Hello friends!

as some of u may, or may not, have heard we have been working for the past two months on this project of getting on-screen touch navigation controls for the CWM recovery menu!

most of this work is based on the basic touch capabilities which were ported from SteamMod recovery... majority of the work was carried out by me... with some valuable inputs from my team mate DooMLoRD...

we had already released this working version on various devices which include phones like Ideos X6; Samsung Galaxy SL; SE Xperia X10, Arc, PLAY & even tablets HTC Flyer & Kindle Fire...

we finally managed to merge our sources for various devices (at least for the phones) into a common repo!

These dont currently contain sources for tablets as devices we tested on required very specific changes. We are trying to generalize them. If somebody needs it urgently, post a request as a reply in this thread. We will send them as they currently stand.

These sources are modified ClockworkMod Recovery v5.0.2.7 sources i.e. modification over CM7 git tree for gingerbread branch.

[ credits ]

a BIG thanks to koush & the CM team for their awesome work on the CWM recovery sources

sztupy for his great work on SteamMod recovery!

[ sources ]

For CWM recovery v5.0.2.7 (branch: gingerbread)

https://github.com/Napstar-xda/android_bootable_recovery

[ info for developers ]

now coming to the main part...

we have posted this thread so that it may help other developers port our work to their device... we can use this thread as a medium to communicate if u need any specific help (

FOR DEVELOPERS ONLY... NO NOOBS PLEASE

)... we will also share our experiences and updates on our further work on this touch based system... yes this in not the end of it...

Here is a sneak preview of the things we have already implemeted and are currently testing...

[youtube]JVWqgGfV0SM[/youtube]

it will soon be released for supported devices...

we are well aware that koush is already working on a touch version of CWM recovery... we do not mean to compete with anyone... since we have been working on this for a while, we felt others might benefit from this and learn something new, we sure did learn a LOT ourselves throughout this project...

feel free to use these sources to port this to ur device! but if u use them kindly credit us (Team UtterChaos) and post a link to this thread from ur OP....

enjoy!

P.S.:

this is

not meant

to be a tutorial thread on how to compile recovery from sources! there are many tutorials available for that, SEARCH!!!!
[Android Software Development] DooMLoRD:
[ device specific sources ]

HTC Flyer

Kindle Fire

something new that we are working on:

[youtube]7FN4toSbB5A[/youtube]
[Android Software Development] Napstar:
Guide for porting to a new device

Guide for porting to a new device:

Download ClockworkMod Recovery v5.0.2.7 sources (branch- Gingerbread) from https://github.com/CyanogenMod/andr...tree/2b56f849652676b3e848025123717598d6c74e3d

Apply touch related changes from my repo.

In BoardConfig.mk file from your system-device directory, if you have set some value for; BOARD_CUSTOM_RECOVERY_KEYMAPPING then apply default_recovery_ui.c related changes from my sources into your custom recovery_ui.c sources (Placed anywhere in your source tree.)

Customizing recovery_ui.c for your device of interest:

Set TOUCH_CONTROL_DEBUG flag to 1, set maxX and maxY to 0 from recovery_ui.c

Compile this modified recovery and boot into recovery. Then touch anywhere on screen and note down the values printed for gr_fb_width() and gr_fb_height()

Open recovery_ui.c and modify resX and resY with values returned for above twofunctions.

Now touch extreme corners of your touch panel and note down highest X and Y values printed on screen.

In recovery_ui.c modify maxX and maxY to these extreme values.

Recompile your recovery and test it out.

​

Enjoy touch version of CWM recovery, made available by Team UtterChaos
[Android Software Development] clienthax:
Attempting port to gt540 (5.5.0.4 recovery)

Quite some substantial source differations, but i have the first few touch patchs in place,

compiling now
[Android Software Development] clienthax:
Mhm.. i get

[UI_WAIT_KEY] key code: 330

Key: 14a

when i press on the screen which is BTN_TOUCH

Whatdo :/
[Android Software Development] Napstar:
We forgot to mention that our patches are meant for gingerbread branch (v5.0.2.8) and not for ics branch (v5.5.0.4).

There are a lot many differences between these two branches itself. So, currently these patches will not work for CWM recovery v5.5 (ICS).

We are still working on porting these changes to ICS branch.
[Android Software Development] clienthax:
Ye i noticed the changes, but i managed to hackup a 5.5.0.4 with your patchs applied ;)

Are you going to be doing any more commits today?
[Android Software Development] eyronic:
Is there a shutdown button? I read somewhere in the optimus 2x forums that it's missing. I need it because reboot doesn't work on my phone. Ramhack is messing with it. Using optimus 2x.
[Android Software Development] DooMLoRD:
the new CWM commits (from koush) have removed the "power off" option...

though u can add it to ur self:

https://github.com/DooMLoRD/CWM-Recovery-Modded/blob/master/bootable/recovery/recovery.c#L784

and

https://github.com/DooMLoRD/CWM-Recovery-Modded/blob/master/bootable/recovery/recovery.c#L991
[Android Software Development] sibiru:
Is it working for galaxy gio gt-s5660 ?

How to make it work on gio?
[Android Software Development] Napstar:
It works on Galaxy SL I9003 and few SE phones listed in OP.

Please use sources posted above, or ask your device developer to use these changes for building CWM recovery.
[Android Software Development] squadzone:
Working :D

its Work for Samsung Galaxy Mini ( Gt-s5570 / tass ), but need to resize the menu image and create overlay

this the thread

http://xdaforums.com/showthread.php?p=21278990

and for overlay, check to my github

THANKS FOR YOU ALL, :D
[Android Software Development] DooMLoRD:
great to see this working on other devices!

we encourage all (interested) devs to try n get it working on their devices... feel free to interact with us/other devs using this thread as a platform or via p.m....

also hopefully some time later this week we will should be able to finalize FULL touch-screen interface as shown in the video by Napstar (1st post)... we have improved the graphics ;)

BTW if anyone is interested in porting this to HTC devices let me know... those devices sometimes need SPECIAL changes... the development device we have (HTC Flyer) needed some changes to get touch-screen to even work while in recovery mode!; and thats not even considering the headache of skewed axis, orientation of touch-sensitive panel is different from the orientation of device display...
[Android Software Development] squadzone:
great, i like the video, im waiting for that, Thanks for you :)

but, i want to ask about,

why my screen goes to 4 line, i mean like this

|.....X.....|............|............|............|

|............|............|.....X.....|............|

|............|...X.......|............|............|

|............|............|............|...X.......|

|............|............|............|............|

|............|............|............|............|

| <back>|<down>|...<up>..|..<ok>..|

so if i touch on cross up (X) at same line, the button will blink like i touch the image button

do i need to change something?

how to make point touch like video?

i mean we can choosing without touch the image button?

sorry for my bad english xD
[Android Software Development] Napstar:
In this version, for simplicity we have kept the complete column active for touch inputs. So that user need not struggle finding accurate touch position OR to help easy holding device and calling any action by touching respective columns.

And since this not the case for our next version where precise touch inputs are required, so is shown in video.
[Android Software Development] PoorCollegeGuy:
Hey guys, just dropping by to say hi and let ya know that this thread has been featured on the XDA Portal:

http://www.xda-developers.com/android/team-utterchaos-releases-their-touch-recovery-source/

:) see ya next time.
[Android Software Development] Smasher816:
Looks great guys. This is something I have always wanted.

Its a shame Koush hasn't released his source, especially seeing the Nexus S and SGS phones being so similar.

My only wish would be this on ICS, but I see thats already planned.

I will try to get this compiled for my Captivate i897, is there anything special I need to do first?
[Android Software Development] mb-14:
Hey guys i managed to port the recovery to viewpad 7 variants and its working pretty fine.

But the white text on the recovery screen is merging with the back icon.So i would suggest you change the colour of the icons to make it more visible.Or if any other workaround is possible please suggest.
[Android Software Development] DooMLoRD:
Hi the workaround, specifically for tablets, is to make the buttons align in vertical manner to the right hand side of device... We have implemented the code in such a way that the developer needs to only edit the default_recovery_ui.c file... Specifically the function which returns the locations of objects to be drawn...

We have already implemented it in recovery for HTC FLYER and kindle fire.... U can check the screenshots by following the links to those threads from my signature below...

We will try n post the sources soon for tablets we worked on...
[Android Software Development] squadzone:
yeah, thats happen to me too, i think the problem is layout menu option

since my device is ldpi, and screen is very2 small, i need to change the layout menu so button not overlay with letter, i will report if this works :)
[Android Software Development] mb-14:
Thanks dude,was able to align icons in vertical manner, but had to change ui.c to get precise touch input.Your code is easy to understand:).Almost any type of icon layout can be implemented.(im thinkin GBA emulator style).:D
[Android Software Development] DooMLoRD:
Yes I know thats why we shared the sources with the community... ;)

Btw all of the credit goes to Napstar for coding it... I only kept bugging him with feature requests and final cleaning up the code to make it more readable and general :p
[Android Software Development] DooMLoRD:
current work-in-progress version:

[YOUTUBE]7FN4toSbB5A[/YOUTUBE]

we have released it for testing for Xperia ARC, PLAY users...

there are some minor glitches but we are sorting them out ;)
[Android Software Development] GSLEON3:
HTC...

Hey guys,

I was working on a TWRP2 recovery for the HTC Holiday (Vivid), was having to many issues with testing & soft bricks, something in the GUI code not playing nice with Rezound/Vivid & newer HTC devices.

I'd like to take another stab using the CWM source. Could you please hook me up with the Flyer Source & binary so I can go through it & see how close it is to HTC phone devices?

I'd really appreciate it.
[Android Software Development] KillerKink:
Very cool and excellent work guys!

I would like to port this to Teclast p76ti. Where can I get the sources for tablet?
[Android Software Development] DooMLoRD:
yes of course i will post the sources we used for Flyer either as a tar ball or push them to git... they are not completely clean but u will get an idea of what can be done...

as for the binary u can get it from:

http://xdaforums.com/showthread.php?t=1413915

yesterday i pushed the Kindle Fire recovery sources here:

https://github.com/DooMLoRD/CWM-Recovery-Modded-Kindle-Fire

u can try those directly as those are generic one for most landscape devices... just read thru the ui.c file to update the dimensions if required...
[Android Software Development] KillerKink:
Thanks! Forked.

Is this the active development tree that I can pull the latest changes?
[Android Software Development] DooMLoRD:
its my personal dev. tree... but yes all changes (atleast for that device) will be pushed there...

btw Kindle Fire requires special reboot commands, that why i have created wrappers for reboot commands:

/sbin/reboot_system

/sbin/reboot_recovery

/sbin/reboot_fastboot

just create/modify those files in the ramdisk and use the reboot commands required for ur device...
[Android Software Development] KillerKink:
I see. I managed to get it to run with the 4 soft buttons on the right and the touch does get registered. However, the coordinate are out so it only register the down key. Trying to figure out why.

Does this tree only show the 4 white soft buttons? Your video seem to be way more polish.
[Android Software Development] DooMLoRD:
yes the sources currently uploaded are for on-screen navigation buttons only...

we r still actively working on the full touch recovery u see in the video... there are some glitches... we r working on fixing them
[Android Software Development] KillerKink:
ok. Let me know if you need alpha tester though. I wouldnt mind. :)

---------- Post added at 04:12 PM ---------- Previous post was at 03:36 PM ----------

ok, have to make the following adjustment for the key to be correctly registered.

int position = key->y*4;

I am using y coordinate instead of x and the mouse resolution is only 1/4 of the screen resolution.
[Android Software Development] clienthax:
Are you planning on porting this to ics any time soon?
[Android Software Development] KillerKink:
many thanks for your wonderful work. I have managed to get a working version of cwm with touch support. I have put a link back here on my thread.
[Android Software Development] DooMLoRD:
we do plan to port it but the core recovery, even for ICS is the same, there only change being the LUN file for the latest USB gadget, once u update that in device defconfig the USB mounting in recovery will start working for ICS kernels...

glad to hear that! but which device? tablet/phone?
[Android Software Development] clienthax:
i managed to get most of it done, but the problem is the minui stuff, its changed ALOT from gingerbread to ics

ev_get isnt even a method anymore
[Android Software Development] DooMLoRD:
is there any specific reason u are using the ICS branch?
[Android Software Development] KillerKink:
Teclast p76ti (7" capacitive tablet). I have only used your two commits to port to the latest cyanogen recovery branch(cwm v5.0.2.8).

currently I only use it for rom update so I have not tested the other feature of cwm but it should work.
[Android Software Development] clienthax:
yes, im using it because i have a rom that builds with the recovery image for my phone, i found the commit to the ics branch that changed all of miniui etc and changed it back to the old way, but it keeps all the bug fixs etc from later versions

Now to test :D
[Android Software Development] DooMLoRD:
here u go.... the sources for Flyer are attached...
[Android Software Development] clienthax:
Still got same problem with gt540, no x,y only touch reconginised :/
[Android Software Development] DooMLoRD:
enable debug mode and check if X,Y touch is recognized...

also on HTC devices there is a specific binary/init.rc change which needs to be running in order to enable touch screen... ntrigd or something
[Android Software Development] clienthax:
i have the debug thing turned on, just doesnt print any x,y attall :/
[Android Software Development] Napstar:
What keycode is it printing then?

I hope you are working on gingerbread branch.
[Android Software Development] clienthax:
[UI_WAIT_KEY] key code: 330
[Android Software Development] Napstar:
You are working on ics branch. There are major changes in graphics.c file in ics branch.

We will port our commits for ics soon.
[Android Software Development] clienthax:
i undid this commit to get it the same as gb https://github.com/CyanogenMod/andr...56f4db49c1fde314e1e0b02b32cfc6ceca1dd#diff-20

so it in theory should work :/
[Android Software Development] scanno:
Hi,

I am thinking about giving this a try by porting this for the Advent Vega tablet. I have built CWM 5.0.2.8 from the CM7 tree. Can i merge the sources from here into the CM7 recovery sources?

Verstuurd van mijn Vega met Tapatalk
[Android Software Development] DooMLoRD:
yes... we worked on the CWM 5.0.2.7 sources... so as long as u are on the GB branch u can easily merge the changes :)
[Android Software Development] hubo19890319:
must it based on your moded kernel？
[Android Software Development] DooMLoRD:
No not at all.. U can even use stock zImage (kernel)...

Recovery resides in the ramdisk...
[Android Software Development] scanno:
Thanks.. I replaced the recovery sources from the CM GB brache with the Touch version. The Advent Vega has a recovery_ui.c in its device dependent directory, so i merged this with the default_recovery_ui.c and changed the resolution values and compiled it.

Conclusion it works for the Advent Vega / PoV Mobii. I have 4 touch buttons on the bottom of the screen and can use them to navigate through the recovery menus.

The only thing is that when you browse a directory, that the text overlaps the buttons. Have to figure out way to limit the text lines so the bottom lines are not used for displaying text.

Verstuurd van mijn Vega met Tapatalk
[Android Software Development] Napstar:
Good to know that.

Thanks

For overlapping text, reduce value for max_rows definition from ui.c

Or if you have your landscape mode display then follow kindle fire sources for shifting buttons from bottom to right side.

PS. Please post your thread link in this thread.