Related
Root Tracker is source code for a super-simple Android 2.2+ device tracking system that responds to SMS messages with embedded control passwords.
Root Tracker is designed to be installed on a rooted device in /system/app, so it can survive a hard reset. Root Tracker has no user interface, all the better for hiding it from a thief. The code must be customized for the particular user and device, as passwords and other configuration items are hard coded, and each user should change the package name and other details to make it sound like a system package, in order to even better hide the package from a thief. Don't use the current values in the source, as a smart thief (there aren't many, I expect, but there may be some). Plus, I expect that different users will have different requirements.
After customizing and installing, go to your system Settings and set Root Tracker's device admin class as a Device Administrator.
Actions available:
gps
wipe
lock (locks screen [if set as Device Administrator; otherwise, sets screen timeout to a very short value to make device very hard to use], turns off adb, disables NoLock)
unlock
root shell command (output returned via SMS).
I wrote Root Tracker because I was uncomfortable about having my phone tracked and potentially wiped by a closed source app, like the various anti-theft trackers currently available. A crucial design principle was to make RT simple enough that one can easily verify from the source code what exactly it is doing.
The passwords are plain text in the apk. You can replace this with hashing if you like, but I didn't bother.
Also, instead of invoking the Android system's data wiping, which is known to be of problematic quality on some devices, it uses dd to overwrite the data partition, which may be more reliable (but of course, you have to ensure RT is installed in /system/app). Moreover, this means that the wipe works even if the thief is clever enough to go to the device settings and revoke Root Tracker's device administrator status. I don't know how well this works. This is a feature I did not test since I don't want to deal with restoring a backup. I worry that wiping the data partition will cause a reboot at some point. (Still, I have deleted the contents of /data before, and restored them via tar, and the device did not reboot while deleting.)
The gps command responds instantly with last cached GPS and Network location, then turns on GPS (even if disabled) and Network location (this one may show a dialog, so I recommend keeping Network location on in your Settings, or else disabling the Network location code). Then it waits for a GPS fix. If while waiting for a GPS fix, it gets a new Network location value, it sends that, but keeps on waiting for a GPS fix. If it gets a GPS fix before getting a Network fix, it quits looking for the Network fix (you can change that in the source code).
Note: Installing this on a device that isn't yours (unless you're law enforcement with an appropriate warrant) is likely illegal and is certainly not nice. This is designed for one's own use.
When you buy a new phone for your child. You want it must be a cool phone, but you also don't want your child uses WiFi function.
I have seen many people wondering here and there to Disable the WiFi permanently in their device. So i thought to make a thread regarding this.
I have seen many posts asking to remove or rename the WiFi Modules to Disable the WiFi but when i tried that unfortunately it failed to delete the Module.
So i moved on for another step and found easy steps to Disable WiFi permanently
Tested & worked in HTC M8 (4.4.2) & Nexus 5 (5.1)
This is a simple trick played in Build.prop which can disable the WiFi of your device for ever.
All you need is :
Rooted Device
ES File Explorer
RB Text Editor
First of all i recommend you to make a system backup with TWRP
here we go :
1. Open ES File Explorer and get Root access
2. Go to system folder and open Build.prop using RB Text Editor (i recommend you to backup original file)
3. Remove the below mentioned lines in Build.prop
Code:
[COLOR="red"]wifi.interface=
wifi.supplicant_scan_interval=[/COLOR]
4. save it and reboot!!
You can notice that WiFi buttons are no longer in use
Warning!
Im not responsible for any damage caused. Always Make Backup
Disclaimers:
PM me before you post!
#Reserved
Does this cause problems with broadcasting a Hotspot?
olearius said:
Does this cause problems with broadcasting a Hotspot?
Click to expand...
Click to collapse
No i guess
did not test that yet
please before i install new version of cm 12 how i can edit wifi to not turn on auto
Is there any Way to Disable Mobile Network Internet also ? Like 2G Edge , 3G ,4G etc.,
There is manual option to Disable Data Usage.
Is there any permanent Solution ?
Yes you can disable data permanently....
ashu55 said:
Is there any Way to Disable Mobile Network Internet also ? Like 2G Edge , 3G ,4G etc.,
There is manual option to Disable Data Usage.
Is there any permanent Solution ?
Click to expand...
Click to collapse
From my experience you have three options: 1. go into settings and disable your data that way, 2. download an app that allows for easy data on/off switching or 3. which I'm going to do myself when I buy a new (used ebay) phone in the next couple weeks for someone: contact my prepaid carrier and ask them to "disable the data". They can do this at the carrier-level. This will prevent a child for example from re-enabling the data just by clicking a button on their phone. I just verified with my carrier today that they can in fact do this. Good luck!
Hello .. sir ... I had seen that file in that text editor .. i dont found that coding... Nw what i can do.. pls tell me...
[email protected]
This did not work for my phone, as those program lines are not present in my build.prop folder, but I found a solution for my Samsung Galaxy S5 Neo (6.0.1) that I know many others are looking for, it will probably work for all the galaxy models or at least some of them. Here it is:
1. Root your phone using "oneclickroot.com", they will do everything for you, including installing TWRP and SuperSU. Be sure to pay attention to how to access TWRP (Team Win Recovery Project)... for me it was by holding down the volume up, home, and power keys simultaneously and then releasing the power key on seeing red letters. It might vary phone to phone.
2. Make a system backup with TWRP after rooting by accessing TWRP and simply clicking "backup" and then swipe. In the event that you need to restore just access TWRP and click and swipe "restore".
3. Use a file managing app like "Root Browser" by JRummy from google play to go into these file folders: "system/etc/wifi"
4. In the Wifi folder delete the first four files:
bcmdhd_apsta.bin
bcmdhd_ibss.bin
bcmd_mfg.bin
bcmd_sta.bin
4. Now reboot your phone by simply turning it off and back on again.
5. All done, your phone's wifi will no longer work.
6. If for whatever reason you don't want to be able to get it back ever again, just go delete your system backup in TWRP and you won't be able to get it back.
If you don't see these files in your phone after rooting, don't be discouraged. I figured it out with a little experimentation and I knew absolutely nothing about programming or androids... I still don't. Just make a system backup with TWRP and experiment by deleting different files that have "Wifi" in their name. Only delete one at a time or a small group of files at a time, and restart the phone every time as programming changes will not take effect until you do. Every time you brick (disable) the phone, just use TWRP to restore your OS (Operating System) using your TWRP backup. It only takes about 2 minutes to restore every time. I bricked my phone about 4 times in the process of figuring this out. Very simple and easy.
Also, your carrier will usually be willing to apply a "data block" to your account if you call them. For $2/month Koodo will apply a data block that makes it impossible to access data.
Hello,
I couldn't find neither the file "Build.prop"
neither these files.
I have an intel tab with android 5.0
me too
I have android 6.. didn't find any of them...
Jasmin74 said:
Hello,
I couldn't find neither the file "Build.prop"
neither these files.
I have an intel tab with android 5.0
Click to expand...
Click to collapse
And to enable it whats the number Code ?? I have lenovo Vibek4 note , my wifi configured interface is Disable, Please help
If I did this to disable wi-fi on my child's phone, could they simply undo it by doing a factory reset of the phone?
Disable Wifi on Moto G6 / Pie
I recently had to do the same thing with my child's phone. She was just too good at circumventing the usual child protections and getting on the internet to surf adult material and chat with random stalkers halfway around the planet.
She has a Moto G6 with Android 9.0 PIE.
1. Rooted it
2. Loaded a file manager and after much trial and error found that wifi could be disabled with name changes on:
/vendor/lib/modules/wlan.ko -> wlan.bak
/vendor/lib/modules/pronto_wlan.ko -> pronto_wlan.back
Then, reboot the phone.
The user can attempt to start wifi, but it fails. No boot issues.
thedude06 said:
If I did this to disable wi-fi on my child's phone, could they simply undo it by doing a factory reset of the phone?
Click to expand...
Click to collapse
Yes, they could. That's why I also used Google Family Link to set up a minor child account for her and made it the main account for the phone after I changed the file names above, but before rebooting. GLF prevents a factor reset from within the phone or changing the user. She could try to boot into recovery and perform a factory flash, but then it's going to want the same google account as before....and she doesn't have the password. Fastboot is locked as well. The only issue you might have is that google somehow thinks all 14 yr-olds should be independent enough to remove supervision, but I guess you could do the same thing that the kids do to get around age limits - change the birth date.
I also shut off data at the wireless provider.
Now, she's got a smart phone that calls and texts, but can't get on the internet or play store. Also, without the internet, no updates that will wipe out these changes.
Does not work for me
Hi
I have a Samsung Galaxy Grand Prime with LineageOs, rooted. I didnt find the files you were speaking about.
Except build.prop, but the mentioned lines didnt even exist in my phone files. Is there any other way to disable wifi permanently ?
Thanks
Sorry for the bump, but I really need to disable wifi in a Android 10 LineageOS based rom, but none of this solutions works...
How can I do this?
How to find Driver Files to disable the Wifi
There were a couple of bumps on this thread regarding driver files for wifi and how people weren't able to find these files on their phone.
The answer is that if you don't see the driver files mentioned in the thread above, it's because they're called something else, if they exist at all.
For the Moto 6, I spent a fair amount time doing trial and error renaming of system files until something worked. It took me some time and research to determine that for PIE, the .ko files represented some sort of driver files. Then, I went searching for .ko files with wifi in them, and then finally, I located the two files mentioned in the thread above. For your phone, they may be in a completely different directory, or named something different.
I knew that I had figured it out when I booted the phone, and was unable to get the wifi to work or even detect any signal.
Maybe there's a parameter file on your phone that controls the wifi settings, or maybe you rename driver files like I did.
I've done this a couple of times now on my kid's phones, and for each phone, the driver files were different. The last phone I did, I went ahead and posted to this forum so maybe someone else can get some benefit.
Best of luck!
-Oldguy51
An alternative solution for this issue is to assign a wrong universal local IP address for all wifi connections and the final user cant change it... Just Saying.
Wrong Universal Local IP Address
Orbitv said:
An alternative solution for this issue is to assign a wrong universal local IP address for all wifi connections and the final user cant change it... Just Saying.
Click to expand...
Click to collapse
That's in interesting concept. How would you do this on an Android phone?
etienne_9000 said:
Does not work for me
Hi
I have a Samsung Galaxy Grand Prime with LineageOs, rooted. I didnt find the files you were speaking about.
Except build.prop, but the mentioned lines didnt even exist in my phone files. Is there any other way to disable wifi permanently ?
Thanks
Click to expand...
Click to collapse
mdio said:
Sorry for the bump, but I really need to disable wifi in a Android 10 LineageOS based rom, but none of this solutions works...
How can I do this?
Click to expand...
Click to collapse
Well Well Well, I'm just 2 years late bumped on this thread .
It's Andoid 11 minimum in these times or even 12 & now 13 is also available.
But I managed to keep Wifi off while keeping Bluetooth Pairing & BT file transfers On, Hotspot On & Data On specially because Flight Mode no longer Disables WiFi, Bluetooth & Hotspot (only keeps Data off) since andoid 9 i think.
------------------ Worked on Andoid 11 GSI, Galaxy M-Series -----------------
I] If you just want WiFi disabled permanently, then Here are the steps that worked :
> Install Magisk or SuperSU And Optionally TWRP/Any Custom Recovery
> Install any Root Exploration app & grant it Root permissions
> Create a Backup (nandroid or anything that can backup your data)
> Using the Root Exploration app navigate to (vendor/etc/wifi)
> Look for the file ( wpa_supplicant_overlay.conf ), Tap and select Text Editor option
> Change to this -> [ p2p_disabled=0 ] , [ update_config=0 ], [ pmf=0 ] then tap Save.
> Reboot.
> Go to Settings >> Apps >> Bluetooth MIDI Service >> Reset the app
> Go to Settings >> Apps >> Bluetooth >> Reset the app
> Reset Network Settings (Settings >> System >> Reset Options >> Reset WiFi, Mobile & Bluetooth)
> Reset Firewall Settings(AFFirewall+, Netguard etc.)
> Reboot to Recovery
> Wipe Dalvik/ART Cache & Cache
> Reboot to System
Now WiFi & Location should be permanently disabled but you can still connect BT wireless & send/receive BT files (mp3, jpeg etc. but not apk, exe etc.) also Hotspot, Data , Manual Location (Not GPS Location) works.
#BUGS: Windows does not Connect Automatically to phone Hotspot, manual reconnect needed everytime. GPS Location breaks but Manual Location entry can be picked-up by apps like Opera Browser etc.
II] There is also another same way to get WiFi, BT, Hotspot Disabled while keeping ONLY Data Enabled but that was not the original question on this post so no need I guess.
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?
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.
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>*