I purchased a RadBeacon USB from Radius Networks and iBeacon Locator on my Nexus 7 says the calibration is: -59.
My iPhone 5s sees it, the measured power is: -64, so I press OK to copy this value to the Measure Power field of the beacon settings. You must apply the settings to update the Measured Power on the beacon device.
So I press Apply and use the PIN 0000.
Apply Settings.
It says "Invalid PIN".
I use my 4 digit PIN that I use for everything and it says "Connection timed out".
Now in the instructions it says "If you are unable to discover you beacon using the RadBeacon Config App, remove the plastic cover and firmly press the configuration button above and to the right of the battery holder. This will restart the 30 minute configuration window and your beacon should show up in subsequent scans.
Define firmly.
I didn't think it had a battery. What is a battery holder?
Does this button give any kind of tactile feedback when pressed so that I can know that I'm pressing it?
There's a square opening on the top-right of both sides after removing the metal cover. Is one of them the button?
Is there a product that doesn't have this 30 minute restriction so that I can get it to work the first time as a proof-of-concept, and not have to worry about it being bricked after 30 minutes?
Sorry you are having trouble, Philip.
You are correct that your RadBeacon USB does not have a battery. We also sell a RadBeacon tag, which does have a battery and it sounds like you are reading the instructions for that model. So please ignore those instructions.
To restart the config time window on your RadBeacon USB, simply unplug it and plug it back in. Then try using the iPhone RadBeacon app to configure it using the default pin of 0000. If it does not accept that pin, and you did not change the pin to something else you remember, contact us at support#radiusnetworks.com and we will arrange a replacement.
Understand that the configuration time window is simply a security feature to keep other folks from trying to reconfigure your beacon. You can always restart the time window by cycling power. So you don't need to worry about bricking your device -- just be careful not to change the pin without writing down the new number.
Related
I have 4 of Mikrotik 'Wap AC's.
3 of them are fine. But the fourth one turned out to be a problem, an enigma.
I have reset it (30-30-30) several times but it just refuses to be visible on LAN --WinBox cannot locate it, doing a full network scan returns nothing.
Also, it has no WiFi presence either since neither of the radios come on line.
My question is this:
Now that I have removed the motherboard from the enclosure, is there any way I can hard reset it? Shorting some contacts or something similar.
You might use the netinstall software and try to upload the correct firmware.
The reset button has three functions:
Hold this button during boot time until LED light starts flashing, release the button to reset RouterOS configuration (total 5 seconds).
Keep holding for 5 more seconds, LED turns solid, release now to turn on CAP mode. The device will now look for a CAPsMAN server (total 10 seconds).
Or Keep holding the button for 5 more seconds until LED turns off, then release it to make the RouterBOARD look for Netinstall servers (total 15 seconds).
Remember boot time is after power is connect that means you must keep hold the reset button.
After that you can follow the steps for netinstall https://wiki.mikrotik.com/wiki/Manual:Netinstall.
Faced with the fact that Netinstall does not see the connected access point, it was decided to disable the firewall. After that, the device appeared and I was able to flash it.
I set my tango down for a couple of months while busy with other things. I charged it for a bit, turned it on and saw the red battery icon. I charged it overnight and saw the green battery symbol. I clicked the power button The splash screen came up, said it was installing updates and screen turned off. That evening I tried to turn it on and it wouldn't do anything. Next morning it turned on - splash screen - white screen, off. Now it doesn't do anything at all. I've tried - volume button and power, both volume buttons...nothing. Has anyone else had this problem? Any ideas? Thanks.
On the below instruction. it only diagnose your device for hardware and BSP level problem. Tango Core and Apps related is not included.
To diagnose your device problem. First we need reset your device.
Hard Reset device
Press your device power key for around 8-10 secs.
sometimes you will see the backlight of screen is off.
Diagnose what is going on on your tango devices
2.1 Check basic bootloader function.
Plug in device with a charging usb cables.
2.1.1 if your device is out of power.
It will show red battery icon. or green icon which you device still enough battery to boot it up.
2.1.2 if your device is not any icon pop up.
Try 1 step again. or
switch different Usb cables and chargers or charging docks.
If it still doesn't work.It is possible a hardware issues now. you may need to contact project-tango-help#google.com
2.1.3 if you do see the battery icon, but without charging icon on it.
That mean something wrong with your charging cable or devices. Switch different charger and cables. if problem still exists. you may need to contact project-tango-help#google.com
2.2 Check the Software side of the devices
if you can see the icon in 2.1.1, that is good.
Normally on Green icon, you can boot up your device.
2.2.1 after the icon is gone, press the power key are 1-3 secs, device will boot up.
you will see the tango icon and the rolling tango icon as part of booting process.
if you get stuck at this two process forever. it means that there is some problem on booting image on android. please go to section 2.3.
if you can see the Android UI without problem. you are fine.keep a eye on your battery. if it show 50% on charging full. and some weird condition. you may need to contact project-tango-help#google.com for more details.
2.3 Recovery your device by android recovery mode.
if you android system can't boot up successfully, Recovery your device is needed. Remember it will wipe out all your data,and cache. so try to backup your data if possible.
2.3.1 If you device can access by ADB, try : adb reboot recovery
or try below steps:
{ make sure device is off,
press the power key with volume Up and Down key at the same time for around 2-3 seconds, till you see Bootloader menus
you will see
{
Continue
Fastboot protocol
Recovery mode
Reboot
Power off
Force Recovery
}
by using volume Up and Down, and power key you can select the item.
select "Recovery mode"
2.3.2: now you are at Tango android recovery mode.
it will show
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
Using Volume down key for moving, and power key for selecting.
The same step as normal Android recovery step.
1. wipe cache partition
2. wipe data/factory reset
then select reboot system now.
Waiting device to boot up.
2.3.3, If your device is still not good. Google didn't provide the tango image for customer fastbooting the device. you had to contact project-tango-help#google.com for next step.
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 using windows WLAN APIs (Windows Desktop not Metro Apps) to scan WiFi networks.
I'm curious what will be the behavior of the WiFi scan when Airplane mode is enabled before the scan is completed?
I'm trying to create such scenario but it very hard to catch such timing.
Any ideas?
Technically speaking, "Airplane Mode" Takes the Radio Transmitters in your iPhone and changes their frequencies of transmission to frequencies that are sympathetic to Aeronautic Instrumentation, such as Guidance Systems for example.
Due to the frequency change, if you're scanning Networks and then you change the properties of the Network adapter, the adapter has to restart. So, your Scan will be temporarily interrupted.
Test it on your iPhone, download something from App Store and switch modes during the download, see what happens. The Icon will suddenly stop and will display "SEARCHING" and will then re attempt to pick up the connection again.
Is it possible to track the accelerometer value while under the lock screen?
I managed to write a simple application which counts from 1 up to 100 using a timer which fires an event on which I increment a counter.
But when I use register a handler for the ReadingChanged event of the accelerometer it will not be fired anymore once the screen has been locked. Even if I unlock the screen again I will have to readd my handler.
the msdn documentation tells on the one page:
http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff941090(v=vs.105).aspx
"Valid reasons to disable idle detection in Windows Phone OS 7.1 applications include ones where core functionality continues while the phone is locked (for instance, an exercise tracking app)"
but the sensor api also tells:
http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh202968(v=vs.105).aspx
"The Sensor APIs cannot be used while the application is running under the lock screen. For more information, see Idle Detection for Windows Phone. The Sensor APIs also cannot be used in background agents. For more information, see Background Agents Overview for Windows Phone"
I hope they will change the api soon, because of that it is not possible to write any good sleep tracking / sport tracking applications ... :(
I was helping a guy with this a couple of days ago. He had an app that tracks GPS and accelerometer data under lock screen.
Turned out the app accelerometer data stopped tracking when under manual or auto lock screen.
There may be an issue here to be looked into.
Under lock screen it is a good idea to minimise power usage... disable all uncessary code, like ui updates. My understanding of one the motivations for idle detection and running under lockscreen being opened up during CTP was in response to a lot of feedback from developers of map/tracking apps that basically need this for their app to be of any use.
I'm not sure of the usage case where you'd want to use the accelerometer under the lock screen.
Apps typically run under the lock screen when you need them to do something when you're not interacting with the device. e.g. playing music or downloading a large file.
If you wanted accelerometer data I'd assume that the device is being held and, therefore, presumably, looked at. Given this, why would you therefore want to run under the lock screen?
That being said, if you had a good reason to do so, you should still be aware that:
when your application runs under a locked screen, it ... must minimize
power usage
(from the Marketplace Certification Requirements.)
In my understanding, reading values from sensors is not minimizing power usage.