Database Users

[APP] Quick CPU Overclock

Hi all, I'm developing a quick solution to overclock/save battery so get this!
This app lets you to control your CPU clock and governor. The widget lets you choose the CPU profile with just one click.
The quickest CPU control application. Switch easily and fast between CPU profiles by tapping the widget on your homescreen or using the app.
You can create multiple CPU profiles. You want to play and need more power? Overclock your CPU! Need more battery life? You can easily double it.
You can choose the right profile whit just one tap, whenever you want.
Automatic detection CPU's available frequencies and governors.
Dual core devices support.
Features:
+ Overclock your CPU (more power)
+ Powersave battery (speed down)
+ Advanced real-time device infos (kernel, uptime, CPU load, CPU clock, stats, memory, battery, etc.)
Two widgets: switcher and single.
Link:
https://play.google.com/store/apps/details?id=org.jop.android.cpuprofiler
HERE'S THE PRO FREE BETA VERSION:
https://play.google.com/store/apps/details?id=org.jop.android.cpuprofilerprobeta
PRO features:
+ Save/backup profiles
+ Automatically set a profile when a trigger is pulled (es. screen off, phone on charging, low battery)
+ etc.
Please give it a try and report any issue, obviously , free pro version for you when ready
THANK YOU!

[Q] CM10 hide navbar like CM7

I looked around for this but couldnt find it. I recently went to CM10 (12-26 nightly) from CM7 and noticed there isnt a navbar hide button like in CM7. Is there anyway to hide the navbar while in app? 90% of usage comes from my 3 year old daughter playing dr panda, cut the rope, where's my water, ect... and i know she will constantly hit the nav buttons if their not hidden like previously. I hate to go back to CM7 as this seems much smoother and prettier too.

indigoataxia said:
I looked around for this but couldnt find it. I recently went to CM10 (12-26 nightly) from CM7 and noticed there isnt a navbar hide button like in CM7. Is there anyway to hide the navbar while in app? 90% of usage comes from my 3 year old daughter playing dr panda, cut the rope, where's my water, ect... and i know she will constantly hit the nav buttons if their not hidden like previously. I hate to go back to CM7 as this seems much smoother and prettier too.
Click to expand...
Click to collapse
Go to system-power menu-expanded desktop and select to enable it. When you want to hide Nav bar all you have to do is press power button for 4 seconds (just like rebooting). The menu pops up. Select expanded desktop to enable/disable Nav bar. When Nav bar is hidden long press n button to bring up recent apps.

Thanks, exactly what I was looking for!
Since you have 2 NC's do you have any tips for speeding up CM10? I set the CPU to performance and 1100 mhz on boot. Im really unfamiliar with kernels and such, I tried the V6 script before and didnt notice any difference.

indigoataxia said:
Thanks, exactly what I was looking for!
Since you have 2 NC's do you have any tips for speeding up CM10? I set the CPU to performance and 1100 mhz on boot. Im really unfamiliar with kernels and such, I tried the V6 script before and didnt notice any difference.
Click to expand...
Click to collapse
The Nook Color has 512mb of ram, which 449mb is available for user programs. The optimal performance occurs when the CPU operates at 1100 MHz and free ram of at least 180mb. These are my settings for cm10: standard background apps running and kill app back button enabled in developer option-allows kill app by long press of back soft key in navigation bar, interactive governor, min CPU 300 MHz, max CPU 1100 MHz set on boot, I/o scheduler bfq set on boot, zram at 26%, purging of assets allowed and kernel same page merging enabled. I have never experienced sods with this setup-lucky for me. Over clocking to 1200mhz proved to be unstable most likely due to enabled hardware acceleration. CM7 does not have hardware acceleration, thus over clocking on that ROM went higher. I also turn off push notifications for email, games etc. These reduce battery runtime. I can't comment on v6 since I don't use it. Your mileage may vary. Hardware performance may vary on each device. That is why manufacturers underclock the processor even though the cpu is rated higher.

indigoataxia said:
Thanks, exactly what I was looking for!
Since you have 2 NC's do you have any tips for speeding up CM10? I set the CPU to performance and 1100 mhz on boot. Im really unfamiliar with kernels and such, I tried the V6 script before and didnt notice any difference.
Click to expand...
Click to collapse
From my experiece and understanding, V6 does not really give a noticeable performance boost, it changes the OOM settings to help keep the device memory free so that you don't need to kill apps to free up memory. It can also change other settings to improve launcher stability, etc.

For those who get AOSP sound stuttering...

I've been having this issue since around October last year and finally found a way to minimize it.
Here's what i did:
- Installed Performance Profile xposed module, and added a spotify profile.
- - Upped the NICE priority for foreground and background.
- - Set min CPU frequency to 384Mhz.
- - Set CPU governor to interactive and IO scheduler to row.
- Installed Trickster Mod
- - Changed Read Ahead Buffer Size from 128 to 256, as this is what it is on Sense.
- Disable wi-fi optimization
- - Settings > Wi-fi > Advanced > Uncheck Wi-Fi optimization
- (Optional) Installed Viper4Android
Now i get pretty much flawless sound with minimal and barely audible stutters/crackles once every hour or so :victory:

Thanks, will try

✭[Updated : 17/2/17][GUIDE][Discussion] Hacks And Tweaks For Battery Life✭

Hello Folks.
So, everyone is facing battery life problems in our Xperia Devices. And many of you are getting 3-4 hours of SOT. Here are Some of my hacks and tweaks to have a prolonged battery life and approximately 6+ hours of SOT.
- The device used for these tweaks is Xperia Z2 with eXisteZ Rom. These tweaks may differ on different Rom. It can be better it can be worse.
- FAQ's in the #OP2
Let me first show you some results.
1. 100-6% 9hrs and 15 mins of SOT (by me )
{
"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"
}
2. Here is @cristixperia's 7+ hours SOT after following this thread
Important:
Battery life majorly depends on the battery condition or how old is the battery. So, If your battery is like 1 year old then it will have a less SOT than a new battery with same hacks. So, please see the condition of your battery , which probably gets worsened with time.
Battery life also depends on the thermal conditions of battery. If the battery temperature is hot the drain will be more. The temperature should be around 30-35 or less for good battery life and charging rate. So, make sure you battery is not extremely heated or extremely cold.
I'm adding Priority Levels of each step out of 5. So, it will be easy for you to understand the importance of a step in saving you battery life.
So, Here it Goes. Enjoy.
1. Greenify (Priority:5)
Credits for this app to @oasisfeng
Greenify is the one of the best battery saving apps. It can be used to hibernate the background apps or the apps you use less often. Plus when it is used with Xposed and Donation Package features is saves some real juice.
Download Links:
Greenify
Greenify Donation Package
I'm using version 3.1 build 1 with Donation Package. Here are my settings.
Here is the List of apps to be Greenified :
List 1
List 2
P.S.: GREENIFYING SYSTEM APPS CAN CAUSE SOME SERIOUS PROBLEMS. PLEASE ASK BEFORE HIBERNATING SYSTEM APPS.
2. Fixing the Google Play Services Drain (Priority:5)
Google play services have been draining the juice from our battery from a very long time. >_> with no fix. And they have always benn the top battery drainers. So, apparantly @iXaidyiu and I have found a fix for this drain.
METHOD 1 : Using AppopsXposed
1. Install AppopsXposed from Xposed Installer.
2. Open AppOpsXposed and select Google Play Services and disable the following (see the screenshot).
3. Open AppOpsXposed and select Google Play Store and disable the following (see the screenshot).
4. Open AppOpsXposed and select Google Play Framework and disable the following (see the screenshot).
5. Open AppOpsXposed and select Google App and disable the following (see the screenshot).
After these steps reboot you device and see the google play services drain gone. But that will be gone from the battey(settings) after a full charge or it will show the previos drains.
Thanks to @iXaidyiu for playing with AppOpsXposed and finding this.
METHOD 2 : Using HEBF Optimizer
Credits for this app to @IvsomEmidio
Download Links:
HEBF Optimizer
Follow these steps to get rid of Google Play Services Drain
1. Open HEBF
2. Select Chuck-Norris Type of User(if it is the first time you are opening the app)
3. Select BATTERY from sidebar.
4. Enable GOOGLE PLAY SERVICES DRAIN FIX(Master)
5. Enable all 4 options i.e. Locations Services, Check-IN Services, System Update Services, Usage Report.
6. Reboot and Enjoy.
3. AMPLIFY (Priority:5)
Amplify is a serious battery saver. Amplify can help you to limit some wakelocks, services and alarms for saving battery life. A great tool if used in the right way. It is the best battery saver I've come across and is a must have app if you are running Xposed.
P.S. : How to Set Up Amplify
Or you can use this guide how to use AMPLIFY+ GREENIFY + POWERNAP as combination by @v7 to have the best battery life of your device.
4. Force Doze (Priority:5)
credits for this great app goes to @ssrij
Download Links:
Force Doze
ForceDoze is an app that forces Doze mode right after you turn off your screen. Instead of waiting for the default time period (30 mins), Doze kicks in immediately. ForceDoze also disables motion sensing, so Doze doesn't activate while in your pocket or while the device is moving with screen off, giving far more battery savings than standard Doze functionality.
Here are my Force Doze's Settings.
Apps to be Whitelisted:
ForceDoze doesn't increases your sot but it makes sure your battery remains at the same level you left it. So, technically it increasesyou Screen ON Time. Seriously a great app. But whitelist your instant messengers and the apps you want to get notification from. because force doze can delay notification and can have some serious issues with your phone. use wisely.
For Queries and problems go to the main thread --> here
5. L Speed (Priority:5)
by @Paget96 Thank you brother for this amazing app.
Lspeed is a powerful app with the simplest interface. And can make a serious difference in your screen on time if applied with appropriate settings.
SETTINGS by @iXaidyiu
SETTINGS by @Paget96
Important:
1. Do not use Lspeed And HEBF simultaneously. If you want to use them both at the same time, Make sure you dont enable anything from HEBF except Google Play Services Drain FIX. And change the Lspeed's Apply on Boot time to 20 secs, from settings. JUST TO BE SAFE.
2. If you are using Force Doze then disable Lspeed's Agressive Doze and vice versa. OR Else there will be some conflicts.
6. Disabling Fast Dormancy (Priority:5)
What is Fast Dormancy? In simple terms its a device feature that enables mobile devices to notify the cellular base stations when the radio resource allocated to the device is no longer in use, so that the radio resource could be immediately released other than waiting for a timeout event. For instance lets say you are browsing a webpage using your cellular data plan. You stop at a certain webpage (for example to read this article) the connection is maintained and the device will be registered on the network even if data isn’t received or transmitted (always on) and will remain like that until a timeout event is invoked (as per the network rules as to how much time to wait before connection is terminated due to idle timeout). During this time the device’s battery will be drained needlessly in addition to increased congestion on the cellular network due to numerous idle connections. From a device perspective radio power consumes battery so employing fast dormancy should save battery power and increase its life. This also has an advantage to networks as it reduces congestion. But This doesn’t come without a major disadvantage to the very same cellular networks and operators. The making and breaking of the connections increases the signaling traffic and wastes network resources. The workaround to this was done by Nokia Siemens in collaboration with Qualcomm to employ NCFD or Network Control Fast Dormancy in which the device is put on a battery saving idle state while maintaining its network identity without the need to establish a new connection and request a new identity for the device on the network.
Can Increase your battery life by 30%.
How to Disable Fast Dormancy?
Check out this thread by @mirhl. All credits goes to him. The thread is pretty old but it still works.
But if you have problem in understanding here is a simple guide:-
1. Get you carrier MCC and MNC from Wikipedia.
2. Open youe file manager and go to root/etc/fast-dormancy/fd_custm_conf.txt
3. There you will see two lines ending with MCC and MNC with two zeroes.
4. Change those zeroes to the MCC and MNC code you got from Wikipedia
5. Save it. Reboot And Enjoy.
7. KCAL FLASHABLE MODULE FOR MINIMUM BRIGHTNESS (Priority:4)
The credits for this awesome module goes to sir @venkat kamesh.
Brightness has always been the biggest battery drainer of all time excluding the google play services. This module will help you to achieve lower brightness than the minimum threshhold. There are many other options also grayscale display is my personal favoutite. I was testing this module for like 1 week and the results are great. This can significantly increase your battery life.
After flashing this module, you'll see a COLOR CONTROL app in your app drawer.
1. Go to the app.
2. Enable Set on Boot.
3. Change minimun value from 35 to around 100. And then change the value of red blue green to the minimum value.
4. Now change your minimum value to what suits your eyes. and save. I've personally set it to 140. Set according to what suits your eyes.
5. Also the grayscale display is awesome for the users that like black and white display.
Dont set MINIMUM to 0 or else your screen will go black and you wont be able to see a thing unless you've a Sharingan
P.S. : Battery on point. [emoji14]
8. Stamina Mode (Priority:4)
Okay. So, Most of us use stamina mode after 15-20% only. But i've been using it from 100% for past one week ans the results are amazing. I've set to Device Performance Preferred and still it is working better than no stamina mode.I can assure you it can increase your SOT by almost 1+ hr if you keep it on Always On.
1. Go to Settings < Battery < Stamina Mode.
2. Select Always On.
3. Select Power Saving Level
4. Select Device Performance Preferred.
9. Removing Xposed Modules (the battery drainers) (Priority:4)
So, i've noticied that some of the xposed modules drains battery when activated. so' ll be listing them below. You can also contribute by telling me some of those xposed modules.
-> Flat Style Coloured Bars
-> Flat Style Bar Indicator
-> Google Assistant Enabler
You can also share your experiences with different xposed modules. if you think that a specific xposed module drains battery please post below and it will be added to the OP after some testing.
The Next 3 steps are regarding turning the screen to black for saving battery. These methods work best on Amoled Displays. As our Xperia Devices have LCD displays so these might be not as effective on our Devices. But I've got the 9+ Screen On time using these. And when I swithed back to white the SOT got to almost around 6-7 hrs with the exact same usage. So i'm sharing these methods. (This was for all those people who were saying dont post fake methods or these methos don't work.)
10. Monochrome App (Priority:4)
Download Link:
Monochrome
Monochrome automatically turns on monochrome (or black & white) mode when your battery is low, to further reduce display power consumption when your battery level is low. This means your device will eat less battery. Simple but effective app. With stamina mode combined, after 15% it can give around 1-1.5 hr + SOT.
11. Black Notification Panel And Notification (Priority:3)
(works great with n-ify xposed modules)
Credits to @iXaidyiu for telling this.
Okay. So we all know white color drains more battery than black. This method will turn your notification panel black. Saving some battery and also looking aesthetically good. So my friend or i should say brother, @iXaidyiu found a way to turn the notification panel and the notification black. Saving almost 10-15% battery.
Follow the steps for this type of notifications.
1. Go to settings > eXistenZ >Notification Panel > Notification Settings
2. Enable Custom Notification Color
3. Select the Notification Background Color to #000000 or to black.
if you are using Android N.ify Xposed Module then :-
4.If you are on n-ify, go to N-ify > Notifications
5. Enabe custom actions background color.
6. Select the Actions Background Color To #FF141313 or to Black.
P.S.: THERE IS A BUG WITH THIS METHOD. THAT IF THE MESSAGES ARE MORE THAN 1. YOU'LL NOT BE ABLE TO SEE THEM. BUT IT WORKS FINE.
4. Black Keyboard and Apps (Priority:3)
As i've told earlier black saves a lot of battery and is also good for your eyes. And we people use keyboard for all the purposes. So, having a black keyboard instead of a white one saves some battery.
Use google keyboard and choose a pitch black theme.
The more you use the black color, the more the battery. So, its on You how much battery you want.
use black themes in your apps. DARK WALLPAPERS. and using black color at most of the places will save some serious juice.
12. Miscellaneous Tweaks (Priority:4)
-> Disable wifi and bluetooth scanning from Settings > location > menu > scanning to save some more battery.
-> Facebook and Facebook Messenger are big time battery drainers. So, try switching to another light apps for some battery saving. I use Folio for Facebook. Its night mode is awesome and it has options to refresh notification in a specific interval of time. You can also use some other apps like SlimSocial for Fb or MaterialFB. You'll also see increase in performance of your device after removing Fb and fb messenger.
-> Even if your Wifi is off,your phone searches for Wifi Signals.To switch off this feature,Go to Settings > Wifi > Options(Top right corner) > Advanced >Scanning always available(Off).
-> Do not use Adaptive Brightness. Also try to keep your Brightness to Minimum.
-> Removing unnecessary apps. They keep draining Battery in the background. For this, you can use my DEBLOATER SCRIPT. You'll also see an increase in performance of your Device.
So, this is all. With these methods you can also get 6-7 hrs of SOT. And i'll be posting more methods if I get to know some.
P.S. : I'm not responsible if something happens to your device. Proceed with precaution. Stay Safe.
SPECIAL THANKS TO THESE PEOPLE FOR HELPING THIS THREAD:
1. @iXaidyiu
2. @panzerox123
3. @Davey126
4. @Paget96

This FAQ comes in various sections:
General FAQ over eXistenZ MM ROM (Z2/Z3):
Declaration on the compativitiness of the battery savers and tweaks:
ReadMe over Amplify tweaks:
L Speed
Core Strategies on Achieving Ideal Battery Life
"Mobile Radio Active"!?
--------------------------------------------------------------------------------------------------------
1. General FAQ over eXistenZ MM ROM (Z2/Z3):
1.1 This ROM is DISCONTINUED due to @niaboc79 swapped phone.
1.2 Installation
1.2.1 Install ONLY v5.01 and v5.6.5 in a row will be enough.
1.2.2 If you come from AOSP-M/AOSP-L/AOSPA-M/PACMAN-L/etc..., please perform a clean install by first wiping /system, /data, /cache and /ART in TWRP and then kick start the ROM installation process.
1.2.3 If you are rolling back from AOSP-N/etc... that is based on android N, please first restore stock .FTF via flashtool by androxyde, then wiping /system, /data, /cache and /ART in TWRP and after that kick start the ROM installation process.
1.2.4 If you are switching from other stock based roms, eg Kypotian-M/PureX-M/Mr SL-M/etc..., please first wipe /system, /cache and /ART and then kick start the ROM installation process.
--------------------------------------------------------------------------------------------------------
2. Declaration on the compativitiness of the battery savers and tweaks:
iArvee said:
...
-Greenify's Aggressive doze kicks in 7 minutes after screen off, I don't know why 7 minutes but I'm guessing there's a reason behind it. Well, roughly 5-7 minutes. Since they work together, I guess it's not so bad to have both of them make sure that your phone is on doze.
-It stays in memory, yes but it's inactive. If the app is completely stopped/closed, writing the app to memory again would use more battery. Think of the regular hibernation similar to force closing an app.
-Indeed you are right, it's hard to play with settings like that. May I suggest adding init.d scripts? Or use HEBF/Lspeed? I tried this interactive governor profile tweak on the Z2 months ago and it brought me to at least 5 hours SoT, with 30% brightness (auto) and mobile data on most of the time.
...
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------
3. ReadMe over Amplify tweaks:
The suggested elements to be limited and look after in v7's thread is not Sony specific. So we have to EXPLORE ON OUR OWN to find the best ways to conserve energy using the daemon tool. So what I am suggesting on behalf @Dr. Death is that besides adopting most of the rules listed on v7's thread concerning using Amplify to conserve energy, we should also explore and test setting rules for other wakelockes too. Last but not least, so what I am implying about is that we all have an unique list of installed apps on our phone from each other, therefore there isnt really a must do list for apps' wakelocks and alarms, after all it is up to you to choose from performance and battery. Considering that, me and @Dr, Death WILL NOT provide any further lists for recommendation so as to let you guys explore on your own.
Happy tweaking!
--------------------------------------------------------------------------------------------------------
4. L Speed
Dr. Death said:
1. Lspeed's Performance Governor increases performance but there was a large drain in battery compared to battery governor. And with brightness increased to >30% , the drain increased exponentially. The performance of the phone was increased though (acc. to benchmark scores).
2. Lspeed's Battery Governor makes a big difference in saving your battery. Though, I've also noticed that it also decreases some amount of performance. But I've been using the battery governor and I've not seen a lag or freezing down of any app. You cant even tell there is a decrease in performance without benchmark scores. And the difference in SOT the battery governor can make is almost 30 minutes to 1 hour. So, I'm using it and you people can also use it, if you want more battery
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------
5. Core Strategies on Achieving Ideal Battery Life
Davey126 said:
- stop apps from launching at startup/wake and on network events
- reliance on native doze (w/Doze on the Go enabled on Android 6)
- proactively hibernate misbehaving apps - especially on Android 4/5
- sensible app selection and configuration (avoid the pigs)
- common sense settings for screen brightness, radios and sensors
- minor govonor tunings if needed (eg: delaying jump to max freq)
- primary tools: Greenify, BBS/GSam, AppOpsXposed, SD Maid, MAT
Best guidance: find excellent resources like this thread, read, observe, read some more, react only to items that warrent attention and yield meaningful results with minimal side edfects. Ignore everything else.
Those who love to tinker with their devices should avoid all the above. It's boring, effective and leaves ample time for other activities.
Click to expand...
Click to collapse
Davey126 said:
Agreed. Tuning and measurement are key. That said, some devices do not idle/perform well at low frequencies. A Moto G4 Play (Snapdragon 410/MSM8916) serves as an example. While the stock kernel allows 200Mhz bottoming out at 400Mhz imposes no penality while delivering a better overall experience. Clearly this weakling does not reflect state of the art cpu/chipsets; nor is it an outlier.
Don't get me wrong - I love the idea of underclocking/volting when it can be done easily and yields measurable benefits with no undesirable side effects. Usually other tunings are required to achieve that.
Also recognize there's a cost (albeit minor) associated with regular frequency hopping. Holding the idle frequency steady in the absence of a significant load yields the best results IME.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------
6. "Mobile Radio Active"!?
Davey126 said:
Radios can be significant drainers in low signal strength conditions as power is ramped to maintain a stable connection. On the mobile front I often find 3G (when available) yields an acceptable compromise, although LTE will typically come out ahead on overall power consumption when signal strengths are moderate/strong provided modem quickly drops into idle mode when not in use. The latter is largely outside user control although custom kernels can sometimes help.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------
Credits to the followings:
@Dr. Death for leading this tutorial
@iArvee for declaring facts
@Davey126 for providing core tweaking strategies
--------------------------------------------------------------------------------------------------------
Anything I found useful and important in the comments will be pushed up here

CHANGELOG
12/18/16
Added Kcal Module for Minimum Brightness.
Added Additional Methods.
Click to expand...
Click to collapse
12/23/16
FAQ's added by @iXaidyiu.
Click to expand...
Click to collapse
12/28/16
Updated the list of apps to be greenified.
Click to expand...
Click to collapse
2/1/17
Lspeed App
Click to expand...
Click to collapse
17/2/17
1. Updated the whole thread.
2. Added Fast Dormancy.
3. Added HEBF.
4. Added Priority Levels.
5. Added @Paget96's Settings to the thread.
Click to expand...
Click to collapse

Thanks bro ?
Xperia Z2™

This is wonderful. Tomorrow I will flash ExistenZ again and make the proper combinactions I only can't really understand how to use Amplify, but I will give it a try! Thanks again!

manfred18 said:
This is wonderful. Tomorrow I will flash ExistenZ again and make the proper combinactions I only can't really understand how to use Amplify, but I will give it a try! Thanks again!
Click to expand...
Click to collapse
I've attached the thread for amplify. There is a step by step guide. Enjoy your battery life

Dr. Death said:
I've attached the thread for amplify. There is a step by step guide. Enjoy your battery life
Click to expand...
Click to collapse
I didn't know about N-ify, it's great, I've already installed it. Probably there are many mods that I don't know. So I suspect ExistenZ is the best ROM overall for Z2 now?

Nice tutorial
Envoyé de mon F8331 en utilisant Tapatalk

niaboc79 said:
Nice tutorial
Envoyé de mon F8331 en utilisant Tapatalk
Click to expand...
Click to collapse
Tysm. It means a lot to hear it from you.

manfred18 said:
I didn't know about N-ify, it's great, I've already installed it. Probably there are many mods that I don't know. So I suspect ExistenZ is the best ROM overall for Z2 now?
Click to expand...
Click to collapse
Which version you are using for n-ify ?
Yes Indeed existenz is the best rom :')

Dr. Death said:
Which version you are using for n-ify ?
Yes Indeed existenz is the best rom :')
Click to expand...
Click to collapse
I've installed 0,2 probably.
ExistenZ is great, but I have a bit lag somewhere sometimes
But when I installed new drivers from Qualcomm I've got 63000 in Antutu. But lag sometimes exists.

manfred18 said:
I've installed 0,2 probably.
ExistenZ is great, but I have a bit lag somewhere sometimes
But when I installed new drivers from Qualcomm I've got 63000 in Antutu. But lag sometimes exists.
Click to expand...
Click to collapse
Get the latest version of beta n-ify for regular updates from here.
https://ci.paphonb.xyz/jenkins/job/AndroidN-ify/
Installed new drivers how ?63000 is sick? I got Max 57k. Tell me about this I installing drivers.

Dr. Death said:
Get the latest version of beta n-ify for regular updates from here.
https://ci.paphonb.xyz/jenkins/job/AndroidN-ify/
Installed new drivers how ?63000 is sick? I got Max 57k. Tell me about this I installing drivers.
Click to expand...
Click to collapse
http://forum.xda-developers.com/z3/themes-apps/mm-6-0-1-qualcomm-adreno-drivers-june-t3415394 I've got easily 63000. I have screenshots It's for Z3, but you can install safe for z2

I thought the pixels of the screen were off only on AMOLED panels. Our panel is IPS, the black colors drains the same amount of battery as the white colors..

manfred18 said:
http://forum.xda-developers.com/z3/themes-apps/mm-6-0-1-qualcomm-adreno-drivers-june-t3415394 I've got easily 63000. I have screenshots It's for Z3, but you can install safe for z2
Click to expand...
Click to collapse
Tried 2 times still got 59k and 61k ._.
Will test some more. Though ty for this :')

Little Snevil said:
I thought the pixels of the screen were off only on AMOLED panels. Our panel is IPS, the black colors drains the same amount of battery as the white colors..
Click to expand...
Click to collapse
Yes you are right, about the amoled one but even on our screen it saves battery. I've tested. Without the black notifications and black keyboard I used to get 5-6 hr of SoT but after switching it, it has changed significantly.

Dr. Death said:
Yes you are right, about the amoled one but even on our screen it saves battery. I've tested. Without the black notifications and black keyboard I used to get 5-6 hr of SoT but after switching it, it has changed significantly.
Click to expand...
Click to collapse
Oh, that's really impressive. I've loved your tutorial, I'll give it a try after doing a fresh install of EXistenZ. And report. Unfortunately I don't like black backgrounds that much, so I will keep white colors the most.
Btw, my battery is 21 months old, let's see how it works.

Little Snevil said:
Oh, that's really impressive. I've loved your tutorial, I'll give it a try after doing a fresh install of EXistenZ. And report. Unfortunately I don't like black backgrounds that much, so I will keep white colors the most.
Btw, my battery is 21 months old, let's see how it works.
Click to expand...
Click to collapse
Yep, waiting for your report.
Some more methods will be added today or tomorrow :')
Your appreciation is much required :')

Dr. Death said:
Yep, waiting for your report.
Some more methods will be added today or tomorrow :')
Your appreciation is much required :')
Click to expand...
Click to collapse
I'll test your method later, because I decided to gain my warranty of Sony (it's till 17 January), so I will send it to them, for new battery

manfred18 said:
I'll test your method later, because I decided to gain my warranty of Sony (it's till 17 January), so I will send it to them, for new battery
Click to expand...
Click to collapse
Yep, sure.

New Roms - not on XDA.

Hello, I bought a new Xiaomi Mi8 and gave my daughter my old Le Pro 3
Although I love Miui, and my new Mi8. I really do miss checking out new roms and generally living the life of a flashaholic.
So while waiting to unlock the bootloader of my Mi8, I have taken control of my daughters old X522. So now, I am now checking out the many, many ( wow there is alot!) many, many Roms built for the Leeco X52x series. Yeah, you guys have alot more Rom's than the Le Pro 3 community. But, I have found some more for you to check out!
In my quest to learn more about the Leeco X5xx series, and make it better for my kids. I have scoured the web, and found some roms that are not currently available on XDA. So I am posting, and will be posting these roms here for your enjoyment too. Because I do not always have access to official Github sources, they simply don't exist, or I am just being too lazy to look for those things and create a proper thread in the Roms section, I am posting them here in the Discussion section. Only fellow flashaholics will find these roms below.
Anyway, if you guys want to try some new Roms , check out the links below.
Please note, that I personally created nothing.
I am simply sharing the work of someone else.
But I will certainly give them their due credit when possible and I will add their updates to this thread along with additional Roms whenever possible ( expect to see several additions soon.) ENJOY!
Thanks to @MpS005 for helping me with correcting the developer and sources information.
He stated via PM that he experienced a fingerprint lock screen security issue. Personally I have not yet seen that issue myself. However, coming from the Leeco Pro 3 group that issue was common on many roms and we have found workarounds. Below is what previously worked for me.
Solution
Extract boot.img : and reflash along with bootloader. Then use adb to verify that the bootloader is unlocked
After flashing Magisk, you should no longer experience the fingerprint unlock issue again.
Pie Roms
ROM] [9.0] [LeEco Le 2] [Stable S-2] Bliss-v11.4 [UNOFFICIAL - 2019013 )
Version: Pie Bliss-v11.4-Stable-s2-UNOFFICIAL-20190130-1830.
Bliss ROM by @TekXS UPDATE!
Version: Pie
File name: Bliss-v11.4-Stable-s2-UNOFFICIAL-20190130-1830.zip
File size: 683 MB
Build date: 2019/01/30
Build Type: UNOFFICIAL.
Device Changelog:
* Enable HEVC encoding
* Updated perf stack
* Added f2fs support (needs updated recovery)
* Updated thermal configs
Download Link: https://drive.google.com/file/d/19Hx3Gzj0FvZMO7ewcruFIFGNm4iuTZE-/view
Developer/unofficial Maintainer: @TekXS
Main Development Website : https://blissroms.com/ ( Find answers to any questions there)
GitHub: https://github.com/BlissRoms
Google Plus: https://plus.google.com/communities/118265887490106132524/s/Leeco
So many options and killer battery life!
Device Changelog:
====================
01-29-2019
====================
* frameworks/base/
72ba452 Fix battery bar default colors
====================
01-28-2019
====================
* frameworks/base/
44f7d3e [1/4] base: qs status bar header image
4a81417 base: SystemUI: add tuner to hide qs drag handle
c0e3c33 Add Dialer's missing strings
b719798 fwb: Dialer auto proximity speakerphone [1/2]
7ed2c33 Merge changes from topic "bt-sbc-hd-dualchannel-pie" into p9.0
====================
01-27-2019
====================
* frameworks/base/
0f392ed PrivacyGuard: fixes from Lineage
0e242d7 appops: Switch to Privacy Guard for P (1/2)
07e2517 AppOps: track op persistence by name instead of id
====================
01-26-2019
====================
* frameworks/base/
8f142bb Merge changes from topic "ambopt" into p9.0
5c07c57 Merge "utils: Introduce FileUtils class" into p9.0
====================
01-25-2019
====================
* build/make/
5558357 bliss_gsi: Track vndk-tests repo from BlissRoms
====================
01-24-2019
====================
* frameworks/base/
0e9a541 Add weather alternative to ambient bottom view [1/2]
57b8f59 Fix current formating on lockscreen for devices, that report directly in Ampere. Shamelessly extracted from: base: Lockscreen Charging info (3/3) by: xyyx <[email protected]>
1287fe2 fwb: Ambient Display battery toggle [1/2]
====================
01-23-2019
====================
* frameworks/base/
6b1248b Utils: Add method to determine battery temp
b11048d Only show bluetooth icon when connected
6a0f03d Add ability to toggle bluetooth battery level [1/2]
96008e5 Statusbar battery level device filter: add a few more ones
45f34f1 Statusbar bluetooth battery level: improvements
e352cd2 SystemUI: Show bluetooth battery level when available
c4c889e Battery icon style: improve text/hidden switch [1/2]
425120e Fix latest remaining battery icon glitches [1/2]
295c379 Battery icon: circle styles fixes
d997601 Battery icon: force show pct in QS header and when charging/powersave
a24bbaf Add the powersave hint to the circle battery
5923fa8 Battery styles : Fix icon portrait level
cc15aeb Inherit battery meter style in view [1/2]
4d44f72 Clean up battery styles
965de78 Battery icon: show outside percentage on charging
9864972 Add big circle battery
103ddb3 Text battery style: show a when charging
3848ab3 Battery icon: show pct on the right of the icon like stock
0b2e987 BatteryMeterDrawable: Add hidden option
71f4212 BatteryMeterDrawable: Add text style
533b543 BatteryMeterDrawable: Add battery styles
12f31b4 Revert battery commits
====================
01-22-2019
====================
====================
01-21-2019
====================
====================
01-20-2019
====================
* build/make/
9195f33 [x86 builds] Use all cores for building again
065b1d1 [x86 builds] Updates
* frameworks/base/
9729a16 AbsListView: Fix widget couldn't find any view fc
2d62b65 lockscreen: Add option to pass swipe-up-to-unlock (1/2)
f4daa2a base: Keyguard: Hide check button when using PIN quick unlock
dae706a Themes: Allow volume slider and thumb to work with custom images.
48c0d6d Extended audio panel - fixes for unlinked notifications
483915c Unlock keystore with fingerprint after reboot (1/2)
8047f33 base: allow hiding lockscreen shortcuts on secure lockscreen [1/2]
4fb02ae LockPatternUtils: Make settings getter and setters protected
18a54f5 Forward port CM Screen Security settings (1/2)
f45d9b2 Keyguard: Forward port lockscreen quick unlock (1/2)
db56d50 Keyguard: Add option to scramble pin layout when unlocking (2/2)
3b71e5f Fingerprint authentication vibration [1/2]
ce5d7a9 KeyguardHostView: Auto face unlock v2 for pie
b3cc55a Check for Face Unlock Running before skipping bouncer via trusted face to prevent skipping bouncer with other trusted options.
840694b Add toggle for face auto unlock (1/2)
2998b4c KeyguardHostView: Dismiss keyguard automatically when face is recognized
3ebf9c2 Ambient music: Use animated icon
====================
01-19-2019
====================
====================
01-18-2019
====================
* hardware/qcom/audio-caf/msm8952/
87e2703 audio: Use normal tinycompress
* hardware/qcom/fm/
af17486 libfm_jni: Fix typo in ctl.stop
131be18 libfm_jni: Rename the QC introduced props to have vendor tag added
====================
01-17-2019
====================
* build/make/
085c7c8 Merge "build: fix dex pre opt build with ims" into p9.0
* frameworks/base/
c9e1508 SystemUI: Animate the keyguard when charging
====================
01-16-2019
====================
* frameworks/base/
f673135 Ambient music Now Playing: more improvements
b0d8c56 Ambient music NowPlaying: be sure to clean track info when needed
14fa46d Ambient Display Music Ticker: Nuke song count info
67601a0 Ambient Music Ticker: make it pixel like
1516244 Ambient music: check if isMediaNotification after final inflation
1b01ba3 Ambient music / Now playing: show also on lockscreen
b4e0210 Ambient music ticker: make it work within Now Playing on Pixel devices [1/2]
76f7780 Ambient music ticker: don't trigger if it's not a media notification
dd6dee2 Ambient music: be sure to clean track info on media notification drop
6dcb2bb A few more improvements for Ambient Music
b4c9822 Ambient music: don't trigger clean layout mode when in AoD
3efa93bc Ambient music ticker AoD: make it compatibile with double tap sensor
9dcfd9e Fix lockscreen double tap to open notifications after ambient music
eba6163 Ambient display music ticker [1/2]
1d48dec Port ambient Now Playing container from Pixel [stripped down version]
ea3b8cd ScreenOff skip track: add Spotify/kdeconn/... remote session compatibility
5a5915e Fix volume rocker skip track on Ambient Display and Lift to Wake
c95d97b base: fix double volume events on screen off
9dbf7ee [1/2] base: volume key music control
724a7fb Squash revert all of Ambient Play commits
4ac9c79 Merge changes from topic "ambivis" into p9.0
bfea61a hwui: Remove deprecated compiler flag
62bb638 Update the screenState for keyguard while screen turning on
dbdab69 Delete the check of mService when BluetoothHeadset doUnbind
d41cc6f Make services with uid 1000 restart if their host process crashes
5b25fca ConnectionRecord: make SystemProcess Watchdog when clean app process
1d3c3b0 Change the listening logic of MtpStorageManager
beb9f2b Fix motion event offset of DecorView is moved in the window
b8f6795 PMS: Improve code stability and avoid vm reboot
3edcf69 PMS: No need to call permissionsState.getPermissions
f8c2621 Binder: Fix improper JNI call for dumpProxyDebugInfo
ee5731f Fix Possible Deadlock with getFeatureState
d56025d Bluetooth: Fix NPE when accesing Manufacturer Data of invalid ScanRecord
c04d0e8 hwui: stability: check mmap return value
1a45fc2 Provide Synchronization to destroyUiAutomationService()
bb0cd5c ConnectivityService: null check before accessing getCurrentScore()
dd6da21 SystemUI: Fix crash when unlocking via fingerprint
2293506 Fix ExifInterface for .heic when meta is at the end
f6e2c36 SystemUI: Name Cellular Tile based on carrier
e86f7fe Do not move the multi-window divider when showing IME
4d4665d Preserve x18 while preloading SP-HALs in the zygote
3a2a85c Crash app on foreground service notification error
b717807 KeyStore: Check for daemon death and reconnect if needed
f75ce11 Refusing to enter PIP mode when activity destroyed
11e688c Fix PIP media session listener for secondary users
9355b38 Fix the behavior of keyguard bouncer in a corner case
bf812e1 VrManagerService: Solve the null pointer exception
cfb4a61 SystemUI: Fixes context for tiles without longClick
0a57701 ActivityManager: Fix display id JE issue
37f5893 Activity: Fix class not found exception
b991746 am: Fix top activity resume with secure keyguard
8e1928d Fix app shortcuts string when changing language during first boot
70778bc Fix NPE when creates wifi tracker after setting pin
4705e17 do not remove system when provider publish timeout
6e90e16 service: ResetListener in StorageManagerService
3083048 system_serverrocess: Crash on Android user-switching
4b33ea4 Screenshot: Fix possible NPE
eace40d Fix a 'memory leak'
b7a0a64 Sync Preference in UI for new cached device
0488000 Synchronize on a static final object to lock mDeviceBusy
19cace7 Avoid that the bound process has a higher priority than caller
d4c4f5b Framework: Remove some methods from boot image profile
2b5da96 Fix data source for HEIF exif extractor
484dc88 Fix issue which exception happens with ExifInterface for HEIF content
203ad84 Change caught exception in MediaScanner when ExifInterface is created
de67c7a Remove NotificationVisibility storage pool
9edbd2f view: add null check for dispatch touch view
ad79539 Fix UsbDeviceManager null object reference
e094105 ExifInterface: Avoid infinite loop on stream seeking failed
bbd6fa3 Revert "ViewRoot: Ensure we release surface from setWindowStopped"
245db064 ConnectivityService: Fix idle timer rule leakage
02e7d31 PackageManagerService: update client app info when related shared library updated.
a94d81e ExternalStorageProvider always throws exception when renaming
f95e200 audio: dispatchPlaybackChange with handlerThread
1a0522a Settings: Only valid screen power consumption need to smear
9600552 Fix ix Intent restoreFromXml missing type
3db5733 pm: Fixes can not boot issue
51a1915 pms: Fix the IndexOutOfBoundsException issue
7f2cdbb Location: Skip processing when receiver pointer is null
13e1b49 InputMethodManager: Fixed memory leak when window Dismissed
a6c3713 WindowManager: Remove unused calling for better performance
1693588 SystemUI: Fix ArrayList callbacks not being thread-safe
0b1d48b Parse Exif OffsetTime in MediaScanner
319c53cf Use getCompressedSizeLong to get correct size for 2G file
3e2b336 Reduce the uncessery wm call while checkKeyguardVisibility
f687616 aapt: Fix compiler warning (clobbered by longjmp)
a474587 aapt: add check for untranslatable "string-array"s
4425df3 aapt: Use a std::map instead of a SortedVector
bf140dc aapt: Speed up the style pruning
bbc5695 WindowManagerService: Remove status bar perm checks
0f16e14 BatteryStats: Correct formatter for pkginst in battery stats
c0ad81b Persistent disable background app notification by default
936f0e4 services/job: Fix two Jobscheduler bugs
d5cb54f ActivityManager: fix npe in ProcessRecord
c1cc77e frameworks: Fix null pointer Issue
7be3c0e hwui: Don't run comparisons on non-jank frames
97aff26 Avoid needless Integer.valueOf() object allocation.
c09b02f ViewConfiguration: misc changes (rev)
0179561 libs: hwui: Enable perf mode and disable pgo
decbdb0 Notification: Remove logspam from apps without channels
c78d66f InputWrapper: Opt out early if session == null
a944e2c TelephonyManager: Prevent NPE when registering phone state listener
3af7f3c hwui: Disable fine-grained logging
e73eb2d Change up some of the clocks
1ec3693 Add sneaky analog clock (1/2)
14a43d5 Add Spectrum clock (1/2)
0583bc2 dotOS Analog clock[1/2]
f441fa6 Fixup the normal analog clocks
42c01e2 Add in 2 more lockscreen clock options.
61eae8c New stock style clock with accent color
62678b3 [1/2] Add sammy accent clock and a variant
2b64d22 lockscreen : Add small size style [1/2]
7466b66 Add in analog clock with numbers
4853c47 LS: Add spidey clock style [1/2]
98a783e Lockscreen clock styles: Fix bottom margins & ambient display/AOD visibility
f95e2e1 Lockscreen items/clocks: KeyguardSliceView improvements/cleanup
ab8d49b Lockscreen clock styles: Move everything to the keyguard [1/2]
295f1d9 Always keep clock/date & other items visible while dozing
5f2aac6 Lockscreen/ambient analog clock: improve design
b50eada Ensure the clockview is aligned correctly each time
7c583d5 Remove the 0 from the 12 hour format from the 'Digital (bold)' option
c94b764 Keyguard items: code improvements
53deb94 Hide lockscreen items [1/2]
bb479ca Introduce lockscreen clock/date styles [1/2]
31f2331 Code smart
This Rom is the best rom that I have used on this device! In fact maybe the best AOSP Rom that I have ever used!....Enjoy!

Reserved

Based aosp or caf

tsongming said:
Pie Roms
ROM] [9.0] [LeEco Le 2] [Stable S-2] Bliss-v11.4 [UNOFFICIAL - 2019013 )
Version: Pie Bliss-v11.4-Stable-s2-UNOFFICIAL-20190130-1830.
Bliss ROM by @TekXS UPDATE!
Version: Pie
File name: Bliss-v11.4-Stable-s2-UNOFFICIAL-20190130-1830.zip
File size: 683 MB
Build date: 2019/01/30
Build Type: UNOFFICIAL.
Device Changelog:
* Enable HEVC encoding
* Updated perf stack
* Added f2fs support (needs updated recovery)
* Updated thermal configs
This Rom is the best rom that I have used on this device! In fact maybe the best AOSP Rom that I have ever used!....Enjoy!
Click to expand...
Click to collapse
Are you still using this bliss ROM? How does it compare with popular x522 Pie ROMs in terms of system stability and also camera?
Sent from my Le X526 using XDA Labs

twistyplain said:
Are you still using this bliss ROM? How does it compare with popular x522 Pie ROMs in terms of system stability and also camera?
Click to expand...
Click to collapse
It's still on the phone but I haven't used the phone in almost 2 weeks. Not since unlocking the bootloader on my Mi8.
Because of your message I checked it, and I thought that I turned it off. But it was still on with about 2% battery left... I am shocked that it had any battery left.
I tried a bunch of Roms on that phone and for me it was the absolute best rom that I have used on the x522. Never experienced any issues of any kind, even the Pixel 3 mod made specifically for the x5xx phones worked extremely well.
No issues, with locksceen or anything else at all. Someone really should continue development on on that rom because it's fantastic.
I am not sure if they will load but I will attach a couple of photos... Might be too large. I BTW, these were taken in a very dark room, with Night mode.

tsongming said:
Because of your message I checked it, and I thought that I turned it off. But it was still on with about 2% battery left... I am shocked that it had any battery left.
Click to expand...
Click to collapse
The phone was staing with sim inserted or without?

bobdubrovsky said:
The phone was staing with sim inserted or without?
Click to expand...
Click to collapse
No working sim because its in the Mi8.
But actually there is an old Tmobile Sim that had data only. But its not in service anymore...this was my daughters phone until I gave her my old Le Pro Pro 3 and I switched her to At&t However, the sim, still gets a signal though I will look tomorrow to see what the drain percentage is., has to be low.
I am going to bed now its 5am, .Good night.

tsongming said:
It's still on the phone but I haven't used the phone in almost 2 weeks. Not since unlocking the bootloader on my Mi8.
Because of your message I checked it, and I thought that I turned it off. But it was still on with about 2% battery left... I am shocked that it had any battery left.
I tried a bunch of Roms on that phone and for me it was the absolute best rom that I have used on the x522. Never experienced any issues of any kind, even the Pixel 3 mod made specifically for the x5xx phones worked extremely well.
No issues, with locksceen or anything else at all. Someone really should continue development on on that rom because it's fantastic.
I am not sure if they will load but I will attach a couple of photos... Might be too large. I BTW, these were taken in a very dark room, with Night mode.
Click to expand...
Click to collapse
If this ROM is that good, I might just end up keeping it. I have some questions though... Which pixel 3 mod is made specifically for x5xx? I'm assuming it's a camera mod.
It doesn't look like fast charging is working. Is there a way to turn it on? Also, does ir remote control work?
Sent from my Le X526 using XDA Labs

twistyplain said:
How does it compare with popular x522 Pie ROMs in terms of system stability and also camera?
Click to expand...
Click to collapse
If you look for the best pie rom, imho, do it between Liquid Rmx 20190118, AOSP Ext new build and Havoc new build.
---------- Post added at 10:25 AM ---------- Previous post was at 10:14 AM ----------
twistyplain said:
It doesn't look like fast charging is working. Is there a way to turn it on?
Click to expand...
Click to collapse
Use this QC-patch

twistyplain said:
If this ROM is that good, I might just end up keeping it. I have some questions though... Which pixel 3 mod is made specifically for x5xx? I'm assuming it's a camera mod.
It doesn't look like fast charging is working. Is there a way to turn it on? Also, does ir remote control work?
Click to expand...
Click to collapse
The bliss ROM is the best for tsongming as he don't want to use his phone. There's no need. he don't cares about bugs& performance in it. He wants battery and it is giving to him. He uses Mi8 now and will care about bugs and performance and stability there, le 2 is useless for him now:laugh:
As bobdubrovsky said liquid and aex are best....
and the pixel3 mod, is the gcam v1.1 by nullbytepl , which came prebuilt in PE in earlier build and you didn't like that camera, I remember
@bobdubrovsky do you know if casting works on ROS Miui?

MpS005 said:
@bobdubrovsky do you know if casting works on ROS Miui?
Click to expand...
Click to collapse
No idea. I did only test installation RosMiui for short review.

MpS005 said:
@bobdubrovsky do you know if casting works on ROS Miui?
Click to expand...
Click to collapse
I don't know if casting works on ROS MIUI. I never got to try it before I flashed another ROM.
Sent from my Le X526 using XDA Labs

twistyplain said:
If this ROM is that good, I might just end up keeping it. I have some questions though... Which pixel 3 mod is made specifically for x5xx? I'm assuming it's a camera mod.
It doesn't look like fast charging is working. Is there a way to turn it on? Also, does ir remote control work?
Sent from my Le X526 using XDA Labs
Click to expand...
Click to collapse
The Camera is GCam-6.1.013-Le2-V1.1.apk
Its charging at 3298ma , but the battery is still low., so it will drop to 1800ma once its reaches 50 or 60% I unplugged it after making the last post because I don't like charging overnight..
Also I significantly underclock the cores out of habit, which may explain why it performs so well. Some of the Pie Roms that I tried on this phone would get too hot too quick, and burn up battery life.
I agree that there are other good roms out there. Personally, I liked this one the most on that device

MpS005 said:
The bliss ROM is the best for tsongming as he don't want to use his phone. There's no need. he don't cares about bugs& performance in it. He wants battery and it is giving to him. He uses Mi8 now and will care about bugs and performance and stability there, le 2 is useless for him now:laugh:
As bobdubrovsky said liquid and aex are best....
and the pixel3 mod, is the gcam v1.1 by nullbytepl , which came prebuilt in PE in earlier build and you didn't like that camera, I remember
@bobdubrovsky do you know if casting works on ROS Miui?
Click to expand...
Click to collapse
You are right that I don't use this phone, so definitely don't take my word for it, because it's not a daily driver. However, I am impressed with this phone. It is a million times better than what I knew, and its sad that the kernel can't be upstreamed to 4.9 because the fluidity and performance could be even better.
The camera came from here" https://forum.xda-developers.com/le-2/themes/v1-1-google-camera-6-1-013-port-le2-t3880934

bobdubrovsky said:
If you look for the best pie rom, imho, do it between Liquid Rmx 20190118 and AOSP Ext 20190308.
---------- Post added at 10:25 AM ---------- Previous post was at 10:14 AM ----------
Use this QC-patch
Click to expand...
Click to collapse
Yes, I agree I tried Liquid Remix and loved it. But I liked this one a bit more, too bad it is out of date now. BTW, I have seen your posts, here and on 4PDA, you could update it?

bobdubrovsky said:
If you look for the best pie rom, imho, do it between Liquid Rmx 20190118 and AOSP Ext 20190308.
---------- Post added at 10:25 AM ---------- Previous post was at 10:14 AM ----------
Use this QC-patch
Click to expand...
Click to collapse
The liquid remix ROM that's currently up is from 20190225. I'll give that a try. The download for AEX is so slow ?. It's like watching paint dry.
Do you recommend flashing custom kernels or keeping stock kernel?
Sent from my Le X526 using XDA Labs

twistyplain said:
The liquid remix ROM that's currently up is from 20190225. I'll give that a try. The download for AEX is so slow . It's like watching paint dry.
Do you recommend flashing custom kernels or keeping stock kernel?
Sent from my Le X526 using XDA Labs
Click to expand...
Click to collapse
There is a build upcoming for liquid. wait sometime

MpS005 said:
There is a build upcoming for liquid. wait sometime
Click to expand...
Click to collapse
I already tried three ROMs since yesterday. First Liquid remix, then Bliss, and finally AEX. Out of all three, the one that's closest IMO to becoming a daily driver is AOSP Extended. It is very smooth, almost completely lag-free, and the camera is passable. Here are my thoughts on these three ROMs.
The first one I installed is liquid remix. The first thing that rubbed off me the wrong way was the lack of fluidity. This rom does stutter. A LOT!! It's hard to use it five minutes without experiencing a stutter in the UI and sometimes full on freezing. Another thing that I didn't expect is that the stock camera cannot record video. Every time I tried I changed from photo to video mode I got an error that it can't connect to the camera. I installed the v2 of gcam port by nullbytel for le 2 and it couldn't start. Not even once and rebooting didn't help. The last straw came when the phone went to sleep and couldn't turn on after pressing the power button. I had to force restart the phone. The ir worked when I tested it with the flashable leeco remote. The reason I can't keep liquid remix is the failure of the camera. The constant stuttering is also too much and the sleep of death is the final nail on the coffin. I didn't use any custom kernel with it.
Second is Bliss rom. The UI is acceptably smooth and it is somewhere between liquid and AEX. It has numerous customization options which is an added bonus. Cameras work acceptably, both built in and gcam port. The biggest failure of this rom is failure to record or read back fingerprints. When I tried to record my fingerprint, the process of touching the sensor to record the impression caused it to hang permanently. Sometimes it would record a few touches and freeze up the entire settings app forcing me to fc. What's worse is that after these failed attempts, after rebooting, the fingerprint sensor failed to work completely. The inability to add fingerprint security is a deal breaker for me so I removed the os.
Lastly I installed AOSP Extended. Right off the bat this ROM is impressively smooth, it's way better than lineage, pixel experience, and even better than arrow os pie. Everything seems to work well from the get-go. The installed camera, works and takes good photos and videos. Of course shutter times are not as good as EUI but there is a marked improvement in the photo capability of new pie ROMs. AEX is based on lineage and I had an issue with the stock kernel. It had very aggressive touch boost which made the CPU stick to maximum frequency even when it wasn't needed. I noticed unnecessary heating when I was just performing light tasks which made me question its ability to handle heavy workloads. I underclocked big cores to 1.3 GHz and there was still noticeable heating which is inexcusable.
The cameras on AEX worked with stock kernel but failed when I installed overload 4.1 or 4.2. I had to change the kernel to reduce the heating but unfortunately I would have to do without cameras which is not an option. I could also feel that I had to wrestle with it a lot to keep the phone cool and preserve battery. Graphene kernel worked even with the cameras but it didn't solve the unnecessary heating. Fastest charging I saw with AEX was 2440 milliamps which is not close to the 4300 ma I am used to with smalleui.
After a day of experiments I have now removed these three ROMs but if I ever think about going pie again, AOSP Extended will be my first choice.

twistyplain said:
I already tried three ROMs since yesterday. First Liquid remix, then Bliss, and finally AEX. Out of all three, the one that's closest IMO to becoming a daily driver is AOSP Extended. It is very smooth, almost completely lag-free, and the camera is passable. Here are my thoughts on these three ROMs.
The first one I installed is liquid remix. The first thing that rubbed off me the wrong way was the lack of fluidity. This rom does stutter. A LOT!! It's hard to use it five minutes without experiencing a stutter in the UI and sometimes full on freezing. Another thing that I didn't expect is that the stock camera cannot record video. Every time I tried I changed from photo to video mode I got an error that it can't connect to the camera. I installed the v2 of gcam port by nullbytel for le 2 and it couldn't start. Not even once and rebooting didn't help. The last straw came when the phone went to sleep and couldn't turn on after pressing the power button. I had to force restart the phone. The ir worked when I tested it with the flashable leeco remote. The reason I can't keep liquid remix is the failure of the camera. The constant stuttering is also too much and the sleep of death is the final nail on the coffin. I didn't use any custom kernel with it.
Second is Bliss rom. The UI is acceptably smooth and it is somewhere between liquid and AEX. It has numerous customization options which is an added bonus. Cameras work acceptably, both built in and gcam port. The biggest failure of this rom is failure to record or read back fingerprints. When I tried to record my fingerprint, the process of touching the sensor to record the impression caused it to hang permanently. Sometimes it would record a few touches and freeze up the entire settings app forcing me to fc. What's worse is that after these failed attempts, after rebooting, the fingerprint sensor failed to work completely. The inability to add fingerprint security is a deal breaker for me so I removed the os.
Lastly I installed AOSP Extended. Right off the bat this ROM is impressively smooth, it's way better than lineage, pixel experience, and even better than arrow os pie. Everything seems to work well from the get-go. The installed camera, works and takes good photos and videos. Of course shutter times are not as good as EUI but there is a marked improvement in the photo capability of new pie ROMs. AEX is based on lineage and I had an issue with the stock kernel. It had very aggressive touch boost which made the CPU stick to maximum frequency even when it wasn't needed. I noticed unnecessary heating when I was just performing light tasks which made me question its ability to handle heavy workloads. I underclocked big cores to 1.3 GHz and there was still noticeable heating which is inexcusable.
The cameras on AEX worked with stock kernel but failed when I installed overload 4.1 or 4.2. I had to change the kernel to reduce the heating but unfortunately I would have to do without cameras which is not an option. I could also feel that I had to wrestle with it a lot to keep the phone cool and preserve battery. Graphene kernel worked even with the cameras but it didn't solve the unnecessary heating. Fastest charging I saw with AEX was 2440 milliamps which is not close to the 4300 ma I am used to with smalleui.
After a day of experiments I have now removed these three ROMs but if I ever think about going pie again, AOSP Extended will be my first choice.
Click to expand...
Click to collapse
Bliss has fingerprint bug. I forgot to tell earlier.
Liquid new builds are not that fluid, but the dec and jan builds were very fluid.
AEX is best rom with OTA support. the slow charging problem is actually not a problem. The Devs had reduced the maximum charging speed to 2500mAh to provide better battery life and durability. Don't know how but battery gives more power on pie ROMs with slow charging.
And using overload kernel does not affect cameras. There might be some error with you! You might use any KA profile and edit it afterwards according to you. The most popular profile on Telegram are CrazyNANA V5, V6 and Miracle. These are made (by kabixi) for overload kernel 4.15 or 4.22. He prefers OL 4.15 for everything. Next time you can try one of them.
And I'll check camera with overload kernel again. I am already using AEX. It's giving good battery to me without heat on stock kernel

MpS005 said:
Bliss has fingerprint bug. I forgot to tell earlier.
Liquid new builds are not that fluid, but the dec and jan builds were very fluid.
AEX is best rom with OTA support. the slow charging problem is actually not a problem. The Devs had reduced the maximum charging speed to 2500mAh to provide better battery life and durability. Don't know how but battery gives more power on pie ROMs with slow charging.
And using overload kernel does not affect cameras. There might be some error with you! You might use any KA profile and edit it afterwards according to you. The most popular profile on Telegram are CrazyNANA V5, V6 and Miracle. These are made (by kabixi) for overload kernel 4.15 or 4.22. He prefers OL 4.15 for everything. Next time you can try one of them.
And I'll check camera with overload kernel again. I am already using AEX. It's giving good battery to me without heat on stock kernel
Click to expand...
Click to collapse
Never experienced your fingerprint issue with the Bliss Rom. However since charging it and attempting to use it today, it definitely has had some serious issues issues today...making it unusable.
Not completely sure why the problems suddenly appeared since the phone hasn't been used and I did not previously have any issues with it.
Today, the phone became exceptionally hot and the screen would not stay bright.. Even with brightness turned all the way up.
No that I am thinking about it, these issues could be caused by something I installed such as a Magisk mod or more likely the thermal tweaks that I made.
"Their may be some error with you"
I don't know if you intended to be rude towards @twistyplain , but it sort of reads that way We are adults, so let's keep it civil.
So with full respect to twisty.
I made a flashable thermal file from an xml file that Twisty shared... so you may be onto something when you said caused by him. ( Assuming you said it in a respectful jest)
Thermals very well could cause camera issues,display issues, and heating while charging, and especially with Pie Roms.
For example, the camera thermals, if based on EUI may possibly conflict with pie. At least this was definitely the case with the LePro 3.
In early January I made an incomplete spreadsheet to compare thermals between various Roms and devices, (More info to the tight) Finally the user Jasbashque solved our issues and it was his thermals that ended up being implemented into every Pie rom.
The end result was much better battery life, less throttling, and less battery failures from excessive heat while charging.
Here is the comparison sheet. I can make a flash able thermal if I can get some useful help with what would be ideal.
https://docs.google.com/spreadsheet...MBq6Ld9Jc7Mm1FZxzwtsLwcmR6o/edit?usp=drivesdk