So i read on android police and a couple other sources that last week an update for the 2nd Gen moto 360 allowed for continuous heart rate monitoring. Thing is I see no where that that is the case.
My moto body still says I have 0/30 minutes of elevated heart rate despite being very active. There is no setting for it or place where it logs.
Does anyone have a lil insight into this?
if you open the heart rate app, it just keeps taking your rate continuously. it doesn't take it once, then tell you to tap for rescan...it just keeps going
jayochs said:
if you open the heart rate app, it just keeps taking your rate continuously. it doesn't take it once, then tell you to tap for rescan...it just keeps going
Click to expand...
Click to collapse
I've ready from several sources that the Moto Body app takes readings all throughout the day (which i believe because i can see the sensor going from time to time), but that it doesn't display it anywhere on the app. However if you sync google fit and moto body then google fit will display the readings taken by moto body.
Related
Has anyone discovered the correct motion for waking up the LG G watch with the twisting wrist motion.
I can never consistently reproduce the motion. At times the device doesn't even turn on not matter how hard I flick my wrist. Leaving always on feature kills battery.
The moto 360 has no troubles recognizing the wake up motions I make.
I wish I had you're problem. Mine constantly wakes up any time I move without me wanting it to.
From my messing around with the watch after I bought it I have had a 100% success rate waking the watch up this way:
Twist your wrist towards you and then stop moving your wrist once the watch face is facing you (as if your going to talk into the watch face)
I have an LG G Watch with 5.0.1 since a few days and I tried and sent back an identical LG G watch on 4.4W.1 a while ago and didn't experience it. Basically, I am noticing that after leaving the watch alone lying somewhere (I don't wear it at home) for some time (can't really say how long but at least an hour, I think) the display turns OFF. A single tap and it wakes up and then works "normally" until the next time...
The other G Watch with the older Wear version didn't have this behaviour so is this a feature of the latest Wear version (or possibly an LG-exclusive mod to squeeze even more battery life) or is it maybe an "issue"..?
I am saying this especially because I installed the Slumber app to automatically turn the display OFF while charging but realized that it's easier and more elegantly done by simply choosing the new "Theater mode" in Android Wear 5.0.1 and uninstalled the app. I don't know if what I am seeing is due to having installed Slumber but I really don't think so.
Does anybody know for sure what it is and how it exactly works..?
TIA
I was just about to post about this I think it's a bug though... I don't use a Slumber app or anything, I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Anyone know what the problem is or how to fix it?
philessthanthree said:
I think it's a bug though... I don't use a Slumber app or anything,
Click to expand...
Click to collapse
Just to be clear, I don't use it anymore and uninstalled it just after getting the 5.0.1 update with its Theater mode. My worry was that having had it installed triggered this behaviour but since you get it without ever installing it I can put that to rest.
I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Click to expand...
Click to collapse
Have you ever got it while it is on your wrist..?
Reading this I just removed my g-watch and after a few minutes I see that my screen was OFF. Never happen when I have watch on my wrist the last 2 days. Screen alaways ON and turn on with movement OFF. So yes it is a new feature of the last update 5.01.
Same here, it happened twice on the table, and once on my wrist this morning.
Must be something like the ambient mode in Moto 360 that does this. For one moment I thought I accidentally triggered the cinema mode.
I always take my watch off at work and the screen keeps turning off after 30 minutes. I did a full reset in case it was an overhang from the old version but it's still turning off.
So based on all of the above replies it seems it's a feature of the latest Android Wear. I am not calling it a bug because, except for a single reported case from our friend with the Moto 360, it seems to never happen while wearing it, so the logic appears to be "save the battery when not in use".
Just to "investigate" it some more, I am trying to time it and confirm it's 30 minutes for me too like StuBFrost says, and may you all please confirm you have Ambient turned ON (i.e. the display is always ON) and state whether you have the new Tilt to wake up setting ON (i.e. the Display lights up from its dimmed state when you tilt your wrist).
My settings are Display always ON and Tilt to wake up OFF.
It would be good to have some more reports from owners of different Wear smartwatches, to this end I posted also in the general Android Wear forum but no replies so far. I am going to update that post with our findings and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think it might be a good feature to keep ON in many cases but it absolutely should be an *option*!
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
StuBFrost said:
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
Click to expand...
Click to collapse
Trying to time it, I think I can say (I am still trying to cover all of the different scenarios) that any event which normally wakes the display up to normal brightness (i.e. an incoming call) resets the countdown. BTW, I think you are right and it's 30 minutes off the wirst with no movement, no tapping on it and no event like the ones just mentioned. "Normal" incoming notifications don't seem to reset the countdown.
Like I said, I don't think it's a bad idea in and of itself (I would use it in most cases) but they should have made it an option! And, ideally, they would let us set the time after which the display turns itself off.
I use and *strongly* prefer Android instead of limited and dumbed down Windows Phone and even worse Apple's useless crap exactly because of its customizability and powerfulness...
"Funny" thing is that from further testing, this feature doesn't kick in while on the charger (which could actually be pretty useful for most people...) LOL
ADDENDUM: the kind of events which resets the countdown to this "deep sleep" state (i.e. an incoming call) also wakes the display up from "deep sleep".
I am running the LG G Watch, version 5.0.1 with accompanying Android Wear app on my phone version 1.0.5
Screen is set to ALWAYS ON.
Tilt to wake is OFF.
It happens BOTH on my wrist and off my wrist. The timing is variable from my limited observation, but I haven't tried to directly time it.
on my lg g watch too
may I ask something related? on mine, it happened to be able to stop display (full black) with a swype from bottom to the top, never been able to do it again. Anybody faced that?
My S6 edge is being very strange, and i am not sure if it was happening all along and i didnt notice it or if it just started recently. but I recently bought an Obliq crystal clear case for the back of my phone, and when i have it on my phone and put it down, i can see the whole case light up red because of the heart rate sensor turning on. This only happens when you put something near the heart rate sensor, so by putting your phone back side down, the heart rate sensor turns on and stays on when its sitting on a table top. I am afraid this is severely hurting the battery life of my phone. Can anyone else tell me if you are experiencing the same problems or do i have a defective phone or do i have a setting out of wack? See a video of the problem on youtube below.
Un install goggle fit. If you have it. From what I've heard its a bug with it
Hi there people. I need your help.
As you may know the moto 360 sport features a barometer among other sensors.
As I have been playing around and developing an app for that I found out that actually it does not work correctly.
To be more precise it gets one reading and then stops until reboot, or random. This should not work like so.
I have contacted several developers and all agreed that the sensor does not work correctly.
That leads me to think that either it's a huge software bug or Motorola has screwed us for 2nd time (1st is battery capacity)
What I am asking from you is to download AID64 (shows sensor info) and check if it works for you.
It will be working if you change location (eg walk, change location, or move your hand). If it does not change then no.
Thanks in advance.
P.S. Similar thread in G+ moto 360 community
i believe you refer to pressure sensor, it stays at 738.0 hPa, no change after movement
noxaro said:
i believe you refer to pressure sensor, it stays at 738.0 hPa, no change after movement
Click to expand...
Click to collapse
Yes man. I have already opened a case with Motorola.
You can compare it to how it changes if your phone has one.
It's a big ffff bug. I hope is SW.
Hi, I just got the notification that the Android 13 update is ready for my phone. But I'm not really sure if it's worth to go through with the update. I wouldn't want to wait another 6 months for stupid fixes needed. If anyone was brave enough to install it let me know how your experience has been so far. Thanks!
CONFIRMED BUGS FOUND BY USERS AFTER THE UPDATE:
Screen flickering when using auto refresh rate. The screen quickly changes between 120hz and lower causing flickering especially on darker tones (from grey to black). This is almost certain to happen, be ready if you choose to go through with the update!
Increased contrast. Screen constrast has been increased requiring increased brightness for outdoor visibility. Poor viewing performance in bright day light and overall darker hues at lower brightness levels
Charging issues. Phones are not charging correctly when turned on, constantly disconnecting. Charging when the phone is off is the only solution. Wireless charging is also affected and unusable due to overheating that stops the phone from chaeging
Moto Secure folder locked. Moto Secure folders cause the phone to crash and can't be unlocked anymore. Do not use Moto Secure folders to avoid data loss!
Ready For broken. If you try to connect your smartphone to the TV no output is displayed
HDR video playback is broken. When trying to play back HDR video from any app it shows as SDR. No brightness increase as it was in Android 12.
POSSIBLE ISSUES:
Overall performance degradation. Some users are experiencing slow downs and an increased heat output from the device
Audio playback not working. Some users are reporting audio not working after boot. Startup sound works as usual
Increased battery consumption
Connectivity issues might appear during calls or mobile data usage. Reports are not clear about specific conditions in which these issue appears
Screen flashes white when waking the device through the fingerprint reader
Fingerprint reader breaks and might show up as not working in the built in diagnostic software
MISSING FEATURES AFTER THE UPDATE:
Dolby app lost the custom EQ setting
WORKAROUNDS:
A device reset might get rid of most of the issues, beside the flashing screen when using auto refresh rate
To fix the auto refresh rate it is possible to lower the maximum refresh rate from 120Hz to 90Hz. Thanks to @mansell68 for posting it in the thread. Download the app https://play.google.com/store/apps/details?id=by4a.setedit22 and change the parameter "peak_refresh_value" to 90. This will solve the issue for now and let the phone switch between 60 and 90Hz correctly.
Read here.
My friend have the edge 30 pro, after update he had the same issue.
I told him to completely reset the phone after update, but he didn't do it.
giacomowrc said:
Read here.
My friend have the edge 30 pro, after update he had the same issue.
I told him to completely reset the phone after update, but he didn't do it.
Click to expand...
Click to collapse
I update my edge about 2 days ago and this is the only issue that i found with, just like says on Lenovo's forums I set the refresh rate on 60hz for the moment until we get an update.
@giacomowrc thank you very much for reporting this issue! I knew there would be something wrong with the update. Motorola just doesn't care anymore.
@iOrizon thank you a lot too for reporting back on the issue. So there's no amount of resetting it to factory that would fix this issue?
@MeltingSnowman tbh this issue doesn't affect me so much so I prefer to wait for a fix instead of reset my phone. There is no a mayor issue that force me to do that, for me at least, and in general I think that is a solid update.
I update it yesterday.
Everything is perfect, no issues, 144hz and automatic refresh working.
Very Stanley and fluid.
With all turner on on the night ONLY consumes 6% of battery on 12 hours.
Great job from Motorola.
Waiting for official a13 update.
@giacomowrc @iOrizon @almmpt you might be having two different releases? The one is asking me to update to is T1SH33.35-23-20. Also I think I got one of the first batch of units since I got it soon after launch. So I might be more affected in case they different hardware revisions that act differently depending on the software.
Also 6% on a 12h night is a bit much to be honest. I wish they addressed the incorrect scheduling that kills this phone's battery but doesn't seem to be the case.
MeltingSnowman said:
@giacomowrc @iOrizon @almmpt you might be having two different releases? The one is asking me to update to is T1SH33.35-23-20. Also I think I got one of the first batch of units since I got it soon after launch. So I might be more affected in case they different hardware revisions that act differently depending on the software.
Also 6% on a 12h night is a bit much to be honest. I wish they addressed the incorrect scheduling that kills this phone's battery but doesn't seem to be the case.
Click to expand...
Click to collapse
I have This.
With bluetooth, WiFi, and paired with Samsung Smartwatch 5 Pro with all sensors enabled.
100% imperial.
I have the Chinese variant and we still haven't received android 13
almmpt said:
I have This.
With bluetooth, WiFi, and paired with Samsung Smartwatch 5 Pro with all sensors enabled.
100% imperial.
Click to expand...
Click to collapse
The wifi and bluetooth pairing with the smartwatch might explain the battery drain, makes sense.
Thanks for the screenshot. But I'm seeing that your play store security updates are stuck to last year and the security patches for the OS are from february. Do they don't get updated with Android 13?
MeltingSnowman said:
The wifi and bluetooth pairing with the smartwatch might explain the battery drain, makes sense.
Thanks for the screenshot. But I'm seeing that your play store security updates are stuck to last year and the security patches for the OS are from february. Do they don't get updated with Android 13?
Click to expand...
Click to collapse
Hi. The security patch is only from february 2023 on A13.
mansell68 said:
Hi. The security patch is only from february 2023 on A13.
Click to expand...
Click to collapse
Bruh, this is so stupid! So the security patch is basically rolled back one month. This doesn't make sense. Thanks for the insight.
I updated a couple of days ago. I feel like the battery drain increased, but maybe it'll bounce back? I definitely like the split data/wifi buttons in the notification - I like turning off unneeded services.
I loved the side bar in 12 and it's still great, but I definitely don't see a reason to give it a permanent on-screen indicator in 13 (the half-transparent bar near the power button). It makes a visual mess if I'm using something that has a scroll bar. Let us turn it off...
Samug11 said:
I updated a couple of days ago. I feel like the battery drain increased, but maybe it'll bounce back? I definitely like the split data/wifi buttons in the notification - I like turning off unneeded services.
I loved the side bar in 12 and it's still great, but I definitely don't see a reason to give it a permanent on-screen indicator in 13 (the half-transparent bar near the power button). It makes a visual mess if I'm using something that has a scroll bar. Let us turn it off...
Click to expand...
Click to collapse
Thanks a lot for the feedback. I was concerned that they would make a mess of it and it happens to be the case, adding to the screen flickering an increased battery drain.
So there's no option to disable the indicator and keep the double tap on the power button to make that side bar appear? What a bummer...
P.S. if you don't mind me asking you have no screen flickering right? Did you get an early batch of the phone or a later one? I'm trying to figure out if they changed hardware revisions for the display and that's causing the flickering. Also any weird colour shifts appearing at night? Like having a darker tint at low/lowest brightness settings?
MeltingSnowman said:
Thanks a lot for the feedback. I was concerned that they would make a mess of it and it happens to be the case, adding to the screen flickering an increased battery drain.
So there's no option to disable the indicator and keep the double tap on the power button to make that side bar appear? What a bummer...
P.S. if you don't mind me asking you have no screen flickering right? Did you get an early batch of the phone or a later one? I'm trying to figure out if they changed hardware revisions for the display and that's causing the flickering. Also any weird colour shifts appearing at night? Like having a darker tint at low/lowest brightness settings?
Click to expand...
Click to collapse
To be fair I hadn't noticed any screen flickering yet, but I keep the refresh rate at 60 Hz.
Samug11 said:
To be fair I hadn't noticed any screen flickering yet, but I keep the refresh rate at 60 Hz.
Click to expand...
Click to collapse
If you don't mind trying, see if auto refresh is bugged.
MeltingSnowman said:
P.S. if you don't mind me asking you have no screen flickering right? Did you get an early batch of the phone or a later one? I'm trying to figure out if they changed hardware revisions for the display and that's causing the flickering. Also any weird colour shifts appearing at night? Like having a darker tint at low/lowest brightness settings?
Click to expand...
Click to collapse
I got the phone the moment it was available in EU - a little over a year ago. Didn't notice anything extraordinary when it comes to colors.
Will try adaptive refresh rate for a few days.
Samug11 said:
I got the phone the moment it was available in EU - a little over a year ago. Didn't notice anything extraordinary when it comes to colors.
Will try adaptive refresh rate for a few days.
Click to expand...
Click to collapse
Mine's from the same batch.
Thank you for being so helpful, I really appreciate it. I can link you the Lenovo forum's thread where people are reporting the issue, if you happen to experience it aswell.
Finally arrived in India. Downloading now and will update on my experience soon