what are stock vm values of g4? - G4 Q&A, Help & Troubleshooting

I'm talking about dirty ratio, dirty background ratio, swappiness,vfs cache pressure etc, anyone with can pls post this values? thanks

fedef12evo said:
I'm talking about dirty ratio, dirty background ratio, swappiness,vfs cache pressure etc, anyone with can pls post this values? thanks
Click to expand...
Click to collapse
For my H815K (Telstra variant), it is:
dirty_background_ratio = 5
dirty_ratio = 20
swappiness = 80
vfs_cache_pressure = 100

Related

[TWEAK] Automatic Brightness levels!

Issue: http://code.google.com/p/cyanogenmod/issues/detail?id=2298
After toying around with the automatic brightness I'm now here to share my settings ...
I use the following settings:
Light sensor filter enabled.
Window length 10 seconds.
Reset threshold 400 lux.
Sample interval to 0.5s.
Light levels use custom checked.
Screen dim level, not sure what it is for but I have it on 1 instead of 20. ((edit: I found what it is for, it's the step size the filter takes? Or not? :s))
Edit other levels...
Number of levels: 18
0 1
10 1
117 17
225 33
272 49
320 65
480 80
640 96
960 112
1280 128
1940 144
2600 160
4200 175
5800 192
6900 207
8000 223
9120 239
10240 255
Allow light decrease checked.
Decrease hysteresis to 10%.
I hope people like my light settings, if you don't please tell me why
Reasons why some settings should be altered:
Reset threshold, should be able to set to 100 and 200 lux. At the moment if you walk into light it takes the filter some time to go up, so 100 or 200 lux would trigger a reset faster. Also the sensor starts at 225 lux so why 400 as a minimum in the first place?
Window length, as for the above, if you walk into light a smaller window length would help put brightness up much quicker in combination with a smaller reset threshold.
If the above two settings could be added in CMParts/ODParts that be great as the filter would be much more responsive to short period light changes. For example if you go from outside to inside or visa versa.
And maybe it would even be a better idea to remove the whole custom light levels and add a linear function to it to go with the filter (configurable) and just have 254 steps (1-255) over 10-10240?
Adding 254 steps yourself is ... A PAIN ><
English please
guys i know there is a problem with the light sensor in desire and i have the same case with mine it this is all about it please let me know how to fix it please.
shazan said:
guys i know there is a problem with the light sensor in desire and i have the same case with mine it this is all about it please let me know how to fix it please.
Click to expand...
Click to collapse
What ROM are you using? CyanogenMod and forks of it (OpenDesire, DeFrost etc) have a custom preferences menu where you can check out the light sensor values. That is when you leave the filter off and goto edit other levels. Hold your phone in line with a TL light and it should jump to 1280.
Do you see the top most number change when light changes?
Call me crazy, but I am ><
I put the whole table into the automatic backlight custom levels: http://www.linux-box.nl/~sjoer/1to255/1to255.php
And it works really well with light changes, it should work even better if reset threshold can be lower (200 or maybe 100) as it will respond to bright light <> no light much better.
how did you did that?
without typing lol
This is insane..... so much trouble for such a simple task. Automatic Brightness. On winMO i used g-lite wich was satisfacatory. A have the desire for a month now. I searched from a similar soft and i didn't find. But i'm not gooing to try this much trouble for something that should be easy. Thank you.
Im sorry but....HOW do I apply this ?
Can this be applied to other roms?
I am using Pinky desire and would love to do this.
Phil
philje123 said:
Can this be applied to other roms?
I am using Pinky desire and would love to do this.
Phil
Click to expand...
Click to collapse
yes and for stock roms please
The screen minimum value is 10-255, so how can I set "1" to the first 2 levels?
I set 10, and I like the settings overall.
sfjuocekr said:
I hope people like my light settings, if you don't please tell me why
Click to expand...
Click to collapse
First off, "10 1" is redundant as you already cover that from 0 to 9. So 17 levels should be enough. Second, on the last line "10240 225" you probably meant "10240 255". Testing your settings with these modifications now. I find you have a lot of levels, probably can do with less to reduce flickering, but as I said, testing these first.
Can we use these settings in a Sense rom and if yes how?What file do we have to edit?
so useless guys.
setup max brightness and enjoy the brilliant screen.
it takes less battery than this tool to constantly check your ambient brightness.
Can someone please make a post about how to use this (and especially on Sense Roms)? So far it only shows us "which sensor-level should be what brightness" but it doesn't provide any information on how to apply it.
I assume CM either has an app for this installed (if so, please tell us WHICH so we can use it too) or a shell-script in background (if so, tell us WHICH) adjusting the settings.
Could anyone post a how-to use these settings?
Edit: Nvm, it's under: Cyanogen Settings.
Btw under "Edit other levels" you should only change the boxes that's under "Lower"? You shouldn't touch "Screen" and "Button"?
Trying this out, and will see how it goes. Only have 5 levels on my current setup, so this should be a lot smoother
snudel said:
so useless guys.
setup max brightness and enjoy the brilliant screen.
it takes less battery than this tool to constantly check your ambient brightness.
Click to expand...
Click to collapse
Is that true?
any more improvements?
and how can i backup this setting?
i wont to input it again when i flash a new rom :-(
sfjuocekr said:
Issue: http://code.google.com/p/cyanogenmod/issues/detail?id=2298
After toying around with the automatic brightness I'm now here to share my settings ...
I hope people like my light settings, if you don't please tell me why
Click to expand...
Click to collapse
Since the source code of Sense kernels is available now, would it be possible to write the tool for Sense ROMs too? You sure would do a lot of people a big favor

Freezes and SYSCTL config

Hi,
My "defy" always had freezing and lag problems when I try to run heavy applications, such as 3D games, or Gmaps, etc.. in every ROM I've tried (CM7, MIUI, stock froyo, stock gb, etc.)
I read that a solution could be setting the minimum values of memory with an application called SYSCTL CONFIG (it's in the Market)
Anyone also has this problem? What values ​​do you use? Increasing this value, can cause problems?
Code:
Mine are:
Min Free Kbytes: 8192
Dirty Ratio: 95
Dirty Background Ratio: 60
Pressure VFS Cache: 20
PD: This is the post I found: http://forum.xda-developers.com/archive/index.php/t-1047153.html
Same here ... : )
I had to use Sysctl config to set the min free Kbytes to 8192.
But all remaining parameters are left in default values.
Dirty Ratio = 20
Dirty Backgr. = 5
VFS Cache Pressure = 100

Smarreflex - Values explained +1350mv calibration fix

Ok dears, I accidentally came across this. Now there is nothing smart about smartreflex.
voltage.h contains values about min and max range for smartreflex calibrations for CORE IVA and MPU, that we already knew...
Now I found this:
http://gitorious.org/pandroid/kerne...a10c87d6445/arch/arm/mach-omap2/smartreflex.c
Let's quit fooling around:
/* Default steps added for 1G volt is 5 in uV */
static unsigned long sr_margin_steps_1g = 62500;
/* Default steps added for less than 1G OPP's is 3 in uV*/
static unsigned long sr_margin_steps = 37500;
Click to expand...
Click to collapse
Does this explain enough for you? Below 1ghz each step is 3.7500, above it is 6.25
You don't get it?
static void sr_add_margin_steps(struct omap_sr *sr)
{
int i;
/*
* Add 5 steps for 1g and 3 steps for other OPP's by default
* REVISIT: Make it configurable through sysfs dynamically
*/
for (i = 1; i <= 3; i++)
sr1_opp_margin = sr_margin_steps;
sr1_opp_margin[4] = sr_margin_steps_1g;
for (i = 1; i <= MAX_VDD1_OPP; i++) {
printk(KERN_INFO "sr1_opp_margin[%d]=%ld\n", i,
sr1_opp_margin);
mpu_opps.sr_vsr_step_vsel = 0x0;
mpu_opps.sr_adjust_vsel = 0x0;
}
printk(KERN_INFO "steps added, volt will be"
"recaliberated automatically\n");
}
Click to expand...
Click to collapse
How did that translate for you? Is that just hardcoded to read the OPP table??? The first three elements in the MPU OPP table are below 1GHZ: 350, 700, 920
The rest is above...
I hope I helped some developers with this.
Since I'm no programmer I'm having a hard time to understand this.
Does it mean smartreflex is not good at all?
For me I hate smartreflex. I always get better battery uptime (especially in standby I get around 0.5% usage per hour) when I undervolt by myself.
When I use smartreflex my usage in standby is about 3 to 5%.
In my opinion smartreflex is for noobs who don't wanna fool around themselves...
Gesendet von meinem Galaxy Nexus mit Tapatalk 2

Some Modifications you can make on your Build.Prop

I found this from freeyourandroid.com thought i would share it. I would happy If an experienced user has anything to say about it:
The following lines in the build.prop file can be added and edited to change several properties in your device:
debug.sf.hw = 1
Render UI with GPU (relieves pressure on CPU)
dalvik.vm.heapsize = 32m
Set size of Dalvik VM heap (how much RAM each instance of the VM is allowed); depending on how much RAM that is available to a device, this can be increased.
persist.adb.notify = 0
Stop debugging icon from appearing in status bar
windowsmgr.max_events_per_sec = 120
Increase to improve scrolling response
persist.sys.use_dithering = 0
Do not use surface dithering (surface dithering improves image quality)
debug.sf.nobootanimation = 1
Disable boot animation
ro.HOME_APP_ADJ = 1
force home launcher into memory
ro.sf.lcd_density = 240
Set screen density; change according to your device or what suits you, a lower value will display more but may be too small to use on a device with a smaller screen. Also note that changing the pixel density will make some applications in the new market ‘incompatible with your device’.
mot.proximity.delay = 150
Lower to fix black screen after calls issue
ro.telephony.call_ring.delay = 0
Decrease dialling out delay
ro.gsm.2nd_data_retry_config = max/_retries=3, 2000, 2000, 2000
Change MMS APN retry timer from 5s to 2s
wifi.supplicant_scan_interval = 120
ro.ril.disable.power.collapse = 0
pm.sleep_mode = 1
Increase battery saving potential
ro.com.android.dataroaming=true
Enables data-roaming by default in the build
ro.com.android.dateformat=dd-MM-yyyy
Changes default date format to day-month-year
ro.config.alarm_alert=*.ogg
ro.config.ringtone=*.ogg
ro.config.notification_sound=*.ogg
Changes the default sounds for each item. Must correlate to ogg files available in /system/media/audio/
ro.build.display.id=NAMEOFROM
In Settings>About Phone, it lists the name of the build number. This is where you set it.
ro.product.locale.language=en
ro.product.locale.region=GB
Sets the default region and language. You must have the correct letter combo, and the language must be available for this to work.
video.accelerate.hw=1 or 0
Whether to use hardware acceleration to render videos, doesn’t work on all devices
** Mind you, my attempt to change failed, because it said "failed to save". You probably wont have this problem.
Some add-ons
Please always do a backup before you made any changes
And try to do it one by one or at least group by group
So you would know which are working and which are not
And easier to revert changes
Good luck
HERE THEY COME:
Improve overall media quality
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Click to expand...
Click to collapse
Qualcomm display settings -- Video acceleration and HW debugging
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.qc.hardware=true
com.qc.hardware=true
Click to expand...
Click to collapse
Increase overall scrool speed
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
Click to expand...
Click to collapse
Touch tuning
touch.pressure.scale=0.001
Click to expand...
Click to collapse
Improve touch responsiveness through Hardware Rendering
debug.sf.hw=1
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
debug.composition.type=cpu
Click to expand...
Click to collapse
According to some CM7 users, it is better for us to add debug.composition.type=cpu, please kindly refer to: http://madteam.co/forum/tutorials/(tut)big-performance-increase-on-cm79/
16 bit transparency
persist.sys.use_16bpp_alpha=1
Click to expand...
Click to collapse
Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=true
media.stagefright.enable-record=true
Click to expand...
Click to collapse
Improve Voice Call Clarity
ro.ril.enable.amr.wideband=1
Click to expand...
Click to collapse
All the credit goes to the OPs of the build.prop shared, I am just sharing what did I learnt from their helpful posts, hope it helps
https://play.google.com/store/apps/...vbS5qcnVtbXkuYXBwcy5idWlsZC5wcm9wLmVkaXRvciJd
Click to expand...
Click to collapse
Try Build Prop Editor to do the things
i thought these links will be a good source to see
http://forum.xda-developers.com/showthread.php?t=1735128
http://forum.xda-developers.com/showthread.php?t=1697040
ro.HOME_APP_ADJ = 1
Click to expand...
Click to collapse
AFAIK this code doesn't work anymore on ICS
** Mind you, my attempt to change failed, because it said "failed to save". You probably wont have this problem.
Click to expand...
Click to collapse
have you set your permission R/W ?
windowsmgr.max_events_per_sec = 120
Increase to improve scrolling response
I heard that the value still can be increased into 250 for single-core processor device. And on my phone the value is 250

Paranoid Android w/Franco.kernel, first impressions

Hi all,
with this post I want to suggest a configuration for those who want to give a boost to their GN and also want to have good battery life and a better look.
I've tried out Paranoid Android 3.15 (JB 4.2.2) rom on my GN with the latest GApps, flashing the kernel with the one provided by Francisco Franco (franco.kernel). This kernel gave a new life to my battery (-1% per hour with screen off).
Thanks to a previous post in this forum, I also modified some settings in the Francisco Franco update app:
Max Frequency: 1305 MHz
Min Frequency: 192 MHz
Governor: interactive
Governor Tunables: 15000 / 95 / 729 MHz / 45000 / 15000 / 85
IO Scheduler: row
IO Scheduler Tunables: 100 / 75 / 5 / 4 / 4 / 3 / 2 / 15 / 25
Read Ahead Buffer: 512; NR Requests: 512
TCP Congestion Avoidance Algorithm: westwood
Color Multipliers: 190 195 215
RGB Gamma: -4 0 5
Trinity Contrast: -5; OMAP4 Gamma: Disabled; CAB: Disabled
Click to expand...
Click to collapse
With his stock kernel, the PA rom is good and responsive; Franco.kernel gave a boost to my GN wich is now way faster and with smooth transitions. Before changing the kernel, the AnTuTu score was of approx 5300 points. With Franco's one the score was of 8000 points (see attached screen).
I've also installed Holo Glass (beta) Theme (which I suggest, it's beautiful and lightweight), using it with the Phablet option provided by PA (just ignore and apply when prompted to leave or continue anyway applying the theme, in use there are no particular issues).
I'm a newbie of the forum so I cannot insert links to post screenshots, so I upload a zip with the screens.
Now try doing some bluetooth streaming to your car stereo at that lower frequency - you'll hear a faint noise coming your phone as it squeals with pain and anguish.
Those are my settings taken directly from my settings post. Quote me properly or give me credit next time please.
just read your post. yesterday i installed PA 3.15 with Franco 376 and it my battery got drained. maybe i want to apply your setting to trickstermod. thanks...

Categories

Resources