I think i found a solution for the colors!!!,
I could remember from my Ipaq 5450 an old registry hack to speed up the 5450, you can set the colors to a lower level and then speed up you're ppc with it.
Now, when i opened the key with an registry editor, there was a value of 8192, that means the Qtek 2020 could not handle more then 8196 colors because of this key, so i changed it to 65536, and i think it worked, i cannot check only I don't see many differences, but i think the colors are better now.
So,
Install the attached PHM Registry Editor, and open it.
Browse to HKEY_LOCAL_MACHINE\SYSTEM\GDI\GLYPHCACHE\
You can change the "limit" value :
to any logical color so you can use the following value's the higher the value the slower you're xda becomes:
2
4
8
16
32
64
128
256
512
1024
2048
4096
8192
16384
32768
65536
Good Luck!
If this registry hack damages you're PPC or Qtek 2020 or any other Device i'm not responsable, but i don't think it's gonna damage you're ppc
Unfortunately I don't see any difference,this let me think about that Reg value doesn't work.(65536)
Can't confirm it's working...
1. XDAIIs have 16 bit/65536 colour displays - 13bits is not stamdard.
2. Color depth is display-dependent (I have 12/4096).
3. My registry shows 8192, too, but this cant be same for bot XDA and XDAII.
The registry entry sounds more like a limit of graphic cache - this way of course if you decrease the number it would speed the system up. :?
This switch does nothing to color limit. It is just a glyph cache size:
MSDN quote:
"The HKEY_LOCAL_MACHINE\System\GDI\GlyphCache registry key specifies the size limit for character glyphs.
...
To set the size of the glyph cache, use the HKEY_LOCAL_MACHINE\System\Gdi\Glyphcache registry key. This key is read only when the OS boots.
The following example shows how to set the size of the glyph cache.
HKEY_LOCAL_MACHINE\System\Gdi\Glyphcache
"limit"=DWORD:x
The value specified for the limit is the size in bytes of the glyph cache per realized font. This number is automatically multiplied by 4 for antialiased fonts.
A realized font is any unique combination of font, height, weight, and effects (for example, outline or emboss). A font is realized the first time an application uses it for drawing, and is unrealized when the application deletes the HFONT."
Мамаич, я тут че-то не врубился: что за глиф кэш такой?
Are you guys sure abt this?....but by the looks of the screen, the colors are 65K type.
If you are talking about my point "12/4096", it only applies to XDA1.
XDA2s have 16/65k displays.
The number discussed in this topic looks like some kind of cache size...
So,do you think 8192 is quiete good value or need to be increased?
Regards,
Been using 65536 for my GlyphCache from day one. This has got nothing to do with colours but it speeds up your display rendering.
Battery life depletes faster.
increasing this value is recommended if you use Asian fonts. You can also increase it for font-intensive applications (for example if you read text files written in several fonts). I think that 8192 is large enough, but you can try to test different values with SPB benchmark. I don't think that increasing over 16384 would give much speedup.
2 bob190cm: Please write in english, it is an "official" language of this forum.
As you wish, Mamaich the Official!
So, what exactly is the GlyphCache? :?:
bob190cm said:
So, what exactly is the GlyphCache? :?:
Click to expand...
Click to collapse
As far as I remember, when OS renders a character of a truetype font with given name, size, bold/italic/etc parameters it first renders it to a bitmap. And these bitmaps are cached to speedup performance. This registry value determines the size of such cache.
OK! Got it.
Thanx!
I've traditionally kept my heap for other Android devices at 32MB. I've noticed with the Charge that it defaults to 48mb for Froyo and 64 for the newer GB releases. I've also noticed that putting it back to 32 seems to stop the home screen from continuously redrawing and a couple of other issues. Is there any downside to having a slightly smaller heap?
The way I understand it is it's for more performance when we use apps that require more memory. I keep mine at 40.
Where can you change the heap size?
It's in build.prop
I just use the VM Heap Tool, saves messing around in SQLite Editor.
I just use script manager.
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
What is the optimal VM Heap size for our phone?
I am running Sky ICS 4.4 rom and the Vm is set at 72m.
how much you is VM heap size ?
Stock ICS has 120+ MB VM heap size
bump ....