Advanced charging controller - Xiaomi Poco X3 NFC Questions & Answers

As I love my new phone I would love to make the battery last as long as possible. I stumbled upon Advanced charging controller (ACC https://forum.xda-developers.com/t/advanced-charging-controller-acc.3668427/ ). Sadly it doesn't work on my Poco X3 (Lineage 18.1, Optimus Drunk kernel). Did anyone by any chance make ACC work? Or is there any other reliable way to make charging stop at 80% and possibly limit charging current?

you should be more specific, which version didn't work on your phone, magisk module or AccA (acc Android application), if magisk module, uninstall it, download latest AccA from github, install it (root required), if freezes after opening, restart phone, if still freezing, install older version and try again (AccA v. 1.0.29 works on all my devices including poco x3)...

Thanks jeryll, spot on right when I was about to test AccA.
Edit: I got F-Droid's v1.0.29(33) and it appears to be working fine without any fidgeting...

Thanks for your response and sorry for not being more specific. Initially I have been using AccA 1.0.31 (the newest build). In the App everything looks fine (daemon running etc). But when I plug in the phone and come back later it will be at 100%. I have experimented with different versions (the one you mentioned as well) and Acc modules. I think sometimes the charge will stop at the set percentage, but then resume after some seconds. Which switch are you using? Automatic or a specific one?
Are you on Miui or a custom ROM? Android 10 or 11?

pnin said:
Thanks jeryll, spot on right when I was about to test AccA.
Edit: I got F-Droid's v1.0.29(33) and it appears to be working fine without any fidgeting...
Click to expand...
Click to collapse
Does it work with the original charger as well? I have been able to make it work with regular chargers, but not with the supplied 33W charger. I suspect there is some kind of override in the fast charger.
Which switch is working for you if you try "acc --test"? For me it ist "/battery/input_suspend 0 1", but sadly without idle battery and not with the original charger.

I don't use MIUI, only custom ROMs, mostly A11, for me AccA 1.0.29 is working correctly on custom ROMs with or without built-in special charging limits (because some have it buggy, I use AccA there)... No specific switch used, default config after installing, just start stop charging levels changed in app and saved. Works. Tested with or without original POCO charger.
Acc --test throws the same result "/battery/input_suspend 0 1". Especially for you I tried to install latest magisk version of acc (used magisk 21.4), guess what, works too, soo maybe try another magisk, or reflash your phone with fastboot version of MIUI, or something...

jeryll said:
I don't use MIUI, only custom ROMs, mostly A11, for me AccA 1.0.29 is working correctly on custom ROMs with or without built-in special charging limits (because some have it buggy, I use AccA there)... No specific switch used, default config after installing, just start stop charging levels changed in app and saved. Works. Tested with or without original POCO charger.
Acc --test throws the same result "/battery/input_suspend 0 1". Especially for you I tried to install latest magisk version of acc (used magisk 21.4), guess what, works too, soo maybe try another magisk, or reflash your phone with fastboot version of MIUI, or something...
Click to expand...
Click to collapse
Thanks for trying. I am using magisk 22.0, but that seems to be the only difference. As I said, with generic chargers "stop at certain percentage" works well, only with the original charger it doesn't. I thought I had solved the puzzle, since in the documentation it says that certain fast chargers override the switches, but now you say that for you the original charger works as well. So I guess I'll experiment some more. Maybe it is the Optimus Drunk kernel I am using, or Magisk 22.0 or some strange other stuff. For now I'll just use a different USB charger.

TMooV said:
Does it work with the original charger as well? I have been able to make it work with regular chargers, but not with the supplied 33W charger. I suspect there is some kind of override in the fast charger.
Which switch is working for you if you try "acc --test"? For me it ist "/battery/input_suspend 0 1", but sadly without idle battery and not with the original charger.
Click to expand...
Click to collapse
FYI, I'm on Xiaomi.eu v12.0.7.0 with updated firmware, but I don't use the factory charger -- speed charging goes against battery health according to all credible sources that I have found.
I usually charge overnight and I just wanted to rest easy that the phone isn't getting micro-topups that also wear the battery down.
This strategy has served me well with past devices as I have never had to replace any battery.

TMooV said:
Thanks for trying. I am using magisk 22.0, but that seems to be the only difference. As I said, with generic chargers "stop at certain percentage" works well, only with the original charger it doesn't. I thought I had solved the puzzle, since in the documentation it says that certain fast chargers override the switches, but now you say that for you the original charger works as well. So I guess I'll experiment some more. Maybe it is the Optimus Drunk kernel I am using, or Magisk 22.0 or some strange other stuff. For now I'll just use a different USB charger.
Click to expand...
Click to collapse
I have the same problem on another device, same thing, acc works with the slow charger (18w) but doesn't with the fast one (55w). I tried on stock os, on lineage os and same damn thing. A guy on Acc telegram group told me it could be the adapter. Not sure about this but worth asking you if you use an adapter too. I use it since the charger has a chinese plug

Seccostecco said:
I have the same problem on another device, same thing, acc works with the slow charger (18w) but doesn't with the fast one (55w). I tried on stock os, on lineage os and same damn thing. A guy on Acc telegram group told me it could be the adapter. Not sure about this but worth asking you if you use an adapter too. I use it since the charger has a chinese plug
Click to expand...
Click to collapse
I am not using an adapter. My theory is that the fast charger has some internal electronics that bypass the "pause" switch or uses a different switch altogether. For now I am just not using the fast charger any longer, since fast charging ist bad for the battery anyways.

TMooV said:
I am not using an adapter. My theory is that the fast charger has some internal electronics that bypass the "pause" switch or uses a different switch altogether. For now I am just not using the fast charger any longer, since fast charging ist bad for the battery anyways.
Click to expand...
Click to collapse
Aye you're right but this thing triggers me, I know it's not good for the battery but it's satisfying charging from 20 to 80 in less than 20 minutes. Then i don't know what's the problem. I know for sure some people have it working on fast charger but I have no clue on what makes it different between same device/rom. Hope someone will figure it out.

Is there any updates?
I have the same problem (((

drneed said:
Is there any updates?
I have the same problem (((
Click to expand...
Click to collapse
Which ROM and which version of ACC are you using?

Noter2017 said:
Which ROM and which version of ACC are you using?
Click to expand...
Click to collapse
xiaomi.eu 12.5.2.0 / 11
AccA 1.0.27-1.031 tested
acc v2020.6.14-v2021.2.25 tested
Currently installed 2020.10.28 and 1.0.29
No battery restriction for AccA. Ultra battery saver is off as well.
Last versions 1.0.31 and v2021.2.25 on my previous xiaomi note 7 pro (12.0.3.0) worked really well.
----
I tried different versions of the daemon and the app. It can limit current, but can't stop charging at 85%.
When I connect a charger (cap ~80%) it starts charging (but it shouldn't), after 15-20 sec it stops (it should), but then it starts charging again and never stops. At that moment the daemon was still running, I checked (accd, command).
Sometimes daemon also stops.
PS. Original cable+charger and even weaker charger were tested, but no luck.

Related

Prospective new s3 user here - root, tethering, ROM on 4.4.2?

I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!
rice923 said:
I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!
Click to expand...
Click to collapse
Root is still possible. Tethering *USED* to work on stock by using the FoxFi app. I haven't tested it in quite some time though. There's a limit for the free version, use it for testing though.
Sent from my SCH-I535 using XDA Free mobile app
I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too
rice923 said:
I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too
Click to expand...
Click to collapse
Do tell how. Especially if you did start with a Verizon galaxy s3 sgh-i535 that was not rooted and was running on stock Verizon Android 4.4.2
To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints
rice923 said:
To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints
Click to expand...
Click to collapse
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
I remember seeing you around MWs FML thread! 5.0 is looking decent over there, so I'm very happy for them.
If you get the chance, I'd definitely recommend CM11. It make me feel like I'm running a nexus device again, except significantly faster than the gnex with a better camera.
Regarding the charging speed, I don't think it's a kernel issue. With the phone plugged in, I keep getting notifications that it's being disconnectedAnd reconnected spontaneously. I've done some reading and and it seems there is a bit of oxidation or hardware issue within the charging port. The port also requires soldering of the mother board to change. I've resorted to ordering some qi chargers[emoji106]
As for the camera, this seems to be an old issue of cm11. I flashed a camera fix zip, but to no avail. The focus issue seems to be problematic only at macro distances though. I can't find a fix besides touching to focus prior to taking macro shots
Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3
ShapesBlue said:
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3
Click to expand...
Click to collapse
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.
Rushead said:
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.
Click to expand...
Click to collapse
Then yes there are several kernel options for fast charge. I know of lean kernel and ktoonsez off hand that are
From my CM11 S3
Don't want to start a new thread even though the title is irrelevant at this point, but was hoping someone could chime in regarding the camera auto focus issue. The camera focuses beautifully when I touch the screen, or when I allow it to autofocus. When I proceed to take the pic, it will try to focus again and take the pic right as it's completely blurry. This happens on both the stock CM11 camera and google camera.
I tried to flash the zip mentioned here http://forum.cyanogenmod.org/topic/85493-camera-wont-focus-cm11/ and nothing has improved.
Does anyone have any insight about this? These symptoms are identical to what many have mentioned in the thread above, so this is certainly not an isolated incident. Thoughts or input?
Who reads titles anyway?
I flashed Slim, and messed around with the camera a little, but I had wifi issues and am in the process of flashing cm11 11-09.
On Slim, the camera seemed to work fine. I took some "macro-esque" shots of text that came out pretty good (at least as good as the GNex, if not better).
I'll let you know how it fares with cm11...
So far, camera FCs on hitting the "No Thanks" button for location reporting.
OK, Camera is now functional (probably didn't wait long enough for the phone to settle on initial setup). The quality is mediocre. I'm still messing with it and will report back.
switching phones, want to keep/root the old Galaxy s3 as a lab/toy
Have an old Verizon Galaxy S3. Just got a new TMo Sony Xperia Z3 (which I am liking so far).
Will soon disconnect my Verizon service. Would like to root the S3 and use it wifi only as a experiment/toy thing, since there's no trade in value (cracked screen).
Possible? Cyanogenmod recommended?
I'm a total n00b at all this, and would steer totally clear of it for my main driver. But since I don't really NEED this phone anymore, thought this would be a safe way to dip my toes in. If I brick it in the process, no great loss.
Any advice or links would be much appreciated. Definitely want it to keep working as a wifi device and not brick once I cancel my Verizon service. Would be cool to be able to play with some of the fringier apps that require root. Those are my only requirements. Camera, cell service, etc all unnecessary. But do need wifi and don't want to create a big vulnerability to the rest of my home wifi network from this device once I'm done.
Thanks again!
evbb, depending on your current OS version, you might be able to root. If you are on the most current official OS, then you will likely just be staying with that.
Rushead, any update on how CM11 11-09 is going? If everything looks stable, I think I'll make the jump to that build.
Update about my charging times: The phone seems to charge at a normal rate if I use a 12V car charger made by Griffin (item does not specify amperage). I don't believe amperage has antying to do with my situation, as I've been yielding miserably slow charge times with the Nexus 7 (2.1 amp) charger. The phone is also very picky with cables. I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...
When my wife had the phone it was extremely loose as far as cables went. I could use virtually any cable whereas my GNex is super picky.
I haven't had much time to mess with the camera yet. I'm using it as a WiFi device, too, so I can't comment on data, signal, etc. But so far it seems pretty stable. The battery drain is excessive imo. On standby for most of the day, battery was dead by 10pm. That's factory kernel.
For those looking for a decent tethering app there's one on sale, free on the Amazon app store. Easy Tether is the name of the app. It's free 11/14 & 11/15
http://www.amazon.com/s/ref=amb_lin...d_t=101&pf_rd_p=1973721462&pf_rd_i=2350149011
From my CM11 S3
rice923 said:
I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...
Click to expand...
Click to collapse
You should try a very specific type of cable. The problem is the fact that you use a data cable at all. What I use is an aftermarket universal USB cable and it has the detachable tip for other phones. What this does is force the phone in "Charging (AC)" mode no matter what charger you use. Attached are 2 pictures to help identify exactly the kind of cable to solve your issue. I can charge my 7000 mah battery attached to my phone in 5 - 6 hours. A 2100 ah battery should be 1 - 2 hours with this.
Sent from my SCH-I535 using XDA Free mobile app
Some chargers identify as a USB hub rather than an AC adapter, and others do not. This is why on some chargers, it still charges slow. If ever the phone thinks it is on USB, it will not allow more than 650mah to pass through the cable. So even if you had a 10amp charger, it would not use that much if it identified as a hub.
Using the cable I mentioned removes the ability for any charger to send the identifier info to the phone. Reason? You are missing the data+/- cables that data is transmitted through. Only the +/-5v wires remain.
Sent from my SCH-I535 using XDA Free mobile app
But why would the phone have a constant disconnection and reconnection while being plugged in? That's the part that confuses me.
Regardless, I just received my qi charge in the mail! It's been pretty nice so far! I'm happy to answer any questions about it if anyone is interested
Rushead, wanted to give you a heads-up about the latest CM11 build I used. I clean flashed 11-15 and everything was great except for the camera, which consistently gave me a "cannot connect to camera" error. Otherwise, it seemed like a great build with some great options. I gave up and clean flashed 01-15. Camera is all great except for the autofocus issue mentioned before. GPS lock is great, and battery life is loads better than my GNex days.
Regarding my qi chargers, I am pulling a net positive charge of 315mA on my house charger (Nexus 7 2.1amp AC adapter). This is with the phone turned on, connected to Wi-Fi, screen off, and doing nothing.
My car qi charger is doing about the same. I ran the GPS with screen on (auto brightness) and the charger only charged the phone 3% in 2 hours with screen on and GPS running the whole time. I might switch the DC socket to the included one to see if I get better results.

Battery life lineage OS versus Color OS

Hi, I am thinking to flash lineage OS to my oppo R7 plus and I was wondering how good is the battery line in lineage OS as consider to color OS. Battery life is the most imp thing for me in my cell phone. Any body using lineage OS work oppo R7 plus - can your answer me with some figures. I wil like to know some numbers. Like if I am getting 24 hours in color OS, how many hours I will get in lineage OS?
Thanks for any answers.
Hey there i'm on the latest LineageOS build , your mileage may vary but from 100% to 0% in my experience is in 1 day and multiple hours , Screen on time around 7-8 hours. Good luck !
Hi, thanks for the reply. That sounds good. One more question, VOOC charging is supported by Lineage OS?
Thanks
aiglesh said:
Hi, thanks for the reply. That sounds good. One more question, VOOC charging is supported by Lineage OS?
Thanks
Click to expand...
Click to collapse
Of course. you'll see charging rapidly on your lock screen.
Thanks a lot.
Two last questions before I can go for it.
1. If I don't like lineage OS and want to go back to stock color OS, is there any tutorial for that ( I searched but found nothing and even the official international oppo forms are closed recently).
2. Any major drawback of lineage OS as compared to Color OS? Any major features that is not working on lineage OS?
Thanks again.
how did you managed to flash lineage os ? please help me
There is tutorial here on the forums. I have not yet flashed it though.
aiglesh said:
Thanks a lot.
Two last questions before I can go for it.
1. If I don't like lineage OS and want to go back to stock color OS, is there any tutorial for that ( I searched but found nothing and even the official international oppo forms are closed recently).
2. Any major drawback of lineage OS as compared to Color OS? Any major features that is not working on lineage OS?
Thanks again.
Click to expand...
Click to collapse
If I were you, I wouldn't touch LOS with a barge pole on this phone.
I've been running the nightlies (which are really weeklies) for months and they just seem to get less and less usable.
Firstly, forget Bluetooth if you use LOS. Using any BT headset or speaker usually results in an extremely sluggish and/or resetting phone if a call then happens. I can be quite happily walking along listening to TuneIn on a BT headset but, if a call then comes in, I have about a 20% chance of taking it without the phone dying. Same if I place a call. Which basically makes BT useless unless you never want to talk to anyone., which is kinda what they're for.
I also sometimes experience frequent random slowdowns just by activating the phone (maybe once per 2-3 days). It was working fine when I put it down. Then I pick it up and press the on switch. It then takes over a minute for the screen to come on, and further interaction with it is glacially slow until you reboot it.
Other times, it doesn't become unusably slow but is still noticeably sluggish (after activating) for no apparent reason.
Various apps crash that didn't crash before. Not always, but often enough to be annoying. In particular, Titanium Backup crashed on startup for months. It doesn't now. I don't know what changed.
Double tapping the screen to wake it up sometimes works and sometimes (maybe every 10 days) doesn't.
Battery life is noticeably less than stock.
GPS (Google Maps) doesn't always work. A few days ago I had to visit somewhere I'd never been to before. I tried to follow myself, on the bus. My position didn't update after leaving the bus station.
And don't get me started on TWRP as the recovery. It claims to support USB OTG but it doesn't, which is a major problem if you want to back up the phone to a USB flash stick. You can't. And the developer completely ignores bug reports about it.
I have two of the phones, both of the r7plusf model, so I'm sure these aren't problems with a specific phone.
And the nature of most of these problems is that you can't capture logs to file a bug.
All in all, if you have this phone just stick with what OPPO gives you, warts and all, unless you *really* want an ulcer. Or, if you really want to use LOS, get another phone.
Sorry for the late reply.
PS - if a dev happens to be listening, contact me. I'd love to help fix this stuff in any way I can.
NeBlackCat said:
If I were you, I wouldn't touch LOS with a barge pole on this phone.
I've been running the nightlies (which are really weeklies) for months and they just seem to get less and less usable.
Firstly, forget Bluetooth if you use LOS. Using any BT headset or speaker usually results in an extremely sluggish and/or resetting phone if a call then happens. I can be quite happily walking along listening to TuneIn on a BT headset but, if a call then comes in, I have about a 20% chance of taking it without the phone dying. Same if I place a call. Which basically makes BT useless unless you never want to talk to anyone., which is kinda what they're for.
I also sometimes experience frequent random slowdowns just by activating the phone (maybe once per 2-3 days). It was working fine when I put it down. Then I pick it up and press the on switch. It then takes over a minute for the screen to come on, and further interaction with it is glacially slow until you reboot it.
Other times, it doesn't become unusably slow but is still noticeably sluggish (after activating) for no apparent reason.
Various apps crash that didn't crash before. Not always, but often enough to be annoying. In particular, Titanium Backup crashed on startup for months. It doesn't now. I don't know what changed.
Double tapping the screen to wake it up sometimes works and sometimes (maybe every 10 days) doesn't.
Battery life is noticeably less than stock.
GPS (Google Maps) doesn't always work. A few days ago I had to visit somewhere I'd never been to before. I tried to follow myself, on the bus. My position didn't update after leaving the bus station.
And don't get me started on TWRP as the recovery. It claims to support USB OTG but it doesn't, which is a major problem if you want to back up the phone to a USB flash stick. You can't. And the developer completely ignores bug reports about it.
I have two of the phones, both of the r7plusf model, so I'm sure these aren't problems with a specific phone.
And the nature of most of these problems is that you can't capture logs to file a bug.
All in all, if you have this phone just stick with what OPPO gives you, warts and all, unless you *really* want an ulcer. Or, if you really want to use LOS, get another phone.
Sorry for the late reply.
PS - if a dev happens to be listening, contact me. I'd love to help fix this stuff in any way I can.
Click to expand...
Click to collapse
I'm on the same nightlies , i don't have any issues you mentioned (yes even bluetooth works perfectly) ! the only bug i have started with last month's nightlies which makes headphones audio stutter at low volume.
rch.aj34 said:
I'm on the same nightlies , i don't have any issues you mentioned (yes even bluetooth works perfectly) ! the only bug i have started with last month's nightlies which makes headphones audio stutter at low volume.
Click to expand...
Click to collapse
This blows my mind. What didn't I do right? Didn't I sacrifice enough chickens?
TBH the Bluetooth problem (at least) is well documented, as well as being a massive dealbreaker.
Funnily enough though I don't have an audio stutter problem. But I don't use physically attached headphones.
Are you open to a crash-off, in which we both install the same LOS version and (if necessary) start adding apps until we either see my problems or we don't?
rch.aj34 said:
Of course. you'll see charging rapidly on your lock screen.
Click to expand...
Click to collapse
This helped me too, thanks. I put an inline meter and it was only drawing 1.x amps but without the meter I can see "rapidly charging" on the lockscreen. Pity there is no battery icon change for Oppo's in LineageOS (14.1).
One more thing, if you're still active... which country are you in? I first put 15.1 on my R7Plusf and right off the bat WiFi didn't work.. even after reboot etc.
I flashed 14.1 and every single thing works perfectly so far!

USB connection issues

Hi all,
I've been running my Xtrons unit for a while now, with Malay v2 Android 8 for a few months. Everything used to work great, but since last week (without changing anything) my USB connection works crappy. My USB with music and DAB are connected directly through the two USB connections at the rear with an extension. They both stopped working suddenly, but the USB stick I have connected still has its power LED on. So there is power to it.
A few reboots later it worked again, but the next day it was gone again. I then checked the MCU settings and disabled PVR USB (I believe), and it worked again after a reboot. When it works, it works great by the way. The next day it still worked, so I was thinking I solved it.
However, the same afternoon same issue... Few minutes later (without a reboot) it worked again... Tried to disconnect everything and plug in either the DAB or the USB stick, but same result.
I strongly think its a software issue since I can 'solve' it with rebooting it sometimes. Anyone ever had something like this?
No one? Same problem today. Started my car and no USB whatsoever. 10 minutes later without doing anything everything worked fine for the remaining part of my journey to work.
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
tw39515 said:
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
Click to expand...
Click to collapse
It's a GS unit. Not sure if they're the same perhaps. Weird that it suddenly appeared.
I have the same issue.
when I connect USB/64GB and 3G dongle USB constantly reconnects. I'm on dasaita px5/4GB
1st up and not to be one of the thread patrol guys we seem to have running round the Android auto forums..
But general help questions like this should be in the QA area..
Maybe mods should shift it..
But to answer the question with a bit of experience lately..
In my USB thread on SSD's and the USB M2 casing I have used.. I found a similar thing going on with the USB ports..
As reported there.. plug in the M2 SSD (which of course is plugged into the controller in the housing)
And it's seemily pulling too much power as it affected the ability for a GPS lock..
Unplug it and GPS works..
My thinking there is as said..to me it is like it is either a software glitch and or power interruption. I am leaning more towards the power theory.
There is a bit of reading around on USB port burn out on some of the boards.. so it's almost like a case of being careful on actually plugging in to much to ...
In my case 3 USB ports..
This does bring up another point that has been bothering me the last few days as I hunt for a better storage situation..
My reading on 128g USBs via the comments section is showing up extremely hot usb's.. thus it's something to think about . As in these things in a glove compartment could end up being a fire hazard..
And or even in the case here, causing sort of interference back through the system..
Some of the more electronically minded techies with the right testing equipment would be able to have more input.. and I can bet you that the engineers in the factories making these things are not talking or reporting back to their bosses anything along these lines.. as they will be all about protecting thier jobs.. and no one is going to want to put thier hand up and say.. hey..I think we have a problem..
tw39515 said:
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
Click to expand...
Click to collapse
Tried the 'fix' from here, which should restart the usb hub, but all it does it restart the wifi, as can be seen in the code. The problem is that USB worked fine for me now twice while testing. So couldn't test if the 'fix' actually does help.
I can't seem to get Tasker to run with root... It says that my device is not rooted, although other apps give the SuperSU pop-up that ask for root access...
Tried the .sh file in the other tried, and an app to reset the USB hub, but no luck. Rebooting a few minutes later worked.
I have the same issue. I figured out that it is temperature related. When the outside temperature is ABOVE 11-12°C the USB works fine. When its colder It constantly reconnect every 20(?) Seconds. When the Car Heat Up enough the Error is gone again.
Still no solution for my issue. Also have it in the nice (12-14 degrees C) weather in the past few days. What else can I try before I bin it and go to another HU?
edit: Oh, and how can I get this to hardware?
Bose321 said:
Still no solution for my issue. Also have it in the nice (12-14 degrees C) weather in the past few days. What else can I try before I bin it and go to another HU?
edit: Oh, and how can I get this to hardware?
Click to expand...
Click to collapse
We need to replace the USB Controller Chip GL850 to GL852. You can get the Chip in AliExpress.
€ 3,47 11%OFF | 5 stücke GL852 GL852G USB hauptsteuerspan SSOP-28 SMD
https://s.click.aliexpress.com/e/cPrldP21
EDGN said:
We need to replace the USB Controller Chip GL850 to GL852. You can get the Chip in AliExpress.
€ 3,47 11%OFF | 5 stücke GL852 GL852G USB hauptsteuerspan SSOP-28 SMD
https://s.click.aliexpress.com/e/cPrldP21
Click to expand...
Click to collapse
Yeah I've seen that, but it's too small for me to try. I'm not that great in soldering, so don't want to ruin my unit haha.
Install the Hal9k Rom, where you can restart the internal USB hub on startup and then USB devices will work again.
Ati_gangster said:
Install the Hal9k Rom, where you can restart the internal USB hub on startup and then USB devices will work again.
Click to expand...
Click to collapse
Already tried that, and I have the Malaysk ROM which also has the 'fix'. Also tried to run it manually. Also have a USB Controller app that can do this.
Worked a few times but doesn't anymore now.
check this thread
https://forum.xda-developers.com/an...x5-mcte-low-temperature-fix-wifi-usb-t3868388
there are at least two solutions. one is mentioned before - to swap the GL850 chip. second is not checked yet.
mahtew said:
check this thread
https://forum.xda-developers.com/an...x5-mcte-low-temperature-fix-wifi-usb-t3868388
there are at least two solutions. one is mentioned before - to swap the GL850 chip. second is not checked yet.
Click to expand...
Click to collapse
Already tried the second 'solution'. Didn't work for me.
My best bet now is the new chip. I've ordered 5 of them, gonna check if I can solder it, or let it be soldered once it's arrived.
Bose321 said:
Already tried the second 'solution'. Didn't work for me.
My best bet now is the new chip. I've ordered 5 of them, gonna check if I can solder it, or let it be soldered once it's arrived.
Click to expand...
Click to collapse
It's good feedback (that second method doesn't work ). also ordered three chips and going for swap.
i have other issues though. when using USB dongle or copying files from usb to internal mem my screen is blinking (like darker-brighter in fast pace).
i hope that swap will help with this issue also
mahtew said:
It's good feedback (that second method doesn't work ). also ordered three chips and going for swap.
i have other issues though. when using USB dongle or copying files from usb to internal mem my screen is blinking (like darker-brighter in fast pace).
i hope that swap will help with this issue also
Click to expand...
Click to collapse
Sounds weird as well! Good luck.
My unit disconnect USB with vibrations on the road. I also try replace USB chip.
karolp1993 said:
My unit disconnect USB with vibrations on the road. I also try replace USB chip.
Click to expand...
Click to collapse
I think you need to see very closely in where the usb cable is welded in the morherboard and try to find cold weldings. I had same problems with my pumpkin and when i completely dissasemble it i saw a ton of cold welding and i reweld everything and its rock solid now.

Question Android auto not working on S22 Ultra

Hello,
Anyone managed to make AA work on their S22 Ultra?
I know it's a known topic, but seems that no debeloper (Samsung or Google) cares to make it fix...
Before answering, please note that i have already tried to clear AA cache and data, to disable/enable the app, tried different apk versions, tried different cable, and no luck at all!
My A21S, Oneplus 6t and Onplus 8 worked fine, so is not an issue from the cars (Skoda Kamiq or Skoda Ovtavia IV).
Any ideas? It's frustrating that such an expensive phone doesn't have Android Auto working...
Thanks!
I have tried everything (I believe) to make it work but still, AA is not working. I gave up and I will wait for another software update.
last time I checked it worked perfectly
2021 renault captur
tobias14 said:
last time I checked it worked perfectly
2021 renault captur
Click to expand...
Click to collapse
Are you using wireless android auto?
drfundy said:
Are you using wireless android auto?
Click to expand...
Click to collapse
no, wired
tobias14 said:
no, wired
Click to expand...
Click to collapse
Dang. I always had a problem with WAA on my s21 ultra. Was kind of hoping they had fixed it.
Forgot to mention an important detail: EU variant (with Exynos, not 8gen1)...
Also tried both, wired and wireless, and is not working.
AA icon appears in notification panel for 1 sec, then it crashes... While on head unit, it's loading the connection, then sais it is failed
Strange, for me it works but it takes ages (like a minute or two) to load the homescreen each time. Afterwards it works normally. The sound works right on. Wireless AA, Exynos, EU
works great here out of the box with Nissan Sentra. Wired...
cheers
Clear the cache and data from the android auto app, then remove your phone completely from your car. Try adding it again. That worked for me. However, I'm on the SD variant, and using AAwireless. As for that, I had to put it on passthrough at first, then AA pushed an update and it worked without.
gettinwicked said:
Clear the cache and data from the android auto app, then remove your phone completely from your car. Try adding it again. That worked for me. However, I'm on the SD variant, and using AAwireless. As for that, I had to put it on passthrough at first, then AA pushed an update and it worked without.
Click to expand...
Click to collapse
What difference does the passthrough make, please?
alex24alpida said:
Forgot to mention an important detail: EU variant (with Exynos, not 8gen1)...
Also tried both, wired and wireless, and is not working.
AA icon appears in notification panel for 1 sec, then it crashes... While on head unit, it's loading the connection, then sais it is failed
Click to expand...
Click to collapse
Here eu version, italian, work perfectly with booth cable and wireless, make sure to use an original samsung cable if cabled, sometimes data transfer interrupt and AA not work.
2019 Lincoln Nautilus with Sync3 working fine. Always delete your old phone(s) from the vehicle before pairing the new one.
AAWireless module working fine as well. Did a reset on the module and had it up and running in a minute.
fortuneman said:
What difference does the passthrough make, please?
Click to expand...
Click to collapse
I have no idea lol. Someone in another thread tried it and it worked.
I forgot to add, 2020 Audi A5,.
Wireless and wired working on my s22 ultra. The Motorola MA1 has been flawless also
Submit an error report after replicating the issue
Samsung Members app > Get help > Send feedback > Error reports
Mine works (2021 RAV4 XSE Hybrid), but I have to say every voice command twice. The first time I say it, there's a 15-20 second pause, and I get "Oops, something went wrong with the network connection, please try again later". I repeat it right afterwards and it works fine. It's a pain in the damned ass.
Same thing is happening with the S22 and the S22 Ultra. Lots of people complaining on Google's forums about S22 issues.
It seems to be a common issue, my Pioneer DMH-Z5350BT goes to the black screen when I connect my SD S22 Ultra.
Hopefully, there will be a fix soon!
Post Nine said:
Submit an error report after replicating the issue
Samsung Members app > Get help > Send feedback > Error reports
Click to expand...
Click to collapse
..i have also reported, hopefully, it will help!
Mine works for the most part.
SGS21U AT&T Stock unrooted, Wired AA 2016 Ford Escape, US.
fortuneman said:
Strange, for me it works but it takes ages (like a minute or two) to load the homescreen each time. Afterwards it works normally. The sound works right on. Wireless AA, Exynos, EU
Click to expand...
Click to collapse
Agree on the timing, but I never really cared since I always wait for everything on the car to fully load before I drive.
Only thing that's gone wrong was two days ago. I didn't have my cord, so I was on Bluetooth. For the first time ever, it said device was not available when I would switch to Bluetooth in the car. They were both connected - and still connected. I cleared cache and data, unpaired both ends, rebooted phone restarted car, re-paired, but nothing. Was the only time that has ever occured to me.

Question My first issues with the X5 Pro

So I've received my X5 Pro today. After installing everything, I've wanted to move some backups on to the phone. So I've connected the USB cable to my PC, but the connection gets cut every like 2-3 seconds. It always recovers itself, but it only lasts another 2-3 seconds and this loops.
After installing drivers from "https://xiaomidriver.com/poco-x5-pro" it still does not work.
Same issue.
Also, when I keep the phone locked, so it should only charge the device, the same thing is happening.
==
Also, looks like the fingerprint reader is not very responsive after the phone has not been moved for some amount of time. It is not recognizing my finger at all, and I have to use the Pin to unlock it. When it is unlocked, it works just fine. This is only happening after a longer (2-5 minutes) of downtime, I guess.
UPDATE: After some time and adding multiple fingerprints again, it seems to work fine now. I am not sure if it was the re-adding of the fingerprint, or it just needed some time, but ye. Looks like it is working fine now.
Did anybody experience something similar?
gmbhneo said:
So I've received my X5 Pro today. After installing everything I've wanted to move some backups on to the phone. So I've connected the USB cable to my PC, but the connection gets cut every like 2-3 seconds. It always recovers itself, but it only lasts another 2-3 seconds and this loops.
Also, looks like the fingerprint reader is not very responsive after the phone has not been moved for some amount of time. It is not recognizing my finger at all, and I have to use the Pin to unlock it. When it is unlocked, it works just fine. This is only happening after a longer (2-5 minutes) of downtime, I guess.
Did anybody experience something similar?
Click to expand...
Click to collapse
Did you try installing the usb driver on your pc?
Legitimate_ process 99 said:
Did you try installing the usb driver on your pc?
Click to expand...
Click to collapse
Are there any device specific ones?
After installing drivers from "https://xiaomidriver.com/poco-x5-pro" it still does not work.
Same issue.
I had the same kind of issue with my X3 Pro and now my X5 5G, took me a good amount of Googling to solve it... Windows10 is the cause of those troubles.
You'll need to :
1) disable USB power saving on EACH root hub and port in "Device Manager"
see https://www.hamoperator.com/Fusion/FusionFiles/K9EQ-Fusion-PDF-0023.pdf
2) disable driver signing mode (but first you'll most likely need to turn off Secure Boot in your BIOS/UEFI, or the commands will return a "permission denied" error)
see https://windowsreport.com/driver-signature-enforcement-windows-10/
Worked like a charm for me. Sadly, the second procedure has to be repeated often, as Windows reactivates it stealthily and without even asking for your opinion...
Ok so at least, the USB Port is working fine on my Linux Notebook. So it has to be my PC or Windows ... good news in terms of the device.
gmbhneo said:
Ok so at least, the USB Port is working fine on my Linux Notebook. So it has to be my PC or Windows ... good news in terms of the device.
Click to expand...
Click to collapse
This is consistent, since as far as I'm aware the Linux kernel does not enforce any driver signing onto its users : it leaves the task of ensuring the drivers that the user chooses to add to the system have been verified as safe by the user beforehand (maybe it's placing a bit too much trust into the user's skills or discipline, but this is a completely different discussion)...
Thank heavens, that practice of driver signature enforcement is limited to and specific to Microsoft...
Just in case...
I had similar issues with another Xiaomi device, and reason was that I didn't use the device's USB cable to connect to the PC, but I used an older USB-C cable. Once I used the USB-C cable with the red USB connection it worked.
Thought of sharing this info in the rare case this is the issue.
Kalaoras said:
Just in case...
I had similar issues with another Xiaomi device, and reason was that I didn't use the device's USB cable to connect to the PC, but I used an older USB-C cable. Once I used the USB-C cable with the red USB connection it worked.
Thought of sharing this info in the rare case this is the issue.
Click to expand...
Click to collapse
I've tested this before. It is still not working with the cable coming in the box. I've tested around 4-5 cables, I guess. So it really seems to be an OS related issue.
I have the same issue of fingerprint scanner nor working on my Poco X5. Deleted the fingerprint and re-added it. Still not working.
EDIT: just stumbled on a post while googling for a solution. It's Nova7 that caused the issue. Now the fingerprint scanner is working.
Well then I'd advise using a totally different computer...
I just had the issue on my main laptop (Win10, but it's become very cluttered over time. I need to do a clean reinstall -and an upgrade to Win11 while I'm at it- as soon as I get a 1/2 day of spare time) : the device isn't picked up when plugged in.
Switching to my ultra-light notebook (Dell Latitude 7280, Win11) solved the issue, it's being recognized at once.
As a sidenote : if your computer features USB3 ports (as many computers of less than 4 years of age do), I'd strongly recommend getting a USB2 hub to plug your phone in, and most importantly to flash anything on it, because (according to the infos I've gathered here and there anyway) USB3 is apparently known for being pretty unreliable -sometimes even treacherous- for flashing purposes with Xiaomi devices... This might apply to other Qualcomm-powered devices as well, but I don't own any such devices that are recent enough to be able to confirm it, although my Galaxy Note3 (Intl QC version) never complained about it in the past.
gmbhneo said:
So I've received my X5 Pro today. After installing everything, I've wanted to move some backups on to the phone. So I've connected the USB cable to my PC, but the connection gets cut every like 2-3 seconds. It always recovers itself, but it only lasts another 2-3 seconds and this loops.
After installing drivers from "https://xiaomidriver.com/poco-x5-pro" it still does not work.
Same issue.
Also, when I keep the phone locked, so it should only charge the device, the same thing is happening.
==
Also, looks like the fingerprint reader is not very responsive after the phone has not been moved for some amount of time. It is not recognizing my finger at all, and I have to use the Pin to unlock it. When it is unlocked, it works just fine. This is only happening after a longer (2-5 minutes) of downtime, I guess.
UPDATE: After some time and adding multiple fingerprints again, it seems to work fine now. I am not sure if it was the re-adding of the fingerprint, or it just needed some time, but ye. Looks like it is working fine now.
Did anybody experience something similar?
Click to expand...
Click to collapse
Xiaomi side mounted fingerprint reader has already known as not so reliable. Even older device with back cover fingerprint has lower rate of failure on recognising thumbprint. Either go for back cover fingerprint reader or an under display one. My guess is because they have larger area to recognise thus lowered the failure rates.
Bonjour, je viens de recevoir mon Poco X5 Pro, je suis passé au Miui 14 et je n'ai aucun problème comme vous le décrivez. le lecteur d'empreintes parfait et je n'ai aucune déconnexion avec l'USB lors des transferts de fichiers !
Snakeforhire said:
Well then I'd advise using a totally different computer...
I just had the issue on my main laptop (Win10, but it's become very cluttered over time. I need to do a clean reinstall -and an upgrade to Win11 while I'm at it- as soon as I get a 1/2 day of spare time) : the device isn't picked up when plugged in.
Switching to my ultra-light notebook (Dell Latitude 7280, Win11) solved the issue, it's being recognized at once.
As a sidenote : if your computer features USB3 ports (as many computers of less than 4 years of age do), I'd strongly recommend getting a USB2 hub to plug your phone in, and most importantly to flash anything on it, because (according to the infos I've gathered here and there anyway) USB3 is apparently known for being pretty unreliable -sometimes even treacherous- for flashing purposes with Xiaomi devices... This might apply to other Qualcomm-powered devices as well, but I don't own any such devices that are recent enough to be able to confirm it, although my Galaxy Note3 (Intl QC version) never complained about it in the past.
Click to expand...
Click to collapse
This is quite true but mostly for Chinese OEMs who are still primarily using usb 2.0 on their phones. I've noticed it happen more on win 11 though, compared to win 10. But you seemed to have the opposite experience so I'm not sure if there's a trend correlating to windows. Haven't had issues with older OnePlus devices and Motorola.
I've got a problem regarding Poco X5 Pro 5G, when my phone is off and I put the charger....it chargest to %95 without any problem and gets stuck at %95. Doesn't matter how long I wait it doesn't help at all. But if I start up my phone then the charging continues to %100. Does anybody know what's causing this behavior?

Categories

Resources