I just noticed a strange behaviour....
Starting with this rom, but I checked and is so also with other builds.
I'm used to change my DPI density settings to 180, for have a "larger" screen and use 6x6 rows*colums with LauncherPro, to have more widgets on the home screen.
I noticed that setting the DPI to 180 (in the build.prop file) causes an error when going in the contact slide, in the part where you can "link" your contact with their facebook account.
As I click on the "chain" to make the link, the contact app closes itself with this error
processcom.android.htccontacts has been terminated
So I did some tests and it seems that the problem is only with dpi settings of 160 and 180, from 190 to 240 no problem at all.. it works without errors...
Sense ROMS aren't really compatible with LCD Density changes. Use a Non-Sense one if you like having more on your screen (like I do).
StephanV said:
Sense ROMS aren't really compatible with LCD Density changes. Use a Non-Sense one if you like having more on your screen (like I do).
Click to expand...
Click to collapse
Thanks
Yes, you are right.. the strange is that the erro happens only below 180...
Have been using LCD Density changer from 240 to 220 dpi on the gorgeous super AMOLED plus screen.
Only recently I realised that in the Android Market the install/download button does not appear when this resolution is changed from default. If I were to set to 240, it is OK. However this does not affect all apps. Searching apps is fine, just not able to install/download.
Now I have to change to default 240 to install certain apps then change to desired resolution.
Anyone knows how to solve this?
In short, there's no permanent fix that I now of, but just a warning:
Use an app like LCD Density Changer in the Market so you can safely toggle the resolution without getting stuck and needing to wipe your data
If you set the resolution in the build.prop below 240 it not only removes the download/install from the page in the Market but with the latest Market version it also gives a message highlighted in bright yellow that the application in not compatible with the device. I also found that even if I changed the build.prop line back to 240 and rebooted I was stuck without access to the majority of the apps I use. I had to wipe data to fix the problem.
What I'm doing is leaving my resolution at 210 and once a week switching back to 240 to update any apps that need updating. Occasionally I have to switch the resolution to download a new app as well. It's not exactly convenient, but it works.
So I just bought my brand new Note 4 (SM-N910W8) and of course the first thing I did was root it and install xposed framework. Everything works fine, I always change the DPI on my Note phones because I like to make use of the extra screen real estate. This worked fine as well, that is until I installed my Sview (S View cover) on it.
The sview window appears fine in the new DPI but across the bottom portion there is a black bar (the screen is off on the bottom third of the window).
I tried using the Xposed app settings mod to change the sview portion of the UI back to 640 DPI (the native resolution), but this didn't work!
has anyone else experienced this on the Note 4? any suggestions to make it work while having the rest of the phone in 480 DPI mode?
Helllpppp
Can you post a picture of what's exactly happening?
c_est_la_vie said:
So I just bought my brand new Note 4 (SM-N910W8) and of course the first thing I did was root it and install xposed framework. Everything works fine, I always change the DPI on my Note phones because I like to make use of the extra screen real estate. This worked fine as well, that is until I installed my Sview (S View cover) on it.
The sview window appears fine in the new DPI but across the bottom portion there is a black bar (the screen is off on the bottom third of the window).
I tried using the Xposed app settings mod to change the sview portion of the UI back to 640 DPI (the native resolution), but this didn't work!
has anyone else experienced this on the Note 4? any suggestions to make it work while having the rest of the phone in 480 DPI mode?
Helllpppp
Click to expand...
Click to collapse
I'm about to do the same
What new setting did you put for the dpi?
This seems to be the same problem with the lock screen and dpi settings. Unfortunately it seems like the dpi settings are baked into the system ui and cannot be modified unless dpi is changed for everything. If been there. Good luck
ravni said:
I'm about to do the same
What new setting did you put for the dpi?
Click to expand...
Click to collapse
I edited the build.prop to have a DPI of 480 instead of 640 (the native DPI).
It's the same thing that happens when you make the same change to the DPI on Note 3 with S-View covers as well.
I am still trying to figure a way to fix this, has anyone found anything new?
The Picture 1 shows what's happening to the Sviewcover. Picture 2 shows me tricking the phone into believing that the Cover is closed (by using a magnet).
I used Xposed App Settings to set the system DPI to 480 (from 640 stock). I set the Sviewcover.apk to 640 as well so the Sviewcover is not misaligned to the left side.
BUT here is the problem, there is a Black bar at the bottom half of the Sviewcover which renders it useless and ugly. The ONLY way I have found to fix this is NOT to alter the DPI for "Android System" and leaving it stock. That way the Sviewcover would show up perfectly without the black bars.
But that defeats the purpose of altering the DPI first place. Why can't samsung allow two zoom levels for user to choose so we can either choose big icons or more screen spaces?
there is a semi solution for this
usually people use rom toolbox to change the entire dpi.
first you must return the dpi to the normal 640 in rom toolbox
then in app settings Xposed change com.android.systemui dpi to 480
and then go to Android System (Android) and change the dpi back to 640
don't forget each time you must turn on the app setting and save after the change
this might effect some of the apps and show it in normal size but it will fix your problem
plus you can change any app's dpi to 480 from app settings later and make it small again.
c_est_la_vie said:
So I just bought my brand new Note 4 (SM-N910W8) and of course the first thing I did was root it and install xposed framework. Everything works fine, I always change the DPI on my Note phones because I like to make use of the extra screen real estate. This worked fine as well, that is until I installed my Sview (S View cover) on it.
The sview window appears fine in the new DPI but across the bottom portion there is a black bar (the screen is off on the bottom third of the window).
I tried using the Xposed app settings mod to change the sview portion of the UI back to 640 DPI (the native resolution), but this didn't work!
has anyone else experienced this on the Note 4? any suggestions to make it work while having the rest of the phone in 480 DPI mode?
Helllpppp
Click to expand...
Click to collapse
In app settings, as well as setting the DPI to 640 you also have to tick the box "apply res to widgets" If you don't, the widgets still render at the system DPI. You have to apply the 640 DPI to the com.android.keyguard (I think that's what it's called it's got keyguard in the name).
Yup, Batfink is right. I forgot about the apply to widget setting, bur when I finally applied it everything was good.
omid_freesky said:
there is a semi solution for this
usually people use rom toolbox to change the entire dpi.
first you must return the dpi to the normal 640 in rom toolbox
then in app settings Xposed change com.android.systemui dpi to 480
and then go to Android System (Android) and change the dpi back to 640
don't forget each time you must turn on the app setting and save after the change
this might effect some of the apps and show it in normal size but it will fix your problem
plus you can change any app's dpi to 480 from app settings later and make it small again.
Click to expand...
Click to collapse
This will make the main UI at 640DPI which defeats the purpose of changing the DPI first place.
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
Applethrow said:
Yup, Batfink is right. I forgot about the apply to widget setting, bur when I finally applied it everything was good.
Click to expand...
Click to collapse
I checked "apply to widgets" for both Keyguard and Sviewcover but the Black bar is still present.
When I come to think of it, I only changed dpi for the system.ui process. Then set keyguard, camera, contacts etc to 640. Didn't touch Android System.
Applethrow said:
When I come to think of it, I only changed dpi for the system.ui process. Then set keyguard, camera, contacts etc to 640. Didn't touch Android System.
Click to expand...
Click to collapse
This is a semi-fix as you would have to alter the DPI for EVERY app to render at 480DPI but I guess this is the ONLY method at the moment :crying:
Yes, you are absolutely right. Just tried it and s-view window got a black bottom bar. Maybe I'll have switch to my wallet flip cover lol
The only thing I don't like on the PRIV is that the icons and everything else is very large on the screen. Defeats the purpose of having a high res display. I have always rooted my phones and decreased the screen density to give me more real estate.
Since the PRIV cannot be rooted (yet), there seems to be a way to adjust the screen density in the build.prop file. Details here: http://www.androidbeat.com/2015/07/how-to-change-dpi-of-android-device-without-root/
Since it is less than a week since I got the device, am quite afraid to try it out. Has anyone tried this on the PRIV?
I tried to change the density with this method, but I couldn't even get adb to detect the priv even tho I activated usb debugging in the dev. options.
But for now I use Nova Launcher to set the app icons to 80% size and I changed the font size to small in the settings. This makes everything look way better.
.K' said:
I tried to change the density with this method, but I couldn't even get adb to detect the priv even tho I activated usb debugging in the dev. options.
But for now I use Nova Launcher to set the app icons to 80% size and I changed the font size to small in the settings. This makes everything look way better.
Click to expand...
Click to collapse
Did you load the BlackBerry usb drivers for your computer?
TechKnowGrappler said:
Did you load the BlackBerry usb drivers for your computer?
Click to expand...
Click to collapse
Yeah, I downloaded and installed these: https://swdownloads.blackberry.com/Downloads/entry.do?code=4EE0932F46276313B51570F46266A608
The device doesn't get the authentication popup and it's not listed in "adb devices".
.K' said:
I tried to change the density with this method, but I couldn't even get adb to detect the priv even tho I activated usb debugging in the dev. options.
But for now I use Nova Launcher to set the app icons to 80% size and I changed the font size to small in the settings. This makes everything look way better.
Click to expand...
Click to collapse
Launchers don't serve the purpose for me, because they only make the the home screen look better. But yes you are right, something is better than nothing....
Hi everyone!
I was planning on getting the Note 8, and wanted to see how the UI / stock apps handle a custom LCD density using ADB. So because the S+ is so close to the Note 8 in size, I thought this would be my best indication on how TW / SE handles a custom LCD density.
I find that the "Display Size" settings in Display dont shrink things down quite enough for me. To give you an idea, I set my OnePlus 3T's density to 289, from stock 480.
I wanted to know what the lowest number you could set the LCD density using the "adb shell wm density xxx" before the keyboard / chrome kick into "tablet mode" where it shows tabs and the keyboard changes to the strange tablet mode.
Could someone please change their LCD density real quick and show me a few screens of the dialer, settings, and random screens? I would greatly appreciate it!!!
You can just change the density at a granular level in the OS on the fly by enabling Developer Options and changing the Minimum Width value under the Drawing section. The higher the value, the smaller the the content on your display will be. I have mine set at 490 dp.