adb command to switch to 3dof - Oculus Quest

Hi everyone,
I've been trying to find the right adb command to switch to 3dof mode for a few days and cannot find anything working.
Wonder if anyone found something?
I identified with logcat that GuardianInput changes, with GuardianSetConfigParam CONFIG_PARM_3DOF_MODE, but I'm not sure this is the setting that needs to be changed.
In the dumpsys I also found:
_id:863 name:CONFIG_PARM_3DOF_MODE pkg:com.android.shell value:ON
Can someone tell me how can I turn this setting off?
Thank you!

Related

ADB USB Driver

the USB driver for windows is available at:
http://dl.google.com/android/android_usb_windows.zip
It seems to work... I will update this thread with what I find.
Thanks for posting the driver!
I've tried a few things with adb, and so far I can't get an install to work over usb. I tried the following command.
C:\...\android-sdk-windows-1.0_r1\tools>adb install OperaMini.apk
579 KB/s (0 bytes in 278155.000s)
pkg: /data/local/tmp/OperaMini.apk
Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED]
Click to expand...
Click to collapse
http://www.android-freeware.org/tutorial/how-to-install-apk-files-on-android-device-emulator Had some basic info about the emulator, not sure what would be different for the G1.
The "adb shell" option allows you to access a shell on the phone over USB, which is really great but it appears you don't have root privileges. Any ideas on how to obtain root priveleges? Also, is there a command to install from the android shell? When i cd to /sbin i get access denied. I'm trying to figure out some kind of way to invoke an install either from the device or over USB.
I have the same problem... working on it now...
I don't know about the USB installs, but it seems to be something with the APK as well. I also have the OperaMini.apk and it does nothing. I downloaded the iTunes remote via the G1 and it installed just fine without getting a PC involved.
It looks like you have to put the phone into a "Debug on USB" mode to use ADB. It's working for me now.
http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Thank you dagentooboy!
Can someone explain this for this not so savvy person?
chrimage said:
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Click to expand...
Click to collapse
I think that is caused by an issue with the the AndroidManifest.xml file within the APK having to do with going from "beta" to "live" Android. The same reason most of the apps were pulled from the store. I don't believe it takes a major change to make it compatible, but it's fully compiled so, unless you have a decompiler, I think we may be out of luck on that particular one. I have installed other apk's successfully using the same method.
Mikey1022 said:
Can someone explain this for this not so savvy person?
Click to expand...
Click to collapse
ADB is the Android Debug Bridge that comes as a part of the SKD. I don't think it was really intended as an end user tool. It has to be called from a command line. I know people have built basic UI's for it for file manipulation when the SDK was the only thing out there. If a better solution isn't found shortly I think we'll see one be made, or else I'll make one myself. In the end it seem to make a big difference of what you're trying to install some things work and some don't, there are some differences between the beta SDK and the G1.
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Valicore said:
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Click to expand...
Click to collapse
the su command and sudo su returns "no permission" or "access denied" or something like that. That is also the same message i get when typing arbitrary commands that shouldn't be anything. And like i said earlier, /sbin along with many other directories are inaccessible. Hopefully someone will find a way to access the root account on the G1 pretty soon.
yes... must... have.... root...
Also a normal shell would be helpful esp when looking thru /proc/ for information.
Please help (ahhhhhh)
Okay So I am pulling my hair out here... I just booted android on my Vogue for the first time, everything works great, voice calls and sms.. But I can get a Inet connection but I am using Cricket not sprint so I added the username and password lines in default.txt and can connect, but Cricket uses a proxy for all http connections. So I found this article http://fggarcia.blogspot.com/2007/11/setting-up-proxy-for-android-emulator.html , which basicly says to use the adp app that comes in the sdk to add some lines to make the proxy. NOW, here is my problem... I can not for the life of me get my come (in windows or linux) to see my vogue while its in android..
In windows it does not appear ANYWHERE in the device manager... So I cannot install the driver, and in Linux it doesnt make a blip in dmesg..... USB debugging is marked and so is use adb....
It does charge when plugged in to the comp running linux.....
Can anyone please help me... And thanks to DZO and everyone else for there hard work on this project..
check too make sure your Android isnt listed under usb mass storage devices in device manager.
Ya USB isn't possible on Vogue yet, I just extracted data.img and added the proxy that way, but it still doesn't work. My Problem is I need all connection to use the proxy wap.mycricket.com:8080. I am not trying to be cheap or anything like the tzones thing for tmobile. Its just the only data plan cricket have use this proxy. So any Ideas would be greatly appreciated.
my computer already had a driver installed and when i try to update it with this one it says there is no better match for my hardware
anyone got a solution for this
Im really sorry to bump this old thread up but i need the r3 drivers and i dont know why they are nowhere to be found on the official page... i think its a region lock thing...

Enable NFC via shell command?

Before you act like I'm an idiot, I've searched for days and was unable to find the answer.
What should I put into the command line in order to enable NFC via shell?
Any help appreciated.

Failed to connect

Kitkat on nexus 5
Recently, about a week, I will get a popup that says "failed to connect". I'm sure it is some app that I'm blocking from the Web, but the message has no identifier. So I don't know which app is trying to reach the Internet.
Is there a log or tool somewhere that would help identify which app is putting up that error message?
'adb logcat'
So, do you mean in a terminal app, I enter
adb logcat > something.txt
Do I need to install a logcat app or just a terminal app?
Thanks for helping.
Anderson2 said:
So, do you mean in a terminal app, I enter
adb logcat > something.txt
Click to expand...
Click to collapse
on the device, you need to become root to be able to use 'logcat'. 'adb logcat > something.log' would be the way to do it from a computer.
Anderson2 said:
Do I need to install a logcat app or just a terminal app?
Thanks for helping.
Click to expand...
Click to collapse
depends on how you want to go from here. you know that you can use either a computer or the device itself. so, what would be the easier way to achieve this?
a) 'adb logcat >futurelogfile.txt' would be nice, since it will redirect all logcat output to a file in your computer, ready for analysis; after this is running, just reproduce/wait for the bad behaviour ( on the device, ofc)
b) open a terminal app on the device, become root, run 'logcat > /sdcard/badbehaviour.log', go back to your homescreen leaving logcat running in the background, and reproduce/wait for the bad behaviour;
your choice.
EDIT: i wanted to remember stuff i knew existed, and i stopped by again to drop this link, for further reading on 'adb logcat' usage, if anybody wants to.
Thank you very much. That's very helpful. I'm already rooted.

Navigation gestures in Nokia 7 plus

Hi
Has anyone tried the XDA Navigation gestures app on the Nokia 7 Plus? If so can you guide me through the process that involves granting permission via adb. I did follow the steps as mentioned, but I am not seeing the desired results.
Thanks
I tried that too. I got "permission denied" or something like that.
yes, i use it without problem, with "8.1 June" and also "P DP2rev2"... for grand use exactly adb command what app show, if you have any problem then i think is with non functional adb and/or with badly rewrite adb command, try post output from terminal/command_prompt after you second try it
btw: you have enabled USB Debuging in Developer Settings on phone right?
edit: info about installing adb is here
I had a problem using the ADB. It kept saying "adb" wasnt a correct command. But I figured out that I had to type ".\adb" to make it work
Using it here without any major issues except sometimes a bit laggy

Is there a way to turn this pop up notification crap?

everytime I get a message or notification wether its whatsapp or whatever, it pops up from above and im sick of this!
is there a way to simply disable this feature? please any one
I know exactly what your talking about - i hate it too. Lucky I found the solution. Do you know how to use ADB? install the easy ABD thing, got into developer mode, connect ur phone etc. Then just run this ADB command:
adb shell
settings put global heads_up_notifications_enabled 0
exit
Done! Fixed! Sorted!
Dean F said:
I know exactly what your talking about - i hate it too. Lucky I found the solution. Do you know how to use ADB? install the easy ABD thing, got into developer mode, connect ur phone etc. Then just run this ADB command:
adb shell
settings put global heads_up_notifications_enabled 0
exit
Done! Fixed! Sorted!
Click to expand...
Click to collapse
MY MAN! I owe you!

Categories

Resources