Galaxy S7 G930F mmc0_detect and bbd_wake_lock wakelocks - enormous battery drain - Android Q&A, Help & Troubleshooting

40$ Paypal for the person who finally helps me to solve my problem!
I have a very serious battery problem with my Galaxy S7 G930F.
Even at night when I do not use it and I turn on flight mode and energy saving mode it drains up to 10% battery per hour. When I go to bed with 60% sometimes the battery is completely discharged when I wake up in the morning.
I have had that issue for a long time now an I have already tried a lot to investigate what is causing the problem.
The first thing I tried was to completely wipe everything and reflash the official Nougat ROM. It did not help at all (I did not configure anything or install any apps! so the problem can not be caused by some app).
Then I tried both the SuperStock ROM and the Superman ROM for G930F - but the problem persistet. (I fully wiped everything in TWRP before flashing the new ROMS)
Using the App Wakelock Detector I found out that my phone is unable to go to deep sleep at all - and I also found out that the Kernel Waklocks mmc0_detect and bbd_wake_lock are causing this problem.
I have found out so far that the mmc0_detect problem can be caused by a faulty SD-Card - but I have not SD-Card installed!
The bbd_wake_lock comes from the broadcom sensorhub driver.
I have no idea what to do now, because I don't have better knwoledge to resolve the root cause of the problem.
Could it be a hardware probleme since the problem persists even with a clean install of a new ROM? I did not install any apps and the problem is already there.
Thanks for your help.
i.imgur.com/FfGOKMo.png
i.imgur.com/SEhPDeY.png
(sorry I can't post images yet)

I'm having the same problem too... I've also done the same steps that you did (factory reset, clean install superman rom, removed SD card, formatted SD card on the phone etc etc)... i'm starting to think that it's hardware problem....
the only difference I have with you is that my phone's a G930FD

Hi there....I'm running into the exact same issue. This is 100% Wifi related. If I turn off Wifi both these wake locks go away. I used better battery stats to track it.
I'm not sure what can be done to prevent it (other than turning off Wifi). Any ideas??
Thanks.

Related

bluefix problem

hi
install latest Epinter JB rom. applied the bluesleep.fix.
after a while the phone finally goes into deep sleep mode (which was never done before)
after some time in deep sleep mode the phone just turns off and require battery removal and turning on again
does anyone came up with this problem ?
when the rom is installed clean with no bluesleep fix it works fine
thanks

[Q] Non-stop crashing and rebooting

Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Daimao1984 said:
Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Click to expand...
Click to collapse
Hey,
pls backup ur apps and then do this:
0) Do a nandroid Backup via recovery
-- backup and restore
-- backup to internal (or external) sd card
1) Download Rom
2) Put it on internal sd card
3) Go into recovery mode
4) DO A FULL WIPE!! (U won't loose ur backup on sd card [but u can copy it to PC, too, if u want])
-- wipe data/ factory reset
-- wipe cahe partition
-- advanced > wipe dalvik cache
-- mount and storage > format data/system/cache
5) Then flash Rom
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Then flash Gapps
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
7) Recovery > wipe cache partition
8) Recovery > advanced > wipe dalvik cache
9) Then flash Dorimanx
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Reboot and u r done!
Links:
ROM: U should have already the newest one, or at least u know, where u find it.
Dorimanx Kernel
Gapps
Much success,
CHEERS
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Updating: I've been restoring my old nandroid backups for the whole day to see if the problem had anything to do with Jelly Bean. Well, I've gone back to the old ICS days and every version of it had the same random and constant rebooting. Even versions that didn't have any problem before.
I'm beggining to think I have a hardware failure of some sort. Do any of you guys know what could cause this kind of hardware failure? Since the phone has been getting hot for no apparent reason, it seems to me its a problem with the SGS2 cooler. Is that even possible?
OK so I have this problem but only when using my backup battery. (Not official). When It gets around 30% it begins to make my screen flicker and loose signal and just die.
So maybe you haven't got an original (official) battery in your s2?
Sent from my Galaxy SII
I dont think I have an unofficial battery. Its the same battery that came with the phone (bought from Amazon), and also, mine says Samsung on the back. Dunno if its enough to assume its official. Is there another way to check if my battery is official?
Daimao1984 said:
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Click to expand...
Click to collapse
Do u check if u r using the correct Roms for u phone? (i9100, i9100p, i9100g,etc)
CHEERS
Send from my SGSII-i9100, running RootBox nightly with Dorimanx Kernel.
Hi I am also facing the same problem. Mobile is getting hot near the camera lens.

[Q] Continuous reboot on Xperia logo

Hello,
My Xperia Mini started to reboot continuously and the only way to stop it is to remove battery. I think this have something common with battery, because after this happened battery charges very slow (about 5% per hour) but when I plug the charge cable it works fine.
I tryed to flash another rom and kernel but this doesn't helped.
Before that happened it was another issue, when I was turning on the phone battery sometimes was showing 100% (after restart it was fine).
I have unlocked bootloader and root.
When this reboots started I was staying under the sun, can it be caused by overheat? Does anybody know how to solve this problem?
Thanks.
This continuous reboot is called bootloop. You may have installed an incompatible mod before or well, something just happened. This should not have anything in common with battery. Reflash your choice of rom then wipe dalvik cache. If still doesn't work, wipe data.
fundre said:
This continuous reboot is called bootloop. You may have installed an incompatible mod before or well, something just happened. This should not have anything in common with battery. Reflash your choice of rom then wipe dalvik cache. If still doesn't work, wipe data.
Click to expand...
Click to collapse
I already flashed another rom with kernel (inlcusive stock) and wiped dalvik cache, also made a hard reset and formatted the flash card but still no luck . I think is caused by bad battery becase when is plugged it works fine, it's like battery doesn't charge anymore (it doesn't get warm) and always shows 100%. I will try to replace it and say the result.
mag3nta said:
Hello,
My Xperia Mini started to reboot continuously and the only way to stop it is to remove battery. I think this have something common with battery, because after this happened battery charges very slow (about 5% per hour) but when I plug the charge cable it works fine.
I tryed to flash another rom and kernel but this doesn't helped.
Before that happened it was another issue, when I was turning on the phone battery sometimes was showing 100% (after restart it was fine).
I have unlocked bootloader and root.
When this reboots started I was staying under the sun, can it be caused by overheat? Does anybody know how to solve this problem?
Thanks.
Click to expand...
Click to collapse
hi,
I had the same problem with my mini pro.... the problem was a faulty battery.... maybe its the same for you... (here I'm referring only to the 100% battery problem... not the bootloop)
romikavinda said:
hi,
I had the same problem with my mini pro.... the problem was a faulty battery.... maybe its the same for you...
Click to expand...
Click to collapse
If there is problem in battery then phone wont even boot to get in bootloop
& BTW GOOGLE is solution go there

Deep Sleep Issues, event wakelocks 0-8

Hey everyone. redoing my thread now that we have tried alot of solutions, hopefully someone has a vague idea of what we can do to my phone lol.
So then, my phone (redmi note 3 snapdragon) refuses to go into deep sleep no matter what combination I've tried.
Tried Combos
1. RR+ radon and agni
2. Miui 8 stable and dev preview (7.1.5 and 8.1.1.0)+ stock, radon, and neon kernel (flashing using miflash with unlocked bootloader official)
3. Cm13 latest nightly+ radon, stock, and agni
4. Nitrogen os+ nagato kernel (current rom)
All combinations we're tried with clean installs (factory data, system,cache and internal storage)
Hardware methods tried
1. Physically disconnecting fingerprint sensor (goodix)
now then, with wakelock detector, we can see im troubled with a 99% awake time, along with 100,00's of event wakelocks over 6hours, now event wakelocks deal with the actual hardware of the phone from what i've seen, which makes little sense to me because the screenshot i am attaching was just over an entire night of not touching the phone. so why it has any activity is bizarre to me. so heres what we have tried so far on my previous thread.
Tried methods of fixing event wakelocks
1. Greenify, force doze, wakelock blocker and blocking everything in frustration. deep sleep battery saver.
2. physically deleting events one by one (going into dev/input/eventx (x being wakelocks 1-10) after deleting some my display eventually stopped working, most likely because i just deleted the event that controls the lcd i assume. rebooting fixed the problem and remade the events in their directory so no harm done.
3. removing zram usage figuring it was a thrashing problem (saw a thread in the hd desire of the same issue. didnt help sadly.
4. flashing modem in radon thread, ended up making my phones earpiece not work for calls and still had the wakelocks.
5. disabling gps, along with auto brightness and auto rotate
so then if anyone needs any other information just let me know, currently using an iPhone for the time being so im desperate lol. but still id rather fix and find the problem then go for returning the phone. better to solve a problem for future people in my shoes then just thrust it away is how i see it. also someone bug the strix and darkstrix about this maybe they know the solution. anyway thanks for reading and i hope we can fix my phone soon
^Update^ now using epic rom 7.1.12 from the xda thread, still got wakelocks on stock without any other apps.
I have same problem in all versions of stock MIUI Rom. I too tried all sorts of combination but the problem remains. Finally I'm using RR Rom 5.7.4 (20161113 build) + radon Kernel. My deep sleep problem have been solved (though not 100%). Now my phone looses very little battery in standby time like 1-2% over a night. Before RR Rom I tried many custom Rom but had same problem. If you have not tried the ROM (RR Remix 20161113) I've mentioned above give it a try. Best Of Luck.
Thanks rj I'll install and post logs after work. Fingers crossed that it fixes my problem.
use the rom android 6.0.1 with module powernap , u can fix it !!
http://repo.xposed.info/module/net.jzhang.powernap
Small update: testing stamina mod currently with xposed. ressurection remix will be next only because xposed seemed a bit easier lol
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Then once try nexus rom i am getting good battery life in this rom too.
rjrulz007 said:
Then once try nexus rom i am getting good battery life in this rom too.
Click to expand...
Click to collapse
surer rj which one?
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
That happens to me when background data enabled . when i disable backround data through data usage settings , the battery backup gets better, but sure my social apps wont sync.
It seems the wakelock come from android system itself , go check logcat and you will get messages like "ANDR_PERF_RESOURCES FAILED TO APPLY PERFORMANCE" , the likes of "decided to move IRQ from cpu0 to cpu1" , and the likes of "FPC listener : waiting..." , thats all that i notice and thats happening every single milisecond on every MM roms i have tried so far....
Well when i used miui 7 LL global didnt get that much messages on logcat , but its LL ...
I guess the problem is related to source code , i dont know .
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
D4xel said:
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
Click to expand...
Click to collapse
yes sir still nothing
rohit4kk said:
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
Click to expand...
Click to collapse
hey dont worry man you'll be the first when we find an answer lol
Zaccary said:
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Click to expand...
Click to collapse
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
deltatux said:
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
Click to expand...
Click to collapse
thanks for the tip but we are running on airplane mode only at this point just to make sure we don't have more things to worry about battery drain. i appreciate the information though ^_^
Mine kenzo, tried all miui version, always the same.
sbor-si said:
Mine kenzo, tried all miui version, always the same.
Click to expand...
Click to collapse
I'm not alone!!!
Hey hopefully we find an answer buddy
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
sbor-si said:
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
Click to expand...
Click to collapse
i believe last time i tried 7.3.2.0 it gave me constant reboots and lagged quite a bit. but i also heard it was the best for battery so i can try flashing through miflash again after work. im also going to be trying this rom here https://forum.xda-developers.com/re...nzo-lldlm18-1-3m866beta-real-factory-t3375250. since it uses edl mode instead of fastboot so hey maybe that will knock something lose?
Well, right now I'm trying to get it working - without luck. I can flash 7.3.2. with miflash via edl without troubles, phone started normaly, all seems good, until "No service" for gsm signal. Bad luck. I think that modem version from that old flash is not compatible with hardware.
But it looks so good - Android takes 20% and Android system 6%...

Wake-Lock Problem.

Hello and compliments of the season.
I have a Poco, fully stock MIUI 11 with all latest updates of all apps and services. I have done my best to disable all unnecessary apps and permissions and ads etc. I've even factory reset my phone yesterday.
But even in doing all of this, my phone refuses to go into deep sleep. Overnight I'm losing 35% battery when before I used to lose only about 2%. I've disabled Sync, disabled anything that's auto, no backups enabled.
Still the phone shows "Awake"
I am aware of some Wake-Lock detector apps that I can use... But I'm not sure how or which to use.
Please advise. I have attached screenshot of overnight battery.
But can anyone teach me the best way to do this.
use $adb bugreport to generate the zipfile
Upload the zip file to https://bathist.ef.lc/ and see for yourself whats happening
Thank me later
rahulmanpur said:
use $adb bugreport to generate the zipfile
Upload the zip file to https://bathist.ef.lc/ and see for yourself whats happening
Thank me later
Click to expand...
Click to collapse
Can you give me step by step instructions.
Do I need a PC or can I do it from my phone itself?
Here is my bug report.
I've attached the bug report if anyone is willing to help me. I don't understand how to use Battery Historian page. So if anyone is willing to help me I would be very grateful.
Update : Failing everything I can do at home, I took the phone to the service center. They flashed 10.2 firmware and the problem still persist. Then they flashed 11.05 and the problem is still there. He even opened the phone and cleaned all sensors and cables etc. Took three hours of time but problem is still not solved. Fortunately I was not charged even though I'm out of warranty.
I don't have any options now.
I can unlock bootloader and flash custom ROM but the problem will still be there.
I can only hope that Android 10 will fix the issue.
If anyone can give any advice I would be grateful.

Categories

Resources