yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Geraaaaa:
I found an important bug in the lastest version (6.26.6) for Galaxy S4 (I9500).

The option "format /data and /data/media (/sdcard)" in "Mounts and Storage" causes the loss of permissions to modify the internal sdcard.
[Android Software Development] Bhargav97:
Screen Resolution: 240x320 (I thought you'll make out from screenshot)

Stitch.png:

Virtual_keys.png:

I forgot to mention that our virtual keys are messed up and looks just white as seen in above image. It's taken from location which you asked me.

So Something goes wrong at compile! But what?

AND The default gesture actions are:

I think Slide left should have been screen shot. As it's what you mention in your device-specific threads. And what's Press/Lift, Press/Move?

The default recovery screen looks like this:

Menu highlight color and Menu seperator color and battery/time colors are also not original by default.

Here's the BoardConfig.mk file of Galaxy 5 with all the PhilZ Touch flags we use:

# Copyright (C) 2007 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# BoardConfig.mk
#
# Product-specific compile-time definitions.
#

include device/samsung/msm7x27-common/BoardConfigCommon.mk

## Fonts - minimal footprint (saves ~2MB)
MINIMAL_FONT_FOOTPRINT := true

## Lights - generic driver works better for galaxy5
TARGET_PROVIDES_LIBLIGHT := false

## Kernel, bootloader
BOARD_KERNEL_BASE := 0x00200000
TARGET_BOOTLOADER_BOARD_NAME := galaxy5
ifdef BUILD_WITH_30X_KERNEL
TARGET_KERNEL_CONFIG := cyanogenmod/cyanogenmod_galaxy5_defconfig
else
TARGET_KERNEL_CONFIG := cyanogenmod_galaxy5_defconfig
endif
TARGET_OTA_ASSERT_DEVICE := galaxy5,GT-I5500,GT-I5503,GT-I5508

## Recovery
BOARD_BML_BOOT := "/dev/block/bml9"
BOARD_BML_RECOVERY := "/dev/block/bml10"
BOARD_LDPI_RECOVERY := true
BOARD_USE_CUSTOM_RECOVERY_FONT := "<font_7x16.h>"

## Bluetooth
BOARD_BLUETOOTH_BDROID_BUILDCFG_INCLUDE_DIR := device/samsung/galaxy5/bluetooth

## Camera
TARGET_CAMERA_SENSOR_MP_SIZE := 2
TARGET_PREBUILT_LIBCAMERA := false

##PhilZ recovery tags
TARGET_COMMON_NAME := galaxy5
TARGET_SCREEN_HEIGHT := 320
TARGET_SCREEN_WIDTH := 240
BRIGHTNESS_SYS_FILE := "/sys/class/leds/lcd-backlight/brightness"
BOARD_HAS_LOW_RESOLUTION := true
BOARD_USE_LEGACY_TOUCHSCREEN := true
BOARD_HAS_DOWNLOAD_MODE := true
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_BOOTIMAGE_PARTITION_SIZE := 8388608
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 8388608
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 230686720
BOARD_USERDATAIMAGE_PARTITION_SIZE := 190054400
BOARD_FLASH_BLOCK_SIZE := 131072
BOARD_KERNEL_CMDLINE :=
BOARD_BML_BOOT := "/dev/block/bml9"
BOARD_BML_RECOVERY := "/dev/block/bml10"
BOARD_RECOVERY_HANDLES_MOUNT := true
BOARD_CUSTOM_RECOVERY_KEYMAPPING := ../../device/samsung/msm7x27-common/recovery/recovery_keys.c
TARGET_RECOVERY_FSTAB := device/samsung/msm7x27-common/ramdisk/fstab.msm7x27
TARGET_RECOVERY_PIXEL_FORMAT := RGBX_8888
[Android Software Development] Phil3759:
I am aware of it. Will see how to fix it. I guess it affects all cwm based recoveries, not only PhilZ Touch

If i remember well, 240x320 png files were from you or charaso...

They seem broken in fact. I will see how to fix them
[Android Software Development] Bhargav97:
They were from [MENTION=4141775]chraso[/MENTION].

But then why they work when chosen in recovery?
[Android Software Development] Geraaaaa:
Yes, you are right. The bug appears in the 6.0.4.8 version of CWM, I checked it a few hours ago.
[Android Software Development] Phil3759:
I am sure it is there even from very early versions, since selinux and new media_rw permissions
[Android Software Development] Phil3759:
I verified at home:

His virtual keys have no transparency. I just committed proper ones

Let me know if you have issues

Background on start black is related to your sources

The proof: the pic you posted from cm/out/project/device/recovery/root/res/images/stitch.png above. It is plain black and empty + looks like jpeg corrupted

Check your sources
[Android Software Development] Phil3759:
check gerrit/android_system_vold commits in review

There is some useful things for f2fs

There are also the needed tools in efs2prog

Just cherry-pick them probably
[Android Software Development] hachamacha:
Thanks.

Just took a look: Mostly these two seem interesting:

http://review.cyanogenmod.org/61238

http://review.cyanogenmod.org/62530

and just noticed this:

http://review.cyanogenmod.org/#/c/61273/

Many of the others that catch my attention seem to have been merged long enough back so that today's "repo sync" should have pulled them.
[Android Software Development] DAMAGE_INC29:
Sgs4 flasher

Can I flash it using sgs4 flasher?
[Android Software Development] speedyranger:
Yes!

GT-I9505_4.4.2 with TⓐPⓐTⓐLⓚ4&EchoeRom V.20_FNC9
[Android Software Development] ketut.kumajaya:
Please give me in recovery "mount" command output.
[Android Software Development] Geraaaaa:
CMW 6.0.3.2 is fully working. To fix this loss of permissions I just formatted again with the same option but with that version of CWM and the problem was solved. You could base your excellent recovery on that version of CWM.
[Android Software Development] ali.filth:
hi [MENTION=4666971]Phil3759[/MENTION],

sorry for noobs question :p

last night i was update my cm11 source to KVT49L, but if i build recovery from your last source, i get error like this :

bootable/recovery/minui/graphics_overlay.c: In function 'alloc_ion_mem':
bootable/recovery/minui/graphics_overlay.c:164:17: error: 'struct ion_allocation_data' has no member named 'heap_mask'
bootable/recovery/minui/graphics_overlay.c:166:20: error: 'ION_SYSTEM_CONTIG_HEAP_ID' undeclared (first use in this function)
bootable/recovery/minui/graphics_overlay.c:166:20: note: each undeclared identifier is reported only once for each function it appears in
bootable/recovery/minui/graphics_overlay.c: In function 'free_overlay':
bootable/recovery/minui/graphics_overlay.c:304:31: error: storage size of 'ext_commit' isn't known
bootable/recovery/minui/graphics_overlay.c:335:35: error: invalid application of 'sizeof' to incomplete type 'struct mdp_display_commit'
bootable/recovery/minui/graphics_overlay.c:336:24: error: 'MDP_DISPLAY_COMMIT_OVERLAY' undeclared (first use in this function)
bootable/recovery/minui/graphics_overlay.c:338:21: error: 'MSMFB_DISPLAY_COMMIT' undeclared (first use in this function)
bootable/recovery/minui/graphics_overlay.c: In function 'overlay_display_frame':
bootable/recovery/minui/graphics_overlay.c:358:31: error: storage size of 'ext_commit' isn't known
bootable/recovery/minui/graphics_overlay.c:416:35: error: invalid application of 'sizeof' to incomplete type 'struct mdp_display_commit'
bootable/recovery/minui/graphics_overlay.c:417:24: error: 'MDP_DISPLAY_COMMIT_OVERLAY' undeclared (first use in this function)
bootable/recovery/minui/graphics_overlay.c:419:21: error: 'MSMFB_DISPLAY_COMMIT' undeclared (first use in this function)
make: *** [/home/ali/cm11/out/target/product/arubaslim/obj/STATIC_LIBRARIES/libminui_intermediates/graphics_overlay.o] Error 1
make: *** Waiting for unfinished jobs....

whats wrong with my source?
[Android Software Development] Phil3759:
Try to remove this flag:

TARGET_USES_QCOM_BSP

extra.fstab is to be able to format in specific file systems
[Android Software Development] hachamacha:
I just realized my extra.fstab error which is in of course, page 2 ;) :

Every time I read that post I realize how much I missed while reading it. I understand it's for special cases, but wanted to see it detected by the recovery.
[Android Software Development] Phil3759:
Try new 6.41.4 I released for i9500 and give a feedback please
[Android Software Development] eris23:
Can I post my 6.41.4 build for mako on its thread?
[Android Software Development] danarama:
Isn't there a mako thread?
[Android Software Development] Phil3759:
Yes, it is a stable build
[Android Software Development] Walmer:
Sorry for the noob question, and I already was reading all the FAQ.

I have the 6.26.6 version installed, to Update the new version I just have to flash the .Zip file of 6.41.4 with my actual Philz Recovery (6.26.6)?

Thank you in advance for your support!

Regards
[Android Software Development] eris23:
Is 6.41.5 stable?
[Android Software Development] Phil3759:
6.41.5

Great news for all developers:

I open sourced all parts of the code, including the prebuilt libtouch_gui

Use and modifications are licenced under GPL v3:

You are REQUIRED to release the sources for any modification you aim to distribute using this code

It seems that the touch part of recovery is no more a sensitive part to release as Koush is less implied in CWM and touch code is officially being added

I have no more reasons to keep it closed source

Be fair: publish and share any modifications, no bitbucket crap closed code...
[Android Software Development] hachamacha:
Great news! Thanks for open sourcing libtouch_gui. Cheers.

[MENTION=4666971]Phil3759[/MENTION]:

General question: When you are doing new devices, is there any generalization that can be made about cherry-picks from the Gerrit code under review? I'm curious if you find yourself using it, doing git's ** cherry-pick*? OR: Can you usually manage to get things working OK just using all the mechanisms you've provided in your recovery (like in BoardConfig.mk)?

My CM11 code is getting messy with cherry-picks that I've let get disorganized and I'd rather get new devices working from this end if possible.

And my last note: Updated the moto_msm8960 and nexus thread with 6.41.5, working on ~8 more devices.
[Android Software Development] Phil3759:
I regularly do repo sync before device updates
[Android Software Development] GreySephiroth:
Hi Philz, would you be so kind as to help me with the touch gui source for the cm-10.1 version ? I've succesfully compiled a recovery for my phone but I would also love to make it touch. If i try version 10.2 or 11 , it won't boot into recovery, it will just reboot. Would be very thankful. Have a nice day
[Android Software Development] Phil3759:
I no longer support old branches

You have to debug it with kernel dmsg and logs to see what's wrong
[Android Software Development] shoey63:
Thanks for making libtouch_gui open source Phil. :good:

Now, at last I can increase vibration intensity by modifying

/libtouch_gui /touch_gui.c Line 222 #define VIBRATOR_TIME_MS 25

And change it to 50 to get some proper haptic feedback for Yuga:cowboy:
[Android Software Development] hachamacha:
Still working on msm8960dt unified: In the meantime:

6.41.5 build thread has been updated - latest builds. Have only been able to test xt1060, but all builds up.
[Android Software Development] acabreram:
Hi Shoey! There is any way to get just Phily cwm and no dual recovery for Z1 Compact.
[Android Software Development] shoey63:
Post kernel.sin for your device, and I will try and make it;)

Edit: You will need unlocked bootloader
[Android Software Development] denzel09:
Hi, it could be possible for you update moto g version ?

Thanks
[Android Software Development] hachamacha:
It'd be good to know:

- Which device (xt102* / xt103*) do you have?

- Do you have a link to the device-specific thread for your phone?

Also: I'm not sure there's device repo's in the cm11 source to git and build from, but there are probably some around. I think Phil has an xt1032 one.
[Android Software Development] denzel09:
xt1032, there is already a working version by philz for both xt1032 and xt1033.

Maybe you can use his repo?
[Android Software Development] hachamacha:
Just realizing that there's a "unified moto g" branch under devices called "falcon". I'll give that a shot. I saw that Phil has a repo for xt1032 as well, but doing a unified one would be nice if it happens to work. I see the clause for it in ./bootable/recovery/boardconfig/BoardConfig.mk.

Thanks.

---------- Post added at 09:05 AM ---------- Previous post was at 08:58 AM ----------

Is there a Philz Touch thread under development for your device? If so we can switch to that one.
[Android Software Development] Phil3759:
falcon is officially supported since the beginning
[Android Software Development] denzel09:
http://xdaforums.com/showthread.php?t=2639583
[Android Software Development] matrixzone:
Thanks for the updates

Sorry if it sounds rude.

D2lte is still supported or the support had been stopped? We have didn't have any updates since last couple of updates..
[Android Software Development] hachamacha:
Nice, and thanks. If you feel like adding me as a contributor, I can try to crank out some up to date builds.
[Android Software Development] acabreram:
umm i have locked bootloader for the moment well any way thanks a lot bro!!

but there is a way to delete TWRP from my recovery i am using this http://xdaforums.com/showthread.php?t=2647480

why there is not support for more sony devices i mean there is for z1 and it´s almost the same Z1 compact, ok ok i feel a little frustrated!!

Thanks!!
[Android Software Development] hachamacha:
falcon build

Regarding the unified Moto G / falcon build:

I just realized that the device thread isn't a DEVDB type, so I can only post a build at the end. I'll post it here and at the end, and if [MENTION=4666971]Phil3759[/MENTION] wants to upload it to goo.im, that's great. I can't test these builds, so I rely on the users for feedback in the device thread.

Here is a link for goo.im if you like:

Falcon 6.41.5 build link:

Moto G/Falcon links : 6.41.5 : Image : http://d-h.st/Ksi and Zip : http://d-h.st/6YT
[Android Software Development] unibombz:
Is there ever going to be a build of this for the Galaxy Note I717 ?
[Android Software Development] DSA:
Have a read of post 2
[Android Software Development] Phil3759:
I plan to release my

LAST

mass update for the most known devices and mainly those I got a good support/feedback from users.

Users logs and feedback is what made all this possible

Now, I released all sources.

It is funny to see that a few trolls already did only one commit to them: Replace PhilZ Touch by their own name like this one big troll:

https://github.com/thenameisnigel/OpenRecovery/commit/716c7ccc919c24868f3fbfbdba5f343877c6bb9e

With full sources, you only need to get some developer for your device to build this instead of CWM or TWRP. They can modify what they do not like in GUI freely

This game took a lot of my personal time, I decided it is over.

I am continuing to support source updates, fixing bugs, helping people that want to compile it them selves...

Maybe, a new game will start with new cm internal recovery, if it is decided that CWM will not be supported anymore by CyanogenMod team

Future:
[Android Software Development] danarama:
Can I just say, it's been a blast. Thanks for ALL you time, help and patience!
[Android Software Development] Phil3759:
Again, big thanks for your generous donations

You did a lot for this project, since the very start of it
[Android Software Development] danarama:
You're welcome. I'd donate more if I could :)

...and thanks. You always needed someone to manage "crowd control" ;)

It's a sad day and a triumphant day all at the same time. I mean, what new features are there to add? Not much! It's a complete recovery...
[Android Software Development] Android-Andi:
Hey [MENTION=4666971]Phil3759[/MENTION] !

Thanks for your great work again and for makeing your Libtouch Gui OpenSource :)

I am trying to get latest PhilZ Touch to our Samsung Golden (S3 mini).

It compiles, but needs our own graphic.c - else i get a black screen.

It boots and can flash files, but reboot is not working - none of all the reboot actions.

Here´s the device tree: https://github.com/andi34/android_device_samsung_golden/tree/philztouch

Any idea?

Edit:

Recoverylog: http://pastebin.com/PeQwucwZ
[Android Software Development] hachamacha:
Congratulations on a big job well done and for having the sense to knock it off while leaving it in a great condition. Glad I got in on the last few months of it.

Cheers ;)
[Android Software Development] unibombz:
I suppose it is not supported. I don't think I know enough about compiling my own, for the I717. Guess out of luck with that then?
[Android Software Development] danarama:
Are there no developers for i717? Theres no development forum for that device?
[Android Software Development] buggerritt:
Thank you for doing this for so long. It's the only recovery I've been relying on for some time. I am interested in learning to compile it for galaxy s4 l337. Not sure if I have enough know how to not make it a huge bother for you though. I'm no coder.

On the grid via GoldenEye+Domination +Wanam Xposed enhanced l337 on AT&T's 4G LTE network.

Wurrrrrrrrd!
[Android Software Development] eak1080:
Compiled 6.41.5 with libtouch 1.21

[MENTION=4666971]Phil3759[/MENTION]

View attachment philz_touch_6.41.5-hammerhead.zip

Link in OP downloads if you want.
[Android Software Development] danarama:
Please don't post these builds in my Nexus 5 thread. If you're trying to take over my official thread, please ask instead of trying undermine my update schedule. I have my reasons for not updating the official thread / version.

Feel free to compile away but I don't appreciate you trying to take over like this. This compile doesnt meet the conditions we need for it to be usable. It has glitches,.
[Android Software Development] yuweng:
its b'cos you're not using fstab v2 try hunting it here & here & cross-check it with your device. Typically you'll need below build flags when building for legacy devices . . .

[COLOR="Blue"]#Common PhilZ Touch build flags for legacy devices[/COLOR]
TARGET_COMMON_NAME := HTC BRAVO [COLOR="Blue"]<- Change accordingly to your device name[/COLOR]
BOARD_RECOVERY_USE_BBTAR := true [COLOR="blue"]<- Most legacy device doesn't boot without this flag[/COLOR]
BOARD_USE_NTFS_3G := false [COLOR="blue"]<- Most legacy device doesn't boot without this flag[/COLOR]
TARGET_SCREEN_HEIGHT := 800
TARGET_SCREEN_WIDTH := 480
BOARD_HAS_LOW_RESOLUTION := true
BRIGHTNESS_SYS_FILE := "/sys/class/leds/lcd-backlight/brightness"

i already smell something fishy but really never saw this coming . . . :o

Source

And guess i'm the only one here that uses BOARD_RECOVERY_USE_BBTAR . . . :o

bootable/recovery/nandroid.c:1097:13: error: expected ';' before 'ui_print'

And i've added support thread here for MediaTek devices & Thank you so much again for the regular updates . . .
[Android Software Development] Phil3759:
Will fix compile error

Thank you
[Android Software Development] ekoee:
deleted: i'm an idiot.

my bad, going to my device thread.
[Android Software Development] danarama:
Please post in your device thread. This is the development thread, not a user support thread. each device has it's own dedicated thread for user support.
[Android Software Development] GreySephiroth:
Wow , thanks for the info, will try this tonight. But, a question here, if I'm not building for a legacy device, but a new one, would I have to add/edit something else somewhere ? I'm trying to build advanced touch recovery for HTC Desire 200 (codename gtou). I appreciate your help, so here's a big Thank you!

Edit: I mean somethings else besides the fstab and adding the flags mentioned above
[Android Software Development] yuweng:
AFAIK, mkvendor.sh is good enough to build a working recovery for mostly any android devices, refer to here <- look at Method 1: Use mkvendor.sh to generate skeleton files

AFAIK, for building PhilZ Touch, if your device doesn't support it & you didn't specify it at the BoardConfig.mk then it simply won't boot . . . :cowboy:

Refer to here & here . . . :cool:
[Android Software Development] shoey63:
It's been a wild ride Phil:D

I was there at the beginning, and I'm still here ;)

Many thanks for all the hard work you have put in. You have fulfilled my dream of a perfect, safe CWM touch recovery, ever since I bricked my Note1 with dodgy CWM.zip touch recovery 5.8.15.

I look forward to following this, and any other projects you may start in the future.

Thanks again:good:

Edit: remember this from September 2012?

http://xdaforums.com/showpost.php?p=32044901&postcount=154

Things have come a long way since then.....
[Android Software Development] gr8nole:
[MENTION=4666971]Phil3759[/MENTION]

Version 6.41.6 for the Galaxy Tab 3 T210 (lt02wifi) and T211 (lt023g) for addition to goo.im.

Thanks.
[Android Software Development] Phil3759:
uploading :good:

If you can provide md5 sum for the zip installer, it would be great too

cd path/where/zip/file
md5sum philz_touch_6.26.1-lt023g.zip > philz_touch_6.26.1-lt023g.zip.md5
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] should i attach Tab 2 Recoveries here for you also to upload to goo?

You know i have my own recovery thread (because i compile different recoverys for my devices), but i can "move" my PhilZ Recoveries in future to your Tab 2 Threads if you like.

And any idea about my issue posted yeserday
[Android Software Development] gr8nole:
md5s

lt02wifi.zip - 2617b63fe31d90764897f96d7115d005

lt023g.zip - 8eb3be1781c0fdf52bb2897e3aea7eea
[Android Software Development] Phil3759:
It is up to you, really. Do what is best for you.

However, if you post here a link to your files (not every update, but what you think is significant), it would be nice so that I can upload to goo server
[Android Software Development] Saalschlacht:
Hi Phil, i like your special recovery very and used it only on my old GT-I9300. But now i have a GT-I9295 and didn't find your greatful work for this phone.

Is there someone who tried to use another version on this model or will you support by time my GT-I9295?

Gesendet von meinem aktiven GT-I9295... ;)
[Android Software Development] Phil3759:
fstab: you really shouldn't define partitions twice. This a source of conflicts

Follow fstab v2 rules and format the file as you see in all other cm-11.0 devices and my trees

Once you fix that, if it doesn't work, could be your bootloader needs special commands sent to some PARAM partitions we see on many new devices

For that, you have to look into boot/recovery stock ramdisks mainly at their init and shell files
[Android Software Development] unibombz:
What would I need, or perhaps you need to have your current release supported for the I717 (Samsung Galaxy Note 1) ?

Regardless thank you for the recovery that I have used on various other models. It is fantastic and my favorite recovery by far ! Much appreciate all the efforts! Sad to see it going, hope the future brings something fantastic as well from the team!
[Android Software Development] hypnz:
Phil thank for your hard work and your efforts!!
[Android Software Development] Phil3759:
6.41.6 (12.05.2014)

Some 68 devices are getting a direct update from me in the next days:

The below devices already have up to date versions by official maintainers
[Android Software Development] ali.filth:
[MENTION=4666971]Phil3759[/MENTION]

thank you for your hard work and your efforts..This is the best recovery ever, complete and very beautiful..and from this, I started learning android development..salute to you..you are the best Recognize Developer.

Send from my Pager using xda-developers app
[Android Software Development] tetakpatak:
I totally agree, PhilZ is the caviar- best recovery ever made.

I also really like TWRP but PhilZ is simply perfect.

tetakpatalked from Nexus 7 flo