Assigned
Status Update
No update yet.
Comments
na...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
- Android bug report (to be captured after reproducing the issue)
Android Wear devices connected to Android devices
-
On you Android phone, following the instructions below, under the section ‘Instructions on your companion phone or tablets (Android)’
-
Launch the ‘Android Wear’ app on your phone or tablet.
-
Tap on the three vertical ellipsis on the top right hand corner of the screen and click on “Report Wearable Bug” to capture a bug report from the watch
-
On the watch, you will observe a notification card with the text “Bug report #X is being generated”. It can take up to 20 minutes for the bug report to be generated and transferred to your phone.
-
Once the bug report is done, the notification card on the watch changes to “Bug report #X captured” and you will receive a notification on the phone that reads “Wearable bug report finished.
-
Tap to send." Tap on this notification and email the bug report to a pre populated email address
Instructions on your companion phone or tablets (Android)
- On your Android device, go to Settings > About phone or About tablet.
- At the bottom of the screen, touch 'Build number' seven times in quick succession. You’ll see a message saying you’re now in developer mode.
- Press Back to go back to the main Settings screen.
- Touch Developer options.
- At the top of the screen, make sure 'Developer options' is set to ON.
- Check the box next to USB debugging.
- Check the box next to Bug report shortcut.
- Reproduce the issue or error message on your phone or tablet. It’s important that your device logs at least one occurrence of the problem.
- Immediately after seeing the issue, press and hold the power button until the power menu appears.
- Select Take bug report, then select Report in the dialog that follows.
- After a significant delay -- up to two minutes -- your phone or tablet will vibrate and display a notification saying ‘Bug report captured’. Touch the notification to open Gmail with the report attached. +After replying to this message, you can disable developer mode and bug reports by going to Settings > Developer Options and sliding the top toggle to OFF.
du...@gmail.com
I can't seem to access this issue from my original user (this issue doesn't load in 3 browsers and 2 computers), so I'm posting the bug report from this user.
I have followed the following steps:
1. Run an app with the following permission:
<uses-permission-sdk-23 android:name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS"/>
2. Run either one of the two pieces of code:
// Will fail silently with ActivityTaskManager system_server I START u0 {act=android.settings.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS dat=package:cmp=com.google.android.apps.wearable.settings/com.google.android.clockwork.settings.FakeSettingsActivity}
val intent = Intent(Settings.ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS)
intent.setData(Uri.parse("package:" + context.packageName));
context.startActivity(intent);
// Will crash the app with android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.IGNORE_BATTERY_OPTIMIZATION_SETTINGS dat=package: }
val intent = Intent(Settings.ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS)
intent.setData(Uri.parse("package:" + context.packageName));
context.startActivity(intent);
I executed the first piece of code and then the second, and captured a dump state. See here (shared with android-bugreport@google.com):
https://drive.google.com/drive/folders/1VTzRUWLs0zekwXkYybG9GhoItWLfU7p_?usp=drive_link
I have followed the following steps:
1. Run an app with the following permission:
<uses-permission-sdk-23 android:name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS"/>
2. Run either one of the two pieces of code:
// Will fail silently with ActivityTaskManager system_server I START u0 {act=android.settings.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS dat=package:cmp=com.google.android.apps.wearable.settings/com.google.android.clockwork.settings.FakeSettingsActivity}
val intent = Intent(Settings.ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS)
intent.setData(Uri.parse("package:" + context.packageName));
context.startActivity(intent);
// Will crash the app with android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.IGNORE_BATTERY_OPTIMIZATION_SETTINGS dat=package: }
val intent = Intent(Settings.ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS)
intent.setData(Uri.parse("package:" + context.packageName));
context.startActivity(intent);
I executed the first piece of code and then the second, and captured a dump state. See here (shared with android-bugreport@google.com):
ca...@gmail.com
Replying via e-mail: I attached the bug report in the above comment.
Would appreciate your assistance.
*Uri*
On Thu, Oct 31, 2024 at 7:10 PM <buganizer-system@google.com> wrote:
Would appreciate your assistance.
*Uri*
On Thu, Oct 31, 2024 at 7:10 PM <buganizer-system@google.com> wrote:
na...@google.com
Thanks for the information. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
du...@gmail.com
That is exactly the reproduction steps.
On Wed., Jan. 13, 2021, 11:20 , <buganizer-system@google.com> wrote:
On Wed., Jan. 13, 2021, 11:20 , <buganizer-system@google.com> wrote:
na...@google.com
Thank you for reporting this issue. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
du...@gmail.com
Thank you for your response. Looking forward for your fix, since is
critical to my business.
On Tue., Jan. 19, 2021, 22:14 , <buganizer-system@google.com> wrote:
critical to my business.
On Tue., Jan. 19, 2021, 22:14 , <buganizer-system@google.com> wrote:
ph...@gmail.com
I my opinion this bug priority and severity should be increased. Built in GPS of any smartwatches is not used at all. This is at least S2 P1. Users are started to use another tracking devices because os this Wear OS issue.
ca...@gmail.com
You either just a dumb ass with some school credits or just, some self
centred ass person Alex that wanna eventually end up in jail ! It's not by
fate you sent me this email to begin with it's not by fate I knew of you
being associated with someone I've known very well here....I know more and
have more than you think yeah Lastnight made my understanding fact I tried
being understanding which just made me look dumb.....you played this long
enough since 2017 in different ways with my devices leave me the fuck alone
over some pussy before everything you have falls in front of your
face.....its not working no more I don't care how the next person
help....your choice!!
On Thu, 7 Jan 2021, 6:06 pm , <buganizer-system@google.com> wrote:
centred ass person Alex that wanna eventually end up in jail ! It's not by
fate you sent me this email to begin with it's not by fate I knew of you
being associated with someone I've known very well here....I know more and
have more than you think yeah Lastnight made my understanding fact I tried
being understanding which just made me look dumb.....you played this long
enough since 2017 in different ways with my devices leave me the fuck alone
over some pussy before everything you have falls in front of your
face.....its not working no more I don't care how the next person
help....your choice!!
On Thu, 7 Jan 2021, 6:06 pm , <buganizer-system@google.com> wrote:
ph...@gmail.com
Why this comment here?
du...@gmail.com
Any news regarding this bug? Come on guys, the location is not working on smartwatches, it's a OS critical BUG :( People are migrating to iWatch because they can track as standalone devices.
na...@google.com
We’ve investigated, but unfortunately have not been able to reproduce it with the steps provided. The watch is able to acquire a GPS signal while outdoors and out of range from from the phone. If you are able to reproduce the issue again or have additional information to help us, please let us know.
na...@google.com
I'll be closing this issue this issue due to not having enough actionable information. If you continue to have this issue, please open a new issue and add the relevant information (bugreport etc.) along with a reference link to this bug for context. Thanks.
du...@gmail.com
In 1 hour I will send you a video of how to reproduce the issue
On Wed., Mar. 17, 2021, 08:49 , <buganizer-system@google.com> wrote:
On Wed., Mar. 17, 2021, 08:49 , <buganizer-system@google.com> wrote:
na...@google.com
du...@gmail.com
Here it is the video with reproduction steps. The current location is never
received when BT is off on phone.
https://photos.app.goo.gl/rb4d5dGQprBXDHwCA
On Wed., Mar. 17, 2021, 08:54 , <buganizer-system@google.com> wrote:
received when BT is off on phone.
On Wed., Mar. 17, 2021, 08:54 , <buganizer-system@google.com> wrote:
du...@gmail.com
If you previously openness the maps on smartwatches ch while by connection
on then switching off the bt from phone and forcing closet the maps on
Smartwatch will result showing the last known location.
It is important to close the bt connection from phone, force close the maps
on Smartwatch, wait 10 mintues and open it again. Move outside with a
Smartwatch that has internet (sim) and see the current location is never
updated even if the location is on on Smartwatch, and has GPS built in
On Wed., Mar. 17, 2021, 10:25 Marius Duna, <dunatv@gmail.com> wrote:
on then switching off the bt from phone and forcing closet the maps on
Smartwatch will result showing the last known location.
It is important to close the bt connection from phone, force close the maps
on Smartwatch, wait 10 mintues and open it again. Move outside with a
Smartwatch that has internet (sim) and see the current location is never
updated even if the location is on on Smartwatch, and has GPS built in
On Wed., Mar. 17, 2021, 10:25 Marius Duna, <dunatv@gmail.com> wrote:
na...@google.com
Thank you for the detailed explanation. I have shared this information with the engineering team. In the meanwhile could you please provide a bugreport from both the watch and the phone, so we can investigate further?
du...@gmail.com
Thank you for your response. Feel free to do it by yourself. Thanks and
Regards
On Wed., Mar. 24, 2021, 04:05 , <buganizer-system@google.com> wrote:
Regards
On Wed., Mar. 24, 2021, 04:05 , <buganizer-system@google.com> wrote:
mr...@gmail.com
Is there any news with this bug?
du...@gmail.com
cd...@gmail.com
Ive got the same issue on my wear OS device. Doesn't matter if I'm on wifi, airplane mode or anything GPS is never found. I've installed Wear GPS Fix which finds satellites but will never fix them so I know the GPS in the device is working but wear OS does not work with it. I've checked with a colleague with a Fossil Gen5 and he has exactly the same issue.
du...@gmail.com
Thanks, finally someone is able to reproduce the critical issue. Google
team wasn't able...
On Tue, 22 Jun 2021, 00:30 , <buganizer-system@google.com> wrote:
team wasn't able...
On Tue, 22 Jun 2021, 00:30 , <buganizer-system@google.com> wrote:
du...@gmail.com
What info do you need? You have the videos link, the steps. Just put the
phone on airplane mode and watch will not receive new locations anymore.
On Wed 29 Sep 2021, 03:34 , <buganizer-system@google.com> wrote:
phone on airplane mode and watch will not receive new locations anymore.
On Wed 29 Sep 2021, 03:34 , <buganizer-system@google.com> wrote:
Description
If the phone is not in range the locations are no more received
I am using various apps/smartwatches to test it even the Google maps on wear device is not capable to track the location.
Correct behavior would be detecting the location if the watch has built in gps and no connection to smartphone.
Wear OS - latest version