If you change DPI on Marshmallow, the camera app starts registering touches incorrectly (wrong coordinates).
I was wondering if somebody can check if DPI change still affects the camera app in Nougat. It should not because you can change DPI easily now so I would assume Motorola would fix this.
Finally, if it indeed has been fixed. Does anybody have the APK of the app for use with Marshmallow?
Related
Hi all,
My new phone did not survive a single day without (towel-)root. So after getting root, I was thinking about changing DPI.
default in /system/build.prop is 480. I changed it to 360 and 420, both seems fine for the GS5. As a scale referenced I used values from http://forum.xda-developers.com/galaxy-nexus/general/info-official-galaxy-nexus-lcd-density-t1392089 - my Galaxy Nexus is running at 246 just fine.
But sadly, the stock lock screen is now shifted left. Any idea how I can replace the stock lock screen with another fingerprint-ready lock screen? A lock screen with 4x4 pattern would also do.
Thanks in advance.
PS: If I have time, I will make a thread similar to the linked above.
Is the camera workin properly on 360 and 420? thanks and the phone keypad?
I may be wrong but as far as i know you have to edit SystemUI for the lockscreen to look correct, or you can use app settings from xposed to change SystemUI back to 480 but that changes more than the lockscreen. As for camera and keypad, those need to be changed back to 480 in app settings, i wouldnt say its required but its not going to work very well on anything but stock dpi, i personally run 320.
Sent from my SM-G900A using Tapatalk
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
So I rooted and wanted to set the screen PPI/DPI to the actual calculated value of 400-403 (Motorola says it's 403 but the actual calculated value is 400.53). Problem is, it screws up the icons in the camera app and Google Search bar on the homecreen. I've attached screenshots to show you what I mean, but I'm sure most of you are aware of this happening as it tends to when you lower the DPI/PPI. The screens of the screwed icons are at 403 DPI/PPI and the screens where the icons are fine are at the default 480 DPI/PPI.
Does anyone know of a way to fix this? Or is it just something that can't be helped at lower DPI/PPI values?
How did you change your DPI? I read that the adb method alone is not enough. You must change the value on build.prop too. Making the two things may work.
update app camera via Google Play Store que resolve!!!!
Or use appsetting to change dpi in apps.
Skickat från min XT1562 via Tapatalk
I have this exact same issue. I changed DPI to 400 using adb. I also have profile picture thumbnails messed up in both Viber and Whatsapp. So far I haven't found any solutions. Changing DPI to 360 works for the camera, but not for thumbnails in Viber or whatsapp.
I'm using 440. Stock is 480. If you in increments of 40 it works. Try 400
ToYeD said:
So I rooted and wanted to set the screen PPI/DPI to the actual calculated value of 400-403 (Motorola says it's 403 but the actual calculated value is 400.53). Problem is, it screws up the icons in the camera app and Google Search bar on the homecreen.
Does anyone know of a way to fix this? Or is it just something that can't be helped at lower DPI/PPI values?
Click to expand...
Click to collapse
Mother of all ad blocking ???
dpacmittal said:
I have this exact same issue. I changed DPI to 400 using adb. I also have profile picture thumbnails messed up in both Viber and Whatsapp. So far I haven't found any solutions. Changing DPI to 360 works for the camera, but not for thumbnails in Viber or whatsapp.
Click to expand...
Click to collapse
PPI is a hardware component i.e how many pixels are there in a inch of screen.
DPI is a software component in broad terms i.e how much area a software is allocated. so changing it to too low will have bad effects.
change the DPI to 430-440 it looks nice and it will solve your problem.
---------- Post added at 06:29 AM ---------- Previous post was at 06:23 AM ----------
LuizHenrique91 said:
How did you change your DPI? I read that the adb method alone is not enough. You must change the value on build.prop too. Making the two things may work.
Click to expand...
Click to collapse
it would be easy if you are rooted. simply go to /system/build.prop and look for ''ro.sf.lcd_density=480'' and change it accordingly.
ToYeD said:
(Motorola says it's 403 but the actual calculated value is 400.53).
Click to expand...
Click to collapse
It's 403,5.... The screen is not exactly 5.5 inches
Sent from my XT1562 using Tapatalk
Do what I did, install the AppSettings via Xposed, choose the DPI you want normally in build.prop, In the AppSettings settings, select Motorola Camera and place it in the DPI 480 (stock), so I use here without problems.
Anyone else having problems with latest oxygen OS dpi? Changing its value breaks the ui in several places, like the quick settings and reboot menu.
Why do they insist on having a non-stock ui is beyond me. Anyone has a fix for this?
dgershko said:
Anyone else having problems with latest oxygen OS dpi? Changing its value breaks the ui in several places, like the quick settings and reboot menu.
Why do they insist on having a non-stock ui is beyond me. Anyone has a fix for this?
Click to expand...
Click to collapse
I think that you have to stick with the standard dpi
dgershko said:
Anyone else having problems with latest oxygen OS dpi? Changing its value breaks the ui in several places, like the quick settings and reboot menu.
Why do they insist on having a non-stock ui is beyond me. Anyone has a fix for this?
Click to expand...
Click to collapse
How are you changing the DPI? build.prop or an app?
Yes, I can confirm the DPI issues. I wasn't able to find a fix other than keeping the stock 480 DPI and adjusting around it (text size, launcher adjustments, Xposed modules for status bar etc.) All of which is a pain and appears to be because they wanted to skin the OS to look like N, and some menus don't scale. I have moved back to N and if you find a solution please post it...
Hey guys, i know that global DPI can be changer from build.prop or in the developer option settings. I did that and so far everything is working fine( on Sac23 V3 oreo based S9+ port) but the Gboard is scaling to a kind of tablet mode and even the biggest setting is ⅔ of the biggest keyboard on smaller DPI scale (on 410 to 441 its great but if i change it to 450 and up the keyboard gets smaller).
In the past on previous phones i have used Xposed with the App Manager(sorry if name isn't correct) to change the DPI of different apps. I have also teied editing the xml file from the gboard apk so the biggest setting would be even bigger. With these options come flaws:
1. With Xposed Framework i can't have safetynet which is needed for Snapchat and Netflix and bunch of other apps to work.
2. If i change the XML after every update from playstore i have to make changes again.
Is there any other possible way ( maybe Magisk Module) that does DPI changing per app?