Turn On Live updates By default in Android Studio Database Inspector? - android-studio

How to have live updates on database inspector as a default setting when running app?
At the moment I have to manually click the tick box for each of the tables I use every time the app is launched.

Related

Android Studio , how to control a website through a mobile app

I'm new to Android studio and i was wondering that, how can I control a website through an android app.
For example: there is a listbox on the website with values and I want to select a value through my app
and press a submit button ,without opening the interface.
is it possible?
You should connect your application and website to same database on server.with application you change the values on database and you can see the result on website.you will need related libraries or classes to implement network connection between android app and server like:retrofit or volley

Can't add an existing database to a project

I have a SqlServer Compact Edition database that I developed and use in a project. I want to use the database in a new application. I create a new project, click Project|Add New Data Source. I choose Database/Dataset. On the "Choose your Data Connection" screen, I click the New Connection button. On the "Add Connection" screen, I select my Data Source, SQL Server Compact Edition, and click Browse under Connection Properties. At this point, I get a message that Visual Studio has stopped working, and is restarting. It then shuts down and restarts.
I have used a database created in one application in another several times without a problem.
I have uninstalled VS via Programs and Features, and reinstalled it, and it still does it.
I have tried vs_ultimate.exe /uninstall /force. That does not give me the option to uninstall, it just reinstalls VS.
I'm using VS 2012.
What's going on?
Thanks

Android Studio won't run application from studio ide?

I've got an application I've been working on and am having an issue with android studio. When I click "build->run" and then select my device, the application never runs on my phone (and the log in android-studio that automatically comes up does not have anything, whereas in the past when I have used this feature it usually says something like, "waiting for phone..." and then the application pops up and automatically opens on the phone and you get some other pertinent information). I have the phone already in developer mode with the install from unknown sources set to on. When I manually move the application from its gradle build location to the phone and then install it manually in file explorer, all is well and the application performs as expected. As I need to debug, however, this is not a very viable solution. Anybody have any advice as to how to get it to run from the IDE? I have tried rebuilding and invalidating the cache/restarting android studio, to no avail.
When I click the run tab at the bottom I have an empty window. When I click the debug tab, I see:
Waiting for device.
Target device: samsung-samsung_sm_g920a-randomIntegerId
Uploading file
local path: /home/eric/Documents/class/OOSE/final_project/2015-group-17/project_code/android/Place2B/app/build/outputs/apk/app-debug.apk
remote path: /data/local/tmp/oose2017.myApp
Note: I am building the application on a LUbuntu 15.04 VM on a windows 8 host, and am using the latest version of android studio.
EDIT: gradle console indicates a successful build as well (obviously since moving the .apk manually to the device works properly).
Open 'Run->Edit Configurations...', and look for your app module in the column on the left-hand side.
Select it, then go to the 'General' tab.
Under the 'Activity' section, there are a couple of radio buttons. Make sure that 'Launch default activity' is selected.

iOS7 Testing Background fetch in Simulator?

I know there are ways to do it with XCode 5 but is it possible with my infrastructure?
I'm using Visual Studio 2012 and MonoTouch.
In XCode I can go under Debug > "Simulate Background Fetch" or there is also a second way: XCode Menu, "Product" => "Scheme" => "Edit Scheme" enable the option "Background Fetch".
Unfortunately this is currently not possible in Xamarin Studio/Visual Studio.
But we're working on it, and it will be included in a future release.
I noticed the new update of Xamarin Studio 5.0 included Background Fetch support. (http://docs.xamarin.com/releases/studio/xamarin.studio_5.0/xamarin.studio_5.0/)
When debugging using the simulator, go to Run->Simulate IOS Background Fetch
This can now be done in Xamarin Studio only and only using the iOS Simulators. Make sure your iOS project already has the Background Fetch permission selected (in your iOS project properties or manually in your info.plist). Then, in Xamarin Studio, you choose Run -> Run With -> Custom Configuration -> Select Background Fetch -> Run
That will launch your app in the background and will force a background fetch to happen.
Once you do that, you should not have a separate option listed under your configuration dropdown for iOS. There should not be a .iOS and an ProjectName.iOS - Background Fetch option in the dropdown. The nice thing about this is that, after selecting ProjectName.iOS - Background Fetch and running the app, while the app is still running, you can go to Run -> Simulate iOS Background Fetch to run the fetch multiple times. This option is always greyed out for me if I run my app using the Custom Configuration window though.

How to Reset Remote Debugger Connections in VS2012 Once Set

In Visual Studio 2012, you can select Remote Machine from the Build Toolbar
On the first click, the Remote Debugger Connections dialog popups up and allows you to set where you're debugging against.
The problem is once the value has already been set, navigating to Remote Machine or right clicking anywhere on it will not allow you to change the original configuration.
The value from that popup is stored in your project file. You can access it by going to the Debug tab on your project properties. You can change the value there, or if you clear it out, you can get the popup again next time you navigate to remote debugger

Resources