Thank to Workshed for finding the errors!
Universal Script for Android Phone No more RING lag phone rings by the 2nd ring and screen and caller ID pops right up.
There are a few vers to test I am uploading my ver of it now it has a few tweaks removed for the CPU and kernals. But added a few thats it works much better now and it will get along with other Twaeks like supercharger.
All Zips from this post are flashable from recovery.
Here is the link to the OP I found it on. http://forum.xda-developers.com/showthread.php?t=1205259
This Is VER 2 there where errors in the 1st ver and also on the OP that i found this on.
I patched it up and also tested it and the file is running great without any errors as far as I can see.
By the end of the 2nd ring the phone lights right up with caller ID and rings even with custom ringtone. The dialer when placing a call is so much faster when it opens it just POPS.
#!/system/bin/sh
#00Ring_lag_v2 computerfreek#
MAX_PHONE() # remove lag when answering phone calls
pidphone=`pidof com.android.phone`;
if [ $pidphone ];
then
echo -17 > /proc/$pidphone/oom_adj; # exclude com.android.phone from oom-killer;
renice -20 $pidphone; # set highest nice level for com.android.phone;
log -p i -t ScreenState "*** MAX phone *** set oom_adj(-17) and nice(-20) for com.android.phone";
exit;
else
sleep 1;
MAX_PHONE;
# Background process to check screen state;
(while [ 1 ];
do
cat /sys/power/wait_for_fb_wake;
AWAKE_MODE;
cat /sys/power/wait_for_fb_sleep;
SLEEP_MODE;
then
# One-time process to optimize com.android.phone;
(while [ 1 ];
sleep 10;
MAX_PHONE;
; \ fi
Click to expand...
Click to collapse
Here is the Links
http://dl.dropbox.com/u/17779317/New%20folder/00Ring_Lag_v2.sh
http://dl.dropbox.com/u/17779317/00Ring_Lag_v2 Raw TEXT to place in a file and add it to your init.d folder.
http://dl.dropbox.com/u/17779317/ringlagv2/00ring_lag_v2.zip Flashable Ver 2
If you are runing the v4.0 of worksheds GSB then here is a Patch that will replace the One on ROM with V2 http://dl.dropbox.com/u/17779317/ringlagv2/00ring_lag_v2_GSB_patch.zip
computerfreek said:
OH that sucks ! Download prankdial from market and prank your self! lol it will call you.
If you pm me your number and I can call you from my gv.
Hows the phone runing with other things after adding the script?
Click to expand...
Click to collapse
Sorry to jump threads on you, I didn't want to clog up CondemnedSoul's thread with questions/comments specifically about this script....
After loading & rebooting, I didn't notice any problems. The phone seems a bit snappier with this in general, although I still haven't tested the incoming calls thoroughly yet. I am running this script on Comndemned v17 S2h in combination with the v6 SuperCharger, and the 3G & Kernel Tweaks. Based on a recommendation from CS, I also modified the following line in the build.prop from
ro.telephony.call_ring.delay=500
to
ro.telephony.call_ring.delay=0
I haven't noticed any conflicts or issues yet, but I wouldn't necessarily classify myself as a heavy user.
I have another question for you. Since it was easy enough to modify the CPU speed, if I change the governor in the following line
GOVERNOR_SCALE="ondemand";
to smartass so that it will match my CM7 performance settings, will that cause any issues? Does this script need to be set to ondemand in order to work correctly?
computerfreek said:
I found this Universal Script for Android Phone it just ROCKS I am testing it on GSB3.8 workshed and now when I call my cell it starts ringing after just 1 ring! I tested it on Gin-sen-tazz but I don't think it is working on GINGER SENSE ROMS
Here is the link to the fourm I found it on. http://forum.xda-developers.com/showthread.php?t=1205259
The only thing I changed on the it was the MAX CPU from 800 to 710 and it all seems to be working great. I will see in a few hours after leting the phone sit and then calling it.
Hope this will help Others on CM7 GB roms.
Here is the one I am useed on my phone. http://dl.dropbox.com/u/17779317/00tweaks
Click to expand...
Click to collapse
So all you have to do is copy 00tweaks and put it in your init.d folder???
PillClinton said:
Sorry to jump threads on you, I didn't want to clog up CondemnedSoul's thread with questions/comments specifically about this script....
After loading & rebooting, I didn't notice any problems. The phone seems a bit snappier with this in general, although I still haven't tested the incoming calls thoroughly yet. I am running this script on Comndemned v17 S2h in combination with the v6 SuperCharger, and the 3G & Kernel Tweaks. Based on a recommendation from CS, I also modified the following line in the build.prop from
ro.telephony.call_ring.delay=500
to
ro.telephony.call_ring.delay=0
I haven't noticed any conflicts or issues yet, but I wouldn't necessarily classify myself as a heavy user.
I have another question for you. Since it was easy enough to modify the CPU speed, if I change the governor in the following line
GOVERNOR_SCALE="ondemand";
to smartass so that it will match my CM7 performance settings, will that cause any issues? Does this script need to be set to ondemand in order to work correctly?
Click to expand...
Click to collapse
That shouldn't cause any issues at all. It should just default your governor to smartass instead of ondemand.
CondemnedSoul said:
That shouldn't cause any issues at all. It should just default your governor to smartass instead of ondemand.
Click to expand...
Click to collapse
Done, & no issues to report yet. I also changed
GOVERNOR_FREQENCY_MIN="245760"; to GOVERNOR_FREQENCY_MIN="480000"; for the purpose of matching my CM7 settings.
bigdaddyblues said:
So all you have to do is copy 00tweaks and put it in your init.d folder???
Click to expand...
Click to collapse
Well you chave to copy and set the permissions.
Or use flashable ver of the 710MHZ for eris http://dl.dropbox.com/u/17779317/00tweaks.zip
PillClinton said:
Done, & no issues to report yet. I also changed
GOVERNOR_FREQENCY_MIN="245760"; to GOVERNOR_FREQENCY_MIN="480000"; for the purpose of matching my CM7 settings.
Click to expand...
Click to collapse
I don't think matching it matters so much as it is set to RUN the the CPU speed set 1 time on start up be for cm7 sets it's speed. CM7 looks like it will override it after it's booted. So even if you load the 710MHZ ver and have cm7 set at 600mhz it will drop to 600 after cm7 is fully loaded.
I think there may be a conflict between this script & zeppelin's v6 supercharger. I had 3 screen redraws today for the first time in ages. When I was using the supercharger by itself, I had no problems.
I removed the 00tweaks & rebooted for now.
Sent from my Condemned Eris
One other question about the 00tweaks. I looked through the script & noticed it has some tweaks built in for dialer one. Since I don't use dialer one, could it be modified to tweak go contacts ex instead?
Sent from my Condemned Eris
PillClinton said:
One other question about the 00tweaks. I looked through the script & noticed it has some tweaks built in for dialer one. Since I don't use dialer one, could it be modified to tweak go contacts ex instead?
Sent from my Condemned Eris
Click to expand...
Click to collapse
I was thinking the same thing I don't see why not it looks like it will work for any service app I don't know if contacts is a service or not. You can PM tazz811 on the OP. And see if you can help you with that. Link to OP If you get it working for other apps please post back here so we can all use it. http://forum.xda-developers.com/showthread.php?t=1205259
PillClinton said:
I think there may be a conflict between this script & zeppelin's v6 supercharger. I had 3 screen redraws today for the first time in ages. When I was using the supercharger by itself, I had no problems.
I removed the 00tweaks & rebooted for now.
Sent from my Condemned Eris
Click to expand...
Click to collapse
I have been testing it with and without supercharger and it seems fine for me. However it be nice if we can just make a new script for just rintone lag so there will be no conflicts at will even if your just OC with CPUboost.
I think we will see soon DEV apping just the phone LAG stuff into there ROMS. This way we can just boost or OC with any other apps or scripts.
I don't think they are playing well. I don't usually use the super charger script, but had applied multi tasker setting after a few apps were killed by system that I wanted running in background. First, I notice extremely poor battery life - some service kept the phone awake all night so it didn't fully charge. This also happened yesterday with xda app, but don't know what did it last night. Also, notice that the super charger minfree values did not stick, so the 00tweaks must over ride them at startup. I was having the background app problem before the tweaks, so I suspect that the super charger kernel tweaks conflict with the 00tweaks. Undid both for now
Sent from my ERIS using XDA App
Getting rid of the 00Tweaks seems to have solved my screen redraw issue for the moment. I was also having some issues with lag after leaving certain apps, and that is gone too.
klobkelosh said:
I don't think they are playing well. I don't usually use the super charger script, but had applied multi tasker setting after a few apps were killed by system that I wanted running in background. First, I notice extremely poor battery life - some service kept the phone awake all night so it didn't fully charge. This also happened yesterday with xda app, but don't know what did it last night. Also, notice that the super charger minfree values did not stick, so the 00tweaks must over ride them at startup. I was having the background app problem before the tweaks, so I suspect that the super charger kernel tweaks conflict with the 00tweaks. Undid both for now
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
What desktop launcher are you rinning ? I am running launcherpro plus with no redraws.
Adw stock with cm7.
Sent from my ERIS using XDA App
klobkelosh said:
Adw stock with cm7.
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Maybe it the laucher or the ROM your on mine is working great, But has also been the same with or without supercharger is I do not get redraws or any teaking. I am Runing worksheds last release 3.8 and it is working great. I never use ADW so can't tell you if it is that or not. As if I test or use a rom and it has ADW or any other lanucher on it I always add lancher pro on it and resign the rom befor I even install it.
Maybe you can talk to TAZZ811 on the like from the OP. and see if he can help use out with just the phone lag tweak with no mem or kernals tweaks. Thats what I think we need.
I am sicking with it on my phone I hate missing calls And with this tweak my phone lights right up with the caller ID and it's ringing just as the 2nd ring starts. I hope others try this out and see if they get the same thing.
It maybe as easy as just removing or #out the kernal and mem tweaks on the script.
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
klobkelosh said:
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
Click to expand...
Click to collapse
Nice, I did the same thing. I tried leaving in a few of the other tweaks to see if I notice any difference (either way). If I start running into problems again, I'll check your version out.
klobkelosh said:
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
Click to expand...
Click to collapse
Nice I was testing with that also. I hope it all works out for you with your setup. I can make a flash .zip ver of each one to make it easy for others.
Thanks for testing this out. I hope DEV's just start rolling it in there roms.
klobkelosh said:
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
Click to expand...
Click to collapse
klobkelosh, sorry for the newbie question... how do i get to the init.d folder? and i tried deleting the extension in file manager with no luck
Related
I just want to know if anyone else is running this script. I refused to believe my Nexus S was not behaving, after all, it's a Nexus S! But, eventually even I had to get real. Truth is, lately, no matter what ROM I'm running after a few days things would slow down way too much. Lag, Launcher redraws, FCs due to lag. Things were too slow.
Anyway, I used the V6 SuperCharger script and it really has changed things. I used the MegaRAM option for 512 MB phones and I swear it has been a revelation. Even overclocking couldn't bring about this change. Currently, I'm on MIUI which most people consider to be a bit heavy and clunky. However, after supercharging with the MegaRAM option and Bulletproofing the launcher it's unstoppable! Highly recommended for those of you experiencing phone lag. Make sure to follow the Dev's instructions for using his script. All credit to user: zeppelinrox. Amazing stuff!
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
I used the 2nd MegaRAM option as well. But, I'm going to test out the first option. As I understand it, the more memory you want free in the 3rd slot the less multi tasking you can do (as this is where the secondary apps will be places)...I THINK!
As per that thread if 25 MB is good enough on a Milestone, a Nexus S should do well with 40 MB.
THIS from the thread:
zeppelinrox said:
Additional Info: You can find each app's priority and OOM.
....................... In AMM, Press Menu > Running Processes > Group by OOM grouping.
....................... Expand each group and see what apps are included and each app's priority level. (Higher numbers get killed first!)
....................... If you tap on an app, you can get additional info. Tip: Check and see what's included with android.process.acore
The default minfree values ("kill thresholds") for each OOM group are, as far as I can tell: 6, 8, 16, 20, 22 and 24 mb. (CyanogenMod 6.1.2)
This means that: when free memory lowers to 24 mb, EMPTY_APPS get killed; at 22 mb free ram, CONTENT_PROVIDER apps get killed; and so on...
Now, because the Milestone has only 256 mb of memory, I found these numbers too low, especially the 3rd one.
Basically, with those settings, you will usually be sitting with only 20 - 25 mb of ram.
Possibly less. Basically, it's the 3rd number (16) + 5. That's your free memory.
And my phone just chokes when it has that little ram available. Lag, home screen redrawing, the launcher getting killed.... ugh....
After extensive fiddling around, I've come to the conclusion that setting the third slot to about 25mb works great.
No home screen redraws while not being too aggressive on secondary/background apps while having about 30-35mb free all the time
BTW, free ram is not wasted. Android will use that memory to cache the file system and this speeds things up. See this informative post.
Click to expand...
Click to collapse
Si_NZ said:
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
Click to expand...
Click to collapse
Just tested the 1st MegaRAM option and things are quite smooth. Launcher is not as buttery as with the 2nd option but, it's still great. The browser does quite well too, pinch to zoom is smooth but, scrolling is a little stuttery on a heavy page like Engadget's.
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
never heard of this till this morning, thanks for bringing it up
trying it out now
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
I love it when a tweaker tells tweakers not to tweak.
Really!
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
you should know that two scripts running can cause issues......
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
I didn't said anything against your script, just told the users to not use it on my custom ROM. A think that as maker of your script you should know - two RAM scripts on same ROM are doing only damage.
They don't stay running.
They execute and end.
Whichever one runs last is the one that sticks.
Many people were using juwe's script with the V6 script and things ran fine so it's not a big deal.
Of course, if somebody wanted to, they can delete the minfrees in any of their custom roms and plug them into supercharger...
Why do you guys like scaring the crap out of people for nothing? lol
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
Great to hear from you. Haha. Just about to ask you
does it work well with cm7?
mohsin125 said:
does it work well with cm7?
Click to expand...
Click to collapse
I'm running it on cm7, and my phone seemed to be a bit snappier
time will tell though
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
rican408 said:
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
Click to expand...
Click to collapse
use this guide, and it will be easier than you could imagine
http://forum.xda-developers.com/showthread.php?t=1126940
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Haizum74 said:
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Click to expand...
Click to collapse
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Just an update on my settings. The MegaRAM seem to really speed everything up but, I find that they weren't being nice to my Whatsapp (I was missing messages now and then) I think Whatsapp would receive the message but get immediately killed before it could broadcast the notification. Once it even seemed to exit in app for no reason at all. So I switched to Balanced Settings 3 and so far Whatsapp as well as the launcher and phone in general has been very responsive.
Sent from my Google Nexus S using XDA App
deejaylobo said:
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
I went for Megaram option 1 (I think). I disabled password and it then worked but by this time I had uninstalled the script. Any particular option you suggest? Cheers for the reply too.
It depends on your usage. I would suggest starting out with Balanced settings 3 and moving up or down the menu depending on whether you want more(down) or less speed(up). I've found that the trade off is speed vs multitasking. Though, I think zeppelinrox could confirm whether I'm right.
Hi,
Since I'm not yet able to post directly into the main thread, I'll post some opinions and experiences here.
The original Thread: http://forum.xda-developers.com/showthread.php?t=1364411
Current setup:
ROM: NEXUS MV 2.12.25
Kernel: GLaDOS 2.5 CFS - 3.0.8
So far, great ROM at all.
No reboots, no crashing apps...
But there are some things a bit annoying:
- On the NSTools, the "backlight dimmer" function only disables the capacitive buttons after the selected time, doesn't change anything in the display (I really don't know if it's a bug or not);
- Most of the times (not always) when I press the button to lock screen, after the animation the screen "flashes" and only after that I hear the "click" sound, but I think it's more a kernel issue than a ROM issue;
- The Assasin's Creed Revelations Game doesn't load the Main Menu completely, only the title appears and I can't select anything. I've reinstalled it and the problem still occurs, but I don't know if it's a ROM problem or some crazy incompatibility.
And also I'd like to send my suggestions:
- I've used another ROM (wich I really don't remember exactly what was) with a launcher where there was an option to prevent the apps menu to slide into the widgets, it would be nice to have it here too... (don't know if it can be implemented on ROM or only on the Launcher)
- I miss an option to enable/disable 3G data connection on the top menu of the slider, like CM7.
I can't think on any other thing to add for now...
The ROM is really fast and stable, thumbs up to MarkVis
Keep the good work!
I've noticed some serious problems after updated to NovaLauncher beta 7. Whatsapp hangs many times during use and system says "low RAM" when I try to send pictures via whatsapp.
I've changed back to beta 5 and still had some hangs and crashes.
I really don't know what's the relation between Nova Launcher and Whatsapp, but I'll try the new GLaDOS v.2.8 to see if I have any changes.
Sent from my Full Android on Crespo using XDA App
Following what was posted on the GLaDOS thread...
http://forum.xda-developers.com/showpost.php?p=20935218&postcount=1843
endursa said:
i recompiled the framework-res.apk with the mentioned bluetooth adapter quick switch set to false and now my deep idle status shows TOP=OFF usage
please be aware that i only tested this file on the OTA 4.0.3 IML74K Rom!
just Flash from recovery!
any other rom on the same base could work with this zip file, but i don't assist in repairing any other roms!
To get the original framework-res file from your Rom back just extract the framework-res.apk file from the original rom zip and replace the one in my uploaded package!
Click to expand...
Click to collapse
I've tried it with various versions of GLaDOS kernel and MV ROMs and it doesn't work, my phone hangs at initialization and keep on an infinite loop.
Also doesn't work with AOSP+ ROM, same infinite loop...
ledzpg said:
Hi,
Since I'm not yet able to post directly into the main thread, I'll post some opinions and experiences here.
The original Thread: http://forum.xda-developers.com/showthread.php?t=1364411
Current setup:
ROM: NEXUS MV 2.12.25
Kernel: GLaDOS 2.5 CFS - 3.0.8
So far, great ROM at all.
No reboots, no crashing apps...
But there are some things a bit annoying:
- On the NSTools, the "backlight dimmer" function only disables the capacitive buttons after the selected time, doesn't change anything in the display (I really don't know if it's a bug or not);
This is the intended functionality, to turn off the capacitive buttons LEDs off, not the backlight/SAMOLED for the whole display
- Most of the times (not always) when I press the button to lock screen, after the animation the screen "flashes" and only after that I hear the "click" sound, but I think it's more a kernel issue than a ROM issue;
Common problem with the brief flash while locking, most people have it and i'd imagine some a bit worse than others. The click and similar sounds on my Nexus S have always lagged to some extent, nothing has changed for me (though i turn all of this off anyway).
- The Assasin's Creed Revelations Game doesn't load the Main Menu completely, only the title appears and I can't select anything. I've reinstalled it and the problem still occurs, but I don't know if it's a ROM problem or some crazy incompatibility.
Lots of apps are still not updated (or won't be updated) for ICS, something which we may have little to no control over. This sounds like one such issue.
And also I'd like to send my suggestions:
- I've used another ROM (wich I really don't remember exactly what was) with a launcher where there was an option to prevent the apps menu to slide into the widgets, it would be nice to have it here too... (don't know if it can be implemented on ROM or only on the Launcher)
Pretty sure some launcher replacement apps can do that, and roms like CM9 alpha probably offer this.
- I miss an option to enable/disable 3G data connection on the top menu of the slider, like CM7.
Extended Controls and Widgetsoid provide this functionality in nearly the same way as CM7/CM9
I can't think on any other thing to add for now...
The ROM is really fast and stable, thumbs up to MarkVis
Keep the good work!
Click to expand...
Click to collapse
ledzpg said:
Following what was posted on the GLaDOS thread...
http://forum.xda-developers.com/showpost.php?p=20935218&postcount=1843
I've tried it with various versions of GLaDOS kernel and MV ROMs and it doesn't work, my phone hangs at initialization and keep on an infinite loop.
Also doesn't work with AOSP+ ROM, same infinite loop...
Guess those ROMs have some modifications which break that stock framework file, the same one works perfectly on my stock ICS. I'm sure the updated file will be added into some ROMs as standard soon.
Click to expand...
Click to collapse
I need to write this because answering within the quotes doesn't contribute to the 10 letter minimum
Harbb said:
I need to write this because answering within the quotes doesn't contribute to the 10 letter minimum
Click to expand...
Click to collapse
Yeah, I've noticed some things of your answer after a good time reading... hehehe
And at some part of the main threads (need to search again), somebody posted about how to end the screen flash after pressing the lock button, I've just didn't tested yet.
But thanks for the reply, I keep reading the threads and testing almost every new ROMs released to see if the deep idle correction is already implemented or not hehehe
That's just a bluetooth fix though, if you turn bluetooth off deepidle should work perfectly fine. This would only really be a problem for you if you use a bluetooth earpiece, headset or car loudspeaker.
I always keep bluetooth and gps disabled unless I need them, but even this way I only got the TOP=ON deep idle, not TOP=OFF.
That's why I was trying that fix
I'm starting to think that's the GTalk's camera thing...
Hello.
I've got a stock Android 3.2.1 (A501 4.066.29 COM GEN1) rooted with Stock/HV/Taboonay V3.7 for HC 3.2 16-10 - 1.64Ghz/UV control kernel.
The question is:
how to set cpufreq parameters (governor, max_freq,..) WITHOUT using 3rd party apps so that the parameters were restored after reboot.
Thank you for reading this.
Either the kernel needs to support init.d scripts or a service needs to execute on boot.
That kernel doesn't support init.d and Voltage Control has a startup service.
CuriousTech said:
Either the kernel needs to support init.d scripts or a service needs to execute on boot.
That kernel doesn't support init.d and Voltage Control has a startup service.
Click to expand...
Click to collapse
Forgive my ignorance but I can't put to use your answer.
I don't get where is Voltage Control and what I have to do.
Get Voltage Control from the market, make adjustments, save as boot. You'll be given the option to save as init.d script or startup service.
Well.. I tested it. Odd app.
First of all it can see only one core. It's funny. After reboot cpu0 works in conservative mode, max_freq 1.4 GHz and cpu1 in ondemand mode, 1.0 GHz.
I tried to edit init.d script and add the 2nd core but after reboot cpu worked with the default kernel values - script didn't work at all.
Moreover Voltage Control shows voltages turned upside down - the less cpu frequency the bigger voltage values. I fear to use this app
Download setcpu or antutu cpu master it recognizes dualcore , has the boot option
More education would be advised To you PLEASE DONT BREAK YOUR TABLET
Please do not take this the wrong way..
it does sound like you do not know what your doing.. I suggest you read more about over clocking./under voltage of a TEGRA 2 DEVICE.. That will get you more understanding about what you need to do. And maybe even help you decide if you really want to do this or not.. There is alot of resources online about this subject. I have tried custom kernel with set cpu.. I use it on my 650 mhz phone. clock it to 768. but it has a huge battry issue when running at that speed.Not to mention It would be dangerous to leave it on my purse with something running might be a fire bug.. GOOD LUCK .
Basically lower voltage at higher frequencies keeps the CPU stable. Leaving it linear would increase temperature exponentially.
Script Manager can run scripts on startup but I don't know how you could disable them if they keep it from starting up.
I didn't know about VC and dual core though. My bad.
ef1x said:
Download setcpu or antutu cpu master it recognizes dualcore , has the boot option
Click to expand...
Click to collapse
Thank you.
I tried all cpu related apps from the Market that I was able to try. Now I want to try to get along without them.
erica_renee said:
Please do not take this the wrong way..
it does sound like you do not know what your doing.. I suggest you read more about over clocking./under voltage of a TEGRA 2 DEVICE.. That will get you more understanding about what you need to do. And maybe even help you decide if you really want to do this or not.. There is alot of resources online about this subject. I have tried custom kernel with set cpu.. I use it on my 650 mhz phone. clock it to 768. but it has a huge battry issue when running at that speed.Not to mention It would be dangerous to leave it on my purse with something running might be a fire bug.. GOOD LUCK .
Click to expand...
Click to collapse
Thank you Erica
I don't understand? You want something that does the same thing but you don't want to know it's there?
I found one app called System Tuner that lets you adjust CPU frequencies individually. I don't know why though.
CuriousTech said:
Script Manager can run scripts on startup but I don't know how you could disable them if they keep it from starting up.
Click to expand...
Click to collapse
Thank you but it looks too bulky for such a small task. And I still don't want to use 3rd party apps
CuriousTech said:
I don't understand? You want something that does the same thing but you don't want to know it's there?
I found one app called System Tuner that lets you adjust CPU frequencies individually. I don't know why though.
Click to expand...
Click to collapse
Actually I don't like how these apps work. And I thought that setting up a few parameters would't be difficult. It seems I was wrong.
Yep. Code has to execute to do stuff, otherwise that stuff doesn't get done.
System Tuner Pro allows voltage adjustments on overclock settings. If you're interested. Also, has a lot of packages integrated into one (task manager, app freezer, etc). They have a free version in the Market if you're interested. It's nice to have several apps, in one nice package.
Moscow Desire
Thank you but I actually don't need it anymore
I have rolled back to the stock kernel because of constant "sleep of death" issue.
huck_d said:
Moscow Desire
Thank you but I actually don't need it anymore
I have rolled back to the stock kernel because of constant "sleep of death" issue.
Click to expand...
Click to collapse
It's because the 3.7 kernel you used, is really not compatible with the a501. The ultra-low voltage causes "screen freeze" and the "sleep of death" when under 3g only. It's a known issue with the 501 and 3.6 and 3.7 kernels also. I would reccommend RTrips 3.4+. Probably his best for for a501.
I ship it with my own Alexandra II and III rom. No issues with it, and none ever reported.
Had I noticed when I woke this morning, you had an a501, I could have given this advice. Sorry, didn't have enough coffee
---------- Post added at 02:21 PM ---------- Previous post was at 02:18 PM ----------
Moscow Desire said:
It's because the 3.7 kernel you used, is really not compatible with the a501. The ultra-low voltage causes "screen freeze" and the "sleep of death" when under 3g only. It's a known issue with the 501 and 3.6 and 3.7 kernels also. I would reccommend RTrips 3.4+. Probably his best for for a501.
I ship it with my own Alexandra II and III rom. No issues with it, and none ever reported.
Had I noticed when I woke this morning, you had an a501, I could have given this advice. Sorry, didn't have enough coffee
Click to expand...
Click to collapse
The problem, is that a lot of dev's, don't have a501's, only a500's. So they really can't test a lot on it. And sometimes, the issue doesn't happen for 2 or 3 days. Sometimes less. I'm going to experiment a little this weekend, with some of the newer kernels, and mess with the voltage's and see if I can get it stabilized where it doesn't freeze on 3g only.
Moscow Desire ,
Thanks for clearing it up and the advise. I'll try either 3.4 kernel or your ROM.
huck_d said:
Moscow Desire ,
Thanks for clearing it up and the advise. I'll try either 3.4 kernel or your ROM.
Click to expand...
Click to collapse
If you go to RichardTrips kernel thread, you will see a link to his older kernels.
You will find the 3.4 listed on his server. I think you just need to flash it, although I usually dump Dalvak cache.
Alex II is an easy install. Alex III (3.2.1) is a little more ... interesting to install, but not difficult. If you run into an issue, post it in my thread. Everybody else has got it installed, so I think you'll have no issues either.
It's the only "certified" 3.2.1 for the Acer a501 that I know if. Not that the other roms are bad, because they really are good, but, the 3.2.1 they advertise, are from system dumps after running an update, or adding missing files to a 500 rom. The TMPL is an Acer release.
In this thread we should share our own little tweaks to this amazing ROM.
I'll add to this first post any stuff that is proven to increase speed or makes using the ROM easier or more enjoyable
Note, this isn't intended to include mods and addons, as there is already a great thread for that
IMPORTANT:
Always backup stuff! And reboot after teaking!
Please note that, the ones I've found more useful, I add a USEFUL tag in front of them
____________________________________
BUILD.PROP tweaks
With root explorer or any other method of your liking, go to /system/ and edit the file build.prop.
- To increase max fps limit possible, add:
Code:
windowsmgr.max_events_per_sec=150
I'm not sure this one is really useful, I think android already sets this already to around 1.5x screen refresh rate. The gains could be negligible.
- Disable error checking, add:
Code:
ro.kernel.android.checkjni=0
- USEFUL Stop debugging icon from appearing in status bar (doesn't disable adb), add:
Code:
persist.adb.notify=0
- USEFUL Force home launcher into memory, add:
Code:
ro.HOME_APP_ADJ=1
_______________________________________________
OTHER TWEAKS AND TRICKS
- VERY, Extremely, Mega-USEFUL - Go to:
Code:
/system/lib/elg
Open egl.cfg and delete the 1st line (0 0 android), reboot the phone.
Everything should be much smoother, I notice this especially opening folders with a lot of icons in Apex Launcher. I think this disables the default android software rendering method and uses only GPU. Don't ask me if this is different than setting composition mode to gpu in build.prop, I don't know, I just know everything is much faster
USEFUL - Only works with Aurora 2.07+ and synaptics screen - Tweak your screen duplicate filter, like in x5settings for .32 kernels.
Go to:
sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity
Open the file "sensitivity" and tweak the value. Default is 4. Higher values reduce screen flickering/jitter but screen can become less sensitive, lower values, the contrary. Personally I use 8, works very good for my fingers, adjust you value accordingly. Note, this takes effect immediately, but doesn't stick after a reboot. To make it stick after a reboot, go to "/system/etc/", open one of the scripts, I recommend "ini.qcom.post_boot.sh", and add this at the end:
Code:
echo 8 > sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity
where 8 is the value you want. Save, reboot and check is the value is there, in the "sensitivity" file.
- USEFUL - Great tips on how to save battery without turning everything off (bonus, doesn't use BS calibration myth):
http://www.androidcentral.com/keeping-your-charge-how-improve-battery-life-your-android-phone
Works AMAZINGLY thank you
Edit1: Also may i ask what CPU settings do you use? any overclocks/governor?
Edit2: I got that funny text glitch just before, i decided to wipe cache and dalvik and i haven't had it again yet. Ill get a screen shot if it happens again but im pretty sure you know what i mean, all the text for apps look like squiggly lines/really odd ive seen this happen normally in previous versions of aurora but oh well ill come back with more info if anything else happens thanks again!
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
spirosbond said:
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Regarding the logcat, yes, probably disables that functionality, I've read in other sites, it just disables checking for errors, thus performance improvements. When I have time, I'll check if logcat is still there... the composition thing I think it tells the OS to always use GPU no matter what, I see a great improvement with that one, don't know if anything is affected, but so far, everything is great
EDIT: these tweaks were from here:
http://forum.xda-developers.com/showthread.php?t=1578065
Sent from my U8800
Here are some more:
http://www.freeyourandroid.com/guide/build-prop-modifications
If you try some, please post results, to add to first post.
spirosbond said:
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Logcat still works
Added synaptics TS setting like there was in X5settings app (Touchscreen Filter).
fjsferreira said:
Added synaptics TS setting like there was in X5settings app (Touchscreen Filter).
Click to expand...
Click to collapse
hi there, i have changed it right now to value 10 and its the same, its trembling...
i have kernel v3 from Dzo 2.0.5 rom.
and have restart the phone too
r1c4rd0 said:
hi there, i have changed it right now to value 10 and its the same, its trembling...
i have kernel v3 from Dzo 2.0.5 rom.
and have restart the phone too
Click to expand...
Click to collapse
Yes, I think so, maybe it was just placebo... also, it doesn't stick after a reboot, the ROM would need init.d startup script support and a script to change the value everytime... try change it to 40 or something, and report, it it still trembles, I'll remove from the first post...
fjsferreira said:
Yes, I think so, maybe it was just placebo... also, it doesn't stick after a reboot, the ROM would need init.d startup script support and a script to change the value everytime... try change it to 40 or something, and report, it it still trembles, I'll remove from the first post...
Click to expand...
Click to collapse
will try it right now
edit: changed the value and no diference... then i restart and no diference too...
I think it doesn't work... I've changed it to 1 and notice no difference... I'll remove that thing from front post and post here if anyone wants to study it...
- Something to try, it seems not to work... - Improve synaptics screen sensitivity!
Do you miss x5Settings setting about touchscreen filter? I've been studying x5settings source code and found out what file needs to be changed to achieve the same result in Aurora. Go to:
- sys/module/synaptics_i2c_rmi_1564/parameters/
Edit the file "sensitivity" and set a value appropriate for you. I've set it to 8 and touchscreen seems better now. Maximum value I think is 64, and that works great too. I think this isn't placebo Pinch to zoom in pics doesn't "tremble" when holding the fingers on the screen as it did before, here.
EDIT: it doesn't stick after a reboot! And values change by itself, don't know why, maybe it doesn't even work... Try it for your self
fjsferreira said:
- Something to try, it seems not to work... - Improve synaptics screen sensitivity!
Do you miss x5Settings setting about touchscreen filter? I've been studying x5settings source code and found out what file needs to be changed to achieve the same result in Aurora. Go to:
- sys/module/synaptics_i2c_rmi_1564/parameters/
Edit the file "sensitivity" and set a value appropriate for you. I've set it to 8 and touchscreen seems better now. Maximum value I think is 64, and that works great too. I think this isn't placebo Pinch to zoom in pics doesn't "tremble" when holding the fingers on the screen as it did before, here.
EDIT: it doesn't stick after a reboot! And values change by itself, don't know why, maybe it doesn't even work... Try it for your self
Click to expand...
Click to collapse
hey fjsferreira if you want stick after a reboot, you must to paste this command "echo 8 > /sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity" (without the quotes) into 1 of the files in /etc/init.d
number 8 is choise by us... but make 8 for this example
r1c4rd0 said:
hey fjsferreira if you want stick after a reboot, you must to paste this command "echo 8 > /sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity" (without the quotes) into 1 of the files in /etc/init.d
number 8 is choise by us... but make 8 for this example
Click to expand...
Click to collapse
The problem is, there isn't an /etc/init.d :S maybe it can be added to one of the scripts in /etc/
fjsferreira said:
The problem is, there isn't an /etc/init.d :S maybe it can be added to one of the scripts in /etc/
Click to expand...
Click to collapse
yes it can...
r1c4rd0 said:
yes it can...
Click to expand...
Click to collapse
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
fjsferreira said:
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
Click to expand...
Click to collapse
yes it works, but i think its related to his new v3.0 kernel...
in .35 kernel, if i´m not worng, we can change that value.
i think placebo dont work with me lol
fjsferreira said:
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
Click to expand...
Click to collapse
I tried 8 and 10 but the flickering didn't reduce. Thanks for the tip though. I hope you get it working...
Question:
What is the difference between the mod:" get rid of cpu composition" and setting the line
debug.composition.type=gpu
at build.prop?
By making the above change doolde jump graphics where improved
Cheers
You have ro.HOME_APP_ADJ=0 to force the launcher into the memory, but wouldn't the right value be 1?
FlashTH said:
You have ro.HOME_APP_ADJ=0 to force the launcher into the memory, but wouldn't the right value be 1?
Click to expand...
Click to collapse
Correct. I've fixed it, thank you!
Sent from my U8800
i dont know if you notice, but wen the phone is charging touchscreen feels more jumpy...
can anyone confirm this?
maybe this will interest dzo in the ics port? in this site there are the amtel and synaptics drivers:
port ics input drivers
drivers from HTC Legend touch the same as desire:
drivers synaptics from htc
thanks
So a while ago I discussed with my friend rohit joshi (developer of tegra overclock) about a system file called adj, and how it may be responsible for sometimes disturbing ram behaviour. It couldn't be adjusted AFAIK on 4.1, but it seems to allow modification on 4.3.
1: Mount system R/W
2: Open /sys/module/lowmemorykiller/parameters/and open the file named adj
3: Change it to the following: 0,10,25,50,80,150 and save the file
Now please observe ram management in intense situations such as using chrome or heavy games, so far I have noticed no irrational behavior like asphalt 8 committing suicide etc, but its early days and we need more data. Custom values are welcome but please mention what you used
Note: These values reset upon reboot
Sent while my supervisor wasn't looking
Great,work on eXistenZ 2.1.5!
Before:429MB ram free
After:563MB ram free!
On stock without this mod i have 429mb free LOl
I think Supercharger solve those problems this way for two years now.
Hmm this isn't really it's purpose, also these values fluctuate on their own btw . It's supposed to stop foreground processes and other important stuff from getting killed in low memory situations, for example once my alarm stopped responding because I was busy extracting a zip file. This fix is for this kind of wierdness
Sent while my supervisor wasn't looking
asphalt 8 close by itself if i play tokyo track.. on other track game works nicely
@non4 said:
3: Change it to the following: 0,10,25,50,80,150 and save the file
Click to expand...
Click to collapse
Could you explain more what these values are...
is it oom_adj parameters
and why changing them so drastically?
Default values are 0,58,117,235,529,1000
Shouldn't we try first minfree parameters which are also IMHO odd...
15000,17532,20065,22598,25131,30263 which equals (Nx4/1024)
58.6 68.5 78.4 88.3 98.2 118.2 Megabytes
I change mine to 8192,16384,18432,24576,32768,65536 or 32,64,72,96,128,256 Mb
so far so good... will see over a longer period of time... :silly:
freedom74 said:
Could you explain more what these values are...
is it oom_adj parameters
and why changing them so drastically?
Default values are 0,58,117,235,529,1000
Shouldn't we try first minfree parameters which are also IMHO odd...
15000,17532,20065,22598,25131,30263 which equals (Nx4/1024)
58.6 68.5 78.4 88.3 98.2 118.2 Megabytes
I change mine to 8192,16384,18432,24576,32768,65536 or 32,64,72,96,128,256 Mb
so far so good... will se over a longer period of time... :silly:
Click to expand...
Click to collapse
I changed them this way simply based on advice given, as I say different values are welcome I don't fully understand it myself however what I know is it seems to be working. I have been told that newer snapdragon devices have different adjacent values to other phones. This causes apps that SHOULD be closed to instead not be closed and so the system resorts to closing your fave game or whatever. Adjacent and minfrees have a relationship but I'm not sure exactly how it works, will try and find some better info on it
Sent while my supervisor wasn't looking
poran123 said:
asphalt 8 close by itself if i play tokyo track.. on other track game works nicely
Click to expand...
Click to collapse
Hmm just spotted your comment there, I've been running Tokyo fine on high graphics, have you done anything else to the ram like change the minfrees? Feel free to play around with these values and report if you have any luck
Sent while my supervisor wasn't looking
@non4 said:
Hmm just spotted your comment there, I've been running Tokyo fine on high graphics, have you done anything else to the ram like change the minfrees? Feel free to play around with these values and report if you have any luck
Sent while my supervisor wasn't looking
Click to expand...
Click to collapse
i didnt change anything only did what is written on the op....
poran123 said:
i didnt change anything only did what is written on the op....
Click to expand...
Click to collapse
Lol, I just got the dreaded home crash! Will continue to experiment, it makes no sense how bad it is, I just ran this game on high graphics on a galaxy s2 and homescreen didn't even redraw when I was done!
I found some info on this driver here:
https://android.googlesource.com/ke...4ac/drivers/staging/android/lowmemorykiller.c
It might actually be worth trying higher values instead of lower ones from what I'm reading here
Sent while my supervisor wasn't looking
How is it going with adj settings?
According to http://forum.xda-developers.com/showpost.php?p=5442369&nocache=1&z=6948587024309106
adj values determines how apps will be killed in case of Out Of Memory situations
Numbers are, similar to minfree settings connected to
ForegroundAPP, VisibleAPP, SecondaryServer, HiddenAPP, ContentProvider, EmptyAPP and hence the numbers
0,58,117,235,529,1000
The higher number, more probably the process will bi killed.
You can say "if free memory goes below XXXX then kill some process with oom_adj greater then YYY; if free memory goes even more below than ZZZ then start to kill some processes with oom_adj greater than XYXY. and so on.."
Click to expand...
Click to collapse
So, values 0,10,25,50,80,150 for adj
will give results but also kills too many processes, maybe some important ones.
Maybe someone that have expeirience with linux kernels can answer the question:
Who sets oom_adj parameter of a process?
IMHO, by setting these adj values, you tell system to treat all processes with oom_adj higher than 150 like EMPTY_APP
Will try changing adj settings but perhaps with some less agressive parameters... let's say half of the original
0,25,50,100,250,500
someone told that actually sony latest framework that eat ram.. not by apps/bloatware.. which mean even though we kill foreground app.. it will load more cpu after that.. will raise more probs such as lags n battery drain.. but simply for playing heavy games i think it works..
sony knows this issue... maybe they will fix it in the next update.. maybe
I've been playing around and conclude that this works somewhat but you must lower your minfrees too for maximum effect, not sure what the best combination of values is just yet, seems lower = better, but too low may cause lag as ram fills up. One more thing is I noticed sometimes adj changes it's values back, perhaps if it considers them invalid as it only happens with certain values I tried
Sent while my supervisor wasn't looking
danielhariri said:
sony knows this issue... maybe they will fix it in the next update.. maybe
Click to expand...
Click to collapse
Is there a place to report a bug?
Yes I know they are aware of the issue but if more people report a bug, greater is the chance that they release a patch.
hi
i Change it to the following: 0,10,25,50,80,150 and save the file but When it was reset phone, Has not changed ... whay ?
/sys is not a real directory
It's a virtual file system so everything you change vanishes after reboot.
If you have some settings other than defaults you want to put into /sys you can do it via init.d scripts during the boot time.
Sent from my C5303 using xda app-developers app
freedom74 said:
/sys is not a real directory
It's a virtual file system so everything you change vanishes after reboot.
If you have some settings other than defaults you want to put into /sys you can do it via init.d scripts during the boot time.
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
Catch !! sorry
I just did that? 0,58,117,235,529,1000 After rebooting Can not be changed? not changed!!
Well, I said if you want your values get inserted automatically you need init.d script.
But since these values we talk about here are still unconfirmed and for testing I think it's better to stick with manual entering rather than automatic.
What I do is that I typed as SU in command prompt using Android Terminal app a command
echo "0,10,25,50,80,150“ > /sys/module/lowmemorykiller/parameter/adj
Same for minfree settings
Sent from my C5303 using xda app-developers app
freedom74 said:
Well, I said if you want your values get inserted automatically you need init.d script.
But since these values we talk about here are still unconfirmed and for testing I think it's better to stick with manual entering rather than automatic.
What I do is that I typed as SU in command prompt using Android Terminal app a command
echo "0,10,25,50,80,150“ > /sys/module/lowmemorykiller/parameter/adj
Same for minfree settings
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
And for init.d
#! /system/bin/sh
echo "0,10,25,50,80,150“ > /sys/module/lowmemorykiller/parameter/adj
Sent while my supervisor wasn't looking