yashsingh1/xdaforums huggingface dataset:
[Android Software Development] cooldudezach:
This isn't an issue with what rom you're using, it's about how the github repo needs to be set up. You need to have a github repo set up to build cwm under a cm-11.0 branch. Once that is set up, then Phil3759 can build his recovery for you.
[Android Software Development] Phil3759:
Update 6.16.9 *** Only for jflte ***

This build is now using the new independent libtouch source code

There are no changes kernel and other things wise, just a massive code cleaning, many bug fixes at compiler stage and potentially on run time and moving all touch source to dedicated separate files.

Next updates will bring a prebuilt libtouch support. I will upload to git at that time, once all done

I just need you to flash and test if all settings/features are still fine, as they were :good:
[Android Software Development] chavdar:
I flashed it and found no difference -great as usual. Only the saved settings from 6.15.4 did not worked. Had to set some GUI options agan.

When I do some backup/restore will posr again

Sent from the GT-I9505 Galaxy
[Android Software Development] chraso:
Hi philz,

Thank you again for making this recovery.

I had successfully compiled the 6.15.4 from github sources.

Now that I know it works for my device, galaxy5, I would like to know more about the EXFAT module

How do I make 1?

Also the BRIGHTNESS_SYS_FILE.

As I don't know what it should be, but our phone have no sensor for auto brightness.

So is it useful without the auto brightness sensor?
[Android Software Development] Phil3759:
exfat support must be enabled in kernel and in minivold:

https://gist.github.com/PhilZ-cwm6/6856758

BRIGHTNESS_SYS_FILE

it is for full builds to enable you to change screen brightness in recovery

Very soon, you could have a libtouch that auto detects all these flags, no more need to wait for me to port devices
[Android Software Development] Phil3759:
Help Request

I am trying to compile recovery using the prebuilt libtouch_gui.a file I could compile

However, if I try to use something like this:

include $(CLEAR_VARS)

LOCAL_MODULE := libtouch_gui
LOCAL_SRC_FILES := libtouch_gui.a

include $(PREBUILT_STATIC_LIBRARY)

and link against it with:

LOCAL_STATIC_LIBRARIES += libtouch_gui

I end up with:

Any developer used to CM sources can help me here?

Edit: seems I could get it to compile :victory:
[Android Software Development] wmfaiz:
[MENTION=4666971]Phil3759[/MENTION] can you do cwm for lenovo k900???
[Android Software Development] Bhargav97:
Just wait for few days until phil3759 implements his libtouch successfully. Then, tell any developer of your device to make one for your device from Github source. Because, I think after the implementation of libtouch, there's no work that phil3759 will takeup(device-specific).
[Android Software Development] wmfaiz:
Well k900 doesn't have any recovery at all except stock recovery
[Android Software Development] ermacwins:
[MENTION=4666971]Phil3759[/MENTION] I take it that it works fine for 19300 on stock 4.3 roms?
[Android Software Development] Phil3759:
Finally, I could get the external libtouch to be linked to recovery :fingers-crossed:

Missing my phone... Will try to plug it hoping it can handle a small flash to test
[Android Software Development] tetakpatak:
[MENTION=4666971]Phil3759[/MENTION] your dual-boot recovery for Tab 2 is fantastic! [MENTION=5153662]Android-Andi[/MENTION] has released yesterday the NEXT-2.1.6 kernel version for all three P51xx tabs., I was dreaming of this moment since I've tried your PhilZ touch for the first time.

Now we can use dual-boot, flash zips from ADB sideload and have this beauty of a recovery.... Thank you, Phil, Andi and [MENTION=4021423]ketut.kumajaya[/MENTION] so much for making us all this dream has become true!

Now let's see how far is the development of Ubuntu touch for P51xx meanwhile :D
[Android Software Development] aviwdoowks:
Would you please reply?

Thanks

http://xdaforums.com/showpost.php?p=50597773&postcount=27
[Android Software Development] danarama:
If you post there, no need to post here. Replies will happen when required. .please don't spam. Be patient
[Android Software Development] Phil3759:
6.18.7 (25.02.2014)

Developers info post updated

<< POST 2 >>

updated parts in dev post:
[Android Software Development] tvm2487:
Can you build the recovery for the epic 4g touch using this kernel and vendor files because when CM made there graphics update it caused video issues on our device this kernel and vendor files revert that update

https://github.com/mtb3000gt/android_kernel_samsung_d710

https://github.com/mtb3000gt/android_vendor_samsung_d710

https://github.com/mtb3000gt/android_vendor_samsung_d710-common
[Android Software Development] hkfriends:
Hi Phil

Would you please to port your recovery to Pantech A890S ?

Kernel Source: v1.29

http://opensource.pantech.com/model/list.asp?Category=Mobile

Many thanks
[Android Software Development] llcoolveer:
Phil ,if i hit the i9300 link for the downloads it won't bring me anywhere ??!! The Mediafire link shows an old 5.00.5 version and the Goo.im dev (http://goo.im/devs/philz_touch/CWM_Advanced_Edition) link returns me right back to this topic ...:cowboy:

I hope you can lead us to the right place for that awesome recovery of yours again...:good:

Thanks in advance and keep up the good work Phil

LLCOOLVEER
[Android Software Development] BadUsername:
Link is working fine, try to open it in a different browser.
[Android Software Development] llcoolveer:
Houston,we got lift-off...:good: first time ever Google Chrome flunked in XDA related stuff....thank god there is IE...*sometimes*

Thanks,

LLCOOLVEER
[Android Software Development] Bhargav97:
Finally...We'll try to compile full version for Galaxy 5.

Now, if it works...what all do you need to include Galaxy 5 in "Supported Devices" list?

You are very fast...

Thanks for your great efforts.... :)

Sent from my KitKat bars...
[Android Software Development] mikereidis:
Hi, Thanks for your work. :)

------------------------------------------------------------------

EDIT: Never mind. I just found Advanced setting for Storage. :)

Maybe /data/media should be the default. I previously even set the recovery to defaults.

------------------------------------------------------------------

LG G2 Sprint LS980 w/ I think latest philz_touch_6.13.1-ls980.zip

CM11 Nightly OTAs have never worked. It reboots to recovery and asks if I want to "Install Untrusted Package".

But I see the error:

E: failed to open /data/media/0/0/cmupdater/cm-11-20140225-NIGHTLY-ls980.zip (No such file or directory)

The problem is that it's trying to access ".../0/0/..." instead of single 0: ".../0/..."
[Android Software Development] Phil3759:
you just link me to your thread or attach them here and I will upload them to goo.im and main OP

you can add your signature here:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/advanced_functions.c#L3328

But please do not remove my parts ;)

Yes, it is well covered in the FAQ

If I default to /data/media, users will complain not seeing their files in phone and when in MTP mode
[Android Software Development] cooldudezach:
I'm assuming that you are no longer going to build all the recoverys since you released the libtouch?
[Android Software Development] Phil3759:
I do not think I am going to keep up updates as I did till now

However, I am planning to update all devices again to have a proper kitkat based recovery since many patches were added to cm-11.0 branch and recovery

After that, I will support developers to compile it when they have issues

It is just like if it was opensource
[Android Software Development] Bhargav97:
It means that the supported devices won't get updates from you? Developers will have to sync their repo and build recovery again for their devices when an update arrives?
[Android Software Development] Phil3759:
Yes, I am not going to spend all my time on this

I will focus on selected devices, recovery source improvements and support developers if they have issues in porting it

It is really like if it was open source now. You can modify most recovery parts, add your custom code, make it dual boot, f2fs... while still having full GUI functions
[Android Software Development] cooldudezach:
Awesome. I figured that's how it was, just wanted to make sure. :) Thanks again for all the hard work you've put into it :good:
[Android Software Development] HippoMan:
Forgive my confusion, but does this mean one more set of updates (up to 6.17.8) on http://goo.im/devs/philz_touch/CWM_Advanced_Edition, and then that's it?

Or is 6.15.4 the last set up updates that you will have built for that site?

In either case, thank you for all your great work!

.​
[Android Software Development] RS050377:
[MENTION=4666971]Phil3759[/MENTION]

In new version 6.18.7 the time is 1 hour behind, in version 6.15.6 it works ok an my Galaxy S4 Kit Kat. Is there a new time bug?
[Android Software Development] thereassaad:
Hello phil3759 I need link to download new update for S3

☆ thereassaad ☆
[Android Software Development] chraso:
Hello Phil,

I need help on the brightness_sys_file.:confused:

As I'm confused for what to type at there I undeclered it at boardconfig.mk :rolleyes:

Now I get the error as below.

Phil, note that, this error came only in your latest github source release.

It wasn't coming in olderversions.

Edit:

found what was wrong.

Mods can delete this post
[Android Software Development] cooldudezach:
Here's a question for you. I'm building the newest philz for another of the zte devices which has a dedicated partition for the internal sd rather than /data/media. However, I can't figure out why it's defaulting to /data/media. If I try to set /sdcard as a mountpoint for the internal sd, I get "mount: mounting /devices/platform/msm_sdcc.1/mmc_host on /sdcard failed: Too many symbolic links encountered"

---------- Post added at 05:29 AM ---------- Previous post was at 05:27 AM ----------

This is where I found mine:

BRIGHTNESS_SYS_FILE := /sys/class/leds/lcd-backlight/brightness
MAX_BRIGHTNESS_SYS_FILE := /sys/class/leds/lcd-backlight/max_brightness

however, I'm not sure if that's true for all devices. I saw mentions while searching google that other devices have it in /sys/class/backlight/{stuff}/brightness
[Android Software Development] chraso:
Hello Phil,

I gets blank screen even after defining the BRIGHTNESS_SYS_FILE tag in BoardConfig.mk file.

I 'm facing this problem only in ur new source release.

In older version screen was there.
[Android Software Development] Phil3759:
Please put the quotes, even if it is supposed to work without, not sure

The max brightness flag is not used

For devices without datamedia, you must set your fstab properly to /storage/sdcard1

Look at the device htc_fireball in CM repo to set up your fstab accordingly

BRIGHTNESS_SYS_FILE := "/sys/class/leds/lcd-backlight/brightness"

BRIGHTNESS_SYS_FILE is only used to toggle display brightness

Maybe reboot into system and try to provide a log

There are no changes in device tree. Could be your device needs a special graphics.c
[Android Software Development] Android-Andi:
Hey [MENTION=4666971]Phil3759[/MENTION] !

Thanks for the great news and update :)

I can compile for p31xx and p51xx in future from time to time - i allready updated it to 6.17.8 for us ;)
[Android Software Development] danarama:
Yeah here's a question [MENTION=4666971]Phil3759[/MENTION] , Do you want me to take over N5 compilation?
[Android Software Development] titanic_fanatic:
[MENTION=643734]Philz[/MENTION]3759, I don't think it's necessary for me to create a new thread and was wondering if it would be ok if I uploaded to my androidfilehost and just had you link to it in the existing thread for my device? What do you think about that?
[Android Software Development] kornspitz:
This also working with lg p880?
[Android Software Development] Phil3759:
Freedom guys :highfive:

You do what you prefer, what you want, just follow the little recommendations I added in post 2

What I mainly ask for: providing a recovery.img link so that I can update goo.im official host

Apart from that, you're welcome

The more devs go compiling this, the less I have to do

I will provide the sources to modify minivold for exfat/ntfs and also to automatically add extra.fstab without modifying BoardConfig
[Android Software Development] Bhargav97:
As stated earlier by you (phil3759) [MENTION=4141775]chraso[/MENTION] fixed brightness_sys location and even then still we're having a blank black screen.

If I touch screen at different places, brightness changes for that moment (like if I am opening any menu) and same happens with volume keys.

There's no log file in recovery. Recovery log file is available only of older recovery (through which I flashed philz recovery).

About graphics.c, We've already got a working TWRP (only mounting not fixed)...so it may not be a problem of graphics.c. Maybe tag can be different.

What can be done now?
[Android Software Development] titanic_fanatic:
CELOXHD - New Philz & Download Link

Alright, I have compiled 6.18.7 without a hitch ;) I have uploaded it to my androidfilehost.com account along with the rest that are in your goo.im. Here is the link so that you can update goo.im, and If I could get you to also add the link to the device thread you started for us, that would be awesome:

Philz Touch CWM

Waiting patiently for the modified minivold, and thanks a bunch for making the libtouch_gui. This will be so much easier for everyone in the end I think.
[Android Software Development] Phil3759:
If your graphics.c misses this:

void gr_fb_blank(bool blank)
{
#ifdef RECOVERY_LCD_BACKLIGHT_PATH
int fd;

fd = open(RECOVERY_LCD_BACKLIGHT_PATH, O_RDWR);
if (fd < 0) {
perror("cannot open LCD backlight");
return;
}
write(fd, blank ? "000" : "127", 3);
close(fd);
#else
int ret;
if (has_overlay && blank) {
free_overlay(gr_fb_fd);
}

ret = ioctl(gr_fb_fd, FBIOBLANK, blank ? FB_BLANK_POWERDOWN : FB_BLANK_UNBLANK);
if (ret < 0)
perror("ioctl(): blank");

if (has_overlay && !blank) {
allocate_overlay(gr_fb_fd, gr_framebuffer);
}
#endif
}

then add it at bottom of your file maybe

Also, what is your max_brightness file content if you "cat" it?

cat /path/to/max_brightness

Try to swipe right on the screen. By default it should increase brightness if the issue is a low default start value

You can also try to set a higher value in the /data/philz-cwm6/***.ini config file so that it is loaded on first start

If these fix your issue let me know and I will implement a proper fix
[Android Software Development] Phil3759:
Minivold patches uploaded:

https://github.com/PhilZ-cwm6/android_system_vold
[Android Software Development] emmanueldmc:
I have philz 6.15.4 for the JFLTECAN (galaxy s4) my problem is I can not delete the backups from any file explorer like es file explorer...any! Pleas any help?
[Android Software Development] titanic_fanatic:
Did you grant the file explorer root permissions by sliding out the left menu and selecting root explorer listed under tools. You have to also have to remount the partition as rw either by shell our by file explorer. Es allows you to do that under root explorer.

Sorry if you knew this already ;)
[Android Software Development] Bhargav97:
It has most of these lines under RECOVERY_LCD BACKLIGHT_PATH but is missing these:

if (has_overlay && blank) {
free_overlay(gr_fb_fd);
}

AND...

if (has_overlay && !blank) {
allocate_overlay(gr_fb_fd, gr_framebuffer);

Can absence of these cause a blank screen?

And...swiping right won't do anything, I tried just now.

Will soon let you know otput of cat-ing that.
[Android Software Development] cooldudezach:
I figured out what I had been doing wrong. I had used the same device tree as the nex, making changes as needed, so the fstab ended up as /storage/sdcard instead of /storage/sdcard0. It's all good now. Should be ready to have it marked as official support here soon. :)

Question:

For links to device threads, do they need to be on xda? I don't do much over here, all my work is over on android forums.

Edit:

another question: while building for another device which has interesting screen dimensions (480x854), I get this error:

/home/cooldudezach/android/zte/cm11/out/target/product/hera/obj/NOTICE_FILES/src//system/lib/libstdc++.so.txt
make: *** No rule to make target `bootable/recovery/device_images/bg/480x854_bg.png', needed by `/home/cooldudezach/android/zte/cm11/out/target/product/hera/obj/RECOVERY_EXECUTABLES/stitch.png_intermediates/stitch.png'. Stop.

Where do I edit the source to fix this?

Double Edit: Nevermind, I realized after looking in that directory that I just needed a new image of the proper dimensions (In the terminal, it wasn't so easy to see what the directory was, xda formatted it nicely lol)
[Android Software Development] Phil3759:
I added the image to my git ;)

You can publish your work everywhere you like. Just follow the small rules in post 2 please

Mainly, push your needed changes to my repo or post them here in

tags to maintain the official git uptodate

The project will keep alive if people start to maintain it. That's why I made the touch library

Also, a link to your files so that I add them to goo.im mirror
[Android Software Development] Bhargav97:
We also had to do that for our Galaxy 5 which has dimensions 240x320.
[Android Software Development] Phil3759:
added too

Please do not forget to push needed changes to bootable/recovery/boardconfig/BoardConfig.mk to my git or link them here

Another easy way is to fork my work on git and submit your patches to your own git

I would see your changes drom this link:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/network

And you can easily push patch commits from your repo :)
[Android Software Development] sweets55:
Phil3759 - Not sure if this is the placed to ask but any chance your going to make a recovery for the LG Flex? We don't have a recovery yet but I guess maybe this weekend.
[Android Software Development] danarama:
La de dah de dahhhhhhh *reads post 2*
[Android Software Development] DoctorQMM:
anyone have insight to resolve the following error encountered on 6.0.4.7 [on t0lteatt (both 6.12.8 and 6.15.4)]:

"set_perm: some changes failed. E:Error in /storage/sdcard1/downloads/GNote2/SkyNoteAir/SkyNote Air Vanilla Update F3.5.zip (Status 7). Installation aborted".

I flashed recovery partition back to 6.0.4.5 (6.07.9) and updater-script installed successfully... however, when on 6.0.4.7, get the error. Am I missing a setting somewhere on 6.0.4.7 ? Thx
[Android Software Development] Bhargav97:
What you'll have to do is:

i)Go through your updater-script and find out a/all the "set_perm" command/s which have been given for a file which actually doesn't exist in your zip and remove those lines.

It's all because of new format of updater-script that has been implemented in cm-11.0 branch recoveries.
[Android Software Development] Phil3759:
I added a special option to let users only deal with device name assert line

It is in faq
[Android Software Development] tetakpatak:
Post #2762 ;)
[Android Software Development] habylab:
You're right. He could just bung in Semaphore kernel, if approved.

It is a bit more complicated than the others, isn't it?

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Android Software Development] shoey63:
Well I would assume procedure is similar ie. unpack Zimage with Chenglu's script, make changes to recovery and ramdisk, then repack with Tar Gz padding.

Complicated is Xperia Z. Doesn't even have a stock recovery :confused:
[Android Software Development] Phil3759:
No recovery mode at all?

I will look at it but sadly, only after i am done with dual boot

If, by the time, there is a custom recovery by some dev, it will be even easier
[Android Software Development] shoey63:
Well there must be. I've seen it during an OTA update - just no known button combo to access the stock one. Some pretty clever Devs over there though (Even [MENTION=591147]Entropy512[/MENTION] owns the device). I'm currently running CM10.1 WITH CWM 6.0.3.2. Already good enough to use as a daily driver after only a couple of months development (Thanks to Sony sharing sources) There are others who have got CWM going too, as well as TWRP. [MENTION=2784807]DooMLoRD[/MENTION] has his githubbed. But yeah, all in good time, when you have finished your current projects :thumbup:
[Android Software Development] Phil3759:
Well, if there is already a cwm, it won't be a big deal, at least to boot it. After that, we could need some debugging for extra features, but not necessarily. The easiest would be to have someone compile it from my source and test the non touch version. If it is ok, it would be debugged at 90%
[Android Software Development] undead_assault:
Hi Philz,

thanks for those amazing kernels you present.

I've got a question, why do you choose Superuser over SuperSU?

Because from my little understanding, it seems like SuperSU is more rich-featured than its counterpart. It can unroot, and also switch to other root application (superuser).
[Android Software Development] wpkwolfseye:
Ok, here it is. Hope you can make it work, Phil. Would greatly appreciate it. Thats from the latest German Firmware which I am going to install now, since it appears what my N8010 was running was not the latest.

Some other thing that might be related. With the Tablet i also ordered a 64 GB SD Card which I formated in the Tablet and it works fine. However, and that might be only related to the CWM I am running atm, the SD Card is not recognized by the CWM. Will that be the same with your CWM or do I have to format it different to make it work ?

Thanks in advance.

Wolfseye
[Android Software Development] Phil3759:
5.06.4 (06.06.2013)

Also, N8010 specific recovery released:

http://xdaforums.com/showthread.php?t=2202714
[Android Software Development] wpkwolfseye:
Thank you so much, Phil ! :) Now it works and also recognizes my ext. Memory Card with 64 GB. Thanks, appreciate it. ;)
[Android Software Development] Phil3759:
MicroMax (unofficial repack by [MENTION=5243421]icspanneer[/MENTION])

- A56/A57
[Android Software Development] icspanneer:
Thanks for adding this main thread.. :)
[Android Software Development] Phil3759:
You're welcome :good:
[Android Software Development] Bushido76:
Hey Phil,

thank you very much for providing and maintaining my favourite recovery... :)

Today I've got a question. I use a 64GB external sdcard, which is divided into two partitions (1: fat32 / 2: ext4). When I enter the recovery I realize, that the ext4-partition is mounted as "ext-sd". At the first hand it doesn't seem to be a problem, but at the second hand I experienced the following problems:

- A factory reset/wipe always cleans the ext-sd partition. In my case I use this partition to run Ubuntu Linux (5GB).

- A backup to external-sd (fat32) always makes a backup of ext-sd (ext4) which is not needed in my case.

Is there an option to avoid the automatic mount of ext-sd?

Thanks in advance,

Bushido
[Android Software Development] Phil3759:
1- it is sd-ext and not ext-sd

2- you can use custom backup mode to not backup sd-ext

3- do not factory reset, instead: format /data and format /cache in your case will do the job

Most use sd-ext as a holder for additional /data space, so it was included in factory reset by default in original cwm
[Android Software Development] Damien White:
Is there any chance that 5.06.4 will be available on Manguro? I keep checking daily, but I noticed that it's still at 5.06.0.
[Android Software Development] Phil3759:
Look at change log please

There is no point at updating for your device
[Android Software Development] Dinky:
AT&T i337 - Galaxy S4 i9505 with booloader lock

Would you please make a lokified version for AT&T i337? It will be greatly appreciated.
[Android Software Development] Phil3759:
Not for now, sorry

Porting new devices is paused, unless filling previously discussed conditions

Have some real life stuff to deal with and need to focus on new features
[Android Software Development] RuralGalaxy:
Nice recovery friend! Thanks for share!