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
Related
Would downloading the .apk from an outside source provide the same results? Also, would AT&T be onto this?
I sideloaded the app because I like the Bluetooth pan tethering capability... Was able to set up a working ad-hoc network but not able to get Bluetooth tethering working.
I prefer the phone's built in wireless tethering as it's a true access point
Just delete tetheringmanager2.apk from /system/app to use the phone's built in tethering.
Sent from my SAMSUNG-SGH-I777 using xda premium
V3nomous said:
I prefer the phone's built in wireless tethering as it's a true access point
Just delete tetheringmanager2.apk from /system/app to use the phone's built in tethering.
Click to expand...
Click to collapse
+1 or if you dont want to delete the file just rename it to tetheringmanager2.ap
On cm7 wireless tethering works perfectly. I hadn't ever tried it until it recently got enabled. I tethered my captivate to it that didn't have a similar card in it just to test it out. I got really good download and upload speeds on the Cappy wifi tethered too.
Sent from My KickAss CM7 Captivate
Alright ill try removing that file, would freezing it give the same results?
Also, I dont wanna get caught by AT&T, ive heard about people getting letters, etc.
Built-in wi-fi hotspot is better becuse it is a true wi-fi AP. Wireless Tether app only gives you adhoc network that a lot of devices, like Android tablet, are not compatible with.
You get caught regardless what app you use. AT&T judge you by the amount of data you use and what's in those data. They could care less what tethering app you use.
CollegeProfesor said:
Alright ill try removing that file, would freezing it give the same results?
Also, I dont wanna get caught by AT&T, ive heard about people getting letters, etc.
Click to expand...
Click to collapse
Freezing it with TiBU is similar to removing in that it will not run, but it is still there incase you need it for something later on.
Good luck with avoiding the letter...
Don
dlwoodjr said:
Freezing it with TiBU is similar to removing in that it will not run, but it is still there incase you need it for something later on.
Good luck with avoiding the letter...
Don
Click to expand...
Click to collapse
Well if im going to run into problems with AT&T im not going to bother.
Thanks though
How do you rename it?
adb shell
cd /system/app
mv TetheringManager2.apk TatheringManager2.ap
mv: can't rename 'TheringManager2.apk': Read-only file system
Before adb shell:
Code:
adb remount
Fluffster said:
How do you rename it?
adb shell
cd /system/app
mv TetheringManager2.apk TatheringManager2.ap
mv: can't rename 'TheringManager2.apk': Read-only file system
Click to expand...
Click to collapse
Or find it with Root Explorer...long press...go down to Rename.
Sent from my SAMSUNG-SGH-I777 using XDA App
tylerdurdin said:
Or find it with Root Explorer...long press...go down to Rename.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
I don't think you read my whole message. This could not be done as it was claiming "READ ONLY" file system.
I also tried this with Root Explorer with the same results, it can not do it. I assume I need to do this from CWM or something else. If someone can help point me in the right direction as to how to do this, that would be awesome.
I did find a fix (temporary) for this using System Tuner, go under apps/system then click TetheringManager and FREEZE it, once you do that you can Wifi Tether with no problem, perm fix? Dont know.. But that is working right now.
Fluffster said:
I don't think you read my whole message. This could not be done as it was claiming "READ ONLY" file system.
I also tried this with Root Explorer with the same results, it can not do it. I assume I need to do this from CWM or something else. If someone can help point me in the right direction as to how to do this, that would be awesome.
I did find a fix (temporary) for this using System Tuner, go under apps/system then click TetheringManager and FREEZE it, once you do that you can Wifi Tether with no problem, perm fix? Dont know.. But that is working right now.
Click to expand...
Click to collapse
Adb remount
Sent from my SAMSUNG-SGH-I777 using XDA App
Fluffster said:
I don't think you read my whole message. This could not be done as it was claiming "READ ONLY" file system.
I also tried this with Root Explorer with the same results, it can not do it. I assume I need to do this from CWM or something else. If someone can help point me in the right direction as to how to do this, that would be awesome.
I did find a fix (temporary) for this using System Tuner, go under apps/system then click TetheringManager and FREEZE it, once you do that you can Wifi Tether with no problem, perm fix? Dont know.. But that is working right now.
Click to expand...
Click to collapse
In Root Explorer, when in /system/app, click the button at the top that says "Switch to R/W." Then rename it.
Entropy512 said:
Before adb shell:
Code:
adb remount
Click to expand...
Click to collapse
That did the trick.. Thanks
Since the Note 3 is new, and so far, there is only one custom Rom, I've seen the "how do I disable camera sounds" question asked a few times.
I'm sure your favorite developer will incorporate this feature, into future Roms, like they have in the past, for previous devices. This is mainly for us impatient noobs.
You must be rooted. Using a root explorer, navigate to /system/csc. Backup your feature.xml. Navigate to /system/csc/SPR/system/csc. Copy feature.xml. Navigate back to /system/csc. Paste the new file, over writing the old one. Open the new feature.xml, scroll to the camera section, and change:
<CscFeature_Camera_ShutterSoundMenu>false</
CscFeature_Camera_ShutterSoundMenu>
to:
<CscFeature_Camera_ShutterSoundMenu>true</
CscFeature_Camera_ShutterSoundMenu>
Save, exit,
Set permissions to rw-r--r--
Reboot
Note: I used 'Root Explorer'. ES File Explorer may also work.
Here is a list of potential csc parameters, gathered from other phones. I didn't create this list. I found it about a year ago, and thought it might be interesting, to play around with.
Edit: the text file came from @kkoolpatz
http://forum.xda-developers.com/showthread.php?t=2033894
I followed this exactly I'm still not getting that option to silence the shutter. Is there a detail you left out or am I just missing something? I tried twice
Sent from my SM-N900P using XDA Premium 4 mobile app
SantinoInc said:
I followed this exactly I'm still not getting that option to silence the shutter. Is there a detail you left out or am I just missing something? I tried twice
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I edited the OP, to make it clearer, and modified the method, slightly.
One other possibility. Backup your feature.xml. Navigate to /system/csc/SPR/system/csc. Copy feature.xml. Navigate back to /system/csc. Paste the new file, over writing the old one. Open the new feature.xml, and change:
<CscFeature_Camera_ShutterSoundMenu>false</
CscFeature_Camera_ShutterSoundMenu>
to:
<CscFeature_Camera_ShutterSoundMenu>true</
CscFeature_Camera_ShutterSoundMenu>
(You're changing 'false' to 'true,)
Save, exit,
Set permissions to rw-r--r--
Reboot
Very useful. Thank you.
Thanks for the clarification in the OP. I now got it to work. Problem I had before was that I did not realize that I was simply changing false to true. Super simple.
Sent from my SM-N900P using XDA Premium 4 mobile app
12MaNy said:
Very useful. Thank you.
Click to expand...
Click to collapse
I'm glad it worked for you. Thanks for the feedback.
SantinoInc said:
Thanks for the clarification in the OP. I now got it to work. Problem I had before was that I did not realize that I was simply changing false to true. Super simple.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Great! It's good to hear that the instructions where clear enough to be followed. There's a lot more that can be enabled, such as using the camera during calls. It's the same principle, just a matter of searching through the feature.xml, and flipping or changing the variables.
Something to add to the first post. Make a backup of the original in case you ever screw up.
Compusmurf said:
Something to add to the first post. Make a backup of the original in case you ever screw up.
Click to expand...
Click to collapse
Always good advice, but it's already there. Unless you're talking about a nandroid...
Must have missed it. I was going to post the same thing since that was one of the first things I did when rooted but never got around to it. Glad someone posted it for others. Always good to share info. However you should have done it in the DEV section with a [MOD] Tag. Post some of the other tweaks too. It'll disappear here in General.
Compusmurf said:
Must have missed it. I was going to post the same thing since that was one of the first things I did when rooted but never got around to it. Glad someone posted it for others. Always good to share info. However you should have done it in the DEV section with a [MOD] Tag. Post some of the other tweaks too. It'll disappear here in General.
Click to expand...
Click to collapse
Yeah, maybe so. I went back and forth in my mind, and decided that this really isn't development, so here we are in 'General'.
I had a bunch of these edits, when I had my Note 2. I'll have to dig through, and see what additional features we can enable on the Note 3. Any help is definitely appreciated.
Geez, i wonder why Sprint wont include this option by default. On the at&t Note 3, the option to silence is already baked in.
optimummind said:
Geez, i wonder why Sprint wont include this option by default. On the at&t Note 3, the option to silence is already baked in.
Click to expand...
Click to collapse
Sprint can't afford a lawsuit when some idiot takes a silent upskirt photo and someone decides to sue them for not having it make noise.
I'm on stock rooted and es explorer gives me a permission denied error when I try to overwrite features.xml from the SPR folder to system/csc, also unable to rename or edit directly from system/csc but I can copy and paste elsewhere to back up.
Tavo_7 said:
I'm on stock rooted and es explorer gives me a permission denied error when I try to overwrite features.xml from the SPR folder to system/csc, also unable to rename or edit directly from system/csc but I can copy and paste elsewhere to back up.
Click to expand...
Click to collapse
Open ES File Explorer and tap the phone menu button. A pane should open on the left side of the screen. Scroll to the bottom, and turn "Root Explorer" on. When the Super User prompt pops up, be sure to allow it.
Root explorer was already on, but I toogled on off just in case and it still fails. See screenshots
Tavo_7 said:
Root explorer was already on, but I toogled on off just in case and it still fails. See screenshots
Click to expand...
Click to collapse
I'm not sure what the problem is. ES File had some problems with root, about a year ago, but I thought they got that fixed. I use it everyday, but not the root functions. Maybe you can try going into SuperSU, selecting ES File, and tapping "forget", then go back into ES, and accept the SU prompt.
LMMT said:
I'm not sure what the problem is. ES File had some problems with root, about a year ago, but I thought they got that fixed. I use it everyday, but not the root functions. Maybe you can try going into SuperSU, selecting ES File, and tapping "forget", then go back into ES, and accept the SU prompt.
Click to expand...
Click to collapse
Still failing after forgetting, I also reinstalled both ES and SU and no good. Any other free root explorers I can test? Or can anyone else using es verify if it's working for them?
Tavo_7 said:
Still failing after forgetting, I also reinstalled both ES and SU and no good. Any other free root explorers I can test? Or can anyone else using es verify if it's working for them?
Click to expand...
Click to collapse
There are several free in the Play Store. Maybe try a few?
LMMT said:
There are several free in the Play Store. Maybe try a few?
Click to expand...
Click to collapse
I downloaded 'Root Browser' from the play store and this did the trick, ES Explorer is having root issues with the Note 3, well at least on my phone since no one else confirmed. I added the shutter menu (working) , enabled camera during calls (working), and tried to add a call button from the logs list but this didn't appear to work.
Thanks again!
Tavo_7 said:
I downloaded 'Root Browser' from the play store and this did the trick, ES Explorer is having root issues with the Note 3, well at least on my phone since no one else confirmed. I added the shutter menu (working) , enabled camera during calls (working), and tried to add a call button from the logs list but this didn't appear to work.
Thanks again!
Click to expand...
Click to collapse
Good. I'm glad you got it working.
Just wanted to post that I have installed Viper4Android and it works beautifully on my rooted S5. This app is the #1 reason I root.
This app will change the way you think about sound (seriously). Every time I demo the difference to someone by turning it on and off they immediately ask me to install it for them.
Installed using directions by @docnok63, paraphrased below for your convenience. I have only tested this app on my rooted T-mobile S5, and only with spotify (it's the only player I use). Of course you should always backup first and only you are responsible for what you do to your device.
1. Ensure you are rooted. From this point on, grant all superuser requests.
2. Download ViPER4Android FX. Get the latest version under the "Android FX" heading.
3. Extract the 4.x .apk from the zip. If you haven't already, smart-install Busybox from the play store.
4. Move the 4.x .apk to root system/app using a root-friendly file browser of your choice. Reboot to reset permissions.
5. Launch the app (from your app drawer). Grant root to let it install drivers. I've always gone with super audio quality; I suppose it's up to you. It may ask you if it can modify some files to disable power saving...just let it happen. :good: Reboot again.
6. Go straight to settings/sound/music effects (at the bottom) and toggle Viper4Android as default.
7. Open root system/build.prop using a file explorer and text editor with root access. You change three lines of code as follows. Some may already have been changed.
Code:
Ipa.decode=true should read Ipa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
8. Save the file and reboot once more. Open the Viper4Android app and have at the sound settings; play around until you find what works for you (just make sure to check "Enable" :highfive. You can edit the settings as you have music playing. When you get it where you want it, toggle the enable button and see how far you've come.
You can explore the main app thread here for some ideas on customization.
All credit due to @viper520, @zhuhang, and @docnok63.
All I did was paraphrase. Hope this helps someone!
Mine still doesn't work D: followed these instructions exact I'm not sure where I'm going wrong.
EDIT: Does work, just doesn't work in the default Samsung galaxy music app.
Carlislee said:
Mine still doesn't work D: followed these instructions exact I'm not sure where I'm going wrong.
EDIT: Does work, just doesn't work in the default Samsung galaxy music app.
Click to expand...
Click to collapse
I have not been able to get this to work with the stock app on any version of KK but it works fine with Poweramp. Just have all EQ and processors in Poweramp turned off and in Poweramp settings/audio/advanced tweaks make sure everything is unchecked.
MikeyLee said:
I have not been able to get this to work with the stock app on any version of KK but it works fine with Poweramp. Just have all EQ and processors in Poweramp turned off and in Poweramp settings/audio/advanced tweaks make sure everything is unchecked.
Click to expand...
Click to collapse
WOW...it works here for me. At first it didn't. I looked for updates and it offered v2.3.3.0 Installed that and it's really noticeable with my ear buds. This is with Google music player. I have PowerAmp premium too. Have not tested on that but it for sure works with the latest APK I referenced and it is installed as a system app. One of those build.prop edits was already set while the other two needed to be changed, just an FYI. If you aren't on the latest APK, update. I am on the latest update of Alliance ROM here on my T Mobile S5 variant....fyi.
Hi guys can someone tell me what to do if i cant find the build.prop stated above on my device?
do i have to make the new one or to leave it as it be?
since i dont feel any difference and when i change the preset i dont feel any changes so please help me i would be very gratefull thx a lot
Nice one. Was just trying to get cyanide dsp working, was getting frustrated and then saw this... fantastic sound!
Cheers mate!
Sent from my SM-G900F using xda app-developers app
theoryzz said:
Hi guys can someone tell me what to do if i cant find the build.prop stated above on my device?
do i have to make the new one or to leave it as it be?
since i dont feel any difference and when i change the preset i dont feel any changes so please help me i would be very gratefull thx a lot
Click to expand...
Click to collapse
It's in system folder. You need to use an appropriate method of editing that allows you to change from read only to read write. Also for me you have to be running 2.3.3.0 version of Viper. And finally, at least for me, I set this up and it runs until I also use the app Poweramp. Seems as soon as I use PowerAmp with the equalizer on, it breaks the functionality within 2 seconds of starting any song. If you use the menu function while running the Viper app, look at driver staus which not only shows the version but if you are running a song it will say yes to processing which verifies the app is running. (build prop editor by JRummy Apps in Playstore is free and works great) (Of course Root Explorer is my all time favorite, paid app that has a ton of functions, including editing)
So it didn't work for me, unless deleted the mod and installed everything from scratch as a normal app instead of a system one. To make it work with Poweramp, had to enable " compatible mode", add "music fx" button to "tone/vol" screen and turn it on. Now it works.
Anyone here having trouble with signal after flashing this mod?
Or is it just me
Sent from my SM-G900H using xda premium
Awesome! Trying this out soon.
Here the sound is much better.
However commands double and triple clicks in the headset no longer work with the Power Amp.
This happened to anyone else?
what settings are everyone using? I dont know what to mess with
Guitarfreak26 said:
what settings are everyone using? I dont know what to mess with
Click to expand...
Click to collapse
Headset enabled:
V4A FX, Playback AGC, ViperBass, ViperClarity.
Do you use any custom irs? Or Profiles?
Sent from my SM-G900F using Tapatalk
Guitarfreak26 said:
Do you use any custom irs? Or Profiles?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
G900H rooted.
jmaxyyz said:
G900H rooted.
Click to expand...
Click to collapse
lol)
Gassity said:
lol)
Click to expand...
Click to collapse
Cada zé mané que me aparece...
Sorry for my poor english. What I meant is that my S5 was only rooted and the rest is all as it came from the factory.
But after a while the controls on the headset started to function normally. Thank you.
thanks, what a difference...waow !!
No one get music stuttering when screen off???
Its very annoying.
Hey, I can't get it to stick. It keeps asking to install the driver. My rom is "Project Infinity". I tried to move it to system/app but it says it's read only. I have busy bus installed. I don't know what to do, can someone please help me?
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?
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