7000000.ssusb Kernel wakelock and battery drain

[riccetto80]

Actually it seems I spoke too soon. My phone no longer wants to charge anymore with this module installed (unless the phone is turned off) and the Deep Sleep function also just stopped working.

your phone being wich model and wich android version?

i (mi a1, android 8.1 October patch, magisk), atm, edited directly with mixexplorer the config file directly from N to Y and the phone charge and work as usual, deep sleep too.

magisk module, seems to do exactly the same thing, change the option file from N to Y.


EDIT:

after a full day of usage i can confirm, editing the config file changed my idle drain from 0,55 to around 0,4% / hour!!! not bad!!!

today i also added the 7000000.ssusb wakelock to fk kernel manager wakelock blacklist, will check if this diminish idle drain even more and/or if i will have issue with phone with this wakelock blacklisted!

 

[txenglan]

your phone being wich model and wich android version?

i (mi a1, android 8.1 October patch, magisk), atm, edited directly with mixexplorer the config file directly from N to Y and the phone charge and work as usual, deep sleep too.

Mine is a mi a1, lineageOS 15.1 (latest update). I just disabled the magisk module and now the phone charges properly again. That said, I'm guessing deep sleep will now be broken again. I'll test to confirm and I'll also try the method you mentioned.

 

[txenglan]

Ok, I decided to wipe out the Magisk module since I had installed it from TWRP instead of via Magisk itself. Then I did the manual edit of the config file, which seemed to work (until reboot of course). My next step was to either make the manual edit persistent or re-install the Magisk module via the Magisk manager. I re-installed the Magisk module via the manager. Rebooted a few times and everything seemed normal (Depp Sleep active and charging working). I then started an update of LoS which again broke charging but this time, after the install completed, charging came back after a reboot. So far so good.

 

[Carlos_EVH]

your phone being wich model and wich android version?

i (mi a1, android 8.1 October patch, magisk), atm, edited directly with mixexplorer the config file directly from N to Y and the phone charge and work as usual, deep sleep too.

magisk module, seems to do exactly the same thing, change the option file from N to Y.


EDIT:

after a full day of usage i can confirm, editing the config file changed my idle drain from 0,55 to around 0,4% / hour!!! not bad!!!

today i also added the 7000000.ssusb wakelock to fk kernel manager wakelock blacklist, will check if this diminish idle drain even more and/or if i will have issue with phone with this wakelock blacklisted!

Where is the wakelock blacklist option in Fk Kernel manager? I can't find it in the app, i have the same issue with the 7000000.ssusb wakelock

 

[riccetto80]

Where is the wakelock blacklist option in Fk Kernel manager? I can't find it in the app, i have the same issue with the 7000000.ssusb wakelock

enter kernel option page, scroll to the right the menu on top of the kernel option page, till section "wakelocks" you can add there wakelocks to be blacklisted.

this is what i remember.

ATM i dont have my phone around, as soon possible i will see exactly the page name and write here.

 

[Carlos_EVH]

enter kernel option page, scroll to the right the menu on top of the kernel option page, till section "wakelocks" you can add there wakelocks to be blacklisted.

this is what i remember.

ATM i dont have my phone around, as soon possible i will see exactly the page name and write here.

Thanks dude but I figured out how to solve the problem with those wakelocks without kill them with an app. It's a procedure that I have to do everytime I plug an usb but it works, at least for me.

After unplug the cable because whatever reason (battery fully charge, transfer files, usb adb, etc.) I opened BetterBatteryStats and went to Kernel wakelocks and see how 700000.ssusb, NETLINK and HVDCPD_WL are at the top of the list increasing the wakelocks after every reload in the app. You can use GSAM Battery Monitor with the same results if you prefer and it's free.

I took a microusb cable with a female USB connector to plug normal pendrives, mouse, keyboards, etc., a microusb to type C adapter and a random pendrive and plug them together to the phone while monitoring with BBS the wakelocks (refreshing the list in the app every 5 seconds or so).

After a few plug and unplug the cable the wakelocks stopped increasing and the phone started to enter to deep sleep like it did weeks before.

I tried to do the same thing after different charges and works fine everytime I did.

You can see my stats before and after I did the "trick".

Enviado desde mi Mi A1 mediante Tapatalk

 

[txenglan]

Update on my findings with the Magisk module:

Phone stopped charging properly again but I rebooted and charging has resumed. Seems like I'll have to do this once in awhile.

Does anyone know if Xiaomi is planning to fix this problem once and for all? I see varied descriptions of what sounds to be the same issue going back over a year. It doesn't sound like it's an actual hardware issue per se so is there a reason why they haven't fixed this yet?

 

[Carlos_EVH]

Update on my findings with the Magisk module:

Phone stopped charging properly again but I rebooted and charging has resumed. Seems like I'll have to do this once in awhile.

Does anyone know if Xiaomi is planning to fix this problem once and for all? I see varied descriptions of what sounds to be the same issue going back over a year. It doesn't sound like it's an actual hardware issue per se so is there a reason why they haven't fixed this yet?

Dude, try my method above your message, you only need a cable like that (mine is not OTG but I think It will work with an OTG too), a micro usb to usb type C, and any pendrive, keyboard, or whatever you plug in the usb, and start pluging and unpluging all together until the wakelock stops messing with the battery, checking the wakelock with Gsam Battery Monitor or BetterBatteryStats.

It's like the phone thinks that something is plugged in the usb and send power through the usb draining the battery. Or at least, that is my conclusion.

 

[riccetto80]

well this is interesting, but we cannot do this "cable method" each time we recharge the phone!!!

 

[Carlos_EVH]

well this is interesting, but we cannot do this "cable method" each time we recharge the phone!!!

Yes, that the main con of the method, but It happens to other phones like Asus, Huawei, Lenovo, etc. And no one has found a real solution.

Enviado desde mi Mi A1 mediante Tapatalk

 

[txenglan]

Dude, try my method above your message, you only need a cable like that (mine is not OTG but I think It will work with an OTG too), a micro usb to usb type C, and any pendrive, keyboard, or whatever you plug in the usb, and start pluging and unpluging all together until the wakelock stops messing with the battery, checking the wakelock with Gsam Battery Monitor or BetterBatteryStats.

It's like the phone thinks that something is plugged in the usb and send power through the usb draining the battery. Or at least, that is my conclusion.

Thanks for trying to help. I'm not going to mess around with all that just so I can solve this problem. All of this is something I expect Xiaomi to solve. I've already done as much as I'm going to do. If this doesn't get resolved soon, I'm going to move on and throw this phone in the garbage. Again, thanks for the ideas.

 

[riccetto80]

Thanks for trying to help. I'm not going to mess around with all that just so I can solve this problem. All of this is something I expect Xiaomi to solve. I've already done as much as I'm going to do. If this doesn't get resolved soon, I'm going to move on and throw this phone in the garbage. Again, thanks for the ideas.

this wakelock being an issue seems to be common with different models/manufacters, not just xiaomi and mi a1!

also, seems not everybody have the same drain, in my case drain is little, in other case the drain is very big!

 

[txenglan]

this wakelock being an issue seems to be common with different models/manufacters, not just xiaomi and mi a1!

also, seems not everybody have the same drain, in my case drain is little, in other case the drain is very big!

It's such a strange problem. My GF has exactly the same model of the mi a1 yet she hasn't had any issue. She bought me my phone last summer and I didn't notice the deep sleep issue until around October. I know it definitely wasn't there before September. I also had a weird speaker issue around the time I noticed the issue with then magically disappeared. I've also read that some people with the deep sleep problem wake up one day without having done anything special and it's gone.

Have you tried stock Pie on this phone? If so, same problem?

 

[riccetto80]

No, i haven't tried stock pie and i will avoid it because of all bugs and issue, at least for a couple of month.

 

[txenglan]

Checked Accubattery today and Deep Sleep is back all by itself (no mods). I've read of this happening to other people - both the emergence of the problem and then the mysterious disappearance.... Hopefully mine stays like this as I've had the issue for months.

 

[prorooter007]

Checked Accubattery today and Deep Sleep is back all by itself (no mods). I've read of this happening to other people - both the emergence of the problem and then the mysterious disappearance.... Hopefully mine stays like this as I've had the issue for months.

Same happened to my Tissot. Really strange.

 

[txenglan]

Same happened to my Tissot. Really strange.

When did that happen? Since I've changed nothing, I'm wondering whether this mystery is actually solved by an app update. This would explain why no one has a definite solution ..

 

[prorooter007]

When did that happen? Since I've changed nothing, I'm wondering whether this mystery is actually solved by an app update. This would explain why no one has a definite solution ..

It happened with me on stock ROM from April update. It was in custom ROM too ,Then I flashed custom ROM in August and manually disabled that wakelock, Though I keep changing roms Mysteriously it disappeared 2 months ago. Seems like a water/dirt damaged hardware issue to me as someone from the 4pda opened his Tissot , disconnected usb type c port and cleaned the type c port with ethanol/alcohol and reconnected type c port and the problem got fixed for him.

 

[txenglan]

It happened with me on stock ROM from April update. It was in custom ROM too ,Then I flashed custom ROM in August and manually disabled that wakelock, Though I keep changing roms Mysteriously it disappeared 2 months ago. Seems like a water/dirt damaged hardware issue to me as someone from the 4pda opened his Tissot , disconnected usb type c port and cleaned the type c port with ethanol/alcohol and reconnected type c port and the problem got fixed for him.

Very strange. Mine has been like this for months despite messing around with custom ROMs. I did find a way to manually bring back deep sleep but not without drawbacks... But since Friday, the problem had just disappeared. I can't see how it could be dirt to be honest. I think there's something else going on that no one had figured out just yet.

 

[prorooter007]

Very strange. Mine has been like this for months despite messing around with custom ROMs. I did find a way to manually bring back deep sleep but not without drawbacks... But since Friday, the problem had just disappeared. I can't see how it could be dirt to be honest. I think there's something else going on that no one had figured out just yet.

Its most probably dirt / water or somehow damaged usb port.
The 7000000.ssusb is otg wakelock . The phone keeps searching for otg , it keeps otg turning onn and off so the phone doesn't goes to deepsleep that's probably a damaged usb c issue like somehow something is connecting some of the pins in the c port .