Database Users

Battery Manager force close on official 2.2

I'm running the official build of Froyo (2.3.15) and I'm still getting a force close in the usage stats in Battery Manager (process.com.android.settings). At first, I assumed it was a bug in the leak but I have the same problem on this official release. I reset my phone, using SBF, then I did the OTA to 2.2 and rooted using the Droid 2 rooting method. The strange thing about this issue is that it comes and goes with no rhyme or reason. Anyone else seeing this on the official release?

I've seen the error, but not consistently. When it works, it gives more detailed break down of the usage, which is an improvement.
Not sure what got it to work... fooled with it fit a while... FC... FC. Then ban, it worked.

usually plugging it in them taking it off forces it to work then if you actually restart or turn off and back on the phone then bam fc is right back of course mine has been doing this ever since any of the 2.2's came out highly annoying it is.

No I.D. said:
I'm running the official build of Froyo (2.3.15) and I'm still getting a force close in the usage stats in Battery Manager (process.com.android.settings). At first, I assumed it was a bug in the leak but I have the same problem on this official release. I reset my phone, using SBF, then I did the OTA to 2.2 and rooted using the Droid 2 rooting method. The strange thing about this issue is that it comes and goes with no rhyme or reason. Anyone else seeing this on the official release?
Click to expand...
Click to collapse
Having same problem no luck here rooted droid x style posted by wimervision on youtube... very easy

I only seen it work one time. Errors and fc the rest.
Sent from my DROIDX using XDA App

just saw this, havent tried it tho
http://www.droidxforums.com/forum/d...-rmd-battery-manager-longer-battery-life.html

zsg1313 said:
just saw this, havent tried it tho
http://www.droidxforums.com/forum/d...-rmd-battery-manager-longer-battery-life.html
Click to expand...
Click to collapse
Why delete the files? Can't you just rename them to .bak instead of .apk?

willy1234x1 said:
Why delete the files? Can't you just rename them to .bak instead of .apk?
Click to expand...
Click to collapse
Yes it's the same premise. I think the bottom line of that thread is that the got does not have them running/installed.

This has only happened to me when phone was connected to wall charger.
Sent from my DROIDX using XDA App

So strange. I had been reading all over the net about people having this issue but I never experienced it, not even once. Then all of a sudden it happened last night and happens every single time I try to open the Battery Manager now.
The only things I changed were that I applied Beesley's droid.prop edits manually (with 210 as the number used for LCD Density). I also downloaded WatchDog but I don't think that's a problem. Bummed about this

*#*#4636#*#* in the dialer gives the same info... and more...

Enough with the rebooting already!

I know there are lots of threads about problems with the Atrix including rebooting. What I haven't seen is any consensus on what to do about it. Mine reboots randomly 2 or 3 times a day. Sometimes when I'm on a call or using maps or just sitting idle.
Its happened on and off through all software versions. I'm currently running latest OTA (rooted) but otherwise stock. Is it a software bug to be fixed? Is it bad hardware? Should I seek replacement?
I love my Atrix and am really looking forward to Gingerbread next month. Is it too much to hope that this next update will solve the rebooting issue?
Flame away!

wookiebush said:
I know there are lots of threads about problems with the Atrix including rebooting. What I haven't seen is any consensus on what to do about it. Mine reboots randomly 2 or 3 times a day. Sometimes when I'm on a call or using maps or just sitting idle.
Its happened on and off through all software versions. I'm currently running latest OTA (rooted) but otherwise stock. Is it a software bug to be fixed? Is it bad hardware? Should I seek replacement?
I love my Atrix and am really looking forward to Gingerbread next month. Is it too much to hope that this next update will solve the rebooting issue?
Flame away!
Click to expand...
Click to collapse
What launcher are you using? I ask because Now that I've swapped from LP+ to ADW EX I rarely get a "reboot" anymore. On the other threads you may have read that its possible you are experiencing a graphical shell crash and not a reboot.

I'm currently using apb 3d shell. But also occurred with LP. When the reboot happens, it goes all the way dark and proceeds through the whole boot animation. Seems like a reboot to me.
Sent from my MB860 using Tapatalk

yeah mine randomly reboots too... its happened more lately -- but still only once a week maybe..
It happened once when I had GPS on -- my only guess is there has to be something with incoming/outgoing data where the phone resets itself to clear something out? i dont know jack sh1t about smartphones, but I do know that the times Ive caught it rebooting I noticed the phone being very sluggish and data trickling in even though I'm in a good service area.

wait for the GB update, it is supposed to fix the issue according to the reports. I personally have not had a single reboot using ADW EX.

I had the random reboot issue when I first got my phone in March. The beginning of April I reflashed stock sbf updated to latest version then got gingerblur (currently running gingerblur 4) haven't had a random reboot since I started using gingerblur maybe try that? I don't know that's what fixed it for me I just know it never random reboots since I did this. My two cents take it or leave it

Serious lagging...... rooted/no custom ROM

Quick brief:
I am still on 2.1, but I am rooted.......but not using any custom ROM/kernels. I mainly wanted to root to rid of the bloatware. I am rooted, and have CW installed. I used RootExplorer to rid of the bloatware. I have one ongoing issue, and 2 getting progressively worse.
1) My battery has progressively started to wear down faster. I've had my phone over a year now, so I went ahead and purchased a new factory battery. I have properly cycled the battery as you should with a new one (kill it dead, let it charge fully.....did this a couple times). I have not noticed much more of an extended life with the new battery, over the original.
2) I have been using LauncherPro since I rooted. I understand a custom ROM would probably run a ton better, but I barely was able to root my phone successfully by myself.....so I am not sure I want to try flashing it. I really like the customizable features LauncherPro has. Recently though, the phone has gotten really laggy. I notice it most when using the text feature. I had Handcent installed, which I downloaded on the phone at day 1.....so I figured it was that app hanging up. I uninstalled it, and am using the default messaging service. Sometimes its fairly quick, but it still hangs up......even using the default. I also tried DL'ing a new Launcher, and tried Regina. It was lightning fast, but after a few hours....it wouldn't run properly. I assigned it to run as default, but after 3-4 hours.......it would prompt me on which launcher to use.......so I uninstalled it. Now I am still using the default TW launcher.
3) When I rooted, I deleted a few apps that are critical to run nav......like text to speech. I reinstalled them and got my nav working again.....but 90% of the time when I use nav......it takes the upwards of 10-15 minutes for it to find my location. Wtf? My phone is super hot by then too, so obviously my battery drops significantly.
Anyone help out with any sorts of resolution? Fwiw I don't have any apps running that I can see in task manager. I also have cache cleaner......so that is emptied regularly. When I started getting laggy, I installed the cache cleaner.....and it seemed to help alot. Then it got right back to as laggy as it was before......
I'm stumped.

Well, 2.2 came out a while ago and 2.3 is on its way. I say upgrade to 2.2 then to MIUI.
Sent from my SCH-I500 using XDA App

Enyo. said:
......then to MIUI.
Click to expand...
Click to collapse
Say what?
Sorry, guess I need to read up a bunch more to get acquainted with all of the acronyms.

MIUI is a custom ROM a very good one actually.
Sent from my SCH-I500 using xda premium

Jmatch said:
MIUI is a custom ROM a very good one actually.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Oh ok, thanks for clearing it up.......sorry for the noobiness.
I have a friend that has flashed his Galaxy multiple times.....so I am going to get him to flash my Fascinate. I'll find the DL for that one, and show him.
Anyone else have any idea why I could be so laggy, so sudden? Also, I noticed lag when using PowerAmp as well.

Not a clue, haven't been on 2.1 in such a long time. 2.3.5 here. But usually doing a full wipe/reinstall solves any lag issues. As for the gps, well, it sucks tremendously on our fascinates. I suggest the MIUI rom and glitch kernel. I get great battery life, no lag, 10 sec gps lock, and so much more
Sent from my SCH-I500 using XDA App

tripacer99 said:
Not a clue, haven't been on 2.1 in such a long time. 2.3.5 here. But usually doing a full wipe/reinstall solves any lag issues. As for the gps, well, it sucks tremendously on our fascinates. I suggest the MIUI rom and glitch kernel. I get great battery life, no lag, 10 sec gps lock, and so much more
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
+1... +1...

Jmatch said:
MIUI is a custom ROM a very good one actually.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
+1 for this using the glitch kernel found here:
http://forum.xda-developers.com/showthread.php?t=1252871
i also flashed the latest gingerbread radio and im having good results

I'll definitely research those mentioned.
Just seems odd my phone all of a sudden force closes on alot of apps I've used since day 1.

LXative said:
I'll definitely research those mentioned.
Just seems odd my phone all of a sudden force closes on alot of apps I've used since day 1.
Click to expand...
Click to collapse
Did you use Super-1-Click-Root to root your phone? It has a nasty side-effect of lagging up the phone post-root (at least in my, and others' experience)
Try turning off your phone, pulling out the battery for a minute, putting it back in and rebooting. That fixed mine.

Japots said:
Did you use Super-1-Click-Root to root your phone? It has a nasty side-effect of lagging up the phone post-root (at least in my, and others' experience)
Try turning off your phone, pulling out the battery for a minute, putting it back in and rebooting. That fixed mine.
Click to expand...
Click to collapse
Nope, I did it using one of the methods in the sticky in this forum. Thanks for the suggestion though.

I'd suggest following the steps to flash completely back to stock FIRST using pentafive's rom here (http://forum.xda-developers.com/showthread.php?t=1178544) and ODIN (your friend will know this if they've flashed a lot of phones). Do not use PST, it doesn't always work. Once you get fully back to stock, flash whatever new rom, radio, kernel, etc that you want (see here for a good list... http://forum.xda-developers.com/showthread.php?t=1013312).
I was having a lot of force closes after rooting (manually via adb) and a flash back to stock using penta's ROM corrected them all. I then flashed on to a new ROM and have had zero problems so far.

maybe get 2.2 or 2.3 and get voodoo?

Update:
Haven't flashed a ROM yet, but I got bored and wanted to try some easy things. I popped the cover off and took the SD card out, and rebooted the phone. Fast as lightning on reboot, with the SD card out. I stuck the card back in......and it was fine. It went 3-4 days, then all of a sudden starting lagging again really bad. Mind you, before I just pulled the card out......I clear my cache, don't have any apps running besides the launcher and whatever app I am trying to run, and have also rebooted with/without removing the battery many times......to no avail. So after 3-4 days, when it got laggy again......I took the SD card out and rebooted, and its fast as lightning again.
Corrupt SD card possibly?

LXative said:
Update:
Haven't flashed a ROM yet, but I got bored and wanted to try some easy things. I popped the cover off and took the SD card out, and rebooted the phone. Fast as lightning on reboot, with the SD card out. I stuck the card back in......and it was fine. It went 3-4 days, then all of a sudden starting lagging again really bad. Mind you, before I just pulled the card out......I clear my cache, don't have any apps running besides the launcher and whatever app I am trying to run, and have also rebooted with/without removing the battery many times......to no avail. So after 3-4 days, when it got laggy again......I took the SD card out and rebooted, and its fast as lightning again.
Corrupt SD card possibly?
Click to expand...
Click to collapse
Anyone have a suggestion? This has happened many times now, it keeps repeating itself.
Phone starts lagging, removed SD card and reboot, fast as lightning. After 1-2 days, lagging again. Repeat.

If your SD was corrupted the phone would let you know, or things would start disappearing from the card.
This is the nightmare that we fassy owners have got to go through till we find the right Rom and tweak. Gingerbread has made this phone way better whether you use a TW or an Mtd Rom. Do some research and try one of them
Don't be afraid, it's fun
PWGB,TKSGB10-10, adren shot xix, honeycomb2.03, ec09 radio.

laureanop said:
If your SD was corrupted the phone would let you know, or things would start disappearing from the card.
This is the nightmare that we fassy owners have got to go through till we find the right Rom and tweak. Gingerbread has made this phone way better whether you use a TW or an Mtd Rom. Do some research and try one of them
Don't be afraid, it's fun
PWGB,TKSGB10-10, adren shot xix, honeycomb2.03, ec09 radio.
Click to expand...
Click to collapse
Thanks for the reply. I am definitely not afraid to change ROM's, I'm just afraid to do it myself. I'll be doing it in the next week or two, a friend from work is going to flash it for me.
As for the laggy times though......I can't see how the card isn't the culprit. Every single time my phone gets laggy, when I pull the SD card it.....its lightning. A few times also, when the phone is starting to lag......I'll open my gallery and its usually all jumbled up, or it won't show me all of my pictures.
Maybe I need to reformat my SD card? Can I do that through my phone somehow?

Droid Incredible slow down after midnight

Don't know what the hell is going on but it's so frustrating I am about to throw my phone out the window. Recently I upgraded to stock plus v3.01 ROM and also Ext4 4 ALL kernel since I was running into the dreaded data/data memory full issue. Everything seems to be working fine until recently the phone would slow to a crawl right around midnight, I would be watcing a flash video clip before midnight, then right at 12, everything just slow down and nothing I do would resolve this...I can reboot, take the battery out..etc..phone would still be super slow, pretty much the same way until next morning. GoLauncher EX would crash all the time during this time as well, is if there's some kind of ghost process running in the background sucking up all the resources. I checked Mybackup and doesn't look like there's any schedule backup service...so I am pulling my hair out still don't know what's wrong. Anyone else experienced this before, any idea what can be causing this?

This happened to me when i was using that same rom! What i did was just install a different rom.

Try looking on Ebay for a new flux-capacitor for it they always go bad

I had this ROM too... it was cool, but a battery hog.... Back to CM7 Nightly's.... shouldn't have left to begin with....

1. does not belong in this forum
2. try asking the developer, or even in the ROM's forum

Too much porn. Those midnight shows will do it.
Sent from my ADR6300 using XDA App

Thanks for the feedback..looks like the ROM is the culprit..time to upgrade to something else

Cool story bro
CM7 nightly

Haven't had any problems with Stock+ regarding this issue....

definitely very strange.....

Very strange issue. Has it been reported to the ROMs dev?

[Q] Does your Kindle Fire become unresponsive much?

So I tend to answer more questions that I ask on here, but now it's my turn!!
So, I've noticed at times that my KF is totally unresponsive from sleep. No power light, nothing. I have to press the power button for 20 seconds, then again to power on. This used to happen every so often on the Stock ROM.
However, since I've been on CM7 w/ TWRP/FFF, it hangs up every single day. At first I thought it was due to low charge, but it's doing it whilst the battery is over 90% full. I've had a nose around the CM7 settings and tweaks, but can't see anything obvious.
Running services at startup are:
Settings (presumably because I'm looking at settings to see this info!)
Google Services
Amazon Video (Not sure why this is running. I may uninstall to see if this is the problem) - Uninstalled. Will see how it goes.
DSPManager
Swype
Anybody else seen this? Anybody else got any ideas on how to resolve this?

Do a search for V6 SuperCharger and do some research on it I use it on my Fire and my 2 Android Phones it really helps with memory management
Sent from my Kindle Fire using Tapatalk

I've not experienced this problem. My kindle fire has been pretty much perfect and I've never had to force a reboot. I'm also using the Sywpe keyboard.

asb2164 said:
Do a search for V6 SuperCharger and do some research on it I use it on my Fire and my 2 Android Phones it really helps with memory management
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Thanks, but I don't think memory is the problem here (I have 282MB free system memory right now). Something is putting it to sleep permanently.
I guess it's going to be a process of elimination. I might possibly go back to stock to see if it's really CM7 or the device hardware itself playing up.

sl0ttedpig said:
Thanks, but I don't think memory is the problem here (I have 282MB free system memory right now). Something is putting it to sleep permanently.
I guess it's going to be a process of elimination. I might possibly go back to stock to see if it's really CM7 or the device hardware itself playing up.
Click to expand...
Click to collapse
I would not even bother reading the information I provided, reading is pretty hard chase a lot of gremlins first instead of the running a Script.
Sent from my Kindle Fire using Tapatalk

asb2164 said:
I would not even bother reading the information I provided, reading is pretty hard chase a lot of gremlins first instead of the running a Script.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Wow, seriously?!
I *did* read about it, and concluded that it was a memory management app. Given my symptoms, I cannot find one example of where this app would help me, and I'm not about to install something that is possibly just going to add further variables to an already odd behavior.
Show me where you think it's going to help (specific examples), and I'll gladly accept your thanks/suggestions.
Until then, I would ask you keep your snark for sites like Slashdot.

You did not read about it if you had you would have known it is not an app but a Script.
I do not hold people's hand and give links I make you search for it I am sure someone will come along and make you a video
Sent from my Kindle Fire using Tapatalk

asb2164 said:
You did not read about it if you had you would have known it is not an app but a Script.
I do not hold people's hand and give links I make you search for it I am sure someone will come along and make you a video
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Again, Wow Seriously?!
Your definition of me not reading is based on me calling it an app over a script!? Interesting logic there.
However, I'm still wondering how you deduce that this is going to help my problem, and hence why I asked for specifics. I'm quite capable of finding information, but it's like you saying to me "Dude, install Angry Birds, it will solve all your problems". My conclusion was that there was nothing in that post that specifies "This will also help your system if it sleeps permanently" (clearly I'm paraphrasing there, just in case that wasn't clear). If I'm missing something, I'm all ears, but blindly recommending apps for no reason is no help to anyone.

Other than almost every decent ROM you will find on XDA already has this built into it and it will help I will leave it at that.
You also may try to wipe Data, Cache and Dalvik I usually do that at least 3 times on my HTC EVO Shift when I flash a new rom before it runs good.
Try that and see if it helps.

asb2164 said:
Other than almost every decent ROM you will find on XDA already has this built into it and it will help I will leave it at that.
You also may try to wipe Data, Cache and Dalvik I usually do that at least 3 times on my HTC EVO Shift when I flash a new rom before it runs good.
Try that and see if it helps.
Click to expand...
Click to collapse
It may well be the CM7 ROM that was compiled for the KF, but what also makes me suspicious now is for the number of reads on this thread, not one other person has said "Yeah, I have the same issues", which either leads me to believe its a resident app, or possibly something wrong with my hardware. I'll keep digging, and possibly flash back to stock (as I said).
For the benefit of doubt, I'll always do a Factory Reset, and wipe all the Cache/Dalvik Cache. It's something I've done since I was flashing ROM's on my first Droid. But thanks for the suggestion.

You may have a bad flash back up your apps and re-flash CM7 and restore your apps and see if that helps.
I have rooted and flashed a lot of phones and I have had that happen a couple of times I re did the flash and everything was fine.

asb2164 said:
You may have a bad flash back up your apps and re-flash CM7 and restore your apps and see if that helps.
I have rooted and flashed a lot of phones and I have had that happen a couple of times I re did the flash and everything was fine.
Click to expand...
Click to collapse
I guess it's entirely possible. I'll do a Titanium Backup now, re-flash, and see what happens. But as mentioned in my OP, I had this happen on stock 6.2, just not as frequently, so I'll be hoping that it is a bad flash, and not something inherently worse.
See how much better this conversation is now!

Sounds fishy to me as well. Did you clear the caches when installing new ROMs? I've had mine since it was release and have yet to have it hang and I've had 6.1,6.2, and now CM7 running flawlessly

Your problem is a bit unique so I don't mind throwing out a few ideas.
Mine is solid as a rock I am ready for a good overclocking kernel so I can stretch it's legs
Sent from my Kindle Fire using Tapatalk

altitude909 said:
Sounds fishy to me as well. Did you clear the caches when installing new ROMs? I've had mine since it was release and have yet to have it hang and I've had 6.1,6.2, and now CM7 running flawlessly
Click to expand...
Click to collapse
Yep, I always clear everything when moving to a new ROM. It's a habit that was drilled into me during my first custom ROM exploits on my Droid. I've even told people on here to do it too, so I'm practicing what I'm preaching!
I think what I'm going to do is, reflash to stock 6.2.1, use the new root method, push TWRP/FFF again, and then CM7. A little drastic, but I think that having a clean run at this might prove/disprove the theory.

My stock rom does this occasionally. Have to hold the power button for 20 secs to reset it.

krelvinaz said:
My stock rom does this occasionally. Have to hold the power button for 20 secs to reset it.
Click to expand...
Click to collapse
Yeah, this is happening a little too frequently for my liking. Occasionally is fairly OK, every day is not. But it has got worse since going to CM7, but that could be purely coincidence at this point.
Trying some different things right now, but it will be a few days before I know for certain.

This may not be the problem at all, but I'll toss it out here anyway. On some of my Archos tablets, I have had this issue where the screen brightness was set very low. Anyway, if your brightness is set low, you might increase it to see if that makes a difference. I don't remember exactly at what level this problem starts, but I think it is when it is set below 20%.

butterflygirl said:
This may not be the problem at all, but I'll toss it out here anyway. On some of my Archos tablets, I have had this issue where the screen brightness was set very low. Anyway, if your brightness is set low, you might increase it to see if that makes a difference. I don't remember exactly at what level this problem starts, but I think it is when it is set below 20%.
Click to expand...
Click to collapse
Thanks, that hadn't crossed my mind, but I like my brightness at a pretty high level, and as the sensor is not working currently, it pretty much stays at that level.
Back at stock 6.2.1 now. Going to root it and leave it like this for a few days to see what happens.

sl0ttedpig said:
It may well be the CM7 ROM that was compiled for the KF, but what also makes me suspicious now is for the number of reads on this thread, not one other person has said "Yeah, I have the same issues", which either leads me to believe its a resident app, or possibly something wrong with my hardware. I'll keep digging, and possibly flash back to stock (as I said).
For the benefit of doubt, I'll always do a Factory Reset, and wipe all the Cache/Dalvik Cache. It's something I've done since I was flashing ROM's on my first Droid. But thanks for the suggestion.
Click to expand...
Click to collapse
Not sure if you have resloved this issue, but having read most of the Forum Dev Thread for the CM7 initial release and the newest reboot of the first ROM I think many others are having this issue as well. I remember reading many post people were referring to something similar to your problem as "the sleep of death." I however am not having that problem with mine, but thought it might be helpful to know that it might not be your device specific and may be something with CM7 itself with some devices.