LG G2 is More Awesome with ̶3̶2̶0̶d̶p̶i̶ 380dpi
I came from galaxy note 2 before had G2
On that forum, people love 240dpi
Because the original 320dpi is too big and bulky
Not as crisp as 240dpi
After I got my G2
I realize, the current dpi is too big
And I edit build.prop and change to 320dpi
And modified home to works with 320dpi
You got to try it
It's really awesome G2 with 320dpi/380dpi/400dpi
I wish some skillfull dev will port original apps from 480 to 380dpi
In the mean time.... i just had to learn trial and error changing dimens
To make it looks good on 380
===========380dpi===========
@sosimple point me, he use 380 dpi, after I tried it, It's my favorite DPI now..
===========================
- - - How To Change DPI Manually - - -
===========================
1. You must be rooted (need root explorer/build.prop editor) + Xposed Module (App Settings)
2. search ro.sf.lcd_density=480
3. change it into ro.sf.lcd_density=380
4. reboot
drc13 said:
People might find experimenting with different DPI's easier with an app like texdroider rather than manually editing the build prop.
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
Click to expand...
Click to collapse
of course, many apps on playstore can change density
just search playstore
*some LG apps doesn't works properly with new DPI
*even playstore is acting weird
--------- the fix ---------
1. For LG Camera App and LG Message App
http://forum.xda-developers.com/showthread.php?p=48743938#post48743938
Install Xposed Frameworks - Open the apps - go to download menu
1. Install App Settings Module (for LG apps)
2. Install All apps in Play Store (for Playstore Fix)
3. reboot
4. open App Settings, Search Camera - click - On - DPI = 480
5. open All Apps in Play Store Module - change fake dpi to 480
I use between 390-400 I also use tiny text in the display settings so everything fits much nicer. I haven't tried 320 but I imagine that would be a bit too small for me.
320 r u serious? im using 400 and already feel thats little bit too small
Im using my tablet port for G2 and it hurts my hand using it. Woudnt advise to use at 300 or lower
480
Build prop set to 480, xposed app settings changes everything else that's compatible to 320.
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
spiderio said:
I came from galaxy note 2 before had G2
On that forum, people love 240dpi
Because the original 320dpi is too big and bulky
Not as crisp as 240dpi
After I got my G2
I realize, the current dpi is too big
And I edit build.prop and change to 320dpi
And modified home to works with 320dpi
You got to try it
It's really awesome G2 with 320dpi
I wish some skillfull dev will port original apps from 480 to 320dpi
In the mean time.... i just had to learn trial and error changing dimens
To make it looks good on 320
Click to expand...
Click to collapse
Unless you're running a ASOP ROM, stock LG apps dont scale right under a different density. It sucks. I agree though everything looks better at 320.
phatmanxxl said:
Build prop set to 480, xposed app settings changes everything else that's compatible to 320.
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
Unless you're running a ASOP ROM, stock LG apps dont scale right under a different density. It sucks. I agree though everything looks better at 320.
Click to expand...
Click to collapse
I am using 380 dpi. If you use xposed app settings , you can define stock lg apps to run in default dpi (480) so you have no problem at all..
sosimple said:
I am using 380 dpi. If you use xposed app settings , you can define stock lg apps to run in default dpi (480) so you have no problem at all..
Click to expand...
Click to collapse
Yea, I felt it was just easier to adjust the apps that looked better at 320 instead of the whole phone.
sosimple said:
I am using 380 dpi. If you use xposed app settings , you can define stock lg apps to run in default dpi (480) so you have no problem at all..
Click to expand...
Click to collapse
After I tried 380 and it's indeed better than 320..
It's not too small and still crisp great looking now..
anyone know how to edit lghome.apk dimens for 380..
I use app settings for LG camera.. set it 480
For home.apk is better hardcodded than using appsetting.
I am still searching how to make the quickwindow apps in 480 dpi, I haven't found for now.
Yup 320 DPI looks just like my note was on 240 DPI :laugh:
How come this all seems backwards to me...comparing to a PC LCD monitor? I thought that more dot per inch was better...made things smaller...and yet I keep reading that fewer DPI's are the way to go?? What am I missing here?
Dedided to try 320 (from 380 which i had).. A bit small but i think i can use it..
Sent from my LG-D802 using XDA Premium 4 mobile app
jaseman said:
How come this all seems backwards to me...comparing to a PC LCD monitor? I thought that more dot per inch was better...made things smaller...and yet I keep reading that fewer DPI's are the way to go?? What am I missing here?
Click to expand...
Click to collapse
Maybe you should read this
http://stefan222devel.blogspot.com/2012/10/android-screen-densities-sizes.html?m=1
i have mine set at 380 dpi. looks great! thanks!
Im still on the stock rom but rooted and using xposed framework w g2 xposed and greenify. I changed dpi under android system but once rebooted i kept getting a bootloop and had to boot into recovery and flash the xposed disabler. Was the android system the correct tab to change or which ones are you guys using?
I also have build prop tweaker from the PS. Under ro.sf.lcd_density_secondary it states 480. If u change that will that take effect?
Sent from my LG-D800 using Tapatalk 2
jeff5347 said:
Im still on the stock rom but rooted and using xposed framework w g2 xposed and greenify. I changed dpi under android system but once rebooted i kept getting a bootloop and had to boot into recovery and flash the xposed disabler. Was the android system the correct tab to change or which ones are you guys using?
I also have build prop tweaker from the PS. Under ro.sf.lcd_density_secondary it states 480. If u change that will that take effect?
Sent from my LG-D800 using Tapatalk 2
Click to expand...
Click to collapse
idk, i just changed ro.sf.lcd_density from 480 to 380 and rebooted (using buildprop editor)
ethanhunt123 said:
idk, i just changed ro.sf.lcd_density from 480 to 380 and rebooted (using buildprop editor)
Click to expand...
Click to collapse
That did it
Sent from my LG-D800 using Tapatalk 2
400 seems about right to me. But I don't like to worry about having really precise selections.
updated thread with how to change dpi for noobs :good:
Related
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
I have unfortunately touchwiz can't handle the change, i mean it still works but it doesn't adapt to the new size, neither does the dialer. tried turning off compatibility mode in spare parts, but that did nothing.
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Okay im looking at that line so how do i edit it? Forgive me im new to this stuff /
SGS2 rooted and Overclocked to 1.5ghz stock rom p
No prob. Using Root Explorer, navigate to /system/ and make sure to hit the button in the top right "Mount R/W"
Long press "build.prop" and select Open in Text Editor
Make the change to the line "ro.sf.lcd_density=240" to whatever you want (200 probably works best)
Hit Menu softkey and choose "Save & Exit"
Root Explorer will automatically save a backup copy of build.prop
Reboot your phone to apply DPI change.
There is also a free root file manager called Super Manager, but I haven't used it.
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
nickshertzer said:
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Click to expand...
Click to collapse
Nick I tried your method several different ways and have been going around an around with this for several weeks on our phone and also Sprint version too and the revert back does not stick or still allow to download/update the apps from the market. Tried restarting, clearing cache and resetting the market data and restarting but it still would persist and not allow the updates and incompatibility. The only success I experience is right after I update to a newer version of ROM or clean install all together (which for obvious reasons) resets the phone and then allows the update actions. It is just very frustrating that the DPI change would hinder "Certain Apps" from updating. Anyone have ideas on a future solution besides Nicks input on the manual fix? I think we have brilliant screens with lots of potential for various display options and I miss using the 200dpi settings, but application updates and use of the market is much more important for daily use.
---------- Post added at 11:27 AM ---------- Previous post was at 11:20 AM ----------
fone_fanatic said:
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
Click to expand...
Click to collapse
I have used the dialer files from this thread you mentioned and it all works fine on this ROM the only down side is once you theme that it changes to the themed dialer and goes with the 240 adjusted dialer. I would hope you could share your input and steps (If not too complex) to allow themers to integrate into their themes for multi dpi users.
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
poofyhairguy said:
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
Click to expand...
Click to collapse
this has been posted as an issue, go here and star it to bring it to the attention of the android devs.
qwertyaas said:
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
Click to expand...
Click to collapse
Lowest res on the market? 800x480 is the industry standard at the moment. Not the best, but certainly not the lowest.
Sent from my Galaxy S II (i777) using XDA Premium.
I use 180 on a daily basis. In order to get around the dialer issue. I replace contacts.apk in Unnamed 2.21 with the one from Mikey's Serendipity 8.2 works perfectly except for the already in-call dialer pad which i rarely ever use is still small but the regular dialer is now stretched to full screen. It comes down to editing a .xml file or two if you want to attempt yourself.
Hperdroid has touchwiz that works on 160. it is my understanding most market things work with that density
Sent from my GT-I9100 using xda premium
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
hekoman said:
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
Click to expand...
Click to collapse
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Man_Cave_Tech said:
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Click to expand...
Click to collapse
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
jazzboyrules said:
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
Click to expand...
Click to collapse
Ok, thanks for the input. I'll give that a try when I get home from work tonight.
Sent from my Galaxy S II (i777) using XDA Premium.
I've been using a LCD Density of 185 for as long as I can remember. It's rare now to see an app that doesn't like a custom lcd density setting. Occasionally I run into an app on the market that doesn't like it, and I get the banner at the top of the screen. Since I edit the build.prop for my density setting I have to keep an app handy just incase I get the market issue. But it's an easy fix- use app to get back 240 density> manage applications> market> clear data. Open market> download desired app! Love 185. Probably wouldn't go any lower personally but... for the most part, most apps will happily still work and fill the screen
What do we won lowering the density?
RatusNatus said:
What do we won lowering the density?
Click to expand...
Click to collapse
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Coreym said:
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Click to expand...
Click to collapse
But it's not the same using a launcher that gives you more columns and rows?
Just saying
Saludos desde Ecuador
Change Pixel Density for Galaxy Note 3 and Recommended DPI Settings for System Apps.
Requires Root!
Works on any Rom!
With the Note 3 Packing a 1920x1080 resolution, the first thing I did when I got the phone was work on taking advantage of the real estate the screen has to offer. Many of the Pixel density settings from the Note 2 work on the Note 3, but keep in mind the formula changed with the new screen size and resolution change. I'm just going to call it "Preferred DPI" as most will agree, its a comfortable viewing option.
The easiest way I have found is to change the overall layout from 480 to 320, then going in and tweaking some individual apps.
Overall most of the apps will function as normal, however some system apps will not look right, especially the Dialer and Camera/Gallery views.
Note 2:
Factory DPI: 320
Preferred DPI: 240
Note 3
Factory DPI: 480
Preferred DPI: 320
To change all apps and programs to be viewed in 320 mode is to modify the build.prop settings.
There are multiple ways to do this, but the easiest I have found is to download Rom Toolbox. The Lite version will allow you to easily edit the app. Support your devs, buy pro or donate and give credit to these app & rom creators.
Rom Toolbox Lite Rom Toolbox Pro
Step 1: Changing phone pixel density from 480 to 320
Open Rom Toolbox
Go to the Performance Tab
Select the build.prop Editor
Click the Magnifying Glass to search
Type in "Density"
Click on the ro.sf.lcd_density
Change the Property Value from 480 to 320
Click YES on reboot prompt
Step 2: Download and Install Xposed Framework and App Settings Module
Without rewriting guides that are already available, you can read the general guides here on how to install Xposed Framework.
Guide by Max from High on Android
Download Xposed Framework by Xda Developer rovo89
Download Xposed App Settings Module by rovo89 & Tunstwenty
You will need to install Xposed Framework, and the Xposed App Settings Module by clicking on the above threads. The threads are maintained and updated regularly. Xposed has the ability to update itself, and also provides updates to the modules, which is a great feature.
Once these are installed you can then begin to change apps back to 480 DPI if they don't look right.
Step 3:Recommended Apps to Revert to Stock Density
You can change any app you wish, but the ones that I recommend to keep at stock DPI mainly due to cropping issues are the dialer, contacts, camera, and gallery.
I am currently running Jellybombed Rom, so you may see some extra apps in screenshots, as well as blue text.
I also ran this on the stock rooted Samsung Rom, and the Rooted Deodexed rom before going to Jellybomb.
These are my personal preferences, and im sure I have more than I need selected, but I wanted to make sure all elements worked.
Camera for example has many sub apps such as editing and trimming.
Contacts has 4 tabs for Phone, Groups, Favorites, Contacts
Phone has 4 tabs for Keypad, Logs, Favorites, Contacts.
Bolded are the most essential, the non bolded are personal preference. Feel free to add your own.
com.arcsoft.picmovie
com.arcsoft.picturesbest.app
com.android.app.popupcalculator Calculator
com.sec.android.app.camera Camera
com.sec.factory.camera Camera
com.sec.android.app.collage Samsung Gallery
com.sec.phone - Phone
com.android.contacts - Contacts
com.android.providers.telephony
com.arcsoft.picaction.app
com.arcsoft.demo.piclear
com.sec.android.gallery3d Alternate Gallery
com.google.android.gallery3d Alternate Gallery
com.lidroid.sgs.secretcode
com.android.mms - Texting
com.android.phone - Phone Dialer
com.sec.sprextension.phoneinfo
com.sec.android.mimage.photoretouching
com.sec.android.filter
com.samsung.everglades.video - Samsung Video App
com.sec.yosemite.phone
com.lifevibes.trimapp
com.sec.android.app.storycam
com.sec.android.app.videoplayer - Samsung Default Video Player
com.android.vpndialogs
ma.wanam.xposed
com.google.android.youtube
I have not had any issues with the Android Market, and DPI settings yet, however there is a module called Play Store Fixes you can run within Xposed.
The launcher I use is ADW Launcher
The current Rom used in the screenshots is Jellybomb Domination
Support Josh Beach & kevinrocksman
This is so necessary for the note 3. Thanks for the post!!
Awesome job.
Any clue what app the pen input app is? The one you activate by clicking the pen square over inputs?
It looks like it follows the app's dpi, but wondering if that can be pegged at 480 for every app?
320 feels a tinge too small. Any idea what other settings could be used easily that aren't so small?
I just went in and changed a bunch to make it better. Thanks for the suggestion.
Do you know which is the lockscreen?
Any idea what program the sview case window is under?
Sent from my SM-N900P using xda app-developers app
Jbroad572 said:
Any idea what program the sview case window is under?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
It's not a particular program, from what I've read you would have to leave the system at 480 and individually change apps to 320 to keep the S View Window working properly :\
datajosh said:
It's not a particular program, from what I've read you would have to leave the system at 480 and individually change apps to 320 to keep the S View Window working properly :\
Click to expand...
Click to collapse
Im going back to stock deodexed this weekend to test out some things.
I had some issues with editing pictures ( mainly getting the redeye tool to work with pinch to zoom) so Im going to go back to "as close to stock" as possible to rule out any theme/app settings from Jellybombed.
Ill try to play with the factory apps a bit to get a better list.
Im one of those .. "as soon as i get a phone I root, change dpi, then freeze or remove every system app with "samsung" or "sprint" on it.. and this time around its knox to add to the list.
Then again thats what I done with hundreds of computers for the last 15 or so years, so the habit kind of carries on =)
Not a fan of bloatware =)
rawdikrik said:
320 feels a tinge too small. Any idea what other settings could be used easily that aren't so small?
Click to expand...
Click to collapse
I would love to see more screenshots. I had rooted and went to 240dpi on my original note, and love the way that looks. Still on the fence with rooting my note 3. Haven't read enough about knox, even though I know there are ways to root without tripping knox now. But I m itching to change my dpi
Thanks for the guide. I put mine at 370 dpi, which looks good for me, without being too tiny
Sent from my SM-N900P using Tapatalk
anyone tried changing DPI to "Android System" and "System UI"? I had this changed on my Note 2 (to 240) so that the settings and overall UI was smaller. I tried changing it on the Note 3 to different DPI to test out but it seem sto leave a small border right under the status bar. I tried 320, 350, 370, 400 .. I'm using Nova Launcher btw. (JellyBombed ROM)
onebelo said:
anyone tried changing DPI to "Android System" and "System UI"? I had this changed on my Note 2 (to 240) so that the settings and overall UI was smaller. I tried changing it on the Note 3 to different DPI to test out but it seem sto leave a small border right under the status bar. I tried 320, 350, 370, 400 .. I'm using Nova Launcher btw. (JellyBombed ROM)
Click to expand...
Click to collapse
Hmm surprised since your running Nova. . I thought only stock launcher did that. .
Speaking of which. . Anyone thinking about redoing the stock launcher to handle the better dpi?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
cherylbaker said:
Hmm surprised since your running Nova. . I thought only stock launcher did that. .
Speaking of which. . Anyone thinking about redoing the stock launcher to handle the better dpi?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
yea specially since it looked fine on the note2. Perhaps it's the higher res of the note3?
Does the lockscreen have a separate package? Or is it part of a larger package?
Im trying to change the phone dialer back to stock, but despite the changes it stays the same at 370. What am I doing wrong?
badnews640 said:
Im trying to change the phone dialer back to stock, but despite the changes it stays the same at 370. What am I doing wrong?
Click to expand...
Click to collapse
Try checking all 3 of these settings to 480
com.android.providers.telephony
com.sec.phone
com.android.phone
You can set them manually to 480 (stock)
If you set your overall DPI to something like 370 you need to make those apps bigger individually to 480
cherylbaker said:
Hmm surprised since your running Nova. . I thought only stock launcher did that. .
Speaking of which. . Anyone thinking about redoing the stock launcher to handle the better dpi?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I use a scaleable launcher ( ADW EX) for that reason.
In the past when I tried to modify the stock launcher or system UI, it would cause all kinds of force closes..
The primary reasons i believe is due to how Touchwiz integrates its widgets- like clock for example
Changing just systemUI or Launcher but not changing all the other components manually that are linked to it can trigger "Unfortunately System UI Has stopped Working" errors.
The keyboard is another one thats tied in, as well as the lockscreen.
I haven't gotten around to trying to do all of that, or learning how to yet.. which is why i made the guide with the already available apps.
By changing the overall system UI and using a different launcher, you can have the smaller slim status bar, without having everything else break, since all of the DPIs match. Then finding different processes to tweak with "App Settings" allows you to experiment safely without risking breaking everything.
One super annoying issue i had back when I did DPI tweaking on my Note 2 was if you didnt flash a replacement keyboard in recovery, you would have to setup android by continously tapping the error message all the way through phone setup until you could get to the settings screen to change the samsung keyboard to a different one. Samsung's keyboard dosen't like dpi changes on the note 2. But so far no issues personally with the note 3.
chaosrecords said:
Try checking all 3 of these settings to 480
com.android.providers.telephony
com.sec.phone
com.android.phone
You can set them manually to 480 (stock)
If you set your overall DPI to something like 370 you need to make those apps bigger individually to 480
Click to expand...
Click to collapse
Along with a hunch, I found another thread that stated to change contacts and contact storage as well as dialer storage. That fixed it.
http://forum.xda-developers.com/showthread.php?t=2440365
Quick question can u provide more detailed instructions to reverting those apps u listed back to stock dpi...I try to do it through xposed app settings but the corrections aren't taking
Sent from my SM-N900P using Tapatalk
---------- Post added at 08:14 PM ---------- Previous post was at 07:36 PM ----------
lunchboxVA said:
Quick question can u provide more detailed instructions to reverting those apps u listed back to stock dpi...I try to do it through xposed app settings but the corrections aren't taking
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Nvm phone dpi and contacts dpi both have to be changed at the same time
Sent from my SM-N900P using Tapatalk
Does anybody else have an issue when they change there dpi where whatsapp wallpaper changes to a standard white background?
Any way around it?
its annoying and i have been researching for days and cant seem to find anything to fix it.
I would like to try tablet ui in all the apps and system,so please suggest suitable DPI.
about 280 to 290
If you are rooted I would use xposed an app settings and just do pre app changes as some apps dont play well with the changes
blueether said:
about 280 to 290
If you are rooted I would use xposed an app settings and just do pre app changes as some apps dont play well with the changes
Click to expand...
Click to collapse
Thanks. Ya am using xposed. I have installed Phab7 module which makes status bar at bottom like tablet. Also using app setting modules for chrome, youtube etc.
Wanted to try changing DPI and see how it goes , well will give 280 dpi a try and if I feel comfortable then its good otherwise will stick to current Phab 7 and app settings modules.
One question.
If I change DPi of system UI to 280 in app settings modules will it give tablet like bottom status bar as in Phab7 module?
- DPI 290 and lower = Tablet statusbar (split)
- DPI 320 (and lower) and 800x1200 DP (in App Settings) tablet mode for apps
There is 4 dpi densities. 160, 240, 320 and 400. 160 and 240 are full tabled UI. 320 and 400 are phone UI. On 280 you got some kind of Phablet UI where some apps look like a phone UI (Play store) and some app like tablet UI (Chrome).
I have set dpi density to 240 on my ZU and it is just about to be to small but to me it is still okay. If you like you can enlarge font a bit. (Settings/display/font size) I just like tablet UI so much.
UI, UI, UI how many times I sad that? UI, UI....
simunovic said:
There is 4 dpi densities. 160, 240, 320 and 400. 160 and 240 are full tabled UI. 320 and 400 are phone UI. On 280 you got some kind of Phablet UI where some apps look like a phone UI (Play store) and some app like tablet UI (Chrome).
I have set dpi density to 240 on my ZU and it is just about to be to small but to me it is still okay. If you like you can enlarge font a bit. (Settings/display/font size) I just like tablet UI so much.
UI, UI, UI how many times I sad that? UI, UI....
Click to expand...
Click to collapse
That depends on how you're doing it. There are, like you say, only four official DPIs (160, 240, 320 and 400) but you can kick it into tablet mode way before 240 if you also adjust the DP. You can't do that by editing the build.prop, so we have to use a module like App Settings to set the DP to 800x1200, and then you'll get tablet mode at a higher DPI (without the split statusbar of course, since that required the DPI to be under 290). Yes, i've tried tablet mode at 400 DPI. A million cries could be heard across the universe when i hit "Apply". It's that bad.
320 DPI and 800x1200 DP looks right since the stock DPI for the Ultra (except for the GPe version) is 320, so all UI elements are properly fit. Anything under 320 is too small for me (personally) since i want to actually hit stuff with my finger when i'm standing on my legs, but that's just me though and people can set it to 20 DPI if they want too.
LordManhattan said:
That depends on how you're doing it. There are, like you say, only four official DPIs (160, 240, 320 and 400) but you can kick it into tablet mode way before 240 if you also adjust the DP. You can't do that by editing the build.prop, so we have to use a module like App Settings to set the DP to 800x1200, and then you'll get tablet mode at a higher DPI (without the split statusbar of course, since that required the DPI to be under 290). Yes, i've tried tablet mode at 400 DPI. A million cries could be heard across the universe when i hit "Apply". It's that bad.
320 DPI and 800x1200 DP looks right since the stock DPI for the Ultra (except for the GPe version) is 320, so all UI elements are properly fit. Anything under 320 is too small for me (personally) since i want to actually hit stuff with my finger when i'm standing on my legs, but that's just me though and people can set it to 20 DPI if they want too.
Click to expand...
Click to collapse
Yes i know about DP. I use to have Xposed with module for that. But then you have to set apps manually. That is way to much work for me and then I can not use ART cache and whole phone is a bit slower and battery is affected too. That is the reason I just simply put in DPI density to 240 in build.prop and forget about it. 6.44" screen is big enough for that. Anyway to me it is but like you sad it is just personal opinion.
simunovic said:
Yes i know about DP. I use to have Xposed with module for that. But then you have to set apps manually. That is way to much work for me and then I can not use ART cache and whole phone is a bit slower and battery is affected too. That is the reason I just simply put in DPI density to 240 in build.prop and forget about it. 6.44" screen is big enough for that. Anyway to me it is but like you sad it is just personal opinion.
Click to expand...
Click to collapse
True, it's a lot more work with App Settings, but if you don't want a "One size fits all" it's the only thing to do. There are also a lot of apps that i don't want in tablet mode, so the build.prop way of doing it isn't my style anymore. But like we've both mentioned already, it's all about personal preferences.
Thanks guys for all the responses.
Will give changing DPI to 240 in build.prop a try as I am already using app settings module.
@simunovic
So at 240 dpi status bar will be at bottom too? as I am more comfortable with bottom status bar.
@LordManhattan
Also if I change system UI using app settings module to 290 will it give tablet statusbar (split) as you mentioned.Or do I need to change something else too in app settings?
techpal said:
Thanks guys for all the responses.
Will give changing DPI to 240 in build.prop a try as I am already using app settings module.
@simunovic
So at 240 dpi status bar will be at bottom too? as I am more comfortable with bottom status bar.
@LordManhattan
Also if I change system UI using app settings module to 290 will it give tablet statusbar (split) as you mentioned.Or do I need to change something else too in app settings?
Click to expand...
Click to collapse
I don't think you can move status bar to the bottom anymore. Tablet UI dues not have that in 4.4.2 KitKat anymore. I am not sure about App setting module but regular way (build.prop editing) I don't believe is possible. You can try Paranoid Android ROM if you like. There is all of that and more. Personally I like that "old way" Tablet UI. To bad they changed that.
simunovic said:
I don't think you can move status bar to the bottom anymore. Tablet UI dues not have that in 4.4.2 KitKat anymore. I am not sure about App setting module but regular way (build.prop editing) I don't believe is possible. You can try Paranoid Android ROM if you like. There is all of that and more. Personally I like that "old way" Tablet UI. To bad they changed that.
Click to expand...
Click to collapse
I am using stock 4.3 rooted so its possible on having status bar at bottom. Currently I am using Phab 7 xposed module and I have status bar at bottom.
Ya for kitkat it wont be possible.
Tried 240 DPI via build.prop and really love it. Really makes best use of big ultra screen. Has two status bar notifications one in phablet mode and other phone mode. Overall pretty impressed with it,going to stick with it. Also changed status bar to bottom by Phab7 so in end got what i aimed for
simunovic said:
I don't think you can move status bar to the bottom anymore. Tablet UI dues not have that in 4.4.2 KitKat anymore. I am not sure about App setting module but regular way (build.prop editing) I don't believe is possible. You can try Paranoid Android ROM if you like. There is all of that and more. Personally I like that "old way" Tablet UI. To bad they changed that.
Click to expand...
Click to collapse
Paranoid Android is only in Beta for Android OS 4.4.x at the moment, they don't include hybrid settings until it leaves Beta. Even so, they are saying that the combined bar as we knew it is gone.
ETA: The only thing that I don't like about the combined bar is that it is hidden on the lockscreen, meaning no quick access to notifications.
Coming from N5, I've played around a lot with the DPI settings, to find the perfect spot (361).
Can you also change the DPI settings on the Z2? N5 has it via editing the build.prop but don't know how Sony does this. I'm yet to receive the phone (on Tuesday) but wanna know in advance.
You can simply edit the build.props to change the dpi
Something to know about xperias is they are extremly close to AOSP with the way the firmware works
Its how xperia FWs are, they are very light
Sent from my D6503 using XDA Premium 4 mobile app
I used DPI Changer app from the play store to change mine, also allows you to backup & restore build.prop file as well
It can be a pain to find the correct DPI that doesn't cause issues with some apps, I originally changed it to 400 for a couple of weeks but that was still a bit too big, 320 was too small, 360 was fine but Tv Show Favs app layout got a bit missed up (the main screen was instead a bar on the left of the screen) Ended up settling on 370.
Oh, it's pretty much the same? Good news then!
On my N5, I use 361 due to issues that 360 causes with some apps, and hoping to do the same on soon-to-be-mine Z2, since it was the perfect spot. But if that won't work, and 370 works (as per above post), that's great! Cheers guys.
BanziBaby said:
I used DPI Changer
Click to expand...
Click to collapse
Thanks man, this works wonders!
BanziBaby said:
I used DPI Changer app from the play store to change mine, also allows you to backup & restore build.prop file as well
It can be a pain to find the correct DPI that doesn't cause issues with some apps, I originally changed it to 400 for a couple of weeks but that was still a bit too big, 320 was too small, 360 was fine but Tv Show Favs app layout got a bit missed up (the main screen was instead a bar on the left of the screen) Ended up settling on 370.
Click to expand...
Click to collapse
I'm trying to figure out why DPI Changer doesn't work for me. I also tried Texdroider, which I previously used on an LG G2 with success. Both apps appear to go through the motions, but when I apply the changes and reboot, nothing is changed.
I'm running a D6503 rooted .402, locked boot loader and I installed SuperSU from the Play Store. Running Root Checker confirms I am rooted.
I'm hoping to be able to set the DPI so it can match the look and feel of the Z Ultra
Thanks in advance for any help!
Hadn't thought of changing DPI in quite a while, actually since my Xperia Z. I'm too going to play around with DPI till I find something a bit smaller but then again not too small. I've always thought that the interface had gotten unnecessarily big after the Xperia T.
Edit: Anyone happen to notice what the original DPI value was on the Z2? I changed mine a little too quick..
If anyone likes the ZU the exact DPI is 320
For Z2 Tablet it is 140
And for default it is 480
Sent from my D6503 using XDA Premium 4 mobile app
@orbitalcomp I did have issues with SuperSU granting root to dpi changer, had to apply the new dpi twice & even then sometimes it wouldn't apply on reboot, also had issues with AdAway failing to copy & apply the new hosts file, tried using the full unroot option in SuperSU but it just stuck saying uninstalling please wait. Had to use Solid Explorer to delete the SuperSU apk file & the binary then downloaded the recovery version of clockworkmod superuser & flash that, no issues with dpi changer or AdAway or any other root apps.
Maybe it just me but I have always found SuperSU to be a bit flaky & buggy at times both on the Z2 & my old Galaxy S & Galaxy S3, never had any issues with clockworkmod superuser
I have setted DPI to 320 by editing build.prop.
Then you can apply some different DPI settings App per App using AppSettings Xposed, working great!
BanziBaby said:
@orbitalcomp I did have issues with SuperSU granting root to dpi changer, had to apply the new dpi twice & even then sometimes it wouldn't apply on reboot, also had issues with AdAway failing to copy & apply the new hosts file, tried using the full unroot option in SuperSU but it just stuck saying uninstalling please wait. Had to use Solid Explorer to delete the SuperSU apk file & the binary then downloaded the recovery version of clockworkmod superuser & flash that, no issues with dpi changer or AdAway or any other root apps.
Maybe it just me but I have always found SuperSU to be a bit flaky & buggy at times both on the Z2 & my old Galaxy S & Galaxy S3, never had any issues with clockworkmod superuser
Click to expand...
Click to collapse
Thanks for the reply, BanziBaby. Not sure if you had the same issue originally, but when installing SuperSU from the Play Store it would not update the binaries on first run. After a reboot, SuperSU would open and it was able to grant permissions to the different apps, but I guess it wasn't a full grant.
Is there anyway to install a working version of SuperSU without going through recovery? I'm assuming I have to unlock my boot loader to install a recovery, right?
sensei_sai said:
I have setted DPI to 320 by editing build.prop.
Then you can apply some different DPI settings App per App using AppSettings Xposed, working great!
Click to expand...
Click to collapse
Do the stock apps all handle the 320 dpi just like the Z Ultra, meaning there are more icons allowed on the home screen, dock, and app drawer?
I remember when I had my ZU, I was even able to install tablet apps straight from the Play Store since it apparently registered as a tablet/phone hybrid. That would be nice on the Z2 as well.
orbitalcomp said:
Thanks for the reply, BanziBaby. Not sure if you had the same issue originally, but when installing SuperSU from the Play Store it would not update the binaries on first run. After a reboot, SuperSU would open and it was able to grant permissions to the different apps, but I guess it wasn't a full grant.
Is there anyway to install a working version of SuperSU without going through recovery? I'm assuming I have to unlock my boot loader to install a recovery, right?
Do the stock apps all handle the 320 dpi just like the Z Ultra, meaning there are more icons allowed on the home screen, dock, and app drawer?
I remember when I had my ZU, I was even able to install tablet apps straight from the Play Store since it apparently registered as a tablet/phone hybrid. That would be nice on the Z2 as well.
Click to expand...
Click to collapse
When changing DPI to 320 all apps load into phablet mode (aka ZU size) and some which dont support phablet load into tablet size
In other words... No problem
Sent from my D6503 using XDA Premium 4 mobile app
I have an issue with the Xperia launcher when I change DPI..
The icons on the launcher just get smaller and smaller and unlike google now launcher it doesn't adapt to the changed DPI.
Anyone else have this? I really don't want to switch away from Sony's launcher and smaller dpi is pretty awesome on a larger screen.
lyubor said:
I have an issue with the Xperia launcher when I change DPI..
The icons on the launcher just get smaller and smaller and unlike google now launcher it doesn't adapt to the changed DPI.
Anyone else have this? I really don't want to switch away from Sony's launcher and smaller dpi is pretty awesome on a larger screen.
Click to expand...
Click to collapse
with which DPI? If I remenber well I had the same until I switched to 320 DPI, which is just perfect.
With everything I randomly tried around 400. Rebooted twice after applying 320 and it actually worked!
Ended up using the DPI Changer app, since editing the build.prop directly didn't seem to work after multiple reboots, but 361 is doing the job so far.
Success!
I was finally able to get my root and SuperSU binaries to take after some trial and error from reading the Easy Root Tool thread. Took a combination of installing the SuperSU.apk and rooting multiple times to do it.
Now I'm running 320dpi after changing the setting in DPI Changer...it looks fantastic! I always thought the Z Ultra had the best looking dpi for a smartphone, now it looks perfect on the Z2.
Couple things I noticed...the launcher now rotates to landscape, plus I'm not able to install the tablet version of Slingplayer like I could on the ZU, says it's incompatible in the Play Store. No big deal really, since the phone version works fine, I just like having the full remote of the tablet version.
Thanks to everyone for their input!
orbitalcomp said:
Success!
I was finally able to get my root and SuperSU binaries to take after some trial and error from reading the Easy Root Tool thread. Took a combination of installing the SuperSU.apk and rooting multiple times to do it.
Now I'm running 320dpi after changing the setting in DPI Changer...it looks fantastic! I always thought the Z Ultra had the best looking dpi for a smartphone, now it looks perfect on the Z2.
Couple things I noticed...the launcher now rotates to landscape, plus I'm not able to install the tablet version of Slingplayer like I could on the ZU, says it's incompatible in the Play Store. No big deal really, since the phone version works fine, I just like having the full remote of the tablet version.
Thanks to everyone for their input!
Click to expand...
Click to collapse
Can confirm that also on Z3 is 320DPI for Home launcher just amazing
Xperia Z2 dpi change
I have tried to use all application in playstore as well as build.prop editing in system but still nothing happens I'm running in marshmallow 6.0.1 with 23.5.A.1.291 build hope you could help me guys thanks
pulizpunk said:
I have tried to use all application in playstore as well as build.prop editing in system but still nothing happens I'm running in marshmallow 6.0.1 with 23.5.A.1.291 build hope you could help me guys thanks
Click to expand...
Click to collapse
You need to reboot after editing.
Sent from my Sony D6503 using XDA Labs
Hi Xda
ive seen the Siny C5 E5533 that have the one handed mode....,
it activated when u pull your finger from left down corner to the center the screen, the screen will chenge and get smaller ....,
the samsungs note 3 and above has that,
so is there any way to have that future on our ultra??????
Try Niwatory for exposed framework.
I managed to set it up with GravityBox on Menu soft key doubletap.
Sent from my C6833 using Tapatalk
I've just cranked the DPI up to 400, and I'm able to use it one-handed. I also have about 2 years of one-handed "training" with the ZU - and fairly big hands, so I guess it's not a solution for most people
Klaos3000 said:
I've just cranked the DPI up to 400, and I'm able to use it one-handed. I also have about 2 years of one-handed "training" with the ZU - and fairly big hands, so I guess it's not a solution for most people
Click to expand...
Click to collapse
how did u do that????
how did u changed your DPI & also dont u have any problem with that????
d1g1m4n said:
Try Niwatory for exposed framework.
I managed to set it up with GravityBox on Menu soft key doubletap.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Ive tried Xposed and it said xposed cant install the basement ...... or with the proccesor...........,
so have u tried the gravity box?????
Install Xposed framework zip with your recovery. Search for that zip on forum. Then install Xposed Installer apk. Then search for Niwatory with Xposed Installer modules list
Sent from my C6833 using Tapatalk
d1g1m4n said:
Install Xposed framework zip with your recovery. Search for that zip on forum. Then install Xposed Installer apk. Then search for Niwatory with Xposed Installer modules list
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
thnxalot bro
but ive got bootloop......,
rezadentevil said:
how did u do that????
how did u changed your DPI & also dont u have any problem with that????
Click to expand...
Click to collapse
I did it manually through the build.prop in /system, but you can use an app to change it too. The default DPI is 320, so things are fairly small on screen, but I use my ZU mainly as a phone and not a small tablet, so a higher DPI will make everything bigger, including the fonts. 320 DPI and 480 DPI (and some lower ones) are officially supported by Android, and running any other DPI can break some things (mostly UI glitches), like the Sony Launcher. It won't break it to the point where it doesn't work, but it's not made for other DPIs than the official ones, so it won't look right. So if you're using the Sony Launcher, then 480 DPI would be the recommended DPI above 320. 480 DPI will however make everything very big, and it'll behave like a smaller Z series device like the Z5 (DPI wise), which will make it funny on the Z Ultra since it has a much bigger screen than anything else, so it'll look somewhat comical the first day. I use 400 DPI, and haven't experienced any issues (using Nova Launcher), and everything is scaled properly.
You need root though, and if you do have root, I recommend you to just try out some different DPIs before settling. I personally like 400 and 420 DPI.
It'll be much easier to use the ZU one-handed with a higher DPI (since everything on screen will be bigger and easier to hit), it'll also boil down to your hand size. Cranking the DPI up won't do you any good if you have hands the size of a small goat, so just keep that in mind too
Klaos3000 said:
I did it manually through the build.prop in /system, but you can use an app to change it too. The default DPI is 320, so things are fairly small on screen, but I use my ZU mainly as a phone and not a small tablet, so a higher DPI will make everything bigger, including the fonts. 320 DPI and 480 DPI (and some lower ones) are officially supported by Android, and running any other DPI can break some things (mostly UI glitches), like the Sony Launcher. It won't break it to the point where it doesn't work, but it's not made for other DPIs than the official ones, so it won't look right. So if you're using the Sony Launcher, then 480 DPI would be the recommended DPI above 320. 480 DPI will however make everything very big, and it'll behave like a smaller Z series device like the Z5 (DPI wise), which will make it funny on the Z Ultra since it has a much bigger screen than anything else, so it'll look somewhat comical the first day. I use 400 DPI, and haven't experienced any issues (using Nova Launcher), and everything is scaled properly.
You need root though, and if you do have root, I recommend you to just try out some different DPIs before settling. I personally like 400 and 420 DPI.
It'll be much easier to use the ZU one-handed with a higher DPI (since everything on screen will be bigger and easier to hit), it'll also boil down to your hand size. Cranking the DPI up won't do you any good if you have hands the size of a small goat, so just keep that in mind too
Click to expand...
Click to collapse
Thanx alot my friend
my only problem was the keyboard , and it seems it get so much better than before, im on unlocked,rooted official 5.0, amd now DPI is 400.........,
Thnx so Much
Klaos3000 said:
I did it manually through the build.prop in /system, but you can use an app to change it too. The default DPI is 320, so things are fairly small on screen, but I use my ZU mainly as a phone and not a small tablet, so a higher DPI will make everything bigger, including the fonts. 320 DPI and 480 DPI (and some lower ones) are officially supported by Android, and running any other DPI can break some things (mostly UI glitches), like the Sony Launcher. It won't break it to the point where it doesn't work, but it's not made for other DPIs than the official ones, so it won't look right. So if you're using the Sony Launcher, then 480 DPI would be the recommended DPI above 320. 480 DPI will however make everything very big, and it'll behave like a smaller Z series device like the Z5 (DPI wise), which will make it funny on the Z Ultra since it has a much bigger screen than anything else, so it'll look somewhat comical the first day. I use 400 DPI, and haven't experienced any issues (using Nova Launcher), and everything is scaled properly.
You need root though, and if you do have root, I recommend you to just try out some different DPIs before settling. I personally like 400 and 420 DPI.
It'll be much easier to use the ZU one-handed with a higher DPI (since everything on screen will be bigger and easier to hit), it'll also boil down to your hand size. Cranking the DPI up won't do you any good if you have hands the size of a small goat, so just keep that in mind too
Click to expand...
Click to collapse
do u know anyway to have samsung keyboad on zu ?????
rezadentevil said:
do u know anyway to have samsung keyboad on zu ?????
Click to expand...
Click to collapse
Try this one?
http://forum.xda-developers.com/showpost.php?p=59650881&postcount=1064
Klaos3000 said:
Try this one?
http://forum.xda-developers.com/showpost.php?p=59650881&postcount=1064
Click to expand...
Click to collapse
thanx alot bro, but i have got bootloop...., i did a factory and cash.....but i didnt work
also i tried so many samsung keyboards, but none of them has worked.....,
rezadentevil said:
thanx alot bro, but i have got bootloop...., i did a factory and cash.....but i didnt work
also i tried so many samsung keyboards, but none of them has worked.....,
Click to expand...
Click to collapse
Hmm, probably some libs and stuff that got messed up, and it's probably only compatible with TouchWiz devices (framework dependencies or something). Now we know, though.