Develop Reference

Find the distance to Eddystone beacon from the device using Android Beacon Library

I am developing an android application to find the distance from Eddystone beacon to the mobile device. I am using Android Beacon Library and following this example. when I locate my beacon nearly 1 meter away from my device, it shows like below. it shows small values and changes continuously. How to solve this and get at least nearly accurate value.

The "underestimate" shown in the question suggests one or more of the following may be true:
The Beacon has not been calibrated.
The receiving phone device model may have an unusually high measurement of signal strength requiring a device-specific adjustment of its distance calculation.
See here for more information on how to address these issues.
Even once you address the above, set your expectations properly. Bluetooth LE distance estimates are rough. They are useful for telling you if another device is within a couple of meters or many meters away. But they cannot tell you the precise distance to a bluetooth transmitter.

What exactly is txPower for Bluetooth LE and how is it used?

I am trying to understand what exactly txPower is and how to use it, since I am planning to develop and Android app that uses Beacons.
I have seen 2 definitions online:
1.The transmitted power of the beacon.
2.The received power 1 meter away from the beacon.
How are these two definitions related?
Also, when transmitting a Beacon signal from a device using an app such as QuickBeacon, how do I determine what to set the power (txPower) to?

Most beacon formats contain a single byte in the transmission that indicates what the expected signal level should be when you are one meter away. This byte is sometimes called txPower (short for transmitted power) and sometimes measured power.
Do not confuse this with a second configuration setting on some beacon models that lets you vary how strongly the transmitter actually sends its broadcasts. This is typically called transmit power, which is why measured power is a less easily confused term.
The measured power field is used to make distance estimates. If the phone sees that its signal level is the same as the measured power field transmitted by the beacon, it knows it is exactly one meter away. If it has a stronger signal, it knows it is closer. If it has a weaker signal it knows it is further away. Using a formula, you can get a rough idea of the distance in meters.
Making this distance estimate accurate requires having the measured power field set properly to the expected signal level at one meter. It is often pre-configured into the beacon by the manufacturer, but it is typically adjustable. Why would you want to adjust it? If you place the beacon inside a cabinet, it might attenuate the signal. If you place the beacon against a metal wall, it might increase the signal due to reflections. For this reason, it is recommended that you calibrate a beacon by measuring and setting its measured power value after installation.
Calibration involves using a phone to measure the beacon signal level (using a measurement called the Received Signal Strength Indicator or RSSI, which is measured in dBm). To calibrate, you hold a phone with a typically performing bluetooth receiver (ideally an iPhone 6, but Nexus devices work well too) exactly one meter away from the beacon, and measure the average signal strength over 30 seconds. Many beacon configuration apps and tools like Locate for iOS and Android have calibration utilities.
Once you have the calibration value, you need to configure it inside your beacon per the manufacturer's instructions. This will give you more accurate distance estimates.

Check that issue maybe it helps:
Get Tx Power of BLE Beacon in Android also you could check out some devBytes from Google about BLE
https://www.youtube.com/watch?v=vUbFB1Qypg8
If you are using specific BLE beacons you need to referenced the datasheet and check how tx power is measured. As you already mentioned there is different definitions for it. During my dev I found that most suitable is that : txPower is measured in some distance from transmitter with way without obstacles. So if there is a wall for example txpower will be lower. Consider that.

txPower has defined the range of the Bluetooth signal to transmit the beacon.

How to measure the distance between an iPhone acting like an iBeacon and an Android device

I'm using my iPhone as an iBeacon device, and on the other side I have an Android 4.4.2 device scanning for the Bluetooth LE iBeacon signal from the iPhone. I searched for a good and easy way to calculate the distance between iBeacons and my Android phone, but I couldn't find anything that can help me with this.
Could you help me on this matter?

It's impossible to measure beacon distance accurately, I'm afraid, which is why Apple's own code just says "Immediate", "Near", "Far" and "Unknown". The best you can do is set up a reconstruction of the conditions you expect then do trial and error tests to map signal strength to probable distance. Trust me: I've spent a lot of time trying to do beacon distance measurement using a range of hardware.
Remember that the LE in Bluetooth LE means "Low Energy" – this stuff really is designed to use as little power as possible. That means the signal from iBeacons gets interrupted by people, walls and other objects. So, if I'm holding a beacon in my hand and put my phone next to it, I'll get a strong signal. If I move the beacon behind my back, the signal strength will collapse. If I just turn around, that has the same effect (for the same reason).
If you want to go down the "best you can do" approach, you effectively have to recreate at least partially the environment where your app will be used. So, if your app will be used in an office, find an office and place some beacons around there. Same for being in a shop.
Then get your app out and measure beacon strength at various distances to the beacon, potentially with obstacles in the way. With some averaging, you end up with something like "at 1 metre my signal strength was X, at 5 metres it was Y, at 10 metres it was Z", etc, and you then feed that into your distance calculation. It is, effectively, an educated guess.
If you find any library that claims to do beacon distancing for you, it just means they've taken their own educated guess based on their own signal strength testing.
One tip: if you're able to, stick your beacons to the ceiling. This minimises the chance of obstacles (read: people) getting between your beacon and your app.

We built a distance estimation formula into the Android Beacon Library of the form: d=A*(r/t)^B+C, where d is the distance in meters, r is the RSSI measured by the device and t is the reference RSSI at 1 meter. A, B, and C are constants. You can read more about it here. To use it with the library, you range for a beacon and then simply call:
beacon.getDistance();
This returns a distance estimate in meters. The library code is open source, so if you don't want to use the library you can copy the formula and use it directly.
As #TwoStraws notes, distance estimates are pretty rough guesses of how far a beacon is away, and the results you get vary with lots of factors:
The gain of the antenna on the receiving device. (Every Android device model is slightly different)
The noise on the A/D converter inside the phone that measures bluetooth signal strength.
The radio noise in the room.
Any obstructions between the transmitter and receiver.
Any surfaces (especially metal) that reflect radio signals.
Just be sure you set your expectations properly. Distance estimates are good for deciding if a beacon is close or far, or whether one beacon is closer than another. But they are less useful for measuring absolute distance.

calculate distance from beacon when user is moving in a vehicle

How to calculate distance using BLE beacons if the user is moving in a vehicle with 2-15kmph speed?Also,if the distance won't give me accurate results is there any other mechanism with the help of which I can calculate the nearest beacon.The default implementation does not give me proper results as there is a 20sec lag in distance estimates.
Secondly,in which cases should ARMA filter be used.

Beacon distance estimates are only estimates, so you must set accuracy expectations accordingly. In order to reduce noise on radio signal levels, many samples are averaged over a period of time.
Figuring out the appropriate averaging time depends on the use case. As you have noted, the Android Beacon Library uses a 20 second running average by default. This gives a distance estimate based on where the vehicle was on average over the past 20 seconds.
For a vehicle going up to 15km/hour (~5 meters / sec) with a beacon transmission radius of 50 meters, it will be in range of the beacon for a maximum of 10 seconds. How many distance measurements do you need to get? If one is enough, average over 10 seconds. If you need more, set the period even shorter.
Understand that reducing the sample interval will add more noise error to the distance estimates, because you will have fewer statistical samples to work with. A few things you can do to make the most of the samples you do get:
Set the beacon to advertise as frequently as possible. Some beacons advertise at 1Hz or less to save battery. This leads to poor distance estimates. Increase it to 10Hz or more if possible.
Turn off bluetooth configurability/connectability on your beacon. Some Android devices will only allow one signal level sample per BLE scan (1.1 secs by default in the library) in connectable mode. This can lose you 90% of your samples at 10 Hz.
Configure the beacon transmitter to be on its highest power setting and calibrate it properly. Stronger signals have a higher signal to noise ratio, giving better distance estimates.
The ARMA filter uses a nondeterministic sample interval based on % change in each sample. It is more appropriate for use cases with slow moving beacon receivers.

Determining distance accuracy from beacon

I have couple of questions regarding the Radius networks Beacon.
How can we get the accurate distance between android devices and
beacon? So far the distance we're getting through
"android-beacon-library" is fluctuating.
How can we limit the beacon's transmission radius, say allowing
beacon to transmit only for 5 meters or to 20 cms ?
Please find the image with beacon distance reading for various devices (Moto g , Nexus 5 , Nexus 4 and iPhone 5s)

You will always see fluctuation on beacon distance estimates, so you have to set your expectations appropriately. Beacon distance estimating works by starting with a measurement of the radio signal strength using the bluetooth radio on the mobile device. A stronger signal means that the beacon is closer, where a weaker signal means the beacon is further away. The beacon transmits a reference value of its expected signal strength at 1 meter, saying in effect "If you are one meter away, you should see my signal level as -56 dBm". A formula inside the mobile phone then tries to make a guess of how far it is away based on the signal level at any given time. If the signal is a little bit weaker than -56dBm, such as -65dBm, the formula might estimate that the distance is 2.5 meters.
This technique is imperfect, and there are several reasons for fluctuation:
There is always background radio noise (like the static on an old AM radio) which causes individual signal strength measurements to vary.
There is error on the analog to digital converter inside the bluetooth radio, which also causes individual signal strength measurements to vary.
The bluetooth radio waves reflect off of some objects and are absorbed by others, making the actual signal strength change at different positions the same distance away, and when other objects in the vicinity move around.
The antenna pattern on both the transmitter and the receiver are not perfectly spherical. This means that when you rotate your phone or the beacon, you will see a slightly different signal level.
There are a few things you can do to minimize the error:
Use a beacon that transmits as frequently as possible, preferably at 10Hz or more. More transmissions mean more statistical samples of the signal level, which when averaged together help mitigate errors from sources 1 and 2 above.
Use as high of a transmitter power setting on your beacon as possible. The stronger the signal, the lower the noise level will be (relatively speaking) from source 1 above.
When possible, place your beacons where there is a clear line of sight to the receiving devices. Overhead often works best.
However, the best you can hope to do is reduce the variation as much as possible. You cannot eliminate it. For this reason, you must design your app so such variation is acceptable. If it helps your use case, you can also lower the beacon transmitter power so that devices only detect the beacon when they are relatively close.
Using Radius Networks' RadBeacon USB and RadBeacon Tag models, you can adjust the transmitter power using the free RadBeacon configuration app for iOS and OSX. The apps have a slider control to increase and decrease the transmitter power.
You should note, however, that by lowering the transmitter power, you will also increase the amount of variation on your distance estimates. This is because the signal to noise ratio will be lower.
Full disclosure: I am Chief Engineer for Radius Networks.

you can't really tell the distance to one beacon. That's why indoor localization is so hard.
you can't say exactly how far a beacon should transmit its signals, but on most beacons (I don't know about Radius networks) you can change the txPower / transmit power. This varies from beacon to beacon (and also depends on the environment around the beacon), so you'll have to do your own experiments to find the sweet spot.