We all know new google assistant is pretty cool on Pixel devices.Google kept it to Pixel only but various developers helped us to bring it to any device and now it is completely bug free.I have compiled all the steps in one thread to make it working on YU Yureka device(works on any other device too).
So let's start then.
Requirements
1. Obviously rooted android with a custom recovery.
2. Android version 6.0+
That's it.
Features
1.) Pixel Launcher along with new wallpapers app ,new dialer app from google and Pixel ringtones.
2.) Working google assistant.('Ok Google' working too.)
How To Install
( TIP* Before proceeding with installing Zips just clear your google app data to help in the process of enabling assistant successfully)
1.) Download the zip of pixel experience(for your android version) by FaserF as attached here :- https://www.androidfilehost.com/?w=files&flid=122156
2.) Furthur download these 3 zips to make assistant working :- https://www.androidfilehost.com/?w=files&flid=121914
(these will add required build.prop 'ro.opa.eligible_device=true' and 'ro.product.model=Pixel'
+ making a backup of your current build.prop and not touching your original build.prop settings.)
2.) Copy them to your device...all the zips.
3.) First flash GoogleAssistantVelvet.zip .
4.) Then flash GoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop).
5.) Finally flash GooglePixelExperience-flashable-(whatever vesion of android you are on).zip and reboot.
6.) U can now flash additional zips like those of boot animation.
Google assistant may not appear on long tapping home button for a few times but eventually it will appear.
To fix 'ok Google' detection just download the chopAssistant app from play store (here is the link :- credit to @masterchop for making this app ChopAssistant https://play.google.com/store/apps/d...ssistant&hl=en)
That's all...I know its a lot to do but then just let's think about the rewards. :laugh:
Bugs
I have tested this method myself on my Yureka device(CM14.1 unofficial build) and for me everything is totally fine.
Report if u find any.
F.A.Q.
1.) Long tapping home button takes to old google now on tap
Give it about 5 minutes and try again...If still doesn't work then clear google velvet app data,then uninstall the google app completely and download google app beta from play store by registering for a beta tester. Reboot...Assistant will appear now.
2.) Dialer app crashes
Give it all permissions.
3.) Google app crashes
Give it all permissions.
Quick review:-
I want only assistant to be working fully. Do i need to flash both Pixel experience zip??
This module enables Google Assistant on Nougat phones/tablets.
If you have Marshmallow/Nougat device you may no longer need this module after Google rolls out Google Assistant to all eligible devices. Find out more at https://blog.google/products/assistant/google-assistant-coming-to-more-android-phones/
Version 10.0.2 no longer changes phone model/manufacturer and requires Magisk 10 (thanks @candiesdoodle for investigation). Magisk 9 users can download the legacy 10.0.1 version which is the latest version which doesn't use Magisk 10-introduced features and also it still changes the phone model/manufacturer.
Make sure to check the README at GitHub for instructions/requirements/links.
NOW IN OFFICIAL MAGISK REPO!
According to this, you don't need this module if you're using Open Gapps.
I see you made some resetprop changes. Is this all that's required to run Google Assistant?
Does the Xposed module of similar description do the same?
oreo27 said:
I see you made some resetprop changes. Is this all that's required to run Google Assistant?
Does the Xposed module of similar description do the same?
Click to expand...
Click to collapse
Yes it is .
Will this fix the settings in the google app for "okay google" detection? I flashed v1 of the module and now those settings are greyed out/I'm unable to say "Ok google" and activate it from the home screen (or any other screen)
Edit: Flashing v2 didn't fix. I'm going to clear app data and see if that does it
Edit 2: Clearing app data didn't fix it. Any ideas?
nickmilla15 said:
Will this fix the settings in the google app for "okay google" detection? I flashed v1 of the module and now those settings are greyed out/I'm unable to say "Ok google" and activate it from the home screen (or any other screen)
Edit: Flashing v2 didn't fix. I'm going to clear app data and see if that does it
Edit 2: Clearing app data didn't fix it. Any ideas?
Click to expand...
Click to collapse
When you try to enable it does it enable for about a half second and then disable? If so, enable it and then quickly tap delete voice model. After that you should be able to enable it properly.
loserskater said:
When you try to enable it does it enable for about a half second and then disable? If so, enable it and then quickly tap delete voice model. After that you should be able to enable it properly.
Click to expand...
Click to collapse
No, it just won't enable at all. Completely grayed out on my HTC 10 running Nougat :/
Only issue I have noticed with this.. When enabled, HDR+ mode is no longer available on nexus 6p. Disable this mod and HDR+ shows up again. Any way around it?
mpgrimes said:
Only issue I have noticed with this.. When enabled, HDR+ mode is no longer available on nexus 6p. Disable this mod and HDR+ shows up again. Any way around it?
Click to expand...
Click to collapse
I've getting this as well
nickmilla15 said:
Will this fix the settings in the google app for "okay google" detection? I flashed v1 of the module and now those settings are greyed out/I'm unable to say "Ok google" and activate it from the home screen (or any other screen)
Edit: Flashing v2 didn't fix. I'm going to clear app data and see if that does it
Edit 2: Clearing app data didn't fix it. Any ideas?
Click to expand...
Click to collapse
Try these steps:
1. Disable the module
2. Reboot
3. In the Google Now setup voice model/OK Google from any screen
4. Enable the module
5. Reboot to recovery
6. In recovery, wipe cache and dalvik/cache
7. Reboot
8. You should have google assistant working.
mpgrimes said:
Only issue I have noticed with this.. When enabled, HDR+ mode is no longer available on nexus 6p. Disable this mod and HDR+ shows up again. Any way around it?
Click to expand...
Click to collapse
No clue, I'm guessing HDR+ probably depends on specific prop which my module overrides in order to enable Assistant.
Still in trouble.... Cannot format Dalvik cache as twrp for the model does not support f2fs data partition. But resetprop succeed and shows Pixel XL in status. Any ideas?
Well....It turns out to be a delay. After I woke the phone with "Ok, Google" twice, the assistant appears.
stangri said:
Try these steps:
1. Disable the module
2. Reboot
3. In the Google Now setup voice model/OK Google from any screen
4. Enable the module
5. Reboot to recovery
6. In recovery, wipe cache and dalvik/cache
7. Reboot
8. You should have google assistant working.
Click to expand...
Click to collapse
Not working for me on viper10 4.4 full ROM. Only seems to make a delay in OK Google detection. Otherwise, no assistant.
acupunk said:
Not working for me on viper10 4.4 full ROM. Only seems to make a delay in OK Google detection. Otherwise, no assistant.
Click to expand...
Click to collapse
4.4 as in KitKat?
Confirm version of magisk.
Check the "model number" in phone status.
stangri said:
4.4 as in KitKat?
Confirm version of magisk.
Check the "model number" in phone status.
Click to expand...
Click to collapse
No kit kat for awhile. ? Viper10 is a nougat 7.0 rom on the htc-10. I'm using magisk v10 12/29/16 build. All of my other modules are working.
Thanks for the mod. I have 10.0.1 installed and have followed the directions to enable the assistant. While the assistant has been enabled, every time I activate it with "OK Google" the assistant setup comes up and asks me to train my voice and what not. This does not happen when enabling the assistant by long-pressing the home button, in which case the assistant activates normally without the prompt to set it up. I am on the Oneplus 3T running OxygenOS 4.0.0 and Google app v6.9.36.21.arm64.
yaoming123 said:
Thanks for the mod. I have 10.0.1 installed and have followed the directions to enable the assistant. While the assistant has been enabled, every time I activate it with "OK Google" the assistant setup comes up and asks me to train my voice and what not. This does not happen when enabling the assistant by long-pressing the home button, in which case the assistant activates normally without the prompt to set it up. I am on the Oneplus 3T running OxygenOS 4.0.0 and Google app v6.9.36.21.arm64.
Click to expand...
Click to collapse
You didn't delete Google Now's cache/clear its storage instead of clearing cache/dalvik/art from recovery by any chance? Did you train the voice model before installing the module?
I've had it happen to me once, the solution was to disable the module, reboot, train the voice model in Google now, enable module, reboot to recovery, clear cache/dalvik/art and then boot up. As far as I remember it's a hit or miss process. As others reported you may want to wait a bit after the phone boots up after final step before invoking Assistant.
stangri said:
You didn't delete Google Now's cache/clear its storage instead of clearing cache/dalvik/art from recovery by any chance? Did you train the voice model before installing the module?
I've had it happen to me once, the solution was to disable the module, reboot, train the voice model in Google now, enable module, reboot to recovery, clear cache/dalvik/art and then boot up. As far as I remember it's a hit or miss process. As others reported you may want to wait a bit after the phone boots up after final step before invoking Assistant.
Click to expand...
Click to collapse
I actually did both, cleared the Google app cache before following the instructions to wipe the Dalvik/ART and cache in recovery. I cleared the app cache due to having to do this in a different incarnation of the assistant installer on a different device.
stangri said:
Try these steps:
1. Disable the module
2. Reboot
3. In the Google Now setup voice model/OK Google from any screen
4. Enable the module
5. Reboot to recovery
6. In recovery, wipe cache and dalvik/cache
7. Reboot
8. You should have google assistant working.
Click to expand...
Click to collapse
These steps worked for me on HTC 10 LeeDrOiD.
Step 3 was the key I was missing. I couldn't register my voice and that was because I hadn't enabled "OK Google from any screen".
Also after I launched Google app I waited a little to see Google Assistance prompt.
Unfortunately not working on OP3. Tries everything listed here.
"Google Now" doesn't support in my country.
I tried to install google assistant by enabling ok google detection (as per OP) but it didn't work.
Magisk 10.2 installed and rooted properly.
Device: OP3, Android version: 7.0
Is there any idea?
So apparently with the latest Google app update I no longer need the app to bypass the voice training popup on either of my devices.
Hi, i have problem using AOSP N [7.1],
im unable to access menu options for some apps using menu hardware key,
usually menu options can be accessed with tapping or hold down the menu hardware key.
i already set the button settings for the hardware key actions, but its not work.
with using software enabled option i still can get access to the menu options (there will be extra button on software keys),
but i dont like that software because my screen is getting smaller.
Pls help me with this problem..ty...
PS: im using ROM AOSP N [7.1] December patch with all the fix patch installed, but without google pixel patch, because i got stuck in "setting up android" screen.
U can install gravity box and in that u can reassign the hardware keys but u device needs to support Xposed installer I think so, when I am using 6.0.1 ghost ROM it supports the Xposed installer but I don't know whether aosp supports the Xposed or not
Mohan Sai said:
U can install gravity box and in that u can reassign the hardware keys but u device needs to support Xposed installer I think so, when I am using 6.0.1 ghost ROM it supports the Xposed installer but I don't know whether aosp supports the Xposed or not
Click to expand...
Click to collapse
Lol. There is no Xposed for nougat yet.
Then there is another way in playstore we have app named keymapper which is enough to reassign any apps or actions to our hardware keys
Hi all this is just an information. Today I'm going to present you Samsung's Bixby for J7 series which running on Nougaut in Samsung Based Custom ROM or Official ROM.
This is a simple step procedure.:fingers-crossed:
(Sorry I didn't tested on MM and LP, you can test if your device is MM/LP, because this won't do any harm to your device)
INSTALLATION PROCEDURE
1. Install these 3 as normal APKs.(Link in Download section)
(DON'T WORRY YOU CAN'T DIRECTLY OPEN IT FOR NOW)
2. Install Shortcutmaker app from Playstore
(Link is in Download section)
3. Open it and tap on Bixby Home app>Bixby Home option.
(PFA down)
4. Tap on try option.
5. Then allow all the permissions that it needs.
6. After that just restart your phone, and voila.
7. Just swipe left from Homescreen. You're done.
DOWNLOADS
1. Bixby APKs.
https://drive.google.com/file/d/1g2rZbtyGnESFV4lpf7XHB9roLjrErDKk/view?usp=drivesdk
2. Shortcutmaker App.
https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut
Very big thanks to me for sharing this to you.
I hope this is helpful and clear to you. If you have any confusion regarding installation please write down in comments section. Please don't tag the whole post. Just comment that's enough.
I m using bixby, not doing anything with shortcut makers or others, when i swipe left in homescreen it will open
sourav143 said:
I m using bixby, not doing anything with shortcut makers or others, when i swipe left in homescreen it will open
Click to expand...
Click to collapse
Ok fine. It will also work. I just did it in another way. That's it.
my device strucked in boot loop after installing bixby on genisys custom rom
pruthvi.g.gtl said:
my device strucked in boot loop after installing bixby on genisys custom rom
Click to expand...
Click to collapse
How the hell brother. Since you are not playing with system files. It just apps.
no Bixby Voice?
Can't Launch Bixby, it won't update, so it quits.
How to turn on the voice?
The link for at least the bixby apks are broken.
I just installed magisk through the magisk manager app and it went just fine, but now when I've rebooted my home and menu buttons aren't working. I get the vibration response but no action. the menu key does bring up manus in apps but it doesn't do what it did before installing Magisk... Can I reset the buttons functionality somehow? I'm running LineageOS 14.1 on a Redmi Note 4. Please help!
his is an Android issue.
Step instructions:
- Download Nova Launcher. If you cannot from the google play store, search for it on Chrome and download an apk version
- Install it (you may get a pop up advising you need to let apps installed from chrome, go to settings and allow it)
- Once installed, click on Open. This should launch the Nova Launcher
- Long press anywhere on the screen
- Choose Widgets.
- Look for the Activities widget and hold and place it anywhere on the screen.
- Scroll down to Setup Wizard. There's two, one that's "Setup Wizard" and the other "SetupWizard" without a space. Choose the first. There should be an option under it called ".SetupWizardUpgradeActivity". It might be slightly different for you pending the version OS you have but that's what came up for me.
- Select that to create the widget shortcut then click to open.
- This will bring you to the setup wizard and then just click Next all the way through (turn off any preferences you may have in the past)
You can uninstall Nova Launcher afterwards if you want. You don't need to set it as default.
Can I use this for a noname android car head unit? What is the
custom recovery that I could use?