I deleted SetCPU and SD Card Boost, installed Rom Toolbox since it has a lot of features including CPU slider.
ROM: Gummy Froyo 2.2
My Settings
CPU 1400 / 100 min / smartass
Build Prop Tweak:
VM Heap: 96m
Max Events: 60
Auto Memory Manager:
Preset: Mild
Foreground Apps: 1MB
Visible App: 3MB
Secondary Server: 78MB
Hidden App: 78MB
SD Boost: 2048kb
Sysctl Tweaks
Min Free Kbytes: 2746
Dirty Ratio: 90
Dirty Background Ratio: 65
VFS Cache: 25
Oom Kill Allocating Task (unchecked)
Problem:
Phone freezes when playing games such as GT Free+ HD and Homerun Battle 3D
I don't play games but my
vm heap 80m
max events 150
memory 10mb
16mb
24mb
48mb
52mb
72mb
sd boost
2048kb
min free 2098
dirty ratio 65
dirty backround 35
vfs cache 48
oom checked
Thanks. Anyone else?
Sent from my SCH-I510 using XDA App
Though you may have a newer and more powerful 1GHz processor, otherwise your phone is not unlike the HTC Evo 4G. Give the following a try. A bit of it will seem quite unorthodox, but I believe that you may be stunned by the improvement:
My Settings
CPU 1400 / 100 min / smartass
Build Prop Tweak:
VM Heap: 48m (or 64MB works well, too)
Max Events: 150
Auto Memory Manager:
Preset: Mild
Foreground Apps: 6MB
Visible App: 12MB
Secondary Server: 40MB
Hidden App: 60MB
Content Provider: 80MB
Empty Application: 100MB
SD Boost: 2048kb
Sysctl Tweaks
Min Free Kbytes: 8192
Dirty Ratio: 95
Dirty Background Ratio: 60
VFS Cache Pressure: 200
Oom Kill Allocating Task (unchecked)
Good luck!
What about for a LG G Stylo LGMS631
I would really love to see this on our phones:
http://forum.xda-developers.com/showthread.php?t=1543892
is it possible with our AOKP and CM9 builds? can a Dev please make this possible? as i think the size of our screen can really work this one out!
what do you think...
wow no one seems to care about this one....?
Looks like its just changing the DPI to one that is recognized as a tablet. Seems it's 129 for the GNex... he posted something showing a formula for finding the "magic number" for other devices.
From his post:
Code:
int shortSizeDp = shortSize * DisplayMetrics.DENSITY_DEFAULT / DisplayMetrics.DENSITY_DEVICE;
mStatusBarCanHide = shortSizeDp < 600;
full description here: http://baroqueworksdev.blogspot.com/...ice-cream.html
nexus has a width of 720 and a density of 320. shortSizeDp = 720 * 160 / 320 = 360. lower than 600, phone mode.
now put the dpi to magic number 192. shortSizeDp = 720 * 160 / 192 = 600. tadaaa, tablet mode.
Click to expand...
Click to collapse
Edit: It's also using a modded nova launcher. Not sure, however, I don't see why the launcher wouldn't work for us.
In fact, I just spent a little more time looking through this and I think it will work close to 100% with CM9 or AOKP roms. Hmmmm, just gotta find out the right DPI. (I haven't bothered, busy at work.)
Looking at DisplayMetrics:http://developer.android.com/reference/android/util/DisplayMetrics.html
There are a few preset densities which may interest us:
DENSITY_DEFAULT = 160
DENSITY_HIGH = 240
DENSITY_LOW = 120
DENSITY_MEDIUM = 160
Assuming that the above values holds true to the Sensation, then the following would give a 600 output:
DENSITY_DEFAULT = 160 (540 * 160 / 144 = 600)
DENSITY_HIGH = 240 (540 * 240 / 216 = 600)
DENSITY_LOW = 120 (540 * 120 / 108 = 600)
DENSITY_MEDIUM = 160 (540 * 160 / 144 = 600)
Still checking it out!
EDIT: Additional info - DENSITY_DEFAULT is directly linked to DENSITY_MEDIUM (DENSITY_DEFAULT = DENSITY_MEDIUM) so that explains why changes to DENSITY_MEDIUM affect the OS system wide (Not sure if this is the case in all ROMs).
Still checking, but bed time for me!!!.........
Seems we also need a modified services.jar
There is some info here: http://forum.xda-developers.com/showthread.php?t=1467051
Thread here for AOKP B33: http://rootzwiki.com/topic/23418-mod-tabletui-for-240-dpi-legacy-devices-aokp-b32b33/
Instructions state: Set density to 128 MAX & Tablet mode will be automatically activated However, since our Sensations have a screen width of 540, not 480 as most legacy devices, we may still need to find that "Magic Number"
Haven't tried it as i'm not running an AOKP based ROM but we need to know what to change in services.jar and then this should be able to be implimented in all ROMs!
Hope this helps
EDIT: The services.jar above uses the following formula: (480 * 160 / 128 = 600)
We should be able to do it using (540 * 160 / 144 = 600) 144 MAX - However, it wont hurt to try 128 since our device has a default density of 240?!
Also, don't forget to set your Font size to huge (or large) in ROM Control.
I have created a flashable zip for AOKP B33/34 which includes a Patched Launcher, Phone, Market & services.jar.
This should work on all AOKP ROMs!
This should also parse the build.prop and adjust your LCD Density to 128.
Also, don't forget to set your Font size to huge (or large) in ROM Control prior to flashing this.
I haven't tested this - I have created it blind so if you are going to try it then please make a nandroid backup first!!!
Should you try it, then Please leave feedback but don't get upset if it doesn't work for you - If it doesn't work then just restore your nandroid backup!
I hope this is of some use to someone
BTW: Flash using recovery!
If you're colorblind, please disregard this thread. Rate this thread to express how you deem the color saturation and accuracy of the OnePlus 2's display. A higher rating indicates that you think that color accuracy is very high and saturation is excellent.
Then, drop a comment if you have anything to add!
Anandtech frowns on the greys
XDA_RealLifeReview said:
If you're colorblind, please disregard this thread. Rate this thread to express how you deem the color saturation and accuracy of the OnePlus 2's display. A higher rating indicates that you think that color accuracy is very high and saturation is excellent.
Then, drop a comment if you have anything to add!
Click to expand...
Click to collapse
According to Anandtech the accuracy of colour is not very good, especially in the greyscale range. Also, he says that it is a little too blue even otherwise. Does anyone here have any different opinions?
(Can't post the link here yet)
Color saturation is very poor, as I have switched from Xiaomi Mi4 it looks as if colors are washed off.
The stock calibration is too bleak for my taste. I added a little more contrast and saturation. It's android after all
Coming from the Galaxy Note 2 and LG G3, I'd say the colors are great. Not insane like on Galaxy phones though, but much better than on LG G3. For blue/red, the color temperature is settable even on the stock OxygenOS. It appeared too warm at first, so I sent the dial almost all the way to "cool" to get what seemed like a correct white color.
I had note4 and oneplue 2 color saturation is very bad.
Using Boeffla kernel I managed to get this display almost perfect concerning whitebalance and colors.
How about lets see some display settings you guys used to improve color/image quality
I find the screen too cool (I came from a s6 which i found too warm).
Would love to see some settings too.
tlxxxsracer said:
How about lets see some display settings you guys used to improve color/image quality
I find the screen too cool (I came from a s6 which i found too warm).
Click to expand...
Click to collapse
for me by far, the best display is Samsung AT&T Captivate, no phone had reached my expectations until now. I'm satisfied with OnePlus 2. I would be happy if someone shared KCAL settings.
Hi i'd like to have a screen like Samsung Phones with good saturation and good contrast. How can I do for changing those option(If I need boeffla kernel how can I configure the app for having à magnific screen?)
(I haven't installed yet but I will do it soon)
Thanks
As a happy owner of a x-rite ColorMunki, I've managed to find the time to run some tests on the phone screen and find a suitable configuration for Boeffla Kernel's color settings.
First, some values for the un-calibrated display, with the default configuration (rgb 255, saturation 255, hue 0, display value 255, contrast 255) and maximum brightness:
Black level = 0.2751 cd/m^2
50% level = 122.72 cd/m^2
White level = 578.07 cd/m^2 (quite close to the 600 cd/m^2 that OnePlus claims)
Approx. gamma = 2.24
Contrast ratio = 2101:1 (am I mistaken or OnePlus claimed "only" 1500:1??)
White chromaticity coordinates 0.2896, 0.3019
White Correlated Color Temperature = 8532K
Gamut coverage: 90.1% sRGB (not great)... http : // imgur. com /wb8kylH ... sorry but I can't post proper links yet.
Extremely "cold" color setting, with a quite remarkable contrast ratio and decent brightness. I'm quite impressed by this display!
To achieve a D65 (6500K) whitepoint and 2.2 gamma, as per sRGB standards, I've used the following settings:
red: 255
green: 233
blue: 159
saturation: 255
hue: 0
display value: 260 (it basically affects the gamma)
contrast: 255
resulting in:
Black level = 0.2804 cd/m^2 (shouldn't change)
50% level = 122.72 cd/m^2 (dictated by the gamma)
White level = 517.92 cd/m^2 (lost some brightness, unavoidable)
Approx. gamma = 2.19 (much closer to 2.2)
Contrast ratio = 1847:1 (I can live with that!)
White chromaticity coordinates 0.3121, 0.3288
White Correlated Color Temperature = 6540K
In my opinion, increasing the saturation above 255 is counter-productive, as it will only result in clipping. Furthermore, the vast majority of media content (unless you're working with professional Adobe RGB-based workflows) has most likely been designed for sRGB devices - or at least something with comparable gamut coverage. AMOLEDs are exceptional in terms of "color richness", but might result - if not properly calibrated - in unrealistic over-saturated colors.
The side-effect of these settings is the appearance of banding in images with blue gradients, such as... blue skies. I'm afraid, though, that this can't be solved in any way.
Cheers
GiMo84 said:
As a happy owner of a x-rite ColorMunki, I've managed to find the time to run some tests on the phone screen and find a suitable configuration for Boeffla Kernel's color settings.
First, some values for the un-calibrated display, with the default configuration (rgb 255, saturation 255, hue 0, display value 255, contrast 255) and maximum brightness:
Black level = 0.2751 cd/m^2
50% level = 122.72 cd/m^2
White level = 578.07 cd/m^2 (quite close to the 600 cd/m^2 that OnePlus claims)
Approx. gamma = 2.24
Contrast ratio = 2101:1 (am I mistaken or OnePlus claimed "only" 1500:1??)
White chromaticity coordinates 0.2896, 0.3019
White Correlated Color Temperature = 8532K
Gamut coverage: 90.1% sRGB (not great)... http : // imgur. com /wb8kylH ... sorry but I can't post proper links yet.
Extremely "cold" color setting, with a quite remarkable contrast ratio and decent brightness. I'm quite impressed by this display!
To achieve a D65 (6500K) whitepoint and 2.2 gamma, as per sRGB standards, I've used the following settings:
red: 255
green: 233
blue: 159
saturation: 255
hue: 0
display value: 260 (it basically affects the gamma)
contrast: 255
resulting in:
Black level = 0.2804 cd/m^2 (shouldn't change)
50% level = 122.72 cd/m^2 (dictated by the gamma)
White level = 517.92 cd/m^2 (lost some brightness, unavoidable)
Approx. gamma = 2.19 (much closer to 2.2)
Contrast ratio = 1847:1 (I can live with that!)
White chromaticity coordinates 0.3121, 0.3288
White Correlated Color Temperature = 6540K
In my opinion, increasing the saturation above 255 is counter-productive, as it will only result in clipping. Furthermore, the vast majority of media content (unless you're working with professional Adobe RGB-based workflows) has most likely been designed for sRGB devices - or at least something with comparable gamut coverage. AMOLEDs are exceptional in terms of "color richness", but might result - if not properly calibrated - in unrealistic over-saturated colors.
The side-effect of these settings is the appearance of banding in images with blue gradients, such as... blue skies. I'm afraid, though, that this can't be solved in any way.
Cheers
Click to expand...
Click to collapse
Ive tried these settings and it just made my screen really yellow and warm, I still prefer using the "extreme amoled" setting listed in AK's kernel thread.
tofuboi01 said:
Ive tried these settings and it just made my screen really yellow and warm, I still prefer using the "extreme amoled" setting listed in AK's kernel thread.
Click to expand...
Click to collapse
Well, all displays differ physically... but most importantly it's a matter of personal preference.
Personally, I am accustomed to the "yellow and warm" display (I'd find the default settings way too cold and blue ) as it matches every other screen that I have around me, and I find it appropriate to rely on an industry-standard color space/calibration. At this point, I can blame the content creator (i.e. whoever took the picture/drew the image) for not using sufficient saturation .
GiMo84 said:
Well, all displays differ physically... but most importantly it's a matter of personal preference.
Personally, I am accustomed to the "yellow and warm" display (I'd find the default settings way too cold and blue ) as it matches every other screen that I have around me, and I find it appropriate to rely on an industry-standard color space/calibration. At this point, I can blame the content creator (i.e. whoever took the picture/drew the image) for not using sufficient saturation .
Click to expand...
Click to collapse
I am using your screen value, contract and saturation setting though, it makes a change from the extreme amoled look but using opposite colours, R:235,G:245,B:256. I prefer cooler/whiter looking screen i guess haha.
Rooted, flashed boeffla kernel, installed boeffla app and adjusted color, saturation and gamma. Looks better than any other 1080p for me now.
tofuboi01 said:
Ive tried these settings and it just made my screen really yellow and warm, I still prefer using the "extreme amoled" setting listed in AK's kernel thread.
Click to expand...
Click to collapse
I cannot find the thread
alexferdean said:
I cannot find the thread
Click to expand...
Click to collapse
AK kernel thread is closed as the developer switched phones but if you go onto the thread over at original development AK kernel and look at post 2, there's a list of kcal settings.
kimas65 said:
I had note4 and oneplue 2 color saturation is very bad.
Click to expand...
Click to collapse
which is the best phone overall?? i have a note 4 and im thinking to buy oneplus 2
The Funky Pear said:
which is the best phone overall?? i have a note 4 and im thinking to buy oneplus 2
Click to expand...
Click to collapse
Stay with note 4
Sent from my A0001 using Tapatalk
Solution 1:
It is well known that custom third-party kernels have a screen-shaping function, which is the legendary KCAL.
We can reduce all RGB channels. The default RGB channels in the kernel are three groups of [0-256] digits. We can reduce the numbers of these three groups by 10-20, that is, 240 240 240 or 245 245 245. The result of this is light transmission and reduced brightness. However, the reduced brightness is completely unperceivable to the human eye.
Modifying the screen parameters through the kernel does not affect performance at all. This is achieved by modifying the MIPI displayerial interface specification (which can be understood as the display interface processor)
Afterimages have been on screen for more than a year:
240 240 240 (this configuration can greatly reduce the residual image!)
Slightly ghosting screen:
245 245 245 (this configuration allows the screen to see no ghosting!)
New screen:
247 247 247 (This configuration allows the screen to never produce ghosting!)
A kernel adjustment software is provided in the JZ kernel. My kernel has limited the RGB maximum value to 248 250256. At present, only the JZ kernel supports mutations in the G5. Below I have provided a download address or modification through the kernel adiutor.
In addition, synaptic support is related to the kernel. Scripts and resource files are in the kernel. Therefore, downloading a synapse on the Internet is as easy as flashing the supported kernel.
JZ kernel supports both English and Chinese synpase!