I wanted to use the App Settings module for Xposed to switch some apps to use their tablet interface (namely, Chrome though at least other GApps I've tested behave similarly) while keeping the system DPI higher. 384 DPI on Note 4 successfully switches to apps' tablet interfaces as in the left screenshot (e.g. adb shell wm density 384):
{
"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"
}
But when I set specific apps to 384 DPI with Xposed App Settings while keeping the system DPI higher (480 in the image below), it stays on the phone interface, but scaled for the lower density, and sometimes with inconsistency issues (visible with the right screenshot with a part of the bottom cut off, as well as the address bar not fully hiding when scrolling down). Changing the App Settings display dimensions can activate the tablet interface but will result in a severely inconsistent GUI.
Is there a way (within App Settings, Xposed, or otherwise) to spoof DPI completely for an app without actually changing it for the system? It seems that the system DPI is still having an effect on some apps; is this a limit with what resources App Settings can affect?
I wasn't able to find any answers by just searching, so I thought I'd post device-specific first. Thanks!
Related
For some day now I have been fooling around and learning how to modify APK files and such so I could finally fix the Torch app included with Wayland_Ace's CM10.1 for the Galaxy Ace.
I noticed that the Strobe Frequency Slider was being messed up by some of the margins and I also decided I would decompile the source and remove the options for High Brightness in the main app and the widget options because it does not work on the Galaxy Ace. After a few hours of setting everything up and fooling around with the source, I've managed to accomplish what I was going for.
This is what it looks like now:
{
"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"
}
Basically, I hid the high brightness option in the main app and removed the warning about it in the initial popup and the about view, because with the option removed you don't need to be warned. I also went into the source and XML and removed the high brightness option from the widget options. Finally, I fixed the margins on the strobe slider so it was no longer messed up, and I centered the light bulb better.
_____________________________________________________________
Simply boot into CWM and flash the file attached below. This was created from the Torch app from Wayland_Ace's CM10.1 ROM and has only been tested on his CM10.1 ROM on a Galaxy Ace. I doubt it will work for other devices. It's up to you if you want to try it and if you do, make a backup of your current Torch app just in case.
I modified dpi to 240 using Xposed App settings by setting dpi of Android and System UI to 240.
Nearly everything is okay, except for several things.
First one is Recent apps screen.
When you call up recent apps screen, there you can see thumbnails of recently used apps.
As you can see the first screenshot I attached, the thumbnails are scaled incorrectly. Actually frame around the thumbnails is not correctly scaled.
{
"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"
}
The Second one is similar with the first one, but occurs on another app.
When I send a photo using the app, also.frame is the matter.
I also modified dpi of the app to 240 with App Setting module..
I assume some application related to the frame needs modification of dpi, but I can figure it out.
Maybe modifying build.prop makes things simple, but when I did, samsung stock apps made problems, and some of them were not properly corrected even if I set their dpi to 320 via App Settings. This is why I modified System UI and Android rather than build prop.
Sent from my SHV-E250S using Tapatalk 4
I've changed the System.UI dpi to 530 with App Settings (Xposed module) and it works great. The issue I'm having is that that Knock On wallpaper is not full screen anymore. Anyone have an idea how to fix this? Also, any way to get rid of the white square?
{
"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 might be a little late but as far as the white brackets, I use G3 Tweaksbox (you can get it here or on the play store) and it has an option to remove them. There's a lot of other tweaks too, especially if you pay for the full version. Hope this helps!
Thanks, used G3 Tweakbox and its an awesome app. Couldn't fix the dpi though, so just set it to default.
Same problem I'm having. I'm not using knock code but the lockscreen shows a small version like that for a second after turning the screen on and then goes to normal. Using 530 dpi also.
Sent from my LG-D851
I set my DPI to 530 using Texdroider_DPI app not Xposed and don't have this problem... Most likely just an effect from it being through Xposed.
- Tapatalked from the G3
I updated my OnePlus from Android stock 11 to 12 and my fonts and all were small, even on the settings so this is not simple font size settings, but after I turned developers Options off all fonts and sizing screen resolution went back to normal. Where in developers Options is this setting or in settings? Ty
Ostrich Man said:
I updated my OnePlus from Android stock 11 to 12 and my fonts and all were small, even on the settings so this is not simple font size settings, but after I turned developers Options off all fonts and sizing screen resolution went back to normal. Where in developers Options is this setting or in settings? Ty
Click to expand...
Click to collapse
"adb shell wm density"
Assuming you know about adb. Enter that and it will give you density, kinda like font size. Play with the number it gives you until you find one you like.
"adb shell wm density 400"
"adb shell wm size" will give you the resolution
Be careful with this setting
{
"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 shall check that out. Yes I am familiar with ADB and Ty very much, I'll let you know.
The external screen behaves as a regular phone screen, but the inner/main/foldable screen behaves as a tablet screen, which changes some apps behavior a bit. For example Opera shows tabs in that mode, unlike the fullscreen layout of the "phone mode", and Youtube does not go fullscreen when you turn the phone, instead it just rotate the video screen (like a webpage).
Is there a way to force the "phone mode" in this screen? IMO it is not big enough to act as a tablet.
{
"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 don't think that setting tells Android that you want phone resolution so that apps present differently. This setting is more for Samsung-modified apps and global settings screens can split navigation, erc.
It was exactly that, unfortunately I also liked the split view in some apps
Thank you Atthorpe.
strann0 said:
It was exactly that, unfortunately I also liked the split view in some apps
Thank you Atthorpe.
Click to expand...
Click to collapse
Right?, I wish they would make it so we could choose which we wanted per app