Is it possible to port this for lg p760? This phone is officially support by cyanogenmod and it has a working cwm 6. Thanks
why you dont want to share it if you not going to use for comercial purposes??
not criticism just asking :angel:
why you dont want to share it if you not going to use for comercial purposes??
not criticism just asking :angel:
The most part is open source and you can build for any device
The non shared parts are 2 main things:
- Touch GUI
- Make update.zip from current ROM or from existing nandroid backups
The Rom name, multi-zip... are not shared because they use parts of gui settings. When I have time, I will separate them and make them open source too
Reason: non shared parts will be the payed parts in ROM Manager
It's a stock kernel, why would there be?
sent from my galaxy SII using tapatalk
Not the kernel causing drain, it's your ROM and/or setup.
sent from my galaxy SII using tapatalk
Ok wait. I mentioned this before on the PhilZ thread in the SGS3 i9300 section.
In most devices (such as the SGS3) the kernel and the recovery are separate.
This is a recovery. For those aforementioned devices, flashing this over a custom kernel, will retain that custom kernel. Flashing custom kernels over this recovery will not get back the stock recovery.
In any case, this is a recovery! Not a kernel.
As for battery: the recovery does not affect the battery usage of the ROM.
The kernel might, but for that - you have to find info in your kernel's dev thread, or try using a tool such as BetterBatteryStats to weed out the cause for your battery drain.
Sent from my GT-I9300 using xda app-developers app
Project Status: No Longer Updated
As I mentioned before, I have a lot of new important projects in my real life. I am very happy to abandon this project for real life alternatives.
CWM is a dead project for now, until some dev resurrects it. I was about to do, until these new projects came.
Current version will probably work a while for many devices. Some devices with new ROM installers could have issues. Just use TWRP and avoid the new CM Simple Recovery
If the current version works for you, there is no reason you don't use it though. No need to ***** in all threads because it doesn't work for you. Just move on to other alternatives.
- touch interface:
- toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate, SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keysNote: after scroll, there is a minimal small delay (0.5 sec) to validate on next touch. This is by design and not a bug. It is there to limit erroneous validation while scrolling
- written from scratch full touch code
- basic scroll kinetics for faster scrolling on demand
- safe full touch : no wrongly validations while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
- adjust scroll sensitivity in a huge palette
- adjust menu height in a huge palette
- adjust touch accuracy
- 30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
- user custom background png can be selected in addition to 30 solid colors option
- show / hide background icon
- show / hide bottom virtual buttons
- show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
- set number of bottom log rows to show
- pause on logs mode: no more miss logs during zip installs
- auto dim screen after user configurable delay
- auto turn off screen after user configurable delay
- adjust brightness and turn off screen with a gesture action
- show/hide clock and remaining battery %, even during nandroid operations
- clock and battery stats now effectively refresh every 5 seconds and during nandroid operations
- toggle vibrator on/off on touch
- toggle key repeat for volume up/down scrolling when maintained pressed
- key repeat also enabled for virtual buttons
- set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
- capture recovery screen shots with a gesture action (only some devices)
- basic theme support
- one file to save all settings
- backup and restore settings file
- backup and restore only GUI settings
- reset to default settings option
- prompt to restore your settings from a backup when they are wiped by a new ROM install
- option to auto restore your settings from a backup without a prompt
- all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
- toggle menu options are automatically right aligned and menu text left aligned based on device display size
- configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
- true JB 4.2 migration: toggle between /data/media and /data/media/0
- Secure recovery lock with passkey
- browse phone with root access using full GUI in Aroma File Manager
- terminal access from recovery with root access through Aroma File Manager
- Multi Zip Install menu: check multiple zip files to install in a row
- Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
- exFAT, NTFS and Ext4 support in recovery for external storage through kernel modules for many devices for faster write speed
- TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
- Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
- support .android_secure backup/restore from external storage
- optional reboot after custom backups/restores
- sd-ext support (ext4)
- nandroid backups support /preload in backup and restore jobs (custom and stock modes)
- nandroid backups support /misc in backup and restore jobs (custom mode)
- devs: 5 extra optional partitions supported in nandroid operations by editing recovery.fstab
- set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
- recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
- cancel nandroid operation with back button
- create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
- nandroid backup path auto-renamed with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
- custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
- backup/restore EFS in both tar + img formats, now with time tags for both tar and .img
- support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
- during custom restore, you can see the contents of the folder you want to restore from
- delete custom or TWRP backups from recovery menu
- full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
- full support for openrecovery script specifications include all backup and restore options
- run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
- define ors backup target volume from within Nandroid Settings menu
- ors backup/restore in stock clockworkmod or TWRP modes
- advanced power options menu
- detailed build info in About menu
# Info on some tags:
- KERNEL_EXFAT_MODULE_NAME: This will force minivold to use much faster kernel modules instead of slow fuse
it will only work if you have modified vold sources (contact me for info)
you'll also have to copy modules to ramdisk and load them in init.rc or a loader script
you need either an exfat enabled prebuilt kernel or to compile exfat modules along kernel
you also need to patch minivold: [url]https://github.com/PhilZ-cwm6/android_system_vold[/url]
- KERNEL_NTFS_MODULE_NAME:
Same as above, but for ntfs.
- TARGET_USERIMAGES_USE_F2FS := true
will enable f2fs support and ext4 <-> f2fs conversion and backup migration
obviously you need to add f2fs support into the kernel
read about the extra.fstab use to use specific and distinct f2fs and ext4 mount options
else, it will drop to bare minimal ext4 or f2fs mount options if not defined in recovery.fstab
- 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 always assumed to be "/recovery"
- BOARD_HAS_LOW_RESOLUTION:
(optional) for all devices below 1024x768 resolution.
it forces default touch sensitivity to a lower value. It can be altered in GUI Settings
- BOOTLOADER_CMD_ARG:
This will override ro.bootloader.mode. Mostly used for Samsung devices to access download mode
- TARGET_COMMON_NAME
The device name that will be displayed on recovery start and in About dialogue
- BRIGHTNESS_SYS_FILE:
Needed to be able to alter screen brightness
- ro.cwm.backup_partitions:
this can be set on boot or during compile into default.prop. exp in device.mk:
PRODUCT_PROPERTY_OVERRIDES += \
ro.cwm.backup_partitions=/modemst1,/modemst2,/devlog
it will add support to backup/restore those partitions in nandroid custom jobs provided they are also defined in recovery.fstab
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/rootdir/etc/extra.fstab:recovery/root/etc/extra.fstab
# add here entries already existing in main device fstab, but for which you want a blk_device2, fs_type2 or fs_options2
# mount point must be the same, mmcblk device must be your device true path
# you can set the f2fs mount options for partitions you want to be able to toggle between f2fs/ext4
# it will enable faster transfer speed for devices supporting usb mount storage
# makes it possible to partition vold managed storage (sdcard/usb disks) and format it to ext2/ext3
# used also to stat for size of mtd/yaffs2 partitions
# blk_device2 # mount_point fs_type2 fs_options2 flags (not used in extra.fstab code)
/dev/block/mmcblk0p28 /storage/sdcard0 auto defaults defaults
/dev/block/mmcblk1p1 /storage/sdcard1 auto defaults defaults
/dev/block/sda1 /storage/usbdisk0 auto defaults defaults
/dev/block/mmcblk0p30 /data f2fs [options] [flags]
- Compile for your device by replacing bootable/recovery contents with files from my git
- Set the needed options in bootable/recovery/boardconfig/BoardConfig.mk
- It is very important to set the correct options so that libtouch_gui can be initialized properly
- Optional: you can add your signature here, but do not remove other About ui_prints please, keep credits
https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/advanced_functions.c#L3328- post a link to your thread or attach your recovery.img here and I will upload them to goo.im and main OP for official support
- If you have errors, bugs or need a specific feature for your custom kernel, just let me know by PM
- If errors are related to libtouch_gui, try to disable the PHILZ_TOUCH_RECOVERY flag here by adding a #
https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/Android.mk#L6
Then, post here your error log when compiling