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
Related
When trying to run my test app on a HVD emulator, I get the following error message:
App Launch: The Huawei Lite Simulator supports only Lite projects.
Meanwhile I've realized, that currently one can only use hardware or a remote emulator for such a project. But when trying to set this up, the Harmony OS Virtual Device Manager responds with 404:
Is there anything to do about it?
I haven't tried with DevEco Studio on Windows so far, but with Android Studio on Linux, which appears to be functioning now.
With HMS Toolkit version 1.0.5, it will ask for Huawei ID and then also lists devices in Düsseldorf or Ireland (where the one is a city and the other a country). However, there are currently only EMUI ROM available. It integrates better than before, but without an HarmonyOS 2.0 ROM, it still doesn't provide the expected environment.
error screen Error: operationError(Operation failed)
This is IOS 13.3. mobile device. Sensor is core: 1.1.0.
The sensor works fine with the app, and the DFU update does put the device in dfu mode (led on), but does not upload anything.
I'm trying to upload the most recent jumpmeter_app.zip (no version#).
Does the firmware zip filename need to start with Movesense_xxx.zip?
Movesense firmware updated the bootloader and BLE stack on version 1.2. That means that when updating from version <1.2 to >=1.2 you'll need to use the Movesense_xxxx_w_bootloader.zip DFU package. Between the big version jumps the smaller DFU package (without _w_bootloader in name) works fine and is much faster to update.
If there is a problem in the actual update with the Showcase app (iOS or Android) even if the sensor goes to DFU mode just fine, it is a good idea to try to run the update with the "nRF Connect" app (by Nordic Semiconductor) from app store.
Just for your information, the same situation will be between <= 1.9.4 and (coming) v. >=2.0.
Full disclosure: I work for the Movesense team
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
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.
I have installed android tools and eclipse successfully (making the hello World and hello widget examples) and have run these successfully on the Xperia X10 add-on that I downloaded from the developer site of SE.
However, my phone is running the updated Android 2.1, and any apps that I make will either have to run on 1.6, or will not be able to be tested on the Xperia X10 during development without moving it to my physical phone.
I have contacted Sony and they told me there is no add-on with 2.1 on it. And that is all they would say.
My Question:
Is there anyone out there who has developed for this phone, who knows what to do? Do I somehow run the SE update tool on the virtual phone to upgrade the OS of the image? Or am I missing something much more obvious?
As of April 2011, this is (an estimate of) Android usage share:
That's 3.5% for Android 1.6 and 2.7% for Android 1.5. As time goes by, those percentages will only decrease.
Just develop for 2.1.
Why do you prefer to use the emulator, anyway? Most Android devs (myself included) have found that the emulator is painfully slow, and it's just plain easier to plug in a real phone and test on that.
You can use the adb for getting your phone in debug mode.
Or you can just install your APKs via OTA or via USB in your physical phone.
Or you could just develop on 2.1 knowing that almost everything will work. I don't get the problem, really.