Good evening all!
Am I the only one that received a Gear Manager Update today?
I received something earlier today but I can't see any change in the software version number.
Alex
All you buddayyyy
Yes, it is updated for me.
I got the update too but have not noticed any differences.
According to change log, it is updated to support Gear Circle.
Where is the change log?
b0Ne83 said:
Where is the change log?
Click to expand...
Click to collapse
where you downloaded the app.
I also got today. Noticed some changes:
1. While calling, Mute button is added to the main screen and volume slider as well
2. In drop down menu, a different icon is shown when connected to Bluetooth or remote connection via phone
3. Battery life improved, me thinks.
4. Auto Call forwarding added to Call Menu
5. Smoother Interface
Adding tasks is still not supported.
Akram. said:
I also got today. Noticed some changes:
1. While calling, Mute button is added to the main screen and volume slider as well
2. In drop down menu, a different icon is shown when connected to Bluetooth or remote connection via phone
3. Battery life improved, me thinks.
4. Auto Call forwarding added to Call Menu
5. Smoother Interface
Click to expand...
Click to collapse
It is a Gear Manager update on the phone side we are talking about here, not Gear SFirmwre update.
foxbat121 said:
It is a Gear Manager update on the phone side we are talking about here, not Gear SFirmwre update.
Click to expand...
Click to collapse
Yup, but i have noticed when I owned the Galaxy Gear and the gear 2 that some Gear manager updates would change things like this and even Svoice! Sometimes even the vibration would change on the gear 2.... Remember this watch is also an extension of your phone. Most of the watches services and apps are running on your phone first.
But none of what Akram posted occurred without a firmware updated. I noticed zero changes on my watch. So, I think he is just confused this thread as talking of Gear firmware update which is not even new for most of us (there is a day-one update and that's about it).
foxbat121 said:
But none of what Akram posted occurred without a firmware updated. I noticed zero changes on my watch. So, I think he is just confused this thread as talking of Gear firmware update which is not even new for most of us (there is a day-one update and that's about it).
Click to expand...
Click to collapse
i do, also the battery usage is a littel better. I'm normally down to 81% by now and its sitting at 93 with heavy usage.
I have seen good days and bad days on battery life. So, today it appears to be the bad day for me. Already at 81% 1 hour after took off the charger with BT connection. So, no, the update to Gear Manager doesn't change anything for me for battery life.
If the app update causes the phone connection to the device to draw less power from the device (less poling for notifications, updating time and better location management) I could see how it could have an affect on the Gear S battery life ... I haven't noticed any differences though.
Don't know if it happenedwith this update, but I see a watch face that is very cool and more features on it, #of steps,readable date, weather, etc.
Keep it coming samsung!
The update appears to have broken having apps open automatically (or by touching Open app on device) when a notification pops up on your watch. This has happened with previous updates then the next update fixes that issue and now this one broke it again. To use this function, you need to have Smart relay checked in Notifications in the Gear Manager.
Related
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
Click to expand...
Click to collapse
I'm not getting extended disconnects; just failing to answer questions about half the time. If it fails, I can try again and it often works.
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
I'm experiencing the exact same thing on my Gear Live. Its paired with stock S5. I just tried for like 5 minutes to get it to save a note and it would think for a while and then just disconnect.
mosi76 said:
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
Click to expand...
Click to collapse
This is exactly everything I've noticed as well.. Seems to have gotten waaaaay worse after yesterday's update
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Click to expand...
Click to collapse
Happens to me, too. Completely random though. Repairing the watch fixes it, but it is indeed annoying. We will have to wait for Google to fix this together with all the other bugs.
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Thanks, I'll give it a shot.
What about trying to reply using voice within a received Hangout or email? I'm always getting an error "Can't reach Google at the moment". Am I the only one? But if I select a default reply from the available list, I can reply with no problems...
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
I found it only improves it a little, but it's not a full fix. Sometimes my watch works the whole day without connection problems and then suddenly multiple times in a short period of time.
I've read that the gear live has the same problem, so I guess it's android wear wide. Hopefully google is going to bring out an update soon which fixes all the annoying bugs.
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
Like stated by the previous post this is a simple fix. The only one that can truly fix the issue is Google. I have used this for a week and not had any issues relating to bluetooth disconnecting. One issue I noticed was Google Search sometimes breaks after using it multiple times in a short amount of time. I usually have to just force stop Google Search every 3 days also.
This has always been an issue I had even before Android Wear. If I used Google Now too much I couldn't get the "Okay Google" command to work. It seems this also happen when using wear too much. A simple force stop fixed it, but it is annoying when you want it to just work. Another thing I noticed was custom roms are having issues with Android Wear in my case.
Every time I use a custom rom on my Nexus 5 and try to use my LG G Watch I have constant disconnects and Google Search issues. Maybe Android Wear isn't playing nice with custom roms, but after using rooted stock for the last week I am experience very few issues compared to when using different custom roms. I noticed whenever I used a custom rom I got the "Connected, running sync loop". I have no idea if this causes the constant disconnects, but on stock with the simple "Connected" I have no issues.
I started out with the same problem using a Gear Live with a Sony Xperia Z1 Compact. The thing that fixed it for me was turning off battery saving mode on the phone - called stamina on the Xperia - that was turning off BT to save power. Now I rarely see the disconnected message.
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
SIlvRav said:
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
Click to expand...
Click to collapse
I have found this issue for Android Wear for my LG G watch R and Galaxy Note 3. If I use watchmaker, I have it set to vibrate twice upon disconnect and vibrate once upon connect. It is constantly disconnecting and immediately reconnecting (2 vibrations, followed immediately by a single vibration). This is extremely annoying and I see the same problem stated in the beginning, the voice search is constantly disconnected or cannot reach the server.
Cheers,
B.D.
I've been using my Gear S in combination with a Note Edge since February 2, and the battery life was good (typically 50% or so at the end of the day). About two weeks ago the Gear S started draining really fast, running out of battery before my day was over. As part of my troubleshooting, I factory reset both the Gear S and the Note Edge, and ran several tests with and without Bluetooth and 3G (I left GPS and WiFi off all the time). The only thing that is causing the rapid battery drain is the Bluetooth connection to the phone (i.e., connected remotely via 3G = great battery life; connected via Bluetooth = crappy-ass battery life).
Is anyone else experiencing this particular scenario (Bluetooth connection recently starting to drain your battery)?
Thanks for any help you may provide.
Have you installed any new apps that could cause this and it functions only on Bluetooth? I had wearable widgets and clock which were not even active but seemed to cause battery drain and slowness.
nktwister said:
Have you installed any new apps that could cause this and it functions only on Bluetooth? I had wearable widgets and clock which were not even active but seemed to cause battery drain and slowness.
Click to expand...
Click to collapse
No, I haven't installed any apps on the Gear S since I reset it. It would be nice to have a battery monitoring app.
OK, maybe the charger is different and the battery is not being charged at full power..
nktwister said:
OK, maybe the charger is different and the battery is not being charged at full power..
Click to expand...
Click to collapse
The battery gets charged to 100% using the original power supply and charging cradle. And like I said before, the watch lasts forever when connected via 3G, so it can't be a battery issue. I was thinking it was a bad Gear Manager update, but then a lot of people would be having the same issue.
There are many reports of BT battery drain after recent Gear Manager update (a month or two ago). Some solved it by re-install the Gear Manager. Not everyone is affected.
foxbat121 said:
There are many reports of BT battery drain after recent Gear Manager update (a month or two ago). Some solved it by re-install the Gear Manager. Not everyone is affected.
Click to expand...
Click to collapse
I guess you can count me as one of the affected ones. Reinstalling Gear Manager is not doing diddly squat. I ran another test: no apps whatsoever, the only variable being the connection to the phone via Bluetooth. 45% over 5.5 hours during the night, with Do Not Disturb on. Balls...
foxbat121 said:
There are many reports of BT battery drain after recent Gear Manager update (a month or two ago). Some solved it by re-install the Gear Manager. Not everyone is affected.
Click to expand...
Click to collapse
Here's what I've found being with a Gear since V1 was first released. Gear Manager is a PIA and when updates to it or the device occur flaky things can happen. Whenever I update either I always do the following in the order shown:
Unpair the Gear in BT settings so it's no longer a connectable BT device
Hard reset the Gear by long pressing the power button and doing a recovery
In application manager on my phone I go through each Gear-related Samsung and/or third party app installed and delete it making sure the core Gear Manager app is the last uninstalled. Some of the secondary Gear apps come back after they're are installed but get removed with the removal of the core Gear App at the end
Reinstall Gear Manager from Samsung Apps on my phone and go through the whole pairing process again with the Gear being seen by the phone and the phone being seen by the Gear as "virgin."
Even though my G-S was virgin, I set it up enough to take the AT&T update and once it was updated went through all the steps above.
I've had no issues like call forwarding not working, connections are fantastic, and battery life seems reasonable (I've had the G-S less than a week so don't have anything to compare it to). I never had some of the other issues people reported on the Gear I either.
The main difference I would think between connecting via BT and 3G would be the sync of the notifications - on BT it would be synchronous and trying to get all notifications and on 3G the phone just pushes notifications and possibly the watch is not waiting for them.. maybe check the application list in Gear manager to see if any app could be sending a lot of notifications or continuously running..
I recently just did a factory reset on both the Gear S and the Note 4. I used to have around 300 apps that would auto download every time I logged into my Google account. I deleted my Google back up so those apps wouldn't download again. I don't have nearly as many apps on both devices and my battery life has improved dramatically. The more apps you have, the more your battery drains. It doesn't matter if its a smartwatch or a phone.
Thanks for all your suggestions. I had no apps installed on the watch at all, and I only had notifications turned on for texts. Since I had just factory reset the Note Edge, it was also a fresh installation of Gear Manager, and only one Google account set up on the phone - no other apps. So, empty phone, empty watch, and the battery was still draining like crazy when connected via Bluetooth. Then all of a sudden, it fixed itself, without me doing anything. No new version of the Manager, no changing of settings, nothing.
I'm glad it's fixed, but it's bugging me that I have no clue how it got fixed. I've been installing apps on the phone, and everything is still OK. Now I'm going to install apps on the watch, and I have a feeling it'll all be OK with that too.
I have had the same issue and in fact the battery drains fast if gear s bluetooth is on even without it being connected, I have factory reset it and reinstalled gear manager with almost zero apps connected and still get fast drainage, battery dies in less than 3 hours, no idea what to do next apart from Samsung warranty
Hello while I really love this phone it's got a few annoyances. I created this thread to see if I'm the only one and if anyone else reports any more.
Frequent FC of the Google and Google photos app
Random things happening if phone is not restarted frequently (eg all sound went quiet until restart)
Keyboard skin doesn't change for lock screen
Let me know if your having these issues or if you have any not listed.
Bugs I've had so far:
- one reboot while using snapchat
- sometimes it takes a lot of time for the device to wake up
- autobrightness is terrible in low light conditions(stuttering and inconsistence)
- while streaming audio with bluetooth in my car the radio somtimes shows audio paused while it's still playing. In this case remote controls also stop working
My xperience
I only had the phone for four days, because I found a dead pixel on my screen. I am currently expecting a replacement or a refund. During that time I noticed that changing the theme does not change anything else besides the home and lock screens. There were some random drops in wi-fi connection. I also noticed a couple of stutters here and there. Two or three apps crashed on exit. I also miss the picture album widget with the swiping pictures on screen. That is not present here.
So no one seems to be getting any issues like me ?
Sent from my Sony Xperia XZ1 using XDA Labs
kistigun said:
Bugs I've had so far:
- one reboot while using snapchat
- sometimes it takes a lot of time for the device to wake up
- autobrightness is terrible in low light conditions(stuttering and inconsistence)
- while streaming audio with bluetooth in my car the radio somtimes shows audio paused while it's still playing. In this case remote controls also stop working
Click to expand...
Click to collapse
Agree about the autobrightness, it's inconsistent and keeps changing in low light conditions. Makes reading an absolute chore.
I'd also love a way to quick enable glove mode, my previous Samsung had that in the drawer menu.
for those of you who have owned sony phones, has there been timely updates to fix bugs like the ones being reported in this thread? some companies like to release updates with new features but without fixing bugs so im just making sure before i pull the trigger on an XZ1
thank you all!
I've had this issue after the recent update to build 47.1.A.2.324 . Google assistant doesnt work with Music ( default sony music app) . it used to work before this update, and it doesnt work anymore and asks me to set google music as the default music service.
WiFi signal drops when I hold my hand on the backside.
1. The phone seems to reboot itself frequently.
2. Sometimes no sound when alarm is going off. I overslept once because of this
3. Quite often no sound when phone is ringing. Need to reboot the phone for it to act normal again.
4. Crashing when picking up phone. Call goes to call waiting and phone rings again. When picking up there is a very loud biping sound throughout the conversation. This goes away when rebooting.
NockIt said:
1. The phone seems to reboot itself frequently.
2. Sometimes no sound when alarm is going off. I overslept once because of this
3. Quite often no sound when phone is ringing. Need to reboot the phone for it to act normal again.
4. Crashing when picking up phone. Call goes to call waiting and phone rings again. When picking up there is a very loud biping sound throughout the conversation. This goes away when rebooting.
Click to expand...
Click to collapse
I've aso had problem 2 & 3. I also overslept myself 3 times over this, very anoying!!!
Edit: found this on the sony forum on how to get smart lock menu back:
https://talk.sonymobile.com/t5/Xperia-XZ1/47-1-A-2-374-new-update-13-10/m-p/1268608#M467
Its a android 8 bug
Solution:
Disable trusted agents on security settings.
Restart phone
Enable security settings. Thats it.
NockIt said:
1. The phone seems to reboot itself frequently.
Click to expand...
Click to collapse
Oh god, i was going to change to the XZ1 this week after returning my Compact due to the rebooting, I thought they'd be different enough internals to not have the same issue. I guess its a Sony/Oreo issue then.
a freeze occourred waking up the phone from camera button. The camera button was set to "open and shot"
I had to reboot via vol+ and power...
Updated to 47.1.A.2.374 yesterday, sadly all bugs remain the same. And I can add one; the smart lock menu is empty and all smart lock function dont work anymore
kistigun said:
Updated to 47.1.A.2.374 yesterday, sadly all bugs remain the same. And I can add one; the smart lock menu is empty and all smart lock function dont work anymore
Click to expand...
Click to collapse
Its a android 8 bug
Solution:
Disable trusted agents on security settings.
Restart phone
Enable security settings. Thats it.
I can add another issue. That is bluetooth delayed when I watch video on youtube and play some games.
NockIt said:
1. The phone seems to reboot itself frequently.
2. Sometimes no sound when alarm is going off. I overslept once because of this
3. Quite often no sound when phone is ringing. Need to reboot the phone for it to act normal again.
4. Crashing when picking up phone. Call goes to call waiting and phone rings again. When picking up there is a very loud biping sound throughout the conversation. This goes away when rebooting.
Click to expand...
Click to collapse
Similar problems here even on the latest build 47.1.A.2.374. Also Google assistant frequently stops responding and then the phone becomes unresponsive and eventually restarts without prompting. Never had problems like this on the XZ when that was released. Seems to be some issues with Google services on this Sony hardware. Suggest everyone having issues pound the send feedback option and hope that someone in Google or Sony are listening!
My notification tones keep going off at random intervals and nothing's in the status bar that could've set it off.
Can confirm random reboots.
Bought the phone from clove and Amazon.
Amazon was horrendous reboots during setting the phone up - returned.
The clove one had no reboots until today, several times.
Some fkd up kernal CPU bogusness going on here.
Sony need to sort this.
I'll check with matlog tomorrow if anything stands out
Phone Idle is always 1st entry of battery drain list, does anyone have similar situation?
roytam1 said:
Phone Idle is always 1st entry of battery drain list, does anyone have similar situation?
Click to expand...
Click to collapse
same here.... battery life is suffering. Stock firmware was better
I use Spotify in my car and have set it to manually manage and allow it to run in the background..
However, the audio always cuts off to after a while after the screen goes off.
When I wake the phone I see Spotify still playing (audio via fone now, but this means it's kept running in background which is good) and Bluetooth remains connected to the device. It's like the android system just stops sending audio via Bluetooth after a while
Does anyone know how to solve this? My only workaround now is to keep the phone awake via an app like Google maps...
I'm on mate 10 pro. 8.0.0.131 c636
Sent from my BLA-L29 using Tapatalk
Same for me with deezer app and car audio which hadn't any disconnects on my other mobiles. No help though....
I tried to change the codec in developer options, which didn't change. I hadn't any bluetooth cutoff since then (couple of days now). Maybe coincidence.
I have discovered the same problem just today (my mate pro is fairly new). It is clearly a software bug. It also fails to update the track name on my car stereo - still shows the first track name even several tracks in.
To get it playing again I turned Bluetooth on and off. Quite annoying. I hope it gets fixed.
happens on my P10, happens on my mate10 pro as well.
It's not a bug, just unintuitive EMUI.
Fix Launch settings for Spotify and add the app on the "Ignore battery optimization"-list under Special Access menu.
It can be difficult to find. Search for "Special" and it will pop up, or click
Settings/Apps & notifications/Apps/Settings/Special Access/ignore battery optimization/
vembryrsig9 said:
It's not a bug, just unintuitive EMUI.
Fix Launch settings for Spotify and add the app on the "Ignore battery optimization"-list under Special Access menu.
It can be difficult to find. Search for "Special" and it will pop up, or click
Settings/Apps & notifications/Apps/Settings/Special Access/ignore battery optimization/
Click to expand...
Click to collapse
I did try this and it still doesn't work.
I don't think it's an issue with the app itself as this also happens on stock music app on stock launcher.
Audio cuts out, plays via the phone speakers so the app itself isn't being optimized or shutdown.. Seems like the Bluetooth function is though
Sent from my BLA-L29 using Tapatalk
I set spotify up with battery optimisation off and with manual launch in battery settings as part of my initial set up. That is not the cause of this Bluetooth problem, unfortunately.
Mine cuts off regardless of app and screentime... so even if i am playing music behind navigation, the bluetooth audio still pushes via the phone after a while
bluetooth still showing connected to the device.
The issue seems resolved for me, but don't know exactly what fixed it.
The only 2 things I did was to manually manage all apps(battery settings), prevent almost all apps from running in background except the audio apps (music/Spotify, and other impt widgets.. Which was already done previously)
And reset defaults on developer mode (not that i changed anything)
See if u guys have any luck with this
Sent from my BLA-L29 using Tapatalk
Hey guys,
Greetings from a Mediapad owner. (EMUI should have it's own subforum)
I first experienced this issue, or a similar issue for myself a few days ago - audio would cut out with the screen off, and would be choppy at best with the screen on (but my music player in the background). The music player itself would stay open, and as soon as I put in the foreground, audio would resume from where it left off (i.e. playback would be paused while the app was in the background).
I am also looking for insight. My suspicion is that EMUI's launch feature is responsible for killing an Android system process related to media, bluetooth, and/or battery optimization in this instance. Launch only allows you to specify preferences for user apps; system apps are managed automatically by Launch no?
Here is the insight I can provide:
This issue went away for me as soon as I plugged in a charger. Connected to a charger, EMUI's battery optimization is apparently less aggressive.
After trying random things, I once again attempted to stream music in the background without a charger plugged in. Eventually, the issue fixed itself. I am not sure if I did anything to accomplish that, however there are two things that may have contributed:
As with another poster above, I tried to change the bluetooth driver in Developer Settings. I was unsuccessful and there was no change for a while after.
The other thing I did, is I found what I think is the standard Android battery usage screen that EMUI hides from us, and I played around with it. This screen showed me that "Android System" was not set to ignore battery optimization. I tried to change that and couldn't. Really, I didn't change anything, but in this process it is possible that an Android system app relating to battery optimization may have been reopened after having been killed off?
The only way I know how to access that screen btw, is to download an app titled 'pNutsAnySettings' and then click on the tile with the battery percentage on it.
I had exactly the same issue with my Mate 10 pro in my car. Audio would cut off from car and continue playing on the phone but the car said it was still connected to the phone. I had the same kind of issue with my Garmin Forerunner watch which would constantly disconnect throughout the day meaning I missed smart notifications.
I found on another thread (Cant remember what one) that if you have root, use Titanium Backup to freeze the Power Genius app. Since doing this a few weeks ago I have not had the issue again in the car and my Garmin now stays connected all day and night
djclark25 said:
I found on another thread (Cant remember what one) that if you have root, use Titanium Backup to freeze the Power Genius app. Since doing this a few weeks ago I have not had the issue again in the car and my Garmin now stays connected all day and night
Click to expand...
Click to collapse
I read that same thing as well - but freezing the Power Genius app (via Xposed Edge Pro) didn't help in my case. Maybe it would have if I had rebooted, or something.
In any event, I believe that freezing the Power Genius app partially if not fully disables EMUI's launch feature, which I generally like...
This problem returned for me last night. I turned bluetooth off and back on again. That fixed it.
My mate 10 Pro does this too. 2011 Camaro SS with MyLink conversion. I go into BY, hit the info icon and disconnects the media playback then reconnect it. Works for a few days. Comes back. No clue why
(Unrooted stock btw)
Update: I finally disabled Power Genius and rebooted. No more pesky issues and if anything my battery life has improved. Only differences I observe (on my Mediapad): there are no longer 'app usage' battery stats inside the EMUI settings app (I can access them by other means), and Launch now needs to be managed through the Settings app (rather than the App Info screen).
thref23 said:
Update: I finally disabled Power Genius and rebooted. No more pesky issues and if anything my battery life has improved. Only differences I observe (on my Mediapad): there are no longer 'app usage' battery stats inside the EMUI settings app (I can access them by other means), and Launch now needs to be managed through the Settings app (rather than the App Info screen).
Click to expand...
Click to collapse
What app now
leo72793 said:
What app now
Click to expand...
Click to collapse
The app you need to freeze or disable is Power Genius. It's a component of EMUI. It won't show up in your main app list, but if you are rooted you can use an app like Titanium or Service Disabler to do the trick. If you aren't rooted - this is a prime example of why people root.
If that's what you were asking?
Hi,
yesterday i received my Amazfit Verge.
I could not test it completely before an upgrade to OS 3.2.0.7 (I was running 3.2.0.5) came in.
I tested this watch on 2 phones (samsung s9 plus and a Motorola G4 plus).
Before testing I did a reset of the watch.
Both show the same problem, when testing the warnings the incoming call warning does not work.
When a call comes in the warning also does not work on the watch, all other warnings work.
Is this a problem with the watch or is it a software glitch in 3.2.0.7 and how to solve this?
Do you have latest version of Amazfit app installed on phone with all permissions granted? If yes, try adding the phone/contacts/favorites to the notification settings in the app.
deboopi2 said:
Is this a problem with the watch or is it a software glitch in 3.2.0.7 and how to solve this?
Click to expand...
Click to collapse
Interesting - I just checked it with my Verge on 3.2.0.7. The first time I tried, it took relatively long - about 10 secconds - before I received the notification on my watch. The seccond time it came right away.
Have you tried to let it ring a little longer?
I'm running on release 2.6.7
Phone/contacts/favorites are hidden by the smart filter, they should not get selected.
I selected them anyway but the result is exactly the same
I've been waiting for 20 seconds now and I still do not have a notification on the watch.
I have exact same problem. Notification works only when I enable BT call function on watches.
I have the same problem, incoming calls are not visible. Samsung Galaxy S8 Android 9.
same problem here with a Samsung S10.....anyone solved it???
deboopi2 said:
Hi,
yesterday i received my Amazfit Verge.
I could not test it completely before an upgrade to OS 3.2.0.7 (I was running 3.2.0.5) came in.
I tested this watch on 2 phones (samsung s9 plus and a Motorola G4 plus).
Before testing I did a reset of the watch.
Both show the same problem, when testing the warnings the incoming call warning does not work.
When a call comes in the warning also does not work on the watch, all other warnings work.
Is this a problem with the watch or is it a software glitch in 3.2.0.7 and how to solve this?
Click to expand...
Click to collapse
Did you marked in Watch App, notification section call/phone? Do you getting all others notifications like message, calendar and ect.? In 3rd screenshot https://play.google.com/store/apps/details?id=com.huami.watch.hmwatchmanager you can see notification area. Here you must add all apps from yours phone from which you want to get notifications. If will not help, try reset factory settings of watch. For me working everything fine. Also, if in watch you will not see caller name, need to give permission of that (in smartphone). By the way i hope you understand that watch with smartphone must be connected via bluetooth?
P.S. I got 3 updates, now i got latest where was integrated Alexa (working in US only). With all software versions which i had and have working all notifications very well, included call. I guest you will not added it in Watch App notification section that. I have not Xiaomi brand smartphone too. Brand of smartphone havn't any effect in getting notifications I hope But maybe China manufactor don't like Samsung, so... you can chat with Amazfit support us.amazfit.com. But i'm really don't want to believe that this is true. Maybe something bad is with Samsung smartphones, cos this problem have a lot of people here
I had a Xiaomi Mi9 before and all worked very well!!
Now that i switched to a S10 with all the same settings that i had before, the notifications (whatsapp, telegram, gmail..ecc..) are perfect BUT if someone calls me the Verge vibrate for a second, the screen lights up and...stop!! no name, not even number calling.....when the call attempt ends it also notify me the missing call....!! I am pretty sure this problem is connected to samsung phones with pie but i really hope there is a way to fix it because i would hate to sell my Verge.....
agv83 said:
I had a Xiaomi Mi9 before and all worked very well!!
Now that i switched to a S10 with all the same settings that i had before, the notifications (whatsapp, telegram, gmail..ecc..) are perfect BUT if someone calls me the Verge vibrate for a second, the screen lights up and...stop!! no name, not even number calling.....when the call attempt ends it also notify me the missing call....!! I am pretty sure this problem is connected to samsung phones with pie but i really hope there is a way to fix it because i would hate to sell my Verge.....
Click to expand...
Click to collapse
I starting to think that this is not Verge problem, but problem is with Samsung smartphones, even newest models. I have none Xiaomi smartphone and it's working fine. It's not Samsung too. So i advise you to chat with Samsung support too, but ofcourse try to talk with Amazfit support us.amazfit.com (it's US, but only this support have live chat) if will be closed chat, try en.amazfit.com via mail support, but keep in mind today is saturday, so answer via mail or chat will be opened only from monday. It can be that these models working with each other with this problem
Answer from Amazfit Support:
Amazfit Support (Amazfit)
May 12, 23:02 PDT
Hi Milan,
Thank you for contacting Amazfit Customer Support. We apologize if the product caused you any inconvenience!
Could you please let us know where did you purchase your watch? Please kindly attempt the following steps:
1. On the home screen of the Amazfit Watch App tap Me in the lower right hand corner tap Setting tap Notifications setting tap the toggle switch to enable Push notifications tap App notification setting and select app in the list to enable or disable the specific notifications.
2. Make sure Not push, phone’s screen is ON is turned off.
3. Check if you enabled the Silent mode on the watch. If you enabled silent mode, you can't receive any notifications at all.
4. Make sure your phone notification bar is functioning. Please note that alerts will only appear on watch if they pop up on phone.
5. Open Amazfit Watch APP MeSettingSystem PermissionsAccess notificationstoggle on Amazfit Watch if it’s off. If it’s on, turn it off and on, reboot your phone, restart App and try again.
6.Open Amazfit Watch APPMeSettingSystem PermissionsAutostart tap Background operation permission setting to add Amazfit
Watch APP to the white list of background operation permission.
7. Open Amazfit Watch App Me Setting System Permissions Read contacts to allow Amazfit watch app to read your contacts in settings or the security app on your phone.
If the issue persists, please send us all the pictures and show us how you enabled the permissions. Then submit a feedback from the watch and Amazfit Watch App. Also send us the Amazfit ID to help us locate the issue.
Sincerely,
Seven
Amazfit Support
everything is checked and there is no incoming call anyway
yeah same preset answer they give to anyone.......
i also have all checked but the problem persists!!
I think it's standard form of answer to costumer. So consultants doing just copy - paste process from base of information. I think company request to do that from theirs workers, so don't be suprised. By the way i got some too about battery, but it's better to get answer like this one if don't get it at all, i had some examples when i did not got answers at all or answers into my questions
Any idea how to fix it?
zapas17 said:
Any idea how to fix it?
Click to expand...
Click to collapse
Try to do factory reset of watch. I tried several times and after last reset i could hear caller when i answered to ring. But i need to check again that. By the way i did some reset of watch without restore of my data. So maybe this can help you.
No helps. I think it's problem new software for verge.
Still happens on my new Note 10 too, damn it! Coming from Note8 I havent experienced this before.