• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Cleaning bloatware

I decided to clean some of the bloatware off of my rooted Pixel 3XL. The first bloatware I removed using ‘adb shell pm uninstall --user 0 <package>’ and there were no problems. However, it was pointed out that I should have TWRP installed in case something goes wrong. While I can do this, the phone is actively used and I am concerned about making a mistake. So, a bit more looking and I found something that suggested using ‘adb shell pm disable --user 0 <package>’.

The problem is that this didn’t work. When I tried ‘adb shell pm disable --user 0 com.verizon.obdm_permissions’, I got the error message ‘Security exception: Shell cannot change component state for com.verizon.obdm_permissions/null to 2’. Did some searching, but nothing indicated how to resolve this issue.

My question: Can 'pm disable' be used (and what should I do to avoid the error) or is ‘pm disable’ not a viable option for non-system bloatware?
You're using the old adb command which is unreliable. Try the new command instead.

Code:
adb shell pm disable-user --user 0 <package>

Help No in-car charging or Android Auto

Also try different cables as well
He did mention a new cable in the OP. That, and a bad port on the phone were some of my initial thoughts, but the devices work in the other vehicle. I *think* USB does some type of low power listening to determine when a device is connected, then ramps up the power for charging and communication. I think this is what he is seeing with the initial connection / charging notification. When things are firing up something is going wrong so the USB is shutting down (either from the phone or the head unit) to prevent damage to anything connected. That's why, having eliminated the phone ports and the cable, I think it could be debris or other problems with the usb port in the car.

Please help me to optimize code in C++.

now I had solved this problem only using one line:
Code:
--- a/system/vold/fs/Vfat.cpp
+++ b/system/vold/fs/Vfat.cpp
@@ -68,7 +68,9 @@ status_t Check(const std::string& source) {
         cmd.push_back(source);

         // Fat devices are currently always untrusted
-        rc = ForkExecvp(cmd, nullptr, sFsckUntrustedContext);
+        //rc = ForkExecvp(cmd, nullptr, sFsckUntrustedContext);
+
+               ForkExecvpAsync(cmd);

upload certificate with a key that is too weak.

I built a new Android app in the MIT AI2 program. I just tried to publish it on the Play Store, using the Google Play Console. When I tried to upload the .aab file, I got this error :

Your Android App Bundle uses an upload certificate with a key that is too weak.

What can I do in AI2 for this one?
Here's the official documentation for signing your app bundles.
https://support.google.com/googlepl...B&visit_id=637823029693292460-3874495408&rd=1

Help System won't post. yes video, no keyboard response

Whelp, sorry for the late update, but since then I was able to source an Asus p8z77-v motherboard, a fractal meshify c case locally, and an i7 3770 (locked). Amazingly, once built and put through its paces, the locked chip let me auto over clock up to 41×103 with 1.18vcore. With my refilled 240 aio on it, even with prime95 and avx workload, no core went above 66C. Based on what I could research about ivy bridge, it seems I got myself a really solid bin for a locked chip.

Filter

Back
Top Bottom