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
I'm one of those persons that tests stuff all day long, from kernels, to custom made kernels, overclocking, benchmarks, roms and that stuff so I felt in the need of something that could provide me with CPU Temp and current CPU Frequency because I was testing governors and cpu throttling.
No, you don't need ROOT, you can do this on a 100% stock tablet.
What you need
USB Debugging enabled on your tablet.
ADB in your computer (if you don't have/know about this, you should find a manual )
How to do it
1) Connect your tablet to the computer (you can do this over usb or you can use adb wireless apps)
2) Open up a command shell (Windows users: CMD, Linux/Mac users: Terminal)
3) Type adb shell (Make sure you are in the folder where your adb program is located, if you have setup System Variables you can skip that)
4) Your terminal/cmd should say something like this now: [email protected] / [email protected], the line of text your will have to copy paste is this one:
while :; do sleep 2; echo -n "TEMP: ";cat /sys/devices/virtual/thermal/thermal_zone0/temp;echo -n "FREQ: "; cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq; done
Click to expand...
Click to collapse
5) This will auto-run every 2 seconds until you stop it, temperature is in Celsius and Frequency is in Hz (384000 Hz represents 384 Mhz), the sensor we are reading gives an average CPU temperature based on the actual load and expected load, this is natively done by the tablet. If you want to read a more accurate sensor you can change the thermal_zone0 for thermal_zone7, the difference should not be much but on stock kernels that sensor sometimes doesn't report any temperature and you will see an error. If you are using @franciscofranco kernel (http://forum.xda-developers.com/showthread.php?t=2446431) you can read sensor 7 always, and it's recommended.
If you find this little trick useful, enjoy it, just thought that someone could use it.
P.D.: You can run this as well on a Terminal from Android.
ADVANCED: If you know a bit about what I did in that command, you can tune it as you like to do whatever you want, here is a breakdown of what this command does.
while :; (this is what keeps the infinite loop going)
do (the trigger to start running commands)
sleep 2;(basic sleep command works as a timer, this is in seconds)
echo -n "TEMP"; (We write a text line to identify the 2 values, with -n operator we do it in the same line as the next order)
cat /sys/devices/virtual/thermal/thermal_zone0/temp; (we output the temperature value from the following file with a cat )
echo -n "FREQ"; (We write a text line to identify the 2 values, using -n again gives us another line of text)
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq;(we output the current cpu speed value from the following file with a cat )
done (this is how we tell the while loop that we are done with commands and that it should run again)
You can give this script some other uses, like creating a log file with sensor readings to measure per example, battery drain, or signal strength.
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
Hi,
to find your Panel manufaturer ID do the following via ADB or Terminal (Note: enter it after fresh boot, the kernel log gets flooded with useless stuff very quick):
Code:
dmesg | grep -i mdss_dsi_panel_init
The output will be something like:
Code:
mdss_dsi_panel_init: Panel Name = 9
Available Panel Types
jdi_novatek_hd_cmd_panel (Panel Name = 9)
lgd_novatek_hd_cmd_panel (Panel Name = 8)
somc,default_panel_0 (Panel Name = default)
somc,default_panel_1 (Panel Name = default)
Without root permission denied?
Sent from my iPad using Tapatalk
@Tommy-Geenexus
Cool Bro!
JDI = JVC
LGD = LG display
And default is... "default"?
Lol how do we know what's the "default" manufacturer?
Regards
mele80 said:
Without root permission denied?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Try via adb shell (adb shell dmesg). This works fine for me without root.
langeveld024 said:
@Tommy-Geenexus
Cool Bro!
JDI = JVC
LGD = LG display
And default is... "default"?
Lol how do we know what's the "default" manufacturer?
Regards
Click to expand...
Click to collapse
Nope, JDI = Japan Display Inc, but LGD is LG (don't know for sure).
The default one is prob. not used in shipping units
Tommy-Geenexus said:
Nope, JDI = Japan Display Inc, but LGD is LG (don't know for sure).
The default one is prob. not used in shipping units
Click to expand...
Click to collapse
Thanks!
Is it possible related to colour and/or buying location and such? (as I've read everyone is talking about)
langeveld024 said:
Thanks!
Is it possible related to colour and/or buying location and such? (as I've read everyone is talking about)
Click to expand...
Click to collapse
I honestly can't tell, but it may or may not be, only a Sony representative can answer that
Returns nothing here when used via ADB. A manual dmesg check also gives nothing.
I got number 9. Do they differ in quality?
Random Username said:
I got number 9. Do they differ in quality?
Click to expand...
Click to collapse
Can't tell so far. People who returned their Z5C to get a new one could check which Panel they got and report any differences.
Im kinda noob when it comes to ADB controles, so any ''detailed'' step by step guide for entering commands to check this thing? I ender adb shell and when i enter the command from the OP i get nada. Help?
Tommy-Geenexus said:
Hi,
to find your Panel manufaturer ID do the following via ADB or Terminal:
Code:
dmesg | grep -i mdss_dsi_panel_init
Click to expand...
Click to collapse
You should probably mention that this will work quite early after system start.
dmesg log is cluttered rather quickly and shows only recent records. That's why some people report nothing in the output.
Back to the topic, I have 9 for the phone bought in central Europe. So, this will be probably most dominant display for EU region.
bubimir13 said:
Im kinda noob when it comes to ADB controles, so any ''detailed'' step by step guide for entering commands to check this thing? I ender adb shell and when i enter the command from the OP i get nada. Help?
Click to expand...
Click to collapse
Turn on usb-debugging, enter adb shell and the command above. Thats it.
OtaruM said:
You should probably mention that this will work quite early after system start.
dmesg log is cluttered rather quickly and shows only recent records. That's why some people report nothing in the output.
Back to the topic, I have 9 for the phone bought in central Europe. So, this will be probably most dominant display for EU region.
Click to expand...
Click to collapse
Yeah you're right, the log get's cluttered pretty easy, working on that already on my Kernel.
Added it to the OP.
also got 9. And also an CE1 version (Croatia). Guess this is going to be a standard for most of Europe.
panel 9 here as well, anyone actually gotten the LG panel? Might just be testing hardware or similar?
Panel 9 here as well...
mdss_dsi_panel_init: Panel Name = 8
report by my Xperia Z5 Compact White
bought in 2015/10/3 in Taipei, Taiwan
mdss_dsi_panel_init: Panel Name = 9
z5c black Germany.
Display has a slight shadow topside that is most noticeable during boot when the white animation is playing.
Panel 9
E5823 Black Italy Rev3
Is there any way to decrease the minimum time for Wear to enter Wifi power save mode? The lowest is 15 minutes, I'd think something like five or lower would be more useful in most cases.
Hi
[NUMINIT] said:
Is there any way to decrease the minimum time for Wear to enter Wifi power save mode? The lowest is 15 minutes, I'd think something like five or lower would be more useful in most cases.
Click to expand...
Click to collapse
Most likely inside an SQLite DB. Like this one:
Code:
/data/data/com.android.providers.settings/databases/settings.db
ranf said:
Most likely inside an SQLite DB. Like this one:
Code:
/data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
It's there, thanks! Now to figure out what the value "2" means on wifi_sleep_policy...
Never mind, there's no entry for that. Seems to be pretty hard to change...
You have root? busybox installed? Then we might have a look at the output from:
Code:
busybox find /data/data/ '*.db'
ranf said:
You have root? busybox installed? Then we might have a look at the output from:
Code:
busybox find /data/data/ '*.db'
Click to expand...
Click to collapse
Oh, I did find settings.db, but there's no entry for the power save timer within the file.
There's a ton of redundant data, though, my God...