Setting Priority for Bluetooth Auto connection - android-bluetooth

I am currently working on bluetooth auto-connection. I wanted to know how can I set priority 0 for the last connected device so that in the next auto connection the system tries to connect with this device first always.
I wanted to know where to make these changes in android source code.

Please have a look at this guide form Android:
https://source.android.com/devices/automotive/ivi_connectivity
You can not customize which device to be connected first and which to be connected last but you modify existing policy or write your own custom policy to handle how many and which devices should be connected on next reconnection.

Related

What is the best way to determine the connection state of an AWS IoT device?

How can I determine if a particular AWS IoT device is currently online? I could send an MQTT message and make the device answer it. But is there some implicit way on seeing if a device is online/connected?
You can also use Fleet Indexing with enabled Connectivity Indexing
https://docs.aws.amazon.com/iot/latest/developerguide/managing-index.html and do search for your deviceId. In results you can check connectivity. Also you can search for all connected devices by using search with query connectivity.connected:true
Ok, there is a dedicated internal MQTT topic for it. Subscribe to $aws/events/presence/# to get presence events for all your devices.

Setting up zigbee network with X-CTU 6.3.2

I'm trying to create Zigbee P2P using XB24C27WIT-004 modules with Digi USB explorers(CP2102). I am using 2 laptops and connected the XBee modules to each of them. I have added the modules to X-CTUs and changed the DL of one module as MY of another module and vice versa. Both are on same channel and same PAN ID. But i couldn't see the serially transmitted data from one console to another. The console window is as shown in the image. The commands are being seen when i'm trying to discover other radio.The console window. The function is set to ZIGBEE TH Reg for both modules.
Have you configured one as a coordinator (ATCE=1) and the other as a router (ATCE=0) so they can join to each other? The Router can keep ATDH and ATDL as 0 to target the coordinator. I'm not familiar with using the 16-bit network address for the destination, so I'd recommend setting ATDH to the router's ATSH, and ATDL to ATSL.
To confirm that the devices are joined to each other, their operating PAN ID (ATOI and ATOP) must match. Once you see that, see if the router can send data to the coordinator, and then from the coordinator to the router. You can use ATNR on the router to perform a Network Reset so it will try to re-join your coordinator. You might need to set ATNJ to 0xFF on the coordinator to allow joining.

Any reason why latency in updating timelineitem to my glass device?

i see latency issue - when i send a timelineitem from my glassware app, it takes a long time to appear on glass device.
I see the item in developer playground (https://developers.google.com/glass/playground)
Is it isolated issue on my WiFi (unlikely)? or some optimization done at Mirror server which queues timelineitems and sending in a specific interval to glass device?
Thanks
After doing some more investigation (In my case, i have setup private network inside enterprise network), i found out that some of the ports are blocked by firewall settings for incoming traffic from outside network, so glass device was not getting notifications from the Mirror Server.
It is possible either Channel API or XMPP is used in receiving notification messages from Mirror server to Glass. Those ports might have blocked by my firewall settings. I ran wireshark, still it is not clear which protocol or port is used in receiving notifications.
Also it is possible that glass device could get (HTTP GET) newly available cards from the mirror server by polling on specific time interval or other cases(changing WIFI network, etc).
I called Glass help, i could not get any feedback.
I would really appreciate if someone (from Google) could shed some light (port and protocol details) on how Glass gets notification from mirror server when new timeline card is available.
This is a known issue:
https://code.google.com/p/google-glass-api/issues/detail?id=185
Issue has been fixed by updating to XE10.

Passbook notification failing

Followed the intermediate Passbook tutorial from the book "iOS 6 by tutorials"
http://www.raywenderlich.com/store/ios-6-by-tutorials
I'm able to send a pass by email, add it to pass book, update it in my app and it updates when I open passbook but I'm not getting any notification. Notifications are turned on in the settings.
My guess is that it could be the firewall of my server. I'm new to the howl server setup. I'm running on a godaddy vps (centos).
When I run a list on iptables I get the following:
iptables -L -vn
Does this look right ?
Any clue appreciated !
Thanks
This is unlikely due to a firewall issue on the server side - but could possibly be an issue with the firewall of the router that your device is connected to. Apple delivers push notifications to devices on port 5223, so this needs to be open on your local router (assuming you are connected by wifi). If you can receive push notifications from other Apps (WhatsApp, Facebook, etc.) then you can rule out firewall as an issue.
You state that the pass does get updated - this implies that either a push is being received by Apple and is triggering the device to retrieve the new pass from your web service, or if you are using replacePassWithPass to update the pass via an App, this is functioning as expected.
In order for the pass to display a notification message:
A pass data field must have changed (changing pass types, colours, images or label values will not trigger a notification), and
The field must have the changeMessage key set (ideally the changeMessage contains %# which will be replaced by the new field value)
If the above two criteria are met and you are still not receiving a notification, then try hooking your device up to Xcode and watching the console log as you update a pass.

What is the alternative way of sending user location via sms on iOS6?

i have done a security app which locate a iPhone and send the GPS location of the phone through message to an associated number this functions works good until iOS 5, but the issue is sending SMS without users knowledge is restricted in iOS 6, so i need a help here instead of sending message, is there any other possible way or replacement for this function? any answer related to this method are appreciated.
Thank you.
You haven't specified whether your ios app has a server. If yes, you can transmit location to server and that in turn can transmit it to intended user via specific api.
If this is not correct, APNS is your friend. This is a way to send messages to desired devices only, the ones who explicitly registers through your app.
Another quite equivalent option is to store it in public back-end like parse.com. As soon as other devices start your app, they can pull your location from there. If their device is already live, parse.com can make sure to notify them as soon as you change your location value in their DB.

Resources