Related
Update 09.12.17: The methods below may not fully work on the latest OS versions. There is an ongoing discussion in the last pages so I hope it gets cleared out eventually, sadly I've been busy with my studies and haven't touched my phone since initially making this thread (it's on OOS 4.0.2). I write this just to make sure I don't waste your time accidentally, so please check the latest replies if you're on newer OS versions.
Hello everybody,
*the undermentioned methods and app(s) require root*
I have asked you guys in the AKT thread if you would like to see a small tutorial on how to stop the constant "com.google.android.gms/.measurement.PackageMeasurementService" and "net_scheduler" wakelocks that might or might not be responsible for the device waiting longer than it should before dozing off.
Please keep in mind that this method does work for me, and might or might not work for you, as everybody uses different things/apps so in case you see unwanted behavior, just revert back and sigh that the method has failed you.
I am not responsible for any hardware-/software damage that may occur upon using these settings.
So, now that we've got all the generic stuff out of the way, first few words about why this might bother you:
1) You don't like your device doing stuff you didn't make it do.
2) You want to minimize wakelocks
3) You're here because you just saw the two beforementioned wakelocks and already decided you want to get rid of them.
So, regarding the first one, all I can say is I got the method from this reddit post , which briefly explains which services are doing the waking and what they are. Starting with "At the heart of Firebase is Firebase Analytics, a free and unlimited analytics solution. .." got me raising an eyebrow, as I don't like handling control of my device to other people, without me even knowing.
UPDATE: I have merged the two approaches into just using one app and making the changes on a global level, so you can just do them in like 5 minutes and forget about it, but in case you have problems with disabling package measurement you can also check the hidden text just below for instructions using another app, which was basically "the old way".
So to get rid of the "snooping", as already described in that post, you need to download MyAndroidTools.
Disclaimer: Disabling some services/receivers may "crash" the app. I found it is normal, just go back to where you were and check if you managed to disable the thing you wanted, if yes, then it was successful.
1. Open the app
2. Click on the top left to open the panel, click on Broadcast Receiver.
3. On the menu that opens go to the right column named System. Click search on the top right, type "Play" and choose the Google Play Services option.
4. In the search bar there type at least "ana" and disable the two found results with the names "AnalyticsReceiver" and "AnalyticsSamplerReceiver"
5. Hit x and search again for at least "meas". You will see three results with the names "AppMeasurementInstallReferrerReceiver", "AppMeasurementReceiver" and "PackageMeasurementReceiver*". Disable all three.
****Update 15.02.17*** Apparently this one resets every once in a while, I blame this again on Google's efforts to have their spying on, but anyways. Go to services->system->Google Play Services->search "meas"->disable both "AppMeasurementService" and "MeasurementBrokerService". The third one (PackageMeasurementService) will restart too so don't bother. This should do the trick though.
6. There was discussion about "Campaign Tracking" . I only found it in the same System menu, in Android Pay, by searching at least "cam" you get the result "CampaignTrackingReceiver". Disable it if you feel you want to. I don't use Android Pay and cannot say if it breaks something there, but otherwise have it disabled and haven't noticed any problems so far.
7. Search for Google Play Store in System. In that option, search for at least "app" and disable "AppMeasurementReceiver". Hit x and search for at least "fir", then disable the two results with names "FirebaseInstanceIdInternalReceiver" and "FirebaseInstanceIdReceiver"
8. Done. All the setttings are now global for any sort of app measurements, as far as I know.
This is the "old way" of dealing with app measurement. If you have done the steps above just ignore (hide) this part and continue with disabling net_scheduler below.
So to get rid of the "snooping", as already described in that post, you need to download Root Package Disabler or equivalent alternative.
ATTENTION: As per the last version of the app, I see there might be a bug which reverts some settings when you use the search bar, so please try and find the services by hand in stead of searching, as it is more reliable.
1. Open the app
2. Start with the left-most pane, e.g. "Installed". There you can see all your installed apps
3. Click on the first app on the list, it will display a small menu. Apps that use services will have the bottom-left option named "SERVICES" available, click there. This will take you to the services list that this app uses.
4. Click on the searching icon on the top-right in order to filter the services we need disabling.
5. Write at least "appm" . If the AppMeasurementService is used by this app, it will now be displayed.
6. Tick that off (the switch will turn gray)
7. Hit x, and search again for at least "fireb". This will display all services that use the Firebase SDK. You may also check under the name of the service and see the word is contained in the "executable name", so it might not always have "an official" name that states Firebase, but still use one of their "executables" (sorry for lack of detail)
7.1 Check for any other services that have "analytics" in their description, although I haven't checked if this stops something useful, but I doubt it.
8. When you're done with the current app, it will no longer call these services and cause wakelocks as long as the services remain stopped. To my experience the settings stay after reboot, it's just the above mentioned bug you have to keep in mind since it happened to me now while making the guide, and I know it came with the latest update.
9. Go back to the installed pane and maybe tick on the star next to the app in question. It will be added to the "favourite" list where you can have all those apps and don't bother to search them again if needed.
10. Repeat from step 1 for the next app and go through all your apps. If not you will still get calls to this service from the apps that still have these services on. Also a reminder here, you have to remember and check every new app you install, as most apps do have the service enabled.
11. After you're done with all apps in "Installed", check out bloatware (I think I haven't found anything there, but it's worth checking).
12. "System" apps that I know have some of those services: Calendar, (probably) Chrome (I have that disabled so dunno), Drive, Duo, Gboard, Google Play Services, Google Play Store, Google VR Services.
Here are two pictures how an app's services list looks like, and one with some of the services disabled:
all services on
some services off
After doing these steps, you should charge your battery to 90% to reset the battery statistics and you should see that the "com.google.android.gms/.measurement.PackageMeasurementService" wakelock no longer occurs (or stays really, really low, and not thousands like before). If you still have it after all this, then you probably have an app you haven't disabled the services for.
The second approach will get rid of the "net_scheduler" wakelock. Thanks to @denon480 for the idea, it's post #34 in this thread It involves installing (again) MyAndroidTools or equivalent alternative.
1. Open the app
2. Click on the top left corner to open the menu panel.
3. Click on Broadcast Receiver
4. Navigate to the System pane
5. Click on search on the top right. Search for Google Play Services. Click on them when they show up
6. In the search top right, write at least "sche" and you will see the two receivers responsible for the "net_scheduler" wakelock, "SchedulerInternalReceiver" and "SchedulerReceiver" . Here's a picture how it looks
7. Switch the first one off. The app will quit, don't worry.
8. Go back to where you were (steps 1 to 6) . You will see that you indeed managed to swtich that receiver off.
9. Switch the second one off. The app will quit, again no worries.
10. Check if you managed to switch the second one as well. After that you're done!
I hope I could help you guys out. I know there is nothing fancy in these methods but felt a thread might be useful as I saw a good number of requests when I mentioned it in the AKT thread.
Also sorry for misleading the guys I already told it was going to be a short guide, I honestly thought it would take way less words than it did. But I think it is for the better.
Have fun.
* Reserved *
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
MeggaMortY said:
* Reserved *
Click to expand...
Click to collapse
I think Everything is fine or?
tzbigworm said:
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
Click to expand...
Click to collapse
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
1+3_FA said:
I think Everything is fine or?
Click to expand...
Click to collapse
Yup looks great.
MeggaMortY said:
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
Click to expand...
Click to collapse
Crazy how much of a beast that phone was. People forget it's actually a windows phone, Android was put on it so much lol!
Thanks for the tips. Works great!
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
youknownothing said:
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
Click to expand...
Click to collapse
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
MeggaMortY said:
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
Click to expand...
Click to collapse
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
youknownothing said:
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
Click to expand...
Click to collapse
Assuming you're disabling services, which we are lol (should've been more obvious for me too I guess), I'd say you should be fine, and even say maybe the same goes for just using MyAndroidTools, just scroll through the Service menu in Table Third-Party and you'll see the same settings you applied with the other app/Package Disabler. I guess I was lazy to realize that since I liked I can favourite the apps I need to keep an eye on in the Package Disabler.
So all in all you should be okay, but even better you may try and just use MyAndroidTools for both. I have some exams coming so I won't be able to test those things but will make sure to update the tutorial if indeed that turns out to be right (for the app you suggested or even just MyAndroidTools).
Give a shout in case you find out something more. And thanks for the info
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Mr.Jay said:
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Click to expand...
Click to collapse
Like mentioned, it works fine for me, and probably depends on personal usage. I don't use Google Pay for example, and Chrome, and Google Music.... but besides those I haven't had problems anyway.
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
NJGSII said:
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
Click to expand...
Click to collapse
Have you disabled location history in the Google App? The problem is this guide fixes only one concrete aspect of the whole "Google stalking experience" shenanigans. Please check for the thing I mentioned and also in Settings -> Backup & Reset, make sure Back up my data is off if you haven't logged in an account and intend to use that - these two things were also draining battery for me when I was on the go as far as I can remember.
LMcR92 said:
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
Click to expand...
Click to collapse
I did some checking on that list and am currently testing a way to only use MyAndroidTools for the whole aproach. If it turns out to be working the whole guide would get reduced to like 10 clicks, since the settings are global. I'll post more info after a day or so to make sure it is working, but as for now I see promising results.
Anyone used Franco's Servicely app to do this?
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
MeggaMortY said:
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
Click to expand...
Click to collapse
Will Doing like #1 post notifications from Gmail?
techusthad said:
Will Doing like #1 post notifications from Gmail?
Click to expand...
Click to collapse
Don't know what you mean by #1 - disabling the AppMeasurement stuff, e.g. first set of instructions? I haven't had problems with Gmail and I use it with two accounts on there.
Hi everyone!
I just created my first Tasker plug-in. This plug-in enables you to send an adb shell command to any other device on the network that has adb over wifi enabled. I for example use it to turn my androidtv on or off by sending it the command "input keyevent POWER". You can also open specific activities in apps for example or simulate touch input.
Please read the description before using it and don't hesitate to leave feedback/bug reports/tips! This is my first app ever published so I still have a lot to learn.
You can download it for free from the play store:
https://play.google.com/store/apps/details?id=com.ADBPlugin
Edit: It's now also available on XDA Labs! You can find it here
First update is live!
This includes proper (cat)logs and Tasker errors if something went wrong, so if you run in any problems, you can now tell me . It also plays a lot nicer with the Tasker timeout system.
@Humpie
Thanks for this plugin. I allready made a project for my sony android tv. Start apps and controll media play.
But to make the plugin better I have some featur requests:
It would be nice to be able to work with tasker variables. e.g input text "%mytext".
Another feature reqest would be to get a output variable for commands with output like adb shell pm list packages.
MartelKombat said:
@Humpie
Thanks for this plugin. I allready made a project for my sony android tv. Start apps and controll media play.
But to make the plugin better I have some featur requests:
It would be nice to be able to work with tasker variables. e.g input text "%mytext".
Another feature reqest would be to get a output variable for commands with output like adb shell pm list packages.
Click to expand...
Click to collapse
Thanks for the tips! Will definitely add variable support and I'll also have a look at output variables. They are visible in the logs already, but not yet to tasker.
Why can't we use the built-in code Acton in Tasker? Is there a difference?
loogielv said:
Why can't we use the built-in code Acton in Tasker? Is there a difference?
Click to expand...
Click to collapse
In fact there is, since android 4.something google removed adb from android devices, so you can't perform adb commands from your phone, well aside from my plugin that is.
There would however be no difference if your remote device did have Tasker and you programmed it so that a certain action does something with code. However, you would have to figure out a way to contact that device etc...
Second update! The Plugin now has Tasker variable support!
(enjoy @MartelKombat btw I'm still thinking about how to implement your other request!)
I doont understand. I can type the code, but i do have to remove the "adb sell" part of the code but it's good to go… is that not what this plugin does?
Humpie said:
Thanks for the tips! Will definitely add variable support and I'll also have a look at output variables. They are visible in the logs already, but not yet to tasker.
Click to expand...
Click to collapse
Humpie said:
Second update! The Plugin now has Tasker variable support!
(enjoy @MartelKombat btw I'm still thinking about how to implement your other request!)
Click to expand...
Click to collapse
Any news on the output variable? I have high hopes since you mentioned you already see the output in the logs...
Thanks a lot for this plugin! It makes an unrooted phone much easier to control!
How to run root commands on an unrooted device with this plugin
I just wanted to share how I use this plugin, just to give others an example of what this nice plugin is capable of.
Recently, I bought a new device and for now, I have no intention of rooting it. Coming from a rooted OnePlus One, this means some of my Tasker profiles do not work as expected anymore and I have to find workarounds.
On LineageOS (and CyanogenMod before that), we have the option to display left/right cursor arrows in the navigation bar when typing text. I always loved this feature, since placing the cursor in the right position by tapping will always be a hit&miss game. Since my new device (S7 Edge) has no onscreen navigation bar, I was searching for a replacement solution to move the cursor. I came up with the idea that it would be quite handy to use the volume buttons for this. So, the idea was the following:
IF the keyboard is shown THEN use the volume keys to move the cursor (and suppress any volume changes, if possible).
It took me a while to figure out how to determine whether the keyboard is out (solution: install another keyboard and intercept the "change input method" notification as a trigger). Suppressing the volume keys' usual behaviour was easy (AutoInput -> Key Suppress) but the final step turned out to be quite difficult: How to move the cursor?
After doing some extensive research, I always came to the same point: "not possible without root". Damn.
But then, this plugin came in. The keyword "remote" in its name might suggest that you can use this plugin only to act from one device to another, but that's not true. Actually, you can use this plugin to run adb commands on the same device.
What does that mean? It means that you can run an adb shell command like "adb shell input keyevent xy" on your phone WITHOUT ROOT. In my case, I can run "input keyevent 21" and "input keyevent 22" to move the cursor. So, how can we do that?
Prerequisites:
Connect your device via ADB to a PC (google it if you don't know how) and run the command "adb tcpip 5555". That's it, you can disconnect your device now.
Then in Tasker, create an action with this plugin and type in the following:
IP Address: localhost
Port: 5555
ADB Shell Command: input keyevent POWER
Hit the play button to test this action. If you've done everything right, your screen will turn off.
Congrats, you just executed a command on an unrooted device which usually requires root privileges!
Important:
The only downside is, the tcpip setting does not survive a reboot, so you have to set the port 5555 again via PC after rebooting the device.
I hope I explained the important part well enough. If that's not the case, don't hesitate to quote me and I'll answer here.
digitalpig82 said:
Any news on the output variable? I have high hopes since you mentioned you already see the output in the logs...
Thanks a lot for this plugin! It makes an unrooted phone much easier to control!
Click to expand...
Click to collapse
I'm sorry for my absence, really busy with school etc. (honestly, I also completely forgot, I hope you can forgive me). I'll try to look into it soon (this week or the next) and see how far I get. I really like that you like my plugin! I just found out myself last week that I can let unrooted phones send shell commands to themselves using my plugin, so I'm glad to see you found it out as well! (I used it for snapchat to simulate volume key presses, which is also possible without root indeed: https://www.reddit.com/r/tasker/comments/699sav/project_share_handsfree_snapchat_picture_and/ It also works for other camera apps that require you to hold the button to film, like whatsapp etc)
Edit: I hope it pleases you to hear that today I started working on it again. I already have the responses bundled in a list in Java, now I just need to parse them to Tasker
loogielv said:
I doont understand. I can type the code, but i do have to remove the "adb sell" part of the code but it's good to go… is that not what this plugin does?
Click to expand...
Click to collapse
Yes, you have to remove the "adb shell" part since all my plugin does is access the adb shell part. This means commands like adb pull etc won't work, that requires a different type of connection, that for now I can't achieve with Tasker. But running any remote shell command should be fine (like how you would run it if you were directly running the commands from a terminal on your phone)
digitalpig82 said:
I just wanted to share how I use this plugin, just to give others an example of what this nice plugin is capable of.
Recently, I bought a new device and for now, I have no intention of rooting it. Coming from a rooted OnePlus One, this means some of my Tasker profiles do not work as expected anymore and I have to find workarounds.
On LineageOS (and CyanogenMod before that), we have the option to display left/right cursor arrows in the navigation bar when typing text. I always loved this feature, since placing the cursor in the right position by tapping will always be a hit&miss game. Since my new device (S7 Edge) has no onscreen navigation bar, I was searching for a replacement solution to move the cursor. I came up with the idea that it would be quite handy to use the volume buttons for this. So, the idea was the following:
IF the keyboard is shown THEN use the volume keys to move the cursor (and suppress any volume changes, if possible).
It took me a while to figure out how to determine whether the keyboard is out (solution: install another keyboard and intercept the "change input method" notification as a trigger). Suppressing the volume keys' usual behaviour was easy (AutoInput -> Key Suppress) but the final step turned out to be quite difficult: How to move the cursor?
After doing some extensive research, I always came to the same point: "not possible without root". Damn.
But then, this plugin came in. The keyword "remote" in its name might suggest that you can use this plugin only to act from one device to another, but that's not true. Actually, you can use this plugin to run adb commands on the same device.
What does that mean? It means that you can run an adb shell command like "adb shell input keyevent xy" on your phone WITHOUT ROOT. In my case, I can run "input keyevent 21" and "input keyevent 22" to move the cursor. So, how can we do that?
Prerequisites:
Connect your device via ADB to a PC (google it if you don't know how) and run the command "adb tcpip 5555". That's it, you can disconnect your device now.
Then in Tasker, create an action with this plugin and type in the following:
IP Address: localhost
Port: 5555
ADB Shell Command: input keyevent POWER
Hit the play button to test this action. If you've done everything right, your screen will turn off.
Congrats, you just executed a command on an unrooted device which usually requires root privileges!
Important:
The only downside is, the tcpip setting does not survive a reboot, so you have to set the port 5555 again via PC after rebooting the device.
I hope I explained the important part well enough. If that's not the case, don't hesitate to quote me and I'll answer here.
Click to expand...
Click to collapse
So...is it possible to create a version of the plugin that runs locally and doesn't disappear on a reboot?
kenkiller said:
So...is it possible to create a version of the plugin that runs locally and doesn't disappear on a reboot?
Click to expand...
Click to collapse
I would like to be able to create such a think but I don't think Google would allow it since it's a big security flaw to have adb opened to the world at all time without notifying the user. Some devices however have a debug over wifi function hidden in the developer options (like the nvidia shield android tv), there you can just enable it and it will probably survive a reboot.
However what I would advise to do if this option is not available, is to create a .bat file on your desktop containing "adb tcpip 5555". That way after a reboot you can just plug in your phone, click the bat file and be done!
Humpie said:
I would like to be able to create such a think but I don't think Google would allow it since it's a big security flaw to have adb opened to the world at all time without notifying the user. Some devices however have a debug over wifi function hidden in the developer options (like the nvidia shield android tv), there you can just enable it and it will probably survive a reboot.
However what I would advise to do if this option is not available, is to create a .bat file on your desktop containing "adb tcpip 5555". That way after a reboot you can just plug in your phone, click the bat file and be done!
Click to expand...
Click to collapse
Hmm....But there's this custom nav bar app where it allows users to grant it adb shell permissions, and the permission survives over reboots. Auto tools and Securetask relies on the same process as well.
I guess what we're asking for is something that's not as encompassing as your plugin. Me, I just want to execute the power command without root in a way that respects smart lock, which is possible now with your app but doesn't survive a reboot, or with the custom nav bar app, which survives a reboot, but restricts me to using it in a tiny button on the nav bar, as the dev doesn't seem interested in exposing the commands to external usage.
---------- Post added at 07:30 AM ---------- Previous post was at 07:28 AM ----------
We discussed it in this part here....
https://forum.xda-developers.com/an...avigation-bar-customize-t3590967/post72212488
kenkiller said:
Hmm....But there's this custom nav bar app where it allows users to grant it adb shell permissions, and the permission survives over reboots. Auto tools and Securetask relies on the same process as well.
I guess what we're asking for is something that's not as encompassing as your plugin. Me, I just want to execute the power command without root in a way that respects smart lock, which is possible now with your app but doesn't survive a reboot, or with the custom nav bar app, which survives a reboot, but restricts me to using it in a tiny button on the nav bar, as the dev doesn't seem interested in exposing the commands to external usage.
---------- Post added at 07:30 AM ---------- Previous post was at 07:28 AM ----------
We discussed it in this part here....
https://forum.xda-developers.com/an...avigation-bar-customize-t3590967/post72212488
Click to expand...
Click to collapse
It seems this app uses specific android permissions to be able to send events etc. However my plugin has no direct access to the android system (only by using the adb bridge), so granting my plugin these permissions won't help. What however would help is if I could find a way to enable adb over wifi using only some permissions... I have no clue whether this is possible though as the app would have to call service.adb.tcp.port 5555 for itself and that needs root or an adb connection (so it still requires a laptop XD). I'm still trying though.
Humpie said:
It seems this app uses specific android permissions to be able to send events etc. However my plugin has no direct access to the android system (only by using the adb bridge), so granting my plugin these permissions won't help. What however would help is if I could find a way to enable adb over wifi using only some permissions... I have no clue whether this is possible though as the app would have to call service.adb.tcp.port 5555 for itself and that needs root or an adb connection (so it still requires a laptop XD). I'm still trying though.
Click to expand...
Click to collapse
No worries. It's just that it's so close yet so far, heheh.... I guess I'll have to reboot only when home.
kenkiller said:
No worries. It's just that it's so close yet so far, heheh.... I guess I'll have to reboot only when home.
Click to expand...
Click to collapse
I found out it is in fact possible to have wireless adb survive a reboot! However it requires a build.prop edit.
in \system\build.prop "service.adb.tcp.port=5555" needs to be added at the end of the file and then after a reboot adb over wifi will still be enabled (at least it was in my case).
The downside is that this modification can't be done via adb without root unless you have a custom recovery like TWRP and run adb while having that opened and /System/ mounted.
I'm trying to create a zip that modifies the build.prop how it should be modified, but I don't think it's possible to run it through a non-custom recovery...
Edit: I added my .bat file for modifying the build.prop adding that line. It uses an adb connection that requires more rights than what android allows when booted, but should probably work if you are able to access adb from recovery and you are of course booted in recovery mode (using recoveries like TWRP or even some stock manufacturer ones).
Update 4.3 is live!
As requested you can now access the output from the console directly in Tasker.
I tried to order everything neatly in a list, with each line in the console being an item in the list, but this does mean that the initial "device\sdcard $" et cetera get added as an item as well.
But since I didn't want to cut off anything important I just kept it that way. You can just modify the list in any way you want (AutoTools has some handy Array handling tools built in).
I also added some hints in the main screen just for fun.
If you run into any strange behaviour, bugs or have tips, please tell me!
digitalpig82 said:
Any news on the output variable? I have high hopes since you mentioned you already see the output in the logs...
Thanks a lot for this plugin! It makes an unrooted phone much easier to control!
Click to expand...
Click to collapse
Enjoy
Since most people are using my Plugin locally instead of remotely, I'm thinking of renaming it to just 'ADB Shell [Tasker]'. It would make it simpler when googling it. What do you think?
Hello people,
So I've had the OnePlus 6t for a week now and one of the things that really bothered me was that I could not figure out how to turn peeking off.
Some people in here and on other forums have commented that it's not possible to turn pop up notifications off in Android Pie. I was somehow not completely convinced of that.
After being pestered some more with the pop ups while streaming, I started going through every single setting and finally found the way to turn them off.
So you go to Settings -> Apps and notifications -> See all apps.
Then you select the app to which you want to turn off pop ups.
Then go to notifications and look for a checkbox that says either "all notifications" or just "notifications" or something similar. This is different for each app. Some apps will have multiple such checkboxes.
You then click on behavior. This is where you can change the way the notifications are delivered to you.
You can choose to receive notifications completely silently or just select "make sound" to receive notifications without peeking. Basically, any selection apart from the first one which says "make sound and pop up on screen" will turn off peeking / pop up notifications.
I apologise if this is common knowledge or if this was already posted but I had a hard time figuring this out and wanted to share it.
works good for apps that have the notification channels coded in.... however Google's own hangouts app doesn't which is just silly...
for those who don't want it on at all, the ADB method is probably best because its universal
use the following adb command:
adb shell settings put global heads_up_notifications_enabled 0
Reboot your phone. Done!
edit...link added
https://forum.xda-developers.com/android/general/howto-4-to-disable-heads-notifications-t3197660
dadoc04 said:
works good for apps that have the notification channels coded in.... however Google's own hangouts app doesn't which is just silly...
for those who don't want it on at all, the ADB method is probably best because its universal
use the following adb command:
adb shell settings put global heads_up_notifications_enabled 0
Reboot your phone. Done!
edit...link added
https://forum.xda-developers.com/android/general/howto-4-to-disable-heads-notifications-t3197660
Click to expand...
Click to collapse
Fancy seeing you here sir?
I really hate these retarded peek / pop up notifications.
Biggest crap ever, and no easy way to disable them (i.e. in Telegram).
I only saw the option in the "gaming mode" of the OP, there I can disable that ****.
The other option seems to be via the adb shell, which is super retarded as well.
That's the main reason I use android to have full customization, that's Google for implementing retarded features without the option to disable them.
If anyone found an easy way to get rid of it, that'd be great.
He I will try to advise you how to optimise and debloat your phone for better performance and battery as well as free of bloat device.
I have used this method over the years for my S10 | S10+ | S20+ | S20Ultra | S21Ultra | P40 |P40 Pro and OP8 Pro and many other phones. And works as expected.
Prerequisites:
#1. ADB AppControl
Which can be found here:
[TOOL] ADB AppControl 1.8.0 🚀 Ultimate App Manager & Debloat Tool + Tweaks
ADB AppControl 🚀 Root is not required. Works with any Android device. Can do almost everything you dreamed about with applications. ADB AppControl - the desktop program, that will allow you to easily manage applications on your android device...
forum.xda-developers.com
ADB AppControl - android applications manager and debloat tool. Official website. Free download.
Thanks to @Cyber.Cat for this application of for posting it.
#2. Windows computer or for MAC owners, Parallel Desktop to run Windows
#3. Android phone which you want to optimise
Steps for debloating bloatware:
#1. Download and install ADB AppControl from the above link
#2. Activate Developer Options: go to Settings >> About phone >> Software information >> tap 7 times on Build Number
#3. in Developer Options enable USB debugging mode
#4. Open ADB AppControl
#5. Connect your phone to your computer
#6. Allow USB connect message on your phone several times until ADB AppControl shows connect message on top
#7. Chose what applications you would like to disable or uninstall (i recommend you disable them not uninstall)
#8. From bootom right corner in ADB AppControl chose Disable option
#9. Check the box to delete cache and data [it is on top where you chosed Disable option at the previous step]
#10. Press Apply
#11. Confirm that you agree to disable the selected apps on the popup message which will appear
#12. Unplug your phone from the computer
#13. Shut down the phone
#14. Connect the phone again to your computer [being closed]
#15. Quick press Volume button + Volumne Up button until you see on your screen the logo
#16. Release the buttons
#17. Now you are into the phone recovery
#18. Chose the option to clear cache [NOT phone reset] with your power buttons
#19. Select the option to clear cache by presing the power button
#20. Chose restart phone
E voila.
There is no miracle bloatware list. It depends from phone to phone.
Being on a S21 series forum I will post what I debloated for my S21Ultra SM-G998B device.
com.android.apps.tag
com.android.bookmarkprovider
com.android.chrome
com.android.dreams.basic
com.android.dreams.phototable
com.android.hotwordenrollment.okgoogle
com.android.hotwordenrollment.xgoogle
com.android.managedprovisioning
com.android.printspooler
com.android.providers.partnerbookmarks
com.android.providers.userdictionary
com.diotek.sec.lookup.dictionary
com.facebook.services
com.facebook.system
com.facebook.appmanager
com.google.android.apps.tachyon
com.google.android.printservice.recommendation
com.google.android.projection.gearhead
com.google.android.tts
com.google.ar.core
com.google.audio.hearing.visualization.accessibility.scribe
com.justride.stbbuch
com.plantronics.headsetservice
com.samsung.android.accessibility.talkback
com.samsung.android.app.ledbackcover
com.samsung.android.app.notes
com.samsung.android.app.notes.addons
com.samsung.android.app.readingglass
com.samsung.android.app.routines
com.samsung.android.app.settings.bixby
com.samsung.android.app.spage
com.samsung.android.app.tips
com.samsung.android.ardrawing
com.samsung.android.aremoji
com.samsung.android.aremojieditor
com.samsung.android.arzone
com.samsung.android.bixby.agent
com.samsung.android.bixby.agent.dummy
com.samsung.android.bixby.service
com.samsung.android.bixby.wakeup
com.samsung.android.bixbyvision.framework
com.samsung.android.game.gamehome
com.samsung.android.game.gametools
com.samsung.android.kidsinstaller
com.samsung.android.knox.containeragent
com.samsung.android.knox.containercore
com.samsung.android.livestickers
com.samsung.android.mateagent
com.samsung.android.service.airviewdictionary
com.samsung.android.service.pentastic
com.samsung.android.service.tagservice
com.samsung.android.six.webtrans
com.samsung.android.spay
com.samsung.android.spayfw
com.samsung.android.svoiceime
com.samsung.android.visionintelligence
com.samsung.android.vtcamerasettings
com.samsung.desktopsystemui
com.samsung.knox.securefolder
com.samsung.SMT
com.sec.android.app.bluetoothtest
com.sec.android.app.desktoplauncher
com.sec.android.app.dexonpc
com.sec.android.app.kidshome
com.sec.android.app.magnifier
com.sec.android.cover.ledcover
com.sec.android.desktopmode.uiservice
com.sec.android.emergencylauncher
com.sec.android.mimage.avatarstickers
com.sec.android.widgetapp.webmanual
com.sec.spp.push
com.spotify.music
com.swiftkey.swiftkeyconfigurator
com.touchtype.swiftkey
de.axelspringer.yana.zeropage
with the above done I always get 6hrs+ of SoT and battery live of over 1day and 10hrs in a single charge with 120hz WHD+ resolution
Thanks for this method... I am using it with my S21 Ultra and works fine
So, Im trying to figure out a way to safely disable the Samsung Dialer. Ive already installed the google dialer but I broke the calls when i uninstalled it the first time. Im trying to figure out which package is the one to disable. Trying to remove as much Samsung as possible
Good to see this Debloat for the OnePlus, etc....
Excuse me, I´m totally new to the package disabling and I´m really looking forward to get it working on my new S21 Ultra. Could somebody please take some time, and explain to me what does it do and if the apps will still work even after disabling? (For example the bixby voice wakeup was disabled as seen in the screenshot, will my phone be able to get awaken via Bixby if it is disabled?)
Secondly I´d like to ask you if there is some sort of "best" list of packages to disable. I really want to maximize the battery life and performance of my device since it´ll be my inevitable workstation for couple of months.
Kind regards!
If you are new to this and your device will be an inevitable workstation for a couple of months I would wait with the most crazy debloat.
You can only disable things you know of, if you disable bixby bixby wont work, at all.
Hi everyone, if I do an OTA update the process will reinstall debloated apps?
Saluzzo97 said:
Hi everyone, if I do an OTA update the process will reinstall debloated apps?
Click to expand...
Click to collapse
No.
You can double check by seeing number of installed apk in settings.
But I never had a problem with debloated app reinstalling.
lyzgaard said:
No.
You can double check by seeing number of installed apk in settings.
But I never had a problem with debloated app reinstalling.
Click to expand...
Click to collapse
Thank you very much!
Hello all, it has been sometime since I rooted my phone / removed all the extra crap lol.
Is there a way to know what each Items do?
I know in the past the roms would be debloted and you had a stock rom and had the option to add what you wanted.
Thank you
Nice start with original post. I'm also looking for any further explanation or categorization of s21+ bloat please?
If uninstalled, can app be reinstalled manually from play store if desired later?
What phone is best for clean customizable ROM now?
Guessing Pixel series, but what else... OnePlus?
I've custom rom'd my s3 to s8, but now want to have Netflix working on my s21. Just don't want apps I never use taking up space and populating the share menu options, etc.
does debloating drain battery?
xkawsx said:
does debloating drain battery?
Click to expand...
Click to collapse
There are a couple of apk's who can drain battery if you deleted them.
I don't remember their name but if you debolat them the phone won't get into deep sleep....
But you can always double check if the phone enters deep sleep by installing CPU Spy from Play Store.
Just a little headsup on two packages you should NEVER disable!
Device Services (com.samsung.android.kgclient) - If you disable this, you will LOCK YOURSELF OUT of your phone (Error 3020). Chances are good to recover from this if you have TWRP installed or USB debugging always enabled. Otherwise a factory reset is the only solution. Nevertheless, this is a core component and WILL cause problems if disabled.
Device Security (com.samsung.android.sm.devicesecurity) - If you disable this, app installations will take significantly longer (about 5x). Not sure why, but better leave it.
In general, if you are not 100% sure what a package does, leave it! Even if someone on the internet says "I disabled it and had no problems"... There is a high possibility that you don't achieve optimization by disabling, but crippling your device and creating lots of errors in the background you don't know about (thus using more battery).
As far as I can tell, the list in the OP seems reasonable though.
@AllAboutTech Might be helpful for beginners if you add those 2 warnings to the OP.
AtrixBomb said:
If uninstalled, can app be reinstalled manually from play store if desired later?
Click to expand...
Click to collapse
You can always use ADB to re-enable apps, as long as you just disabled them (not uninstalled).
Connect to your phone via ADB and use the following command:
adb shell pm enable <package_name>
// Edit: I guess the ADB AppControl from the OP also allows to re-enable apps.
If you have uninstalled system apps, some of them might be re-installable via Play / Galaxy Store, but definitely not all.
bluediablito said:
Is there a way to know what each Items do?
Click to expand...
Click to collapse
Someone over at the S20 forums made a pretty good list some time ago:
Google Sheet
Lartsch said:
Just a little headsup on two packages you should NEVER disable!
Device Services (com.samsung.android.kgclient) - If you disable this, you will LOCK YOURSELF OUT of your phone (Error 3020). Chances are good to recover from this if you have TWRP installed or USB debugging always enabled. Otherwise a factory reset is the only solution. Nevertheless, this is a core component and WILL cause problems if disabled.
Device Security (com.samsung.android.sm.devicesecurity) - If you disable this, app installations will take significantly longer (about 5x). Not sure why, but better leave it.
In general, if you are not 100% sure what a package does, leave it! Even if someone on the internet says "I disabled it and had no problems"... There is a high possibility that you don't achieve optimization by disabling, but crippling your device and creating lots of errors in the background you don't know about (thus using more battery).
As far as I can tell, the list in the OP seems reasonable though.
@AllAboutTech Might be helpful for beginners if you add those 2 warnings to the OP.
Click to expand...
Click to collapse
That's strange. I always delete both of these without any poblems.
Device Security it's part of the Macfee antivirus thingy options.
I always get rid of because I think Play Protect does the job.
When I delete this all that's happens is that the Security Option is gone from Device Care Settings.
And I don't get those anyoing security notifications about enable it.
No problem with app install.
As for kgclient that's part of the Samsung Payment Service, I have never had any problems with deleting it.
That said, I have never used Samsung Pay.
Im on S21 Ultra european model unbranded right now.
lyzgaard said:
That's strange. I always delete both of these without any poblems.
Device Security it's part of the Macfee antivirus thingy options.
I always get rid of because I think Play Protect does the job.
When I delete this all that's happens is that the Security Option is gone from Device Care Settings.
And I don't get those anyoing security notifications about enable it.
No problem with app install.
As for kgclient that's part of the Samsung Payment Service, I have never had any problems with deleting it.
That said, I have never used Samsung Pay.
Im on S21 Ultra european model unbranded right now.
Click to expand...
Click to collapse
Hey, that's interesting. A friend also tested and confirmed the lock out / slow install.
Is your device encrypted?
Lartsch said:
Hey, that's interesting. A friend also tested and confirmed the lock out / slow install.
Is your device encrypted?
Click to expand...
Click to collapse
No I haven't encrypted it, also I don't use Secure Folder.
Maybe this has something to do with Knox Vault on encrypted phones?
Samsung Pay is also a part of the Knox vault.
Exynos, modell named SM-G998B/DS
1) Introduction
I recently acquired a Find X3 Pro Lensman edition and wanted to share the few tweaks that I operated on it, seeing that some people were also relying on importation for the Find X3 Pro.
As I used ADB to operate the majority of the changes you'll see next, I invite you to follow the XDA guide to install it, or the official Android documentation.
For a quick resume of the command lines that will be used, you can visit this link to have a quick explanation on what they are doing.
Don't forget to activate the dev options and the USB debugging before throwing yourself in the debloating process (also know that ColorOS might deactivate by itself for security reasons, so you might have to reactivate it from time to time, but after some reactivation, ColorOS will let it stay, strange behavior, but be aware that it can happen).
2) Debloat list
These packages will be uninstalled through the ADB command line
Code:
adb shell pm uninstall -k --user 0 your.package.name
Basic stuff (that you can replace for better options)
com.heytap.music
com.heytap.yoli
com.finshell.wallet
com.oplus.pay
com.heytap.browser
com.sohu.inputmethod.sogouoem
com.coloros.calendar
com.coloros.weather.service
com.android.contacts
com.nearme.instant.platform
com.iflytek.speechsuite
com.heytap.quicksearchbox
com.opos.ads
com.oplus.cosa
com.android.mms * (setting another default SMS/MMS app will result in warning prompts everytime you try to send something with the replacement app, to reinstall it, use the following command:
Code:
adb shell cmd package install-existing com.android.mms
)
Breeno related packages (ColorOS voice assistant, only works with CN language)
com.coloros.ocrscanner
com.coloros.directui
com.heytap.speechassist
com.coloros.assistantscreen
com.coloros.colordirectservice
com.coloros.floatassistant
com.oplus.ovoicemanager.wakeup
Don't forget to install replacement apps for contacts, phone, SMS and browser.
You can uninstall most other of the OPPO proprietary apps or CN bloat apps with a basic uninstallation directly performed from your smartphone, and most of them are restorable through ColorOS (Parameters > Apps > Restore deleted system apps) if you realize you've done something wrong.
3) Various tips and observations
From my personal experience, the PEEM00 units cannot use a third-party launcher consistently, even when set up through ADB. I tried to add various launchers (Nova, Nothing, Lawnchair 2, etc.), but they never appeared in the default launcher selection list. I managed to trick the system with
Code:
adb shell cmd package set-home-activity "com.teslacoilsw.launcher"
, but Nova wasn't able to fully take over and the "back home" gesture was alternating between ColorOS launcher and Nova.
I've thought about unlocking the bootloader to push Nova (or any other launcher) as a system app, but it might be an overkill solution.
OPPO is having a very angry "energy management" process, so you'll need to manually change the optimisation for the apps you want to persist in the background (personally, I changed pretty much everything to "Always ask"). You'll find the app list in Battery > Advanced parameters > Optimize battery usage.
If you want to deactivate the use of 5G bands and only use 4G+ and lower bands, you'll have to select the corresponding optimization recommendation in Settings > Battery > * recommended optimizations (top banner) > Disable 5G.
To add Google services, you'll have to load the Play Store with the com.android.vending package. You'll find it easily across the web, just make sure you download it from a trusted provider (I installed mine from APK Mirror).
OPPO doesn't seem to have released the sources for the Find X3 Pro to this day, which is a little disappointing, as I'd really like to see crDroid on it, but the smartphone in itself is quite enjoyable to use as is (moreover, the microscope lens wouldn't be usable this easily, as the OnePlus 9 Pro camera app is already requiring proprietary packages and vending folders to work properly, and it seems to use the same requirements and system packages as its OPPO brother).
To easily find the packages names, I highly recommend using Solid Explorer to check the system apps list directly on the Find X3 Pro while you debloat through your terminal on the side.
I'll surely edit this post as I find new items to add, modify, etc. Feel free to suggest your own modifications, I'll gladly look into it.
Redacted under update PEEM00FLU_11_C.08, some details might change depending on your own version (available packages, paths, etc.).
Edit 1 (22/06/2022) : added some packages in the debloat list and separated the Breeno (CN voice assistant) related ones from the general ones.
Edit 2 (26/06/2022) : added more packages and reinstalled com.android.mms, added a few tips.
Thanks for this. will try debloating my PEEM00
For some weird reason, when I uninstalled Quick Search Box (com.heytap.quicksearchbox) my PEEM00's home launcher now has this strange icon in the left (probably related to quick search box or pictorial, iirc). It doesn't let me swipe to the left (lol) and the animation of the swipe is gone. It actually doesn't bother me, because untill now the phone is working properly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Roveri said:
For some weird reason, when I uninstalled Quick Search Box (com.heytap.quicksearchbox) my PEEM00's home launcher now has this strange icon in the left (probably related to quick search box or pictorial, iirc). It doesn't let me swipe to the left (lol) and the animation of the swipe is gone. It actually doesn't bother me, because untill now the phone is working properly
View attachment 5649423
Click to expand...
Click to collapse
It's because of the presence of the main Google App.
Jaxom84 said:
It's because of the presence of the main Google App.
Click to expand...
Click to collapse
I uninstalled it and it worked like a charm, many thanks ! Btw, do you know if there's any way to know the package's description? There are some packages that look suspicious to me, and I'm wondering if it's safe to uninstall them (I know that there are many threads about debloating Find X3 Pro, but some of them didn't work for me)
Roveri said:
I uninstalled it and it worked like a charm, many thanks ! Btw, do you know if there's any way to know the package's description? There are some packages that look suspicious to me, and I'm wondering if it's safe to uninstall them (I know that there are many threads about debloating Find X3 Pro, but some of them didn't work for me)
Click to expand...
Click to collapse
Think that you may have to reinstall it if you need Google Assistant or Lens.
I'd recommend you to search on the web with their names, you'll usually find your answer easily, but yes, some packages are too Chinese to be widely known outside of this country and you might struggle finding solid clues for some of them.
Jaxom84 said:
Think that you may have to reinstall it if you need Google Assistant or Lens.
I'd recommend you to search on the web with their names, I'll usually find your answer easily, but yes, some packages are too Chinese to be widely known outside of this country and you might struggle finding solid clues for some of them.
Click to expand...
Click to collapse
Yeah, Lens need the Google app to work, I've installed it again and the icon comes back whenever I restart my phone, no clue on this, but ok, I can handle it. I'll be searching those packages on the web, and if I have any doubts or any suggestions to you, I'll be here. Thanks for your advice
Roveri said:
Yeah, Lens need the Google app to work, I've installed it again and the icon comes back whenever I restart my phone, no clue on this, but ok, I can handle it. I'll be searching those packages on the web, and if I have any doubts or any suggestions to you, I'll be here. Thanks for your advice
Click to expand...
Click to collapse
The strange thing is that you can normally disable the Discover panel on other phones (which completely hides the option), but I can't manage to find the option on the PEEM00 (be it in the Google app or the phone's settings).
Jaxom84 said:
1) Introduction
I recently acquired a Find X3 Pro Lensman edition and wanted to share the few tweaks that I operated on it, seeing that some people were also relying on importation for the Find X3 Pro.
As I used ADB to operate the majority of the changes you'll see next, I invite you to follow the XDA guide to install it, or the official Android documentation.
For a quick resume of the command lines that will be used, you can visit this link to have a quick explanation on what they are doing.
Don't forget to activate the dev options and the USB debugging before throwing yourself in the debloating process (also know that ColorOS might deactivate by itself for security reasons, so you might have to reactivate it from time to time, but after some reactivation, ColorOS will let it stay, strange behavior, but be aware that it can happen).
2) Debloat list
These packages will be uninstalled through the ADB command line
Code:
adb shell pm uninstall -k --user 0 your.package.name
Basic stuff (that you can replace for better options)
com.heytap.music
com.heytap.yoli
com.finshell.wallet
com.oplus.pay
com.heytap.browser
com.sohu.inputmethod.sogouoem
com.coloros.calendar
com.coloros.weather.service
com.android.contacts
com.nearme.instant.platform
com.iflytek.speechsuite
com.heytap.quicksearchbox
com.opos.ads
com.oplus.cosa
com.android.mms * (setting another default SMS/MMS app will result in warning prompts everytime you try to send something with the replacement app, to reinstall it, use the following command:
Code:
adb shell cmd package install-existing com.android.mms
)
Breeno related packages (ColorOS voice assistant, only works with CN language)
com.coloros.ocrscanner
com.coloros.directui
com.heytap.speechassist
com.coloros.assistantscreen
com.coloros.colordirectservice
com.coloros.floatassistant
com.oplus.ovoicemanager.wakeup
Don't forget to install replacement apps for contacts, phone, SMS and browser.
You can uninstall most other of the OPPO proprietary apps or CN bloat apps with a basic uninstallation directly performed from your smartphone, and most of them are restorable through ColorOS (Parameters > Apps > Restore deleted system apps) if you realize you've done something wrong.
3) Various tips and observations
From my personal experience, the PEEM00 units cannot use a third-party launcher consistently, even when set up through ADB. I tried to add various launchers (Nova, Nothing, Lawnchair 2, etc.), but they never appeared in the default launcher selection list. I managed to trick the system with
Code:
adb shell cmd package set-home-activity "com.teslacoilsw.launcher"
, but Nova wasn't able to fully take over and the "back home" gesture was alternating between ColorOS launcher and Nova.
I've thought about unlocking the bootloader to push Nova (or any other launcher) as a system app, but it might be an overkill solution.
OPPO is having a very angry "energy management" process, so you'll need to manually change the optimisation for the apps you want to persist in the background (personally, I changed pretty much everything to "Always ask"). You'll find the app list in Battery > Advanced parameters > Optimize battery usage.
If you want to deactivate the use of 5G bands and only use 4G+ and lower bands, you'll have to select the corresponding optimization recommendation in Settings > Battery > * recommended optimizations (top banner) > Disable 5G.
To add Google services, you'll have to load the Play Store with the com.android.vending package. You'll find it easily across the web, just make sure you download it from a trusted provider (I installed mine from APK Mirror).
OPPO doesn't seem to have released the sources for the Find X3 Pro to this day, which is a little disappointing, as I'd really like to see crDroid on it, but the smartphone in itself is quite enjoyable to use as is (moreover, the microscope lens wouldn't be usable this easily, as the OnePlus 9 Pro camera app is already requiring proprietary packages and vending folders to work properly, and it seems to use the same requirements and system packages as its OPPO brother).
To easily find the packages names, I highly recommend using Solid Explorer to check the system apps list directly on the Find X3 Pro while you debloat through your terminal on the side.
I'll surely edit this post as I find new items to add, modify, etc. Feel free to suggest your own modifications, I'll gladly look into it.
Redacted under update PEEM00FLU_11_C.08, some details might change depending on your own version (available packages, paths, etc.).
Edit 1 (22/06/2022) : added some packages in the debloat list and separated the Breeno (CN voice assistant) related ones from the general ones.
Edit 2 (26/06/2022) : added more packages and reinstalled com.android.mms, added a few tips.
Click to expand...
Click to collapse
I removed most of the recomended list, but now there is an issue with calls, people I'm calling can't hear me some times and need to make the call again, normally second time I call they can hear me. do you know if any of the removed applications can cause this?
jemadrid said:
I removed most of the recomended list, but now there is an issue with calls, people I'm calling can't hear me some times and need to make the call again, normally second time I call they can hear me. do you know if any of the removed applications can cause this?
Click to expand...
Click to collapse
Never experienced such issue, sorry.
Jaxom84 said:
I've thought about unlocking the bootloader to push Nova (or any other launcher) as a system app, but it might be an overkill solution.
Click to expand...
Click to collapse
how would you unlock the bootloader? I tried to do that a few months ago and i couldn't find a way
demonicCookie said:
how would you unlock the bootloader? I tried to do that a few months ago and i couldn't find a way
Click to expand...
Click to collapse
Strange, I have access to it in the developer's settings.
Jaxom84 said:
Strange, I have access to it in the developer's settings.
Click to expand...
Click to collapse
Did you actually try doing it? Cos the unlock device option doesn't really do anything. I selected it but when I try to unlock it it doesn't work.
demonicCookie said:
Did you actually try doing it? Cos the unlock device option doesn't really do anything. I selected it but when I try to unlock it it doesn't work.
Click to expand...
Click to collapse
I'll surely give it a try by the end of the week, as the kernel's source for the PEEM00 should get released soon (if the OPPO-source owner told me the truth). Count on me to tell you as soon as I can.
Jaxom84 said:
I'll surely give it a try by the end of the week, as the kernel's source for the PEEM00 should get released soon (if the OPPO-source owner told me the truth). Count on me to tell you as soon as I can.
Click to expand...
Click to collapse
So have u unlocked your device now they source code released
burhanhanzada199888 said:
So have u unlocked your device now they source code released
Click to expand...
Click to collapse
Unlocked without issues, you did well to remind me.
so is it possible to root now is there any way
burhanhanzada199888 said:
so is it possible to root now is there any way
Click to expand...
Click to collapse
Maybe soon, I'd gladly undergo some tests for crDroid or PixelExperience.
oh ok also can u please guide to where to start to build own rom previously i have expereince of installing custom rom and custom recovery but not actually making it also i have seen some guides and videos but they saying i need 300 gb of space is it true or is there any alternative i really want to try this i have programming experience
Jaxom84 said:
Unlocked without issues, you did well to remind me.
Click to expand...
Click to collapse
how u unlocked like what command of adb u run and r u able to boot into bootloder?