Assigned
Status Update
Comments
an...@google.com <an...@google.com> #2
I can attest that Yakju 4.1.2 update on stock Galaxy Nexus broke radio, bluetooth and wifi. The phone enters airplane mode on its own. The radio loses all telco signal (only recover after a 10 second airplane mode). Bluetooth pretends to connect but the headset is unusable. Wiifi that the same issue as bluetooth.
All in all, the phone connectivity is in a really poor state. Most people could not reach me today and I had to keep checking the phone the whole day to see if the radio/wifi was still working which it mostly wasn't.
All in all, the phone connectivity is in a really poor state. Most people could not reach me today and I had to keep checking the phone the whole day to see if the radio/wifi was still working which it mostly wasn't.
mr...@google.com <mr...@google.com>
as...@google.com <as...@google.com> #3
[Comment deleted]
ja...@gmail.com <ja...@gmail.com> #4
Comment has been deleted.
mr...@gmail.com <mr...@gmail.com> #5
[Comment deleted]
mr...@gmail.com <mr...@gmail.com> #6
Same issue. Cannot tether. Wifi will connect and assign an IP. No throughput.
Version 4.1.2 Build JZO54K
Version 4.1.2 Build JZO54K
Description
The default behavior on an Andriod phon should be do zoom on the phone's current location based on GPS. E.g.,
But when you add any zoom parameter, it launches at long, latt = 0,0 (the middle of the ocean).
So I think including the zoom parameter, for some reason, overrides this default.
What steps will reproduce the problem?
1. Got to
2. Or use any valid zoom parameter, even 15
3.
Also add the following details:
- Device (and version of Android) you have verified this issue on: Moto G4 (also an issue on Chrome running on a MacBook Air)
- Google Play Services client library version:
- Google Play Services version on the device:
- Android SDK Version:
- Was this working correctly on a previous version of Google Play Services?
(If yes, which client library and SDK version?)
No
Also attach screenshots, sample code and optionally an APK if possible.
If the problem exhibits itself in a released version of your app on the
Play Store, optionally provide a link to the app, and explain how to
reproduce the issue in the app.