Related
So what does this do....
http://forum.xda-developers.com/attachment.php?attachmentid=549635&stc=1&d=1300874955
With AWD Launcher i now get a screen with 6 x 6 (columns,rows). I finally get to use the big screen on the Desire HD.
Compatability?
Well i have no idea what sense would do and themes may have issue alone with some apps.
i know that Camera360 Ultimate don't like this until you run in hardware compatibility mode.
But ill never go back to ro.sf.lcd_density=240
This command is in the build.prop file located in the system folder. I recommend 'Root Explorer' for editing. And its all done at your own risk, always backup
FYI, i even did this to my Desire, not HD, and its just brilliant.
I also run at 200dpi, I find if you take it any lower that compatibility starts to become an issue and some games don't look nice in 70% screen usage. Personally I use ES File Explorer to do the editing of build.prop
wont sense be incompatible with this dpi setting?
that screen is so cluttered. I like mine to be open with everything big, easy to see and press. Plus the app drawer is where I keep most my apps
reminds me of an iphone
smurcoch said:
wont sense be incompatible with this dpi setting?
that screen is so cluttered. I like mine to be open with everything big, easy to see and press. Plus the app drawer is where I keep most my apps
reminds me of an iphone
Click to expand...
Click to collapse
yes, thank christ don't run sense it slows dhd down uneccessarily.
to see the difference heres two images first at 240 then at 200
Uploaded with ImageShack.us
I'm running CleanDHD which comes with 190 DPI, and i love it. My screen is way bigger now!
Have found three small glitches, but apps and games runs perfectly.
Confirm that troubles occurs with Camera360 but it's usable. Another application having problems with DPI=190 is CalWidget... it just displays an exception instead of my agenda....
naboleo said:
Confirm that troubles occurs with Camera360 but it's usable. Another application having problems with DPI=190 is CalWidget... it just displays an exception instead of my agenda....
Click to expand...
Click to collapse
can you send the Camera360 dev an email explaining what happens. i don't think that they understood what i was on about
Could you also test wide screen shots with zoom, full zoom or half zoom. I found that it crashes the app at dpi 240 or 200 for me.
cheers,
To save editing the build.prop you can download lcd density changer from the market. A bit easier I find.
I found that sense worked at 190dpi with a glitch on the lockscreen.
Sent from my HTC Desire HD using XDA Premium App
twiztedvvv said:
To save editing the build.prop you can download lcd density changer from the market. A bit easier I find.
I found that sense worked at 190dpi with a glitch on the lockscreen.
Sent from my HTC Desire HD using XDA Premium App
Click to expand...
Click to collapse
LOL!!!!!!! yeah that is a bit easier
Trust me to go and find the hard way of do it
mrjonnyrock said:
can you send the Camera360 dev an email explaining what happens. i don't think that they understood what i was on about
Could you also test wide screen shots with zoom, full zoom or half zoom. I found that it crashes the app at dpi 240 or 200 for me.
cheers,
Click to expand...
Click to collapse
Can you PM the dev's email ? Didnt find it, and user forum seems to be about feature requests and votes... Will try those setting
Confirmed also for notification glitch ... See screen captures
twiztedvvv said:
To save editing the build.prop you can download lcd density changer from the market. A bit easier I find.
I found that sense worked at 190dpi with a glitch on the lockscreen.
Sent from my HTC Desire HD using XDA Premium App
Click to expand...
Click to collapse
the problem with LCD density changer
is that the change doesn't survive reboots, where as changing build.prop does.
I may have missed something but can't get Camera360 crash...
2 other app that are not perfect :
- the stock dialer is too small the dialer part
- freecell has problems too
ghostofcain said:
the problem with LCD density changer
is that the change doesn't survive reboots, where as changing build.prop does.
Click to expand...
Click to collapse
I have LCD Density changer 5.3 and works perfect for me. Even with a reboot.
I don't see myself going above 180dpi anymore, I just love the screen estate I get with this. Also looks much cleaner.
This is with dpi on 170 and I'm thinking of going lower, the keyboard stays the same size so I go nothing got lose
The proper lcd density seems to be 270 for this build.
download 'LCDDensity for Root' by Elviss Kustans from market and set density to 270dpi.
solved the weird positioning of shortcuts and widgets on stock launcher
alternatively you can edit the build.prop
I chose this method to quickly find the proper number
NOTE: The Change in density is required for the stock launcher of 2.3.4 HKTW rom. The device is otherwise crisp at default with other launchers.. So do not bother incase you dont want to use stock launcher.
I'm still trying to decide between 270 and 275.
Build.prop says 275 is correct for qHD screens, but 270 fits a little better.
rjohnstone said:
I'm still trying to decide between 270 and 275.
Build.prop says 275 is correct for qHD screens, but 270 fits a little better.
Click to expand...
Click to collapse
content on the right edge goes out of the screen
add some 4x1 size widget so that you can compare the space left on both edges.. 270 looked perfect
IMO 260 is ALMOST perfect
would love to try this if i can get one of the root methods to work but thanks for the info! more motivation to try harder lol
270 or 275 I still have the huge space in the bottom part.
Yeah I'm going to use a launcher until the vertical spacing can get worked out.
pmcnano said:
270 or 275 I still have the huge space in the bottom part.
Click to expand...
Click to collapse
That's an issue with the launcher itself.
270 makes all the text bigger. Not digging it
Sent from my MB860 using XDA App
neer2005 said:
270 makes all the text bigger. Not digging it
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah, 270 looks way too big for me. Sticking with the default 240 for now.
Jotokun said:
Yeah, 270 looks way too big for me. Sticking with the default 240 for now.
Click to expand...
Click to collapse
Same here, i really don't see anything wrong with 240 either. 270 is definitely too big for me though
I'm using 268 o.o
updated OP with the note
NOTE: The Change in density is required for the stock launcher of 2.3.4 HKTW rom. The device is otherwise crisp at default with other launchers.. So do not bother incase you dont want to use stock launcher.
anyone know how to remove the black bar in notifications?
Problem is whenever you change the lcd density on atrix the dialer crashes. I've been trying to do this since atrix first came out and knowone has been able to make it work. Are you saying u can change the density on this new build and the dialer does not crash!!??
DukeL said:
Problem is whenever you change the lcd density on atrix the dialer crashes. I've been trying to do this since atrix first came out and knowone has been able to make it work. Are you saying u can change the density on this new build and the dialer does not crash!!??
Click to expand...
Click to collapse
Yes 10char
DukeL said:
Problem is whenever you change the lcd density on atrix the dialer crashes. I've been trying to do this since atrix first came out and knowone has been able to make it work. Are you saying u can change the density on this new build and the dialer does not crash!!??
Click to expand...
Click to collapse
Yes.
The dialer on 2.3.4 works fine at higher pixel densities.
Sent from my MB860 using XDA App
Wow that is really good news! I always wanted to make everything a bit bigger as I thought the icons always looked a tad too small on the qHD resolution. That alone makes it worth upgrading!
Off topic but if you use the stock launcher simply for the new app drawer then this tip may help.
It is possible to use the new MotoBlur app drawer with any launcher. Simply replace the new launchers app drawer with a shortcut to 'all apps' app group.
Nottach said:
Off topic but if you use the stock launcher simply for the new app drawer then this tip may help.
It is possible to use the new MotoBlur app drawer with any launcher. Simply replace the new launchers app drawer with a shortcut to 'all apps' app group.
Click to expand...
Click to collapse
Mind explaining how to do that exactly? I'm on ADW EX and I have no clue lol
Hi there,
is there a way to get the Tablet UI without changing the DPI? I just changed it to 160 and eveything is really, really small Too small for my taste. So I was wondering if there is a way to get the Tablet UI without shrinking everything down?
Janzomaster said:
Hi there,
is there a way to get the Tablet UI without changing the DPI? I just changed it to 160 and eveything is really, really small Too small for my taste. So I was wondering if there is a way to get the Tablet UI without shrinking everything down?
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=1780970
But I didn't tried it yet.
Team EOS's nightly ROM's have a toggle for changing the systembar setup (from phatblet to tablet), but this doesn't activate system-wide tablet UI.
Are you rooted. I am running the latest AOKP and it has Tablet UI baked in.
Sent from my Nexus 7 using xda app-developers app
I use Paranoid Android which allows you to use tablet ui with a dpi of your choice.
I use 190.
*Sent from N7*
You can apply barrmullio's tabletUI code changes on any deodexed rom in the Dev section using my tool the autopatcher.
The tool works on CM10, AOKP and AOSP, and their derivative roms. It can be run on any PC, OSX, Linux or Windows. There is a GUI for Windows, but OSX and LInux will need to enter ONE command on the command-line.
I own a Nexus 7, so I added a bunch of the most useful code changes for our device to the tool.
No dpi ot build.prop edits needed, no market issues at all.
Curious about text size. I'm not rooted and think text on many apps is way small. If changing to 160 makes it smaller, can I assume changing it to 240 makes it bigger? Moon Phase Pro, and Amazon Appstore are 2 in particular that I find difficult to read.
Everything is much larger on my 5" screen Galaxy Player.
tcat007 said:
Curious about text size. I'm not rooted and think text on many apps is way small. If changing to 160 makes it smaller, can I assume changing it to 240 makes it bigger? Moon Phase Pro, and Amazon Appstore are 2 in particular that I find difficult to read.
Everything is much larger on my 5" screen Galaxy Player.
Click to expand...
Click to collapse
yeap. they will be bigger but I think a lot bigger, since stock dpi is 213.
Thanks a lot guys! I used Barmullios mod linked by Glimmling, doing just what I want.
The note was made for 240 dpi, and yet Samsung insist on making it 320dpi and giving us massive icons. I mines 240dpi via build change but it comes at a compromise.
Has anyone managed to get everything working fine at 240dpi or know of a ROM that supports it?
Sent from my GT-N7100 using xda premium
Right now no ROM officially supports it sahilaurora tried asking mike1986 if he will adding 240 dpi but it seems his rom is totally stock.
Omega doesnt offer it too...
You can try cm10 if port if you want
Right now all touchwiz roms will have compromises
Jamal Ahmed said:
Right now no ROM officially supports it sahilaurora tried asking mike1986 if he will adding 240 dpi but it seems his rom is totally stock.
Omega doesnt offer it too...
You can try cm10 if port if you want
Right now all touchwiz roms will have compromises
Click to expand...
Click to collapse
I hope for a ParanoidAndroid version by imilka as on the Note1 soon. See link Note1 http://forum.xda-developers.com/showthread.php?t=1797698.
Hmm...maybe I´m wrong, but it shouldn´t be any problem to change your DPI to 240 DPI using ROM Toolbox (or a similar app). TouchWiz wouldn´t stand this procedure, but you can use Apex or Nova instead without a problem.
And it wouldn´t be the first time that someone asks for providing a 240 DPI compatible version of S-Note It has always worked in the past, so why shouldn´t it work with the Note II?!
I´m not rooted yet (just having a test device), so I can´t try it out...but maybe someone here on the board sacrifieces some minutes to check it out^^
gee2012 said:
I hope for a ParanoidAndroid version by imilka as on the Note1 soon. See link Note1 http://forum.xda-developers.com/showthread.php?t=1797698.
Click to expand...
Click to collapse
We really hope...
I used that ROM alot back when i used Note 1 awesome. but it was already stable enough
In any case, any paranoid android/CM we will be getting on Note 2 will be unofficial as CM team has dropped support for exynos devices
240 works, however you get FC on the keyboard (which is perfect for the Note II) And the camera is all small, so is the dialer.
S-Notes is fine. So if you repalce the dialer,camera app and the keyboard you are fine to use 240 to 200 DPI. But is it worth it loosing the stock keyboard and camera? No..
Losing the stock keyboard is fine IMO, as there are loads of really good alternatives... apart from the fact handwriting with the SPen relies on it. For me that's no big deal, it's a gimmick anyway, but it could be a killer for others.
Hi all,
I've been trying really hard to adapt the stock GNote2 software for 240dpi but to no avail.
Basically the issue is the keyboard which crashes at 240dpi. It works anywhere from 320 down to 270 dpi (280-270 dpi is already nicer than 320 dpi, but it's definitely 240 dpi that we want ) but with a lower DPI it crashes.
What I am saying is that I think all the "button too small" issues can be fixed. For instance I have more or less successfully resized the Samsung keyboard for 280 DPI. All the other apps should be no problem: camera, e-mail...
But with the Samsung Keyboard crashing whatever I do I am stuck. Even when I resized the buttons for 240 DPI. I don't know what to do with that.
Something nice would be to "fake" the system DPI so that the Samsung keyboard still thinks it is at 320 DPI, but there seems no way to do that easilly (i.e. no source code hacking). Paranoid/Android does something like that with their "Per App Dpi" but I am not sure that we would reuse their code on Stock Samsung apps... They suggest that it is tied to CM.
Mmmm... Maybe the note 10.1 apps work with 240dpi... Worth a try
Can someone get this apps and installd it on the note?
- f3w1n -
Continuing on my previous post...
It sees the Samsung keyboard crashes because below 270dpi Android switches to "tablet mode". Application would not be made for it crash.
I don't know if there is any way around that? I guess Android uses the screen resolution to compute the --supposed-- size of the screen and then choose between tablet (big screen) and phone (small screen) modes.
NexusCrawler said:
Continuing on my previous post...
It sees the Samsung keyboard crashes because below 270dpi Android switches to "tablet mode". Application would not be made for it crash.
I don't know if there is any way around that? I guess Android uses the screen resolution to compute the --supposed-- size of the screen and then choose between tablet (big screen) and phone (small screen) modes.
Click to expand...
Click to collapse
Thats why i said to use note 10.1 apps.
- f3w1n -
f3w1n said:
Thats why i said to use note 10.1 apps.
Click to expand...
Click to collapse
Not sure what would be the result, do you have the Note 10.1 apps at hand?
Anyway, I have found the following thread which suggests that we could hardcode the DPI for specific applications: http://forum.xda-developers.com/showthread.php?t=1903519
If we could just force the Samsung keyboard to behave as if we were at 320 DPI, always and whatever the system settings, that would be perfect in my opinion...
I dont have it, but the keyboard can be stracted from the jb ota leaked or try the ics keyboard from any of the note 10.1 roms
- f3w1n -
Hendrickson said:
240 works, however you get FC on the keyboard (which is perfect for the Note II) And the camera is all small, so is the dialer.
S-Notes is fine. So if you repalce the dialer,camera app and the keyboard you are fine to use 240 to 200 DPI. But is it worth it loosing the stock keyboard and camera? No..
Click to expand...
Click to collapse
I'm fine with those compromises, so what's the easiest way for me to switch to 240? Never messed with dpi changes...
I'm sure I saw a comment on a thread here (screenshot thread, perhaps) from somebody running 189DPI... I'd love to hear more about that.
I'm running 240DPI at the moment and for me, with a few quirks, it's fine. I dislike the Samsung keyboard so changed that to Swype on day-one of owning the Note 2. So really all I'm left with is the odd graphical problem or quirk (such as the comedy-looking dialer) which is fine by me.
Can someone using 240 dpi post some screenshots of their icons please
Sent from my GT-N7100 using Tapatalk 2
I have a running 240 DPI rom with fixed camera app and touchwiz. Its got a few set backs for example not spen touchwiz detection. And no samsung keyboard, instead I installed swiftkey.
I might release it soon...
What's the easiest way to change dpi? I'm already rooted and want to try 270 since you guys says that's the lowest we can run without problems.
Brgds... /Tubgirl
Sent from my GT-N7100 via Tapatalk 2
Why we go for 240?its better?
Sent from my GT-N7100 using Tapatalk 2
Tubgirl said:
What's the easiest way to change dpi? I'm already rooted and want to try 270 since you guys says that's the lowest we can run without problems.
Brgds... /Tubgirl
Sent from my GT-N7100 via Tapatalk 2
Click to expand...
Click to collapse
Edit build.prop and reboot or install any dpi changer app
Sent from my GT-N7100 using xda app-developers app
I tried many and settled on 360, the camera is wonky now but everything else feels much better. What is everyone else using?
Update* use xposed framework and app setting module and you can change the camera back to 480, works perfect now!
randyspants said:
I tried many and settled on 360, the camera is wonky now but everything else feels much better. What is everyone else using?
Click to expand...
Click to collapse
I'm getting my G2 tomorrow, have you noticed any issues with changing DPI? I'd like to do so, but whenever I would change DPI on previous Android devices, a lot of the UI would get messed up.
Why not just change font and icon size in settings?
Sent from my LG-P769 using XDA Premium 4 mobile app
The only thing that's weird so far is the camera, the preview when u go to take a picture only takes up about 2/3 of the screen.
I did try originally to just use smaller fonts but everything was still way too big, felt like a fisher price phone for toddlers
guencentHis
You could install Xposed framework and the App Setting module and set camera (and any other apps) back to 480.
psychoace said:
Why not just change font and icon size in settings?
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Changing the DPI is like increasing the resolution, you get more screen real estate as everything is smaller, not just text.
geoff5093 said:
Changing the DPI is like increasing the resolution, you get more screen real estate as everything is smaller, not just text.
Click to expand...
Click to collapse
How can you edit DPI resolution on G2 ?
sorry
wolfgart said:
How can you edit DPI resolution on G2 ?
sorry
Click to expand...
Click to collapse
I was going to ask the same question, not sure you can do it without root.
geoff5093 said:
I was going to ask the same question, not sure you can do it without root.
Click to expand...
Click to collapse
Yes, it requires root.
i can root it ! i've F320K korean model
Let me know
i'd like to know how, too. can you also make the height of the navbar smaller so that you have more screen real estate too?
i have the problems with the video player resolution after the change
magikatane said:
i have the problems with the video player resolution after the change
Click to expand...
Click to collapse
I know you can use texdroider_DPI from the play store to change the density but idk the steps for setting the individual apps like the camera. Can someone give some info here?
Bootloop !!
Hello,
-> I use the official ROM LG.
-> My LG G2 ( D802) is root.
-> I use texdroider_DPI to cross(spend) in 360 DPI.
Unfortunately my G2 no boot not any more ( BootLoop). I restored my image with CWM :good:
How did you modify the DPI in 360 so that it works?
PS: translation with reverso.net
I used texdroider to 400. Looks good. Camera window isn't staying full screen but works.
No other side effects.
I chose 400 because looking through the build.prop, it has notations for 400 being an "alternate_dpi".
I'm assuming for Video out. Anyway no problems.
-sent from my LG G2 using XDA Premium 4
Sitting at 320 here with App Settings/XPosed FW putting the camera back to 480, so you can see the whole preview. At first I thought it was too small but I gave it a day. Now anything bigger just makes me feel like an old person using a phone with huge buttons.
jayochs said:
i'd like to know how, too. can you also make the height of the navbar smaller so that you have more screen real estate too?
Click to expand...
Click to collapse
When you change the LCD density it scales everything.
The way to alter it is changing the LCD density in the build.prop file located in /system/
I used ROM Toolbox Lite to change mine.
cron912 said:
You could install Xposed framework and the App Setting module and set camera (and any other apps) back to 480.
Click to expand...
Click to collapse
Thanks so much, this fixed it for me as well!
my setup
Hi there,
So this is what I'm on right now and I'm in love with my g2:
-just rooted it, no rom
-xposed framework with the G2 and app settings module
-all-in-one gestures from the playstore!!
so I disabled my softkeys with the G2 module and created buttons with the all-in-one gesture app (menu, home and backbutton). BYE BYE softkeys! and then with app settings module I choose to have full screen and 360 dpi for the most common apps. (browser, phone, facebook, xda, ninja sms,...)
I think the app settings module is great cause you can set it per app.
LOVING MY BIG SCREEN and my invincible softkeys!!!
I'm using 200 dpi. Might change it but so far it ok for me.
Thanks for the tip on using xpose framework and using app setting on the camera.
Now everything looks good.
Edit: i change the dpi to 240 since there's a weird bug where i can't access or use the menu key.