Related
I just hate this. The phone might have more than 2 hours battery, but still disables the music player, the radio and a bunch of other stuff saying that battery is too low. Is there anyway to tweak this out?
Personally I love this feature. Coming from multiple Nokia's which used to give me about 10 seconds advance warning before going completely dead, it is refreshing to have a phone which detects well ahead of time that it should take action to avoid running out of juice entirely (and does something about it).
Sent from my GT-I9000 using XDA App
I agree that it is a good idea, but it gives a too early warning. It starts doing this when you have hours of battery juice left.
Especially the photo function annoys me; sometimes I just HAVE to take THAT unique picture!
Sent from my GT-I9000 using XDA App
Quite agree thats annoying (atleast a bit too early).
However, it does not change the fact that this is posted in wrong forum.
is possible disable it?
I hate this feature as well.... I was watching a movie on a plane, and with 10 minutes left in the movie, the damn phone wouldn't let me watch it!! I'm ok with the warnings, please do tell me when my battery is low, but don't restrict me! I want to be able to do whatever I want to MY phone, whenever I want, regardless of how much battery is left... If I have 10 min left of battery and I want to spend those last 10 min of battery watching a movie or listening to music, then LET ME! This is a lousy feature.... Android phones should have an advanced mode that could disable all these crappy features that are clearly geared toward the ignorant consumer group.
Yea I hate this feature, sometimes I need to take one picture but i cant since i have "low" battery..
I really wish there was a fix to disable that =\
Instead of editing each app which disables based on battery life, could we possibly modify the file tht holds the current battery value (if there is one), make it say 30 and change its permissions to read only. Just a thought, awaiting responses.
+1 on hating the restricting feature, at least allow turning the stupid thing off in the settings menu. I rather my phone dies while taking a video rather then preventing me of taking it in the 1st place.
Yes, this is stupid and annoying. I was at some car diagnostics guy who read can errors from my car, and I was taking photos to note them... My battery turned 19 and I wasn't able to took one last picture. So fuc#@%# useless and annoying
Okay folks, I wonder if anyone out there can help... My One is randomly vibrating once, with no notification, and I can't figure out why.
Other threads point to similar issues but not the same problem I have. I've been troubleshooting a lot, but can't narrow it down much. What I know so far:
Appears random. Not a particular time, battery level etc
No notifications appear in the bar. It can happen even when I'm looking at the phone and there is no visual indicator.
I have a Pebble watch, so most notifications can and do come through to the watch - no notifications on it when the vibrate happens.
It also doesn't seem to be any kind of dropped Bluetooth connection with my Pebble, as the Pebble doesn't notify of a lost connection like it normally would.
I have also read threads for other HTC phones where it pointed to nfc being switched on. While I do usually leave NFC on, the vibrate still happens even when I disabled NFC
.
I was holding off until Vodafone decide to release the Sense 6 update, but I'm not holding my breath there...
Is there anything that I could investigate? I was trying to avoid rooting or modding the phone for as long possible, but would be prepared to do it. However, I don't really fancy going down that road if the problem will still be there.
Suggestions appreciated!
paulgildea said:
Okay folks, I wonder if anyone out there can help... My One is randomly vibrating once, with no notification, and I can't figure out why.
Other threads point to similar issues but not the same problem I have. I've been troubleshooting a lot, but can't narrow it down much. What I know so far:
Appears random. Not a particular time, battery level etc
No notifications appear in the bar. It can happen even when I'm looking at the phone and there is no visual indicator.
I have a Pebble watch, so most notifications can and do come through to the watch - no notifications on it when the vibrate happens.
It also doesn't seem to be any kind of dropped Bluetooth connection with my Pebble, as the Pebble doesn't notify of a lost connection like it normally would.
I have also read threads for other HTC phones where it pointed to nfc being switched on. While I do usually leave NFC on, the vibrate still happens even when I disabled NFC
.
I was holding off until Vodafone decide to release the Sense 6 update, but I'm not holding my breath there...
Is there anything that I could investigate? I was trying to avoid rooting or modding the phone for as long possible, but would be prepared to do it. However, I don't really fancy going down that road if the problem will still be there.
Suggestions appreciated!
Click to expand...
Click to collapse
If your phone is not modified in any way, the best thing to do is take it to service
Can't think of a good sig
http://tomhorsley.com/rants/doze-mode.html
I'm definitely reverting back to 5.1.1 when I get the time and energy to fool with it .
sounds like that was written by someone who hasn't even tried marshmallow yet. I have yet to experience any missed notifications, alarms or any issues relating to time in any way. If some apps are being affected by this then its a sign to the developer to fix their ****ty code because all of my apps relating to time at all have been working just fine and alot of them are still the same version they were on lollipop. Doze has improved my batter significantly. It sounds like this article was probably written by a developer who cant code properly and instead of improving his skills he'd rather complain and convince everyone to stay away from updates because he is unwilling to evolve. Even the article looks like it was written in paint...
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
That author seems to think that Marshmallow's Doze is a horrible thing that breaks all apps that rely on background services, namely alarms and notifications, and couldn't possibly be fixed in 10 years (rather than a few months) due to Google's horrible mistake (rather than devs not fixing their code).
Frankly, it sounds like a bunch of hyperbole.
Sent from my ALCATEL ONE TOUCH Fierce using Tapatalk
He's wrong about how doze works. And if he's in the camp that doesn't understand it nor wants to rewrite his app. Then yeh he's the idiot group that Google is targeting and was writing garbage code anyway.
lol complete nonsense, my alarm has worked everyday since i flashed M, even on dev previews...the only issues i have with M are really the "slow to connect wifi when using toggles" and the weird wifi consumption on battery stats
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Kustaa said:
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
Click to expand...
Click to collapse
This actually happened with me a couple of days back, I was travelling, so I put my phone connected to a power bank and went for a nap, woke up to see phone switched off, switching it on throws me a 2nd September date set on my device. Had to manually set the date as no network was available to automatically set the date from servers.
Ubichinon said:
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Click to expand...
Click to collapse
This I had been noticing these days just because of WhatsApp Web. When in standby, WhatsApp Web shows phone not connected error. Just waking the phone reconnects to the WiFi, but happens every 30-40mins.
I have a feeling that folks who never see these problems have their phones charging at night and doze mode doesn't happen when you are charging. I have no convenient way to charge my phone near my bed, so it is not charging and totally idle all night. Email and messaging completely stops. Only the stock alarm clock works. My medication reminder stops working. It might as well be turned off completely. Plus when you do wake up and turn on the phone, all the pent up alerts come through and scare the hell out of you. I hate doze mode.
Settings -> Battery -> ... (menu)-> Battery Optimization --> All apps --> Select whatsapp, etc... and select not optimized.
Test again.
You're welcome.
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Claghorn said:
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Click to expand...
Click to collapse
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Dennis de Swart said:
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Click to expand...
Click to collapse
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Achilles. said:
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks, I will look into that. I'd like to keep Mashmallow as a whole if possible. I think it is a good update in general.
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Claghorn said:
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Click to expand...
Click to collapse
I will look into this over the weekend. I find it odd that there isn't simply a switch to turn Doze off, which is a pity. It seems to me it's part of saving energy in general. A switch under Battery would do nicely. It should not be this complicated. That said, I think the UI of Marshmallow is silky smooth, much better than Lollipop. Marshmallow in general in good. It' just this that annoys me.
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
ElwOOd_CbGp said:
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
Click to expand...
Click to collapse
I get the feeling Google assumes the customer is a developer. A few examples:
- The Nexus 5 does have a notification light: I didn't know until I read 5 reviews and even then I couldn't find any documentation on it. Needed an external app to get it working.
- Battery indicator: I like to have small numbers indicating battery charge: it could be done by hacking KitKat and Lollipop I think. Then at Marshmallow finally there's a (hidden) switch.
- I don't recall having any user guide in the Nexus 5 package. Not that I needed one. But some landing page doing a walkthrough would have been nice. Although there are some walkthroughs in every app
Not fatal flaws, but you wonder why does it need to be that difficult. It scares people away. Not me. I handed the Nexus 5 to some friends on numerous occasions and most found it too "empty". As for me, I want all developer stuff on. So it suprised me, there is no Doze fine tuning. Again, overall I give the Nexus a 8 or 9 out of 10. It fits me. In general I like it. So it's just constructive criticism. The empty layout and raw speed of the Nexus 5 works good in development of apps afterall.
Last night I ran an adb command (generated by the doze mode editor app) to set inactive_to to 24 hours (86400000 milliseconds). I then set an alarm for the next morning in the "Alarm Clock Plus" app (which completely ceased to function after Marshmallow showed up). This morning, the alarm actually went off on time, but the big "Dismiss" button it draws on the screen was totally non-functional. I had to hit the power button to get control (which then caused a popup saying alarm clock plus was non-responsive). I have no idea what caused all that behavior, but at least the alarm actually went off.
Also, with doze mode essentially disabled (in theory anyway), the power dropped from 100% in the evening all the way down to 97% in the morning.
With the exception to facebook and game type apps, Google's apps are the only ones I find that excessively waste resourxes and need to be forced to sleep. If they would get off the constant location polling, media scanning, and logging or at least tone it down a bit some they wouldnt need to implement thier half baked versions of solutions that they hijacked from xda devs
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
Have you tried doing a reset?
When I got mine, it upgraded straight away so I thought "great", it's a clean watch, there can't be anything wrong with it.
Nope..
Apps didn't work.
Battery life was rubbish.
Did a reset when i got a new phone.
Apps worked without issue.
Battery takes me from 5am through to 9pm with 40% left at least, LTE is off but aod is on.
Yes - reset the watch to factory when I deleted the app, pairing etc - went totally to step 0 across the board, short of formatting over the phone itself. But I did one more reset after that last night and charged it all night. So far this morning (wrote most of my note locally last night, posted this morning) I'm holding up pretty well. Nothing running on the watch - bone stock with phone shut off and Ok Google off. 2.5 hours @ 91%. Fingers crossed that this was a fluke. But in my experience today is probably the fluke LOL.
wig said:
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
Click to expand...
Click to collapse
Sorry to bump an old thread how is your usage the last few months? I'm confused between buying this and the huawei watch 2.
Thank you @wig
Sent from my Sony Xperia XZ1 using XDA Labs
No worries. The LGWS has been pretty decent. It seems to me that its bluetooth radio gets confused. For example, when I'm in my car, sometimes the watch disconnects or the car bluetooth disconnects. When I'm in my home office where the WIFI router is, the watch seems to disconnect as well. Beyond these weird edge cases, it stays connected and just works. The disconnecting isn't really bothering me as much as the fact that when it does, it tries to connect over WIFI and drains the battery pretty quickly. I've kind of learned to live with it and the hardware in this watch is better than the HW2. That being said, my experience with connectivity was much better with the HW2. Not sure how it's going now for those who have it. Android Wear has updated both the IOS app and the core OS and apps numerous times since I posted this. So for all I know, HW2 is doing the same thing these days. It does appear Google is trying.
As for the LGWS - go to ebay, find yourself a new one that's super cheap. I ended up getting mine for around $170 which made it a no brainer. One of these days I'll throw a SIM in it just to try it, but have bigger fish to fry at the moment.
Best of luck.
P.S. I just saw you have an android phone - so your mileage may vary and in fact will probably be MUCH better. I'm on iPhone which is 90% of the issue.
wig said:
No worries. The LGWS has been pretty decent. It seems to me that its bluetooth radio gets confused. For example, when I'm in my car, sometimes the watch disconnects or the car bluetooth disconnects. When I'm in my home office where the WIFI router is, the watch seems to disconnect as well. Beyond these weird edge cases, it stays connected and just works. The disconnecting isn't really bothering me as much as the fact that when it does, it tries to connect over WIFI and drains the battery pretty quickly. I've kind of learned to live with it and the hardware in this watch is better than the HW2. That being said, my experience with connectivity was much better with the HW2. Not sure how it's going now for those who have it. Android Wear has updated both the IOS app and the core OS and apps numerous times since I posted this. So for all I know, HW2 is doing the same thing these days. It does appear Google is trying.
As for the LGWS - go to ebay, find yourself a new one that's super cheap. I ended up getting mine for around $170 which made it a no brainer. One of these days I'll throw a SIM in it just to try it, but have bigger fish to fry at the moment.
Best of luck.
P.S. I just saw you have an android phone - so your mileage may vary and in fact will probably be MUCH better. I'm on iPhone which is 90% of the issue.
Click to expand...
Click to collapse
Thank you so much for your reply I think you have sold me the watch. Now I can continue my search to try and find one. Seems at $170 that's definitely a bargain let me know if your wanting to sell ?
Sent from my Sony Xperia XZ1 using XDA Labs
First of all, I really like my galaxy watch 5 pro. I often take my LTE version when I go running, connected to my Galaxy buds live. There are certain issues I have, which drive me bananas:
When it passes a marker (for example, every mile), it breaks up the music, briefly. Usually only for the first one or two markers. And then it reappears later, sometimes. Definitely an intermittent issue. It's like, it pauses and tries to figure out what it is supposed to do: the watch is like 'Do I pause,? do I stop the music? Do I act like there's a major blast of Wi-Fi in the area news connection?' it's like it has a conflict going on inside it.
Secondly even when I've got it on do not disturb, if someone phones me or there are certain kinds of messages that go to my phone, they still forward!! The worst is if somebody calls me, it stops the music! And it's almost impossible to stop the call while running! And I can't restart the music without really fiddling around with the watch, and that is really difficult to do without losing your pace.
It's not a great running watch in my opinion. Samsung needs to fix some things here.
Am I the only one? Maybe it's my watch.
ekerbuddyeker said:
First of all, I really like my galaxy watch 5 pro. I often take my LTE version when I go running, connected to my Galaxy buds live. There are certain issues I have, which drive me bananas:
When it passes a marker (for example, every mile), it breaks up the music, briefly. Usually only for the first one or two markers. And then it reappears later, sometimes. Definitely an intermittent issue. It's like, it pauses and tries to figure out what it is supposed to do: the watch is like 'Do I pause,? do I stop the music? Do I act like there's a major blast of Wi-Fi in the area news connection?' it's like it has a conflict going on inside it.
Secondly even when I've got it on do not disturb, if someone phones me or there are certain kinds of messages that go to my phone, they still forward!! The worst is if somebody calls me, it stops the music! And it's almost impossible to stop the call while running! And I can't restart the music without really fiddling around with the watch, and that is really difficult to do without losing your pace.
It's not a great running watch in my opinion. Samsung needs to fix some things here.
Am I the only one? Maybe it's my watch.
Click to expand...
Click to collapse
A possible reason for the break in the music could be that you are switching between cell towers and there is possibly a gap in the signals, happens to me sometimes when driving down motorways. or maybe there is a setting somewhere to inform you when you reach these markers and its briefly trying to silently play another sound idk dont own the watch so cant really say what the problem is except for some general things it could be.
Secondly bugs bugs and more bugs, dislike them a lot myself lol
What fitness app are you using? I don't wear earbuds when running but Strava seems to work really well. A good fitness app will allow you to customize notifications. Maybe consider disabling wireless data when running.
It drives me bananas. I went on a run today. As it starts telling me my lap info, the music cuts out, the voice is a bit broken up, and then, when I'm in an area with trees, it must confuse the gps which makes the watch decide that I have 'lapped', and it starts giving me new lap times every 5 seconds!!! Makes it impossible to use with earbuds. MYne it is the combination of everything going on, and I admit it's a lot, data, voice ready, music to Bluetooth, gps, Samsung health app running etc... But they sell this as a WORKING solution, and it so often doesn't work properly (for me).
ekerbuddyeker said:
It drives me bananas. I went on a run today. As it starts telling me my lap info, the music cuts out, the voice is a bit broken up, and then, when I'm in an area with trees, it must confuse the gps which makes the watch decide that I have 'lapped', and it starts giving me new lap times every 5 seconds!!! Makes it impossible to use with earbuds. MYne it is the combination of everything going on, and I admit it's a lot, data, voice ready, music to Bluetooth, gps, Samsung health app running etc... But they sell this as a WORKING solution, and it so often doesn't work properly (for me).
Click to expand...
Click to collapse
I just went for a 2 mile walk while listening to earbuds through the watch and Samsung Health was monitoring it and it worked perfectly.
Ok, I may have solved the issue. Will be testing it soon. I switched from Samsung to Google text so speech engine.