yashsingh1/xdaforums huggingface dataset:
[Android Software Development] JEANRIVERA:
This does not work for me I'm on the HTC One

Aroma File Manager Support *Adapted from amarullz and sk8erwitskil

You get here the possibility to browse your phone with root access in a friendly GUI file browser, while being in recovery

You even now get a terminal emulator to run in recovery

Download Aroma File Manager from its Home Page

Get the 1.80 version and name the file aromafm.zip

Put the aromafm.zip in clockworkmod/aromafm/aromafm.zip in external or internal sdcards

In recovery, tap the Aroma File Manager menu or double tap any part of the screen outside menus

It will launch the file manager automatically

Double tap gesture linked to Aroma File Manager can be altered in the GUI Settings menu
[Android Software Development] andreya108:
[RECOVERY][PhilZ Touch 6.17.8] HTC Desire 601 dual sim (zaradug)

Hi!

I have been built the recovery for HTC Desire 601 dual sim (zaradug) from the current PhilZ-cwm6 sources from github and stable/cm-11.0.

Was forced to disable doublebuffering in graphics.c since it causes screen flickering (dunno why).

This image should not be flashed (htc bootloader cannot load kitkat), just boot it via 'fastboot boot philz_touch_6.18.7-zaradug.img'.

So here it is:
[Android Software Development] Bhargav97:
Yes, I saw and tried that option: "Don't allow old updater binary" unchecked it. But, then it gives error just at the device name assert line. Is anything wrong?

And...We've tried adding those lines to graphics.c which were missing but still it's a blank screen.

Any ideas? What can be done now?
[Android Software Development] Phil3759:
Assert is explained in faq

1. If you compile stock cwm from latest sources, screen is ok?

2. Did you try to compile the advanced version only by disabling philz touch flag in Android.mk?

My mod doesn't modify graphics in any way, except brightness

That is easy to figure out through adb shell though as i explained

Black screen with working recovery in background is usually a broken graphics.c file
[Android Software Development] Bhargav97:
Yes, In stock cwm screen is ok.

And...uptil your recovery's version 6.15.4, it was all fine.

After you released 6.18.7, the issues came up.

Okay...will try to compile recovery by turning off the philz touch flag in Android.mk.

Can you help us by just having a look at our graphics.c, if you have time? If you can, I will upload it and give you.
[Android Software Development] Phil3759:
Sorry, i have little knowledge there. And without the device, it is problematic.

Try to reverse the new changes in graphics.c added by cm team (overlay)

Also please:

1- does phone respond to adb commands while screen black in recovery?

2- sync latest stock cwm and try it

3- try my sources with disabling philz touch flag and only compile advanced edition

If both are fine, then it is my libtouch!

In that case, try to replace my custom stitch.png with the one from koush and see if it works. Maybe it is the memory limited to load my custom png for background

I see no other reasons except you did not provide info about brightness i asked for. Libtouch will set brightness by default to 165. If your device has a very high max/min range above standard 255, it can cause issues on some devices

Please try ALL this and give a DETAILED feedback for EACH step i asked for
[Android Software Development] Bhargav97:
Sorry...I forgot that brightness part.

All the detailed info on these steps will be provided by me or [MENTION=4141775]chraso[/MENTION] as soon as possible.

Thanks a lot...
[Android Software Development] AndroidReborn:
Okay I need help.

I was running stock 4.1.2 with siyah kernel 6.0 b5. Now I used gs2 kernel wipe and the installed your kernel through recovery via zip. Now I cannot go beyond the galaxy s2 screen.

Sent from my Nexus 4
[Android Software Development] RK:
This is a recovery not a kernel
[Android Software Development] gr8nole:
[MENTION=4666971]Phil3759[/MENTION]

Can you please add the screenshot flag to the lt02wifi portion in BoardConfig.mk.

I have tested it and it works.

BOARD_USE_FB2PNG := true

Thank you.
[Android Software Development] AndroidReborn:
But isn't a recovery part of the rom?

And in any case, now I'm stuck in bootloop
[Android Software Development] gr8nole:
No, recovery is not typically part of a rom.

If you wiped your kernel, then you need to re-install a kernel to get out of the bootloop.

Sent from my SCH-I605
[Android Software Development] AndroidReborn:
But in the galaxy s2 it is :( So I've been reinstalling kernels for the last hour and I've installed 5 of them, all of them giving bootloop. Wiped everything, still bootloops...
[Android Software Development] tetakpatak:
Can you not flash your previously used ROM again?
[Android Software Development] DavidFlory:
It sounds to me like you may be confusing recovery (which never contains a kernel) with a ROM (which usually does). Exactly what are you flashing and using what tool?
[Android Software Development] tetakpatak:
Actually it does on some phones: on the i9000, recovery and kernel are just always in the package. Recovery can't be flashed alone there. I don't know if it is different or same with his i9100.
[Android Software Development] AndroidReborn:
I'll try to download it. The servers hosting it are down.

Tried restoring backup... Still giving bootloop.
[Android Software Development] Bhargav97:
It's simple.

Go to samfirmware.com and then find firmware for your mobile and download it. Then flash using Odin.
[Android Software Development] RK:
Ah OK. Forgive my ignorance.
[Android Software Development] AndroidReborn:
So, um, can I ask a simple favour from you all? I already have sentinel rom 5.00 downloaded on my sd card which I was going to install after this kernel. And seeing that in any case I'll have to download rom, I can access recovery while using any kernel and I've already wiped everything, can you please tell me any compatible kernel for my phone so that I can install the rom? And the procedure as well? It's based on 4.3.

Of course I'm just requesting you. I'll be highly grateful if you can do that.

---------- Post added at 09:40 PM ---------- Previous post was at 09:36 PM ----------

The link for the rom is http://xdaforums.com/galaxy-s2/development-derivatives/sentinelrom-02-10-2013-t2268064
[Android Software Development] tetakpatak:
Try to wipe all and format /system before restoring your nandroid backup. Do you use same recovery version you had when you created your nandroid?

Otherwise you cannceirtanly revive your i9100 by doing what [MENTION=5165022]Bhargav97[/MENTION] suggested you to.
[Android Software Development] AndroidReborn:
Wipe what? Data, cache and dalvik?

Done... What do you mean by format?

And can you help me with sentinel rom? I posted the link above.
[Android Software Development] Heppieboeddah:
Request

To OP, any change there will be a recovery availble for the Galaxy NotePro 12.2 soon?

Wouldt be great
[Android Software Development] tetakpatak:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.

Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
[Android Software Development] Phil3759:
added to op and goo.im :good:
[Android Software Development] andreya108:
Thank you for support,

anyway, did you ever heard about flickering when using double buffering?

The image in the second buffer is shifted about 1.5 lines on the screen.

I've seen similar photos on the forum. Like this: http://xdaforums.com/showpost.php?p=48396727&postcount=62

But I was unable to find any noticable bugs in graphics.c

And I did not found anything similar in devices affected: different chipsets, different resolutions etc.

Do you have any idea what can it be?
[Android Software Development] bthorne79:
[MENTION=4666971]Phil3759[/MENTION] what would you need to build a recovery for SPH-L720T
[Android Software Development] Phil3759:
I heard once, never reproduced it

If you use a graphics.c without the double buffering it should fix it

I am not very competent in dealing with graphics part
[Android Software Development] hachamacha:
Hi and nice recovery work. Tried an older version of this for the first time on xt926 and think it is terrific. Many thanks.

I'd like to build the latest version using the touch library you wrote since the latest isn't going to be built for xt926 from what I read. I've read post #2 and many others. I was wondering if you'd written a basic "howto" for building the github code once you'd gotten it. I've built many kernels and ROMs and have done a lot of internals/embedded linux work but feel like I'm missing something basic from the github code (it could easily be my brain). In response to post #2 where it says "first build cm11 without errors"(or something along those lines) I just did that.

Anyway, if you'd written this up somewhere, great and please point me to a link or if now and you don't mind a few words about how to get started building it, it'd be much appreciated.

edit: I just realized I misread post 2 about being able to build cm11. It actually says build CWM from cm11 code, so I'll see if I can do that and I'm guessing that'll get me where I want to be.

edit2: OK, just finished building it. Once I understood the whole "swap your recovery for cwm stock", I was able to get it done pretty quickly.
[Android Software Development] Bhargav97:
From now onward, phil3759 isn't gonna take up any device specific recovery building work. The source of his recovery (now, full version) is there at github. Just compile that up yourself or tell any developer of your device to do that.
[Android Software Development] bthorne79:
Mmk
[Android Software Development] JustinXu:
PhilZ Touch 6.17.8 for LG Optimus G Sprint (ls970)

View attachment philz_touch_6.17.8-ls970.zip

just build it with cm sources and it's tested.
[Android Software Development] brolee93:
Hi [MENTION=643734]Philz[/MENTION].

I can see in your changlog you have fix gt n71** but where I can test this?

4.96.6 (28.04.2013)

- support HTC One S (ville)

4.96.5 (27.04.2013)

- change event input handling code to support auto-interpolation

- auto support for devices built-in virtual keys

- enable key repeat for recovery virtual buttons (up/down): now they auto-repeat while pressed

- fix HTC One X nandroid backup was very slow (ramdisk changes)

- fix touch for new N71xx, T889, I317/M repacks based on wanam Adam 2.3 kernel to fix boot delay for non stock kernels

- misc bug fixes and code optimization

4.94.6 (21.04.2013)

- fix compile error for non touch version

- N71xx, T889, I317/M: repack on wanam Adam 2.3 kernel to fix boot delay for non stock kernels

- Fix touch support for HTC One X (endeavoru) and HTC One XL (evita)

- More fixes for HTC Explorer (pico) -.....

Thanks for all [MENTION=643734]Philz[/MENTION]
[Android Software Development] Phil3759:
I am going to update ALL recoveries a last time except Sony (need special repack and they already have great devs involved) .

There are many small things i add compared to stock cwm:

- Exfat and ntfs through kernel static or modules support

- Extra.fstab and fstab edits

- Lzma to fit ramdisk sometimes

- Rotation for some devices

- Use stock kernel for others...

- fix broken device trees...

I will then mainly help advanced users to do those things when they are able to compile and want advanced features.

Just do not expect a basic guide "how do i compile cwm" there are at least 30 such guides on xda and hundreds on google.

Even the cyanogenmod wiki is a good start
[Android Software Development] shoey63:
Hi Phil.

Attempting to compile for Yuga right now:)

I will let you know how it goes;)

Edit: I'm actually tapatalking from my own "self cooked" CM11:D

Edit2 Aaand it's working beautifully.:victory: See you n the Yuga threads soon:cyclops:
[Android Software Development] Phil3759:
added to goo.im
[Android Software Development] Heppieboeddah:
Kicking my message.

What do you need to compile a recovery for the Galaxy NotePro 12.2. And can we expect one for this tablet?

Tia
[Android Software Development] cooldudezach:
Teehee, here's a batch for you Phil3759! I got that pesky flickering screen fixed! In addition, I have now built philz touch for 6 devices :)

To have device forums linked to in the OP, do they have to be forums on XDA?

These ones have been tested so far, when the other three are tested, I'll post 'em here. :)

Virgin Mobile Awe (nex) (this is the device you built 6.16.3 for)

Download: http://d-h.st/mZS

ZTE Source (hera)

Download: http://d-h.st/4in

Boost Mobile Warp 4G (warplte)

Download: http://d-h.st/cV7

EDIT: Oh yeah, I added this little feature, and so I'm letting you know :)

The /storage/sdcard0 and /storage/sdcard1 got annoying, because they can easily switch while booted into android, so I added a boardconfig option to set custom labels for the voldmanaged devices, as shown in the pic.

I'm really hoping you don't reply with 'Oh, you could already do that, like so: blahblah" lol

If you want the code, I can have it up on github later today. The labels also are changed pretty much there is an option to do something with a voldmanaged device. :)

http://i58.tinypic.com/20qxehk.jpg
[Android Software Development] hachamacha:
Thanks for all the work,

Once I actually read the line about "being sure to compile stock cwm correctly", no guide was needed for anything. Many thanks.
[Android Software Development] Phil3759:
Sure, you are free to upload and modify it as you like. Consider it open source. Just put credits. That'all

If you link me or push your changes to github, you contribute to keep all the project alive and enhance it :thumbup:
[Android Software Development] Phil3759:
6.19.2 (01.03.2014)

This a maintenance release mainly to fix bugs for specific devices. Most changes are in ramdisk/device trees and not cwm sources

I am compiling for ALL supported devices, except Sony that is supported by its developers

Expect progressive upload to goo.im in the next 2 days
[Android Software Development] Bhargav97:
phil3759,

Here's what we've done:-

1)max_brightness: Sorry, but there's no such file for our device. Searched whole code and also under /devices/samsung.

2)Stock CWM: Yes, Stock CWM can be compiled and all is working with latest sources.

3)Advanced Edition: No, even this gives the same black screen.

4)Touch disabled and changed stitch.png to koush.png: No, This also gets stuck at a black screen.

5)ADB: Still not tested. Problems with usb of my phone but will let you know asap.

As I said before, already tried adding those two missing lines to graphics.c but still the same problem.

Note: just fyi: we can still get twrp working, only mounting doesn't happen.

Here's a question, this new update: Fix overlay inclusion on MSM targets. Will this help us?

Thanks alot for your efforts...
[Android Software Development] chraso:
Don't see vk png for screen width 240

Hello philz,

Thank you again for maintaining such a good recovery project.

I would like you to note for the device with screen resolution 240x320 there is no file in /device_images/vk/virtual_keys_240.png

I'm attaching the one I resized.

As Bhargav posted already we have tried all the tricks for our device to get the recovery working and unfortunately all fails.

I would like to inform you that our device( Samsung gt-i5500 aka Galaxy 5 ) have not sources for touch screen drivers we have prebuilt library file only.

Attaching it here if that may help.

Edit:

Another userful Info:

I had also compiled the TWRP for same device.

And interestingly touchscreen on that works out of the box.

Without any changes to the any of the line for brightness also works.

I think I should investigate and compare what both recovery does includes.
[Android Software Development] cooldudezach:
Alright, I went ahead and updated the builds to 6.19.2, got more of them tested, and got flashable zips for them all :D

Virgin Mobile Awe (nex) (this is the device you built 6.16.3 for)

Download: http://d-h.st/zpO

ZTE Source (hera)

Download: http://d-h.st/YAi

Boost Mobile Warp 4G (warplte)

Download: http://d-h.st/LDs

Boost Max / ZTE Iconic Phablet (stormer)

Download: http://d-h.st/I6A

ZTE Overture (becky)

Download: http://d-h.st/2DW

ZTE Imperial (apollo) (it's technically not tested yet, but it should be just as fine for official as the others)

Download: http://d-h.st/qvm

AT&T Radiant (metis)

Download: http://d-h.st/K1M

Here's my repo for philz changes. The latest commit adds the labels for sdcard menu options

https://github.com/cooldudezach/philz_touch_cwm6

I'm not that familiar with C, so this is a 'figure it as I go' kind of thing, but I think I did a half-decent job with the implementation.
[Android Software Development] Phil3759:
for now, just ignore the touch, you must debug step by step

Advanced Edition is 100% open source

If screen goes black there, it is wired

Maybe try to get a log from /cache/recovery if it is created or at least from /tmp if you get some adb access

Can be many things: vold, fstab, memory too low...
[Android Software Development] titanic_fanatic:
I'm excited to actually use this ;) Can I ask, does one just define the TARGET_CUSTOM_TAGS in the BoardConfig.mk, and how to define for both internal and external?
[Android Software Development] Phil3759:
But that will cause bad issues:

1- strdup without free

2- libtouch needs the primary_path. Not sure if your code won't break it, but you can try and see, maybe not

In anycase, the strdup use is very very bad idea there
[Android Software Development] Phil3759:
Uploading first batch:
[Android Software Development] Phil3759:
I will upload them to goo.im asap:good:
[Android Software Development] HippoMan:
Thank you, PhilZ, for all your continued excellent work, and all your committed efforts.

6.19.3 works great on my apexqtmo. And 6.19.3 isn't a typo. I guess you made one more bulld before uploading.

Now, I'm hopeful for the version the flo version to show up. :)

.​
[Android Software Development] Phil3759:
yes, some are 6.19.2 and others 6.19.3

Only device specific changes
[Android Software Development] sheraz1015:
HI

hi there

can u please help us by building a recovery for gionee e7 which almost same has specs of note 3 9005 .

thank u

there are many waiting for a proper development

hope u don't disappoint us
[Android Software Development] Bhargav97:
Phil3759 does not take up any recovery building work, especially device-specific...after the libtouch_gui is released. Start this work yourself or tell any developer of your device to do that. Phil3759 may help you if you have any problem.
[Android Software Development] chraso:
refer to xda-university.com for porting to new device
[Android Software Development] DavidFlory:
Has anyone else tried the hlte version on a hltevzw phone? I have the Verizon Note 3 Developers Edition and the latest hlte recovery hangs at the "Samsung GALAXY Note 3" boot screen. I have installed the zip using the preview PhilZ version and using Odin. Both hang. Using Odin to reinstall the older version puts me back ok.

Edit: the MD5s do check.
[Android Software Development] Phil3759:
only for new bootloaders, sadly

I do not plan to bother updating old devices

A dev from your forums can do
[Android Software Development] cooldudezach:
So far it works without any issues as of yet. I've tested most of the functions, and they all work. I'm not really replacing primary_path, just where it adds the text to the menu. What might you recommend to use instead of strdup? Where does free(ctags) (i assume that's correct?) need to go?

Edit: This is where I got the suggestion to use strdup: http://stackoverflow.com/a/2523494

This is how I define it in my BoardConfig.mk:

TARGET_CUSTOM_TAGS := "internal sdcard,external sdcard"

Edit:If you have more voldmanaged devices, you might label them as such:
TARGET_CUSTOM_TAGS := "internal sdcard, external sdcard, USB drive"

It's just a comma-delimited list, and it applies them in order of how they're displayed in the recovery. Also, if for some reason there was a device that had multiple other voldmanaged devices (usbdisk i guess?), this also works for that, so you'll have to take care to pay attention to the order devices are defined in the fstab i guess
[Android Software Development] hachamacha:
For you guys building, a question:

I've been making working images using a git of cm11 and a git of philz code which after a test build of stock cwm I do a :

// setup any unusual params in the post 2 files for my device.
// setup env. "envsetup.sh"
// lunch {mydevice_name}
//
"$ make -j4 recoveryimage

and that seems to work fine.

I don't quite understand the "fakezip" file that "$make -j4 recoveryzip" produces (or that . .build/*/*/makeimages {device} does) because inside it is pretty much everything you'd need for an su environment, busybox and all the associated links, and other /sbin binaries, no recovery.img. Doesn't strike me as being the zip template you'd want to add a recovery.img to.

I guess I had in mind something that is much simpler as a recovery.zip template that merely writes the recovery.img , has the usual manifest and update-binary and updater-script inside.

Am I using some incorrect command to make the .zip templates? I've tried a few things (awk/sed stuff) to try to figure out all the targets from a make at cm11 level but don't see anything else for recovery than the image or zip file.

I don't need the .zip file for me, but in order to contribute to the project it sounds like the zip is the way to go.

Thanks for any help -
[Android Software Development] HippoMan:
Since PhilZ mentioned "strdup without free", I'm assuming that you are not freeing any of the memory that you are allocating via strdup.

The strdup call allocates memory for the string which is passed to it, and it copies that string into the allocated memory. Without subsequently freeing that memory (by calling the free function), the program will continue to hold that memory forever. If your code which calls strdup is invoked repeatedly, and if the allocated strings are not subsequently freed, the memory use will continue to increase within the program, which will never return that memory to the OS. This results in less and less memory being available for other processes within the system, and it can lead to system crashes. This is often called a "memory leak".

Even in the stackoverflow example you cited, the free function is called:

char* token;
char* string;
char* tofree;

string = strdup("abc,def,ghi");

if (string != NULL) {

tofree = string;

while ((token = strsep(&string, ",")) != NULL)
{
printf("%s\n", token);
}

[B][COLOR="DarkRed"] free(tofree);[/COLOR][/B]
}

I don't have your code, so I can't suggest a specific fix for your "strdup without free" problem. However, if you aren't familiar with standard memory allocation routines like malloc, free, strdup, etc., you should not be using them.

.​
[Android Software Development] Phil3759:
Looked better to your code

I see better what you aim. Good idea in fact to change the menu texts for storage volumes

However, your idea should be done completely different:

use strtok rather to avoid any strdup and dealing with pointers

define a recovery setting in a struct that is loaded on start

it would be something like:

vol_display_label.primary
vol_display_label.secondary
...
}

Just an idea but probably needs more work to handle different volume numbers

That way, you do not repeat same code hashes all over the code

Also, not using free after calling strdup is wrong and can lead to memory overload