Background wi fi location

How to disable background WiFi scanning in Windows 10

Even when we choose to connect our PC to a home wireless network, Windows automatically scans for other wireless networks in range. The purpose of the scanning is to help users stay connected to the strongest network, but it can be distracting when it continues for an extended period of time. Fortunately, there exists a setting that lets you disable background WiFi scanning in Windows 10.

Disable background WiFi scanning in Windows 10

1. Open the Run dialog box.
2. Type ‘services.msc’ in the box and hit Enter.
3. Find WLAN AutoConfig entry.
4. Right-click the entry and choose the Properties option.
5. In the Properties window that opens, go to Startup type.
6. Hit the Drop-down menu button, choose Manual.
7. Under the Service Status heading, hit the Stop button.
8. Exit Local Service Editor.
9. Restart your PC.

It is important to note that stopping or disabling the WLANSVC service will make all WLAN adapters on your computer inaccessible from the Windows Networking User Interface. Microsoft recommends users keep the WLANSVC service running if the computer has a WLAN adapter.

Press Win+R in combination to open the Run dialog box.

Type ‘services.msc‘ in the empty field of the box and hit the Enter key.

In the Local Service Editor window that opens, find the entry by the following name – WLAN AutoConfig.

Right-click the entry and select the Properties option.

Next, in the Properties window that shows up, go to the Startup Type option.

Hit the drop-down button adjacent to the above option and select Manual.

Next, under the Service Status heading, hit the Stop button.

When done, the process will disable background WiFi scanning in Windows 10.

Источник

Android Background Wifi Scanning Foreground Service

I am trying to scan Wifi every 10 seconds. I have produced an Android Foreground service to achieve this. The application has all of the right permissions and does get the list of local Wifi hotspots. However, it does this once. I have tried to implement a thread to do this every 10 seconds, as can be seen in the code below. The Log.d() message is logged every 10 seconds but the Wifi is not printed after the first time it is printed.

import android.app.Notification; import android.app.NotificationChannel; import android.app.NotificationManager; import android.app.PendingIntent; import android.app.Service; import android.bluetooth.BluetoothAdapter; import android.bluetooth.BluetoothDevice; import android.content.BroadcastReceiver; import android.content.Context; import android.content.Intent; import android.content.IntentFilter; import android.net.wifi.ScanResult; import android.net.wifi.WifiManager; import android.os.Build; import android.os.IBinder; import android.os.Looper; import android.support.annotation.Nullable; import android.support.v4.app.NotificationCompat; import android.util.Log; import android.widget.ArrayAdapter; import android.widget.Toast; import java.util.ArrayList; import java.util.List; import java.util.Set; public class ForegroundService extends Service < private WifiManager wifiManager; public static final String CHANNEL_ID = "ForegroundServiceChannel"; @Override public void onCreate() < super.onCreate(); >@Override public int onStartCommand(Intent intent, int flags, int startId) < String input = intent.getStringExtra("inputExtra"); createNotificationChannel(); Intent notificationIntent = new Intent(this, MainActivity.class); PendingIntent pendingIntent = PendingIntent.getActivity(this, 0, notificationIntent, 0); Notification notification = new NotificationCompat.Builder(this, CHANNEL_ID) .setContentTitle("Foreground Service") .setContentText(input) .setSmallIcon(R.drawable.ic_stat_name) .setContentIntent(pendingIntent) .build(); startForeground(1, notification); //do heavy work on a background thread wifiManager = (WifiManager) getApplicationContext().getSystemService(getApplicationContext().WIFI_SERVICE); if (!wifiManager.isWifiEnabled()) < //Toast.makeText(this, "WiFi is disabled . We need to enable it", Toast.LENGTH_LONG).show(); wifiManager.setWifiEnabled(true); >registerReceiver(wifiReceiver, new IntentFilter(WifiManager.SCAN_RESULTS_AVAILABLE_ACTION)); new Thread(new Runnable() < @Override public void run() < Looper.prepare(); while (true) < Log.d("Test","00000000000000"); scanWifi(); try < Thread.sleep(10000); >catch (InterruptedException e) < e.printStackTrace(); >> > >).start(); //stopSelf(); return START_NOT_STICKY; > private void scanWifi() < wifiManager.startScan(); Toast.makeText(this, "Scanning WiFi . ", Toast.LENGTH_SHORT).show(); >BroadcastReceiver wifiReceiver = new BroadcastReceiver() < @Override public void onReceive(Context context, Intent intent) < Listresults = wifiManager.getScanResults(); unregisterReceiver(this); for (ScanResult scanResult : results) < Log.d("WIFI",scanResult.SSID + " - " + scanResult.capabilities); >> >; @Override public void onDestroy() < super.onDestroy(); >@Nullable @Override public IBinder onBind(Intent intent) < return null; >private void createNotificationChannel() < if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) < NotificationChannel serviceChannel = new NotificationChannel( CHANNEL_ID, "Foreground Service Channel", NotificationManager.IMPORTANCE_DEFAULT ); NotificationManager manager = getSystemService(NotificationManager.class); manager.createNotificationChannel(serviceChannel); >> > 

Источник

Android wifi geofence/background location querying

I’m writing an Android app (not a novel one), that will turn off/on the user’s wifi based on their location. It will get the approximate location using the network’s location. I’m basically using Google maps to save the geofences they create to my database. I’m curious what’s the best approach in terms of insuring the app doesn’t have to be in the foreground for it to work correctly. Should I use addProximityAlert or something different? Considering I’m creating multiple geofences and the user could potentially have 10 set up, I fear using different proximity listeners for each geofence. Instead, it would seem more power efficient to query for location every 15 minutes or so and then let the app decide if it’s in reasonable range of any of those geofences. Let me know, appreciate the help.

3 Answers 3

You can use the brand new GeoFence feature Google just released. It supports API 8+. The Class reference:

Edit: There is a mention on GeoFences limit in LocationStatusCodes:

Well an entire final project with many hours spent working later, it’s cooked into Android. Just my luck 🙂 Thanks for the advice though, may rewrite it with this.

do you have any reference for the limit of 100 geofences? I was not able to find any information or clue on that limitation.

@usb79 it was mentioned at Google I/O although the developers said there would be a clarification about the limit of Geofences. They may have removed it. I’ll edit my answer.

here is the sample code i write, it’s worked fine for me

public class LocationClientService extends Service implements GooglePlayServicesClient.ConnectionCallbacks, GooglePlayServicesClient.OnConnectionFailedListener, LocationClient.OnAddGeofencesResultListener < private LocationClient mLocationClient; private ListmGeofenceLists = new ArrayList(); @Override public void onCreate() < super.onCreate(); Geofence geofence1 = new Geofence.Builder() .setRequestId("your target place") .setTransitionTypes(Geofence.GEOFENCE_TRANSITION_ENTER | Geofence.GEOFENCE_TRANSITION_EXIT) .setCircularRegion(0.0, 0.0, 2000.0f) .setExpirationDuration(Geofence.NEVER_EXPIRE) .build(); mGeofenceLists.add(geofence1); mLocationClient = new LocationClient(this, this, this); mLocationClient.connect(); >@Override public IBinder onBind(Intent intent) < return null; >private PendingIntent getPendingIntent() < Intent intent = new Intent(this, TransitionsIntentService.class); return PendingIntent.getService(this, 0, intent, PendingIntent.FLAG_UPDATE_CURRENT); >@Override public void onConnected(Bundle bundle) < mLocationClient.addGeofences(mGeofenceLists, getPendingIntent(), this); >@Override public void onDisconnected() < >@Override public void onConnectionFailed(ConnectionResult connectionResult) < >@Override public void onDestroy() < mLocationClient.disconnect(); super.onDestroy(); >@Override public void onAddGeofencesResult(int i, String[] strings) < if (LocationStatusCodes.SUCCESS == i) < //todo check geofence status >else < >> 

then write a IntentService to recieve geofence enter or exit:

public class TransitionsIntentService extends IntentService < public static final String TRANSITION_INTENT_SERVICE = "ReceiveTransitionsIntentService"; public TransitionsIntentService() < super(TRANSITION_INTENT_SERVICE); >@Override protected void onHandleIntent(Intent intent) < if (LocationClient.hasError(intent)) < //todo error process >else < int transitionType = LocationClient.getGeofenceTransition(intent); if (transitionType == Geofence.GEOFENCE_TRANSITION_ENTER || transitionType == Geofence.GEOFENCE_TRANSITION_EXIT) < ListtriggerList = LocationClient.getTriggeringGeofences(intent); for (Geofence geofence : triggerList) < Log.i("test", "triggered Id " + geofence.getRequestId()); >> generateNotification(transitionType); > > private void generateNotification(int type) < >> 

Источник

An Explanation of Wi-Fi Triangulation

Former Lifewire writer Fred Zahradnik has a long history as a writer and is considered an expert on all things related to GPS products and software.

Michael Heine is a CompTIA-certified writer, editor, and Network Engineer with 25+ years’ experience working in the television, defense, ISP, telecommunications, and education industries.

• Wi-Fi & Wireless
• The Wireless Connection
• Routers & Firewalls
• Network Hubs
• ISP
• Broadband
• Ethernet
• Installing & Upgrading

Wi-Fi Positioning System (WPS) is a geolocation system that relies on Wi-Fi to locate compatible devices and users. Wi-Fi often works alongside GPS to improve accuracy. Companies like Google, Apple, and Microsoft use GPS to identify Wi-Fi networks, which can then be used to find someone’s device as it relates to nearby Wi-Fi.

Wi-Fi positioning is useful in urban environments, where there are many wireless networks broadcasting within the same area. It is also useful in places that are out of reach to GPS, such as tunnels, large buildings, and underground structures.

However, WPS does not work when out of range of a Wi-Fi signal; if there aren’t any Wi-Fi networks around, then WPS will not work.

Wi-Fi Positioning System is not to be confused with Wi-Fi Protected Setup, which shares the same abbreviation (WPS). The latter is a wireless networking system that’s meant to make it faster for devices to connect to a network.

How Wi-Fi Location Services Work

Devices that have both GPS and Wi-Fi can be used to send information about a network’s location back to a GPS service. The GPS device transmits the service set or «BSSID» (MAC address) of the access point along with the location determined by GPS.

When GPS is used to determine the location of a device, it also scans nearby networks for publicly accessible information that can be used to identify the network. Once the location and nearby networks are found, the information is recorded online.

The next time someone is near one of those networks but does not have great GPS signal, the service can be used to determine an approximate location since the network’s location is known.

Let’s say, for example, you have full GPS access and your Wi-Fi is turned on in a grocery store. The location of the store is easily spotted because your GPS is working, so your location and some information about any nearby Wi-Fi networks are sent to the vendor (such as Google or Apple).

Later, someone else enters the grocery store with Wi-Fi on but, because there’s a storm outside, they have no GPS signal. Their location can still be determined thanks to Wi-Fi network positioning. Vendors like Microsoft, Apple, and Google are always refreshing this data, using it to provide more accurate location services to users. And it is disclosed involuntarily; vendors do not need Wi-Fi passwords to locate contributing networks.

Anonymously determining user locations is part of virtually every cell phone carrier’s terms-of-service, though most phones allow the user to turn off location services. Similarly, if you don’t want your own wireless network to be used in this way, you may be able to opt out.

Opt out of Wi-Fi Tracking

Google includes a way for Wi-Fi access point administrators to opt out of its WPS database. Simply add _nomap to the end of the network name (e.g. mynetwork_nomap) and Google will no longer map it.

Источник