Goodbye Lollipopalooza... Hello Marshmallicious!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This started out as a personal project... a way for me to learn how to develop and custom features for Android. And I decided to share my work with the amazing Android community... something to give back to the community. Back then, this was a ROM called ThunderKat, based on Android 4.4 KitKat. Over time, it evolved into Lollipopalooza, based on Android 5.0. And now, here's Marshmallicious, based on Android 6.0.
Now, before you go on ahead, let me be clear about one thing. This is and will remain a minimal AOSP based ROM. It will include a small, but useful set of features... features which add a bit more flare to Android AOSP. Beyond this minimal feature set, this will also include some relevant spit and polish (bug fixes and asset/image updates). As time progressed, so did the quality of the work behind the features this ROM offers. Whenever I look back at a feature I developed before, I look for ways to improved. If you expect a lot of additional features, I recommend using one of the more popular ROMs available like CyanogenMod, SlimRoms, ParanoidAndroid, etc.
I develop and maintain this ROM on my own for the most case, occasionally seeking help and porting useful features and fixes that others here in the community have developed. You will see all the relevant references in the cherry-picked commit in my GitHub repositories.
Due to my limited availability, I will now no longer support Lollipopalooza builds
Now that I'm done with the fancy introduction, let's get down to business...
Changelog:
2015/11/07
1. Fixed force close when choosing keyboards in Language & input settings
2. Enabled doze/ambient mode auto power saving modes (More details)
3. Removed SVELTE (Nexus 9 LTE) init configs from Nexus 9 Wifi init configs
4. Disabled bug report service (which is triggered by holding down volume down, volume up and power)
5. Updated SELinux policies for experimental systemless root using open source Superuser (instruction below)
6. Fixed experimental systemless root for devices with encrypted userdata
2015/11/04
1. Android Marshmallow 6.0.0_r2 (MRA58N) base [Includes November 2015 security patches by Google]
2. Movable on-screen navigation bar buttons (centre, left or right) [Settings > Device > Display]
3. Cursor control within text boxes using the volume rocker [Settings > Personal > Language & input]
4. Long-press of back button to kill foreground app [Settings > Personal > Language & input]
5. Native Android Marshmallow recents dismiss/clear all
6. User-defined custom device hostname [Settings > Wireless & networks > More]
7. Displays apps installing and optimising storage progress on first boot
8. Uses Google pre-built WebView if it is installed. Falls back to AOSP WebView
9. SystemUI Tuner enabled by default
10. Dessert Cake dream enabled and set as default doze dream
11. Enhanced Location QuickSettings tile (toggles between the different location mode [Off > Sensors Only > Battery Saving > High Accuracy])
12. Long-press action for all QuickSettings tiles (opens relevant Settings section)
13. Enhanced power menu [Power Off, Reboot, Aeroplane Mode, Users & Sound Toggle]
14. Advanced reboot [Reboot, Reboot to recovery, Reboot to bootloader] (only available for primary user when device is unlocked)
15. Default required permissions set for Google applications to allow GoogleApps packs
16. F2FS support for the cache partition in addition to the userdata partition.
17. Additional filesystems supported (with vold auto-mount capabilities not available yet) [exFAT and NTFS (NTFS-3G)]
18. Forced encryption of userdata partition is disabled
19. DM-Verity (key-based partition verification) is disabled system-wide
20. Full-screen on-screen keyboard in landscape mode is disabled
21. Sysinit supported (init.d scripts)
22. @Captain_Throwback's BeyondStock kernel 2.0.0 included [support NTFS, exFAT and fast-charge]
23. Several assets and images updated to Material-styled versions
24. Ambient (Doze) mode enabled along with burn-in protection
25. A lot of unneeded debug logging disabled
26. Default wallpaper replaced with Marshmallow stock default wallpaper and Marshmallow stock bootanimation added
27. Includes bionic busybox (credit CyanogenMod)
28. Increased number of status bar notification icons from 5 to 8
29. Miscellaneous bug-fixes and tweaks included (for more details, check the GitHub commits)
30. Full GoogleApps pack (with ARM64 320DPI apps where applicable) with the latest updates
Instructions:
1. Download the Marshmallicious ROM package and the Prerequisites package
2. [OPTIONAL] Download the GoogleApps package
3. Reboot into recovery [A custom recovery like TWRP is required]
4. Wipe as required
a. Full wipe when coming from another ROM
b. Wipe cache and dalvik-cache when flashing a Marshmallicious update5. Flash the packages in the following order
a. Prerequisites package
b. Marshmallicious ROM package
c. [OPIONAL] GoogleApps package6. Reboot and let the device boot up and remember that the first boot will take a while since this is a de-odex ROM
Root:
I do not support SuperSU because it is closed-source and, hence, cannot be audited. Anything granting low-level privileges to apps and process need to be open-source and auditable. But I will not blankly turn down support requests involving SuperSU if you have chosen to root your ROM using SuperSU.
That said, I am closely following the development of systemless open-source Superuser by @phhusson as well as the SELinux policy changes by @doitright. This is still experimental and may not support all root apps yet.
Because this is currently experimental, this ROM is not pre-rooted. But I have provided a separate ExperimentalRoot package. This package contains a modified boot image with the su binary, init changes and SELinux policy changes and has been built from source. The su binary was built with the latest changes in @phhusson's Superuser GitHub repository. The init and SELinux policy changes are a slightly varied version of the patch created by @doitright. Also included in the zip is the Superuser apk built with the latest changes in @phhusson's Superuser GitHub repository.
I have branches in my GitHub repository which have the SELinux policy and init changes required for systemless Superuser which include all doitright's changes as well as my modifications.
platform_external_sepolicy
platform_system_core
Instructions:
1. Download the ExperimentalRoot package provided above (make sure it matches the ROM release date)
2. Flash the boot image included in the ExperimentalRoot package using fastboot [fastboot flash boot boot.img]
3. Install the Superuser apk included in the ExperimentalRoot package as a regular app
Downloads:
AndroidFileHost
Marshmallicious-Nexus9-Wifi-20151107.zip [Marshmallicious ROM]
GoogleAppsPack-6.x-ARM64-320DPI-20151107.zip [Full Google Apps Pack]
Prerequisites-Marshmallicious-Nexus9-Wifi-MRA58N.zip [Prerequisites (bootloader and vendor images)]
ExperimentalRoot-Marshmallicious-Nexus9-Wifi-20151107.zip [Experimental systemless open-source Superuser]
BasketBuild
Marshmallicious-Nexus9-Wifi-20151107.zip [Marshmallicious ROM]
GoogleAppsPack-6.x-ARM64-320DPI-20151107.zip [Full Google Apps Pack]
Prerequisites-Marshmallicious-Nexus9-Wifi-MRA58N.zip [Prerequisites (bootloader and vendor images)]
ExperimentalRoot-Marshmallicious-Nexus9-Wifi-20151107.zip [Experimental systemless open-source Superuser]
Theming:
This ROM support RRO/Layers themes. But please be aware that not all RRO/Layers themes support Android Marshmallow yet. If you encounter force closes after installing a theme, reboot into recovery mode and delete /vendor/overlay.
Layers/RRO Themes Info:
1. Join the BitSyko Google+ Community for the latest information and themes
2. Download the Layers Manager app to install/uninstall/preview RRO/Layers themes
3. Download the Layers Showcase app to browse available RRO/Layers themes
4. Visit this XDA thread for a comprehensive list of RRO/Layers themes
Help and troubleshooting:
1. Ask for help if you need, but make sure you do your research first.
2. Be patient. It could take a few minutes to flash the ROM.
3. If you flashed a kernel which replaced the SELinux policy file, you may encounter errors and issues. To recover, you will need to reflash the ROM boot image.
4. If you get "failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP", unmount the system partition and try again
5. If you flashed a kernel with SELinux disabled like the one provided by @USBhost on a previous build, make sure you flash that kernel after flashing the update (before you reboot), or you will get a bootloop and will have to perform a recursive restorecon on the /data partition to restore the SELinux contexts.
6. If you have a folder created in TWRP recovery mode which you cannot access when you boot up the ROM, you will need to perform a recursive restorecon on that folder restore the SELinux contexts.
7. Be ready to provide a clear description of your issues and please provide logcats, dmesg logs and kmesg logs whenever possible.
Sources:
Marshmallicious Manifest
All repositories
Disclaimer
Marshmallows are always delicious... but be careful!!! Make sure you know your limits!!! If you don't know what you are doing, the marshmallows provided here could be life-threatening and render your device inedible. Every marshmallow here has undergone extensive scrutiny, but there is always a chance that something slipped through the cracks since baking is more an art than a science. So if you use the marshmallows here, don't hold the chef responsible for baking these goodies (me!)
Support this project:
If you like my work, buy me a beer so that I can pass time while my laptop churns out builds...
Paypal
Google Wallet (Send Money to craigacgomez[at]gmail[dot]com)
Credits:
Google, NVidia, ARM, Chainfire, 0xD34D, CyanogenMod team, PureAOSP team, Chroma team, BitSyko team, AndroidFileHost, BasketBuild, phhusson, doitright, XDA (any probably some more I can't remember)
Reserved...
And one more... just in case!!
Will test and report back
Upload complete at last (AndroidFileHost crapped out on my half way through!) Link in OP!
craigacgomez said:
Upload complete at last (AndroidFileHost crapped out on my half way through!) Link in OP!
Click to expand...
Click to collapse
Can you edit the ROM to not encrypt data
BTW love the Disclaimer!!
USBhost said:
Can you edit the ROM to not encrypt data
Click to expand...
Click to collapse
Definitely planning on doing that next. I will spend some time on this tomorrow...
Awesome, the first rom is out! let the flashing begin!
craigacgomez said:
Definitely planning on doing that next. I will spend some time on this tomorrow...
Click to expand...
Click to collapse
hows its going
found it?
You have a commit that enbales App Opps? Thanks for this. Loved your ROM for my N10.
USBhost said:
hows its going
found it?
Click to expand...
Click to collapse
Found it. It's actually a kernel change... well, a change in the fstab. Changing the forceencrypt mount flag to encryptable makes it encryptable, but with encryption disabled by default.
Change these line in the kernel initrd fstab.flounder & fstab.flounder64
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
to
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
or fstab.flounder in the flounder device tree.
craigacgomez said:
Found it. It's actually a kernel change... well, a change in the fstab. Changing the forceencrypt mount flag to encryptable makes it encryptable, but with encryption disabled by default.
Change these line in the kernel initrd fstab.flounder & fstab.flounder64
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
to
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
or fstab.flounder in the flounder device tree.
Click to expand...
Click to collapse
So i change it
Then do a factory reset
And i should be good?
jarjar124 said:
You have a commit that enbales App Opps? Thanks for this. Loved your ROM for my N10.
Click to expand...
Click to collapse
I could get you a diff.... or wait for a day or so till I start pushing stuff to GitHub.
craigacgomez said:
I could get you a diff.... or wait for a day or so till I start pushing stuff to GitHub.
Click to expand...
Click to collapse
I can wait. Thanks for your hard work!
like this right??
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/VNR /vendor ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/EBT /bootloader emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/PST /persistent emmc defaults defaults
/dev/block/zram0 none swap defaults zramsize=533413200
USBhost said:
So i change it
Then do a factory reset
And i should be good?
Click to expand...
Click to collapse
Yes...
USBhost said:
like this right??
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/VNR /vendor ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/EBT /bootloader emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/PST /persistent emmc defaults defaults
/dev/block/zram0 none swap defaults zramsize=533413200
Click to expand...
Click to collapse
Correct! There are 2 fstab file (The 64 bit build has 2), edit both...
craigacgomez said:
Yes...
Correct! There are 2 fstab file (The 64 bit build has 2), edit both...
Click to expand...
Click to collapse
ok awesome doing a factory reset now
Edit: can you add long back to kill app
---------- Post added at 07:34 PM ---------- Previous post was at 07:13 PM ----------
it booted
and it worked cheers tytyty
---------- Post added at 07:45 PM ---------- Previous post was at 07:34 PM ----------
it feels so much faster now
Just curious about what people are willing to try when it come to custom ROMs... The Nexus 9 is a 64-bit capable device and AOSP allows for 3 variations in the build
1. 64-bit with 32-bit support (like the stock ROM and this ROM here)
2. Pure 64-bit (no apps with libraries not in 64-bit format would work)
3. 32-bit only (Well, like Android for pretty much every device, though I think Bluetooth doesn't work in that case)
craigacgomez said:
Just curious about what people are willing to try when it come to custom ROMs... The Nexus 9 is a 64-bit capable device and AOSP allows for 3 variations in the build
1. 64-bit with 32-bit support (like the stock ROM and this ROM here)
2. Pure 64-bit (no apps with libraries not in 64-bit format would work)
3. 32-bit only (Well, like Android for pretty much every device, though I think Bluetooth doesn't work in that case)
Click to expand...
Click to collapse
1
Then in about 6-9 months 2
USBhost said:
[/COLOR]it feels so much faster now
Click to expand...
Click to collapse
It doesn't just feel faster. It is faster. And logically so. With encryption enabled there is extra overhead involved in decryption.
Related
Welcome to TWRP with F2FS & Thermal Control!
---- Supports Models d800/1/2/3/4/5, LS/VS-980, L01F, lgl22, and F320* ----
(for d804/5 use the d802 version)
Do NOT post a question if you don't read the first FIVE posts of this thread!!!
Features:
Added: Thermal control, thanks to using AICP kernel. [originally dr87's idea]
Added: As of 3.0.2-1: Using modified cm-13 kernel with my additions of thermal and other changes.
Added: As of 3.1.0-0: Using modified cm-14.1 kernel with my additions of thermal and other changes.
Added: Full F2FS support, including updated driver and f2fs-tools.
NOTE: You must NOT have "Use rm -rf instead of formatting." in the Settings page. If you have this option enabled, you will not be able to change partition type.
Added: Proper support for f320 & lgl22 External SD Card.
Added: Tap to wake.
Added: NTFS support.
Added: Working decryption support.
DO NO ENCRYPT f2fs - Bootloop of ROM and Recovery will occur!
Added: AROMA hack to fix graphics.
Uses: dr87's auto-select correct panel type.
Uses: Bump (So loki isn't needed)
& All of the goodies that already come packed in to the latest version of TWRP!
Please enjoy this recovery and I encourage feedback!!!
F2FS Information:
Clicky Clicky (or scroll down to post #5)
Bugs/Issues:
TWRP Issues, Generally:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues
https://github.com/omnirom/android_bootable_recovery/issues
Major Thanks to:
TWRP Team
Dees_Troy
OmniRom Team
Cyanogenmod Team
Drgravy
Team Codefire
Dorimanx
jakew02
dr87
Khaon
bart452
xiaolu
Yoinx
And everyone else involved with these projects!
Installation:
1) First, you need any version of TWRP installed and working:
I'd recommend using Autorec to get initial TWRP running.
This is the link for KK: http://forum.xda-developers.com/showthread.php?t=2715496
There is also an apk for lollipop, this is much preferred! (Google is your friend.)
You can use any number of other methods to get some version of TWRP installed and running.
2) Once you have a working TWRP, simply flash my zip to upgrade to latest version.
If you flash the image directly, the panel detection script will not run!
(This is only important if you have a jdi LCD panel.)
Troubleshooting:
If you have any issues, please try the Official Build and compare to check that bug is only present in my version. If it is present in both versions, report it to TeamWin or Dees_Troy. If it only bugs in my version, please let me know ASAP.
Also, please check FAQ before asking questions. Thanks!
Download:
https://www.gregtwallace.com/lg-g2/g2-twrp/
Downloads are installable zip files, the images inside of which are already BUMPed.
Sources:
https://github.com/blastagator
Source Readme:
https://github.com/blastagator/cm_device_lge_g2-common/blob/cm-13.0-twrp/README.md
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
XDA:DevDB Information
TWRP Touch Recovery w/ Thermal Control and F2FS, Tool/Utility for the LG G2
Contributors
blastagator, TeamWin, and everyone else listed above!
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-12-23
Created 2014-11-02
Last Updated 2019-12-31
Announcements
May 7, 2016
New CM-13 based build is released! Enjoy all.
May 4, 2016
New release coming this weekend. Make any complaints ASAP about version -g!
VOTE on if you want me to TRY to fix AROMA. (No guarantees!!!)
http://forum.xda-developers.com/lg-g2/general/twrp-poll-aroma-t3372512
April 30, 2016
Release candidate! Give it a test!
http://forum.xda-developers.com/showpost.php?p=66626361&postcount=2543
April 17, 2016
New beta using cm-13 sources. Click HERE. Please test!
April 7, 2016
TWRP 3.0.0-2 is here! Versions older than 2.8.7.3 have been removed from my download site.
February 17, 2016
(Working!) TWRP 3 is here!
More info: https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
.
Change Logs
December 23, 2019 (3.3.1-0)
-TWRP Change Log:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Click to expand...
Click to collapse
April 29, 2019 (3.3.0-0)
-TWRP Change Log:
* Merge AOSP 9.0 r3 (Dees_Troy)
* Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
* Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
* vold decrypt updates (CaptainThrowback and nijel8)
* Support vibration on LED class devices (notsyncing)
* Metadata decrypt support for Pixel 3 (Dees_Troy)
* Support rotating the display via build flag (vladimiroltean)
* Reboot to EDL mode button (mauronofrio)
* Support MTP on FFS devices (bigbiff)
* Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
* Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
* Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
* TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
* Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
* Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
Click to expand...
Click to collapse
September 22, 2018 (3.2.3-0)
-TWRP Change Log:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Click to expand...
Click to collapse
July 21, 2018 (3.2.2-0)
-TWRP Change Log:
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
Click to expand...
Click to collapse
December 17, 2017 (3.2.1-0)
(Bug fixes for 3.2.0)
-TWRP Change Log:
minui fixes (cryptomilk)
Better android-8.0 compatibility in ROM trees (Dees_Troy)
Fix missing library in android-8.0 (nkk71)
Fix inconsistent SDCard naming (DevUt)
Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Click to expand...
Click to collapse
-TWRP 3.2.0-0 Change Log:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP’s backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
Click to expand...
Click to collapse
December 3, 2017 (3.2.0-0)
Removed and replaced with 3.2.1-0
May 20, 2017 (3.1.1-0)
-TWRP Change Log:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
Click to expand...
Click to collapse
March 13, 2017 (3.1.0-1)
Rebuild of 3.1.0-0 (from 2017.03.10) - Add ability to boot with JB bootloader.
-TWRP Change Log:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
Click to expand...
Click to collapse
-Tree
++Bootloader offset is now 128!
If you are having OTA problems, make sure your ROM maintainer adds this to their device tree: https://github.com/blastagator/cm_d...mmit/946434d0881b50437422e7855d5d7a096d9608e1
Also, /misc needs to be mounted: https://review.lineageos.org/#/c/19334/)
++Completely rebased onto cm-14.1
++Remove custom USB - Use G2+TWRP usbs instead
++Tweaks to enable compatibility with old bootloader
-Kernel
++Completely rebased onto cm-14.1
++Tweaks to enable compatibility with old bootloader
++Disable lots of unneeded things and changed kernel compression
------------- All builds above this line are cm-14.1 based. -----------------
------------- All builds below this line are cm-13 based. -------------
May 7, 2016 (3.0.2-1)
-Tree
++Completely rebased onto cm-13
++All file utilities, etc. are now up-to-date with the latest cm-13 tree.
++Changed from debug builds to engineering builds, per TeamWin instructions (thanks @Startrek852)
-Kernel
++Took cm-13 kernel and added my stuff to it
++Disabled some tuner/multimedia stuff we don't need
++Updated f2fs
-TWRP
++New splash screen
++New fstab processing
++Fixed AROMA graphic bug. If AROMA still crashes, try this:
http://forum.xda-developers.com/showpost.php?p=66747442&postcount=2591
++Lots of language updates.
------------- All builds above this line are cm-13 based. -----------------
------------- All builds below this line are omni-4.4 based. -------------
April 7, 2016 (3.0.2-0)
TWRP 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords).
++This fixes decrypt of full device encryption on devices that support decrypt.
++This bug also impacts encrypted backups.
++Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
Click to expand...
Click to collapse
TWRP 3.0.1-0:
-Support new CM 13.0 pattern encryption (sultanqasim)
-Fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-Fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-Translation updates - added Italian, Czech and Polish and significant updates to Dutch
-Progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-Fix input box text display (Dees_Troy)
-Reboot option after zip install complete (bigbiff)
-Other mostly invisible bug fixes and improvements
Click to expand...
Click to collapse
Device / Kernel / etc.
-No changes
February 17, 2016 (3.0.0-4)
TWRP Change Log:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
Click to expand...
Click to collapse
My Change Log:
-TWRP:
++Re-enable RO check/warning - MM is potentially sensitive to RO
++NTFS Support
++Remove bootloader backup (user should use zips to manage bootloader instead)
++Enable extra languages (lots of options!)
-Device Tree:
++Fixed decryption
DO NO ENCRYPT f2fs - Bootloop of ROM and Recovery will occur!
++Fixed USB init problem (created custom usb recovery init by combining parts of g2 init and twrp init)
++Switched to using TWRP init w/ additional inits added via proper method
++Update external_sd init
++Restructure g2 device repo to further isolate 'TWRP' parts
++Enable QCOM Overlay Graphics
++Remove non-functioning LED part of postrecoveryboot.sh
-Kernel
++Fixed decryption
++Updated f2fs (to latest, @dorimanx for helpful commits)
++Enable NTFS
++Update exfat driver
++Fix lge usb gadget config options
++Some other misc. updates
November 9, 2015 (2.8.7.3)
-Sorry about bad 2.8.7.2 build
-Still built off of omni-4.4 source code. (Android-M isn't ready for a full release yet.)
-Vendor: Complete overhaul of vendor blobs, now using cm-12.1-caf branch from lg-devs
-TWRP: Make separate flags for ability to backup or restore partitions
-Device: Add ability to backup/restore Bootloader partitions
++User cannot use TWRP to restore Bootloader, too dangerous!
-Device: Removed system_image
++We don't need this for our phone and it was confusing people who didn't READ the change log
-TWRP/Device: Remove any warnings about system mount RO, this isn't important for our phone
-Device: Set max brightness to actual max (255)
-Device/TWRP: Create default brightness, set it to 175 (~68%)
-Kernel: Latest f2fs driver
++This should fix issue where ROM running kernel with newest f2fs doesn't boot
++Note: This breaks compatibility with ROM using old f2fs driver. Read note below.
-Kernel: Other commits that were needed to make latest f2fs driver work
-Kernel: Config changes that might allow encrypted f2fs to work now!
-Kernel: Enable SELinux
++Before I accidentally completely disabled, now it should boot Enabled, but in Permissive mode.
-TWRP: More tweaking to recreation of media folder / setting internal storage path
-Device: Remove integrated supersu
IMPORTANT - f2fs /data note: If you restore OLD backups, you will probably cause ROM or recovery (or both) to hang! This is obviously bad because your only option at that point is doing a back to stock kdz. To avoid problems, make NEW backups AFTER upgrading to the new version of TWRP. Backups made with 2.8.7.3 can be restored with 2.8.7.3 without causing issue.
October 31, 2015 (2.8.7.2)
-Broken build!
-Device: Add ability to backup/restore Misc partition
++Caused broken build. Do not use this version.
June 24, 2015 (2.8.7.1)
-Make sure you have newest Theme (or no theme).
-Fixed internal storage path, I had it wrong for long time, sorry!!! https://github.com/blastagator/cm_d...mmit/cbfe7d09d95890b4e26f673c9db937840167da9b
-Turned down max screen brightness, no need to fry phone
-Fixed TWRP not assigning proper context to Internal Storage when wiping: https://github.com/blastagator/andr...7903af041ad00146aee866#commitcomment-11848774
++Full wipe of phone will now always recreate folder properly!
++Bumped version up by .1 to reflect change to actual TWRP code.
-Add ability to backup "System Image"
++YOU VERY LIKELY DON'T NEED THIS. (If you're on anything other than stock ROM already, you DEFINITELY don't need it.) We have KDZ flashing to get back to stock.
++This creates a raw, emmc, backup of the System partition (instead of file backup)
++Has to do with new OTA issues (which aren't an issue for G2 yet, if ever)
++Not really important for us, but TWRP added it, so I added it too: https://github.com/omnirom/android_bootable_recovery/commit/eb32b1ff00878e7b01453450fcd04ecb9fcbba52
++See also: https://github.com/blastagator/cm_d...mmit/e28ab9cef31d6574a6f6e1f92b97f94bcbdda584
-TWRP Updates:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Click to expand...
Click to collapse
May 25, 2015 (2.8.6.3)
-Updated f2fs kernel module to match the version used by @dorimanx
-Updated vendor blobs by applying all changes from lg-devs and using newest 12.1 branch
-Updated e2fsprogs (the binaries used to manipulate the filesystem) to latest cm-12.1 version
-Updated to using the newest branch for qcom_common
-Updated f2f2-tools by forking cm-12.1 and making some tweaks (Git)
-Fixes the issue where TWRP won't load if you're using Lollipop with f2fs
-Relocated common manifest to g2-common git
-Enable new Qualcomm HW Decrypt flag
-TWRP Fixes:
++Prevent multiple unlock screens
++<MAYBE> Enable proper decryption of an encrypted /data partition
Much Older Versions:
May 24, 2015 (2.8.6.2)
-Test build that is now removed.
-Only built for d800 & d802.
May 2, 2015 (2.8.6.1)
-Added lgl22 support. All models now supported!
Mar 30, 2015 (2.8.6.1)
-Added ability to backup/restore Sensors partition (per user request)
-Thanks to @_that for tipping my off to my previous error (& @z31s1g who's themeing led to problem discovery)
-TWRP Changelog:
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
Click to expand...
Click to collapse
Mar 28, 2015 (2.8.6.0)
-Improperly built 2.8.6.0
-Used wrong TWRP tree. Oops!
Feb 15, 2015 (2.8.5.1)
-Corrected build of 2.8.5.0
-Edited the init.rc (see: https://github.com/omnirom/android_bootable_recovery/commit/df7abac1a645949ded76418759236bc3b14f107e)
-Also made a slight tweak to move tap-to-wake to a separate init (should make it easier to update the init.rc in the future if it is changed)
-FIXED: sd_card init was not being copied correctly. Relocated it to /etc and made appropriate related changes. (I guess this wasn't getting in the way of sd_card working, but it is proper to include this file.)
-NEW FILE HOST: Now using spideroak.com, they advertise no download limits!
Feb 13, 2015 (2.8.5.0)
-Merged upstream vendor blobs (Updates from lg-devs)
-TWRP Changelog:
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
Click to expand...
Click to collapse
Jan 13, 2015 (2.8.4.0)
-Changed Kernel Configs so default kernel state is SELinux Permissive.
++There was already a change that allowed TWRP to immediately change to Permissive, now it is Permissive immediately.
-Made a few changes to g2-common to accommodate lgl22 (when I get around to getting that working).
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
Click to expand...
Click to collapse
Dec 27, 2014 (2.8.3.1)
-Tweaked the fstab file
++Changed partition type to ext4 from auto - this should fix broken Format Data / Factory Reset. However, f2fs is still supported. My f2fs cache partition still mounted in twrp even though fstab was set to ext4.
++Added the encrypt partition to the fstab. This should enable twrp to mount encrypted /data partitions. I don't know if this is the problem or not. The one person I asked to try it didn't have any luck. Please others try and let me know if it works or what errors you get. NOTE: An encrypted f2fs /data partition will probably NOT work in this configuration.
Dec 24, 2014 (2.8.3.0)
-Version 2.8.3.0
What's new in 2.8.3.0:
MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
MTP will now tell the host PC that storage is removed instead of disabling MTP completely
MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
Update and improve fix permissions and make fixing contexts optional
Update SuperSU in TWRP to 2.40 and update install process
Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
Fix kernel panic during MTP start on some devices
Support unicode fonts on devices with True Type Font support
Fix slider value not showing sometimes (vibration settings page)
Toggle MTP off during adb sideload to set correct USB IDs
Reduce library requirements for 5.0 L decrypt
Other minor fixes and improvements
Click to expand...
Click to collapse
-Update g2-common to ensure se_linux will be set to permissive at boot of recovery
Dec 18, 2014 (2.8.2.1)
-Full repo sync
-Check the omni git for changes
-Looks like Dees_Troy pushed quite a few bug fixes over the past couple of weeks
-Switched device tree to start using 'L' encryption
Dec 11, 2014 (2.8.1.2)
-Rebuild of 2.8.1.1
-Uses the new device trees
-Adds l01f for this version
-BUMPed (2.8.1.1 was not)
-I recompiled this version due to various bug complains involving 2.8.2.0 in general - in case anyone wants to stay on old version til those get sorted out.
++I'm not aware of any specific issues.
Dec 9, 2014
-Created custom l01f kernel config.
-Built and added l01f variant.
Dec 6, 2014 (2.8.2.0)
-Reworked all device trees to use the CM stock device trees + a couple mods to add TWRP support.
-Still using the Omni4.4 source.
-BUMP'ed and new flashing script that still auto-detects panel type but does NOT use loki.
++Bump works on JB & KK bootloader.
-All the other goodies as listed in 2.8.1.9.
-If you're on d800 and want to upgrade to KK bootloader, go here.
Dec 2, 2014 (2.8.1.9)
-Built with Omni 4.4
-TWRP 2.8.2.0 Source (LP5.0 for TWRP source only)
-Labeled as 2.8.1.9 just for clarity when I redo the device trees and rebuild.
-Team Win Change Log:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Click to expand...
Click to collapse
Oct 25, 2014 (2.8.1.1)
-Corrected bug where "Internal Storage" was being listed as "Data"
-F320: Added additional properties to External SD mount.
++Should now be able to wipe External SD under advanced wipe.
++Should not get error when booting TWRP with no External SD card inserted.
Oct 24, 2014 (2.8.1.0)
-Team Win released version 2.8.1.0 [TeamWin Page]
What's new in 2.8.1.0:
MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
Temperature support - thanks to bigbiff
Various other bugfixes and tweaks
Click to expand...
Click to collapse
-Full repo sync and upstream merges on all sources.
-F320 External SD Card is now supported.
-Ability to backup Modem and Recovery partitions
Oct 20, 2014 (2.8.0.2)
-Because incrementing a digit by 1 is always better!
-Full repo sync and upstream merges on all sources.
(That is - TWRP source, device tree source, g2-common source, and aicp source are all the newest available!)
-Compiled completely from scratch. (No need for hodge-podge as previous version.)
-TWRP now shows CPU temperature.
-F320 variant should work now.
(Which is nice for F320 users since it looks like it has been awhile since getting a new version of TWRP!)
-Simplified file naming convention for the downloads.
-Original release used old loki. New zips are posted with newest loki and newest panel detection script! Should work on all phones now.
Oct 19, 2014 (2.8.0.1)
-Changed to AICP kernel to add thermal control!
-Patched AICP kernel to support F2FS.
-2.8.0.1 Base came from DrGravy (this version is a composite of a few different sources)
-Tap to wake works now.
-TWRP Version 2.8.0.1
-Some bug fixes that came along with 2.8.0.1
Oct 18, 2014
-Not actually a new build, just a big information update!
-Added info for adding full f2fs support to your kernel.
-Looking in to compiling TWRP with the AICP kernel to add thermal support.
Oct 10, 2014
-Full repo sync.
-Changed vendor tree from a CM11 build that I had been using to dr87's git.
-Built for (almost) all LG G2 models.
------------- All builds below this line are for D800 ONLY! -------------
Oct 8, 2014
-Fully sync'd everything to the above listed gits
-Moved the tap to wake code out of bootable/recovery and into a custom recovery init.rc
-Moved a couple files into g2-common/twrp folder to improve organization
-Sync'd with main repo to get any code changes and confirm the init.rc wasn't causing issues anymore
-Posting this build in .img and .zip format
Oct 7, 2014 (Build 2)
-Added postrecoveryboot.sh (Forgot to include it in the original build)
Oct 7, 2014
-Initial Release
-Based on latest OmniRom TWRP Source
-Kernel is based on Stock Kernel patched w/ F2FS for 3.4 kernel
FAQ
My OTA isn't working or I am now in a bootloop to TWRP.
To get out of the bootloop, connect to adb shell, and issue:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
This should resolve the problem. If not, search the thread, some people have other suggestions for various places to nuke the bad commands residing in /misc. To avoid the future problem, contact your ROM maintainer with the following info.
Starting in Android N, the ROM uses /misc partition to communicate with recovery. (Therefore if your ROM is M or lower, OR uses the old communication method, this is not relevant to you). To address OTA problems, it is important to note the newly introduced bootloader offset.
https://review.lineageos.org/#/c/165001
Also, /misc needs to be mounted:
https://review.lineageos.org/#/c/19334/
Your ROM maintainer should add these to their device tree. This will insure that ROM will write to the exact place the recovery is reading from.
I see error: "E: mount -0 bind '/data/media' '/sdcard' process ended with error=255" when I switch partition type on /data.
Update to new version, 2.8.7.1. This problem is fixed.
I see error: "assert failed: run_program(" /tmp/loki.sh") == 0" when I flash X. Why?
Loki is only supported by JB BL. Loki is smart enough to check your BL version before flashing. If you are on KK BL and the thing you are flashing uses loki, you're going to get this error. New BL requires you to use bump.
Now that I have bump, how do I update to the KK bootloader?
If you have a d800 (or d801), see my thread here. If you have a d802, see @dorimanx's thread, here. Credit's to dori for inspiring me to make the package for d800.
USB-OTG isn't working, why not?
To use USB-OTG your device needs to be formatted fat32, not NTFS.
I'm having trouble formatting partitions. Why doesn't it work?
Fixed: As of 2.8.3.1
The option to Format Data or do Factory Reset probably won't work. The fstab is set to auto to support f2fs and those two options don't know how to deal with auto (they don't know if you want them wiped to ext4 or f2fs). Therefore, you need to do Advanced Wipe, which works fine. If you are still having trouble, make sure MTP isn't on and make sure your USB isn't plugged in.
OMG, my TWRP thinks this is the 1970s?! HALP!
This is an issue that arises in Android L (for whatever reason). Member murdoch1 found this and confirmed that installing it fixes the 1970 issue in TWRP.
Does [xyz] work?
As far as I know, everything works except for known issues in the common twrp source.
I want to report [xyz] as not working, how do I do it?
Post in this forum. I'll do what I can to fix it.
When will the next version come out?
I don't plan on building again unless a bug is discovered that I can fix, or if TeamWin releases the next version.
Why don't you do [xyz]?
Why don't you do it?
Why doesn't F2FS work?
It DOES work in the recovery. To get it working on your ROM you need to have proper kernel support. Many AOSP ROMs support f2fs partitions. Additionally, dorimanx has added working f2fs on his stock kernel.
Why doesn't AROMA work?
AROMA is old. As of version 3.0.2-1, I added a hack to fix the graphics. If your zip file still isn't working, try my guide:
http://forum.xda-developers.com/showpost.php?p=66747442&postcount=2591
F2FS Information
WARNING: Changing Partition type of /data WILL wipe ALL data, including INTERNAL SD!
You need to specifically backup Internal SD, TWRP does not automatically do this when you backup /data!
(This only applies if you change from ext4 to f2fs, or vice versa; other operations will not magically wipe your partitions.)
WARNING 2: DO NOT ENCRYPT F2FS - ROM and RECOVERY will BOTH bootloop and you'll be doing back to stock method!!!
If you want to use F2FS:
1) Make sure your kernel and ramdisk support f2fs (the dev of your ROM/kernel should have f2fs support noted). Dorimanx stock kernel as well as many AOSP kernels have full f2fs support.
2) Install and boot into my recovery.
3) Go to Wipe, Advanced Wipe, select /data, then click Change Partition Type. Select f2fs, and it will convert. Repeat this process for /cache.
4) Reboot the recovery, NOT reboot to system. DO NOT DO ANYTHING ELSE UNTIL YOU REBOOT RECOVERY!!!
5) Reboot OS. That's it! You're ready to go.
If you want to switch to F2FS without losing your data:
1) Make sure your kernel and ramdisk support f2fs (the dev of your ROM/kernel should have f2fs support noted). Dorimanx stock kernel as well as many AOSP kernels have full f2fs support.
2) Install and boot into my recovery.
3) Make a backup of your /data partition and copy it to your PC via MTP. Also, copy the content of your /sdcard to your computer. Both of these things will be destroyed when you switch partition type!
4) Go to Wipe, Advanced Wipe, select /data, then click Change Partition Type. Select f2fs, and it will convert. Repeat this process for /cache.
5) Reboot the recovery, NOT reboot to system. DO NOT DO ANYTHING ELSE UNTIL YOU REBOOT RECOVERY!!!
6) Copy your backup via MTP to your phone. Restore your /data partition.
7) Copy your sdcard files back to your sdcard. (NOTE: For some reason, when I do this, the files end up getting deleted, you may need to copy the sdcard files over after your reboot into your OS.)
8) Reboot OS. That's it! You're ready to go.
Don't complain if you didn't read everything in all 5 of these posts!
Very nice! Im glad to see more work being done to bring F2FS to the G2. I dont know enough about getting into the ROM and kernels to get this going myself, but I will be following the development more closely now and hope someone else is gracious enough to port one of the stock based ROMs to work with F2FS. I think I remember seeing Dorimanx kernel has support for the file system already too, just no recovery or ROM that was capable at the time.
blastagator said:
Problem: We need a kernel/ramdisk that will mount the partitions in a ROM!
On my ROM I am using Dori's kernel with which has the f2fs module. However, even though it has the module, the /cache partition does not mount when the rom boots. Perhaps a ramdisk fstab issue? - Possibly my next adventure...
Click to expand...
Click to collapse
You may need to rebuild his kernel (or rip the ramdisk out of a pre-built one and inject it back in after modifying it) and explicitly mount the cache partition as f2fs.
https://github.com/dorimanx/LG-G2-D802-Ramdisk/blob/kitkat-ramdisk/ROOT-RAMDISK/fstab.g2
You'd probably need to add it with these, though I'm unsure why it's not already listed. It may be in the built ramdisk, built into the file during the compile... It may also be mounted after boot in one of the .rc scripts... But I'm used to seeing all the partitions laid out in the fstab on previous devices.
Have you tried manually mounting via terminal once you've booted? I'm assuming that works and you're just trying to make it auto-mount?
Yoinx said:
You may need to rebuild his kernel (or rip the ramdisk out of a pre-built one and inject it back in after modifying it) and explicitly mount the cache partition as f2fs.
https://github.com/dorimanx/LG-G2-D802-Ramdisk/blob/kitkat-ramdisk/ROOT-RAMDISK/fstab.g2
Click to expand...
Click to collapse
I was thinking modify the fstab. However, in dori's kernel, the fstab.g2 doesn't even have entries for /system /data or /cache. In the recovery I changed those partitions from ext4 to auto. I planned to do the same on the kernel. Even though the fstab is different, I was going to try adding mounts for those 3 partitions and see what happened. However, I couldn't get the image repacked. I used the non-standard mkbootimg from the compiling of the recovery. I tried several different commands to repack - all of which led to a boot loop. (Except one, which got me fastboot because the offsets were wrong.)
Alternatively I was going to recompile the dori kernel but I haven't really delved into adding the custom ramdisk into that compile, got too tired last night.
Yoinx said:
Have you tried manually mounting via terminal once you've booted? I'm assuming that works and you're just trying to make it auto-mount?
Click to expand...
Click to collapse
Using: mount -t f2fs /dev/block/platform/msm_sdcc.1/by-name/cache /cache
The partition mounted properly using the dori's build of dori's kernel 8.0.1
You can get something like kernel workshop, extract the boot.img into the kernel and ramdisk to play with whatever then repackage it without recompiling.
Yeah, I saw the fstab is a bit odd. I thought they were moving to a new mount system but I couldn't find it handily
Yoinx said:
You can get something like kernel workshop, extract the boot.img into the kernel and ramdisk to play with whatever then repackage it without recompiling.
Yeah, I saw the fstab is a bit odd. I thought they were moving to a new mount system but I couldn't find it handily
Click to expand...
Click to collapse
Dori was nice enough to point it out for me:
https://raw.githubusercontent.com/dorimanx/LG-G2-D802-Ramdisk/kitkat-ramdisk/ROOT-RAMDISK/fstab.g2
https://github.com/dorimanx/LG-G2-D802-Ramdisk/blob/kitkat-ramdisk/ROOT-RAMDISK/init.target.rc#L45
I plan to fiddle with it
Simple enough. They're just running it in the scripts then. I modified my old phone's kernel to have simulated run levels by running a script from each of the points in the init.rc events, so you could run commands at various points throughout the boot sequence via init.d essentially. I liked the feature, but I don't think many others really had a use for it.
Same concept, the only downside by it being hard-coded is that you need to repack each time instead of just modifying an init.d script on the fly.
Glad you found it though
Yoinx said:
You can get something like kernel workshop
Click to expand...
Click to collapse
Try googling "kernel workshop" --- grumble
Sorry man. I usually post from my phone, so it's hard to verify some of what I'm saying...
http://forum.xda-developers.com/showthread.php?t=2073775
It's android image kitchen. I had the wrong name.
Yoinx said:
Sorry man. I usually post from my phone, so it's hard to verify some of what I'm saying...
http://forum.xda-developers.com/showthread.php?t=2073775
It's android image kitchen. I had the wrong name.
Click to expand...
Click to collapse
Thanks. I've been fighting with that as one of my options. The g2 requires a dt.img as well as a non-standard mkbootimg, so it is driving me up the wall!
blastagator said:
Thanks. I've been fighting with that as one of my options. The g2 requires a dt.img as well as a non-standard mkbootimg, so it is driving me up the wall!
Click to expand...
Click to collapse
Interesting. I haven't started really building anything for the G2 yet.... not enough time IRL at the moment. When I flash kernels though, it's just boot.img.
What's this dt.img that you're talking about? The non-standard mkbootimg is typically just just for offsets.
You may be better off just downloading the kernel sources and building from scratch if the imgtools dont work.
Looks like this guy's got a version of the mkbootimg tools that supports dt.img https://github.com/xiaolu/mkbootimg_tools if you're running linux (hopefully, since it makes things MUCH easier)
Yoinx said:
Looks like this guy's got a version of the mkbootimg tools that supports dt.img https://github.com/xiaolu/mkbootimg_tools if you're running linux (hopefully, since it makes things MUCH easier)
Click to expand...
Click to collapse
You sir are a god send! Unpacked the Dori kernel, repacked, and the repacked image booted right up!!! I'll be sure to update if I make any headway with automount
Oct 8, 2014 Build
-Fully sync'd everything to the above listed gits
-Moved the tap to wake code out of bootable/recovery and into a custom recovery init.rc
-Moved a couple files into g2-common/twrp folder to improve organization
-Sync'd with main repo to get any code changes and confirm the init.rc wasn't causing issues anymore
-Posting this build in .img and .zip format
Signed Zip: https://www.dropbox.com/s/sd1lo0mijouu6kg/2014.10.08-blastagator-twrp-2.8.0.0-w.f2fs-signed.zip?dl=0
Zip MD5: https://www.dropbox.com/s/xmw5e4pzw...gator-twrp-2.8.0.0-w.f2fs-signed.zip.md5?dl=0
Img: https://www.dropbox.com/s/gmzfyg7rs8guw1m/2014.10.08-blastagator-twrp-2.8.0.0-w.f2fs.img?dl=0
Oct 10, 2014 Build
-Full repo sync.
-Changed vendor tree from a CM11 build that I had been using to dr87's git.
-Built for (almost) all LG G2 models.
-deleted- (double post)
Your title for the OP says it is for the vs980 as well...
I don't not see a link for it though
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For general discussions, bug reports and FAQ, go here.
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
MTP storage
HW accelerated GUI
HW accelerated video
Camera
Torch
Wifi/USB tethering
USB OTG (Requires external power source)
Hybrid ION/PMEM
Known issues
Camera app is buggy
720p recording broken
Screenshots
CM-12.0 Install Guide
Note: CM for Galaxy W is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
Download CM-12.0 and gapps package and put in external sd card
2015-06-04: CM-12.0 20150603-UNOFFICIAL [DOWNLOAD]
MD5SUM: 88a1dd3cc3d43d74db866d598a27958e
Reverted BLN changes (broke LED)
More detailed changelog
2015-05-23: CM-12.0 20150523-UNOFFICIAL [DOWNLOAD]
MD5SUM: de5c796615ce316173e4a6f095d54899
overlay: Define default quick setting tiles
device: Disable dex2oat watchdog
liblights: Add Generic BLN Support
liblights: Additional updates
sepolicy: Label BLN sysfs
rootdir: Set permissions on BLN sysfs nodes
Credits for various changes goes to: sirmordred, mikeNG
More detailed changelog
2015-05-02: CM-12.0 20150501-UNOFFICIAL [DOWNLOAD]
MD5SUM: 4c089a2d7552146078214b2011c2c23c
Revert "rootdir: Increase Swappiness to 100"
Revert "rootdir: Increase zram disk size to 256mb on 512mb devices"
rootdir: Use lz4 compression for ZRAM
rootdir: Reduce ZRAM size to 128MB
Fixed power off charging
kernel 3.4.107
More detailed changelog
2015-04-11: CM-12.0 20150410-UNOFFICIAL [DOWNLOAD]
MD5SUM: 884d2a2de87187067a7d9b41d1cc49b8
device: Add support for display color calibration (KCAL)
cmhw: Add keydisabler class
rootdir: Set permissions for keydisabler
rootdir: Various updates to init
overlay: Disable dialer lookup by default
Add support for TWRP
rootdir: Fix typo
Credits for various changes goes to: sirmordred, khusika
More detailed changelog
2015-03-14: CM-12.0 20150314-UNOFFICIAL [DOWNLOAD]
MD5SUM: fc56c6a70c5f140538587476f1e3344d
media_profiles: [TEMP] temporarly disable 720p recording for back camera
uevent: Set perm of dev/ledflash as R/W
BoardConfig: Enable some healthd charger options
device: Updated liblight
device: Removed deprecated egl.cfg
prop: Disable offload audio
rootdir: Increase zram disk size to 256mb on 512mb devices
rootdir: Increase Swappiness to 100
Credits for various changes goes to: Christopher83, sirmordred.
More detailed changelog
2015-03-08: CM-12.0 20150308-UNOFFICIAL [DOWNLOAD]
MD5SUM: f843c5cf23993264ef3fa262ebc15a8d
ril: Fix multi-part SMS sending
config: Update audio_policy.conf
README: Make it look nice
device: Support for F2FS formatted /data partition
device: Add ethernet feature
device: Move AAPT config to cm.mk
device: Use local copy of wpa_supplicant_overlay_conf
device: Disable HW MP3 decoder
BoardConfig: Reduced userdata partition size by 16 KB
BoardConfig: Build wifi-hal
BoardConfig: Disabled some more unsupported audio features
rootdir: Remove crypto module triggers
rootdir: Set permissions through init instead of script for bt/mac address
rootdir: Blank/Unblank framebuffer to clear splash screen while on bootanimation
rootdir: Change permissions on external storage mount points
rootdir: Remove sdcard1 from fuse_usbdisk service
rootdir: Updated healthd charger service
overlay: mms: Updated config
overlay: Add new default wallpaper for 480x800
overlay: Set external storage devices as non-emulated
sepolicy: To be fixed-up inside 6a1658d commit
sepolicy: Allow system server to R/W from radio devices
sepolicy: Address some denials
sepolicy: Fix denials writing to external sd in UMS mode
prop: Switch to NuPlayer
prop: Add property to indicate we support usb-otg
camera: Modify base.common.version API define
Revert "device: Move AAPT config to cm.mk"
Credits for various changes goes to: Christopher83, sirmordred.
More detailed changelog
2015-01-23: CM-12.0 20150122-UNOFFICIAL [DOWNLOAD]
MD5SUM: f26042dae35bc2a36aefdb5bac4c1a43
BoardConfig: Disable some audio features
BoardConfig: Make dexpreopt flag compatible for multiplatform compiling
BoardConfig: Enabled extended font support
gps: Zero-out dev structure after checking for NULL
gps: Makefiles cleanup and some changes to correctly build GPS HAL
gps: Some improvements to HAL
sepolicy: Updates from ariesve device
sepolicy: Allow read/write permissions on /dev/multipdp for rild
ril: Ignore getCellInfoList and setCellInfoListRate calls
bluetooth: Updated config
cm: Switch to full phone config
Revert "ramdisk: Remove permissions change for /proc/cmdline on early-init"
ramdisk: Add config for USB charging
ramdisk: Some updates and cleanups
overlay: Updated overlay for recent fw/base changes
overlay: Add deviceHardwareWakeKeys config
overlay: Update device hardware keys integer
prop: Enabled HighEndGraphics by default
prop: Removed deprecated properties
prop: Update the property name for AwesomePlayer usage
prop: Increase max background services to 8
device: Use healtd charger during off-mode charging
misc: Remove obsolete and unsupported stuff
Credits for various changes goes to: Christopher83, sirmordred, Harakhti.
More detailed changelog
2014-12-30: CM-12.0 20141230-UNOFFICIAL [DOWNLOAD]
MD5SUM: 51c2548c0cfaa5e0d58b53055bf58ded
INITIAL RELEASE
New partition layout and switch to emulated storage
NB! Requires new recovery and a complete wipe!
BACKUP ALL YOUR DATA!
Download recovery: recovery-clockwork-6.0.5.1-ancora.zip
Flash it in old recovery. Then go to "advanced" menu, and select reboot recovery. When new recovery has loaded, select wipe data/factory reset, then go to "mounts and storage" menu and select format /system. Then select "format /data and /data/media" (NB. only needed the first time installing the rom). Now you should make sure you have put the rom file on an external sd card. Install that and gapps the normal way. You can also use adb sideload.
For more info on the new layout, see here: https://github.com/arco/android_device_samsung_ancora/commit/d1cb921fb3ecd3e90a35da2af6a878aa294f168d
Another benefit is that it's now possible to install the full gapps package.
Google Apps (UPGRADE REQUIRED)
Google Apps
Before you install CM-12.0: Preparation (First three are optional. If you want to start fresh, these can be skipped)
Install AppBak from Market, run it and save a list of all your apps.
Install SMS Backup and Restore from Market, run it and backup your SMS history.
Install Call Logs Backup and Restore from Market, run it and backup your call log history.
Boot into CWM6 recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
Install
Use CWM6.
Warning: Only use this recovery to flash CM-12.0. Otherwise, you risk bricking your phone, or you might experience boot and stability issues!
Wipe data and cache.
Format /system (only first time coning from older recovery)
Format /data and /data/media (only first time coning from older recovery)
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM12.0 since /system is formatted, wiping your previous add-ons.
Reboot phone.
First boot might take 30-40 minutes, so be patient.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Upgrades
Upgrades from previous versions of CM12.0 are the same process as install, except you do not need to wipe anything. Contrary to popular belief, you do not need to even wipe cache and dalvik-cache when upgrading between CM12.0 versions. You only need to wipe if you are doing a major upgrade, switching to a different ROM entirely, or attempting to fix bugs caused by bad backups or corrupt app data.
Credits
CyanogenMod Team
AriesVE DevConnection Team
Epic Touch CM Team for the install instructions
ivendor and mirred for help with the camera HAL
Everyone that donated beers
Reserved
Thanks arco. You are amazing.
AWESOOOMEEE..
but i'm just install CM11
Damn, Arco, that came out of nowhere.
Nice.
Haters gonna hate
WooooooW
Finally LP
Thank you master
plz add some more reserved posts...
so that i can use all thanks of my daily amount for this thread and your great work!
Also big thx to @Christopher83 @DevConnection_Team & @sir mordred !
tycoo said:
plz add some more reserved posts...
so that i can use all thanks of my daily amount for this thread and your great work!
Also big thx to @Christopher83 @DevConnection_Team & @sir mordred !
Click to expand...
Click to collapse
Now is the time for us to rush in head-on and start comparing branches like crazy.
tycoo said:
plz add some more reserved posts...
so that i can use all thanks of my daily amount for this thread and your great work!
Also big thx to @Christopher83 @DevConnection_Team & @sir mordred !
Click to expand...
Click to collapse
Thanx for your appreciation tycoo
ım just doing minor things on development but arco and others are really linux head.... big thanx to them
OH MY GOOD , great gift for the final time of the year thanks to @arco68 @Christopher83 and other developers :highfive:
hmmm first reviews
system is really stable at this moment but unfortunatly ı couldnt pass the following pop-up message "android is upgrading 1/1 app optimizing" ı faced with that message after first reboot. I tried to clear cache but it didnt work
so ı had to reflash the cm11
EDİT:no need to return back... after 5-6 minutes that message disappeared... .)
sir mordred said:
hmmm first reviews
system is really stable at this moment but unfortunatly ı couldnt pass the following pop-up message "android is upgrading 1/1 app optimizing" ı faced with that message after first reboot. I tried to clear cache but it didnt work
so ı had to reflash the cm11
Click to expand...
Click to collapse
Its happen to me too, but after waiting 5-10 minutes its boot as well
Yey, finally!! Thanks arco. :thumbup::thumbup:
Another lollipop roms will be come, stay tuned
Fatastic work man, another reason to start building VanirAOSP Lollipop for ancora
Oh shyt! Thanks a lot man! :good::good::good:
Thank You Arco ! :good:
Thank you master thank you???
Thank you so much sir. You are amazing ?
Finally lolipop for Wonder?
Thank you for a huge new year gift ?
Sent from my GT-I8150 using XDA Premium 4 mobile app
omg finaly lollipop
thanks arco you're the best
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KatKiss ROM
Nougat 7.1 ReleaseAsus TF300T
Please note that this version is made for and tested on the TF300T model.
This rom is an aosp based rom with my own additions on top of it.
The main motto of the rom being Kiss. Even though the Meerkat could give you a kiss, it stands for Keeps it Sweet and Simple too
Which means that the rom's main goal is efficiency, speed/responsiveness,
while not adding bloated features that will slow things down
DOWNLOADS:
TF300T Latest Rom Version: KatKiss-7.1_TF300T_039.zip | Mirror
Gapps: OpenGapps ARM 7.1 Pico
Latest SuperSU: SuperSU stable
Sound improvements & misc : install the K.A.T App
TF700 & TF201 versions: http://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
TF701 version: https://forum.xda-developers.com/transformer-tf701/orig-development/rom-t3540259
Quick demo video of the current rom: https://youtu.be/bclpP2UJydE
You'll have to excuse the phone quality
it's mostly to show the responsiveness, launch times, switching between apps repeatedly, multi apps, video playing, floating windows and so on, it's not feature exhaustive.
Install Instructions:
Install KANG TWRP Recovery
Backup everything !
Boot into the recovery
The first time or everytime you have an issue when dirty flashing (Especially when changing android versions):
[*] do a full wipe , if you have issues make sure that you format /data (format is different than wipe)
Warning: formatting will remove what is stored in your internal storage, so store the rom /gapps/supersu zips onto an external storage (microSD, SD card..) or make sure you know how to push them back through adb.
Change /data filesystem to f2fs
(wipe => advanced wipe, check /data then "Repair or change filesystem" => change file system => and choose F2FS)
Then everytime (even when "dirty flashing") do the following steps:
Flash the rom
Flash the SuperSU zip
[*]Flash gapps
Wipe cache/dalvik
Reboot
Note that current gapps setup wizard will crash as it is not fully compatible with android 7.1.2 (KatKiss >= 022)
unless you turn on wifi manually after the language selection in the initial setup.
(if you don't have a dock, use the extra wifi button in the navbar)
Rom Main Features:
Native Nougat MultiWindow
High speed and responsive oriented
High performance and overclocked KatKernel included
Built O3 & with High optimization flags
Dock keyboard Support with full special/function keys support
Global Keyboard Shortcuts / KeyOverride Macro association (See post #2 for more info)
HDMI Support
Battery Level Indicator & Dock Battery support + Mods (icon/Text/%)
F2FS, CIFS, ext4, NTFS & Exfat support
Native Android FSTRIM + Manual scripts for Database optimization and fstrim (see post #2)
Media Scanner Filters
System UI editor with Navbar tuner
All Wifi channels support
Integrated cpu & io performance settings panel
Custom Navbars buttons long press actions
User Immersive mode and actions with automode when docked setting
Advanced per application permission management (AppOps)
Ethernet-auto support
Misc utils Busybox, rsync...
Included KatKernel Main Features:
-- Based on latest Asus 10.6.1.27.5 version.
-- CPU Overclockable up to 1700 (1500 default), GPU overclock (OC 520 by default) , uservoltage
-- Built with UberTC GCC 5.4, -O3, graphite + Optimized flags
-- F2FS support
-- governors: interactive pegasusq conservative ondemand powersave performance
-- iosched: BFQV7r5, Zen, ROW, SIO, deadline, NOOP, CFQ
-- FS: ext3-4, VFAT, NTFS, F2FS, NFSV3+4, CIFS
-- TCP Congestion: illinois cubic veno reno bic westwood highspeed htcp vegas scalable yeah
-- Asynchronous Fsync
-- USB NET drivers
-- lowmemorykiller: misc optimisations & fixes
-- backports from more recents kernels (3.4,& 3.9)
-- SLUB
-- exposed SOS/LNX
-- Restrict slave mountspace so Dalvik apps can mount system-wide volumes
-- Misc optimization & fixes: cpufreq, block, mmc, i2c, sched, rcu, arm specific routines, ...
-- Misc security fixes, futex, tty ...
ChangeLog: http://public.timduru.org/Android/KatKiss/7.x/ChangeLog.html
Rom Source: https://github.com/timduru (branch katkiss-7.1)
Kernel Source: https://github.com/timduru/tf300t-katkernel
Credits: Original banner concept by i9apps, Bootanimation by mgeniusm, original drawing by BBF, tetsuo for his contributions, Chainfire for SuperSU, Anthony Restaino for Lightning Browser
WebPage
How to report
What to include in the report
Disclaimer: The usual
Use at your own risk, I won't be responsible for any damages caused to your Transformer or to yourself.
In most cases if something breaks, flashing a rom on top should fix it.
XDA:DevDB Information
KatKiss-Nougatella, ROM for the Asus Transformer TF300T
Contributors
timduru
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Latest stock bootloader, KANG TWRP
Based On: AOSP
Version Information
Status: Stable
Beta Release Date: 2016-09-02
Created 2016-09-02
Last Updated 2019-09-28
Tips
First Install
Make sure you do a format /data the first time you install the rom
(backup your internal storage first if you want to keep something)
The first boot after a rom flash can take a few minutes as ART is slower than dalvik to optimize the applications, but is faster after the 1st time.
(First boot takes ~4-5 minutes without gapps and 10+ minutes with gapps)
Also keep in mind that after a fresh install, it might take a bit of time to get up to full speed as media scanner & google are checking/scanning and restoring stuff.
Note that app optimizations /cache will now occur in background after being installed, only when :
- your device is idle
- on power and fully charged.
So after install , let your device on the charger for a few hours for it to fully optimize.
System UI Tuner
A few things including the navbar buttons can be tweaked in Settings => System UI Tuner
Hardware keyboard layouts
More languages have been added in the default asusec keyboard
Set the keyboard layout through Settings => Language & Input => Physical Keyboard (asusdec)
(to use multiple layouts , you first need to add another Language in Settings => Language & input)
You can switch between layouts using the keyboard icon that appears in the navbar.
Storage Encryption
Encryption is not supported on our devices
Global Key Override/Shorcut Mecanism
Available in Settings => Dock => Add Key Override Actions
This will allow you not only to redefine function keys assignment, and other special keys actions,
but you'll also be able to assign global macro actions / app launch to any key + Meta key combination (shift Left or Right , ctrl..)
You can also add multiple actions to one key combination, simply click again on the "+" button for the same key combination.
For example if you want to assign to one key combination a list of action to run before going to bed for example, like: turn wifi off, Bluetooth off, mute sound, and turn screen off, you can do that
Note that starting multiple applications with one key is kinda a miss and hit for the moment due to some mecanism in android that seems to prevent applications to start too close to each others.
Bluetooth audio devices
For bluetooth audio devices that have "phone audio" capability you need to uncheck the box in the device's bluetooth settings.
Camera
Video recording is 720p max
Storage (fstrim) and Database optimization:
Fstrim is native since 4.3 and will happen in the background if your tablet is idle / sleeping and that your battery is > 70%
There is also a script to run it manually in the rom: /etc/kat/optimizestorage
To optimize the Database: /etc/kat/optimizedb
To run both, open a terminal and run:
su
/etc/kat/optimize
res
res
Oh man sounds sweet but the link is down.
StaticMaal said:
Oh man sounds sweet but the link is down.
Click to expand...
Click to collapse
that's why it says ****Coming soon**** next to the download links
I need to create the thread first to upload basically, 8 minutes left if xda doesn't fail
First Beta Release #006
New rom version available: KatKiss-7.0_TF300T_006.zip
Let's go !
I've been using Nougat for the past few days and It's pretty much usable as a daily rom already I'd say
Unless you need one of the missing /not working feature of course (See 1st post)
I'll be busy for the weekend, so I thought some might want to play with it too
As usual with a major upgrade: FORMAT /data first
(it'll change it to ext4, then you simply need to change it back to f2fs)
Have fun
Sorry man I thought coming soon was meant for the mirror link.
Wow. This is very impressive, I hope to try this soon
Tim, you are..THE MAN!!!
Sent from my TF300T using XDA-Developers mobile app
Installed and seems to run good! I didn't do extensive testing till now though...
Thank you for the great work you are doing!
@timduru
Did I understand correctly?
My steps when moving from version KatshMallow #029 the following:
Full wipe + format /data to ext4
Convert /data to F2FS
Install new ROM (7.0) + GAPPS + SuperSU
BrateloSlava said:
@timduru
Did I understand correctly?
My steps when moving from version KatshMallow #029 the following:
Full wipe + format /data to ext4
Convert /data to F2FS
Install new ROM (7.0) + GAPPS + SuperSU
Click to expand...
Click to collapse
Yep, that would work
You can skip "full wipe", as data format to ext4 does the same, just more complete
Installed. Running fine.
Sent from my TF300T using Tapatalk
Do I have to format f2fs even though I am already on katshmallow with f2fs?
thorrules said:
Do I have to format f2fs even though I am already on katshmallow with f2fs?
Click to expand...
Click to collapse
Yes, full cleaning internal storage needed.
Do I convert /data to f2fs within kang twrp or adb with a command line?
Sent from my Nexus 5X using XDA-Developers mobile app
tamkhanh said:
Do I convert /data to f2fs within kang twrp or adb with a command line?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
kang twrp
Will this fantastic ROM become available for the TF201 as my TF300 has just gone Kaput!!
Is there a possibility to install google now launcher?
When installed from the store, I can't get it to run. And flashing the micro or stock gapps, results in the device not booting. And I waited for like 20 minutes. Or was that too short of a waiting time?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: Disclaimer
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
EvolutionX for Mi Mix 2 [chiron]
* Evolution X allows users to experience Google's latest Pixel updates while integrating useful features from known custom ROMs.
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Encryption on f2fs doesn't workInstallation
Choose your flavor
1. You can choose between the traditional EXT4 or the new EROFS. This fs affect only to /system and /vendor partitions
2. Magisk doesn't work on EROFS at the moment. Anyway I've included KernelSU on kernel, so you can install if you want KernelSU app in order to get root and flash magisk modules
3. Once selected root partitions fs, you can choose fs for /data and /cache partitions between traditional EXT4 or F2FS
4. Note that EXT4 comes with encryption by default and F2FS comes unencrypted
Decide if you want encryption or not
1. If you want encryption, use EXT4 on /data partition
2. If you prefer to go unencrypted, then use F2FS on /data partition
First Time Install / Clean Flash
1. Due to latest changes, is mandatory to use my last TWRP posted below
2. Reboot into recovery mode
3. Go to Wipe --> Advanced Wipe --> Select Data/Cache --> Swipe to Wipe --> Reboot into recovery
4. If you already have /data on f2fs (or ext4 unencrypted) and want stay that way, skip step 5
5. Go to Wipe --> Format Data (internal storage will be wiped too, backup your data) --> Type yes and accept -->
Reboot into recovery
6. Download the ROM and copy it into internal storage
7. Flash the ROM (and magisk if you consider it, but ONLY on EXT4 version, over EROFS will bootloop)
8. Reboot to system
Dirty Flash over previous Evolution X v7.8
NOTE: Do not dirty flash over old versions earlier than v7.8. In that case do a clean flash
1. Due to latest changes, is mandatory to use my last TWRP posted below
2. Reboot into recovery mode
3. Download the ROM and copy it into internal storage. You must use the same version alteady installed (EROFS or EXT4)
4. Flash the ROM (and magisk if is already installed, but ONLY on EXT4 version, over EROFS will bootloop)
5. Reboot to system
Change /cache and /data filesystem from ext4 to f2fs
1. You must format /data partition, so all your data and internal storage will be deleted. Please backup your files
2. Reboot into recovery mode
3. If already encrypted: Go to Wipe --> Advanced Wipe --> Select Cache and Data --> Swipe to Wipe --> Reboot into recovery
4. Go to Wipe --> Format Data --> Type yes and accept --> Reboot into recovery
5. Go to Wipe --> Advanced Wipe --> Select Data --> Repair or Change File System --> Change File System --> F2FS --> Swipe to Change
6. Repeat step 5 but selecting Cache
Change /cache and /data filesystem from f2fs back to ext4
1. You must format /data partition, so all your data and internal storage will be deleted. Please backup your files
2. Reboot into recovery mode
3. Go to Wipe --> Format Data --> Type yes and accept --> Reboot into recovery
5. Go to Wipe --> Advanced Wipe --> Select Cache --> Repair or Change File System --> Change File System --> EXT4 --> Swipe to Change
Hybrid Mode
You can have /cache and /ext4 on different filesystems, so follow previous instructions to put the partitions on your desired filesystem
Download EXT4 version
googledrive / mediafire
MD5: 0b60ab8b443b3c71c341b09bc921bbec
SHA1: f86bcb67e42cdeb89ff30c586c43dd88a7f35669
Download EROFS version
googledrive / mediafire
MD5: b194ede1855579f244eef66854f0aa8d
SHA1: 079a1561c5f4d17500ca20f992a5bdad2ef448a3
Download latest TWRP
googledrive / mediafire
MD5: 5c4845b2f5378abba303688aca000c46
SHA1: a2d71742f2928817fc3426ecba843c50f3cc4291
Android OS version: 13.0.0_r43
Build ID: TQ2A.230505.002
Security patch level: May 05 2023
Build author/Device Maintainer: Huexxx
Source code: EvolutionX GitHub repos
Trees and Kernel: Huexxx GitHub repos
Status: Stable
SELinux Status: Enforcing
Release date: 2023-05-07
Buy me a Beer!
Features / Changelog 2023-05-07
- kernel:
-- Switch to EROFS legacy version (less changes to base 4.4 kernel avoiding possible problems)
-- Switch to Simple Low Memory Killer
-- Add SchedTune and CpuSets Assist
-- Several EAS tweaks
-- Several sched/mm/cpufreq commits
- Source updated (upgraded to android 13.0.0_r43)
Features / Changelog 2023-04-26
- kernel:
-- Backported support for EROFS fs
-- Backported support for Cgroup v2 Freezer
-- Switched to 2SI (two stage init)
-- Added KernelSU support
- Source updated (upgraded to android 13.0.0_r41)
Features / Changelog 2023-03-26
- kernel:
-- Reverted some not wanted commits
-- Some logspam removed
-- Boot time has been reduced by 26 seconds
Features / Changelog 2023-03-07
- Source updates (upgraded to android 13.0.0_r30)
- Kernel: Added several commits regarding EAS and cpufreq
- Trees: Added quota flag to data mount (needed TWRP 3.7.0 with quota support)
- Sepolicy: Address some denials
- Dropped Go version
Features / Changelog 2023-01-28
- Source updates
- New Go version! (with Go Gapps)
Features / Changelog 2023-01-21
- Source updates
- Launcher3:
-- Import widget overlap from Lawnchair
- Kernel updates
- Dropped Flipendo, Turbo and Turboadapter
- Some commits on qcom-caf display hal
Features / Changelog 2023-01-09
- Sources updates
- Switch to OSS libnotifyhal (make proximity sensor work without binder, new lineageos approach)
- Drop vndk-ext packages
- Switch BTAudio to AIDL
- Switch to common fingerprint HIDL
- Config SQLite to operate in MEMORY mode
Features / Changelog 2022-12-28
- Sources updates
-- Switch to EvoX modded Launcher3
- kernel:
-- Some QCom commits
- Downgraded audio and listen blobs to older revision
- Drop Soundtrigger, Renderscript and qti perf stack
- Updated sepolicies
- Misc tweaks
Features / Changelog 2022-12-01
- Fixed problem on latest release (EvoX sources related)
- Update GPS hal and blobs from LA.UM.9.6.3.r1-06200-89xx.0
Features / Changelog 2022-11-29
- Source updates
- kernel:
-- Switch to LLVM tools for compiling
-- Xiaomi updates
-- Backport binder from 5.4-lts
-- Lots of commits/patches
- Updated audio, listen, thermal-engine, display and DRM blobs
- OpenGL ES driver updated to OpenGL ES 3.2 [email protected]
- Updated Display HAL to LA.UM.10.6.2.r1-01900-89xx.0
- Fixed soundtrigger (Ok Google)
- Reenabled thermal-engine
- Lots of thing that I forget now...
Features / Changelog 2022-11-10
- Source updates
- Fixed Night Light
- Fixed LiveDisplay
Features / Changelog 2022-11-08
- Source updates
-- Upgrade to release 13
-- November security patch
-- Readded FaceUnlock
- Screen recorder
-- Limit to 60fps
-- Use AVC 3.2 for performance
Features / Changelog 2022-11-03
- Source updates
- Vendor tree updates
-- Blob cleanup
-- Update ANT+, Bluetooth and PowerOffAlarm blobs
- Avoid dexpreopting prebuilts to save space
- Add more gapps now that system image is smaller
- Add support for Smart Charging
- Replace Pixel Launcher with mod (allow more desktop grids)
- Replace GrapheneOS Camera with latest one from GrapheneOS repos
- Improve selinux policies
Features / Changelog 2022-10-16
- Source updates
Features / Changelog 2022-10-11
- SoftAP:
-- Add list to select Country Code spoof
-- Reenabled ACS
-- Fixed problems disabling hotspot
-- Extend funcionality to QS button
- Fixed DocumentsUI
- Some selinux denials addressed
Features / Changelog 2022-10-08
- SoftAP: Add AP band preference
- Fixed security settings page
- Selinux Enforcing
Features / Changelog 2022-10-06
- Fixed 5GHz hotspot
-- Spoof country code to use US (best option)
-- ACS disabled (it avoids 5GHz bands sometimes)
- Debloated a bit, so many gapps by default
- Added Graphene Camera v16
- Added GoogleCamera to MGC-8.4.300_Parrot043_V1.5
- Selinux permissive atm
Reserved
You are the best Huexxx! Once again, our Mix 2 will be able to enjoy the latest software for another year.
I've been using it for a few weeks now and it works incredibly well. Better performance and battery life than with Android 12.
Is the proximity sensor working properly? Thanks
Yeah, working.
Thanks @Huexxx for your hard work and keeping our Mix 2 alive and up to date!
Hello, I've installed your rom, and it seems to work correctly, but fails the call recording with "Cube recorder" app:
With crDroid rom it worked like a charm, but with this rom, it can record my voice, but not the other side (very bad recording, unusable); I've also tried to install pixelify magisk's module to use its call recording feature, but when I try "record" within a call, it shows "recording failed".
Thanks !
Excellent rom, thank you very much for your great work
PS one question: is it possible to change the carrier name?
rogerty said:
Hello, I've installed your rom, and it seems to work correctly, but fails the call recording with "Cube recorder" app:
With crDroid rom it worked like a charm, but with this rom, it can record my voice, but not the other side (very bad recording, unusable); I've also tried to install pixelify magisk's module to use its call recording feature, but when I try "record" within a call, it shows "recording failed".
Thanks !
Click to expand...
Click to collapse
Take a logcat just after the problem and I can look into it... maybe is selinux related.
Also, A13 is relatively young, and some apps aren't prepared for it.
spoo333 said:
PS one question: is it possible to change the carrier name?
Click to expand...
Click to collapse
IDK man, I haven't navigated through all the settings :/
Thanks for the update
Coming from LineageOS (Android 11) I followed the steps in #1 and updated to recommended TWRP. No problems so far. GPS, NFC, Fingerprint, Bluetooth not tested yet.
SafetyNet pass with Magisk Universal SafetyNet Fix 2.3.1 is working.
P.S. The Quick Settings menu in Android 13 is looking pretty ugly.
ty so much. I cant believe this old device can experience the latest system.
I also come from lineage and I find that the device has become faster with the EvolutionX rom .
Question: Does this unofficial version get any ota updates?
Thanx
rmax78 said:
I also come from lineage and I find that the device has become faster with the EvolutionX rom .
Question: Does this unofficial version get any ota updates?
Thanx
Click to expand...
Click to collapse
It won't probably get OTA updates ever... becuase I'm not planning to make it official.
New release on OP!
@Huexxx Do you plan to release regular (or monthly) updates to all of your 13.0 ROMs (Evolution X, CherishOS, StagOS) in the future?
11insomnium said:
@Huexxx Do you plan to release regular (or monthly) updates to all of your 13.0 ROMs (Evolution X, CherishOS, StagOS) in the future?
Click to expand...
Click to collapse
Yes, I plan to "mantain" them.
Great work, thanks. I wish to have opportunity for automated updates for this ROM installable from settings, or should switch to some other 13 ROM?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: Disclaimer
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CherishOS for Mi Mix 2 [chiron]
* Has a Pixel UI noodles by Hung Phan. So many features that you probably won't find in any ROM. All you can dream of and all you'll ever need. Just flash and enjoy...
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Encryption on f2fs doesn't workInstallation
Choose your flavor
1. You can choose between the traditional EXT4 or the new EROFS. This fs affect only to /system and /vendor partitions
2. Magisk doesn't work on EROFS at the moment. Anyway I've included KernelSU on kernel, so you can install if you want KernelSU app in order to get root and flash magisk modules
3. Once selected root partitions fs, you can choose fs for /data and /cache partitions between traditional EXT4 or F2FS
4. Note that EXT4 comes with encryption by default and F2FS comes unencrypted
Decide if you want encryption or not
1. If you want encryption, use EXT4 on /data partition
2. If you prefer to go unencrypted, then use F2FS on /data partition
First Time Install / Clean Flash
1. Due to latest changes, is mandatory to use my last TWRP posted below
2. Reboot into recovery mode
3. Go to Wipe --> Advanced Wipe --> Select Data/Cache --> Swipe to Wipe --> Reboot into recovery
4. If you already have /data on f2fs (or ext4 unencrypted) and want stay that way, skip step 5
5. Go to Wipe --> Format Data (internal storage will be wiped too, backup your data) --> Type yes and accept -->
Reboot into recovery
6. Download the ROM and copy it into internal storage
7. Flash the ROM (and magisk if you consider it, but ONLY on EXT4 version, over EROFS will bootloop)
8. Reboot to system
Dirty Flash over previous CherishOS v4.7.5 or later
NOTE: Do not dirty flash over old versions earlier than 4.7.5. In that case do a clean flash
1. Due to latest changes, is mandatory to use my last TWRP posted below
2. Reboot into recovery mode
3. Download the ROM and copy it into internal storage. You must use the same version alteady installed (EROFS or EXT4)
4. Flash the ROM (and magisk if is already installed, but ONLY on EXT4 version, over EROFS will bootloop)
5. Reboot to system
Change /cache and /data filesystem from ext4 to f2fs
1. You must format /data partition, so all your data and internal storage will be deleted. Please backup your files
2. Reboot into recovery mode
3. If already encrypted: Go to Wipe --> Advanced Wipe --> Select Cache and Data --> Swipe to Wipe --> Reboot into recovery
4. Go to Wipe --> Format Data --> Type yes and accept --> Reboot into recovery
5. Go to Wipe --> Advanced Wipe --> Select Data --> Repair or Change File System --> Change File System --> F2FS --> Swipe to Change
6. Repeat step 5 but selecting Cache
Change /cache and /data filesystem from f2fs back to ext4
1. You must format /data partition, so all your data and internal storage will be deleted. Please backup your files
2. Reboot into recovery mode
3. Go to Wipe --> Format Data --> Type yes and accept --> Reboot into recovery
5. Go to Wipe --> Advanced Wipe --> Select Cache --> Repair or Change File System --> Change File System --> EXT4 --> Swipe to Change
Hybrid Mode
You can have /cache and /ext4 on different filesystems, so follow previous instructions to put the partitions on your desired filesystem
Download EXT4 version - Vanilla
googledrive / mediafire
MD5: d3566ba4e209c9787475ba03c8de6a3c
SHA1: 658bae71db757c1508dd76e62a1baad42758b881
Download EROFS version - Vanilla
googledrive / mediafire
MD5: e4f61ade8c0c4673ccb1e695a85a644d
SHA1: 6f20c5f42b5061032c5429f71b9a9e3beb108e96
Download EXT4 version - GApps
googledrive / mediafire
MD5: e5d05a9a40db2c48b33708c7e92851df
SHA1: ae69120b7d25cf4cdb7b0889eacb9f4bfbf8769e
Download EROFS version - GApps
googledrive / mediafire
MD5: 5053f017308d9eaf2845089bbe51a06f
SHA1: a84cb0b0c37a7803f89170115ab4fc35c85c770e
Download latest TWRP
googledrive / mediafire
MD5: 5c4845b2f5378abba303688aca000c46
SHA1: a2d71742f2928817fc3426ecba843c50f3cc4291
Android OS version: 13.0.0_r43
Build ID: TQ2A.230505.002
Security patch level: May 05 2023
Build author/Device Maintainer: Huexxx
Source code: CherishOS GitHub repos
Trees and Kernel: Huexxx GitHub repos
Status: Stable
SELinux Status: Enforcing
Release date: 2023-06-10
Buy me a Beer!
Features / Changelog 2023-06-10
- Launcher3:
-- Changed to real modded CherishOS base
-- Switch from Google's Smartspace to Quickspace
-- Option to force monochrome non-themed icons
- ThemePicker:
-- Changed to moded ProtonPlus base
-- Allow color picker on vanilla versions too
- Removed keyguard Google's Smartspace
- Add Omnijaws Weather API
- Add Jelly browser on vanilla version
- Kernel:
-- Update kernelsu
Features / Changelog 2023-05-09
- Source updated
- Fixed Wallpaper & Style (basic colors)
Features / Changelog 2023-05-06
- kernel:
-- Switch to EROFS legacy version (less changes to base 4.4 kernel avoiding possible problems)
-- Switch to Simple Low Memory Killer
-- Add SchedTune and CpuSets Assist
-- Several EAS tweaks
-- Several sched/mm/cpufreq commits
- Source updated (upgraded to android 13.0.0_r43)
Features / Changelog 2023-04-27
- kernel:
-- Backported support for EROFS fs
-- Backported support for Cgroup v2 Freezer
-- Switched to 2SI (two stage init)
-- Added KernelSU support
- Source updated (upgraded to android 13.0.0_r41)
Features / Changelog 2023-03-26
- kernel:
-- Reverted some not wanted commits
-- Some logspam removed
-- Boot time has been reduced by 26 seconds
Features / Changelog 2023-03-09
- Source updates
- Encryption fixed!
Features / Changelog 2023-03-07
- Source updates
- Temporary removed forced encryption from device trees
Features / Changelog 2023-03-06
- Source updates
- ReAdded option to install custom themed icon packs for Launcher3
- Kernel: Added some commits regarding EAS and cpufreq
- Some adjusts in a try to make encryption work
- Sepolicy: Address some denials
Features / Changelog 2023-03-01
- Source updates (upgraded to android 13.0.0_r30)
- Removed the option to install additional themed icons from Launcher3 (I'll study to return it)
- Some kernel commits
- Some device tree commits
Features / Changelog 2023-01-28
- Source updates
Features / Changelog 2023-01-20
- Source updates
- Launcher3:
-- Bring back 'At a Glance'
-- Import widget overlap from Lawnchair
- Kernel updates
- Gapps slimming diet (many apps have been dropped)
- Some commits on qcom-caf display hal
Features / Changelog 2023-01-19
- Source updates
- Improved sepolicies
- Imported Launcher3 from EvoX:
-- Adapted to work with CherishOS
-- New app icon and modified name
-- Removed 'At a Glance' due to CherishOS sources
-- (I'll try to restore it)
Features / Changelog 2023-01-17
- Source updates
- Improved sepolicies
Features / Changelog 2023-01-10
- Sources updates
- Switch to OSS libnotifyhal (make proximity sensor work without binder, new lineageos approach)
- Drop vndk-ext packages
- Switch BTAudio to AIDL
- Switch to common fingerprint HIDL
- Config SQLite to operate in MEMORY mode
Features / Changelog 2022-12-28
- Sources updates
- Downgraded audio and listen blobs to older revision
- Downgraded display drivers to fix camera problems
- Drop Soundtrigger, Renderscript and qti perf stack
Features / Changelog 2022-12-01
- Source updates
- kernel:
-- Switch to LLVM tools for compiling
-- Xiaomi updates
-- Backport binder from 5.4-lts
-- Lots of commits/patches
- Updated audio, listen, thermal-engine, display and DRM blobs
- OpenGL ES driver updated to OpenGL ES 3.2 [email protected]
- Updated Display HAL to LA.UM.10.6.2.r1-01900-89xx.0
- Update GPS hal and blobs from LA.UM.9.6.3.r1-06200-89xx.0
- Fixed soundtrigger (Ok Google)
- Reenabled thermal-engine
- Many more...
Features / Changelog 2022-11-10
- Fixed Night Light
- Fixed LiveDisplay
Features / Changelog 2022-11-09
- Source updates
Features / Changelog 2022-11-08
- Source updates
-- Upgrade to release 14
-- November security patch
-- Readded FaceUnlock
Features / Changelog 2022-11-03
- SoftAP:
-- Add AP band preference
-- Add list to select Country Code spoof
-- Extend funcionality to QS button
- Added GrapheneOS Camera v56 from GrapheneOS repos
- On GApps version:
-- Replace Pixel Launcher with mod (allow more desktop grids)
-- Added GoogleCamera to MGC-8.4.300_Parrot043_V1.5
- Selinux Enforcing
reserved
OP Updated.
OP Updated-
OP Updated!
OP Updated!
Man I'm so glad someone hasn't given up on this phone. It's pretty awesome with how thin and lightweight is. I've got the Mix3 and it's a heavy brick. Thanks for keeping the Dev going. Definitely going to download and give it a shot.
OP Updated.
have this rom installed(latest), gps green light is always on. and it says that its being used by google play services.and it cant be disabled. or there is any option to disable it?
one more bug found:
when i'm trying make(not to attach existing one) and send photo in Telegram or WhatsApp - it hangs.
when i'm trying make(not to attach existing one) and send photo in Telegram or WhatsApp - it hangs.
Same result for me. Video clip is recording and available for editing (via long tap), but when trying to make photo - Telegram hangs just after the tap and the flash fires.
OP updated!
Huexxx said:
OP updated!
Click to expand...
Click to collapse
Hi, Google drive link for GAPPS image seems to be broken for me. Thanks for updates
Have you checked sha1 or md5 hashes?
Have you managed to download from mediafire?
Is the first complain in that way so maybe is an isolated problem...
If someone else reports the same I'll re-upload it.
Huexxx said:
Have you checked sha1 or md5 hashes?
Have you managed to download from mediafire?
Is the first complain in that way so maybe is an isolated problem...
If someone else reports the same I'll re-upload it.
Click to expand...
Click to collapse
I've downloaded and installed image from Mediafire - it's OK.
Link from Google Drive - it says error "File not found" - so I can't even check it.
Strange, I've just downloaded it from link without problems... maybe it was an isolated problem.
I faced a problem but solved it.
I had the official CherishOS (Android 11) for chiron installed with the latest official TWRP for chiron. When I installed the Nanhumly built TWRP it couldn't decrypt. So I went back to the official TWRP and flashed this CherishOS (Android 13) with NikGapps and Magisk. It installed and system booted up alright. When I went back to recovery, now the official TWRP couldn't decrypt. So I flased the Nanhumly build and it could decrypt now.
So I figured that the official one works up to Android 11 and the Nanhumly build is for 12 and above. I'm a n00b so this is a revelation for me. That's why I'm sharing the experience for fellow n00bs.
Great build Huexxx. It's running smoothly. I'll report back after few days of use.
Happy New Year! Cheers!
picchishaitan said:
I faced a problem but solved it.
I had the official CherishOS (Android 11) for chiron installed with the latest official TWRP for chiron. When I installed the Nanhumly built TWRP it couldn't decrypt. So I went back to the official TWRP and flashed this CherishOS (Android 13) with NikGapps and Magisk. It installed and system booted up alright. When I went back to recovery, now the official TWRP couldn't decrypt. So I flased the Nanhumly build and it could decrypt now.
So I figured that the official one works up to Android 11 and the Nanhumly build is for 12 and above. I'm a n00b so this is a revelation for me. That's why I'm sharing the experience for fellow n00bs.
Great build Huexxx. It's running smoothly. I'll report back after few days of use.
Happy New Year! Cheers!
Click to expand...
Click to collapse
Exactly, I recommend in my op to use nanhumly's build to use encryption (or not).
OP Updated!
NOTE: I haven't tested this build by myself, so make a backup prior to flash it.
Tried out 2023-01-10 (Vanilla)
That camera issue seems to be fixed.
For some reason the the CherishOS Launcher has been removed and replaced with a plain .launcher3 launcher. (No customizing settings available)
Does any one know where I can get an APK for the CherishOS Launcher? (Was available in 2022-12-01)
Edit: As an added benefit of the new launcher is that it is compatible with any Launcher that has Quickswitch support. So I was able to install the latest Lawnchair 12.1 dev and still have working gestures