Android信标库后台服务-视频播放或加载某些API数据时的UI滞后

Question

I'm developing a beacon application scanner (in Background when Bluetooth is activated) with Android Beacon Library . The problem is whenever I activate the scanner in as a background, and I try to play a video with MediaController in another Activity or to load some API data, the video is not playing or sometimes it plays with lagging and the same as the API loading action.

But when I disable the scanner all works fine.

I don't know if the library runs its services in another thread or the same thread that blocks the UI, so I want to know how can I resolve this problem with multitask solution if it is possible.

I used

this is the CustomApplication file:

import android.R
import android.app.*
import android.content.Context
import android.content.Intent
import android.os.*
import android.util.Log
import com.example.anymarketmobile.views.subactivities.HomeActivity
import org.altbeacon.beacon.*
import org.altbeacon.beacon.powersave.BackgroundPowerSaver
import org.altbeacon.beacon.startup.BootstrapNotifier
import org.altbeacon.beacon.startup.RegionBootstrap

class BackgrounApplicationBeacons : Application(), BeaconConsumer, RangeNotifier {
    //  Init Properties
    lateinit var mBeaconManager: BeaconManager
    var mRegion: Region? = null
    var mMonitor = false
    var mLastDetectedBeacon: Beacon? = null
    val TAG = "==>"

    //  Actions & Callbacks
    override fun onBeaconServiceConnect() {
        mBeaconManager.addRangeNotifier(this)
        try {
            mBeaconManager.startRangingBeaconsInRegion(mRegion!!)
        } catch (e: RemoteException) {
        }
    }

    override fun didRangeBeaconsInRegion(beacons: MutableCollection<Beacon>?, region: Region?) {
        Log.i("==>Beacons:", "${beacons?.size}")
        if (beacons?.size!! > 0) {
            val beacon = beacons.iterator().next()
            if (beacon.id1 != mLastDetectedBeacon?.id1) {
                Log.i("${TAG}beacon detected:", "${beacon.id1} , ${beacon.distance} m")
                mLastDetectedBeacon = beacon
            }
        }
    }

    //  Start monitoring beacons
    fun startMonitoring() {
        mBeaconManager = BeaconManager.getInstanceForApplication(this)
        Log.i("==>", "Application launched:")
        if (mBeaconManager.isMainProcess) {
            mBeaconManager.beaconParsers.clear()
            mBeaconManager.beaconParsers.add(
                BeaconParser().setBeaconLayout(Constants.DEFAULT_BEACONS_LAYOUT)
            )
            mBeaconManager.setEnableScheduledScanJobs(false)
            val backgroundPowerSaver = BackgroundPowerSaver(this)
            mBeaconManager.backgroundBetweenScanPeriod = 0
            mBeaconManager.backgroundScanPeriod = 2100
            mRegion = Region("test", null, null, null)
            // mRegionBootstrap = RegionBootstrap(this, mRegion)
            mMonitor = true
            val builder = notificationBuilder()
            mBeaconManager.enableForegroundServiceScanning(builder.build(), 456)
            Log.i(TAG, "startMonitoring")
            mBeaconManager.applySettings()
            mBeaconManager.bind(this)

        }
    }

    //  Stop monitoring beacons
    fun stopMonitoring() {
        mRegion = null
        mBeaconManager.removeRangeNotifier(this)
        mBeaconManager.unbind(this)
        /*mRegionBootstrap?.disable()
        mRegionBootstrap = null*/
        Log.i(TAG, "stopMonitoring")
        mMonitor = false
        mLastDetectedBeacon = null
    }

    fun isMonitoring() = mMonitor


    //  Forground notification builder
    private fun notificationBuilder(): Notification.Builder {
        val builder = Notification.Builder(this)
        builder.setSmallIcon(R.drawable.ic_search_category_default)
        builder.setContentTitle("Scanning for Beacons")
        val intent = Intent(this, HomeActivity::class.java)
        intent.putExtra(Constants.FOREGROUND_SERVICE_COMMUNICATION_BEACON_SCAN, mMonitor)
        val pendingIntent = PendingIntent.getActivity(
            this, 0, intent, PendingIntent.FLAG_UPDATE_CURRENT
        )
        builder.setContentIntent(pendingIntent)
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
            val channel = NotificationChannel(
                "My Notification Channel ID",
                "My Notification Name", NotificationManager.IMPORTANCE_DEFAULT
            )
            channel.description = "My Notification Channel Description"
            val notificationManager = getSystemService(
                Context.NOTIFICATION_SERVICE
            ) as NotificationManager
            notificationManager.createNotificationChannel(channel)
            builder.setChannelId(channel.id)
        }
        return builder
    }
}

I expected to avoid any lag or slowly execution.

Answer 1

Much of the work of the Android bluetooth stack is on the UI thread -- all detection callbacks are made on the UI thread for example. The Android Beacon Library maintains its own background thread pool and immediately switches detection processing to a lower-priority background thread once a packet comes in from the operating system. As a result, the library processing overhead on the UI thread is minimal -- limited to just handing off work to a different thread for each packet seen.

However, the operating system portion of the BLE detection processing is a different story, and some of it is done on the UI thread. I would be surprised if there were significant Android OS processing on the UI thread from a BLE scan unless a very large number of BLE devices were visible at the same time. I have not specifically tested this on a Huawei HOL-19, but I have tested it on stock Android devices (eg Pixel and Nexus devices) and confirmed the UI processing is minimal in cases where a dozen or fewer BLE devices are visible.

You might try a different device to see if it might be a Huawei HOL-19 specific issue.