Hi I'm developing an app that needs the most accurate GPS localization. Using the method that uses "kitchen sink" to show all Titanium's possibilities it gives me the network geolocation, can I have the device detection?
PS: The project is actually developed for Android, but will be soon ported to iPhone.
So, to clarify, you're basing your code off of this example? And the issue is that you are getting network-based geolocation, instead of GPS-based geolocation?
Have you tried replacing the preferredProvider with Geolocation.PROVIDER_GPS, instead of the string "gps"? As in:
Ti.Geolocation.preferredProvider = Ti.Geolocation.PROVIDER_GPS;
If you are using TiStudio instead of TiDeveloper you can use the sample project GPS to start with. It's bundled in the download so just fire it up and use that code as a working copy to learn from. It's android ready as well :-)
Related
Trying to get an android version of a react-native 0.61.2 app running...
The app intends to use react-native-geolocation-service but can not get past this error:
"Error: #react-native-community/geolocation: NativeModule.RNCGeolocation is null."
I understand that react-native-geolocation-service uses #react-native-community/geolocation on iOS but this is android. I have searched the entire project for the string RNCGeolocation and it's not there. How can I get running with react-native-geolocation-service on android?
For anyone dealing with this, i've tried every solution out there and still didn't work. I found that Geolocation uses a native location api (ou native module), and sometimes the problem is that the api seems not to be "there". So I installed react-native-location, that seems to provide (some of the same?) functions of that native api and, after that, I installed and was able to use #react-native-community/geolocation.
Hope it helps :)
I'm trying to develop an Android APP to discover and access onvif cameras under VS2017 and Xamarin.
By 'Add Web Reference', I added Web Reference of DeviceMgmt and RemoteDiscovery of onvif website.
For generated DeviceMgmt code, there is DeviceBinding class and when I set its url to e.g.
"http://192.168.0.22/onvif/device_service",
all functions like GetCapabilities() and GetDeviceInformation() can work.
For generated RemoteDiscovery code, I noticed there is DiscoveryLookupBinding class, but don't know how to set its url to call Probe().
I tried "239.255.255.250", but it's invalid.
If anybody has the related experience? Any ideas are appreciated, thanks.
For people who may be interested in.
Later for DeviceMgmt and Media services, I used Xamarin-generated references code.
But for Device Discovery, I created a Binding Library (Android) to still use my old java code. And it works well.
I am a beginner and I want to implement Phone Calling feature in an app for android and iOS. Using Phonegap ,Is it feasible in case of tablet formfactors also like iPad or Nexus 7 etc? From my understanding, Tablets do not support calling feature otherwise. Can some one provide an idea if we can leverage Phonegap plugins, if there is any such option there. Plus, please provide some insights on integrating Phone-cellular/wifi calling? Many thanks in advance.
Just try the code from this link http://rickluna.com/wp/2012/02/making-a-phone-call-from-within-phonegap-in-android-and-ios/
It will initiate a call in phonegap which will support for both IOS and Android.
Please use this function to open the mobile's dialled (both Android and iOS) and pass a mobile number as a parameter:
function callingFunction(mobile_number) {
window.location.href = "tel:" + mobile_number;
}
I am making an andriod app using 'andriod for processing lib" of processing (ie. running android mode in processing 2.0.3 and lauching it on my device).
Spacebrew (http://docs.spacebrew.cc) is a easy to use web socket library for processing , also availabel as javascript.
if i run the spacebrew example codes in andriod mode, the app gets launched in my device but doesnt show up in my spacebrew admin. whereas if i run the same thing in my mac, it shows up correctly. guess the websocket communication is not happening while using "andriod for processing". But this is the easiest way to use web sockets. So can anyone help me figure out on how to make spacebrew work in processing (android mode)
this is for my college project. any suggestions on how to get this running please? thankyou in advance
Thanks for pointing me to Spacebrew, didn't know about that!
I've just tested it from Android Mode and it does work, but there is a tiny quirk you might be missing out: permissions!
Normally, if your app uses extra permissions, the application's manifest allows you to use these. In Processing, that's also possible via Android > Sketch Permissions and in the case of Spacebrew, INTERNET is the permission you need enabled, as you can see below:
I just a did a test myself and it seems to work just fine with the amazon hosted demo:
Note that the Spacebrew Processing library uses the java websocket library, but only sets up a WsClient client. You can if you want use this jar in an Android SDK eclipse project and have your Android app act as a websockets server as well, not just a client (just in case this will become handy to you at some point in the future)
Okay here's the deal:
I want to download the full source of the MMS/SMS application that ships with Android phones. I want to be able to modify it, and add a little custom functionality to it.
I am developing using Eclipse, and I'm on Windows 7. I have noticed that there is now a Git for Windows, but I am pretty lost in it and not sure how to integrate everything with Eclipse.
Basically, I want to just get it to the point where I have all the source code visible in Eclipse and be able to see the app run JUST like the built-in texting/MMS app that is already on my phone. Then I'll know that I can modify it and proceed.
Any ideas?
Thanks!
There's a mirror of the SMS/MMS app on GitHub here. Just import that to Eclipse and customise away.
Unless you want to customize and use it only on your own phone (without publishing), this is not a good idea. This is because it uses classes that are hidden from the sdk. By default you won't even be able to build the apk via eclipse, but there is a way. The reason why this is a bad idea is that the hidden apis are not guaranteed to remain the same through different api-levels and your app can stop working with the next android update, and might also not work on previous api-levels. In-fact your app might not even work on selected phones running the same api-level.