Will Android Things run on OrangePi 2G IoT board?
Will Android Things run on OrangePi 2G IoT board.
It's not clear what exactly you're asking, so there are 2 possible options below:
If you mean whether Android Things can currently run on the board, then the answer would be No. The board is not currently supported by the Android Things project.
If you mean whether Google is going to support the platform in the future, then you should contact Google about that or fill in a feature request.
Related
I've seen this topic going around and the answers on each site and post have given it a wide range when talking about how to automate IOS devices from Windows PC.
One side, I've seen it where mainly the answer is: it's not possible due to Apple's rules, or its really messy to set up and not worth the effort to maintain, (though not explained in detail why its messy.) On the other side, I've read articles and posts about recommendations of IOS simulators such as iPadian, Smartface, etc; along with articles suggesting to stay from this software recommendations stating that they likely contain malware and viruses.
I've found other sources suggesting Experitest, Appium Studio, Quamotion, TestProject to test and automate IOS on Windows PC. However, after reading the concerns of being cautious around these sites, and unable to proof if these studios/software legitimately support simulating real IOS environments on Windows and the arguments that are against going this approach, I can't tell which sources are reliable on this topic anymore.
The interest for me asking this question, as you can guess, is that I want to find a way to automate IOS on Windows and experience how run tests on iPhone.
I usually write my code in Eclipse Studio and use Oracle VM to create Android Emulators to test on. I'm fine if I need to have a physical IOS device in order to test.
All advice is appreciated.
Thank you
The best option I would suggest to automate iOS app on Windows is to use cloud based solution like BrowserStack, SauceLabs, etc.
This way you're sure that you will be using actual iOS device and the app would behave the same way as it would on real physical iOS device.
You can even inspect the app using Appium inspector and run the tests with ease as well.
The only drawback of using such solution is that most of them don't support latest version of Appium.
So the work around for this would be to setup Microsoft Azure DevOps pipeline on Mac OSX virtual machine and use latest Appium server version.
The tools you mention - Experitest, Appium Studio, Quamotion,... all use the same approach: they communicate with real, physical iOS devices over a USB connection and then launch an agent (WebDriverAgent or similar) on the device which you can use to automate iOS devices.
They will usually require you to at least configure an iOS developer certificate and provisioning profile (much like you would when you are testing on a Mac).
Most of them also offer you a free trial and support, so you can go ahead and install the software and give it a try.
I'm trying to make my personal google assistant, and platform is using i.MX7 as website suggested.
My question is, could I bring it up with my own hardware design? (i might try some other wireless to connect through zigbee/bt/ble/wifi..etc.
To make your own Google Assistant IoT device, you should read the documentation for the Google Assistant SDK. This will allow you to make calls to the Assistant from any Internet connected device.
The second part of your question, about Android Things, isn't clear about what you want. You can build your own developer board for Android Things, using one of the supported SoMs, but you cannot use a different baseboard altogether. While you can use external wireless modules connected through user-level drivers, you will not be able to do the same at a lower-level. On Android Things boards, like the Raspberry Pi and IMX7, BLE and Wi-Fi are included in the hardware already.
My team and I are students and we are currently embarking on a final year project to develop an Indoor positioning system (IPS) mobile application on IOS (IPhones only). Would like to clarify our doubts on certain areas.
1)Is it true that IPhones Apps that calculates the wifi signal strength from access points is still not allowed in app stores?
2) I have seen quite a number of SDKs using Wi-fi triangulation to create IPS for android. Other than redpin which provides open source SDK for IOS, is there other SDKs available to develop IPS on IOS?
Thank you so much.
1) True 2) AFAIK No.
See this SO answer on outdoor positioning and another SO answer on the Apple80211 private framework to access the WiFi (app rejection if you use it ofc). There are also hardware solutions like Cisco Mobility Services Engine.
WiFiSlam used signal strength + SSID + inertia. They claim to use signal integration with a better algorithm than Kalman. See http://youtu.be/OGdvjvla1Tc#t=1033s They were bought by Apple and now are gone from the Internet, but it seems possible, although complicated, to develop a software only solution for indoor positioning.
Another thing, even when you set kCLLocationAccuracyBestForNavigation but the position is still all over the place when compared to a GPS unit. See http://web.archive.org/web/20110912081330/http://rnr.davidlokshin.com/post/825290568
You can only access Wi-Fi-signals from your app if you jailbreak your device. This is not a good solution of course. We at indoo.rs eventually decided to go for Bluetooth instead of Wi-Fi.
We provide an SDK for that, by the way. ;)
1) True. There are no public APIs that supply signal strength. (The only info that can be gathered with public APIs is the SSID of the currently connected Wi-Fi network.)
2) I don't know.
We have a fairly simple mobile application, completed for iPhone and Android that does the following:
queries a web service to verify the user's account information
display an animation to show that the user, in fact, has a valid account
We got the application working very quickly on a PlayBook by using the Android version.
Now the customer has asked us to explore getting it to work on other BlackBerry devices.
None of us know that much about BlackBerry, and the main source for our question returned from google searches (http://us.blackberry.com/developers/choosingtargetos.jsp) comes up as 404 page.
According to this chart there is still a wide variety of devices in use. Which ones does it make sense to target?
Thanks
I had posted an answer last year about this here on stackoverflow, but as you noted, that link has recently broken.
The only thing I've found that's similar is this BlackBerry developer page. It shows, for example, that paid apps are being purchased by devices that are about 97% on OS 5.0 and above.
From what you've told me, I don't know that your app is going to be that different on different devices, aside from maybe the obvious smartphone vs. Playbook difference. Different devices certainly have different screen sizes, so you'll need to make sure your UI is coded to handle that gracefully.
If you guys are new to BlackBerry, you might want to stay away from OS < 5.0. There are some things in prior OS versions (e.g. location services / maps, browser, and networking) that are a little tough to work with, and with such a small percentage of paying customers still on OS < 5.0, it probably isn't worth it to you.
So, I guess I'm recommending that you target specific OS levels (e.g. 5.0+). That will be a bigger driver for how you build your app, than a specific set of devices. This is because each OS version adds more and better APIs to use.
Once you've decided which OS to target, then you should download the SDK for each major OS. For example, if you use the Eclipse BlackBerry plug-in, you can install the 5.0 SDK (aka component pack), the 6.0 SDK, the 7.0 and 7.1 SDK.
Once you have those SDKs installed, you'll then have a bunch of simulators (each SDK has a simulator folder). Run your app on all those simulators, and that'll probably be a good start.
Of course, there's no substitute for running on real hardware, too, but if your app does mostly standard things (not interacting with hardware sensors, just displaying web pages, and making HTTP requests), the simulators should give you a pretty good test environment. They certainly will give you all the screen size configurations.
Can anybody please help me out with the difference between tablets, iPads and palm devices. I am new in this area and have no idea what are the specifics of this devices or how they differ from one another. iPad is from Apple, are there any other devices similar to iPad but are from HP or Android????
Also what is the difference in developing apps on this machines. Like if I can develop app for an iPad, will it be easy for me to develop a similar one for HP or Android device(if they have something similar to iPhone).
There has been a lot of press lately about tablet devices, Apple seems to have set the pace with the iPad and the iPad 2 is rumored to be announced sometime soon.
iPad apps are written primarily in Objective-C using the iOS SDK free from Apple on the iOS Developer Center. It does cost $99 to deploy apps to a device and distribute them however. There are other tools to develop iOS applications such as MonoTouch and PhoneGap
Blackberry is about to release the Playbook which from my understanding runs Adobe Air applications.
HP just announced the Touchpad which runs WebOS, the applications are primarily built using web technologies (HTML, Javascript, etc)
Then there are a slew of devices coming out that run Android, I think the next one that will be available to consumers is the Motorola Xoom. Android apps are developed primarily in Java using the Android SDK which is free and platform independent.
This market is evolving very fast and there are a lot of players, it seems Apple has the solid ground a this point.
Developing applications for these devices can differ quite a bit, one way that you can reach all devices is by developing a tablet centric webapp such as Yahoo!'s tablet site
I-Pad apps can only be created on a mac PC and will likely share no code with an HP device, I believe HP do make an android laptop but not a touchpad.
Touchpads similar to i-pads do exist and some do indeed run android. Take a visit to your nearest computing or electricals store and they are bound to have one.
A palm device is smaller and fits within the palm of your hand, The i-phone or a blackberry would count as a palm device. Any regular 'non' smartphone(iphones blackberrys again) also classifies but i dont believe this is what you are looking for.
Android is not a company, Android is an operating system that your code will run on. Other companies make the device which then has android installed.