I am trying to integrate the multi window feature provided by Samsung Mobile SDK in my android app. I am following the MultiWindowSample given by Samsung. The sample independently works perfectly fine but when I integrate it in the app or call the same activity through the app, this call
SMultiWindowActivity.makeMultiWindowIntent(intent, SMultiWindowActivity.ZONE_A)
simply launches the chosen app (acquiring the full screen) without any MultiWindow view at all.
Is there anything that I am missing out or any constraint that I need to take care of? I am testing it with Samsung S4 which supports MultiWindow.
Related
new freelancer dev here.
I've been developing an Android App with Android Studio as apart of some freelance work I've been doing. I do all my testing and debugging on a virtual emulator of an android device while my client reviews the app on his tablet after the testing is done. With this latest version, everything worked perfectly on my emulator, but the app won't even start on my client's tablet. He tried testing the app on a different tablet and while the app runs, it doesn't function properly (Such as buttons not running different methods, crashing after specific inputs, etc.). We are both very confused at what is going on and don't know how to begin tackling this problem. Previous versions of the app work, but they do not have all the required functionality. Nothing major a lot was added or changed from the last version and this most current version. The app has worked on a variety of different emulator settings as well.
I am using the Android Studio built in emulator tools for testing and using Android Studio as my IDE. My app is written in full java while using XML for the layouts of the different pages of the app.
I'm not looking for any immediate fixes/solutions, but more of a general direction to go, because I don't even know how to start fixing this issue.
Also, I'd like to reiterate, previous versions of the app have worked perfectly fine, and all versions of the app work fine on my emulator. The most recent version only fails to start/run properly when run on my client's tablet(s).
I've tried matching my emulator to my client's tablet as closely as possible to try to recreate any potential issues, but I haven't been able to get any of the errors or bugs to appear during debugging. Since we're pretty far apart, I haven't been able to have access to either of the two tablets that he has tried running the app on. My client formatted the original tablet that he was using to test the app but is still having the same issue of the app not starting.
I've written an android app in Android studio, and would like to add android wear functionality. I've looked into it online, but I can only find help on how to make a stand-alone android wear app. Is it not possible for me to just add a new activity to the application that is used by the smart watch, or do I have to create a whole new app for the smart watch that requests data from the main phone application?
It depends on what it is you need the wear app to do?
In the past I have decided all I actually needed was the ability to respond to notifications on the watch so therefore I just modified the notifications to work well on android wear.
Example. https://developer.android.com/training/wearables/notifications/creating.html
But if for example you need the ability to start the app from the watch and work without any phone interaction, you will need to create a stand alone android wear module.
I am trying to create Phonegap app that runs in a "kiosk mode" that won't allow the user to either leave or close the app, have acces to the notification bar or use anything else than the app we created.
The idea is that we incorporate a tablet (samsung galaxy tab 4 10.1) in an endcap which will then be placed in certain stores. Whether or tot the physical buttons on the tablet will accessible to the user has not be defined yet.
I do have experience with Phonegap but i have no idea on how to accomplish this.
So far i have tried several guides and resources, i.e. this one: http://www.andreas-schrade.de/2015/02/16/android-tutorial-how-to-create-a-kiosk-mode-in-android/ or solutions as SureLock but without succes.
The tablet we want to use: samsung galaxy tab 4 10.1 (SM-T533)
Android version: 4.4.4
Phonegap version: 5.1.1
Cordova Kiosk Mode - Cordova plugin to create Cordova application with
"kiosk mode". App with this plugin can be set as Android launcher. If
app starts as launcher, it blocks hardware buttons and statusbar, so
the user cannot close the app until the app request it.
https://github.com/honza889/cordova-plugin-kiosk
Kiosk mode is highly platform specific. I'd recommend building a native app instead of using phonegap.
If you absolutely want to use phonegap you'd have to implement these hacks inside a plugin (which is in fact native code, so you don't gain anything).
Is there a way of telling, within the application the spcific device model that the app is being run from. For example for it to be able to tell the difference if the app is running on a Nexus S or a HTC Desire or the Samsung Galaxy Tab?
This give name of overall product
android.os.Build.PRODUCT
You can also try others by Build.*
I'm currently only using the Honeycomb emulator to test a new Fragment-based release, which requires the LVL licensing service. However, every time I start my app on the emulator, it fails the licensing test and my emulator cannot add Google accounts, so I can't try that way either.
How can I get it to work?
I believe that nobody has been able to get the LVL libraries working on any emulator except 2.2. See this posting and this issue report.
I am having the same issues with LVL... however to create the google account on your emulator make sure you create it with the google libraries.. IF you create the emulator with the google libraries you will get the google account set up when you create accounts.