Related
Hi guys,
Just a couple of question that i hope someone here could help answer or point me in the right direction...
[I've searched the forums, and i can't seem to get the answer i'm looking for]
I'm running Axura Captive Edition 2.4 w/Setiron
1) How does voltage control work? is there a guide somewhere i could read up before i start using it?
2) how does setcpu differ from voltage control? Is it possible to run setcpu instead of voltage control? (as i am more familiar with voltage control)
3) Does Axura 2.4 comes with lagfix? What will happen if i try applying the lagfix from the OCLF from the android market? (i tried this with axura 2.2 and it bricked my phone and refused to start till i odin stock)
4) At the moment, i've read that axura already has OCLF - but i'm clocking only 1100+ on quadrant... and averaging 12Mflops on linpak. Is this normal?
5) Any other recommendations?
randy_khoo said:
Hi guys,
Just a couple of question that i hope someone here could help answer or point me in the right direction...
[I've searched the forums, and i can't seem to get the answer i'm looking for]
I'm running Axura Captive Edition 2.4 w/Setiron
Click to expand...
Click to collapse
1) How does voltage control work? is there a guide somewhere i could read up before i start using it?
Click to expand...
Click to collapse
You set the voltages at each freq. as needed...Each phone is different and what may work for someone else..may not work for you.Start small and work your way up.You can always hit the menu button on that app ...it will link you where you can read and discuss it on the I9000 forum...
2) how does setcpu differ from voltage control? Is it possible to run setcpu instead of voltage control? (as i am more familiar with voltage control)
Click to expand...
Click to collapse
Set CPU has it's own parameters it uses...as does voltage control...and NO...you can't just use it...the kernel developer says not to use it..
3) Does Axura 2.4 comes with lagfix? What will happen if i try applying the lagfix from the OCLF from the android market? (i tried this with axura 2.2 and it bricked my phone and refused to start till i odin stock)
Click to expand...
Click to collapse
Yes..and use what comes with it otherwise you may wind up with another brick..
4) At the moment, i've read that axura already has OCLF - but i'm clocking only 1100+ on quadrant... and averaging 12Mflops on linpak. Is this normal?
Click to expand...
Click to collapse
Benchmark scores mean nothing in the real world when lag fixes are enabled...
5) Any other recommendations?
Click to expand...
Click to collapse
Yes...more research on your part. Get on that thread and search out the support thread for Axura as well...Read up on over-clocking and under-volting...and the different lag fixes...what they are and what they do...While your at it...read up on the different modems..what each can or can't do..
Yes...there's a ton of reading evolved...but..if you don't take the time to go over the material completely..then you will really never understand it. All of your questions have been asked in that thread already...so start at the very beginning of the first page...and read it all...there is a ton of information in it where different issues have been discussed...That's what you need to do...wither or not you do is up to you.This forum also has a great search feature to use...you would be surprised how easy it is to find out all kinds of things about your phone and just about anything ever discussed about it...I know it takes more effort to do it this way...but..once you do..you won't feel like your in the dark about everything when something goes wrong..The folks on that thread are good people..and will help you with most problems..but you really do need to do your part as well..
Mac
EDIT: This app has been suspended, it serves no purpose anymore.
By popular demand, here's an app to set undervolt-values. It works on any ROM which runs on a suitable kernel, but needs init.d-support to be able to keep settings between reboots. (If your device supports it you'll get a button you can use, if not a little message in its place.)
WARNING: By using this app, you're playing with fire. It's in fact very likely you'll lose data if trying to see "how low you can go". Do not experiment without backing up everything first.
It's easy to use, and easy to freeze your phone with, make sure you know what you're doing. (Yes, changes become effective as soon as you apply them.)
It's clever when it comes to the volt_scheduler script as well, it only edits the line which sets the values at startup, meaning you can change the script as much as you like, the app won't touch anything else in it. (It also fixes the script-permissions on Topogigi 1.9, which aren't set correctly on a default install.)
The app will NOT let you change the startup-script until you have applied the settings. This is an attempt to avoid applying bad undervolts at startup. (The theory is that your phone will freeze if you're undervolting too much, and hence you won't be able to save those values to the startup script. If you try hard enough however, you will be able to save unstable settings, with the possible consequence of boot-loops and data-loss. I'm not kidding, be careful!)
NOTE: If you're using a system-monitor (System Tuner for example) and it doesn't show the voltages you applied, you need to force-stop and restart it before it'll show the current values (pun intended.)
NOTE2: Tegra 2 never supplies less than 770mV to the CPUs. The app will let you set undervolt below 770 though, and will in brackets show you what the real undervolt (on Tegra2) actually is. (Until recently I thought this was a hardware limit, but learned it is a kernel-limit. There may be kernels out there which can go lower. If the minimum frequency's default voltage is not the same as the kernel's minimum, the numbers in brackets will be off by the difference between the two.)
HEEELP: "I was very stupid and saved the undervolt-values to the startup script without testing properly first. Now it keeps rebooting. Is there anything I can do?" See Post #2.
Happy undervolting!
Click to expand...
Click to collapse
HEEELP: "I saved the undervolt-values to the startup script without testing properly first. Now it keeps rebooting. Is there anything I can do?"
Yes. The phone cannot be damaged by undervolting, but your data might. First thing you should do is to stop the reboots by pressing and holding "Power" and "Volume Down" to enter CWM.
You will need to have ADB installed on your computer. (The following instructions are for Windows-users.)
Select "Mounts and Storage" in CWM and select "Mount /system"
o In a shell, type:
If you're using a Topogigi ROM:
Code:
adb pull /system/xbin/volt_scheduler c:\
If you're using anything else:
Code:
adb pull /system/etc/init.d/S_volt_scheduler c:\
Now edit the file c:\volt_scheduler or c:\S_volt_scheduler in a PROPER editor like Notepad2 or Notepad++. DO NOT use the regular Notepad. You'll see a line with some numbers enclosed in quotation marks. Replace those numbers with zeroes. Save it.
Then type (Topogigi)
Code:
adb push c:\volt_scheduler /system/xbin/volt_scheduler
del c:\volt_scheduler
adb shell chmod 755 /system/xbin/volt_scheduler
adb reboot
or for other roms:
Code:
adb push c:\S_volt_scheduler /system/etc/init.d/S_volt_scheduler
del c:\S_volt_scheduler
adb shell chmod 755 /system/etc/init.d/S_volt_scheduler
adb reboot
If you're lucky, your phone will boot properly. If it still boot-loops, you've had some sort of corruption and need to wipe. If it still loops you've had corruption on the system partition, a full re-install (or backup-restore) is the last option.
Good job! Since I don't need OC but UV is useful for me.
greaatt... sadly this afternoon i already edit the script manually
wait for some hours, and i can use this wonderful tool!
nevermind, just download & let's play with this.. (editing script every testing is kinda annoying.. )
Thanks! I use your clock adjustment tools too
gideonrs said:
greaatt... sadly this afternoon i already edit the script manually
wait for some hours, and i can use this wonderful tool!
nevermind, just download & let's play with this.. (editing script every testing is kinda annoying.. )
Thanks! I use your clock adjustment tools too
Click to expand...
Click to collapse
You're very welcome.
thanks for ure great effort.
can you specify the UV settings that will not damage the phone?
p.s. i really like unlock silly values option
Thanks.
edit: can i use -50Mv
shpapy said:
thanks for ure great effort.
can you specify the UV settings that will not damage the phone?
p.s. i really like unlock silly values option
Thanks.
edit: can i use -50Mv
Click to expand...
Click to collapse
I wish it were that easy. Every phone is different. Mine seems to be completely stable at -75 across the board, and at 800Mhz I can run it at the lowest voltage possible, 770mV. Which is why I run everything at -50 ;-) (I learned a long time ago that balancing on the edge sooner or later makes you fall off.)
Other people have reported that their max stable undervolt is -25mV. There's no single recipe for everybody.
The correct way to test it is to set both min and max-frequencies to the same (for both awake and sleep-modes), then decrease voltage by one step, then run the toughest apps you can think of for at least 15 minutes each. If nothing weird happens, write down the numbers, decrease one step again, etc. etc. until you have found the breaking point for that particular frequency.
Then, and this is important, you need to make sure the phone is able to wake from sleep with those same values. For this you need to set sleep-mode to the normal frequencies again.
If everything works out with that, rinse and repeat with the next frequency. After you're done, you should have a nice set of numbers - increase them all by 25mV. That's your lowest stable voltage for each frequency.
thanks allot for the detailed and super fast reply.
as i mentioned in the edit i edited the Mv to 50 all across the board and its fine
also when gaming (thanks for the tip, i was just running quadrant each time)
i am running neoblaze with FR19 (2.2)
I UV by 50mv and then saved the profile with pimp my CPU and applied at boot since I use init.d
I wonder how much more battery I can squeeze more now
Sent from my LG-P990 using XDA App
Awesome apps Trym! I downloaded this and the OC one. Left some stars on the market too.
salisbury_steak said:
Awesome apps Trym! I downloaded this and the OC one. Left some stars on the market too.
Click to expand...
Click to collapse
Thanks!
10chars.
shpapy said:
I UV by 50mv and then saved the profile with pimp my CPU and applied at boot since I use init.d
I wonder how much more battery I can squeeze more now
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
I guess I can easily do that from the app. Currently looking into how to best determine if a system has working init.d support.
EDIT: Done.
TrymHansen said:
I guess I can easily do that from the app. Currently looking into how to best determine if a system has working init.d support.
EDIT: Done.
Click to expand...
Click to collapse
so what is the next step with the app?
shpapy said:
so what is the next step with the app?
Click to expand...
Click to collapse
I don't have any more plans for it at the moment, it does what it was designed to do. Open for suggestions though. I did add support for startup-scripts on ROMs with init.d. (I modify PimpMyCpus script, if it's there, to avoid conflicting scripts. If not I create it.)
TrymHansen said:
I don't have any more plans for it at the moment, it does what it was designed to do. Open for suggestions though. I did add support for startup-scripts on ROMs with init.d. (I modify PimpMyCpus script, if it's there, to avoid conflicting scripts. If not I create it.)
Click to expand...
Click to collapse
Please bring back set on boot
Thanks!!!!
Sent from my LG-P990 using XDA App
shpapy said:
Please bring back set on boot
Thanks!!!!
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Long story short: Some ROMs didn't apply the settings at boot due to non-functioning init.d. So I made some changes to better discover which ROMs support it. So, in theory, if the button isn't there, you're running a ROM which it doesn't work on anyway.
This is all very new to me, If I mistakenly remove the button on ROMs where you have working init.d, please report back here with the details of the ROM. (Update to the latest version of the app first.)
I tested it on GR4 cooked with stock kernel (no working init.d support, even when you replace the kernel), GR4 cooked with custom kernel (working init.d), Fr19 (Working init.d), Topogigi (which it was originally designed for - always working) etc.
CM7 has init.d support, but refuses to set the undervolt-values both live and and boot (VorkKernel), I'm looking into that.
I have fr 19 with the latest neoblaze which supports for sure since i checked the logcat. also now with topo 2.0 its missing
Sent from my LG-P990 using XDA App
I jumped the gun i had to clear data working fine now
Sent from my LG-P990 using XDA App
shpapy said:
I jumped the gun i had to clear data working fine now
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Ok, good to hear.
Just a heads up that it now works on VorkKernel (CM7) as well, from appversion 0.6.5.
I'm experiencing something I didn't have before.
Applications gets closed instead of keep running in background when they get minimized for any reason, either if I press the home button or I get an incoming call.
An annoying example is receiving a call while using GPS navigation: after the call screen comes out the navigation software is closed and when I try to resume it, it will start as a new launch.
I've tried some search, and I understand could be something related to android memory management. But I'm not such an expert, and I don't see thing like this here in the SGS forum, which is (I think) still good enough as a device to be able to manage a call and a navigator both running together. Plus, I didn't have this before.
I'm on 2.3.3 JV3
Thanks.
Same problem here 2.3.5 jvs
Sent from my GT-I9000 using XDA App
eresac said:
I'm experiencing something I didn't have before.
Applications gets closed instead of keep running in background when they get minimized for any reason, either if I press the home button or I get an incoming call.
An annoying example is receiving a call while using GPS navigation: after the call screen comes out the navigation software is closed and when I try to resume it, it will start as a new launch.
I've tried some search, and I understand could be something related to android memory management. But I'm not such an expert, and I don't see thing like this here in the SGS forum, which is (I think) still good enough as a device to be able to manage a call and a navigator both running together. Plus, I didn't have this before.
I'm on 2.3.3 JV3
Thanks.
Click to expand...
Click to collapse
I've only experienced this with games, I think it might be because apps/games are not optimized for Gingerbread
Well it seems I'm not alone.
Any suggestion is welcome.
Well if ypu arecrooted then flash semaphore kernle and then install semaphore tool.
Then change ram settings to mulitasking 32 mb from the semaphore tool app.
sent from the beast known as samsung galaxy s. ;-)
BHuvan goyal said:
Well if ypu arecrooted then flash semaphore kernle and then install semaphore tool.
Then change ram settings to mulitasking 32 mb from the semaphore tool app.
sent from the beast known as samsung galaxy s. ;-)
Click to expand...
Click to collapse
You're suggestion worked for me. Thank you very much.
I'm still wondering why it's happening now, and not before...
eresac said:
You're suggestion worked for me. Thank you very much.
I'm still wondering why it's happening now, and not before...
Click to expand...
Click to collapse
Did you change ROMs? Kernels? Anything? Somehow your RAM settings must have changed.
V6 Supercharger script can also accomplish the same thing, in case anyone needs a solution but wants to keep their current kernel.
upichie said:
Did you change ROMs? Kernels? Anything? Somehow your RAM settings must have changed.
V6 Supercharger script can also accomplish the same thing, in case anyone needs a solution but wants to keep their current kernel.
Click to expand...
Click to collapse
Well, I can say this behavior appeared after upgrading to stock (official/kies) 2.3.3 (CF-root ed as the previous).
Honestly I can not state from what change depended from.
Anyway, just my humble point of view after facing that, this thing could open a nice discussion on android memory manager, and the strategy/philosophy above.
eresac said:
Well, I can say this behavior appeared after upgrading to stock (official/kies) 2.3.3 (CF-root ed as the previous).
Honestly I can not state from what change depended from.
Anyway, just my humble point of view after facing that, this thing could open a nice discussion on android memory manager, and the strategy/philosophy above.
Click to expand...
Click to collapse
There is plenty of information regarding Android's memory management—on this forum and abroad—if you're interested in learning.
Did you upgrade from Froyo? If so, that would be why.
upichie said:
There is plenty of information regarding Android's memory management—on this forum and abroad—if you're interested in learning.
Did you upgrade from Froyo? If so, that would be why.
Click to expand...
Click to collapse
This means that Froyo is better in memory usage, at least for the SGS, I guess.
I simply didn't take care about that when decided to upgrade, thinking "SGS is powerful enough". Think I'll have to investigate.
Anyway thanks for all your support.
This is post 1: Andrev OC daemon.
Undervolting is in post #2: http://forum.xda-developers.com/showpost.php?p=30979035&postcount=2
So recently, I have had a few people asking me about the Andrev OC daemon that I use on nearly every rom/kernel.
So I thought as a way to give back a bit to the community, I would write this
Original thread: http://forum.xda-developers.com/showthread.php?t=1222020
The whole reason behind having the Andrev or Virtuous Daemons is to limit the screen off CPU frequency in order to save battery.
Diamondback said:
Introduction to the new Overclocking Daemon
This ROM features a completely new way of Overclocking and managing screen states.
The History
But before explaining it further, let's talk about previous solutions.
There are several different approaches to archieve "screen-state-scaling".
That means basically that the govenor changes if you turn the screen off and changes back to normal when turning the screen on.
This is mainly used to restrict the amount of CPU usage (the frequency in fact) during screen off. This can lead to a major battery life increase.
The solutions so far were:
App like SetCPU, which change automatically the govenor based on profiles
integrated solutions in the govenor itself
Both these solutions have major problems.
The one with a tuner app is always a little laggy right after turning on the screen because SetCPU (or any other CPU tuner) needs some time to change the govenors (up to 7 seconds). This leads mostly to major lag in the lockscreen.
The second solution is the smartass govenor. It has already a screen-state-scaling included, so it reduces the frequency when the screen turn off.
This could be a really nice solution but it has some problems too.
Smartass most of the time is not really stable and has problems with its frequency scaling.]
Click to expand...
Click to collapse
The Virtuous and Andrev daemons are basically the same thing, just that the andrev one is easier to install IMO
The Virtuous daemon comes pre installed in a lot of virtuous roms, insluding Unity, Infinity, Affinity
The thread itself has not been updated this year, but hey, it has been written for single core devices, and works very well on my phone. The reason behind not being updated I think is that it has reached its potential, the developers of the daemons have moved on to newer multi core devices like the HTC sensation and One X.
So anyway, enough introduction, let's get to the guide:
*You need to be rooted to install this, it should work on any single core device*
*I also recommend having a custom kernel with more available frequency steps*
*I am not responsible for anything that happens to your device. This is quite easy and safe, but if you are a talent at screwing up your devices then maybe a but more research would be good*
*READ THROUGH THE WHOLE GUIDE BEFORE STARTING SO YOU KNOW WHAT YOU'RE DOING*
This works with every custom rom I have tested, I have not tested it on MIUI V4. On MIUI GB it works.
For reference, I am using ARHD 3.0.1 with l0st.prophet's v2.2 kernel now.
You can try the flashable zip in the original thread but I was never able to get that to stick
1. Download the latest Daemon Controller apk. Latest versions and older versions can be found here
http://forum.xda-developers.com/showthread.php?t=1949502
2. Install the apk like a normal app, open it, grant it superuser permissions.
3. Go to the Options tab, the forth one, and from there install the daemon. It is an automated process. When its done, close the app by pressing the back button a few times and open it again.
4. You should see all the sleep/wake options in the OCD tab. Set them to whatever you like. For reference, I set mine to 245min/1200max Lionheart screen on, and 245/368 conservative screen off. Click on apply. I recommend that you use a higher frequency/fastergovernor for screen on max, because thats where you will get your performance. For screen off limit to a lower frequency and more conservative governor in order to save battery for when the high speed is not needed, eg, when you listen to music. Too low frequencies will cause problems. But, you don't want to have the phone at 1.2GHz playing music, do you?
Kernel governors thread: http://forum.xda-developers.com/showthread.php?t=1631894
5. Right click and save as http://bit.ly/oI85wL as a .txt file, and put it in /system/etc/init.d of your phone. Take off the .txt so it is just 83oc, then use script manager to set the file to run at boot/as root by navigating to /system/etc/init.d of your phone and pressing on the 83oc file, making sure that the gear and the superuser icon are pressed.
*With newer versions this file is automatically generated so you don't need to replace it, if it is already there *
Long press it, go to properties and set its permissions to rwxrwxrwx (9 boxes ticked)
You might need to use another file browser like es file explorer to do this, smanager sometimes FC's trying to do this (thanks interaser for reminding me)
6. The Andrev OC daemon should now be installed. I use CPUspy to monitor my CPU speeds. Reboot the device and leave it for a few mins, then open up the daemon controller app and check if it says "Active Daemon: Andrev OC" at the top. If it does, success! If it doesn't you might have done something wrong, try again from the start, see if you've done EVERYTHING correct, then post here.
7. Click on my the thanks button for this post, and the linked posts. Its just courtesy
Click to expand...
Click to collapse
Happy overclocking! Remember that overclocking too much could be bad for your processor.
Many thanks to Sybregunne for his work and continued support in his own thread, and this one too
And to all the members who gave feedback
Undervolting
Undervolting guide: From post #12 by me
Why undervolt?
Undervolting is basically feeding less voltage to your processor, while delivering the same performance.
Its kind of like forcing you to run a marathon, but giving you less water. You will probably make it, but some may collapse/ hot reboot because there is not enough water/voltage. If you drink less water/use less voltage, you will save on water/battery while having the same end result of finishing the marathon. But if you don't have enough, you might collapse/reboot and try again, with more water/voltage. With normal voltage/water supply all will make it. Hope that helps you to understand.
Using less voltage will help save battery while keeping the phone cooler, not that the incredible s has cooling problems, unlike the Nexus 7 and One X with the Tegra 3
You can use an app called 'incredicontrol' from the play store.
https://play.google.com/store/apps/...=W251bGwsMSwxLDEsImNvbS5pbmNyZWRpY29udHJvbCJd
Alternatively, I now use TricksterMOD to do voltages and stuff. Its very easy with tricksterMOD
This will work on all roms with custom kernels that have the voltage control (VDD interface). It requires a kernel which supports undervolting.
This requires more patience than the daemon, and will probably cause instability at some point during testing.
OLD METHOD I USED TO USE: INCREDICONTROL
1. Download the app, grant it superuser permissions. Go to the svs tab and press the - button at the top left once. You should notice all the values go down by 25 mv
2. Scroll down to the bottom, click apply and exit the app, play around with the phone as normal. Because 'save for boot' wasn't checked, it will reset back to normal after a reboot, in case it causes instability.
3. if it's stable, go back to the app and click on -25 again, and apply. Play with the phone more to ensure that its stable.
4. Keep doing this until it becomes unstable, remembering the last stable value. My phone can handle -75mv under volting, yours will probably be similar. I advise not to do more than -100mv
5. When you find a stable setting, set that setting, and scroll down to the bottom. This time choose 'save for boot' and apply. Now the settings should stick after a reboot.
6. Done! Don't delete the incredicontrol app. The phone needs it iirc for undervolting to stick
7. Click thanks please
Takes me a while to write these thing up for you guys
Click to expand...
Click to collapse
Now, it is much easier to use TricksterMOD. Voltage control is in the column on the far right in the app's GUI
1. Test voltages as above
2. When you find a stable setting, press menu --> set on boot -->tick enable.
Click to expand...
Click to collapse
WARNING
if you undervolt too much and save for boot, you phone probably will boot loop. You will have to reflash the ROM and kernel. So don't save for boot until you've played around with the phone for an hour or so to ensure that its stable.
Any questions, feel free to ask them
Also remember that not every processor is the same even though our phone is the same, so some may handle overclocking better than others
This is good. You have an interesting writing style.
Nonverbose said:
This is good. You have an interesting writing style.
Click to expand...
Click to collapse
lol why is that? I am hoping that it's understandable?
First of all, thanks mark for this how-to guide. Always want to try this as i acknowledged the lag problem with using oc app such as setcpu (when switching the screen on and off) .
And yes, you do have a good writing style mate :thumbup:
Sent from my Incredible S using xda app-developers app
markj338 said:
lol why is that? I am hoping that it's understandable?
Click to expand...
Click to collapse
Yes it's understandable. What I mean is that it's informative, relevant and well structured. Write more!
Nonverbose said:
This is good. You have an interesting writing style.
Click to expand...
Click to collapse
I assume he means you write as if you are talking to a friend in a chatty manner. Not a bad thing just most people write in a blunt manner.
Sent from my HTC Incredible S using Tapatalk 2
vizzy said:
I assume he means you write as if you are talking to a friend in a chatty manner. Not a bad thing just most people write in a blunt manner.
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
Oh okay haha, I don't want to be all formal and stuff because this is a forum, I don't want this to come across like a textboook or a lecture or something
Now only i realize that you open a thread for this
how about UV? Should be simple for you as can be added on this thread too?
Yep,write more about UV buddy ^_^
sinosuke said:
Yep,write more about UV buddy ^_^
Click to expand...
Click to collapse
Undervolting guide is now in post #2
http://forum.xda-developers.com/showpost.php?p=30979035&postcount=2
I have updated the first 3 posts with some new information for ease of use and more guides
Press thanks if you like my guide/found it helpful/found my writing style interesting
Enjoy!
Hi, i used setcpu before and already uninstalled it. After installing and using this, i can't find a way to make the oc settings to stick on icecoldsandwich. The only way is for me to manually change the cpu freq in rom controll setting.
Any thoughts guys? Thanks
Sent from my Incredible S using xda app-developers app
larkhillv7 said:
Hi, i used setcpu before and already uninstalled it. After installing and using this, i can't find a way to make the oc settings to stick on icecoldsandwich. The only way is for me to manually change the cpu freq in rom controll setting.
Any thoughts guys? Thanks
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
Untick set at boot from Rom control
Did you put the script in place?
Sent from my HTC Incredible S
Did both of that. The sleep setting works well though. I only need to change the wake value on rom control and that's something i can live with
Thanks for the guide :beer:
Sent from my Incredible S using xda app-developers app
larkhillv7 said:
Did both of that. The sleep setting works well though. I only need to change the wake value on rom control and that's something i can live with
Thanks for the guide :beer:
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
Editing the values in rom control will disable the daemon iirc
Does the daemon controller app tell you that the andrev daemon is active? It worked for me in ICe Cold
Did you remember to set the script to run at boot? Could you please post what else is in your /init.d folder?
Good job again Mark
Keep them up
letmedanz said:
Good job again Mark
Keep them up
Click to expand...
Click to collapse
Thank you, glad I can finally contribute some information to the community I have taken so much from
Sent from my Nexus 7
Daemon control FC on Miui...any alternative?
Sent from my HTC Incredible S using xda premium
linezero said:
Daemon control FC on Miui...any alternative?
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
If you can't update your su binary, I would give up lol
Or you could manually install it
Not working for me on cooldroid either, its FC'ing
I will resort to using incredicontrol for my CPU speeds with no daemon
Yeah, I'm new to all these kernels and shtuff and I was just wondering if customs OC kernels like ElementalX will interfere with apps like Whatsapp as it runs in the background to receive messages. Thanks in advance and sorry for being such a nub.
Androidian10 said:
Yeah, I'm new to all these kernels and shtuff and I was just wondering if customs OC kernels like ElementalX will interfere with apps like Whatsapp as it runs in the background to receive messages. Thanks in advance and sorry for being such a nub.
Click to expand...
Click to collapse
I run many custom kernels and did not notice any interferences...
It's not so much the kernels as it is the person setting their parameters. Such as if you have a background app wanting to use a certain level of memory when the screen is off lets say 440mhz and you set your screen off max to 300mhz you're going to cause your system a lot of confusion for nothing. However I wouldn't recommend any apps that are running constantly as your phone will never go into deep sleep. That being said you can create a wide variety of profiles in most tuner apps to allow for things such as this.
Sent from my HTC One using xda premium
itsbeertimenow said:
That being said you can create a wide variety of profiles in most tuner apps to allow for things such as this.
Click to expand...
Click to collapse
Could you elaborate on this? Tuner apps? I have SetCPU but I don't dare mess around with anything in there except setting the max and min CPU values.
But anyways I caved in and flashed ElementalX a few minutes ago. UI seems snappier to me.