After having some issues with wear OS I decided to try Lineage OS Rom. Surprisingly when it came to setting up my Ticwatch I found that the Wear OS app and the Mobvoi app had a completely different set up, like I was using a new app or a different phone.
On the stock ROM I had issues with notifications coming through, assistant activating & calls via the watch.
However the same apps on LOS ROM went through a completely different set up including full assistant walk through, pairing the watch as hands free for calls and as a trusted device for unlocking the phone.
The Mobvoi app was also went through a different set up for fitness etc.
The watch seemed to work 10 times better.
Going back to stock emui I now have the original issues back, the app wasn't as thorough during set up. I've been through every setting and there is definitely functions missing.
Quite annoying that the changes made on Emui are stopping major functions from working.
Has anyone else noticed anything similar?
Related
I have an LG G3, and I immediately paired & connected my R watch to it while running on 5.0.2 L no problem. When I noticed a few glitches with my blue tooth music play-back in my car, I decided to restore a previous KitKat nandroid I had backed up. I don't attribute the BT glitches to the watch. I had recently flashed the Lollipop rom hadn't driven with it a lot with BT. I'm thinking it's the rom.
Anyway, when I restored my old KitKat nanny, I had a problem connecting the watch. It paired just fine from my BT screen on my phone. I got the code confirmation on both devices and clicked "yes", but my watch just sits at "connecting...". After a while, it returns to the watch face. When I go back into my watch settings, it says "disconnected". I can click "connect" on the watch, but it goes through the same loop.
I realize there are device and software details left out of this OP, but I wonder if anyone can see something basic that I'm doing wrong based on what I've said. I tried unpairing and starting from scratch. Maybe there's something with the Kitkat rom (Vanir 4.4.4) that doesn't play nice with the watch, but maybe it's the way I'm pairing through the phone rather than through the watch.
Any ideas?
I have a galaxy note 3 running a leaked version of lollipop and I am having nothing but disconnection issues
I know when the watch was still on KK and my phone was I didn't experience any..
So don't know if it's my rom either or the watch since the lollipop update on that..
I'm toying with going back to KK on my phone and trying again to see if it fixes the issue
Will keep an eye on this thread and see what others say.
Whenever I restore a phone backup I always have to do a full Reset on the watch or it won't sync. Apparently the sync mechanism can't just pick up wherever and continue.
The only annoyance with this is having the "OK GOOGLE" banner hanging in there and getting rid of it (how I'd love to just kill it once and for all...) and the initial unskippable tutorial on the watch (dtto, kill it with fire!)
Apart from that, it is quite simple to reset and setup the watch again.
1) hold the crown on the watch
2) do a Reset from the menu
3) unpair the watch on the phone
4) when the watch starts up, pair it from the inside of the Android Wear handheld app.
I don't think there's a difference between choosing "Forget XXX watch" from the Android Wear menu before pairing or not in this scenario.
Back on kit kat on phone and watch is running perfect not disconnected once today
Hi,
I had been using Android Auto with a Huawei P8 lite. It never crashed, but only the response times where a bit sluggish.
I got a brand new Samsung 5 Neo, and after setting up the phone, there was immediately an update to Marshmallow.
When I started using Android Auto, I was pleased to see that the overall experience was faster and better than my Huawei.
But for some reason, during (longer) drives, my Spotify (and Google Music), would crash in the middle of a song. (first a stutter, it could happen after two songs, five songs, there is no logic in it). After it crashes, Google Maps becomes unresponsive. The only thing that helps is disconnecting the cable.
After reading the web, I learned that it could have been because of the marshmallow update.
So after trying all the usual fixes (rebooting phone before using Android Auto, keep data always alive, etc), I decided to downgrade to Android 5.0.
At first sight, I thought everything was solved, but after a few days, the exact same problem started to appear
I will now try to clear the app cache, and reboot the phone each time, but I'm a bit dissapointed that it doens't work as it's supposed to work.
Any tips, remarks are welcome.
Downgrading to Android 5 didn't help, so I flashed it to a version of Android 6.
Magically the issue got away. And interesting fact, after a few days without any problem, a song started to stutter (I thought "not again"), but there was a message on android auto that said: "no internet connection", and the song paused (without the whole head unit crashing). Interesting enough, the whole playlist is available offline on my phone. So I guess, it's some sort of background data the music app needs (maybe the syncing to last.fm), that caused the issue. But glad, for some reason in this build, they handle the exception better.
Downgrading to Android 5 didn't help, so I flashed it to a version of Android 6.
Magically the issue got away. And interesting fact, after a few days without any problem, a song started to stutter (I thought "not again"), but there was a message on android auto that said: "no internet connection", and the song paused (without the whole head unit crashing). Interesting enough, the whole playlist is available offline on my phone. So I guess, it's some sort of background data the music app needs (maybe the syncing to last.fm), that caused the issue. But glad, for some reason in this build, they handle the exception better.
I really didn't know where to pitch this issue, but here's the problem:
Google fit has been working nicely for a long time on my GWR, but recently I installed a health app on the phone, and it required GF to be installed on the phone to pull the steps etc off it. However as soon as I installed it on the phone, fit on the watch stopped syncing to the GF server. It just refused, for days. I checked the web app, nothing there either. I uninstalled both, reinstalled, changed settings, tried everything really. Not just that - but when I turned on the body sensors option in the phone app, it just started using the phone's sensors, which is no good., I wanted it to read the watch's data. It just wouldn't have it.
Eventually I got the watch syncing again, but with a lot of messing about, and the phone app not installed.
Has anyone else got the same problems, or can shed any light of this perhaps? A quick scan online shows quite a few have had these sync issues over the last few years.
EDIT: Just looked at the history on both the watch and the web view, and the steps for most days completely differs between the two. That is if the watch app can be bothered to sync at all, sometimes patches of empty entries on the web view will eventually appear with data, sometimes several days later. Yet still be mismatched.
GWR: OS 7.1.1, AW 2.0 (2.8.0.182823779)
S8+: OS 7.0 (G955FXXU1AQL5)
I've seen this problem all over the internet for quite a few years on many different models of phones and Android. I have it happening on both my 6P and Note 9, figured I'd post here since it's the newer device.
It's mainly happening with Greenify and App Volume Control Pro. I already did all the fixes I've found online, such as making sure the apps are not being optimized by battery optimization settings, and whitelisting them in any where else that might be causing them to be disabled. The only thing I've not done is lock the apps in the recent apps viewer from being closed when you tap close all because it shouldn't matter anyways, I don't leave them open (truthfully I rarely open the actual apps anyways). They don't need to be left open to do their things, that's what persistent notifications are for, to make sure they keep running in the background. Now that I notice though, Greenify does not have a persistent notification on the Note for some reason. I checked all settings, it's not blocked or hidden anywhere. IDK. And AVCP doesn't have one on either device, don't think it ever has for as long as I've been using it. Can only lock apps in the recent list on the Note anyways afaik. (But this issue isn't happening to anything else under accessibility access settings)
I don't use programs like CCleaner or anything, the only thing similar I have on the devices is Samsung's Device Maintenance app, but that obviously is only on the Note so I don't see how it's the cause since it's happening in the 6P as well.
Both phones are running Oreo 8.1. The only thing not stock is that I have elementalx and TWRP installed on the 6P, otherwise it's the stock ROM and whatnot, no root.
This problem happens what I will say is randomly, because it can happen after rebooting the phone or after waking it up. Whether that seems to be 10 minutes or 10 hours doesn't seem to matter. Checking my accessibility has just become habit. The way I first found this was happening was because AVCP makes a toast message when I open an app that I have it set to change the volume for, like a game. The messages were not popping up so I looked into things a bit more when it kept happening.
Anyone have any suggestions other than what's been said in the past?
Same Problem, my device : Vivo Nex S 8/128gb Android Oreo 8.1 no stock rom it has Funtouch OS and no solution for the Bug/Issue.
I don´t know what keeps accessibility resetting several times a day. very annoying!
The knowledge in your article is very useful, thank you
Hello all,
I have the 960U1 US Unlocked version of the Note 9 I've had since Day 1 release of last August. It's quite the powerhouse of a phone, and has everything of what you want in a smartphone. I was aggravated by how late the Pie update came, but I never expected how many issues came along with that changed the user experience since Oreo. After updating to Pie, I did a factory reset for a clean run but then I ran into these following issues:
Download, installing, and uninstalling apps from the Play store: I've tried to download apps, which get stuck at 99% or 100%, but then just hangs there to not install. Same thing with uninstalling. It'll say uninstall for an abnormally long time.
GPS issues: I travel frequently on weekends. Sometimes I would like to pull up my Google Maps timeline to review where I went and at what times. One weekend, I went out of town 3 hours away from home and yet my timeline showed me saying I stayed all day and night where my Home location is. Map guidance still worked, but it still showed me that my "current location" was still being at home.
Bluetooth Power indicator pop up: This is a recent issue I found that other Samsung users in other forums encountered as well. I have a Sony WI-1000x Bluetooth neckband that does extremely well for all the bells and whistles it does. I've noticed that after I factory reset again after experiencing the previous 2 issues to get them fixed, there is a pop up that keeps appearing every 10 or so seconds that tell me my headset is battery at 100%. I have found no way of disabling that, and I had to unpair/pair my headset as well as clear Bluetooth data in System App settings to try and get rid of it. Good thing it hasn't been doing that after several tries, but now there is another issue with BT.
Bluetooth notification sound output: I've noticed when my BT is connected, I don't hear notifications from my text messaging app, e-mail, Arlo, and social media apps. I've checked to see that my Sound settings are all up and running as it should be. Then I went to try and play a notification sound, and nothing came out of my phone speakers. It only played through the headset itself, and that's an annoyance as I don't wear them all the time in my ear unless I'm using it for phone calls or listening to media. It seems to be an Android Pie issue and I have yet to find a permanent solution as this wasn't an issue before on Oreo. The only workaround I've found is using the SmartThings Audio Output toolbar in the Notifications drop down and select to play Media from my device. The notification sounds work then, and I can still answer calls through my headset. But it's a dumb issue that I have to manually set this whenever I want to go back to listening media.
The Note 9 is a great phone despite the small shortcomings it had before the Pie update. Now it's after the Pie update, all these issues come up and I don't understand what happened in what Samsung did. I'm almost tempted in calling Samsung to ask if my phone just somehow became defective, but I don't want to have something done and they send me some refurbished model when I kept my phone in near mint condition. What are your guys' thoughts about the issues I've had and what solutions would you suggest?
GigaSPX said:
Hello all,
I have the 960U1 US Unlocked version of the Note 9 I've had since Day 1 release of last August. It's quite the powerhouse of a phone, and has everything of what you want in a smartphone. I was aggravated by how late the Pie update came, but I never expected how many issues came along with that changed the user experience since Oreo. After updating to Pie, I did a factory reset for a clean run but then I ran into these following issues:
Download, installing, and uninstalling apps from the Play store: I've tried to download apps, which get stuck at 99% or 100%, but then just hangs there to not install. Same thing with uninstalling. It'll say uninstall for an abnormally long time.
GPS issues: I travel frequently on weekends. Sometimes I would like to pull up my Google Maps timeline to review where I went and at what times. One weekend, I went out of town 3 hours away from home and yet my timeline showed me saying I stayed all day and night where my Home location is. Map guidance still worked, but it still showed me that my "current location" was still being at home.
Bluetooth Power indicator pop up: This is a recent issue I found that other Samsung users in other forums encountered as well. I have a Sony WI-1000x Bluetooth neckband that does extremely well for all the bells and whistles it does. I've noticed that after I factory reset again after experiencing the previous 2 issues to get them fixed, there is a pop up that keeps appearing every 10 or so seconds that tell me my headset is battery at 100%. I have found no way of disabling that, and I had to unpair/pair my headset as well as clear Bluetooth data in System App settings to try and get rid of it. Good thing it hasn't been doing that after several tries, but now there is another issue with BT.
Bluetooth notification sound output: I've noticed when my BT is connected, I don't hear notifications from my text messaging app, e-mail, Arlo, and social media apps. I've checked to see that my Sound settings are all up and running as it should be. Then I went to try and play a notification sound, and nothing came out of my phone speakers. It only played through the headset itself, and that's an annoyance as I don't wear them all the time in my ear unless I'm using it for phone calls or listening to media. It seems to be an Android Pie issue and I have yet to find a permanent solution as this wasn't an issue before on Oreo. The only workaround I've found is using the SmartThings Audio Output toolbar in the Notifications drop down and select to play Media from my device. The notification sounds work then, and I can still answer calls through my headset. But it's a dumb issue that I have to manually set this whenever I want to go back to listening media.
The Note 9 is a great phone despite the small shortcomings it had before the Pie update. Now it's after the Pie update, all these issues come up and I don't understand what happened in what Samsung did. I'm almost tempted in calling Samsung to ask if my phone just somehow became defective, but I don't want to have something done and they send me some refurbished model when I kept my phone in near mint condition. What are your guys' thoughts about the issues I've had and what solutions would you suggest?
Click to expand...
Click to collapse
I had issues with android pie sprint model. Ended up flashing android oreo back and no more issues. Theirs guides out their all u need to do is download the correct files and flash file ,real easy process just follow instructions. Do your research and ull be good
GigaSPX said:
...
I have the 960U1 US Unlocked version of the Note 9...
The Note 9 is a great phone despite the small shortcomings it had before the Pie update...
What are your guys' thoughts about the issues I've had and what solutions would you suggest?
Click to expand...
Click to collapse
timex300 said:
I had issues with android pie sprint model. Ended up flashing android oreo back and no more issues. Theirs guides out their all u need to do is download the correct files and flash file ,real easy process just follow instructions. Do your research and ull be good
Click to expand...
Click to collapse
Hey GigaSPX, noting you have a 960U1 US Unlocked, I've been working on this step-by-step for a 960U1:
Confirm These Steps to Downgrade US Unlocked SM-N960U1 from Pie to Oreo
If you decide to go this route, take a look and share your experience.
Thanks for the links and guide tips to downgrade to Oreo, but I enjoy One UI too much to give up on that user experience. I still have my Note 8 and I know it benefited significantly from the pie update to have it last all day unlike before on Oreo.
GigaSPX said:
Thanks for the links and guide tips to downgrade to Oreo, but I enjoy One UI too much to give up on that user experience. I still have my Note 8 and I know it benefited significantly from the pie update to have it last all day unlike before on Oreo.
Click to expand...
Click to collapse
You're welcome.
Good to know about your Pie experience on your Note 8.