yashsingh1/xdaforums huggingface dataset:
[Android Software Development] ali.filth:
ok..i'll try to change the value, thank's for your quick response.

and about batteries not show the actual percentage on htc sensation? what makes it not work?

please upload arubaslim and delos3geur latest update.

thanks a lot
[Android Software Development] gnarg:
Hi Philz...

My latest recovery for klte do not mount my 128 gb sdcard, isn't recovery supporting 128 gigs?
[Android Software Development] andrew.mackew:
@op

Hi PhilZ: first off thank you for all your hard work.

I wonder if the last update has any impact on t0lte. In this case, should we wait for an update anytime soon? Thanks
[Android Software Development] Phil3759:
some devices need a custom path 'BATTERY_LEVEL_PATH '

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

Try to search under /sys/class/power_supply for the file called capacity
[Android Software Development] matrixzone:
Just eagerly waiting for d2lte update 6.27
[Android Software Development] Rohan Taneja:
Will this work on Xolo Q1100?

Specs:

-MSM8228, upgraded hardware as of Moto G's hardware

-1280*720 resolution

I've already compiled one CWM 6.0.3.6 for my device.

Here's the Stock Recovery: http://d-h.st/9Zq

If you can make, please do it sir!
[Android Software Development] Pons:
If you can compile CWM for this device, compiling PhilZ shouldn't be too much of a stretch. Read the first couple of posts in this thread, and that should point you in the right direction so you can do it yourself, instead of relying on Phil who might not even have your device. Teach a man to fish...
[Android Software Development] smsmasters:
Is there any port for the XOLO Q1000? http://www.gsmarena.com/xolo_q1000-5533.php

It's a Mediatek MT6589 device.

Cheers!
[Android Software Development] ali.filth:
confirmed, there has been a mistake in making the Odin flashable files, please upload them back to your download website.

LINK : arubaslim

LINK: delos3geur

I'm really sorry for this. Thank you very much
[Android Software Development] Phil3759:
New: HTC One M8 Verizon (m8vzw)

http://xdaforums.com/showthread.php?t=2725348
[Android Software Development] yuweng:
Master Shifu [MENTION=4666971]Phil3759[/MENTION] i've just tried out, out of curiosity, CWM boots up on my old armv6 MT6573 on cm-11.0 source & Philz Touch does too with adb but blank screen . . . :o

i use armv6 bionic on cm11 source . . .

Manual edit ~/cm11/.repo/manifests/[COLOR="blue"]default.xml[/COLOR] & change the line <project path="bionic" name="CyanogenMod/android_bionic" groups="pdk" /> to
[COLOR="blue"]<project path="bionic" name="androidarmv6/android_bionic" revision="cm-11.0" />[/COLOR]

BoardConfig.mk that i use . . .

USE_CAMERA_STUB := true

# inherit from the proprietary version
-include vendor/CSL/Mi357/BoardConfigVendor.mk

TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := MT6573

TARGET_CPU_ABI := armeabi-v6l
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv6-vfp
TARGET_CPU_VARIANT := arm11

TARGET_BOOTLOADER_BOARD_NAME := Mi357

BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x10000000
BOARD_KERNEL_PAGESIZE := 2048

# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072

TARGET_PREBUILT_KERNEL := device/CSL/Mi357/kernel

BOARD_HAS_NO_SELECT_BUTTON := true

TARGET_USE_CUSTOM_LUN_FILE_PATH := "/sys/devices/platform/usb_mass_storage/lun0/file"

[COLOR="Blue"]#Philz Touch build flags for MTK
TARGET_COMMON_NAME := CSL Mi357
BOARD_USE_MTK_LAYOUT := true
BOARD_MTK_BOOT_LABEL := "/[COLOR="Red"]boot[/COLOR]" [COLOR="Red"]<- Must use this label or it won't backup boot.img . . .[/COLOR]
BOARD_USE_NTFS_3G := false
TARGET_SCREEN_HEIGHT := 480
TARGET_SCREEN_WIDTH := 320
BOARD_HAS_LOW_RESOLUTION := true
BRIGHTNESS_SYS_FILE := "/sys/class/leds/lcd-backlight/brightness"[/COLOR]

recovery.fstab that i use . . .

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

boot /boot mtd defaults defaults
recovery /recovery mtd defaults defaults
cache /cache yaffs2 nosuid,nodev,barrier=1 wait,check
userdata /data yaffs2 nosuid,nodev,noauto_da_alloc,barrier=1 wait,check
system /system yaffs2 ro,barrier=1 wait,check
/dev/block/mmcblk0p1 /external_sd vfat defaults lun=/sys/devices/platform/usb_mass_storage/lun0/file

Refer to update here & here . . .
[Android Software Development] Phil3759:
Provide full step by step to sync an armv6 full repo. I will try to find sometime to build libtouch_gui for it once
[Android Software Development] yuweng:
Thank you so much for looking into this, Master Shifu Phil3759, its just out of curiosity as i've pm to Bhargav97 earlier about this too . . . :o

repo init -u git://github.com/androidarmv6/android.git -b cm-11.0 <- Source
[Android Software Development] Phil3759:
will look at it

But please, STOP calling me Master Shifu
[Android Software Development] yuweng:
But you are a Master Shifu . . . :laugh:

Noted . . . :o
[Android Software Development] shoey63:
Best not to modify default.xml, otherwise future repo syncs will fail. A better way is to create an xml file in <build directory >/.repo/local_manifests and delete projects, then add the replacements in there.
[Android Software Development] Phil3759:
sure

But now I see he edited his post

Seems there is a dedicated full git for that: https://github.com/androidarmv6

Will just repo sync, pick up one random device and just compile libtouch so that they can use it

The idea is far from restricting developers because of the closed source
[Android Software Development] shoey63:
Yes, I think I will do that. 1.5 seconds of intense vibration is a little bit too aggressive for mine. I might halve it.

Thanks for the tip:good:
[Android Software Development] Phil3759:
do you know how to increase intensity? I mean /sys/dev... file to echo to?
[Android Software Development] shoey63:
Is it here? Or do I have to search in the many files contained in /sys/dev on the device itself?
[Android Software Development] Phil3759:
looks good

try to echo something higher there

echo [value] >/sys/class/timed_output/vibrator/level

not sure about [value] range,

then echo your timer to vibrate it

echo 1000 >/sys/class/timed_output/vibrator/enable

doc:

http://wongchiachen.blogspot.ch/2011/11/vibrator-function-support-in-android.html
[Android Software Development] aidasaidas75:
http://xdaforums.com/showthread.php?t=2716440
[Android Software Development] shoey63:
There is no /sys/class/timed_output/vibrator/"level" file to set a value to, so vibration always occurs with the same intensity, but

echo 50 >/sys/class/timed_output/vibrator/enable

would be a good value to set for each touch action.

TWRP does it this way it seems, but not sure if it can be adapted.

Edit: Why not just increase vibrator time in your sources? Longer time = greater intensity. Is there a file I can edit?
[Android Software Development] drive2droad:
Are there any plans to release an update to 6.0.4.8 based recovery for maguro , we seem to be stuck on 6.0.4.7 !! thanks anyways [MENTION=4666971]Phil3759[/MENTION] .
[Android Software Development] matrixzone:
Same with d2lte
[Android Software Development] danarama:
Please don't ask for ETA / update "plans"
[Android Software Development] Chromium:
Im trying to compile for the HTC Desire (bravo). Cloned the latest sources and added the following to BoardConfig.mk :

#HTC Desire - bravo
else ifeq ($(TARGET_PRODUCT), cm_bravo)
TARGET_COMMON_NAME := HTC Desire
TARGET_SCREEN_HEIGHT := 800
TARGET_SCREEN_WIDTH := 480
BOARD_HAS_LOW_RESOLUTION := true
BRIGHTNESS_SYS_FILE := "/sys/class/leds/lcd-backlight/brightness"

But Im getting this build error:

bootable/recovery/nandroid.c: In function 'restorecon_recursive':
bootable/recovery/nandroid.c:1482:5: error: too many arguments to function 'selinux_android_restorecon'
In file included from bootable/recovery/nandroid.c:50:0:
/home/priyesh/bs/out/target/product/bravo/obj/include/selinux/android.h:33:12: note: declared here
make: *** [/home/priyesh/bs/out/target/product/bravo/obj/EXECUTABLES/recovery_intermediates/nandroid.o] Error 1

I previously tried building CWM as instructed by the guide, and that was successful. Thanks in advance.
[Android Software Development] jtash01:
GUI font size option?

Is there an option to make the GUI font size larger?
[Android Software Development] Phil3759:
you did not repo sync or clobber since 3 to 4 weeks probably ;)

make clobber
repo sync

# now build for your device

The flag is BOARD_USE_CUSTOM_RECOVERY_FONT

example:

BOARD_USE_CUSTOM_RECOVERY_FONT := \"roboto_23x41.h\"
[Android Software Development] Phil3759:
[MENTION=4478781]yuweng[/MENTION] [MENTION=5165022]Bhargav97[/MENTION]

I uploaded needed commits to be able to build for arm v6

It should be fine now
[Android Software Development] Chromium:
Thanks for the reply. I did a make clobber prior to building, but like you said I havent done a repo sync in a while. Im actually trying to avoid doing a repo sync since my sources are kind of a mess at the moment and doing one will probably break everything. Do you know which specific repos need updating? That way I can cherry-pick the individual commits? Thanks again.
[Android Software Development] Phil3759:
Update 6.27.6

6.27.2 --> 6.27.6

And, my first arm v6 board:

LG Optimus One P500 (p500)
[Android Software Development] Phil3759:
https://github.com/CyanogenMod/andr...mmit/1b478eadff95edfe79bdc1211bdb8bb9cdd394d2
[Android Software Development] ali.filth:
Damn..Why you don't tell me about this in my previous question Phil? :D

Send from my Pager using xda-developers app
[Android Software Development] Phil3759:
But i said you need clobber and sync

You did not ask about exact commit LoL
[Android Software Development] yuweng:
You have my deepest respect for you, we Chinese called it the Kowtow . . . :laugh:
[Android Software Development] Phil3759:
Great, it works on first run :D

I asked once for armv6 instructions and I was given some "chinese" steps

Your instructions were rather clear, a simple repo init followed by repo sync

I am keeping it cloned to be able to update libtouch_gui for armv6 when needed. It takes just 7Gb at the end, not a crazy 50 Gb
[Android Software Development] Chromium:
Thanks, that put me in the right direction. I tried cherry-picking that but it resulted in some other errors. So I decided to revert this commit, and that did the trick. Hopefully it doesnt cause any issues :)

I have this problem now that every time I touch a menu, it moves down 2 selections.

ie: I click the down button: It goes down once, plus an extra two times.

I click the up button: It goes up once, then goes back down twice.

This only happens when I use the touchscreen. Navigating using the hardware buttons is working fine.
[Android Software Development] Phil3759:
The way you fix compile errors, makes debugging things a bit outrageous :D

I'd say, save your changes/edits in a separate branch

make clobber and repo sync

try to merge to your custom branch and eventually fix conflicts

After that, we can see if your issues are still there and try to fix them
[Android Software Development] Chromium:
Haha, truer words have never been spoken.

Thanks, Ill give it a try when I have some time. I appreciate your helpfulness :)
[Android Software Development] yuweng:
What ! 50GB, that would be the combination of froyo, gb, jb, cm10.1, cm10.2, cm11 in total . . . :eek:

Luckily you are not taken for a ride . . .

Small talk aside, Updates . . . :o

On my MT6573, i found out that i have to use this flag BOARD_MTK_BOOT_LABEL := "/boot" then only it'll backup the boot.img, attach is the log . . .

Credits to suhas.holla he has tested & confirmed that the mount USB storage is working perfectly on his MT6589 with the init.usb.rc . . .

i guess i have not much hope in getting it to work on my old MT6577 then . . . :fingers-crossed:

Once again, Thank you so much for your work in supporting MTK devices . . . :good:
[Android Software Development] Phil3759:
It is explained in boardconfig.mk

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

# - BOARD_USE_MTK_LAYOUT := true
# will enable backup/restore of boot, recovery and uboot partitions on MTK devices
# - BOARD_MTK_BOOT_LABEL := "/bootimg"
# This flag is optional, it is used only if BOARD_USE_MTK_LAYOUT is defined
# If not defined while previous flag is enabled, default boot label is assumed "/bootimg"
# Else, it is assigned the defined value
# In fstab.device used by recovery (recovery.fstab), boot mount point must be the same as what we
# define in label
# It is also mandatory that it is defined to real device label (cat /proc/dumchar_info)
# Partition size is grabbed during backup/restore from /proc/dumchar_info
# uboot label is defined as "/uboot". It is automatically backed-up/restored with boot and recovery
# recovery label is assumed to be "/recovery"

This is the most important part:

Both conditions must be matched

By default, it is "bootimg"

To see if your your MTK chip uses another name such as "boot", use this command:

cat /proc/dumchar_info

If it is not named "bootimg", you must define the BOARD_MTK_BOOT_LABEL to match what your chip needs

recovery.fstab must also have the same entry as mount point
[Android Software Development] yuweng:
Thank you so much again for the detail explanation, i really appreciate it . . . :highfive:

A little OT, do you plan to add ubifs support as they are quite a few of android devices that uses them nowadays & it is suppose to be the fs of the future, idk . . . :o

Source (1) (2) (3)
[Android Software Development] hachamacha:
[MENTION=4666971]Phil3759[/MENTION]

msm8960 thread up to date. Cheers.

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

I must have forgotten I'd done this other one for the unified msm8960-dt (moto's / maxx / ultra / etc). I've never had one of them so it's untested. Since you've already done your thing for the moto's, is there any interest in the unified build (if I get it tested)? It's based off the kk/cm11/msm8960dt.. There is no thread yet pending your thoughts.
[Android Software Development] sonulohani:
Thanks philz... This recovery rocks
[Android Software Development] john291:
Hello there i need to get my Phone back to stock this evening,but i cant seem to get it to work..

I keep getting this message:

What do i do wrong?
[Android Software Development] Chromium:
Looks to me like it worked fine. The message about sd-ext is just saying that your phone/sdcard does not have an ext partition so its skipping restoring to it.
[Android Software Development] john291:
It doesnt work because my Phone just boots again my custom rom(insertcoin):(
[Android Software Development] aoaleman:
Did you perhaps do a custom/advanced restore?
[Android Software Development] john291:
i tried three times:(

its always going back to my custom rom
[Android Software Development] aoaleman:
This time try "Restore from /sdcard". Not "Custom Restore..."
[Android Software Development] Phil3759:
because you are restoring your custom rom
[Android Software Development] aoaleman:
Or that, I guess he didn't backup the stock ROM...
[Android Software Development] john291:
I tried everytime restore from sdcard:(

---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------

I didnt back up my stock rom,

But my cid was htc__ E11

EN: version main: 1.54.401.5

So i downloaded:1.12.401 E11 nand en de 1.12.401 stock recovery
[Android Software Development] Phil3759:
you are amazing

you got 3 answers, so no need to hammer, just start thinking
[Android Software Development] john291:
Everything worked now,

But now my bootloader says relocked instead of locked?

Is there a way to get it locked for my htc warranty?
[Android Software Development] danarama:
That's nothing to do with this recovery. Please post in your device forum.
[Android Software Development] Phil3759:
Please let him talk

I never laughed so much

You know, I am rarely rude, but this would merit a world tweet

[MENTION=2353158]john291[/MENTION]

No bad feelings, please. Just read answers you got and your posts. If you do not start laughing right away, I'd be really concerned about your current health
[Android Software Development] tetakpatak:
LOOOOOL :D

tetakpatalked from Nexus 7
[Android Software Development] yuweng:
At my thread, i have have this & it really stops . . .

No offence though . . . :o

Notice to annoying n00bs & newbies

Most of your questions are already answered on this thread so pls read it...
[Android Software Development] Bhargav97:
I'll report back soon.

Thanks a lot!

So, did you make any changes in libtouch for armv6 support?
[Android Software Development] meskes:
I'm unsure of where to post this question for a few reasons; I doubt it's device specific, I doubt it's it's a bug and finally, this more to do with morbid curiosity and hoping that maybe it'll give me a little more architecture insight. Anyhow, I updated to the latest Recovery version, (thanks for the update, Phil) and I noticed that the recovery "broke" root, which it promptly offered to fix. My question is why would a recovery update break root in the ROM? Aren't the two separated, and more or less only share the kernel image? Thanks in advance for your guidance and input.

M
[Android Software Development] danarama:
The recovery doesn't break root. It detects missing root. which can also be a bad implementation of root. Maybe you updated to a version where root detection works differently and it identified a bad implementation that always existed but remained previously unidentified

Recovery and kernel are not shared on the S3. The recovery has its own kernel.
[Android Software Development] meskes:
I do run CM11 Nightlies, so a "bad" implementation is entirely possible... I just thought it odd that it'd say something like that with this particular ROM, is all. Like I said, it seemed to have fixed it, so I'm not too worried. Besides, it's not like I couldn't have just reflashed the ROM anyway, if there was some lingering artifacts. Also, thank you for the clarification as to my share kernel portion of the question.
[Android Software Development] R00S:
Dump from Galaxy note 10.2 2014 edition 600 with wifi only. https://www.dropbox.com/s/zr2tlhlz8kyz645/mobileodin.txt

---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------

Dump from galaxy note 10.2 2014 edition, 600 version with wifi only https://www.dropbox.com/s/zr2tlhlz8kyz645/mobileodin.txt
[Android Software Development] shoey63:
[MENTION=4482179]meskes[/MENTION]

Philz recovery has the latest SU binary. CM11 uses Koush superuser, not SuperSu, so you will always get that notification.
[Android Software Development] Pons:
Chances are his recovery isn't all the way updated. CM has a symlink for su that PhilZ was reporting as broken. That's been fixed recently, but I don't recall the version off the top of my head. Should be fixed if he updates his recovery.
[Android Software Development] Phil3759:
Exactly

It is a bug introduced in 6.26.4 and fixed in 6.26.9:

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

Anything start from 6.26.4 and before 6.26.9 will detect cm builds as having broken root
[Android Software Development] KopiJahe:
Can you add mtk's nvram partition backup support? It's like EFS partition, consist with two part: /dev/nvram (dd) and /data/nvram (tar)

I've successfully ported this recovery to my phone (big thanks to [MENTION=4478781]yuweng[/MENTION]), but my main concern is that user can wipe nvram, but not backup it.

Thanks
[Android Software Development] Phil3759:
example to fix this in your device tree, device.mk

#hide partitions from format/mount: (device.mk)
#system.prop
# CWMR Options
ro.cwm.forbid_format=/devlog,/reserve
ro.cwm.forbid_mount=/devlog,/reserve
[Android Software Development] KopiJahe:
I've added this lines to my device.mk:

#hide partitions from format/mount: (device.mk)
#system.prop
# CWMR Options
ro.cwm.forbid_format=/nvram,/secro,/logo,/ebr1
ro.cwm.forbid_mount=/nvram,/secro,/logo,/ebr1

but those partitions is still there

also, how can I add those partitions to backup list?

Thanks
[Android Software Development] hachamacha:
Here's one way: (there are others)

I'm not sure what your intent is above ^^ but it looks perhaps backwards logic from what you want. You want to be able to format or mount, you remove the entry from that list if it's there, not put it there. Other files that might need changing (see these three):

./device/{brand}/{devname}/device_{devname}.mk // the file above.
./device/{brand}/{devname}/rootdir/etc/fstab.qcom // won't see fs' unless you modify/add/del from this. I added some partitions in here.
./device/{brand}/{common}/sepolicy/file_contexts // setup sepolicy for what you added in here (or do a find ./{cm11} -iname 'file_contexts' if not there.

caution: once you start playing with those, a 'repo sync' could fail or put them back to repo state so either save/branch/whatever.
[Android Software Development] KopiJahe:
Here's what I meant before, on MTK devices, nvram partition is like EFS partition on samsung devices, it stores IMEI, MAC Address and other things like baseband config. I want user to be able to backup and restore this partition. There's also some other partition as below:

/dev/sec_ro [COLOR="Blue"]<-- this somehow related to nvram, IMEI 2 is usually become invalid / 00000 is this partition is empty or corrupted[/COLOR]
/dev/ebr1 [COLOR="Blue"]<- holds information about partitions sizes[/COLOR]
/dev/ebr2 [COLOR="Blue"]<- same as above (didn't present on mtk-based devices which uses "datamedia" layout[/COLOR]
/dev/logo [COLOR="Blue"]<- stores boot splash logo (like sony devices logo.rle file)[/COLOR]

I want user to be able to backup & restore those partitions as well, but not wipe/format it

Can this achieved with PhilZ recovery?
[Android Software Development] Phil3759:
I never thought you'll do it that way!

Take time to read through make files how to...

device.mk:

PRODUCT_PROPERTY_OVERRIDES += \
ro.cwm.forbid_format="/devlog,/reserve" \
ro.cwm.forbid_mount="/devlog,/reserve"

you can also add the simpler lines to system.prop in device tree: (no quotes or back slash!!)

ro.cwm.forbid_format=/devlog,/reserve
ro.cwm.forbid_mount=/devlog,/reserve
[Android Software Development] KopiJahe:
I'm sorry for that.

Will try and report ASAP

--edit

Added this lines to system.prop

ro.cwm.forbid_format=/bootimg,/nvram,/sec_ro,/logo,/ebr1,/uboot
ro.cwm.forbid_mount=/bootimg,/nvram,/sec_ro,/logo,/ebr1,/uboot

It works!

Now, can I add them to backup list?

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

Thanks a lot for committing changes for armv6 support. They're working! :good:

Time for some new devices: ;)

Samsung Galaxy Mini (tass)

Samsung Galaxy Gio (gio)

Samsung Galaxy Fit (beni)

Samsung Galaxy Ace (cooper)

Samsung Galaxy 5 (galaxy5)

Samsung Galaxy 551 (callisto)

I and [MENTION=4141775]chraso[/MENTION] will maintain these devices in future. You can add these to OP. And also add to goo.im (if you want to).
[Android Software Development] DrunkUncas:
Just wanted to say thanks.

This has been flawless for months, through dozens (hundreds?) of flashes.

So much better than the alternatives.
[Android Software Development] Phil3759:
6.29.2 (26.04.2014)

This version is a huge change at the backup/restore range

I added native selinux context backup/restore inside tar

This will bring solid TWRP backup/restore compatibility with selinux context

However, there is a huge probability it breaks compatibility with stock CWM backups

I personally do not care as this is how backup/restore should be

If it ends up to be an issue, it could be I add a toggle to enable/disable in archive selinux context

It should be fully compatible with old CWM backups
[Android Software Development] Phil3759:
edited above post:

New version should be fully compatible with old CWM backups