Related
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 a banking app that works great once Magisk is running, however as soon as I reboot the banking app runs at boot (I assume before Magisk does its hiding) and detects root/magisk and some functions stop working.
I can wipe data and start again and everything is fine until the next reboot, so the hide works, just not fast enough during boot
Is there any way to stop apps booting at start like bootmanger does - https://play.google.com/store/apps/details?id=de.defim.apk.bootmanager&hl=en
I'm running Lineage OS 14.1 so have 7.1.1 so no xposed aptions currently....
You can go to Memory in settings. There is "Apps at boot" or something like that (my phones language isn't set to English, so I don't know the exact name). But there you could prevent apps to start at boot.
Worked perfectly, and managed to clean up a few others as well!
Thanks so much
Pulling my hair on this one; I have rooted the tab successfully, flashed cAndroid 5.01 and it runs great, but won't accept any of the dozen version of Gapps (GPS stop, AOSP keyboard fail, Play Store Hangs, etc.) I have tried, so I thought, let's just try AOSP or cAndroid Nougat, which I have successfully flashed to my Nexus 7 2012 (note re-purpose addiction). Various sideloaded apks work with no issue on the 5.0 ROM, no google apps or services.
I am running CW Mod for flashing and SR5-SuperSU 2.8 for root and the AOSP Rom exits with Status 0, and the cAndroid exits with Status 7, and I am hesitant to edit the install script. Rootcheck show device rooted successfully.
Any help with either would be appreciated, ultimate goal is getting Onenote to run, again, which I have done for both 5.x and 7.x on nexus, using old APKs
Upate your Recovery to the TWRP Version >= 2.8.7.0..
Do you have a link for the twrp build for the gt-p7310, can't find it listed under twrp supported devices
thanks
Searched with every criteria I can come up with, can't find a .zip for GT-P7310 or p5wifi for >2.7
SOLVED
Found right copy of TWRP, installed and now running Nougat on the tab, thanks for the assist
Spoke to soon , update to 7.1.2 goes fine, but no keyboard works none of them will activate when a text field is tapped
You can actives the keyboard under setting, language and inputs , vituelle keyboards
Thanks for the update ; I have the device working properly now with 7.1.2 AOSP thanks to updating my TWRM ; everything works but anything Google or Microsoft - I have tried every version of GApps Zips, APKs GPS back to 10.0.8, Gmail, Play, Gboard, etc. and everytime I introduce anything Google , it flakes out, get service stopped messages from Play Services, Gboard stops, etc. Oddly enough GHandwriting works which i use alot on m other tabs with Onenote, which also won't run, I am assuming b c of GPS; Onenote installs passively, but errors out 8000400 evertime, which seems to be some kind of sign in error, but TS steps I have found have not worked. OTher than the Google and MS snafus, device runs better than ever and i am resolved to using Evernote and exporting over to one note when i need to, any ideas would be appreciated , I like the size of this device and hate to trash anything useful - Thanks for the reply
DESCRIPTION
If you have the Pixel Experience module installed on your phone and installed Google Phone from the Play Store or ever tried to use a patched Google Phone version (such as this one), you may have noticed that Google Phone force closes when you try to search for a contact or while opening the keypad. This Magisk module attempts to fix that and it works by replacing your non-AOSP contacts storage with Google's own version, the one supported by Google Phone.
IMPORTANT NOTES
Supports Android versions from Android 7 (Nougat) to Android P.
It will remove any phone/dialer/contacts/people applications from your phone (if supported) because they are incompatible with Google's Contacts Storage.
You should only install this module if you want/need to use Google Phone and Google Contacts.
TESTED/SUPPORTED DEVICES
HTC 10 (Sense based ROMs).
Note: It should work with other devices but I have no means no test them myself, I can only rely on the community to test this for me.
SPECIAL INSTRUCTIONS
Install the Magisk module as usual but DO NOT reboot your device just yet.
Go into "Settings » Accounts & Sync" and disable "Automatically sync data".
Go into "Settings » Apps" a, look for "Contacts Storage" (it's a system app) and clear application data.
Reboot your device now!
Go into "Settings » Accounts & Sync" and enable "Automatically sync data".
Google Phone should now work without force closing, hopefully.
Note: If you ever want/need to disable this module, you should also follow the procedure above (disable module, disable data synchronization, clear contacts storage data, reboot, and re-enable contacts synchronization).
DISCLAIMER
Install this module at your own risk.
Developer is not responsible for what you do on your device.
Please take all necessary precautions (like a nandroid backup) before installing this module.
DOWNLOADS
Google-Contacts-Storage-v0.0.0-TESTING.4.zip
XDA:DevDB Information
Google Contacts Storage, Tool/Utility for the XDA Community Apps
Contributors
rfgamaral
Version Information
Status: Testing
Current Beta Version: v0.0.0-TESTING.4
Beta Release Date: 2018-08-02
Created 2018-08-01
Last Updated 2018-08-02
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
stathis95194 said:
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
Click to expand...
Click to collapse
I also got that error when developing this module but I never got it after installing/enabling it, only after disabling it.
For some reason, the system does not recognize the /system/priv-app/ContactsProvider/ContactsProvider.apk (although the file is there). I'm not sure how to fix this to be honest, so I recommend you restore your backup to get you back to a working state. Maybe try the whole process again (makre sure you follow every single step) and instead of rebooting the system after installing the module, reboot to recovery and wipe dalvik/ART and cache. If that doesn't help, restore the device again until a solution for this problem is found.
Like I said, I also had this problem and because I live on the edge, I didn't make a backup of my system (idiot me). I had to make the system recognize the ContactsProvider.apk file and wen into recovery, deleted, copied it back from my ROM, set proper folder/file permissions, wiped dalvik/ART and cache and rebooted, the problem was gone. I installed my module again and it worked. But I'm honestly afraid to disable it and get that error back.
Which is weird because I'm replacing this file systemlessly, that's the whole point of Magisk. Maybe I'm doing something wrong, I'm no expert... We'll probably need help from someone with more knowledge on the whole Android system. But for the record, I currently have the version available on this thread installed on my phone. I have the Pixel Experience module installed and installed Google Phone from the store, it doesn't force close and all features seem to be working. I just need to get this module stable.
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
rfgamaral said:
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
Click to expand...
Click to collapse
Yeap I always take a nandroid before messing with the phone. Let me try the new version and report
Sent from my HTC 10 using Tapatalk
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
stathis95194 said:
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
Click to expand...
Click to collapse
Awesome, glad you got it working.
Now I just need to understand why installing this module crashes android.process.acore... But it's a bummer that this is happening, a little price to pay, I guess? At least until a fix is found... That and that whole install procedure which is required to avoid other different crashes because of incompatible storages.
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
gunnerhk said:
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
Click to expand...
Click to collapse
That's really weird, on so many levels... :/
Screenshot as proof :laugh:
Guys I'm in a major fix here. Any help would be appreciated.
K20 Pro Global Version - Currently on MIUI Global 11.0.1.0(QFKMIXM)
Rooted via Magisk
Everything was perfectly fine until I noticed 'microG installer Revived' on Magisk and decided to install it.
After I rebooted, Youtube Vanced wouldn't open stating that it won't run without Google Play Services. Same issue with Gmail as well. I went into the microG settings and accepted all the missing permissions. Added my Gmail account, signed in and accepted all the other permission pop-ups that came after.
Despite this everything is still messed up. Gmail and Youtube still gives the same error msg and Chrome keeps crashing.
I tried uninstalling microG but that was an even bigger mistake as the Google Play Services I installed via apk kept crashing.
If someone could pls guide me on how to get the system to how it was prior to the microG installation :crying:
So I managed to fix it somewhat. Uninstalled microG then installed the right version of Google Play services as well as the calendar and contacts sync apks.
No more crash messages but the issue I'm having now is that some app notifications don't work and others (such as Whatsapp) work only sometimes.
And for some really weird reason my Gmail no longer is (or has the option) in dark mode.
Anyway to fix these issues guys?
I've the same problem with my Huawei Mediapad M5 tablet. I've tried to reflash the original "SYSTEM.img" from fastboot mode, but nothing changed. I don't want to do a full reinstall because of this mistake, is there any solution?
Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine
heynando said:
Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine
Click to expand...
Click to collapse
It's an absolute nightmare, not sure why the devs don't just update the Magisk version, and I agree the Magisk version works perfectly fine
MicroG works only on systems that don't have GAPPS. That should have been included in the documentation.
I had the same problem (I installed the microG installer revived on a cell phone that had google play services, which caused me that error; I installed the magisk module without knowing what it was for), I solved it by doing the following:
1. Uninstall micro-g and google play services and then restart the terminal.
2. Download and Install (install as system application with lucky patcher) the latest version of the google play services apk, restart.
3. Log out or remove google account from device, reboot device.
4. Login or add google account on the device again, restart the device for the last time; and voila problem solved.
I can't remove my account for some reason, and also I can't add a new google account
Hi Guys, have the same problem. has anyone found a solution? would hate to reset it
Trying to work out what it could be for the first post. It sounds like MicroG was installed while the Google Play services were already on the device.
I have actually manually removed Google Services using the debloater magisk module and run it via terminal.
I'm currently using CrDroid Android 12 and it's working fine with MicroG revived version. I have been testing the Android 13 with MicroG and have issues with the Play Store signing in