Database Info

"Plugin Sample"

What is "plugin sample" under partial wake usage? It kept my phone awake for 26m under the sensor...

Good question. It seems to be destroying my battery. Some investigation is definitely needed.

I think this deserved a bump.... still no answer as to what it is, and its definitely a battery killer.
I'm having the same issue... I usually can squeak out 2 days on a charge during the week since I'm mainly on Wi-Fi, but today my battery died at work after only 11 hours off the charger. Number one killer was "Plugin Sample" which used 56%. Thats absurd. I DL'ed a task manager to see what was up, but I didnt see anything out of the ordinary.

My wife's phone has the same problem...can't seem to find the fix for it. I rooted her phone to the same rom/kernel as mine and it's still there draining the battery.

Angry Birds
Out of curiosity, do all of you have Angry Birds installed, and played it recently? [this does apply to the thread]

I just discovered this problem today. I don't have Angry Birds and never have, so it's probably not that. I did notice that the process was labeled as android.process.acore when I first opened the battery use list, then quickly changed to plugin sample.
I've seen something called .acore force quit before, maybe on my old G1 or maybe on this phone. It seemed to require a reloading of the home screen icons.
Does anyone else on this thread use Launcher Pro?

Same Problem Here!!!!!
Could someone PLEASE help those of us with this problem!?!?

i use Launcher Pro and have plugin sample on my phone.
i cant stop or uninstall the item and it also has some hardcore permissions, which is why im searching here looking for what its used for.

Just a thought, would it be the plugin option on the browser? I read somewhere that to save battery you should change that setting from the default "always" to "on demand."
Sent from my HTC Glacier using XDA App

hah2110 said:
What is "plugin sample" under partial wake usage? It kept my phone awake for 26m under the sensor...
Click to expand...
Click to collapse
This app has one function that I know of:
It clears your missed calls notification.
Found it by accident after I removed trust in LBE Privacy Guard for a bunch of random apps and noticed my missed calls stopped dismissing.
Found this app in the logs being constantly denied access.

Battery Problem [CM7]

Hi everybody!
So I am using CyanogenMod 7 Beta5.1 And I'm having huge battery problems...
It's draining abnormally fast (30% lost during night).
It started to happen when I got problems with my Defy and flashed 3.4.3-11
And now updated to 3.4.2-117.
Before these problems it usually drains only 3% during night!!
Also everytime I boot my phone, when it's completely booted I hear the camera sound (when you open camera app,it makes a physical sound).. It never happened before...
I overclocked my phone to 1100Mhz but I don't think it really affects the battery (when screen off it's set to 500Mhz)
Please help me!....

I was having that problem and I turned fast boot off and it solved the problem for me. The phone doesn't really shut down all the way if fast boot is on.
Sent from my Desire HD using XDA Premium App

schultzy001 said:
I was having that problem and I turned fast boot off and it solved the problem for me. The phone doesn't really shut down all the way if fast boot is on.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
fast boot? The one from setvsel?

schultzy001 said:
I was having that problem and I turned fast boot off and it solved the problem for me. The phone doesn't really shut down all the way if fast boot is on.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
how can u shutdown fastboot? wanna give this a try...

schultzy001 wrote
"Sent from my Desire HD"

um... a new thread? really?
by the way, i have this problem too since beta 1.. i don't know why..
but i still like it because CM7 is so fast without OC.
i try to compare froyo and CM7, with same apps and same apps settings,
CM7 lost the battery faster than froyo, even when in flight mode.
the strange one is, even the memory usage is so low on CM7 (no motoblur crap),
but why battery still drains so fast..
in battery usage statistics,
on CM7, it shows that "Display" is the one who responsible drinking so much juice (60% and the other is just 3-10%).
on froyo, is not the "Display" which responsible drinking most of the juice, it is "Cell Standby".
i thought gingerbread should have good battery management, and the battery should last much longer than froyo.
i'm sure it is a bug on CM7 for Defy.
but whatever, at least we have a Gingerbread on Defy from a great dev like Quarx.
while motorola working so slow on releasing froyo with its motoblur crap.

Hi guys,
I'm having this issue too, and i note since a few days ago. I don't know why, but my Defy is sucking his battery too fast. Could it be a bug ?

it's a little bit difficult to follow the bugs and the solutions in a huge thread like the other one. so i think that this that could be a mayor problem for all of us should be treated in a differente thread.
I use Motocharge since 1 day to follow how it discharge during the day.
I say it in the other thread, the phone loose a lot of battery when i don't touch it. sometimes it loose like 5% in 15mins and i don't touch it. maybe it doesnt sleep well, i don't know..
I hope that Quarx can solve this, because in the other betas of him i don't have the problem. only in the 5.1.

battery draining
I think It´s a bug, because I used before BETA 5.0 and without any battery life was almost 3 days in normal use, bur now with BETA 5.1 only two days or less.
By the way I´d proved with 3 or 4 diferent roms, but the same result.
But I´m sure Quarx will deleted this bug in the next version

same problem for me,but b3 and b4 is ok
Sent from my MB525

apart from low battery life.....i noticed substantial increase in battery temp..normally its 32-34 deg cel.....but wid CM7 it raises to 42-45 deg cel.....waiting for a solution so that i can come back to CM7...

I use Toggle 2G/3G to switch to 2G when phone goes to sleep. I set wifi to never sleep and use it as much as possible over 3G. I also set brightness levels long time on 16 so that in the shadow I always use just a little energy. This way I almost get double battery live.
+ it's better for battery to charge every night, empty or not, and let it go lower just occasionally.
Link to Toggle app:
http://forum.xda-developers.com/showthread.php?t=739530

yes, this issue is really annoying, 30% battery drain overnight.
something is definitely running unreasonably... hope find it.

I think it depends upon what "type" of defy u have. My battery that only used to last for 12-14 hours in eclair now went for 2 days last 2 charges.
Also depends upon how many widgets and apps u running... hard with mobile phones to judge battery as so many independent variables.
Sent from my MB525 using XDA App

OK Guys, this is an old thread, but I think it should be deleted or at least people should read this before registering this thread in their mind:
The battery drain 'issues' were almost always due to two things:
1- For the beta 6 version or older of CM7- there was a bug with the auto-brightness which was heavily stressing the cpu and making the system lag badly - hence: the battery drain. To fix this: you have to stay on auto-brigthness. So just make sure that the auto-brightness box is checked and ON. Additional info: some users also complained about the 4 action buttons (menu, home, back and search) not lighting up ---> fix: un-check auto-brightness and re-select it: done!
2- Users did not set their Network baseband properly. Fix: use the Defy Baseband Switcher application and select the newtwork that applies to you. If you don't do this, your phone might have signal reception (phone and sms) but it will use more power to communicate and get a proper lock to your phone service provider.
I don't know what is the exact build # that brought the Defy Baseband Switcher (as far as I can remember, CM7 beta 4.1 had it) but all the 'newest' CM7 will have it anyway.
And if you want to further decrease your battery consumption, you can still do it like this:
- use the bootloader cpu settings: OC'ing and governernor type to change the cpu speed. [From CM7 default 1000MHz to the Defy's stock 800MHz] and change the governor type from "interactice" default to "on demand" [OK: I'm not sure about governor change will improve or not but that is the Froyo's default I believe].
- install SetVsel to underclock --> by lowering cpu Vsel upon the 3 cpu frequencies. Do some reading; you might need to uncheck its "[email protected]" option AND also have Milestone Overclock installed for it to work properly.
- USE a recent nightly (post May 29th: there was a possible problem with custom recovery backup restoring prior to that) and you will be able to set your screen display brightness as low as you want [fix the bug described in point 1- above].
- use DroidWall and/or the CM7 built-in applications' permissions control to block some apps' access to internet and networks. BE WARNED though: changing permissions CAN make an application stop working or create problems - don't submit bug reports if you do that.
- Avoid high usage of apps that drain battery quickly (TuneIn radio is power-thirsty one that comes to my mind...) and apps that have to create catalogs and thumbnails (ex: Photoshop, Titanium Backup, Gallery, ...)
- If possible: use 2G network only, disable data synch, auto updates of apps and social networks.
- set your WiFi sleep policy to "Never" [while in Wi-Fi settings, press menu button/ Advanced] and avoid frequent Wi-Fi ON/OFF switching.
- Lower your display brightness and switch that screen off at any chance you got!
There are many other ways I'm sure, but those are the main ones anyway...
I've seen high temps yesterday on my Defy, but I later realized that I forgot to re-set my Baseband after a CM7 nightly install... It 'could' also happen when a (background) service goes "beserk" and overload the cpu: absolutely not necessarily related to CM7 --> faulty apps and bugs happen... Just stop and clear the cache of that app and/or reboot your phone and problem should be gone.
CM7 is now really stable; a VERY FEW little hickups remaining still (like with the camera, but negligeable), but the large amount of new user controls that it brings clearly overcomes the 1 or 2 minor bugs left --> IMO, just having control over each and every applications' permissions justifies forgetting about using Eclair and Froyo. Problems in CM7 are being actively sorted out and new user controls and other useful options are added in almost daily manner through the nightly builds.
I'm categoric: on CM7, I now have more control over where my battery juice goes that I've ever had on Froyo....
So please stop alarming people with high battery usage drainage on CM7 and give it a try by following the right proper steps; I'm sure that you won't regret it.

marhensa said:
um... a new thread? really?
by the way, i have this problem too since beta 1.. i don't know why..
but i still like it because CM7 is so fast without OC.
i try to compare froyo and CM7, with same apps and same apps settings,
CM7 lost the battery faster than froyo, even when in flight mode.
the strange one is, even the memory usage is so low on CM7 (no motoblur crap),
but why battery still drains so fast..
in battery usage statistics,
on CM7, it shows that "Display" is the one who responsible drinking so much juice (60% and the other is just 3-10%).
on froyo, is not the "Display" which responsible drinking most of the juice, it is "Cell Standby".
i thought gingerbread should have good battery management, and the battery should last much longer than froyo.
i'm sure it is a bug on CM7 for Defy.
but whatever, at least we have a Gingerbread on Defy from a great dev like Quarx.
while motorola working so slow on releasing froyo with its motoblur crap.
Click to expand...
Click to collapse
Display instead of cell standby showing up first in battery consumption means that Froyo (or CM7) uses less battery. The display just stayed the same of course, unless it's tuned brighter, the percentage increased because it's a relative measurement.

260-270mA drain while idle

Been experiencing a high battery drain past few days on both VirusROM and BAMF 1.6.3. According to CurrentWidget it keeps at 260-270mA most of the time with screen off. On it jumps up to 400-500mA pretty much right away.
The strage thing is that I haven't really changed anything and have seen 40-60mA draw while idle before.
Partial wake usage mainly lists Android System, everything else has really short duration times.
Any idea how I could track down what's using so much power during idle? Have very few apps installed and all that are installed are pretty standard I think.
Here's a list of what I have:
Where's my droid
Appstore (amazon)
ShootMe
Solo Lite
Facebook
Fandango
Go Launcher EX (maybe this? was updated recently)
Calendar (widget for EX) as well as two themes for EX
Google Maps
Gmail
GO SMS Pro and a theme
Foursquare
Screen Off and Lock widget
ROM Manager
CurrentWidget
SoundHound
Ginger keyboard
Shush!
ColorNote
gTabSiMiClock
Ringer Volume
Retro Cam+
SMS Backup
As far as general settings, Wifi and GPS are always on as well as syncfor gmail and FB, but then again they were since day one and I've seen idle draw at 40-60mA always before.
Thanks for the help.

Have you changed your wallpaper recently?
Mine used to be orange with flames, and it used to do the same thing. Since then, I changed it to a space themed wallpaper that's mostly black and dark blue . My current power usage has gone down significantly to idling at 30 unless I use it!! Try that!!
You could also recalibrate your battery if you haven't done that since ROMing, I did that at the same time too, but I don't think that did it.

Darker wallpaper hmm. Well I changed it to something darker though it doesn't make sense that it would drain battery differently while screen is off, but I guess it doesn't have to make sense heh.
I did use all kinds of wallpapers before even live ones and never really seen such high idle use before. Will try to drain battery and recharge as I haven't done that in a while.

Going to try and wipe everything and just install bamf 1.6.3 along with currentWidget and see what happens I guess. And if issue is fixed will slowly add apps one at a time to try and find which one causes the problem. It also possible that TitaniumBackUp is causing the issue as lately I was using it to reinstall all apps instead of going to the market and doing it that way.

make sure you re calibrate your battery after ROMing, if you haven't done that already. That fixed all my idling power consumption (and charging) problems

Try applying airplane mode. That will help you see if your radios are eating battery.

Reinstalled the rom and while I didn't want to install any apps market restored everything I had, but I did not use TitaniumBackup this time and so far everything is fine. Idle is back down to 40s mA.
I guess was some glitch in the backups. Because everything else is the same.

[Q] Battery history sensor usage

I've had my G2X close to a month now and the battery life hasn't been very good. After using the LG update tool to go to 2.3.3 I noticed Tasker was using 25% of the battery, about the same as cell standby and phone idle. I installed CM7, nightly 99 and noticed the same behavior. I never noticed Tasker using much on my Nexus One, so I started looking through the battery history and noticed the sensor usage stat being really high for Tasker. I turned off the one profile I had that would have been causing sensor usage and didn't notice a drop until I rebooted.
I noticed the same behavior out of the Camera app and Dialer. Today I saw the same behavior out of the Kindle app. Anyway I tried to do a little more scientific experiment and opened Google Sky Map and let it load used it a few seconds and got out of it. I put the phone to sleep and let it sit for 30 minutes, I came back and checked and the sensor usage of Sky Map was 15 minutes. I then opened a task killer and stopped Sky Map and put the phone to sleep for another 10 minutes and saw the sensor usage was now at 20 minutes. Anyway it seems after any app uses the sensors, it continues to use them until I reboot. Has anyone else noticed this behavior? Is there a known way to fix it?

Update: I noticed this only happens when auto rotate is turned on in display properties. I just did a quick test where I had auto rotate turned on, I started the Kindle app. When I exited, I noticed the sensor usage was still climbing. I turned auto rotate off, then started Google Sky Map, when I exited it, the sensor usage stopped climbing. However, the sensor usage kept climbing for Kindle. If I turn auto rotate completely off, the sensor usage doesn't increase after the app exits. Very strange, but I have a work around.

Update 2: The same behavior happens on my nexus one, I just never noticed because I keep auto rotate off most of the time. I guess its an android issue rather than something with the G2X

Brightness bug and camera 3D bug in ICS

Well as you may know the automatic brightness does not work properly under bright sunlight.
And the 3D camera does not take the pictures in the resolution set (check file size) if you access to the camera by the 3D application icon. (If you change from 2D to 3D it does work correctly.)
So I am open this thread to let you know about this, hopefully some developer give us any solution.
Sent from my LG-P925g using Tapatalk 2

same thing happen to me.. my auto brightness censor is not working. Also my 3d cam have problem. But i can still take shots in 3d.

bartdotnet said:
same thing happen to me.. my auto brightness censor is not working. Also my 3d cam have problem. But i can still take shots in 3d.
Click to expand...
Click to collapse
For the brightness, I had the problem for a long time because I was dimming the screen to the minimal possible: but when i once held the brightness button I found out automatic brightness was on at the same time!
So automatic brightness on and yourself dimming the screen at the same time must go wrong.
Have you checked that already?

guys may i ask this question here..images after ics always seem out of focus,or at least 90% of the time (digged through settings,tried different camera apps,still nothing)

and some says the 3D pictures not at the same altitude in ics, making the user dizzy , but it was fine in GB, so they have to stuffed two systems both GB and ICS in it.
luckily my P920 works fine in 3D picture shooting.

I have taken 20 pictures in 3D over a period of a month since upgrading to ICS They all display OK but the resolution is 320 x 240. The phone has been re-booted several times, the battery changed in this period so it is not a settings malfunction. This is not a size listed in the settings menu and is really useless except for viewing on the phone screen. I don't know how this setting happened but just tried taking a 3D photo by using the 3D camera app icon as I had before and it took a full size picture 2048 x 1536 as set in the menu [default]. I seem to remember that a camera bug affects the camera when the battery is low, but my battery was at a good level for all the pictures taken and 3D and 2D videos worked fine. From now on I will check the file size after every photo taken to make sure no more are useless.

I just noticed this myself.
The Thrill 4G forum noticed it, too:
http://forum.xda-developers.com/showthread.php?p=50990556
I'm trying to reproduce it manually, but not getting much luck.
Stock AT&T ICS Rooted and a ton of stuff deleted. I've completely wiped and reformatted different ROMs since then, though.
I think, somehow, that Dropbox is the culprit. I want to blame that, or some kind of auto-sync...
Edit:
http://forums.androidcentral.com/android-applications/11496-dropbox-sugarsync-referrals-here-2.html
I think I'm right. I've seen other reports of this.