Database Develop

Tips: Set individual apps to run as tablet mode on any rom (root)

I found this out by watching ZedoMax's video. Just want to repost in case people didn't see it. Sorry, root is required. Also yes I am aware of Paranoid Android, but this method work with all roms. You can set tablet mode per app that you want and not affecting the entire system. You can change font size per app as well.
Instruction:
1. Download Xposed Installer (apk) and App Settings and install both of them.
2. Run Xposed Installer and press "Install/Update". Then also select the "Modules" tab, check the box to enable "App Settings". Then reboot.
3. Run "App Settings", select any app in the list you want to change to tablet mode. Change the value for the "DPI" and resolution (Screen (dp)) to the desired value, then press "Save", then Launch the program. Keep trying different values until it successful set the app into tablet mode.
Tips:
-If you are making change to an app that contain important data, use Carbon or Titanium Backup to backup your data first, just in case.
-I find "DPI" set to 200 or 240 and "resolution" to 1280x800 tend to work. Though not all apps come with a tablet mode.
-You can change the "font scale" value to make fonts bigger or smaller as well.
-If you experienced any app crashing, toggle it off in the App Settings menu and "Save". Also, setting the "DPI" to 0 is equivalent to the default DPI value.
-Some recommended settings to try for the Nexus 7:
Browser: DPI: 200, Resolution: 1280x800
Contacts: DPI: 240, Resolution: 1280x800
Launcher: DPI: 200, Resolution: 1280x800, Font Scale: 120 (bigger icons, tablet mode)
Play Music: DPI: 160, Resolution: 1280x800, Font Scale: 140 (This will fit lots more songs on the screen.)
Play Store: DPI: 200, Resolution: 1280x800, Font Scale: 80

Handy!
Great little tip for people who don't really want to install a custom ROM.
Thanks!

cool! how does this affect performance? does it create any lag or stutter?
Edit: how do you install the zip file? it fails whenever I try to install it through recovery.
edit 2: you actually have to rename the zip file as an apk file, then install it normally in android. Not really sure why he didn't just upload it as an apk to begin with. anywho this is working great!

OrangeFlash81 said:
Great little tip for people who don't really want to install a custom ROM.
Thanks!
Click to expand...
Click to collapse
Except that after you do this, you're not on a stock ROM anymore

It doesn't affect the performance, but I can imagine running apps on higher resolution might require more performance, but I've tried it with plenty of apps.
One thing I notice is it only affect 2D graphic. The resolution setting won't affect 3D games so no chance for getting better fps.
Sent from XDA app

This is very helpful wish I knew about it before i switched to PACman ROM.

Scalinh issues on apps like facebook.

Just got my p9 a few hours ago but the scaling and text is like on a 240p screen even though i changed the font size

what system version you have?
It is brand new?
Did you check programming settings-> "minimum width"? Set it between 380-410 DPI
Also check if you didnt enabled simple mode(but it should just change main screen not DPI)

Mediapad m3 behaves like a big smartphone not like a tablet

android apps are almost all for smartphones only a few apps have extensions that allow you to make better use of your tablet's screen size,
after installing some apps that have a different shape on the tablet i noticed that on mediapad m3 nothing changes, they are the same shape as a larger smartphone,
i wonder and wonder you:
maybe the m3 is not recognized as a tablet or needs to be changed some settings?

There have been quite a few threads or sub-threads on this. the DPI needs to be changed to have the M3 render some apps in their tablet modes, most of the discussions revolve around Chrome (no tabs in original DPI and YouTube). Try running this command from ADB:
adb shell wm density 320 && adb reboot
320 works well for me on Nougat, but you might need to experiment with what works well for you and the version you are on. If you haven't changed your view mode, the change should stick after rebooting, if you have then chances are you will need to use a DPI changing app to update your settings after each reboot.

johje said:
There have been quite a few threads or sub-threads on this. the DPI needs to be changed to have the M3 render some apps in their tablet modes, most of the discussions revolve around Chrome (no tabs in original DPI and YouTube). Try running this command from ADB:
adb shell wm density 320 && adb reboot
320 works well for me on Nougat, but you might need to experiment with what works well for you and the version you are on. If you haven't changed your view mode, the change should stick after rebooting, if you have then chances are you will need to use a DPI changing app to update your settings after each reboot.
Click to expand...
Click to collapse
thanks for the reply, i already knew the change of DPI,
maybe i have not explained the problem well, so let's take an example:
if you install Metatrader 5 on smartphone and on a true tablet you will see two different shape on display while on mediapad m3 i see the same shape no difference,
the same problem occurs each time i install an application that must appear on a tablet differently from a smartphone

There is no general "tablet" identifier, but apps decide based on screen size / resolution / dpi if they change their layout or not: https://developer.android.com/guide/practices/screens_support.html#qualifiers
So changing the DPI is the currently best option.
(Perhaps some apps tweaked this by overwriting these qualifiers for certain models based on the device identifier.)

fluxxis said:
There is no general "tablet" identifier, but apps decide based on screen size / resolution / dpi if they change their layout or not: https://developer.android.com/guide/practices/screens_support.html#qualifiers
So changing the DPI is the currently best option.
(Perhaps some apps tweaked this by overwriting these qualifiers for certain models based on the device identifier.)
Click to expand...
Click to collapse
thanks for your contribution, something strange happens that i explain:
also my bank offers an app that has a different shape depending on where it is installed and installing it from google play to the mediapad m3 comes on the tablet version, unfortunately the layout is not compatible with the screen but changing the dpi the issue is solved and the app becomes fully usable, while the metatrader 5 app does not seems to recognize mediapad m3 as a tablet and it installs with the shape of the smartphone.

maybe i understand where the issue is:
i belive that mediapad m3 has a wrong package installer or a bug in it.
I came to this conclusion after this test:
i download the apk file on pc then transfers it to old consumer tablet and also to mediapad m3,
so i manually installed it in both
then i saw that in the mediapad m3 had been installed the smartphone version while in the “old tablet” had properly installed the tablet version,
what do you think?

@johje, @fluxxis, i was confusing, i was thinking in wrong way, i apologize, your suggests was right

There is a choice of display settings in system settings. You can choose small, medium or large.
Probably this setting changes the logical resolution of the display. Small is the right setting, after reboot the tablet behaves as a tablet should.

antisztar said:
There is a choice of display settings in system settings. You can choose small, medium or large.
Probably this setting changes the logical resolution of the display. Small is the right setting, after reboot the tablet behaves as a tablet should.
Click to expand...
Click to collapse
Hi... so we have to change display settings in the small view and launch the adb command?
In another thread I read the chance of modify the minimum value from 640 to 720 dpi in the developer settings.
What's the right choice?
Thanks.

how to change the size of the screen like in Nougat on Huawei p9.

I have a p9 updated to nougat and I find no option in the settings----> display to change the screen size. I saw that in the developer settings there is the "minimum width" and I set it as 420 (for having a very condensed screen) but some camera elements have glitches. How can you have the condensed screen without having glitches? * I do not have the root *
Thanks much

Giovanni9921 said:
I have a p9 updated to nougat and I find no option in the settings----> display to change the screen size. I saw that in the developer settings there is the "minimum width" and I set it as 420 (for having a very condensed screen) but some camera elements have glitches. How can you have the condensed screen without having glitches? * I do not have the root *
Thanks much
Click to expand...
Click to collapse
The "minimum width" setting is the dpi. For the camera if you set the dpi higher the Pro mode switch goes towards the shutter button, but if you set the dpi over 410 this switch glitches out and stays in the air. So the simple answer is don't set the dpi over 410.

_Frostplexx_ said:
The "minimum width" setting is the dpi. For the camera if you set the dpi higher the Pro mode switch goes towards the shutter button, but if you set the dpi over 410 this switch glitches out and stays in the air. So the simple answer is don't set the dpi over 410.
Click to expand...
Click to collapse
Yes, I was wrong to write, I said how to change the DPI of the screen. I set 409 to not have pro mode on the depth shutter and have the most condensed screen.
How does huawei not put it in the settings accessible to everyone (in the display to understand)?

Giovanni9921 said:
Yes, I was wrong to write, I said how to change the DPI of the screen. I set 409 to not have pro mode on the depth shutter and have the most condensed screen.
How does huawei not put it in the settings accessible to everyone (in the display to understand)?
Click to expand...
Click to collapse
I could be wrong, but i think its stock and manufacturer puts the dpi slider outside the developer settings, because you could mess up your screen. And i think it's accessible enough that people who know what DPI even means can change it. And you also don't need to mod anything to access developer settings, so everybody can use them.

_Frostplexx_ said:
I could be wrong, but i think its stock and manufacturer puts the dpi slider outside the developer settings, because you could mess up your screen. And i think it's accessible enough that people who know what DPI even means can change it. And you also don't need to mod anything to access developer settings, so everybody can use them.
Click to expand...
Click to collapse
Right, I did not think so

hey there,
i run Oreo on p9 AL10 and dev settings are 420dpi and no glitches in camera or anywhere.
Question, how to make settings survive a boot? it always defaults back to 360dpi after boot.
i played with build.prop but nothing worked for me. any ideas?
thx

AA 480p issue

Hey folks,
I am using this module to enable AA on my BMW headunit:
a.aliexpress.com/_U4Jz5
It kinda works nice except for one thing, resolution is not so clear due to dpi settings. Someone else dug into the system and found that in
etc/androidauto/androidauto_config.xml
The resolution is set to 480p instead of 720p and dpi is set to 150 instead of 180.
We have no SSH access but can only upload .bin update files as we dont know the password.
Does anyone know if it would be possible to change 720p to true and up the dpi somehow?
Carplay apparantly is 720p on this unit.
<DisplayWindow><!-- Head Unit side configuration--> <X_Coordinate value="0"/> <Y_Coordinate value="0"/> <DisplayWidth value="1280"/> <DisplayHeight value="480"/> </DisplayWindow> <Display><!-- Phone side configuration--> <DisplayWidth value="232"/><!-- Physical width--> <DisplayHeight value="87"/><!-- Physical height--> <Density value="170"/> <RealDensity value="153"/> <ViewingDistance value="400"/> <Resolution480P value="true"><!-- fps: 30 or 60--> <fps value="30"/> </Resolution480P> <Resolution720P value="false"> <fps value="30"/> </Resolution720P>

Nobody?

Anyone?

Do you have a copy of the BIN? My guess is unpacking and repacking the BIN will be the hardest part of this. You probably won't be able to do this without source scripts. You are in the right place regarding the XML file inside. All android head units, regardless of what they are, have to tell our phones what resolution to serve up. If the head unit says to run 1024x600 then that is what you are getting.
An alternative would be to ask the manufacture to release an update set to the proper settings.
---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------
Here you go The Andream unit you have should likely work with one of these firmwares. Do a lot of reading there before you proceed. I cannot be responsible for you flashing the wrong software to your unit.
I have a similar unit to yours and was able to get mine running at the proper resolution.

@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream (version: NBT-02B) unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).

ckarv said:
@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream cool:unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).
Click to expand...
Click to collapse
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.

heresy_fnord said:
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.
Click to expand...
Click to collapse
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks

ckarv said:
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks
Click to expand...
Click to collapse
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
This is accurate.
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
I don't know, perhaps this is true.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
Your scale of text is set by the DPI essentially. Its a combination of resolution and DPI. Basic example, if I was to set my DPI to 200, the text on my screen would be smaller.
* Attached a picture of my screen with 200 dpi.
This is a 10.25" screen with 220DPI
In your case, the one update file was made for a 10.25" screen. The thing is, there will be a DPI difference between the two even if the resolution is the same. I suspect you need check with that community to see if there is an update that maintains widescreen mode but uses the different DPI.
EDIT: To be fair, I think your screen looks "normal" but then, it looks like your clock and such are the same scale as mine. Maybe AA is just smaller text in general?