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.
Related
This is my first post on xda. Sorry if I make mistakes
For people who have failed with N-ify and changing build.prop methods
For Cyanogenmod 13 users
Required stuff
Latest version of the google beta app
Xposed module
ok so here's how you do it
Install the google beta app
Install the Xposed module named Assistant Enabler
Activate and reboot
You'll notice that long pressing the home button will do nothing ,so
Go to settings>apps and tap on the 3 dots drop down list
Tap on advanced then go to default apps
Tap on Assist & voice input and then Assist app and select Google app there
If its already there dont worry, tap on it and select Google app again
Long press the home button and the google assistant should popup
Now for the stock marshmallow users
Install the latest version of google app beta
Install the Xposed module named Assistant enabler, activate and reboot
Thats it. You're done. Long press for the assistant to popup
That's it , Thanks.
http://forum.xda-developers.com/cro...utorial-google-assistant-marshmallow-t3480120
Google Pay has stopped working over a week ago and i was hoping for a fix but nothing has come? Did I do something wrong?
Running Android 6.1.6 Magisk Manager
Edit
There is also a bug with the manager? When i select apps for Magisk Hide it doesn't save and when i reload the list all that apps are unticked again??
Thanks in advance
Logs?
Didgeridoohan said:
Logs?
Click to expand...
Click to collapse
Magisk doesn't show any logs, where do I go to turn on Android logging?
JoshuaM765 said:
Magisk doesn't show any logs, where do I go to turn on Android logging?
Click to expand...
Click to collapse
There's your problem...
MagiskHide uses Android logging to detect when it needs to hide from an app or process.
Have you disabled logd? Used something like Kernel Adiutor to disable logs? Etc... Turn it back on and things will start working again.
[HIDE[/HIDE]
Didgeridoohan said:
There's your problem...
MagiskHide uses Android logging to detect when it needs to hide from an app or process.
Have you disabled log's? Used something like Kernel Adiutor to disable logs? Etc... Turn it back on and things will start working again.
Click to expand...
Click to collapse
I don't ever remember disabling logs or using a kernel adiutor. Would I need to edit to turn it on and how would I go about doing this?
Just to confirm, run this in a terminal emulator:
Code:
su -c magiskhide --enable
If it reports that logs are disabled, we can keep on this track.
The question is what happened "over a week ago" that caused things to change. Did you by any chance update Magisk? From v15.4 there was a change that for some devices wrongly disables MagiskHide because it can't detect that Android logging is running. That's been fixed and should be in the next release. You could try the unofficial snapshots by @kantjer, if you're impatient... Just be aware that they might not be built from release ready code.
Didgeridoohan said:
Just to confirm, run this in a terminal emulator:
Code:
su -c magiskhide --enable
If it reports that logs are disabled, we can keep on this track.
The question is what happened "over a week ago" that caused things to change. Did you by any chance update Magisk? From v15.4 there was a change that for some devices wrongly disables MagiskHide because it can't detect that Android logging is running. That's been fixed and should be in the next release. You could try the unofficial snapshots by @kantjer, if you're impatient... Just be aware that they might not be built from release ready code.
Click to expand...
Click to collapse
It was working then I got Xposed for Magisk but that put it in a boot loop so i factory reset and rerooted with Magisk and its now stopped working. When I do the terminal emulator i get "Logb is not running, cannot run logcat"
JoshuaM765 said:
It was working then I got Xposed for Magisk but that put it in a boot loop so i factory reset and rerooted with Magisk and its now stopped working. When I do the terminal emulator i get "Logb is not running, cannot run logcat"
Click to expand...
Click to collapse
Is logcat running? You can test this by using an app like Matlog. If it shows the log, it is a matter of the Magisk v15.4+ bug of detecting logging fully. Solution in that case would be to wait for the next release, test an unofficial snapshot linked above, or revert to a Magisk version prior to v15.4.
Didgeridoohan said:
Is logcat running? You can test this by using an app like Matlog. If it shows the log, it is a matter of the Magisk v15.4+ bug of detecting logging fully. Solution in that case would be to wait for the next release, test an unofficial snapshot linked above, or revert to a Magisk version prior to v15.4.
Click to expand...
Click to collapse
Yes Matlog works, where would i get an unoffical snapshot from?
JoshuaM765 said:
Yes Matlog works, where would i get an unoffical snapshot from?
Click to expand...
Click to collapse
I linked it a few posts ago...
Oh, sorry missed those.
Thanks for all the help, i will report back if it works.
Thanks so much, it was solved using the custom Magisk update link that you posted, Thanks again
JoshuaM765 said:
Thanks so much, it was solved using the custom Magisk update link that you posted, Thanks again
Click to expand...
Click to collapse
Thank you. That's the first confirmation I've seen of anyone with this issue having things working with the current code. That means the fix works...
Next official release (likely a beta) will have the fix included.
I'm also having trouble getting Google pay to work. The app also automatically gets disabled by my phone, and i have to search for it in the play store to re enable it. Magiskhide is enabled. Might it be because I'm in Mexico right now?
basily said:
I'm also having trouble getting Google pay to work. The app also automatically gets disabled by my phone, and i have to search for it in the play store to re enable it. Magiskhide is enabled. Might it be because I'm in Mexico right now?
Click to expand...
Click to collapse
Kindly Do The Following
- Clear Data&Cache Of Google Pay
- Disable Telephone Permission Of Google Play Services
- Try To Use Google Pay
Dreamer(3MF) said:
Kindly Do The Following
- Clear Data&Cache Of Google Pay
- Disable Telephone Permission Of Google Play Services
- Try To Use Google Pay
Click to expand...
Click to collapse
Thanks for the advice, but i tried it and same result.
basily said:
Thanks for the advice, but i tried it and same result.
Click to expand...
Click to collapse
Send The Full Logcat Of Google Pay & Inform Me About The Installed Version Of Magisk.
Didgeridoohan said:
Just to confirm, run this in a terminal emulator:
Code:
su -c magiskhide --enable
If it reports that logs are disabled, we can keep on this track.
The question is what happened "over a week ago" that caused things to change. Did you by any chance update Magisk? From v15.4 there was a change that for some devices wrongly disables MagiskHide because it can't detect that Android logging is running. That's been fixed and should be in the next release. You could try the unofficial snapshots by @kantjer, if you're impatient... Just be aware that they might not be built from release ready code.
Click to expand...
Click to collapse
I have the same issue as my Google Pay doesn't work now (after 16.3). Now I am on magisk 16.4.
I tried this Terminal command, su -c magiskhide --enable which returns that hide is already enabled.
My Google Pay was working normal now not working. By the way, SafetyNet test pass through.
smohanv said:
I have the same issue as my Google Pay doesn't work now (after 16.3). Now I am on magisk 16.4.
I tried this Terminal command, su -c magiskhide --enable which returns that hide is already enabled.
My Google Pay was working normal now not working. By the way, SafetyNet test pass through.
Click to expand...
Click to collapse
If you have MagiskHide working (passing SafetyNet), there's no need to mess with the enable command. That was just to confirm if the user has an issue where Magisk couldn't detect if logging was running (that's been fixed in v16.4).
Does Google Pay still work on Magisk v16.0? Or is it a matter of an update to Google Pay? What happens if you disable Telephone permissions for Google Play Services (like users of the Tez app have to do)? Or If you add all phone services you the Hide list?
Dreamer(3MF) said:
Send The Full Logcat Of Google Pay & Inform Me About The Installed Version Of Magisk.
Click to expand...
Click to collapse
Ok, I'm trying to get a logcat using terminal, but it keeps coming out at over 1mb, and xda won't let me attach a text file over 512kb. Shall i get it with adb with some filtering? I'm not very familiar with logcats, so your suggestion would be welcome.
I'm on the latest stable magisk: v16.0. For safetynet check, it successes, but ctsProfile, and basicIntegrity false.
I'm on a Nexus 6P, fully updated.
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:
I'm using galaxy s6 stock 7.0 g920tuvs6frc1 with magisk 17.1 3.2.2 twrp ,no other root apps busybox uninstalled I've renamed a few files in my root directory that had magisk and haven't found any more. Passing safety net but it still won't let me play. Please help.
Pokémon go use detection of file now you can't bypass just with safetynet
thekiller8967 said:
I'm using galaxy s6 stock 7.0 g920tuvs6frc1 with magisk 17.1 3.2.2 twrp ,no other root apps busybox uninstalled I've renamed a few files in my root directory that had magisk and haven't found any more. Passing safety net but it still won't let me play. Please help.
Click to expand...
Click to collapse
You need to hide the magisk manager app
Clear the repo then
Settings - hide magisk manager with random package name
Tick pokemon go in magisk hide
Force close pokemon go if you previously ran it then start it again
Works perfectly fine for me plus I've got fake GPS joystick systemlessly installed too
TheFixItMan said:
You need to hide the magisk manager app
Clear the repo then
Settings - hide magisk manager with random package name
Tick pokemon go in magisk hide
Force close pokemon go if you previously ran it then start it again
Works perfectly fine for me plus I've got fake GPS joystick systemlessly installed too
Click to expand...
Click to collapse
do you hide magisk before ticking the pokemon app ? i mean before you tick it in magisk.
And are you using expert mode on your gps app ? i tried earliere but i couldnt get gps signal
mikimouse666 said:
do you hide magisk before ticking the pokemon app ? i mean before you tick it in magisk.
And are you using expert mode on your gps app ? i tried earliere but i couldnt get gps signal
Click to expand...
Click to collapse
Doesn't matter when it's ticked as long as it is
Expert mode for GPS - installed systemlessly to priv app with systemizer module
TheFixItMan said:
Doesn't matter when it's ticked as long as it is
Expert mode for GPS - installed systemlessly to priv app with systemizer module
Click to expand...
Click to collapse
okey thanks, ill try now and hope i can log in/dont get gps failuer.
im getting rubberbanding
mikimouse666 said:
okey thanks, ill try now and hope i can log in/dont get gps failuer.
im getting rubberbanding
Click to expand...
Click to collapse
Set the update frequency/interval to 1
TheFixItMan said:
Set the frequency/interval to 1
Click to expand...
Click to collapse
same results, my app is fakegps route and joystick (paid app) maybe i need some other google play version perhaps ?
edit: it works now after i installed another google play version + 1sec update interval, thanks alot "TheFixItMan"
mikimouse666 said:
same results, my app is fakegps route and joystick (paid app) maybe i need some other google play version perhaps ?
Click to expand...
Click to collapse
There's also disable GPS service framework or something like that - can't remember the exact wording
That should be disabled (ticked) whilst using the app
Other than that it's a matter of playing around with the settings - long as you have a decent device it should be able to handle it
Works OK on my galaxy g5 running lineageos 15.1 - its not perfect but usable
TheFixItMan said:
You need to hide the magisk manager app
Clear the repo then
Settings - hide magisk manager with random package name
Tick pokemon go in magisk hide
Force close pokemon go if you previously ran it then start it again
Works perfectly fine for me plus I've got fake GPS joystick systemlessly installed too
Click to expand...
Click to collapse
Great ! Work fine thx
Do you have "How to" for fake gps joystick systemlessly ?
MrOops said:
Great ! Work fine thx
Do you have "How to" for fake gps joystick systemlessly ?
Click to expand...
Click to collapse
Use app systemizer module to set gps joystick systemlessly in priv-app
Run gps joystick in expert mode with interval set to 1
You might need to disable location service too (top option in the GPS joystick settings)
TheFixItMan said:
Use app systemizer module to set gps joystick systemlessly in priv-app
Run gps joystick in expert mode with interval set to 1
You might need to disable location service too (top option in the GPS joystick settings)
Click to expand...
Click to collapse
Welll.... Gps joystick systemlessly is a module ( i see 3 gps modules with gps tag in magisk) or is a Google play store app ? What to choose ?
MrOops said:
Welll.... Gps joystick systemlessly is a module ( i see 3 gps modules with gps tag in magisk) or is a Google play store app ? What to choose ?
Click to expand...
Click to collapse
I'm referring to this paid app
https://play.google.com/store/apps/details?id=com.incorporateapps.fakegps_route
Install normally then use app systemizer module to convert to systemless priv-app
Thx I tried several applications and I jump. Do you know why ?
MrOops said:
Thx I tried several applications and I jump. Do you know why ?
Click to expand...
Click to collapse
Did you manage to fix the issue?
Lately after flashing a custom rom on my Samsung Note 5, I realized the latest PoGo version is attempting to read background services.
This is what I did to bypass all that and have a stable spoofing experience.
1. Install magisk 17.1 from beta channel
2. Download app systemizer terminal module from magisk
3. Download appninja's GPS joystick from playstore
4. Generate a new app from joystick and remove the original app
5. Use terminal emulator to systemize your generate joystick app (priv-app)
6. Restart and launch your joystick app. Go into settings and disable location service. Other settings are useful depending on which environment you're running on. Keep AGPS off as it will consume lots of data (bandwidth)
7. Test spoof with Google maps or any map app
8. Install Pogo
9. Use magiskhide to hide Pogo
10. After realizing that the latest PoGo version is scanning for background services, I had to stop magisk manager from the cached running services (can be done from developer options > Running services if you ever launched magisk manager before running Pogo). The latest magisk version will not generate a magiskmanager folder in your phone storage anymore to bypass Pogo's file scan
11. Finally I can launch GPS joystick (generate version), launch Pogo and spoof peacefully without any rubberbanding
12. If you want to use apps like Waze or Google maps for real life navigation, you'll have to turn off 'disable location service' from GPS joystick.
Good luck!
paperheart said:
Did you manage to fix the issue?
Lately after flashing a custom rom on my Samsung Note 5, I realized the latest PoGo version is attempting to read background services.
This is what I did to bypass all that and have a stable spoofing experience.
1. Install magisk 17.1 from beta channel
2. Download app systemizer terminal module from magisk
3. Download appninja's GPS joystick from playstore
4. Generate a new app from joystick and remove the original app
5. Use terminal emulator to systemize your generate joystick app (priv-app)
6. Restart and launch your joystick app. Go into settings and disable location service. Other settings are useful depending on which environment you're running on. Keep AGPS off as it will consume lots of data (bandwidth)
7. Test spoof with Google maps or any map app
8. Install Pogo
9. Use magiskhide to hide Pogo
10. After realizing that the latest PoGo version is scanning for background services, I had to stop magisk manager from the cached running services (can be done from developer options > Running services if you ever launched magisk manager before running Pogo). The latest magisk version will not generate a magiskmanager folder in your phone storage anymore to bypass Pogo's file scan
11. Finally I can launch GPS joystick (generate version), launch Pogo and spoof peacefully without any rubberbanding
12. If you want to use apps like Waze or Google maps for real life navigation, you'll have to turn off 'disable location service' from GPS joystick.
Good luck!
Click to expand...
Click to collapse
thanks, this helped. one thing though, I had to hide magisk manager itself in the settings, then I was able to play pokemon go
Did anyone encounter Magisk Hide "suddenly" not working? I met it twice these days after playing PokeMonGo for 10+ hrs, the "incompatible OS" screen popped up (which means PokemonGo detected root).
Magisk 16.7 or 17.2
MagiskManager 6.0.0.
Google service 14.3.66 (it seems to be able to detect root as well. Safetynet randomly not working)
I don't know how to fix it so I simply restore an old working TWRP backup image.
Does anyone here have the problem that when he hides Magisk he cant acess the app anymore? It stucks at the logo forever!
paperheart said:
Did you manage to fix the issue?
Lately after flashing a custom rom on my Samsung Note 5, I realized the latest PoGo version is attempting to read background services.
This is what I did to bypass all that and have a stable spoofing experience.
1. Install magisk 17.1 from beta channel
2. Download app systemizer terminal module from magisk
3. Download appninja's GPS joystick from playstore
4. Generate a new app from joystick and remove the original app
5. Use terminal emulator to systemize your generate joystick app (priv-app)
6. Restart and launch your joystick app. Go into settings and disable location service. Other settings are useful depending on which environment you're running on. Keep AGPS off as it will consume lots of data (bandwidth)
7. Test spoof with Google maps or any map app
8. Install Pogo
9. Use magiskhide to hide Pogo
10. After realizing that the latest PoGo version is scanning for background services, I had to stop magisk manager from the cached running services (can be done from developer options > Running services if you ever launched magisk manager before running Pogo). The latest magisk version will not generate a magiskmanager folder in your phone storage anymore to bypass Pogo's file scan
11. Finally I can launch GPS joystick (generate version), launch Pogo and spoof peacefully without any rubberbanding
12. If you want to use apps like Waze or Google maps for real life navigation, you'll have to turn off 'disable location service' from GPS joystick.
Good luck!
Click to expand...
Click to collapse
Thanks! this method works perfectly.
Hirs_E_Fruit said:
Does anyone here have the problem that when he hides Magisk he cant acess the app anymore? It stucks at the logo forever!
Click to expand...
Click to collapse
Yes, I have the same problem. Very annoying! It works fine after hiding, but after a reboot the hidden magisk manager can't find root and freezes. After the reboot I have 2 magisk managers installed, the original is back again. It lost it's settings and I have to update it again. I remove the not working one, update and hide the new one that appeared after reboot, and it is all working again until the next reboot.
2 question:
does actually by rooting Pixel 5 will make loose Google Pay functionality ?
does Bank apps will be affected from root here ?
Whitch methods to 100% make working things above ?
Hi!
For 1) use safetynet fix - https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
For 2) use magisk hide feature
This is how it works for me without any issues
somin.n said:
Hi!
For 1) use safetynet fix - https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
For 2) use magisk hide feature
This is how it works for me without any issues
Click to expand...
Click to collapse
can you tell me:
how to force an app in Full Screen ? I can't see any option to make this job.
the best app here to make camera ring notifications ?
Just an fyi, some apps can still detect root. I have root via magisk, safety net fix, magisk hide for apps needing it with safety net passing but Chase app, while it runs, certain features such as points, redemption etc fail with the message about root or malware devices.
wolfgart said:
can you tell me:
how to force an app in Full Screen ? I can't see any option to make this job.
the best app here to make camera ring notifications ?
Click to expand...
Click to collapse
Are you talking about the black bar that covers the camera hole in landscape mode? There's a new magisk module that fixes that.
Download the module.zip from here: https://github.com/logmd/N3O-No-Nonsense-Notch-Overlay/releases
Flash that with Magisk Manager and reboot.
Go to settings > system > developer options > scroll down to display cutout > select the Pixel 5 option
That's it, no more black bar
wolfgart said:
2 question:
does actually by rooting Pixel 5 will make loose Google Pay functionality ?
does Bank apps will be affected from root here ?
Whitch methods to 100% make working things above ?
Click to expand...
Click to collapse
I was shocked this worked so easily, but if yiu go into the terminal just issue this command:
Code:
chmod 440 /data/data/com.google.android.gms/databases/dg.db
```
For me Google pay immediately started working, don't really remember where I found this tip somewhere googling...lol so credit to unknown.
I've been successfully able to use GPay and other security/DRM sensitive apps with the folllowing:
Magisk 23001 with MagiskHide and Universal SafetyNet Fix 2.1.1
Magisk 23014 with DenyList and Universal SafetyNet Fix 2.2.0
Use MagiskHide/DenyList on all components of Google Play Services (com.google.android.gms) and Google Play Store (com.android.vending), as well as GPay, banking apps, and DRM sensitive apps such as Netflix, Hulu, Prime Video, etc.