Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,785,791 Members 53,747 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Resolution in Custom Roms

Tip us?
 
babarali_47
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 7
Join Date: Mar 2012
Default [Q] Resolution in Custom Roms

Peace be upon you all. I am new here and I hope I am posting to the correct forum. I recently installed Cyanogenmod 11 on my galaxy S3 (I am new to rooting and it was my first custom rom ). I noticed that resolution didn't seem as crisp as on the stock firmware. Later on I noticed the same thing with AOKP. I checked the resolution and it was 780X1280 with a pixel density of 320 ppi, whereas the native resolution of S3 is 720X1280 with a pixel density of 306 ppi. I tried to change pixel density using rom toolbox, but still couldn't notice any difference. Any ideas? Thank you
 
Darkened_Sky
Old
#2  
Darkened_Sky's Avatar
Senior Member
Thanks Meter 268
Posts: 429
Join Date: Jun 2013
Quote:
Originally Posted by babarali_47 View Post
Peace be upon you all. I am new here and I hope I am posting to the correct forum. I recently installed Cyanogenmod 11 on my galaxy S3 (I am new to rooting and it was my first custom rom ). I noticed that resolution didn't seem as crisp as on the stock firmware. Later on I noticed the same thing with AOKP. I checked the resolution and it was 780X1280 with a pixel density of 320 ppi, whereas the native resolution of S3 is 720X1280 with a pixel density of 306 ppi. I tried to change pixel density using rom toolbox, but still couldn't notice any difference. Any ideas? Thank you
it probably didn't work. but to get sure: you have rebooted after the change? look into your build.prop (in system folder) for the value "ro.sf.lcd_density" if it is still 320. if yes then try to change it manually to the value you like. then save and close it and reopen the build.prop to look if the change sticks.
I often noticed that rom toolbox (pro) has a problem with the integrated superuser app, so that it don't get r/w permissions to system.
That is the reason why I switched to SuperSu by chainfire, with this Rom Toolbox and all other root apps never had problems
Samsung Galaxy SIII I9300 Pepple Blue
Kernel: arter97 dualboot/f2fs kernel
File system: /data on F2FS
Recovery: arter97 f2fs enabled philz touch
1st Rom: Temasek's unofficial cm11
2nd Rom: Archidroid 1.X sammy 4.3 based
The Following User Says Thank You to Darkened_Sky For This Useful Post: [ Click to Expand ]
 
babarali_47
Old
#3  
Junior Member - OP
Thanks Meter 0
Posts: 7
Join Date: Mar 2012
Quote:
Originally Posted by Darkened_Sky View Post
it probably didn't work. but to get sure: you have rebooted after the change? look into your build.prop (in system folder) for the value "ro.sf.lcd_density" if it is still 320. if yes then try to change it manually to the value you like. then save and close it and reopen the build.prop to look if the change sticks.
I often noticed that rom toolbox (pro) has a problem with the integrated superuser app, so that it don't get r/w permissions to system.
That is the reason why I switched to SuperSu by chainfire, with this Rom Toolbox and all other root apps never had problems
Thanks for your reply friend. It probably did work, icons looked a bit small but, still the text seemed a bit blurry and wasn't as crisp as on the stock rom. I restored the backup of stock rom and checked pixel density and resolution. it showed a resolution of 720x1280 and ppi of 320. Whereas general specs of the phone say it is 306. Or I don't know that 306 is something else .... To sum it up, both the stock rom and CM show a pixel density of 320. But, stock has a resolution of 720 whereas CM had 780 pixels..... don't know what to do.
 
babarali_47
Old
#4  
Junior Member - OP
Thanks Meter 0
Posts: 7
Join Date: Mar 2012
Things are working fine on Temasek's unofficial CM 10.2 rom. Maybe it was a problem with that rom I installed
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes