yashsingh1/xdaforums huggingface dataset:
[Android Software Development] yuweng:
AFAIK, latest MTK devices with 4.2.1/ 4.2.2 uses /data/media format while below that uses /emmc is the real internal sd & mmcblk1p1 is the external (micro sd card)

For my device, at the app drawer -> Settings -> Storage it actually have Internal Storage about 762Mb which is not accessible, Phone Storage about 2GB (emmc) & the SD Card (mmcblk1p1) which is the external micro sd...

For latest device with /data/media i guess we'll have to get their input to confirm it... :D
[Android Software Development] Phil3759:
can you try:

/dev/bootimg /bootimg emmc defaults defaults
/dev/recovery /recovery emmc defaults defaults
/emmc@android /system ext4 ro,noatime wait
/emmc@cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/emmc@usrdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
/emmc@fat /sdcard vfat defaults defaults
/dev/block/mmcblk1p1 /external_sd vfat defaults defaults
[Android Software Development] yuweng:
it says mount: mounting /emmc@fat on /sdcard failed: Too many symbolic links encountered

v6.26.7 display the correct size for boot it doesn't finish & i have to force-reboot it...
[Android Software Development] Phil3759:
does this command return something on your device?

cat /proc/emmc
[Android Software Development] Phil3759:
I tried to follow the code to see where it will bring us

The only potential failure I see is here:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/flashutils/flashutils.c#L19

int device_flash_type()
{
if (the_flash_type == UNKNOWN) {
if (access(BOARD_BML_BOOT, F_OK) == 0) {
the_flash_type = BML;
} else if (access("/proc/emmc", F_OK) == 0) {
the_flash_type = MMC;
} else if (access("/proc/mtd", F_OK) == 0) {
the_flash_type = MTD;
} else {
the_flash_type = UNSUPPORTED;
}
}
return the_flash_type;
}

If you do not have a "/proc/emmc" node or if YOU HAVE a "/dev/block/bml7" node, it will probably drop to bml or mtd

I only patched emmc code, so dropping to anything else will fail

Try to do

cat /dev/block/bml7
cat /proc/emmc
cat /proc/mtd

give me what it finds for each command line
[Android Software Development] yuweng:
Thank you so much again my Master Shifu for your fast response... :laugh:

root@android:/ # [COLOR="blue"]cat /dev/block/bml7[/COLOR]
cat /dev/block/bml7
[COLOR="blue"]/dev/block/bml7: No such file or directory[/COLOR]
1|root@android:/ # [COLOR="blue"]cat /proc/emmc[/COLOR]
cat /proc/emmc
[COLOR="blue"]partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0000ac40 00000800 "sec_ro"
emmc_p3: 00010740 000c7800 "android"
emmc_p4: 000d8740 000c7800 "cache"
emmc_p5: 001a0740 001a1000 "usrdata"
emmc_p6: 00341f40 003f99c0 "fat"[/COLOR]
root@android:/ # [COLOR="blue"]cat /proc/mtd[/COLOR]
cat /proc/mtd
[COLOR="blue"]dev: size erasesize name[/COLOR]
root@android:/ # [COLOR="blue"]cat /proc/dumchar_info[/COLOR]
cat /proc/dumchar_info
[COLOR="blue"]Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000004000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000008000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000408000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000908000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000928000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000000988000 2 /dev/block/mmcblk0
recovery 0x0000000000b00000 0x0000000000f88000 2 /dev/block/mmcblk0
sec_ro 0x0000000000100000 0x0000000001a88000 2 /dev/block/mmcblk0p2
misc 0x0000000000060000 0x0000000001b88000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001be8000 2 /dev/block/mmcblk0
expdb 0x0000000000200000 0x0000000001ee8000 2 /dev/block/mmcblk0
android 0x0000000019000000 0x00000000020e8000 2 /dev/block/mmcblk0p3
cache 0x0000000019000000 0x000000001b0e8000 2 /dev/block/mmcblk0p4
usrdata 0x0000000034300000 0x00000000340e8000 2 /dev/block/mmcblk0p5
fat 0x000000007f338000 0x00000000683e8000 2 /dev/block/mmcblk0p6
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate[/COLOR]
root@android:/ #
[Android Software Development] Phil3759:
I found the bug on my side

Will fix it asap
[Android Software Development] Phil3759:
6.26.8

- MTK support: derp

Can you test the new source update

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/5fb840ef6d206bcc0c9a156ea37cdecbcbb0de97

Please, define these 2 macros in boardconfig

BOARD_USE_MTK_LAYOUT := true
BOARD_MTK_BOOT_LABEL := "/bootimg"

If it fails, could be i am missing the cflags in flashutils/Android.mk and mmcutils/Android.mk
[Android Software Development] juicio90:
Hey bro!! Have new little trouble: aroma file manager don't work anymore with the lasted version... tried to downgrade to 6.25 and had black screen. Flashed again into fotakernel 6.26 and tried aroma... Any idea?

Edit: mmmm... I think the pimped kernel cause it a problem.. And tried restore boot.img it's working fine again. :what:
[Android Software Development] tiny4579:
[MENTION=4666971]Phil3759[/MENTION]

I saw there was updated root detection. I flashed CM and it asked if I wanted to flash su. CM uses a symlink in /system/bin to the real su binary in /system/xbin. What do you think about ignoring symlinks to su so it doesn't prompt to install su again?
[Android Software Development] danarama:
Why do they do that? Anyone know?
[Android Software Development] Phil3759:
Yes, seems in deed...
[Android Software Development] Bhargav97:
Something about making it easier to update IIRC...

Infact, it's there because of Busybox. Xbin contains mostly busybox appelets while bin has the commands that are purely used by android.
[Android Software Development] Phil3759:
Big thanks for your generosity. I guess it works with last commit?
[Android Software Development] yuweng:
Its my token of appreciation & Yes, indeed it does & hopefully it is enough to spend my Master Shifu a decent lunch, may be . . . :confused: :o :laugh:

Normal backup, custom backup & restore works perfectly now... :good:

Though i still couldn't get the mount USB storage to work but it does show mass storage when i added the below to init.rc

write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18D1
write /sys/class/android_usb/android0/idProduct D001
write /sys/class/android_usb/android0/functions adb, [COLOR="blue"]mass_storage[/COLOR]
write /sys/class/android_usb/android0/iManufacturer ${ro.product.manufacturer}
write /sys/class/android_usb/android0/iProduct ${ro.product.model}
write /sys/class/android_usb/android0/iSerial ${ro.serialno}

Without it, only adb at Device Manager when plugin...
[Android Software Development] danarama:
This has always been the case though. /bin for standard binaries and commands, /xbin for all root related stuff. Don't see why they need to start symlinking
[Android Software Development] Phil3759:
Mount usb storage: maybe it is impossible or you need a custom lun path flag in BoardConfig.mk

I see your background is mozaique. What is your real screen resolution?

Also, many thanks for your feedback. I was really waiting for someone to help ensuring mtk support is good

Now, we know MTK boards are working
[Android Software Development] tareq_0:
What's the new on v 6.26 ?

أرسلت من GT-I9300 بإستخدام تاباتلك
[Android Software Development] Phil3759:
Maybe it is vold unable to use mtk nodes!

Vold uses virtual nodes, not the real device blk

Many older legacy devices seem broken with mount usb storage

If you have adb shell and you can mount both sdcards in recovery, it is already very good
[Android Software Development] Pons:
I noticed this and threw up a comment on the gift commit. And I'm guessing for better compatibility for poor root apps that use absolute paths.

Check the changelog on the first page.
[Android Software Development] danarama:
Makes sense I suppose. I guess devs should stop giving root app devs excuses and just cut them off ;)
[Android Software Development] Phil3759:
can you look and review this commit

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/7d8aeddbef29bfb1a0e349dd2ce21ac5e1e2b851

It should fix considering cm roms as having broken root and stop replacing Koush SU with Chainfire one (even if I think Chainfire implementation is more compatible with stock ROMs)
[Android Software Development] Pons:
At work right now, but at a casual glance it looks good. I'll have to throw a build together tonight and test.
[Android Software Development] Phil3759:
no hurry

let me know when you can test so that I can roll an update for selected devices

won't update all for sure, just the most used ones
[Android Software Development] yuweng:
Update : 480x854 res is working on my other MTK daily use JB 4.1.1 so it means MTK ics kernel doesn't support res higher than 320x480...

Update1 : Hmm, ics kernel does work after all... :o Found the clone of my old MTK, use its kernel & i got the 480x854 res working though adb & USB mount is not working . . .

Funny though, adb & USB mount is not working on this 4.1.1 but i could get a log out of it, hopefully it'll be usefull...

Update1 : Use init.usb.rc from stock boot.img & got adb working . . . Add init.usb.rc to root of ramdisk folder & add the below to Philz Touch init.rc . . .

import /init.recovery.${ro.hardware}.rc
import /init.usb.rc [COLOR="blue"]<- Add this[/COLOR]

on early-init
start ueventd
start healthd

on init
export PATH /sbin:/system/bin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard

symlink /system/etc /etc
[Android Software Development] Phil3759:
Your fstab log shows this:

6 /emmc vfat /emmc@fat 0
7 /sdcard vfat /dev/block/mmcblk1p1 0
8 /storage/sdcard0 vfat /devices/platform/mtk-sd.0/mmc_host 0
9 /storage/sdcard1 vfat /devices/platform/mtk-sd.1/mmc_host 0

you are mixing vold and non vold devices/mount_points

Try the fstab I proposed you a few posts above:

/dev/bootimg /bootimg emmc defaults defaults
/dev/recovery /recovery emmc defaults defaults
/emmc@android /system ext4 ro,noatime wait
/emmc@cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/emmc@usrdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
/emmc@fat /sdcard vfat defaults defaults
/dev/block/mmcblk1p1 /external_sd vfat defaults defaults

See if at least you have access to external_sd that way

If /sdcard fails, you must find the real emmc block
[Android Software Development] Phil3759:
or maybe replace

/emmc@fat /sdcard vfat defaults defaults

by

/dev/block/mmcblk0p6 /sdcard vfat defaults defaults
[Android Software Development] yuweng:
i have tried all different combinations & it doesn't work, only by using both mount points/ voldmanaged & continue tapping on the mount /sdcard then it'll work afterwards... :laugh:

If the physical mount point taken out then there is no mount /emmc & mount /sdcard shown here so its like Philz Touch operating without internal/ external sdcard. . . :laugh:

Actually i've found inside the Lenovo S939 Kitkat 4.4.2 boot ramdisk here has various *.rc files that mounts the sdcard but it seems nobody is downloading it... One i found may be needed, idk, just hoping more MTK users/ DEV would come forward to help out as my knowledge on this is quite limited... :o Refer to conclusion here . . .

# MTK project .rc configure
#
# NO SHARED_SDCARD feature option
#

on init
# See storage config details at http://source.android.com/tech/storage/
mkdir /mnt/media_rw/sdcard0 0700 media_rw media_rw
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
mkdir /storage/sdcard0 0700 root root
mkdir /storage/sdcard1 0700 root root

export EXTERNAL_STORAGE /storage/sdcard0

# Support legacy paths
symlink /storage/sdcard0 /sdcard
symlink /storage/sdcard0 /mnt/sdcard
symlink /storage/sdcard1 /mnt/sdcard2

service fuse_sdcard0 /system/bin/sdcard -u 1023 -g 1023 -d /mnt/media_rw/sdcard0 /storage/sdcard0
class late_start
disabled

service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1
class late_start
disabled

init.no_ssd.rc
[Android Software Development] pmorales:
Hi Phil, I invite couple of beers in advance, for your final version for Exynos SM-G900H model. Thanks.

Transaction ID: 4X738524UM0025816
[Android Software Development] Phil3759:
Thank you for your generosity

Galaxy S5 - SM-G900H (k3gxx)

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

Please flash and give feedback
[Android Software Development] Phil3759:
6.27.0 (17.04.2014)

New devices support threads

- Galaxy S5 Exynos SM-G900H (k3gxx)

- Amazon Kindle Fire HD 8.9 (jem)

- Amazon Kindle Fire HD 7 (tate)
[Android Software Development] Pons:
Haven't been at the house long enough to compile and test, but I asked someone to compile and test one for his m7. He used your Android build system, and says it compile fine, but it compiles the CM kernel. Took approximately 4 minutes to do a 2gb back up. And it no longer complains about broken root on CM.
[Android Software Development] Phil3759:
Currently zip files over 2gb are not supported
[Android Software Development] shoey63:
Can you adb sideload it?

Edit: That won't work either, unless you have 2.4 GB or more of RAM:p
[Android Software Development] Phil3759:
Using TARGET_PREBUILT_KERNEL is no more properly supported by CM. They are dropping it progressively

Users unused to compiling, should instead use TARGET_PREBUILT_RECOVERY_KERNEL

Actually, when using TARGET_PREBUILT_KERNEL you MUST rename/delete the cm kernel having the same device name

In your case, cm repo has a kernel under

kernel/htc/m7

When compiling android_device_htc_m7 with TARGET_PREBUILT_KERNEL, you need to rename or delete kernel/htc/m7 folder or you end up with issues and errors. Kernel will also be compiled inline, but I am not sure if it will be used, overriding user TARGET_PREBUILT_KERNEL

On the other side, compiling android_device_htc_m7vzw has no issues as you do not have a m7vzw kernel folder

You must be aware of this when using my modified device trees

A workaround would be fixing cm core files to skip any inline kernel check when we have TARGET_PREBUILT_KERNEL

Actually, stock cwm won't even compile when using TARGET_PREBUILT_KERNEL and TARGET_USES_QCOM_BSP flags:

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

CM Team doesn't seem to will fixing this as they are probably dropping support for TARGET_PREBUILT_KERNEL
[Android Software Development] chevanlol360:
Hey philZ where would i go to change a few settings like the menu height, scroll sensitivity etcc from source in your recovery folder? thanks
[Android Software Development] tetakpatak:
PhilZ is name of the recovery.

Phil3759 is its mighty developer's user name.

tetakpatalked from Nexus 7
[Android Software Development] Phil3759:
https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/libtouch_gui/libtouch_gui.a
[Android Software Development] chevanlol360:
ok i got into the libtouch_gui.a file but how do i edit the .o files? thanks
[Android Software Development] Phil3759:
you can't
[Android Software Development] chevanlol360:
....... so then i cant edit those settings at all from source?
[Android Software Development] Phil3759:
If you need to provide users with default settings, bundle your zip installer with a script checking for config file in /data/philz-touch folder

If no settings file is detected, you inject a config file with your recommended settings
[Android Software Development] chevanlol360:
got ya thanks.
[Android Software Development] Phil3759:
6.27.2

[MENTION=2872010]rootSU[/MENTION]

I am sure you will appreciate the prompt to cancel backup/restore ;)
[Android Software Development] hachamacha:
[MENTION=4666971]Phil3759[/MENTION]:

Carrying on from the Moto X thread:

https://github.com/CyanogenMod/android_device_samsung_jflte/blob/cm-11.0/init/init_jflte.c is a good example. Thanks for pointing that out.

Edit:

Both of those ^^ are really good additions.

edit:

Regarding my nutty post over in moto-x land : It was actually me finding this:https://github.com/CyanogenMod/android_device_motorola_moto_msm8960dt/blob/cm-11.0/init/init_moto_msm8960dt.c

It made me think that kk/cm11/msm8960dt already was the unified cm11 for the moto/maxx/ultra/etc. line.
[Android Software Development] lijoc:
Sir Can you port this for Samsung galaxy s4 active. I9295. I have tried many kernels but I feel yours is best but am not able to use it on my device running kitkat.
[Android Software Development] tetakpatak:
Cheers, mate :D PhilZ touch is custom recovery.... (but I totally agree with "best")

tetakpatalked from P5110
[Android Software Development] lijoc:
Sorry I meant recovery only.
[Android Software Development] titanic_fanatic:
[MENTION=4666971]Phil3759[/MENTION] I noticed that raw partition backups are taken using the cat command. Is there a specific reason you've used the cat command vs the dd command? Is it more reliable?
[Android Software Development] Phil3759:
cat provides better exit codes to verify success vs failure

I use them to generate the log
[Android Software Development] shoey63:
alright Phil, what plans do you have for +PHILZ_BUILD := 6.27.3 ?
[Android Software Development] Phil3759:
changes are irrelevant as you can see, that's why I won't update OP to avoid the hammering ;)

I do not plan anything on my todo list for now, rest quiet LoL

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/d692056cc0337e65f62dfb9b526bb87615a1d381
[Android Software Development] shoey63:
Thanks Phil, and Happy Easter :)
[Android Software Development] cyberspaceguy:
Anyone knows if this amazing last version recovery works with miui europe version file zip for i9505 please?
[Android Software Development] Bhargav97:
[MENTION=4666971]Phil3759[/MENTION],

I've been waiting for long time now to see if somebody's making (updating) PhilZ-Touch for Galaxy Grand (GT-I9082) or not (it's stuck on 6.19.2) but I found that nobody is ready to make one. I don't know what makes people say no for making JUST a recovery... :(

I would have made one but unfortunately I deal with androidarmv6 sources and not CM sources. I can't afford to download CM sources now.

So, I'm requesting you to update the I9082 whenever you have some time. No hurries. :)

Sorry to disturb you...

Happy Easter...

Thanks
[Android Software Development] danarama:
I think this is perfect example of people who don't deserve an update ;)

If no one is willing to chip in and help support Philz on their device, why should Phil update it?

I'm not speaking for Phil here. My views have nothing to do with Phil's philosophy at all, but still I think my question is valid
[Android Software Development] shoey63:
Hey Phil, just a quick confirmation that vibrate on"cancel" and "restore backup " is fully functional on Yuga with. 6.27.2. :thumbup:
[Android Software Development] tetakpatak:
In some corners of this world, the internet isn't as well accessible as in some other countries. Maybe don't forget that fact also.... it is not possible to say "it is all just laziness", IMHO

We have for example an awsome young talented developer for the i9000 who could be the perfect PhilZ contributor, but he simply can't sync CM sources for this reason from his country.

tetakpatalked from P5110
[Android Software Development] Phil3759:
Yes, I can release it in a few minutes, but why not all the +140 devices in that case?

I have a life and they got an update a month ago. Their recovery is perfectly functional.

They don't even have an official cm support but a dedicated developer supporting them here:

https://github.com/pawitp/android_device_samsung_i9082

Why do not ask him!

A choice had to be done, I did it. Things are open source and I cannot afford compiling all the time for all devices
[Android Software Development] Phil3759:
you can adjust buzzer time here:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/nandroid_advanced.c#L28

in milliseconds
[Android Software Development] Bhargav97:
[MENTION=2872010]rootSU[/MENTION],

If you would check out the device thread, many people are asking there for an update. AFAIK, last 5-6 posts are just for a request of an update. AND REMEMBER, everyone of them can't compile.

And, the question: Why should Phil update it?

I don't think it's a nice question. It's his recovery so he should be atleast caring to update his recovery for all devices (atleast, which are officially supported) after a certain interval of time atleast. Though the things have changed, libtouch is here, but he should be updating recovery atleast for helpless person like me (and it's not only me, see device-specific thread). Howeverm it's upto Phil that how popular he wants to keep his recovery up, so...

Also, what [MENTION=5051515]tetakpatak[/MENTION] said is a partial case with me. Read my post carefully. I'm already working on 'androidarmv6' sources (they're already 20 GBs). See my signature, I also ported for many devices. So, it's not about laziness, it's about helplessness.

[MENTION=5051515]tetakpatak[/MENTION],

Thanks!

[MENTION=4666971]Phil3759[/MENTION],

I don't think he's interested in recoveries because he didn't even update his cwm (it's on 6.0.4.5 only). And, I don't fully remember but I do ask hime once for PhilZ Recovery but no response (not sure though, I'll have to see). I understand you but you know, I waited too long or an update, really.
[Android Software Development] danarama:
It only needs 1 person to compile. There must be at least 1 dev in that device forum.

See Philz previous response.
[Android Software Development] ali.filth:
Update 6.27.3 arubaslim & delos3geur

update for Samsung Galaxy Core (arubaslim) & Samsung Galaxy Grand Quattro (delos3geur)

arubaslim : LINK

delos3geur : LINK

for LG OPTIMUS L7 I need to fix the problem aromafm inverted, you can give more detailed input, like what I added flag in the boardconfig ? or ? for information, i'm using prebuilt kernel for this device.

and for HTC sensation I need to fix percentage of battery that does not work, can you tell me how to fix it?

thank
[Android Software Development] Bhargav97:
[MENTION=4666971]Phil3759[/MENTION],

Here's an update for GT-I9082 (Galaxy Grand Duos): From the latest branch (most probably 6.27.3)

TAR file (please post this tar also at thread. We need sometimes ODIN to flash recovery so...)

http://goo.im/devs/playfulgod/recoveries/samsung/i9082/philz.tar

IMG file (please make zip and post at device-specific thread):

http://goo.im/devs/playfulgod/recoveries/samsung/i9082/philz.img

All the credits goes to [MENTION=4666971]Phil3759[/MENTION] and [MENTION=2999829]PlayfulGod[/MENTION]. Thanks a lot. I just requested [MENTION=2999829]PlayfulGod[/MENTION] and rest all was done by him. :)
[Android Software Development] Phil3759:
Please do not take it personal

Hope you got my point from IRC

And, no, I do not care about anything except my personal life, the real one, not the xda and github geek part

Previously, there were flags to swap axis

Now, author is using this:

https://github.com/amarullz/AROMA-Filemanager/blob/master/src/libs/input/input_driver.c#L111

I have no idea where that code leads and how do you alter it. Maybe it is now some static values to set to 0/1 instead of defines
[Android Software Development] KopiJahe:
Hi, I've successfully compiled your recovery with yuweng's steps for my MTK device (ZTE N986), but the thing is, the output file is larger than my recovery partition (7.13 MB vs 7 MB), even with TWRP it's only 6.xx MB. Can I somehow reduce the filesize (by disabling certain feature perhaps)?

Thanks
[Android Software Development] Phil3759:
https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/boardconfig/BoardConfig.mk#L46

and this

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/boardconfig/BoardConfig.mk#L48

Basically:

BOARD_USE_NTFS_3G := false
BOARD_HAS_NO_FB2PNG := true