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
Related
Since Sony Xperia X10 is now running on 2.1, topics related to 1.6 is not mentioned here.
This thread are created based on compilation of other threads related to optimization, and meant as an entry point for user interested in optimization.
Understanding your Android
Just to put something short, so we can understand our Android and some points related to optimization better.
Android is an open source operating system owned by Google that is maintained by Android Open Source Project (AOSP). The operating system is based on modified Linux kernel, where most of the application is written in Java language and running on DalvikJVM.
Android do things differently than old generation OS like Symbian, and below is the explanation related to performance.
Unlike Symbian, Android designed to have as many as application loaded and running in the OS, it maintain list of least used application that will be unloaded when a requests for more memory is made when the free OS memory is already low.
These are the nature of JVM, where allocation and deallocation of memory is managed by garbage collector as doing things in bulk is faster then working with small chunks. So you don't have to be alarmed when you open a memory viewer application and see your Android is running on low memory. Freeing RAM with task killer is only momentarily, as you uses the phone again, the free memory will goes down again.
Android phones stores system application, data and files internally in NAND flash area and stores user data in internal memory storage or external storage such as SD cards. This memory is different than your operating sytem memory.
Operating system memory is memory allocated for the kernel, native application and most application you download from market. Installing a lot of application will not directly reduce free RAM, nor uninstalling or removing files will increase free RAM directly. Action such as removing ringtones, wallpaper and even Sony PC Companion ISO will not free your RAM
In general there are two type of android application. One is a standalone application that only run if you open the application, and the other one is running even you haven't open the application which called service.
By design, guideline and suggested practice, application should not continue to run lengthy processing when it get pushed to background via home button, back button or switching to other application; properly build application will just go idle. Which means you should be less paranoid about application eating you processing power.
But service is meant to run lengthy operation as they don't have user interface and runs in background. Some service meanth for pushing or pulling data from internet, reading your files and do processing like playing songs, or just doing something then update the widget just to make you happy. Unnecessary services are the things that you should be aiming if you want to optimize your Android.
General FAQ about Optimizing Sony Xperia X10 2.1
I just updated to 2.1 and my phone really feel slower than 1.6
Since you had been using 1.6 for quite some time, your SD card should have quite a lot of photo and media. Just after you updated to 2.1, and add your Google and maybe Facebook account, the new Face Recognition service is actually already starting to scans all your photo, then when your Google and Facebook contact arrived, it will try it best to match photo and contact. This new Face Recognition really kicks hard in your processor, then after a while your phone will be as fast and even better than old stock 1.6.
I still feel that the phone is slow, is there any simple and quick way to optimize
The simple and quick to optimize your phone instantly is by changing the 2.1 dalvikvm to JIT capable dalvikjvm. You can read and apply them by reading the thread referred below, but before you do that open the below link in background tab and please do read more first.
Android 2.1 OPTIMISER V002 by Jerpelea
2.1 Customizer v0.99.1 by ttxdragon
Both optimizer contains script that will erase your "junk/unused" application from your phone, be sure to read them first before executing. My suggestion is you apply JIT modification first, before going optimizing by remove your "junk/unused" application.
Please do remember that you have to Root your X10 first.
How to root the phone
You can root the phone using methods below.
OneClick z4root Android Application
SuperOneClick Windows Application
Is [INSERT APP NAME] here is save to remove?
By removing unused application, you will gain certain amount of performance gain. Below are the links with app list.
2.1 Customizer v0.99.1 by ttxdragon
Official List of Apps that Can be Removed from a 2.1 x10 by exekias
And still a lot more in other Sony Ericsson X10 forum section but those two is quite complete
And in case you forgot to make backup you can go to
2.1 System Apps - In Case You've Deleted Them by XperiaX10iUser
After doing all that my Quadrant Benchmark is still low
You should run Quadrant as least two or three time or until you get best score, the first one usually yield low score, because a lot of memory allocation process to Quadrant happening during the first run.
Tuning Utilities
Memory Usage - Application to see how much memory used by your application and services
Advanced Task Manager - Application to see is your application running on foreground, background or idle and its memory usage
Quadrant Standard - General benchmarking tools to see if your changes make improvement
Linpack - Processor benchmarking
Titanium Backup Pro - Back up application, the paid version can freeze your app rather then uninstalling it.
Fine Tuning Guide
About Widget, Application shortcut and Live Wallpaper
Even though widgets looks really good in your phone, some widgets required simple periodic process for updating its display, some have a full blown service running to support it. A very instant example that you can see in your phone is the Power Control widget and the new Status Switch widget.
Power Control widget update triggered by configuration change such as wifi on and off, while Status Switch widget which have a battery level is triggered by a running service. Just put Status Switch widget then go to Settings -> Application -> Running Services. Then you will see there a Status Switch Update service running in background to update the battery level.
By selectively put widgets on your home screen, you can gain extra processing and memory. Timescape widget is even worse, it have three service running to support it.
Application shortcuts also uses extra memory in your home screen app and your home screen app is usually system persistent, reducing number of shortcut will give extra RAM and reducing the required rendering process during scroll.
Live Wallpaper just as the name said looks really nice and require extra memory and process of course.
Tuning via build.prop
Some value can be added and modified into build to increase the performance of X10.
dalvik.vm.heapsize=32m
This will change the maximum memory size per application. If you decrease the value, smaller application starts faster, but big application like games will prone to crash, if you increase the value too much, smaller application takes longer to start, but big application will extra gain benefit from less garbage collecting.
Reference: Test: How changing the max amount of memory per VM Heap can effect your ROM (Cyanogen)
windowsmgr.max_events_per_sec=60
This will change the maximum number of touch screen gesture events per second, the bigger the value, the smoother the scrolling will be
There still some more build.prop tweaks that you can do, but not all of them will be processed by X10 as each device behave differently.
reservation for more article to go
Nice clean guide, should help newcomers. Good work!
synlar said:
Nice clean guide, should help newcomers. Good work!
Click to expand...
Click to collapse
Thanks, but i am quite depressed after reading it my self and found that i make a lot of typo. Had to revise and revise again.. lol.
Nice piece of work there Xeviro..
Can you post your build.prop please i cant find the windowsmgr.max_events_per_sec=60 one in mine.
Wolfbreak said:
Can you post your build.prop please i cant find the windowsmgr.max_events_per_sec=60 one in mine.
Click to expand...
Click to collapse
That one you add by your self to you build.prop. If you look further in google, there still a lot of other build properties that you can set to Android.
There is another way to add and test build.prop instantly by using adb shell command "setprop key value" and "getprop key". Some property will take effect immediately, some require you to reboot.
How do you prove that the windowsmgr.max_events_per_sec=60 actually works? After applying that I tried input benchmark and it still showed 33hz.
ooidort said:
How do you prove that the windowsmgr.max_events_per_sec=60 actually works? After applying that I tried input benchmark and it still showed 33hz.
Click to expand...
Click to collapse
Ok, i just checked, that for this build.prop property to take effect, you need to reboot the device first. I just test on my, giving 10 and 200 in value. With 10, the input benchmark showing less then 20hz most of the time, while with 200 it gives me 40hz+.
Also you can see if you scroll the app list with 10 and 200 value, you can see the difference.
xeviro said:
Ok, i just checked, that for this build.prop property to take effect, you need to reboot the device first. I just test on my, giving 10 and 200 in value. With 10, the input benchmark showing less then 20hz most of the time, while with 200 it gives me 40hz+.
Also you can see if you scroll the app list with 10 and 200 value, you can see the difference.
Click to expand...
Click to collapse
I definitely notice the difference between 10 and 200, but it still doesn't go above 33hz... Maybe it's the framerate cap doing it's thing?
xeviro said:
Thanks, but i am quite depressed after reading it my self and found that i make a lot of typo. Had to revise and revise again.. lol.
Click to expand...
Click to collapse
Good write up! I was actually going to say something about the typos/errors, because I'm a jerk, but, you noticed them too, so I feel satisfied.
I hope people will read your little intro about RAM and realize a task killer's real purpose is to kill rogue services that kill battery.
xeviro said:
That one you add by your self to you build.prop. If you look further in google, there still a lot of other build properties that you can set to Android.
There is another way to add and test build.prop instantly by using adb shell command "setprop key value" and "getprop key". Some property will take effect immediately, some require you to reboot.
Click to expand...
Click to collapse
But where do i need them to add? At Beginning or at End or Middle?
iead1 said:
Good write up! I was actually going to say something about the typos/errors, because I'm a jerk, but, you noticed them too, so I feel satisfied.
I hope people will read your little intro about RAM and realize a task killer's real purpose is to kill rogue services that kill battery.
Click to expand...
Click to collapse
Please forgive my typo and grammars, i life in country where people simplify their way of communication. I cannot talk proper now. hahaha
Wolfbreak said:
But where do i need them to add? At Beginning or at End or Middle?
Click to expand...
Click to collapse
Anywhere
xeviro said:
Please forgive my typo and grammars, i life in country where people simplify their way of communication. I cannot talk proper now. hahaha
Anywhere
Click to expand...
Click to collapse
If i add this to the end of my build.prop my phone does not accept SIM unlock code anymore .... ??
EDIT: Strange, second time it worked ... btw. what is the default value ?
Ive added dalvik.vm.heapsize=32m to see what diff it will make and well..
wow.. it killed my phone.
It will show sony ericsson on the screen when you turn it on and just stay there!
So yeah... how can i fix this?
It's bricked, you'll need to reflash the software!
:-(
OP- Great thread, thank you!
Post on my Rooted 2.1 X10i using Tapatalk Pro and Swype
Yeah i knida noticed...
fixed now but im not trying that heapsize thing again..
Anyone here have the original/untouched nordic build.prop? I'm really appreciate it if you share it here. ^_^
Sent from my Xperia X10i (2.1 and rooted) using XDA app
Seansmit17 said:
Ive added dalvik.vm.heapsize=32m to see what diff it will make and well..
wow.. it killed my phone.
It will show sony ericsson on the screen when you turn it on and just stay there!
So yeah... how can i fix this?
Click to expand...
Click to collapse
Seansmit17 said:
Yeah i knida noticed...
fixed now but im not trying that heapsize thing again..
Click to expand...
Click to collapse
Its working correctly in my phone, and this heapsize settings is the most common one in android modding. you go check google and see the results.
I also attached build.prop from my phone.
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
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
I chanced upon an app that could enable android users the ability to true multitask. Android is designed to cleverly close apps in the background that it deems unimportant. This feat is brought to fruitation through the assigning of minfree values. The higher the minfree value, the more seceptible the app is in being axed to conserve ram and computing space which inturn conserve battery.
With this in mind, theoretically, if we assign an app with a minfree value of 0, the apps will not be killed even when kingdom come. Pardon my attempt at humour if you aren't chuckling.
Now to the crux of this post. There is an inherent difficulty to assign minfree values and not everyone is a coder. Luckily there is an app on the market which let users assign minfree values and better yet, filters the apps into hidden apps and stuff. Simply download this free application from the market:
https://play.google.com/store/apps/...t=W251bGwsMSwxLDEsImNvbS5ycy5hdXRva2lsbGVyIl0.
Go to settings, enable advanced mode to get access to the first three values. One simply inputs "0,0,0,0,0,0". And voila, theoretically all hidden/background apps will not be killed and true multitasking is achieved.
A quick test of some programs that are designed to close after home button is pressed does not close now. Am happy to report that this trick does not close any background app. Only downside is user has to manually close the apps, which for me is more than ok. Hope this helps!!
[Update] I have changed all fields to 0. So technically what I am telling the GSIII is "do not have coffee breaks,toilet breaks and oh, "I own your sorry ass".
Am excited to report that N.O.V.A. 3 still continued running after opening maps with GPS, XDA, Maps, Internet browser. All of which are running.
[Update 2] Edited the values to "0,0,1,1,1,1" as a failsafe in case all rams have been used up. E.g. NOVA3 and MC3 concurrently running due to carelessness. Will report any drastic behaviour or successfully implementation without much drawbacks.
Sent from my GT-I9300 using xda premium
I'm interested to know how this affects battery life.
jiggytom said:
I'm interested to know how this affects battery life.
Click to expand...
Click to collapse
I am pretty sure this will suck the bejesus out of the battery. : ) Plus we aren't using the software for its intended use.
I did the same
Interesting to try...
sebarkh said:
I did the same
Interesting to try...
Click to expand...
Click to collapse
If in the event u have reached a satisfactory value do share! I was inspired by the "backgrounder" program of jailbroken IOS devices. It does the same thing except our way is different. From my Iphone days I have fetishes of true multi tasking. : )
Sent from my GT-I9300 using xda premium
The Linux/Android kernel WILL run OOM-Killer (Out-of-memory) with SIGKILL (removes the process from RAM and CPU without letting it any chance to save data or report) when the memory is full and it cannot continue operation otherwise.
Dalvik _should_ work around a full memory but by disabling this feature it won't so you might experience some data loss.
Consequently it is necessary to have a sufficiently large Swap-Partition on your SDcard to allow the kernel to get more memory whenever needed. It won't be fast when it hits the limit but at least it still works.
d4fseeker said:
The Linux/Android kernel WILL run OOM-Killer (Out-of-memory) with SIGKILL (removes the process from RAM and CPU without letting it any chance to save data or report) when the memory is full and it cannot continue operation otherwise.
Dalvik _should_ work around a full memory but by disabling this feature it won't so you might experience some data loss.
Consequently it is necessary to have a sufficiently large Swap-Partition on your SDcard to allow the kernel to get more memory whenever needed. It won't be fast when it hits the limit but at least it still works.
Click to expand...
Click to collapse
Well on top of that, the Minfree was programmed so that the CPU doesn't have to overwork and so it can run at lower frequencies.
Interesting app, but I'm going to leave the programming to the experts.
Plus prog is too much of a hassle for too little gains in this case. Hahaha.
I have to say that I miss the way the Palm Pre multitasked the best. I also like how pre handled contacts with multiple numbers/IM/google etc (something that ios6 is finally going to attempt to do). It would incorporate all of them into one message window using icons. If only some of that could be incorporated into Android!
So the dev section here has been active recently with some high quality work, and I am looking to add to the fun
**SEE POST 2 FOR CHANGE LOG**
***VERY IMPORTANT IF YOU ARE GOING TO USE THIS MOD, you need to navigate to the /system/etc folder on your device, and rename the file "init.lge.zramswap.sh" to "init.lge.zramswap.sh.bak" so it does not run at boot.
This is a step by step instruction on how to replace the /system/etc/init.qcom.post_boot.sh file for the LG V10. Be it known, however, that this instruction (and file) can be used with any device running the Snapdragon 808 SoC combo.
What does this do?
Simple. It turns your device into an even more efficient powerhouse. Here are is a list of everything done:
-Interactive Governor tuning for performance and better battery life, a quick description of what I did...
-low load, quick response, low frequency
-high load, quick response, higher frequency
-modified input boost settings for Interactive
-Adjusted GPU target load values
-Switched IO scheduler to noop, and tuned accordingly
-Adjusted minfree values (RAM management, it is a little more multi-tasking friendly)
-Adjusted VM parameters - swappiness, dirty ratios, cache pressure, centisec values, etc (again to complement multi-tasking... your data will hang out a little bit more before being written to disk, but house cleaning won't happen all at once, so there is still good performance and your system won't bog down while it is flushing the toilet)
-DISABLED zRAM!!! - I have no idea why a device with 4 GB of RAM has zRAM enabled. This is purely a waste of CPU cycles and other system resources. You want physical memory, not compressed memory.
-Changed congestion algorithm to cubic (better network performance... assuming the network bandwidth is already there
-Cleaned up the shell file and fixed some errors.
-More to come!
How to do this, we'll just get right to it.
Download this app https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Download this file https://drive.google.com/open?id=0BzM9W6qUvx-gcm1SVDhsTDVWZ3M
And while you are here, check this out, decide which one you want.
http://forum.xda-developers.com/showpost.php?p=66792862&postcount=109
Very important you put the file on the root of your INTERNAL SDCARD!!!
Do not forget to do this.
After you do that, open terminal emulator, and type the following commands in the order they are presented (I would highly recommend just copying them from this post and switching back and forth between your browser and the terminal app):
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
Double check the file has been replaced with a file explorer of some sort, double check permissions, then reboot. Good to go.
Some of this stuff explained http://forum.xda-developers.com/tmo...nux-virtual-machine-explained-part-1-t3386956
CHANGE LOG***
May 1, 2017
-Pretty major overhaul of the file. I've done some stuff on the Axon 7 that has been pretty effective. Rolling those changes out to other devices. https://drive.google.com/open?id=0BzM9W6qUvx-gcm1SVDhsTDVWZ3M
May 31, 2016
-Replaced corrupted files. Good to go now!
Dangerously version (fixed) https://drive.google.com/open?id=0BzM9W6qUvx-gVHBGWEp3QkpURVE md5sum: a632c866e22114c0e18fa335f005293e
May 25, 2016
Quite a bit of changes here...
-VM completely readjusted. vfs_cache_pressure set back to default 100 to fairly reclaim memory pages that have been allocated to block specific data about file location, etc.. there are tons of write ups on this stuff if you guys want to investigate more into what this setting does, how it works. It's basically a fairness multiplier centered around a value 100. + or - that value increases or decreases the probability that the kernel will reclaim those certain memory pages relative to swap.
-Swappiness reduced drastically... from 80 to 40 (default is 60 depending on which kernel you are running)
-dirty ratio and dirty background ratios reduced drastically to avoid massive amounts of data being flushed and causing system hangups when that ceiling is hit. (lol this happened to me... system ran out of mem... *shrugs* I go hard bros)
-Increased the probably of the system to reclaim memory pages, and made a pretty big adjustment to writeback_centisecs and expire_centisecs
-Changed functional aspects of the interactive governor again - it is perfect. Nominal user experience. Same with touch input_boost. This system definitely has a sweet spot, and I'm pretty sure we've found it now.
-Decided to ditch the laptop mode idea and not mess with the RAM console outputs, the functional loss wasn't returning enough reward. So, here we are.
-Adjusted minfree once more, to
-It is important to note that the system will, admittedly, not multitask quite as aggressively. I had to do this, however, for myself mostly. As I was achieving OOM conditions and hitting the high ceilings set in other parameters like dirty_ratio and when it hits that wall, man it hits hard. Complete lock up for a good 40 seconds while everything is getting dumped from memory. I need a phone with more RAM lol. Didn't think that would ever happen on my mobile set up with 4 GB of it but here we are. I suppose I could re-enable zRAM for myself? But that would hardly help as compression ratios aren't going to yield me an extra gigabyte. Ok now I'm rambling. DOWNLOAD THE FILE!
Very interesting, I'll be trying this in the next hour or so! Thanks for posting.
Edit: Made changes as per the instructions and rebooted successfully. No issues so far, we'll see! Thanks again.
Nice...
Desde V10 (LG-H901)
For all variants? Is it compatible with H961N LP?
Looks promising and wanted to try.
How do I know it worked? I followed the steps
Sent from my LG-H901 using XDA-Developers mobile app
roosxter said:
How do I know it worked? I followed the steps
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
After every line he explains what it does, you would recognize the changes through your usage or maybe non-usage (as far as battery life and RAM management goes)
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
iamtheon said:
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
Click to expand...
Click to collapse
i got problem with the !!!!!!cd /sdcard , writing
i tried cd /storage/emulated/0
and worked for me
11868 said:
i got problem with the !!!!!!cd /sdcard , writing
i tried cd /storage/emulated/0
and worked for me
Click to expand...
Click to collapse
I tried that, but doesn't hurt trying again.
Edit: It worked. I did the same thing lol oh well thanks @11868
Can this be done with the root explorer instead of terminal emulator?
So this can be used on the G4? And does this overwrite settings within the kernel? If I push this file and I don't like the results can I flash a kernel to get rid of the changes?
iamtheon said:
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
Click to expand...
Click to collapse
Your system wasn't mounted as rw when you executed the command
agrenwa said:
Can this be done with the root explorer instead of terminal emulator?
Click to expand...
Click to collapse
It can, yes, I just prefer the old school way. You can manually drop the file in the /etc folder after deleting the previous one. Just need to make sure the permissions are set appropriately.
klbjr said:
So this can be used on the G4? And does this overwrite settings within the kernel? If I push this file and I don't like the results can I flash a kernel to get rid of the changes?
Click to expand...
Click to collapse
Yes, this can be used on the G4 and any other device using the Snapdragon 808. Overwrite settings within the kernel? No, I wouldn't say that. sysfs is more of a userspace / virtual file system that allows you to interact with the hardware... but the parameters we are working with here are completely writable, not permanent, and more important, will reapply AFTER boot. So, no, flashing a kernel will not revert the changes. If you want to go back, you'll need the original file to replace mine with.
Hope this answers your questions.
Since the file is hosted on Dropbox, anyone who has a dropbox account please choose the login option, and transfer the file to your dropbox before downloading it from your own storage to avoid OP's dropbox being blocked for too many downloads in a row.
Good Job OP, nice to see Junior Members doing something great in the dev section
So I did it last night, and so far battery life seems to be much worse than before when nothing has changed but these tweaks. Any idea why? Battery stats is the same for me as usual with the exception of Android System being at 6% and Android OS at 6% use each.
So far so good, not sure what battery usage will be like. I had terrible lag in a game called Underworld Empire and that has disappeared! How badly was the kernel/system coded before?!
Question , how come your file is smaller than the original? Was there a lot of excess code that was useless?
Sent from my debloated rooted LG V10 using Tapatalk
rirozizo said:
Since the file is hosted on Dropbox, anyone who has a dropbox account please choose the login option, and transfer the file to your dropbox before downloading it from your own storage to avoid OP's dropbox being blocked for too many downloads in a row.
Good Job OP, nice to see Junior Members doing something great in the dev section
Click to expand...
Click to collapse
I'll try to upload the file elsewhere, didn't consider that. However, it is a very small file and dropbox might not notice/care. Good observation.
danstheman7 said:
So I did it last night, and so far battery life seems to be much worse than before when nothing has changed but these tweaks. Any idea why? Battery stats is the same for me as usual with the exception of Android System being at 6% and Android OS at 6% use each.
Click to expand...
Click to collapse
Coincidence maybe? Keep monitoring, report back.
Also, bear in mind: rebooting your system causes a little more activity within the OS the first day or so (particularly google services) and it does have an effect on battery drain.
amoot329 said:
So far so good, not sure what battery usage will be like. I had terrible lag in a game called Underworld Empire and that has disappeared! How badly was the kernel/system coded before?!
Question , how come your file is smaller than the original? Was there a lot of excess code that was useless?
Sent from my debloated rooted LG V10 using Tapatalk
Click to expand...
Click to collapse
Yes, it is smaller because I removed everything that was not relevant to the msm8992 SoC. Qualcomm uses common files for just about everything and anything they can - saves them time, hassle and consolidates work somewhat.
Most of the content removed from the stock file is for other platforms not relevant for us.
warBeard_actual said:
I'll try to upload the file elsewhere, didn't consider that. However, it is a very small file and dropbox might not notice/care. Good observation.
Click to expand...
Click to collapse
I recommend Google Drive or Box
@warBeard_actual
Great job buddy on this.... @freeza mad af!
To everyone else I've been using this for a while and am happy to report my buddy warBeard_actual has been killing it!
bencze, proof or it didn't happen