Is there a way to change DPI without root?
Update: I used adb to change DPI to 600 from 640 with no issues.
Everything looks a lot better now.
Sent from my HTC 10 using XDA-Developers mobile app
I looked into it but didn't try it myself, but found this video. Good luck and godspeed!
https://www.youtube.com/watch?v=Psj0jWPdafw
martinezma99 said:
Is there a way to change DPI without root?
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
I really would like to know also. Just came from an s7 edge which required a small trick to change dpi.
Pretty easy to do with adb. Google it and you'll find a plethora of tutorials.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
I changed the DPI (density) to 600 from 640 (default) with no issues.
Sent from my HTC 10 using XDA-Developers mobile app
martinezma99 said:
I changed the DPI (density) to 600 from 640 (default) with no issues.
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried using this command "adb shell wm density 66 && adb reboot" and the phone won't boot. The stock wallpaper just flashes. Any ideas? Anyone?
gsxrfl1k6 said:
I tried using this command "adb shell wm density 66 && adb reboot" and the phone won't boot. The stock wallpaper just flashes. Any ideas? Anyone?
Click to expand...
Click to collapse
I'm assuming that 66 on comment is an error. The density I'm using is 600.
Sent from my HTC 10 using XDA-Developers mobile app
martinezma99 said:
I'm assuming that 66 on comment is an error. The density I'm using is 600.
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry, typo. I used adb shell wm density 600 && adb reboot
I can't do anything because the phone won't boot so I can run adb
gsxrfl1k6 said:
I tried using this command "adb shell wm density 66 && adb reboot" and the phone won't boot. The stock wallpaper just flashes. Any ideas? Anyone?
Click to expand...
Click to collapse
Did you try the below command to make sure your device is recognized?
adb devices
Sent from my HTC 10 using XDA-Developers mobile app
martinezma99 said:
Did you try the below command to make sure your device is recognized?
adb devices
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, it was, but not now. It just says device unauthorized. Like i said it won't boot. Is there anyway to revert the change if the phone won't boot?
Have you tired entering recovery and doing a hard reset?
I'm not sure what else you can do if phone will not boot. Try recovery mode.
Sent from my HTC 10 using XDA-Developers mobile app
martinezma99 said:
Have you tired entering recovery and doing a hard reset?
I'm not sure what else you can do if phone will not boot. Try recovery mode.
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
When I try to go into recovery to reset I just get a red triangle with an exclamation point.
gsxrfl1k6 said:
When I try to go into recovery to reset I just get a red triangle with an exclamation point.
Click to expand...
Click to collapse
That is stock recovery.
Press and hold the Volume Down button, then press the Power button to switch on your*HTC 10*and release it, but keep holding the Volume Down button. You'll see a screen with the option to boot into Recovery*Mode among several other options.
Select boot to recovery and press power.
The red triangle screen appears.
Press and hold*Vol up. Tap*power. Release*vol up*when you see the blue recovery menu.
Sent from my HTC6545LVW using Tapatalk
Got it. Thanks!
martinezma99 said:
Is there a way to change DPI without root?
Update: I used adb to change DPI to 600 from 640 with no issues.
Everything looks a lot better now.
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
The only graphic issue I have noticed so far is on the lock screen. Shortcuts along the bottom were random squares of colors rather than the icons. I never use those shortcuts anyhow, so I just removed them.
If I change mine DPI to anything other than 640 my screen just flashes and I have to change it back to 640 via ADB,
I had the same issue, but tried it again and it worked the second time.
gsxrfl1k6 said:
Yeah, it was, but not now. It just says device unauthorized. Like i said it won't boot. Is there anyway to revert the change if the phone won't boot?
Click to expand...
Click to collapse
if you are getting " device unauthorized ", you need to make sure you have developer options enabled AND USB debugging enabled
once you enter adb devices, it will start up on the command prompt and on you mobile device you should get a prompt requesting permission to access the device, click the check box and allow the connection, once this is done try again
adb devices and it should have the device authorized this time
hope that helps
on the other hand when i tried changing my DPI on my HTC 10 which is rooted it does change it but also the keyboard images i can only see 3 images QWE covering the screen side to side when i come back i'll see if i can post a picture, i have my HTC with TWRP, s-off, rooted, unlocked bootloader
TopoX84 said:
if you are getting " device unauthorized ", you need to make sure you have developer options enabled AND USB debugging enabled
once you enter adb devices, it will start up on the command prompt and on you mobile device you should get a prompt requesting permission to access the device, click the check box and allow the connection, once this is done try again
adb devices and it should have the device authorized this time
hope that helps
on the other hand when i tried changing my DPI on my HTC 10 which is rooted it does change it but also the keyboard images i can only see 3 images QWE covering the screen side to side when i come back i'll see if i can post a picture
Click to expand...
Click to collapse
Thanks. I think what happened is I didn't permanently authorize it (or whatever the option says), so when it wouldn't boot and I killed the server and restarted, there was no way for me to authorize it on the phone since it wouldn't boot properly. I wiped it anyway, oh well. Won't make that mistake again.
{
"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"
}
This is what I was talking about
this are the steps i used: open CMD and used command " adb shell wm density 600 && adb reboot "
then went ahead to check if this was still showing unfortunately it is.
just using the " adb shell wm size reset && adb reboot " wont solve it, at least on my device
i had to download " Easy DPI changer :" from the playstore, give the app root access and press the reset DIP option.
after rebooting the same issue showed up so
i went ahead and clicked on " Easy DPI changer " the reset button and used the " adb shell wm size reset && adb reboot " as well, checked again and it was back to normal
i'm running:
DEVICE: HTC 10 (Unlocked, Rooted, unlocked bootloader, S-OFF)
ROM: LeeDrOiD 10 - V1.0.1
MODS: LeeDrOiD 10 Tweaks
RECOVERY: TWRP 3.0.2.2
Sent from my HTC 10 using XDA-Developers mobile app
Related
I just bought a Pixel XL Verizon phone yesterday that has been updated to Oreo. I am coming from a Nexus 6 that I rooted and ran PureNexus on for 2 years. I had Samsung Galaxy phones before it. So I have always had my back button on the right and recents on the left. Is there any way to change it on a locked bootloader Pixel XL running Oreo? I have tried searching and everything I have seen says that I need root to do it. And from I can tell so far, there isn't a system UI tuner anymore.
Am I screwed? Should I just sell this Verizon version and get a Google version?
fatphatboy88 said:
I just bought a Pixel XL Verizon phone yesterday that has been updated to Oreo. I am coming from a Nexus 6 that I rooted and ran PureNexus on for 2 years. I had Samsung Galaxy phones before it. So I have always had my back button on the right and recents on the left. Is there any way to change it on a locked bootloader Pixel XL running Oreo? I have tried searching and everything I have seen says that I need root to do it. And from I can tell so far, there isn't a system UI tuner anymore.
Am I screwed? Should I just sell this Verizon version and get a Google version?
Click to expand...
Click to collapse
I would buy Google. I'm on Verizon and I did. I'll never buy another phone from them.
I used this app to make the edit then uninstalled - https://www.xda-developers.com/customise-the-navigation-bar-android-oreo/
If you don’t have root access, you’ll need to download either Minimal ADB & Fastboot or the official Google binaries to enable the required WRITE_SECURE_SETTINGS permission for the application.
To do so, you’ll need to first enable USB Debugging by going to the Developer Options menu. If you don’t see Developer Options, scroll down to “About” and tap “Build number” seven times until the “You are now a developer” toast appears. Back out and above “About” will be the “Developer options” menu. Enter this and enable USB Debugging. Launch adb from your computer by pressing shift + right click in the same folder containing your adb files, then choosing to “open command prompt here” if you’re on Windows. For Mac and Linux users, you’ll need to open terminal then cd to the directory where you downloaded the files. Follow the instructions in the app to grant the appropriate permissions.
Click to expand...
Click to collapse
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Thank you so much! Very easy and no apps to install. Used this method on my Pixel 2 xl
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
Any risks at all to doing this? I detest the placement of the back and home buttons on the Pixel 2 XL. Am i risking any bricking with this method? I find it to be incredibly annoying that Android doesn't allow this swap via settings. Putting the back on the left is just bad design. Thanks in advance.
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
I don't have a Pixel 2 XL, just a Pixel XL but I am on Oreo. I have had absolutely ZERO issues since doing this. I love my phone after changing the layout. Maybe localfinesse can chime in and let us know if there are any issues on Pixel 2 XL's phones doing this.
Works very well and very easy to config. Thanks!
Glad it is working for everybody.
Does this technique void the warranty like rooting would?
silverghozt said:
Does this technique void the warranty like rooting would?
Click to expand...
Click to collapse
no, it should not... and I do know someone who rooted their pixel and later needed an RMA for other reasons. their warranty wasn't void and they got a replacement...
edit; scratch my other comment / removed. that u were the same user as the pixel 2 Xl user.
Swap back and recent button
I have found a quick fix to swap the navigation buttons instead of going through the root and downloading, blah blah blah. The only issue is that when you do this, many of your toggles/menus in settings and google apps will be reversed on your screen. This isn't an issue for me because the priority is getting these two buttons reversed more than anything else.
Settings
System
(Tap) 'About Phone' 7 times
"You are now a Developer"
Go back to System menu
Developer Options
Scroll down to 'Drawing'
turn on 'Force RTL layout direction'
Finished
Your navigation buttons are now flipped.
You will now notice when you go into many Google apps, everything will be from right to left now. Your contacts dots will be on the right now. If this is an issue, then go back and switch it back and go through the download process to fix the navigation bar on its own.
T
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
Thank you so much. I tried the other method but it didnt work for me but your one worked flawlessly and instantly. You helped me a lot.
Menu button
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
I am curious if this method could be used to bring back the menu button, since long press on the recent apps button opens multitasking. Thoughts?
There is also an app in Playstore called Custom Navigation Bar that lets you do some cool things.
https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner&hl=en
Kentguy86 said:
I am curious if this method could be used to bring back the menu button, since long press on the recent apps button opens multitasking. Thoughts?
Click to expand...
Click to collapse
It is a bit wordy and you need a png for your system to point to and use but yes, you can add a menu button this way:
adb shell
settings put secure sysui_nav_bar "key(82:file:///storage/emulated/0/custom/ic_sysbar_menu.png),recent;home;back,space"
My png is in a folder on my internal sdcard in a folder called custom.
{
"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"
}
Or add dpad left and right
settings put secure sysui_nav_bar "key(21:file:///storage/emulated/0/arrowleft.png),recent;home;back,key(22:file:///storage/emulated/0/arrowright.png)"
You have to link to a png because there's no native icon any longer?
You are the man!
Worked like a charm! Thanks a million! It's instant, too.
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
Anyone tried this on P w the gestures enabled?
settings put secure sysui_nav_bar "space,recent;home;back,space"
i am Confused.
Does Space means we have to press space button before coma .
Or Does it mean we havr to copy paste comand as its written.
I am soory but what doest space means?
I have the Xiaomi Redmi Note 5 Global Version, ROM oreo 8.1.0, Global ROM 9.5.6.0
Tethering (4G hotspot) does not work.
Does anyone else have this problem??
{
"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"
}
What do you mean by doesn"t work ? You can turn it on, but there is no internet access or it won't turn on at all, or what ?
Sent from my WHYRED global
4G works but cannot be shared with the hotspot.
Hot spot turns on. You can connect another mobile phone to the hotspot by wifi but no internet connection.
Just did a speed test on Nexus 7 2013 connected to my Redmi Note 5 global (WI-FI_by_MikiGry). Everything seems fine...
http://cloud.tapatalk.com/s/5b01fcef1f6d1/1526856485498.jpg?
http://cloud.tapatalk.com/s/5b01fce...-05-21-00-45-21-694_com.android.settings.png?
http://cloud.tapatalk.com/s/5b01fd2...-05-18-23-02-23-504_com.android.settings.png?
Sorry for posting pics like that. Tapatalk doesn't want to post the normally for some reason :/
Sent from my WHYRED global
MikiGry said:
Just did a speed test on Nexus 7 2013 connected to my Redmi Note 5 global (WI-FI_by_MikiGry). Everything seems fine...
http://cloud.tapatalk.com/s/5b01fcef1f6d1/1526856485498.jpg?
http://cloud.tapatalk.com/s/5b01fce...-05-21-00-45-21-694_com.android.settings.png?
http://cloud.tapatalk.com/s/5b01fd2...-05-18-23-02-23-504_com.android.settings.png?
Sorry for posting pics like that. Tapatalk doesn't want to post the normally for some reason :/
Sent from my WHYRED global
Click to expand...
Click to collapse
Yes, everything the same as mine, very strange.
Maybe some setting that I need to change.....
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"
Thanks a lot
meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"
Click to expand...
Click to collapse
Thanks to your method, I solved this issue.
My setting is also null.
Same issue after checking.
Hope they release a patch for it, don't fancy mucking about doing ADB stuff but will if I have to
meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"
Click to expand...
Click to collapse
Thanks for your suggestions, I changed the settings as indicated and did the ADB and changed the value to "0" (it was "null").
But still no luck, tethering (hot spot) still not working.
Maybe if I flash a different ROM ? (EU weekly or RR?)
Hi,
Me too, tethering doesn't share Internet connection, but only when SIM is in slot 1.
If a put the SIM card in slot 2, everything works fine.
However, if I use another carrier SIM card in slot 1, tethering works as expected...
Tried both sim slots with one sim, then 2 sims, no joy.... No tethering... wifi connects but no internet...
meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
settings put global tether_dun_required 0
"
Click to expand...
Click to collapse
So I follwed the steps but when I try to execute the upper command to set this parameter I get an Android "android.permission.WRITE_SECURE_SETTINGS" denied error.... I enabled USB debugging and I´m successfully connected to the WHYRED device via ADB.
Any tips to solve this?
I also used the commande "settings put global tether_dun_required 0" and hotspot is now working as expected.
Envoyé de mon Redmi Note 5 en utilisant Tapatalk
Kusie said:
So I follwed the steps but when I try to execute the upper command to set this parameter I get an Android "android.permission.WRITE_SECURE_SETTINGS" denied error.... I enabled USB debugging and I´m successfully connected to the WHYRED device via ADB.
Any tips to solve this?
Click to expand...
Click to collapse
You need to also enable "USB Debugging (Security settings)" in additional to just "USB debugging". It is located in Developer options next to "install via USB" toggle.
To enable it you must be logged into your Mi account. You can log out later, and the setting will keep its value. While you're there you might also consider enabling "installing apps over USB" which also requires you to be logged in.
And yes, the fix indeed works.
Thank you, will try and hope it works.
meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"
Click to expand...
Click to collapse
Thanks a lot! I just register here to thank you!!! Worked in Xiaomi Redmi Note 5 Global Version 4GB 64GB
Awesome bro.. Thank you so much really.. Was frustrated because of this issue.. Your help indeed solved the issue. Greatly appreciated.. :fingers-crossed::fingers-crossed::fingers-crossed:
meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"
Click to expand...
Click to collapse
tamilselvan9j said:
Awesome bro.. Thank you so much really.. Was frustrated because of this issue.. Your help indeed solved the issue. Greatly appreciated.. :fingers-crossed::fingers-crossed::fingers-crossed:[/QUOTE
I was wondering who could help me to enable tethering, someone mentioned ADB, can i have the link for that please
The mi suit doen't work neither wondershare tunes go
Click to expand...
Click to collapse
maksant said:
tamilselvan9j said:
Awesome bro.. Thank you so much really.. Was frustrated because of this issue.. Your help indeed solved the issue. Greatly appreciated.. :fingers-crossed::fingers-crossed::fingers-crossed:[/QUOTE
I was wondering who could help me to enable tethering, someone mentioned ADB, can i have the link for that please
The mi suit doen't work neither wondershare tunes go
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-hotspot-connecting-fix-t3796847
Click to expand...
Click to collapse
I want it to be completely disabled, I managed to make it go away with Tasker but it comes back when I swipe up or use the keyboard.
With the XDA gesture control app it does goes away completely, but the app is really buggy, so I guess it can be done someway.
I also tried with a magisk module but it didn't do anything, any ideas?
adb shell wm overscan 0,0,0,-150
hides the navigation bar using the same method the XDA app uses.
adb shell wm overscan reset
Goes back to normal
Enviado desde mi XT1635-02 mediante Tapatalk
moxtrom said:
adb shell wm overscan 0,0,0,-150
hides the navigation bar using the same method the XDA app uses.
adb shell wm overscan reset
Goes back to normal
Click to expand...
Click to collapse
I'm getting this error: /sbin/sh: wm: not found when trying to run that code. Any ideas on what i might be doing wrong?
I'm getting this error /sbin/sh: wm: not found , any idea why?
Ivanrl said:
I want it to be completely disabled, I managed to make it go away with Tasker but it comes back when I swipe up or use the keyboard.
With the XDA gesture control app it does goes away completely, but the app is really buggy, so I guess it can be done someway.
I also tried with a magisk module but it didn't do anything, any ideas?
Click to expand...
Click to collapse
You better use the latest beta of navigation gestures from XDA, just join the telegram link.
Ivanrl said:
I'm getting this error: /sbin/sh: wm: not found when trying to run that code. Any ideas on what i might be doing wrong?
Click to expand...
Click to collapse
are you trying to run this from recovery?
if so, try running it while the system is booted. From what i noticed, a lot of adb commands don't work in twrp.
So i bought an android tv and when i went in toDevice preferences, i couldn't find accessibility menu anywhere. I searched it in all the menus in settings. i updated all apps and cleared data of apps and restarted the tv several times. I even factory resetted the Tv
Tv- vu premium 50 inch
Android ver - 9
.
please help
broyoto said:
So i bought an android tv and when i went in toDevice preferences, i couldn't find accessibility menu anywhere. I searched it in all the menus in settings. i updated all apps and cleared data of apps and restarted the tv several times. I even factory resetted the Tv
Tv- vu premium 50 inch
Android ver - 9
.
please help
Click to expand...
Click to collapse
I have the same problem with my TV, as I found out the problem is from the brand side. They choose a rom that that does not have this... The only way to give permision to an app is only through ADB that it is not an easy job
I also have the same issue with my TV, waiting for the solution.
I've gone crazy **** about this issue. I badly wanted to use Button Mapper but couldn't find the app under Accessibility Services. After 1 whole day of head storming, I was able to do it. It's the only way for now as the above user said some TVs not enabled accessibility menu in settings. This can be solved by their system update but till then we have to do manually with ADB.
You should have knowledge of ADB shell commands running through USB debugging with the help of ADB minimal tools or android SDK(please google if you don't know).
Enable developer settings and USB debugging. Connect TV to your computer having ADB tools. Remember only USB 2.0 port will work so don't use 3.0
Run "adb devices" to check whether TV got connected.
If connected then run this command
"adb shell settings put secure enabled_accessibility_services PKGname/ServiceName"
,here package name is your app package name where as service name is one of the app's services which seeking accessibility service.
For example I tried for Button Mapper(to map the remote buttons and it won't run without accessibility service enabled).
"adb shell settings put secure enabled_accessibility_services flar2.homebutton/flar2.homebutton.utils"
After that run another command for WRITE_SECURE_SETTINGS(this is must)
"adb shell pm grant PKGname android.permission.WRITE_SECURE_SETTINGS"
in my case it is "adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS"
This will resolve the issue without any problem. If you know adb commands then you can play with all the permissions and services for the apps.
Run above commands without quotes. To check apps package,permissions,services you can user any app manager/analyser app. I'm using FX explorer which is best file explorer and app manager. I'm attaching snaps which will be helpful. Let me know if you still face issues.
{
"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 same way I resolved this and other apps
The only thing you need to do with Button Mapper is this:
adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS
The app will take care of the rest after it has that permission
Perhaps anyone knows this:
In my tv sony XH900 (it has accessibility menu, it's not my problem), when i use button mapper and give accessibility permission through the menu, it works fine, but there is one bug:
Volume buttons +- doesn't work continually.. By keep press + for example, it just increase sound only 1 step. I have to press and left, the button many times to increase sound more steps..
Is this the default for all tv if you use button mapper or only mine?
Is there any solution?
Thanks,
I have the accessibility menu but when I install any app it doesn't appear on accessibility menu at all.
sophiesaelig said:
I also have the same issue with my TV, waiting for the solution.
Click to expand...
Click to collapse
flar2 said:
The only thing you need to do with Button Mapper is this:
adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS
The app will take care of the rest after it has that permission
Click to expand...
Click to collapse
Wow...Din't expect your reply. If you're official developer or team of Button Mapper, just want to tell you one thing.
"You saved my ass so many times". I just love your app and have been using it since a year, happy to say I paid for full version since starting.
ReX-Hell2heAven said:
I've gone crazy **** about this issue. I badly wanted to use Button Mapper but couldn't find the app under Accessibility Services. After 1 whole day of head storming, I was able to do it. It's the only way for now as the above user said some TVs not enabled accessibility menu in settings. This can be solved by their system update but till then we have to do manually with ADB.
You should have knowledge of ADB shell commands running through USB debugging with the help of ADB minimal tools or android SDK(please google if you don't know).
Enable developer settings and USB debugging. Connect TV to your computer having ADB tools. Remember only USB 2.0 port will work so don't use 3.0
Run "adb devices" to check whether TV got connected.
If connected then run this command
"adb shell settings put secure enabled_accessibility_services PKGname/ServiceName"
,here package name is your app package name where as service name is one of the app's services which seeking accessibility service.
For example I tried for Button Mapper(to map the remote buttons and it won't run without accessibility service enabled).
"adb shell settings put secure enabled_accessibility_services flar2.homebutton/flar2.homebutton.utils"
After that run another command for WRITE_SECURE_SETTINGS(this is must)
"adb shell pm grant PKGname android.permission.WRITE_SECURE_SETTINGS"
in my case it is "adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS"
This will resolve the issue without any problem. If you know adb commands then you can play with all the permissions and services for the apps.
Run above commands without quotes. To check apps package,permissions,services you can user any app manager/analyser app. I'm using FX explorer which is best file explorer and app manager. I'm attaching snaps which will be helpful. Let me know if you still face issues.
Click to expand...
Click to collapse
Thank you, I did it at the same app.
I tried to do it for this app " Mouse toggle for Android tv" but it didn't work, Can you help me?
Deleted member 1198227 said:
Perhaps anyone knows this:
In my tv sony XH900 (it has accessibility menu, it's not my problem), when i use button mapper and give accessibility permission through the menu, it works fine, but there is one bug:
Volume buttons +- doesn't work continually.. By keep press + for example, it just increase sound only 1 step. I have to press and left, the button many times to increase sound more steps..
Is this the default for all tv if you use button mapper or only mine?
Is there any solution?
Thanks,
Click to expand...
Click to collapse
If any have found workaround let me know, this bug is very annoying
ReX-Hell2heAven said:
I've gone crazy **** about this issue. I badly wanted to use Button Mapper but couldn't find the app under Accessibility Services. After 1 whole day of head storming, I was able to do it. It's the only way for now as the above user said some TVs not enabled accessibility menu in settings. This can be solved by their system update but till then we have to do manually with ADB.
You should have knowledge of ADB shell commands running through USB debugging with the help of ADB minimal tools or android SDK(please google if you don't know).
Enable developer settings and USB debugging. Connect TV to your computer having ADB tools. Remember only USB 2.0 port will work so don't use 3.0
Run "adb devices" to check whether TV got connected.
If connected then run this command
"adb shell settings put secure enabled_accessibility_services PKGname/ServiceName"
,here package name is your app package name where as service name is one of the app's services which seeking accessibility service.
For example I tried for Button Mapper(to map the remote buttons and it won't run without accessibility service enabled).
"adb shell settings put secure enabled_accessibility_services flar2.homebutton/flar2.homebutton.utils"
After that run another command for WRITE_SECURE_SETTINGS(this is must)
"adb shell pm grant PKGname android.permission.WRITE_SECURE_SETTINGS"
in my case it is "adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS"
This will resolve the issue without any problem. If you know adb commands then you can play with all the permissions and services for the apps.
Run above commands without quotes. To check apps package,permissions,services you can user any app manager/analyser app. I'm using FX explorer which is best file explorer and app manager. I'm attaching snaps which will be helpful. Let me know if you still face issues.
Click to expand...
Click to collapse
flar2 said:
The only thing you need to do with Button Mapper is this:
adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS
The app will take care of the rest after it has that permission
Click to expand...
Click to collapse
Bought a tv in europe ( developper and usb debuggibg activated) can't run any adb command though. Adb: not found
Hey everybody,
I guess I was not the only one being a bit disappointed that google didn´t make adaptive audio available for the Pixel 4 devices as well.
To be honest I personally think it´s a bit of a gimmicky feature that´s not very critical, but making it exclusive to Pixel 5 left a bitter after taste.
Here´s how to enable the feature persistent across reboots on a rooted device:
1. Download the pixel 5 device personalization app from apkmirror and install the app:
https://www.apkmirror.com/apk/google-inc/device-personalization-services/device-personalization-services-r-11-playstore-pixel5-353007393-release/device-personalization-services-r-11-playstore-pixel5-353007393-android-apk-download/
2. Flash the attached magisk module Adaptive_Audio_Settings_Enabler.zip via magisk manager app and do a reboot.
Wait a few minutes after the phone booted successfully and the entry in settings will appear.
Manual command method, doesn´t survive reboots but works on unrooted devices as well:
1. Download the pixel 5 device personalization app from apkmirror and install the app:
Device Personalization Services R.12.playstore.pixel5.357001175 APK Download by Google LLC - APKMirror
www.apkmirror.com
2. Make sure to have USB Debugging enabled via developer options and have a working adb environment. Then connect your phone to pc.
3. Type the following:
Code:
adb shell
4. then type (this step is not needed)
Code:
su
grant superuser permission in the window that opens on your phone.
5. Now paste the following commands:
Code:
device_config put device_personalization_services AdaptiveAudio__enable_adaptive_audio true
Code:
device_config put device_personalization_services AdaptiveAudio__show_promo_notification true
You can enable it now in settings and try the feature for yourself.
A few notes here:
I´m unsure how much profit this feature really gives, even on the Pixel 5. When enabling it on my 4XL the sound gets a bit more bassy.
Judging from the logs it should be working as it is with the steps described above. It might be that it´s tuned towards the Pixel 5, but well... Having options is always nice
The guide with the manual commands works without root, for those that don´t like to run rooted. I was able to disable and enable the feature back again without the need for root. Maybe some apps can execute scripts without root on the phone so it will stay across reboots. Somebody else has to figure this out though.
Have fun with it
{
"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"
}
Reserved
Wow, would you also happen to know how to enable night sight portrait mode on P4?
Thanks m8, you are a legend.
Works great on my 4XL stock, no root.
I followed the guide without the "su" part on adb shell
Thank you for the tip, but whenever I reboot the phone it will not stick, I'm currently rooted.
Zilla0617 said:
Thank you for the tip, but whenever I reboot the phone it will not stick, I'm currently rooted.
Click to expand...
Click to collapse
You´re correct. I didn´t notice it, because it takes a short while for the setting to disappear after rebooting.
I made a magisk module, that passes the command every boot after a timeout. Magisk required obviously
Freak07 said:
You´re correct. I didn´t notice it, because it takes a short while for the setting to disappear after rebooting.
I made a magisk module, that passes the command every boot after a timeout. Magisk required obviously
Click to expand...
Click to collapse
After installing the module, I added the commands using adb shell but adaptive sound still does not persist after a reboot.
Zilla0617 said:
After installing the module, I added the commands using adb shell but adaptive sound still does not persist after a reboot.
Click to expand...
Click to collapse
Flash the module in magisk manager, reboot, wait a few minutes and the entry should pop up. It needs a few minutes. There’s no need for any manual commands with the module.
Freak07 said:
Flash the module in magisk manager, reboot, wait a few minutes and the entry should pop up. It needs a few minutes. There’s no need for any manual commands with the module.
Click to expand...
Click to collapse
It's working. Thank you
Working like a charm thank you mate.
how i do adb Do you have an example please?
How do I get back to the original device personalization service app?
oraned said:
how i do adb Do you have an example please?
Click to expand...
Click to collapse
There are plenty of guides on xda on how to setup adb.
How to install ADB on Windows, macOS, and Linux
If you're on Windows, Linux or macOS, you can follow these step by step instructions to install ADB on your desktop or laptop PC.
www.xda-developers.com
If you are rooted with magisk and unfamiliar with command line, there's also the magisk module.
tifone said:
How do I get back to the original device personalization service app?
Click to expand...
Click to collapse
Open it in play store and hit uninstall. Then update again and it will install the latest one for pixel 4.
https://play.google.com/store/apps/details?id=com.google.android.as
Open this link when viewing xda via browser on your phone.
I am sorry telling you that my friend but I am rooted and did yesterday the process and everything was ok, after some seconds as you said the adaptive sound wan in my menu.
Today as I went to check if it was still there, kaboom, disappeared so I uninstalled everything and did it from the beginning, so it can be installed again.
Have an idea why?
Let's go ahead and give this a try. Thanks
Can confirm that it still does work. But after rebooting even with the root method and the module still showing up in magisk adaptive sound vanished in settings. Reinstalling the module makes it appear again and function.
Edit: The feature just vanished without a reboot. Guess Le Googs doesn't wan tus usingit RIP.
The comment above and I are experiencing the same symptoms. When a module is installed, it is initially visible in the configuration, but sometimes it is not present after a period of time. If you reboot each time, it will come back.
However, I wish it could be maintained without rebooting.
tifone said:
The comment above and I are experiencing the same symptoms. When a module is installed, it is initially visible in the configuration, but sometimes it is not present after a period of time. If you reboot each time, it will come back.
However, I wish it could be maintained without rebooting.
Click to expand...
Click to collapse
How long does it persist for you after you reboot?
zetsumeikuro said:
How long does it persist for you after you reboot?
Click to expand...
Click to collapse
That can't be verified. However, sometimes when time passes, it may not be in the setting.
I don't think there's a solution, but thanks for letting me use a service that doesn't support it.
I think I figured out why it sometimes disappears when I check it after some time.
I'm using the dolby digital plus module, but after deleting this module once, I tested to see if it disappears after a while, and the adaptive sound was maintained.
I'm not sure if it's causing a conflict between modules. I also noticed that the two modules run together at first.