Succefully installed & tried the ROM: Dorimanx-Light on HTC HD2 and now I want to stop many applications and services from starting at boot, especially those which do "unclear" extensive Internet communication in the background.
I hope to save net-packets, CPU and battery by doing this.
So, please tell me what happens if I block the following apps/services starting on the boot:
- Download Manager
- FOTA Notifier
- FOTAKiller
- Google One Time Init
- Google Partner Setup
- Google Play Store
- Google Services Framework
- Media Storage
- Google Search
- Market Feedback Agent
- My Uploads
- Pico TTS
- Superuser
- ReportingServiceManager
- ROM Manager
(It is very welcome if someone explained here what is the purpose of running them at boot?)
I'm planning to stick to the rule to always set up apps off-line, after downloading the on my PC first, so are these Android's market-orinented services really indispensable, please?
Dear Sirs,
We are evaluating BlissROM version 11.10, with Android 9 Pie (in the rankings they appear in the first places), in our Kiosk, with Intel Core i5 MicroPC, RAM 8 Gb., SSD 128 Gb.
We need to load and operate with the Consalud APP application, which works well with the Bluestacks Android emulator, but with Blissrom, it does not load, displaying error message "Consalud App cannot be used on devices with development options activated".
With the developer mode activated (Settings / SWystem / Developer options / On), we have tried configuring each parameter with its value alternatives, and we have also deactivated the developer mode (Settings / SWystem / Developer options / Off), and the Consalud APP deploys The same error message.
We have tested versions 11.4 and 11.10 of BlissROM, with the same result.
In Google Drive I have a folder for share pictures and Consalud APK.
I request your help to diagnose and solve this problem.
Thank you very much in advance.
Gino La Mura
[email protected]
My phone is rooted, mainly to be able to use most open source apps and disable google since I don't use google tools.
It is a pity that there is no open source custom ROM for my phone.
- ASUS ZenFone 5Q ZC600KL
- Magisk
- TWRP (only as retriever)
But I have no idea how to get the following to work:
- Screenshot
It only works if I have activated:
Screenshot +
com.asus.stitchimage
- GPS
It only works if I have activated:
Google services framework
com.google.android.gsf
Google Play services
com.google.android.gms
Is there a way to replace these tools with open source using Magisk?
Thanks
I've noticed many have been able to access the new assistant 2.0 but only on custom ROMs.
Has anyone been able to achieve it on stock?
Having it on Stock as I type.
ademmer said:
Having it on Stock as I type.
Click to expand...
Click to collapse
Was their a mod process you had to follow to get it on Google Pixel 2 XL?
If not and your in the US then it has probably been rolled out to you. However I didn't think the 2 XL was getting it. I'm based in Ireland and it hasn't been implemented on mine.
I am located in Germany, unrooted, Stock ROM, Beta Google app.
ademmer said:
I am located in Germany, unrooted, Stock ROM, Beta Google app.
Click to expand...
Click to collapse
Really? Very strange. Must be region specific so and Germany is one on the whitelist.
I'm on beta aswell and nothing
Finally got it working. Just need to get call screening up and running and I'm good.
warrencoakley said:
Finally got it working. Just need to get call screening up and running and I'm good.
Click to expand...
Click to collapse
How did you get it? Is your phone rooted? Care to mention the steps?
Yasharkhan said:
How did you get it? Is your phone rooted? Care to mention the steps?
Click to expand...
Click to collapse
The only thing I done was change the magisk props to the Google Pixel 4a and it appeared.
Yasharkhan said:
How did you get it? Is your phone rooted? Care to mention the steps?
Click to expand...
Click to collapse
Yes my phone is rooted
I have also enabled Google Assistant 2.0
Hi,
I have enabled Google Assistant 2.0 on my rooted Pixel 2XL by following some of the suggestions in this thread whilst passing the SafetyNet check using magisk!
Method:
1 - Download Termux on Google Play store
2 - Download MagiskHide Props Config module from magisk
3 - Download Busybox for Android NDK module from magisk
4 - Open termux, type
Code:
su
to give superuser privileges to the command line.
5 - Type
Code:
props
and allow time for the checks to be made.
6 - type 1 to select "Edit device fingerprint"
7 - You will be prompted to choose a letter this time, type f to select "Pick a certified fingerprint"
8 - Follow the prompts to select your device fingerprint desired -- In my case, I chose google (7) and selected Pixel 4XL (23) as my device's fingerprint.
9 - I allowed for my device to be rebooted
10 - I repeated this process, however, instead of choosing "Edit device fingerprint" you need to choose "Force BASIC key attestation"
11 - Select to ENABLE key attestation, but also "pick from device list" and choose Pixel 4XL as your loaded value.
12 - Reboot when prompted and check safetynet, if pass then check if google assistant 2.0 has been enabled
roboprod said:
Hi,
I have enabled Google Assistant 2.0 on my rooted Pixel 2XL by following some of the suggestions in this thread whilst passing the SafetyNet check using magisk!
Method:
1 - Download Termux on Google Play store
2 - Download MagiskHide Props Config module from magisk
3 - Download Busybox for Android NDK module from magisk
4 - Open termux, type
Code:
su
to give superuser privileges to the command line.
5 - Type
Code:
props
and allow time for the checks to be made.
6 - type 1 to select "Edit device fingerprint"
7 - You will be prompted to choose a letter this time, type f to select "Pick a certified fingerprint"
8 - Follow the prompts to select your device fingerprint desired -- In my case, I chose google (7) and selected Pixel 4XL (23) as my device's fingerprint.
9 - I allowed for my device to be rebooted
10 - I repeated this process, however, instead of choosing "Edit device fingerprint" you need to choose "Force BASIC key attestation"
11 - Select to ENABLE key attestation, but also "pick from device list" and choose Pixel 4XL as your loaded value.
12 - Reboot when prompted and check safetynet, if pass then check if google assistant 2.0 has been enabled
Click to expand...
Click to collapse
Thank you very much for your extensive help!
your instructions worked great on my device!
roboprod said:
Hi,
I have enabled Google Assistant 2.0 on my rooted Pixel 2XL by following some of the suggestions in this thread whilst passing the SafetyNet check using magisk!
Method:
1 - Download Termux on Google Play store
2 - Download MagiskHide Props Config module from magisk
3 - Download Busybox for Android NDK module from magisk
4 - Open termux, type to give superuser privileges to the command line.
5 - Type and allow time for the checks to be made.
6 - type 1 to select "Edit device fingerprint"
7 - You will be prompted to choose a letter this time, type f to select "Pick a certified fingerprint"
8 - Follow the prompts to select your device fingerprint desired -- In my case, I chose google (7) and selected Pixel 4XL (23) as my device's fingerprint.
9 - I allowed for my device to be rebooted
10 - I repeated this process, however, instead of choosing "Edit device fingerprint" you need to choose "Force BASIC key attestation"
11 - Select to ENABLE key attestation, but also "pick from device list" and choose Pixel 4XL as your loaded value.
12 - Reboot when prompted and check safetynet, if pass then check if google assistant 2.0 has been enabled
Click to expand...
Click to collapse
I'm also on a PIXEL 2 XL and tried the change to 4 XL but i was getting an error in health services pop up, overheating of the device and lag. Changed to 4a and all is good in the hood.
Do the (F-Droid) Kaltura and Evozi device id developer tools report a different Android ID for you as they do for me?
If so, why?
Kaltura XDA thread
Kaltura F-Droid tool (named "kDI Device Info system permission")
Evozi XDA thread
Evozi Google Play Store tool (named "Device ID")
Note: There is a Kaltura Google Play Tool named "Kaltura Device Info" which is not being discussed here.
Note: The actual ID's are obfuscated where the GSF ID's match between the two tools, but not the Android Device ID.