so dpi setting is not avail in developer settings. Going into display and setting to small would probably be around 411 dpi. i usually with a qhd set mind to around 450-480. have anyone been able to change dpi with ADB? IF so how.
This is the command...adb shell wm density (what ever size you want, minus the parenthesis) && adb reboot
I haven't tried it on the V30 yet because I just assumed it wouldn't work. It didn't work on the G6 if remember correctly. It won't hurt anything if you try it and it doesn't work. It just won't change anything.
Only thing is, you may not be able to use Android pay.
lyall29 said:
This is the command...adb shell wm density (what ever size you want, minus the parenthesis) && adb reboot
I haven't tried it on the V30 yet because I just assumed it wouldn't work. It didn't work on the G6 if remember correctly. It won't hurt anything if you try it and it doesn't work. It just won't change anything.
Only thing is, you may not be able to use Android pay.
Click to expand...
Click to collapse
adb has be done on a pc only? or can be also done in terminal emulator without root?
lyall29 said:
This is the command...adb shell wm density (what ever size you want, minus the parenthesis) && adb reboot
I haven't tried it on the V30 yet because I just assumed it wouldn't work. It didn't work on the G6 if remember correctly. It won't hurt anything if you try it and it doesn't work. It just won't change anything.
Only thing is, you may not be able to use Android pay.
Click to expand...
Click to collapse
That may not work, as
most all the ADB commands, at least the flash commands, have been removed on the carrier-branded models.
Only the official carrier unlocked versions have full ADB commands.
If you find different information, please share.
eduardmc said:
adb has be done on a pc only? or can be also done in terminal emulator without root?
Click to expand...
Click to collapse
I don't know
You can change it in settings, under display.
Sent from my LG-H931 using Tapatalk
bricky23 said:
You can change it in settings, under display.
Sent from my LG-H931 using Tapatalk
Click to expand...
Click to collapse
i guess u didnt read my post
eduardmc said:
i guess u didnt read my post
Click to expand...
Click to collapse
I guess your right. One thing that I did notice however. After changing the size to small in settings, I have some lag in places where there was none before. Anyone else notice this?
Sent from my LG-H931 using Tapatalk
bricky23 said:
I guess your right. One thing that I did notice however. After changing the size to small in settings, I have some lag in places where there was none before. Anyone else notice this?
Sent from my LG-H931 using Tapatalk
Click to expand...
Click to collapse
really? mmm would try that out now and see if it does make a different
Related
Let's start a list of build.prop modifications that work!
net.tethering.noprovisioning=true
Enabled tethering
persist.debug.wfd.enable=1
Enables miracast. Go into cast settings and enable wireless display
Change persist.audio.fluence.voicecall to false
Disable noise cancellation
This is all I have found so far. What other mods are you using?
User contributions:
enable multi window
ro.build.type=userdebug
lock screen auto rotate
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
Disable the nav bar
qemu.hw.mainkeys=1
ro.build.type=userdebug
That will allow you to enable multi-window.
I'm guessing these changes will break Android pay?
Sent from my Nexus 6P using Tapatalk
will.bates94 said:
I'm guessing these changes will break Android pay?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I would like to know the same. I want to enable miracast but not break android pay
will.bates94 said:
I'm guessing these changes will break Android pay?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I think it would be best practice to assume that any mods to the sys folder, including modifying build.prop, will cause the SafetyNet tests to fail, therefore causing Android Pay and all other apps that use that API to stop working. That being said, I THINK some mods to the build.prop have gone undetected. Also, reverting any changes should restore full functionality.
I enabled miricast. It doesn't work with every app, but maybe that's due to a root check or something...
SomeGuy4 said:
net.tethering.noprovisioning=true
Enabled tethering
Click to expand...
Click to collapse
I heard a rumor that the native tether works out of the box, so the build.prop mod may not be necessary....? I am able to turn it on, but i didn't try connecting to it with another device yet, so I can't verify.
I'd love to know more build.prop mods, too!
AranelAlasse said:
I enabled miricast. It doesn't work with every app, but maybe that's due to a root check or something...
I heard a rumor that the native tether works out of the box, so the build.prop mod may not be necessary....? I am able to turn it on, but i didn't try connecting to it with another device yet, so I can't verify.
I'd love to know more build.prop mods, too!
Click to expand...
Click to collapse
I have the tethering build.prop edit and I am able to add a card to Android Pay. I have not been able to test it at a retailer yet.
As far as native tethering goes, that will depend on your carrier. I have Cricket who actively started blocking it a while ago so they can charge a $10 fee to turn it on. Prior to that it worked fine natively.
iamyourdemize said:
As far as native tethering goes, that will depend on your carrier. I have Cricket who actively started blocking it a while ago so they can charge a $10 fee to turn it on. Prior to that it worked fine natively.
Click to expand...
Click to collapse
Interesting. I have Verizon, and still on the unlimited data plan... Hotspot worked great for me last night for several hours using the native toggle (without a build.prop edit). I'll be curious and wary for a while, though, to see if something on my bill changes...
Android pay works for me after the tweaks. I actually temp booted TWRP to add these two lines into the build.prop therefore root not needed at all to accomplish this.
sarcoptic said:
I actually temp booted TWRP to add these two lines into the build.prop
Click to expand...
Click to collapse
I tried to modify build.prop in TWRP, but couldn't figure out how... What steps do you use to do that?
AranelAlasse said:
I tried to modify build.prop in TWRP, but couldn't figure out how... What steps do you use to do that?
Click to expand...
Click to collapse
1. Boot twrp
fastboot boot recovery.img
2. Go to Mounts and mount the system partition, by default mine was not checked
3. Pull build.prop
adb pull /system/build.prop
4. Edit build.prop
net.tethering.noprovisioning=true
persist.debug.wfd.enable=1
5. Push build.prop
adb push build.prop /system/build.prop
6. Set permissions
adb shell
chmod 644 /system/build.prop
7. Reboot and profit
sarcoptic said:
1. Boot twrp
fastboot boot recovery.img
2. Go to Mounts and mount the system partition, by default mine was not checked
3. Pull build.prop
adb pull /system/build.prop
4. Edit build.prop
net.tethering.noprovisioning=true
persist.debug.wfd.enable=1
5. Push build.prop
adb push build.prop /system/build.prop
6. Set permissions
adb shell
chmod 644 /system/build.prop
7. Reboot and profit
Click to expand...
Click to collapse
Aah, I see. Yes, I read about doing it that way, but I didn't have my computer cord handy and couldn't use adb or fastboot. I was trying to use the terminal inside of TWRP. vi just gave endless output... and I saw that ed is on there somewhere, but didn't know how to use it... plus i don't know if those editors are usable from TWRP command line or if they're only there for the system's use. It's been too long since I've been in the linux world (sad. ), so I didn't try very hard.
---------- Post added at 12:34 PM ---------- Previous post was at 12:31 PM ----------
on a different note, I think the (experimental) multi-window feature can be enabled via build.props, but I don't recall the details.
I edited my build.prop to turn off noise cancellation (change value to false)
Afterwords, safetynet still passes (using safetynet helper app).
luigidk said:
I edited my build.prop to turn off noise cancellation (change value to false)
Afterwords, safetynet still passes (using safetynet helper app).
Click to expand...
Click to collapse
what is the benefit of turning off noise cancellation?
Sent from my Nexus 6P using Tapatalk
slaydog said:
what is the benefit of turning off noise cancellation?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
so people can hear you better (most of us get "we can't hear you" though we're shouting) (that's what i understood from the post)
slaydog said:
what is the benefit of turning off noise cancellation?
Click to expand...
Click to collapse
Some say it makes a difference in call quality, some not. Worth a shot if you have issues.
RockyAJ said:
so people can hear you better (most of us get "we can't hear you" though we're shouting) (that's what i understood from the post)
Click to expand...
Click to collapse
jejb said:
Some say it makes a difference in call quality, some not. Worth a shot if you have issues.
Click to expand...
Click to collapse
Thanks for the heads up, guys!
Sent from my Nexus 6P using Tapatalk
AranelAlasse said:
I tried to modify build.prop in TWRP, but couldn't figure out how... What steps do you use to do that?
Click to expand...
Click to collapse
Why not just use a root explorer and go to the system folder. Remember to reboot for changes to take effect.
Sent from my Nexus 6P using Tapatalk
SomeGuy4 said:
Why not just use a root explorer and go to the system folder. Remember to reboot for changes to take effect.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just wanted to do it without an app, that's all. I didn't feel like cluttering up my phone just yet. In the end, I gave up anyways and just use an app after all. But I would still love to know if there's a way to edit text files inside of TWRP...
Pull the build prop thru adb then modify it and push it back .. No app needed
I switched my DPI and like an idiot I didn't make a backup in titanium backup like I should have. I don't have ADB set up but USB debugging is ON and I have LGUP and LG Bridge installed . What should I do to even reflash the phone with stock?
I ended up having to re-root it with the TOT in upgrade mode, which over-wrote everything. Unfortunately, there doesn't seem to be a way to flash single files, and I could never figure out how to remount /system as RW, to edit build.prop by hand and push a fixed copy
Anyone found a way to safely edit the DPI yet?
Sent from my VS990 using XDA-Developers mobile app
christiebunny said:
Anyone found a way to safely edit the DPI yet?
Sent from my VS990 using XDA-Developers mobile app
Click to expand...
Click to collapse
There's a T-Mobile thread about this. For starters you can edit freely but unfortunately systemui and the second screen (can't recall app name) will have to remain stock. There is an app that does this for you, unfortunately can't recall the name either but take a look in other V10 sections.
I know about Xposed's "per app hacking" app, but Xposed still isn't working with the VZW V10, last I knew?
Ephemera said:
There's a T-Mobile thread about this. For starters you can edit freely but unfortunately systemui and the second screen (can't recall app name) will have to remain stock. There is an app that does this for you, unfortunately can't recall the name either but take a look in other V10 sections.
Click to expand...
Click to collapse
Found a working res/dpi, without using Xposed's 'per app hacking'. (I thought Xposed wouldn't run on this!)
'Resolution changer' from the market, set to [email protected]; works fantastic with everything!
With one tiny problem... the touchscreen is much less responsive, and the right edge becomes almost nonresponsive totally unless I do a sort of slide-tap when I tap something.
Anyone know how to resize the digitizer grid and/or edit the sensltivity? :/
christiebunny said:
I know about Xposed's "per app hacking" app, but Xposed still isn't working with the VZW V10, last I knew?
Click to expand...
Click to collapse
Have you tried the modified Xposed set to work with odexed ROMs?
Just got the G5 to move back from iPhone to android. Hate iPhone! But it's silly that my iPhone 6S can fit more content on the screen and it is a highly inferior screen than the G5...
Is there any easy way to change DPI without being root? What's the recommended DPI for this screen without breaking apps like camera?
Ideally would like to root and install app settings & xposed but not sure if my model can be rooted yet. It's the international model bought from EE in the UK.
How do I check for locked bootloader?
Rockin my G5
Hello, I know i'm late but I just got my G5 today and was looking for information much like you were but didn't find any so i experimented. to note, i do have the t-mobile variant so obviously if you have a different version of the phone your results could be different. I haven't tried any DPI's lower than 560 but that being said 560 seems to be perfectly stable and was easily changed through adb! and WOW does it make a difference on this device! for me at least, 560 seems to be the sweet spot! Really, i don't understand why OEM's don't set their DPI's to reasonable settings in the first place.. i mean, we have quad-hd displays for androids sake, LET US USE THEM.. anyways, rant aside:
You'll want to install ADB and the LG drivers obviously but once that's setup go to your phone, enable developer options and enable USB debugging and OEM unlock (the latter may not be necessary but my device wasn't being recognized initially so i enabled it. Also, for some reason i'm finding with this phone that it doesn't want to be recognized in MTP (file transfer) mode but seems to work fine in "camera mode".
first, type "adb devices" to make sure that the device is being recognized.
once your device is being recognized by adb (it may say unauthorized, ignore this) simply type the following command.
"adb shell wm density 560 && adb reboot"
or you can obviously change out the number to whatever DPI you want, but the lower you go the higher the chance that things like the camera will stop working properly. So far i have not had any issues at all with any system apps, the camera seems to have scaled perfectly as it should and this is generally the app that breaks for me. if i find any apps or anything not working i'll update my post here, but so far so good!
I hope this helps you out! If you have any further questions let me know!!
(little update, first and ONLY thing i've had issues with is the "always on display" doesn't seem to show time correctly.. oh well!! its a very fair trade and since the always on display can be shut off in settings its not even an eyesore. )
Hey bud,
Tried setting it to 560 using this method, think its probably a tiny bit too small, would probably prefer maybe in the middle between 640 (stock) and 560. I noticed that on 560 swiftkey didnt work properly (cant live without swiftkey!!) and as you said, the always on display showing time - signature works fine though.
Have reverted it for now, maybe yourself or someone will find a perfect number which gives minimal issues with apps. Otherwise, might just wait on root to edit the build.prop instead.
mcall_r said:
Hey bud,
Tried setting it to 560 using this method, think its probably a tiny bit too small, would probably prefer maybe in the middle between 640 (stock) and 560. I noticed that on 560 swiftkey didnt work properly (cant live without swiftkey!!) and as you said, the always on display showing time - signature works fine though.
Have reverted it for now, maybe yourself or someone will find a perfect number which gives minimal issues with apps. Otherwise, might just wait on root to edit the build.prop instead.
Click to expand...
Click to collapse
so try a different DPI? just replace 560 in the command with whatever you want to and see how it looks. only takes a couple minutes to do. also, if you like swiftkey.. you should really try Swype. much better keyboard and it scales perfectly with and dpi i've ever tried on any phone.
Anyone seen the drivers for the LG G5 or or alternative that will work?
anothervictim. said:
Anyone seen the drivers for the LG G5 or or alternative that will work?
Click to expand...
Click to collapse
ya know, i owned the lg v10 before this phone and never updated my drivers. works just fine. does lg not have drivers posted for the g5??
ngoblirsch said:
ya know, i owned the lg v10 before this phone and never updated my drivers. works just fine. does lg not have drivers posted for the g5??
Click to expand...
Click to collapse
I didn't see it listed. I'll check out the v10. I imagine it's the same. Thanks!
ngoblirsch said:
ya know, i owned the lg v10 before this phone and never updated my drivers. works just fine. does lg not have drivers posted for the g5??
Click to expand...
Click to collapse
You need to search for the LG H850 on LG's website. H850 is the actual model number. But as other comments suggest, the drivers for the V10 will probably work fine.
Any working dpi's without bootloops? I don't use always on Display
Sent from my LG-H850 using XDA Labs
I've got my dpi set to 540, anything lower causes stability issues.
Ixstala said:
I've got my dpi set to 540, anything lower causes stability issues.
Click to expand...
Click to collapse
Thanks, 540 is working very well. I like it
Sent from my LG-H850 using XDA Labs
Lycidias said:
Thanks, 540 is working very well. I like it.
Click to expand...
Click to collapse
Are there any issues with any of the apps at 540 DPI? Any chance you could post a picture of the settings screen or something with the DPI at 540?
xPhantom said:
Are there any issues with any of the apps at 540 DPI? Any chance you could post a picture of the settings screen or something with the DPI at 540?
Click to expand...
Click to collapse
No issues, everything is working fine
Sent from my LG-H850 using XDA Labs
Lycidias said:
No issues, everything is working fine
Click to expand...
Click to collapse
Thank you! That looks awesome. I'm going to do this now.
Edit: SwiftKey does not seem to like the new DPI... keyboard is all messed up looking, haha.
I'm using 600 on mine, everything seems fine.
Is this a code that can be used on any phone? Could I use this on my Xperia Z5?????
I'm using 560 as someone suggested, and LastPass doesnt scale properly and PlaySTore, the blue top dev icon is too large, otherwise no problems at all.
I tried this with 540. Here's the list of things that weren't working right:
Uber | sprites like cars and pins were tiiiiiiiiiiny or squished. Still useable but not pretty.
Anything that required photo cropping or editing (Instagram, Bumble, etc) the photos were multiples larger than they should be | For instance, in instagram, you'd share a photo to it and it'd show up in the initial cropping window as huuuuuge and unscalable, but if you hit next it'd be normal size. So you just had to use guesswork to position the photo.
Swiftkey keyboard | As reported, also displayed HUGE, even though it responded to key presses in the right places.
Starbucks | Also seeing the "dots" on the map that show locations as super tiny. Not a big deal here.
In general, it seems anything that overlays graphical elements or that brings up photos for editing is at risk. I miss how this worked on my G4, but I guess that's because I did it via root. Can't wait.
Reseted the dpi but the always on Screen and the home button are still broken.
Weird thing. I used "wm density x" too, and, well... anything different than 640 (default), and android.process.phone keeps crashing....
fonix232 said:
Weird thing. I used "wm density x" too, and, well... anything different than 640 (default), and android.process.phone keeps crashing....
Click to expand...
Click to collapse
I'm sorry to those of you having problems.. Not sure what to tell you though, I changed my dpi to 560 the day I got my phone and the one and only issue I've had so far is my always on display not working right. Every other app has worked flawlessly. For those having problems, what variant of the phone do you own? H830 here
Anyone else noticed in the developer options, the setting to change the DPI (minimum width) is just not there? Never run into an Android phone on Nougat missing this setting before. Anyone know if there's a way to adjust it or get it back?
It was missing on the G6 too. Bastards, lol.
Moostafa29 said:
It was missing on the G6 too. Bastards, lol.
Click to expand...
Click to collapse
Is there any kind of workaround? The default sizing of everything is just too big.
My G6 is my backup phone, so I haven't tried anything to remedy this. I did read that there is a way to do it through ABD commands, but I haven't tried it myself. We used to have root for US LG phones, and changing the dpi was one of the first things I'd do. Changing the dpi would break several of the LG apps, so perhaps they removed the option in order to avoid that.
I remember trying to use ADB commands when I had the AT&T LG G6, and it didn't work. I assume that the V30 won't work either, so I haven't even tried. If you want to try, Google how to change dpi with ADB command, then let us know if it works or not. :good:
I've enabled AOD and for whatever reason, it's not working. I've messed with all the settings in the section, and nothing seems to make a difference.
I did go through and disable a lot of the bloatware on the phone (per this post, though I was selective about what I disabled), and it would make sense to me that something I disabled would be the culprit, but I would expect the AOD options to not even show up in Settings if I had disabled that service.
Any ideas?
oldenglish said:
I've enabled AOD and for whatever reason, it's not working. I've messed with all the settings in the section, and nothing seems to make a difference.
I did go through and disable a lot of the bloatware on the phone (per this post, though I was selective about what I disabled), and it would make sense to me that something I disabled would be the culprit, but I would expect the AOD options to not even show up in Settings if I had disabled that service.
Any ideas?
Click to expand...
Click to collapse
Yes, ideas from that very thread. You disabled LG Setup Wizard with ADB, didn't you?
A simple search of that thread found this:
Nay Tyzon said:
Of note, when disabling LG Setup Wizard using the LG Package Disabler, the Always On Display continues to work.
Only after deleting LG Setup Wizard using the adb procedure did I encounter the problem with the non-working AOD!
Click to expand...
Click to collapse
And no, menu options won't magically disappear just because you cripple stuff that makes them work...
Many things are connected to each other. So, you'll either get lag (while the software tries to find something that's missing) or stuff just won't work.
Sent from my official open market LG US998 V30+
ChazzMatt said:
Yes, ideas from that very thread. You disabled LG Setup Wizard with ADB, didn't you?
A simple search of that thread found this:
And no, menu options won't magically disappear just because you cripple stuff that makes them work...
Many things are connected to each other. So, you'll either get lag (while the software tries to find something that's missing) or stuff just won't work.
Sent from my official open market LG US998 V30+
Click to expand...
Click to collapse
I disabled/frozen LG Setup Wizard and AOD is working fine?
Oh and if i freeze all AOD related apps it does disappear in the menue?
Sent from my LG-H930 using XDA-Developers Legacy app
Mr. Schnabel said:
I disabled/frozen LG Setup Wizard and AOD is working fine?
Oh and if i freeze all AOD related apps it does disappear in the menue?
Sent from my LG-H930 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It sometimes depends on how you froze it. Read the post I quoted.
Sent from my official carrier unlocked LG V30+ US998
Thanks, didn't catch that. I can confirm I did disable com.android.LGSetupWizard, but not sure how to go about re-installing it. Any tips? I used pm uninstall -k from a shell to remove it.
ChazzMatt said:
It sometimes depends on how you froze it. Read the post I quoted.
Sent from my official carrier unlocked LG V30+ US998
Click to expand...
Click to collapse
Ah ok i see. Using SdMaid here to freeze the apps and not ADB ...
Sent from my LG-H930 using XDA-Developers Legacy app
So can anyone help me sort out how to get the com.android.LGSetupWizard library reinstalled to fix this?
I used 'pm uninstall -k' to remove it.
Yes, do what I did and hard reset your phone. It'll all restore to stock condition.
BTW for anyone else reading, just "disabling" LG Setup Wizard does not have the same effect as removing using ADB commands -- in other words, Always On Display will continue to work. Once you "uninstall" and reboot, that function ceases to work.
Nay Tyzon said:
Yes, do what I did and hard reset your phone. It'll all restore to stock condition.
BTW for anyone else reading, just "disabling" LG Setup Wizard does not have the same effect as removing using ADB commands -- in other words, Always On Display will continue to work. Once you "uninstall" and reboot, that function ceases to work.
Click to expand...
Click to collapse
Thanks. I was hoping to avoid that, and looking to find the package installer itself to reinstall, but I guess a reset is the easiest route.