Related
Short version: my default setting is vibrate. But recently my phone has been setting to silent without my doing anything. I'll leave me phone alone for an hour or so and when I unlock it I'll have missed calls and texts because it didn't vibrate, and my sound setting will have been changed to "silent" . This doesn't happen all the time, probably about half the time.
Some notes:
- the physical vibration works, I don't believe it's a hardware issue.
- persistent apps I am using: 1 tap quick bar, covinent eyes, onavo extend.
- no custom roms, not rooted.
- I always set my phone back to vibrate. I did to one experiment where I set my ring tone volume at max to see if it would still set itself to silent. Which it did.
- I also did a test where I left my phone out of my pocket to see if maybe I was accidentally hitting the screen and volume rocker. Still changed on its own without me touching it.
- there are no crash reports or force closes as far as I know, and I don't use app killers.
Rant: I'm very disappointed in HTC. The software on this phone is buggy and jittery. And where the heck is my jelly bean?
I uploaded screens of my software information incase anyone's interested.
Please help me with my mystery. I searched the forums for people with similar problems and haven't really found anything.
Thanks!
Sent from my HTC One X using xda app-developers app
its because you have installed onavo extend for sure. same problem here
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
danlo said:
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
Click to expand...
Click to collapse
Were you using headphones that day? I've seen this issue, and I think it's an audio issue (software). When I had this issue, the speakers didn't work either.
Sent from my Nexus 5 using Tapatalk
I was using my Bluetooth headset but I've been using this pair since day 1. This just started happening yesterday.
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
TJCacher said:
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip!
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
I've had the same issue, but I can add that this is happening with games as well. Specifically, asphalt 8 causes this problem. Obviously, when I'm switching between apps, I wouldn't want to kill an ongoing game or song just to make the hotword work. The HC issue is annoying and I hope there's a fix to always keep it live no matter which apps are in the background...
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
My hotword detection also suddenly doesn't work. I've toggled the option in google now settings, rebooted, cleared cache, turned off google music... nothing turns it back on.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
didn't help me. can't figure out what is going on. so frustrating.
---------- Post added at 11:12 PM ---------- Previous post was at 10:26 PM ----------
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
gaetawoo said:
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
Click to expand...
Click to collapse
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
TJCacher said:
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I've talked to them, they know about it and are working on it, but that say it could be an OS issue.. that are trying to figure it out.
This happens to me at least couple times a day. Either Wi-Fi disconnect or a OK Google three I n a row consecutive search. Solution: kill the g search app it will automatically restart and you'll be gtg
Pebble whatsapp notifier causes this same problem. Unchecked it in accessibility and viola! Always listening again..
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
I have the same issue and none of that work for me, it gets stuck with real racing, i force the stop once and it started to work again but minutes later it was hallow again, please help
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
Are you on stock? I thought this was a result of the new launcher in today's version of cm.
Sent from my Nexus 5 using XDA Premium 4 mobile app
xdapro said:
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
Click to expand...
Click to collapse
I love you dude or dudette I was going balled trying to figure this out, thanks a lot!
I found out that the hot word detection only works on the default launcher. If I add the google search widget on apex launcher, I get the search bar with a hollow mic, and hot word detection does not work.
If I use default launcher I got the full mic and hot word detection works.
Sent from my Nexus 5 using xda app-developers app
I'm not at the point where I'm considering putting another ROM on my shiny (literally!) new Z3, but the biggest thing I miss from Slimroms is the apparent total lack of Quiet Hours or anything like it. (In case you don't know, it lets you prevent the phone from making a noise, vibrating, lighting up etc when an incoming text, phone call etc occurs). Apparently, when I'm sleeping I'm always one piece of spam, or an alert that someone's replied to one of my posts here, from being woken up. And i'm not desperate to mute my phone because then i'll miss (potentially) important phone calls.
How are you dealing with this?
Info
poldie said:
I'm not at the point where I'm considering putting another ROM on my shiny (literally!) new Z3, but the biggest thing I miss from Slimroms is the apparent total lack of Quiet Hours or anything like it. (In case you don't know, it lets you prevent the phone from making a noise, vibrating, lighting up etc when an incoming text, phone call etc occurs). Apparently, when I'm sleeping I'm always one piece of spam, or an alert that someone's replied to one of my posts here, from being woken up. And i'm not desperate to mute my phone because then i'll miss (potentially) important phone calls.
How are you dealing with this?
Click to expand...
Click to collapse
there is lots of planner/tasker app in play store for you to manage almost everything you want
:good:
Does the Z3 have the "Smart Connect" app? If so there are automation options there. For example, you can set it to go to complete silent, start the alarm and clock app IF the phone is plugged in and it is between x and y hours.
Smart connect set new event based on time, set time start, volume off, vibrate off, set end time volume up, vibrate on.
Sent from my D6603 using Tapatalk
Smart connect should work fine, but if you want choices I use Agent and it works great.
Got what you need right here:
https://play.google.com/store/apps/details?id=net.epsilonlabs.silence.ads&hl=en
Been using this on my Galaxy S3 for a long time before I upgraded to the Z3. Works great, and is very very low resources. I use it to set my phone to silent at work automatically.
skywalker6705 said:
Got what you need right here:
https://play.google.com/store/apps/details?id=net.epsilonlabs.silence.ads&hl=en
Been using this on my Galaxy S3 for a long time before I upgraded to the Z3. Works great, and is very very low resources. I use it to set my phone to silent at work automatically.
Click to expand...
Click to collapse
Just tried it, but it's no good because I can't silence notifications without silencing incoming phone calls at the same time. The app suggests what I want isn't possible without a custom rom.
Have a look at this absolute fantastic app: https://play.google.com/store/apps/details?id=com.nightskeeper
This is the best quite hours solution in Play Store imo and should be exactly what you need. btw you can define whitelists and the app has an excellent emergency function: when someone calls e.g. more than three times in 5 minutes, the app lets the phone ring although quite hours are activated
Swyped from my insane XZ3 with Tapatalk.
Paulikid said:
Have a look at this absolute fantastic app: https://play.google.com/store/apps/details?id=com.nightskeeper
This is the best quite hours solution in Play Store imo and should be exactly what you need. btw you can define whitelists and the app has an excellent emergency function: when someone calls e.g. more than three times in 5 minutes, the app lets the phone ring although quite hours are activated
Swyped from my insane XZ3 with Tapatalk.
Click to expand...
Click to collapse
Thanks, tried that out but needs too many permissions and it's way too complicated.
skywalker6705 said:
Got what you need right here:
https://play.google.com/store/apps/details?id=net.epsilonlabs.silence.ads&hl=en
Been using this on my Galaxy S3 for a long time before I upgraded to the Z3. Works great, and is very very low resources. I use it to set my phone to silent at work automatically.
Click to expand...
Click to collapse
Tried it; looks good but doesn't work.
corallus said:
Smart connect set new event based on time, set time start, volume off, vibrate off, set end time volume up, vibrate on.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
Using this for now. Limited but at least it works. Using it to turn off data and sound so it's basically like turning the power off.
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Unfortunately i can't help but i am getting the same issue
Sent from my SM-G930F using Tapatalk
I tried applying different dialer apps and they only serve to change the dialer/contact screens, but the default calling screen containing the HOLD button remains unchanged. I found that using Skype as the default dialer fixes this issue since it uses its own dialing/calling screens, but obviously it's not practical to just rely on Skype. So the problem still remains unresolved.
As an update, someone on Reddit posted a download link to the Google dialer app here at: http://forum.xda-developers.com/galaxy-s6/themes-apps/app-google-dialer-t3323432
This installs a new dialer, which actually provides a new calling screen as well, fixing the main issue. The default dialer is better in my opinion since it opens up the dial pad immediately while this one doesn't, but this is a good option at this point
gomulkaaa said:
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Click to expand...
Click to collapse
even worst than calls is when you press it while watching youtube vids, i wish there was a lock of some sort cuz the music stops paying all the sudden
It's embarrassing when I put my clients on hold and don't realise until they don't respond to me. The cheek hold doesn't result in any audible sound so you can be talking for 20 seconds with the other end on hold. I love the S7 edge but I'm contemplating sending it back. I'll try the Google dialer mentioned above first though
Same issue here. I talk on the phone almost 2 hours a day and this is happening at least 1-2 times in every call! Checked my proximity sensor and it's working as it should.
Any workarounds? Maybe someone can edit the phone.apk and remove this stupid button or disable it? I am against rooting but I will definitely root my phone if there's a fix for this.
Damn, I suffer exactly the same issue! Found this googling for ideas...
Very old thread, but I just wanted to give a suggestion to others with the same issue. I really love the Google Phone dialer app, which actually replaces the calling screen during calls with this app's own screen, so you no longer have the Hold button at such an unfortunate location. If you do choose Google's app, I recommend this specific version: http://www.apkmirror.com/apk/google-inc/google-phone/google-phone-2-05-07_rc4-release/google-phone-2-05-07_rc4-android-apk-download/
The caller-ID function by Google actually works with this version, whereas the other .apk files floating around do not have this function working properly.
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
robot1000 said:
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
Click to expand...
Click to collapse
Finally searched for the answer to this today, after several accidental holds on work calls.
The solution above with Google Phone APK worked for me. I just went to SETTINGS - APPLICATIONS - DEFAULT APPLICATIONS and then under Calling App near the top, changed it from Contacts to Phone. . For some reason, I cannot open the phone app itself (gives an error message) but calls do use the phone app rather than Samsung stock dialer.
Turn off screen!! Most phones allow you to turn screen off without interrupting the call.
Same issue with a galaxy A5 2016
Can't understand why samsung doesn't fix it
https://www.sammobile.com/2017/10/21/5-reasons-why-tizen-3-0-for-samsungs-smartwatches-rocks/
"With Tizen 3.0, you can turn off the bezel wake function to prevent the ring from waking up the screen." ?
Watch only mode.
I would be very interested to know how accurate the S3 would be in watch only mode.
Presumably, in watch only mode, the device would have no phone or network connection so would not be able to auto-update itself?
I thought the interval setting (e.g. Permanent) for pulse measurement is also included in Tizen 3? At least on Gear Sport and Fit2 Pro it's included.
bobsie41 said:
I would be very interested to know how accurate the S3 would be in watch only mode.
Presumably, in watch only mode, the device would have no phone or network connection so would not be able to auto-update itself?
Click to expand...
Click to collapse
I don't understand what new functionally the watch only mode brings. The S3 can be put in airplane mode. This turns off cellular, WiFi, and BT, thus making the watch an island unto itself. It's not completely dumb, apps not requiring connectivity still work (ie. stopwatch, HR monitor, calendar, S Pay) and previously inputted data is still available. In this mode, the battery will last for several days. The biggest drain will be the watch face.
BTW, auto updates can be turned off. It's a setting in the Gear Manager app.
we are still waiting tizen 3
IMHO we have to wait longer...
Not expect too "soon".
If we have luck then maybe as Xmas "gift" in late December.
Best Regards
I'm not launching nuclear missles or solving the national debt so most of the upgrades don't impact me. Mine does what I want it to do now and I'm afraid an "improvement" will screw up a good thing. A new OS is a risk just to get rid of the little clock on the top when I'm in Standalone.
afblangley said:
I don't understand what new functionally the watch only mode brings. The S3 can be put in airplane mode. This turns off cellular, WiFi, and BT, thus making the watch an island unto itself. It's not completely dumb, apps not requiring connectivity still work (ie. stopwatch, HR monitor, calendar, S Pay) and previously inputted data is still available. In this mode, the battery will last for several days. The biggest drain will be the watch face.
BTW, auto updates can be turned off. It's a setting in the Gear Manager app.
Click to expand...
Click to collapse
In watch only mode, the watch can last for several weeks, not just several days.
unfortunately they forgot to mention a terrible new feature: notifications are instantly dismissed by the sleep gesture.
the watch has a "wake up" gesture which wakes the screen when you turn your wrist to look at it, but enabling it would already force the inverse on you as well.
turning your watch away from your face(or towards you while not in an upright standing position, which is why it's such a failure) will make it go back to sleep.
this was annoying enough before version 3, but now this will also dismiss notification pop-ups.
this means the watch now frequently keeps marking new notifications as read and dismissing them before I even get a chance to read them.
so I receive a notification, I turn my wrist to look at it, and I'm presented with my watchface with no notification or unread-marker.
so now whenever I receive a notification I have to rotate the bezel or swipe into the notification history to see the notification, when I should just be able to see it instantly.
I was under the 2.3.2.4 version. I am to go under the 2.3.2.3 version and the miracle the update 3.0.0.1 came fast in case for information
Not yet rollout to my s3. Just curious If the whatsapp notification issue is fixed or not.
getter1 said:
Not yet rollout to my s3. Just curious If the whatsapp notification issue is fixed or not.
Click to expand...
Click to collapse
If you mean reading last messages...
No, it's not fixed.
Sent from my HTC 10 using XDA Labs
UA Record issue with Tizen 3
It also broke UA Record app. After update UA started, pause button worked (used for my rest between set of exercises performed in gym) but when I tried to use Resume button - application stopped and I had back again my watchface. No exercises recorded. So I decided to reinstall app and what? App is freeezing on it's start screen and after few minutes I have ma watchface back again. Till now it was the only app used by my so often and now it's a sh...t. Does anytime Samsung have to spoil good working things?
Update. Wow. today is working. However another issue - I tried to add new widget in a Quick panel and what? I have message "Installing ... " since two hours and nothing more
watch is lagging after 3.0.0.1 update, any fix coming
Maik268 said:
If you mean reading last messages...
No, it's not fixed.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sad... thanks!
Maik268 said:
If you mean reading last messages...
No, it's not fixed.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Why are they so ignorant about this issue? Havent any of the engineers at samsung tried to actually use this watch on daily life?! I am so bored of using another app to fix samsung's fault