Database Users

[INFO] Auto-Backlight Settings for Cyanogenmod ROMs

Some of you would already know that the lightsensor filter in the Evo kernels is now working ( I would say atleast 80% working ) and responds best to Desire builds.
I have it working just fine for the last few hours on the AndroidMedaUltimate 1.3 version. Here are my settings in case you wanna try out.
CAUTION : If you change the values too many times, lightsensor stops responding and you will not see any changes in values. I believe thats CM related.
My Setup
Build : AndroidMedaUltimate 1.3
Kernel : StockEvo Autobuild dated Oct 29
(No SetCpU/taskkillers/etc)
1. Make sure Auto Brightness is disabled under Settings->Display
2. Goto Settings->Cyanogenmod Settings->User Interface->Automatic Backlight
3. Under Light Sensor filter, make sure Enabled is unchecked (No filters!)
4. Under Light levels, check "Allow Light Decrease" and set "Decrease hysteresis" to 0% (Yes thats no typo, for some reason sensor responds faster this way )
5. Check "Use Custom"
6. Tap on Edit Other Levels...
7. Now set values as in below screenshot and table
Lower ....... Upper ............Screen...........Buttons
0 ____________ 169 _______________ 85 _____________ 255
170 __________ 279 _______________ 120 ____________ 255
280 __________ 749 _______________ 170 ____________ 255
800 __________ () _______________ 254 ____________ 255
Note - The last value is 254, for some reason when I had it as 255 and went outside, brightness got stuck at max and sensor stopped responding
Click to expand...
Click to collapse
8. Tap Save & Apply
9. Wait for few seconds and try covering and changing light, you should see the sensor values change on top
10. Once that starts happening, enable Auto Brightness under Display settings
11. Reboot (Best Practice )
---------------
You can add more levels and adjust the lower/upper range alongwith the Screen values (30-255) to suit you better. However, the more you change it the more its likely to end up not working. Dont know why.

Interesting, will be testing this today with Shubcraft 2.0 and post my findings.

thanks, done the changes and testing with Htcclays V1.4.
edit: it is working very well for me.no lightsensor issue for me.
many thanks for your tip.

Thank you works grat

v-b-n said:
1. Make sure Auto Brightness is disabled under Settings->Display
2. Goto Settings->Cyanogenmod Settings->User Interface->Automatic Backlight
3. Under Light Sensor filter, make sure Enabled is unchecked (No filters!)
4. Under Light levels, check "Allow Light Decrease" and set "Decrease hysteresis" to 0% (Yes thats no typo, for some reason sensor responds faster this way )
5. Check "Use Custom"
6. Tap on Edit Other Levels...
7. Now set values as in below screenshot and table
8. Tap Save & Apply
9. Wait for few seconds and try covering and changing light, you should see the sensor values change on top
10. Once that starts happening, enable Auto Brightness under Display settings
11. Reboot (Best Practice )
---------------
You can add more levels and adjust the lower/upper range alongwith the Screen values (30-255) to suit you better. However, the more you change it the more its likely to end up not working. Dont know why.
Click to expand...
Click to collapse
Thanks very much for this, a few questions if you please.....
I'm using Typhoon 3.8.0.
I'm finding these settings under
Settings->Cyanogenmod Settings->Display->Automatic Backlight
not
Settings->Cyanogenmod Settings->User Interface->Automatic Backlight
And I don't know if that has any underlying significance - like it not being implemented in the same way in Typhoon?
Secondly you don't mention the "screen dim level" setting I see in the same "Display" menu. I've wound it down to 6 (default is 20), but not seeing much difference?
Thirdly, I've used the settings in the "other levels" as your table shows, but I wonder why you used those settings, what drove you to pick those numbers?
Finally, you talk about changing it too much stopping it working....when that happens what do you do to revert? Reboot? Or return to defaults and reboot? or something else?
Thanks, I'm hoping this will help balance out the fact that up to now I've not used auto-brightness so as to keep the battery life up but it's a bit of a pain in bright light to see the screen....
Thanks

[HOW TO] Save batterylife on Galaxy 3

Saving Battery on G3 - like a boss!
As I found a lot of posts about too much battery drain I decided to make a step-by-step tutorial to get a better battery life. I will also give some advice about internal system tweaks, for root users only
First of all: You don't need to adapt to all settings I will explain. This isn't even necessary, but just keep them in mind
And:
- All settings are for Galaxy 3 (with CM-based ROMs) but can also be used for other phones/ROMs
- Sorry for any mistake. I'm not a native English (I'm German). But I hope this text is understandable
- I didn't glued pictures on it, but I tried to guide you through the menus as much as I can
Now we will start:
You'll need:
- your phone
- SetCPU (I recommend Pro-Version)
- internet connection
- and some time
[SCREEN TWEAKS]
The biggest and badest part of the phone is the display. Unfortunately we can't live without it...
But there are ways to make it less worse:
1. Darken it as much as you can: You don't need to have over 50% of brightness when you are at home. And even outside you don't have to use it on the highest level. Try to make the contrast higher, or just hold your hand as a shield over the screen, when you just want to check the clock.
The easiest way to control the brightness is the "Power Control" widget:
{
"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"
}
Or for CM-based ROMs: Enable the brightness control on the notification bar: Settings -> CM -> Interface -> StatusBar Tweaks -> Tick "StatusBar Brightness Control"
Now you can swipe over you statusbar for changing the brightness easily
2. Timeouts: As a long-time-G3-user I just can tell you, that you don't really need them. Normally I switch off the screen / lock it, if I put my phone away. Only when I wait for something to load, I take care, that the screen don't turn off. So setting the automatic screen timeout to 1 minute seems nice. You can choose whatever you want, but keep it under 5 minutes
And you should (if you don't do it) switch your screen off more frequently (when you put your phone away) and don't wait until the timeout does the job. Not a big deal, but very effective.
[CONNECTION TWEAKS]
1. Close to the timeout-settings there is another option for your Wifi-connection: How your W-LAN reacts, when your screen switches off. Thats often a big battery problem in connection with (inefficient) 3G networks. Check this setting under:
Settings -> Wireless Controls -> Wifi settings -> (press menu button) -> advanced -> Wi-Fi sleep policy: Set to [Never]
So your phone will never switch from Wifi to 3G (or 2G) when screen is turned off. The Wifi on a phone has less power consumption than 3G networks. And switching between them is even more worse than just have 3G in idle
2. Only use mobile data-connection if necessary:
This point is self-explanatory. If you don't shut this down completly (in order not to miss emails), switch to 2G networks (For faster switching use a widget or the power-control in your notification bar). This is a compromise between battery saving and connectivity. Better switch it off completly
3. Activate flight-mode sometimes.
Also self-explanatory: When you sleep, you don't need to get calls or messages. Just activate it before you go to sleep and deactivate it, when you wake up (or switch off your phone completly -> even more effective )
4. Deactivate Wifi if you can
When your preferred Wifi networks are out of range your phone tries to search for them constantly. This search routine needs more power than just being connected to one network. Tip: Switch off your Wifi when your leave your house. If this is too much work for you, use a bigger interval for the scanning. This value is set in the build.prop file (/system/build.prop) and can be edited with Root Explorer or anything similar. Search for this line: "wifi.supplicant_scan_interval=xyz". Set the "xyz" e.g. to "300", to scan every 5 minutes
5. Fast Dormancy:
[This option should be set properly to prevent higher battery drain!]
Only set this if your provider supports Fast Dormancy. If you enable this and your provider doesn't support it, you'll have higher battery drain. The other way around the same. Just look it up
Enable/Disable:
for stock-ROM: "Call" *#9900#
for other ROMs: build.prop -> Line "ro.ril.fast.dormancy.rule=" ("1" enable or "0" to disable)
[GENERAL TWEAKS]
1. Task-Killer:
DON'T. USE. AUTO-TASK-KILLER!!! NEVER.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Read this article and you'll get it.
For those TL/DR guys: When an auto killer kills an app, mostly the app will restart itself and will be killed the next time (mayber after 5 or 10 minutes, depends on auto-killing-interval). Restart - kill - restart - ... Bad for batteries.
A full RAM is great for Android, but a fully loaded CPU isn't. The RAM is managed perfectly by the system. For the CPU you should use some CPU-watching apps like "Watchdog". It watches the CPU load caused by apps every xy seconds and informs you when an app using too much CPU.
2. Widgets:
Every widget is using ressources. You should take care of it and only use those, which you really(!) need. A bouncing clock with flashing lights and seconds hand is not really useful and is draining battery like hell. Just check every widget and decide for yourself
[CPU TWEAKS]
This part is only for rooted phones and for those who understand, what I'm talking about
1. Frequencies:
Never set the lowest/minimus frequency to any higher value than the lowest one. How is a CPU supposed to sleep when it's artificially set to a higher frequency?
For OC phones: maximum of 800 MHz should work fine for most things.
2. SetCPU:
This is a powerful app. USE IT!
Profiles: You should set them like this:
Charging Any; Priority 100; max 1000 MHz; min 83/100 MHz (depends on kernel); ondemand
In Call; Priority 95; max 800 MHz; min 83/100 MHz; ondemand
01:00 - 06:00 (sleep time ); Priority 90; max 83/100 MHz; min 83/100 MHz; powersave
Screen OFF; Priority 85; max 200 MHZ; min 83/100 MHz; ondemand
Just play around with them and decide which are the bests for you and don't forget to enable them
Voltages:
You can trouble-free set the voltage for 400MHz - 1000 MHz down by -50 mV. If it causes freezes, try -25 mV. Done? Save and Set -> both in top-right-corner. Tick -> Set on boot (bottom-left)
Governor:
I recommend the ondemand-govenor.
Now I'll explain the settings:
powersave bias: When the governor recalculates the frequency, and the result is 800 MHz, it multiplies the value (800 MHz) with (1000 - x)/1000. E.g. if 300 is set: 800 MHz * (700/1000) = 800 * 0.7 = 560 MHz -> New frequency = 600 MHz (nearest to 560). I recommend = 0.
ignore nice load: On Linux systems (like Android) there are processes which are "nice". There don't want the CPU to jump to higher frequencies. And we don't want it as well: Don't ignore while recalculating -> Set to 0
up treshold: If the CPU load goes above this value, it will jump to the maximum frequency which is set (e.g. 800 MHz). Should be set between 75 - 85.
sampling rate: The governor will recalculate the frequency every xyz µs (1 / 1.000.000 seconds) I use: 20000
sampling down factor: When your CPU jumps to the highest frequency, the next recalculation will be in [sampling down factor] * [sampling rate] µs. It means, your CPU will last longer in higher frequencies before recalculating. Default = 90 (when the sampling rate is at 20000 µs = default, your CPU will last 1,8 seconds on the highest frequency). I recommend = 20.
Don't forget to tick: set with profiles, and set on boot.
If you don't did this before: Untick "Set on Boot"-Option in your CM-Settings -> Performance -> CPU - section. Otherwise your new SetCPU option won't work properly
[OTHER TWEAKS]
NEVER CLOSE APPS WITH PRESSING THE HOME BUTTON, USE THE BACK BUTTON! please
Don't use Live Wallpapers.
Keep an eye on the build-in-battery-consumption menu -> Settings -> About Phone -> Battery Usage
Disable Auto-Rotation if not necessary.
Disable Bluetooth.
Disable Settings -> Location & Security -> Use Wireless Networks
Disable (only when not needed!) Settings -> Accounts & Sync -> Auto-Sync
You'll have to sync every app manually (no more "new Email" popups in notification bar)
Disable [Open Market / Play Store] -> [Menu Button] -> Settings -> Update notifications
Settings -> CM Settings -> Performance:
Enable JIT for better performance
Disable Boot animation for faster boot.
VM-Heap = 32 or 48 MB (not less)
You can hit "thanks" if you want, and maybe someone can make this thread sticky, so everyone can see it
Hope you liked it
And, of course, you can post some more tips, so we can expend this list

save battery g3
hello
i am zsolt
and i would like say that i have alredy probed all roms for galaxy 3
foryo, gb, ics, aokp
my opinion that froyo is a good rom but insufficiently stable, all kernel probed but the best was Kyorarom Ascendency (v0.5.2 - JPU Based) with own kernel
i have 4-5 days battery life average usage!!! important set cpu ondemand 83-800 Mhz if possible,not use live wallpapper and delete stock gallery.apk and google-maps!
aokp rom is very very good, but so still to much defects! with Latest G3mod build by Arakmar 12/04/2012.zip i have set 83-800 Mhz ondemand (not setcpu,in rom control) turn off gps,wifi,data and i was 3% under 21h!!! (i used 4-5calls, and 30 minutes gps whit igo) that is excellent!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
and now i use [ROM][CM7.2] Kyrillos' ROM v10.2 because in aokp the video isn't smooth. in kyrillos almost good! same sets here like aokp and same kernel!
19h under i have used 4 times call, and 15 minutes gps, and 40 minutes video playing still i have 88% baterry power!!!!! GREAT!!!!!
to my mind the kernel is very very important for how much battery uses our phone!!!!
thanks

Great guide!

good detail . thany you for your guide

save battery
hello
i am zsolt again
best option is turn off wifi, gps, 3g/2g, but when you use that
another, set cpu ondemand on oc version 100-800Mhz, non-oc 222-667Mhz and set screen off 83-333Mhz
the root of the matter...... the kernel......sure!!!!
best kernel(which best powersave,but not very smoothly) till now g3mod 2.5 non-oc kernel(because i not play), but to whomsoever not enough the oc version is too good!!!
thanks!

As zsolt64 said, kernel is very important when we talk about the battery. Anyway, good and useful "how to". Thanks!:good:

[Q] Can't change CPU frequency

Hello all,
since I installed the nightly build on the [ICS][CM9]Defy/Defy+ kangs by FuZZ_ topic, I'm unable to change the frequency on my defy(the max is set to 0, the minimum is set to 300) so it always run in 300 mhz, I've tried using the vsel, but the textfields to change the values doesn't appear, tried changing it on the files over gpu0 folder, but when I try to save it it says "unable to save file" and I've set its permissions to write to all users(other,group,owner) and tried the performance menu over the configuration. Any help?

Push the botton above to restart the device. In the menu that is shown on the screen tap on restart. Then select bootmenu option. accept. wait until restarts. go to cpu settings nd there you can change the vsel and frequency.
:laugh:

how i change CPU frequency
glupsnif said:
Push the botton above to restart the device. In the menu that is shown on the screen tap on restart. Then select bootmenu option. accept. wait until restarts. go to cpu settings nd there you can change the vsel and frequency.
:laugh:
Click to expand...
Click to collapse
hi
how do i change the CPU frequency in the bootmenu? i see the CPU setting but don't know how to change them
thx

IGK80 said:
hi
how do i change the CPU frequency in the bootmenu? i see the CPU setting but don't know how to change them
thx
Click to expand...
Click to collapse
get into CPU Settings, set Clk1 to 300, Clk2 to 600, Clk3 to 1000, Vsel1, 2, 3 to respectivly 30, 46, 58, Status shall be Enable, Load all modules: Enable, Scaling my proposal choose Smartass, slide down and click Save, then Go Back and Reboot
and give a feedback

[Hack]Improved Hardware Auto Brightness

This is a hacky fix but it is a fix.
It gives you a backlight that will go from dim to full bright without the need for any other apps running. It's not uber configurable like dedicated apps as it's limited by hardware but it requires 0 ram, 0 runtime and 0 battery
Append the following to hw_config.sh. The sleep is a hack but a viable one - hw_config is fired up by one of the rc files as a oneshot service so it should be OK to extend it's operation
If you prefer you could just make a standalone script with everything after the sleep command (make sure you have the dev= assignment from hw_setup too!) and fire it off with a script executer of your choice
Code:
#this sleep ensures that the system is up and done [email protected] with light levels before setup
sleep 30
#select als group for backlight
echo 1 > $dev/leds/lcd-backlight1/als_group
echo 1 > $dev/leds/lcd-backlight2/als_group
#set both to max. brightness - als will lower
echo 255 > $dev/leds/lcd-backlight1/brightness
echo 255 > $dev/leds/lcd-backlight2/brightness
#set custom als curve
echo 7,1,48,72,24,255,0 > $dev/als_group1
#set custom filter frequency
echo 1000 > $dev/als_filter_down_speed_mHz
echo 1000 > $dev/als_filter_up_speed_mHz
#turn on hardware als
echo 1 > $dev/als_on
Notes
Make sure you have completely uninstalled any other light controllers - Velis in particular wreaks havoc even when disabled - it still receives the screen on intent and resets the brightness which results in a black display - guess how I know ....
Make sure you have disabled auto brightness control in the standard Sony settings and set the slider to full bright for good measure
I use nobootanimation so my phone boots a bit quicker than some. It might be that sleep 30 isn't long enough for an animated startup
Best thing is probably to create a setup script and run that to satisfy yourself the hack works. Then add it to hw_config and increase the delay if it doesn't work!
If you want to know more about the als setup check HERE or read the AS3677 datasheet.
Sadly I wasn't able to find out how the ALS curves are loaded into the current system, hence the direct hardware poking
There's some useful debug capability built into the sysfs
cat $dev/debug to see light sensor outputs and calculated backlight settings
cat als_group1 to read back the curve settings complete with a graph showing the response curve
A software guy could probably easily make an apk that hooked to the SCREEN_ON intent to program all this (and have a nice gui to show/edit the curve) but I'm a hardware engineer so that ain't me!

It's easier to just use Lux. Thanks anyway.

pakatsui said:
It's easier to just use Lux. Thanks anyway.
Click to expand...
Click to collapse
LUX, YAB or other brightness app will don`t work correct on all my Xperias. Only with "system brightness settings" active in the background this apps will change the brightness in realtime. When i close the systemsettings brightness will change no longer or with some luck once when unlocking.
so i will test this Hack, hope it helps to become a wide range in realtime.

heross said:
LUX, YAB or other brightness app will don`t work correct on all my Xperias. Only with "system brightness settings" active in the background this apps will change the brightness in realtime. When i close the systemsettings brightness will change no longer or with some luck once when unlocking.
so i will test this Hack, hope it helps to become a wide range in realtime.
Click to expand...
Click to collapse
Lux works fine. I'm using it now.
Sent from my Xperia SP using xda premium

Hello t_o_f,
today i have made test this fix in Car navigation from sunlight to the moon. awesome. this is the best fix i have always seen for xperia autobrightness. :good::laugh::good: ten points from germany.
the best, lowest brightness it is configurable with the Stock slider!

Call me daft. I disabled auto brightness, jacked the brightness to high, and have no other brightness apps installed. I appended the above to /etc/hw_config.sh and rebooted.
auto brightness didn't work. It was still jacked up to high so I enabled it and tested, still not working. Did I do something wrong? I'm on 254 rooted.

[ROOT][OP5T] Remove OnePlus 5T Cluster 2 2361Mhz Frequency Cap

Overclocking
OnePlus 5T A5010
This is an overclock solution for the clock speed
limiter on the OnePlus 5T's second cluster of CPUs.
Requires root access, and advised to make
a TWRP recovery backup before attempting this.
ElementalX Kernel Manager
Download
X-plore File manager
Download
(Or root browser of your choice)
Build.prop Editor
Download
SSD Boost
Download
1.
First, open up X-plore and navigate to
root/system/etc/vendor/perf/targetconfig.xml
Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361Mhz limiter.
Replace the config1 brackets with this
Code:
<Config1>
<TargetInfo
Target="msm8998"
NumClusters="2"
TotalNumCores="8"
SocIds="292,319"
SynCore="1"
CoreCtlCpu="-1"
MinCoreOnline="0"
CpufreqGov="1" />
<ClustersInfo Id="0" NumCores="4" Type="little" />
<ClustersInfo Id="1" NumCores="4" Type="big" />
</Config1>
If you've already flashed ElementalX kernel
you can reboot and skip step 2.
2.
Flash the custom kernel
from the ElementalX tab in the app.
Choose custom installation and proceed
to select the overclock frequency caps in recovery.
3.
Set the max frequencies to 2035 and 2592Mhz
and tick the on boot icon blue.
Disable core_control and enable msm_thermal
tick both set on boot.
Enjoy your heightened and less restricted
CPU speeds.
See below for tuning
You should notice a considerable boost
in performance with these apps/tweaks.
Hope this helps anyone that's been having trouble.
Feel free to comment whether or not it worked for you.
Buy me a beer:
PayPal.me/newton3788​

ElementalX Tweaks
CPU Min/Max
Cluster 1: 518Mhz / 2.03Ghz
Cluster 2: 806Mhz / 2.59Ghz
CPU Boost
Core 0: 748Mhz / Core 4: 1.26Ghz
Duration: 100ms
GPU
GPU Boost: High
Interactive governor tunables
I've added the downloadable cluster profiles at the bottom.
You may place them in the ElementalX gov_profiles folder.
Cluster 1:
go_hispeed_load - 75
above_hispeed_delay - 20000 2035200:30000
timer_rate - 20000
hispeed_freq - 1670400
timer_slack - 50000
target_loads - 70 1804800:85 1900800:90
min_sample_time - 25000
Cluster 2:
go_hispeed_load - 85
above_hispeed_delay - 20000 2592000:50000
timer_rate - 20000
hispeed_freq - 2035200
timer_slack - 50000
target_loads - 80 2265600:85 2457600:90
min_sample_time - 25000
Build.prop Tweaks
ro.min.fling_velocity=6000
ro.max.fling_velocity=12000
persist.sys.composition.type=dyn
debug.composition.type=dyn
debug.egl.force_msaa=true
persist.sys.use_dithering=1
persist.sys.scrollingcache=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.config.nocheckin=1
ro.kernel.android.checkjni=0
logcat.live=disable
wifi.supplicant_scan_interval=400
ro.media.enc.jpeg.quality=100
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
Open Xplore and edit
root/vendor/etc/build.prop
Replace and add these:
dalvik.vm.heapstartsize=32m
dalvik.vm.heapgrowthlimit=384m
dalvik.vm.heapsize=768m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=8m
dalvik.vm.heapmaxfree=16m
Developer Options
Force GPU Rendering off
Disable HW Overlays off
I've yet to find a solution for the random stuttering
But I'll add it if I do​

newton378 said:
ElementalX Tweaks
​
Click to expand...
Click to collapse
Thanks for your tips here mate.
can you tell how s battery life affected
after this changes,i m trying your settings
but i faced deep sleep problems,do you face this too?

broky said:
Thanks for your tips here mate.
can you tell how s battery life affected
after this changes,i m trying your settings
but i faced deep sleep problems,do you face this too?
Click to expand...
Click to collapse
My device sleeps fine, I use the greenify app to hibernate apps on screen off. I can't account for any tweaks you've made to your device apart from what I've detailed here, mine is stock OOS with the EX kernel. Battery life drops depending on usage but you don't overclock to save battery.
edit: I was having battery problems but I've since flashed stock OOS and set everything back up, the battery life is superb with these governor profiles.

OK,I was just anxious about deep sleep,
I know overclockung drains battery.
Will keep on trying this
EDITnewton378
why don t you post this on oneplus 5 thread also, so more people see it and test it?
(just a suggestion)

broky said:
OK,I was just anxious about deep sleep,
I know overclockung drains battery.
Will keep on trying this
EDITnewton378
why don t you post this on oneplus 5 thread also, so more people see it and test it?
(just a suggestion)
Click to expand...
Click to collapse
http://imgur.com/a/Bhqj83w
No problem with deep sleep on my end.

newton378 said:
http://imgur.com/a/Bhqj83w
No problem with deep sleep on my end.
Click to expand...
Click to collapse
were you using the phone for 2 hours constantly?
or you left the phone idle?

broky said:
were you using the phone for 2 hours constantly?
or you left the phone idle?
Click to expand...
Click to collapse
Constant use and then idle for 10 minutes, deep sleep initiated quickly. No idea what problem you're having, sorry.

newton378 said:
Constant use and then idle for 10 minutes, deep sleep initiated quickly. No idea what problem you're having, sorry.
Click to expand...
Click to collapse
Testing as we talking,till now my deep sleep is fine.
Probably something else caused this,thanks for your response and help.

Update

newton378 said:
ElementalX Tweaks
CPU Boost
Core 0: 748Mhz / Core 4: 1.26Ghz
Duration: 100ms
​
Click to expand...
Click to collapse
you mean
A
0:748Mhz
1:0
2:0
3:0
4:1.26Ghz
5:0
6:0
7:0
or
B
0:748Mhz
1:748Mhz
2:748Mhz
3:748Mhz
4:1.26Ghz
5:1.26Ghz
6:1.26Ghz
7:1.26Ghz
??
i use configuration B and the device is faster than ever but i need to know if this is right:good:

broky said:
you mean
A
0:748Mhz
1:0
2:0
3:0
4:1.26Ghz
5:0
6:0
7:0
or
B
0:748Mhz
1:748Mhz
2:748Mhz
3:748Mhz
4:1.26Ghz
5:1.26Ghz
6:1.26Ghz
7:1.26Ghz
??
i use configuration B and the device is faster than ever but i need to know if this is right:good:
Click to expand...
Click to collapse
I don't think it matters as each cluster's frequencies are locked in sync. Core 1-3 follow 0 and 5-7 follow 4. Setting SynCore to 0 in targetconfig.xml is supposed to allow all cores to fluctuate on their own but it doesn't. Controller must be embedded deeper in the system.

broky said:
OK,I was just anxious about deep sleep,
I know overclockung drains battery.
Will keep on trying this
EDITnewton378
why don t you post this on oneplus 5 thread also, so more people see it and test it?
(just a suggestion)
Click to expand...
Click to collapse
I believe the phone doesn't enter deep sleep when charging due to rapid charging technology. Not sure if turning the phone off to charge helps it stay low power.
I figure this because I left it charging overnight and I had 33 minutes deep sleep and 10 hours of min frequency.

is it required elementalx kernel?cuz i'm using arter kernel right now

filandry said:
is it required elementalx kernel?cuz i'm using arter kernel right now
Click to expand...
Click to collapse
For the tweaks in the second post, no. If you want to have the overclocked CPU speeds, it's made possible by flashing EX kernel with custom settings.
I've tried flashing bluspark kernel over EX kernel and the result was relatively smoother than stock OOS with only EX kernel, however a lot of the settings in EXKM were automatically reverting to bluspark defaults when changed. I don't advise flashing custom kernels over each other unless you want to experiment and have a backup.
You can still remove the limiter on the second cluster's cores with the targetconfig.xml tweak for 2.45Ghz max clock speed.

newton378 said:
For the tweaks in the second post, no. If you want to have the overclocked CPU speeds, it's made possible by flashing EX kernel with custom settings.
I've tried flashing bluspark kernel over EX kernel and the result was relatively smoother than stock OOS with only EX kernel, however a lot of the settings in EXKM were automatically reverting to bluspark defaults when changed. I don't advise flashing custom kernels over each other unless you want to experiment and have a backup.
You can still remove the limiter on the second cluster's cores with the targetconfig.xml tweak for 2.45Ghz max clock speed.
Click to expand...
Click to collapse
so i only need this right?(for remove limiter)
First, open up X-plore and navigate to
root/system/etc/vendor/perf/targetconfig.xml
Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361Mhz limiter.
Replace the config1 brackets with this

filandry said:
so i only need this right?(for remove limiter)
First, open up X-plore and navigate to
root/system/etc/vendor/perf/targetconfig.xml
Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361Mhz limiter.
Replace the config1 brackets with this
Click to expand...
Click to collapse
Correct.

newton378 said:
Correct.
Click to expand...
Click to collapse
okay,will give it try :good:
edit :
yes it worked,although it's litte bit different from your guide..
here's my guide to remove second cluster cpu clock limiter (no overclock) using stock cpu clock speed :
First, open up Explorer and navigate to
/system/vendor/etc/perf
Find and Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361600 limiter number and change it to 2467600
Save And Exit,and then reboot the devices

filandry said:
okay,will give it try :good:
edit :
yes it worked,although it's litte bit different from your guide..
here's my guide to remove second cluster cpu clock limiter (no overclock) using stock cpu clock speed :
First, open up Explorer and navigate to
/system/vendor/etc/perf
Find and Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361600 limiter number and change it to 2467600
Save And Exit,and then reboot the devices
Click to expand...
Click to collapse
Yes, that would effectively raise the frequency cap but it works the same removing it altogether. Hence, cluster 1 doesn't have the max freq parameter in there and it can hit 1.9Ghz by default.

a10
does it work for android 10