Status Update
No update yet.
Comments
ed...@gmail.com
Using the stock 2.3 launcher this happens..there is also times when the screen will not scroll and only will scroll once the phone is rebooted..
sa...@gmail.com
Got my Nexus S today from the Carphonewarhouse. Phone updated to 2.3.1 and after having it plugged in I added two email accounts. When I returned to the home screen via the 'home' button I have the same issue as the OP. A reboot was the only way to resolve this.
xa...@gmail.com
I am also having this issue but it did not happen until I deleted an app that was on the home screen.
ca...@rootstrap.com
I have also encountered this problem many times. I had to restart the device to be able to drag and drop again.
ma...@gmail.com
I am having the same problem on the Nexus S. When I have the problem, I have to reboot the phone. Then when I reboot it, I sometimes find these icons that went missing in one of the created folders (even though I never dragged it to any folders). I am also usually unable to move folders into a different location without fully shutting down and rebooting the phone. It will work after a fresh reboot but very quickly start to experience the same issue again. The only way I have been able to get icons where I want them in some cases is to long hold the desktop where I want to set it and create the shortcut manually there. Opening up the "all applications" menu and dragging to the desktop fails to work unless it is freshly rebooted. Sounds like another Nexus S bug.
sd...@gmail.com
Try to kill the launcher and not restarting the phone it works for me
Description
Call
bluetoothAdapter = (BluetoothManager) context.getSystemService(Context.BLUETOOTH_SERVICE)
bluetoothAdapter.getBluetoothLeScanner().startScan() *without* any of the permissions
ACCESS_COARSE_LOCATION or
ACCESS_FINE_LOCATION
granted by the user via ActivityCompat.requestPermissions() et al. procedure.
- What happened.
BLE devices are not discovered. Console display error message:
BluetoothUtils: Permission denial: Need ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION permission to get scan results
- What you think the correct behavior should be.
The BLE devices that we want to connect to *don't need the location service*. The operation of our devices *does not require any information about their location*.
The user must not grant the above mentioned permissions. Granting these unnecessary permissions is very irritating our users.
The user must not need to enable GPS on his Android device in order to discover our BLE devices.
- Don't forget to mention which version of Android you're using, and/or which
device the problem appears on (model and Android version).
This issue affects only API level >= 23, i.e. Android 6.0 Marshmallow.