I have tried everything I can think of and everything I have looked up online. None get me progress. On the phone I have activatied developer mode, I am using a cord that can transfer files, and I have given computer permission to access my phone. On the computer end I have updated every thing I can think of and I am able to see my phones storage from it but the device does not appear on android studio.
The laptop runs on Windows 8 (unfortunately).
Ask if any other info is needed.
Thank you in advance, I'm getting desperate.
CHECK IF YOUR DEVICE API LEVEL IS LOWER THAN THA APP MINIMUM API LEVEL
it might happen that the app you are building is build for a higher android-version. like if you are building an app for api 21 and your device is have api level 17 then it wont show your device in the list of connected devices. once i faced this problem
Related
I have downloaded all the API versions. Here is what my SDK Manager tab looks like.
But when I try to create a new Virtual device I do not see the option to create Virtual Device other than API 28 and API 23.
My Virtual Device Configuration Page looks like.
This is what I want
How can I get the multiple options to create Virtual device with different API level (Oreo, Nougat, Pie etc.)
VPN was the culprit.
I was in the enterprise network and and I was using VPN. I did not realize that VPN was restricting the AVD manager to show the available SDK platform for download.
Solution?
I simply turned off the VPN, reopened the AVD Manager and it worked.
I have worked many years in Android Studio but recently I started using VPN. So I was not able to figure out what went wrong. It seems a silly question but hope it helps someone someday!
attempting to run the saferoom demo running against an emulator defined as Pie (API 28). using android studio 3.4 on a Lenovo Windows 10 Professional system. sdk for API 28 is being used.
At open the app shows the message "You do not have a secure keyguard!" as a long toast on the emulated screen.
How is this corrected?
no change to the code from Github clone.
resolved by opening settings in the emulator and setting a pin number for log on to the emulator. However - each time the emulator is restarted, the settings need to be changed again. Maybe there is a way to control this in code or some setting in android studio?
What I meant by "the settings need to be changed again" was a mistake. Once set up with a pin, the emulator does retain the pin across restarts. The app itself asks for the pin. Apparently pin, password, or fingerprint must be set up through the settings app in the emulator at least once in order for the emulator to have a secure keyguard. for my app, requesting the pin at startup is a good thing.
Thanks for the question. it helped clarify things for me.
Eclipse is not detecting my phone. It's a Samsung Galaxy S2 HD LTE, Android version 4.0.4. Working in Windows 7. I have enabled USB debugging and updated the driver for it, but when I go into Eclipse Run --> Run Configurations --> Target it is not listed.
Not sure if this is relevant but I heard in another thread that the build target for your project has to be <= to the version of your device. If this is the case, all the options here are higher and there doesn't seem to be a way to add another so I'm not sure what to do. Also checked the manifest file to see what the min SDK is. It's 8 (which corresponds to android version 2.2) so that is fine.
I'm wondering if it has to do with "Android" being listed under Other Devices in the Device Manager (as per image below). I'm not even sure what this is. The phone itself says it's already updated, but when I try to update Android it can't find the driver software.
Another issue could be that when I connect the phone to my PC, it lists it as a camera instead of a mobile device, and displays the message "Connected as a camera" on the phone itself. The first time I connected, it also showed some error message about how device was not installed properly, but I haven't seen this message again and so not sure what to do about that, or that stupid Autoplay window that pops up every time I connect.
If you have any ideas please let me know!
Check if your Android Composite ADB Interface is correctly installed.
You can refer OEM USB Drivers and Debugging on real device for more details.
I've been having some trouble getting my Arduino ADK to work with my Toshiba Thrive (or AT-100 in EU). It's running 3.1, but I'm aware in the US there has been an update recently to 3.2. Unfortunately the 3.2 update isn't available in the EU yet. I'm wondering if there is anyone who has successfully got this working on 3.1 or 3.2?
So here's the deal. I've used the API level 12 libraries to suit the 3.1 build, but had to manually edit the AndroidManinfest.xml file so the minSDKversion and the targetSDKversion both read 12, as was mentioned by John regarding the Samsung Galaxy Tab problems.
However, unlike john's issues, I've been able to get the DemoKit app to compile and install fine, except for 8 warnings regarding the color wheel LED controller values not being used.
The screen even loads up on the Toshiba asking me to attach the ADK, but when I do it does nothing. I've tried resetting and unplugging and re-uploading the firmware to the ADK board.
Like John, I've also tried changing the Accessory API's from com.android.future.usb to android.hardware.usb along with the manifest file, but now it doesn't even install, giving the error message INSTALL_FAILED_MISSING_SHARED_LIBRARY, with Logcat saying W/dalvikvm(18874): Refusing to reopen boot DEX 'system/framework/pm.jar
I feel like I'm so close but there is just one small thing wrong. Can anyone shed any light on this?
There possibly is an answer here:
http://www.thriveforums.org/forum/toshiba-thrive-development/5410-arduino-adk-demokit-application-3-1-thrive-100-a.html#post58900
Havent tried it out myself though - will do it if i don't find any other option.
I am testing facebook Single-Sign-On application.
I am using android platform 2.2 and api level 8. I have similarly created emulator with the same configuration. It is working fine in emulator. But when i test it on actual device that is HTC Desire HD ver 2.2 froyo updated. It opens up a dialog with facebook as title and shows loading screen then disappears.
I am unable to understand the reason for such behavior.
Please help me on this.
Regards,
Pankaj
You need to get the debug on device working and see the error that appears in LogCat.You can find instructions oh how to use debug on device here
You can plug in your device using the usb cable (making sure usb debugging is on in the options).
then debug your application and you will see what the cause is in the debugging console.
I suspect tho your problem is to do with how you are transferring the apk file to the phone (it needs to be signed for facebook SSO to work and you need to have set the key correctly in your facebook app).
See here for more information:
http://www.juje.me/2011/04/export-the-signature-of-your-android-app-for-facebook-api-use/