Database Info

[ROM][7.1][UNOFFICIAL][MSM8610][CUSTOM] LineageOS 14.1 for LG L FINO - LG L Fino ROMs, Kernels, Recoveries, & Other Devel

{
"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"
}
LineageOS 14.1 FOR LG L FINO​
NOTICE: THE DEVELOPERS OF THIS ROM DO NOT SHARE ANY RESPONSIBILITY FOR DAMAGED DEVICES, AFTER INSTALLING, OR IN THE PROCESS OF INSTALLING THIS SOFTWARE. MODIFYING YOUR DEVICE IN ANY WAY VOIDS YOUR WARRANTY. PLEASE CONTINUE AT YOUR OWN RISK.​
SUPPORTED DEVICES
LG L70pn (D290n)
LG L70pds (D295)
FEATURES
All the device hardware is fully supported and working
Official LineageOS's Snap camera application and Jelly web browser
Adoptable Storage support
Doze mode
CUSTOM FEATURES
Substratum Theme Engine support
MicroG support
Custom kernel with Upstream additions and several security fixes
Custom PowerHAL, based on Nick D2's PowerHAL for msm8226 devices.
F2FS formatted /data partition
Sony's DASH open source sensor library
CODE REPOSITORIES
KERNEL: https://github.com/geekydoc/android_kernel_lge_msm8610/tree/cm-14.1-advance
DEVICE: https://github.com/geekydoc/android_device_l70pn/tree/cm-14.1 and https://github.com/geekydoc/android_device_l70pds/tree/cm-14.1
BUG REPORTING
If you find a bug, please report it by posting a reply on this forum thread. Always try to include a logcat in your bug report. If an App misbehaves, take the logcat while that App is open and you try to reproduce the issue. You can learn how to get a logcat here.
FIRST TIME INSTALLATION INSTRUCTIONS
Backup sensitive data
Get and install TWRP for your device variant, see this thread and DOWNLOADS section below for TWRP recovery images with full F2FS support
Obtain the latest zip from the DOWNLOADS section below
Do a full wipe before installing. On TWRP, go to Wipe -> Advanced Wipe and select ART Cache, Data, Cache, System. If you were using Adoptable Storage on a previous ROM, it won't get recognized by the new ROM, in this case select External Storage too. This will erase all the data stored on your SD card.
Flash the zip using TWRP
Go back to the main recovery screen, then go to Wipe -> Advanced Wipe -> Select data partition only -> Repair or Change -> Change Filesystem -> F2FS
Reboot and enjoy
DOWNLOADS
Latest build is: lineage-14.1-20190112-UNOFFICIAL
Latest builds can be downloaded from the links below:
L70PN: https://mega.nz/#!49oFQACQ!_Hd_JvD5L5W2WnnEgY6IeoZOR3UYNC-086U65XpNLlA
L70PDS: https://mega.nz/#!15gl0YjT!439KVpJpLWO2CX8AklF6LPPrOPXLBcWrGVCn-yTQrS0
TWRP 3.1.0 recovery images, with full F2FS support and based on the project's custom kernel:
L70PDS:https://mega.nz/#!Y8BQVLyQ!h1WDBc9MUkXKqNHC_Z70KuoXhHhf-i-t4IEHa8i3xLc
L70PN:https://mega.nz/#!8gY1VIiR!jMcbcBpcbMhfy8qgjrY1MFZRKu2mpemJnquwiTy-564
Boot Images with inverted storage | Last Updated: 19/01/2019
Install these boot images if you want to use your external Micro SD card as the data partition. Internal data partition will not be available if you install these boot images. Your Micro SD card must have only one partition formatted in f2fs filesystem. You can install these images through TWRP recovery (make sure you have the latest version installed, as previous versions have a bug when installing .img files). Also make sure you install the boot image after installing the ROM zip.
You will have to re-flash the inverted memory boot image after every ROM update.
To install the boot image through TWRP, go to Install->Install Image->Select the image file->Select boot->Flash.
L70PN:https://mega.nz/#!b3o3CS7D!4xVC1avDGKvzhzFH6ZVaRC7WPV4yAMaeQZFD8c42yjA
L70PDS:https://mega.nz/#!b3o3CS7D!4xVC1avDGKvzhzFH6ZVaRC7WPV4yAMaeQZFD8c42yjA
EXTRA DOWNLOADS
AddonSU : Use this to enable Super User access. Flash through TWRP recovery.
OpenGApps : Use this to enable Google Apps and Google Play Services on your ROM. Due to insufficient system partition free space, only pico package can be installed. Select ARM->7.1->pico. Flash through TWRP recovery.
Substratum Theme Engine : Install this application if you want to use Substratum Themes. It can work rootless on this ROM.
GUIDES [External Links]
Decrease Cache partition size to make room for more applications on internal storage
SPECIAL THANKS
@g-pl for contributing to the kernel/device code
@D1stRU3T0R for helping syncing the kernel with latest upstream version
@FaBMak and @Arcline for providing translations for the Update Notifications application
@mountaser halak for conducting stress tests for the PowerHAL and for building flashable zips for this project
@proudlytm for testing and bug reporting and building the TWRP recovery for L Fino
@Quarx2k for the msm8226 kernel
@vm03 for his work on getting CyanogenMod on msm8610 devices
The CyanogenMod/LineageOS team
XDA:DevDB Information
UNOFFICIAL LineageOS 14.1 PORT FOR LG L FINO, ROM for the LG L Fino
Contributors
christpp, mountaser halak, g-pl, proudlytm
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2016-12-06
Last Updated 2019-02-10

CHANGELOG:
Also checkout the official distribution Changelog
lineage-14.1-20190112-UNOFFICIAL
Sync with LineageOS/Substratum Sources
Kernel: Add Kernel Mode NEON Support
Kernel: Crypto: Add NEON optimized SHA1, SHA512, SHA256 and AES routines
Kernel: Binder: Disable preemption while holding the global Binder Lock
lineage-14.1-20181221-UNOFFICIAL
Sync with LineageOS/Substratum Sources
Kernel: sched/fair: Implement fast idling of CPUs when the system is partially loaded
lineage-14.1-20181012-UNOFFICIAL
Sync with LineageOS/Substratum Sources
lineage-14.1-20180705-UNOFFICIAL
Sync with LineageOS/Substratum Sources
lineage-14.1-20180506-UNOFFICIAL
Sync with LineageOS/Substratum Sources
Kernel: Address around 30 CVEs
System: Enable cpuset CGROUP support
lineage-14.1-20180315-UNOFFICIAL
Sync with LineageOS/Substratum Sources
Kernel: dm-crypt: Multi-Proccessor/Parallelization Patch Backport
Kernel: sched: Do not schedule realtime tasks on CPUs currently servicing Interrupts.
Kernel: GPU: Fix some direct references to HZ
Kernel: Disable Intelli-hotplug
System: Build.prop: Enable 'sys.use_fifo_ui' property
System: Switch the external SD card I/O scheduler back to BFQ
System: Media Codecs: Use Google's decoder for MP3 files
lineage-14.1-20180217-UNOFFICIAL
Sync with LineageOS/Substratum Sources
Kernel: Scheduling updates for some low-latency functions on GPU, mmc and crypto
lineage-14.1-20180127-UNOFFICIAL
Sync with LineageOS/Substratum Sources
Kernel: Fix 20 more CVEs
Kernel: Set HZ to 500 and enable CONFIG_SCHED_HRTICK
System: Audio: Disable audio offload
lineage-14.1-20180104-UNOFFICIAL
Sync with LineageOS/Substratum Sources
Kernel: Fix 20 more CVEs
Kernel: Revert "Remove CPU boost on interrupt/wakeup"
Kernel: Tweak Virtual Memory management
lineage-14.1-20171205-UNOFFICIAL
Sync with LineageOS/Substratum Sources
Kernel: Fix a bunch of CVEs
System: Reduce ART Heap sizes
lineage-14.1-20171109-UNOFFICIAL
Sync with LineageOS/Substratum sources
Kernel: Remove CPU boost on interrupt/wakeup
Kernel: Enable Westwood+ TCP congestion algorithm and set as default
Kernel: Fix a number of CVEs
System: Enable microG support
System: Update Notifications: Add Bulgarian translation and update strings.
lineage-14.1-20171012-UNOFFICIAL
Sync with LineageOS/Substratum sources
Kernel: GPU: Overclock to 480MHz
Kernel: block: Introduce ZEN I/O Scheduler
Kernel: Disable some USB driver debug code
Kernel: HZ: Set CONFIG_HZ to 300
Kernel: defconfig: Enable CONFIG_CCSTACK_PROTECTOR_STRONG
Kernel: Address multiple CVEs
System: Overlay: CarrierConfig: Enable config_enable_mms_with_mobile_data_off
lineage-14.1-20170926-UNOFFICIAL
Sync with LineageOS/Substratum sources
Kernel: Sync with upstream v3.4.113
Kernel: F2FS: Disable CONFIG_F2FS_CHECK_FS
System: Dialer: Change recording stream
lineage-14.1-20170818-UNOFFICIAL
Sync with LineageOS/Substratum sources
System: Update Notifications: Fix translations
lineage-14.1-20170727-UNOFFICIAL
Kernel: Cpufreq: Introduce 192 MHz core frequency
System: Enable full Substratum theme engine support
System: PowerHAL: Get back to using Interactive governor
System: Update Notifications: Add pt-BR translation (credit to @FaBMak)
lineage-14.1-20170711-UNOFFICIAL
System: ART: Enable interpret-only filter to reduce vm cache size
System: Mixer_paths: Camcorder: Use speaker-mic for audio recording
System: Update Notifications: Move to System Settings and simplify code
L70pds: Cleanup system apps
lineage-14.1-20170703-UNOFFICIAL
Sync with LineageOS sources
Kernel: Introduce and enable PegasusQ cpu governor
Kernel: Multiple CVEs fixed
System: Set external SD card I/O scheduler to ROW
System: Change cache partition type back to ext4
SystemowerHAL: Configure for PegasusQ governor
lineage-14.1-20170606-UNOFFICIAL
Sync with LineageOS sources
Kernel: Fix potential refcount leak in su check
Kernel: Fix multiple security holes / buffer overflows
lineage-14.1-20170518-UNOFFICIAL
Kernel: Only expose su when daemon is running
Kernel: f2fs: Sync with upstream f2fs-stable 3.10.y [taken from g-pl's kernel repository]
System: Change cache and data partitions to f2fs
System: Kill Gello Browser and introduce Jelly as an alternative lightweight browser
System: Introduce Update Notify Service
NOTICE: A full wipe and manual format of cache and data partitions to f2fs is needed to boot this package. See this post
lineage-14.1-20170503-UNOFFICIAL
CMActions: Add option to pulse only if device is on a flat surface
System: Reduce camcorder mic volume to limit sound distortion
System: FS: Change Cache partition to F2FS.
lineage-14.1-20170419-UNOFFICIAL
Sync with LineageOS repositories
lineage-14.1-20170405-UNOFFICIAL
System: Disable Sony's Timekeep
CMActions: Move to Display Settings and cleanup the code (based on official motorola_msm8226 commits)
lineage-14.1-20170314-UNOFFICIAL
Kernel: Set cpu input boost frequency to 787 MHz
Kernel: Switch back to simplified version of intelli-plug
lineage-14.1-20170308-UNOFFICIAL
System: Enable Sony's Timekeep
Sensors: Use Sony's DASH sensor HAL
Kernel: Introduce simple hotplug daemon
lineage-14.1-20170221-UNOFFICIAL
Kernel: Enable SDcardFS support
Kernel: Enable F2FS and sync with upstream stable 3.4.y
Kernel: ZRAM and ZSMALLOC: rebase from 3.15
Kernel: Enable Linaro's Power Efficient Workqueues
Kernel: Improvements on GPU and lowmemorykiller
Kernel: Enable CONFIGFS filesystem
System: Fix Fm recording
System: Enable FFmpeg Codecs [FLAC support]
System: ZRAM: Switch to lz4 compression, use multiple cores if needed
lineage-14.1-20170213-UNOFFICIAL
Kernel:intelli_hotplug: Run all work on a single, freezable workqueue with one worker.
System: Re-enable FMRadio app
lineage-14.1-20170209-UNOFFICIAL
Rebrand to LineageOS since CyanogenMod is now abandoned.
Kernel: ext4: Multiple bug-fixes/backports
Kernel: Resolve possible deadlocks in scheduler and cpu-boost driver.
Overlay: Change doze pulse timings and increase ambient display fade-out time to avoid possible kernel hangs.
cm14.1-20161206-UNOFFICIAL
Initial build

SD CARD FORMATTING/SPEED TWEAKING GUIDE
​
NOTICE: I WILL NOT SHARE ANY RESPONSIBILITY FOR BROKEN DEVICES OR SD CARDS, OR LOST DATA AS A RESULT OF FOLLOWING THIS GUIDE. PLEASE CONTINUE AT YOUR OWN RISK.​
Before reading this, please keep in mind that the L Fino seems to be not powerful enough to handle adoptable storage easily. This is a hardware limitation rather than a software one. So, getting a huge SD card and trying to extend the internal storage by adopting it won't get the job done. Google's adoptable storage mechanism is actually really heavy for devices, even devices more capable than the L Fino can't cope with it. There are though some tweaks that might get adoptable storage performance more acceptable.
PART 1 : FORMATTING THE SD CARD AS ADOPTABLE
I will describe a procedure that involves giving commands to the device through a shell, everything can be done either through adb or through a terminal app on the device. Root privilledges will be needed. Be warned that after this procedure you will loose all the data on the SD card, so backup any important data.
Open an adb shell or the terminal app on your device.
The android partition tool needs to find an empty partition table on the SD card, otherwise it will break and the re-partitioning will never be completed. Issue the following command to become superuser:
Code:
su
Now, give the following command to enter the fdisk utility, with the SD card selected:
Code:
fdisk /dev/block/mmcblk1
Fdisk will provide its own command prompt. There, to create an empty partition table, issue:
Code:
o
Then, to write changes to the disk issue:
Code:
w
Reboot the device so the kernel will read the new partition table
Re-enter an adb shell or the terminal app
Issue the following commands:
Code:
su
Code:
sm list-disks adoptable
Checkout the output. It should only output one line, which contains the disk label for the SD card. Let's assume this label is 'disk:179_128'
On this stage there are two things you can do:
Convert the whole SD card to adoptable
Convert a part of the SD card to adoptable, leaving the rest as portable
I would advice going with the second option, because it has some advantages: It leaves space for putting rom zips and other flashable files on the portable storage, which is the only one that TWRP recovery can currently read and also makes it possible to have music and other documents on the portable storage. Portable storage is always read faster than adoptable.
So, if you want to convert the whole SD card to adoptable, issue this command:
Code:
sm partition <DISK_LABEL> private
where <DISK_LABEL> is the output of the previous command, in our example 'disk:179_128' , so the command becomes sm partition disk:179_128 private
Otherwise, if you want a dual partitioning, issue this:
Code:
sm partition <DISK_LABEL> mixed <PERCENTAGE_OF_PORTABLE_STORAGE>
<DISK_LABEL> should be replaced as above and <PERCENTAGE_OF_PORTABLE_STORAGE> is the whole SD card space percentage that will be given to portable storage. For example, if I need 80% of my SD card to become portable, the command will become : sm partition disk:179_128 mixed 80
Check the output of the above commands. If they do not output anything, it means that the procedure was successfull. Otherwise, you will have to retry everything from the beginning.
Reboot the device and it should recognise the partitions.
PART 2. TWEAKING KERNEL SETTINGS TO GET ACCEPTABLE PERFORMANCE
There are many factors that can affect the performance of adoptable storage, including the number of apps installed on it, the type of apps, the SD card speed rating and the SD card size. On the kernel side, there are some variables that can be tweaked which could lead to better performance. The ideal values for these variables also depend on the above factors, so they actually are specific on each "device setup". If you are interested in finding the best values for your usage purposes, you will have to experiment by changing these values yourself.
Kernel I/O scheduler:
This rom comes with BFQ I/O scheduler enabled at boot. This is the scheduler used by official LineageOS roms and it can handle normal loads adequatelly. It was enabled at some point on cm-13.0 on our device, and actually improved device responsiveness a lot. That though does not mean that it is the best scheduler for each use case. Other available schedulers on the current kernel are: noop, deadline, row, cfq, fiops . If you want to try a kernel I/O scheduler that is not available in the current kernel, please open a feature request and I will add it.
To change the scheduler, you can use one of the available apps on the play store, or from the terminal (as superuser):
Code:
echo 'scheduler' > /sys/block/mmcblk1/queue/scheduler
where 'scheduler' is the scheduler name.
Code:
cat /sys/block/mmcblk1/queue/scheduler
gives the currently selected scheduler (the one included in "[ ]").
Each kernel I/O scheduler has its own variables that can be changed at runtime.
A guide that describes kernel I/O schedulers and what each scheduler-specific variable does can be found here . This guide also describes read ahead buffer, discussed below.
Read Ahead Buffer:
This is a cache of files opened recently and it is used to speed up opening them again if needed. The ideal value for this variable depends mainly on the SD card size. This rom has the value set by default to 2048 KB. Note that larger Read Ahead Buffer does not mean better performance. Performance is limited at very high values and might even drop significantly. If the value is set too high it might cause read/write errors and reduce the SD card lifetime.
To change the read ahead buffer, you can use an app from the play store , or from the terminal (as superuser):
Code:
echo 'size' > /sys/block/mmcblk1/queue/read_ahead_kb
where 'size' is the size in kilobytes
That is all that I am currently aware of about the adoptable storage subject. I will update the post if I have something new to share.
If somebody has some more information to share for tweaking adoptable storage, please share it with us and I will update the post.
Thank you

Wow that was quick!
Screenshots!!

A few things I've noticed:
#1: Not able to install apks through CM file manager. But it works in ES File Explorer
#2: might not be related to the ROM, but in Allo, while in the chat window, any notification received comes out like a distorted radio noise.

Ky$h said:
A few things I've noticed:
#1: Not able to install apks through CM file manager. But it works in ES File Explorer
#2: might not be related to the ROM, but in Allo, while in the chat window, any notification received comes out like a distorted radio noise.
Click to expand...
Click to collapse
Hey, thanks for testing this and reporting issues! I have these issues too and I believe that they are CyanogenMod bugs. I will take a look at the Github repos to find some more information about these. If they are device-specific, I will try to resolve them.
Also, your screenshots have been included the first post, thank you

My friend have this phone, how I can open his bootloader whitous sd card, and how I can install this ROM? (maybe I'm not the only one who want to know)

D1stRU3T0R said:
My friend have this phone, how I can open his bootloader whitous sd card, and how I can install this ROM? (maybe I'm not the only one who want to know)
Click to expand...
Click to collapse
http://forum.xda-developers.com/d290n/how-to/megathread-lg-l-fino-root-roms-mods-t3310862 :good::good::good:

RESURRECTION REMIX V5.8.0 FOR LG L FINO for l fino is out its based on cm14.1
link to the thread
http://forum.xda-developers.com/d290n/development/rom-resurrection-remix-v5-8-0-lg-l-fino-t3514725

mountaser halak said:
RESURRECTION REMIX V5.8.0 FOR LG L FINO for l fino is out its based on cm14.1
link to the thread
http://forum.xda-developers.com/d290...-fino-t3514725
Click to expand...
Click to collapse
Page not found, fix it

D1stRU3T0R said:
Page not found, fix it
Click to expand...
Click to collapse
sorry for that
try it now
http://forum.xda-developers.com/d290n/development/rom-resurrection-remix-v5-8-0-lg-l-fino-t3514725

@christpp, you mada a very strange ROM. No bugs so far!

cm 14.1 is ready, great news! :good:
Ky$h said:
A few things I've noticed:
#1: Not able to install apks through CM file manager. But it works in ES File Explorer
#2: might not be related to the ROM, but in Allo, while in the chat window, any notification received comes out like a distorted radio noise.
Click to expand...
Click to collapse
A have file manager bug on other phone running cm 14.1 too so it's not specific to our phone only.

News. About once per day, my phone shuts down and I have to pull out the battery. L70PN version.
PS. I will try to access it from adb, but I am never home when this happens.

gpopac said:
News. About once per day, my phone shuts down and I have to pull out the battery. L70PN version.
PS. I will try to access it from adb, but I am never home when this happens.
Click to expand...
Click to collapse
Strange. Never happened to me. Did you dirty flash it?

No, it was a clean install, with everything reformatted. Maybe adoptable storage is to blame for this? I just started using it.
What partition scheme are you using, the default one or the one used for CM 13 with more space for system and data?

gpopac said:
No, it was a clean install, with everything reformatted. Maybe adoptable storage is to blame for this? I just started using it.
What partition scheme are you using, the default one or the one used for CM 13 with more space for system and data?
Click to expand...
Click to collapse
The default one

I’ll try to reformat partitions, although there seems to be enough space with this layout on every partition.
EDIT. It didn’t help. I will try to remove adoptable storage. Maybe my MicroSD is bad. Here is my logcat, maybe something is usefull, but I just don’t see it...

gpopac said:
I’ll try to reformat partitions, although there seems to be enough space with this layout on every partition.
EDIT. It didn’t help. I will try to remove adoptable storage. Maybe my MicroSD is bad. Here is my logcat, maybe something is usefull, but I just don’t see it...
Click to expand...
Click to collapse
Hey,
This behavior is caused by a kernel deadlock. It is introduced by the changes made to the kernel in order to enable kernel-based power and cpu hot-plugging management. The kernel deadlocks when the phone is coming out from suspend. Phone is working normally until the power button is pressed to get it out of suspend (I think this won't affect phone calls coming in, I would not rely on the phone for an alarm though ). When this happens, it is sometimes possible to make the phone reboot by holding the power button for some time. Till now, I haven't been able to sort out where in code this deadlock is arising from. I am in the process of backporting/upgrading kernel code to get this fixed. I have already patched many potential deadlocks in kernel code.
A new release will be built when I manage to get this fixed (hopefully soon).
Thank you

Thanks christpp! I was going to blame the new kernel, since the problem reoccurred after disabling the adoptable storage. I think this line explains the problem:
Code:
W libsuspend: Error writing 'on' to /sys/power/state: Invalid argument

Related

{
"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"
}
Mounts2SD - Storage & Memory Management
Mounts2SD started out as a simple sd-ext script which only difference between it an others like it, was that it did not use symlinks to create links between /data and /sd-ext. To day it has grown to be so much more. It now comes packed with an Application for controlling the script, viewing current states and more. The script itself has grown to become a large storage and management script with features that controlls SWAP, ZRAM, mount optimization, storage thresholds, different external and internal MMC configurations, cache and more. The content management is able to move a lot more different content between /data and /sd-ext, including the new internal storage, which on some devices, is placed in /data/media, and it also contains more than one option for storing system content on both /data and /sd-ext.
Mounts2SD is no longer just a script for devices with low storage capabilities. It can be used for a lot of things and is useful on almost any device, even those without external sdcard.
Links
The Source -> Go There
Documentation and Important Information -> Go There
Supported Languages
English
Danish
French (By @PerfectSlayer)
Dutch (By @Skippernl)
Portuguese (By @_MarcoMarinho_)
Italian (By @GMagician)
Hungarian (By @@steveboy25)
Upcoming Features
Since DevDB has future requests capabilities, I will keep a list here of planned/deciding features to avoid repeating requests.
Application Manager with fallowing options:
Convert/Revert regular applications to/from system applications
Status: Done
View and Clear Application Caches
Status: Pending
Manually kill the application
Status: Deciding (does not fit the Storage and Memory management category)
Downloads
Google Play
Install directly from Play Store
===========================
3.4.8 (6.0.20) APK (Nov 01, 2013)
[Default Mirror] SourceForge.net
This is the Application which can be installed directly on the phone
-------------------------------------------------
3.4.8 (6.0.20) Recovery ZIP (Nov 01, 2013)
[Default Mirror] SourceForge.net
This is the Recovery Package for when updating the ROM on an M2SD configured device
Older Downloads
2.2.0 (5.5.0) APK (Jan 26, 2013) (MD5: dd54ace01d9b17c72081a06cd1d072c7)
[Default Mirror] SourceForge.net
[Default Mirror] MediaFire.com
This is the Application which can be installed directly on the phone
-------------------------------------------------
2.2.0 (5.5.0) Ext4 ZIP (Jan 26, 2013) (MD5: 80c218ff53009c8a0ccde1927361def2)
[Default Mirror] SourceForge.net
[Default Mirror] MediaFire.com
This will provide you with an recovery ZIP for newer Ext4 devices
Does not have the file /proc/mtd
-------------------------------------------------
2.2.0 (5.5.0) MTD ZIP (Jan 26, 2013) (MD5: 4762d7d85c9cd934f97ba3ba36294fdd)
[Default Mirror] SourceForge.net
[Default Mirror] MediaFire.com
This will provide you with an recovery ZIP for older MTD devices
Will have the file /proc/mtd
Change Log
Version: 3.4.8
Added Hungarian translation by @steveboy25
Preferences: Fix nullPointerException issue
Upstart Script: Fix boot issues on a few devices
Older Change Log
Version: 3.4.6
Update RootFW
Script/App: Add busybox fail-safe
Tab Controller: Do not crash on IllegalStateException
Update Italian messages translation by @GMagician
Version: 3.4.4
Startup Script: Try default busybox as fallback if the runner selected one fails
Preferences: Fix another reported crash while loading configurations
EventHandler: Fix reported crash
Preferences: Fix reported crash while loading configurations
Fix internal busybox being restored on boot even thought it was removed
Upstart Script: Only unmount pre-mounted sd-ext if not on /data
Update Italian messages translation by @GMagician
Version: 3.4.2
Fix bug when sd-ext is not mounted
Fix typo which breaks IMMC configs on MTD devices
Fix reported nullPointerException crashes
RootFW: Fix nullPointerException crash on extensive loading
RootFW: Do not try to destroy a null property
Version: 3.4.1
Major rewrite
Complete rewrite of the entire application
Updated RootFW (Library)
Updated TaskManager (Library)
Added Debug File builder to the log tab
Added separate configure option for converted system applications
Minor typo fix in default locale by @GMagician
Italian translation updated to 3.3.2 by @GMagician
Version: 3.3.4
Fix sqlite3 installer to avoid boot loops
Replaced the binary and removed replacment of the libraries (They are kernel specific)
Handle old reversed mount from within the application
Is also handled by the script, but in case someone changes the configurations before rebooting after upgrading from the 2.x app, we need to have this handled before that
Version: 3.3.2
Fix reported crashes
Version: 3.3.0
Settings: Fix a few small bugs
Translated V3.2.0 new messages+some improvements by @GMagician
Add new App Manager
Used to convert apps into system apps and revert them back. No apps are moved to /system, but instead moved between /data/app and /data/app-system
Note that this feature is a paid feature. The downloads at XDA are unlocked, but installs and updates from Play Store is not
Settings: Add fallback installs for S-On devices
Uses the recovery as a fallback installer for the script and sqlite in case of HTC S-On protection
RootFW: Rebuild Instance Extender
Fixes a small issue where the shell was not always connected after boot on the first app launch
Version: 3.2.0
Add Italian translation by @GMagician
Preferences: Avoid using RootFW.Filesystem.statFstab if possible
RootFW.Filesystem.statMount is faster
Upstart Script: Fix a few shell bugs in environment setup
Possible boot loop cause
Settings: Cleanup script installer
Should fix the issue with the script not always getting installed
Settings: Add SQLite3 installer
New feature to install and/or fix the SQLite3 binary
RootFW: Do not use goldfish files on non-emulator devices
Avoid having wrong partitions located and recovery cleaned
Version: 3.1.8
Add Portuguese translation by @_MarcoMarinho_
Allow translating tab names for tablet layout
In tablet layout, there is text displayed for each tab. This should also be translated
Update English language file
Small corrections
Add missing tablet layout tab names strings
Add Danish translation
Settings: Allow translating upstart script info
Also display words like 'Versions', 'Bundled' and 'Installed' in Application Settings
Upstart Script: Fix not detecting folder suppport
Fix issue where the Application alerts about some Data folders not being moved
RootFW: Fix nullPointerException when no SWAPS are active
Issue where the Application would crash if no SWAP or ZRAM device was activated
RootFW: Fix hanging issues with Kutch SuperUser Daemon mode for Android 4.3
Bug in the SuperUser Daemon which would make some Shell types hang randomly
Version: 3.1.4
Added Dutch translation by @Skippernl
Upstart Script: Handle empty values better
Reset properties if their values are empty
Better log entry structure to better detect empty property values
RootFW: Fix write() not working
Bug in the write() method was causing empty values to be written to the property files
RootFW: Fix ArrayIndexOutOfBoundsException issue
Would sometimes cause a crash when getting stats on none existing directories
Version: 3.1.2
Update french locale and fix default one by @PerfectSlayer
Use the correct strings in the infobox
Display a log announcment instead of safe-mode information when there are warnings/errors in the log
RootFW - Fix java divide by zero Exception
Was causing crash when calculating usage percentage on partitions with 0 bytes used
Make better compatibility between different devices and ROM's
Revert Busybox binary
Create a more controlled environment to have the script executed in
Better variable export feature
Change temp dir /tmp ~> /mounts2sd-tmp
To fix issues where a ROM clears /tmp after boot
Generate more logging to help debug issues
Now generates both the regular /mounts2sd-tmp/log.txt and /data/local/mounts2sd.log which is not deleted on device shutdown
Click to expand...
Click to collapse
XDA:DevDB Information
Mounts2SD, a App for the No Device
Contributors
dk_zero-cool, PerfectSlayer, Skippernl, _MarcoMarinho_, GMagician
Version Information
Status: Stable
Current Stable Version: 3.4.8
Stable Release Date: 2013-11-01
Created 2013-09-04
Last Updated 2013-11-01

Reserved

Good job. And by the way u made small mistake. Stable version should be 3.1.8
Sent from my HTC Explorer A310e using Tapatalk 4

@rcane said:
Good job. And by the way u made small mistake. Stable version should be 3.1.8
Click to expand...
Click to collapse
Thanks, it has been corrected

When i try to install the script. Error popup that it failed to move 10mounts2sd.sh to system/etc/.
using galaxy note, jelly bean 4.1.3

jasonkhoo87 said:
When i try to install the script. Error popup that it failed to move 10mounts2sd.sh to system/etc/.
using galaxy note, jelly bean 4.1.3
Click to expand...
Click to collapse
Same problem here.

jasonkhoo87 said:
When i try to install the script. Error popup that it failed to move 10mounts2sd.sh to system/etc/.
using galaxy note, jelly bean 4.1.3
Click to expand...
Click to collapse
Okay, could you instead post this as an issue (top pane)?
Sent from my GT-I9300 using XDA Premium 4 mobile app

Says I need busybox and int. I should also say rooted sgh-i137 running skyrom 9.3
Sent from my SAMSUNG-SGH-I317 using Xparent Cyan Tapatalk 2

hmmmm....can't use this app on my Xperia Mini Pro (Carbon Rom v4.2.2)....i manage to install the scripts and after change a few in setup i reboot the phone then BAMMMMMMMM.....stuck on bootlogo....

iPusak Gaoq™ said:
hmmmm....can't use this app on my Xperia Mini Pro (Carbon Rom v4.2.2)....i manage to install the scripts and after change a few in setup i reboot the phone then BAMMMMMMMM.....stuck on bootlogo....
Click to expand...
Click to collapse
And I will gladly help you with this problem, but please use the Bug Report feature at the top of the Thread. It makes it much easier to keep track of current reports. Also, can you add a logcat entry of this issue as well?

dk_zero-cool said:
And I will gladly help you with this problem, but please use the Bug Report feature at the top of the Thread. It makes it much easier to keep track of current reports. Also, can you add a logcat entry of this issue as well?
Click to expand...
Click to collapse
Hope you have a copy of that paragraph so that can just paste.. probably need to use it often.
Sent from my OptimusBlack using xda app-developers app

Is it compatible with link2sd?
I'd like to move swap and cache on the second partition.

There's a separate q&a thread...just in case you weren't aware....
http://forum.xda-developers.com/showthread.php?t=1342387

romualdrichard said:
Is it compatible with link2sd?
I'd like to move swap and cache on the second partition.
Click to expand...
Click to collapse
Of cause not. Link2SD is not compatible with Mounts2SD or vise versa. You can't have two sd-ext scripts doing the same things and expect it to work.

using 4ext recovery and have sd-ext set up on sd card. rom boots fine. and i have the latest version of mounts2sd installed, under app settings i have the start up script installed, have green ck dot for applications, but still get insufficent avl, im very green when it comes to apps2sd and mounts2sd, the guides are not too helpful. any help here would be great. thx. jake

jaxenroth said:
using 4ext recovery and have sd-ext set up on sd card. rom boots fine. and i have the latest version of mounts2sd installed, under app settings i have the start up script installed, have green ck dot for applications, but still get insufficent avl, im very green when it comes to apps2sd and mounts2sd, the guides are not too helpful. any help here would be great. thx. jake
Click to expand...
Click to collapse
What does the size information say about your partitions? You can see this in the app. If cache or data is using to much space, it does not help much to have moved the APK's. And also, what about the Threshold, is that displaying more than what is left on data?

If dont check options that move data from /data/data into/sd ext/data/ whether to open the app to be faster?.
My memory card is 4gb class 4.

dejanxxxx said:
If dont check options that move data from /data/data into/sd ext/data/ whether to open the app to be faster?.
My memory card is 4gb class 4.
Click to expand...
Click to collapse
It all depends on the sdcard whether it slows down or not. I have a 16GB Kingston class4, and this card has faster read and write speed than the internal nand on the SGS3, so I actually gain speed by moving content to sd-ext.
The best cards when using sd-ext, is Kingston, Samsung and ScanDisk. The best class value is 2, 4 and 6 (High values is not good when using sd-ext). The worst is class10 (Don't know why). Also, lower readahead is mostly a good thing, but not if you do a lot of PC~>Phone transfers. So if you don't copy much from PC to Phone, I would lower it to 128KB.
Also, you could always try. If you think that your phone get's slower by moving /data/data, then you can just move it back.

dk_zero-cool said:
Kingston class4, so I actually gain speed by moving content to sd-ext.
The best cards when using sd-ext, is Kingston, Samsung and ScanDisk. The best class value is 2, 4 and 6 (High values is not good when using sd-ext). The worst is class10 (Don't know why). Also, lower readahead is mostly a good thing, but not if you do a lot of PC~>Phone transfers. So if you don't copy much from PC to Phone, I would lower it to 128KB.
Also, you could always try. If you think that your phone get's slower by moving /data/data, then you can just move it back.
Click to expand...
Click to collapse
Thanks, my card is Kingston, mean you say that be better that put lower readahead, on me when look on script for readahead is default 512kb, did leave thus?. Some say that be better that be a 2048kb readahead.
For copy from PC to phone, use air droid, I copy litlle much from PC to phone and conversely, and now how would you put in for readahead?
Ok, I do like you say for readahead,and leave on 512kb, it is deafult read.
Now I leave data/ data, on my internal memory,and only 47mb use.I have small internal memory 158mb free wheb flas ROM. On default is 512mb RAM.

dejanxxxx said:
Thanks, my card is Kingston, mean you say that be better that put lower readahead, on me when look on script for readahead is default 512kb, did leave thus?. Some say that be better that be a 2048kb readahead.
For copy from PC to phone, use air droid, I copy litlle much from PC to phone and conversely, and now how would you put in for readahead?
Ok, I do like you say for readahead,and leave on 512kb, it is deafult read.
Now I leave data/ data, on my internal memory,and only 47mb use.I have small internal memory 158mb free wheb flas ROM. On default is 512mb RAM.
Click to expand...
Click to collapse
Many people think that higher number means better performance, but they never take into account the scenarios. Large readahead is great for large file transfers and small readahead is good for many small reads and writes. So if you often copy multiple gb of music, movies etc to your phone, then yes, a large readahead would be better. If the system is constantly writing small amounts of data to the drive, then smaller readahead is better. The best would properly be around 4kb, but since you also use the first partition as a storage device, it is best to find a middle (Around 128kb, 256kb or 512kb depending of how much transfers you make).
It's like people who thinks that a large CPU is better in their computer, without thinking about whether or not their old HDD can actually keep up with that speed. Grater number does not mean better. A perfect balance is what you should go for.

{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (LOLLIPOP), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Unofficial build of CyanogenMod 12.1(Android 5.1.1) for the HTC Explorer (Pico)​
Notable features:
No Maps 7 glitches, Browser glitches, Gmail glitches, etc.
Uses ION memory allocator
Native Sd-Card -- Using sd-ext partition for system and data
F2FS Support In kernel and Device tree
Uses the newest Adreno (graphics) libraries and firmware available for our platform (these graphics libraries are newer than the graphics libraries in any other ROM)
Significantly smoother/faster graphics as a result of the new graphics libraries
Removed many hacks designed for old graphics
CAF KitKat 2.7 branch Adreno blobs
What's working:
RIL
Data Connection
Display
Stock browser
Camera
WiFi
GPS
WiFi tethering
Bluetooth
Bluetooth tethering
SDcard
Video playback
Audio playback
Headset
Audio Recording
Sensors of All type
Not working:
OMX ( hardware decoding/encoding )
Camcorder
Download:
BETA#1 : http://forum.xda-developers.com/showpost.php?p=61134823&postcount=316
CyanogenMod 12.0 Builds
Gapps :- https://www.androidfilehost.com/?fid=95897840722646482
Install instructions:
Use Class 6 or Class 10 sd-card for best performance
Make 2 ext4 sd-ext partitions like this
1st partition :- sd-data --->> 1GB minimum
2nd partition :- sd-system --->> 1.2 GB
Flash the updated [03/02/2015] TWRP 2.8.5.0 Recovery
Convert your /data and /system partition to f2fs you can find it in wipe option
Wipe all partitions
Flash the cm-12.1-*-UNOFFICIAL-pico.zip
Reboot
If you Stuck at HTC Splash Screen go into bootloader mode, take out boot.img from rom zip and flash it
Reboot
Done!
After first boot reboot back to recovery
Flash Gapps
Source:
https://github.com/CyanogenMod
Thanks to:
All Pico developers before me
PecanCM (TeamHackLG)
LegacyXperia
Use BUG Tracker in Thread to report your Bug
If you want to help fixing those bugs, please report the bugs in the bug tracker and provide me logcat or i cant help you. Thanks!
Logs are needed (logcat/dmesg/last_kmsg), not just "got FC" or "+1" useless replies.
You can get more info here on how to take log HERE
Donations :-
Buy Me A cup of Bear click on donate to ME button
XDA:DevDB Information
Android 5.0 lollipop ( CM-12.1 ) For HTC Explorer, ROM for the HTC Pico (Explorer)
Contributors
kirmaniarslan, Sachin Thomas
Source Code: https://github.com/HtcLegacy
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Rooted
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2015-03-03
Created 2014-11-19
Last Updated 2015-06-11

Changelog :-
CyanogenMod 12.1
Beta#1 03/06/2015 :
- Lollipop 5.1.1
- CM-12.1 Upstream
- Fixed Deepsleep issue
- Disable dialer lookup by default
- Switched to QCOM power HAL
- Added LZ4 Compress/decompress support
- Update zram and zsmalloc up-to 3.17 kernel changes
- inherit media_codecs_google_video_le.xml better for low end devices
- update ril.h for 5.1
- Disable dex2oat watchdog
- Don't disable jit cache
- Set dalvik.vm.dex2oat-filter=balanced
- Disabled LTE as our device doesnot support it
- Update Audio policy for 5.1
- Call broken and Wifi Calling fixed
- Increase ZRAM swap size to 192MB
- fixed heatset and Data connection problem on kernel level ( no patches needed )
CyanogenMod 12.0
Beta#3 02/03/2015 :
- CM Upstream
- Fixed Data Connection
- Fixed Headset thanks @thewisenerd for fix
- Fixed MTP connection with PC
- Enabled WITH_ART_SMALL_MODE you can read it more here : http://source.android.com/devices/tech/dalvik/configure.html#with_art_small_mode
- Symlink dalvik-cache to nand for performance and also decreases the battery usage ( u can see it as sd-ext in recovery for cleaning it )
- Disabled data encryption
- Updated audio_policy.conf from HTC one M7
- Set sd cache to 1MB
- Enable LOGD
- Using NuPlayer instead of Awesome player
- Based on Aw3some mod thanks @thewisenerd
- Gapps Lags Fixed
- Headset profile update from DX kernel 3.4
More Kernel Changelog
Beta#2 29/01/2015 :
- Cm Upstream
- Fixed GPS
- F2FS support in kernel and device tree added for /system and /data partition
- Fixed Sound Recorder
- Enable cortex a9 optimization
- Update HtcMsm7x27aRIL class
- Disabled alpha trasformation in animations
- Added New CPU GOV Intelliactive and set it to default governer
More Kernel Changelog You can Check from HERE
Beta#1 20/01/2015 :
- CM Upstream
- Fixed Camera (Still camcorder is broken )
- Setup for chromecast support.
- Lowmemory killer tweaks to fix oom issues
- Sepolicy inherit from common qcom sepolicy
- Force camera API to version 1
- Updated partition layout
- Set background process to 4
- Inherit dalvik-heap props with 512mb ram (This fixes browser Image Cache problem)
- Enable SystemUI flags to optimize performance
- Builtin bcmdhd module in kernel to fix loading and unloading issues
- Add custom HtcMsm7x27aRIL to fix SignalStrength on gsm
- Disable TARGET_CPU_SMP
- Disable Atlas service
- Cleaned up system.prop
- Disable JIT
- Configure ksm with low ram
- Allow legacy allocations from MM heap
Alpha#2 - 28/11/2014 :
- CM Upstream
- Enable dex-preoptimization to speed up first boot sequence
- Patches for performance Much stable and faster now
- SELinux Support : Set to Permissive mode
- Temp fixed soft reboots
- Forced high-end graphics for transparent lockscreen and statusbar
- Ril fixed GSM working but data connection is not fixed
- Added FFMPEG codec configuration
- Added SELinux support in kernel
- Disabled kernel features
- Added Multi User support upto 4 users allowed can be enabled with ( ro.config.low_ram=false in build.prop )
- Using Awsome Latest layout
Alpha#1 - Nov 19, 2014 :
- Initial upload
- Updated Libaudio
- Disable LOGD
- Enabled Minikin fonts
- Display and Media hals based on msm8960 with some hacks for msm7x27a
- Used dlmalloc instead of jemalloc
FAQ :-
Q: Why SD-ext and what is Partition layout ?
Ans:There is not much space in system partition even with awsome partition layout and secondaly here is the partition layout
/dev/block/mmcblk0p3 mounted as /system i used this partition so that you dont have to create partition again and again
/dev/block/mmcblk0p2 mounted as /data
Q; How Can I clean my sd-ext partitons ?
Ans : you can flash this before flashing rom http://forum.xda-developers.com/showthread.php?t=2392001
Q: I am stuck at HTC splash screen what to do ?
Ans:Simply Take out boot.img from Rom zip and flash it in fastboot mod
Code:
Fastboot flash boot boot.img
Q: I can't find developer options and performance settings, why?
A: Settings -> About phone -> Click 'Build number' several times
Q. No ROOT access WTF ?
Ans : Enable it from Developer option

CyanogenMod 12.0
CyanogenMod 12.0 Builds :-
BETA-3:http://forum.xda-developers.com/showpost.php?p=59174157&postcount=244
BETA-2: http://forum.xda-developers.com/showpost.php?p=58525401&postcount=177
BETA-1 : http://forum.xda-developers.com/showpost.php?p=58297444&postcount=142
Alpha-2 : http://forum.xda-developers.com/showpost.php?p=57106417&postcount=76
Alpha-1 : https://www.androidfilehost.com/?fid=95784891001612903
BasketBuild Mirror

Pico still alive, thank you kirmani for the sweet lollipop Hope it gets stable soon.

@kirmaniarslan You really Rock bro.. Didnt even think of getting a lollipop on our device. Salute you bro Really a grand salute.. You are keeping our device alive and running up.

wow amazing plzz build cm12 for redmi 1s a.k.a armani

Awesome work !!!! hope

Great Stuff Here i See (Y) Good Luck... if people have some issues they can P.M me i have some minor fixtures which can be done in Lollipop... as for now Lollipop is in alpha stages and is a real pain in the arse...
I'll be reporting issues myself when i see other than the given one's in the OP

Thanks man....awesome work

wow the feels!
bro kirmani is really hyping us up!
great work man!
I'll stay tune for this

Booted Successfully
It takes about 10-12 minutes to boot on Class 10 SD-Card

Wow good going pico rocks

Awesome!
BTW, guys is there any way to flash this recovery with any app in pico? (No PC atm)

Error
I'm getting a (bad) error. Any one else getting the same? I'm on CWM 5.0 and on Thinking Bridge rom.

kratikedat said:
I'm getting a (bad) error. Any one else getting the same? I'm on CWM 5.0 and on Thinking Bridge rom.
Click to expand...
Click to collapse
Use the given recovery

I installed from a 4GB mem card
It took 30mins or more to boot... but after booting too, it bootlooped! Same happening again and again!
Need to make any partitions?

TheStrix said:
I installed from a 4GB mem card
It took 30mins or more to boot... but after booting too, it bootlooped! Same happening again and again!
Need to make any partitions?
Click to expand...
Click to collapse
Havent u made sd-ext if yes then flash the rom again after wiping

kirmaniarslan said:
Use the given recovery
Click to expand...
Click to collapse
My bad, didn't read theiinstructions thoroughly enough. Another noob question if you dont mind, how do I flash a recovery over my existing recovery? Does the pico being s-on have an issue with it? Sorry again for the noob question!

Aswin08 said:
Awesome!
BTW, guys is there any way to flash this recovery with any app in pico? (No PC atm)
Click to expand...
Click to collapse
Use terminal emulator
keep the recovery3.img in the root of sdcard
su
cd sdcard
flash_image recovery recovery3.img

Aswin08 said:
Awesome!
BTW, guys is there any way to flash this recovery with any app in pico? (No PC atm)
Click to expand...
Click to collapse
@Ashwin08 this may help for you http://forum.xda-developers.com/htc-explorer/general/how-to-flash-recovery-phone-t2831744

{
"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"
}
​
Hi everyone,
I'm proud to present our build of CyanogenMod 12.1 for the Galaxy S Plus (GT-I9001).
Pay attention:
At the moment the builds are for testing purposes.
Also this rom has partition re-assignments and use internal sdcard partition as new data partition, while the internal sd card is now emulated and shares the available space of data partition.
Working features:
Audio
Receiving and making calls
GPS
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Legacy sensors / Virtual sensors (Gravity, Linear acceleration, Rotation vector)
Wifi
Bluetooth
MTP storage
HW accelerated gui
HW accelerated video
Camera
Voip video calls
BLNv10
USB/Wifi tethering
VSync
Phantom key presses filtering
USB OTG (check here for the needed Y cable)
MicroSD exFAT support
zRam
F2FS support for /data partition
Known issues:
Video recording at 720p quality may cause a force close of Camera app, so it's better to use 480p quality until this issue will be fixed
Not working features:
Let me know...
Disclaimer:
Your warranty is now void.
We are not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you.
Click to expand...
Click to collapse
How to install the rom:
If you're coming from a stock rom, a previous Android version (CM 9, CM 10, CM 10.1, CM 10.2 and derivatives) or if you have a CM 11.0 older than Release 15, read carefully the following steps
Download the rom, gapps and the new TWRP recovery (its mandatory)
If you have an external sd, you may already copy the downloaded files on it, please don't flash anything yet, read the following steps
Backup your data, like call history, contacts, sms, favourite app settings inside external sd (by using Titanium Backup or other apps available on PlayStore)
Backup your internal sd content, because all its content will be lost (you may copy the full content on a pc or inside a new folder of your external sd)
If you have WhatsApp, copy the folder /sdcard/WhatsApp inside /external_sd/Whatsapp, so you are ready to restore all your conversations after the re-installation of the app
Copy the content of the folder /sdcard/DCIM inside /external_sd/DCIM, so your taken pictures stored inside internal sdcard will be preserved
Reboot inside CWM or TWRP recovery which not includes new partition assignments
Perform a nandroid backup inside external sdcard (inside TWRP, Backup -> Select all the partitions -> Select Micro SD card as storage -> Swipe)
Install the new TWRP recovery that includes new partition assignments
Reboot inside TWRP recovery again, because now you must be sure to use the new one (inside TWRP, Home -> Reboot -> Recovery)
Wipe Data as ext4 or f2fs partition (Wipe -> Advanced Wipe -> Select Data -> Repair or Change File System -> Change File System -> EXT4 or F2FS -> Swipe)
Wipe Dalvik Cache, Cache, System and Android Secure (inside Wipe -> Advanced Wipe)
If you haven't copied the installation files yet, be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files inside internal sd or external sd
Install the rom package
Install the gapps package
Reboot the system
If you performed a backup with an app, on external sd or on pc, you may restore the saved data and copy/move /external_sd/Whatsapp folder to /sdcard/Whatsapp again
If you're coming from CM 12.0 or CM 11.0 Release 15 and above
Download the rom and gapps
Backup your data, like call history, contacts, sms, favourite app settings inside external sd (by using Titanium Backup or other apps available on PlayStore)
Reboot inside TWRP recovery (that includes new partition assignments)
Perform a nandroid backup (inside TWRP, Backup -> Select all the partitions -> Select Micro SD card as storage -> Swipe)
Wipe Data as ext4 or f2fs partition (Wipe -> Advanced Wipe -> Select Data -> Repair or Change File System -> Change File System -> EXT4 or F2FS -> Swipe)
Wipe Dalvik Cache, Cache, System and Android Secure (inside Wipe -> Advanced Wipe)
Install the rom package
Install the gapps package
Reboot the system
If you performed a backup with an app, on external sd or on pc, you may restore the saved data
If you're updating a CM 12.1
Reboot inside recovery (always the new one)
Install the rom update
Reboot the system
Downloads:
TWRP 2.8.1.0 recovery [17/01/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: f0c43dc355571554be6d0bad047c94cd
Note: This recovery includes new partition assignments and supports F2FS partitions
Android 5.1 Gapps: [Open Gapps] [Mardon Gapps]
Choose the ones you prefer...
CM 12.1 Release [23/01/2016]: [DevHost Mirror] [MediaFire Mirror]
MD5: 259d8fef9e00bcea3e29db56c2dbc1e8
Code:
- Lollipop 5.1.1 (LMY49F)
- Synched with latest CyanogenMod 12.1 sources
[B]kernel/samsung/msm7x30[/B]
- Kernel 3.4.110
- lowmemorykiller: avoid false adaptive LMK triggers (credits to Vinayak Menon)
- mm: vmpressure: scale pressure based on reclaim context (credits to Vinayak Menon)
- mm: vmpressure: account allocstalls only on higher pressures (credits to Vinayak Menon)
- mm: vmpressure: fix backport (credits to Dave Daynard)
- block: bfq: Squashed update from BFQ-v7r5 to BFQ-v7r8 (credits to Michael Bestas)
Stock Kernel [23/01/2016]: [DevHost Mirror] [MediaFire Mirror]
MD5: 3aa3d526b06111b425026419c042e1a5
Note: This stock kernel is already included inside the rom, it's provided in case you installed a custom kernel and would like to re-install the stock one
Old Builds:
CM 12.1 Release [10/08/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: 147ac0b7c99aebcaf99d592f11a3186a
Code:
- Lollipop 5.1.1 (LMY48G)
- Synched with latest CyanogenMod 12.1 sources
[B]device/samsung/ariesve[/B]
- device: Don't copy FFMPEG config anymore (credits to Steve Kondik)
- libhealthd: fix warning (credits to Dan Pasanen)
- ramdisk: Enable adaptive LMK (credits to Steve Kondik)
[B]kernel/samsung/msm7x30[/B]
- Kernel 3.4.108
- mm, oom: make dump_tasks public (credits to Liam Mark)
- mm: vmpressure: allow in-kernel clients to subscribe for events (credits to Vinayak Menon)
- mm: Add notifier framework for showing memory (credits to Laura Abbott)
- android/lowmemorykiller: Account for total_swapcache_pages (credits to Liam Mark)
- lowmemorykiller: Don't count swap cache pages twice (credits to Liam Mark)
- lowmemorykiller: use for_each_thread instead of buggy while_each_thread (credits to Vinayak Menon)
- lowmemorykiller: enhance debug information (credits to Liam Mark)
- lowmemorykiller: Dump out slab state information (credits to Laura Abbott)
- lowmemorykiller: Run the lowmemory notifier when killing (credits to Laura Abbott)
- lowmemorykiller: Do proper NULL checks (credits to Susheel Khiani)
- lowmemorykiller: adapt to vmpressure (credits to Vinayak Menon)
Stock Kernel [10/08/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: e2c53ba45bb56d00742a4f6f02aa09dc
CM 12.1 Release [07/06/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: da230bc13260f8ddcd839c821593ba19
Code:
- Lollipop 5.1.1 (LMY48B)
- Synched with latest CyanogenMod 12.1 sources
[B]device/samsung/ariesve[/B]
- device: Set dalvik.vm.dex2oat-filter=balanced (credits to mikeioannina)
[B]kernel/samsung/msm7x30[/B]
- Revert "epoll: use freezable blocking call" (credits to Rafael J. Wysocki)
- suspend: Return error when pending wakeup source is found. (credits to Ruchi Kandoi)
- subsystem: CPU FREQUENCY DRIVERS- Set cpu_load calculation on current frequency (credits to rahul.khandelwal)
- cfg80211: add space after the b/w in db.txt (credits to Mihir Shete)
- usb: ks_bridge: Ignore completion error in RX path (credits to ChandanaKishori Chiluveru)
- ipv4: Missing sk_nulls_node_init() in ping_unhash(). (credits to David S. Miller)
- msm: msm_fb: wait for VSYNC instead of DMA_P for LCDC (credits to Justin Philip)
- msm: Kconfig: Disable SPARSEMEM for msm7x30 targets (credits to mikeioannina)
- video: msm: Tone down logging (credits to mikeioannina)
- Update defconfigs (credits to arco68)
Stock Kernel [17/05/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: 4fe208f9497b94a62bca50da092ed410
CM 12.1 Release [17/05/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: 6ae73ac20db3ea3ab8d8776254448053
Code:
- Lollipop 5.1.1 (LMY47V)
- Synched with latest CyanogenMod 12.1 sources
[B]device/samsung/ariesve[/B]
- Revert "rootdir: Increase Swappiness to 100" (credits to arco68)
- Revert "rootdir: Increase zram disk size to 256mb on 512mb devices" (credits to arco68)
- rootdir: Use lz4 compression for ZRAM (credits to arco68)
- rootdir: Reduce ZRAM size to 128MB (credits to arco68)
- overlay: Define default quick setting tiles (credits to arco68)
- device: Use ART small mode (credits to mikeioannina)
- device: Disable dex2oat watchdog (credits to mikeioannina)
Stock Kernel [17/05/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: 549024aaf01b7ca3b2b5e696a78c7521
CM 12.1 Beta [02/05/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: fb2a6c490384f5db98ef8fa087f0923a
Code:
- Lollipop 5.1.1 (LMY47V)
- Synched with latest CyanogenMod 12.1 sources
[B]device/samsung/ariesve[/B]
- BoardConfig: Enable BOARD_SUPPRESS_BLOCK_DISCARD (credits to Christopher83)
[B]hardware/qcom/display-caf/msm7x30[/B]
- gralloc: Add allocation support for standard NV12 (credits to Justin Philip)
- gralloc: handle YCbCr 420SP format in lock_ycbcr (credits to Justin Philip)
- gralloc: Fix incorrect handle validation check (credits to Naseer Ahmed)
[B]hardware/qcom/media-caf/msm7x30[/B]
- mm-video: vdec: initialize m_native_buffers_enabled flag appropriately (credits to c_sridur)
- mm-video:vdec: Fix random ION memory call failures (credits to c_sridur)
- mm-video: venc: Fix reconbuffer free crash. (credits to c_sridur)
Stock Kernel [02/05/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: aee5cdf433e1b4f70c89f171844277da
CM 12.1 Beta [17/04/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: ef72f0efaf486e3797eecd0fc674f945
Code:
- Lollipop 5.1 (LMY47I)
- Synched with latest CyanogenMod 12.1 sources
- Now the icon of mobile network signal should work fine again
[B]device/samsung/ariesve[/B]
- device: Disable dialer lookup by default (credits to mikeioannina)
[B]kernel/samsung/msm7x30[/B]
- Kernel 3.4.107
CM 12.1 Test [09/04/2015]: [DevHost Mirror] [MediaFire Mirror]
MD5: 5ad2f5d0af2bffc208b01c8fada688c6
Code:
- Lollipop 5.1 (LMY47I)
- Synched with latest CyanogenMod 12.1 sources
Sources:
AriesVE-DevCon-TEAM on GitHub​
Credits and Thanks to:
CyanogenMod Team for the huge work
arco68, Christophe83, CastagnaIT, krislibaeer, ivendor, educk for their development on this device
mikeioannina, Blefish for their development on other legacy devices
ktulu84, Rhonin86, smeroni68, XeLLaR* for their help in testing
Nello96 for the team logo
Olli H., Harald K. for their donations
XDA:DevDB Information
[GT-I9001][LP 5.1.1] CyanogenMod 12.1 by ADC-Team - Kernel 3.4.x, ROM for the Samsung Galaxy S Plus I9001
Contributors
Christopher83, DevConnection_Team, arco68, CastagnaIT, mikeioannina, Blefish, krislibaeer, ktulu84, Rhonin86, smeroni68, XeLLaR*, sirmordred
Source Code: https://github.com/AriesVE-DevCon-TEAM
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery that includes new partition assignments
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 04
Stable Release Date: 2016-01-23
Created 2015-04-11
Last Updated 2016-01-30

Screenshots:
Screenshots Tab
Frequently Asked Questions:
My device keeps on booting inside recovery instead of rebooting the system, what I can do?
If you have recovery bootloop problem, you should take a look at this post
How can I use BackLightNotifications feature?
BLNv10 is activable/deactivable from AriesParts (Advanced Settings) or BLN Control Application (Free or Pro version)
Is the new recovery compatible with an old rom (CM 11.0, CM 10.2, CM 10.1, and previous)?
No, the new recovery is compatible only with new CM 12.1, CM 12.0, CM 11.0 Release 15 and next releases. If you want to restore a previous backup taken with an old recovery (without partition reassignments), you should re-install the old recovery first, reboot inside recovery again and then restore the backup.
What does the emulated internal sd card mean and where my files are stored on it?
The emulated internal sd card is a special folder (/data/media) available inside data partition and also simlinked to /sdcard, it's recognized as a FAT storage and can be used in place of the previous internal sd card. The emulated sd card shares the available space of data partition, but it's not wiped when you choose to wipe Data from recovery.
How can I get the transparent status bar and transparent lock screen background?
By default, these features are disabled, because they are available for non lowram devices only, but you can enable them by activating Force High-End GFX switch inside Settings -> Performance or Advanced Settings app (a reboot is needed).
How can I enable Developer options?
You can enable this menu section by tapping 7 times on Build number inside Settings -> About phone.
How can I enable Root Access for apps?
You can enable it inside Settings -> Developer Options -> Root Access, set it to Apps only or Apps and ADB.
The granted root permissions for any app can be found inside Settings -> Privacy -> Privacy Guard, then long press on the app to show or manage its permissions.
How can I enable Advanced Reboot options?
You can enable the Advanced Reboot options inside Developer options.
What is Battery saver feature and how can I enable it?
This is a new feature of Android L that allows to improve the battery life by reducing the device's performance, limiting vibration, most background data and limiting the synchronization for emails, messaging, etc... It can be enabled when the device is not charging inside Settings -> Battery -> Top left menu -> Battery saver.
I cannot mount internal SD card via mass storage, how can I fix this issue?
You must use MTP protocol since emulated sd doesn't support mass storage.
This is common on all devices with an emulated sd, that's why the mainly supported protocol is now MTP (expecially on Lollipop).
During a reboot the system shows "Optimizing Apps" again, why?
As arco68 said, the optimizing apps on second boot is TRIM running. Google changed this in 5.0.2, so now it runs automatically once a day, either during the night while phone is charging or after you reboot.
Music app (Eleven) force closes during start or shows duplicated artists, albums, songs, how can I fix this?
Probably one of the databases of media provider is corrupted or contains wrong data, try to delete the content of /data/data/com.android.providers.media/database, perform a reboot and test music app again.
I cannot connect to my wifi router, how can I fix this issue?
It has been reported that inside some country regions is not possible to successfully connect to wifi router.
If you have this problem, check your wifi router configuration and try to switch from WPA2 to WPA security.
This possible workaround has been reported by an Iranian user.
I'd like to go back to CM 11.0 Release 15 or a next CM 11.0 release, what should I do?
- Reboot inside recovery
- Wipe Cache, Dalvik Cache, Data, System, Android Secure
- Perform the restore or the clean installation of CM 11.0
I'd like to go back to CM 11.0 Release 14 or a previous Android version, what should I do?
- Reboot inside recovery
- Wipe Cache, Dalvik Cache, Data, System, Android Secure
- Reinstall old recovery (without partition reassignments)
- Reboot inside the old recovery (Home -> Reboot -> Recovery)
- Inside Advanced Wipe menu wipe SDcard as FAT partition (Wipe -> Advanced Wipe -> Select SDcard -> Repair or Change File System -> Change File System -> FAT -> Swipe)
- Perform the restore or the clean installation of the old Android system
What is F2FS file system?
F2FS (Flash-Friendly File System) is a new file system designed for delivering maximum file-system performance on flash-based storage devices. For more info: F2FS
How can I switch to F2FS format type for /data partition without loosing data?
By switching from EXT4 to F2FS format type for /data partition, without performing any backup, you will surely lost all your user data files and internal sd content.
To avoid that, follow these steps:
- Perform a backup of your internal sd (/sdcard) by copying the /sdcard content inside a new folder on /external_sd or on your pc (through MTP)
- Reboot into recovery
- Install latest TWRP recovery with F2FS support
- Reboot -> Recovery to reboot inside the newly installed recovery
- Perform a full backup of your current configuration, inside Backup -> Flag all partitions -> Set a customized name if you want -> Set Micro SD card as storage -> Swipe to Backup
- After the backup process has completed, go inside Wipe -> Advanced Wipe -> Select Dalvik Cache, System, Cache -> Swipe to Wipe
- Always inside Wipe -> Advanced Wipe -> Select Data -> Repair or Change File System -> Change File System -> F2FS -> Swipe to Change
- Install new rom and gapps
- Restore your data partition from previously made backup, Restore -> Select latest backup -> Select Data only -> Swipe to Restore (don't care about ext4 warnings)
- Restore your /sdcard backup
- Reboot System
- Check if your data is using F2FS format type by running the following command inside Terminal Emulator or through ADB:
Code:
mount | grep f2fs
If everything is ok, you should get
Code:
/dev/block/mmcblk0p28 /data f2fs <various comma separated options>

How to perform the calibration of Magnetic / Acceleration / Orientation Sensors
Horizontal Calibration:
Open Advanced Settings and select Horizontal Calibration, place the phone over a flat and horizontal surface, then press Calibrate.
Magnetic Field Calibration
After installing a compass app or another app that uses the magnetic sensor, open that and perform an 8 shape, as shown in this video.
The calibration movement is a combined one over all axes and will result in a residual magnetism removal (reset), please perform a slow movement, it's not important the direction you'll follow, just do once or more times until you get the correct calibration.
To know if the calibration is correct, you must know where is approximately the North and look with a compass app if the needle is pointing there. If it's so, try rotating the phone of 90, 180, 270 degree, finally go back to 360 degrees and look if the needle is pointing always to North during the performed rotation.
If this easy test give positive results, your magnetic sensor has been correctly calibrated.
​
Note:
After performing the above calibrations, the orientation and magnetic field sensors will give the correct values with all apps.
Our phone is known to have a native shift of some degrees respect to the North, but this is a hardware limitation due probably to the orientation of the chip welded on the board.
This procedure can be used also after a new flash of a compatible custom kernel in case the sensors are not correctly working.
Legacy Sensors / Virtual Sensors
These sensors are called virtual, because our device hasn't a real hardware chip for them, but by utilizing some data processing techniques and by merging the values coming from accelerometer and magnetic field sensors, it's possible to extrapolate the approximated values of these virtual sensors.
Please note that not all apps support the virtual sensors, to perform a test we suggest the app S Tools+.

Reserved, just in case...

Please, read carefully all the opening post content, you must follow the installation instructions to avoid any problem...
My custom kernel for CM 12.1 will be available in the future, I think that's important to have a good working rom first.
The first builds of this rom will be surely for testing purposes, don't think that everything will work as expected, so don't install it if you need a good working device.
I wish you a nice week end!

Thanks Christopher, you're awesome!
Gesendet von meinem Nexus 5 mit Tapatalk 2

Downloading right now....!
Thnx Dev...!

you. are the man of i9001
U have too much care about our device..........
Thank u ..................

You're a genius.
You know you're totally insane (in the good way of course) ?
Thank you so much for your hard work on our phone, all the sections should have these kind of dev'.

sivanadh47 said:
U have too much care about our device..........
Thank u ..................
Click to expand...
Click to collapse
absolutely right !
---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------
This is one great Easter present ! Our huge respect .

many thanks
Youre the best! You keep S plus alive!
Android 2.2 - 5.1
Kernel 2.6-kernel 3.4
Will try and report soon.
Now, I want to ask you a question. I know youve already done a lot and we cant ask you more, but I wonder: ¿Will you at least try to compile kernel 3.10 from that huavei msm 70x3 which got it? I wanna see how would it perform.
Many thanks!

THX Cris,
another Masterpiece
During the testphase i was astonished how much better the CM 12.1 performes in comparison to the CM 12. The version before this one provided a "very quick" responding CallUI (about 2 seconds) while the latest needs nearly 6 seconds to start. i hope i will be quicker again. Another small bug is the missing provider connection symbol - but the connection is present and it works.
I wish you all a lot of fun with the newest ROM - THX again Chris - there are no words to express our gratitude to how much you have given us
Rhonin

USB OTG is working
Thank you so much Christopher83 for this project
As mentioned by Rhonin86 there are no words to express our gratitude to how much you have given us :highfive:
Regarding the USB OTG, I tested and can confirm that it is working :good:
I also agree with Rhonin86 in relation to better performe of the CM 12.1 in comparison to the CM 12.
This was my experience just after the first boot after installation ..continue to test it :fingers-crossed:
Obs: I use Minimal Edition Gapps
Best regards,
Hugo
Edit 1
@Christopher83
Wifi tethering is working fine :good: and my free ram also
Edit 2
MicroSD exFAT is also working
Man, this test build is much faster than the CM12 :good:

and
What about battery?

tonibm19 said:
What about battery?
Click to expand...
Click to collapse
Try and tell US
PS: Linux Kernel 3.10 would bring 0 performance increase since we dont have a x64 SoC. Even the Nexus5 doesnt have a 3.10 kernel for this reason.
Gesendet von meinem Nexus 5 mit Tapatalk 2

Awesome Test
Although it's a test its feels like a full release blazing fast
Thank You Christopher83:good::highfive:

What? Already a 5.1 release? But I've just updated to last 5.0 version! - Just joking, I'll give it a try and let you guys know.
It's probably going to be great so I'll just say thanks now! :highfive:
EDIT: Well, I didn't even get to flash the ROM. I just tried to do the usual steps:
1. Advanced wipe
2. Wipe everything except external sd card
But for the first time, it got stuck on formating the cache partition. I thought it may take more time but in the end the best idea seemed to turn off the phone.
nope. bad idea
Now I can't even boot to recovery/download, it's stuck on Samsung logo. Did it ever happen to you or is there something that can be done?
Yes I know this is off-topic
EDIT2: Kept the battery out for some time and now I am able to boot into recovery

battery
battery juts a bit , but we'll see further. Thx
one percent per hour, not the bell phone only sleeps

Won't boot for me
EDIT: Nvm works. Forgot to wait

Awesome work Christopher , 5.1 work smoothly I believe that with more time and more development , this ROM will work perfectly

{
"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"
}
Hello everyone,
with this post i present you my Customized LineageOS 11.0 build (based on Android 4.4.4) for the Samsung Galaxy S Plus (GT-9001).
This Rom is based on the work from the ADC-Team and their CyanogenMod 11.0 ROM. The included Kernel is based on Christopher83's UV K^Kernel.
I made this Rom mostly for myself, because i still use this device as my daily driver.
Please take a look at the feature list to see if you like them or not. Also, please read the installation instructions carefully!
Disclaimer
Your warranty is now void.
We are not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you.
Click to expand...
Click to collapse
Features
Latest LinageOS version with current security patch level
Kernel 3.4.113 compiled with latest Linaro 7.3.1 Toolchain
Rom compiled with latest UberTC 4.8.5 Toolchain
Build with optimization flags and added misc performance optimizations
F2FS support for Data and Cache
SDFAT driver for ExFAT and vFAT support
Hardened Kernel and ROM configuration
A lot of fixed security vulnerabilities (e.g. the spectre bug)
Debloated by removing some apps and more stuff (like the theme engine)
microG support
Build with NoAnalytics
Removed some of Google's proprietaries
Up to Date Fennec web browser
Some Vendor Blobs got replaced with open source alternatives (rmt_storage, libgemini and rild till now)
Some upstream updates (Font, tzdata, APN, ...)
Rom and APKs signed with private keys
a lot more...
Installation
If you are installing this Rom for the first time, please do a clean installation:
Download this Rom and the latest TWRP recovery from the ADC-Team with F2FS support (look inside the Download section)
Optional: Download a Gapps package, even tho i strongly suggest not to install them, because of possible performance issues and privacy concerns
Put all of the downloaded files on an external SD card (if you don't have one, you can copy the Rom (and Gapps) on the internal SD card via MTP after the wiping step)
Optional: Backup all of your data
Install the new recovery, then reboot into recovery again
Change the filesystem for the Data AND Cache partition to F2FS (Wipe -> Advanced Wipe -> Select Data -> Repair or Change File System -> Change File System -> F2FS -> Swipe -> Redo steps for Cache)
Wipe Dalvik Cache, Cache, System and Data partition
Install the ROM
Optional: Install Gapps
Reboot the system
If you want to update from the 03.08.2018 build or older to a newer version you have to flash a migration zip first.
Read more about it in the second post.
If you already installed this build, then you can just update it:
Download the new build and copy it to your device
Wipe Dalvik Cache and Cache
Optional: Wipe System (I do this step every time. Its usually not needed and will (hopefully) tell you if it's necessary)
If you are using Gapps you have to install them after the Rom update again
If you are using Adaway, you have to download your Hostfiles after this step again
Install the Rom update
Reboot the system
Changelogs
04.11.2018 build:
LineageOS
-september security bulletin
-added disclaimer to the security patch level
Kernel
-a few patches from lineageos' msm8974 kernel repo and jdc teams kernel repo
-more spectre patches
-changed default governor to interactive
-fixed a "few" compiler warnings
Rom
-update tzdata to 2018g
-update apns
-remove more debug programs
-speed up (scroll-)animations and shutdown
-moved gps hal to the device tree
-add rom informations to the updater script
Apps
-updated fennec to 63.0
Again: if you browser starts to crash after updating, you have to clean Fennec's data. I am sorry if that happens.
Click to expand...
Click to collapse
Old Changelogs:
10.09.2018 build:
LineageOS
-august security bulletin
Kernel
-misc security patches
-updated ancora defconfigs (because of a request)
-implemention of a quickwakeup driver
-use gzip instead of xz for compression
-overclock GPU to 275MHz (thanks to marcindevelopment)
-some more small things
Rom
-updated apns
-removed some debug programs
-removed recovery resources from the zip
-misc cleanups
-readded all the languages and fonts! (thats why the build is about 30mb larger)
-signed builds!
Apps
-updated fennec to 61.0.2
Again: if you browser starts to crash after updating, you have to clean Fennec's data. I am sorry if that happens.
ZIPs
-addonsu zip
-addonsu-remove zip
-migration zip
Click to expand...
Click to collapse
03.08.2018 build:
LineageOS
-july security bulletin
-added some missing September 2017 patches
Kernel
-added LineageOS' SDFAT driver, removed ExFAT driver
-added Spectre V1 and V2 patches
-some security patches from LineageOS' samsung_msm8974 kernel tree
-added some more hardened kernel configurations from AndroidHardeningArchive's Kernel tree
-use optimizations for the memory manager again
-updated android-alarm driver
-a lot of firmware loader updates
-reverted all of the latest binder updates
This fixes the broken touchkey backlight timeout option
-added some K^Kernel patches i somehow missed
-switched some I/O schedulers and governors
-added an interface that lets you disable the logger
-removed execution domain support
Rom
-renamed Rom from UNOFFICAL to customized
-reworked brightness fix, now it works for every brightness value
-whitelisted some OpenGL ES methods (Google Maps and some other Apps my run faster now)
-readded arabic language and font (because of a request)
-disabled LineageOS statistics by default, only relevant for a clean installation
-removed CM's recovery keys
-updated Wallpaper Picker
-updated APNs
Click to expand...
Click to collapse
13.07.2018 build:
Kernel
-Compile GPU driver and crypto modules with -O3 again
-Reverted a faulty commit
-Removed F2FS encryption support (not supported for Kernel 3.4)
-Implemented CPU boost (thanks to MarcinDevelopment)
-Small performance optimizations
-Fixed some compiler warnings
Rom
-Deleted one unnecessary vendor blob
-Disabled GPS by default, only relevant for a clean installation
-Updated APN's
-Use low-res bootanimation
-Boot with 1/4 of the maximum brightness
-Implemented the hacky maximum-brightness-after-boot workaround
-Small cleanups
Apps
Fennec
-Updated Fennec (they forgot to build some languages)
If you browser starts to crash after updating, you have to clean Fennec's data. I am sorry if that happens.
Click to expand...
Click to collapse
08.07.2018 build:
Kernel
-Kernel compiled with -Os flags instead of -O3
This should fix the hw button bug (thanks to outofmemory13)
-a lot of binder updates
-properly implemention of UID-based routing
-some more things from LineageOS' samsung_jf kernel tree
Click to expand...
Click to collapse
06.07.2018 build:
Since this Changelog would be too big to add every change that was made from the latest CyanogenMod Rom from the ADC-Team, this is more a of a mashup, I am sorry if I forgot something important.
Notable CyanogenMod/LinageOS changes
-rebranding to LineageOS
-new Bootanimation
-updated translations
-some layout fixes
-some fixed FCs
-updated APNs
-some security vulnerabilities got fixed (like Krack and Blueborne)
-implementation of the security patch level
Current version is June 2018
Kernel
-updated Kernel version to 3.4.113 (EOL)
-compiled with latest Linaro 7.3.1 Toolchain
-changes from the ADC-Teams cm-12.1 branch
-switched to the UV configuration per default (if you notice stability issues related to the undervolting, you can manually change the voltage tables)
-update BFQ scheduler and make it default, also removed some other schedulers
-switched to Lulzactive as the default governor, also removed some others
-misc performance optimizations (e.g. disabled CRC check, some disabled logs, stats and debugging, LZ4 compression, disabled LMK and more)
-updates for F2FS and ExFAT (1.2.9 -> 1.2.19)
-TCP changed to Westwood
-build with some optimization flags (O3 and Graphite optimizations)
-mark SD card as non removable
-included power efficient workqueues
-a lot of fixed vulnerabilities
-hardened build configurations/changed some configs, that were really bad for security (e.g. disabled devmem, disabled AIO, updated LSM_MMAP_MIN_ADDR value and more)
-raised default min CPU frequency (this fixes the audio stuttering in Apollo music player)
-lowered min display brightness
-disabled virtual terminal (this means 1MB more available RAM OMG!!!)
-a lot more
Rom
-synced with latest CM/LOS changes
-compiled with latest UberTC 4.8.5 Toolchain
-changes from the ADC-Teams cm-12.1 branch (the ones that are applicable for cm-11.0)
-compiled with Archidroid Optimizations V3 (I cleaned them up a bit)
-F2FS support for Cache and Data
-upstream changes to the media drivers (CAF media, audio and display driver)
-implemented ioprio for a more responsive phone (thats why i recommend to use BFQ)
-switched from Superuser to SU (you can enable root inside the developer options, there is also a new SU panel inside the advanced privacy guard)
-microG support (fake signature support can be enabled inside developer options)
-replaced Google Analytics with a self-compiled NoAnalytics version
-hardened SQLite (enabled secure delete)
-hardened WPA Supplicant
-updated APNs from the lineage-15.1 branch
-updated time zone data
-optimized GPS (with a security fix)
-some vendor blobs got replaced with open source alternatives (rmt_storage, libgemini and rild till now)
-more volume steps
-improved performance (e.g. by optimizing the scrolling cache, by showing simple dialog for optimizing apps, or disabling some debugging)
-sounds cleanup
-updated fonts and emojis
-you can now pull down the status bar when your device is locked
-smaller touch target for the emergency call button on a locked screen
-updated wallpaper
-misc hardening (e.g. by increasing the maximum password length)
-use Cloudflare DNS servers instead Google's
-remove some precompiled stuff (like old face recognition files)
-removed theme engine (even when not in use, it used about 5MB of RAM)
-removed some apps (like Terminal, SoundRecorder, STK, CMAccount, CMHome, VoiceDialer, VoicePlus, VideoRecorder, LiveWallpaper, CMUpdater, Email, PrintSpooler and even more)
-removed some languages
-added ASCII art and real-time installation infos
-added lockscreen rotation option
-speed up some animations
-some upstream fixes
-new power off charging animation
-a new bootsplash logo
-a lot more
Apps
Browser
-changed it to Fennec 61.0 from F-Droid
The security issues in the original browser and Kitkat's webview are too terrible.
CMFileManager
-removed the exit warning
Apollo music player
-fixed back button
-remind the last song that was played
LockClock
-fixed the interface for low font sizes
-removed Google proprietary
Trebuchet
-updated all apps icon
Settings
-updated icon
-updated battery/system icons (gingerbread is now dead!)
-updated german translations
-new contributors cloud
-removed theme options
-support for microG and SU
Click to expand...
Click to collapse
Downloads
04.11.2018 build
Old Downloads:
10.09.2018 build
03.08.2018 build
13.07.2018 build
08.07.2018 build
06.07.2018 build
Sources
LineageOS sources: https://github.com/LineageOS
My repositories: https://github.com/wangenau?tab=repositories
My manifest files: https://github.com/wangenau/android
Credits and Special Thanks
LineageOS/CyanogenMod
Mozilla
ADC-Team
JDC-Team
LegacyXperia
CopperheadOS/thestinger
Christopher83
sirmordred
coldwindofnowhere
DafabHoid
outofmemory13/MarcinDevelopment
ArchiDroid/JustArchi
XDA:DevDB Information
Customized LineageOS 11.0, ROM for the Samsung Galaxy S Plus I9001
Contributors
wangenau
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery with F2FS support
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-07
Last Updated 2018-11-04

Additional Informations
Signed Builds
Starting with the 10.09.2018 i will start to sign my builds with my own private keys. That includes the Rom itself, but also the APKs inside of it (instead of precompiled apps i include, which is only fennec till now).
This means you (or someone else) can only update the Rom and the system APKs with files that are signed by me. With this noone should be able to install a bad system APK or a bad build on your device.
To update your device from an older build, you have to add those keys to your device first. I made a flashable zip for that purpose. So if you want to update from an build that is older than the 10.09.2018 you have to flash this zip first.
Download migration zip
You only have to do this procedure once. If you do a clean installation you don't even have to it.
But that also means you can't go back to an older build after going to signed builds. (If you really want to for whatever reason, edit the migration zip for that purpose, or ask me how to do it)
To check if one of my builds has the correct signature, simply use:
Code:
keytool -J-Duser.language=en -list -printcert -jarfile zip_name.zip
The resulting fingerprints of my builds (after the 03.08.2018) are listed as follows:
Code:
Certificate fingerprints:
MD5: A2:42:4C:F5:4E:DD:3A:A2:C8:20:3A:AF:A1:D6:B9:99
SHA1: F2:13:38:21:53:55:89:CD:30:96:18:99:DD:7B:6D:81:DF:18:79:5F
SHA256: 94:56:09:A6:38:84:CB:BD:82:A5:A9:30:2F:D7:7C:EC:95:AA:57:FE:88:3B:9B:16:79:61:64:B4:AC:79:53:CC
SU
This Rom comes with su preinstalled. This means you have the ability to use Apps that need root permissions. If you don't want this you can remove su with this flashable zip.
Download addonsu-remove zip
If you want to add su back after removing it, you can do that with this zip.
Download addonsu zip
Simply flash these zips inside your recovery and reboot your device afterwards.
Bugs
There are a few small bugs, that will probably never get fixed (if you know how to fix these write me how to do it )
Bugs that can be fixed with a reboot:
no mobile data connection
SD Card stops working
Other Bugs:
MX Player does not work (and it will also freeze your system)
apparently this applies to RAR and Solid Explorer too
a user reported FC's and slowdowns inside the app "Aliexpress" with the lulzactive governor

Tips and Tricks
To get access to the Performance and Developer options go inside About phone inside Settings and tap 7 times on the Build number.
The default governor is interactive. Personaly i use lulzactive. Switching the governor may give you better performance and/or batterylife. But using interactive should be more stable. You can change the governor in the Performance section inside.
Under Performance Settings you can also overclock the cpu. I would say it is pretty save to overlock the cpu, since i am running my device for 5 years at 1.82 GHz (unless you have a different hardware revision)
If you experience random shutdowns after overclocking, you should lower the maximum cpu speed or raise your cpu voltage.
Using this Rom without Gapps is recommended. If you need some Google services you can use MicroG instead. To use it activate Signature Spoofing under Developer options. Google Maps i use, in combination with MicroG and Mozilla's Unified Nlp Backend. Also i use a rather old Maps version (9.14.0). But if you don't need the newest features und just some Maps, this version performs really good, even on our old device.
If you are using Adaway (also a recommendation) don't forget to add mtalk.google.com to your whitelist.
If you want an open source app store i can recommend F-Droid.
These pages (including the following posts) also contain useful informations about Rom and Kernel:
ADC-Teams CM11 Thread
Christopher83's K^Kernel Thread

Hello everyone again,
i finally created this thread and uploaded my rom. I had this in mind for a long time and i use my own LineageOS version since quite some time (i made my first commit in November 2015 i guess) and now it is in time for the 7th birthday from this device . I tried to make this device more secure, while still providing good performance and battery life.
I hope you like this rom, but again: I made this mostly for myself. And since i am not a power user (which is quite impossible with this device ), there might be some things that are broken that i didn't noticed, or stuff got removed because i didn't needed it. If you notice something of this or you find some bugs or have a question, feel free to post about it and i will take a look at it.
You can see all of my sources in the first post and even my manifest to make the build as reproducible as possible.
You can also take a look at the changelog for more informations (creating this changelog really took some time), at the two screenshots i uploaded and most important at the installation instructions.
I guess i don't have more to say for now, so happy flashing!

wangenau said:
-compiled with latest Linaro 7.3.1 Toolchain
Click to expand...
Click to collapse
HW Keys bug exist because of linaro. Switch to other toolchain or remove O3 flag (change to Os)
I'll use rmt_storage from sources you provided. I've used rmtfs all time, but seems that there's better replacement. Thanks!

outofmemory13 said:
HW Keys bug exist because of linaro. Switch to other toolchain or remove O3 flag (change to Os)
I'll use rmt_storage from sources you provided. I've used rmtfs all time, but seems that there's better replacement. Thanks!
Click to expand...
Click to collapse
You are welcome
And thank you for the infos about the hw buttons, i will definitely test this out!

Update
Hey, here is a small update. It should fix the hw button bug. I also merged some other changes to the kernel, but nothing big.
Changelog:
Kernel
-Kernel compiled with -Os flags instead of -O3
This should fix the hw button bug (thanks to outofmemory13)
-a lot of binder updates
-proper implemention of UID-based routing
-some more things from LineageOS' samsung_jf kernel tree
Click to expand...
Click to collapse
Download 08.07.2018 build
md5sum: 759dc4d116a68888e5bdfbd929b607bb

Update
Hey, here is another small update. This one fixes the brightness bug after booting. I couldn't find the cause of this, but I used my high-class scripting skills *cough* to create a workaround. I think there are no more major bugs left, unless you find one
Changelog:
Kernel
-Compile GPU driver and crypto modules with -O3 again
-Reverted a faulty commit
-Removed F2FS encryption support (not supported for Kernel 3.4)
-Implemented CPU boost (thanks to MarcinDevelopment)
-Small performance optimizations
-Fixed some compiler warnings
Rom
-Deleted one unnecessary vendor blob
-Disabled GPS by default, only relevant for a clean installation
-Updated APN's
-Use low-res bootanimation
-Boot with 1/4 of the maximum brightness
-Implemented the hacky maximum-brightness-after-boot workaround
-Small cleanups
Apps
Fennec
-Updated Fennec (they forgot to build some languages)
If you browser starts to crash after updating, you have to clean Fennec's data. I am sorry if that happens.
Click to expand...
Click to collapse
Download 13.07.2018 build
md5sum: 175f19c16373524fa16a56389b5ecc31

thanks, I have this phone locked in the drawer, I'm installing the rom, I'll let you know how it goes, thanks for everything.
If you have time and desire can you make a ressurection remix?

pablonik79 said:
thanks, I have this phone locked in the drawer, I'm installing the rom, I'll let you know how it goes, thanks for everything.
If you have time and desire can you make a ressurection remix?
Click to expand...
Click to collapse
You are welcome!
I am excited to hear your feedback.
Sadly I don't think that I will spend my time on another rom for this device, just because I still use this phone as my daily driver and I don't want to experiment to much with it. And my internet connection is also not the fastest, so downloading a whole new source code takes really long for me.

Hi Wangenau, This is to let you know thatI am very happy with this ROM, it is snappy, secured and almost everything is working. It looks like mobile data is not working. Any chance that you look into this?

noltha said:
Hi Wangenau, This is to let you know thatI am very happy with this ROM, it is snappy, secured and almost everything is working. It looks like mobile data is not working. Any chance that you look into this?
Click to expand...
Click to collapse
I am glad you like it!
But it is strange that mobile data is not working for you, for me it is working fine. Sometimes there is a rare case where mobile data randomly(?) stops working. You could try to reboot the device, while making sure that Settings->Mobile network settings->Data enabled is marked, wait a bit and see if the problem persists.
Let me know if this will fix your problem :fingers-crossed:
Edit: Removed second option because it is not a good tip

Solve my phone problem
I hope to solve the problem of a phone when I install the ROM is installed and does not work please respond quickly

hhssa said:
I hope to solve the problem of a phone when I install the ROM is installed and does not work please respond quickly
Click to expand...
Click to collapse
Hey, I just saw your post. Sorry if I don't understand, but what is your problem exactly?

wangenau said:
I am glad you like it!
But it is strange that mobile data is not working for you, for me it is working fine. Sometimes there is a rare case where mobile data randomly(?) stops working. You could try to reboot the device, while making sure that Settings->Mobile network settings->Data enabled is marked, wait a bit and see if the problem persists.
If that won't help, you could try to download , move it inside the zip under system/bin/ to replace the existing rild file and flash the zip again (after wiping cache, dalvik cache and system).
Let me know if this will fix your problem :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your suggestions, a simple reboot fixed everything! Many thanks for all your time and efforts you put into this rom, highly appreciated!

noltha said:
Thanks for your suggestions. So maybe I will need to do a re-flash of the rom. I live in the Netherlands, maybe a different band or so. Will try all suggestions and come back
Click to expand...
Click to collapse
A reboot fixed it, so now everything is working!
Really like this Rom!
Many thanks for all efforts!

wangenau said:
Hey, I just saw your post. Sorry if I don't understand, but what is your problem exactly?
Click to expand...
Click to collapse
My problem is after installing the rum does not work the phone

hhssa said:
My problem is after installing the rum does not work the phone
Click to expand...
Click to collapse
I really need more informations to help you. Here are some:
Are you able to boot the device or did the flashing process fail? If it failed, is there an error message in the recovery terminal?
Did you followed the installation guide from the first post exactly?
Did you make a clean Installation, installed the needed recovery version und formatted data and cache as f2fs?
Do you have the right device? (this rom only works in the Galaxy S Plus, not on the Galaxy S or others)

wangenau said:
I really need more informations to help you. Here are some:
Are you able to boot the device or did the flashing process fail? If it failed, is there an error message in the recovery terminal?
Did you followed the installation guide from the first post exactly?
Did you make a clean Installation, installed the needed recovery version und formatted data and cache as f2fs?
Do you have the right device? (this rom only works in the Galaxy S Plus, not on the Galaxy S or others)
Click to expand...
Click to collapse
I've done all the steps but the phone stays in the animation mode for a long time and the phone is not working

hhssa said:
I've done all the steps but the phone stays in the animation mode for a long time and the phone is not working
Click to expand...
Click to collapse
That is strange. Have you tried to redownload the build and reinstall it?
And what was your rom before updating?

{
"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"
}
PixelExperience for Mi Pad 4 (Plus) [clover]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13
Extra Features
PixelExperience feature
Whats working?
Almost everything
Known issues
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
--
ATTENTION: How to flash
* For full steps please check the PixelExperience wiki
Since pixel experience is packed with pixel gapps, the system partition can't hold that large originally.
So I switched to retrofit dynamic partition(aka super.img) and fastbootd(userspace fastboot).
It's logical and won't affect the real partition table which means you can still go mi flash for fastboot or 9008 to flash the system/vendor partiton for un-brick.
However this method DOES NOT support twrp.
To install/OTA update this ROM, you MUST use the pe recovery which is provided with the ROM.(For official, it is also a MUST for publishing, OTA update won't need flash again after/before rom flash, just need you keep the recovery)
For flashing recovery, use following command on your PC
fastboot flash recovery <img name>
Boot to recovery
Tap "Factory reset -> format data"（This will delete all your data! Only need for first time switch to PixelExperience）
Then tap Apply Update -> Apply from adb
Start sideload by following command on the PC
adb sideload <zip.name>
# Or you can just put ROM on a fat32/exfat/ntfs sdcard/usb otg and insert/plug it, then you can choose it in pe recovery like twrp.
If you see any "metadata" related error, just ignore it, it's common on the first dynamic partition flashing, and won't appear next time
To switch to other ROMs, format data in PE recovery first, and then install another recovery then the ROM.
Eg.
1. reboot to pe recovery -> Factory reset -> format data
2. Back to recovery home -> Advanced -> reboot to bootloader
3. flash another recovery such as twrp
4. press vol+ and power to boot recovery
5. do another factory reset (and a format data if it is twrp)
6. install(/sideload) another ROM's OTA zip like MIUI stock or LineageOS etc.(Warning: the ROM to install must have same kernel version with recovery. Eg. you can't use twrp-4.19 to format then install stock MIUI)
Stay tuned
My clover Telegram group
QQ Group: 372404210
Download
Download
History archive/Screen Overclock Image(Use it at your own risk! May damage device and have FASTER battery drain)
​
Android OS version: 13
Security patch level: May 2023
Build author/Device Maintainer: Alcatraz323
Special thanks to kyasu, pix106
Device Source code: Device
Kernel Source code: Kernel
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09

FAQ:
1. How to enable/disable the task bar below?
Long press the space in taskbar or gesture indicator(the white bar)
2. Why 90/85/75/60Hz still laggy or feel like 30hz? Can you provide a overclocked image on pe website?
Google need warms up, so after you booted like for 5mins, it will be smooth on that refresh rate. Also don't give too much expectation on SDM660, it's just a mid-range cpu.
As for OFFICIAL version, I can't provide any overclock, so the full ROM package will be only provided with 60hz.
3. Why twrp get's error/Must use PE recovery?
Check the "ATTENTION" on #1.
4. What is 13 / 13 (Plus edition)?
The 13 (Plus Edition) NOT means it's for pad 4+, It's PE+, the 13、13 (Plus edition) both available for Mi Pad 4/4+. PixelExperience Plus will have more custom features.
Also, if you are already on normal edition, you can directly dirty flash the same date plus edition or newer plus edition.
5. How to solve heating/power drain too fast on idle?
Usually this won't happen when you clean flash this ROM, and often caused by LTE driver and a system application updated by the Google Play Store called: Android System Intelligence
So, just try enable airplane mode and uninstall the update for that app then reboot will solve (Settings - Application - Find "Android System Intelligence" and click top-right corner button)
6. Why there is always a {"Press any key to shutdown"/fastboot cmd error(like send size error something else} on PC when I try to do something in bootloader like flashing a recovery/unlocking bootloader?
Your USB port on your PC, your cable and your device is not matched. Like Mi Pad 4 is USB 2.0 but you connect to a PC with USB 3.X on that(Usually laptop user). Change your usb setup to match it same: PC USB2.0 cable USB2.0. Or you may google for USB3.0 Reg patch for xiaomi. I don't have it here.
7. How to flash certain partition with pe recovery? (like boot, frp, recovery, persist)
Use
fastboot flash partition_name partition_name.img
OR
In pe recovery:
Advanced - enable adb
Then On PC:
adb push partition_name.img /tmp
adb shell
dd if=/tmp/partition_name.img of=/dev/block/by-name/partition_name
8. Why I lost all my sensor/can't rotate screen after flash?
Clover has a fragile persist partition, sometime it will broken and cause these syndrome after a rom flash. It's not only happen when you flash pe, but flash any rom. Just flash a persist.img backup(yours' is best, but you can also download from others like from other's backup on xda post(like this: https://forum.xda-developers.com/t/...omi-mi-pad-4-unofficial.4514507/post-88228039), thanks ichigo_kurosaki), for the flashing instruction please check the #7 FAQ above.
9. Why my video recorded in 2160p(4k) can't playback(stucking)?
First of all, this device is originally support to 1080p30, the 60fps and 4k recording is force enabled, then SDM660 has a poor video decoder profile, some software may not try to decode 4k even it's announced 4k compatible, you may try playback the 2160p(4k) recordings from your computer, it will work. Or you may try some professional player like VLC.
==============================================
Special notice: Flash the OFFICIAL RECOVERY and CLEAN FLASH if you are from UNOFFICIAL or OTHER SYSTEM please!!!
Current Update(Both PAD 4/4 Plus):
PE Normal Edition(13):
2023.5.19
Device:
kernel: qcom sdm660 kernel update LA.UM.11.2.1.r1-03900-sdm660.0(kernel main/kgsl/wifi-fw-api)
device: qcom sdm660 driver/HAL update LA.UM.11.2.1.r1-03900-sdm660.0(camera/audio)
device: add fastbootd option in advanced reboot(pe plus only, normal pe has no advanced reboot function)
device: add a switch in battery management system to turn off charging ripple animation
Upstream:
Minor platform framework fix
PE Enhanced Edition(13 Plus Edition):
Dirty flash in rec to manually switch to PE Plus, but backup data in case for any accident!!!
Everything above included, and:
- N/A
==============================================
History Updates (non-plus):
2023.2.10 - First release
Introduce PE 13 for Mi Pad 4 (Plus)
2023.2.12
Device:
kernel: switched to 4.19
device: add mi settings
2023.2.18
Device:
kernel: fixed wake brightness burst
kernel: backported fuse passthrough from kernel 5.4 for better android storage performance
device: fixed camera stuck in 3rd app
device: moved xiaomi settings back in Settings -> System
device: added auto removal for wifi only/no fingerprint models
device: switched to erofs, f2fs, fbeV2+emmc_optimization(MUST use new recovcery and FORMAT DATA)
device: fixed weird power off charging ui
device: fixed SD card format in two modes
device: fixed microphone
device: enabled ZRAM writeback
2023.2.20
Device:
device: fixed backlight adjustment on Plus variant
device: fixed usb mode detect on Windows(Mtp or so)
2023.2.24 - First OFFICIAL build
Device:
device: fixed real MAC reading
device: fixed charging led won't work on high battery percent
device: fully translated xiaomi settings for CN
2023.2.27
Device:
device: fixed brightness driver burst for 8inch. (Plus has no burst issue)
device: fixed device setting can't display by side as tablet mode
kernel: update to 4.19.273
kernel: power optimized
2023.3.3
Device:
device: fixed "UNKNOWN SOC TYPE" in some system info type apps (SDA660)
device: fixed cpu freq scheduler always locks max freq by uclamp
device: enabled 60fps recording in camera
device: enabled cgroup freezer
Upstream:
February security patch
Google Apps updated
Fixed battery drain and lag spike caused by Pixel Launcher (Need to uninstall previous updates of Android System Intelligence or do a clean flash if the issue persists)
Fixed SafetyNet not passing
2023.3.24/5
Device:
kernel: update to 4.19.278
kernel: backport 5.10 fuse filesystem
kernel: reduce power consumption for 8 inch screen
device: reduce continuous ui rendering jitter/lag
2023.4.1
Device:
device: add "Usb fast charge on usb3.0 port"(500mA - 900mA) in Xiaomi Settings
device: switch to aosp task/cpu management for some critical tasks(util clampimg)
device: audio quality HUGE fix
device: "Mi Pad 4 Plus" will be differred in System info as well as the default dpi
device: lower memory pressure caused by bad Qualcomm legacy io scripting
device: optimize round corner
device: won't show a fingerprint page on first boot setup for 8inch now
device: complete software codec2 support (aosp_sw)
device: use [email protected] HAL(full USB config panel like reverse charging/role change)
device: set baseband as "Wi-Fi Only" instead of "Unknown" for wifi variant
device: further improve ui/animation lagging
device: optimize RAM consumption
device: optimize background app caching
device: deprecated sdcardfs and use native Android 11 new filesystem base, which supports better scope storage
device: more balanced irq control
device: other minor fix
kernel: minor optimize
Upstream:
Fixed something bad in QPR2(0324/5, below is copied from last)
Android 13 Quarterly Platform Release 2 (QPR2 - lots of new ui/behavior changes)
Enabled multi user switcher on lock screen for large screen device(>600dp)
Source rebased with March security patch
Updated GApps
Updated translations
Minor fixes
2023.4.19
Device:
kernel: update to 4.19.279
kernel: switch default io scheduler to bfq(reduce cpu consumption/power/lag, also +1500 AnTuTu storage score)
kernel: fixed step-chg/sw-jeita(thermal) for pm660_charger/fg
kernel: fixed otg passive mode issue, need one REBOOT after OTA/sideloading
device: fixed system partition not in erofs(increase boot up speed, system app speed)
device: make setup wizard landscape available
device: enable auto rotate by default
device: separate notification and ringtone volumes
device: fixed charge speed issue for LTE/Plus after hang off a call
device: force recovery update with system
device: irq balance now using 4 big cores (previously only 2 big cores)
device: CloverParts: add volume panel trigger in QS
device: CloverParts: add my battery manage system (Settings -> Battery -> Battery Management System) - Step charger / thermal charger switch
- Mode: limit battery around 40-60%
- Mode: limit battery around 80%
Upstream:
April security patch
Updated translations
Optimizations on battery usage of Pixel Launcher
Minor issues fixed
2023.5.3
Device:
kernel: update to 4.19.282
kernel: sdm660 kernel driver update from qcom(wifi/kernel/audio)
kernel: minor fix & optimize
device: expand wifi signal tolerance(reduce disconnect on bad wifi)
device: update display driver for sdm660(gralloc - HAL/display)
2023.5.7
Device:
emergency fix: 0503(PE Plus): headphone jack
emergency fix: 0503(PE Plus): camera video recording
device: allow 5G hotspot(called "Extend compatibility" in settings, reuquires a factory reset if you need it)
Upstream:
May security patch
Updated translations
Updated Google Apps
Minor issues fixed
2023.5.19
Device:
kernel: qcom sdm660 kernel update LA.UM.11.2.1.r1-03900-sdm660.0(kernel main/kgsl/wifi-fw-api)
device: qcom sdm660 driver/HAL update LA.UM.11.2.1.r1-03900-sdm660.0(camera/audio)
device: add fastbootd option in advanced reboot(pe plus only, normal pe has no advanced reboot function)
device: add a switch in battery management system to turn off charging ripple animation
Upstream:
Minor platform framework fix
==============================================
History Plus Updates:
2023.2.10 - First release
- N/A
2023.2.12
- N/A
2023.2.18
- N/A
2023.2.20
- N/A
2023.2.24 - First OFFICIAL build
- N/A
2023.2.27
- N/A
2023.3.3
- N/A
2023.3.24/5
- N/A
2023.4.1
- N/A
2023.4.19
- N/A
2023.5.3
- N/A
2023.5.7
- N/A
2023.5.19
- N/A

Reserved

Saw your patch on Gerrit for fixing launcher on tablets, I didn't realize that you have a clover!

perfect rom installed. I wanted to ask if you could build on kernel 4.19 and include the xiaomi parts to have screen color management and volume enhancement
( kernel 4.4 is no longer supported eol )

Piccolo1 said:
perfect rom installed. I wanted to ask if you could build on kernel 4.19 and include the xiaomi parts to have screen color management and volume enhancement
( kernel 4.4 is no longer supported eol )
Click to expand...
Click to collapse
Trying 4.19, and screen color manage is in Display->Live display for now

Alcatraz323 said:
Trying 4.19, and screen color manage is in Display->Live display for now
Click to expand...
Click to collapse
if it can be useful to you there is a very good developer pix106 you can use his 4.19 trees and believe that he also integrates the xiaomi parts. of the xiaomi parts it was useful to boost the volume of the speaker
pix106 - Overview
pix106 has 49 repositories available. Follow their code on GitHub.
github.com

Piccolo1 said:
if it can be useful to you there is a very good developer pix106 you can use his 4.19 trees and believe that he also integrates the xiaomi parts. of the xiaomi parts it was useful to boost the volume of the speaker
pix106 - Overview
pix106 has 49 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
Successed with his kernel, uploaded 4.19 version, you may try it
thanks for the information, and the future version will be developed base on 4.19

Alcatraz323 said:
Successed with his kernel, uploaded 4.19 version, you may try it
thanks for the information, and the future version will be developed base on 4.19
Click to expand...
Click to collapse
I'm happy to have been helpful to you. I installed your new rom and it's perfect! Thank you ❤

Piccolo1 said:
I'm happy to have been helpful to you. I installed your new rom and it's perfect! Thank you ❤
Click to expand...
Click to collapse
Hi! You have mi pad 4 8'?

Zirafa said:
Hi! You have mi pad 4 8'?
Click to expand...
Click to collapse
Yes 8 LTE

Hi , fantastic rom , however I constantly get Bluetooth keeps stopping error? any help appreciated

aGoodEightInches said:
Hi , fantastic rom , however I constantly get Bluetooth keeps stopping error? any help appreciated
Click to expand...
Click to collapse
reset the tablet from the settings

0218 Updated
WARNING: Huge change to filesystem, MUST use new recovery and do format data before moving on
Check #2 for changelog

Hi
What are these files for?
boot_XXhz.img
And what's the difference?

LeshaRB said:
Hi
What are these files for?
boot_XXhz.img
And what's the difference?
Click to expand...
Click to collapse
Screen refresh rate overclock, may damage device

Thank you for a great rom.
I installed version 2023-02-18 and during various tests, I noticed an issue with microphone sound not being input.
The test app used Google recorder, and it was able to record the bluetooth microphone, but not the mipad4 device microphone.

NetHana said:
Thank you for a great rom.
I installed version 2023-02-18 and during various tests, I noticed an issue with microphone sound not being input.
The test app used Google recorder, and it was able to record the bluetooth microphone, but not the mipad4 device microphone.
Click to expand...
Click to collapse
Will look into it

Thank you very much for the great work.
Very fluid and so far working perfectly.
It only lacks the play protect certification. Uncertified device.
I hope to give my Mi pad 4 tablet a long life with this ROM.

Batoyer1 said:
Thank you very much for the great work.
Very fluid and so far working perfectly.
It only lacks the play protect certification. Uncertified device.
I hope to give my Mi pad 4 tablet a long life with this ROM.View attachment 5840005
Click to expand...
Click to collapse
That's common for Jan pe, fixed in coming Feb