What spec/version of Websockets does iOS 5.1+ use? - ios5

I've been making adjustments to a websocket server I'm using, but I'm finding my efforts in vain since I haven't been able to determine which spec (hixie/hybi?) of websockets the most recent version of iOS is using.
Is it Hixie 76 or Hybi? Thanks!

Here is test link, use any device / platform to test it: http://websocketstest.com/
On iPhone 4 (Version 5.0.1) supports drawft-76.
And here is overall support statistics of availability of technology over different browsers / platforms: http://caniuse.com/#feat=websockets

Related

I have version 1.1.0 of my movesense. Can I flash the firmware to 1.9 without any problems with Showcaseapp-1.9.6.apk?

I downloaded the Showcaseapp-1.9.6.apk. (I am on android)
I downloaded 1.9.0_hr_wakeup_DFU.zip
The showcase app does not show my Smart Sensor (movesense) in the app under "movesense connection" also can't select device because its not listed.
The following message from the readme is confusing me:
WARNING: in case the new firmware is not based on the latest Movesense stack, the device looses the capability to be updated!!!
Does this mean I have to update from 1.1 to 1.2 to 1.3 and so on?
Kind regards
No worries, you can update directly from 1.1 => 1.9. However, since your firmware is that old you need to use the "_w_bootloader" DFU packet (contains updated bootloader which was introduced in v1.2). Basic rule is that you'll need the "_w_bootloader" DFU packet if there was softdevice / bootloader change between the two versions.
There may be some issues updating the sensor if you are using the latest Android showcase app (1.9.x). In that case you can download older version from movesense-mobile-lib bitbucket site / downloads. iOS sample app should not have that limitation but you will need also the nrf connect / nrf toolbox apps.
Full Disclosure: I work for the Movesense team

Minimum Android version with flutter

Which minimum android version is supported by flutter?
Do some plugins have any effect on which version is not supported?
I tried to run my flutter app on an android emulator, but with the version android 16 it doesn't work and the app crashes. Do I have to change the compile version in some config files or why doesn't it work?
Flutter support 16. But to run app on Android emulator, use over 19.
https://github.com/flutter/flutter/issues/11094
https://github.com/flutter/flutter/issues/9108
https://github.com/flutter/flutter/issues/8610
From Flutters FAQ
flutter.dev/docs/resources/faq#what-devices-and-os-versions-does-flutter-run-on
Mobile operating systems: Android Jelly Bean, v16, 4.1.x or newer, and
iOS 8 or newer.
Mobile hardware: iOS devices (iPhone 4S or newer) and ARM Android
devices.
Note Flutter currently does not support building for x86 Android
(issue #9253) directly, however apps built for ARMv7 or ARM64 run fine
(via ARM emulation) on many x86 Android devices.
We support developing Flutter apps with Android and iOS devices, as
well as with Android emulators and the iOS simulator.
We test on a variety of low-end to high-end phones but we don’t yet
have an official device compatibility guarantee.
We believe Flutter works well on tablets. We do not currently
implement all of the tablet-specific adaptations recommended by
Material Design, though we are planning further investment in this
area
The answer to this question also, partly, needs to take into consideration what parts of Android you want to take advantage of in your application. The question of what min version Flutter supports has been answered here a couple of times so I won't answer that, but the Android support libraries will also need specific min versions.
If you plan to use plugins of any kind then you will probably hit multiple issues if your min version is too low. Do you need Firebase? Do you need specific camera functions?
Google also just announced required bumps for min versions with regards to Google Play that you should review.
My advice is to follow documentation, analytics and best practices to determine what you "true" min version should be.
The Flutter documentation has this answer to Android and iOS. Now it says that support: Android Jelly Bean, v16, 4.1.x or newer, and iOS 8 or newer. However, this information can change according to the new Flutter version. By this reason, it is better that you review the next link:
https://flutter.dev/docs/resources/faq#what-devices-and-os-versions-does-flutter-run-on
Furthermore, it would be best if you analyzed the plugins because they could need higher versions of Android and iOS.
This answer can be useful :
Devices and OS versions on which Flutter runs
Mobile operating systems: Android Jelly Bean, v16, 4.1.x or newer, and iOS 8 or newer.
Mobile hardware: iOS devices (iPhone 4S or newer) and ARM Android devices.
You can learn more here

Upgrading iOS and appium version in Device Farm

Can we upgrade the iOS and appium version on Device farm AWS. Can we use existing devices onto cloud ?
I work for the AWS Device Farm team.
Thank you for the feedback.
While we certainly get the importance of updating to the latest and greatest version of Appium on our part whenever we update the version we make sure all versions of OS and make/models undergo a thorough extensive test. This is a work in progress and you should see the Appium version updated soon.
As far as devices go it is on the same lines where we make sure that we are able to offer the same experience across all devices. We are working on getting the latest iOS devices in our fleet right now and this should be very soon in coming week or two.
Hope that answers your question.
As far as my knowledge goes , Device farm does not provide with latest iOS version, the appium thats mentioned in device farm was 1.4.XX and we at office use 1.5.3 which supports of multiple devices on a single computer

AppWarp Unity SDK fails to connect with CONNECTION_ERROR error

I'm running into this basic issue while integrating the AppWarp Unity SDK (no version is specified, downloaded on 10 of March) with Unity 4.3.4 Android player.
The AppWarpVikingMobile sample fails with the same error.
"telnet appwarp.shephertz.com 12346" does connect to the server. Wireshark shows no packets (running with a filter "host appwarp.shephertz.com").
There is a similar issue asked here on February, but it is unresolved still.
Seems that it's SDK import/compatibility issue.
Any ideas?
When running in the player you have to use the AppWarpUnity.dll asset. Its only when building the apk to run on a physical device you need to build with AppWarpUnityMobile.dll asset (and NOT AppWarpUnity.dll) along with the native plugins provided.
It can be a bit confusing because Unity has different restrictions on different versions (Pro and Free) for different platforms with regards to plugins and sockets. AppWarp's goal is to give developers a way to use it with or without the Unity Pro on all platforms.
The interface exposed by the assets is the same so your application code need not change.

Does Bluestacks support Renderscript?

As the most of you will know Android Emulators for >3.x don't support Renderscript. Now I found an Android Player called Bluestacks (tge most of you will know it I think). So I wanted to ask, if it's just me or does Bluestacks also not support Renderscript.
Regards,
Ahmad
Google has published a compatibility library for Renderscript, which allows you to use it starting from Android 2.2 (API8).
This means that Renderscript could run even on bluestacks if it is still android 2.3.
The disadvantage is that it uses the CPU unless the OS version is 4.3 and above.
more information about it is available on the android developers blog, here
It is supposed to support RenderScript. As RenderScript is a part of android framework, all renderscript openGLES operations should be forwarded to host stack eventually.
According to the Bluestacks help forum Bluestacks is equivalent to Android 2.3.4 which doesn't support Renderscript as far as I know.
Actually the emulator images for Ice Cream Sandwich (4.0.x) and JellyBean (4.1.x) which come with the Android SDK does support Renderscript. The Honeycomb (3.0, 3.1, 3.2) emulator images do not.