Database Develop

Using google phone, how to hide Dialler?

Hey all,
I've installed a version of the google phone app via apkmirror and it works. But I want to hide the dialler app!
I am using Oreo 8.0.0.362 and tried to freeze dialler with titanium backup, and although it says it is Frozen I still see the icon and it still works.
Can I uninstall dialler? Is there a solution to getting rid of it?
And! What latest apk of google phone can we use? I've got a v14 nonnexus atm.

Never mind! Apparently unfreezing and freezing again made it go away!
I do wonder what Google phone app we can use!

If you have Magisk 15.4 installed on Oreo (EMUI 8) then you can install my module (attached). It's based on @P1N2O module (https://github.com/Magisk-Modules-Repo/google-framework-magisk) I've only updated version and files inside which are taken from GApps for Android 8.0 ARM64 2018-02-17.
After that you're able to install Google Dialer straight from Play Store You can set it as default dialer and it works almost perfectly - from time to time Mate9 show system InCall UI for incoming calls instead of google's. I don't know really why, I have no time to check it.

rufik said:
If you have Magisk 15.4 installed on Oreo (EMUI 8) then you can install my module (attached). It's based on @P1N2O module (https://github.com/Magisk-Modules-Repo/google-framework-magisk) I've only updated version and files inside which are taken from GApps for Android 8.0 ARM64 2018-02-17.
After that you're able to install Google Dialer straight from Play Store You can set it as default dialer and it works almost perfectly - from time to time Mate9 show system InCall UI for incoming calls instead of google's. I don't know really why, I have no time to check it.
Click to expand...
Click to collapse
Cool! I had 15.4 installed and tried to add your module. And although it says it succeeded, I cant find phone in the app store. Check-in magisk I Saw that I'm at v16 now.
Can I reflash the 15.4 in twrp and try again?

Ok this is strange. I used the magisk uninstaller, and then reinstalled a 15.4 version for mate 9, which ante0 sent me.
Installed the manager and magisk says I have 15.4
Cant install your module though. It says data/magisk is not set up properly and that I should install magisk v14.0+!
EDIT: uninstalled magisk, installed it again and tried the module. Same error. Tried it again, and it worked! Nice! So, if at first you dont..

After flashing module you can try to clear data of Google Play Store and reboot.
If you encounter errors after flashing magisk just try to dirty flash it again. I think this module should work with magisk 16 if module template hasn't changed.

Magisk Manager Has Stopped. (Crashing on open)

Phone: LG Aristo (LGMS210)
ROM / Android version: Android 7.0
Root (yes/no): Yes
Xposed, or any other modifications: no
Any physical damage prior to defect: no
Magisk Manager keeps stopping. I opened it today and I got the message "Magisk Manager has stopped, open app again" I can't open it without it crashing. I've tried clearing cache, clearing data, reinstalling the APK. What do I do? This is a very big problem as i cannot run any rooted apps without getting the message that magisk has stopped.

Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?

Have you tried uninstalling Magisk and then reinstalling?[/QUOTE]
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.

MMJv3 said:
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.
Click to expand...
Click to collapse
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?

I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,

dafreaking said:
I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,
Click to expand...
Click to collapse
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.

Clear Repo Cache
Disconnect from internet, go to settings and clear the repo cache helped me to open it again

Didgeridoohan said:
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?
Click to expand...
Click to collapse
I am facing the same issue. Magisk Manager crashes as soon as I open it (precisely within 3-5 sec of opening the app). Though the root is working perfectly and all apps requiring root behave as intended.
I am attaching a magisk log taken from the magisk manager within the 3-5 seconds window.
Kindly let me know if it's the correct log. I am a noob and still learning the intricacies.
Any help/guidance will be greatly appreciated

Magisk Manager works for me when I wait for a few seconds after opening the app. Cool Tool shows high CPU activity right after starting MM. Once the CPU idles again, MM works without crashing.
This is not a fix, but it may help until a new version gets released.

Didgeridoohan said:
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.
Click to expand...
Click to collapse
v5.8.0 just released does fix this.

Didgeridoohan said:
Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?
Click to expand...
Click to collapse
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader

zfk110 said:
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader
Click to expand...
Click to collapse
I encounter the same issue today !!

eric672913 said:
I encounter the same issue today !!
Click to expand...
Click to collapse
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5

zfk110 said:
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5
Click to expand...
Click to collapse
Great! Thanks a lot.

For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.

JoostA said:
For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.
Click to expand...
Click to collapse
Thanks for this! Was exactly my problem.

Phone: Sony Xperia Z3 Compact (D5803)
ROM / Android version: Android 7.1.2 (LineageOS)
Root (yes/no): Yes
Xposed, or any other modifications: AFwall+ 3.0.4 (IPv6 disabled)
Any physical damage prior to defect: no
After flashing new LineageOS + Magisk.zip and installing the Magisk Manager Apk, the app is also crashing with no internet connection for me. But if I make airplane mode on, then it does work for me.

Magisk not opening or crashing again and again.
First of all desable or uninstall your superuser app and then open magisk manager app again it's very simple. When you done all of magisk installation then you can again activate or install your superuser app.
If it is not working then please tell me i can help you.

Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?

Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing SOLVED
jhavron said:
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?
Click to expand...
Click to collapse
Updated Magisk Manager and was able to download the updated apk using the manager. I then rebooted to recovery and installed the new APK, cleared delvik, & cache, rebooted. Bam! SOLVED

Xiaomi Mi8 Play Market Error 192

Finally unlocked bootloader and installed HavocOS to my Xiaomi with all needed wipes: data, system, cache. However, I've faced an issue with Play Market downloads. When I try to download a large app it goes up to 100% and then starts over, stops at 2% and awaits for wi-fi connection ( though I am connected over Wi-Fi). It is the same for all apps over 1Gb in size (e.g. PUBG, Asphalt 9 and so on). Also tried to clear cache and data for Play Market, Google Play Services and no good too.
I've tried to reinstall ROM, gapps, tried Xiaomi EU Rom (stable) and got the same error there. I guess it has something to do with security, so I've tried different google account - but result was the same.
Please suggest any resolution

Just bought this phone myself. But this my guess based on my experience with other devices.
I suspect that your play store status is uncertified?
I am sure it is!
You need to fix that first, then play store function should return to normal.
The easiest way to resolve this issue without reinstallation to use the Magisk Module : Magiskhide Props Config
Next go to the main page for that module and read the instructions ( Google it)
Note, you must also install Termus and enter commands per instructions on Op page for the module. Trust me it's easy.
Essentially you are changing the fingerprints to a Play Store certified device (It only works as long as the module and Magisk stays installed)
I have attached screenshots from my other phone, where I had the same issue and resolved it.
Sent from my Xiaomi MI 8 using XDA Labs

[Question] YT Vanced shown you are offline message

I installed YT Vanced with microG on Xiaomi K20 Pro (xiaomi.eu Rom) via vanced manager.
It worked for a day then it always shows you are offline message.
Uninstalled them then reinstalled them.
Worked for a few hours then offline message returned.
Donnow what's the problem.
Any suggestions to solve this issue?

NaAZoOR said:
I installed YT Vanced with microG on Xiaomi K20 Pro (xiaomi.eu Rom) via vanced manager.
It worked for a day then it always shows you are offline message.
Uninstalled them then reinstalled them.
Worked for a few hours then offline message returned.
Donnow what's the problem.
Any suggestions to solve this issue?
Click to expand...
Click to collapse
Did you search on XDA for the dedicated Vanced YT thread (not related to any particular phone). AFAIK, people reported various problems with microG (things may highly depend on the ROMs).
Probably MIUI breaks the MicroG connection (you may try to disable Battery Optimization for MicroG, not sure would it help)
Btw, you can easily install Magisk and then the root Vanced YT
Mi 9T (not Pro) on my side, Xiaomi eu Stable, using the root Vanced YT with no issues

zgfg said:
Did you search on XDA for the dedicated Vanced YT thread (not related to any particular phone). AFAIK, people reported various problems with microG (things may highly depend on the ROMs).
Probably MIUI breaks the MicroG connection (you may try to disable Battery Optimization for MicroG, not sure would it help)
Btw, you can easily install Magisk and then the root Vanced YT
Mi 9T (not Pro) on my side, Xiaomi eu Stable, using the root Vanced YT with no issues
Click to expand...
Click to collapse
I Already disables battery optimization for MicroG.
I Don't want to root the mobile. not sure that rooting will keep me receiving updates for stable rom from Xiaomi.eu

NaAZoOR said:
I Already disables battery optimization for MicroG.
I Don't want to root the mobile. not sure that rooting will keep me receiving updates for stable rom from Xiaomi.eu
Click to expand...
Click to collapse
Rooting has nothing with preventing Xiaomi.eu updates.
I used Magisk for 6-7 months with Weeklies - updating them every week, and recently similarly updated my Stable.
You receive the notification, let it dowmload and reboot (or you download manually), it boots to TWRP and flashes the new ROM
Only that you loose root for the moment because the ROM updates your old, patched (by Magisk) boot.img with the new one, unpatched
You install Magisk again and continue with your previously used modules, root apps, everything.
(You must only be careful if using e.g. Smali Patcher module or similar that was created for a particular framework version, and when ROM updates it would update the framework causing incompatibilty and brick - disable/uninstall that module before updating)
I just keep the Magisk app, once I update the ROM I exteact and patch the new boot.img, reboot to TWRP, flash the newly patched boot img, and continue with the updated ROM + Magisk.
(You can even prepare the Magisk patched that new boot.img before rebooting to TWRP for updting the ROM, and immediately upon flashing the new ROM and before rebooting, to flash also the new, patched boot img - then you already reboot to the updated ROM by immediately having the Magisk again)
Besides - there is no magic or place for fear here. Magisk by ittself by no means interfere with Xiaomi.eu updating and its 'OTA' system. However, you must not install some suspicius modules that would rename your phone model to something else - then (and only then) it could prevent recieving the notifications (similarly if you 'debloat' System Updater or if you block the site it needs for periodically checking for system update)
Otherwise, again, Magisk is in boot.img, while Xiaomi.eu requires custom nRecovery for updating - hence one totally independent to another. And the new ROM zip contains the new boot.img that will flash over your old one, no matter was your old boot.img patched with Magisk or not
Suggesting you to read the Xiaomi.eu forum to see how many users use Magisk (and novody ever reported a problem that Magisk itself prevented or messed up with OTA)

zgfg said:
Rooting has nothing with preventing Xiaomi.eu updates.
I used that for 6-7 months with Weeklies and recently updated Stable.
You receive the notification, let it dowmload and reboot (or you download manually), it boots to TWRP and flashes the new ROM.
Only that you loose root for the moment because the ROM updates your old, patched (by Magisk) boot.img with the new one, unpatched
You install Magisk again and continue with your previously used modules, root apps, everything.
(you must only be careful if using e.g. Smali Patcher modules or similar that were created for a particular e.g. framework version, and when ROM updates it would update the framework)
I just keep the Magisk app, once I update the ROM I exteact and patch the new boot.img, reboot to TWRP, flash the newly patched boot img, and continue with the updated ROM + Magisk.
(you can even prepare the Magisk patched that new boot.img before rebooting to TWRP for updting the ROM, and immediately upon flshing the new ROM and before rebooting, to flash also the new, patched boot img - then you slready reboot to the updated ROM with Magisk
Besides - there is no magic or place for fear here. Magisk b ittself by no means interfere with Xiaomi.eu updating and its 'OTA' system. However, you must not install some suspicius modules that would rename your phone model to something else - then (and only then) it can prevent recieving the notifications (similarly if you 'debloat' System Updater or if you [by AdAway] block the site it needs for periodically checking for system update)
Otherwise, again, Magisk is in boot.img, while Xiaomi.eu requires custom nRecovery for updating - hence one independent to another. And the new ROM zip contains the new boot.img that will flash over your old one, no matter was your old boot.img patched with Magisk or not
Suggesting you to read the Xiaomi.eu forum to see how many users use Magisk (and novody ever reported a problem that Magisk itself prevented or messed up with OTA)
Click to expand...
Click to collapse
thank you for detailed reply, highly appreciated.
i don't need to install any modules, i don't need root.
i just need YT Vanced to work without getting you are offline message.
does rooting solve this issue?

NaAZoOR said:
thank you for detailed reply, highly appreciated.
i don't need to install any modules, i don't need root.
i just need YT Vanced to work without getting you are offline message.
does rooting solve this issue?
Click to expand...
Click to collapse
Vanced root does not install and use MicroG. It actully works the following way:
- It installs the particular version of YT (16.29.39 for the time being)
Therefore, if you already have a newer YT, you must uninstall that newer first
- YT gets installed as the so-called split/bundle app, meaning that YT is not a single apk file but a bundle of them (split to language, display resolution, ARM architecture etc specifics component apks)
- Vanced Manager then 'replaces" the official YT base.apk, one of those split apks (actually makes the Magisk to mount it over the official YT base.apk, on every reboot)
- You must make sure that Google Play never updates YT because you would loose the Vanced YT (by blocking Automatic updates for YT in Google Play or better by so called detaching YT from Google Play - Google Play would not know that the old YT 16.29.39 is installed and would not bother to update)
That's the difference between root and non-root Vanced.
Without root, Vanced cannot replace the required part of the official YT app with their patched version.
Instead, non-root comes as a completely independent app (having also the different package name), hence you can in parallel have both the non-root Vanced YT and the official YT apps installed.
But because of all the non-root Vanced YT needs its own mechanism to login to your YouTube account - and for that it requires MicroG.
For the troubles with MicroG some users use particular older versions of MicroG and similar tricks - I don't use non-root and cannot advise you in that direction. You can read more in the XDA dedicated Vanced thread
In short, root Vanced uses the same mechanism for login and connection to YT server. Do you have disconnections with the official YT - not, hence should not have with the Vanced root either

zgfg said:
Vanced root does not install and use MicroG. It actully works the following way:
- It installs the particular version of YT (16.29.39 for the time being)
Therefore, if you already have a newer YT, you must uninstall that newer first
- YT gets installed as the so-called split/bundle app, meaning that YT is not a single apk file but a bundle of them (split to language, display resolution, ARM architecture etc specifics component apks)
- Vanced Manager then 'replaces" the official YT base.apk, one of those split apks (actually makes the Magisk to mount it over the official YT base.apk, on every reboot)
- You must make sure that Google Play never updates YT because you would loose the Vanced YT (by blocking Automatic updates for YT in Google Play or better by do called detaching YT from Google Play - Google Play would not know that the old YT 16.29.39 is installed and would not bother to update)
That's the difference between root and non-root Vanced.
Without root Vanced cannot replace the required part of the official YT app with their patched version.
Instead, non-root comes as a completely independent app (having also the different package name), hence you can in parallel have installed both the non-root Vanced YT and the official YT apps.
But because of that non-root Vanced YT needs a separated mechanism to login to your YouTube account - and for that it requires MicroG.
For the troubles with MicroG some users use particular older versions of MicroG and similar tricks - I don't use non-root and cannot advise you in that direction. You can read more in the XDA dedicated Vanced thread
In short, root Vanced uses the same mechanism for login and connection to YT server. Do you have disconnections with the official YT - not, hence should not have with the Vanced root either
Click to expand...
Click to collapse
Excellent explanation
Thank you.

Mate 40 pro gms

Hello guy i managed to get gms semi working, I dont know what to do next
Tried everything i dont have any ideas anymore hope somebody can use this and make it working
Playstore gets data but u cant download it crashes
Play services is version 7.3.29
Services framework is version 4.4.4(newer doesnt work)
Account manager version 7.1
Youtube works with account but sometimes crashes

Perhaps if you share the steps someone can use that info and make it happen.

Okay
1. Installed lzplay
2. Installed googlefier
3.installed only microg gms from googlefier and logged in with my account
4.I disabled microg gms trough adb so that account stays loged in while uninstalling(there is tutorial how to disable apps)
5. Installed Services framework version 4.4.4
6. Installed google account manager version 7.1
7. Installed google play services version 7.3.29
8. Instaled Playstore
9. If playstore wont open just go airplaine mode and delete data of playstore and services framework
Playstore opens and gets all data u can search everything but when u click download it crashes if u want working youtube u need to update google play services to this one i put here but when u install this apk i get error that this device is not play certified
Edit: uploaded all apks that i used,except play services 7.3.29 you will have to download it from apkmirror(i doesnt want to upload)

Please specify: China only device with Harmony, not with EMUI.

On Chinese models, GMS should be fully functional, as far as I know.

Well, as i've searched on youtube it's complicated to sideload GMS on HarmonyOS for chinese devices, no matter if it's Mate 40 Pro or P50 Pro, it's complicated...

robi101012981 said:
Please specify: China only device with Harmony, not with EMUI.
Click to expand...
Click to collapse
But in the video says EMUI 12 and NOH-NX9, the Chinese model it's not the same as far as I know.

dizeL69 said:
Hello guy i managed to get gms semi working, I dont know what to do next
Tried everything i dont have any ideas anymore hope somebody can use this and make it working
Playstore gets data but u cant download it crashes
Play services is version 7.3.29
Services framework is version 4.4.4(newer doesnt work)
Account manager version 7.1
Youtube works with account but sometimes crashes
Click to expand...
Click to collapse
it is a big step ahead, hope someone will find out the complete solution. how about downgrade to EMUI 11 and try the steps one more time?

Hi!
I'm using Mate 40 Pro (C432 - HW-EU => NOH-N29).
It's rather easy to downgrade using the HiSuite from EMUI 12 down to 11.
In my case I'm setting up the Hi Suite Proxy (3.3) downloaded from it's official page:
Releases · ProfessorJTJ/HISuite-Proxy
Modifying HiSuite and manipulating it's connection data to install Roms before they officially get released. - ProfessorJTJ/HISuite-Proxy
github.com
Just install HiSuite, Hi Suite Proxy, patch the HiSuite, start up the phone and connect.
I additionally turned on the Programmer Mode in the phone.
Once connected via HiSuite, in the UPDATE section, except the UPGRADE (if available) it allows to install another variant -> in my case it's allowing to DOWNGRADE (Roll-back) down to EUMI 11 (in my case: 11.0.0.253).
IMPORTANT - it's deleting/erasing all the data, so before ANY actions it's wise to backup the files on the phone.
After downgrading I was trying many methods:
- LZPlay / G-Play,
- Googlefier,
- MicroG (several variants, including the one where it allows to use different 'ID's' -> i.e. Nexus X5 (which worked partially in opposite to other sollutions).
- LightHouse -> variant available on AppStore (Huwaei) isn't working, but the one downloaded from this forum did allow me to create the Google account.
Unfortunately any mixes/fixes of GPS, GFS, Account Managers, Google Play Store - are recognizing and forgeting the accounts, while attempting to remove the MicroG or LightHouse.
Perhaps you can help by explaining how to freeze the MicroG (by ADB?) and I'll be able to move-on.
My goals are:
- make the Android Auto to run;
- make the GApps -> Google Assistant, Chrome (with sync), Google Calendar to work;