WiFi P2P是否导致设备WiFi自动连接功能不起作用?

如何解决WiFi P2P是否导致设备WiFi自动连接功能不起作用?

我遇到一个问题,我的设备在有效范围内时会停止自动连接到WiFi网络。我的应用程序具有一项在后台运行的服务(即使该应用程序被杀死),该服务每分钟都会注册和注销一次服务,以便使用WiFi P2P重复检测附近的设备。

 private final BroadcastReceiver broadcastReceiver = new BroadcastReceiver() {
        @Override
        public void onReceive(Context context,Intent intent) {
            String action = intent.getAction();
            if (WifiP2pManager.WIFI_P2P_STATE_CHANGED_ACTION.equals(action)) {
                int state = intent.getIntExtra(WifiP2pManager.EXTRA_WIFI_STATE,-1);
                if (state == WifiP2pManager.WIFI_P2P_STATE_ENABLED) {
                    Log.d(TAG,"WiFi P2P Enabled");
                    if (ActivityCompat.checkSelfPermission(getApplicationContext(),Manifest.permission.ACCESS_FINE_LOCATION) != PackageManager.PERMISSION_GRANTED) {
                        return;
                    }
                    manager.discoverPeers(channel,new WifiP2pManager.ActionListener() {
                        @Override
                        public void onSuccess() {
                            Log.d(TAG,"Discover Peers Successful");
                        }

                        @Override
                        public void onFailure(int i) {
                            Log.d(TAG,"Discover Peers Unsuccessful");
                        }
                    });
                } else {
                    Log.d(TAG,"WiFi P2P Disabled");
                }
                // Check to see if Wi-Fi is enabled and notify appropriate activity
            } else if (WifiP2pManager.WIFI_P2P_PEERS_CHANGED_ACTION.equals(action)) {
                Log.d(TAG,"Peers detected");
                if (manager != null) {
                    if (ActivityCompat.checkSelfPermission(getApplicationContext(),Manifest.permission.ACCESS_FINE_LOCATION) != PackageManager.PERMISSION_GRANTED) {
                        return;
                    }
                    Log.d(TAG,"Peers Requested");
                    manager.requestPeers(channel,peerListListener);
                }
                // Call WifiP2pManager.requestPeers() to get a list of current peers
            } else if (WifiP2pManager.WIFI_P2P_CONNECTION_CHANGED_ACTION.equals(action)) {
                Log.d(TAG,"Connection Changed");
                // Respond to new connection or disconnections
            } else if (WifiP2pManager.WIFI_P2P_THIS_DEVICE_CHANGED_ACTION.equals(action)) {
                Log.d(TAG,"WiFi P2P State Changed");
                // Respond to this device's wifi state changing
            }
        }
    };

 WifiP2pManager.PeerListListener peerListListener = new WifiP2pManager.PeerListListener() {
        @Override
        public void onPeersAvailable(WifiP2pDeviceList wifiP2pDeviceList) {
            Log.d(TAG,"Peers available");
            String deviceEncrypt = "";

            if (!wifiP2pDeviceList.getDeviceList().equals(peers)) {
                peers.clear();
                peers.addAll(wifiP2pDeviceList.getDeviceList());

                deviceNameArray = new String[wifiP2pDeviceList.getDeviceList().size()];
                deviceArray = new WifiP2pDevice[wifiP2pDeviceList.getDeviceList().size()];
                int index = 0;

                for (WifiP2pDevice device : wifiP2pDeviceList.getDeviceList()) {
                    deviceNameArray[index] = device.deviceName;
                    deviceArray[index] = device;
                    index++;

                    try {
                        deviceEncrypt = AESUtils.encrypt(device.deviceAddress);
                        Log.d(TAG,"Encrypted MAC Address discovered: " + deviceEncrypt);
                    } catch (Exception e) {
                        e.printStackTrace();
                    }
                }
            } else {
                Log.d(TAG,"No peers found");
            }
        }
    };

我意识到这可以防止设备在有效范围内自动连接到已知的WiFi网络。任何想法如何解决这个问题?下面的代码每分钟都会注册和注销一次broadcastReceiver,以实现一致的对等检测(此操作在onStartCommand函数中运行)。

private void refreshTime() {
        handler.postDelayed(runnable = new Runnable() {
            @Override
            public void run() {
                Log.d(TAG,"Refreshed");
                registerReceiver(broadcastReceiver,intentFilter);
                unregisterReceiver(broadcastReceiver);
                registerReceiver(broadcastReceiver,intentFilter);
                handler.postDelayed(runnable,delay);
            }
        },delay);
    }

解决方法

回答我自己的问题。因此,manager.discoverPeers是阻止Android自动连接到已知Wifi网络的原因。我通过将refreshTime()拆分为两个不同的函数来解决此问题。

private void refreshTime() {
        refreshHandler.postDelayed(refreshRunnable = new Runnable() {
            @Override
            public void run() {
                Log.d(TAG,"Refreshed Registered");
                registerReceiver(broadcastReceiver,intentFilter);
                refreshHandler.postDelayed(refreshRunnable,refreshDelay);
            }
        },refreshDelay);
    }

private void stopDiscovery() {
        peerHandler.postDelayed(peerRunnable = new Runnable() {
            @Override
            public void run() {
                manager.stopPeerDiscovery(channel,new WifiP2pManager.ActionListener() {
                    @Override
                    public void onSuccess() {
                        Log.d(TAG,"Peer Discovery Stopped");
                        try {
                            unregisterReceiver(broadcastReceiver);
                            Log.d(TAG,"Refreshed Unregistered");
                        } catch (IllegalArgumentException e) {
                            Log.e(TAG,e.toString());
                        }
                    }

                    @Override
                    public void onFailure(int i) {
                        Log.d(TAG,"Peer Discovery Failed to Stop");
                    }
                });
                peerHandler.postDelayed(peerRunnable,peerDelay);
            }
        },peerDelay);
    }

stopDiscovery()调用manager.stopPeerDiscovery()并在onSuccess上取消注册broadcastReceiver。

两者都以两个不同的间隔运行。 refreshTime()每1分钟运行一次,而stopDiscovery()每2分钟运行一次。这将使discoverPeers()停止一分钟,并使操作系统自动连接到已知的Wifi网络。

再次。如果有人对此有更优雅的方法,请与我分享。谢谢。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-