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
This may be a noob question but id like to know what all the hype is with switching your dpi. Can anyone help me out?
daveyglow said:
This may be a noob question but id like to know what all the hype is with switching your dpi. Can anyone help me out?
Click to expand...
Click to collapse
To be honest I dont understand it myself. The only plus to it is being able to fit more on the screen.
It gives your screen a high definition look. Think of it like a youtube video. If you watch a video in fullscreen and it is slightly blurry and then shrink it to half screen. The picture gets so much clearer. Changing your DPI is purely cosmetic. But it can cause apps to not run properly and apps not to be available from Google Play (Android Market). But there are fixes for this too.
Agoattamer said:
It gives your screen a high definition look. Think of it like a youtube video. If you watch a video in fullscreen and it is slightly blurry and then shrink it to half screen. The picture gets so much clearer. Changing your DPI is purely cosmetic. But it can cause apps to not run properly and apps not to be available from Google Play (Android Market). But there are fixes for this too.
Click to expand...
Click to collapse
i don't get how you can raise the DPI if the phone itself has say 800X480.
Shimmty said:
i don't get how you can raise the DPI if the phone itself has say 800X480.
Click to expand...
Click to collapse
It's a setting offered on the Absolution ROM. I'm not sure if its a CM feature or what other ROMs offer it but Abolsution allows you to mess around with the DPI.
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
Hi all,
First thing I do on a Win7/Win8 device is 'make the font smaller' (DPI?), the thing with 150% / 125% / 100% (default. 125%)
I have the feeling, most of the time, the nexus 5 is set to 150%
One of the results could be you get more icons your homescreen => more rows, more columns
Can this be changed ? without rooting.
Thanks!
PS: yes, it is absolutely amazing and blazing fast
nope, and you couldn't do it if you were rooted either unless you coded it yourself
Sent from my Nexus 5 using xda app-developers app
n7of9 said:
nope, and you couldn't do it if you were rooted either unless you coded it yourself
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
wrong ... yes you can change the display density (as in make everything smaller do display more stuff) and no you can't change it without root access
the setting you're looking for is the ro.sf.lcd_density property in the build.prop file. There are several editors available to do that.
veli0s said:
wrong ... yes you can change the display density (as in make everything smaller do display more stuff) and no you can't change it without root access
the setting you're looking for is the ro.sf.lcd_density property in the build.prop file. There are several editors available to do that.
Click to expand...
Click to collapse
Okay thanks a lot for that, I'll have a look.... in a few days because I'm not about to root my brand-new phone
lowlow2 said:
Okay thanks a lot for that, I'll have a look.... in a few days because I'm not about to root my brand-new phone
Click to expand...
Click to collapse
If you're planning on rooting in the future, I hope you've already unlocked your bootloader...
Sent from my Nexus 5
I'm trying to change my DPI with Build Prop editor but every time I reboot, the changes revert to stock.
Timdor said:
I'm trying to change my DPI with Build Prop editor but every time I reboot, the changes revert to stock.
Click to expand...
Click to collapse
Change it manually with a file explorer.
Timdor said:
I'm trying to change my DPI with Build Prop editor but every time I reboot, the changes revert to stock.
Click to expand...
Click to collapse
Trying now. Is there any reason that would be different than the build prop editor? It worked on all my other phones
I just changed dpi to 420 in build.prop ...looks way better now! 400 was to small for me!
Im on 380 and its perfect, for me. The default was absolutely huge.
tremblingwater said:
Im on 380 and its perfect, for me. The default was absolutely huge.
Click to expand...
Click to collapse
Amen. I tried 300 and it wouldn't boot. Had to make a flashable build.prop. I'll try your suggestions. 280 looked interesting, though lol also, which app do you guys use for it?
update: set it to 380 and i like what i see.
RussianBear said:
Amen. I tried 300 and it wouldn't boot. Had to make a flashable build.prop. I'll try your suggestions. 280 looked interesting, though lol also, which app do you guys use for it?
Click to expand...
Click to collapse
I normally just edit the build prop using a build prop editor. I have also used 'texdroider_dpi' from the playstore. The default for the N5 seems to be 480, for anyone who forgets.
RussianBear said:
Amen. I tried 300 and it wouldn't boot. Had to make a flashable build.prop. I'll try your suggestions. 280 looked interesting, though lol also, which app do you guys use for it?
update: set it to 380 and i like what i see.
Click to expand...
Click to collapse
I used the editor integrated within ES-Explorer for editing build.prop!
Anyone remember the default dpi? I changed it but I want to go back. Don't remember if it was 440 or 460. The number in the tabs in chrome is offset and it annoys me in smaller dpi.
olieebur said:
Anyone remember the default dpi? I changed it but I want to go back. Don't remember if it was 440 or 460. The number in the tabs in chrome is offset and it annoys me in smaller dpi.
Click to expand...
Click to collapse
I think it was actually 480.
RussianBear said:
Amen. I tried 300 and it wouldn't boot. Had to make a flashable build.prop. I'll try your suggestions. 280 looked interesting, though lol also, which app do you guys use for it?
update: set it to 380 and i like what i see.
Click to expand...
Click to collapse
I think 350 is the minimum.
At 380 now and liking it.
ArkAngel06 said:
I think it was actually 480.
Click to expand...
Click to collapse
Yup, it is.
elliot.newnham said:
I think 350 is the minimum.
At 380 now and liking it.
Click to expand...
Click to collapse
I had some other app that would let me preview it before rebooting, and for whatever reason 280 worked, so I've upped it to 300 and got a black screen on boot...lol
I changed my DPI to 320, and I noticed that when I press home the keyboard pops up every single time. But when I return it to stock 480, it doesn't. I really want to keep it at 320 but the keyboard popping up on pressing home is annoying. Any ideas?
If you're looking to make things "smaller" (icons and such) You can do it with a 3rd party launcher like Nova or Apex. There you have the ability to make things smaller than the huge stock.
I just changed my DPI to 445 which is the true DPI of this display. Everything is perfect now!
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.