I am looking for a simple app (preferably for iPhone, but if not then for Android), which pops up a message when it receives a signal from a beacon.
The beacon is a Sensoro 4AA, we only purchased it for demonstration purposes.
The idea is: once we turn the smartphone's bluetooth on, the beacon is detected and the message just pops up.
Is there such an app (as simple as can be), where I can just insert the beacon's details (uuid, addtess, or whatever is needed) and maybe some text or link, in order to achieve that?
Thanks
You can use Beacon Simulator for Creating, broadcasting and Scanning Beacons as per your needs and testing.
For Android: https://play.google.com/store/apps/details?id=net.alea.beaconsimulator
For iOS: https://itunes.apple.com/us/app/noteacons-beacon-simulator/id1136196655?mt=8 or https://itunes.apple.com/us/app/dropbeacon-a-beacon-simulator-for-development-purposes/id866760594?mt=8
I hope this helps!!!
Related
I have been doing lots of research trying to figure out if it is possible to create wear notifications with custom layouts over the past few months, but am struggling to find a solution.
I have tried to implement the following suggestions to no luck:
https://possiblemobile.com/2014/07/create-custom-ongoing-notification-android-wear/
http://android-wear-docs.readthedocs.org/en/latest/sync.html
Custom UI for Android Wear Notifications
Most of what I have read have instructed that in order to do this, I should create an android wear app with a data listener. The idea being the phone would send certain data to the watch (say a string) based on the type of notification it wants to send. I would disable the automatically generated wear notification. In its place, the Android Wear app listener would know what type of notification it is based on the string and display my custom pages for that notification instead.
My first problem I have run into is I have no idea how to debug code like this. Since in Android studio you can only launch the device app or the wear app, but not both at the same time.
The other question I have is, does the Android Wear app run in the background when the Device App is running? Do you have to open the Android Wear App first for the listener to be even working (if so then I guess this is not a solution to custom notifications)?
Is it actually possible to create custom layout android wear notifications?
If you want to use a custom layout for your notifications, you should create the notification on the watch, following Creating Custom Layouts. You can even make the custom notifications clickable, you can add actions that will open activities on the watch, etc.
For that, you can send a message from your phone to your watch and the listener implemented on your watch will receive it and then, create and display the notification using the correct layout corresponding to the message sent, for example.
In this case, the best way is to implement a WearableListenerService on your wearable. Its lifecycle is handled by the system which binds it only when necessary.
To debug, you install the wear app on the wear emulator or your watch, you install the mobile app on your phone and finally you connect the two following this tutorial if you're using the emulator or via bluetooth if you're using a watch (link in the tutorial).
The Android Wear app connects your phone to your watch, whether it is an emulator or not. So, in order for your message to be received, you must have connected wear and mobile via Android Wear. Then, once the connection is established, you don't necessarily need to keep it open. So yes, the Android Wear app runs in background.
I have had a pack of four jaalee beacon stickers delivered and I'm having a problem getting them 'woken up'.
According to the website, you have to tap the beacons two or three times. I've tried this a few times but still no cigar, I can't detect them using various bluetooth sniffers.
I'm wondering if I'm tapping them too hard, too soft.
Also found a Jalee app which asks me to press a button on the stickers, no button is visible but I pressed for a few seconds and one of the four stickers 'beeped' once... but the app failed to pair with it. I couldn't get the sticker to beep again.
This was a cheap alternative to Estimote stickers I ordered but which never arrived. So far, beacon sticker technology doesn't seem to be 'there'.
The beacon stickers I have need a few things to happen to be enabled.
1) Download the Jaalee app, I'm not sure it was available when my stickers first arrived. This is the correct app for iPhone for the kind of stickers I have.
App store link for Jaalee thinnest smart tracker... app
2) Open the app and select a kind of activity to which the beacon is to be enabled (they are trying to ape Estimote I believe). I chose the magnifying glass.
3) On the following dialog select + to add a new sticker.
4) Squeeze the beacon sticker firmly in the centre for several seconds until it beeps.
5) Hold it close enough to the phone/mobile device running the app to enable the app to pair with the beacon and enable it.
At this point the Jaalee beacon should be detectable with a standard Bluetooth sniffer app such as 'LightBlue'
Firmly tap the beacon on a table and it should beep. You may need to turn it over a tap the other side. They need a firm tap.
Once woken up it will be available to connect to and reconfigure. If left it will go back to sleep after about a minute.
I'm exploring the end user experience for a beacon prototype but I'm struggling to find any end-user scenarios that involve the app becoming active / opening up on the screen when within range.
I can get the app to send a notification and this is the most likely experience on both Android and iOS but does anyone know if it is possible to get the app to open up?
It's unlikely that I'd want real customers to have their experience interfered with in this way, I think it's ok if the app is already running and is open but not if it's running but not open.
Thanks
On Android this is possible. The reference app for the Android Beacon Library demonstrates how to do exactly this.
On iOS, it is not possible due to OS security restrictions. See here for details. The best you can do is send a local notification to the user when the beacon is detected, then if the user gestures to it, bring up the app.
I did everything verbatim on this sample (How do I discover a Chromecast device using Android?).
The chromecast icon turns to white on indicating there are devices available.
When I pressed it, the application unfortunately stops.
What can be going wrong? The only step so far I want to achieve is list all available devices.
Cheers!
For example in this demo: http://demos.telerik.com/kendo-ui/scheduler/index
On a desktop browser, clicking on the event opens an editor. On a mobile touch device, tapping on the event does nothing. This repros also when running Chrome device emulation as iPhone.
Telerik claims that this works here:
http://www.telerik.com/forums/creating-or-editing-event-in-mobile-browser
so I don't understand how they can make that claim.
Can someone please confirm that this does not work, or if I'm doing something wrong? I am just evaluating their product at this stage, so I do not have paid support subscription required to reply on that forum thread.
I figured out the answer to my question. On mobile devices, the scheduler needs to be configured for mobile using mobile:"phone" or mobile:"tablet", as well as instantiate a kendo.mobile.Application.
Here's an example: http://dojo.telerik.com/#ggkrustev/uCiNU