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.
Related
I'm following along with the tutorial provided by the Android Developers official site and using the help files in Android Studio, but I'm finding out of date screenshots and feeling very confused and a little frustrated.
I have a Pixel 2 connected via usb.
I've enabled developer mode on the device.
I've got it not sleeping when connected via USB.
I've enabled USB debugging in the Developer Options on the phone.
...I just need to figure out how to get my Mac to see it via Android Studio.
The tutorial alludes to a configuration screen that I don't see in studio. I see something similar but the device drop down is disabled.
Hit the sync button,
Wait for downloads(don't stop the hidden downloads)
Restart if necessary, wait for the first invocation to complete work.
Then enjoy your first app.
Happy coding :)
answer: hit the sync button (elephant/mouse looking icon with a diagonal arrow), wait for downloads, don't stop the hidden downloads, then restart if necessary, wait for first invocation to complete, ...then it will (hopefully) work.
I've followed https://developers.google.com/web/tools/chrome-devtools/remote-debugging
and am fine up 'till "Step 2: Debug content on your Android device from your development machine."
I'm logged into the same Google account on dev and remote browsers in all cases.
I see the device w/serial number, and it displays the fact that Chrome is running on the Android device, but I do not get the Chrome version or URL entry field as shown in the screen shot.
This is Android 5.0.1, with current versions of Chrome on both the OS X 10.10.x dev machine and the Android device.
I have also tried with all combinations of Chrome/Canary on the dev machine and Chrome/Chrome Dev on the Android machine with identical results.
Thinking it might be a browser extension or something, I also put Chrome and Canary on a freshly installed OS X 10.12.x beta with no extensions etc. with identical results.
Obviously, USB debugging is on, but the device also requires me to select one of three modes for the USB anyway. Selecting "charge only" disconnects the debugger, the other two lead to this same behaviour.
So...
A> Is there something I need to do that's not in the instructions on the above referenced page?
B> Is it possible that the carrier (TracPhone, it's a throw-away dev machine) is doing something funky at the Android level to keep this from working?
Please be gentle, this is my first Android experience so maybe I'm missing something obvious to the old hands out there.
Thanks,
ssteinerX
I'm new to the Android OS and I am having trouble interacting with a virtual device. I've installed the Android SDK + Java + Eclipse and I'm trying to get a virtual device running and debug an apk I have.
I create a AVD and start it up and get this basic screen below but none of the other Android OS options you'd see on a standard phone. I can't even really control this device as the buttons seem to have no effect. I can't get into settings or see default installed applications, etc..
What am I doing wrong? I'd expect to have a basic clean Android OS startup when I launch these virtual devices but I get this funky screen and can't do anything with it, controls don't seem to work.
Worth noting I am doing this from a VMWare Workstation running Windows 2012 R2, not sure if there are issues if I'm running this all in a VM.
UPDATE:
OK so it appears I was using the Android 4.4W which I think is for wearable devices and why the OS was basically empty. I changed it to Android 4.4.2 x86 by cloning a Nexus 5 and now I just get a blank screen when I try to start the emulator. Here is a screenshot, any ideas?
Update:
You are using Android Wear API target, please try with regular android API (L preview or API 19 or below). I was able to reproduce your issue if i used Android Wear Target, it works if i used non-wear target. Android wear target is for 'wear' device types.
When configuring the AVD, you can pick different "skins" , please see below highlighted in redbox
If you are using a custom (or vendor) defined device type, go into AVD Manager -> Device Definitions and double-click your device entry, it will open the below window, make sure Buttons tab says Software
You can also navigate the emulator UI with keyboard shortcuts, often quicker this way.**
A. Ashoke is right about using skins, you may choose a skin when you create or edit the emulator. Here is a screen-shot. Check the 'skin' dropdown. (It may not be available for some 'devices' you select here.
You are using VMWare, so you might be behind a proxy. You may need to provide proxy, using following steps -
Click on Menu
Click on Settings
Click on Wireless & Networks
Go to Mobile Networks
Go to Access Point Names
Here you will Telkila Internet, click on it.
In the Edit access point section, input the "proxy" and "port"
Also provide the Username and Password, rest of the fields leave them blank.
When you will load it for the first time, it may again ask for your credentials. So provide there as well.
I'm using a mac machine to build a android application, but it will crashed when run on device. but with the same code and key I build the application using another machine (windows). it is working well on devices.
Using my mac I already build several other apps and those are working well.
Can any one give me a solution?
First get the feedback of your client device as Kumar suggested.
get the clients device specifications,screenshots and try to reproduce on emulator.Exactly what caused the error may want you to ask him what steps to follow to reproduce the error.etc
is it possible to test this app on emulator with out any code changes?
Yes.You have a DDMS perspective.Just go to the top right corner above the coding window.There's a sort of plus (+) button there.From there you have a DDMS perspective.In this perspective,you can control emulator.You can feed the GPS co-ordinates here.
Look at this
Sounds like you are using some new API that your client doesn't have. He might be running an older OS. Run Android Lint checks and see if you get an API warnings.
Check your client's OS version and your own. Create emulator with your client's OS version and see if it's crashing.
I have installed Mono for Android setup, I was able to follow through the Hello World example, I have the Android SDK Manager working with my AVM's I can even start an emulator when prompted during deploy -> select device selection. Howerver, once the emulator starts it never shows in my Select Device list, so I can't really test anything by pushing it to the emulator.
Am I missing anything? Is there any other way to deploy a compiled package to android emulator when using VS2010/Mono setup?
Thanks a lot for your insight.
I had similar behaviours in Netbeans. Here is what I do:
After the emulator has started the first time, it is "locked". Just unlock it by dragging the green thingy from left to right. Then just press "RUN" again in the IDE.
Sometimes, it works to just hit "Run" again without changing anything. Just wait a minute after trying the first time.
I discovered that being patient with the emulator often helps :)
In my case, I had to be running VisualStudio as an admin in order to get the running emulators to appear in the list.