I have a Sony Xperia Z3 and I love the Lifelog. I have won a smartwatch samsung Gear S2. The problem is that I can not do Gear and Lifelog work together. There is some step-by-step I can use to configure the app with smartwatch?
thank you
Fernando
Unfortunately unless there is an app written for the Samsung Gear S2 you will not be able to pull Lifelog data using the watch.
Related
I am looking for a safe privacy-protected alternative to google apple microsoft nokia blackberry OS's. Thank you.
Ubuntu touch. But there are only few phones that run it.
Is it fair to assume that if we tested on these platform, we've covered all QA requirements?
Our assumption is that testing on 7.0 is the same as 7.X, and similarly for Android, testing on an OS like Gingerbread would cover all 2.3 variants, and similarly Jelly Bean would cover all 4.1-4.3. Our assumption is that there isn't much difference btwn the variants.
Please advise on what good coverage is. Thanks.
iPhone 5C/7.0.4
iPhone 5S/8.0
iPhone 5/6.0
iPhone 5S/7.0.4
S2 Skyrocket/2.3.5/GINGERBREAD
LG Nexus 5/4.4.2/JELLYBEAN
Samsung Galaxy S4/4.2/JELLBEAN
HTC One X/4.0.3/ICE CREAM SANDWICH
Samsung Galaxy S3 Mini/4.1.1/JELLYBEAN
Samsung Galaxy Tab 7.7/3.2/HONEYCOMB
Generally testing on any of the variants of the following will be sufficient for passing QA:
iOS 4/5 (if you decided to include support for these)
iOS 6
iOS 7
Android 2.2 (if you decide to include support for it)
Android 2.3 (any one of 2.3.x will work)
Android 4.0.3
Android 4.3
I've seen this post Can Adobe AIR app communicate with iPhone calendar
But it is out of date, and things have changed since then.
Does anyone know if this is possible short of a hack?
My research hasn't been promising, as it looks to be impossible at this point in time. Anyone found otherwise?
AIR 3 which is coming out soon, will allow us to do communicate with native code.
I bought an iPod touch 3rd Gen half year ago, and I got recently an iPad WiFi. I also have a Onyx Bold Blackberry.
I don't have a Mac Book or any other apple product of laptop.
As a programmer, I speak C, Delphi and Java. I'd like to start playing around in mobile application.
I don't know whether I should start in Blackberry platform, iPod /iPad platform, or Android platform.
Ok, for each platform, what is the cheapest way to get started to play around the language?
1. Blackberry
2. iPod
3. Android
Learn HTML5 and you can build apps that can work on all platforms such as IPhone/IPad, Android and Blackberry. You can just build a mobile version of your site such as mobile.mysite.com. You can then choose to implement the server side with the language of your choice/familiarity.
The path of least resistance and also of lowest cost for you is Java development for Android. Only problem, you don't seem to have an Android phone. Though i'm sure you can pick up a used one cheap.
Why: The Eclipse IDE is free, there are free Eclipse plugins available from Google for Android dev, there's no annual dev cost like with iPhone/iPad development
In my opinion, you should start with an Android phone. You will be able to write your applications in Java, and test your applications on the device. The iPhone requires that you write your applications in objective-c, and requires developers to be a part of the iPhone Developer's Program in order to run their applications on an actual device (The membership fee is $99/year).
The documentation for the Android OS is superb, and once you have installed the Android SDK with the Eclipse Plugin, you can have a hello world application finished in a few minutes.
Let's say i have an app on BB, Android, iPhone and Windows Mobile.
So can we test apps developed on any platform on DeviceAnyWhere? Please confirm.
Here's the link: http://www.deviceanywhere.com/
In short, yes. The most popular devices available will be on DA. I've tested an app on about 20 different phones, from Nokia, Blackberry, iPhone, Droid and the likes.
Furthermore, the devices are 'actual' devices - not emulators which is great. You might find some of them sluggish though - testing has proven tedious in previous experiences.