CM13 - non-default DPI issue - G 2014 Q&A, Help & Troubleshooting

Hi,
when setting a non-default DPI (240) several app UI are broken. The positon of UI elements are misplaced.
Anyone else experiencing the same?
DocMAX

DocMAX said:
Hi,
when setting a non-default DPI (240) several app UI are broken. The positon of UI elements are misplaced.
Anyone else experiencing the same?
DocMAX
Click to expand...
Click to collapse
i have problem when i change the DPI, the device reboot and is infinite bootanimation, i need to forze the reboot and then it show Optimizing apps ... and it boot fine, that's my problem while change the dpi. strange problem

I experience the sam that @JAppina92 but i use 280 dpi and no problem
Enviado desde mi Moto G 2014 mediante Tapatalk

japoina92 said:
i have problem when i change the DPI, the device reboot and is infinite bootanimation, i need to forze the reboot and then it show Optimizing apps ... and it boot fine, that's my problem while change the dpi. strange problem
Click to expand...
Click to collapse
Bro it's CM 13 bug softboot is broken...
We Are Titans
---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------
DocMAX said:
Hi,
when setting a non-default DPI (240) several app UI are broken. The positon of UI elements are misplaced.
Anyone else experiencing the same?
DocMAX
Click to expand...
Click to collapse
You better try changing dpi with any root Explorer by editing buildprop from there. It help me when my ui elements are misplaced. Go to root > system > buildprop and edit it with text editor find lcd density and change it to 240 or whatever u want and then reboot...
We Are Titans

Reset DPI to stock
Hey all,
I change my phone (moto g xt1032) dpi via adb command. But unless o type 260 i type 560 in command.
adb shell wm density 560 && adb reboot.
The device boot ok, but now i cant enter on the main screen (see attachement) and the adb dont work anymore (phone is locked).
Someone know how to reset the phone or dpi to stock in this mode ?
Regards

Done
puiatmp said:
Hey all,
I change my phone (moto g xt1032) dpi via adb command. But unless o type 260 i type 560 in command.
adb shell wm density 560 && adb reboot.
The device boot ok, but now i cant enter on the main screen (see attachement) and the adb dont work anymore (phone is locked).
Someone know how to reset the phone or dpi to stock in this mode ?
Regards
Click to expand...
Click to collapse
Hey, i found how to resolve my problem.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/99825/p/30,6720,9151
And if someone wanna change DPI withou root, do the following:
Use ADB:
adb shell wm density “INSERT_DPI” && adb reboot
ex: adb shell wm density 260 && adb reboot
If you want to reset the DPI back to its original value, run the following command in ADB:
adb shell wm size reset && adb reboot

Related

Launcher(any) lag fix

As mentioned here and here:
adding "echo ro.HOME_APP_ADJ=1" to /data/local.prop fixes the launcher redraw lag.
Documentation:
http://code.google.com/p/sipdroid/wiki/FAQ
Due to limited memory home screen often takes several seconds to load. Luckily these phones allow root access. Issue the command "echo ro.HOME_APP_ADJ=1 >/data/local.prop" and reboot, to lock home screen in memory.
Click to expand...
Click to collapse
update:
it does seem to made a difference
Here are the commands: (batch file to do this here,post#5)
Code:
adb remount
adb pull /system/build.prop .
edit build.prop with a decent text editor and add these two lines a the end
#fix for screen redraw lag
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
Code:
adb push build.prop /system/
adb reboot
you could try
Code:
adb shell stop
adb shell setprop ro.HOME_APP_ADJ=1
adb shell start
if it works you just have to add ro.HOME_APP_ADJ=1 to build.prop.
g4rb4g3 said:
you could try
Code:
adb shell stop
adb shell setprop ro.HOME_APP_ADJ=1
adb shell start
if it works you just have to add ro.HOME_APP_ADJ=1 to build.prop.
Click to expand...
Click to collapse
tried:
Code:
adb shell stop
adb shell setprop ro.HOME_APP_ADJ 1
adb shell start
My phone hot rebooted after the last command.
After it rebooted I ran
Code:
C:\Users\meeee>adb shell getprop ro.HOME_APP_ADJ
4
Since its 4. I guess it did not stick.
Also tried setting it and immediately reading it, did not stick.
Code:
C:\Users\meeee>adb shell setprop ro.HOME_APP_ADJ 1
C:\Users\meeee>adb shell getprop ro.HOME_APP_ADJ
4
The setting stuck after putting it in build.prop, time to check if it made any difference...
Code:
C:\Users\meeee\Desktop>adb shell getprop ro.HOME_APP_ADJ
1
Don't reboot, try the commands and watch out if your problem got fixed. If it works like that you can add the line to build.prop.
g4rb4g3 said:
Don't reboot, try the commands and watch out if your problem got fixed. If it works like that you can add the line to build.prop.
Click to expand...
Click to collapse
It did it on its own.
seems to be working, updated op with the commands.
britoso said:
seems to be working, updated op with the commands.
Click to expand...
Click to collapse
Added this cmd to build.prop but see no changes... what lags you talking about btw?
For me my home screens were sluggish. There was a delay when I tried to switch desktops.
I made a little bat.file, which adds those 2 lines to your build.prop.
- put "Launcher_lag_fix.bat" in ..Android/tools/
- doubleklick
- and wait till reboot.
rori~ said:
I made a little bat.file, which adds those 2 lines to your build.prop.
- put "Launcher_lag_fix.bat" in ..Android/tools/
- doubleklick
- and wait till reboot.
Click to expand...
Click to collapse
thanks rori.
No one has posted yet what the command actually does. All it does is tell Android to try to keep the launcher in memory.
Shouldn't affect anything like the scrolling or any response while actually using the launcher, but will fix some lag for when going back home from any other app, as it doesn't have to re-launch the launcher if it was kicked out of memory.
Various options like this exist in some launchers, and I think Cyanogenmod has this option in the settings too. They are not all the same as this command though, so this may work better for some people while the other ways to do it may work better for others.
Clarkster said:
No one has posted yet what the command actually does. All it does is tell Android to try to keep the launcher in memory.
Click to expand...
Click to collapse
As per this it locks the 'screen' in memory. (maybe they mean the screen buffer)
Due to limited memory home screen often takes several seconds to load. Luckily these phones allow root access. Issue the command "echo ro.HOME_APP_ADJ=1 >/data/local.prop" and reboot, to lock home screen in memory.
Click to expand...
Click to collapse
Makes sense as I always have had launcher locked in memory before this and was still having my home screen redraw very slowly when I switched to it.
A good find
Btw just for info there were issues in apps from pre release system dump of arc
However if u r using apps from the retail dump 'they don't lag'
Sent from my U20i using XDA App
rori~ said:
I made a little bat.file, which adds those 2 lines to your build.prop.
- put "Launcher_lag_fix.bat" in ..Android/tools/
- doubleklick
- and wait till reboot.
Click to expand...
Click to collapse
can you specify where is the android/tools mentioned, can it be found in all android phones?
Btw, I have seen ">>" and ">" then "space" /data/local.prop in other websites, while in the sipdroid article, it is exactly
"echo ro.HOME_APP_ADJ=1 >/data/local.prop".
otivaeey said:
can you specify where is the android/tools mentioned, can it be found in all android phones?
Btw, I have seen ">>" and ">" then "space" /data/local.prop in other websites, while in the sipdroid article, it is exactly
"echo ro.HOME_APP_ADJ=1 >/data/local.prop".
Click to expand...
Click to collapse
adb comes with the sdk, for my windows machine its at
C:\android-sdk-windows\platform-tools
in unix ">" sends text to a file (deletes whatever was there) and ">>" appends at the end of a file. If you're not familiar its easiest to just add the one line manually at the end of build.prop.
Hey y'all, wondering if anybody can help me with this:
I'm at work and don't have access to ADB. Can I use Root Explorer to copy the file to the sdcard, mount the card on a PC, edit it, and then use Root Explorer to copy it back again? Or will that cause issues with permissions or something?
EDIT: Well it's intellectual now, I nandroided back to my previous ROM due to some other issues. I'd still like to know though.
Ya the root explorer thing should work but just to be safe I would nandroid first cause worst case scenario your phone freezes you pull battery boot into recovery restore nandroid. But seriously I don't think it will be a problem.
Just out of curiosity I wanted to see if I could do this without a computer at all and turns out all you really need to do is download estrong (or any other root explorer), turn root explorer option on, mount /system and go and edit build.prop through the the built in note editor in estrong. So that might be an alternate solution for you kippswanson.

[Q&A] Android M Developer Preview / Images & Flashables

Q&A for Android M Developer Preview / Images & Flashables
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Android M Developer Preview / Images & Flashables. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Anyone try it with project fi
Sent from my Nexus 6 using XDA Free mobile app
I am currently downloading.... I am on verizon. i wonder how much is going to break.
We need non encryptable boot.img so the boot.img should be modified right ?
Anyone else microphone broken in M? Doesn't work at all throughout the OS for me
It seems to be when you set up hotword detection. That doesn't work, once you try it borks the mic until you restart.
Are Android M Dev Preview Updates OTA?
So I've installed the Android M Developer Preview on my Nexus 5 and I wanted to know whether the updates Google rolls out for it (not official M but incremental bug fixes e.t.c) will these small updates be OTA or will I have to manually flash them? Was it the same with L developer preview.
im trying to flash it, but when i run the flash all bat i get missing boot.sig and so on. everything is extracted... i guess i jumped the gun a little
boot animation?
Flashed few mins ago. Still hanging google logo. Is it normal? Where is boot animation?
---------- Post added at 09:30 PM ---------- Previous post was at 09:22 PM ----------
Flashed few mins ago. Still hanging google logo. Is it normal? Where is boot animation?
Change DPI on Android M
To change DPI and not bugs like stretch contacts photos and google play big icons (by method wm density) try this:
1. boot to recovery
2. mount /system
3. go to command line
HTML:
adb pull /system/build.prop
4. change line ro.sf.lcd_density=xxx (xxx means dpi, on N5 i like 400)
5. save this file
6. go to command line
HTML:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
Use Wug's to Flash....
You can use Wug's Nexus Toolkit for this... do the following:
1. Download and Install Wug's
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
2. Unlock BootLoader if you haven't using the toolkit
3. Once Unlocked, Use the toolkit to FLASH STOCK with Normal Conditions....
4. Dialogue Box should come up that will allow to browse to an image file on your computer... make sure to download the Android M Preview directly from Google...
https://developer.android.com/preview/download.html
Don't leave the download page for the preview as you'll need to cut and paste the MD5 Check Hash from the preview page into Wug's
5. Using Browse.... select the download .tgz on your computer
6. Copy & Paste MD5 Hash
7. Wug's will pretty much do the rest for you with zero issues.... I like to put it into ADB bootloader mode myself before I begin the flash since its really simple to do......
Keep in mind that unlocking the bootloader and / or flashing the preview will completely wipe your phone... so make sure to backup anything important..... :good:
Hope this helps those having booting and loading problems....
FOR DPI..... and / or screen re-sizing
It is much simpler and less evasive (won't cause bootlooping) by just doing the following ADB command:
adb shell wm size hhhh x vvvv
where hhhh is your horizontal resolution and vvvv is your vertical.... takes some trial and error to get something that works.... but it does not manipulate dpi which may cause bootlooping
Hope this helps too :laugh:
Interesting, I never flashed the stock boot.img, but I get the verification error on boot up. I was curious why everyone was concerned about it though cause it doesn't really impact anything does it? (flashed the noencryption-boot.img).
FYI for Verizon Users, there was a tip in here about enabling Multi-window, well I didn't know you can ADB in TWRP, so while changing the build.prop you can also enable the hotspot tether. Works.
*My posts still get sent to q&a threads. As well as my post count never seems to go up. Love it.
daledenton said:
Anyone else microphone broken in M? Doesn't work at all throughout the OS for me
It seems to be when you set up hotword detection. That doesn't work, once you try it borks the mic until you restart.
Click to expand...
Click to collapse
Yes, I'm having the same problem.
mahst68 said:
You can use Wug's Nexus Toolkit for this... do the following:
1. Download and Install Wug's
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
2. Unlock BootLoader if you haven't using the toolkit
3. Once Unlocked, Use the toolkit to FLASH STOCK with Normal Conditions....
4. Dialogue Box should come up that will allow to browse to an image file on your computer... make sure to download the Android M Preview directly from Google...
https://developer.android.com/preview/download.html
Don't leave the download page for the preview as you'll need to cut and paste the MD5 Check Hash from the preview page into Wug's
5. Using Browse.... select the download .tgz on your computer
6. Copy & Paste MD5 Hash
7. Wug's will pretty much do the rest for you with zero issues.... I like to put it into ADB bootloader mode myself before I begin the flash since its really simple to do......
Keep in mind that unlocking the bootloader and / or flashing the preview will completely wipe your phone... so make sure to backup anything important..... :good:
Hope this helps those having booting and loading problems....
FOR DPI..... and / or screen re-sizing
It is much simpler and less evasive (won't cause bootlooping) by just doing the following ADB command:
adb shell wm size hhhh x vvvv
where hhhh is your horizontal resolution and vvvv is your vertical.... takes some trial and error to get something that works.... but it does not manipulate dpi which may cause bootlooping
Hope this helps too :laugh:
Click to expand...
Click to collapse
adb shell wm method break some images thumbnials and icons (for example hangouts, contacts and play store). Better method i wrote up to your post...
Android M on other devices than Nexus
Hey Guys, i wondered if I can install Android M on my OPO (using Multirom) or if this is not possible because it's only for Nexus 5,6,9 & Player? Thanks for the answer
Dragobourd said:
Hey Guys, i wondered if I can install Android M on my OPO (using Multirom) or if this is not possible because it's only for Nexus 5,6,9 & Player? Thanks for the answer
Click to expand...
Click to collapse
No you cannot.
Rooting Android M
I realized that the device verification message pops up if we flash the perm_recovery_signed.zip file. Is there anyway to get around this?
sakacjakub said:
To change DPI and not bugs like stretch contacts photos and google play big icons (by method wm density) try this:
1. boot to recovery
2. mount /system
3. go to command line
HTML:
adb pull /system/build.prop
4. change line ro.sf.lcd_density=xxx (xxx means dpi, on N5 i like 400)
5. save this file
6. go to command line
HTML:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
Click to expand...
Click to collapse
Is there any benefit using this instead of:
Code:
adb wm density 480
adb reboot
?
Gingerbread1611 said:
Is there any benefit using this instead of:
Code:
adb wm density 480
adb reboot
?
Click to expand...
Click to collapse
Yes... I had graphical glitches with adb wm density method (400 dpi). Contact picture thumbnails are messed up, also in WhatsApp, Hangouts has very big profile photo and Play Store has very big icons (best developer)...
sakacjakub said:
Yes... I had graphical glitches with adb wm density method (400 dpi). Contact picture thumbnails are messed up, also in WhatsApp, Hangouts has very big profile photo and Play Store has very big icons (best developer)...
Click to expand...
Click to collapse
Damn, just checked the playstore and i also have those big icons. I'll try your method now, thank you.
/edit: I just saw you actually answered it in the post i quoted... Im sorry, didn't see that.
Don't know if anyone already answered but at the I/O announcement and on the website they've said they plan to roll out OTAs as new M Previews are made available. On the graphic there seems to be at least 2, 3 more.

[TUTORIAL] How to enable MULTIWINDOW and change Density on M Developer Preview

As we don't have root yet on the M preview, here is quick tutorial how to enable Muiltiwindow and change density.
You will need TWRP and Total Commander with adb plugin.
1. Boot the TWRP
2. Go to Mount and check the system checkbox
3. Plug the device to PC
4. In Total Commander go to network/adb/your device/system and find build.prop
{
"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"
}
5. Copy the file to some safe place for backup
6. Open the file in editor (F4)
7. Change the line
Code:
ro.build.type=user
with
Code:
ro.build.type=userdebug
8. You can also change the density in the line
Code:
ro.sf.lcd_density=480
I prefer 420.
9. Save the file and copy it back (if you change it on PC).
10. Done
Just FYI, there is a much more simple way to change the DPI without root. You just need a single ADB command.
With the phone powered on, just open up a window in terminal (OSX) or command prompt (Windows) like you would to perform fastboot or ADB commands, and type the following:
adb shell wm density DPI && adb reboot
Just replace "DPI" with the desired DPI. So if you want a 420 DPI, this will be your command:
adb shell wm density 420 && adb reboot
Then just hit enter, the phone will reboot, and voila! enjoy your new DPI.
how to flash twrp on M !!
bicho19 said:
how to flash twrp on M !!
Click to expand...
Click to collapse
fastboot flash recovery
rivera618 said:
fastboot flash recovery
Click to expand...
Click to collapse
i know, but can you provide me with the img file that work with Android M
bicho19 said:
i know, but can you provide me with the img file that work with Android M
Click to expand...
Click to collapse
It is the same as for Lollipop
Man, I can confirm that this tutorial works perfectly, thank you!
Have you understood how to use multiwindows?
In my case, I can't understand which is the second app he shows on the screen. I can chose one from recent menù, but the second seems to be chosen randomly!
Maybe I'm just tired
Will it cause missing applications from PlayStore as it did every time I changed DPI?
To check, try to download 'Tinder'. Or go to the Store webpage from a computer and try to find an App that it's incompatible with your Nexus 5 (And it shouldn't)
bregan90 said:
Will it cause missing applications from PlayStore as it did every time I changed DPI?
To check, try to download 'Tinder'. Or go to the Store webpage from a computer and try to find an App that it's incompatible with your Nexus 5 (And it shouldn't)
Click to expand...
Click to collapse
Tinder installs/opens fine with DPI set to 420 (just tested it). I used the adb commands to change DPI, worked perfectly.
Own a mac, cant seem to get adb to work properly.
swirly05 said:
Own a mac, cant seem to get adb to work properly.
Click to expand...
Click to collapse
./abd "commands go here"
Don't forget the ./
ape96 said:
Man, I can confirm that this tutorial works perfectly, thank you!
Have you understood how to use multiwindows?
In my case, I can't understand which is the second app he shows on the screen. I can chose one from recent menù, but the second seems to be chosen randomly!
Maybe I'm just tired
Click to expand...
Click to collapse
From the resent menu you can set the top and bottom windows.
When u then in some time launch one of them, it is still will be on top or bottom, but another one will be the last used, but it will not be scrollable some or them, or not always. Still a little buggy, . As the new "half frame" app will be on top.
But if you run both apps from resents that you made top and bottom, then they will both scroll.
The new photo app shows some display bugs with density set to 420
neFAST said:
The new photo app shows some display bugs with density set to 420
Click to expand...
Click to collapse
Dunno. Seem to be working fine for me...
What are those bugs? Try to change to 400 or smth else.
playahate said:
From the resent menu you can set the top and bottom windows.
When u then in some time launch one of them, it is still will be on top or bottom, but another one will be the last used, but it will not be scrollable some or them, or not always. Still a little buggy, . As the new "half frame" app will be on top.
But if you run both apps from resents that you made top and bottom, then they will both scroll.
Click to expand...
Click to collapse
I start to understand! It's a big buggy, but it seems that it will improve a lot
It's a useful function, though
ape96 said:
I start to understand! It's a big buggy, but it seems that it will improve a lot
It's a useful function, though
Click to expand...
Click to collapse
Yap. I like it too.
Added the pic to 1st post. Watching YouTube and browsing the same time...
I changed DPI to 420 but there is no option to enable multiwindow?
how do I fix?
swirly05 said:
Own a mac, cant seem to get adb to work properly.
Click to expand...
Click to collapse
You might need to install the latest ABD and Fastboot, compatible with M Preview: https://github.com/simmac/minimal_adb_fastboot/tree/preview
razor17 said:
I changed DPI to 420 but there is no option to enable multiwindow?
how do I fix?
Click to expand...
Click to collapse
I flashed a zip file posted by another user to enable multi window. Then did the adb command from this thread and its all working here.
Edit: here's the post I got the zip from. Flashed it and enabled multi window. Then I adb command DPI to 420. Working for me. Hope this helps
http://forum.xda-developers.com/showthread.php?p=61061093
height soft key
sn0warmy said:
Just FYI, there is a much more simple way to change the DPI without root. You just need a single ADB command.
With the phone powered on, just open up a window in terminal (OSX) or command prompt (Windows) like you would to perform fastboot or ADB commands, and type the following:
adb shell wm density DPI && adb reboot
Just replace "DPI" with the desired DPI. So if you want a 420 DPI, this will be your command:
adb shell wm density 420 && adb reboot
Then just hit enter, the phone will reboot, and voila! enjoy your new DPI.
Click to expand...
Click to collapse
it's a way to change height navigation bar / soft key ?

Changing the DPI/"display size" on the stock global rom without root

tldr; the stock global MIUI rom lacks a display size setting, but an awesome free option by zacharee1 lets you set it anyway, even without root, and with no need to reboot or anything:
https://labs.xda-developers.com/store/app/com.zacharee1.dpichanger
----
I love the Max 2 -- way more than I thought I would! I bought it as a replacement for my old, sadly dead Nexus 7 tablet, but if it had LTE bands for US T-Mobile, this might have been my next phone. But for all that, MIUI made some "customization" decisions to android that I just don't understand... like two finger drag for expanding a notification... and removing the "Display Size" setting.
On other Android N roms, you can easily adjust the zoom/DPI/display size, making things smaller or larger. The stock global MIUI version on the Max 2, however, is missing the setting (and the "Smallest width" setting in developer options.) I thought I was out of luck after trying an option from the play store that failed, but found an app in XDA Labs from zacharee1 that worked!
It did require enabling adb, and developer options; in addition steps, I had to go to developer options and enable "USB debugging (security settings)" with a sim card inserted. Normally I used the Max 2 without one, but if you don't have a sim card inserted it will tell you to insert one, then fail.
Anyway, if anyone else would like to fit a bit more content on the screen, I'm really happy with this app so far! Some of Xiaomi's own apps don't quite scale well, which is probably why they disabled it, but they just have extra padding around the content. They still work just fine.
Awesome!
Sorry, noob here. When I run the command it tells me "error : no devices/emulators found"
I have turned on both USB debugging options in developer options and am using Minimal ADB and Fastboot. No Root.
Any help would be greatly appreciated!
Worked well!
Just chiming in and letting you guys know that the app package is zacharee1 (one), not zachareel (L). Gave me some problems for a bit!
user4001 said:
I have turned on both USB debugging options in developer options and am using Minimal ADB and Fastboot. No Root.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Oh, sorry. I've never used minimal adb before -- have you tried running the adb command as an administrator? (You might have to run "adb kill-server" first, it will used an existing adb server with fewer privileges if it exists.)
whd5015 said:
Worked well!
Just chiming in and letting you guys know that the app package is zacharee1 (one), not zachareel (L). Gave me some problems for a bit!
Click to expand...
Click to collapse
Nice! That's a good tip, too, thanks. (I've wasted hours before figuring out a capital O wasn't a 0 before...)
ldrn said:
Oh, sorry. I've never used minimal adb before -- have you tried running the adb command as an administrator? (You might have to run "adb kill-server" first, it will used an existing adb server with fewer privileges if it exists.)
Nice! That's a good tip, too, thanks. (I've wasted hours before figuring out a capital O wasn't a 0 before...)
Click to expand...
Click to collapse
I'll try the administrator thing, thanks. I have no idea what
what ADB kill server is but will Google when I get home.
I tried it without root. I using adb in administrator mode, but it gives me an error:
C:\adb>adb shell pm grant com.zacharee1.dpichanger android.permission.WRITE_SECURE_SETTINGS
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
Any suggestions?
ruairi said:
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
Click to expand...
Click to collapse
Actually, yep! In developer options, there is a "USB debugging" toggle, then three lines down a "USB Debugging (Security settings)" toggle, that's the error you get when you have the first one toggled but not the second. You need both turned on.
(I'm speaking from personal experience, I made that same mistake at first; it's a bit confusing that the names are almost the same!)
thanks @ldrn, I'll give it a shot.
Works like Charm. I have set the DPI to 410 Thanks!
adb shell wm density XXX
i use "adb shell wm density 420"
display will refresh every time i change dpi. no sestart require
Is this safe for MIUI rom?
w4h1d said:
Is this safe for MIUI rom?
Click to expand...
Click to collapse
Yes it is safe tested in MIUI Global 8.5 | Stable
make sure USB debugging (Security settings) is enabled in developer options
The link is dead. Where can I download the app?
inunt said:
i use "adb shell wm density 420"
display will refresh every time i change dpi. no sestart require
Click to expand...
Click to collapse
So do I have to write this command on my computer? No app needed? If app from first post is needed, where can i find it?
Link is not working. Please new link? Thank you.
Link dont work
Can some one tell me what is the stock value of DPI
reversegear said:
Can some one tell me what is the stock value of DPI
Click to expand...
Click to collapse
stock value of dpi is 440
Link does not exist
The link to above app says that the file does not exist on the server. Can anyone please give me the valid link for it?

nokia 7 plus screen size and density

hello
i have nokia 7 plus
i am try in some adb commant to check phone bootloader unlock
but i unfortunately run this two both comand
// Emulate device
adb shell wm size 2048x1536
adb shell wm density 288
// And reset to default
adb shell wm size reset
adb shell wm density reset
when i am try to rest it will be done but when i will reboot device again screen size & density will change and it become smaller (only half screen will be useable )
so plz help me to out this problem
every time i need to run reset command from pc then it will go to normal state...
thanx

Categories

Resources