Related
I can't seem to change DPI on any of these new ICS roms..
I have to! I'm not blind!
So it's stuck at 240 dpi.. I've tried DPI changer apps, but on every reboot my phone hangs at boot logo (splash screen, logo.jpg)
Maybe changing DPI on these roms doesn't work?
I feel you mate!
Last I checked It worked on LP6, from LPH onwards it doesnt work!
I dont know the reason but yeah hasnt been working for me too.
Damn this is unbearable! Even blind people can see these huge icons. Someone must know of a fix..
Look here http://forum.xda-developers.com/showpost.php?p=23438841&postcount=11877
edit the build.prop file in system folder and change the value from 240 to 160 or some other value you like.
Done that, same effect..
I done that, except deleting the backup build.prop.bak. I don't see why that'd help so I'll exclude it for now..
Got stuck at splash screen still!
I know on LPH and a few other ICS roms that the build prop has two locations you need to set the LCD Density. If you changed one already, look for the other one as there should be two locations within build prop.
Ok I've confirmed it by installing LPQ, rooting and changing LCD density. As mentioned, there are two 'ro.sf.lcd_density=240 locations in build prop. Change both of them to desired density level. I changed both of mine to 210 and after a reboot, the LCD changed without issue and a lot smaller.
blue265 said:
Ok I've confirmed it by installing LPQ, rooting and changing LCD density. As mentioned, there are two 'ro.sf.lcd_density=240 locations in build prop. Change both of them to desired density level. I changed both of mine to 210 and after a reboot, the LCD changed without issue and a lot smaller.
Click to expand...
Click to collapse
just tried by changing both 'ro.sf.lcd_densities' to 160 with root tools and am stuck with bootloops...
I am a bit of a noob when it came to editting the build.prot but i changed both values and rebooted ,, everything is lots smaller now...
Now to learn how to size the desktop to fit the smaller writing/icons..
This method worked perfectly for me.
I went 192. After some tweaking apex got the desktop to look far less.. Err.. Big.
The email app and dialer are a bit skewed though.
Sent from my GT-I9100 using XDA
tried every other way suggested here and came up with bootloops.
so i did this instead, using 7zip for the PC,
1. opened the cwm flashable custom rom's zip in the PC,
2. opened the build.prop with notepad where i had already set the *.prop to open with notepad
2. changed both locations from 240 to whatever i desired.
3. updated the build.prop back to the zip (it'll prompt when you close the build.prop)
4. Copied back to the SD card
5. and flashed
and voila, no worries, no bootloops
i hope this helps
I tried everything (changing on phone directly, flashing changed boot.prop, changing through the app), but in each case phone will not boot after change. I would really like to know what is the factor influencing this.
Did anyone succeed to change dpi on stock LPQ (rooted with CF and reverted to original kernel)?
vandric said:
I tried everything (changing on phone directly, flashing changed boot.prop, changing through the app), but in each case phone will not boot after change. I would really like to know what is the factor influencing this.
Did anyone succeed to change dpi on stock LPQ (rooted with CF and reverted to original kernel)?
Click to expand...
Click to collapse
I can only get dpi to 182 in criskelo ics rom and litening ics rom all other ics rom dont work.
shanume said:
I can only get dpi to 182 in criskelo ics rom and litening ics rom all other ics rom dont work.
Click to expand...
Click to collapse
Changing DPI on these roms work
ROM - (16 March 2012) TurkbeyRom Ics V1 4.0.3 Blue-Black Themed XXLPQ
Manually set your desired DPI : edit build.prop
078gregory said:
Look here http://forum.xda-developers.com/showpost.php?p=23438841&postcount=11877
Click to expand...
Click to collapse
I tried, but it doen't work. After change the file, it saves successfully, but i cannot find build.prop.bak.
I used root explorer and worked fine for me.a few fred weeks ago
Sent from my GT-I9100 using Tapatalk
i have LPG, tried density modders and manually changing build.prop, every time tje phone wont boot !!!!
I've but the omega rom on my SG2 and would like to know i editing the file to change my resolution will work? Since there seems to be mixed results. On Gingerbread used LCD density changer to get this done and would like to recreate the resolution on my ICS rom now.
thanx guy
i load lcd density modder and i setup 320dpi and my phone reboot but it is not open. How to correct it. Could you pls upload orginal file. The name is /system/build.prop
Phone : Galaxy s2 ics lp4
u can factory reset the phone,tht app neva workd for me on the dpi sometimes if supported then some apps don open or market dosnt open....
I also met this problem.I flash again 4.0.3 firmware ,then problem solved.
320 cannot be used. You need to keep the value from 184 (working setting) to 240.
Just so you know... when you change the dpi, the lower the number... the more dense it will be .
and just to let u know at times changing lcd density might make your device incompatible with market or google play for some apps. play safe
Hi.
flashed the "Fouth bar" (4.0.4) rom on my device, and the latest A1 kernel as well. because some games didn't appear on the market, i backed up my device in case of trouble and tried to change the device dpi with an app. it said it "Couldn't find Configuration File". another app did let me change it (to 160) but the device got into a sort of a bootloop because of it, so i restored it into working form. i'd like to know if and how i could more apps compatible in the market, and change the dpi successfully.
Thx, e.
Change DPI by modifying the build.prop file in /system
I have found a good work around for those of you who may enjoy more usable space on your screen. With the screen the S4 comes with it only makes sense to use it. Only follow these steps after you are running on Hyperdrive ROM successfully (I am guessing this will work with other roms as long as Xposed Framework can be installed).
Background Work (no major changes yet)
1) Open the app Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Framework Installer
3) Click Install/Update
4) Select the tab 'modules' from the top
5) Check all the boxes you see (I had 3)
4) Click Reboot
Let's get started
1) Reopen Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Per App DPI Settings
3) Select Google Keyboard
4) Turn the switch to ON
5) Enter 160 for DPI, 100 for Font and check the box labeled 'xlarge res'
6) Click save and click yes.
7) Repeat steps 4-6 with the apps Swype and Samsung Keyboard
8) Make sure you followed the above steps then continue
9) Now find an app called Android System from the list and select it.
10) Enter 280 and don't change anything else (I don't know what you would be doing so I stayed away)
11) Click save and click NO.
12) Restart and enjoy.
I went back and changed System UI to 340 as I didn't like how small the notification bar became. Also recommending ExDialer as the stock keypad won't 'stretch' and lastly as a must, look into a good launcher. I am using NOVA Prime.
If you want to undo changes you can simply turn everything 'Off' and click Save and No. Then restart.
Hopefully this helps some!
If I am missing anything or if anyone wants to add more detail let me know! Side note: random but AOSP helper was installed on my device also allowing easy toggle from 3G to 4G with JuiceDefender...
Colton
Mods can you list this as a [HOWTO]... sorry left that out.
awesome.. .thank you!
OMG thank you for this, i has given up on how to do anything on it. I did not know how to use Xposed frameworks, this is what i needed, than you very much:good:
Has anyone tried changing the overall system DPI and then changing just the misbehaving Samsung applications back to stock (i.e., Contacts/Dialer, Camera)? I pretty much manually set all of my apps to between 320 and 340, but the Notification dropdown is way too big. (Email and Gmail both at 320 in order to become usable).
This made my launcher grid super tiny and the keyboard is unusable it is so small. I can imagine how some slight DPI adjustment could be good, but this is aweful!
that being said, I will use this method to adjust things how I would like them.
I'm glad it worked well for you guys but both of those changes made things worse for me. I put it back on stock and am very happy with it.
I'm running 320 DPI in my build prop. To fix the dialer I went into the per app DPI and changed the contacts app and phone app to stock 480 DPI and also the calculator app as well. They all run just like stock now no problems at all
Forgot to mention gallery as well
Sent from my SCH-I545 using xda premium
im using 360 in my build.prop. and have had no problems. only thing i had to fix was my market. which i used this market found here
http://forum.xda-developers.com/showthread.php?t=1839871
using the correct version of the one in my current rom(hyperdrive). Dont ask me why this works. But someone else said they tried it and it worked. so i did and it worked. Sometimes ive noticed it will all the sudden on reboot, change to a different version of the market. But that has only happened a couple of times. and usually it didnt matter(most apps still showed up like normal). But i dont know that this will work the same way for everyone since it seems to be a semi flakey method.
It works fine in HyperDrive RLS 4. Don't try to change the build.prop for the first boot, though. Let it boot once, then change it. Let's just say that the results were a hung device first.
I added clock back to 480 because there are issues with it.. The year view in Calendar is a bit off, but that's the only screen that doesn't work right... The Market works fine at this resolution (360). This is much easier than what I was doing before...
Now Touchwiz can be somewhat usable as it isn't huge gigantic text everywhere (even on the Tiny selection in Screen)
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
kcellb said:
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
Click to expand...
Click to collapse
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
jeffreycentex said:
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
Click to expand...
Click to collapse
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
colton22 said:
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
Click to expand...
Click to collapse
I had problems with the first two downloads. Then I was able to get one to work early this morning... Also note that it is supposed to be a wipe'd flash, so make sure you do the format data/cache 3 times, then format system... I generally do a flash of the rom first to make sure that there aren't problems, though, before I format system...
I only use 320, 360, and 480's as DPI's on the S4.
Your approach is the way I used to do, but I wanted everything smaller, so every time I installed a program, I changed it to 320/360.. But then I wanted 320/360 to be the overall and only make exceptions for the things that demand stock DPI.
Understood - I didnt wipe to flash as i never did before without an issue. I am downloading stock ODIN now as something is up with my data partition...? It hangs on every second+ boot from restore/install and will not even boot off an install. I will go to stock odin, root, recovery and then install. Also downloading a fresh copy of Hyperdrive RLS4... Thank you for the tips.
C22
Found a better way!
Okay so I am now on RLS 10.2.0...
Download some type of Root file manager... I paid for/use Root Explorer love it.
Navigate to /system and long press build.prop
Find the line that contains screen density =480 and change it to your desired DPI (I am using 280)
From there all apps/everything is changed to that dpi... some stock apps you will have to use xposed to change them back to 480 just to make it work because they show different resolutions horribly.
I followed these steps...
http://forum.xda-developers.com/showthread.php?t=2269483
works great! Enjoy.. Also on the Multi DPI stock app post, the only one that works with the Verizion phone is the Gallery S4 v2.zip file... The others I am trying to work with the dev on getting up and running for our phones.
Colton22
deleted
Thanks
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
babarali_47 said:
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
Click to expand...
Click to collapse
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
Darkened_Sky said:
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
Click to expand...
Click to collapse
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.
Things are working fine on Temasek's unofficial CM 10.2 rom. Maybe it was a problem with that rom I installed