Oculus application enable mode developper for oculus quest 2 - android

I'm facing a really weird bug in oculus application for android devices.
I have 6 oculus devices and I'm developing a project using unreal engine 4 everything was normal until sudelly my oculus device all of them refuse to connecr with UE4 or even side quest ( no device found showing in side quest) i tryied to install and desinstall th ADB but always showing the same problem no divices found I did a lot of research and the only solution is to enabled the mode developper in oculus app ( I enable ot the first time I connecr to the occlus App for the 6 devices ) I open the app but I could'nr find the mode developper at all it was there like 2 days ago and now it's gone I try older verson I install it in different verson of phone but I get nothing please dose anyone face this problem before or have no idea because I'm stuck in this for a while and couldn't continue developing my game
Ps : I tried to factory reset all the occulus device and create new account with facebook connect it to tha oculus App but still the same problem

I had a similar problem where I couldn't find the developer mode option in the headset settings of my Oculus app on my iPhone. I saw the pinned comment on this video which said that as of Feb 2021, Oculus requires developers who have an Oculus developer account to verify their accounts using their credit/debit card. I went to my Oculus account, profile>payment methods. I then added my credit card and now the Developer mode option appears on my phone app! Turn this on and if you do adb devices on your terminal your quest headset should show up.

Related

Installing app in Android emulator shows "This app is not available for your device"

I'm trying to install a Google Play app on an Android emulator on a Windows 10 machine, but see the message "This app is not available for your device". I've tried creating different virtual devices (Pixel 3 w/Play Store, Pixel 4 w/Play Store, Nexus 5 w/Play Store, etc.) with different SDK versions (Android 9.0, 10.0, and 11.0) using both Android Studio and Visual Studio, but all result in the same message.
I've tried the "Clear Cache" and "Clear Storage" tricks on the virtual device's Google Play app, but that didn't work for me.
If I load Google Play Store in a Chrome browser and find the app, I get the same message, but I also see that my device that is incompatible is named "Google sdk_gphone_x86". I've also pulled up the same app in an Incognito browser window and it looks like it will install, but once I sign in to my Google account, I get the same message.
Other coworkers are able to install the app with a similar configuration so I know this app can be installed. It looks like it may be connected to my Google account.
Does anyone have any suggestions of what else to look at?
After several days of troubleshooting, I finally found the answer so I thought I'd post here for anyone else occasionally experiencing this problem.
For some reason, this particular app didn't work with Hyper-V hardware acceleration. In order to finally get it working, I disabled Hyper-V and installed HAXM instead.

Issues testing a media app in development mode

For a couple of days recently, I was able to get my (prototype) media player app to show up as a menu item and run in the Android Auto app, in the Desktop Head Unit, and on my car. This is an app built and installed using Android Studio and run on a phone in developer mode with Android Auto in developer mode with the head unit server running. Older reports on StackOverflow say that uploading to Google Play is necessary to test an app in a real car, but I did not find this to be true.
However, recently, it stopped working (on the Android Auto app and the car, have not tried DHU), and I do not understand what has changed. I suspect the issue might be related to signing my app, because it only started working when I started signing my app. The only clue I have are two cryptic messages in the log, which I also saw before I started signing the app.
I Finsky : [25252] ude.dispatchTransaction(7): PlayGearheadService <my.package.name>, app owners empty
W CAR.VALIDATOR: Package DENIED; failed all other checks [my.package.name] [CONTEXT service_id=13 ]
The problem turned out to be simple. The Android Auto app developer setting "Unknown sources" apparently was reset by an update. Enabling it fixed the problem.

Robot Pepper Not able to run Android application on Real Pepper

I have developed an app for pepper using android studio. the app run fine on emulator, but cannot run it on real pepper robot. I have connected real pepper robot through IP, but when I run through android studio cannot find the real pepper robot tablet in the list of devices.
From android.aldebaran.com site under connecting to real pepper its say
Developer mode should be activated.but couldn't find any such option on real pepper
kindly help with above querys folks
You can't simply skip the activation of the developer mode. You need to set the developer mode in the settings of the real pepper tablet. Check out this manual.
To show the settings on the tablet follow these instructions (Source)
Open a terminal
Connect to Pepper using SSH (ssh nao#PEPPER_IP, ...)
Run the followin command
qicli call ALTabletService._openSettings
-> The Settings menĂ¼ should now be opened on the tablet.
There should be something like this:
If you can't do this, you can't go on...
We had this problem and the cause is that Android apps controlling Pepper is only possible when Pepper is running version 2.9, and it looks like you're on 2.5 or earlier.
However, there's no apparent way to upgrade to 2.9 - we had to fight with Softbank support to get a pre-release version installed, and one robot had to be shipped back to get fixed after doing so. Even now, it doesn't appear to support any of the 2.5 Basic Channel activities.
Since ~August last year we have had two robots on differing versions on 2.9 (2.9.0.129 and 2.9.1.36), neither of which have received any updates.
The Aldebaran community forum appears to have been disabled. Though you can get to individual posts from Google, there's no navigation.
The Android plugin and emulator were updated towards the end of last year, and their Android documentation seems to have improved in recent months, so there's hope that something is going on, but it's hard to find anything public.
To activate developer mode on the tablet, you should follow this steps:
open a terminal (Putty )
add nao#xxx.xxx.xxx.xxx x is your robot ip
press 'yes'
enter your robot password
enter this code: qicli call ALTabletService._openSettings
That code open the tablet setting on the tablet of pepper. Then the procedure is same as smartphone.
When the setting on the tablet opened follow these steps:
Go to 'About tablet'
Scroll down to find the Build number, then tap 5 times quickly. You
should see the toast opes and say that developer mode is activated.
Then go to Developer option and activate it.

Connecting cellphone to android studio for developing

Trying to get my phone connected so I can use it to test things I am trying to develop. My phone is LG G3. I verified that it is in developer mode. When I connect it to my computer I see the phone in the device manager.When I right click on it and choose update driver, and search online for update I get a message that I already have the latest version installed. When I open Android Studio and connect my phone it doesn't show up in available devices. Does anybody have an idea what I am missing?
After much searching and advice I finally managed to find the driver that I needed.
In the interests of helping anyone else who runs into this problem, here is what I found:
Go to the LG UK site: http://www.lg.com/uk/support/software-firmware
Select your model number
On the page that opens there are a few options for updating. I chose option 2 (USB Driver), and downloaded the installer.

Whitelisting ChromeCast: How to turn on developer mode

I just received my ChromeCast and I am wanting to start developing with it. The problem is that in order to integrate it into your app and use it for testing, your device must be whitelisted. This process can take up to 5 days and it should be just a simple form to request whitelisting:
https://developers.google.com/cast/whitelisting
My issue is that in order to register it, I need to retrieve the device's MAC address from the Debug view. To access the Debug view I have to enable "Developer Mode". Step 2 in the process states:
On the Apps label, click seven (7) times. The message, "developer mode
enabled" appears.
but inside the ChromeCast app there is no Apps label? Has anyone figured out how to turn on developer mode yet?
--UPDATE--
The original instructions on the Whitelisting page were meant for the Android App and I was using the Mac app. Inside the ChromeCast Android app, if you click the Apps label 7 times it does enable Developer Mode.
In the Mac version you can find the Chromecast MAC address in Device Settings.
Plug in your Chromecast - make sure it has power and is setup. Download the free "Chromecast" app from Google Play.
The app will find any devices on the network. As of this writing the app will show what devices it finds at the top of the screen. At the bottom it show's "Apps" including YouTube, Netflix an Google Play Movies & TV.
If you tap on the "Apps" header 7 times it will put the device into Developer Mode as described.
The Windows version of the chromecast app shows the MAC address to the left of the help button in the device specific screen even without developer mode.
In new ChromeCast app click on DEVICES Tab 7 times. It will enable devloper mode.

Categories

Resources