Database Users

How to check if your ROM is optimized ?

So,
Since the release of the kernel, there is oviously some work going on to optimise the ROMS, and I currently have the following setup.
Modaco 2.2 cooked ROM with custom kernel, and with compcache enabled.
It certainyl feels pretty snappy, but it always did with Spare Parts helping with the visual effect of speed.
I guess what I'm asking is if there is a way of checking to see if my phoe is actually utilising the compcache correctly, and if there are any other apps or scripts I can run to check if everything is ticking along nicely.
for example, I have meminfo installed, but I'm pretty new to all this, and I'm not sure what numbers I should be looking at , and what their values should be, to indicate that everything is nice....
Like I said, it's pretty snappy right now, and I have no complaints, but I just would like to get a handle on numbers to make sure I'm in the right ballpark.
Hoping someone can shed some light....

Shell into adb on your computer and type:
Code:
# free
Or download a terminal program from the marketplace and do the same on your phone.
You should see numbers in the Swap row of the data it returns.

Good question. I just flashed modaco's 1.2 Kernel over Fresh 1.1. Thus far I've noticed a big speed boost in dialing and loading apps. The Dialer speed is major at it used to be my biggest complaint with the Hero. Hit a contact and wait like 5 seconds or more .I have no way to verify though.

Tikerz said:
Shell into adb on your computer and type:
Code:
# free
Or download a terminal program from the marketplace and do the same on your phone.
You should see numbers in the Swap row of the data it returns.
Click to expand...
Click to collapse
total used free
Mem: 195916 193684 2232
Swap: 131064 90256 40808
Total: 326980 283940 43040
#
I'm worried about my Mem Free number (2232)
Doesn't seem a lot....??

I removed all of the # using es explorer, but it keeps giving me an error when trying to save it. Can someone please post instructions on an alternate way to enable compcache

noonanjs said:
I removed all of the # using es explorer, but it keeps giving me an error when trying to save it. Can someone please post instructions on an alternate way to enable compcache
Click to expand...
Click to collapse
I actually had the same problem. What I did was uncheck remount as read/write, re-check it, and after that was able to save the file, reboot and jus like that it was done

[How To] FIX APP LAG

I could not find this on the Captivate Forum. I found this method on another forum referenced below. This has significantly increased the overall speed of my Captivate.
**REQUIRES ROOT**
**limits your App space to 130MB, which can possibly cause issues**
**Do NOT use with large number/size of apps**
**This should not be a permanent fix, but works until somethings else comes up**
**If you approach the size limit you will get errors and/or strange things**
Here is the original post. *READ THE THREADS!*
http://forum.xda-developers.com/showthread.php?t=727279 (Method 1 only)
-also-
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
Note: This method moves the app data from the SD space to the NAND space which significantly increased the speed of the phone , but PLEASE read the links and associated discussion. You are limited to 130MB app space on NAND, which can be limiting depending on which apps you use.
The following can be done using adb or using terminal emulator (available on the Market) without the adb commands
How to check how much app memory you are currently using:
Code:
adb shell
su
cd /data/data
busybox du -h|busybox grep M
How to apply Method 1:
Code:
adb shell
su
busybox cp -rp /data/data /dbdata
mv /data/data /data/data.bak
ln -s /dbdata/data /data/data
reboot
How to undo Method 1 (no loss):
Code:
adb shell
su
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data
reboot
How to undo Method 1 (restore to point of application):
Code:
adb shell
su
rm /data/data
mv /data/data.bak /data/data
reboot

so are you working on the method 2? building a kernel to run app data on the ex-sd card method. this method is okay but has limitation.
for those who have alot of apps, i wouldn't bother. you phone will constantly have forceclose notification. however, if you do not have too many apps, it does make your phone smoother and faster. done the bench mark and brought it up about 100 points. not bad for a quick/temp fix.
but... still need a REAL fix. Mimocan who was the builder for the kernel for i9000 should be working on a kernel for us. Unless he is now into the new froyo bull crap. not worth my time right now. trying to run the 2.1 smoothest possible is the key for me.

does this method or method 2 fix the laggy issues in Dolphin HD browser and Touchdown Exchange?

I don't use Dolphin, but it made a MASSIVE difference in using Touchdown.

Running this currently on my Captivate flashed with the I9000 JM2 ROM w/ Captivate Kernel & SamSet 1.6 and I am getting a ~960 on quadrant. During the test you can see the I/O portion goes SIGNIFICANTLY faster. App load times also feel faster. Samset includes MCR Scripts to set this up for you.
Note: I tried to post links but since I am new to the forum I was blocked.

This worked wonders for Dolphin HD! Thanks!
Sent from my SAMSUNG-SGH-I897 using XDA App

I cannot get the Android SDK to install on my computer so can't use ADB. What Terminal emulation program do you recommend and how would I connect my phone to it?

Baldilocks said:
I cannot get the Android SDK to install on my computer so can't use ADB. What Terminal emulation program do you recommend and how would I connect my phone to it?
Click to expand...
Click to collapse
Terminal Emulator is available on the market

div3rg3nt said:
Running this currently on my Captivate flashed with the I9000 JM2 ROM w/ Captivate Kernel & SamSet 1.6 and I am getting a ~960 on quadrant. During the test you can see the I/O portion goes SIGNIFICANTLY faster. App load times also feel faster. Samset includes MCR Scripts to set this up for you.
Note: I tried to post links but since I am new to the forum I was blocked.
Click to expand...
Click to collapse
replace http with hxxp.
Do you have any downsides with flashing with the i9000 firmware? are you still limited to 130mb of app space?

If you read the modaco post Paul states that the 130 mb will take awhile to fill because the apps themselves are not stored but the data is.
"On the plus side, we're only moving data not the apps themselves, so filling up 130MB will take a while."
So that is good news I think I am going to try it. Thanks for the guy that posted how to check how much dbdata you have.

Works for me. Getting 980-1003 on Quadrant scores.

Just tried this. My captivate has been rather laggy and slow, specifically with apps such as twitter, facebook and pandora. I've been debating returning the phone and going back to iphone 4, but after the fix, it seems like a jump from an iphone 3g to a 4. Much snappier, but seeing that the custom kernel can yield 1500+ q scores, I'm actually not only hopeful, but excited about the future of the device.
Sent from my SAMSUNG-SGH-I897 using XDA App

too bad i cant apply the fix since i have 120 apps installed and they take up more than 130 MBs

As the previous poster said, its the application data space that is limited, not the space for actual apps. You can have a lot of apps installed, just not too many open and caching data.
Sent from my SAMSUNG-SGH-I897 using XDA App

I got a 973 running the stock Galaxy S I9000 and this fix. Not bad

Hmm I might have to give this a shot when I get home from work. Are most of you using this fix running stock Captivate rom?

Quadrant went from about 895 to 967. I can tell it's quicker. When I used to drag and drop apps and stuff there would be a lag, no lag now. I'm using a stock rom. This thing is going to be a monster once the modaco speed fix becomes available.

Ok before I did this I got a Quad score of 901. I checked my app data and I was at 120mb so just to make sure I deleted some apps I've never used and got down to 100mb. I did this (easy as pie BTW) and I got a Quad score of 951, but here's the deal. It booted completely from powered on to finishing "Scanning media" about x3 faster AND it was actually usable during "Scanning media", I don't know about anyone else but when it usually did that the phone was basically unusable during this period. So IMO even though it only gained like 50 points on Quad this thing is WAY faster with no lag that I can see zooming around between apps/launching them and such. Not a perma fix but this is a great band-aid till a real fix is found THANK YOU!!!!

Hmmm the more i read this thread the more i want to try this and according to the original poster its just as easy to undo as it is to set up so i guess there's nothing to loose.
Sent from my HTC Liberty using XDA App

well.. least we are takin steps in the right direction. i hear the kernal patch boosts your quadrant scores to about 1700.. so yeah. there's that to look forward to now.

CPU maxing @ full speed, 100% load after 24-48 hrs? FIX FOUND!

First off, I cannot take credit for finding this, I was referred to a bug report thread on the Google Android site by XDA user aweaver33, who I thank VERY much for pointing me on the right direction.
So, several of us have had this issue with various custom kernels, where after typically 24-48 hours, the phone would slow to a crawl. If you were to open an app like System Panel, you would see that the CPU load was pegged at 95%+, and speed would be maxed out. You would also see that the process using all the CPU is Android System.
The problem has to do with the file "time_in_state", which literally keeps track of how much time the CPU spends at any given speed in MHz. There is a limit to the size this file is supposed to reach, 256 bytes. Once it exceeds this size, the next time Android tries to access it, it flips out and gets stuck trying, and pegs the CPU. A lot of devs and users blamed SetCPU, and it is true that SetCPU does have an EFFECT on this issue, it does NOT cause it, and indeed the issue can occur whether SetCPU is installed or not.
The issue is brought on by custom kernels that add additional frequency steps for the CPU to choose from, which causes that log file to grow. Which is why older or stock kernels will not cause this. Some ROMS incorporate a workaround so you may not have this issue.
Anyways, the issue is explained better in the link aweaver33 gave me. I will link to the original thread I posted with the conversation we had and the link he gave. I can confirm that, using the info he gave me, the issue has been fixed. I am currently just over 120 hours of uptime with no problems.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1082363&highlight=stock+kernel+gpu+
EDIT: attached the script files for those who want them. You can drop one or the other (NOT BOTH) in /etc/init.d if your rom has this folder already (creating the folder and adding it won't work), or you can download Autostart (root) from the market for free, and drop the file in /data/opt (create the opt folder). This difference between the two is one runs only once at boot, the other runs every five minutes. If you use SetCPU, you need the one that runs every five mins, as every time you open SetCPU it resets permissions on the time_in_state file.

flashable zip? not everyone is comfortable with code and scripts

If I knew how, I would. I wasn't even comfortable with it. But I was so tired of the locking up, I was willing to try anything (after a Nandroid of course). I'm not sure you *could* do this in a flashable zip. I can post the script I'm using. It only runs once after reboot, unlike aweaver's, which runs every five mins (good if you're using SetCPU, as opening SetCPU resets the permissions of the time in state file).
This script should work if dropped into /etc/init.d. *If* your ROM has that folder by default. Mine does not, so I had to download a free app from the market called Autostart which is free and very small. For that app you create a folder in /data/ and drop the script in there.
Sorry guys but I'm no dev so this is the best I can do, maybe someone else can make it flashable?

would it also be fixed by simply deleteing the log file as well rather than setting it to unreadable

It can't be deleted. System instantly replaces it.

bast525 said:
It can't be deleted. System instantly replaces it.
Click to expand...
Click to collapse
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Do you know if it is a problem in gingerbread as well?

mirrin said:
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Click to expand...
Click to collapse
I don't think you can delete it. I can't figure out how to.
mirrin said:
Do you know if it is a problem in gingerbread as well?
Click to expand...
Click to collapse
Issue 9733 is still listed as New, so either Google hasn't fixed it in Gingerbread or they just don't bother statusing their bug reports.

Why do you feel the need to delete it? If you are trying to delete it, you are likely using Root Explorer. Why not just use that to change the permissions of the file? Tap and hold, select permissions, and unchecked all permissions except for the top left one. This will stop the bug, but the permissions will be reset after a reboot, or after opening SetCPU.
I imagine that deleting the file might actually cause FC's or may cause the same bug but I dunno since it wont delete.

dyetheskin said:
flashable zip? not everyone is comfortable with code and scripts
Click to expand...
Click to collapse
I've never created a flashable zip before, but I'd be willing to look into it if the demand is really there. The problem I see is that I'd have to make certain assumptions about how everybody's ROMs are configured. It looks like the most portable approach would be to append a line to the end of /bootcomplete.inc.rc. Do people really find it easier to boot into recovery and flash a zip than to add one line to a file themselves? Personally, I'm always hesitant to flash a zip other than a full ROM because I'd be uncertain how it interacts with other changes I've made to my system.

Inc is
not bad
But. 48hours?
Sent overrow from my Optimized Inc using XDA App

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

Request for App: Toggle Switch for All GPU Rendering

Some report display is much sharper with better contrast like official stock reader in a modded ROM posted here forcing all rendering to be done on the GPU. However I'm happy with my set up and some report other unrelated problems with that ROM and in any case I want to keep my ROM. I asked in that thread if a little app just forcing all rendering to GPU could be made but there was no reply.
Many of us would love it if anyone could make an apk that will only do one function:
Force all rendering to be done on the GPU.
Maybe also with a toggle switch for on/off preferably?
Or even a CWM install file if a switch toggle app is too difficult and has to be a permanent fix.
Forcing all rendering will free up CPU more too for a faster system.
Any one interested in taking up the challenge?

from
http://forum.xda-developers.com/showthread.php?t=1933615
In file /system/lib/egl/egl.cfg
Delete the line
0 0 android
You can do it via ADB.
Remember to mount /system with R/W.
http://nookdevs.com/Nook_Simple_Touch_write_enable_the_system_directory
You can also use any terminal emulator app or any file explorer with root support (rhytm software) + any text editor.
You really need an app for that?

osowiecki said:
from
http://forum.xda-developers.com/showthread.php?t=1933615
In file /system/lib/egl/egl.cfg
Delete the line
0 0 android
You can do it via ADB.
Remember to mount /system with R/W.
http://nookdevs.com/Nook_Simple_Touch_write_enable_the_system_directory
You can also use any terminal emulator app or any file explorer with root support (rhytm software) + any text editor.
You really need an app for that?
Click to expand...
Click to collapse
Thanks osowiecki for your reply..
I use Total Commander which is like the old NC file manager. Easy dual pane transfer with Windows ftp etc. and easy atts management, editing etc. too:
http://forum.xda-developers.com/showthread.php?t=2574655
I deleted the line: 0 0 android, from egl.cfg, seems a bit clearer but not sure. Wanted an app for quick reboots to compare.
In the thread you linked jam_dev says:
jam_dev said:
In file /system/lib/egl/egl.cfg
Delete the line
0 0 android
(I suspect doing this forces h/w rendering, needs more testing)
Click to expand...
Click to collapse
h/w can mean CPU as well as GPU but lets assume he means GPU rendering as opposed to s/w rendering using CPU.
But the issue remains that he's not sure that line deletion forces all rendering to h/w? Any ideas?
Thanks again.

Anyone knows for sure about forcing all rendering to GPU for sure?