Related
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
Never had one so far. Running stock 4.2.2/Franco kernel nightly_110
-Edit- currently undervolted -75 mV.
just stop messing your phone up with stupid OCing and benchmarks... This issues are installed to protect the hardware from crashing... ( Red light of death... )
My phone just fine. never had this SOD.
Never had an issue on this device. On my old phone, dropping the min CPU speed too low would cause it a LOT.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
You don't have an option for unable to turn on phone without a reset: no blinking led. This is also a scenerio.
Please take a look here! http://forum.xda-developers.com/showthread.php?t=2195278
I've tried almost everything (wipe& re wipe , install stock ) and nothing seem to solve it.... most frustatin thing is when I hit "home" after playing heavly and ...bamm it goes black screen & hav to reboot pressin home&vol+
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Im using it now (customROM&UV) since it doesnt affect my issue.... I tried completly stock for 2 days and keep crashin... or at least on g.earth as I didnt install any app/game to be sure its not an app related issue.
Cant figure out what happens, it can play games w/o any issue, but sometimes when I change orientation it just goes black
PD: I dont hav enough time, but ill do a logcat to see what can possibily make it freeze
My case is not listed in the poll options:
- the phone went into standy, good battery, no calls, no high loads;
- LED was inactive totally.
- then I was unable to turn it on normally (only through reboot).
While in this state, trying to call the phone resulted in "long" tones, i.e., like the network saw the phone. The phone did not ring.
This happens with the latest stock firmware on the 2nd day of my use. Non-reproducible. Phone returned.
Would be delighted to learn if that's a hardware or software issue
Not necessarily SOD but experienced extreme battery drain under these situations
1- Charging via USB and left phone connected after PC shut down.
2- Charging via Wireless Charger left it on the pod.
In 1st ASA pc is shut down
and
In 2nd ASA Phone charged completely , as I suspect the charging process goes backwards ! It someone drain current from your battery to the power source.
AFAIK none of these issue are positive with normal good old AC charging. However you can still use a workaround by using the app called "Safe Charge"
This is my experience
MY nexus 4 is not going into sleep mode..i am on android 4.3 ..sometimes it goes into deepsleep perfectly and then suddenly it just doesnt sleep .. i checked wakelock detector and saw that it isnt going into sleep mode ..i checked better battery stats and power manager service is the one keeping the device awake .. then i went into battery and saw that android os is keeping the device awake! when i reboot the device then it goes into sleep mode properly but then again randomly it stops sleeping ... some1 plz helpp .. its causing too much battery drain..
the bbs log file is attatched
I hav uploaded some screen shots too but they are not the ones with the bbs log ..they wer taken at a different time..
same thing for me too.
Cjshino said:
same thing for me too.
Click to expand...
Click to collapse
what is your android version and which rom?? rooted or not?
zerohunk said:
what is your android version and which rom?? rooted or not?
Click to expand...
Click to collapse
4.3 rooted, stock everything
try with wakelock detector or similar....
The statistics of default android battery gives no specific information
XaviCampos said:
try with wakelock detector or similar....
The statistics of default android battery gives no specific information
Click to expand...
Click to collapse
i tried wake lock detector .. it showed that the device is being held awake but in the wakelocks tab there was nothing that was keeping the device awake for so long
Do you have alarms or anything of sort? (it might matter)
Disable all syncs, try to off (most) of those chat apps like wechat and line etc(go to settings>apps force stop), wechat in particular drains quite a lot.
I don't use stock but mine is close to it but I deleted lots of bloats from TB.
I only leave whatsapp on.
Infact, try out using Airplane, if even in airplane the battery still sucks, try reflashing everything using bootloader.
the thread title says that your n4 doesnt go into sleep mode.. where do you have something showing this?? battery loss does not equal not going into sleep mode. have you checked if your device goes into sleep mode, or are you just assuming? use something like cpu spy to see if your device is going into sleep mode..
Indeed, try CPU Spy. I use unrooted stock 4.3 and mine deep-sleeps just fine.
Sent from my Nexus 4 using Tapatalk 4 Beta
simms22 said:
the thread title says that your n4 doesnt go into sleep mode.. where do you have something showing this?? battery loss does not equal not going into sleep mode. have you checked if your device goes into sleep mode, or are you just assuming? use something like cpu spy to see if your device is going into sleep mode..
Click to expand...
Click to collapse
this happened when i rebooted it .. it went into deep sleep perfectly for 2-3 hours after that and then after 3 hours it stopped going into deep sleep again even with screen off for 4-5 hours more..
here are some screenshots of my current batteery stats
zerohunk said:
this happened when i rebooted it .. it went into deep sleep perfectly for 2-3 hours after that and then after 3 hours it stopped going into deep sleep again even with screen off for 4-5 hours more..
here are some screenshots of my current batteery stats
Click to expand...
Click to collapse
those screenies tell a better story. 48% android os is way to high! it seems as it gets stuck doing something.
simms22 said:
those screenies tell a better story. 48% android os is way to high! it seems as it gets stuck doing something.
Click to expand...
Click to collapse
yess .. i dont know what to do.. will factory reseting solve it??
zerohunk said:
yess .. i dont know what to do.. will factory reseting solve it??
Click to expand...
Click to collapse
Since update I'm having the same problem as OP has. Reboot solves problem for a day or two, but it returns.
I'm at the point when I'm ready to try factory reset.
andrewf403 said:
Since update I'm having the same problem as OP has. Reboot solves problem for a day or two, but it returns.
I'm at the point when I'm ready to try factory reset.
Click to expand...
Click to collapse
yaaa evn i am looking for a solution
This is battery stats from the first day after OTA: http://imgur.com/Bn9B8FA
You can clearly see when device stop going to sleep, and Android OS drained battery for more than 11 hours.
When I saw this, I rebooted the phone, and next day everything was OK. Battery life was even better, than with 4.2.2. But after third day, Android OS was again on top of the list. Again, reboot had solved problem only temporary. Wake lock stats app does not show anything unusual. I'm runing stock not rooted firmware. If I do not find any solution, I'll just wipe it on weekend in hope it'll help.
@zerohunk @andrewf403
Hi, I was facing the same issue.
So did you guys do a factory reset? Did it solve the problem?
mlj11 said:
@zerohunk @andrewf403
Hi, I was facing the same issue.
So did you guys do a factory reset? Did it solve the problem?
Click to expand...
Click to collapse
I made a new thread with all the data, in hope that somebody could help figure this out, but two days and no one else posted there) http://forum.xda-developers.com/showthread.php?t=2392155
Nexus 4 is my main phone and I rely on it in my work very much, so I'm trying to postpone factory reset as far as possible. I think I'll have not very busy day on Thursday so I'll finally reset it and reinstall everything.
andrewf403 said:
I made a new thread with all the data, in hope that somebody could help figure this out, but two days and no one else posted there) http://forum.xda-developers.com/showthread.php?t=2392155
Nexus 4 is my main phone and I rely on it in my work very much, so I'm trying to postpone factory reset as far as possible. I think I'll have not very busy day on Thursday so I'll finally reset it and reinstall everything.
Click to expand...
Click to collapse
Hi, I just replied in your new thread.
delete.....
mlj11 said:
@zerohunk @andrewf403
Hi, I was facing the same issue.
So did you guys do a factory reset? Did it solve the problem?
Click to expand...
Click to collapse
factory reset did not solve the problem for me .. i am trying to find out what is the app/reason which keeps the device awake so that i can by any means avoid using it or something :/ .. but no one seems to have an idea .. can anyone atleast find out and let us know which app/setting or whatever is causing the phone to stay awake??
Hi.
I have been having very strange issues with my battery, and I hope that there are some people here who know about the hardware more than I do and might be able to help me.
First of all, the battery indicator is unstable, it can show me 49% of battery and suddenly tell me there is only 10% left. I am attaching a screenshot of my battery stats where those spikes are visible.
Or worse, the battery indicator might suddenly jump to 0% and make the phone turn off, then when I turn it on it shows that it has at least 25% left.
Second problem, I very often can't charge the phone. I connect the charger, and the notification LED doesn't light yellow, instead, the whole battery menu just disappears from the settings so I can't access it... And after a few hours it might begin actually charging, then the menu is visible.
Battery temp always shows -30 degrees celsius, or some similarly impossible temperature.
After trying to switch to a different kernel (from unleashed to hells core) and to a different rom (from purity to android L and liquidsmooth) I decided this is an hardware problem and bought a new (hopefully original) battery on ebay.
I installed the new battery. Now it does work a little bit better, but still, the problems persist.
Is there anything I can do, before buying a new phone?
It doesn't have warranty anymore, it's one and a half years old.
Thanks
Definitely battery failure. Replace the battery or buy a new phone
Sent from my Nexus 4
This is most definitely due to a faulty battery, so time to get a new phone. At least Shamu's release is right around the corner.
Hi
Thanks for your help.
I did replace the battery a few days ago, and the problem still persists. Which makes me think it's something else.
romitkin said:
Hi
Thanks for your help.
I did replace the battery a few days ago, and the problem still persists. Which makes me think it's something else.
Click to expand...
Click to collapse
I'd try comletly stock rom, and see if the issue persists.
Yup, stock ROM always first step, then replace battery. If it still persists, than it is most likely some other hardware issue that might not be worth it to replace.
Sent from my Nexus 4 using XDA Free mobile app
romitkin said:
Hi
Thanks for your help.
I did replace the battery a few days ago, and the problem still persists. Which makes me think it's something else.
Click to expand...
Click to collapse
Exactly same situation with my Nexus 4. Battery being replaced and it's not better. Just ordered a Moto X 2014 and waiting for it.
I tried the stock ROM. And it didn't solve the problem. Is there anything else I can check about the hardware before replacing the whole phone?
romitkin said:
I tried the stock ROM. And it didn't solve the problem. Is there anything else I can check about the hardware before replacing the whole phone?
Click to expand...
Click to collapse
Have you just flashed a stock rom, or completley restored the phone to factory settings using google factory images?
Serris said:
Have you just flashed a stock rom, or completley restored the phone to factory settings using google factory images?
Click to expand...
Click to collapse
I used a factory image, it deleted everything including my sd-card etc
romitkin said:
I used a factory image, it deleted everything including my sd-card etc
Click to expand...
Click to collapse
Hmm unfortunately this leaves me without any ideas. May ask how old is your phone and did you drop it previously?
It's one and a half years old, and well, I did drop it a lot.However, I always used a good case (ringke fusion) and I don't recall any recent drops prior to the time the problems started.
Ever since I flashed 5.0 to my 900V, my battery life has gone significantly down. Now this can be expected to some extent as I can no longer use Amplify to control NlpCollectorWakeLock (which is one of a few wakelocks going to town on my battery). One of the others is bluedroid_timer, which is part of bluetooth. I did some searching and I saw some other people with the same issue, but no answers. I use a Moto 360 on a daily basis, use bluetooth streaming in my car, and use bluetooth headphones at the gym, so turning off bluetooth isn't really an option. Bluesleep is another one that is spending a lot of time running. Anyone have any ideas? I've read a few threads where people mention this problem, but no one has posted any answers yet. Here is an album of my wakelocks.
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
MattE303 said:
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
Click to expand...
Click to collapse
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
MattE303 said:
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
Click to expand...
Click to collapse
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
https://code.google.com/p/android/issues/detail?id=87778
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
dirkdigles said:
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
Click to expand...
Click to collapse
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
MattE303 said:
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
Click to expand...
Click to collapse
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I did see that and I am a GasBuddy user. There was also mention of NFC, that was the first thing I looked at. Experimenting now with GasBuddy removed.
I'm not rooted so I can't check for individual wakelocks, I have to just run it for a while, then look at the "Awake" bar graph in the stock Battery app, so it takes while to see if anything changed. I really wish Google would give us the choice whether to let 3rd party apps see the detailed battery stats, locking that down made it so much harder to diagnose this kind of thing without root.
Glad you got yours sorted out!
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
ldeveraux said:
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
No idea, but it's mentioned on their Playstore page in a recent app update:
4.6.6
Get deals while you are filling up by turning on Bluetooth.
Click to expand...
Click to collapse
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
MattE303 said:
No idea, but it's mentioned on their Playstore page in a recent app update:
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
Click to expand...
Click to collapse
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
MattE303 said:
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
Click to expand...
Click to collapse
I started experiencing the issue with excessive wakelocks from Bluedroid_timer on my stock Nexus 6 about a month ago. Noticed my battery life dropped significantly as a result. Used Permission Friendly Apps to see which apps were using BT and if I happened to install any around the time this problem began. Only new apps indicating BT connectivity were GasBuddy and Netflix. No idea why GasBuddy needs BT but I'm pretty sure I installed it about the same time the wakelock issue began. Good to know someone else saw the same thing. Just uninstalled it and waiting to see if the wakelocks stop.
Hey guys
recently i bought a Bluetooth speaker and connected it to my A3 (300FU), but now when i check the battery stats to see what is eating my battery it only shows Bluetooth (not even screen, wifi etc) [ see screenshots]
i deleted dumpstat/logcat and also wiped cache partition but it didn't help.... is there an obvious solution or am i missing something here?
*running stock Marshmellow ROM
Any help would be appreciated
i think a few users have it confirmed, Bluetooth seems to be a major drain in MM for A3FU.
i can only advise to update to a newer build. what build are you btw? do a screenshot of About in Settings
i didn't have a problem until recently, when i paired my device with the bluetooth speaker.
should i reset network settings?
I've attached the screenshot.
all users who reported BT issues came from first BT pairing, just like you. and they were all on PH3.
It's a rom bug that you can only hope they notice and fix, and then it's up to you to try the new builds and see if there is any change.
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Bffn45 said:
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Click to expand...
Click to collapse
Quite sure bluetooth is being the idiot here.
I do not own this device but I had this issue on my other A series device and it's because of the Nearby Device Scanning in Other Connection Settings.
This feature is included after updating to Mashmallow and it causes your Bluetooth to be always ON if the feature is ON(By default its ON so go and turn it off).
BTW, how did you get the battery graph on Mashmallow? Didn't Samsung removed it since Lollipop? I can't access it on my device, my sister's J7 and my mom's S7 edge
conanDO98 said:
I do not own this device but I had this issue on my other A series device and it's because of the Nearby Device Scanning in Other Connection Settings.
This feature is included after updating to Mashmallow and it causes your Bluetooth to be always ON if the feature is ON(By default its ON so go and turn it off).
BTW, how did you get the battery graph on Mashmallow? Didn't Samsung removed it since Lollipop? I can't access it on my device, my sister's J7 and my mom's S7 edge
Click to expand...
Click to collapse
Nearby device scanning is turned to off, should i reset network settings? maybe that way it will correct the readings
For the Battery stats --> Settings -->at the System section search for Battery--> Battery usage, or maybe just use S finder
I've got the same issue. Untill I switch Bluetooth on, normal battery stats, as soon as I do, everything is reported as Bluetooth - no screen use, now Android System use. "Nearby Device scanning " option seems to have no effect.
I also had this issue when I upgraded to MM (build CPI1)... even tried factory reset, but problem persisted.
I think it's a bug in the Samsung ROM, no way to get rid of it without a software upgrade.
Same "bug" with my A300FU.
Tried everything...
Installed earlier firmware (rom) with odin (in which I did not have the exaggerated Bluetooth usage)
Installed latest firmware again
Full wipe
Install latest firmware
After installing each rim I have the high Bluetooth usage from the start without installing any app
My colleague with identical A300FU did have the same with the previous 6.0.1 rom, bit after OTA update it dissappeared on his device
So it has to do something with my setup....
According to the battery gauge Bluetooth is using approx 4mAh PER SECOND
Also explored the option to modify the power profile.xml in the framework-res.apk but to no avail (keep getting bootloop)
*frustrated*
Anyone an idea?
Flashing cm12 or cm13 and then reverting to stock 6.0.1 is also not a solution to this issue......
My Wife's Galaxy A5 (2015) also has this bug. All 6.0 firmwares - even latest from January. So stupid - I can't belive that they can't see this bug. There is no battery drain - only bad statistics. But its very anoying because You cant check how long screen was used etc. Scaning of near devices is disabled too - didnt help. Dammed.
Have You find any solution?
I never looked at that screen before, but I recently noticed this too and it freaked me out at first. After testing it tho, I was gonna post and ask other peoples' experience, but then I found this thread.
What I get is that initially my batterystats are recorded normally, but then when i turn on bluetooth, even if it's for 1 second, all stats disappear and bluetooth appears in that list with what appears to be a huge (and impossible) drain.
Bffn45 said:
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Click to expand...
Click to collapse
PlutoDelic said:
Quite sure bluetooth is being the idiot here.
Click to expand...
Click to collapse
I normally have bluetooth on, and I don't actually notice my battery draining any faster than when it's off. Also, if the computed battery usage on this was accurate on my phone, I would run out of power in a matter of seconds. So it's definately a bug in the battery stats.
aerogenes said:
After installing each rim I have the high Bluetooth usage from the start without installing any app
My colleague with identical A300FU did have the same with the previous 6.0.1 rom, bit after OTA update it dissappeared on his device
So it has to do something with my setup....
Click to expand...
Click to collapse
I beg to differ! I flashed lollypop and the problem disappears then, but it's there on both marshmallow builds for our country, even when starting fresh after a data wipe.
Which roms have you tried? And what rom is your colleague on after the OTA that fixed it? Buildnumbers would really help
For me: U1CPH3 and S1CPL1 both have this issue
It seems, for me at least, that after the December OTA security update the bug dissappear and i am now getting normal battery readings.
Bffn45 said:
It seems, for me at least, that after the December OTA security update the bug dissappear and i am now getting normal battery readings.
Click to expand...
Click to collapse
Al right, thanks! Latest rom/update for my country is from december too, but i still have it.
So i'll try downloading a jan 2017 rom for a different country and see what happens
Update:
Installed the S1CQA2 firmware, which should be the latest, and the bug is still there. Just with less unbelievable numbers and it takes a little while longer for it to make all other stats disappear.
Update2:
Looked into the powerprofiles.xml too, but the marshmallow one (which has this issue) is identical to the lollipop one (that doesn't have this issue). Also all there is to edit in there is the amperage usage for actual A2DP, but according to this https://source.android.com/devices/tech/power/values.html a lot of battery usage is just pushed to the batterystats service by the controller.
Now wondering what files are associated to the bluetooth controller. Simply replacing the bluetooth.apk from a different rom where this is working does not solve it either.
After some more digging, and succesfully porting the S5 bluetooth files to my phone, i found out that the samsung S5 suffers from this issue as well andthus the issue was still not fixed
Also, judging from other posts in other forums it appears the Note 4 has it too.
Therefore I think it is a touchwiz bug, and I am clueless on what to try anymore.
This is my third post in this thread in a row but editing my previous posts here might make the new info go unnoticed...
So this is just a heads up that the italian A300FU1CQC2 firmware has finally fixed this bug for me! :victory:
I have had bluetooth on (idle) all day now and it doesn't show up in battery stats at all.
great effort mate, really love it when people monitor the release stream .
Carpe-Dimi said:
So this is just a heads up that the italian A300FU1CQC2 firmware has finally fixed this bug for me! :victory:
I have had bluetooth on (idle) all day now and it doesn't show up in battery stats at all.
Click to expand...
Click to collapse
Thanks for the heads up... I've just flashed the update, and I can confirm that also for me this new firmware solves the BT issue. :good: