Database Users

Smoother Scrolling on the Eris

edit: Most devs have added this to their roms already so don't be surprised if you find it in the build.prop already.
So I saw this mentioned in a tweet by the dev for Launcher Pro:
To get really nice smooth scrolling on your Eris add the following line to your build.prop:
Code:
windowsmgr.max_events_per_sec=60
To add it into your build.prop follow these steps using your adb tool:
Code:
adb remount
adb pull /system/build.prop
(Go into your tools folder and open it with notepad. Add the line I posted and save.)
Code:
adb push build.prop /system/build.prop
Reboot into recovery, wipe dalvik cache, and start the phone up. This can a while to boot up right after because of the wiping dalvik cache. You should notice that scrolling on your phone is much smoother.
I AM NOT RESPONSIBLE FOR YOUR PHONE. IF YOU BREAK YOUR PHONE DOING THIS (it's unlikely!) I AM SORRY BUT I CAN'T HELP YOU.
I currently have mine set to 70 and it's not any noticeably smoother than 60 that I can tell but it is stable so if anyone wants to try bumping it up to 90 or 120 feel free.

Thanks for the advice last night on this Hungry Man. I did this and notice a definite difference in the scrolling. I moved my Launcher pro scrolling speed down now from 100 to 45 because I no longer need it high with this fix. I also didn't wipe Davlik after pushing, but the file is in there when looking with Estrong file manager and the scrolling is definitely better now..
Thanks again..

Glad I could help! Wiping the Dalvik cache isn't really necessary I suppose, I just find it's good practice after doing anything to your build.prop to avoid possible glitches.

any reason why this wouldnt work on other devices?

Where exactly do I add this line? Thanks.

dev/null/ said:
Where exactly do I add this line? Thanks.
Click to expand...
Click to collapse
Just add it to the end of build.prop file.

Worked, I thank you for the reply and to the OP for the info.

Twidroyd
Could I get someone to fire up Twidroyd after applying this patch? Seems to cause super-heavy lag+slowdown in scrolling, but it appears that Twidroyd is the main offender.

This seems to work just fine for me. I guess it seems smoother... I can't really tell. Definitely not laggier.

Wouldn't you be able to open the build prop in something like Root Explorer's text editor and get the same result? I'm just not around my regular computer with adb setup... Thanks.

es0tericcha0s said:
Wouldn't you be able to open the build prop in something like Root Explorer's text editor and get the same result? I'm just not around my regular computer with adb setup... Thanks.
Click to expand...
Click to collapse
yes you can do this also.
Sent from my FroyoEris using XDA App

Implemented this tweak in my latest ROM and it definitely makes a difference
Sent from my nonsensikal froyo

I tried obtaining access through Root Explorer and it says that build.prop is read only?

drtchocky said:
I tried obtaining access through Root Explorer and it says that build.prop is read only?
Click to expand...
Click to collapse
You have to remember to make the directory R/W at the top of the screen.

Can't really tell if it made a difference. Has anyone experimented with setting the number even higher?
EDIT: Upon further review, it seems to have made my scrolling slightly smoother but also more likely to 'hitch'

Yeah, I think this is what I was seeing in Twidroyd. Scrolling is smoother in a list you've already scrolled through, but will stutter as it loads new table cells (a guess on my part, but it seems to make sense.)

Izeltokatl said:
You have to remember to make the directory R/W at the top of the screen.
Click to expand...
Click to collapse
Thanks! Rebooting now....

I think it's likely that if you aren't overclocking your phone may not be able to handle the extra load. If you aren't overclocking your phone or you're usually on a low cpu setting try chaing to 50. Anything above 35 will increase the smoothness, though not to the same extent. I don't suggest passing 60, I'm at 70 and the differences are negligable.
As for the lag and stutters, I haven't experienced that.

I did it. Didn't break anything, but didn't really seem to change anything either.

I have seen a huge difference in smoothness in screen scrolling as well as app drawer. I have large amt of apps and app drawer flies. One thing though I do not have a space before or after the equal sign on my line. Some of you who aren't seeing a huge difference take the spaces out and see if anything changes.

00Ring_Lag_v2. Updated 09/26/2011

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

franco.kernel ksatta changes pre-release

I will release my changes to the franco.kernel in this thread before franco includes them in his kernel for the upcoming releases. So this is a "pre-release" thread for franco.kernel, for the changes I'm making.
v2 (included in [16 SEP] franco.Kernel)
- Speakerphone echo fixed. Works with normal calls, not with Skype (or other voip apps probably). Skype still works like before, echo with speakerphone mode.
The fix can be disabled with
Code:
echo 0 > /sys/module/snd_soc_msm7kv2/parameters/speakerphone_echo_fix
You can post in this thread how it works. It always uses speaker_mono_tx instead of speaker dual mic broadside dev.
- Removed some logging from msm7x30.c (left there by Huawei. They must have a logging fetish or something )
mod_v1 (Included in [11 SEP] franco.Kernel)
- "Use phone's mic with headset"-feature is now user configurable.
By default uses phone's mic with headset/headphones/line-out. So if you want that, no configuration is needed.
To use headset's mic create a file called "10headsetswitch" in "/system/etc/init.d/" and paste the following to it:
"echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch"
Future plans
- Fix speakerphone echo in Skype. Investigate the volume problems (max. volume is too high, etc..).
Flashing instructions
- Boot to recovery
- install from zip
- choose francokernel_X_ksatta_vX.zip.
Notes for devs
The latest franco.kernel has logcat disabled by default, to enable it put this in .config:
Code:
CONFIG_ANDROID_LOGGER=y
To enable kernel debug messages (can be seen with dmesg):
Code:
git checkout 0c1adc36ed u8800-kernel/kernel/printk.c
NOTE: disable logging again before releasing anything, probably slows down the phone quite a bit when logging is on.
Credits
ksatta - use phone's mic with headset
stockwell - user config for headset mic setting
franciscofranco - the franco.kernel
Thanks
wmi543
genokolar
And everyone else if I forgot to mention someone.
Files
franco.kernel-sep11+ksatta_v2.zip - Zip file to flash phone.
franco.kernel-sep11+ksatta_v2-src.zip - V2 source for devs. msm7x30.c file is from u8800-kernel/sound/soc/msm. Also includes compiling instructions.

To make it set to using the phone mic at boot, save the following script into /system/etc/init.d/. Call it whatever you like just with a two digit number at the start (ie. 10headsetswitch)
Code:
echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch
As mentioned this is already configurable in Miui using x5 settings so you don't need to worry about making the script yourself but the voice quality might not be very good (will be fixed for the next version) unless you use the kernel attached from ksatta.

Please could explain how to install this kernel? Because I read the file that you have attache and in the end I finish like in the begginign without knowing how to do it.
Is only need to do by the recovery with the zip file ans what about the secund zip file the smaller one?
Sorry but Ian sure that I am not the only o w that is asking this.
Sent from my u8800 using XDA App

vlc_marcos said:
Please could explain how to install this kernel? Because I read the file that you have attache and in the end I finish like in the begginign without knowing how to do it.
Is only need to do by the recovery with the zip file ans what about the secund zip file the smaller one?
Sorry but Ian sure that I am not the only o w that is asking this.
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Yeah I was a bit unclear, sorry. To flash boot to recovery, install from zip and choose my zip.
edit: Updated first post, flashing instructions

ksatta said:
Yeah I was a bit unclear, sorry. To flash boot to recovery, install from zip and choose my zip.
Click to expand...
Click to collapse
Ok thanks. And for what is the small zip file?
So I will use in this last miui without any problems correct.
Will I get battery problems?
Sent from my u8800 using XDA App

vlc_marcos said:
Ok thanks. And for what is the small zip file?
So I will use in this last miui without any problems correct.
Will I get battery problems?
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Sigh man, I'm growing tired of your questions everywhere in every thread you can find. This is just my kernel compiled with a different file to make this "Use phone's mic with headset"-feature is now user configurable." avaliable.
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Sorry for the smallish OT ksatta, it ****s me reading stupid questions everywhere.
Very nice job like I told you before

franciscofranco said:
Sigh man, I'm growing tired of your questions everywhere in every thread you can find. This is just my kernel compiled with a different file to make this "Use phone's mic with headset"-feature is now user configurable." avaliable.
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Sorry for the smallish OT ksatta, it ****s me reading stupid questions everywhere.
Very nice job like I told you before
Click to expand...
Click to collapse
First of all Ian not from your family so stupidity is not in my genes. Secund if you are tired go to sleep.
I didn't ask to you, so you don't need to react like this. Don't be a small kid.
When I don't know I ask.
So Franco don't give me your ****y opinions when I don't ask for then.
Thanks
Sent from my u8800 using XDA App

franciscofranco said:
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Click to expand...
Click to collapse
I think it's a fair question, I was wondering why my phone wasn't making me coffee
vlc_marcos said:
Ok thanks. And for what is the small zip file?
So I will use in this last miui without any problems correct.
Will I get battery problems?
Click to expand...
Click to collapse
You can already do this in Miui, have been able to for a while. Flashing this version should make the voice quality better though.

Yeah, like franco said, the v1 is just user-configurability for the headset mic thing.
For anyone else wondering, I will report any changes I make in the first post. So the zips here won't have any other changes compared to franco.kernel, except the ones I report in the first post.

vlc_marcos said:
Ok thanks. And for what is the small zip file?
Click to expand...
Click to collapse
I updated the first post to be less confusing. the smaller file is only the source file, only needed by devs.

franciscofranco said:
Sigh man, I'm growing tired of your questions everywhere in every thread you can find. This is just my kernel compiled with a different file to make this "Use phone's mic with headset"-feature is now user configurable." avaliable.
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Sorry for the smallish OT ksatta, it ****s me reading stupid questions everywhere.
Very nice job like I told you before
Click to expand...
Click to collapse
Mate, you seriously need to get a grip and settle down. Maybe lay off the espresso a bit. I know you are doing good things with your kernel and everyone appreciates that and is grateful. However, almost every post you make is aggressive and condescending. Ok so you have it all figured out, that's great. But the majority of us are just struggling and muddling along enjoying Android and trying to learn and contribute as we go. When you attack and belittle most posters it just make you look like a wanker.
May I suggest: if you don't wish to assist then simply don't respond. Someone else will or maybe no one will in which case the post will recede into the past and the poster will look elsewhere.

Maybe you, or anybody here can write me pm with very short info how to compile kernel [what parrameters should pass to it] and make zip package to be installable to phone? Once i tried to compile but image was 2x times bigger than original realese so i was afraid to test it
GolfCranK said:
Mate, you seriously need to get a grip and settle down. Maybe lay off the espresso a bit....
Click to expand...
Click to collapse
it's PASSION man! Who wants to read nice post i want to read **** words man!

Tommixoft said:
Maybe you, or anybody here can write me pm with very short info how to compile kernel [what parrameters should pass to it] and make zip package to be installable to phone? Once i tried to compile but image was 2x times bigger than original realese so i was afraid to test it
Click to expand...
Click to collapse
Maybe you were looking at the uncompressed Image file? zImage is the correct file. But anyway the -src.zip contains compiling instructions, I created them today with a fresh install of Ubuntu 11.04. If you test my instructions and have any problems, inform me and I'll update the instructions.
Before you edited you asked about what v1 does, there's a whole lot of text in the first post, but yes, it only makes the headset mic switch user-configurable Future releases might have more changes

Actually my version uses phone's mic by default. I made it default because franco.kernel has been using phone's mic by default. So, to avoid confusion:
If you want to use headset's mic use "echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch" in the script.
If you want to use phone's mic, don't do anything
edit: This applies to the v1 kernel in this thread, miui uses headset's mic by default. Reason above.

Man, this kernel fixed the only issue I had with Oxygen, and call quality is even great! Now I won't change ROMS ever in the next months (unless Huawei releases official Gingerbread). I'm not gay but this is true, I LOVE YOU!!!!

ksatta said:
Maybe you were looking at the uncompressed Image file? zImage is the correct file. But anyway the -src.zip contains compiling instructions, I created them today with a fresh install of Ubuntu 11.04. If you test my instructions and have any problems, inform me and I'll update the instructions.
Before you edited you asked about what v1 does, there's a whole lot of text in the first post, but yes, it only makes the headset mic switch user-configurable Future releases might have more changes
Click to expand...
Click to collapse
MAN! Thanks! finally someone wrote how to properly compile. THANKS!! You're awesome

ksatta said:
Actually my version uses phone's mic by default. I made it default because franco.kernel has been using phone's mic by default. So, to avoid confusion:
If you want to use headset's mic use "echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch" in the script.
If you want to use phone's mic, don't do anything
edit: This applies to the v1 kernel in this thread, miui uses headset's mic by default. Reason above.
Click to expand...
Click to collapse
lol sorry I edited it now.

My theory about the speakerphone echo is that the audiolibs in 2.3 roms use the wrong routing. They're probably now using the same microphone dev. id. as normal mode, when they should be using the "speakerphone mic" dev.id.
I wasn't able to confirm this yet, didn't get my debug messages out of the kernel yet Normal logcat works, but the kernel debug messages don't show up in it. Also I couldn't find a syslog file.
But I'll continue another day.

Ksatta i see you good with freaking linux stuff and sound So can you make that recording audio and video - audio quality to be good not some arm ****?
I found that codec is here arch/arm/mach-msm/qdsp5v2/audio_amrnb.c How to make that system uses different codec or this but with better sample rate ant bit rate, i can change this in file but i can't find the specification of this codec so maybe it's not supporting 44.1Khz sample rate or even 16Khz.

Thanks ksatta for this ! Was exactly what needed. Btw instead of setting that init script couldn't just change the value from 1 to 0 or it is restored after every reboot?

[Mod][MotoActv] Tweaks+Mods Pack!

ive gathered some things and did a few tests on my MotoActv since ive gotten it and did some tweaks here and there and i added the following features to mine and put them into a flashable zip for u all
-init.d support (plus some scripts to make it faster then ever) (tested and working (makes two files in sdcard on boot to show it) (picks and chooses when to work now for some reason, so i put an app i made that loads scripts when onCreate()'d and sometimes on-boot)
-Viper4Android sound system (only works for bluetooth headsets if enabled, but its sounds better with good settings)(see credits)
-OpenVPN (idk if theres a use for us but i added the required files (no GUI)
-UsbEnabler.apk (see credits)
-Adblock host (hopefully it works i havent been able to test yet)
-lag-free entropy (so far seems to work, as im not lagging switching launchers anymore)
-MotoActv DPI (my own personall app i made for Changing dpi from 90,100, and stock(120)
-Sqlite3 + init.d sqlite3 optimizer
-Busybox Run-parts (for init.d, still picks and chooses when to work)
-100 Dpi When-Flashed (can be changed back to stock with the MotoActv DPI app i made)
-minor-to-major tweaks from init.d scripts and other methods
-DalvikCache2Sd (not sure if it truly tested working, but i do have a tiny bit more space+no lag like other 2SD methods
soon to be added:
I take bare minimum credit for these, i mostly used this personal zip for when i update my MotoActv's rom, this can be universal for other androids, but it was initially made to the MotoActv watch running custom roms
Credits to give:
(will edit when i get forum post urls and OP's names)
Viper4Android:
OP = @zhuhang
Thread = http://forum.xda-developers.com/showthread.php?t=2191223
UsbEnabler:
OP = @fagalto
Thread = http://forum.xda-developers.com/showthread.php?t=2396138
init.d scripts, OpenVpn, Entropy:
i extracted from the rom on my phone so idk where they originally came from
Init.d App(unreleased w/o mod_pack)+MotoActv DPI:
OP:me @jkok for developing and publishing
Thread (MotoActv DPI):
http://forum.xda-developers.com/showthread.php?t=2435370
Gallery+Live Wallapapers:
Google, But @ClearD for giving me the zip with the script+apks
the zip:
i put together, made the script, signed+released for general use for others:
future credits will be made when i add more things.
Download:
Reusable Download Link

Awesome!
Here's a zip (with changed mounting, again; this time using the exact same one that I use for the rom) of the Live Wallpapers + Gallery apks. Hopefully, this one will work fine.

ClearD said:
Awesome!
Here's a zip (with changed mounting, again; this time using the exact same one that I use for the rom) of the Live Wallpapers + Gallery apks. Hopefully, this one will work fine.
Click to expand...
Click to collapse
well thanks ClearD i can do the script just fine, some of the mountpoints are universal like what i use
umount("/system");
or
run_program("xbin/mount", "/system"); (might be wrong on the xbin part, just going by memory
run_program("xbin/umount", "/system");
but the resolution on the galery on your motoactv rom is too big for it, it resizes dont get me wrong, but it needs to do a single horizontal row cause if u overscroll to the farest right u see there is second or more rows going down, imma fine the sourcecode for the galery2.apk, and make a single-row version when i find it =)

jkok said:
well thanks ClearD i can do the script just fine, some of the mountpoints are universal like what i use
umount("/system");
or
run_program("xbin/mount", "/system"); (might be wrong on the xbin part, just going by memory
run_program("xbin/umount", "/system");
but the resolution on the galery on your motoactv rom is too big for it, it resizes dont get me wrong, but it needs to do a single horizontal row cause if u overscroll to the farest right u see there is second or more rows going down, imma fine the sourcecode for the galery2.apk, and make a single-row version when i find it =)
Click to expand...
Click to collapse
Ah, sweet! That sounds good. I couldn't get it to mount properly any other way so far, but it could have been something as simple as a typo. If it does actually work, then I might use that in the future. That's the one I tried with the last iteration.

ClearD said:
Ah, sweet! That sounds good. I couldn't get it to mount properly any other way so far, but it could have been something as simple as a typo. If it does actually work, then I might use that in the future.
Click to expand...
Click to collapse
the universal way i do my scripts is
mount("ext3", "MTD", "system", "/system");
unmount("/system");
and it always seemed to work for me, so thats why i call it universal anyways
but the other ways i posted seemed to work for me when i tried em, i just used this way cause it was in a zip for a motoactv rom (i think it was yours or the battery mod)

Opps! i was wrong, its not
run_program("xbin/mount", "system");
its
run_program("sbin/mount", "system");
lol i had to check my other mod zips lol

jkok said:
the universal way i do my scripts is
mount("ext3", "MTD", "system", "/system");
unmount("/system");
and it always seemed to work for me, so thats why i call it universal anyways
but the other ways i posted seemed to work for me when i tried em, i just used this way cause it was in a zip for a motoactv rom (i think it was yours or the battery mod)
Click to expand...
Click to collapse
Lol no doubt, I went through the same thing with the battery mod, looking over and over for one that worked better. I'd prefer the xbin/mount method, but for some reason, it was hit and miss on my end with end users. Not sure why, unless busybox wasn't set up right somehow.

Just updated the mod_pack with more features!
Sorry but the only thing i havent really been able to fix that well way the init.d it seemed to workwhen i first released this mod_pack, but it seems to pick+choose when to work, so i added 2 other methods for init.d (one of which is an app i made, yet to release that loads the scripts when the app is onCreate()'d and sometimes on-boot when SuperUser allows it)
but there are some great new features that WILL work, along with some of my own personall apps, tweaks, and clock faces =)
Again: this mod_pack is meant for MotoActv's running a custom rom, and Not meant for AOSP based MotoActv Roms
Tested and confirmed working (except init.d that picks and chooses) on @ClearD 's ClearRom 1.2.0 T2 (and my own personal (un)Official 1.2.1 T1 i made for him)

For some reason all of the mods are being denied superuser, any ideas? I am setup to automatically allow all requests
Edit: Installed SuperSU and my problem has been resolved

Has there been anything definitive about the entropy thing? The last consensus I saw by anyone not potentially making money from a fix is that at best it's just forcing the processor to stay awake, decreasing battery life.

Saeviomage said:
Has there been anything definitive about the entropy thing? The last consensus I saw by anyone not potentially making money from a fix is that at best it's just forcing the processor to stay awake, decreasing battery life.
Click to expand...
Click to collapse
well by my testing before my motoactv went kaput it didnt affect the battery any noticeable amount, but it did solve some-to-all of the lag from switching launchers on the ClearDroid 1.2.0_T2 rom, i cannot make or update this mod-pack anymore because i dont like submitting a mod-pack that is untested, and since my motoactv went kaput i cannot test it anymore but if u have any questions feel free to ask and ill try to answer the best i can for now =)

not sure what is the right place to ask this... How does DPI change work? Does it mean the "system" screen resolution is changed? Let say, what is the "Full Screen" resolutions in 90/100/stock(120?) dpi's??? Where to read about it if it is not so simple???

yuiop0 said:
not sure what is the right place to ask this... How does DPI change work? Does it mean the "system" screen resolution is changed? Let say, what is the "Full Screen" resolutions in 90/100/stock(120?) dpi's??? Where to read about it if it is not so simple???
Click to expand...
Click to collapse
Dont worry its ok to ask here, since i made this app after all , i might as well answer how this works =)
well to make it shorter and more understandable to alot more people:
Yes, it is the overall resolution of the screen:
DPI (dots-per-inch) is more like the size range to view images/displays/graphics on ANY of your LCD/LED Screened devices including androids, I-craps(iPhones/ipods )(sorry i dont like apple too much, bad excperiences, dont get offended if u like it as its just my personal preferences), blackberries, windows phones, TV's, computer Monitors, etc:
the stock setting for HDPI phones (the more common screened ones now) is 240, say if u lower it, the images get smaller, if u raise it it gets bigger (maybe even too big for the screen to handle correctly);
but since the MOTOACTV has a smaller screen as u can obviously see (if u have one that is, as i dont know others posesions =P), its default for the stock rom is 120 (1/2 of HDPI if u notice the math) and 120 is as big as it should go cause say for example 130 dpi, it makes the images slightly too big for the screen, but slightly smaller values (100 is usually smallest for alot of peoples eyes for the watch, but for some people like me that like them a tad smaller for sharp small details, i put 90), but literally the smaller the amounts go, the smaller the images(and possible errors, i.e ES File Explorer crashes below 120 DPI untill u restore to 120+) , and for the smaller screen we have u cant go too big (121+), or too small (>=90-100), so i put those details of 90,100,and 120 (no 110 as it doesnt make too much of a difference by what i saw)
but there is (a) way(s) to check what DPI u are at currently:
METHOD1.check your build.prop file under /system/build.prop by doin these ADB commands (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb pull /system/build.prop
<EOC>
check somewhere using notepad for this line (NOTE: if u want to edit to push to your device use notepad++, search for it on google if u dont already have it, as regular notepad corrupts it)
ro.sf.lcd_density=(your current DPI is displayed here)
if u decide to change it that way and want to apply it MAKE A BACKUP!!!, then change it in notepad++ and save it, then goto the directory it is in in the terminal/command prompt and do (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb push build.prop /system/build.prop
adb shell chmod 644 /system/app/build.prop
adb reboot
<EOC>
METHOD 2: Any DPI Checking/changer app (there might be some good free ones, i.e. pimpmyrom has a density changer (DPI changer) that works the same as mine i think, it changes the DPI value in the Build.prop and it WILL stick over reboots, just not rom flashes (as it overwrites it and my change)
if u want to see how i did this(if u understand java/android applications) u can check This app on my github, its acually fairly easy and lightweight compared to others
https://github.com/kittleapps/MotoActvDPI
and the exact class that does this (using a library), is this
https://github.com/kittleapps/MotoA...om/KittleApps/app/motoactvdpi/MainScreen.java
as u can see it changes it to 90,100, and 120 quite simply (with root access of course)
and sorry for this long message but it explains not only your question, but possible future questions on how this app works =)

jkok said:
but there is (a) way(s) to check what DPI u are at currently:
METHOD1.check your build.prop file under /system/build.prop by doin these ADB commands (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb pull /system/build.prop
<EOC>
check somewhere using notepad for this line (NOTE: if u want to edit to push to your device use notepad++, search for it on google if u dont already have it, as regular notepad corrupts it)
ro.sf.lcd_density=(your current DPI is displayed here)
if u decide to change it that way and want to apply it MAKE A BACKUP!!!, then change it in notepad++ and save it, then goto the directory it is in in the terminal/command prompt and do (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb push build.prop /system/build.prop
adb shell chmod 644 /system/app/build.prop
adb reboot
<EOC>
METHOD 2: Any DPI Checking/changer app (there might be some good free ones, i.e. pimpmyrom has a density changer (DPI changer) that works the same as mine i think, it changes the DPI value in the Build.prop and it WILL stick over reboots, just not rom flashes (as it overwrites it and my change)
if u want to see how i did this(if u understand java/android applications) u can check This app on my github, its acually fairly easy and lightweight compared to others
https://github.com/kittleapps/MotoActvDPI
and the exact class that does this (using a library), is this
https://github.com/kittleapps/MotoA...om/KittleApps/app/motoactvdpi/MainScreen.java
as u can see it changes it to 90,100, and 120 quite simply (with root access of course)
and sorry for this long message but it explains not only your question, but possible future questions on how this app works =)
Click to expand...
Click to collapse
There is a 3rd method as well.
Method 3 = Install the Xposed framework and app settings apk found here: http://forum.xda-developers.com/showpost.php?p=44034334&postcount=2315
This will allow per app DPI settings rather than one global setting.
In order for this to work correctly, make sure you move both the Xposed Installer and App Settings apks to the phone after installation and reboot as well.
I like running some apps at 120, others at 100, 90, and even 70 w/ modded font sizes and this allows for all those combinations.

Artimis said:
There is a 3rd method as well.
Method 3 = Install the Xposed framework and app settings apk found here: http://forum.xda-developers.com/showpost.php?p=44034334&postcount=2315
This will allow per app DPI settings rather than one global setting.
In order for this to work correctly, make sure you move both the Xposed Installer and App Settings apks to the phone after installation and reboot as well.
I like running some apps at 120, others at 100, 90, and even 70 w/ modded font sizes and this allows for all those combinations.
Click to expand...
Click to collapse
that is true, but i didnt include that cause i was seeing people having issues with xposed-framework on the MOTOACTV on a few threads, and tbh i made this app+inlcuded in modpack before that method was usable for MOTOACTV (or gingerbread in general), thats kinda why i havent updated the modpack in a while (including the fact mine is damaged for some time now), i managed to fix mine up somewhat but it only turns on the backlight and no button combos work but to turn on backlight XD, so no fastboot recovery, boot-to-system, or quickboot :S and since the device is discontinued i cant get a real fix XD, so unless i personally test the things i put in this modpack, i cant make new versions to distribute for device stability reasons (e.g. in case it is corrupted and breaks someone elses device, as it is un-tested, since i dont have a device to test it on)

jkok said:
that is true, but i didnt include that cause i was seeing people having issues with xposed-framework on the MOTOACTV on a few threads, and tbh i made this app+inlcuded in modpack before that method was usable for MOTOACTV (or gingerbread in general), thats kinda why i havent updated the modpack in a while (including the fact mine is damaged for some time now), i managed to fix mine up somewhat but it only turns on the backlight and no button combos work but to turn on backlight XD, so no fastboot recovery, boot-to-system, or quickboot :S and since the device is discontinued i cant get a real fix XD, so unless i personally test the things i put in this modpack, i cant make new versions to distribute for device stability reasons (e.g. in case it is corrupted and breaks someone elses device, as it is un-tested, since i dont have a device to test it on)
Click to expand...
Click to collapse
Sorry to hear that. I personally haven't loaded the mod pack yet. Was looking into cherry picking parts of it when I saw the question on DPI. I thought it was a general question.
In any case, I personally have not had any issues with Xposed on my actv. What issues have you heard about?

jkok - thank you so much for the explanations. It's become more clear for me but I'm not so experienced in android/development so I have some more questions related to dpi on actv.
My practical interest in this is - to investigate the possibility to run igo primo on this device (for route planning/voice navigation) because I'm not happy with Motorola map application (walk/run outdoor mode). I have some ideas how to modify igo's data.zip for specific screen resolutions (at least I managed to make "custom 640x480" data.zip for primo 2.4.0 WM for htc DIAM100) but I need to know what is the "Full Screen" resoluton (for igo and other applications) in different dpi modes on actv (ClearD 1.2.0 rom currently, just in case). Is it the same - 176x220 for all dpi's (I don't think so as the size of icons/fonts/etc are different). So, the real question is - what is the screen resolution I need to set up in data.zip to try to run igo primo on motoactv. To know that I need to understand if dpi change affects the "full screen resolution" in motoactv/android. And, once more, sorry if the question looks stupid (already explained etc) as I'm not developer...

yuiop0 said:
jkok - thank you so much for the explanations. It's become more clear for me but I'm not so experienced in android/development so I have some more questions related to dpi on actv.
My practical interest in this is - to investigate the possibility to run igo primo on this device (for route planning/voice navigation) because I'm not happy with Motorola map application (walk/run outdoor mode). I have some ideas how to modify igo's data.zip for specific screen resolutions (at least I managed to make "custom 640x480" data.zip for primo 2.4.0 WM for htc DIAM100) but I need to know what is the "Full Screen" resoluton (for igo and other applications) in different dpi modes on actv (ClearD 1.2.0 rom currently, just in case). Is it the same - 176x220 for all dpi's (I don't think so as the size of icons/fonts/etc are different). So, the real question is - what is the screen resolution I need to set up in data.zip to try to run igo primo on motoactv. To know that I need to understand if dpi change affects the "full screen resolution" in motoactv/android. And, once more, sorry if the question looks stupid (already explained etc) as I'm not developer...
Click to expand...
Click to collapse
well im not familiar with those apps, as for the resolutions/dpi im not sure of that :S it could possible be found on google, as basic hdpi (240 dpi), usually is around 480*800, and 120 dpi is like the motoactv 220*176, so i guess there isnt a ratio it follows, just sizing of images maybee :S, but i also just became a developer more resently withing the last 2 years so im still learning

Possible ram fix for 4.3, NEED TESTERS!

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