Hi there,
I was looking through the forum without lucky and I have a question. I have a SG3 and I would like to change the LCD density from build.prop without brick my phone. So my question is if anyone know what are any possible value for this?
The default value for my last SG2 was 240, and now the SG3 comes with 320. I used to use the SG2 with 160, but I'm not sure if this will work with my SG3.
Thanks in advance, and hope that this info help to anyone else in the community.
Regards,
PwOn said:
Hi there,
I was looking through the forum without lucky and I have a question. I have a SG3 and I would like to change the LCD density from build.prop without brick my phone. So my question is if anyone know what are any possible value for this?
The default value for my last SG2 was 240, and now the SG3 comes with 320. I used to use the SG2 with 160, but I'm not sure if this will work with my SG3.
Thanks in advance, and hope that this info help to anyone else in the community.
Regards,
Click to expand...
Click to collapse
I've tried few resolutions but they keep crashin the phone...so i just gave up...as every time i have to reflash the rom i'm using cos i cant open any apps...if somone knows a working settings would be great to share with us
smilu said:
I've tried few resolutions but they keep crashin the phone...so i just gave up...as every time i have to reflash the rom i'm using cos i cant open any apps...if somone knows a working settings would be great to share with us
Click to expand...
Click to collapse
bump
SOLUTION:
Before change LCD Density value in build.prop make sure that you have installed Apex Launcher or Nova Launcher in your SG3. In that way your phone will not crash...
PwOn said:
Hi there,
I was looking through the forum without lucky and I have a question. I have a SG3 and I would like to change the LCD density from build.prop without brick my phone. So my question is if anyone know what are any possible value for this?
The default value for my last SG2 was 240, and now the SG3 comes with 320. I used to use the SG2 with 160, but I'm not sure if this will work with my SG3.
Thanks in advance, and hope that this info help to anyone else in the community.
Regards,
Click to expand...
Click to collapse
From my understanding on the Galaxy S3 if you go any lower then 240dpi you will crash your phone. Anything lower then 240 I believe would be used for tablets, and the like.
I set mine to 240. lcd density did not work. build prop change via rom toolbox did and it looks AMAZING for 10 seconds then crashes. (freezes) eventually reboots (trying to reset in adb from CWM now) suggestions?
what could be causing it to crash I REALLY want that higher effective resolution. BADLY.
running leaked JB rom
I set my GS3 LTE to 240, works really well. However there were a couple of qwerks to note:
The launcher is rubbish, changed to EXLauncher pro
I had to mod the email app to fill the screen. sadly i can't attach the modded apk to this post as it is too big.
The camera app is a little strange, but perfectly usable.
The clock app crashes on launch - very irritating, however i set alarms using the voice controls! i should install an alternative clock app.
nerys71 said:
I set mine to 240. lcd density did not work. build prop change via rom toolbox did and it looks AMAZING for 10 seconds then crashes. (freezes) eventually reboots (trying to reset in adb from CWM now) suggestions?
what could be causing it to crash I REALLY want that higher effective resolution. BADLY.
running leaked JB rom
Click to expand...
Click to collapse
you got it so far. use alternative launcher. use alternative clock
calculator and talk are also borked
there IS a user working on converting the apk's to work on the S3 in fact he has most of them done but they don't work on US S3's only the international S3. he says he will try to make them work for US S3's (fingers crossed)
The S3 at stock res sucks. it was MADE for 240 in my opinion.
FYI I rooted the device with I9305_CWM_Recovery.tar.md5 and CWM-SuperSU-v0.96.zip then changed ro.sf.lcd_density in puild.prop from 320 to 240.
for some reason there are 2 entries of ro.sf.lcd_density. I assume the first one gets parsed and the second one ignored, as I changed the second one first to no effect. eventually i changed both.
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
nerys71 said:
you got it so far. use alternative launcher. use alternative clock
calculator and talk are also borked
there IS a user working on converting the apk's to work on the S3 in fact he has most of them done but they don't work on US S3's only the international S3. he says he will try to make them work for US S3's (fingers crossed)
The S3 at stock res sucks. it was MADE for 240 in my opinion.
Click to expand...
Click to collapse
Completely agree. it seems utterly crazy to make such a nice big high res screen then just scale up all the apps as if it was designed for only people with poor eyesight. I almost put my device on ebay ready to go back to iphone before i started getting into it.
Do you have a link to the the modded files? I was just looking through the camera app dimensions definitions and I don't have the time to change those! The email app just involved 3 dimension changes.
GS3 with slimbean.
I Installed slimbean 4.3 beta.2 and it has my screen density as 245. If you take a look at the screen shot I uploaded it shows what to do for changing screen density. Hope this helps.
Related
Any brave dev out there care to port the Touchwiz calculator and dialer for 190 screen density. Infuse is begging to be run at that dpi, just that those stock app do not scale at all.
Thanks in advance.
Yes this would be much appreciated
Is the 190 DPI really that much better? I have not tried it yet. What is stock?
crawlgsx said:
Is the 190 DPI really that much better? I have not tried it yet. What is stock?
Click to expand...
Click to collapse
It IS , stock is 240 ...
190 is Infuse Heaven.
rraquib said:
190 is Infuse Heaven.
Click to expand...
Click to collapse
Guess I need to get off my butt and try it then :-D
I actually have mine at 200 and love it.most apps are.coded to use only 160, 180, 200, and 240 led density. However, Ymmv
.
crawlgsx said:
Guess I need to get off my butt and try it then :-D
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
I would even settle for 200 but the DIaler looks terrible . Oh well.
h8rift said:
I actually have mine at 200 and love it.most apps are.coded to use only 160, 180, 200, and 240 led density. However, Ymmv
.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
rraquib said:
190 is Infuse Heaven.
Click to expand...
Click to collapse
care to elaborate on how you did that?
I assume it is in the build.prop but I have never edited it myself
There are apps in the market that can do this for you. As for myself, I used root explorer to edit my buildprop. Look for the line with lcd_density, change the value from 240 to 190. Save and reboot.
rraquib said:
There are apps in the market that can do this for you. As for myself, I used root explorer to edit my buildprop. Look for the line with lcd_density, change the value from 240 to 190. Save and reboot.
Click to expand...
Click to collapse
I bought root explorer, changed the lcd_density in build.prop file and now my dialer is shifted to the left. Pretty much everything shifted a little to the left. I love it this way but what did you do to fix the shifting issue?
TIA.
NVM, I was being idiot and did not read that you created this thread to find answers to that.
I noticed that even the apps drawer opens in the top left corner and spacing around it is wasted. I think you have to find all the lcd_density tags and change the values for everything?
S2K_MoZo said:
I bought root explorer, changed the lcd_density in build.prop file and now my dialer is shifted to the left. Pretty much everything shifted a little to the left. I love it this way but what did you do to fix the shifting issue?
TIA.
Click to expand...
Click to collapse
You don't. A dev needs to work on the issue. This is the entire reason this thread even exists.
never mind did it a see the diff..
Icons all outa wack at 190
chvybeatsford said:
never mind did it a see the diff..
Icons all outa wack at 190
Click to expand...
Click to collapse
See, I suppose if you don't wanna use the stock dialer, calculator and TouchWiz you can still use this 190 dpi. Just probably have to use different apps. I personally won't use it but that's cause all of the PNGs in the theme I work on are designed for 240 dpi.
beatblaster said:
See, I suppose if you don't wanna use the stock dialer, calculator and TouchWiz you can still use this 190 dpi. Just probably have to use different apps. I personally won't use it but that's cause all of the PNGs in the theme I work on are designed for 240 dpi.
Click to expand...
Click to collapse
Yea moving back to 240 till stuff is fixed. Looks great at 190 but im not to worried.
Go Launcher Ex and Go Contacts (it includes a Dialer) will get you 75% there @ 190 but the key pad during call is still the stock one . I still think it looks gorgeous at 190 density. Any one knows how the calculation is done. I will try to take a crack at it. At least can start with the calculator with out bricking the phone.
rraquib said:
Go Launcher Ex and Go Contacts (it includes a Dialer) will get you 75% there @ 190 but the key pad during call is still the stock one . I still think it looks gorgeous at 190 density. Any one knows how the calculation is done. I will try to take a crack at it. At least can start with the calculator with out bricking the phone.
Click to expand...
Click to collapse
Makes me wonder if you can control the span via simple XML edits..... hmmm....
You can, some one has done this for another phone. I know where they are in the Main.xml files just don't know what the values should be in relation to the pixel density. Is there any way to make it auto scale?
EDIT: I think the file attached is where the magic needs to happen but how?
Did you try messing with:
android:layout_width="320.0dip" android:layout_height="302.65625dip"
It is in tag:
<LinearLayout androidrientation="vertical" android:id="@id/Linewrapper" android:background="@drawable/call_dial_panel_bg_01" androidaddingRight="6.0dip" android:layout_width="320.0dip" android:layout_height="302.65625dip">
I am tempted to mess with it and see what it does. I am pretty sure that will do something but it will be more like trial and error since we don't know what that measurement equals to...
I would start with the calculator first. Can easily be remedied if things go wrong. Here I am attaching a deodexed Calculator APK. Take a whack at it if you like.
S2K_MoZo said:
Did you try messing with:
android:layout_width="320.0dip" android:layout_height="302.65625dip"
It is in tag:
<LinearLayout androidrientation="vertical" android:id="@id/Linewrapper" android:background="@drawable/call_dial_panel_bg_01" androidaddingRight="6.0dip" android:layout_width="320.0dip" android:layout_height="302.65625dip">
I am tempted to mess with it and see what it does. I am pretty sure that will do something but it will be more like trial and error since we don't know what that measurement equals to...
Click to expand...
Click to collapse
I have had some issues using Rom Toolbox on the Note 10.1 so am a bit nervous to try it to change the LCD Density.
Has anyone had any luck with an app that you can recommend?
mitchellvii said:
I have had some issues using Rom Toolbox on the Note 10.1 so am a bit nervous to try it to change the LCD Density.
Has anyone had any luck with an app that you can recommend?
Click to expand...
Click to collapse
You should be fine -- as long as you know what you're doing -- it's just a build.prop edit.
Rom Toolbox itself was most likely NOT the problem with your font issue,
but more likely the font itself. ICS is less tolerant than GB or Froyo with fonts.
Used to be you could replace Droidsans with just about anything,
now in ICS (and JB) Droidsans is soft-linked to Roboto -- AND replacements to
Roboto, bold, italic, etc. MUST be formatted properly.
You probably could have restored those fonts via recovery/adb and avoided
re-flashing the entire ROM.
Anyway back to your DPI question -- you could also edit build.prop from Root Explorer...
Used Rom Toolbox to change DPI. After reboot it changes back to 160.
Any ideas?
Sent from my awesome Note 10.1
Try editing manually? Do you have Root Explorer?
Just curious, what do you want to change it to?
gwbard said:
Try editing manually? Do you have Root Explorer?
Just curious, what do you want to change it to?
Click to expand...
Click to collapse
For some reason my root explorer will not allow me to enter r/w mode in the system folder. I can manually change it using Rom Toolbox Editor and it seems to change but after reboot it doesn't stick.
I wanted to try 140 and 120.
Sent from my awesome Note 10.1
mitchellvii said:
I wanted to try 140 and 120.
Click to expand...
Click to collapse
Just wanted to mention that I have used Root Explorer to bump my DPI to 120 and it is working swell. I was a little concerned changing the DPI with the s-pen apps, as on both my other Samsung devices (GS2/Tab 7.0 Plus) when I changed the dpi all of the stock apps looked like butt. Note pad only covering part of the screen, dialer looks miniscule and so forth. So far on the Note 10.1 its been golden.
teKuru
tekuru said:
Just wanted to mention that I have used Root Explorer to bump my DPI to 120 and it is working swell. I was a little concerned changing the DPI with the s-pen apps, as on both my other Samsung devices (GS2/Tab 7.0 Plus) when I changed the dpi all of the stock apps looked like butt. Note pad only covering part of the screen, dialer looks miniscule and so forth. So far on the Note 10.1 its been golden.
teKuru
Click to expand...
Click to collapse
Huh, well you have had better luck than me.
I tried setting mine at 140 and bootlooped. Tried pulling build.prop and changing it back to 160 but was denied permission when tried to puch it back. Used ODIN the flash root-injected firmware and now s-pen won't work at all and screen freezes if i awaken tablet from sleep mode.
All gone to hell.
tekuru said:
Just wanted to mention that I have used Root Explorer to bump my DPI to 120 and it is working swell. I was a little concerned changing the DPI with the s-pen apps, as on both my other Samsung devices (GS2/Tab 7.0 Plus) when I changed the dpi all of the stock apps looked like butt. Note pad only covering part of the screen, dialer looks miniscule and so forth. So far on the Note 10.1 its been golden.
teKuru
Click to expand...
Click to collapse
So do you think things look a bit crisper at 120? Do fonts look less pixelated? It could be that I was trying to run 140 and the tablet doesnt like that.
** Update. Went with 120. Definitely more screen real estate. Pixels look about the same.
Tried 120. Actually think fonts look a bit worse. back to 160.
mitchellvii said:
I have had some issues using Rom Toolbox on the Note 10.1 so am a bit nervous to try it to change the LCD Density.
Has anyone had any luck with an app that you can recommend?
Click to expand...
Click to collapse
So then Room ToolBox isn't safe to use for the density change on stock rooted rom?
I sucessfully installed jellybean but I can't seem to change the lcd density..
I have in my build.prop ro.sf.lcd_density=160 and nothing happens.. I still have it set to the original, 240.
I noticed theres a new options in jellybean's build.prop ro.sf.override_null_lcd_density=1, I commented this out and also set it to 0, but still no go.
Any ideas? I've tried various apps and they all have no effect
uh, I may be wrong, but how is you changing a setting going to have a physical change on the hardware that's in your tablet?
incarceration said:
uh, I may be wrong, but how is you changing a setting going to have a physical change on the hardware that's in your tablet?
Click to expand...
Click to collapse
It's NOT a physical change - Changing the LCD DPI Density has been a method used on most versions of Android for years. What rock have YOU been under?
Yep. Same here. Can't find a way to get 160 back to life.
This is pretty much a worst thing Asus could do to us. Or is it JB thing?
Don't know, but i'll try to find a solution to this as i just can't look at 240 density after using 160 for so long.
Oversized icons are really not nice :cyclops:
Hmm this might have something to do with my sensitivity issues too. Before in a certain game I could rapidly tap a button and it would go through. Now on JB it's not registering my rapid taps and I have to tap slower. Looking all over the place for a solution!
Alitheia said:
Hmm this might have something to do with my sensitivity issues too. Before in a certain game I could rapidly tap a button and it would go through. Now on JB it's not registering my rapid taps and I have to tap slower. Looking all over the place for a solution!
Click to expand...
Click to collapse
I'm on CM 10(JB 4.1.1.) and DPI change works through the build.prop without any problems. I wonder if Asus did something to block this in latest update..
Could it be related to the kernel not supporting it?
I mean, they probably changed kernel, so maybe they didn't include this in the final release.
Why is beyond me and my understanding of their logic.
I hope this is not the case.
hm.. this is hard to get used to 240 again. i hope theres a way around this
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Don't try the LCD app.
I'm softbrick right now.
I too dislike the hugh icons.
Sent from my HTC PH39100 using xda premium
jaxboater said:
Don't try the LCD app.
I'm softbrick right now.
I too dislike the hugh icons.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Thanks for taking a risk and let us know.
So this option is off, too.
Yeah this DPI is a bit of a shock
dirran said:
Yeah this DPI is a bit of a shock
Click to expand...
Click to collapse
Could you please explain me-a-noob, what's so shocking about the different DPI? I thought the DPI by default remained "at its best setting". Apparently it is not...
Why would ASUS set the DPI in a way, which would not use the full potential of the screen?
iritoi said:
Why would ASUS set the DPI in a way, which would not use the full potential of the screen?
Click to expand...
Click to collapse
I don't know, but they did it .
I miss my 200 DPI. It would be a real shame when there's no way to change the DPI.
iritoi said:
Could you please explain me-a-noob, what's so shocking about the different DPI? I thought the DPI by default remained "at its best setting". Apparently it is not...
Why would ASUS set the DPI in a way, which would not use the full potential of the screen?
Click to expand...
Click to collapse
It tricks Android into making each pixel smaller. Which means all your icons, text, etc shrink on the screen. This gives you more room on your screen and makes mostly everything look a hell of a lot better. If you do a search for DPI on the general forum, you will find a thread about DPI with screen shots that show you the difference.
phree1 said:
It tricks Android into making each pixel smaller. Which means all your icons, text, etc shrink on the screen. This gives you more room on your screen and makes mostly everything look a hell of a lot better. If you do a search for DPI on the general forum, you will find a thread about DPI with screen shots that show you the difference.
Click to expand...
Click to collapse
Same boat. This really sucks. The DPI change is so abrupt, it almost makes me want to downgrade.
spinaldex said:
Same boat. This really sucks. The DPI change is so abrupt, it almost makes me want to downgrade.
Click to expand...
Click to collapse
Why not just try out a custom Rom? At the Moment Baked BlackBean 4 and unofficial CM10 10/1 versions work very well and give you all kinds of settings and tweaks to work with as well as theme chooser. The only thing that isn't working (well or at all) is GPS and I expect that will be fixed in short order, now that the official TF700 JB update is out.
okantomi said:
Why not just try out a custom Rom? At the Moment Baked BlackBean 4 and unofficial CM10 10/1 versions work very well and give you all kinds of settings and tweaks to work with as well as theme chooser. The only thing that isn't working (well or at all) is GPS and I expect that will be fixed in short order, now that the official TF700 JB update is out.
Click to expand...
Click to collapse
Don't get me wrong, I used CM9 on my TF101 and use it on my phone, BUT I like a stable ROM with barely any noticable issues as I really do use just about everything on my devices, including the GPS. For now, until the custom roms make a bit more headway, I'm not going to switch.
Any luck?
Bump on this topic, no go on lcd mods in build.prop
REALLY would like to go back to 160...i may downgrade if there is no workaround...
I can also confirm lcd changer apps dont work either, got soft brick with one and the others didnt change anything
Agreed, any news?
Has anyone contacted Asus about it and asked?
Or, has anyone tested DPI changes on other Jelly Bean devices such as the Nexus 7 and seen if it works there (which would indicate Asus intentionally disabled it)?
spinaldex said:
Agreed, any news?
Has anyone contacted Asus about it and asked?
Or, has anyone tested DPI changes on other Jelly Bean devices such as the Nexus 7 and seen if it works there (which would indicate Asus intentionally disabled it)?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1922747
That proves that ASUS disabled it I'm still unable to unlock.. I need to switch to custom roms soon; I can't stand the default dpi
Hello there,
I just recently installed a Custom Rom on my Nexus S after being on stock for 2 years+. Reason being that it was quite slow so I thought I give a Custom rom a try. I choose to go with SlimRom since it's quite new and I feel excited about the new 4.2.2 Android. Also I used a custom kernel (marmite).
The problem I am facing is that on the first flash (try) I had a perfect ROM until I faced a problem with Exchange and Email application crashing constantly so I followed the advice from the FAQ to wipe data and try again. I thought it would be a good idea to reflash the latest SlimRom as well since it was fixing the Gmail problem with toast notifications. After that point and after some Apps doesn't render correctly. It's not just one (then I would say it's the app) and it's not all of them. So I am posting here in case you have a better idea of what's happening. See the images I attach for get an idea of what I am talking about. In the Chrome application the tab number is like moved some pixels down and on the other application (Online Radio app) the button is moved few pixels up.
Anyone happened to come across that? Any suggestions to fix it?
Thanks
Hi
I would suggest putting this in the development section under the slim ROM section so the developers can help out
But what DPI are you using?
Good luck
Vs Nexus S4G using tapatalk2
That was my first thought as well, but unfortunately I don't have enough posts to let me post there. If an admin can move it there it would be great.
DPI setting : 182 (default from SlimRom)
Sent from my Nexus S using Tapatalk 2
setting to stock [240] DPI has always
cleared squirrly display errors
both on my old 4G and the current 9020a
i use to run 220 and could go back to it
and it would desplay correctly...
ymmv
artafinde said:
That was my first thought as well, but unfortunately I don't have enough posts to let me post there. If an admin can move it there it would be great.
DPI setting : 182 (default from SlimRom)
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
OK, I forgot about the development section requirements.
But like the previous post mentioned... The DPI should be changed to stock 240 or what he has at 220. Give it a try to see what happens.
Settings/interface/general
Vs Nexus S4G using tapatalk2
I tries setting the DPI to 220 and I saw some improvement. So I gyres it's a combination of the custom DPI and the apps. I can survive for now with the rendering bug since I like the small DPI (182)
Thanks for the suggestions
Sent from my Nexus S using Tapatalk 2
It seems it's a problem with the application, since new versions of chrome fixed it.
Sent from my Nexus S using Tapatalk 2
I'm coming from running a smaller nav bar size of my nexus 4.
I can't stand the icons being this large there is just no need for it.
Do anyone know what scripts I need to edit to get it down to 24dpi ?
Thanks
Sent from my Nexus 5 using XDA Premium HD app
sitnlow4life said:
I'm coming from running a smaller nav bar size of my nexus 4.
I can't stand the icons being this large there is just no need for it.
Do anyone know what scripts I need to edit to get it down to 24dpi ?
Thanks
Sent from my Nexus 5 using XDA Premium HD app
Click to expand...
Click to collapse
You could root and then use a build prop editor to change the density. Or you could wait until roms start appearing (PA, etc). You know, give it time, it should blossom
tremblingwater said:
You could root and then use a build prop editor to change the density. Or you could wait until roms start appearing (PA, etc). You know, give it time, it should blossom
Click to expand...
Click to collapse
This is pretty much it. I'm running 320 DPI right now and it's much more usable, but not perfect yet.
Dungeon47 said:
This is pretty much it. I'm running 320 DPI right now and it's much more usable, but not perfect yet.
Click to expand...
Click to collapse
Found my perfect setting of 400. Didn't really like the huge icons by default, and 320 was way too low for me. 400 suits me fine, and replicates roughly my nexus4.
Don't know why Google changed this personally. Never changed DPI before, is there anything I should be aware of now I have done so?
CrazyPeter said:
Found my perfect setting of 400. Didn't really like the huge icons by default, and 320 was way too low for me. 400 suits me fine, and replicates roughly my nexus4.
Don't know why Google changed this personally. Never changed DPI before, is there anything I should be aware of now I have done so?
Click to expand...
Click to collapse
Google changed it because the screen is higher resolution. The only things to be aware of are the possibility of Play Store having compatibility issues. If you get that, just return to stock DPI, update apps, and go back to what you like. The other thing is that it affects everything, so some apps might change their interface as a result.
Dungeon47 said:
Google changed it because the screen is higher resolution. The only things to be aware of are the possibility of Play Store having compatibility issues. If you get that, just return to stock DPI, update apps, and go back to what you like. The other thing is that it affects everything, so some apps might change their interface as a result.
Click to expand...
Click to collapse
If the screen resolution is higher, why could I fit less on my desktop than my Nexus4? I use Dashclock and it chops off data that was always visible on my N4. Seemed like a backwards step.