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

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.

WiFi exclamation mark

Poco phones are actually Xiaomi devices. How does the device determine if it's actually got internet connectivity via WiFi or not? Does it ping a certain server somewhere?
Maybe the Poco/Xiaomi server is in China, or somewhere, and the device is not receiving a timely response to the pings, hence it's showing the WiFi "!" exclamation mark.

I have occasionally seen a WiFi "!" exclamation on my Huawei phone when hotel WiFi is not so great.

AFAIK Xiaomi intended their Poco branded phones for sale and use in India, Pakistan, and Bangladesh. Is that where you are?

Android Studio starting two apps at a time

When I run app A from project A it also starts app B from project B even though project B is not loaded. Why is app B starting and how to prevent it?

Android Studio Bumblebee | 2021.1.1 Build #AI-211.7628.21.2111.8092744, built on January 18, 2022 Runtime version: 11.0.11+0-b60-7590822 x86_64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 12.1 GC: G1 Young Generation, G1 Old Generation Memory: 2048M Cores: 12 Registry: external.system.auto.import.disabled=true Non-Bundled Plugins: com.knziha.vectorpathtweaker (1.9.1), Dart (211.7808), io.flutter (65.1.2), org.intellij.plugins.markdown (211.7142.37)

A51 accidently flashed the wrong firmware, now doesnt even boot into dowload

Given what you've posted, I think it's truly bricked and you're SOL. Unless you have the correct JTAG rig and software. JTAG is what the manufacturer uses for the initial firmware load on blank chips during production. .


Seems to be some A51 repair videos on YT covering this.
https://www.youtube.com/results?search_query=jtag+a51+samsung

Apps on an Android 10 phone

Qualcomm make the processors used in a large number of phones, so it's very likely that those apps are there for a reason.

com.qti is also qualcomm. Let's consider com.qti.ltebc: since "qti" is Qualcomm, and "lte" is "long-term evolution", i.e. the 4G network standard, I would strongly advise leaving things like that alone.

"tmobile" and "verizon"/"vzw" are US service providers - not sure why the phone would have apps from both.

I will give one bit of advice: don't remove any system apps unless you either have a nandroid backup (i.e. a backup made using a custom recovery) or know how to reflash to stock firmware (and know where to find a compatible firmware image). If you get this wrong the phone may not boot, so you need to have the means to recover it before you start fiddling. One of my top rules for root users is "take a nandroid before you change anything in the system, no matter how trivial).

Filter

Back
Top Bottom