Related
I'm absolutly loving Assist, specifically while driving. However, the volume is really LOUD. It's much louder than the standard notification volume.
Yes, I'm sure it's designed to be loud, but to prevent scaring my family every time it's activated, is there any way to turn the volme on Assist down? I haven't actually tried the volume rockers when Assist is active, since I'm busy driving!
oturn said:
I'm absolutly loving Assist, specifically while driving. However, the volume is really LOUD. It's much louder than the standard notification volume.
Yes, I'm sure it's designed to be loud, but to prevent scaring my family every time it's activated, is there any way to turn the volme on Assist down? I haven't actually tried the volume rockers when Assist is active, since I'm busy driving!
Click to expand...
Click to collapse
Wouldn't that be controlled by the volume slider "Music, Video games & Other media" in sound options? I'm not sure I'm just taking a shot in the dark here.
I really love assist too. However, I only use it to silence my phone at night time before bed and wake in the morning. An option so simple, yet many phones lack it.
Xaroc8 said:
Wouldn't that be controlled by the volume slider "Music, Video games & Other media" in sound options? I'm not sure I'm just taking a shot in the dark here.
I really love assist too. However, I only use it to silence my phone at night time before bed and wake in the morning. An option so simple, yet many phones lack it.
Click to expand...
Click to collapse
You would think so, but I have that slider set to about 60%, and it definitely doesn't appear to change the Assist volume.
oturn said:
You would think so, but I have that slider set to about 60%, and it definitely doesn't appear to change the Assist volume.
Click to expand...
Click to collapse
Assist obeys that volume on my phone. If I set it to around 10%, it's very quiet indeed.
I feel like I'm the only person that can't get assist to actually work. Doesn't tell me who the message is from or say the actual message.
Sent from my XT1058 using xda app-developers app
Mine does not work at all either... no driving, meeting nor sleeping assist work. I tried to clear data and cache but no luck.
Sent from my Nexus 7 using xda app-developers app
terasia said:
Mine does not work at all either... no driving, meeting nor sleeping assist work. I tried to clear data and cache but no luck.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Okay, I did factory reset last night, and all Assist features are working now. Obviously, there was a problem before but I am happy now.
terasia said:
Okay, I did factory reset last night, and all Assist features are working now. Obviously, there was a problem before but I am happy now.
Click to expand...
Click to collapse
Yeah I've done a factory reset, cleared cache in recovery. Everything I can think of. The assist activates when driving, the alert starts, but as soon as it needs to do text to speech with the actual name and message it just stops.
I feel like there is a conflict somewhere but I tried it with a clean install and nothing downloaded. Now that i've got TIBU maybe I should do a clean reinstall of the factory software and re-root and test that. may not be a bad idea.
Mine was doing the opposite so i had to disable it...mine would work fine when driving but would de-activate...so when I got home/to work/wherever and assist 'stopped' it would continue reading out who the message was from and asking me if i wanted it read to me. Which is really annoying because like others, the volume seemed incredibly loud and turning it down didn't help.
Anyone else have this issue? I've had to disable assist because of this, don't want to be sitting in a meeting and get a text and have it start screaming at me.
tjohnstone3 said:
Mine was doing the opposite so i had to disable it...mine would work fine when driving but would de-activate...so when I got home/to work/wherever and assist 'stopped' it would continue reading out who the message was from and asking me if i wanted it read to me. Which is really annoying because like others, the volume seemed incredibly loud and turning it down didn't help.
Anyone else have this issue? I've had to disable assist because of this, don't want to be sitting in a meeting and get a text and have it start screaming at me.
Click to expand...
Click to collapse
I'm having the exact same problem. It ALWAYS announces them to me, whether it's in driving mode or not. Even when my phone is on vibrate... I tried turning the Assist feature completely off, and it still announced them to me, very frustrating
same
jrkeyboard said:
I'm having the exact same problem. It ALWAYS announces them to me, whether it's in driving mode or not. Even when my phone is on vibrate... I tried turning the Assist feature completely off, and it still announced them to me, very frustrating
Click to expand...
Click to collapse
I have this issue as well. I love that it does talk to me when I'm driving (when it should) but to do it for every text message no matter what is crazy. Device should know the difference between when I'm driving and when i'm at home....on my own wifi....with screen on....using my device. Even when actually using the messaging app having a conversation with someone is very annoying, just show it to me in the app don't take me out of the app and make me talk/swipe notification away to look at what I was already looking at. I tried several things to fix it until I gave up and installed a 3rd party sms app from play store. Even tweeted Motorola Mobility about issue and they only linked me to the Touchless Control FAQ, useless.
I guess I could try clearing Assist's data, I'm not willing to do a factory reset or anything over the issue though.
I am on pwnmymoto on vzw motox. had previous 2 releases of moto root as well. not sure if any of these root options may be to blame in the matter.
monkespit said:
I have this issue as well. I love that it does talk to me when I'm driving (when it should) but to do it for every text message no matter what is crazy. Device should know the difference between when I'm driving and when i'm at home....on my own wifi....with screen on....using my device. Even when actually using the messaging app having a conversation with someone is very annoying, just show it to me in the app don't take me out of the app and make me talk/swipe notification away to look at what I was already looking at. I tried several things to fix it until I gave up and installed a 3rd party sms app from play store. Even tweeted Motorola Mobility about issue and they only linked me to the Touchless Control FAQ, useless.
I guess I could try clearing Assist's data, I'm not willing to do a factory reset or anything over the issue though.
I am on pwnmymoto on vzw motox. had previous 2 releases of moto root as well. not sure if any of these root options may be to blame in the matter.
Click to expand...
Click to collapse
I contacted Motorola support, got transferred to level 2, and then level 3... they finally acknowledged that they found a bug they are working on and will hopefully issue an update for it soon. In the meantime, he showed me how to disable it. If you're interested, go into Settings > Apps > All... scroll down to "Motorola Assist Talk to Me", select it, and then click Disable. This will disable the spoken alerts totally until an update can be pushed out. Once the update is pushed out, you will need to go back in here and re-enable it.
Not the ideal solution, but at least we know an update will be coming to fix it
jrkeyboard said:
I contacted Motorola support, got transferred to level 2, and then level 3... they finally acknowledged that they found a bug they are working on and will hopefully issue an update for it soon. In the meantime, he showed me how to disable it. If you're interested, go into Settings > Apps > All... scroll down to "Motorola Assist Talk to Me", select it, and then click Disable. This will disable the spoken alerts totally until an update can be pushed out. Once the update is pushed out, you will need to go back in here and re-enable it.
Not the ideal solution, but at least we know an update will be coming to fix it
Click to expand...
Click to collapse
What's the common denominator here though? What do those who have this bug have in common? Verizon? Pwnmymoto? Excessive luck?
Sent from my XT1060 using Tapatalk 4
monkespit said:
What's the common denominator here though? What do those who have this bug have in common? Verizon? Pwnmymoto? Excessive luck?
Sent from my XT1060 using Tapatalk 4
Click to expand...
Click to collapse
Has nothing to do w/ Pwnmymoto. I was having this issue from day 1 and well before using Pwnmymoto. So it is either Verizon or just Motorola Assist in general.
The speaking of texts while driving was pretty much the main feature i liked w/ Moto Assist (along w/ silencing phone at night) so I'm just going to leave it disabled until an update is out to fix it.
tjohnstone3 said:
Has nothing to do w/ Pwnmymoto. I was having this issue from day 1 and well before using Pwnmymoto. So it is either Verizon or just Motorola Assist in general.
The speaking of texts while driving was pretty much the main feature i liked w/ Moto Assist (along w/ silencing phone at night) so I'm just going to leave it disabled until an update is out to fix it.
Click to expand...
Click to collapse
So it is just the Verizon ones?
Sent from my XT1060 using Tapatalk 4
monkespit said:
So it is just the Verizon ones?
Sent from my XT1060 using Tapatalk 4
Click to expand...
Click to collapse
No clue, haven't paid close enough attention to the people reporting the issue. I'm assuming it isn't specific to Verizon but as I said, nothing to back that up.
tjohnstone3 said:
No clue, haven't paid close enough attention to the people reporting the issue. I'm assuming it isn't specific to Verizon but as I said, nothing to back that up.
Click to expand...
Click to collapse
Was just curious since it seems like some don't have this issue.
I'm happier replacing the stock messaging app than killing all the spoken alerts since that's the only time it gets annoying. Hopefully they will get to it sooner than later since it's just an app update. Thanks for the info.
Sent from my XT1060 using Tapatalk 4
hi guys..
Got my new phone at the launching day.. everything runs perfect..
But yesterday and today i encounter a small issue..
please note that i have fingerprint scanner lock on my phone..
when i pressed the home button just to wake the screen, the screen didn't respond.. only the side buttons lid..
the screen remained black after the second press too.. then i pressed the power button once and the screen woke..
the thing was that when i pressed the power button after this incident the home screen game me a third option, apart from emergency calls (left) and alternative password (right), Unlock via Google placed to the middle..
this happened also today twice..
Any suggestions on this ?? did anyone encounter this ??
please note that i didn't use any other locking method except fingerprint scanner and the home button responds fine in any other case.. Thanx..
I randomly get unresponsive touches when trying to open an app in the app drawer folders. Haven't had the home button issue though
-Sent from Tapatalk
I'm having the exact same problem. Very disappointing for a new device. Not sure if I'm going to return it yet. I've tried factory reset and it didn't fix it.
Guy in the shop said he'll have to send it back to Samsung for testing.
I've gone back to using my old phone !!!!!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
BigAl1044 said:
I'm having the exact same problem. Very disappointing for a new device. Not sure if I'm going to return it yet. I've tried factory reset and it didn't fix it.
Guy in the shop said he'll have to send it back to Samsung for testing.
I've gone back to using my old phone !!!!!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
S-Voice is causing the problem on the home button lag, go trun off the open with home key in the svoice settings....
TheAxman said:
S-Voice is causing the problem on the home button lag, go trun off the open with home key in the svoice settings....
Click to expand...
Click to collapse
I turned it off when I first got the phone and still have it, although not as noticeable
-Sent from Tapatalk
eyecon82 said:
I turned it off when I first got the phone and still have it, although not as noticeable
-Sent from Tapatalk
Click to expand...
Click to collapse
same here I also switch this off and still same problem and format wipe data and cashe don't help
im having similar issues while on a call, i cant type in the extension, i touch the number pad and it does nothing. I turn off screen and now it doesnt want to turn back on. Like anything new, there will be a few hiccups, but samsung are usually fast for that first firmware push. I remember for the S4, i got it on launch day and the same day a new firmware was available, the note 3 took about 10 days before that initial firmware that fixed the few most obvious issues. Dont bring it back, just be patient.
polish_pat said:
im having similar issues while on a call, i cant type in the extension, i touch the number pad and it does nothing. I turn off screen and now it doesnt want to turn back on. Like anything new, there will be a few hiccups, but samsung are usually fast for that first firmware push. I remember for the S4, i got it on launch day and the same day a new firmware was available, the note 3 took about 10 days before that initial firmware that fixed the few most obvious issues. Dont bring it back, just be patient.
Click to expand...
Click to collapse
I've randomly noticed I can't click on an app to open it if it is in a folder I created in the app drawer
-Sent from Tapatalk
I heared some new firmwares have been pushed... Anybody got one?
Sent from my SM-G900W8 using Tapatalk
polish_pat said:
I heared some new firmwares have been pushed... Anybody got one?
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
It gets pushed out in waves, so it may be a few days to a few weeks till you get it. Kind of a bummer
-Sent from Tapatalk
TheAxman said:
S-Voice is causing the problem on the home button lag, go trun off the open with home key in the svoice settings....
Click to expand...
Click to collapse
Did that now and will test it through all day .. so far so good..
will let you know you guys..
hopefully it will get fixed.. if not we wait for an firmware update..
UPDATE
I used my phone all day using the settings above.. (no s-voice at home button and fingerprint lock) I encounter the problem 3-4 times.. other than that all is ok..
Now im going to use all day the pin to lock the screen and see what happens..
thanx
UPDATE
still the same issue with pin lock screen.. So probably an update will solve this..
thanx
z89x23 said:
Did that now and will test it through all day .. so far so good..
will let you know you guys..
hopefully it will get fixed.. if not we wait for an firmware update..
UPDATE
I used my phone all day using the settings above.. (no s-voice at home button and fingerprint lock) I encounter the problem 3-4 times.. other than that all is ok..
Now im going to use all day the pin to lock the screen and see what happens..
thanx
UPDATE
still the same issue with pin lock screen.. So probably an update will solve this..
thanx
Click to expand...
Click to collapse
Hey man,
Had the same issue with my S5, I think the wait for the fix is easier to handle if you know there are other guys having the same issue rather than having something wrong with your specific device. So imho it'd be great if some other guys would reply just to know it's a common issue.
To me SGS5 is a great phone even with all the rants and reviews against buying it, there will be updates, we just need to be patient.
Thanks for the post!
rciochin said:
Hey man,
Had the same issue with my S5, I think the wait for the fix is easier to handle if you know there are other guys having the same issue rather than having something wrong with your specific device. So imho it'd be great if some other guys would reply just to know it's a common issue.
To me SGS5 is a great phone even with all the rants and reviews against buying it, there will be updates, we just need to be patient.
Thanks for the post!
Click to expand...
Click to collapse
I can confirm that i have similar issues too.
Sometimes (2-3 a day) the screen is not waking up from sleep state when i press the home or the power button.
The solution is that i need to press the power button to sleep the device and then press again or press the home button to wake up.
Not a big deal but i hope that this issue is not hardware related and a firmware fix will solve it.
Apart from this, it's really a great smartphone.
Hi,
Just a small update, the issue replicates also when using the Samsung S View case, just bought one and I still get the same behaviour as with the home and power button (i.e. only the softkeys light up, the screen doesn't wake up).
I haven't been able to consistently replicate though, but it seems to happen after long sleep periods.
All the best!
rciochin said:
Hi,
Just a small update, the issue replicates also when using the Samsung S View case, just bought one and I still get the same behaviour as with the home and power button (i.e. only the softkeys light up, the screen doesn't wake up).
I haven't been able to consistently replicate though, but it seems to happen after long sleep periods.
All the best!
Click to expand...
Click to collapse
Hi !
One question.
Which ROM version do you have ?
The ...ANCE, or ANCF ?
thank you all for your replies.. its good to know that its not my device..
Hopefully with the new update they will fix it..
by the way yesterday i missed a call, do to that problem.. the phone was ringing but the screen was sleeping..
So i decided to chance my ROM, from EUR-Greece to NEE-Norther Countries.. Also did a hard factory reset after that.. Volume up + Power + Home.. Also deleted the cache partition..
I used odin.. No problems found.. and Kies recognizes the phone..
So i will check how this goes and get back to you..
Levus said:
Hi !
One question.
Which ROM version do you have ?
The ...ANCE, or ANCF ?
Click to expand...
Click to collapse
Hi
My build number is KOT49H.G900FXXU1ANCE
Levus said:
Hi !
One question.
Which ROM version do you have ?
The ...ANCE, or ANCF ?
Click to expand...
Click to collapse
Was using my original one which got an OTA update as soon i got it open..
SM-G900F EUR G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
Now as i posted above, i m using
SM-G900F NEE G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
I saw an ANCF
SM-G900F TTR G900FXXU1ANCF Android 4.4.2 31.03.2014 1186806
but i dont know the TTR which region is so i decided not to apply..
rciochin said:
Hi
My build number is KOT49H.G900FXXU1ANCE
Click to expand...
Click to collapse
i have the same.. on the NEE ROM
I dont think that was different on my EUR ROM..
z89x23 said:
Was using my original one which got an OTA update as soon i got it open..
SM-G900F EUR G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
Now as i posted above, i m using
SM-G900F NEE G900FXXU1ANCE Android 4.4.2 31.03.2014 1182732
I saw an ANCF
SM-G900F TTR G900FXXU1ANCF Android 4.4.2 31.03.2014 1186806
but i dont know the TTR which region is so i decided not to apply..
Click to expand...
Click to collapse
I have the XEH G900FXXU1ANCE...
I was just thinking that the G900FXXU1ANCF is maybe a little bit newer, as the build number is higher (1186806) So that's a different rom for sure.
Guys,
Today I got a real issue with new s5. When I try to slide the green answer button on screen, it doesn't respons.
I try 2 or 3 times after it works. It's really annoing problem. Anybody has same? Thanks...
zanbay said:
Guys,
Today I got a real issue with new s5. When I try to slide the green answer button on screen, it doesn't respons.
I try 2 or 3 times after it works. It's really annoing problem. Anybody has same? Thanks...
Click to expand...
Click to collapse
Hello,I have the same lag?
Anyone else have noticed this?
Yes, I've got the same problem. It took so long the other day that I missed the call completely.
Sent from my SM-G900R4 using Tapatalk
anyone have an solution?
First thing I would do is a hard reset - A pain I know, but doing so you can check whether it is potentially a Hardware issue with multitouch/touch etc.
Once you've done that, if it's still exhibiting the same behaviour check your screen behaviour on touch reactions on normal day-to-day use. There may actually be an app for it. (the Note 3 suffered some touch problems, not saying the S5 has them but have to check to be sure) .
If it is deemed a software glitch and a reset fixes it then you should be OK. - However if it's a touch screen bug I'd suggest returning/swapping it.
I'm more inclined to believe it's a software glitch, and a factory reset will indeed solve the problem.
Oke,thanks
Same issue! Did a factory reset but didn't help. Send it to local service center, they keep telling me there is no issue with the phone and that when it happens I should record a video as evidence of the problem. So much so Samsung warranty! Plus I have encountered ransom reboots when answering the phone.
Totally unhappy with S5. It is terrible. S4 and S3 were very stable.
vegerfrancois said:
Hello,I have the same lag?
Anyone else have noticed this?
Click to expand...
Click to collapse
i did noticed that too..
on mine if you put directly your finger in the circle and drag it works 1st try..
i still didnt have time to hard reset to be sure..
I noticed this too. I find that you have to hold your finger on the green answer and slide slowly. It's definitely a software problem that will hopefully be fixed in an update.
Factory reset makes no difference as done this for another problem I was having.
Sent from my SM-G900F using Tapatalk
Don't suppose anyone has found a solution to this yet? Or any alternatives to the stock dialer that might perform better?
I also get a lag between selecting a text field and the keyboard popping up which is very frustrating. Had expected more from a brand new phone
I had this problem at first as well, but after the latest update it fortunately disappeared, I did a full wipe as well.
Same problem here! Partially solved with enabling home button to accept calls....
Same here....its a pain in the ass ?
Sent from my SM-G900F using XDA Premium 4 mobile app
rathga said:
Don't suppose anyone has found a solution to this yet? Or any alternatives to the stock dialer that might perform better?
I also get a lag between selecting a text field and the keyboard popping up which is very frustrating. Had expected more from a brand new phone
Click to expand...
Click to collapse
I disabled the lockscreen animation and that helped making the device more snappy. Here are some more usefull tips http://phandroid.com/2014/04/25/samsung-galaxy-s5-first-14-things-to-do/.
I also have this lag when I'm trying to respond. It only woks on the 2nd attempt.
There's definitely a knack to answering a call, which can be quite annoying. Cannot understand why they didn't just leave it alone. Would rather answer my calls with a quick swipe to the right.
Sent from my SM-G900F using Tapatalk
What FW version are you all on? ANG2 seems to have solved it for me!
johan81 said:
What FW version are you all on? ANG2 seems to have solved it for me!
Click to expand...
Click to collapse
I hadn't even noticed it was fixed since I got the new update. Just tested and problem is solved
Sent from my SM-G900F using Tapatalk
Until a firmware update, enable answer with home button.
Sent from my Galaxy S5 using Tapatalk.
Note 4 SM-910C
I'm getting the "unable to use fingerprints. device restarted. enter backup password, then fingerprints can be used next time device locked." ,message continually after restart.
The strange thing is that even resetting my registered fingers and using other apps like lastpass successfully it doesn't fix the issue, anybody else experiencing this issue found a way to fix it?
optical10 said:
Note 4 SM-910C
I'm getting the "unable to use fingerprints. device restarted. enter backup password, then fingerprints can be used next time device locked." ,message continually after restart.
The strange thing is that even resetting my registered fingers and using other apps like lastpass successfully it doesn't fix the issue, anybody else experiencing this issue found a way to fix it?
Click to expand...
Click to collapse
This is expected behaviour. It's designed to require your backup password at each boot, then you can use your fingerprints like normal
I am facing the same problem too.
Is there any solution?
Thank you
use backup password get in, turn finger print off. reboot and get back into your device then turn it back on.
A|ex said:
use backup password get in, turn finger print off. reboot and get back into your device then turn it back on.
Click to expand...
Click to collapse
Way too much work, guys - just deal with it.
Sent from my SM-N910C using XDA-Developers mobile app
c00k1eBSc said:
This is expected behaviour. It's designed to require your backup password at each boot, then you can use your fingerprints like normal
Click to expand...
Click to collapse
It didnt work like this before so im looking for proof that google have changed it for the worse, any links?
optical10 said:
It didnt work like this before so im looking for proof that google have changed it for the worse, any links?
Click to expand...
Click to collapse
As far as I know it is a choice made by Samsung and not Google but I can't be sure since I'm destined to not get MM until 2017 (or at least it feels like it at this point)
c00k1eBSc said:
As far as I know it is a choice made by Samsung and not Google but I can't be sure since I'm destined to not get MM until 2017 (or at least it feels like it at this point)
Click to expand...
Click to collapse
Its the same on CM13.
NickVXD said:
Its the same on CM13.
Click to expand...
Click to collapse
Thanks for informing me of that. I wasn't sure but now I can't get mad at Samsung for that
hi to all how any one that has the same setup will help me understand i will try and keep it short first im using samsung note 4 running 6.0.1 now
ok so here goes i use my gear 2 together with my note 4 as a trusted device you know like every time the gear 2 is close the device must stay unlocked but it does not stay unlocked and there is no Bluetooth disconnecting anything like this i look at that so battery is full the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage but i connect it now and its fine but after a wile (don't know the exact time here ) but say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on and there was nothing like it disconnecting it is as if the phone on its own make sure that it asks the finger print every now and again say like i leave it overnight the next morning first fingerprint then you can use the phone i hate this it kind of bugs me if the steal the phone and the range is to big the device will lock any way why lock when the gear 2 it near the phone any help please
honestly, i stopped reading after few seconds.
have you ever heard about punctuation? - you know, the thing that looks like dots and commas, makes reading much easier.
244 characters in 1 sentence.
wow dude, looks like you dont wanna get helped.
biebie29 said:
...say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on...
Click to expand...
Click to collapse
From the Google Smart Lock support page (https://support.google.com/nexus/answer/6093922):
"Note: When you don't use your phone for 4 hours, and after you reboot your phone, you'll need to manually unlock it with your PIN, pattern or password"
It's a security feature.
EDIT: ...and, wow, yes, that was some run-on sentence!
Is there a root app to disable it or not
biebie29 said:
Hi to all. How any one that has the same setup will help me understand. I will try and keep it short. First, i'm using samsung note 4 running 6.0.1 now.
Ok, so here goes:
I use my gear 2 together with my note 4 as a trusted device. You know like every time the gear 2 is close, the device must stay unlocked. But it does not stay unlocked and there is no Bluetooth disconnecting, anything like this. I looked at that. Battery is full, the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage.
I connect it now and its fine, but after a while (don't know the exact time here ), say after 3 hours of no use, i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near. The gear 2 is still on and there was nothing like disconnecting. As if the phone on its own make sure that it asks the finger print every now and again.
For example, i leave it overnight the next morning first fingerprint then you can use the phone.I hate this. It kind of bugs me if they steal the phone and the range is to big, the device will lock any way. Why lock when he gear 2 it near the phone? Any help please.
Click to expand...
Click to collapse
Fixed that for you
I really had to break that down to make it readable for me. But as others said, it's an Android feature. Afaik there is no way of disabling that all together. There might be some xposed module i haven't heard of, but with my moto360 i couldn't get it to work the way you'd want. Sorry mate
Kinsman-UK said:
It's a security feature
Click to expand...
Click to collapse
As the programmers use to says: Its a feature, not a bug
Some people are just plain jerks, and I wish XDA would take these "grammar police" trolls a bit more seriously and penalize them.
Perhaps OP is using a translator, or is from another country, or is young. That should not matter to any of us and we should offer our help regardless of whether he/she includes proper punctuation or not. I'm sure the effort he/she put into typing it was much greater than that of the ridiculous responses some of you gave.
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
biebie29 said:
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
Click to expand...
Click to collapse
The Note 4 is problematic all around, but 6.0.1 is a problem for every device that has it. It is the reason I left my Nexus 6P, and my Nexus 6. I have a Xiaomi Mi Max, also on 6.0.1 and it has the same major flaws I experienced on all devices running 6.0.1. The problems I speak of are the WiFi and Data stop working briefly while browsing the web, or downloading something. However, I believe this is an issue related to the security patches related to Qualcomm devices on 6.0.1. It seems like an overall radio problem.