If you edit local.prop in /data/ to include the line "ro.sf.lcd_density=XXX" you can set the density size on boot without having to run an app or do a restart every time. Put whatever numbers you want for XXX, 160 is default and the higher the number the bigger the screen items will be. I personally like 120.
This works well with the button_bar off trick to make the notification bar the usual size while still having the buttons up top. Plus it lets you fit another 4 or so apps on the Zeam launcher bar.
{
"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'm curious how this might affect the crappy way the archos uses wallpaper? (cutting off the bottom of of the wallpaper) Would this change the way the wallpaper is scaled?
To be honest I'm not sure if it would actually shift the wallpaper or if that is independent of the lcd density settings, but either way it won't fix the archos wallpaper issue. If you see an actual image of what a picture would have to look like for the archos to make it "fullscreen" you'd see that proportionately zooming out won't work.
http://forum.archosfans.com/viewtopic.php?f=74&t=46103&start=0
Your best bet for that is the multipicture app as much as it sucks to have to run an app just for wallpaper.
Yeah I know, I hate that damn app. Stationary wallpaper. Bleah. My favorite thing is to have scrolling wallpaper. I'm learning how to re proportion the wallpaper. I was hoping that might fix some of it. Oh well. I actually like crop wallpaper better. Just cuz I can still get my scroll on lol
p0rk burn said:
If you edit build.prop in /system/ to include the line "ro.sf.lcd_density=XXX" you can set the density size on boot without having to run an app or do a restart every time. Put whatever numbers you want for XXX, 160 is default and the higher the number the bigger the screen items will be. I personally like 120.
This works well with the button_bar off trick in local.prop to make the notification bar the usual size while still having the buttons up top. Plus it lets you fit another 4 or so apps on the Zeam launcher bar.
View attachment 530219
Click to expand...
Click to collapse
What code did you use to get the menu buttons of the top bar? how can that be done?
Cuzz Face said:
What code did you use to get the menu buttons of the top bar? how can that be done?
Click to expand...
Click to collapse
Courtesy of Jerry101 and this thread: http://forum.xda-developers.com/showthread.php?t=940198
"root gen8
create a file "local.prop" at /data/
add follow line.
ro.board.has_buttonbar=no"
You need root, obviously, and should install button savior. Do that and give it a shot, worst case scenario is you just delete the two "ro" lines from build.prop and local.prop and you are back to normal.
How where you able to edit the build.prod in the system fs.
I'm logged in as root but it keeps saying readonly file.
Please advice...
Try copying it to somewhere else, add the line, and paste it back in and replacing the old one.
That's not making any difference.
I su to root, superuser grants me root rights, but chmod, editing with vi, cp to /tmp edit en pasting back does not work.
Any other ideas?
Are you rebooting after you are done? To be honest, I copied it into my dropbox folder with root explorer, edited it on my linux box, threw it back in dropbox, and moved it back into /system/, but it shouldn't matter doing it another way.
In the market there are file explorers that grant root privileges. This should help you write and delete in /system/. Just remember to go into settings in the explorer and enable the root options.
XDA ICE GLACIER - THEMED / Never stock
I already have root explorer on my device, I will try this in the morning.
I tried to do it in a terminal emulator but that's what giving me te problems.
So, I tried using another file manager, but writing in the system fs is not going to happen on my archos 101.
Just to be clear I'm running the out of the box firmware/kernel that I rooted with Archangel.
When I get a chance I will start from scratch and note my steps to do this. If that doesn't work it would have to be something to do with archangel, i guess. By chance, you aren't in RO mode are you?
Just know I'm not blowing you off but it might be a day or two. I have a horrible feeling (in my mouth) I need a root canal.
p0rk burn said:
When I get a chance I will start from scratch and note my steps to do this. If that doesn't work it would have to be something to do with archangel, i guess. By chance, you aren't in RO mode are you?
Just know I'm not blowing you off but it might be a day or two. I have a horrible feeling (in my mouth) I need a root canal.
Click to expand...
Click to collapse
Good luck at the dentist , I will keep my eye on this thread.
Archos 70it, rooted with Archangel
I just added the line "ro.sf.lcd_density=130" to the the file "local.prop" at /data/ (tanks to Jerry101) after the line ro.board.has_buttonbar=no".
It is working like a charm.
All the best
starsee said:
Archos 70it, rooted with Archangel
I just added the line "ro.sf.lcd_density=130" to the the file "local.prop" at /data/ (tanks to Jerry101) after the line ro.board.has_buttonbar=no".
It is working like a charm.
All the best
Click to expand...
Click to collapse
I think you mean build.prop in /system/ ...?
zebrapad said:
I think you mean build.prop in /system/ ...?
Click to expand...
Click to collapse
Nope /data/local.prop does the trick. No need to change build.prop.
right,
follow jerry101 at "http://forum.xda-developers.com/showthread.php?t=940198" and add this line "ro.sf.lcd_density=130" to "local.prop" at /data/.
Cool, glad that you guys got it working but I did it using the build.prop on my 101. Odd.
Regardless, I'll edit the first post since local.prop works.
Related
Hi, some wallpapers that I made for my dexterised folio.
The 2048x1024 wallpaper:
http://img443.imageshack.us/img443/5628/dextermod1.jpg
FolioMoD not DexterMoD of course! ;-) second edition:
http://img3.imageshack.us/img3/1079/foliomod1.jpg
A different one Foliomod1-1:
http://img829.imageshack.us/img829/2558/foliomod11.jpg
it would be better with a foliomod-wallpaper as dexter isn't the only person working on this mod anymore. and it would be nice to give the others a bit credit as well =) but a nice background non the less
Hi, I have a question. I have recently downloaded a 1024x700 wallpaper for my folio but when I try to apply it only lets me take a small piece of it. Which resolution should I take for it?
Thank you guys.
Sent from my HTC Desire using XDA App
metuskale said:
Which resolution should I take for it?
Click to expand...
Click to collapse
2048x1024 and after you choose what is dispayed in gallery.
kepler1982 said:
it would be better with a foliomod-wallpaper as dexter isn't the only person working on this mod anymore. and it would be nice to give the others a bit credit as well =) but a nice background non the less
Click to expand...
Click to collapse
Done. I should have give a name for each droid but as for honeycomb there'll be thousand of developpers ^^ I havn't got any more, so it ll be just foliomod.
costeph said:
2048x1024 and after you choose what is dispayed in gallery.
Click to expand...
Click to collapse
But I dont understand why wallpaper resolution has to be larger than system resolution
metuskale said:
But I dont understand why wallpaper resolution has to be larger than system resolution
Click to expand...
Click to collapse
I didn t search much more for a solution but in the basics settings I didn t find anything. All toshiba wallpaper seems to be like that.
Well, maybe is beacause if res. is larger and Android needs to crop the image you can select all image and when croped is being transformed to folio's resolution,
it's because of the wallpaper scrolling trough screens (so you need a wider wallpaper) and because toshiba can't do anything right (software wise).
the best solution, in my opinion. is to find/make a picture that's 1024*600. make a canvas around it in photoshop: like here.
save as a .png and put it into /toshiba/wallpaper/ using rootexplorer.
then (in launcherpro) disable wallpaper scrolling.
then you can select it from the toshiba gallery, and it won't be cropped.
someone should really make an app doing this automatically. i'm unfortunately no developer, so i have no idea.
So, as i understand; the file image needs to be croped (due to toshiba's fault?) and beacause of this image resoltion has to be larger.
But which resolution will work? (I mean, how much canvas do i have to add?!?!)
Thanks.
metuskale said:
So, as i understand; the file image needs to be croped (due to toshiba's fault?) and beacause of this image resoltion has to be larger.
But which resolution will work? (I mean, how much canvas do i have to add?!?!)
Thanks.
Click to expand...
Click to collapse
canvas should be 2048*1024, with anchor in top/middle. just like the example.
the cropping is an android thing, as android (officially) don't support screens larger than 800*480
this one is the one on my homescreen
kepler1982 said:
it's because of the wallpaper scrolling trough screens (so you need a wider wallpaper) and because toshiba can't do anything right (software wise).
the best solution, in my opinion. is to find/make a picture that's 1024*600. make a canvas around it in photoshop: like here.
save as a .png and put it into /toshiba/wallpaper/ using rootexplorer.
then (in launcherpro) disable wallpaper scrolling.
then you can select it from the toshiba gallery, and it won't be cropped.
someone should really make an app doing this automatically. i'm unfortunately no developer, so i have no idea.
Click to expand...
Click to collapse
I've tried to copy some wallpapers into the "System/toshiba/wallpaper/eu" folder but RootExplorer keep saying that the filesystem is read-only, although RootExplorer is granted SuperUser permission. Perhaps I'm doing something wrong...?
The system partition is mounted read-only by android.
Do you have an adb connection to your device?
If yes simply type adb remount to a console window to remount the system partition r/w
weeds2000 said:
The system partition is mounted read-only by android.
Do you have an adb connection to your device?
If yes simply type adb remount to a console window to remount the system partition r/w
Click to expand...
Click to collapse
or just press the "mount r/w" button in the upper left corner of rootexplorer when you're in that folder.
{
"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"
}
kepler1982 said:
or just press the "mount r/w" button in the upper left corner of rootexplorer when you're in that folder.
Click to expand...
Click to collapse
I already tried that, but nothing happens...
mddsd said:
I already tried that, but nothing happens...
Click to expand...
Click to collapse
try this command:
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
--copy the wpp---
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
or just download the Gallery3D I have uploaded (working perfectly on 0.4) and make the image your wallpaper like in any other android phone
--just copy it to /system/app--
link --> http://www.megaupload.com/?d=FH8L1QSM
Hello !
I've also a lot of difficulty with wallpapers' size ... But I think I just understand how it do. I've just making a pattern for a 3 desktop home (see in attachment). I test on my folio and it's the good size normally.
I hope it can help somebody, by the way I prefer share it here
Edit : I forget to give you the resolution that I found, with ADW launcher ... A classical wallpaper is 2048*1024 (like original toshiba wallpapers), into wide mode, the resolution is 2048*600 and each desktop do 1024*600 (and central desktop is composed by the left and right desktop, like on the picture )
Edit 2 : @ kepler1982 --> I've just finished a tool which allow you to put your wallpaper directly into the good folder (/toshiba/wallpaper). It runs under Windows (it's a batch script) and it uses ADB. For the moment it's just in French but I will try to post it here tomorrow in English. It's a Ready-to-use tool
Hi again, what about this tool?
I hope I can add some apps and remove some others to foliomod in near future and I would like to add some wallpapers too.
Can you post some wallpapers and that tool plz?
costeph said:
Hi, some wallpapers that I made for my dexterised folio.
The 2048x1024 wallpaper:
http://img443.imageshack.us/img443/5628/dextermod1.jpg
FolioMoD not DexterMoD of course! ;-) second edition:
http://img3.imageshack.us/img3/1079/foliomod1.jpg
A different one Foliomod1-1:
http://img829.imageshack.us/img829/2558/foliomod11.jpg
Click to expand...
Click to collapse
Thanks! They are very nice!
Wallpaper size needs to be 2048x1024 because if you put the Folio in portrait position then vertical resolution is 1024...
Experience Level required,
Some experience of the phones root directories
Basic Level App navigation
I cant be held responsible for what you may do to your phone. Rooting your phone voids your warranty and editing files in your Root directory may brick your phone. unexperience users SHOULD NOT perform this tutorial.
FROM THIS
{
"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"
}
TO THIS
What you need
A Rooted Droid, (i used my A855 with CM7, not sure if others will work)
Launcher Pro Plus (Regular Launcher Pro may work)
Also, there is no framework change, this is just a launcher theme and boot animation
Download The themepack and extract to the Root of your SD card
http://www.multiupload.com/SW5EGWV6VZ
The folder is self-explanatory
Wallpapers can be set from the Home Screen
Dock and Launcher
Go into Launcher Pro's settings via Prefrences button in the home screen
Select Appearance Settings
Select Dock Background
Use custom background
Go into gallery and find atrixdock.png
Go back and Restart LauncherPro
Now you should see the Dock
Because LauncherPro uses 4 Icon Docks we will have to use the following setup
{Phone}{Phone}{Drawer}{Contacts}{Contacts}
So, hold down each icon and set those apps
The icons will look a bit cluttered.
Hold down each icon and set the icon that can be found in the Theme_Atrix folder (the blank icon)
All you should see is the dock.
The dock is set
Boot Animation
Go and get SuperManager from the Market
Go into Settings and "Enable Root Function"
Open the File Explorer
Go up Back up level folder until the titlebar says "/"
Go into system
Choose R/W!!
Go into media
Press and hold bootanimation.zip and choose Delete
Confirm and "Back up level folder" to "/"
Open the Link, "sdcard"
Find the "Theme_Atrix" folder
Hold down and copy "bootanimation.zip"
Paste into /system/media/
Reboot.
If something didnt work, email me([email protected]).
i'm always here and i usually reply within 3 hours
Good Luck!
The dock and blank icon included in Theme_Atrix.zip were made by Tyler Watthanaphand. You are free to Redistribute and Modify.
it works for me thank you
will it work on my milestone running the 2.2 25/2/2011 leack?
same question. does it work for milestone?
It would work as dont see any framework change. Its all based on images being applied thru launcher pro... and a change of the bootanimation.
Sent from my Milestone using XDA Premium App
Is this just a theme for LauncherPro?
Definitely does not look like GingerBlur from the screen shot.
Is it more than Gingerbread with a Blur LP dock?
Thank you
david636 said:
Is this just a theme for LauncherPro?
Definitely does not look like GingerBlur from the screen shot.
Is it more than Gingerbread with a Blur LP dock?
Thank you
Click to expand...
Click to collapse
As far as I can tell, this is supposed to be a theme based on the stock Atrix theme. If that's the case, then it shouldn't look anything like gingerblur as that's simply a different rom/theme for the atrix.
Since it is based off the Atrix stock theme, it shouldn't have gingerbread elements as the Atrix only comes with 2.2 for now.
The Dock can be used for GSM Milestone.Right?
Works for me as well, love it.
Works for me too.. thx
Sent from my Milestone using Tapatalk
I downloaded this yesterday and I revisited the thread just to say thanks, it looks really good and I love how the boot animation says 'dual core' then my phone goes all laggy because of its underpowered processor I hope you make mroe themes like this
I'm having issues with DPI change, I used ADB to change the DPI using a simple adb shell wm density 460 && adb reboot, all good, only issue is a few things are.. weird.. For instance the "top apps" icon, little blue thinggy in the playstore is awkwardly big, it's larger then the font, but I didn't use the phone stock so I don't know if that's just how marshmallow is or if that's a dpi problem. I also noticed when loading The Sims FreePlay, the EA boot logo it extremely over scanned, the letters EA barely fit on the screen, the eBay app, the user display picture is cut off and only shows the bottom right corner on an icon that's huge and again over sized, as well as snapchat sending all of my snaps with extremely small font, yet on my screen before sending they look just fine.
So after looking into this further, the build.prop was never changed, it still says dpi 560, but I know for system files I need to mount /system in order to write to it without root. So I booted to recovery as that allows me write access to system, mounted system, says mounted /system at the bottom of the log, open adb, run adb devices, nothing comes up, it's not found, reboot phone, run adb devices, works fine. What's the deal? I can't get the 6p to work from recovery when mounting /system, it says it's mounted but on the computer end nothing is happening.
I also want to keep this phone as stock as possible, kind of a purist douche bag like that so I don't want to run TWRP, or at least I'm not committed to this DPI change being this important that I want a custom recovery.
So, anyone have any idea why I can't mount /system in the stock recovery? or rather, why I can mount it but why it's not working?
After a lot more work I found out I can't even mount /system without root. So I'm back to square one with the completely stock phone, and changing dpi. Does anyone know how to fix this?
I'll post pictures of the over sized icons. I'm not sure why it's happening, normally it would go the other way, it's almost as if anything lower then DPI 560 puts the phone into a table-esk ui preference so the icons go much bigger. all through it doesn't help at all when changing the dpi even smaller. I've gone to DPI 400 and a few random things screw up every time, I even tried dpi 540 and as soon as I go any lower then 560, the keyboard instantly goes huge, editors choice icons don't fit, and the profile pictures are random apps don't fit. There are also quite a few other issues I can't remember, I didn't sleep well, mind fading.. Anyway, it's more of an annoyance, a lot of apps don't actually work when the DPI is changed, and like mentioned in the first post, I'm not looking to root as a solution, mostly because the latest snapchat updates look for superuser access and block rooted devices.
This is actually why I bought the Nexus 6p was so I don't need root to get the clean AOSP look I wanted with a small but organised DPI that fits everything perfectly to use the most out of the larger screen on my old Note 4 (460 DPI, Google Music icons at the bottom for play, thumbs up or down and skipping tracks are all perfectly spaced apart), but after kernel issues with Samsung blocking root with 5.1.1 and then custom kernels and blah blah blah, I finally got Android 5.1.1 working with root, and then I find out snapchat blocked root so I went out that night and bought a Nexus 6p, now it's looking like I'm going to need root to get a proper DPI change unless someone has found a work around or maybe a DPI that doesn't trigger the UI to glitch out with those massive icons and keyboard. (just pointing out it's not all keyboards, it's just some of them, swiftkey the whole thing is huge, ginger keyboard only the suggested word box is huge, I also use an aftermarket keyboard because emoji is disabled in Marshmallow for anything other then sms apps, so I can't use emoji's in snapchat or instagram with the stock google keyboard)
This is when I try to use SwiftKey Keyboard
{
"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 editors choice icons are oversized and don't fit
Profile pictures on a few random apps (ebay app shown) are all over sized with a tiny photo inside off to the top left corner
flash TWRP then mount /system from within TWRP, then try using ADB, as far as I know stock recoveries never had adb enabled fully, only adb sideload. once you're done flash the stock recovery back.
Good day people,
I have a question which is easy for you guys but almost impossible to find out for me because of bricking the device and the noob knowledge.
I have a Tesla style headunit with 4.4.2 which is rooted.
Please take a look at the picture below. I want to disable (if not possible remove) the two highlighted bars on top and bottom.
The device is rooted. And I already tried different launchers.
Can somebody give me advice were to look in which or at which file?
{
"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"
}
Did you try changing your launcher? Try NOVA, CAR DASH, ...
true2you said:
Did you try changing your launcher? Try NOVA, CAR DASH, ...
Click to expand...
Click to collapse
Good one!! Forget to mention, already did that. Launcher changes but the top and bottom bar remains...
Crunch8101 said:
Good one!! Forget to mention, already did that. Launcher changes but the top and bottom bar remains...
Click to expand...
Click to collapse
I assume it is part of the systemUI or some other "sub" server like apk. Another launcher won't change that.
Do you have a CAN bus installed? If so see if you have a CAN bus apk as well and try to disable that one. You might loose your bottom bar as that is a typical CAN bus type apk overlay.
That is correct, I have canbus. And the top one? Is it just a process which I can stop to check if it is this? Or is it not that simple?
Crunch8101 said:
That is correct, I have canbus. And the top one? Is it just a process which I can stop to check if it is this? Or is it not that simple?
Click to expand...
Click to collapse
I don't know, but my guess is that is is some "menu" like apk that overlays on top of the launcher. More like some kind of secondary systemUI or "sub server" apk. To make a more selective guess, but still a guess, you should show us a listing of /system/app and /system/priv-app
You are right! Checked all the apk in the folder you said and I got to com.android.system-UI this is the UI which is responsible for the top and bottom bar.
But now....it also manages bluetooth calls and settings from canbus so I cannot disable it. So the questions are getting a little difficult now. Were do I begin with this files to edit it that the UI is not shown anymore but the functionality remains?
Thank for taking the time to help me, really appreciate it.
Crunch8101 said:
You are right! Checked all the apk in the folder you said and I got to com.android.system-UI this is the UI which is responsible for the top and bottom bar.
But now....it also manages bluetooth calls and settings from canbus so I cannot disable it. So the questions are getting a little difficult now. Were do I begin with this files to edit it that the UI is not shown anymore but the functionality remains?
Click to expand...
Click to collapse
You can indeed not remove the systemui, but that makes it at the same time also very complicated.
You need to be a java programmer or smali programmer to correct that. And because you don't have the source code (I assume), you need to re-engineer the code. I can't help you there.
If you want to go on with this take a look at jadx to decompile the apk, and make the modifications in smali with apktool.
But that's something really requiring java skills.
Is it to easy to see it like this: disabling systemUI forever. Make new shortcuts from the bluetooth.apk to the desktop. Also making new shortcuts from CAN settings and Nav settings to the desktop? What am I missing here?
Also, you say I need the source code, but I already have the system running so why do I need the source code? My little knowledge can give strange questions sorry
Crunch8101 said:
Is it to easy to see it like this: disabling systemUI forever. Make new shortcuts from the bluetooth.apk to the desktop. Also making new shortcuts from CAN settings and Nav settings to the desktop? What am I missing here?
Click to expand...
Click to collapse
Crunch8101 said:
Also, you say I need the source code, but I already have the system running so why do I need the source code? My little knowledge can give strange questions sorry
Click to expand...
Click to collapse
You need a systemui. It is the base layer for your graphical system. The launcher is just a "presenting" layer on top of that.
It means that you need to make changes to the existing systemui, or find a compatible systemui. The second is almost impossible as these systemUIs are specifically adapted for these head-units.
So only the first option applies: Change the existing systemUI.
You need a person understanding java and smali, and who knows the technicalities of your unit more or less. There are some gurus being able to do that, but the combination is hard to find. And even for him/her it will take hours and hours to find and modifiy it.
Hahaha! Thought it was something with /hide bla bla. Thanks for explaining it to me. I am going to try to get some help here on XDA
Got this solution from the ever resourceful [4pda forum](https://4pda.ru/forum/index.php?showtopic=877711&view=findpost&p=72236272) (Google translated):
1. Install and configure the most convenient way for yourself here is this program [UDN, Ultimate Dynamic Navbar](https://4pda.ru/forum/index.php?showtopic=460767) This is a small launcher that can be configured to auto-hide and "pull" it from the edge or of the screen angle.*Also, what's important is that you can add your own add-ons to it.*button.*This launcher is needed, because*in the full screen mode, there are no other buttons.*
2. mini-program for hiding navbar and systemUI: [NavBar_UIkill.apk](https://4pda.ru/forum/dl/post/12610888/NavBar_UIkill.apk)*(1.52 MB)*It is installed in the standard way.*Then it must be added as a button on the UDN.
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?