I would like to use Googles UIautomatorViewer to analyse a third Party App running in a Android Virtual Device.
So far, I found a lot of toturials for the UIautomatorViewer using a real device and the ADB.
But is there a way to use a emulated device?
Thank you a lot in advance!
Yes. You can analyse emulator easily with uiautomatorviewer.
let me explain steps.
1) create emulated device from android studio and give it name ex. demo
2) Open cmd from emulator folder by typing "cmd" in search bar.
You will find folder here = "C:\Users\admin\AppData\Local\Android\Sdk\emulator"
3) Hit command " emulator #demo " it will open your emulated device called demo.
4) Now open uiautomatorviewer
Start analyse whatever you want on your device.
Related
I've been using this phone a while, and I have been through tough times with it. Two bootloops, Google Play Services crashing infinitely, weird errors, everything. I'd say I've "bonded" with this Samsung and would like to take it up a notch.
I've been looking everywhere for ROMS for this phone and I haven't been able to find any, not figure out how. Maybe I'm just stupid but man it's aggregating.
I have a PC, Samsung driver's, Odin, and of course, my Samsung. I have everything I believe is necessary to flash a custom ROM.
I would appreciate ANY help to get a nice ROM for my phone.
At the minimum, I'd like it to have a theme changer.
Samsung Galaxy Grand Prime One
SM-G53OT1
You can install CM 13 on your SM G5series
CM 13 is a custom ROM used in android devices.
your warranty will be void if you install a custom rom.
careful that installing a custom ROM would sometimes injure your device
permanently.
Follow these steps to root your device to enjoy vast features
Download a recovery.img,USB driver and ADB tools for your corresponding device(extract and install them and keep the extracted file in one folder)
Download and Copy the zipped cm13 and gapps6(arm)to your device's internal or SD storage
Connect your device to a PC in USB debugging mode(just tap 7 times on the developer options in settings to enable USB debugging)
open program files,open minimal adb tools.Type CMD in location bar to open the command prompt in that folder)
type "adb devices" in the CMD without quotes.
"fastboot recovery.img"
Your device will be reboot and
Team win recovery is opened
wipe the system ,cache,dalvik cache
select INSTALL from the option
choose the zipped file cm13 and swipe it to flash the custom ROM.
choose the zipped file gaapps and flash it by swiping.
Your device will be updated to marshmallow after rebooting
What is the best way to debug ionic 2 native features like the camera?
My app keeps crashing after i give permission to use the camera on my android device. Google chrome dev tools won't work in my case.
All help is appreciated!
The disadvantages of Ionic framework is hard to debug when call native plugin.
I have suggestion. Should you put breakpoint 'debugger' or "console.log()" before and after your function call Camera ?. And open chrome with url : 'chrome://inspect/#devices' to check what's happen ?
cheer!
Chrome did leave me with an error:
file:///storage/emulated/0/Android/data/io.ionic.starter/cache/.Pic.jpg exposed beyond app through ClipData.Item.getUri()
I do want to know how to fix this but i will start a diffrend question
I think that you could use chrome for debugging , steps you will follow :
connect your pc with your android or IOS device
open chrome and right click , then choose inspect
from the top bar choose more tools then choose remote devices
then click on your connected device in devices settings
write the command ionic cordova run android --device in your terminal to run your app.
click inspect your device on chrome
I can't find the answer to this question anywhere online and it seems like it should be super simple. I'm a beginner trying to run react-native on a virtual device, so I start by making the virtual device by running
android avd
Which opens the virtual device manager and then I can start my virtual device. But then I can't do anything else in the command prompt! I can't close it either or else the virtual device will close. What's the next step here that I'm missing?
My smart CS friend helped me. Instead of android avd, you should run start android avd.
Goodmorning,
I'm working quite hard on my own app. At this point I want to run it on my android (galaxy note 3) phone. Unfortunately Appcelerator studio doesn't detect my android phone; Windows does. I've tried it with the new Galaxy s7 of a friend, but same result.
Off course I searched the web like crazy and found several possible (old) answers, but none did the magic.
When I consult the log, there's no new info to be read!
Does anyone have a clue where to look? Looking forward to your answers…
Kind regards!
One thing you should check is if you have set up your phone for development. You can see the instructions here: http://developer.android.com/tools/device.html (... tap 7 times... - took me a while to discover!)
And the small obvious thing is in Appcecelerator Studio you may need to select "Refresh devices" when you try to run the project.
/John
When you say "Windows" detects it, what exactly do you mean? Does adb detect it?
If you run
adb devices
on the command line, does it report your device ID?
On my Mac, I run this and I can see my connected S4:
List of devices attached
9726ea90 device
I'm assuming that the Windows version of adb would output a similar report.
With all the Samsung phones I've debugged with, I always have to go to the notification bar and choose "connect as media device" (or something similar). The default connection mode does not work for debugging. And unfortunately, you have to do this every time you connect the device.
Is there any way to automatically launch an application on USB attach or CD insert on Mac OS X? it's easy on Windows, but I found that AutoRun.Inf does not work on the Mac at all.
You can't. Autostarting applications is impossible under Mac OS X.
The next-best thing, opening the CD folder and showing the installer icon, can be done by using (AutoOpen version 1.0) to make a .dmg which can then be burnt to a CD.
Basically, auto-run is considered a security problem and so is not supported in OSX. Sophie Alpert's answer is also a bit overkill. Most installers for OSX simply open up a folder to show the application and, possibly, a readme. Installing is done by dragging the app to your Applications folder.
For other kinds of apps on CDs (say, a slide show or something like that), the developer generally uses hidden folders to hide support data to ensure that the only thing the user will see when they open the CD is the single icon they're supposed to double click to start the app.
It is possible to install a background service that monitors whenever a USB device is plugged in and then launches an App. Google's "Android File Transfer Agent" is such a service that is running in the background and launches "Android File Transfer" whenever you plug in an Android device.
If you are looking for something for just yourself, you could write a small mac app that runs in the background and watches for a particular USB device (by id) to be attached and then run the program. Ideally a small XML plist could be used to map device IDs to the correct program to run. The XCode SDK has sample code that monitors for device additional and removal to get you started.
I agree with JavaCoderEx. I would crontab a task that looks for /Volumes/*/autorun.sh, then runs it once. Maybe touch a file in /tmp/ so you know its already been run, then remove it if the volume disappears.