i trying test battery consumption caused android , ios beacon detector application different beacon protocols , advertisement rates. question advertisement rate of beacons in anyway affect battery consumption of detector applications? these applications scan fixed amount of time , after fixed interval, different advertisement rates have effect?
thanks
yes, in cases app detects more beacons use more battery 1 detects fewer beacons. while true on both ios , android , eddystone/altbeacon/ibeacon, details vary each combinations.
two reasons detecting more beacons using more battery on receiver side:
it takes more cpu power decode each beacon packet array of bytes useful fields , trigger app useful it. more packets need decoded, more cpu (and battery power) used.
if app woken in background when detects beacons, more frequent wake ups cause app run in background more often, again burning more cpu , battery.
on both ios 7+ ibeacon , android 5+ (with android beacon library), bluetooth hardware filters used mitigate effects of (1) when no beacon apps actively ranging, instead monitoring detections in background. not true eddystone or altbeacon formats on ios, because cannot use hardware filters effectively. these formats may use bit more battery power in background on ios when looking detections in background.
the news time battery usage comes play when ranging (scanning) many beacons long periods of time, , of battery usage doing scanning @ all. if app scanning many minutes or hours @ time see significant battery hit. , if 100 beacons around instead of one, see bigger battery hit still.
Comments
Post a Comment