Hi.
I have just updated to CM11.
Can anyone tell me how I can overclock to 1200mhz? In SetVsel I have options for 300, 600, 800 and 1000. Do I simply change the 1000 to 1200? Is there a way to add another box for 1200mhz? Or do you use a different app for the overclocking?
At the moment I have my values at 300/24, 600/34, 800/44, 1000/52.
I have set the GPU to 266mhz.
I have followed the other advice in the CM11 thread such as setting Governor settings in Aero Kernel Control to "on demand".
Thanks for any advice and tips.
John
Aero control / CPU performance / Live OC/UV.
{
"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"
}
Sent from my MB526 using Tapatalk 2
pradeeppk said:
Aero control / CPU performance / Live OC/UV.
View attachment 2911261
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I was getting confused between Aero Control and SetVsel.
Do I need to make sure that the settings in both these Apps are the same for the 4 different SetVsel options?
They are both set to apply at boot so I think one may be cancelling out the other?
No need of setvesel.
Sent from my MB526 using Tapatalk 2
john10001 said:
Thanks. I was getting confused between Aero Control and SetVsel.
Do I need to make sure that the settings in both these Apps are the same for the 4 different SetVsel options?
They are both set to apply at boot so I think one may be cancelling out the other?
Click to expand...
Click to collapse
If they are both set to apply at boot, then whichever app loads last will determine the settings. That's why your recommended to uninstall SetVsel. You don't need it anyway, since Aero Control is better (i.e. specifically written for our defy).
Aero control is perfect for owerclock settings of defy. I have 1300Mhz of maximum clock and work perfectly in interactive governor. 1300/67 1000/52 600/48 400/22
Related
Hello guys,
I found something strange in GingerDX ROM that I have marked in screenshot
Even this process can't be stopped more than 5mins. It starts itself.
In other CM7 ROMS there is no such process that is running in background.
AS written in second screenshot "kept for better speed", may be this is the process that also provide speed to system but also drain battery.
What do you think about it..??? Did anyone also found this..???
{
"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"
}
Well i dont have anything like this and im using gdx22 with alfs06 no cap kernel
Sent from my X8 using XDA App
Nope, haven encounter such issue
Sent from my X8 using XDA App
I am prettu sure have this thing in cached processes, not in running processes. Click the grey or green line on bottom of screen and you will see...
Hit the THANKS button if I helped you!
This mail was delivered from my W8 using Tapatalk!!
android core apps is a cached process. so it rests in the green half of the RAM indicator line. closing it wud result in less RAM
KASHYAP9 said:
Hello guys,
I found something strange in GingerDX ROM that I have marked in screenshot
Even this process can't be stopped more than 5mins. It starts itself.
In other CM7 ROMS there is no such process that is running in background.
AS written in second screenshot "kept for better speed", may be this is the process that also provide speed to system but also drain battery.
What do you think about it..??? Did anyone also found this..???
Click to expand...
Click to collapse
GingerDX v022 on Stock Kernel... NO SUCH PROCESS
"Running" shows ...
Maps, Settings, Maps, Android Weather, 3G Watchdog, DSPManager, Google Services, Android-Keyboard.
It's also not listed in the "All" tab, and I even can't find it with Titanium Backup.
Better investigate which app/mod spilled it into your ROM.
Set my DPI to 175. I like the look. My brother says it makes everything too small. What ya'll think?
https://www.dropbox.com/s/hbbqnclefud7cqf/Screenshot_2012-07-08-06-36-42.png
https://www.dropbox.com/s/awca9bs5wcai1y4/Screenshot_2012-07-08-06-36-53.png
https://www.dropbox.com/s/xqsyn6olqmvckvu/Screenshot_2012-07-08-06-37-35.png
https://www.dropbox.com/s/iacutxxcqyqhyk9/Screenshot_2012-07-08-06-39-23.png
{
"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"
}
I myself find low scale dpi a really nice look.
I haven't tried 175 yet but I'll make sure to take a look at it.
Guess I should get a tablet to suit my needs lol.
Sent from my ADR6300 using Tapatalk 2
I just like the look of high-res myself. If I could find a phone with a 4" 1080p screen I'd be all over it. LOL
That looks like ICS; does your phone app work at that DPI? I always had issues with that when I increased the DPI.
Yep. Its CM9 RC0 and phone app works fine.
Nice, thanks, I guess I'll have to give it a go again.
175 works great..I went into launcher setting and changed homescreen to 5x5 instead of the default 4x4. Makes the screen seem much bigger then it is.
I had to change it back to 200 cuz incoming calls crash my phone app although I was able to dial outgoing calls just fine.
That's odd, because when I set it to 175, I couldn't even dial. I've never been able to pull off that kind of setting on anything other than ParanoidAndroid and not have phone app FCs.
Go 160. 175 isn't an officially supported DPI for android
how do you change the dpi?
j13smiley said:
how do you change the dpi?
Click to expand...
Click to collapse
By build prop or LCD density app.
Sent from my ADR6300 using Tapatalk 2
I tried 160 a bit earlier today and had the exact same issue with the phone app. I would be inclined to believe that it may be a matter of the phone app in our ROMs not supporting anything other than stock DPI without modification to the app itself.
I'm comfortable with 200. Everything works so far.....also I change mine using ROM Tools. Its a slider. But you can use Root Explorer to change the build.prop file as well. Either way works.
Hi,
I just installed Xposed module Unbounce.
Could we use this thread to share our settings ?
It might help if you explained a bit about what Unbounce is for those that don't know, and link to the info
Xposed Repo - http://repo.xposed.info/module/com.ryansteckler.nlpunbounce
Play Store - https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce
It seems this provides the same functionality as Wakelock Detector and Wakelock Terminator. @Lennyuk Would you mind confirming this? And is there anything this or the other apps do that the other doesn't?
Japultra said:
It seems this provides the same functionality as Wakelock Detector and Wakelock Terminator. @Lennyuk Would you mind confirming this? And is there anything this or the other apps do that the other doesn't?
Click to expand...
Click to collapse
Not used it before, but as far as I can tell its like a hybrid between Wakelock Terminator and Greenify.
One of the first modules installed after root. Worked great on my aosp S3 and so far so good on the G3.
I set most of the settings to 300.
Sent from my LGLS990 using Tapatalk
MBCO said:
One of the first modules installed after root. Worked great on my aosp S3 and so far so good on the G3.
I set most of the settings to 300.
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Could you please share with us some of wakelocks you blocked?
What do you think of this screen shot?
{
"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"
}
FYI...Google maps was crashing when clicking on navigation button, had to revert back to default settings
Marcovanbasten said:
Could you please share with us some of wakelocks you blocked?
Click to expand...
Click to collapse
RILJ= 400
NlPWakeLock =400
NlPCollectorWakelock= 400
UlrDispatchingService= 400
Now these work for me. I didn't unbounce everything that woke the kernel or cpu under 3 min. I get very few wakelocks anyway and my phone deep sleeps 90% of the day
I used unbounce "default settings" for 2 days and noticed a stutter swiping through my home screens. Using Nova launcher. I un-installed the app and everything was smooth again.
I'm wondering does Unbouncing(taming) do more harm than good?
Example: if a process can't complete a function, will it make more calls in an attempt to complete the process.
I'm on lollipop so I just noticed but SetCPU hasn't been working for a while.
I need a program where I can say
When screen goes off -> underclock to X, importance 5
When battery at 50% underclock to Y, importance 1
When battery at 35% underclock to Z, importance 2
etc.
I only want it for underclocking. The build in battery control doesn't do much and my battery life is pretty terrible when I use the phone (screen on) a lot. I've tried CPU control pro and it would only allow me to set single profile, not have it changing interactively. If anyone has any good apps they've been using let me know, I need to do something about this.
Thanks!
look4alec said:
I'm on lollipop so I just noticed but SetCPU hasn't been working for a while.
I need a program where I can say
When screen goes off -> underclock to X, importance 5
When battery at 50% underclock to Y, importance 1
When battery at 35% underclock to Z, importance 2
etc.
I only want it for underclocking. The build in battery control doesn't do much and my battery life is pretty terrible when I use the phone (screen on) a lot. I've tried CPU control pro and it would only allow me to set single profile, not have it changing interactively. If anyone has any good apps they've been using let me know, I need to do something about this.
Thanks!
Click to expand...
Click to collapse
Since over/underclocking requires root the answer is there is no such thing for lollipop
Sent from my Note 3 via Tapatalk
donc113 said:
Since over/underclocking requires root the answer is there is no such thing for lollipop
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
I am rooted, on JasmineROM 5.1 (LP 5.0). I just followed the instructions avoiding the OTA and retained root. The CPU control programs I've found work for one setting, just not with profiles.
Let me widen the question out. Does anyone have any good CPU control utilities for LP or KK?
I know there is no going back one you're unrooted on LP although I've heard if you go back to 4.4.4 there is a method.
{
"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"
}
Good day everyone!
I have one specific question regarding our CPU governor. I've just installed CPU-Z and tried to check device's specs. Among other pleasing numbers i've figured out one strange thing . CPU Scaling Governor is displayed as unknown . This is quite strange . As far as i know usually there is 'Interactive' governor displayed. Do we have a custom governor version?
P.S. watching how CPU Cores' speeds change , i've noticed that currently there is a stable work of all Cores all the time even with CPU optimization setting enabled (all 4 cores are always active). Usually this depends on CPU governor , so i'm wondering if that is an intentional feature with propriatary governor from ZTE or some kind of BUG?
B04 version used.
{
"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"
}
deseandr said:
Good day everyone!
I have one specific question regarding our CPU governor. I've just installed CPU-Z and tried to check device's specs. Among other pleasing numbers i've figured out one strange thing . CPU Scaling Governor is displayed as unknown . This is quite strange . As far as i know usually there is 'Interactive' governor displayed. Do we have a custom governor version?
P.S. watching how CPU Cores' speeds change , i've noticed that currently there is a stable work of all Cores all the time even with CPU optimization setting enabled (all 4 cores are always active). Usually this depends on CPU governor , so i'm wondering if that is an intentional feature with propriatary governor from ZTE or some kind of BUG?
B04 version used.
Click to expand...
Click to collapse
Your fw version is strange for me, I've thought that ZTE skipped B04 version for A2017G.
Sent from my A0001 using Tapatalk.
i'm on b05 and i have unknow too on scaling governor on cpuz..