Like the title says. When the phone is screen off but plugged in, OK Google isn't recognized. Works fine if screen is on. In my Google / Voice settings I have turned on Say Ok Google Anytime and Trusted Voice to unlock.
It worked fine on my LG G3 previously before I came to the 3T.
Any ideas?
Sent from my ONEPLUS A3000 using Tapatalk
For me also not works
This is proving to be very annoying.
I tried the Now Launcher to see if it would fix this problem (I was going to use it anyway since autorotate seems broken with stock Launcher).
Now launcher doesn't change the situation. Does anybody have a work-around? This is the first phone/os that I have had this problem with.
Help!
Sent from my ONEPLUS A3000 using Tapatalk
When i tried, it says there is locked screen (i have fingerprinted lock screen), but when i recognized and accepted, it had no reaction. Do you tried only swiped lock screen?
Tried a bunch of things. When screen is off (but charging)I haven't found any combination of settings that work. I use a fingerprint but noticed problem before setting up the fingerprint. Also have set that my voice can be trusted to unlock; also in my car the phone is unlocked as a trusted Bluetooth device.
Sent from my ONEPLUS A3000 using Tapatalk
For me sometimes it has vibration, sometimes it says that phone are locked. But still not works "ok google" on black screen
I guess what does it means. When you press unlcok button, if there is swipe or something, it unlocks device when you say "ok google"
I have the same problem..ok Google does not work when the screen is off..bt works fine when the screen is on
I've asked this question over in the OnePlus community forum on OnePlus.net. I don't think the readership there is as savvy as here though. I've already gotten some patently wrong answers. I'm still hoping someone can suggest a fix or at least work-around.
Sent from my ONEPLUS A3000 using Tapatalk
gioyocho said:
I guess what does it means. When you press unlcok button, if there is swipe or something, it unlocks device when you say "ok google"
Click to expand...
Click to collapse
I have that option checked and it still stops working for me if I haven't used my device for more than 5 minutes.
Sent from my ONEPLUS A3000 using Tapatalk
I also would like to use OK Google with the screen off.
This has been driving me a bit crazy. I can't imagine what is blocking it from working. Glad to hear it isn't just me experiencing it... At least I am not alone.
I can't imagine it is a technology gap on the phone... That would only apply to screen off / not charging cases. Microphone certainly can work with screen off... For example talking on phone the screen shuts off in proximity to the head. And it's not a power issue, since this use case includes charging.
Somewhere there must be a hidden toggle for some feature set the wrong way.
Anybody have skills to investigate?
Sent from my ONEPLUS A3000 using Tapatalk
you can't.
always listening isn't enabled on our phone (something about licensing with qualcomm).
I don't need always listening... I need listening while charging. Even phones from 5 years ago do this...
Sent from my ONEPLUS A3000 using Tapatalk
again, you can't. IT IS NOT ENABLED ON OUR PHONE.
Yes, my nexus from years ago can do it.
but no, our 3T will NOT do it.
exb0 said:
again, you can't. IT IS NOT ENABLED ON OUR PHONE.
Yes, my nexus from years ago can do it.
but no, our 3T will NOT do it.
Click to expand...
Click to collapse
This kind of makes hands-free driving and home voice actions pointless.
exb0 said:
again, you can't. IT IS NOT ENABLED ON OUR PHONE.
Yes, my nexus from years ago can do it.
but no, our 3T will NOT do it.
Click to expand...
Click to collapse
Thanks for the reply. What exactly isn't enabled... or better asked, at what level is it not enabled? The SnapDragon 821 has support for it. So, perhaps this will come in an update or a custom ROM. Or is there some other layer which needs to be developed that OP currently hasn't?
It's beyond shocking that a major feature ... voice response while driving ... would be crippled in a recent model phone. And, I am ignorant of what exactly needs to work. The microphone works fine when the screen is off, and I have no concerns about battery performance when plugged in and charging, so an app should be able to be told to listen to the microphone under these circumstances.
Any further info about what's missing would be greatly appreciated!
It worked for a short time for me. I could say, "ok google" with the screen off, but I'm guessing the app updated or a rom changed one little thing and now it's a pain in the ass.
Sent from my ONEPLUS 3T using Tapatalk
cbwhat said:
This kind of makes hands-free driving and home voice actions pointless.
Click to expand...
Click to collapse
Uhh, yeah. That's why you keep the screen on.
Frankenscript said:
Thanks for the reply. What exactly isn't enabled... or better asked, at what level is it not enabled? The SnapDragon 821 has support for it. So, perhaps this will come in an update or a custom ROM. Or is there some other layer which needs to be developed that OP currently hasn't?
It's beyond shocking that a major feature ... voice response while driving ... would be crippled in a recent model phone. And, I am ignorant of what exactly needs to work. The microphone works fine when the screen is off, and I have no concerns about battery performance when plugged in and charging, so an app should be able to be told to listen to the microphone under these circumstances.
Any further info about what's missing would be greatly appreciated!
Click to expand...
Click to collapse
Yes, the 821 has support for always listening. However, the phone company (OnePlus) has to pay the SOC company (qualcomm) in order to use always listening (more on always listening later). Is it possible for a developer to somehow enable it? Yes. As seen with the Ok Snapdragon concept with the nexus 4, we can indeed enable it. However due to legal issues, that mod was never released.
Another reason is marketing. Motorola was able to promote their Moto X Pure so much because it had their custom "Ok Google" thingiemajig. If every phone had always listening, why buy a nexus / pixel / moto?
If you want the phone to listen and respond to your voice actions while the screen is off, regardless of whether or not it's plugged in, you need always listening. Unless you're in a call, of course.
I've heard that PA and/or CM managed to make a hackaround this for other OP phones, but I cannot confirm that it actually exists as I have never looked into it.
Great explanation. Thank you
Sent from my ONEPLUS A3000 using Tapatalk
Related
I have Moto360 and it's supposed to keep the phone unlocked. Well, once in a while (at least once per day) it doesn't work so I decided to add a Trusted Location (my house). This made it worse because there seems to be some sort of "race condition" and I get a lot more issues at work now. Basically it seems like it's seeing that I'm not home and skips the check of Moto360 presence all-together. I also added an NFC tag (for my car in case I forget Moto360 at home). So having these 3 settings enabled at once makes this a worse experience than just with Moto360 (which isn't reliable to begin with)
Anyway, this unlocking mechanism is one big mess and hasn't been reliable for me. I understand that it's better to be safe than sorry but these are clear bugs.
Anyone else experiencing this?
T-R said:
I have Moto360 and it's supposed to keep the phone unlocked. Well, once in a while (at least once per day) it doesn't work so I decided to add a Trusted Location (my house). This made it worse because there seems to be some sort of "race condition" and I get a lot more issues at work now. Basically it seems like it's seeing that I'm not home and skips the check of Moto360 presence all-together. I also added an NFC tag (for my car in case I forget Moto360 at home). So having these 3 settings enabled at once makes this a worse experience than just with Moto360 (which isn't reliable to begin with)
Anyway, this unlocking mechanism is one big mess and hasn't been reliable for me. I understand that it's better to be safe than sorry but these are clear bugs.
Anyone else experiencing this?
Click to expand...
Click to collapse
That's strange. I have the same setup except my car's BT is a trusted pair also.
No issues here.
Dusty Rhodes said:
That's strange. I have the same setup except my car's BT is a trusted pair also.
No issues here.
Click to expand...
Click to collapse
Is the BT in ur car capable to read your text msg? My note 4 use do it perfect but nexus is not option is grayed out on my car screen.
My home and work are "trusted places" and it works about 50% of the time. At work it barely works...My Nexus 5 was the same way. It is probably a thing on Google's end that they need to update.
T-R said:
I have Moto360 and it's supposed to keep the phone unlocked. Well, once in a while (at least once per day) it doesn't work so I decided to add a Trusted Location (my house). This made it worse because there seems to be some sort of "race condition" and I get a lot more issues at work now. Basically it seems like it's seeing that I'm not home and skips the check of Moto360 presence all-together. I also added an NFC tag (for my car in case I forget Moto360 at home). So having these 3 settings enabled at once makes this a worse experience than just with Moto360 (which isn't reliable to begin with)
Anyway, this unlocking mechanism is one big mess and hasn't been reliable for me. I understand that it's better to be safe than sorry but these are clear bugs.
Anyone else experiencing this?
Click to expand...
Click to collapse
i'm not experiencing this at all. i've had it working with my N5 flawlessly (before i got my N6) as well. if your phone isn't showing that you're at home, your location services might be turned off though.
worst case is that you back up your settings and try a clean wipe/reflash and see if it's working as expected.
*EDIT* are you sure that you're not accidentally hitting the little lock/unlock icon at the bottom of the screen? that will lock it regardless of the trusted devices/location settings.
NICEGYPT said:
Is the BT in ur car capable to read your text msg? My note 4 use do it perfect but nexus is not option is grayed out on my car screen.
Click to expand...
Click to collapse
Mine could work but I use hangouts as my messaging app and THAT doesn't work.
So that you know what I'm working with, I have a 2012 Mustang GT with MyFordTouch.
Dusty Rhodes said:
Mine could work but I use hangouts as my messaging app and THAT doesn't work.
So that you know what I'm working with, I have a 2012 Mustang GT with MyFordTouch.
Click to expand...
Click to collapse
I have a 2014 Charger with Uconnect
Lucke said:
*EDIT* are you sure that you're not accidentally hitting the little lock/unlock icon at the bottom of the screen? that will lock it regardless of the trusted devices/location settings.
Click to expand...
Click to collapse
Wow, that could be it! I didn't even realize this icon is there and I often unlock from the very bottom (old habits). I will pay attention from now on and hopefully this is exactly what it was.
Thank you!
T-R said:
Wow, that could be it! I didn't even realize this icon is there and I often unlock from the very bottom (old habits). I will pay attention from now on and hopefully this is exactly what it was.
Thank you!
Click to expand...
Click to collapse
Haha I had the same problem til I realized this
For the life of me I cannot use my N6 no-handed, even for just a moment. The 5-10 seconds I need to hold my phone up between my shoulder and my face to free both hands.......it never fails that I cause an issue with a live phone call. Obviously the larger screen (larger touch-sensitive area) and the screen being on for some reason during the call.......I always either put the phone call on hold, or even put the current call on hold and manage to dial one of my starred contacts. It is driving me up the damn wall. I am not a huge fan of the L phone interface (the starred favorites especially), I much prefer the KK layout.
Anyone else having as hard of a time as me? I'm wondering if the screen being off during the call would cure this. I guess I could manually cut it off when going to no-hands.......but figured it should do it on its own. Anyone care to either give me some suggestions, or even punch me for my ignorance and tell me what I am doing wrong?
Love everything about the phone, and also loving LiquidSmooth.......just hoping the development gets into high gear soon.
The screen is suppose to be off during calls, that's what the proximity sensor is for. Are you sure you are not hitting the power button while in call, i find it to be sensitive??If its not turning itself off when you put it up to your face, flash back to full stock. Still not working, then its probably a hardware issue???
Sent from my Nexus 6 using XDA Free mobile app
holeindalip said:
The screen is suppose to be off during calls, that's what the proximity sensor is for. Are you sure you are not hitting the power button while in call, i find it to be sensitive??If its not turning itself off when you put it up to your face, flash back to full stock. Still not working, then its probably a hardware issue???
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I forgot to reply I had this issue while stock as well. I wasn't looking to 'fix' this issue with a different ROM either, I just like the capabilities and development done in the ROM's themselves. Can't say I didn't hope something would change though.....
I only experience this with my left hand, LOL. Right handed, no issues with the screen turning off.
wilson289 said:
I only experience this with my left hand, LOL. Right handed, no issues with the screen turning off.
Click to expand...
Click to collapse
Well that is certainly odd lol.....
Anyone else? Surely I'm not the only one....... :silly:
Hi all,
I've just received my Nokia 8 yesterday and I'm impressed so far however one thing is really bugging me.
Does anybody know how to turn off the haptic feedback on the fingerprint scanner when I am waking my device. I can't find the setting anywhere
There's no such one.
Ok fair enough. Thanks
Sent from my TA-1012 using XDA-Developers Legacy app
It is, however, one way to turn off the fingerprint scanner vibration; set the phone in battery saving mode and it doesnt vibrate on scan anymore.
Not ideal, I know.
You can stop the vibrations.
Go to Settings -> Sound -> Advanced -> under the heading "Other sounds and vibrations" go to "Vibrate on tap" and turn that off. This will stop the haptic feedback on the 3 buttons at the bottom of the phone.
Also, to stop the haptic feedback if you set your security to enter a pin number for your SIM card, go to Settings -> System -> Languages & input -> Virtual Keyboard -> Gboard -> Preferences -> and turn Vibrate on keypress off. I personally use the Swype keyboard as my main input method but because the SIM security interface pops up before that keyboard is loaded when you boot, you have to change it in the Gboard settings to see the effect.
Hope it helps
sirthommo said:
You can stop the vibrations.
Go to Settings -> Sound -> Advanced -> under the heading "Other sounds and vibrations" go to "Vibrate on tap" and turn that off. This will stop the haptic feedback on the 3 buttons at the bottom of the phone.
Click to expand...
Click to collapse
I have always had vibrate on tap turned off and the finger print scanner still vibrates when you use it.
I think it's normal, it must somehow notify if the scan went correctly or not. With the screen off, haptic feedback is the only discreet solution. Even my Nexus 5X behaved the same way and did not allow its disabling
I believe their could be away to stop the vibration if we knew the App that it is responsible for fingerprint vibration and turn vibration off in settings of this app.
for example the Nokia 8 vibrate after missed calls, and we can stop that from App notification in settings, so I'm looking to solve this issue the same way.
so any one know which app is responsible for fingerprint reader feed back & vibration ??
bobsie41 said:
Hi all,
I've just received my Nokia 8 yesterday and I'm impressed so far however one thing is really bugging me.
Does anybody know how to turn off the haptic feedback on the fingerprint scanner when I am waking my device. I can't find the setting anywhere
Click to expand...
Click to collapse
It also bother me and i contacted nokia. They said it cannot be disabled
Is this a Nokia issue or it's Oreo related?
EmpiresEmpires said:
Is this a Nokia issue or it's Oreo related?
Click to expand...
Click to collapse
It works like this always, also on Pixel and Nexus. It's a normal behavior, a way to make the user understand in a discreet way that the scan was successful or not.
I don't understand why you are asking this question as if it were a bug or a lack.
Sent from my Nokia 8 using XDA Labs
cri347 said:
It works like this always, also on Pixel and Nexus. It's a normal behavior, a way to make the user understand in a discreet way that the scan was successful or not.
I don't understand why you are asking this question as if it were a bug or a lack.
Sent from my Nokia 8 using XDA Labs
Click to expand...
Click to collapse
Actually it is a bug, I unlock my smartphone like more than 50 times a day and maybe more, I don't need to get notified by vibration every time I unlock my smartphone.
this is an Android misbehavior.
one-option said:
Actually it is a bug, I unlock my smartphone like more than 50 times a day and maybe more, I don't need to get notified by vibration every time I unlock my smartphone.
this is an Android misbehavior.
Click to expand...
Click to collapse
It isn't a bug, it's the normal behavior. It works like this on any smartphone in the world, have you noticed only now and on this specific device?
It's not a notification, it's an haptic feedback: one impulse, finger recognized; two impulse, finger not recognized; nothing, something wrong, doesn't work.
The problem that you put is like saying that I block the device several times a day and don't want the excursion and the click of the physical button, IMHO.
If anything, the problem to be asked would be to make the feedback more discrete by modulating the vibration differently.
Without that feedback, how would you realize if there was an error in the scan or does the reader not work? (considers that the unlock works with screen off and it would be a waste of battery to turn it on only to notify the wrong scan).
In the end it seems to me a philosophical question and in any case should not be placed for this specific device, but for everyone, since it works so everywhere.
No, it's a android feature, not a bug. If it wouldn't work, then it would define as a bug and would be fixed.
But seriously, it would be a minor battery saving trick to be able to disable it. It's the reason why I disabled haptic feedback on typing several years ago, as it effected battery life tremendously.
Just to add to the existing consensus, it is definitely working as intended.
Or perhaps more accurately (seeing as I can't read the minds of Nokia's development team) it is working exactly the same as it does on any of the other android phones with fingerprint readers I have used recently.
Personally I find it useful as it provides feedback on if my fingerprint has been read and if it has been successful.
Because I often unlock my phone as I'm removing it from my pocket or as I'm picking it up so that it is unlocked by the time it's in front of my eyes the physical feedback is definitely appreciated.
cri347 said:
It works like this always, also on Pixel and Nexus. It's a normal behavior, a way to make the user understand in a discreet way that the scan was successful or not.
I don't understand why you are asking this question as if it were a bug or a lack.
Sent from my Nokia 8 using XDA Labs
Click to expand...
Click to collapse
Hello,
I don't know. But my previous Huawei P8 lite (2017) had the option to turn it off.
That's why I'm surprised because the (better) Nokia 8 doesn't have this ability.
It's just to avoid much battery loss that it would be nice to have that option (I have to unlock many times per day..)
one-option said:
Actually it is a bug, I unlock my smartphone like more than 50 times a day and maybe more, I don't need to get notified by vibration every time I unlock my smartphone.
this is an Android misbehavior.
Click to expand...
Click to collapse
If you want to switch off the vibration then put your phone on battery saving mode and see the magic. Have you seen? Have you seen? Have you seen?
Hello all,
I have the Note 8 from last year and the new Note 9 that came with the new Bixby 2.0 this year. I like how sleek and refined looking the new Bixby is this year, but it's seriously dumber than the older Bixby that's on my Note 8!
Some of the common commands I give that works on my Note 8:
Turn on/off Fast Charging
Turn on/off Fast Wireless Charging
Save my location as my home
Check for app updates in the Play Store
When I ask the note 9 to turn on/off Fast Charging, it instead goes to optimize my Battery. When I ask it to turn off my fast wireless charging, it turns off Wifi instead! It couldn't even understand anything about checking for updates in the Play Store, whereas the Note 8 could do it very well (sort of currently).
What gives Samsung? Technology and AI is supposed to be smarter, but this time it's pretty stupid to not understanding basic system commands.
Still trying to figure out which is dumber... Using bixby or posting about how dumb bixby button is. ???.
Ok, Google. Whup bixby's ass.
@rbiter said:
Still trying to figure out which is dumber... Using bixby or posting about how dumb bixby button is. ?.
Ok, Google. Whup bixby's ass.
Click to expand...
Click to collapse
Bixby has its merits. I still use Google 95% of the time due to its smooth performance searching things as well as having 110% accuracy in understanding over Bixby. It's just for some of the specific functions of the phone itself that I want to see how Bixby does that made the Note 8 pretty well.
I really don't have a problem with the Bixby button since I rarely make the same mistake as the general population does with it. This post is really about the Bixby AI itself and how it became less functional than the older version.
Samsung is trying to force it on us. They know it will get better much slower, if at all, if people don't use it. Just look at Siri. Look how fast Alexa made a come up because... Well you gotta give up something to make progress orove forward.
Who would have thought 10 years ago people are paying a premium for the government to spy on them, Siri included. I could see using smart home stuff/IOT if setup properly to maximize the benefits. But most people do not and have not given thought to the many ways. (like very granular A/C and building a proper roof that doesn't trap heat or utilizing that heat to positive energy)
If Google gave up advertising I would use Google assistant more. Heck, I'd probably give in and pay something on a subscription for no ads all the way across my Google apps and Android. Not going to happen if people keep buying that dedicated stuff and putting up with ads and spying. Until then I wear an invisible tin foil hat.
guys dont bash Bixby. if they phase it out, we loose the button.
GigaSPX said:
Hello all,
I have the Note 8 from last year and the new Note 9 that came with the new Bixby 2.0 this year. I like how sleek and refined looking the new Bixby is this year, but it's seriously dumber than the older Bixby that's on my Note 8!
Some of the common commands I give that works on my Note 8:
Turn on/off Fast Charging
Save my location as my home
Check for app updates in the Play Store
When I ask the note 9 to turn on/off Fast Charging, it instead goes to optimize my Battery. When I ask it to turn off my fast wireless charging, it turns off Wifi instead! It couldn't even understand anything about checking for updates in the Play Store, whereas the Note 8 could do it very well (sort of currently).
What gives Samsung? Technology and AI is supposed to be smarter, but this time it's pretty stupid to not understanding basic system commands.
Click to expand...
Click to collapse
I've still not set up Bixby. The main problem is it's inability to recognize your voice.
RaymondPJR said:
I've still not set up Bixby. The main problem is it's inability to recognize your voice.
Click to expand...
Click to collapse
I trained box y on the note 9 to recognise my voice. I also have a note 8 in the same room. When saying hi bixby the note 8 responds but the note 9 doesn't. I think bixby 2.0 is still in its infancy whereas bixby 1.0 on the note 8 is refined. Pity we have to use bixby 2.0 on the note 9.
Sent from my SM-N960F using XDA-Developers Legacy app
I agree, I was so hoping it would be Bixby 1 but with improvements to speech recognition and a refinement. Instead, it's like a completely different, stripped out version
xMadMike said:
I agree, I was so hoping it would be Bixby 1 but with improvements to speech recognition and a refinement. Instead, it's like a completely different, stripped out version
Click to expand...
Click to collapse
GigaSPX said:
Hello all,
I have the Note 8 from last year and the new Note 9 that came with the new Bixby 2.0 this year. I like how sleek and refined looking the new Bixby is this year, but it's seriously dumber than the older Bixby that's on my Note 8!
Some of the common commands I give that works on my Note 8:
Turn on/off Fast Charging
Turn on/off Fast Wireless Charging
Save my location as my home
Check for app updates in the Play Store
When I ask the note 9 to turn on/off Fast Charging, it instead goes to optimize my Battery. When I ask it to turn off my fast wireless charging, it turns off Wifi instead! It couldn't even understand anything about checking for updates in the Play Store, whereas the Note 8 could do it very well (sort of currently).
What gives Samsung? Technology and AI is supposed to be smarter, but this time it's pretty stupid to not understanding basic system commands.
Click to expand...
Click to collapse
Hello
I just bought a note 9, and the main reason I buy notes is s-pen and bixby. Now on note 9, none of my quick commands work, I cannot get bixby voice to recognize my voice, other than 'Hi Bixby'. What use the update, if it completely disables the app? The app is all the time trying to communicate to the network, cannot connect to the network and so cannot carry out any commands.
I am seriously thinking of returning the note 9 (I got it from samsung.com), and will keep my note 8.
thanks
thanks
tahrang said:
Hello
I just bought a note 9, and the main reason I buy notes is s-pen and bixby. Now on note 9, none of my quick commands work, I cannot get bixby voice to recognize my voice, other than 'Hi Bixby'. What use the update, if it completely disables the app? The app is all the time trying to communicate to the network, cannot connect to the network and so cannot carry out any commands.
I am seriously thinking of returning the note 9 (I got it from samsung.com), and will keep my note 8.
thanks
thanks
Click to expand...
Click to collapse
Bixby is terrible, like the general public agrees on, but the phone itself is not. I have both the Note 8 and Note 9, and the Note 9 is a wonderful upgrade from the Note 8. Bigger battery, better camera, and a nicer "whiter" screen.
I mainly use Google Assistant anyways, and it's a much better assistant AI anyway. On both Bixbys, it doesn't really recognize the names I tell it to call unlike Google having utmost accuracy.
tahrang said:
Hello
I just bought a note 9, and the main reason I buy notes is s-pen and bixby. Now on note 9, none of my quick commands work, I cannot get bixby voice to recognize my voice, other than 'Hi Bixby'. What use the update, if it completely disables the app? The app is all the time trying to communicate to the network, cannot connect to the network and so cannot carry out any commands.
I am seriously thinking of returning the note 9 (I got it from samsung.com), and will keep my note 8.
thanks
thanks
Click to expand...
Click to collapse
Returning a Note9 in favor of the Note8 due to Bixby being bad... When Google Assistant is readily available... Whoa. Brain cannot compute this...
PsiPhiDan said:
Returning a Note9 in favor of the Note8 due to Bixby being bad... When Google Assistant is readily available... Whoa. Brain cannot compute this...
Click to expand...
Click to collapse
You think that's funny? Go read some of the reasons for returning and never "ever" buying Samsung again from the official Samsung forums . [emoji1787]
Sent from my SM-N960U1 using Tapatalk
Limeybastard said:
You think that's funny? Go read some of the reasons for returning and never "ever" buying Samsung again from the official Samsung forums . [emoji1787]
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
I concur. Returning this phone because Bixby sucks has to be the silliest reason I've ever heard, considering that Google Assistant is available and is light years ahead of Bixby. I haven't even set Bixby up on my phone and I don't see why I would ever want to.
And perhaps there are reasons to return this phone, but people hyperventilating on the official forums (or anywhere on the internet) have to be taken with a huge grain of salt.
sputnik767 said:
I concur. Returning this phone because Bixby sucks has to be the silliest reason I've ever heard, considering that Google Assistant is available and is light years ahead of Bixby. I haven't even set Bixby up on my phone and I don't see why I would ever want to.
And perhaps there are reasons to return this phone, but people hyperventilating on the official forums (or anywhere on the internet) have to be taken with a huge grain of salt.
Click to expand...
Click to collapse
PsiPhiDan said:
Returning a Note9 in favor of the Note8 due to Bixby being bad... When Google Assistant is readily available... Whoa. Brain cannot compute this...
Click to expand...
Click to collapse
I am really sorry, you feel that I am hyperventilating. I was agreeing to the original post.
Secondly, whatever your reasons for not using Bixby or preferring one AI to another, that is not enough reason to make fun of others.
Thank you both for your very kind words.
Limeybastard said:
You think that's funny? Go read some of the reasons for returning and never "ever" buying Samsung again from the official Samsung forums . [emoji1787]
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
tahrang said:
I am really sorry, you feel that I am hyperventilating. I was agreeing to the original post.
Secondly, whatever your reasons for not using Bixby or preferring one AI to another, that is not enough reason to make fun of others.
Thank you both for your very kind words.
Click to expand...
Click to collapse
Regarding the hyperventilating comment, I wasn't talking about you, but rather the people who are hyperventilating on the official forums. That was in reference to your comment regarding people "never buying a Samsung again."
As to your second comment, nobody was making fun of you, certainly not me. If you feel slighted, please point out where in my post you found offense. Life becomes very difficult when one is overly sensitive. Did I think your overall complaint was ridiculous? Absolutely. Nobody, and I really do mean nobody buys this phone because of Bixby. It offers no additional functionality over the built in Google assistant, and most people don't even set it up. I haven't seen a single review of this device that even mentioned Bixby and useful in the same paragraph. It is just like the old SVoice that Samsung forced on all of us on their older phones, and nobody ever used it. But by all means, feel free to never buy another Samsung device again. Just don't expect Bixby on anything else other than Samsung. With an apple phone you'll get siri and Google assistant, with Samsung you get Bixby and Google assistant, and every other phone comes with just Google assistant.
Look, I get it. Nobody showed you Google assistant, you set up Bixby and were used to using it. Do yourself a favor, set up Google assistant, turn on the "OK Google" voice command, and whenever you need something, say "OK Google" and tell it what you want. Works when the phone is locked, works when you're driving, works completely hands free, just works. And then metaphorically toss Bixby into the garbage where it belongs.
sputnik767 said:
I concur. Returning this phone because Bixby sucks has to be the silliest reason I've ever heard, considering that Google Assistant is available and is light years ahead of Bixby. I haven't even set Bixby up on my phone and I don't see why I would ever want to.
And perhaps there are reasons to return this phone, but people hyperventilating on the official forums (or anywhere on the internet) have to be taken with a huge grain of salt.
Click to expand...
Click to collapse
PsiPhiDan said:
Returning a Note9 in favor of the Note8 due to Bixby being bad... When Google Assistant is readily available... Whoa. Brain cannot compute this...
Click to expand...
Click to collapse
sputnik767 said:
Regarding the hyperventilating comment, I wasn't talking about you, but rather the people who are hyperventilating on the official forums. That was in reference to your comment regarding people "never buying a Samsung again."
As to your second comment, nobody was making fun of you, certainly not me. If you feel slighted, please point out where in my post you found offense. Life becomes very difficult when one is overly sensitive. Did I think your overall complaint was ridiculous? Absolutely. Nobody, and I really do mean nobody buys this phone because of Bixby. It offers no additional functionality over the built in Google assistant, and most people don't even set it up. I haven't seen a single review of this device that even mentioned Bixby and useful in the same paragraph. It is just like the old SVoice that Samsung forced on all of us on their older phones, and nobody ever used it. But by all means, feel free to never buy another Samsung device again. Just don't expect Bixby on anything else other than Samsung. With an apple phone you'll get siri and Google assistant, with Samsung you get Bixby and Google assistant, and every other phone comes with just Google assistant.
Look, I get it. Nobody showed you Google assistant, you set up Bixby and were used to using it. Do yourself a favor, set up Google assistant, turn on the "OK Google" voice command, and whenever you need something, say "OK Google" and tell it what you want. Works when the phone is locked, works when you're driving, works completely hands free, just works. And then metaphorically toss Bixby into the garbage where it belongs.
Click to expand...
Click to collapse
I never commented on the "never buying samsung again" post.
As for bixby, I use it for device maintenance commands mostly. And I have setup google assistant, and use that for most internet related queries etc. So I use both on Note phones, but on my tablets, I use google assistant.
tahrang said:
I never commented on the "never buying samsung again" post.
As for bixby, I use it for device maintenance commands mostly. And I have setup google assistant, and use that for most internet related queries etc. So I use both on Note phones, but on my tablets, I use google assistant.
Click to expand...
Click to collapse
Wait, so you took offense to a reply I made regarding a post that wasn't even yours? I guess I should have been more careful and checked that the person offended by what I wrote wasn't even the person whom I replied to, but you can surely understand my presumption. I mean, I even quoted the posted I was replying to.
But OK, I'll bite. What exactly do you need Bixby to do? What device maintenance commands does it help you with.
This is from the original post:
- Turn on/off Fast Charging
- Turn on/off Fast Wireless Charging
- Save my location as my home
- Check for app updates in the Play Store
For the first 2, my only question is why? How often do you need to toggle it? I've had a GS 7 Edge for 2 years and not once did I need to disable fast charging. No battery degradation either. The 3rd one needs to be done only once I presume. The last one updates automatically over wifi once you are charging. If you don't have it set up that way, you should. And just about everything else is quickly accessible through the notification menu. I am genuinely curious, maybe there is a compelling reason for me to set up Bixby instead of having that dedicated button be a nuisance that gets accidentally pressed all the time.
Bixby use
sputnik767 said:
I concur. Returning this phone because Bixby sucks has to be the silliest reason I've ever heard, considering that Google Assistant is available and is light years ahead of Bixby. I haven't even set Bixby up on my phone and I don't see why I would ever want to.
And perhaps there are reasons to return this phone, but people hyperventilating on the official forums (or anywhere on the internet) have to be taken with a huge grain of salt.
Click to expand...
Click to collapse
PsiPhiDan said:
Returning a Note9 in favor of the Note8 due to Bixby being bad... When Google Assistant is readily available... Whoa. Brain cannot compute this...
Click to expand...
Click to collapse
sputnik767 said:
Wait, so you took offense to a reply I made regarding a post that wasn't even yours? I guess I should have been more careful and checked that the person offended by what I wrote wasn't even the person whom I replied to, but you can surely understand my presumption. I mean, I even quoted the posted I was replying to.
But OK, I'll bite. What exactly do you need Bixby to do? What device maintenance commands does it help you with.
This is from the original post:
- Turn on/off Fast Charging
- Turn on/off Fast Wireless Charging
- Save my location as my home
- Check for app updates in the Play Store
For the first 2, my only question is why? How often do you need to toggle it? I've had a GS 7 Edge for 2 years and not once did I need to disable fast charging. No battery degradation either. The 3rd one needs to be done only once I presume. The last one updates automatically over wifi once you are charging. If you don't have it set up that way, you should. And just about everything else is quickly accessible through the notification menu. I am genuinely curious, maybe there is a compelling reason for me to set up Bixby instead of having that dedicated button be a nuisance that gets accidentally pressed all the time.
Click to expand...
Click to collapse
Hi
No, not any of the above maintenance tasks.
I use (used) bixby for - (at night time)
changing power saving to mid
lowering volumes
cleaning memory
clearing space
The thing is I could put all the above commands in one quick command, and with bixby wake-up with voice pwd, Bixby would perform these without me having to even touch the phone. Of course, now with samsung removing the wake-up with voice pwd, I have to physically unlock the phone.
Yes, I have activated the do not disturb (time-based), so maybe the volume command was not needed
Now, since bixby is no longer working as it was previously, I did find something else to replace that. I tried using IFTTT, but that didn't have the above commands, only completely mute the phone, which I don't want.
I am using routines, which is available through Good Lock on samsung app store (not in google play).
thanks
Although some people have a use for Bixby, I'm not one of them. I tried to remap the button with BX Buttons (?), but it didn't work for me.
I was using Package Disabler Pro on two previous Samsung phones and tablets, so I thought I'd try it on the Note 9. As discussed elsewhere on this forum, that version of the app doesn't work on the Note 9. I bought the recommended Package Disabler Pro + from policedeveloper and it worked fine on the Note 9.
Using the new Package Disabler, I killed all the Bixby apps, which made the button totally inert. I wish I could have remapped it, but at least now I don't accidentally bring up Bixby all the time.
mojoehand said:
Although some people have a use for Bixby, I'm not one of them. I tried to remap the button with BX Buttons (?), but it didn't work for me.
I was using Package Disabler Pro on two previous Samsung phones and tablets, so I thought I'd try it on the Note 9. As discussed elsewhere on this forum, that version of the app doesn't work on the Note 9. I bought the recommended Package Disabler Pro + from policedeveloper and it worked fine on the Note 9.
Using the new Package Disabler, I killed all the Bixby apps, which made the button totally inert. I wish I could have remapped it, but at least now I don't accidentally bring up Bixby all the time.
Click to expand...
Click to collapse
looking up the package disabler from policedeveloper now. thanks!
This is a pretty big issue that blue up on the OnePlus forum and Reddit. People are experiencing ghost touches in apps. It's very easy to also experience this by opening cpu-z and letting it sit there for a minute or two not doing anything. It seems not everyone is experiencing this though. I have tested and do experience it. Do you?
Yup. Mine does with cpu-z open. what do we do?
BossJ said:
Yup. Mine does with cpu-z open. what do we do?
Click to expand...
Click to collapse
Depends if it's a hardware or software issue. Personally I already submitted a return request with OnePlus.
I just cancelled my order.. hopefully there is a software fix for you guys
This only happens to me on cpu-z and not in any other app. So I guess a future software update is gonna fix it.
Left it for a minute and didn't notice anything. On 9.5.3, bootloader unlocked and patched boot image with root.
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
I installed CPU-Z just to check on my International 8GB/256 model and I've got no issue with ghost touches. Not sure what is causing this for you all, but I do hope it is sorted out for you all.
When I turned off NFC the issue went away for me glad I don't use it whatsoever haha
Purest said:
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
Click to expand...
Click to collapse
Well that's not a solution disabling a useful feature to not have ghost touch issue.
On screen/off screen gesture are one of my favorite using it, so not a solution to me.
Simple will return the device.
I haven't order yet but i will next couple of days.
There's many reports across oneplus forum.
https://www.androidpolice.com/2019/...ros-are-suffering-phantom-touch-input-issues/
I left CPU-Z running for at least 10 mins.
And all is OK. Maybe it's a rouge program or something to do with the unlock\twrp?
The only way to be sure is to reset to stock and only install CPU-Z
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
romanB_SK said:
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
Click to expand...
Click to collapse
Wow that's seems real bummer.
Why would OP use Novatek display controller since had bad reputation and bad track record.
So the question is how do we know if all that units effected having all of the them Novatek display controller?
Or if there's another supplier for those units that don't have that issue.
Man things are getting much worse if it's hardware related and not software that I thought.
Sent from my V1821A using Tapatalk
It's extremely annoying it has happened to me a few times even when I was boasting about the new device to some colleagues at work. I thought it was me at first until then I read IRS an actual thing. I won't return it yet but I might if it's not sorted soon. It's extremely irritating.
Sent from my [device_name] using XDA-Developers Legacy app
Looks like ghost touches are related to NFC. Try with NFC turned off.
C3C076 said:
Looks like ghost touches are related to NFC. Try with NFC turned off.
Click to expand...
Click to collapse
Can confirm. My Ghost touches seize when NFC is disabled.
Sent from my GM1913 using Tapatalk
I've started yesterday experiencing that ghost touchs and also screen not responsive to touch in some panel sections (mostly the upper right zone). The phone didn't gave me that problem since I bought. I noticed when this happening, pulling the notification bar down to the tile settings makes that zone work again. Same thing happened when that random ghost touchs happens.
Didn't had any problems, don't use NFC, tried turning it on, ghost touches started appearing on cpuz, but not on other apps. As i don't use NFC i probably won't return the phone.
I just tried with CPU-Z and a few seconds after starting the app, the screen turns crazy tapping here and there. Can confirm also disabling NFC solves it.
Turning off nfc or not using gestures or not using cpuz app is just temporary solution.
And there's multiple reports that ghost issues happening other app too.
And we never know if thing get worse over time.
I'm afraid it's a more common issue than we thought but many users simple didn't notice it until now.
Oneplus should clearly take attention on that issue seriously and fix it ASAP.
Shouldn't be happening at all with any kind app or scenario of usage.
Sent from my V1821A using Tapatalk