This question already has answers here:
Device File Explorer option missing in Flutter Android Studio
(10 answers)
Closed 2 years ago.
I'm a beginner developer and I use flutter, I wanted to download databases inside my app in the emulator within Android Studio.
But no matter where I search, I can't find the Device File Explorer in the android studio, the only thing I find about it is in settings and it's a completely blank page (there is only the path where to download things).
For Normal Android Development, it's easy. Just go to
View -> Tool Windows -> Device Manager
But in Flutter Development, it's a little bit tricky.
First you have to Configure your Android Development with Flutter to see the Device Manager option.
Steps:
Click on the bottom right option where it says Event Log and then Press Configure Now
Done!
No go to the same path again which was
View -> Tool Windows
and here you can see the Device Manager is visible now.
You can just use your real device to test and It will be better.
Just connect your mobile with usb to your computer.
turn on USB debugging in developer mode.
you will see a dialog box in mobile just allow and you are ready to use it.
Hope it will be helpful I suggest it coz once when I was trying my app in emulator it was working fine but when I have tested it on real device many things were not working and I have to start my project from scratch. So I suggest to test on real device and in addition you will easily get file explorer and more.
Related
I am using android studio 3.3.2 and try to test the app on mobile device. I am using haweii mobile. i try to find the solution but nothing help me. I found a lot if solutions on stack but these solutions did't work? Is there any one who could help me to find out the problem?
1- connect mobile to system
2- allow permissions
3- go to mobile settings
4- go to about
5 -then click 7 time on build number
developer mode will on
then there will be development option
go their and click USB debugging on
Hope so it will wok for you
When clicking the Create New Hardware Profile button or the Clone Device button in Android Studio AVD (Windows platform) neither button does anything. In looking for any log files which may indicate what is going on, I located the following folder and do see that upon launch, two thread-dumps are generated, but no logs are written when attempting to perform either function.
C:\Users\Bob.AndroidStudio2.1\system\log\threadDumps-20160718-072320-AI-143.2915827\freeze-20160718-072340-10
I have read through many posts on this and similar issues with AVD, including a defect from Google that was posted almost 2 years ago. I have yet to find any solutions or work-arounds that will address this issue.
Has anyone found a way to fix this?
I was never able to resolve my issue while working with Android Studio in a Windows environment, so my resolution to this was to build/use a system which is running Ubuntu and now everything is working perfectly.
I am trying to test a website responsiveness to see if it works fine on Android devices, but I don't have an Android device. Is there a way to test website responsiveness on Android Studio? I have already tried resizing windows and all those websites that do that. What I want is a software that emulates the Android operating system. If yes, please share how. Thank you.
Yes, you can test a responsive website using Android Studio's emulator. Here are the steps to do this:
Download and install Android Studio - https://developer.android.com/studio/
Launch ADV Manager (Android Virtual Device Manager) within Android Studio and create a new virtual device
Click the play button to launch your app. Choose the device that you created in ADV
When the emulator opens, close the app that opens on the emulator and navigate to the web browser on the device. You should be able to test your website without issue now.
If you run into problems, make sure that you have all updates installed in Android Studio.
Here is a reference that you can use to get the emulator up and running: https://developer.android.com/studio/run/emulator
Open a Chrome Browser -Right mouse click and select Inspect Element.
To the right of the tab Elements is a picture of a phone. Click That. Then you will see the browser resized.
Go to the top drop down menus on top to get some awesome choices.
Select one of the options from the Device drop down.
Then select one of the options from Network drop down.
Reload the page while doing a speed test from the far right tab.
Then you have a single user analysis of your app. For multi-user tests use JMeter.
i m starting (or at least trying to) developing android application(s) and I m using eclipse for it along the android sdk.
Now I m wondering if there's a faster way to "test" and tryout something newly writen in the code than starting it in the emulator?
I'm wondering because I m running on 8gb ram and q9550 (quadcore) and it takes some time (let's say 20secs) to upload and start the apk and now
I'm wondering if this really is the only way to test since it requires huge amount of time, especially when I'm trying something new which doesn't work and thus I'm always gotta run it like this let's say like 20 times until I figure out what's wrong with my code...
You can connect your android phone using USB debugging mode and debug your code. If you can't do that, you can export an apk file (which is quick) and use dropbox/gmail to send it to your phone. I am not a big fan of emulator :)
Here's how to enable usb debugging
http://www.groovypost.com/howto/mobile/how-to-enable-usb-debugging-android-phone/
I would recommend running on your device rather than the emulator.
http://developer.android.com/tools/device.html
In short:
Turn on "USB Debugging" on your device.
On the device, go to Settings > Applications > Development and enable USB debugging (on an Android 4.0 device, the setting is located in Settings > Developer options).
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If you're developing on Ubuntu Linux, there is a detailed guide in the link above.
Now in eclipse, your device should be available to run on.
In the eclipse toolkit, you have the option to run it directly on a device. It's rather quick to do so.
Enable USB debugging as well as installation of apk from sources other than the market. Then assuming you have already setup the required drivers/settings to connect to your phone via ADB, you should be able to run it on the device and debug. In the run dialog, it will list all available devices and you can simply select the one you want to use.
If you already have a run entry (i.e. you've already run your application),
select your project
click Run -> Run Configuration
You should be in your application run configuration (on the left under Android Application -> Your_App).
In the Target tab, you should be able to select your device. It will likely already be in "Automatically pick compatible device...". On my setup, it will run directly on my phone if it's the only available device. You can select Always prompt to pick device which will let you choose every time.
Eclipse plugin (ADT) information: http://developer.android.com/tools/help/adt.html
Information about setting up your device: http://developer.android.com/tools/device.html
I know android emulator is too slow.
You can either use device or
try bluestacks it saves lots of time.
User device only when you want to test your app for particular device.
Here is what you are looking for :
http://developer.android.com/tools/device.html
To summarize:
Plug your phone to your computer with a USB cable.
Make sure the drivers are installed and your phone properly connected.
Make a Ctrl + F11 from eclipse.
It will build the apk, transfer it to your phone and then launch it automatically.
If you have unit tests, Robolectric lets you run them without using the emulator or the device.
you can download bluestacks as emulator, as it is really fast.
after then make settings in eclipse as window->preferences->android->build -> then uncheck the 3rd checkbox written as "skip packaging and...", then apply and restart the eclipse to take effect.
now open the bluestacks in background and just double click the apk file in bin folder of eclipse and bluestack will install it in 2 to 3 secs and you can directly see the result.
NOTE here that you have to only save the file ,you working on in eclipse and only double click on apk, and result will directly appears to bluestacks. Without uninstalling and reinstalling apk in bluestacks.
and you can delete your apk also, it automatically immediately create
a fresh version of apk (thus not required) as soon as you save all your files apk will be updated.
Google BlueStacks.
It runs on Windows and it's really fast.
my problem : the app I have uploaded into my cellular device is shown without the pictures I have insert to it .
steps I have done in order to install:
I have inserted the xxx.apk file into the device via usb
I downloaded an apps installer via the Market
I opened the app using the installer and instead of picture an white background appeared
when I opened the xxx.apk file using file system I found the pictures.
note: even an application icon weren't appearing.
Apparently the res libary having problem to be bined to application.
I might ness to add something to my appliction manifest?
I might need to change something on my device ? (I already made a change and enabled user's not Market application )
I would be very grateful for some life saving answer I need to show my work in a few days in this is the first time i tested her on a real devise.
I also tried an example as shown in hello android book the same example worked perfectly on the emulator where on my android device (Motorola milestone ) the picture and icon weren't shown
Please tell me what I might be doing wrong guys I need to apply my project back at uni(I was the only one in uni who did it on android and in my country most of pep don't even know what android is so getting help outside of forum's like this is not an option ) so please please help me .
I don't know what app installer you downloaded from the Market, but you shouldn't need it. You should be installing the app to your phone using the same SDK tools you used to install it to the emulator. Ie, using Eclipse or the commandline "adb install" commmand.
I'm assuming you used the SDK tools to install the app to the emulators? In which case, start there. Start with looking at what you're doing different between when you installed unsuccessfully to your phone and when you installed to successfully to the SDK.
In my experiences so far, there should be very few differences between working with the emulator and working with the phone.
Well, something is wrong, but what is hard to tell from your question. What pictures are you talking about? Your drawable resources? My guess would be that your application works in the emulator (you have tested it?), but that it doesn't on the phone you're testing with. Have you checked the logcat output?
If you're developing from Eclipse, why not try a debugging session using the phone rather than the emulator?
Hard to narrow down without more details, but a few notes:
Pontus has a point - what's your logcat output? You can use logcat on a real device. Maybe not yours unless it's rooted, but with many phones you can.
Do you link the drawable to your app in the manifest file?
How do you test on emulator vs. device? Do you right-click the app and choose "Run As -> Android Application"? Do you do that for both emulator and device?
When you run on the device, do you first sign it? If so, can you verify the jar/apk and see the contents? Is the drawable under res/drawable?