Xamarin.iOS bluetooth connectivity on iPad locked - xamarin.forms

My BLE device uses SSL certificate on connection which is causing the app to hang when the iPad gets locked. It works fine as long as I don't lock the iPad. anyone faced similar problem?
What I tried is to disconnect the device on sleep and reconnect it on resume. It works fine when the app goes into background and comes back, the problem comes when I lock the iPad and then resume to app. Same events fire whether I lock the device or minimize it.
Can anyone tell me how Xamarin handles these 2 things?
I have enabled background modes and tried everything available on the internet but I couldn't get it working.
It starts working when I kill the app and try to reconnect it.
How do I dispose the connection with my bluetooth device properly on sleep and then start as a new?
P.S I'm using dependency services in Xamarin.Forms.

Related

QGuiApplication pauses the event-loop when remote windows connection disconnected

I am starting a QGuiApplication (Qt 5.12) and using a remote desktop connection to a Windows 10 PC. Everything works fine while the remote desktop connection is open, but when I disconnect and let the application run during the week-end, I can see in the logs that it stops processing Qt events (mostly network related in my case). The last thing the logs show is an "activation change" event.
When I connect again after the weekend, the Qt event loop starts again (the logs show again "Activation Change event") and of course there is a huge amount of queued events and the application gets in a non responding state (I am logging the number of Qt events queue in the loop using qGlobalPostedEventsCount).
This used to work correctly but stopped working, I think due to an update of Windows on the machine (maybe same root-cause than this thread ?).
Is this the expected behavior for applications when the windows remote connection is terminated? Is there a known fix for this?
I have not managed to properly fix the issue. As a work-around, using Microsoft "Remote Desktop" application instead of using the "Remote Desktop Connection" application avoids the issue.

get a broadcast to android app on BLE connection

A question about registering BLE notification on android:
I am developing an app that once the android device detects our beacon/ble hardware, should write something to one of the writable characteristics of that hardware.
Trying to understand, on the android app side how can I register some intent to be called when a ble connection was made to the android framework.
since a broadcast receiver registered in manifest can no longer launch my app and android background services policy was changed, this can't be done. so..
I am trying to use JobScheduler which was designed to be launched based on criteria. this can launch a JobService to do the job.
When the app is in foreground or background this seems to be working.
The thing is, I need to be notified when the app is not running (Not even in background)

{{> loginButtons} not showing on device with wifi off

I am testing my app on an android device and I have a problem with the "{{> loginButtons}". The div is only showing when my device is connected via USB to the computer with its WiFi on. When i disconnect WiFi and the USB the "{{> loginButtons}" disappears.
Kindly assist. I want to have the buttons display even when my device is disconnected and WiFi switched off.
And I want to fly =)
Think about this logically. If you are trying to authenticate a user while your device is offline, what are you doing with the authentication parameters? How --- Where --- are you going to login to?
No where. No where at all.
While your device is tethered, Meteor is smart enough to treat your computer as the application server. Without the tether, or WiFi, your phonegap bundle is trying to connect to something which doesn't exist. I suppose the package authors decided to simply hide their component if there's no application server detected, rather than code in a bunch of error messages.
Instead, what you need to do is to deploy your app. Once deployed, you can use the IP or the domain name as a parameter when you launch Meteor through Cordova. Then your buttons will render, because they can actually do something with themselves.

Meteor mobile application STOPS working over 2G and 3G networks

I am working with a Meteor mobile application with Cordova and PhoneGap.
My app is working fine over a Wi-Fi connection. But whenever I use it on mobile networks, 2G or 3G, it stops working. Meteor.status() returns disconnected all time on mobile cellular networks.
What is the solution for this problem?
This could occur if you have a bad connection. The Meteor in the device's browser can't really tell what network it's on. It just uses whatever it gets.
As soon as it can get a connection back it should reconnect. Keep in mind with 2G (EDGE/GPRS) connections you might have to wait a bit longer for the HTML/JavaScript to connect to the DDP server as all the client HTML/JavaScript data needs to be downloaded first. This can take quite a while.
The other thing is to ensure your (3G) connection isn't over some kind of proxy, especially if you're hosting the application yourself on an unusual port number (websockets usually fall back to long polling, though).

When I try to Port Sample Android app into Blackberry 10 Dev Alpha simulator I Get Error

Connecting 192.168.176.128 to ADB failed!
Please check if the Android player was fully started when you got this error. If not, you can either increase the Android player launch timeout on the BlackBerry->BlackBerry Android Development Tools preference page or wait until the Android player is fully started and try again.
This means that Eclipse, or more specifically the BlackBerry Android tools plugin for Eclipse, could not connect to the ADB (Android Debug Bridge) service on the BlackBerry device.
There are a number of reasons for this:
The Android Runtime and associated services including ADB did not load in time. The default timeout is 5 seconds and if you have not run any Android apps on your BlackBerry it will take more like 20 seconds to load the first time.
The Android Runtime has crashed. In which case you will need to reboot your device. My preferred method for this is a '3 finger reset' which means hold down the power button, volume up and volume down buttons for 10 seconds in order to do a full reset.

Resources