ChopAssistant Not Needed on Shamu with LineageOS - Nexus 6 General

Do you remember how great it felt after you had Pixelised your Shamu so you could use Google Assistant? And then how crushed and defeated you felt after the first (maybe second) time you uttered the words "OK Google" because you were then looking at the "retrain voice model" dialog? That crushed feeling is what led to ChopAssistant, a veritable gift from the Gods. ChopAssistant would just sit quietly out of the way until that dialog appeared and then, quick as a flash, would vanquish it.
ChopAssistant has served us well, however I am very happy to report that it is no longer needed! At least, not on a Nexus 6 Shamu running official LineageOS 14.1. I am not altogether sure if the hero is LineageOS, or if it was how I set it up this time. I'll explain how I did things this time around, and then leave the rest as an exercise to the reader.
I did a 'super-squeaky-clean' flash. The first step was to wipe and format EVERYTHING from within TWRP. Next, rebooted back into TWRP, connected a USB cable and 'adb push'd the LineageOS image (NOT the 'experimental migration' one), the addonsu image, the latest Gapps, and my addon.d script for Pixelising the build.prop. I then flashed, in order, LineageOS image + addonsu + Gapps. No reboot. Next step: mount /system and manually inspect build.prop to make certain my script would still work (script wasn't in place at this stage). Satisfied that it would, I made the changes to build.prop by hand and put my script into /system/addon.d/ with appropriate perms. I did that via a 'adb shell' from my PC (easier on the eyes and fingers). Finally I unmounted /system and rebooted into brand spanking new LineageOS for the first time.
One more thing I should point out... The _ONLY_ way I have been able to get "OK Google" hotword detection to work is when using Nova (Prime), and then only when the search app/overlay is visible. Oh, it works from within the Assistant as well.
Sent from my Pixel XL using Tapatalk

Why so hard?I trained Google Now everywhere, added ro.opa.eligible_device=true to build.prop via root browser, rebooted and it worked.
And it works from everywhere, contacts, browser, launcher, screen off (personalised search), it does over do it though, sometimes it seems Assistant gets triggered by silience, especially when playing games.

It's also not needed if you train OK Google before installing Assistant mod on the stock ROM. Simply reboot and allow Google app to update on its own.

NiksSkersts said:
Why so hard?I trained Google Now everywhere, added ro.opa.eligible_device=true to build.prop via root browser, rebooted and it worked.
And it works from everywhere, contacts, browser, launcher, screen off (personalised search), it does over do it though, sometimes it seems Assistant gets triggered by silience, especially when playing games.
Click to expand...
Click to collapse
You are so lucky! I can't even turn on OK Google detection in Google now's settings. The 'Say "OK Google" at any time' toggle. It turns off immediately after you try turning it on.
Two questions for you... Do you also set 'ro.product.model' to "Pixel XL"? And you are running the official LineageOS, right?
Sent from my Pixel XL using Tapatalk

SteveYoungs said:
You are so lucky! I can't even turn on OK Google detection in Google now's settings. The 'Say "OK Google" at any time' toggle. It turns off immediately after you try turning it on.
Two questions for you... Do you also set 'ro.product.model' to "Pixel XL"? And you are running the official LineageOS, right?
Click to expand...
Click to collapse
1) Nope, Eligible_device was the only change.
2)I am running official 26th of January LineageOS

wabmorgan said:
It's also not needed if you train OK Google before installing Assistant mod on the stock ROM. Simply reboot and allow Google app to update on its own.
Click to expand...
Click to collapse
Assistant mod from Google Play store? I think it adds the same line to Build.prop, just made easier for end user.
Edit: Sorry for double post, I didn't see your post earlier.

Or you can just install Pure Nexus and it will work out the box.

christianpeso said:
Or you can just install Pure Nexus and it will work out the box.
Click to expand...
Click to collapse
Where's the fun in that? LOL Actually, after CyanogenMod closed up shop, and before LineageOS came to life, I had been seriously thinking of trying Pure Nexus. But that may be for another time now as I have been able to get everything working great in LineageOS.
I will keep Pure Nexus in mind the next time I can't get my own way with LineageOS.

SteveYoungs said:
Next, rebooted back into TWRP, connected a USB cable and 'adb push'd the LineageOS image (NOT the 'experimental migration' one)
Click to expand...
Click to collapse
The LineageOS image? Where do I find that? I only see a zip available from the LineageOS download area.

MrBrady said:
The LineageOS image? Where do I find that? I only see a zip available from the LineageOS download area.
Click to expand...
Click to collapse
Yeah, that's what I was talking about. Sorry if that caused confusion.
Sent from my Nexus 6 using Tapatalk

I just clean flashed the 02/03/2017 build of Oct-N with 01/21/2016 Dynamic GApps and OK Google worked perfectly then I updated Google App from Play Store and the next time I said "OK Google" Google Assistant ran perfectly. It's been running perfectly ever since. Weird!! It doesn't usually go that smooth but I'll take it.

Related

Finally, got google wallet to install on the SGS3 (UK)

WARNING: THIS METHOD DOES NOT WORK ON 4.1 (JELLYBEAN)
Ok, so first things first! I haven't tried using it to make purchases yet nor have I tried adding or topping up cards (I've only activated the prepaid google card and got the $10)
After 2 weeks of trying various methods and reading through various xda forums/posts etc and google I finally got it.
You'll need;
The latest firmware on SGS3 (can't confirm it will work on previous firmware)
A rooted device
market enabler
and finally the modaco patched google wallet
If you've never had google wallet on your phone you can skip steps 1-2
1. force close google wallet and clear the cache/data.
2. uninstall google wallet and delete any of it's files you might have saved.
3. backup your build.prop file from the system folder and move the original somewhere else.
4. open your build.prop file and look for the lines that says ro.product.model, ro.product.brand, and ro.product.device.
5. you want all 3 to read htc_jewel like so
Code:
ro.product.model=htc_jewel
ro.product.brand=htc_jewel
ro.product.name=m0xx
ro.product.device=htc_jewel
6. move your edited build prop file back to the system folder.
7. put your google wallet apk in the system/app folder using your chosen method.
8. Do Not open google wallet yet (This is where I was going wrong for most of it)
9. restart device.
10. switch NFC on if it isn't on.
11. open google wallet and follow on screen instructions.
options 12 - 14 might not be necessary but I'm putting them just in case
12. open market enabler and set it to t mobile us.
13. open the play store and find google wallet and uncheck automatic update.
14. you can now reset your google play back to UK.
source(s) various XDA posts (Mainly HTC forum) and Modaco for the patched apk
Steps 12 - 14 won't be necessary for sure.
Once you have got it working have you tried changing your build.prop back to see if it still works? Long term implications of having your phone think its something else could break other apps.
Plus on a side note, I thought Market Enabler didn't work with the new market versions?
what is the benefit of having google wallet in the UK? are we able to use it at all and for what?
I can confirm that Wallet now works in LFB without any of the hacks in the OP
Just have LFB rom installed and push the modified Wallet file in the OP to system, reboot and it works.
NFC.apk was upgraded in LFB this must have been included in the changes.
that's good but tell me... who has seen an NFC enabled payment system anywhere in England?!!? I know McDonalds have it, will this Google wallet work with that?! I don't want to bust out my phone to pay and end up looking like a tit! haha
weezul said:
that's good but tell me... who has seen an NFC enabled payment system anywhere in England?!!? I know McDonalds have it, will this Google wallet work with that?! I don't want to bust out my phone to pay and end up looking like a tit! haha
Click to expand...
Click to collapse
Loads of shops
All McDonalds have them, All Greggs (bakery) have them, Most Pret coffee shops have them now and there are lots more too.
Visa and Samsung are pushing NFC payments for the Olympics so expect loads more to pop up this summer! (along with Visa apps).
weezul said:
that's good but tell me... who has seen an NFC enabled payment system anywhere in England?!!? I know McDonalds have it, will this Google wallet work with that?! I don't want to bust out my phone to pay and end up looking like a tit! haha
Click to expand...
Click to collapse
Quite a few places in London..
I have an AMEX and VISA with contactless but never managed to get it working.. and yes I feel like a tit for trying each time
:crying:
EDIT:
I managed to get google wallet installed as per Lenny UK's instructions with the new firmware.. I just can't add the google prepay card.
And still unsure whether we can use Google Wallet rather than our normal contactless cards in the UK
sweet i did not know about greggs/subway. That's pretty sweet. I really REALLY want to try this. Anyone actually tried it out and about yet?
hboos said:
Quite a few places in London..
I have an AMEX and VISA with contactless but never managed to get it working.. and yes I feel like a tit for trying each time
:crying:
EDIT:
I managed to get google wallet installed as per Lenny UK's instructions with the new firmware.. I just can't add the google prepay card.
And still unsure whether we can use Google Wallet rather than our normal contactless cards in the UK
Click to expand...
Click to collapse
Look for Modaco's forum post with this app, he details how to get money loaded onto the app.
over before it began..."Application Not Installed"
and my only choice is "OK". no explanation. My device is rooted and on siryah kernel, Omega 8.0, baseband XXLFB?
weezul said:
over before it began..."Application Not Installed"
and my only choice is "OK". no explanation. My device is rooted and on siryah kernel, Omega 8.0, baseband XXLFB?
Click to expand...
Click to collapse
You need to push this file to /system/app it will not install like a regular app.... I said this as did the OP... please read
apologies. Excitement got the better of me. Thanks
It seems that you need to make the changes to the build.prop file to add your google prepay card and after that registers, you can resotre your original file.
unfortunately, to add more credit, you need to pay over the odds to use an american credit card.
well hopefully we're all set for when it launches! in the meantime I think my next meal will be on Google thanks for the great thread and info
I got angry with it not working so removed it
Hey Guys, this is great. Quick warning though there is a known issue that if you switch rom, wipe you device or do anything like that without going into wallet first and using the reset wallet option inside google wallet , it can break the nfc secure element in your phone and you will not be able to use google wallet ever again on that phone.
This happened to quite a few people when I wrote a similar thread to this about 3 weeks ago now and some people had to RMA their phone or claim on insurance. I mean it even stopped working on my phone when I tried to remove it properly using the reset wallet option. So i deleted the guide and had the thread closed just incase.
I am not saying that this will happen to you or anything like that, just thought I would warn people as I'm sure as Lenny said there will be alot of english wallet apps coming out this summer for the the Olympics so it might be worth waiting untill then. Not trying to scare people or anything well done to the OP great post just don't want people breaking their new phones.
Lennyuk said:
I got angry with it not working so removed it
Click to expand...
Click to collapse
Likewise, but it does work - you just have to change ro.product.device and ro.product.model in build.prop to "htc_jewel", then force stop the app and clear data in "manage apps", then reboot.
And Robert's your father's brother...
dave_uk said:
Likewise, but it does work - you just have to change ro.product.device and ro.product.model in build.prop to "htc_jewel", then force stop the app and clear data in "manage apps", then reboot.
And Robert's your father's brother...
Click to expand...
Click to collapse
I did try that and still no luck for me.
As for the above warning, its good to note, but a bit worrying that google will lock you down like that?
Lennyuk said:
I did try that and still no luck for me.
As for the above warning, its good to note, but a bit worrying that google will lock you down like that?
Click to expand...
Click to collapse
We're talking about real moneys here, it's not your regular home brew nfc hack. The data need to be tampering proof...
Sent från mein I9300 via Tapatalk 2. Kyllä!
Lennyuk said:
I did try that and still no luck for me.
As for the above warning, its good to note, but a bit worrying that google will lock you down like that?
Click to expand...
Click to collapse
It took me a while too because I had installed the wallet without chaning the build.prop but this is what I did.
in google wallet >settings > reset wallet
delete apk from system/app
restarted the device
backed up and changed the build.prop
placed apk back into system/app
restarted the device
started google wallet
added card.. (it takes about 2-3 mins)
exited wallet
restored original build.prop.
seems like a hassle but I suppose there's a free mcdonald's meal for your hard work

[Q] Google Wallet and 4.2.2 (T-Mobile)

I've been searching for the past 24 hours (almost non-stop) for a way to make Google Wallet work on my phone. And I still haven't been able to find one for the Nexus 4. Other devices, I have... but I don't know if those will work (i.e. GS4 fix will work on N4?).
I'm currently running Illusion v2 Beta. And every time I try to just open up GW to set it up... I get this screen (attached image).
Before I rooted and everything, it was running perfectly. I've uninstalled it. Reinstalled. Cleared data/cache. Tried on WiFi and on Mobile Data... and still nothing works.
So how do I get Google Wallet to work on my phone?
jbdavies said:
I've been searching for the past 24 hours (almost non-stop) for a way to make Google Wallet work on my phone. And I still haven't been able to find one for the Nexus 4. Other devices, I have... but I don't know if those will work (i.e. GS4 fix will work on N4?).
I'm currently running Illusion v2 Beta. And every time I try to just open up GW to set it up... I get this screen (attached image).
Before I rooted and everything, it was running perfectly. I've uninstalled it. Reinstalled. Cleared data/cache. Tried on WiFi and on Mobile Data... and still nothing works.
So how do I get Google Wallet to work on my phone?
Click to expand...
Click to collapse
Have you tried uninstalling it and using Mocados mod? You can find it here: http://www.modaco.com/topic/354635-xmod-region-device-root-patched-google-wallet/
When using Google wallet and changing ROMs you have to reset wallet before you change, read more about it in the link, its an Xposed mod.
22sl22 said:
Have you tried uninstalling it and using Mocados mod? You can find it here: http://www.modaco.com/topic/354635-xmod-region-device-root-patched-google-wallet/
When using Google wallet and changing ROMs you have to reset wallet before you change, read more about it in the link, its an Xposed mod.
Click to expand...
Click to collapse
I have. And not even that worked for me.
Three things to note:
1) Are you near Salt Lake City? T-Mobile issues ISIS SIM cards in Salt Lake City and Austin (beta test market) which are known to conflict with Google Wallet. You will need a NON ISIS SIM card for Google Wallet.
2) Rev 11 phones had a known issue (like mine), which required contacting Google with a debug log. Within a week or two, they will fix the Secure Element initialization issue on their backend.
3) The latest market version has had issues for some with custom (rooted) ROM's. Try an older APK, or stock ROM.
SpookyTunes said:
Three things to note:
1) Are you near Salt Lake City? T-Mobile issues ISIS SIM cards in Salt Lake City and Austin (beta test market) which are known to conflict with Google Wallet. You will need a NON ISIS SIM card for Google Wallet.
2) Rev 11 phones had a known issue (like mine), which required contacting Google with a debug log. Within a week or two, they will fix the Secure Element initialization issue on their backend.
3) The latest market version has had issues for some with custom (rooted) ROM's. Try an older APK, or stock ROM.
Click to expand...
Click to collapse
I am in Salt Lake City, but my sim card doesn't say ISIS... which I think they always do? Mine doesn't say anything.
I'll try and find an older Wallet apk and see if that helps.
If not, guess I'll be submitting a bug report to Google.
Thanks for the info.
jbdavies said:
I am in Salt Lake City, but my sim card doesn't say ISIS... which I think they always do? Mine doesn't say anything.
I'll try and find an older Wallet apk and see if that helps.
If not, guess I'll be submitting a bug report to Google.
Thanks for the info.
Click to expand...
Click to collapse
Try this one: http://forum.xda-developers.com/showpost.php?p=37299470&postcount=3182
SpookyTunes said:
Try this one: http://forum.xda-developers.com/showpost.php?p=37299470&postcount=3182
Click to expand...
Click to collapse
That still didn't work.
How do I go about submitting a bug to Google about this? Do I have to do it from the phone?
jbdavies said:
How do I go about submitting a bug to Google about this? Do I have to do it from the phone?
Click to expand...
Click to collapse
This applies to stock Android, as Google has no way to fix an issue in a third party ROM. If you flash back to stock 4.2.2 and still have the issue, then this is the process Google sent to me:
1. On your phone/tablet go into Settings, About Phone, tap "Build Number" seven times. Developer options will then appear in Settings.
2. Go into Developer Options and enable Developer Options (ON/OFF switch at the top), then enable "USB Debugging" (near the bottom of the screen).
3. Nexus devices: Press and hold volume down + and volume up buttons. Now also press and hold power button until you can feel the phone vibrate.
4. In about 20 seconds, you'll get a double buzz. A Gmail message dialog should appear. Please email the bug report to yourself and then attach it to your email and send it off to [email protected]
Maybe its the ROM your running? I have actually switched between ROMs and have never reset my Google wallet. It just always works .
Sent from my Nexus 4 using xda app-developers app
PJcastaldo said:
Maybe its the ROM your running? I have actually switched between ROMs and have never reset my Google wallet. It just always works .
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I've thought about that. Just haven't felt like switching... because I'm lazy like that. Haha.
But if a fix doesn't come up in the next day or so... I wont have a choice.
Had the same problem a month ago. As stated in the earlier post you got to call Google and send the log cat. They walked me through it over the phone took about a week for them to fix it and then they gave me a 20 dollar play store credit. Still spending that 20 dollars about 8 dollars left to buy more apps.
I couldn't get google wallet to work for like a month. i try today after seeing this post and it works. crazy.
I did call google in the past and they asked for the log but i never sent it.

System dump?

Hi so been on 7.0 for at least a month and just last two days phone was being really buggy so I turned the phone off and back on phone didn't prompt for password to boot.
Is there a way I can save the whole phone on to drive to send to someone to take a closer look to see what virus is on here Im guessing it's a rootkit some how also what way would you run packet capture to see things that way?
Sent from my Nexus 6P using Tapatalk
gjkrisa said:
Hi so been on 7.0 for at least a month and just last two days phone was being really buggy so I turned the phone off and back on phone didn't prompt for password to boot.
Is there a way I can save the whole phone on to drive to send to someone to take a closer look to see what virus is on here Im guessing it's a rootkit some how also what way would you run packet capture to see things that way?
Click to expand...
Click to collapse
I would just grab the latest software image from google and start all over....by the way this doesn't belong here...it belongs in Q&A
Well I think I have a virus I figure people here are going to would want to take a look at that
Sent from my Nexus 6P using Tapatalk
Hii, i would love to take closer look into your phone ? contact me
Viper-GT said:
Hii, i would love to take closer look into your phone contact me
Click to expand...
Click to collapse
let me know what i need to do i did adb backup-full but i doubt it has everything you need.
also couldnt wait so i manually flashed full image downloading the newest beta again.
kornklown69 said:
I would just grab the latest software image from google and start all over....by the way this doesn't belong here...it belongs in Q&A
Click to expand...
Click to collapse
doing this still didnt work even tried another rom manually flashed everything on week 3 my phone started acting buggy restarted phone everything is fine next week i get message that someone has saved new device from my bank bank account if my bank didnt have this feature i would probably not know this happend along with seeing the txt messages showing the second factor authentication.
please tell me how i can get this phone fully backed up with the virus in it to have it sent to someone to review what virus it has?
im going to try emailing other security firms, and google and also look at probably using an iphone for awial.
gjkrisa said:
doing this still didnt work even tried another rom manually flashed everything on week 3 my phone started acting buggy restarted phone everything is fine next week i get message that someone has saved new device from my bank bank account if my bank didnt have this feature i would probably not know this happend along with seeing the txt messages showing the second factor authentication.
please tell me how i can get this phone fully backed up with the virus in it to have it sent to someone to review what virus it has?
im going to try emailing other security firms, and google and also look at probably using an iphone for awial.
Click to expand...
Click to collapse
a virus would be software related...if you did a full wipe and installed fresh software and it continues it might be an app you keep installing...do you get your apps from the playstore or side load as well
kornklown69 said:
a virus would be software related...if you did a full wipe and installed fresh software and it continues it might be an app you keep installing...do you get your apps from the playstore or side load as well
Click to expand...
Click to collapse
playstore only before my phone was locked boot loader and encrypted to have to use pin to boot device.
AS SOON as i get the buggy phone and reboot when it boots up it no longer request pin to boot. on stock rom i was rebooting phone every week to see how long it would take and usually nothing odd until phone got buggy for reason of the reboot.
the buggy issue is shortly opening an app the app will freeze so i hit home nothing happends try to turn the screen off nothing happends until a minute later sometimes phone will reboot its self or i hold power to make it reboot but both take about same amount of time when phone goes into full freeze.
so it being a playstore app and the virus not getting detected google needs to look into how they can patch this...
so im putting this out there so this person or group doesnt forever have a backdoor into peoples phones.
this issue i have had since november last year but havent been so aware about the issue till august. since august ive been dealing with know some how they are getting in and must be an app but i got rid of all games and weird apps that are not nessisary
abs workout, esfile explorer, google+,mint personal finance,tapatalk,accuweather,alaskausafcu,amazon kindle, android auto, android device manager, android pay, calculator, chrome browser, chrome remote desktop, clock, cloud print, contacts, es task manager, facebook, family locator, favorite frequencies, fing, garmin connect, gci my usage, gmail, google, google calendar, google camera, google docs, google drive, google goggles, google keep, google keyboard, google news, google now launcher, google opinion, google photos, google play games, google play music, google txt to speech, hulu, keeper, look out, malwarebytes, maps, messenger, eset mobile security, pandora, playstation phone, phone, shazam, sixaxis controller, skype, speed test, usaa mobile, vlc for android, wifi analyzer, xbox, youtube, zombies run
these are all the apps ive had since ive had this issue.
i was hopping that esfiles exploreres new feature of being notified of new files would help solve this but some folders it doesnt detect like youtube or google music even though in es files explorer i unlocked ability to view the .nomedia
Drop ES File Explorer, to start. Read this article, or do some googling about it on your own;
https://www.androidpit.com/this-is-why-you-should-not-use-es-file-explorer
I have to agree with the article when it says Solid Explorer is a great replacement. I've used it for years now and it's never let me down.
The fact of the matter is, if you manually wiped all of your phone and formatted your internal storage, nothing remains from pre-wipe. If your issue is coming back it can only be a hardware issue (if applicable) or some app you are using, as previously mentioned.
Furthermore, after googling your exact issue I came to find that certain apps that require 'Accessibility Services' can and will disable your pin/password/pattern on boot. Check if any of your apps fit the bill in 'Settings > Accessibility > Services'
Disable any apps which are enabled and reboot. You may have to set up pin, etc., again, but leave the services disabled and see if the issue returns. Let us know!
Edit: Upon more googling, I've found reports of people who had the issue return after disabling & uninstalling the apps in question as well. You may need to flash stock images again and do not install any apps that require accessibility services, or don't grant any of them permission even once.
Edit2: Just another link to check out;
https://blog.g3rt.nl/android-lollipop-encryption-user-interface-flaw.html
Edit3: Issue tracker link; https://code.google.com/p/android/issues/detail?id=219498
Edit4: If you logged into your bank app and factory reset or flashed factory images, logging in again after the wipe/flash will show as a new device. Same goes for having login alerts set for Google / Facebook, etc. Your same phone shows as a new device after the flash or wipe. Guaranteed not a virus.
Double post
RoyJ said:
Drop ES File Explorer, to start. Read this article, or do some googling about it on your own;
https://www.androidpit.com/this-is-why-you-should-not-use-es-file-explorer
I have to agree with the article when it says Solid Explorer is a great replacement. I've used it for years now and it's never let me down.
The fact of the matter is, if you manually wiped all of your phone and formatted your internal storage, nothing remains from pre-wipe. If your issue is coming back it can only be a hardware issue (if applicable) or some app you are using, as previously mentioned.
Furthermore, after googling your exact issue I came to find that certain apps that require 'Accessibility Services' can and will disable your pin/password/pattern on boot. Check if any of your apps fit the bill in 'Settings > Accessibility > Services'
Disable any apps which are enabled and reboot. You may have to set up pin, etc., again, but leave the services disabled and see if the issue returns. Let us know!
Edit: Upon more googling, I've found reports of people who had the issue return after disabling & uninstalling the apps in question as well. You may need to flash stock images again and do not install any apps that require accessibility services, or don't grant any of them permission even once.
Edit2: Just another link to check out;
https://blog.g3rt.nl/android-lollipop-encryption-user-interface-flaw.html
Edit3: Issue tracker link; https://code.google.com/p/android/issues/detail?id=219498
Edit4: If you logged into your bank app and factory reset or flashed factory images, logging in again after the wipe/flash will show as a new device. Same goes for having login alerts set for Google / Facebook, etc. Your same phone shows as a new device after the flash or wipe. Guaranteed not a virus.
Click to expand...
Click to collapse
Thank you! I tried googling but guess I wasn't doing it properly.
I turned off keeper nothing.
I un installed it nothing.
I dont know how to re enable boot encryption pin.
the phone says it is so I'll try clean install again and just not allow keeper anymore I think the issue has come up just after turning keeper on to allow the accessibility features.
Thank you I will keep you informed give it till February if nothing odd happened.
Sent from my Nexus 6P using Tapatalk
gjkrisa said:
Thank you! I tried googling but guess I wasn't doing it properly.
I turned off keeper nothing.
I un installed it nothing.
I dont know how to re enable boot encryption pin.
the phone says it is so I'll try clean install again and just not allow keeper anymore I think the issue has come up just after turning keeper on to allow the accessibility features.
Thank you I will keep you informed give it till February if nothing odd happened.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Also thanks I know about the added devices I cleaned the one to my bank account and I look at my other accounts every once in awial and make sure nothing odd wish my bank account showed what devices instead of only having clean on Facebook I've had things look suspicious ips from another states but the device listed was same as mine so don't know if they are able to spoof that.
I always assumed that some how the cell tower was saying it is relayd to Cali or something.
I live in Fairbanks Alaska.
Sent from my Nexus 6P using Tapatalk
Well turns out it was keeper I switched to last pass uninstalled keeper before uninstall It was telling me 8 hrs of battery life. Now 21 more hrs with already being on for 5 hrs at 78%.
Phone hasn't had any weird issues. Except I had lost the encryption anyways and only after having the new image for one week now been going for three weeks.
Sent from my Nexus 6P using Tapatalk
https://technet.microsoft.com/en-us/library/jj200124(v=ws.11).aspx
Sent from my Nexus 6P using Tapatalk

Bug in "OK Google" in resurrection remix

In the following rom: https://forum.xda-developers.com/s7...-resurrection-remix-os-nougat-t3528861/page57
There is a bug within the OK google flow. The first time you you say OK google and set it up (or by just going into the settings and doing it) it looks fine until you go to use it.
After you set up, when you say "OK Google", it brings up the set up again. When you try to run the set up it detects you saying ok google as part of the set up bringing up ANOTHER set up prompt..and then another...and another, I think you get the point.
So OK google is just broken
I would like to reply to this in the forum post but I don't have enough post creds apparently >.>
That's a bug with Google Assisstant on every non-Pixel phone
Is there a way to disable the assistant while still getting OK google to work?
im on beta 5 xda/rom (s7 edge 935f),how should i install this,i dont even know which one is the rom,please tell me as simple as u can,cause i did install beta 5 via twrp so..i know the basics.
try this
https://play.google.com/store/apps/details?id=choplabalagun.blogspot.com.chopassistant
That app seems to work, the voice training still comes up for about a second but its much better than not having it at all!
Hopefully this bug gets fixed soon.

Google Assistant?

Has anyone managed to get Assistant to work? I'm in the UK. I read on one of the OnePlus community forums that you need to change device language to English (USA), which I've done. Still no Assisstant. Anyone managed to get it to work/have any ideas?
It is only google now, not google assistant
I needed to clear all data after changing language to English (USA). But I've got it working now.
Here's YouTube video showing steps to setup Google Assistant on OP5. https://youtu.be/-bE8ORPID3U
Sent from my Pixel XL using XDA-Developers Legacy app
Ok Google
saccentekennedy said:
I needed to clear all data after changing language to English (USA). But I've got it working now.
Click to expand...
Click to collapse
After you got it working, did you have any issues in retraining your voice. I have a problem where it appears to be listening for me to say Ok Google 3 times but never recognises anything.?
dudiemaroodi said:
After you got it working, did you have any issues in retraining your voice. I have a problem where it appears to be listening for me to say Ok Google 3 times but never recognises anything.?
Click to expand...
Click to collapse
No... Haven't had a problem if I'm honest
saccentekennedy said:
No... Haven't had a problem if I'm honest
Click to expand...
Click to collapse
Thanks for replying. Must be in if the unlucky ones. :laugh:
i changed to English US, got google assistant started up, then changed the language back to English UK.
google does have issues properly understanding you with the wrong accent from my experience.
I am pretty sure I have google assistant
saccentekennedy said:
Has anyone managed to get Assistant to work? I'm in the UK. I read on one of the OnePlus community forums that you need to change device language to English (USA), which I've done. Still no Assisstant. Anyone managed to get it to work/have any ideas?
Click to expand...
Click to collapse
Doesn't work for me either. I have set the language to English USA. Tried to clear Google app cache and data to no avail.
swami.2580 said:
Doesn't work for me either. I have set the language to English USA. Tried to clear Google app cache and data to no avail.
Click to expand...
Click to collapse
I got Google Assistant working by following the instructions from the YouTube video in this thread's post #4. All was fine for a while and then GA no longer worked sometime after I applied one of the OTA's. I can't say that was the cause but the timing was coincidental. GA seemed to react but not fully engage. I tried a lot of things including re-training the "OK Google" but nothing worked.
Finally I followed the part of post #4's cache clearing of Google and Google services apps cache (remember there is more than one cache) and then went through the Google Assistant set up as if it had never been working. That fixed my issues and has been working ever since. I'll see if the same problems arise after the next OTA. So I'd trying clearing the cache of those two apps EXACTLY as shown in the video.
Edit: I've applied OTA for v4.5.5 and have not had any Google Assistant issue
swami.2580 said:
Doesn't work for me either. I have set the language to English USA. Tried to clear Google app cache and data to no avail.
Click to expand...
Click to collapse
You have to clear the data cache for play services as well.
For those that got Google Assistant working are you having any issues such as those described below?
Trusted voice which enables Google Assistant from the lock screen does not work despite the proper settings in place
Creating a Google Assistant shortcut not works
IFTTT doesn't seem to work as advertised (I'm still working on this one)
I've had no end of small issues trying to customize Google Assistant but the main built in functions (e.g. weather, search, Spotify commands, open app) work perfectly.
Just curious about other people's experience. It leaves me feeling Google Assistant is just a beta program/work-in-progress on a phone or a tease to get you to buy a Google Home despite always having a much more capable device in the palm of your hand (your phone). I don't want an ugly Google Home "air freshener" when I already have an Android SD835/8GB phone.
When you say Google Assistant... Do you mean ok Google from screen off?
loudog3114 said:
When you say Google Assistant... Do you mean ok Google from screen off?
Click to expand...
Click to collapse
Google Assistant works with the screen off as long as the OP5 is NOT locked. Working while locked is supposed to work only when Trusted Voice is turned on. Unfortunately I have turned on trusted voice but Google Assistant will not initiate (work) when the OP5 is locked.
OK Google has a different interactive screen than Google Assistant. The OP5 OOS comes with OK Google but you need to manually activate Google Assistant before experiencing its advanced AI features. You would also see new Google Assistant specific settings at the top of the Google app->Settings->Google Assistant->(Settings, What can you do?).
One of the early posts in this thread has the link to manually activate Google Assistant.
Yeah, I have Google Assistant but I am pretty let down by the fact it doesn't work with the screen off and locked. I have heard it's a license that has to be paid to googs
Mine worked with no fuss. What doesn't work is the trusted voice and waking the phone up when the screen is off. That one I can't figure out
loudog3114 said:
Yeah, I have Google Assistant but I am pretty let down by the fact it doesn't work with the screen off and locked. I have heard it's a license that has to be paid to googs
Click to expand...
Click to collapse
goingonstrong2 said:
Mine worked with no fuss. What doesn't work is the trusted voice and waking the phone up when the screen is off. That one I can't figure out
Click to expand...
Click to collapse
I've found a hacky workaround for this issue by using a combination of apps. First off I only use this method when I'm connected to the charger which is no different than the Trusted Voice limitations. Second my lock screen is only enabled when I'm not on a charger.
Use the Caffeine app to block the automatic lock screen. Check settings "Autoactive on USB", "Autoactive on USB type/AC charger", "Enable caffeine at boot".
Buy and install the app Screen Off (No Lock). I couldn't find a free app that turned off the screen but did not also lock it.
Then use the Google Assistant command "OK Google open screen off" to invoke turning the screen off but still having Google Assistant listening for my next command. I also use Tasker and it's Voice Assist plugin connection to Google Assistant so added the "start Screen off" as the last task in my Voice Assist profiles.
---------- Post added at 02:26 PM ---------- Previous post was at 01:51 PM ----------
goingonstrong2 said:
Mine worked with no fuss. What doesn't work is the trusted voice and waking the phone up when the screen is off. That one I can't figure out
Click to expand...
Click to collapse
For the most part Google Assistant works for me but important features either lack reliability or don't work at all.
Google Assistant macros don't work at all despite built in GA commands working (e.g. play on Spotify)
I can't seem to make a IFTTT connection work
The connection between GA and Tasker's VoiceAssist is unreliable. Too often GA intercepts a regular Tasker Event phrase and displays a google search screen but the Tasker event for the phrase does not trigger. This despite the Tasker VoiceAssist toast displaying the correct event phrase. I'll try it a second time and this time it'll work despite GA recognizing the exact same phrase (not a variation).
I've been able to create some cool home theater (Harmony Hub) automation profiles but the unreliability has me wondering if I'm wasting my time. I really like the whole Google Assistant and the Tasker extension but am not prepared to continue developing things unless I can increase the overall stability.
It may just be my OP5 which is running OOS 4.5.5, rooted with SuperSU with Viper4Android installed. Other than that I've not altered the stock OOS experience. I've not even removed any bloat ware.
Does anyone have the Google Assistant macros and/or IFTTT working on their OnePlus 5?
I've previously posted that Google Assistant's macros didn't work for me but I received an update to the Google app v7.7.14.21.arm64 (Beta) and Google Assistant's macros are suddenly working. Even macros I'd previous entered but had never worked. I also added new ones and they also worked.
What stopped working was Tasker receiving the OK Google spoken commands, (no VoiceAssist toasts). I need to explore further as the newly functioning macros may be a far better way to integrate with Tasker. I'll likely retry the recommended Google Assistant/IFTTT/Tasker integration which also didn't work prior to this latest update.
It's working perfectly
Just did as it was said on the video. Everything works perfectly, including the "OK Google" detection while the screen is off. No problems whatsoever.
To Note: Even i changed the language back to English(UK) after all was setup, and works like a charm. :good:

Categories

Resources