I don't know this, but you should be fineAlright, downloading right now. Can i dirty flash over alebcay version?
I don't know this, but you should be fineAlright, downloading right now. Can i dirty flash over alebcay version?
What is battery backup? Same as battery life?Battery backup is too bad on this ROM. Is there any way to improve it like any kernel or anything else I can do?
I don't use my phone much, or I can say that I use to reboot my device many times a day because I rarely use it, then also the battery backup is not good. Is regular rebooting responsible for battery backupBad battery backup? I'm on the stock kernel that came with this ROM, didn't change a single setting and my battery backup is pretty good! The phone works smoothly, battery doesn't drain too fast and charging happens faster than my previous LineageOS ROM. I'm using it complete stock without changing the kernel. Good Battery, Good Performance, Good Features, Everything Works, Not a single reboot since days! This is gonna be my 'winner' ROM once I finish testing more which I have on my list.
I don't use my phone much, or I can say that I use to reboot my device many times a day because I rarely use it, then also the battery backup is not good. Is regular rebooting responsible for battery backup
P.S.- I'm also using everything stock, haven't flashed anything extra
You do realize that Underclocking is a myth. Your governor is responsible for making sure that the CPU frequencies stay low. So, if you only hit high frequencies at 10% of the time, and underclock by 20% the best you can save is 10% or 20%, or just 2% of your battery.Wow, booting won't cause a problem. I've just changed to some other ROM but I remember the best settings with the best battery backup were using CPU at Max 1497Mhz, alucard Governor, No touch boost, No hotplug boost, no wake up boost, CPU Hotplug same which already came activated (the second one) with no. of cores to boost at time = 1, GPU underclocked to 330Mhz, GPU governor simple_ondemand, CPU Voltages global offset -65 mV, Charging rates 2100mA for AC and highest available for USB, Entropy read 1024, Entropy write 2048, read ahead buffer 2048.
I don't play a lot of games so 1497Mhz was good for me. Try higher frequencies until you find it smooth. I suggest don't go beyong 1.9Ghz!
Reboots won't give a bad battery but why do you want to reboot?! By the way I used Force Doze app to make Doze activate immediately as soon as screen turned off.
You do realize that Underclocking is a myth. Your governor is responsible for making sure that the CPU frequencies stay low. So, if you only hit high frequencies at 10% of the time, and underclock by 20% the best you can save is 10% or 20%, or just 2% of your battery.
Your apps make WAY more of a difference than "magic settings"
Sent from my OnePlus3T using XDA Labs
Sources? It's simple math. Remove the underclock and look at how long the CPU spends at each frequency. I prefer smarter governors to a slower phone (using blu-active in the past and now focusing on EAS).interesting statement, please provide me with some sources.... however if you look at boeffla´s(build in battery profiles) and franco´s kernel app ( battery lab) they both underclock for battery saving profiles....
What's easSources? It's simple math. Remove the underclock and look at how long the CPU spends at each frequency. I prefer smarter governors to a slower phone (using blu-active in the past and now focusing on EAS).
What's the point of buying a fast new device and then crippling the CPU? What kind of battery life are you getting right now?
Wow, booting won't cause a problem. I've just changed to some other ROM but I remember the best settings with the best battery backup were using CPU at Max 1497Mhz, alucard Governor, No touch boost, No hotplug boost, no wake up boost, CPU Hotplug same which already came activated (the second one) with no. of cores to boost at time = 1, GPU underclocked to 330Mhz, GPU governor simple_ondemand, CPU Voltages global offset -65 mV, Charging rates 2100mA for AC and highest available for USB, Entropy read 1024, Entropy write 2048, read ahead buffer 2048.
I don't play a lot of games so 1497Mhz was good for me. Try higher frequencies until you find it smooth. I suggest don't go beyong 1.9Ghz!
Reboots won't give a bad battery but why do you want to reboot?! By the way I used Force Doze app to make Doze activate immediately as soon as screen turned off.
interesting statement, please provide me with some sources.... however if you look at boeffla´s(build in battery profiles) and franco´s kernel app ( battery lab) they both underclock for battery saving profiles....
Energy Aware Scheduling
My other device is Xiaomi Mi5 Pro. And now i use AOSP Extended Mod + EAS kernel (by my russian collegue). This pack is dope af... Speed, smoothness, energy efficiency at a high level.Energy Aware Scheduling
It doesn't really apply to Bacon, but my other device is a 3T which is BIG.little.
Colleagues, in connection with the release of the September security update, I decided to build another release. This time it will definitely be the last for Android 7.1.2 Nougat. #Staydirty
Download
Some changes:
android_build: September security updates
android_device_oneplus_bacon: Add assertions on TrustZone version
android_device_oneplus_bacon: Remove useless parameter
android_device_oneplus_bacon: Fix multi version TrustZone support
android_device_oneplus_bacon: Adapt recovery updater lib to new recovery code
android_device_oneplus_bacon: Calculate TrustZone size at runtime
android_device_oneplus_bacon: Use project pathmap for recovery
android_device_oneplus_bacon: Use new RIL from upstream LineageOS
android_kernel_oneplus_msm8974: ASoC: msm: Fix to avoid crash during voip call
android_kernel_oneplus_msm8974: ASoC: msm: qdsp6v2: return error when copy from userspace fails
android_kernel_oneplus_msm8974: msm: crypto: set CLR_CNTXT bit for crypto operations
android_kernel_oneplus_msm8974: unix: properly account for FDs passed over unix sockets
android_kernel_oneplus_msm8974: selinux: fix off-by-one in setprocattr
android_kernel_oneplus_msm8974: ASoC: Add backend user count checking
android_kernel_oneplus_msm8974: ashmem: remove cache maintenance support
Can you tell the current status?
Self-testing (beta). I would gladly lay out a public beta, but this contradicts the rules of DU team. Be patient and you will get a stable beta when DU team will publish their first official build.
This is an unofficial release based on the sources provided by various other authors. Flashing this software may or may not void your warranty; it is your responsibility to know if that is the case.