Hi all,
I love my Tab S 8.4, it's light, elegant, fast with the replacement ROM Definitive ROM NF9. But my old eyes don't like the tiny fonts under icons, as well as in a variety of applications. I've changed the font size in the settings to Extra Large, but that doesn't really help in most apps. One of the reasons I switched to tablets and ereaders was to not have to put on readers every time I want to look at anything.
I've tried using Textdroider to increase the size of things, but it just created a SystemUI bootloop.
Has anyone figured out a way to make everything larger? Without crashing the system? I've also tried using Xposed module App Settings but nothing seems to happen when I use it.
Would love to solve this, otherwise a lower resolution tablet might be in my future. Wish there was something simple like the scaling option in Windows 7.
Thanks for the help.
android94301 said:
Hi all,
I love my Tab S 8.4, it's light, elegant, fast with the replacement ROM Definitive ROM NF9. But my old eyes don't like the tiny fonts under icons, as well as in a variety of applications. I've changed the font size in the settings to Extra Large, but that doesn't really help in most apps. One of the reasons I switched to tablets and ereaders was to not have to put on readers every time I want to look at anything.
I've tried using Textdroider to increase the size of things, but it just created a SystemUI bootloop.
Has anyone figured out a way to make everything larger? Without crashing the system? I've also tried using Xposed module App Settings but nothing seems to happen when I use it.
Would love to solve this, otherwise a lower resolution tablet might be in my future. Wish there was something simple like the scaling option in Windows 7.
Thanks for the help.
Click to expand...
Click to collapse
You can try to change the DPI..
Basically, by setting a higher value everything will be bigger. (But too much and it will become ugly/unresponsive)
There are 2 ways to do this:
1) Change the DPI for the whole device:
This can be done by changing it in the file build.prop.
Afterwards reboot and you're set.
2) Change the DPI per app
Download + install Xposed Framework.
Then open XPosed, go to download and look for the module "App Settings".
Install it, activate it & reboot the device.
Afterwards you can change the DPI settings for each app individually with the App Settings app.
I would advice that you try option 2, as this gives you more options aswel as the changes are immediatly, and you don't have to worry about editing or messing up build.prop.
shifter7 said:
You can try to change the DPI..
Basically, by setting a higher value everything will be bigger. (But too much and it will become ugly/unresponsive)
There are 2 ways to do this:
1) Change the DPI for the whole device:
This can be done by changing it in the file build.prop.
Afterwards reboot and you're set.
2) Change the DPI per app
Download + install Xposed Framework.
Then open XPosed, go to download and look for the module "App Settings".
Install it, activate it & reboot the device.
Afterwards you can change the DPI settings for each app individually with the App Settings app.
I would advice that you try option 2, as this gives you more options as well as the changes are immediately, and you don't have to worry about editing or messing up build.prop.
Click to expand...
Click to collapse
I tried both, as Textdroider changes build.prop. Also, App Settings doesn't seem to change anything. Even after I reboot apps like Opera, or Feedly, still have small fonts. What numbers should I use with it? I tried 400 for dpi and 150 for font scaling.
Thanks for any help with this.
As you found out, changing dpi will give you boot loop. Not a lot you can do.
Feedly is hopeless. The font size is tiny. Try using Amber or gReader.
As for the web, you are at the mercy of web coders. If they use relative font size, you can increase with text scale. If they use absolute font size, which so many of them do, you are stuck. You can try another browser like Firefox to see if its text scaling works any better.
Hi if you are still interested I have a solution. It's not so simple though.
Install the CM12 build (lollipop)
http://forum.xda-developers.com/showthread.php?p=57853197
It's very smooth and stable. Some hardware stuff are missing, because CM12 is new and also Samsung is not helping out the devs any with their lack of driver code release.
Anyway, changing the DPI on this Rom will work. Here's a screen shot of my tapatalk. You can see how big the fonts are at 400 dpi
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried it with DPI changer but it did not take. I just ended up changing /system/build.prop myself. Change permission to 666, open in any text editor, look for
ro.sf.lcd_density=320
and change 320 to 400. Save and reopen file to verify that the change you made sticks. Then change file permission back to 644.
There's another file /system/media/lcd_density.txt. It just contains the text 320. I changed it to 400. I don't know if that is necessary or not but did it anyway. Same procedure above applies.
Reboot and cross your fingers.
If that works, you can experiment and change to something other than 400 if you want. You'll want to do a full nandroid back up before doing this.
Thanks for a solution that isn't "wear readers"
barth2 said:
Hi if you are still interested I have a solution. It's not so simple though.
Install the CM12 build (lollipop)
http://forum.xda-developers.com/showthread.php?p=57853197
It's very smooth and stable. Some hardware stuff are missing, because CM12 is new and also Samsung is not helping out the devs any with their lack of driver code release.
Anyway, changing the DPI on this Rom will work. Here's a screen shot of my tapatalk. You can see how big the fonts are at 400 dpi
I tried it with DPI changer but it did not take. I just ended up changing /system/build.prop myself. Change permission to 666, open in any text editor, look for
ro.sf.lcd_density=320
and change 320 to 400. Save and reopen file to verify that the change you made sticks. Then change file permission back to 644.
There's another file /system/media/lcd_density.txt. It just contains the text 320. I changed it to 400. I don't know if that is necessary or not but did it anyway. Same procedure above applies.
Reboot and cross your fingers.
If that works, you can experiment and change to something other than 400 if you want. You'll want to do a full nandroid back up before doing this.
Click to expand...
Click to collapse
Thanks, that is very helpful...I'm not clear on the hardware limitations of the lollipop build though. I don't care about the fingerprint reader, probably don't even care about the camera, but would want the sound system to work well. Wifi of course too, but bluetooth not so much. What are the limitations of the CM12 lolli build you are running to get the dpi to 400?
Wi-Fi works, it would not be useable otherwise It only seems to connect to my router on 2.4ghz and not 5ghz, but speed is good. Audio works fine. Camera works. When you take a selfie it says cannot connect to camera but it actually does work anyway. I haven't tried Skype. Blue tooth works but I don't have any device to test it with at the moment. I think things like IR and NFC don't work and may never do. No big loss as fat as I'm concerned.
Main issue right now is you need to disable hardware overlay for video to work. This means that you take a performance hit when it comes to graphics, and probably more battery drain than otherwise. Practically speaking, I notice a little bit more blurring with video. 3Dmark is like 5% lower than average score with hardware overlay disabled. Not a huge deal. Netflix, YouTube, Amazon video, MX player, BS player are all working for me.
Overall, the OS is smoother and less laggy than stock. You get all the lollipop goodness, too, of course. CM12 is in early beta and there's not even official CM support for this tablet yet so things can only get better.
If your eyes don't glaze over when you hear things like nandroid backup, recovery, etc, definitely give it a shot.
Related
I changed the screen dpi to 200 but now miui launcher looks weird.
So I'm using adw launcher with 1 extra row and looks nice, however I like the way miui launcher functions, like when I install a app it immediately puts it on desktop, just like the iphone.
Is there any launcher that acts like this and also allows to change number of rows and columns?
this is miui default, folders and other widgets look even weirder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adw is perfect
out of interest, how did you change it?
with lcd density, app from market
Naffets said:
out of interest, how did you change it?
Click to expand...
Click to collapse
You change the LCD density string in build.prop to set it permanently, or use lcd density changer from the market to do a temp change.
You can use a tool called "Absolute System" to edit the build.prop easily.
Sent from my GT-I9100 using Tapatalk
you can use launcherpro which allows to change number of rows and columns
and what would exactly be the point in changing it?
may be engwee wants to see more apps at the same time without moving the screen up and down
Jiniko77 said:
and what would exactly be the point in changing it?
Click to expand...
Click to collapse
changing the lcd density has the same same effect as changing the resolution on your pc monitor. the phone will fit more on the display, so smaller icons and text etc...
any of this apps are changing the phone dialer too ?.....???
None of the sammy aps like dialer change with DPI changes, everything looks smaller and a bit crap, you will either need to find a ROM with DPI changes built in for that or there might be a theme you can use maybe.
My theme is built for changed DPI (shameless plug)
Sent from my GT-I9100 using xda premium
da.trute said:
None of the sammy aps like dialer change with DPI changes, everything looks smaller and a bit crap, you will either need to find a ROM with DPI changes built in for that or there might be a theme you can use maybe.
Click to expand...
Click to collapse
Yes, TouchWiz doesn't play nice with DPI changes. Use Go Contacts (includes dialer) for dialer - I haven't found a MULTI-DPI camera replacement yet tho.
Sent from my GT-I9100 using xda premium
Changing LCD Density
Changing the density changes the whole phone - if you set density to a lower number everything will be smaller on the screen and then you can fit more items on the screen. A higher number will make things bigger and fit less.
An unfortunate side effect of changing DPI however is that quite a lot of apps don't like it and will force close when you try and open them. For example, I just set mine to 200dpi and Angry Birds FC's.
The Market is another app that seems to be fairly DPI sensitive, however in my case right now running CM7 nightly the Market is working fine at 200dpi.
Another effect can also be black bands around apps that are not written to scale to screen DPI but rather with hard coded sizes for LDPI/MDPI/HDPI.
Cheers!
ecips said:
Changing the density changes the whole phone - if you set density to a lower number everything will be smaller on the screen and then you can fit more items on the screen. A higher number will make things bigger and fit less.
Click to expand...
Click to collapse
Gotcha!
You've got PM!!!
Big sorry for polluting the thread, but i can't seem to get a hold of ecips
ayk33 said:
you can use launcherpro which allows to change number of rows and columns
Click to expand...
Click to collapse
like I said in my first post, I'm using ADW and it works fine with it, I was looking for a miui like launcher, with all the apps on desk and no app drawer, probably doesn't exist.
While I was on miui rom I didn't encounter problems with the apps I used, this goes from games to standard apps, like the market.
Now I'm on stock and I saw the dialer is small, but no problem otherwise, when I get called the slider works fine.
the advantage is it makes the screen seem like higher res, browser fits a lot more content, holding it next to a sensation it looks the same, one difference I encountered on sensation is a game megajump, doesn't fill out the screen while on sgs2 with dpi change it still does.
it probably looks so good because of the samoled + subpixel density stuff
It makes it look extremely hi-res. I can't, no, WON'T have my phone at stock DPI, ever.
Sent from my GT-I9100 using xda premium
'Nough said...I switched to 200 and i'm in love baby. Only problem...dialler misplaced and camera screwed up. Any ideas?
my ideea is to live with them, my camera app is fine though
restarted phone today.. and it looks so ugly with the initial dpi
engwee said:
my ideea is to live with them, my camera app is fine though
restarted phone today.. and it looks so ugly with the initial dpi
Click to expand...
Click to collapse
yes camera it's fine at 200 dpi in kg5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an ongoing developer project to make way for a modification that will entirely transform your device, but retain the aesthetics and the experience of your phone. I know you've seen tablet mode roms before, and indeed it's a start, but this ain't enough. This thing has potential, but it is wasted the moment you try to stuff a full blown tablet into your poor phone. Yet we all know our high res phones can very well handle more than silly 1-column layouts. So the magic must be in between somewhere, a place that Google must have overlooked and left blank.
Yes, this rom strives to drop your device into tablet mode, but it won't stop there, it will reshape and redefine ICS to make it all a usefull addition and not just a cute novelty. i'm calling it: Hybrid Mode, best of both worlds.
Donations to CM http://forum.cyanogenmod.com/donate, to D4rKn3sSyShttp://forum.xda-developers.com/donatetome.php?u=3484876, to me http://forum.xda-developers.com/donatetome.php?u=4491046
If you come from another rom than CM9 or PA, factory wipe is a must (wipe data)
Install Rom: http://www.mediafire.com/?ou19f3k0yrp836b -DO NOT DOWNLOAD FROM YOUR PHONE!!!!!
Install Fix: http://www.mediafire.com/?8q9mrvmi6ht984m
Install Gapps: http://tjohansson.is-a-geek.com/files/gapps-ics-20120511-fixed.zip
Wipe Cache
Advanced/Wipe Dalvik Cache
If your statusbar is gone after the first reboot: longpress Powerbutton > Toggle Statusbar
Reboot and edit your Apps Dpi & Layout under Settings/Paranoid Settings
Go to Settings, System, Font size, set it to NORMAL
Check "Auto Hide" in Settings, System, Statusbar, to finally get Fullscreen
Trebuchet Settings: margins:SMALL, show permanent searchbar:YES, Grid: 5x4, resize all widgets:YES, Wallpaper scrolling: OFF
Themes and other goodies you can find here: http://forum.xda-developers.com/showthread.php?t=1646034
---
Tina: http://krebsmilk.de/
Cyanogenmod Team
Franko, for his Kernel
20120521v0.9beta: P.A.L., PROBABLY THE MOST AWESOME FEATURE EVER
First time in Android history that Per-App-Layout has been realized
Comes with a better panel
Allows you to switch between Phone mode (with curtain and bear paw buttons) and tablet UI seamlessly. PAD & PAL work in both domains. That means you can have 3d Youtube in 320 dpi standard Phone mode or mobile Chrome without those horrible tabs in 192 Dpi Tablet mode.
Since PAL solved all scaling issues our Trebuchet fork is now obsolete. It comes with Nova 1.1.4 projected into mobile layout.
20120517v0.6beta: Bugfixes, new PAD panel, Fullscreen-toggle
Fresh cm9 repo
Franco Milestone 3
Bugfixes for PAD preventing it from screwing up some apps (notification icons were bigger for some apps, launchers would display icons bigger or smaller, etc.)
New PAD panel, lists DPI's, can delete values again
Powermenu Fullscreen-toggle, this finally allows you to play games without navigationbar!
20120504v0.4preview: Apps were too small? Problem solved!
First ever Android ROM with Per-App-Density feature, it once and for all solves the problem that was tablet mode. You never, ever have to deal with apps that are too small again since now you can decide how apps, systemapps, framework-elements and even widgets are scaled by defining their native dpi seperately from the system DPI. Its an experimental feature and for now these values are defined in your /system/build.prop - it has drawbacks (maily notifications can look a bit strange), but that will be fixed in time. Warning: Keyboards MUST run in system DPI!
A list of apps and predefined values is included, this should include most of what you need. everything else is blown up to 210 dpi per standard. if you still need apps to be bigger, get a build.prop editor from the market, edit and reboot.
Trebuchet fixes: Folder Name cut-off, landscape name cut-off, divider bars
Please set your Font to "Normal" in the System Settings, you won't need "Huge" anymore and all this does now is provoke overlapping.
20120430v0.3alpha:
Freshest CM9 Repo
Forked Trebuchet and rewrote its layout and parts of its code to adapt it to tablet mode. I went for stock look plus tablet controls and changed the number of icons/widgets shown in the drawer. It's butter-smooth aswell. It has kinks left, those will be solved in the coming days!
100% fixed android standard keyboard
Better Bootanimation
Fixed Gapps package based on 20120429 including Gmail and a working Market
20120427v0.2pre-alpha-gapps:
Fixed Gapps package based on 20120422 including Gmail and a working Market
20120427v0.2pre-alpha:
PARANOIDANDROID custom bootanimation, still has some kinks - first sketch though
crystall clear thumbnails in the recents window, pixel mush no more!
brightness setting easier accessable
ICS toggle button fixes
20120425v0.1pre-alpha:
freshest CM9/nightly repo build (25/04)
recents window way nicer than before. close to stock. i only need to get rid of that darn gradient
keyboard looks like stock now
new bootanimation
camera works
comes with cm9 repo kernel, no color tint
notification clock is smaller, won't overlap so easy
20120425v0.0pre-alpha:
freshest CM9/nightly repo build set to tablet mode
Hacked Nova. I know 1.1 is out, but this one is still closer to stock
Androids keyboard reacts hellish in tablet mode. I fixed it but its still too large, tomorrow i'll fix it proper
I was trying make to recents window look more like stock. COULD be the thumbnails are a tad bigger than before but i'll get to that don't worry
2 notifications icons max in portrait for now to prevent overlapping
Settings comes as the first item in the notification panel, hated to scroll down every time
ALOT will follow, please be patient, i made all that stuff blind because it needed ~13 hours to compile. now compiling is alot faster and i'll see to it that we will have true hybrid mode very soon
im currently uploading a test version for you guys, i cannot guarantee that it'll work, im doing it blindly as i have maguro. if you dont wanna put yourself into a risky position, do not flash. although it really should be fine.
This looks epic
Sent from my GT-P3113 using Tapatalk 2
Looks awesome! Will def try it out! Tks for this!
there you go: http://www.mediafire.com/?rdejrqkw6oc5r7q
please report back if its working, if not i have to take away the link and try something else. thanks!
This looks pretty crazy, I definitely want to check this out, probably wait until I hear something/anything though.
Sent from my Galaxy Nexus using Tapatalk 2
This does look nice.. I'll have to do a how to install and review video
does that mean it works? coz that would be super!
About to flash will report back in a few.
Thank you for working on this/ bringing it to us
Edit: It works xD
And BTW The Bootani is awesome haha
Looks awesome, I've been running tablet mode (the other way) since last night and have noticed some likes and dislikes.
I love the all in one bar at the bottom but don't like the button sizing in some of the apps and other places and I like how the settings menu and gmail are split like a tablet
Might try to flash this when I get home to see how it compares
Sent from my Galaxy Nexus using XDA App
yeah i know what you mean. i've done that before and tablet really has alot of kinks. thats why i grasped the idea to do something about it. im only sitting on it for four days unfortunately so many things need more work. but heres a list so you know what to expect
screwed launcher: partially fixed
screwed phone, incall crashes: fixed, needs layout fixes aswell to look better
market incompatibility: fixed 100%
overlapping clock: fixed
overlapping notification icons: fixed
ugly as heck recents window: partially fixed
screwed android keyboard: fixed 100%
UI elements are too small: soon
apps are too small: i can make some hacks, but i'll look into a more general solution like per app dpi. no idea though if i can pull it off
qbking77 said:
This does look nice.. I'll have to do a how to install and review video
Click to expand...
Click to collapse
+1
Where did you get those awesome face wallpapers? They look great!
I'm using SwiftKey 3 Beta and the keyboard is ridiculously small but other than that I love this tablet look!
Sent from my Galaxy Nexus using Tapatalk 2
i believe it has a hight setting to adjust it. keyboards that work perfect are fixed android one from this rom, skype, thumbkeys, and yeah well swiftkeys so i heard - but i cant type with that thing, makes me dizzy to type and check type and check type and check, so i havent bothered to try it in tabmode.
Thanks for this awesome rom
Sent from my Galaxy Nexus using xda premium
molesarecoming said:
i believe it has a hight setting to adjust it. keyboards that work perfect are fixed android one from this rom, skype, thumbkeys, and yeah well swiftkeys so i heard - but i cant type with that thing, makes me dizzy to type and check type and check type and check, so i havent bothered to try it in tabmode.
Click to expand...
Click to collapse
Thanks for the tip. I'll try a different setting or keyboard
Sent from my Galaxy Nexus using Tapatalk 2
sorry i meant sWype of course. its not in the market, you can get the beta from their site.
I think we can say that we are on fire right now!!!
Does it bother you that apps and menus look too big and sometimes not sharp as it should be ? Do you want to see more details and do less scrolling on web browsers, emails, file explorers and more ? Do you use a third party launcher ? If the answer to all of the above is YES, this is for you!
Please read everything carefully before you begin!
Requirements:
- LG Optimus G Pro
- Root
- Xposed Framework (excellent for other stuff too!).
- App Settings
- Build Prop Editor (you can edit the build.prop with root file explorer too).
- Some Root File Explorer - ES File Explorer (my favorite).
!Warning!
This mod is generally safe, BUT it can harm you device and cause your device to bootloop or FC apps. I'm not responsible for any problem cause by my instructions!
!Warning 2!
You have to have a third party launcher like Nova/Apex/Next/Go etc (as default) before you begin the processes!
1. Root your LGOGP (voids your warranty).
2. Make a backup of the build.prop TO YOUR PC. You can find it in /System/ directory.
3. Install Xposed Framework following the instructions in the link - Xposed Framework
4. Install App Settings from the link and enable it in Xposed Modules - App Settings (don't forget to reboot).
5. Install Build Prop Editor
5. Open Build Prop Editor (don't forget to grant it root privilege) and look for "ro.sf.lcd_density" the property value should be "480". Change it to "360" or "320" (I found it most appropriate, but you can change it to what ever suit you). Save and reboot.
Known Issues:
I did some testing and found 2 major issues.
1. The Home Launcher Force Closing. For now I haven't found a fix (If you don't use the original launcher you're golden). EDIT: I Found a fix. Open App Setting and look for "Home" (come.lge.launcher2), set in its options "xlarge res" (no need to change anything else) and save.
2. Camera view gets messed. This is where Xposed and App Setting come to play. All you have to do is to open App Settings, look for "Camera" (com.lge.camera) and set in its options the DPI to "480" and save.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
reserved for no reason...
Been using the AppSettings for awhile, and found 2 problems
1. Apps seems to delay a bit longer to load, dunno if it's because it redraws or it's just feels longer because you can see first the big interface then small.
2. There is a gap of a few pixels between the StatusBar and the HomeScreen/Apps that have it. FullScreen apps works like a charm.
Hi Kriggs,
With my instructions there isn't noticeable gap as in your screen shoot, I haven't notice any lag as well.
liamR said:
Hi Kriggs,
With my instructions there isn't noticeable gap as in your screen shoot, I haven't notice any lag as well.
Click to expand...
Click to collapse
Yeah, I should've said I'm still using the stock launcher, haven't been able to change the "Android System" to 320dpi, it's him who FC the launcher, and probably who runs the top bar size.
I really like LG's stock launcher and the black line is a minus so I'm keeping it, for now. I'll change build.prop when CM10.1 is all working
I played around with this a few days ago and couldn't get anything to work well except a density of 400 (which also happens to be what the secondary density is set to in the build.prop). Everything seems to scale correctly with the stock applications except the camera. The camera has black on the side and bottom of the screen, but still works ok. On any other density, the launcher ended up being mostly unusable (seemed to convert to a 4x4 homescreen grid). I did not do anything with the xposed framework though, just direct edit of the build.prop file.
can anyone post up some screenshots for comparison .. whats the main benefit here ???
thanks
Is there a way to put apps in tablet mode, 240/213 dpis are unusable here...
zohaer21 said:
can anyone post up some screenshots for comparison .. whats the main benefit here ???
thanks
Click to expand...
Click to collapse
More on screen thingys.
Stock dpi
320 dpi.
With Cyanogem it will look something like this, at leat for me:
draiko913 said:
I played around with this a few days ago and couldn't get anything to work well except a density of 400 (which also happens to be what the secondary density is set to in the build.prop). Everything seems to scale correctly with the stock applications except the camera. The camera has black on the side and bottom of the screen, but still works ok. On any other density, the launcher ended up being mostly unusable (seemed to convert to a 4x4 homescreen grid). I did not do anything with the xposed framework though, just direct edit of the build.prop file.
Click to expand...
Click to collapse
That's the old way to do it, nowadays it's better to just edit everything with AppSettings, the build.prop is good just so you don't have to set every app to the desired density, but you can achieve all on the fly with xPosed.
@Kriggs : thanks ... really makes a huge difference
This is how it looks with my way 360 dpi (attachment).
I found a fix for the LG home launcher FC. OP updated.
liamR said:
I found a fix for the LG home launcher FC. OP updated.
Click to expand...
Click to collapse
Almost all good, 2 things got messed up though:
Wallpaper gets cropped, not live wallpaper though
Transparente top bar in pop-up menus
Also, keyboard letter appears small in 320, setting font scale to 150 gets all back to normal
afaik, playstore won't support for dpi value except 320 - 400 - 480
i use 400 dpi and all look fit for my eyes using nova launcher (won't fit with stock launcher)
Can you guys post some screenies of your home screen and what settings you used. I did this work around a few days ago and my launcher screens came out all screwie especially any custom icons or widgets changed in nova or holo launcher. For example a email icon would be oversized but only 1/4th of the icon would be displayed same for widgets
ivantastic said:
afaik, playstore won't support for dpi value except 320 - 400 - 480
i use 400 dpi and all look fit for my eyes using nova launcher (won't fit with stock launcher)
Click to expand...
Click to collapse
Download and flash the multi dpi play store from the apps and games section of xda, I use the inverted one.
Sent from my Nexus 7 using Tapatalk 2
---------- Post added at 01:51 AM ---------- Previous post was at 01:46 AM ----------
Also to OP you know all you need to do is use a file explorer that uses root to navigate to /system/build.prop open it in a text editor mode and change the dpi to whatever. Just really seems like the long way to download 3 apps when you can do it with 1 and learn a little about Android in the process
Sent from my Nexus 7 using Tapatalk 2
Yeah, this is way too complicated for a 30 second process really. Just edit the stock build prop and reboot, all done.
Sent from my LG-E980 using Tapatalk 2
ballshanglow said:
Yeah, this is way too complicated for a 30 second process really. Just edit the stock build prop and reboot, all done.
Sent from my LG-E980 using Tapatalk 2
Click to expand...
Click to collapse
Yes but then your LG camera does not line up properly with the new dpi, if you don't care about the camera then yes editing the build prop is all is needed. I have set mine to 400 dpi and the xposed module works great.
Erik
Sent from my LG-E980 using Tapatalk 4
Density at 360, jb 4.3
Sent from my LG-E980 using xda app-developers app
Stock on 380 dpi with large font...minimum dpi stock launcher not crash...but only sky and water drop app wallpaper working in app drawer..
Sent from my LG-E988 using xda app-developers app
hi, just wondering if anyone has changed the dpi on the g3. if you have, what is the safe dpi number?
also, is there any web site like sammobile.com for lg phones?
thanks.
I've been playing with this a bit and can't get it right at the moment. I lose some functionality of LG programs and/or icons show as default images. I'm using xposed and App Settings to make the changes. Setting the main UI dpi to my desired setting means I have to set e.g. phone/contacts to 640 dpi to get it to load correctly plus their icons display incorrectly and show as Android default.....
If anyones got any ideas it would be appreciated.
Sent from my LG-D855 using XDA Free mobile app
swine... said:
I've been playing with this a bit and can't get it right at the moment. I lose some functionality of LG programs and/or icons show as default images. I'm using xposed and App Settings to make the changes. Setting the main UI dpi to my desired setting means I have to set e.g. phone/contacts to 640 dpi to get it to load correctly plus their icons display incorrectly and show as Android default.....
If anyones got any ideas it would be appreciated.
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
i set it down to 480 and the systemui just crashes, ended up have to restore the whole thing coz i cant access aromafm or cwm for that matter. last i tried 560 without fc, but i dont know if there is any icon missing. i am still new to this LG environment and still digging for lots of things. seems that it is not as easy as in samsung. on thing for sure, LG's software department needs to polish their software badly. it is just not up to the standard of a flagship phone. so cluttered around.
i am running it at 540 with no issues. i tried it at 520 and got systemui FCs. DO NOT GO BELOW 540!
didnt see this thread and set dpi to 180 and rekt the phone cant store is stuck in boot loop
I'm using 580 right now with no problems. Granted, I don't use widgets or the LG Launcher. Dual Window works fine. The Amazon app works but won't show in Play Store at this DPI.
Sent from my L Double G Triple
Where do you go to change the DPI settings?
s_special said:
Where do you go to change the DPI settings?
Click to expand...
Click to collapse
build.prop.
Loving the new screen density! Makes the phone so much more usable.
Ran into a issue with screen DPI 540 though.
Can't access app info. Keep getting this message.
I also tried 560 and 580 and had the same error message. Anyone else experiencing this?
I also tried using the xposed module app settings to change the phone's settings application to stock 640. nothing seems to work .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok after testing different settings for dpi I had to do a nandroid restore. I couldn't stop the force closes
Restoring DPI back to 640 stock fixes the FC's - just need to find the spot which doesn't FC apps.
radicalisto said:
Restoring DPI back to 640 stock fixes the FC's - just need to find the spot which doesn't FC apps.
Click to expand...
Click to collapse
restoring back to 640 didn't fix my FC. I had to restore my nandroid backup
I ended up trying again but instead of editing the build prop I used the xposed module app settings. I only edited the system UI. That seems to work without any of the error message. Only issue now is that the lockscreen needs to be adjusted.
Does anyone know the file to edit the lockscreen?
I use rom toolbox to change the dpi down to 540 without any big adverse effects. I do notice a slight lag in the touch screen tho
mrush said:
I use rom toolbox to change the dpi down to 540 without any big adverse effects. I do notice a slight lag in the touch screen tho
Click to expand...
Click to collapse
530 is the sweetspot.
Anything below that will cause weird looking icons and possible FC's.
530 and anything above that works just fine.
Hope that helps.
Regards,
Pdash
7
pdash79 said:
530 is the sweetspot.
Anything below that will cause weird looking icons and possible FC's.
530 and anything above that works just fine.
Hope that helps.
Regards,
Pdash
Click to expand...
Click to collapse
Thanks.. I tried editing the build prop again. I love the look but I experience the same single issue. Have you tried launching app info?
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Maybe I should just edit the app info file individually with the module app settings. Anyone know that file?
Is there no solution for my lock screen issue?? There must be a file I missing to manually edit.. When I edit the build prop the UI is great including the lockscreen.
Let me clarify. By editing the one file "system ui"
I get a good result with my overall dpi with exception to my lock screen.
When I turn off the module and edit the build prop DPI my lock screen looks good but I get crashes from the system apps and other apps.
And just for good measure I'll post a Screenshot of my lock screen at factory dpi
I use this app to change dpi to 560 even if 510, nothing happens until I use camera app. 2 left first functions in Setting and Mode disappear. I had to return 640. Is there any way to change dpi safe without any issue?
brian88 said:
I use this app to change dpi to 560 even if 510, nothing happens until I use camera app. 2 left first functions in Setting and Mode disappear. I had to return 640. Is there any way to change dpi safe without any issue?
Click to expand...
Click to collapse
You can change DPI for whole system in build.prop, and than individually in App Settings (xposed module). I have always do that. Usually phone app and camera have to be changed
I'm running at 440 dpi and I've set every LG apps at 640 using Xposed and AppSettings. I use Nova Launcher too in order not to have problems with big icons etc.
Anyone knows if is possible change resolution in adb? Or someting
Pretty sure you used to be able to use the following command
For resolution:
adb shell wm size 1080x1920
For screen density:
adb shell wm density 390
Obviously adjust numbers to suit your needs.
I accept no responsibility for any issues which may occur if you use these commands
Edit:
Did a quick bit of googling and found this which echos the above:
https://www.reddit.com/r/pokemongodev/comments/6554k1/_/dgfpesr
I know this is quite an old post, but couldn't find a newer one mentioning if changing screen res works. Did these commands worked fine with the 6 pro? And is there any noticable difference in battery life/performance if it does work?
I'm interested too. Give it a shot and report back on the results? I'm in the car all day, otherwise I would
There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.
B from C said:
There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.
Click to expand...
Click to collapse
I just tried that and needed to pull out my magnifying glass lol. Everything was so small!!
I've got mine at 474 with font set to large... happy medium for me
Gave it a try just now and it does work, however definitely not what I expected. Basically adds 2 huge top/bottomn notches and brings your rendered screen in the middle. Bottom gestures are almost impossible, as you have to start somewhere middle in the screen. And for unlocking the device - now you need 2 fingers - one to trigger the FP scanner because it ends up in the bottom right and one on the actual Scanner. Also you end up with a weirdly placed camera cutout that you cant remove.
I might try to run my phone like this for a day, as I wanted to experiment how the battery behaves. Menus seems really fast and smooth, but can be because the animations have less space and are shorter . If anyone has an idea for a command to stretch the screen over the whole display, I'd love to try.
Edit: Never mind, dumb me didnt adjust for screen ratio not being what I'm used to. After taking that into account 1080x2340 works. Fingerprint and camera cutout issues still persist though.
While this may be a little small/sharp for some people, I've been running "Smallest Width" at 720, which seems to yield a "Display Size" of 320dpi, along with default font size for awhile and have had no issues with the camera cutout or the fingerprint reader. I also use the AOD Notify app to put a glowing ring around the camera and didnt need to make any offsets so I'm pretty sure my camera cutout is where it's supposed to be.
I ran 320dpi/720width for years on a few Samsung Note devices prior to my P6P so that's what I'm used to (I'm one of those people who run a 4k tv as a monitor with no scaling). You may need to play with different dpi and font combinations until you find something you are comfortable with. In rare situations I have needed to restart the device or clear the cache for all UI elements to resize correctly after a change.
After a couple days of testing (it did indeed took me 2 days to kill my phone) I figured that for whatever reason, on the Pixel (maybe exynos) lowering the render res does indeed save some battery. On 1080p I managed to get around 1%/h - 2%/h less consumption on Screen on Time, which for people like me who manage to get 5+ hours of screen on time can result in quite of a difference. I regularly end days with something between 30-40% battery, which is still really good but I won't go to a second day as the 2 hours charge time is really annoying me .
With the lower resolution I ended the first day with 57% and I ended up with 37.5 hours of standby and 8 hours and 40 min of SoT in a full charge. I even went further by reducing the resolution to 720p, but it is really obvious that Google never made a 720p phone - almost all UI's broke and even changing the brightness was a hassle. I also believe that it might have triggered some rouge process as my phone lost 10% battery in less than an hour, so I switched back to my original 1440p.
To conclude this - is changing your resolution to 1080p worth the broken finger print - depends. In my example, I would probably do it if I know I am going on a trip where lots of pics/videos will be taken and heavy navigation use, as my phone is more of a tool in cases like that and I always try to squeeze every bit of battery I can. If google does implement the ability to change the res though - I would definitely switch.
I just wonder, why does it made such a big difference on this phone, but it didnt for S10(the only battery test I found on a video). Is Android 12 harder to drive? Or are these LTPO panels more intense on the GPU? Or is it even exynos/mali GPU not as efficient as SD on rendering UIs? If anyone wants to chime in - Id' be glad to hear some opinions. ( Or maybe I just used my phone less.. that would be the worst )
P.S. Just to say this was done on 60hz and that your milage might vary, if you decide to try. Everyone's usage is different and in my case I work from home - so WiFi connection (although router is far) but horrible signal, as I am a top flat in the UK (worst case scenario). The setting I used for the adb command is 1080x2340 and denstity was 400, although density is preference I guess and I believe wont affect battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value
liver20 said:
Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value
Click to expand...
Click to collapse
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel
roirraW edor ehT said:
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel
Click to expand...
Click to collapse
And doesn't break the fingerprint scanner like Easy DPI changer does
There must be a way of doing it without opening the bootloader, right? Or do you guys think it's impossible without breaking stuff like the fp scanner? I'd love to lower my resolution but I really didn't want to lose all my stuff and have to reinstall everything at this moment.
Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link
B from C said:
Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link
Click to expand...
Click to collapse
Thanks a million for this. The module fixed my screen flickering - couldn't go over approx 50% without flicker . I set the screen brightness from within Miscellaneous. Only problem is that I can't access Miscellaneous again without module force closing (other options are fine) - looking into the reason for it.