Hi all, simply changing the dpi value through the developer options I finally managed to have the screen aligned to the notch. Just find the "minimum width" item in the developer menu and change the value from 392 to 449 (now I've set it to 430 and "text size & resizing" to XL, seems much better)
Smaller icons but finally full screen ...
Hi. I changed the value but it has stayed the same. No changes in the display size either. Am I doing anything wrong?
lalibm said:
Hi. I changed the value but it has stayed the same. No changes in the display size either. Am I doing anything wrong?
Click to expand...
Click to collapse
hi, I don't know why it didn't work for you.
I didn't do anything else except what I wrote above, as soon as I write the new value and confirm it the screen immediately changes its size.
I'm on Miui 10 developer.
Now I set the value at 430 dpi because it seems more balanced.
Nathan971 said:
hi, I don't know why it didn't work for you.
I didn't do anything else except what I wrote above, as soon as I write the new value and confirm it the screen immediately changes its size.
I'm on Miui 10 developer.
Now I set the value at 430 dpi because it seems more balanced.
Click to expand...
Click to collapse
I tried rebooting several times but to no effect. I'm running 10.0.5.0 Global. Maybe there's a bug. Thanks anyway.
I'm sorry, I'm on 8.12.27 dev and don't know if global stable works in a different way.
I forgot to say that this thing, of course, works for those who want to hide the notch and not lose that part of the screen that remains black under it.
I hope the developers understand that that lost space makes no sense, as it makes no sense to see the notifications for 2 seconds and then make them disappear ... Anyway, happy new year to all of you
Nathan971 said:
I'm sorry, I'm on 8.12.27 dev and don't know if global stable works in a different way.
I forgot to say that this thing, of course, works for those who want to hide the notch and not lose that part of the screen that remains black under it.
I hope the developers understand that that lost space makes no sense, as it makes no sense to see the notifications for 2 seconds and then make them disappear ... Anyway, happy new year to all of you
Click to expand...
Click to collapse
I hate the way notifications behave on MIUI. The fact that I can't swipe either way to dismiss a notification makes no sense. Hopefully Xiaomi releases the kernel source and then development will pick up pace. Cheers and Happy New year
Bobby
How to Align the Screen with Notch in the Mobile with Global Rom 10.2.1.0 ?
there is no dpi setting in my developer mode. (using MIUI Global Stable )
My mom owns a RN6P. I checked it and figured out a way to fit apps with the notch. See what values I set in attachments.
Samples:
{
"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"
}
Edit: I guess XDA servers don't load the images I took. Here are direct links to them:
https://i.hizliresim. com/qdjAdd.jpg
https://i.hizliresim. com/MVo1V1.jpg
Remove the space between "com" and "dot"
Lol, I don't know why XDA tries to fetch my photos to their servers and fail to load.
DarkCod3r said:
there is no dpi setting in my developer mode. (using MIUI Global Stable )
Click to expand...
Click to collapse
The easiest way is to run this command..
Code:
adb shell wm overscan 0,-32,0,0
No need of changing DPI through developer settings and having that ugly small looking UI.
bande.rajkiran said:
The easiest way is to run this command..
Code:
adb shell wm overscan 0,-32,0,0
No need of changing DPI through developer settings and having that ugly small looking UI.
Click to expand...
Click to collapse
where i have to enter this command ?
bande.rajkiran said:
The easiest way is to run this command..
Code:
adb shell wm overscan 0,-32,0,0
No need of changing DPI through developer settings and having that ugly small looking UI.
Click to expand...
Click to collapse
Command executed successfully but still no change.. Same issue.
Follow these tutorials: (need root)!
https://4pda.ru/forum/index.php?showtopic=927965&st=280#entry81179571
https://4pda.ru/forum/index.php?showtopic=843497&st=20#entry64339025
Sent from my Xiaomi Redmi Note 6 Pro using XDA Labs
Someone should make a Flashable TWRP zip file for this fix..
bande.rajkiran said:
The easiest way is to run this command..
No need of changing DPI through developer settings and having that ugly small looking UI.
Click to expand...
Click to collapse
In what part should I execute the command?
bande.rajkiran said:
The easiest way is to run this command..
Code:
adb shell wm overscan 0,-32,0,0
No need of changing DPI through developer settings and having that ugly small looking UI.
Click to expand...
Click to collapse
Thanks!
-20 is better for me.
smartiz77 said:
Thanks!
-20 is better for me.
Click to expand...
Click to collapse
but its not working for all apps.. :/ some apps still not perfectly aligned with notch..
Hi everyone, I'm using a rooted Samsung A10 and had a similar issue with the unallignment of the camera notch. I came across this forum and solved the problem using "adb shell vm overscan" command. However this caused the upper Quick Panel aread become narrower and not only the appearance but also functionally it is too difficult to pull it down when it's such narrow. Please check the photo. Do you guys have any suggestions for that?
Related
Hey guys, I compiled a zip files including instructions on how to make your shadow 96DPI.
Credits goes to fallency from XDA for posting it in the Excalibur section. I just compiled it into a easy to understand zip file.
Screenshot:
{
"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"
}
Download:
http://files.martint.net/shadow/61/96DPI.zip
Directions:
1) Run the WM6.1-131to96dpi cab file
2) when it asks for you to restart, do not restart.
3) Run CeleCMD, and click the "..." button.
4) Go to Menu, Browse Folder, and select the folder where you put the dpi.ccs file.
5) Now you will see the dpi file, and then go ahead and run it.
6) Wait for it go back to the homescreen and then reboot your phone.
Click to expand...
Click to collapse
............................................
this doesnt work
Z51 said:
this doesnt work
Click to expand...
Click to collapse
It does work...there are some bugs tho. Iam using win mo 6.1 clean edition and the com manager is over lapping it self and the wallpaper that i put on is a little to small. At the very bottom the is a black line were the wallpaper didnt streach correctly. But I like it... I will keep you posted on any bugs i come across and see if you can help me fix them....
Thanks
suasp0nte said:
It does work...there are some bugs tho. Iam using win mo 6.1 clean edition and the com manager is over lapping it self and the wallpaper that i put on is a little to small. At the very bottom the is a black line were the wallpaper didnt streach correctly. But I like it... I will keep you posted on any bugs i come across and see if you can help me fix them....
Thanks
Click to expand...
Click to collapse
Clock on CHome CClock page does not display correctly shows as 7:28000
any way to fix this? Using win mo 6.1 as well.
Just Change the settings for your clock to 2400 hours instead of PM and AM.
what does this do?
can anyone tell me what this does? thanks a lot for the info
Love it, except for the signal and battery meters on top
Has anybody else noticed that, when in a screen other than the homescreen (I'm using the colored iconbar plugin from Rinku), the signal, battery, and message icons on the top bar appear as only white boxes? Also, the comm manager doesn't work right, none of the "buttons" glow and I can only choose the phone one by pressing the number 1. Pressing 2, 3, 4, etc don't appear to do anything...
Is there a way to fix this?
I REALLY want to keep the 96dpi running. It looks really nice, and improves my homescreen real estate.
Anyone figure out a way to fix this?
GREAT tweak, other than those minor bugs...
THanks for your work!!
Jeff
drewdown227 said:
can anyone tell me what this does? thanks a lot for the info
Click to expand...
Click to collapse
DPI usually mean Dots per inch, which is another way to describe resolution. i'd say to check out the excalibur forum for the full story... i'm abotu to myself
EDIT:
pudgedaddy said:
...basically this works similarly to increasing your screen resolution on your PC.(minus the actual resolution changing) meaning it fits more stuff on your devices display since it shrinks down what is placed on your screen.
Click to expand...
Click to collapse
has anyone tried this on WM6.0 yet? i have not upgraded to 6.1 for various reasons, btu a change in the DPI sounds like a plus to any rom... i may just have to try this anyway...
phatman81 said:
has anyone tried this on WM6.0 yet? i have not upgraded to 6.1 for various reasons, btu a change in the DPI sounds like a plus to any rom... i may just have to try this anyway...
Click to expand...
Click to collapse
I'm running WM6.1, and it works great, with the exception of the issues a couple posts up from me. I"m still using it though, the issues aren't enough to outweigh the cool benefits!
Install it and enjoy...
Jeff
phatman81 said:
has anyone tried this on WM6.0 yet? i have not upgraded to 6.1 for various reasons, btu a change in the DPI sounds like a plus to any rom... i may just have to try this anyway...
Click to expand...
Click to collapse
I agree. Other than the issues with the clock which was changed with military time everything is great for me. And if you dont like it then remove the cab and it will revert.
What is the Default DPI
Does anybody know what the default DPI is for the Shadow?
I dont get why when I Run CeleCMD all i see is boxes instead of actual words. Any one else having this problem?
I have the White Box Problem as well. They don't seem to be going away and My Buttons 1-9 are non-responsive as well and fix for this!
Default DPI for the shadow is 131
Hi Guys,
i've changed my LCD Density to 200.
Works fine and looks great.
But some Apps, like Facebook, were not stretched to fit the Display.
I've read something about a Compatibility-Mode, but doesn't found anything.
Greets,
sL!zoNe
sL!zoNe said:
Hi Guys,
i've changed my LCD Density to 200.
Works fine and looks great.
But some Apps, like Facebook, were not stretched to fit the Display.
I've read something about a Compatibility-Mode, but doesn't found anything.
Greets,
sL!zoNe
Click to expand...
Click to collapse
find an app, i think its on the market, called Spare Parts, there is a compatibility Mode in there which needs disabling. That should sort it out for you.
Thank you.
can u make a screen that i can see whats different with 200dpi??thank u !!
200 DPI basically makes it "appear" that you have a higher resolution screen. Characters and icons are smaller on the screen so it appears that you have more space.
Changing to 200DPI is more of a nuisance than a blessing when using a screen smaller than 4.3 inches, which is why you'll see more and more people with the HD2 using it.
180 here for me and it's lovely, on the ROM in using Button Savior doesn't seem to want to work properly with 200, athough it has previously with other ROM's using 200 :s
Using Launcher Pro with 5 Rows x 6-7 Columns. The whole screen just seems alot less cluttered.
{
"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"
}
Wow nice and where i can change the DPI??
honki said:
Wow nice and where i can change the DPI??
Click to expand...
Click to collapse
/system/build.prop
in there, about 1/2 way down, change the value of "ro.sf.lcd_density=***" to whatever you want the value to be, either 200 or 180, whatever you feel looks good.
Remember to restart after changing the value.
Or, i think there is an LCD Density changing app on the market, but ive never used it.
`Thank u works great & looks nice!!
but 1 question: it seems to me, that my smart keybord is smaller too? Can this be true?
honki said:
`Thank u works great & looks nice!!
but 1 question: it seems to me, that my smart keybord is smaller too? Can this be true?
Click to expand...
Click to collapse
i guess the density effects the whole system (besides apps that run in an own window like fullscreen games)
I highly recommend Zeam Launcher as launcher, when DPI is changed,
it scales icons and labels very well, 5,6 or 7 columns is also nice!
Widgets size can also be changed when added to screen.
Gushfevah said:
180 here for me and it's lovely, on the ROM in using Button Savior doesn't seem to want to work properly with 200, athough it has previously with other ROM's using 200 :s
Using Launcher Pro with 5 Rows x 6-7 Columns. The whole screen just seems alot less cluttered.
Click to expand...
Click to collapse
Please, what is the name of this battery widget with battery status and current information ?
magoo1275 said:
Please, what is the name of this battery widget with battery status and current information ?
Click to expand...
Click to collapse
Battery Monitor Widget
Sent from my HD2 using XDA App
Calendar Situation:
2560x1440 resolution screen has LESS information displayed verses my 1280x800 tablet.
Solution.
build.prop change to the DPI setting.
380 DPI + reboot+ calendar cache clear == TABLET VIEW!!! 7 day weeks and full month view with text.
390 DPI or greater will revert back to stupid mode.
Now, this is a very short sided solution, but I think my OS looks better with smaller icons... Rather than having 5 icons of width on my home screen, I have 6. I get more mail and more calendar in the widgets too. I honestly don't see a downside.
380 makes it pretty much unusable, IMO. I have it set to 460. 440 was too small for me.
Sent from my Nexus 6 using Tapatalk
just a FYI, native DPI for the N6 is 493.
tflogic said:
just a FYI, native DPI for the N6 is 493.
Click to expand...
Click to collapse
We're taking about the LCD DPI setting, not the physical screen's DPI. The default setting is 560.
Sent from my Nexus 6 using Tapatalk
Acrono said:
380 makes it pretty much unusable, IMO. I have it set to 460. 440 was too small for me...
Click to expand...
Click to collapse
Well, I'm happy with the smaller icons and text as long as I can get a 7 day calendar and a USEFUL month view on my phone.
How do you do this? Need to be rooted?
brian85 said:
How do you do this? Need to be rooted?
Click to expand...
Click to collapse
Yes you need root, then you edit the build prop using ROM tool kit or a good file explorer.
Pilz said:
Yes you need root, then you edit the build prop using ROM tool kit or a good file explorer.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi is another alternative. Works great, lightweight app.
zephiK said:
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi is another alternative. Works great, lightweight app.
Click to expand...
Click to collapse
Good idea but waiting until Xposed works so I can set this DPI only for Calendar and not the whole system.
jeffreii said:
Good idea but waiting until Xposed works so I can set this DPI only for Calendar and not the whole system.
Click to expand...
Click to collapse
Isn't there apps to just change per app basis? If so, what are they?
cheami said:
Isn't there apps to just change per app basis? If so, what are they?
Click to expand...
Click to collapse
AppSettings on xposed...but first we need xposed. No per app settings without it as far as I'm aware.
Can we get pics of the Homescreen/other screen shots running at 380DPI please?
liqn7 said:
AppSettings on xposed...but first we need xposed. No per app settings without it as far as I'm aware.
Can we get pics of the Homescreen/other screen shots running at 380DPI please?
Click to expand...
Click to collapse
As you can see, the items on screen are quite small, and some applications don't know how to size their content. But, I get my full month
{
"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"
}
kajer said:
As you can see, the items on screen are quite small, and some applications don't know how to size their content. But, I get my full month
Click to expand...
Click to collapse
I just updated to 5.0.1 and my DPI was reverted to 560... I have no idea who thought that was a good idea.
jeffreii said:
Good idea but waiting until Xposed works so I can set this DPI only for Calendar and not the whole system.
Click to expand...
Click to collapse
Think it's going to be a very long wait for xposed to work on ART.
Sent from my Nexus 6 using XDA Free mobile app
kajer said:
I just updated to 5.0.1 and my DPI was reverted to 560... I have no idea who thought that was a good idea.
Click to expand...
Click to collapse
This happened because the 5.0.1 update replaced the build.prop file in /sytem with with a new version.
If you want to make the custom 380 dpi stick across updates, you should create a text file called local.prop and place it in the /data directory.
The local.prop text should include the following line:
Code:
[STRIKE]qemu.sf.lcd_density=380[/STRIKE]
Save the file and reboot.
EDIT: this method doesn't seem to work on the stock ROM any longer. It works with CM and mist likely with other AOSP derived ROMs.
hi,
I have been out of android for abit but 1 of the the first things i do is mod my dpi (more icons, more screen, more widgets etc.. for me)
using dpi changer or build prop editor
however this time on nexus 6 it seems to change all except the icons and icon text sizes and widget space
i have tried putting the local build to no avail. is there anything else i need todo or any ideas
i am unlocked and rooted.
thanks
cryptkilleronline said:
hi,
I have been out of android for abit but 1 of the the first things i do is mod my dpi (more icons, more screen, more widgets etc.. for me)
using dpi changer or build prop editor
however this time on nexus 6 it seems to change all except the icons and icon text sizes and widget space
i have tried putting the local build to no avail. is there anything else i need todo or any ideas
i am unlocked and rooted.
thanks
Click to expand...
Click to collapse
Hi cryptkilleronline,
It looks like the local.prop method doesn't work anymore on the stock ROM (CM and other ROMs still support it).
You'll have to reduce the value in build.prop instead.
The only thing I'd recommend is not to use 380 or 370 dpi, as these values seem to cause some issues in landscape mode.
360 dpi works fine.
More details here:
http://forum.xda-developers.com/nex...freezes-landscape-video-t2967032/post57636267
Hi all,
yesterday I finally got my M3 a
I just have got 1 problem I seem not able to fix:
Chrome always seems to think the tablet is a phone... So it runs in phone layout instead of tablet layout
Is there a way to fix it?
(I can't post links since I have less than 10 posts... but you can just google for "chrome tabs phone layout", go to picture search mode.
--> the first picture shows my layout on the left... and the one it should use on the right.)
Thanks for your help and sorry for my bad english.
Just click request desktop site under chrome settings
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
{
"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"
}
Sent from my Pixel XL using XDA-Developers mobile app
Hussainally said:
Just click request desktop site under chrome settings
Click to expand...
Click to collapse
Sorry perhaps I did not describe the problem clearly enough:
It's not my problem to get the desktop version of a homepage getting opened.
The problem is, like on your picture, chrome not showing all tabs on top of the screen (like in the desktop version of chrome or on most tablets like my old nexus7 2013), but to "hide" them behind this little tab icon (showning "3" on your picture) in the right upper corner.
It's like on this picture... It should look like the part on the right side.
(Just replace the three XXX with a "." / dot)
cdn.ilovefreesoftwareXXXcom/wp-content/uploads/2015/01/Chrome-Phone-Layout-vs-Tablet-Layout.png
Edit:
Okay I got a solution. It's pretty simple.
Via ADB:
adb devices (to check if devices connected)
setting density to 391 (or less) via: adb shell wm density 391
--> Tadaa tablet mode in chrome
Are u rooted ?
Sent from my Pixel XL using XDA-Developers mobile app
Hussainally said:
Are u rooted ?
Click to expand...
Click to collapse
Nope,
this one is not rooted yet. So can't use the xposed framework.
@Hussainally
How did you get the homepage button?
xda_dario said:
@Hussainally
How did you get the homepage button?
Click to expand...
Click to collapse
It's been there ever since ..did nothing
Sent from my Pixel XL using XDA-Developers mobile app
Also on the predefined mode, the tabs are not working... like chrome is confused.
I filed a bug on Chrome for that too. but maybe chrome needs to include this device on tablet side of the moon.
I managed to force it into tablet mode (thx to nospherato) but I never had a homepage button.
The adb shell density command does not work on my M3. What could I be doing wrong?
hi flavio,
you took these steps?
1) activated the developer menu
2) activated the usb debug mode
3) connected pc+m3 ("adb devices" should not show "not authorized")
4) typed
adb shell wm density 391
?
(btw on my windows shell I had to use adb.exe instead of adb command... damn win10)
You should at once see the screen getting modified.
nospherato said:
hi flavio,
you took these steps?
1) activated the developer menu
2) activated the usb debug mode
3) connected pc+m3 ("adb devices" should not show "not authorized")
4) typed
adb shell wm density 391
?
(btw on my windows shell I had to use adb.exe instead of adb command... damn win10)
You should at once see the screen getting modified.
Click to expand...
Click to collapse
I did all these steps before but it never got it working.
Somehow I did get it to work now (set it to 320) but I still don't know what I did differently.
And it reverts back to 440 after a reboot. Is that normal?
Yes it is normal it gets reset after a reboot... Also if you change your resolution (power save, lower resolution) it gets reset.
I think you can only get it working permanently if your device is rooted.
Btw: If you use the normal resolution chrome starts to work in tablet mode @391 density.
If you want to use the battery saving mode (1200x1920), it starts at 293. (I prefer this one, as the quick actions do not get messed up here.)
Thanks for the help @nospherato & @Flavio.
I had the same issue with the Mediapad M3. Just got this today and having Chrome in phone mode and not table mode is a big drawback.
I could not even switch between tabs (hitting the square with the number of tabs in it did not show the list of open tabs to close it).
What worked for me was:
adb shell wm density 320
Click to expand...
Click to collapse
This immediately switched Chrome to show the row of tabs at the top and allowed me to close them as well.
Thanks XDA community.
The strange thing is that when you switch back to 400 DPI Chrome stays in tablet mode, i.e. with the tabs above the address bar.
At least in some regions Huawei released an update which should add the option to remove the on-screen navigation and fix the Chrome problem: http://forum.xda-developers.com/showpost.php?p=69664225&postcount=14
Flavio said:
Somehow I did get it to work now (set it to 320)
Click to expand...
Click to collapse
I had the same problem. No bookmark star and can't change the tabs.
Set to 320 works for me to.
Makes me happy!
Back to 400 i had the same problems. So i tested some variable values.
356 and smaller - No Problem
357 or higher - The same Problems.
BTV-DL09 LTE Modell
Is there a way to permanently fix the tabs and user agent from phone mode? I can't close tabs and swiping to switch them is annoying.
If I do adb do I have to redo it every reboot if my only desire is having tabs work? I don't even have my favourites menu or reload buttons.
@Sean09
Well as I know the only other way is to root your device and use expose framework. There is a plugin where you can set things like that for your apps.
If you do not want to root your device, you will at least have to wait for an ota update from huawei.
(If I got it right, this problem does not exist in newer [thai/chinese] versions... but until now, no huawei support could/wanted to tell me if or when eu pads get an update...)
I wonder if we can flash the other firmware that has already had an update made available to it - I assume they'll get updates quicker than we will in the USA as well.
Some apps don't use the entire display. With some apps, I want it to use the whole display while in others I don't. So how do I do that? Also in another form, I read that you use the adb. So I got that but when I run adb devices I don't see my phone. Also my phone is charging, but I'm not able to see the phone on my file explorer either.
Also, I am just 11 years old, so I don't really understand this kind of stuff. So it would be much loved if you guys can explain this in basic terms.
My World Rules said:
Some apps don't use the entire display. With some apps, I want it to use the whole display while in others I don't. So how do I do that? Also in another form, I read that you use the adb. So I got that but when I run adb devices I don't see my phone. Also my phone is charging, but I'm not able to see the phone on my file explorer either.
Also, I am just 11 years old, so I don't really understand this kind of stuff. So it would be much loved if you guys can explain this in basic terms.
Click to expand...
Click to collapse
https://forum.xda-developers.com/es...x-apps-filling-screen-nova-included-t3670404/
vexx109 said:
https://forum.xda-developers.com/es...x-apps-filling-screen-nova-included-t3670404/
Click to expand...
Click to collapse
Yes I tried that.... But the phone is not being recognized on my PC.
You have to go download the adb drivers from Google. And then enable developer options on your phone as well.
vexx109 said:
You have to go download the adb drivers from Google. And then enable developer options on your phone as well.
Click to expand...
Click to collapse
Yes, but I can't find the drivers for the essential phone...
My World Rules said:
Yes, but I can't find the drivers for the essential phone...
Click to expand...
Click to collapse
They're not specific to essential. It's the Google drivers. My advice to you is to start researching this stuff before you begin utilizing adb or any other commands. At this point, we don't even have the stock images so if you screw something up you're SOL right now....
Drivers here:
https://developer.android.com/studio/run/win-usb.html
Sent from my PH-1 using Tapatalk
My World Rules said:
Yes, but I can't find the drivers for the essential phone...
Click to expand...
Click to collapse
Use Minimal ADB and Fastboot. https://forum.xda-developers.com/showthread.php?t=2317790
Enable USB Debugging from developer options in your Android settings.
Connect usb cable.
Press yes on the phone.
Type:
adb shell settings put global ESSENTIAL_LAYOUT_WHITELIST "*"
Sent from my PH-1 using XDA-Developers Legacy app
Oh ok. So I understand how to get the drivers. So now I have to open the adb shell settings put global ESSENTIAL_LAYOUT_WHITELIST. But will that allow all the apps to use the full display?
My World Rules said:
Oh ok. So I understand how to get the drivers. So now I have to open the adb shell settings put global ESSENTIAL_LAYOUT_WHITELIST. But will that allow all the apps to use the full display?
Click to expand...
Click to collapse
you run the command from the command prompt
Sent from my PH-1 using Tapatalk
So after I run the command will it get all the apps to use the full display?
My World Rules said:
So after I run the command will it get all the apps to use the full display?
Click to expand...
Click to collapse
You need the put in the "*" aftewards, because it's a white list the astrisk signifies "Everything" also, it's called a wildcard.
the full command should look like this:
adb shell
settings put global ESSENTIAL_LAYOUT_WHITELIST "*"
Ok guys, so I tried the command. While it has changed and allows some apps to use the entire display. Other apps still have a black bar on the top of the app... How do I remove that bar?
Yes so I tried that... but some apps still have a black bar on the top of the screen...
{
"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"
}
That will likely be something the devs of the apps have to do as the screen ratio is a bit different than what they built the apps for. The best way I can think to describe it is like with movies. If you have a 4:3 ratio show playing on a 16:9 ratio the you're still gonna have the bars. But if you have a movie that can support 16:9 you'll have full screen coverage.
So is it possible to "Stretch the app" to use the entire display?
vexx109 said:
You need the put in the "*" aftewards, because it's a white list the astrisk signifies "Everything" also, it's called a wildcard.
the full command should look like this:
adb shell
settings put global ESSENTIAL_LAYOUT_WHITELIST "*"
Click to expand...
Click to collapse
thanks for the clarity
My World Rules said:
Yes so I tried that... but some apps still have a black bar on the top of the screen...
Click to expand...
Click to collapse
Very few game will likely ever work for this. The resolution and assets are typically not designed to scale to different aspect ratios like this phone has. Even the LG G6 and Galaxy S8 just crop off the edges of games when they make them fit on the display fuilly.
*Off topic*
Just wanted to say reading this thread and the fact that no one jumped down his throat for asking questions and helped him through the steps reminds me of xda back in the day. And slight restored my faith in humanity. Good jobs mofos ✌??
skw5115 said:
you run the command from the command prompt
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
tigercranestyle said:
this is what some apps look like when you use the whitelist editor and hide the navbar simultaneously. youtube and google play movies look like this when you do both.
it looks like your game, by default, hides the navbar. have you tried using the whitelist editor app do nothing to the status bar and unhide the navbar?
Click to expand...
Click to collapse
I don't understand. What do your mean by whitelist editor app... What is that?
tigercranestyle said:
the app located here: https://forum.xda-developers.com/essential-phone/themes/essential-layout-whitelist-editor-t3671285
try using the app to not take advantage of the status bar by unchecking it. then override the default setting off your game by de-selecting the box to show the navbar. seems like it would be better to have a navbar than the black bar up top.
Click to expand...
Click to collapse
Thanks the app works for some apps. However, for most of my video games, there is still a black bar. Like I asked above... is it possible to get the app to stretch to the entire phone.