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:
Related
So I was trying to get the new 2.3.20 firmware and I went to the Archos website. But it looks like there was a new firmware posted this morning. 2.3.26.
I don't know how to direct link, but i'll try.
http://update.archos.com/8/gen8/gen8_2.3.26/firmware_archos_android_gen8.aos
Version 2.3.26 - April 21st, 2011
Wi-Fi: fix cannot scan on an access point above channel 11 regression
Phone tethering: fix TCP/IP header compression setting crash
System stability: avoid Android reboot in case of missing audio
Media library: fix media libray not updated on hard drive based A70
Notification: decrease low battery notification volume
Application: attempt to solve Pandora application not able to switch songs
Application: solve music lag in applications using OGG format
Bluetooth GPS: increase compatibility with 3rd party applications
Display: avoid white/black screen happening sometimes when switching back the display on
Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.
Techngro said:
Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.
Click to expand...
Click to collapse
Not that much of a noob, you posted the link to the firmware that should end my buggy horrors
Thanks jknut for the changelog
Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha
sw6lee said:
Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha
Click to expand...
Click to collapse
I just followed Steps 2, 3, 4 of Chulri's post. Chulri already has the new files for "fw 2.3.26 +rw" for Step 3. I like the optional Step 4 because I don't have to worry about holding down the volume button everytime I boot to get root.
Hi,
Has somebody tested this new release?
I updated to version 3.2.20 last week and I was very happy when I realized that cinema plugin was not required to play all the formats which I was not able to before the update (AAC, AC3, MPEG2, etc)
Can somebody confirm if this has not been "fixed"?
Thank you.
Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.
toyface said:
Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.
Click to expand...
Click to collapse
I just noticed the update when I went to the archosfans 2.3.20 bugs thread to report wifi drop powersave disabled while running tunein radio...
OTA update went fine, just waiting for A43 to charge up, then I'm going to do the A32 as well...
[EDIT]
Power LED blinking -> UI batt meter (and About Device) say 98% charge...
had this once with 2.3.20 showing 97% when LED blinking but next charge and thereafter showed 100% when LED blinking...
[/EDIT]
I had this Problem from the first day.
LED blinks and the battery show around 90%.
If i unplug the power the status goes to 98-100%, most 100%.
If i reboot the device with plugged power, the status is 75-90% after restart.
Sometimes the status falls to 87-91% if i plugged the power in.
I can live with it, but it is annoying.
did they remove bluetooth PAN tether ? I had dun/pan option while setting up BT tether with 2.3.20. but now no more that option. the probken for me is, i am using cdma phone(bell htc touch) but with BT DUN the Archos cannot dial CDMA number #777. I set bell APN (pda.bell.ca) it's not working. Actully even if it works I worry about it because it may charge me more.
Before with 2.3.20 , it worked perfect with BT PAN and my phone set to Internet sharing.
This update cleared up my waking-up issue.
It's pretty much an instant on now after the monitor idles off. Before, (after being off for more than a few minutes) it was a crap-shoot as to whether or not the screen would come on and I often had to fight with it and double, triple, quadruple tap the power button to get things alive. No longer.
still reboot cycles problems when charging the 101..problem started with these last 2 updates.
twit.tv app FCs all of the time with this fw...
I wonder why they released this one OTA as it seems to be more broken than .20 was...
youtube and many other flash video played in the browser hangs after about 15 seconds or so. Soemtime this causes the whole system to freeze requiring forced reboot.
This is the worse build so far, my A70 was most stable at 2.1.08.
Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.
Techngro said:
Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.
Click to expand...
Click to collapse
As a matter of fact I did an Android reset to get away from some of the problems I was having with bootloops and such. This has helped with the general performance of the 101, which I'd say is down to the 64mb swap file I now enjoy.
I did have a couple bootloops until I enabled a lock screen pattern unlock and I have now experienced nothing but fairly good performance
It seems that 2.3.26 is different from vesions before
Need more language for External Keyboard Layout such as Thai
jakkrith said:
Need more language for External Keyboard Layout such as Thai
Click to expand...
Click to collapse
You'd probably be better off posting in the archosfans.com forum's bug list thread for 2.3.26 as Archos employees actually monitor that site and have actually even started some of the buglist/fw release threads... i.e. I'm not sure that they're even aware of the xda-devs gen8 section and even if they were would they bother to read it...
Hello guys, a long time ago now before the official 4.4.2 KK was available for my SM-N9005 I flashed a leaked Polish one. Before the flash my phone was working perfectly, no problems at all. After flashing the firmware I noticed my battery was draining at more than 1 percent a minute and it was pretty unhelpful to say the least, after looking at my battery info in settings says that NFC was using 63% of my battery !!! Now we all know this cannot be right ?! So I tried to disable it but couldn't as it was greyed out. It was stuck on and did not work at all. I waited quite a while and when the official KK firmware was released i flashed it but still no NFC. Now I have updated my phone to Lollipop and my NFC still does not work. Have you guys got any suggestions on how to get this working again ? It's definitely not a hardware fault as it has happened to my note and one of my family members notes after installing this firmware.
Many thanks
I have attached a screenshot that quite clearly says NFC is off although it is actually 'on' and not working. It is greyed out and cannot move it
Maybe something wrong with the nfc chip in your battery? Buy new battery (ebay) and see if that helps?
Sendt fra min SM-N915FY
Already thought of that, thanks anyway though
I've seen this happen on the S5, too. Very annoying problem, nobody seems to know if it's a software or hardware problem.
Have you tried doing a 30 seconds battery pull, and then wiping the cache in recovery? (Dalvik too, if you can.) Also clear out the cache under Settings > Storage. Let it sit for a while and see if it's off. If not, try another battery pull and see if it's off when you turn it back on. That process worked for my S5. (Which has never had any other firmware than PHN.)
Hello! The last OTA update was 12.1-YOG4PAS7DF and everything about it is fine except for 1 thing, the heating issue (well, for me). I don't really know how hot it is but when I'm using wifi for facebook, youtube, etc. , the screen gets warm easily. Anyone got the same issue as mine? Maybe an update will fix it but it's been too long. I'd like to flash some custom roms but I got this wifi connectivity problem with my old phone when I flash a cm13 rom and I'm scared it might happen again.
That's the last i've got too. With last security patch 1 April 2016. I can relate to the heating problem.
But now, when i go to SystemUpdates, i get this message: "WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options". I'm wondering if this will uphold future OTA updates.
Cheers, Miche
MTeeuwen said:
That's the last i've got too. With last security patch 1 April 2016. I can relate to the heating problem.
But now, when i go to SystemUpdates, i get this message: "WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options". I'm wondering if this will uphold future OTA updates.
Cheers, Miche
Click to expand...
Click to collapse
AS say, you need to enable recovery update on Developers options.. If not have DOpt enabled you need to go Settings, select About phone, Tap the Build number entry seven times. On the seventh tap, you will be notified that "You are now a developer."
Regards,
VGC
vgacitua said:
AS say, you need to enable recovery update on Developers options.. If not have DOpt enabled you need to go Settings, select About phone, Tap the Build number entry seven times. On the seventh tap, you will be notified that "You are now a developer."
Regards,
VGC
Click to expand...
Click to collapse
Do you mean that if i don't, i won't get any updates? Is there any other reason i need to be a developer (as a regular user)?
kenot600 said:
Hello! The last OTA update was 12.1-YOG4PAS7DF and everything about it is fine except for 1 thing, the heating issue (well, for me). I don't really know how hot it is but when I'm using wifi for facebook, youtube, etc. , the screen gets warm easily. Anyone got the same issue as mine? Maybe an update will fix it but it's been too long. I'd like to flash some custom roms but I got this wifi connectivity problem with my old phone when I flash a cm13 rom and I'm scared it might happen again.
Click to expand...
Click to collapse
Not only do i have heating issues but my wifi indicator goes funny showing some kind of breaks between it like an exclamation mark and i would have to use 4g instead because wifi wont work. This phone was perfect before the last 2 - 3 updates now, i am contemplating a wipe and see if that helps. i would use one of the custom roms, but i have apps that are not rooted firmware friendly like the barclays app which is very important to me.
I also facing same issue when using wifi
Mobile so heating problems hw to control heating problem and net connect when mobile is so heating
I have 2x ZUK Z1's both running on stock COS 12.1 latest version and none of them are having heating issues or unstable connections...
I am also facing the same problem my phone getting heat without any use. and battery also consume for the same ..please help out me for the solving heating problem.
I'm on Marshmallow 6.0.1 DPE6. I've just done a factory reset to try to resolve this issue, but with no success.
In my Battery Usage under Bluetooth I get a reading for 'Time On' like the attached image. Even though bluetooth had only been on for 1 hour, it's giving a very inflated 'Time On' of over 1 day. This will continue until Bluetooth shows as having been on for many days, even though it has only been a few hours.
I have a Moto 360 (2015) and a Sony SBH52 Headset attached via Bluetooth. I've tried connecting only one or the other, but it doesn't make any difference. I have no other problems, except for the inflated 'Time On' reading in Battery usage stats. Interestingly, I have GSAM Battery Monitor installed, and it gives a correct reading for Bluetooth Time On.
Just wondering if anyone else has the same problem, or if anyone has a solution. I'd like to know if this is a firmware bug, or if it's just me experiencing it. Thanks!
I too did a factory reset which fixed a lot of problems I was having. As for the Bluetooth, I have the Asus Zenwatch 2 and have not experienced what you have stated. Maybe reset the watch and headset
Sent from my SM-N910V using Tapatalk
dabombcra said:
I too did a factory reset which fixed a lot of problems I was having. As for the Bluetooth, I have the Asus Zenwatch 2 and have not experienced what you have stated. Maybe reset the watch and headset
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Thanks for your comment. Sorry, should have mentioned that I already reset everything when I factory reset the phone. Perhaps this is specific to the N910C Exynos ROM 6.0.1 DPE6? I see DPF6 is out in some regions, so I guess I'll wait for that and see if it fixes it. No big deal anyway, as it doesn't seem to be affecting anything - just my OCD
i have the same problem with 910F.
Do you find a solution?
zip88 said:
i have the same problem with 910F.
Do you find a solution?
Click to expand...
Click to collapse
Nope, now on DQE5 (as of today) and I still get this odd reading. My phone uptime at the moment is 3 hours, but Bluetooth is showing over a day in battery stats (see attachment) - doesn't seem to have any adverse effects though as I still get 5+ hours Screen on Time and the actual battery drain from Bluetooth is pretty minimal. Just a weird glitch
for me is not like this.
The battery stats says 184mah and seems to have effect on my battery drain
zip88 said:
for me is not like this.
The battery stats says 184mah and seems to have effect on my battery drain
Click to expand...
Click to collapse
Hmmm, sounds like it could be a different issue then. Sorry, as you've done a factory reset etc I'm not sure what else to try - unless you have a rogue app or Bluetooth device that is causing the problem.
Kinsman-UK said:
Hmmm, sounds like it could be a different issue then. Sorry, as you've done a factory reset etc I'm not sure what else to try - unless you have a rogue app or Bluetooth device that is causing the problem.
Click to expand...
Click to collapse
nope, because it happens immediately after the factory reset.
Maybe some "samsung" updates or play services..i don't know.
I will try to install another firmware
it happens randomly without any warning, once the battery percentage reaches x6% (16,26, 36, 46,...etc) it shows low battery warning (orange bars on top and bottom) and just turn off, (it's currently showing charging because i connected the phone to a charger to turn it on, otherwise it would turn off again once turned on), this happens more commonly and fast when using the camera or any app the uses the camera as its main source like Instagram and Instagram stories, Snapchat)
SnoopDoge said:
it happens randomly without any warning, once the battery percentage reaches x6% (16,26, 36, 46,...etc) it shows low battery warning (orange bars on top and bottom) and just turn off, (it's currently showing charging because i connected the phone to a charger to turn it on, otherwise it would turn off again once turned on), this happens more commonly and fast when using the camera or any app the uses the camera as its main source like Instagram and Instagram stories, Snapchat)
Click to expand...
Click to collapse
There are several threads about a battery issue like this one in Q&A section https://forum.xda-developers.com/moto-g4-plus/help/sudden-shutdown-t3842810
Maybe you have a similar issue, but not with complete shutdown or random reboot
SnoopDoge said:
it happens randomly without any warning, once the battery percentage reaches x6% (16,26, 36, 46,...etc) it shows low battery warning (orange bars on top and bottom) and just turn off, (it's currently showing charging because i connected the phone to a charger to turn it on, otherwise it would turn off again once turned on), this happens more commonly and fast when using the camera or any app the uses the camera as its main source like Instagram and Instagram stories, Snapchat)
Click to expand...
Click to collapse
Maybe a reset would help or you can try flashing Stock ROM/Custom ROM whatever you are using again.
Heeth21 said:
Maybe a reset would help or you can try flashing Stock ROM/Custom ROM whatever you are using again.
Click to expand...
Click to collapse
i'm not risking a reset or flashing a rom (i'm using stock rom) and have my phone damaged, because yea i've seen people doing that they lose features and issue is not solved
SnoopDoge said:
i'm not risking a reset or flashing a rom (i'm using stock rom) and have my phone damaged, because yea i've seen people doing that they lose features and issue is not solved
Click to expand...
Click to collapse
What features have you seen people losing which have not been solved yet?
A reset can always help to determine whether its a software issue or hardware issue.
Heeth21 said:
What features have you seen people losing which have not been solved yet?
A reset can always help to determine whether its a software issue or hardware issue.
Click to expand...
Click to collapse
well... they lose fingeprint option, they lost IMEI numbers, the phone becomes "uncertified" on play store, not receiving future updates, going to back to a way old security patch (just yesterday i saw someone reset their G5s device and the security patch went back to Nov 2017), and i've seen many people done factory reset to fix battery issues but it's not solved
SnoopDoge said:
well... they lose fingeprint option, they lost IMEI numbers, the phone becomes "uncertified" on play store, not receiving future updates, going to back to a way old security patch (just yesterday i saw someone reset their G5s device and the security patch went back to Nov 2017), and i've seen many people done factory reset to fix battery issues but it's not solved
Click to expand...
Click to collapse
Fingerprint problem is seen after using blankflash (idk about any other fingerprint related issue) and is fixed for most of the users. Blankflash needs to be used after getting device hardbricked i.e while trying downgrading bootloader of Stock ROM and then using OTA.
Downgrade is never ever recommended.
IMEI problem can be fixed for every device (unless they do something stupid like restore some other device's "persist" in their device without a copy of their own "persist" which is unique to every device)
Backing up efs via TWRP (which in turns backs up persist too) is a notice that every dev has given to follow, its just a consequence of not following instructions.
Play Store uncertified is while using Custom ROMs and if its while using Stock ROM (have been for a very few cases) a Stock ROM flash via fastboot resolves it.
I do not know about the last two problems which you mentioned, but Security patch changes by flashing a ROM (Stock or Custom)
People who have done factory reset but it didn't resolve battery problem, well a Stock ROM flash via fastboot can always help and if still the problem continues, then its a most probably a hardware issue.
Thank you for letting me know about these, I didn't knew about security patch change on factory reseting, and also sorry if I sounded rude earlier, it was intended