I was just tooling around in my new Quest 2 and, while my level of technical expertise is sufficient to be dangerous, I don't have any real idea what I'm doing as far as rooting, bootloader mods, etc. However, I seem to have stumbled into the regular Android settings after an app I was trying asked for usage permissions, which it seems Oculus doesn't expect any of its bespoke apps to do.
The Android settings behave oddly, though, but more like there's some kind of watcher app that's preventing access to most of these non-Oculus options. Case-in-point, the app that wants usage access, when I enter the Usage permissions screen and select the app from the menu to be taken to the screen where it displays what the app will do with usage permissions and presents the toggle for it, the screen comes up only briefly before the settings dialogue disappears entirely with an error saying that "System has stopped responding". I'm pretty sure if I were fast enough, I could probably toggle it in time, but I could also try to grant those perms via adb (which I only now remembered I could do and thus haven't done yet).
I also found and enabled the actual Developer Options, not the basic one Oculus gives us if we sign up as a developer organization. I am certain that they have actually been enabled: Even though the "{ } Developer Options" menu item keeps reloading the page that its on, settings that you'd expect to find within now turn up in the settings search dialogue.
One of these options is to enable OEM bootloader unlock. Selecting that options from the search results screen (or any other search result you'd find within Developer Options) however does like before, drops you at the menu page with the "{ } Developer Options" option.
It would be absurd if it were to be as simple as enabling that option to gain access to the bootloader and do whatever, even moreso if it was me that first wrote about it -- but, since I'm under the impression that the settings aren't actually broken so much as they are being suppressed, is there a way to toggle these various developer options, including the OEM bootloader unlock, via adb?
(Another point in favor of suppression rather than breakage, the Oculus refuses to take a screenshot of anything I'm doing with a message stating that the device is forbidden from doing so, although in less nefarious language.)
tl;dr -- how might I go about programatically toggling developer options on the device to find out what happens? More broadly, what's a good place to start being more dangerous vis-à-vis my Android technical expertise? I find its structure in every way baffling and nightmarish.
And then just for kicks, there's some oddities, like how the machine name in adb shell comes back as "hollywood" (which I found a bit Baader–Meinhof-y, since I was watching a bunch of Modern Vintage Gamer vids including his one on the Wii and its "Hollywood"-benamed graphics coprocessor). Also, fastboot oem unlock returns a curious error directing the user to visit https://oculus.com/unlock, which doesn't exist, and as far as the Wayback Machine is concerned, has basically never existed.
This settings menu is (or at least it was) fully accessible on my Quest 1 last time I tried it. There does not seem to be an entry point on Quest 2 though.
I am currently enjoying the "Bugjaeger" app from the play store. That is a good ADB solution for the Quest 2. Have fun.
rickthecabbie said:
I am currently enjoying the "Bugjaeger" app from the play store. That is a good ADB solution for the Quest 2. Have fun.
Click to expand...
Click to collapse
Could you please elaborate? Link to any guides or anything?
dwkindig said:
I was just tooling around in my new Quest 2 and, while my level of technical expertise is sufficient to be dangerous, I don't have any real idea what I'm doing as far as rooting, bootloader mods, etc. However, I seem to have stumbled into the regular Android settings after an app I was trying asked for usage permissions, which it seems Oculus doesn't expect any of its bespoke apps to do.
The Android settings behave oddly, though, but more like there's some kind of watcher app that's preventing access to most of these non-Oculus options. Case-in-point, the app that wants usage access, when I enter the Usage permissions screen and select the app from the menu to be taken to the screen where it displays what the app will do with usage permissions and presents the toggle for it, the screen comes up only briefly before the settings dialogue disappears entirely with an error saying that "System has stopped responding". I'm pretty sure if I were fast enough, I could probably toggle it in time, but I could also try to grant those perms via adb (which I only now remembered I could do and thus haven't done yet).
I also found and enabled the actual Developer Options, not the basic one Oculus gives us if we sign up as a developer organization. I am certain that they have actually been enabled: Even though the "{ } Developer Options" menu item keeps reloading the page that its on, settings that you'd expect to find within now turn up in the settings search dialogue.
One of these options is to enable OEM bootloader unlock. Selecting that options from the search results screen (or any other search result you'd find within Developer Options) however does like before, drops you at the menu page with the "{ } Developer Options" option.
It would be absurd if it were to be as simple as enabling that option to gain access to the bootloader and do whatever, even moreso if it was me that first wrote about it -- but, since I'm under the impression that the settings aren't actually broken so much as they are being suppressed, is there a way to toggle these various developer options, including the OEM bootloader unlock, via adb?
(Another point in favor of suppression rather than breakage, the Oculus refuses to take a screenshot of anything I'm doing with a message stating that the device is forbidden from doing so, although in less nefarious language.)
tl;dr -- how might I go about programatically toggling developer options on the device to find out what happens? More broadly, what's a good place to start being more dangerous vis-à-vis my Android technical expertise? I find its structure in every way baffling and nightmarish.
And then just for kicks, there's some oddities, like how the machine name in adb shell comes back as "hollywood" (which I found a bit Baader–Meinhof-y, since I was watching a bunch of Modern Vintage Gamer vids including his one on the Wii and its "Hollywood"-benamed graphics coprocessor). Also, fastboot oem unlock returns a curious error directing the user to visit https://oculus.com/unlock, which doesn't exist, and as far as the Wayback Machine is concerned, has basically never existed.
Click to expand...
Click to collapse
Would you mind explaining how you got the settings page to open on the Quest 2? I am an OG root dev and just picked up a Quest 2 myself, would love to crack into this.
Oh, dang, yeah, sorry things have been mad hectic and I didn't see these responses. I'll provide a write-up tomorrow, ping me again if I don't reply later cause I'm a forgetful idiot.
dwkindig said:
Oh, dang, yeah, sorry things have been mad hectic and I didn't see these responses. I'll provide a write-up tomorrow, ping me again if I don't reply later cause I'm a forgetful idiot.
Click to expand...
Click to collapse
All good, I actually figured out how to launch the settings page from this command:
adb shell am start -a android.intent.action.VIEW -d com.oculus.tv -e uri com.android.settings/.DevelopmentSettings com.oculus.vrshell/.MainActivity
Everything works in this page, except for launching the Developer settings option. This crashes the app as you mentioned, even though I can see the OEM Unlock option in the settings search bar.
This repo is also very helpful, I am getting told to visit the same non-existent page you were as well when running fastboot oem unlock.
GitHub - QuestEscape/research: Sharing our security research on the Oculus Quest
Sharing our security research on the Oculus Quest. Contribute to QuestEscape/research development by creating an account on GitHub.
github.com
Honestly Annoying said:
All good, I actually figured out how to launch the settings page from this command:
adb shell am start -a android.intent.action.VIEW -d com.oculus.tv -e uri com.android.settings/.DevelopmentSettings com.oculus.vrshell/.MainActivity
Everything works in this page, except for launching the Developer settings option. This crashes the app as you mentioned, even though I can see the OEM Unlock option in the settings search bar.
Click to expand...
Click to collapse
Oh, cool, I spent some time myself looking for a similar command, but I don't know much about the inner workings of Android. Do you know if there's a way to programmatically toggle the OEM Unlock switch?
I'll still post my circuitous method of getting there tonight (US/Central), maybe it will be enlightening in some way. I can't take screenshots or video of the process, cause the security policy configured by Facebook disallows it in those places.
Honestly Annoying said:
This repo is also very helpful, I am getting told to visit the same non-existent page you were as well when running fastboot oem unlock.
GitHub - QuestEscape/research: Sharing our security research on the Oculus Quest
Sharing our security research on the Oculus Quest. Contribute to QuestEscape/research development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay, things are a bit different since when I first posted -- I can grant packages usage access without crashing back to Android settings (`com.android.settings`). However, I can launch Android settings directly using App Manager (https://muntashirakon.github.io/AppManager/). Still can't screengrab, though, and still can't access the Developer Options, can only search for them. Interestingly, the breadcrumbs in the search results refer to the uppermost level as `null`.
So i connected my Quest 2 to Android studio and used the debug and the log tool to see why the settings app crashes when trying to enter the developer settings. I got the exception and maybe i can paste it in here when i get home. Also i managed to sign out of my Facebook account and remove the oculus system administrator but that made the headset useless. I also created an app for the oculus that search for all the installed packages and when you click on one of them it's trying to launch the package in vr shell and found some interesting things such as a oculus assistant and a battery charging mode setting.
Honestly Annoying said:
This repo is also very helpful, I am getting told to visit the same non-existent page you were as well when running fastboot oem unlock.
GitHub - QuestEscape/research: Sharing our security research on the Oculus Quest
Sharing our security research on the Oculus Quest. Contribute to QuestEscape/research development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
maybe the page does exist, but you don't have the authority to visit it, so oculus redirect you to somewhere else
maybe its not helpfull, but when you start wireless wifi on the Q via a wired adb host , you can install the app 'remote adb shell' (blue cast icon, pstore) on the quest and connect to localhost. so you have an on device adb shell for pm commands. it has to be this remote app because of lack on adb shell command without magiskmodule (termux crashes to the tv channel). i dont know how the activitys are called in android so maybe you got luck. also are the developer options part of the settings.apk? i think they pulled it out like that so why not making a new settings.apk where the devops are available? on this way there is sure an option to have a lock on the wifi adb too so it doesnt shutdown anytime you reactivate. edit: seems that with the new multitasking feature, its possible to hold up a wifi connection even the hmd was locked, just run the remote shell, connect and dont close it. you can connect via pc too without need to use adb tcpip again. before i setup adb tcpip via ' setprop service.adb.tcp.port 5555 ' again on the remote shell app. i now let it locked, and look how long it can holdup the wifidebug without reactivating via cable.
raeumler said:
maybe its not helpfull, but when you start wireless wifi on the Q via a wired adb host , you can install the app 'remote adb shell' (blue cast icon, pstore) on the quest and connect to localhost. so you have an on device adb shell for pm commands. it has to be this remote app because of lack on adb shell command without magiskmodule (termux crashes to the tv channel). i dont know how the activitys are called in android so maybe you got luck. also are the developer options part of the settings.apk? i think they pulled it out like that so why not making a new settings.apk where the devops are available? on this way there is sure an option to have a lock on the wifi adb too so it doesnt shutdown anytime you reactivate. edit: seems that with the new multitasking feature, its possible to hold up a wifi connection even the hmd was locked, just run the remote shell, connect and dont close it. you can connect via pc too without need to use adb tcpip again. before i setup adb tcpip via ' setprop service.adb.tcp.port 5555 ' again on the remote shell app. i now let it locked, and look how long it can holdup the wifidebug without reactivating via cable.
Click to expand...
Click to collapse
.
if someone knows a working terminal for the quest (the original crashes the keyboard after a while). to replace the remote adb shell app, we could use an adb binary that holds up the wifi with adb shell to localhost (shell commands), while another terminal (local, pc or smartphone) can connect through the adb binary over wifi to localhost/quest-ip (for adb commands). but setting up an adb server (not the service) via adb binary and on-device terminal (even via adb shell) is not possible without root (but the remote adb shell app starts one or does it somelike different without root and on-device). when we know how we could put that logic together in a script or apk then). but anyways:
so its setted up now on my quest for holding up debug over wifi (sideload connection) and have an ondevice shell. it runs minimum 23 hours without needing to activate it via cable (adb device to check connection)
1. download/sideload remote adb shell app
2. connect quest2 to a host via usb
3. open cmd on host: adb tcpip 5555
4. disconnect usb
5. start remote adb shell on the quest and type quest-ip:5555 OR localhost:5555 and click connect
6. type in remote adb shell: setprop service.adb.tcp.port 5555
7. minimze the remote adb shell app and let it run
(8). to disable wifidebug: setprop service.adb.tcp.port -1
now there is no need for reactivating until reboot. if you want to run a command go to -> apps -> unknown sources -> open remote app (as there is no recent button).
you can connect to any adb host via wifi (local, pc, smartphone) even after lock or a matter of time (min 23 hours)
the remote adb shell app:
Remote ADB Shell – Apps bei Google Play
Eine Verbindung mit ADB auf einem anderen Android-Gerät läuft über das Netzwerk
play.google.com
with terminal shortcut app you can make settings-scripts then and run them via iconlist for textureresolution and gpu level or whatever ....
ps: maybe im in the wrong subforum now. should i make a thread?
pps: the app 'autostart and stay' adds an autostart option to the quest, which allows to run a launcher before original launcher comes up. (buggy)
ppps: the app SSH Server can set up a SFTP connection for wireless filetransfers
edit: could be that it just work to the first whyeverdisconnect then the quests tracking is beside and you have to reboot
double
Honestly Annoying said:
All good, I actually figured out how to launch the settings page from this command:
adb shell am start -a android.intent.action.VIEW -d com.oculus.tv -e uri com.android.settings/.DevelopmentSettings com.oculus.vrshell/.MainActivity
Everything works in this page, except for launching the Developer settings option. This crashes the app as you mentioned, even though I can see the OEM Unlock option in the settings search bar.
Click to expand...
Click to collapse
This still works today! I have a Quest 2 running V35, and recently un-linked my Facebook and Oculus accounts. After finally getting my Quest 2 back up (still needed to use the old Oculus apk from an Android device and Quest 1 device selection), the timezone was off, so I used the above adb shell command to access settings, and changed the timezone fine.
I also changed the Device Name, although I'm unsure what ramifications that might cause later.
Edit: Don't change your Oculus account password after doing the FB account bypass. You'll break the log-in session, and have to factory-reset and start over.
you can have more settings when you use SetEdit (Settings Database Editor) from pstore. some props are editable, some need root.
Related
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Kyocera-E4710 - T-Mobile Tethering
I too have purchased one of these excellent flip phones. I really want to be able to tether using T-Mobile's service. Has anyone risen to the challenge yet?
kotton666 said:
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Click to expand...
Click to collapse
Rooting Kyocera E4710
Is it possible to root this phone? I would like to install an Android SIP client, the operator said it's not possible to install anything on it. Even though I enabled apps from Unknown Sources.
kotton666 said:
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Click to expand...
Click to collapse
Not sure if anyone still needs to remove the AT&T address book on this phone without root BUT I managed to do it.
Enable Developer mode on the phone by clicking:
"Menu" from the home screen. Choose Settings-->System-->About Phone.
Scroll down to "Build Number" and hit the "ok" button a few times until it tells you that you're a developer.
Back up one menu and go into "Developer Options".
Enable USB Debugging. (I also enabled OEM Unlocking but I don't think this is necessary)
Next install the Universal ADB drivers onto your computer. Google will help you find them. (I used the ones from clockworkmod but I'm sure any of them would be fine.)
Connect your phone and ALLOW any of the prompts that come up.
Open up an administrative command prompt/terminal and then type "adb devices". Make sure you can see a device listed. I'll look something like:
* daemon started successfully *
6689467283 device
Next run the command:
adb uninstall --user 0 com.borqs.aabsync
You should see a "success" below.
If so run the command: adb reboot
Your phone will reboot and you can disconnect the phone from the computer at this point.
Give it a moment to start up and then hit the "down" arrow on the keypad as normal. You will likely see an empty contact list. Press the key for "Options" then choose "Contacts to display" and choose wherever you have the contacts saved. Let it load them in and you're done.
Hope this helps someone!
david11717 said:
Not sure if anyone still needs to remove the AT&T address book on this phone without root BUT I managed to do it.
Enable Developer mode on the phone by clicking:
"Menu" from the home screen. Choose Settings-->System-->About Phone.
Scroll down to "Build Number" and hit the "ok" button a few times until it tells you that you're a developer.
Back up one menu and go into "Developer Options".
Enable USB Debugging. (I also enabled OEM Unlocking but I don't think this is necessary)
Next install the Universal ADB drivers onto your computer. Google will help you find them. (I used the ones from clockworkmod but I'm sure any of them would be fine.)
Connect your phone and ALLOW any of the prompts that come up.
Open up an administrative command prompt/terminal and then type "adb devices". Make sure you can see a device listed. I'll look something like:
* daemon started successfully *
6689467283 device
Next run the command:
adb uninstall --user 0 com.borqs.aabsync
You should see a "success" below.
If so run the command: adb reboot
Your phone will reboot and you can disconnect the phone from the computer at this point.
Give it a moment to start up and then hit the "down" arrow on the keypad as normal. You will likely see an empty contact list. Press the key for "Options" then choose "Contacts to display" and choose wherever you have the contacts saved. Let it load them in and you're done.
Hope this helps someone!
Click to expand...
Click to collapse
Thanks for posting your solution above.
Unfortunately for me I got as far as installing the adb drivers on my PC, reconnecting the phone, and no prompts came up, neither on the phone nor the PC.
I opened a command prompt window and typed "adb devices" and got the following message:
adb devices is not recognized as an internal or external command,
operable program or batch file.
Any suggestions?
As long as ADB driver isn't made system-wide accessible ( i.e. got added to PATH environment variable of Windows OS ) you get the message mentioned.
My Kyocera E4710 outer screen has an alarm that I can't get to go away. I can't see who is calling me because the alarm blocks the caller info. I have a few alarms but they are all turned off and there is not a way to delete them. I've gone through the user manual and it doesn't show how to get rid of this alarm (which shouldn't show since there isn't one enabled). Does anyone know how to get rid of this alarm on the outer screen? Thanks.
Shield Tablet Bug Fix "missing home button, recent tabs, notification centre" Nougat
Hello Everybody. I have a Shield Tablet running Nougat. I have been experiencing the bug described in the Title a few times, and I finally found a way to solve such bug, at least in my specific scenario. It might not work for everybody but, as I have seen a lot of Users experiencing such bug and being forced to deal with it through a factory reset, I thought posting an easy guide might be helfpful to some. It is not rocket science, but for me it does the trick well. Should you feel there is an easier way to solve the same issue, please, do not hesitate to add it to this post.
I already posted this guide on the official Shield Tablet forum, but I cannot add the link because I am a new User (c'mon dudes, I am not spamming.. just trying to help ). Therefore, I am just gonna copy paste the guide. I apologise if the formatting is not ideal.
Hello Everybody, I know that there is an Android bug that has been creating issues for many years, also on shield tablets. When the bug starts, the home button disappears, it is impossible to open the "recent app" tab, the notification centre cannot be pulled down, and there are many other side effects. Since I started having this issue, I did quite a lot of research. Apparently, all I could find were information regarding how to solve the bug on Lollipop and Marshmallow, but nothing regarding Nougat. The way this bug is usually fixed is by starting the Setup Wizard on the device. Unfortunately though, I was not able to open it due to permission restrictions. Some guides mentioned installing Nova from the appstore, and setting up an action Widget in order to start the Setup Wizard. This did not work for me as well. What I was able to do, instead, was creating and setting up a new User profile, which then fixed the bug on my main User.
I am sure people more experienced and talented than me probably would have been able to find a neater way to make this happen. However, as I am quite a noob with these kind of things, I thought that writing a basic guide might be helpful for others as well.
Before going on, you should know that in my case, the only way to fix the problem is to have "debug settings" enabled on your device BEFORE the bug starts. When I first got the bug, I had not unlocked "debug settings" and I could not do it afterward, as tapping 7 times on the build number did nothing. You also need to have Android Debug Bridge (adb) installed on your computer and configured with the tablet.
Also, the process I will describing now creates a new User and switches to it by using terminal commands and Adb. I am aware that there would be an easier way to achieve the same result by going on "settings>Users" on the tablet. However, if you experience the same bug I was having, you will find out that clicking on the "Users" tab does nothing.
Here is a step by step guide of what I did:
1
Normally boot your tablet and connect it to the computer via usb cable
2
Run a command prompt windows on the computer and run Adb. Even if, due to the bug, you won’t be able to transfer files to the tablet via USB, adb should be able to interact with the shield anyway. To double check this, type the command: adb devices . You should be able to see your device listed.
3
It is now time to create a new User through the command prompt. You can do that by typing the command:
adb shell pm create-user User_Name
Once the new user has been created, the prompt will show you the respective User_ID. You will need to type such number in order to switch to that user, by typing the command:
adb shell am switch-user User_ID
eg. adb shell pm create-user Charlie
Success: created user id 11
adb shell am switch-user 11
4
Your shield should have now switched to the new user just created. At this stage, finish the new user configuration stage on the tablet. Skip all the google services related options, as you do not need them. When the configuration process is finished, the home button, the notification centre, the recent app, etc. should be back. Now that the bug is fixed, it should be possible to go back to your main User profile by simply switching User from the settings menu on the shield: settings>Users. At this stage, if everything went well, you should be logged with your main User, and the bug should have been fixed. It is now possible to go again on settings>Users and delete the new User created on step 3.
This is it. It works well for me and, even if I do not exclude that the bug will present itself again at some point, this is a 5 minutes solution to fix it. I apologise for any english mistake, as English is not by main language. Also, somebody might know of an easier way to solve the issue on Nougat, although I was not able to find any online, and that is why I wrote this short guide. I hope it will be able to help some of you!
Have a nice day!
Alberto
Alright, I was reading around about the Wear24 the issues the Verizon bloatware was causing (Crucial WearOS features being limited/disabled). I decided enough was enough and decided to share this method with you. It involves the "user 0" method. You will still be able to get OTA updates and all that good stuff! If you factory reset the watch, you might have to do this again.
First (Highly recommended), factory reset your watch. Then set it back up and update WearOS (Don't worry about updating anything else) via the play store (You can sideload it too).
Second, after setting up your watch, go to settings -> system -> about then tap on your build number until you have unlocked developer settings.
Third, go to your developer options and enable ADB debugging and debug over Wi-Fi.
Connect to your Wi-Fi and click on the Wi-Fi network you are connected to, it should show your IP address (Take note of your IP address) and MAC address.
Assuming you already have ADB setup on your machine type:
Code:
adb connect your.watch.ip.address:5555
Then
Code:
adb shell
After that you should see something like this: dorado:/ $
If that shows, great! If not, make sure you have authorized your PC on your watch.
Moving on, you want to get the list of Verizon apps installed on your watch so type:
Code:
pm list packages | grep 'verizon'
And you should get the list of Verizon apps in the form of package names that is currently installed.
Next you'll want to uninstall them (All 5 or 4 of them. I can't recall as I have already done this). so here is the command to do so.
Code:
pm uninstall -k --user 0 com.verizon.crapware.mesagesplus
I hope you got the gist of that.
After you have uninstalled the packages, reboot your watch, and you should be able to see the apps that you have installed in the app drawer, and you should be able to set Google Messages as your default! Also as an extra measure, just disable all of the Verizon apps. They'll still show in your system apps, but if you click on permissions, it'll say "App isn't installed".
I'm sorry if the format is crappy. Also, mods, if you feel that this doesn't belong here, feel free to delete this post.
If you are having troubles doing this, I can clarify and help you guys out if need be!
Thanks for this! Just picked up two Wear24's, going to debloat them right away.
I've had this watch since Jan 2018 and I'd like to try this out, however, no matter what I do I can't connect to the watch over adb. Same wifi network, abd is working fine on Note9, debugging over wifi is turned on, just constantly get this error "An attempt was made to access a socket in a way forbidden by its access permissions. (10013)". Any suggestions?
Hi, I'd like to know if it's possible (and if so, how) to directly change android settings via adb commands.
My wife has broken the LCD screen on her phone (OnePlus 7T HD1907, Android 11, rooted with Magisk). I'm having a lot of trouble getting screen mirroring and USB OTG input devices to work at the same time; I have a USB v3 hub, and a USB OTG connector, but I've only been able to consistently get either screen mirroring or input devices to work, not both at the same time. The screen on the phone has now completely failed so I can no longer switch back and forth between the two to make changes on the phone. When I did have it working briefly I turned on the "experimental desktop mode on secondary displays" in Developer Settings, which just made things worse because Android settings don't seem to be available in desktop mode.
I have an identical phone to which I can refer, if needed.
Feenix0 said:
Hi, I'd like to know if it's possible (and if so, how) to directly change android settings via adb commands.
My wife has broken the LCD screen on her phone (OnePlus 7T HD1907, Android 11, rooted with Magisk). I'm having a lot of trouble getting screen mirroring and USB OTG input devices to work at the same time; I have a USB v3 hub, and a USB OTG connector, but I've only been able to consistently get either screen mirroring or input devices to work, not both at the same time. The screen on the phone has now completely failed so I can no longer switch back and forth between the two to make changes on the phone. When I did have it working briefly I turned on the "experimental desktop mode on secondary displays" in Developer Settings, which just made things worse because Android settings don't seem to be available in desktop mode.
I have an identical phone to which I can refer, if needed.
Click to expand...
Click to collapse
I don't know if it contains your specific setting, however, many settings can be read/stored/modified using the foillowing commands from a shell/ADB. using
Code:
# read settings, there are three partitions. Secure, System & Global
settings list secure;
settings list system;
settings list global;
# to read a specific one
settings get secure "sleep_timeout";
# to change a setting
settings put secure "sleep_timeout" "-1";
# there's another command for delete, but I cnat remember it for certain, so dont wish to guess and lead you astray ;) and I am sure you know how to do a web search
The above is for a shell, adding adb shell to the front would run it explicitly from adb.
Trying to change system settings requires Android is rooted.
xXx yYy said:
Trying to change system settings requires Android is rooted.
Click to expand...
Click to collapse
It is.
DiamondJohn said:
I don't know if it contains your specific setting, however, many settings can be read/stored/modified using the foillowing commands from a shell/ADB. using
Code:
# read settings, there are three partitions. Secure, System & Global
settings list secure;
settings list system;
settings list global;
# to read a specific one
settings get secure "sleep_timeout";
# to change a setting
settings put secure "sleep_timeout" "-1";
# there's another command for delete, but I cnat remember it for certain, so dont wish to guess and lead you astray ;) and I am sure you know how to do a web search
The above is for a shell, adding adb shell to the front would run it explicitly from adb.
Click to expand...
Click to collapse
Would I simply type "adb shell" to start the shell after connecting to the device? I'm assuming that this would be a linux shell.
xXx yYy said:
Trying to change system settings requires Android is rooted.
Click to expand...
Click to collapse
I am pretty sure that not ALL settings require root to be changed.
Feenix0 said:
It is.
Click to expand...
Click to collapse
Well, that makes it hypothetical in this case
Feenix0 said:
Would I simply type "adb shell" to start the shell after connecting to the device? I'm assuming that this would be a linux shell.
Click to expand...
Click to collapse
There are many ways to do things.
Personally (if not using the app I created and listed below), I start a shell with adb shell and I am running windows, so that is run from a command shell.
At that point, you enter the ANDROID shell (Not linux, its an android device)
I then change to a root shell with su; Only because anything worth doing usually requires root, and at least some of these will.
And then I can run any of the statements above. I would suggest you run a list of each and save that off as a backup.
Another option to see many of these in action and generate a "restore" of the existing, is using the app I created called TeMeFI
You can find these under the menu Current State>Settings>*
I had an issue when Android 12 (it might have been Android 11, can't remember) first came out where my physical Keyboard connected through USB wouldn't type. I searched for hours on end and FINALLY found something in the official Android docs where you can change either a global setting or a flag to allow keyboard input under certain conditions. I can't remember for sure what it was, but I think it's either while a screen overlay is detected or while an accessibility service is running. Well, here I am years later with that same problem again. Only this time, I can't for the life of me find the answer. If I remember right, I had to put in an ADB command to set a certain flag to allow it. I've searched XDA and Android docs for hours but cannot find it. Please, someone help before I go insane. I really need my keyboard to work.
Edit: nevermind I found it! For anyone looking for the answer, go to the docs here: https://developer.android.com/about/versions/12/behavior-changes-all#untrusted-touch-events
You can fix it for a specific app by doing `adb shell am compat disable BLOCK_UNTRUSTED_TOUCHES com.example.app` or for all apps (doesn't always work) by doing `adb shell settings put global block_untrusted_touches 0`