[Test][Tweak] Force HDPI images and better performance - GT540 Optimus Android Development

Hi guys could some of you test this on your roms to see if it work or not i have tested and i will not tell you what i think because i don't want to plant a seed in you heads to fool you that it works or not i will ask you to post your thoughts
Installation use root explorer and goto your build.prop copy what you see below and past it into it once you have done that reboot your phone.
Code:
# Increase overall responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
debug.composition.type=hdpi
hs.systemserver=16m
hs.app.process=16m
hs.su=8m
hs.app_process=16m
btw i got these setting out of this rom's build.prop
http://forum.xda-developers.com/showthread.php?t=1294593
Thanks and hope to here you thoughts soon

What changes will did do to our phones???
is there a chance of stuffing up??

androidboss7 said:
What changes will did do to our phones???
is there a chance of stuffing up??
Click to expand...
Click to collapse
Try them and see mate and no theres no way of stuffing up.
Sent from my GT540 using xda premium

hmm what does it really do dont think you will say but cmon give some leeway cant really try now. choosing between froyo optimum 4.55 or aosp 4.2

ok guys this is what i think it does but im still researching
Increases touch performance
debug.performance.tuning=1
video.accelerate.hw=1
Forces HDPI icon/images if available
debug.composition.type=hdpi
Gives system binary's extra memory to run applications and superuser su file
hs.systemserver=16m
hs.app.process=16m
hs.su=8m
hs.app_process=16m
for me it seems to make my phone faster and more responsive.

eoghan2t7 said:
ok guys this is what i think it does but im still researching
Increases touch performance
debug.performance.tuning=1
video.accelerate.hw=1
Forces HDPI icon/images if available
debug.composition.type=hdpi
Gives system binary's extra memory to run applications and superuser su file
hs.systemserver=16m
hs.app.process=16m
hs.su=8m
hs.app_process=16m
for me it seems to make my phone faster and more responsive.
Click to expand...
Click to collapse
yes for me too it seemd lil bit faster but hdpi pictures ? no changes maybe theyre not available

install a theme that has mdpi an hdpi support and see if the hdpi icons get used if your on a aosp rom you wont get the hdpi icons due to the framework only have mdpi one's

eoghan2t7 said:
install a theme that has mdpi an hdpi support and see if the hdpi icons get used if your on a aosp rom you wont get the hdpi icons due to the framework only have mdpi one's
Click to expand...
Click to collapse
theme ? im on cyanogenmod 6 ;D

haha then update to CM7 lol

eoghan2t7 said:
haha then update to CM7 lol
Click to expand...
Click to collapse
no xD i like froyo more but I often think of it.. but froyo works just much faster i think i will upgrade in some weeks but i guess i will return to utopia or optimum ;P

just wait for pcfighters rom to be more update to the same standard as mur4iks rom then update to that, that rom will become a beast in the optimus

eoghan2t7 said:
just wait for pcfighters rom to be more update to the same standard as mur4iks rom then update to that, that rom will become a beast in the optimus
Click to expand...
Click to collapse
yes i tested it too its really good work hope it will get off the bugs and it becomes fastest rom

eoghan2t7 said:
Installation use root explorer and goto your build.prop copy what you see below and past it into it once you have done that reboot your phone.
Code:
# Increase overall responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
debug.composition.type=hdpi
hs.systemserver=16m
hs.app.process=16m
hs.su=8m
hs.app_process=16m
Thanks and hope to here you thoughts soon
Click to expand...
Click to collapse
How do i go to build.prop??
And what do i copy on to??
EDIT : I KNOW NOW!!!!

I didn't try them yet.
But, video.accelerate.hw=1 will make the phone use GPU for video playback. This should be the default in most devices. It will fail on ROMs with no GPU drivers.
Forcing HDPI themes onto a MDPI device is NOT a GOOD idea.
HDPI and MDPI refer to the pixel density of the screen. This is a hardware limitation. In other words 320x480 pixels on a 4.2' screen as in GT540 is MDPI. This will create some issues.
1) Performance hit. Images need resources to render. Larger the image and more the pixels, more the resources it needs. An MDPI device should handle MDPI fine but forcing HDPI on it is not. This is more or less like trying to play 720p HD video on our GT540.
2) MDPI is MDPI. HDPI is HDPI. HDPI images are larger and have more pixels(and so have more detail.) But, the MDPI display can only display select number of pixels. This means images would become larger than they should be.
ie on a 300dpi device, a square inch image needs root(300) pixels on each side. On a 100dpi device, a square inch needs 10 pixels on each side per inch. root(300) is larger than 10. In other words, a 1inch HDPI image will take more than 1 inch space on MDPI device.
3) HDPI to MDPI downscaling will not be efficient on a low-end phone.
So, if you want HDPI themes on a MDPI device, the best way is to port the theme. This shouldn't be hard. Extract apk. Edit XMLs and folders replacing hdpi with mdpi. Open up images in a good image editor and downscale them to relevant MDPI resolutions. Compile and resign apk. We are done. =D

I tried the tweak and i feel no difference. No HDPI icons as well as no performance boost. Using Swiftdroid 2.0 RC5

How can i try it with mdpi settings ?
bcoz gamevil games doesnt recognize my hvga screen and maybe this solve the problem
Sent from Tapa-tapitas.

Ok i tried this now!!
Can;t really tell!!!

Yer .... non of these additions to build/system/default .prop will change performance on the devices
For example
debug.composition.type
is a flag for QC devices to set there composition type ... valid values are
cpu / gpu / c2d NOT hdpi mdpi ect
these will do nothing to affect device performance and any affect seen is just a placebo

Related

Q & A's - OverClocking the Tattoo

Will overclocking make the tattoo run smoother? in terms of the live wallpapers cause most the live wallpapers run abit slow.
Running - SP-FroYo_v2.2.1
vura said:
Will overclocking make the tattoo run smoother? in terms of the live wallpapers cause most the live wallpapers run abit slow.
Running - SP-FroYo_v2.2.1
Click to expand...
Click to collapse
I think the main pbs are missing VGA, resolution and OpenGL. Overcloking isn't stable, it causes freeze... and you damage the hw. I think live wallpaper need to be rescaled to work.
francians said:
I think the main pbs are missing VGA, resolution and OpenGL. Overcloking isn't stable, it causes freeze... and you damage the hw. I think live wallpaper need to be rescaled to work.
Click to expand...
Click to collapse
ok thnx for explaining so overclocking is a no go.
so is there a way to rescale the live wallpapers to fit the tattoo?
vura said:
ok thnx for explaining so overclocking is a no go.
so is there a way to rescale the live wallpapers to fit the tattoo?
Click to expand...
Click to collapse
hi
in future pls put ur Questions here : http://forum.xda-developers.com/showthread.php?t=716282
Thread closed as the questioned is answered

Improve 2d performance?

Hi there.
Well I found a couple of threads on how to improve 3d graphics performance but nothing on 2d which is more important to me. So that's why Im asking you guys if anybody knows anything please do let me know even a tinny bit of help would be absolutely appreciated. Cheers !!!
Sent from ...... (guess)
does anybody have any idea ???
OC? or chainfire 3D?
Sent from my GT-P6200 using Tapatalk 2
cheers mate.
but I was thinking of something like tweaks or adreno libs or some sort of script or hardware acceleration or kernel stuff or... not chainfire or oc (overclocked to 980mhz, well it did make stuff a bit smoother but I can't keep it that high, phone will simply melt down, why should we even have to overclock, that just shows the weakness of the OS, 800mhz should be enough to process simple 2d stuff )
Something that could actually make a difference, I'm starting to get fed up with android, my ace originally runs at 800mhz but an iPhone 3gs runs at 600mhz and it doesn't lag as much (in fact it doesn't lag at all, it has less ram than ace)
thanks anyway
Find this line in build.prop
Debug.sf.hw=1
And change it to
#debug.sf.hw=1
already done that, dunno may be it makes things a bit smoother but I didn't notice it so much. thank you very much anyway
Sikorsky96 said:
cheers mate.
but I was thinking of something like tweaks or adreno libs or some sort of script or hardware acceleration or kernel stuff or... not chainfire or oc (overclocked to 980mhz, well it did make stuff a bit smoother but I can't keep it that high, phone will simply melt down, why should we even have to overclock, that just shows the weakness of the OS, 800mhz should be enough to process simple 2d stuff )
Something that could actually make a difference, I'm starting to get fed up with android, my ace originally runs at 800mhz but an iPhone 3gs runs at 600mhz and it doesn't lag as much (in fact it doesn't lag at all, it has less ram than ace)
thanks anyway
Click to expand...
Click to collapse
hmm.. you know that iphone 3GS has a PoverVR GPU ? i think it is better than our ace's GPU (adreno200) .. and their CPU is CortexA8 ! it is just underclocked..
kevintangi said:
hmm.. you know that iphone 3GS has a PoverVR GPU ? i think it is better than our ace's GPU (adreno200) .. and their CPU is CortexA8 ! it is just underclocked..
Click to expand...
Click to collapse
___________________________________
Yep, but still the hardware on our ace isn't as shi* as you think I mean come on its 2d, I am not even on about 3d. There is gotta be a way. I ran a benchmark (quadrant) on cm9 2d was like 65 fps and on cm7 its like 35. wtf. but the 3d (the 3D graphics) is as smooth as hell. what kinda thing is this that can process 3d but not 2d.
cheers!!!!
Sikorsky96 said:
___________________________________
Yep, but still the hardware on our ace isn't as shi* as you think I mean come on its 2d, I am not even on about 3d. There is gotta be a way. I ran a benchmark (quadrant) on cm9 2d was like 65 fps and on cm7 its like 35. wtf. but the 3d (the 3D graphics) is as smooth as hell. what kinda thing is this that can process 3d but not 2d.
cheers!!!!
Click to expand...
Click to collapse
well.. if i may know.. why u need 2D that much ? i have no other ideas installed adrenaline engine ?
kevintangi said:
well.. if i may know.. why u need 2D that much ? i have no other ideas installed adrenaline engine ?
Click to expand...
Click to collapse
_________________________________________
Yep, but doesn't have any effect on 2d.
well I used to play games a lot I mean games like bia2 or nova even dead space, why can our ace process all these 3d stuff with no problem or with the least problems (i mean i wouldn't even expect ace to run dead space have you seen the graphics ??? ) but cant process simple 2d graphics.
I just wanna open up my app drawer and scroll between pages and have no lag i have tried different launchers (go, holo, qq ...) or the phone lags if I scroll down in the settings menu wtf there is literally nothing there but text and a black background.
_________________________________________
surely this is a software issue
Sikorsky96 said:
_________________________________________
Yep, but doesn't have any effect on 2d.
well I used to play games a lot I mean games like bia2 or nova even dead space, why can our ace process all these 3d stuff with no problem or with the least problems (i mean i wouldn't even expect ace to run dead space have you seen the graphics ??? ) but cant process simple 2d graphics.
I just wanna open up my app drawer and scroll between pages and have no lag i have tried different launchers (go, holo, qq ...) or the phone lags if I scroll down in the settings menu wtf there is literally nothing there but text and a black background.
_________________________________________
surely this is a software issue
Click to expand...
Click to collapse
umh, yea.. maybe software issue, btw this always happens in all roms ? mine doesnt seem so ? i think it is ur min CPU freq ? no ?
really, mine doesnt lag at all. some lags do occur when i run several apps at once (tapatalk, opera mini, sms, twitter) at the same time.
side_effect said:
Find this line in build.prop
Debug.sf.hw=1
And change it to
#debug.sf.hw=1
Click to expand...
Click to collapse
It won't change/do anything. Here is link to Android source code.
kevintangi said:
umh, yea.. maybe software issue, btw this always happens in all roms ? mine doesnt seem so ? i think it is ur min CPU freq ? no ?
really, mine doesnt lag at all. some lags do occur when i run several apps at once (tapatalk, opera mini, sms, twitter) at the same time.
Click to expand...
Click to collapse
____________________________
My governor is always set to performance. i've tried min 480 and 245 no dif.
performance doesn't really drain my battery and my phone doesn't get as hot as before, interactive works well too
well think about, cm9 65fps cm7 35fps. its definitely software issue our poor ace has good hardware but not the software it deserves.
what are your suggestions people ???? we gotta find a way.
For settings scroll lag, disable scrolling cache! It helps a lot!
galaxyace152 said:
For settings scroll lag, disable scrolling cache! It helps a lot!
Click to expand...
Click to collapse
_______________________
cheers, but still not quite there. Have you tried cm9 ??? scroll down and you will see what I mean. It's the true meaning of smoothness (in terms of scrolling not ...
_______________________
by the way what is the build.prop code for scrolling cache ???
waiting waiting waiting .... 2 years later still waiting .... 10 years later still waiting .... 30 years later dead by that time
Sikorsky96 said:
waiting waiting waiting .... 2 years later still waiting .... 10 years later still waiting .... 30 years later dead by that time
Click to expand...
Click to collapse
well, here's my opinion about "our-mighty" lag problem.
1. android bellow 3.0(1.5 - 2.3.7) is not using hardware to render UI, it use software rendering instead, so this explain why iPhone 3G(128MB ram, 434Mhz ArmV6, PowerVR MBX<==same GPU as nokia N95) UI scrolling is waaayyy smoother than SGA. even galaxy note is doesnt as smooth as iPhone 3g.(stock GB firmware)
2. android 3.0 & 4.0 is render UI with GPU, BUT some kind of thread-that-response-for touch is not on the TOP PRIORITY, this explain why ICS is lag...specially for our device, and ICS from maclaw is still have some graphical glitches.
3. wanna smooth UI?? try JB alpha.....i think there is no solution for LAG, at least at the moment......
123r4ka456 said:
well, here's my opinion about "our-mighty" lag problem.
1. android bellow 3.0(1.5 - 2.3.7) is not using hardware to render UI, it use software rendering instead, so this explain why iPhone 3G(128MB ram, 434Mhz ArmV6, PowerVR MBX<==same GPU as nokia N95) UI scrolling is waaayyy smoother than SGA. even galaxy note is doesnt as smooth as iPhone 3g.(stock GB firmware)
2. android 3.0 & 4.0 is render UI with GPU, BUT some kind of thread-that-response-for touch is not on the TOP PRIORITY, this explain why ICS is lag...specially for our device, and ICS from maclaw is still have some graphical glitches.
3. wanna smooth UI?? try JB alpha.....i think there is no solution for LAG, at least at the moment......
Click to expand...
Click to collapse
___________________________________________
cheers, but :crying: :crying: :crying: :crying: ...
Does the JB alpha drain battry as fast as The ics ???? or its been fixed i was gonna try it but you know its alpha so thought may be later.
i'll give you a thank tomorrow i'm limited to 8 thanks a day What the actual Fuc*.
___________________________________________
And to all the devs out there is there anyway to do this, and is there a way to make this bloody useless OS to use hardware to render UI.
and is cm9 or 10 ever actually gonna be official for ace ??? i don't think so!!! is it???
Sikorsky96 said:
___________________________________________
cheers, but :crying: :crying: :crying: :crying: ...
Does the JB alpha drain battry as fast as The ics ???? or its been fixed i was gonna try it but you know its alpha so thought may be later.
i'll give you a thank tomorrow i'm limited to 8 thanks a day What the actual Fuc*.
___________________________________________
And to all the devs out there is there anyway to do this, and is there a way to make this bloody useless OS to use hardware to render UI.
and is cm9 or 10 ever actually gonna be official for ace ??? i don't think so!!! is it???
Click to expand...
Click to collapse
i think android wasnt that bad......well, compared to BB OS, and symbian
ICS alpha is not for daily use, at least, it will show you smoother UI, and you can wait for next release.
dont bother to thanks me bro
always happy to help ppl.....

Project Butter on android 4 possible on GB?

Does any dev know if it is possible on Gingerbread to use this "technology" to create "buttersmooth" refresh rates using vsync and videobuffer?
Thank
This is what i know accurate as per my HW knowledge multiplied by driver programing experiences.
Phones' LCD hw as per resolution doesnt support Vertical Sync more than 65Hz. Although LG has used 75Hz to all LG devices. Increasing Vertical Sync only gives high benchmarks by false 2D/3D results. Increasing HW Vertical Sync HZ rather than supported by phone actually worsens performance, needless to mention in longer run it damages LCD controllers. Phone LCD supports max 65HZ refresh rate thats what called VSync(Virtical Sync).
FramBuffer refresh rate is another story. We can setup kernel kill fd signal(SIG KILL) to specific ms to refresh forcefully kill and restart framebuffer artificially but that will gives blinking display. I am already done with FB refresh rate
Sent from my LG-P990 using Tapatalk 2
But spica surely it works in a similar way to PCs? I.e the Vsync is only set to the max possible frame render of the display, e.g. a 60HZ monitor will sync at 60FPS where Vsync will kick in if enabled... you can also do this for any refresh rate like the newer 120hz monitors.
Wouldnt it simply require changing the variables to acknowledge this extra hz in our displays?.
Just curious, probably wrong but it would be nice if it were true as it would be even easier .
Project butter also uses both the CPU and the GPU to render frames. Its switches between the 2 and one can "prepare" while the other one is still being used to render
Sent from my LG-P990 using xda app-developers app
Chris4evernoob said:
Project butter also uses both the CPU and the GPU to render frames. Its switches between the 2 and one can "prepare" while the other one is still being used to render
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Hmm I dont know much about this project.
Wider LCDs for CPU as per the resolution, can support hight refresh rate but our phone LCD cant:/ it works(increasing vsync and it doesnt damage to LCD controllers in short run) but it will cheat benchmark(as softwares detects wrong info and muliplication) but in realtime performance will be worsened. And its not good for LCD controller HW. We will find every phone with 65hz max except LG. As because phone's LCD controller HW can draw only max 65 HZ sync. Increasing it will draw more frames but it wont be used by HW resulting in wasted frames. FrameBuffer refresh is completely different thing unrealated to vsync. If I can find more detailed refrence link about it than I will post the link when i get PC access soon
This project might be using combination of FB and vSync, not only vsync.
Can anybody rdirect me towards link of this project?
Sent from my LG-P990 using Tapatalk 2
I previously had phone Samsung Galaxy Spica((I-5700).
I began Horse Power Kernel Development 1st with these kernel. Reffer this link:
http://forum.samdroid.net/f53/development-kernel-horse-power-4973/
Click on Previous Changelogs History spoiler.
You can see in older changes i have increased Vertical Sync rate to 80Hz. But believe me it gives only massiv e 2d/3d score. But the performance of games were worsenedd incl. Of UI smoothness. I did revert it in newer version.
Yes its just matter of changing values in kernel display driver
I dont anything about butter project, can anubody provide me link of it?
Sent from my LG-P990 using Tapatalk 2
http://www.google.com/search?hl=en&...3.0.0.0.8612.2.0.0.2.2.0.0.0..0.0...0.0...1ac.
Don't know what you are looking for Spica?
And another link with some info.
http://www.androidpolice.com/2012/0...e-responsive-apps-that-anticipate-your-touch/
Thank you for providing links.
Edit: oh sorry w/o reading it I completely misunderstood before. Its different
Sent from my LG-P990 using Tapatalk 2
Okay I read overly not in deep. Its not related to kernel-HW's refresh rate that I was discussing, hence its safe. Okay its related to android framework I guess, not read in deep. Not related with Kernel and kernel needs no changes. Its google's work I guess
It seems good. I will look more deeply tomorrow as soon as I get PC access
Sent from my LG-P990 using Tapatalk 2
IF this would ever be ported to Gingerbread for our phone, it would only be found on CM7 ROMs, not on Stock ROMs.
Android has kinda bad design concerning the scrolling stuff in its framework which causes it to never be as smooth as other Smartphone OS like iOS or WP are or will be.
This base design can't be change easily anymore, in order to NOT break the (available) Android apps.
It's also clear that even though Google can't change the whole base, they will put efforts in creating and finding workarounds for providing a smoother UI anyway.
This and faster hardware will make Android smoother every year.
They have already proven with both ICS and Jelly Bean that they are able to improve the smoothness. But the changes they had to perform for this surely (without knowing further details) affect big parts of the Android Framework.
This means in order to get a smoother scrolling experience on Gingerbread, ROM DEVs would need to backport features and changes of the new OS revisions to GB framework. And I'm sure this is way too much work (for our crappy little phone ).
Also it can only be done if the whole framework source is available, so no smoother scrolling for STOCK. And there is nothing kernel DEVs could do in this case by their own (besides the things they are doing already), unfortunately.
But you guys could ask Temasek to backport smoother scrolling to his CM7 ROM *jokingly - won't be that easy*
Answering to the OP, it's quite impossible... We need to backport lots of changes in GB framework (for example hw acceleration) and to do a lot of work that it doesn't worth it. And the only rom that would support these changes is cm7, and it isn't so stable.
If you like project butter, get a galaxy nexus. We have doubts to get ics update on our 2x...
markop90 said:
Answering to the OP, it's quite impossible... We need to backport lots of changes in GB framework (for example hw acceleration) and to do a lot of work that it doesn't worth it. And the only rom that would support these changes is cm7, and it isn't so stable.
Click to expand...
Click to collapse
Yeah that's exactly what I wrote - just in short But I wouldn't call CM7 unstable.
markop90 said:
Answering to the OP, it's quite impossible... We need to backport lots of changes in GB framework (for example hw acceleration) and to do a lot of work that it doesn't worth it. And the only rom that would support these changes is cm7, and it isn't so stable.
If you like project butter, get a galaxy nexus. We have doubts to get ics update on our 2x...
Click to expand...
Click to collapse
Cm7 is one of the most stable roms on our phone...
Sent from my LG-P990 using xda app-developers app
Stefan Gündhör said:
IF this would ever be ported to Gingerbread for our phone, it would only be found on CM7 ROMs, not on Stock ROMs.
Android has kinda bad design concerning the scrolling stuff in its framework which causes it to never be as smooth as other Smartphone OS like iOS or WP are or will be.
Click to expand...
Click to collapse
Actually scrolling in Android is very well implemented. The reason for the lag is twofold:
1) Android started as keyboard driven OS (a better blackberry), with no touch interface in mind, so the UI thread is of normal priority. That means that touch events don't have a higher priority than any other process that runs on your phone at the same time, thus any animation or transition can be interrupted (in cpu cycles) by another process. Say for example that you are scrolling a long list. Every other process that does something at the same time (updating your widgets, checking your email etc) will get equal time with the cpu as the scrolling animation. That means allot of interrupts during that animation that cause frames to drop and thus lag to occur. It also means that the ui thread must wait for it's time whenever there is a touch event (user interaction through the touchscreen) to respond. Changing the UI thread priority would solve most ui problems with android but it would also indeed break compatibility with older apps.
2) The other problem is that most devs do a very poor implementation of lists. Android lists are actually very efficient but badly documented, and many developers implement them in ways that are sub-optimal. In order to save memory, the list only uses as many views (items) as fit the screen, and when the user scrolls it simply recycles them by changing their content. That means that the objects displayed in the list are cleared from the memory as soon as they leave the screen. So every time you return to the place where those objects where, an interrupt followed by IO with the filesystem takes place (the worst kind of interrupt). That's not such a big problem when the only thing you want to display is text, but what if you use bigger stuff like bitmaps? Then you get allot of lag. To avoid that you have to keep the list objects in memory. If you have too many such objects and want to avoid filling all the heap you can create a cashe with a limited size, or simply load object to the list only after scrolling has stopped (look to the cm9 music player cover art for one such example). Anyway, to make a long story short you can implement very complex and content heavy lists that run like butter on a arm6 600mhz gingerbread phone, but you can also make those same lists lag on OneX with the wrong implementation.
And btw, project butter DOES use the kernel, it makes use of a custom governor that immediately rumps up the cpu freq to the max whenever there is a touch event.
Stefan Gündhör said:
Yeah that's exactly what I wrote - just in short But I wouldn't call CM7 unstable.
Click to expand...
Click to collapse
I didn't say that cm7 is unstable, but it still has some freezes and random reboots... For example, yesterday I flashed cm7 again, after 2h of runtime I opened the browser and the phone froze and restarted himself... It is sufficiently stable, but I cannot use it as daily rom... And it is also battery hungry...
Ricardo has done a really great job on this phone, but cm7 isn't a rom for my business.. I prefer max stability, so I had to flash a 2.2 rom... GB memory leak is very annoying..
Supupa said:
Cm7 is one of the most stable roms on our phone...
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
"one of the most stable"? Maybe you just haven't tried a good stock based rom... I used cm7 for 7 months and i had a lot of problem...that's because of the closed Tegra2 sources...
markop90 said:
"one of the most stable"? Maybe you just haven't tried a good stock based rom... I used cm7 for 7 months and i had a lot of problem...that's because of the closed Tegra2 sources...
Click to expand...
Click to collapse
What do the closed sources have to do with cm7? It's GB as well and they are fully compatible.
I used CM7 for over half a year, never had any real problems.
ICS and GB are very diferent in the way they interact with the hardware.
Butter smoth stuf on GB is not possible.
This is what Ricardo Cerqueira answered about this:
"Project Butter is mostly about synchronizing gfx composition with the display's actual refresh rate... and Gingerbread didn't have a hardware compositor at all."

How to increase screen resolution after I rooted my GT-S5570i ??

I heard that I can increase screen resolution (ppl) of galaxy mini after I root it!! Please tell me how ?
Nooo...peee.
You can ONLY increase your dpi, screen resolution can also be changed using CyanMobile ROM (only for GT-S5570 )
Also, are your Mini fine now ? :fingers-crossed: Cheers if it's fine !
FACEPALM!!!
Lol it won't increase you resolution. It will just resize the UI. And it can be done on any ROMs by an app. You can use search.
ast00 said:
FACEPALM!!!
Lol it won't increase you resolution. It will just resize the UI. And it can be done on any ROMs by an app. You can use search.
Click to expand...
Click to collapse
No, you can. But it will be oversized, use CyanMobile latest release for Mini. You can increase resolution to 480x800, etc. You need to use search !
F4uzan said:
No, you can. But it will be oversized, use CyanMobile latest release for Mini. You can increase resolution to 480x800, etc. You need to use search !
Click to expand...
Click to collapse
Lol it's software thing. Normally you can't change the resolution. It's hardware thing. BTW if you want, then download an MDPI ROM and you are good to go. It's veeeeery very pointless.

Now that we have root, has anyone try to change res to 1080p

I know it won't have a big effect on battery life, but it would be great for game performance.
Has anyone tried or have any ideas on how to try it?
It's not worth it because it has some re escalation problems with the graphical user interface
Jaocagomez said:
It's not worth it because it has some re escalation problems with the graphical user interface
Click to expand...
Click to collapse
Interesting. I tried NoMone Resolution Changer but do see a lot of scaling issues in specific apps and in the GUI.
Maybe there is a way to change it per app? I got a good boost in Epic Citadel running 1080 over 1440.
Coronado is dead said:
Interesting. I tried NoMone Resolution Changer but do see a lot of scaling issues in specific apps and in the GUI.
Maybe there is a way to change it per app? I got a good boost in Epic Citadel running 1080 over 1440.
Click to expand...
Click to collapse
My best guess it's compile cm12 with that resolution and hope for no graphic errors

Categories

Resources