Cap is bootlooping on MPD 2.0 . - Captivate Q&A, Help & Troubleshooting

I need a little help. My I897 is running on MPD 2.0 ROM, w/ EyeCandy v 3.15 and Corn Kernel 7.06, and it is stuck bootlooping at the swirling optical illusion at start-up. I don't know why, all I was doing was playing a couple of games and it was really lagging, and freezing up and it has been a lot lately. I even posted about it yesterday or the day before? Whatever?
So tonight, it just froze while playing a game and it was totally unresponsive so I let it sit. After about 10 minutes, I noticed it was on the optical illusion and stuck with the illusion spinning away. I pulled the battery, restart the phone same thing. Goes through the first start up screens and gets to the swirl thing and goes no further.
I pulled the battery again and replaced it, went into recovery and hit the reboot device and started it up. Same thing.
Should I reflash the Rom? If I do, I have to do a full wipe and that will suck.
Has anyone had this problem on MPD 2.0?
Maybe someone has an answer.
Thanks, whoever tries to help me with this.
Sent from my SGH-T989 using xda premium

kaiserXDA said:
I need a little help. My I897 is running on MPD 2.0 ROM, w/ EyeCandy v 3.15 and Corn Kernel 7.06, and it is stuck bootlooping at the swirling optical illusion at start-up. I don't know why, all I was doing was playing a couple of games and it was really lagging, and freezing up and it has been a lot lately. I even posted about it yesterday or the day before? Whatever?
So tonight, it just froze while playing a game and it was totally unresponsive so I let it sit. After about 10 minutes, I noticed it was on the optical illusion and stuck with the illusion spinning away. I pulled the battery, restart the phone same thing. Goes through the first start up screens and gets to the swirl thing and goes no further.
I pulled the battery again and replaced it, went into recovery and hit the reboot device and started it up. Same thing.
Should I reflash the Rom? If I do, I have to do a full wipe and that will suck.
Has anyone had this problem on MPD 2.0?
Maybe someone has an answer.
Thanks, whoever tries to help me with this.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I'm not so sure what MPD is but Corn kernel is on GB. Therefor, there's no developping nor support being made for it, which could explain why you got no answer on your previous post.
Luckily, you can get in recovery. Make a backup, wipe cache/dalvik and try to boot up. If that doesn't work, back in recovery, wipe cache/dalvik, factory reset and reflash your ROM. Altough, I would suggest looking at the newer ROMs out there as we're up to JB 4.2.1 (you're on GB 2.3.5).
If you go ahead with the upgrade, make sure you follow the full instructions in the OP.

Thanks, I already reflshed and its running. I know that there are newer Roms I only flashed it because I hadn't yet flashed anything from the Collective and the eyecandy theme I wanted to check out also.
But after running great for a couple weeks, it started getting buggy. Now I'm gonna do something else. My SII is running darkside Evolution #5 4.03 by thederekjay w/venom kernel, and I wanted an older Rom in my Cap, for contrast.
I'm not sure what I'll do next. I just needed it running. It is my business line for my electrical contracting company. And it will start ringing in about a ½ hour.
Thanks, for your response and have a great day.
Sent from my SGH-T989 using xda premium

kaiserXDA said:
Thanks, I already reflshed and its running. I know that there are newer Roms I only flashed it because I hadn't yet flashed anything from the Collective and the eyecandy theme I wanted to check out also.
But after running great for a couple weeks, it started getting buggy. Now I'm gonna do something else. My SII is running darkside Evolution #5 4.03 by thederekjay w/venom kernel, and I wanted an older Rom in my Cap, for contrast.
I'm not sure what I'll do next. I just needed it running. It is my business line for my electrical contracting company. And it will start ringing in about a ½ hour.
Thanks, for your response and have a great day.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Wait, the collective? The Collective and The Family used to be one team.. Yet I dunno what you mean by MPD?
And if you're looking into something stable, I would highly suggest either AOKP or AoCP (4.1.2).

MPD is a KK4 based Rom put together by robm1911 of the Collective. The Multiple Personality Disorder ROM http://forum.xda-developers.com/showthread.php?p=27985912
Sent from my SGH-I777 using xda premium

4-2ndtwin said:
MPD is a KK4 based Rom put together by robm1911 of the Collective. The Multiple Personality Disorder ROM http://forum.xda-developers.com/showthread.php?p=27985912
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Oh I see, was made while I was away. Thanks for the clarification 4-2ndtwin

What would you recommend for a stable build? I use my Cap as my business line. So it has to be reliable. Camera, GPS, texting, etc..., all have to function. But I also like to have the little extras. As you know I'm on the kk4 kernel, and I'm OK with flashing, not okay with having to run anything that needs me to use Linux or do any command lines that kinda thing. I still new to everything. Thanks
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

Sorry, but I forgot to mention that it running pretty normal now. I got rid of the eyecandy theme. It is the culprit from what I can tell. Without it the phone is better. Still a little laggy though.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

kaiserXDA said:
What would you recommend for a stable build? I use my Cap as my business line. So it has to be reliable. Camera, GPS, texting, etc..., all have to function. But I also like to have the little extras. As you know I'm on the kk4 kernel, and I'm OK with flashing, not okay with having to run anything that needs me to use Linux or do any command lines that kinda thing. I still new to everything. Thanks
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
kaiserXDA said:
Sorry, but I forgot to mention that it running pretty normal now. I got rid of the eyecandy theme. It is the culprit from what I can tell. Without it the phone is better. Still a little laggy though.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
If you look up, I already made 2 suggestions
AoCP or AOKP (4.1.2)

kaiserXDA said:
Sorry, but I forgot to mention that it running pretty normal now. I got rid of the eyecandy theme. It is the culprit from what I can tell. Without it the phone is better. Still a little laggy though.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
There are also tweaks in recovery that u can choose from and even the ability to change the partitions to Ext4. Check the kk4 corn kernel's op for info on these things.
I use my cappy for work and pretty much have stock kk4, with Root, debloated, Ext4 on all partitions and the tweaks i have are sio Scheduler and smartassv2 Governor. Runs great !
Sent from my SGH-I777 using xda premium

I have it running on deadline and smartass v2 and it runs pretty damn well, I dont know too much about partinoning so I have stayed clear just in case I screw something up.
What about the kernel tweaks (ROM toolbox pro) the voltage controlsyscti tweaks? What is that for, signalling the different MHz -0mV? I'm an electrician and have been for 20 years but electronics is a new hobby and the phones my new medium. I would love to know more, so if you could tell me what I should read or??? That would help me learn more I would be stoked.
Thanks KK

kaiserXDA said:
I have it running on deadline and smartass v2 and it runs pretty damn well, I dont know too much about partinoning so I have stayed clear just in case I screw something up.
What about the kernel tweaks (ROM toolbox pro) the voltage controlsyscti tweaks? What is that for, signalling the different MHz -0mV? I'm an electrician and have been for 20 years but electronics is a new hobby and the phones my new medium. I would love to know more, so if you could tell me what I should read or??? That would help me learn more I would be stoked.
Thanks KK
Click to expand...
Click to collapse
OC = Overclock
UV = Undervolt
SoD = Sleep of Death
I don't suggest changing voltage on the cappy (UV). The processor isn't strong/fast enough, therefor it takes more time to process what you ask of it = more screen time = more battery drain. While screen off though, your battery will be better (can also cause black screen and SoD at unstable state). Screen on is the main battery drain for androids. So basically, reducing your voltage (UV) will lower your battery consumption, of course at a price = slower processing and despite you intention to reduce battery drain, it might increase it. The Captivate has proved to be quite unstable with OC/UV on GB and up.
Up'in your Mhz (OC) will make your phone faster but at the cost of faster battery drain and faster hardware usage. On top of that, both can make your phone unstable. Finding the right combination can take some time if you really wanna get into it. There are guides about it which you can find with a little search, altough, once again, I don't recommend it.

Thanks Bwolf, I really appreciate you taking the time to explain some of that. I have read some some of that stuff in other posts, over the past year or more that I've been on XDA, although it was Greek to me at the time. Now I knowwhat you guys are saying, I just don't know the hows or whys. In time.
I will follow your advice on the voltage and the OC and leave it alone.
There was a time a while back when I first started messing around and I changed something it might have been voltage, and my Cap went nuts. It was sucking down my battery right before my eyes, so fast and getting hot, I pulled the battery and I don't remember how I got it straightened out, but I did. Crazy! So, I know better, curiosity killed the cat (cap) lOL. Thanks Again

kaiserXDA said:
Thanks Bwolf, I really appreciate you taking the time to explain some of that. I have read some some of that stuff in other posts, over the past year or more that I've been on XDA, although it was Greek to me at the time. Now I knowwhat you guys are saying, I just don't know the hows or whys. In time.
I will follow your advice on the voltage and the OC and leave it alone.
There was a time a while back when I first started messing around and I changed something it might have been voltage, and my Cap went nuts. It was sucking down my battery right before my eyes, so fast and getting hot, I pulled the battery and I don't remember how I got it straightened out, but I did. Crazy! So, I know better, curiosity killed the cat (cap) lOL. Thanks Again
Click to expand...
Click to collapse
Hehe np. As for what happened before, pulling the battery most likely reseted your kernel settings (OC in this case) as it probably wasn't ''set on boot''. Probably saved you a lot of hastle too

Related

Just Flashed Cognition.

so i just flashed cognition 3.04, and i love it. so much smoother and faster. i was tired of waiting for the officail 2.2 froyo release. the only thing that i dont understand is that it says that the unlock screen should be the stock glass pane swipe thing. but its not. its just the standard froyo unlock screen. not a big deal just wondering about it. so i guess thats my question.
More people requested stock lockscreen over the glass one. It's really upto DG to change whatever he wants in his rom. I guess he likes to satisfy all his followers
yeah i am not upset with the lockscreen. just wondering if i missed something. its a really nice rom. now i am wondering what else should i add to the phone. i want to keep this rom but maybe overclock it next.
thejanitor86 said:
yeah i am not upset with the lockscreen. just wondering if i missed something. its a really nice rom. now i am wondering what else should i add to the phone. i want to keep this rom but maybe overclock it next.
Click to expand...
Click to collapse
I'm thinking of trying glitterballz lethal with an i9000 rom. Glitterballz' kernel has always worked well for me.
thejanitor86 said:
so i just flashed cognition 3.04, and i love it. so much smoother and faster. i was tired of waiting for the officail 2.2 froyo release. the only thing that i dont understand is that it says that the unlock screen should be the stock glass pane swipe thing. but its not. its just the standard froyo unlock screen. not a big deal just wondering about it. so i guess thats my question.
Click to expand...
Click to collapse
You have to actually read the change log.
designgears said:
v3.04 Changelog:
EXTREMELY FAST FIRST BOOT!
No update version
Stock Lock Screen
Moved Launcher Pro to /data
Fixed Dialer touch sounds
Click to expand...
Click to collapse
This is from his thread.
lol i did read everything in the change log. even researching the things i didnt understand, which was quite a few. ha. but your right. i mistook that for meaning the STOCK captivate lockscreen. and also the two large screenshots threw me off, since the picture posted by designgears of the rom layout clearly shows the lock screen being the glass style one. but if thats the only mistake i made then so be it. what overclocked kernal do you guys recommend with the cognition rom.
thejanitor86 said:
lol i did read everything in the change log. even researching the things i didnt understand, which was quite a few. ha. but your right. i mistook that for meaning the STOCK captivate lockscreen. and also the two large screenshots threw me off, since the picture posted by designgears of the rom layout clearly shows the lock screen being the glass style one. but if thats the only mistake i made then so be it. what overclocked kernal do you guys recommend with the cognition rom.
Click to expand...
Click to collapse
No worries man, just thought I would make sure you knew it was in the change log. I personally am not using a OC/UV kernel because every time I have it has killed my battery. I just left Serendipity for that reason. I have run both Hardcore and Glitterballs kernels and I just never had good luck like others have had.
yeah i probably will leave it alone for now. but i feel i want to do more. any suggestions for other stuff i can add/do to the phone now.
flashman2002 said:
No worries man, just thought I would make sure you knew it was in the change log. I personally am not using a OC/UV kernel because every time I have it has killed my battery. I just left Serendipity for that reason. I have run both Hardcore and Glitterballs kernels and I just never had good luck like others have had.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
Serendipity has given me the best battery life ever. And its rinnin oc.
blazin619 said:
Sent from my SAMSUNG-SGH-I897 using XDA App
Serendipity has given me the best battery life ever. And its rinnin oc.
Click to expand...
Click to collapse
That is the beauty of these phones; I was running Serendipity and just yesterday alone I had to charge twice because it killed my battery. I was running extremely mild settings so I would try and help my battery and it still died. That is why I went away from it, but my phone has been that way with all OC/UV kernels. On the other hand with Cognition I flashed yesterday at 85% battery (yes everyone says flash from 100% and I don't care lol) and after 14 hours I am at 70% battery with normal use for me. If I were on Seredipity or any other OC/UV kernel my phone just sleeping would die. It sucks how much of a difference these phones have between each other.
15% drop in 14 hours.....normal use... :/
newter55 said:
15% drop in 14 hours.....normal use... :/
Click to expand...
Click to collapse
If you dont cut out the rest of my sentence it says at the end "for me". So simply changing the rom immediately made my battery better because i had serious issues on serendipity. Please dont take a part of what i said and try to twist it around.
This is my captivate. There are many like it buy this one is mine.
newter55 said:
15% drop in 14 hours.....normal use... :/
Click to expand...
Click to collapse
If normal use is screen off on airplane mode
flashman2002 said:
If you dont cut out the rest of my sentence it says at the end "for me". So simply changing the rom immediately made my battery better because i had serious issues on serendipity. Please dont take a part of what i said and try to twist it around.
This is my captivate. There are many like it buy this one is mine.
Click to expand...
Click to collapse
Sorry, wasn't trying to twist anything. Just surprised at what you would classify as normal.
I just like to look at the screen too much
Why so serious
newter55 said:
Sorry, wasn't trying to twist anything. Just surprised at what you would classify as normal.
I just like to look at the screen too much
Click to expand...
Click to collapse
I only speak for myself and my stats. I was using that point based on what i have had happen. I have used my phone more today than the previous couple because the battery lasted. On serendipity which is a good rom overall i would lose atleast 35% during the day with airplane mode on. Working in a clinic att does not work in my area so i keep it on to help savebattery. Too bad my phone hates oc/uv kernels.
This is my captivate. There are many like it buy this one is mine.
well i havent charged the battery since i flashed it and its still at 42 percent. and i have been messing with it alot. so apparently my phone loves cognition. ha. but i was wondering if its possible to put the touchwiz app drawer back in. i liked it better since you can move the apps where you want.

CM7 Sleep Fix Progress?

I've been busy lately so I'm having difficulty staying on top of the latest news. What's the progress with CM7 and it's insomnia?(sleep troubles) I love CM7 but if it keeps being a Vampire my Battery will be at risk and I'll have to switch ROMs. Any News?
____________________________________________________
Sent from NookColor CM7 using Tapatalk
Dalingrin is working on the .32 kernel, the future successor to our current kernel. He has fixed the sleep issue in this new kernel but he still has work to do on other aspects of it. This has all happened fairly recently so stay tuned.
Sent from my DROID2 using XDA Premium App
TJNooker said:
Dalingrin is working on the .32 kernel, the future successor to our current kernel. He has fixed the sleep issue in this new kernel but he still has work to do on other aspects of it. This has all happened fairly recently so stay tuned.
Sent from my DROID2 using XDA Premium App
Click to expand...
Click to collapse
Good to know If anybody else has more info I'll gladly accept.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
It would be sweet if the fix gets the battery performance to be as good as that of Stock 1.2!
Waiting eagerly for the release. Using Froyo 0.6.8 R7 in the meantime.
is it just me or CM7 in general goes through a battery noticeably faster? I guess I can try doing a simple comparison using the browser or something.
s52m3 said:
is it just me or CM7 in general goes through a battery noticeably faster? I guess I can try doing a simple comparison using the browser or something.
Click to expand...
Click to collapse
Between the overclocked kernel and the fact that it doesn't go into a deep sleep, yes, CM7 currently consumes battery very quickly relative to stock. It sounds like the new kernel will address the latter, but you're always going to pay some cost for higher performance with an overclocked kernel while you're actually using the NOOK.
SCWells72 said:
Between the overclocked kernel and the fact that it doesn't go into a deep sleep, yes, CM7 currently consumes battery very quickly relative to stock. It sounds like the new kernel will address the latter, but you're always going to pay some cost for higher performance with an overclocked kernel while you're actually using the NOOK.
Click to expand...
Click to collapse
I haven't overclocked anything, I have it set at 800 max in the setup.
s52m3 said:
I haven't overclocked anything, I have it set at 800 max in the setup.
Click to expand...
Click to collapse
Then it's most likely due to the lack of deep sleep.
japzone said:
Good to know If anybody else has more info I'll gladly accept.
Click to expand...
Click to collapse
Like reading the cm7 thread?
khaytsus said:
Like reading the cm7 thread?
Click to expand...
Click to collapse
I don't have time to read all the threads and other things. You know how many things are posted there. I loose hours just reading through threads and I don't have hours to do so right now. So any info on the Sleep Fix would be appreciated.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
So
I'm running the latest nightly, and I highly recommend everyone at least flash up to n63. In there Dal was able to get the speaker to shutup when it's sleeping (you'll still hear the buzz when the screen is on, but when off...nice and quiet )
That, plus the 1.3GHz kernel, I'm getting MUCH better battery, and it seems snappier (and has since the base changed to 2.3.4).
ace7196 said:
So
I'm running the latest nightly, and I highly recommend everyone at least flash up to n63. In there Dal was able to get the speaker to shutup when it's sleeping (you'll still hear the buzz when the screen is on, but when off...nice and quiet )
That, plus the 1.3GHz kernel, I'm getting MUCH better battery, and it seems snappier (and has since the base changed to 2.3.4).
Click to expand...
Click to collapse
Sweet, I prefer to stay as stable as possible but with these updates I'm pretty much sold on at least updating to your specified version. Unfortunately I'm away from home at the moment and this Net connection is slow. I prefer making an Image Backup before I update anyway, just incase. That way I can always Flash back if anything screwy goes on.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
ace7196 said:
So
I'm running the latest nightly, and I highly recommend everyone at least flash up to n63. In there Dal was able to get the speaker to shutup when it's sleeping (you'll still hear the buzz when the screen is on, but when off...nice and quiet )
That, plus the 1.3GHz kernel, I'm getting MUCH better battery, and it seems snappier (and has since the base changed to 2.3.4).
Click to expand...
Click to collapse
Glad to know I'm not the only one to see an improvement on 63, but... I have not been able to replicate it since. I had better than 0.25%/hour right after flashing but have been close to 1% in the day since. Oh well. Someday...
Any new Progress?
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
think they fixed ith with test build in cm7 developer thread
Wow thread got barried.
~~bump~~
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
japzone said:
Wow thread got barried.
~~bump~~
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
IM sorry, but in a tenth of the time you were waiting for somebody to do the search for you, you could have done a search and found your answer.
Hint, its in the dev forum (as previously hinted at 8 hours ago by the previous poster).
The new Beta 2 solve the sleep issue. Lot of dev over there, progressing to Beta 3
http://forum.xda-developers.com/showthread.php?t=960537
Divine_Madcat said:
IM sorry, but in a tenth of the time you were waiting for somebody to do the search for you, you could have done a search and found your answer.
Hint, its in the dev forum (as previously hinted at 8 hours ago by the previous poster).
Click to expand...
Click to collapse
I was busy at the time and couldn't check, it takes time to look through a forum which I didn't have but making a post on a already started topic takes a minute. Now, I have free time to check myself.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
I have nightly 70 running now and the sleep issue can be put to bed. CM7 is now all it should be. I guess I will wait a bit longer for kinks (although everything seems fine for me) to be worked out and I can finally flash to eMMC and ditch the stock rooted ROM.
-Steve

[Q] Extremely Slow performance

Hey guys,
I love my Captivate and I don't want to have to replace it but I'm having serious issues. I installed Cyanogenmod 10 and Devil Kernel and overall its been working ok. But the phone is SO SLOW! From wake up, it sometimes takes about 5 - 10 seconds before it will register that I've done something and even then it takes another 5 - 10 seconds to start an app. Rebooting helps for a little while, but the slowness comes right back.
Most of the time it will freeze up after an input and then do everything I asked it to do in about 2 seconds, then freeze up again.
I've got it OC'd (which I had hoped would help) and I'm using wheatley governor in Devil Kernel. Doesn't seem to make a difference over stock settings. No force closes or instability just absolute gridlock when trying to do anything. Any suggestions or ideas?
jamina1 said:
Hey guys,
I love my Captivate and I don't want to have to replace it but I'm having serious issues. I installed Cyanogenmod 10 and Devil Kernel and overall its been working ok. But the phone is SO SLOW! From wake up, it sometimes takes about 5 - 10 seconds before it will register that I've done something and even then it takes another 5 - 10 seconds to start an app. Rebooting helps for a little while, but the slowness comes right back.
Most of the time it will freeze up after an input and then do everything I asked it to do in about 2 seconds, then freeze up again.
I've got it OC'd (which I had hoped would help) and I'm using wheatley governor in Devil Kernel. Doesn't seem to make a difference over stock settings. No force closes or instability just absolute gridlock when trying to do anything. Any suggestions or ideas?
Click to expand...
Click to collapse
You might wanna check if you have some apps using all your RAM.
Also, you could try these settings for Devil: http://forum.xda-developers.com/showpost.php?p=34660665&postcount=5
Dang !! BWolf56 u are all over the place posting answers and helpin out ! Much appreciated ! :thumbup::beer:
Sent from my SAMSUNG-SGH-I897 using xda premium
4-2ndtwin said:
Dang !! BWolf56 u are all over the place posting answers and helpin out ! Much appreciated ! :thumbup::beer:
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Haha it keeps me busy on slow days at work
I was away from XDA for a while but was about the same back then, actually was more busy around here
Oh and you're quite helpful too, some stuff you think about that wouldn't have even cross my mind at the time :good: :highfive:
BWolf56 said:
You might wanna check if you have some apps using all your RAM.
Also, you could try these settings for Devil: http://forum.xda-developers.com/showpost.php?p=34660665&postcount=5
Click to expand...
Click to collapse
Thanks for the tips! I am really good about closing apps that I am not using, and I try to restart my phone at least once a day (but that really shouldn't be necessary). I know Android and task killers don't get along - any suggestions on something that might work?
jamina1 said:
Thanks for the tips! I am really good about closing apps that I am not using, and I try to restart my phone at least once a day (but that really shouldn't be necessary). I know Android and task killers don't get along - any suggestions on something that might work?
Click to expand...
Click to collapse
Have you tried the Devil settings in the link?
As for task killers, I personaly use ATK (no auto-kill) when I know I'll require some extra RAM for what I'm about to do but unless you have some rogue app taking all your RAM, 5-10 seconds lock shouldn't happen.
Slow performance usually comes from lack of free RAM, therefor, there has to be something (app most likely) using too much. Other thing could be that your phone is too full, so either too many apps (100+) and/or not enough free space on your SD card (less than 1gb).
Does it happen randomly or with specific apps? If specific, are those apps from restore or fresh install?

[Q] Heavy battery drain when on charger

Hi there!
Ok so recently my Cappy has decided its going to be screwy. For some reason if I plug it in to charge, it doesn't charge, instead I get a battery drain 5-7% within about 20 mins. I've tried 5 different cables (Zip cord, walmart one, random ones I found/borrowed, one staright plug in one not usb) and 5 different chargers (car/wall plugin hybrid, apple wall charge two different computers.) and its all the same result. I can still use it as a USB no problem, moved some files around and removed and added soem photos no problem. There is no issue with the port itself (on the outside) my cover snapped off but I make sure to keep it clean.
I also have no odd battery draining I can usually get about 12-14 hours out of it. No out of place wakelocks, no apps running wild, and all my backups are on the cloud or on my laptop. Only thing I could think this is is a hardware issue. That or its just time to get a new phone. Thankfully I have an external battery charger and I've just been switching out batteries.
Any thoughts?
On Slimbean 4.2.2 build 4.2
athdaraxen said:
Hi there!
Ok so recently my Cappy has decided its going to be screwy. For some reason if I plug it in to charge, it doesn't charge, instead I get a battery drain 5-7% within about 20 mins. I've tried 5 different cables (Zip cord, walmart one, random ones I found/borrowed, one staright plug in one not usb) and 5 different chargers (car/wall plugin hybrid, apple wall charge two different computers.) and its all the same result. I can still use it as a USB no problem, moved some files around and removed and added soem photos no problem. There is no issue with the port itself (on the outside) my cover snapped off but I make sure to keep it clean.
I also have no odd battery draining I can usually get about 12-14 hours out of it. No out of place wakelocks, no apps running wild, and all my backups are on the cloud or on my laptop. Only thing I could think this is is a hardware issue. That or its just time to get a new phone. Thankfully I have an external battery charger and I've just been switching out batteries.
Any thoughts?
On Slimbean 4.2.2 build 4.2
Click to expand...
Click to collapse
My guess is that you need a new battery.
Does it show the charging animation? Also, when plugged to the pc, does fast charge help at all?
Does it charge when the phone is turned off?
sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
BWolf56 said:
My guess is that you need a new battery.
Does it show the charging animation? Also, when plugged to the pc, does fast charge help at all?
Click to expand...
Click to collapse
That's just it, I bought 2 new batteries, RavPower ones. They work great and last forever when I charge. My original battery and my cheap one off ebay do the same.
And yes it shows the charging thing, by battery monitor says it's charging and shows the different kinds like a/c or usb, everything acts as it should just no charging.
I have never tried the fast charge, I forgot I even had that. I'll give it a shot.
laughingT said:
Does it charge when the phone is turned off?
sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
Click to expand...
Click to collapse
Also something I haven't tried over a long period. I will try that as well.
Thank you both.
Sent from my SGH-I897 using Tapatalk 2
Also are you OC'ing or changing the Voltages? Probably won't make a difference in this issue but worth looking into. My Cappy refuses to OC at all, even at 102% it starts to act weird (System UI crashes sometimes, I lose signal, etc).
x0ne215 said:
Also are you OC'ing or changing the Voltages? Probably won't make a difference in this issue but worth looking into. My Cappy refuses to OC at all, even at 102% it starts to act weird (System UI crashes sometimes, I lose signal, etc).
Click to expand...
Click to collapse
I actually have mine stable at 110% still don't know how lol. Cappys seem to be very picky. I'll try turning it back down.
Also fast charge didn't change anything sadly. 2% lost in about 6mins. It was sitting on my bed doing nothing l
Sent from my SGH-I897 using Tapatalk 2
Apparently Samsung's hardware consistency control was lacking when the Captivate was made, so that's why they're so picky, which sucks for any kind of troubleshooting or development.
I wish I could get my Cappy to 110%. But try turning it back to 100% see if that changes anything. Also does this happen on multiple ROMs or just the one you're currently on (probably not the issue but hey I've seen weirder).
x0ne215 said:
Apparently Samsung's hardware consistency control was lacking when the Captivate was made, so that's why they're so picky, which sucks for any kind of troubleshooting or development.
I wish I could get my Cappy to 110%. But try turning it back to 100% see if that changes anything. Also does this happen on multiple ROMs or just the one you're currently on (probably not the issue but hey I've seen weirder).
Click to expand...
Click to collapse
I haven't been on a different ROM since I found Slim x3 if anything I'll try turning my phone off to see if it charges.
Oh and I forgot to say I didn't mess with voltages.
Sent from my SGH-I897 using Tapatalk 2
athdaraxen said:
I haven't been on a different ROM since I found Slim x3 if anything I'll try turning my phone off to see if it charges.
Oh and I forgot to say I didn't mess with voltages.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Got it, off-topic but any reason you haven't gone to Slim build 4? I saw slight improvement in performance on my Cappy. Was my daily driver until this morning when I flashed C-Rom v16, which for me is as fast. Just trying to get used to how big everything is compared to Slim, I liked being able to read about 7-8 messages in the messaging app, but now I can only see about 3 lol.
x0ne215 said:
Got it, off-topic but any reason you haven't gone to Slim build 4? I saw slight improvement in performance on my Cappy. Was my daily driver until this morning when I flashed C-Rom v16, which for me is as fast. Just trying to get used to how big everything is compared to Slim, I liked being able to read about 7-8 messages in the messaging app, but now I can only see about 3 lol.
Click to expand...
Click to collapse
Sorry x3 was a smiley not a build number, I'm on 4.2.
Anyways! I let my phone charge while off for about an hour. It was at 49% turned it back on and it was at 23% see what I mean? That's a crazy amount of juice.
Also, yeah I did play around with some other ROMs and I hated how big they all are, I like how small everything is on Slim. It just works better for me. X3
Sent from my SGH-I897 using Tapatalk 2
Oh, sorry haha so used to seeing x5 x6 x7 etc.
I don't understand why it's DRAINING your battery instead of charging it. Seems like something got reversed?
I asked because maybe it was a bad flash or something, although it seems unlikely.
I
x0ne215 said:
Oh, sorry haha so used to seeing x5 x6 x7 etc.
I don't understand why it's DRAINING your battery instead of charging it. Seems like something got reversed?
I asked because maybe it was a bad flash or something, although it seems unlikely.
Click to expand...
Click to collapse
I'll try not to use it so you don't get confused. Its just habit.
I don't either. I really did see much on hardware issues that would drain it like this. I really am stumped by this.
And recently I did flash back to stock and work my way back up to Slim to see if it would help and it didn't. I didn't think to see if it would charge on stock or CM 10 but if it really came down to it I guess I could flash back to stock and play with it. Only reason I don't think it's the ROM is because to my knowledge no one else is having this particular issue.
If you have anything I can do to test or provide info just ask. I'll do whatever is needed to help figure it out. And I'd really like to as I'll have this phone for a bit longer then I thought so I'd like to see it fixed
Sent from my SGH-I897 using Tapatalk 2
Do you have a battery charger? Like one that you just attach the battery to, to charge it. We could then see if it's your batteries (highly doubt) or your cappy (99.999% sure).
I don't really want to suggest checking with multi-meters only because the phone internals would be exposed while it's on and if you're not used to working with hardware like that you could accidentally short something etc.
Why not make a nandroid, flash to CM10, see what happens with your battery then. That way, if you ever need to go back to your current ROM you could just restore it.
x0ne215 said:
Do you have a battery charger? Like one that you just attach the battery to, to charge it. We could then see if it's your batteries (highly doubt) or your cappy (99.999% sure).
I don't really want to suggest checking with multi-meters only because the phone internals would be exposed while it's on and if you're not used to working with hardware like that you could accidentally short something etc.
Why not make a nandroid, flash to CM10, see what happens with your battery then. That way, if you ever need to go back to your current ROM you could just restore it.
Click to expand...
Click to collapse
Yeah I do, it's what I've been doing to keep using my phone, I've had this problem for a month now. I think.
It was suggested I open up the phone and check the charge port, make sure it's clean, that kinda stuff but I don't want to do that unless I'm absolutely 100% sure it's not something else.
Wouldn't hurt. I'll go try it. Thanks for being so helpful. :3
Sent from my SGH-I897 using Tapatalk 2
athdaraxen said:
Yeah I do, it's what I've been doing to keep using my phone, I've had this problem for a month now. I think.
It was suggested I open up the phone and check the charge port, make sure it's clean, that kinda stuff but I don't want to do that unless I'm absolutely 100% sure it's not something else.
Wouldn't hurt. I'll go try it. Thanks for being so helpful. :3
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
No problem, I do this kind of thing daily at my job so being able to help with something I actually like is nice :victory:
x0ne215 said:
No problem, I do this kind of thing daily at my job so being able to help with something I actually like is nice :victory:
Click to expand...
Click to collapse
Huzzah! Well, I got CM loaded, did a full wipe too. Everything looks so big. I'll report back in an hour or two. :3
EDIT
And its charging!
I guess it is in fact the ROM. Dang. I wonder why?
I'm going to see if I can get this to charge fully before bringing it to the SlimBean thread. Just to be extra sure.
EDIT
It seems to get to around 30% (31% as of now) and it just stops. It won't charge any higher. Been like that for about 45 mins.
And EDIT again. x3
Ok so I (still on CM10) couldn't get it go charge past 30% so I decided, I'm gonna poke around and I thought back on the fast charge, I wondered if it had an app, I managed to find one (Fast Battery Charging x2) and ITS CHARGING! I downloaded another app before this called Battery Mix, I love it as it has awesome battery graphs, anyways before I used Fast Battery Charging x2 it (Battery Mix) didn't have any stats on how long it would take to charge, now it does, says about 3 hrs to full, so we shall see where it goes. I don't know how the app works but I will wait and see. If this works I'll hop back to Slim and see if I can't make it work there. I don't know if it will though.
EDIT:
Got to 100%, going to flash back to Slim and see if I can't get it to charge there with the setup in CM 10 I have now, if I doesn't then I guess it must be Slim?
Edit!
Alright so back to Slim and the best I could muster is to keep my battery level the same over night. I tried using the phone for a bit and the battery drain happened again. Overnight I had nothing installed aside from gapps.
Hm...So CM10 w/ fast charge seemed to work, but when you went back to Slim the problem re-appeared? That's extremely odd. I reverted back to Slim 4.2 when C-Rom v16 was slowing down, just dirty restored and charging isn't an issue. Have you tried C-Rom v16? It's based off of Slim Rom I think.
Try it I guess, lets see if it's any other custom CM10 based ROMs. This seems like such an odd issue...
x0ne215 said:
Hm...So CM10 w/ fast charge seemed to work, but when you went back to Slim the problem re-appeared? That's extremely odd. I reverted back to Slim 4.2 when C-Rom v16 was slowing down, just dirty restored and charging isn't an issue. Have you tried C-Rom v16? It's based off of Slim Rom I think.
Try it I guess, lets see if it's any other custom CM10 based ROMs. This seems like such an odd issue...
Click to expand...
Click to collapse
Yeah, C-Rom worked great. Charged and everything. I ended up going back to Slim due to my power button being stupid again. It goes in and out and I couldn't find an option to do volume rocker wake on C-Rom so I switched back to Slim.
Its the weirdest thing. I don't even care about fixing it anymore as just figuring out the puzzle. X3
Sent from my SGH-I897 using Tapatalk 2
athdaraxen said:
Yeah, C-Rom worked great. Charged and everything. I ended up going back to Slim due to my power button being stupid again. It goes in and out and I couldn't find an option to do volume rocker wake on C-Rom so I switched back to Slim.
Its the weirdest thing. I don't even care about fixing it anymore as just figuring out the puzzle. X3
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Haha, I share that feeling. Once something is wrong and I can't figure it out, it's not even about fixing it so much as knowing WHAT was wrong. Not sure if those settings are also available on the new ROM I'm trying now (GamerzROM, oddly enough I was going to port it for the captivate this weekend but I guess the devs beat me too it). If I see them while I'm playing around today I'll shoot you a PM.
But the fact that C-ROM works great, even though it's built off Slim (I think), puzzles me completely. Have you tried any other version of Slim?
x0ne215 said:
Haha, I share that feeling. Once something is wrong and I can't figure it out, it's not even about fixing it so much as knowing WHAT was wrong. Not sure if those settings are also available on the new ROM I'm trying now (GamerzROM, oddly enough I was going to port it for the captivate this weekend but I guess the devs beat me too it). If I see them while I'm playing around today I'll shoot you a PM.
But the fact that C-ROM works great, even though it's built off Slim (I think), puzzles me completely. Have you tried any other version of Slim?
Click to expand...
Click to collapse
Its just so annoying as I don't know a lot but I am trying to learn.
And thanks that would be fantastic actually. I appreciate it. :3
No I haven't I've tried CM 10 stable, Avatar, Pac-ROM (very fun ROM so many settings to mess with), C-ROM, Xylon, and Slim.
Sent from my SGH-I897 using Tapatalk 2

Possible AOIP battery life issue???

OK, I know the battery life issue for 4.2 ROMs has been beat to death, but I've got something weird happening with AOIP on my phone that doesn't happen with other ROMs.
Basically, when I'm at work, the battery graph (from Battery Monitor Widget Pro) looks like in the AOIPbattery image attached below.
As you can see, it ate all but 3% of the battery in about 11 hours. At times Battery Monitor Widget Pro indicated it was using the battery at 11%/hr or more! This is while I'm at work, and the phone is not doing anything, just sitting on the desk with the screen off, connected to a wifi network but not doing anything with that either.
After a few days of that, I decided I needed to try something else. Originally was going to go back to my "old reliable" backup of 4.1 Rootbox, then thought instead that I'd try the last build of 4.2 Slimbean I still had as a backup. Restored that and got all my current data for the apps reloaded, seemed to be working fine (though still had the stuttering and dumping of apps issues, which was why I wuit using it). Thing is, it's using battery not much faster than the Rootbox one did. See the SlimbeanBattery image to see how it did at work. Same scenario (sitting on the desk, connected to wifi, screen off almost all day). The little bit of high usage was while I was at lunch, reading some web pages and rss feeds, so the screen was on for about a half hour.
So, I'm wondering what the heck is making it use batter so fast on AOIP? I tried several things before switching to Slimbean. Airplane mode made no difference. Used Wakelock Detector to see what was using it up, and it was some part of Android OS making AlarmManager go nuts with wakelocks.
I even backed everything up, factory wiped it a couple times, then loaded the base AOIP 6/3 ROM and loaded GAPPS to see if it still did it.
Nothing seemed to make any difference.
In one sense, I'm hoping the new build that keeps getting hinted at might correct some of this, but I kinda doubt it considering how everyone who brings up battery issues usually gets treated.
That's normal for 4.2 Roms
Sent from my HTC One X using xda premium
I see your point, why does one 4.2 room use that much more battery life then the other, it makes no sense to me. Maybe camcory can shed some light in this issue
Sent from my SGH-T679 using xda app-developers app
That's how my battery life has been on all 4.2 Roms. If aoip is worse for you then most obviously you need to switch Roms.
Sent from my HTC One X using xda premium
I really was hoping that you would see that there might be something wrong with AOIP and take a look at it at least, and not throw out the same tired response. While I do appreciate the work put into AOIP, forum thanks have not happened due to the refusal to notice the glaring issue that everyone else does.
I would really like to know if you even read my post, Smartguy? Seems not or you would have noticed that AOIP in that scenario eats battery three times faster than another 4.2 ROM. Why?
I'm not trying to upset anyone, just trying to hopefully get this resolved in an amicable manner.
Some people don't have battery drain issues that bad with AOIP. You should keep in mind that this phone was never intended to run anything above gingerbread. Every one of these phones handles issues differently, which is unfortunate, but if a Dev doesn't have the same issue it is hard to address. Its just how it is.
Sent from my SGH-T679 using xda app-developers app
Yes I read your post I wouldn't respond if I didn't. I have ran all the 4.2 Roms and with all of them I might get 10-11 hours of life. So no I don't see a problem with the ROM and if you do use another one.
Sent from my HTC One X using xda premium
smartguy044 said:
Yes I read your post I wouldn't respond if I didn't. I have ran all the 4.2 Roms and with all of them I might get 10-11 hours of life. So no I don't see a problem with the ROM and if you do use another one.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Wow hard to believe (well not really) this horse has been beat to death more times than a cat has lives! I'm pretty happy with battery life for the performance and OS I'm getting with AOIP. No hiccups and I have access to all the latest android features. The phone has a small battery anyway so if you want better battery life, time for a new phone or switch to a Gingerbread OS. I charge the phone once a day typically so that's hardly an inconvenience.
Thing is there is something major different in AOIP, as I can typically get just over 24 hours out of this battery in anything other than AOIP, including while I'm at work where the battery usage is a little higher than at home in every ROM I've tried (4.1 and 4.2 based included).
AOIP for some reason eats battery at more than 10% per hour only when I'm at work (less than 3% per hour at home) even when I haven't loaded any apps.
Every time I look at what is using it, it is either "cell standby" or "android os" that is using the most with the other of those two second and the screen usage following in a distant third.
I've tried to figure out what specific item in those two are the source, but it always comes back to some generic service or component in the os that is used by almost everything.
Really any advice to try and improve this, other than "use another ROM", would be appreciated.
Try putting your phone in airplane mode while at work and turn on WiFi. That might help with eating the battery. Especially if where you work had a poor cell reception
Sent from my SGH-T679 using xda app-developers app
get a new battery. i dont know what else to tell you. if you are getting 24 hours out of every other 4.2 rom youll be the only one. as i stated i get 10-11 tops on ANY 4.2 rom. so you have 2 choices new battery or different rom
Best thing to to is kill background data turn off Bluetooth WiFi sync and locations when not using your phone for a couple of hours. But your best bet would spring for an 2900mh battery.
tazmaniondvl said:
Try putting your phone in airplane mode while at work and turn on WiFi. That might help with eating the battery. Especially if where you work had a poor cell reception
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
That was the first thing I thought, but it acts the same.
Sent from my SGH-T679 using xda app-developers app
im going to vote you get a new battery if its that big a deal....:good:
go back to gingerbread OS. we gave you suggestions already. 1) new battery. 2) gingerbread OS. simple as that
I just don't understand this. Why is it that everyone refuses to see that there might be something wrong with AOIP compared to other _4.2_ ROMs?
I wasn't complaining about battery life on 4.2 ROMs, just noting that ONLY AOIP has this issue that I saw.
All other 4.2 ROMs used less than half the percent per hour as AOIP.
Telling me to just buy a larger battery when I don't have the money for it is not an acceptable answer. Neither is telling me to go back to the crapload called "gingerbread", whose only advantage is battery life, at the drawback of making everything else run like crap.
Guess I shouldn't have bothered, since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
dwolfman said:
I just don't understand this. Why is it that everyone refuses to see that there might be something wrong with AOIP compared to other _4.2_ ROMs?
I wasn't complaining about battery life on 4.2 ROMs, just noting that ONLY AOIP has this issue that I saw.
All other 4.2 ROMs used less than half the percent per hour as AOIP.
Telling me to just buy a larger battery when I don't have the money for it is not an acceptable answer. Neither is telling me to go back to the crapload called "gingerbread", whose only advantage is battery life, at the drawback of making everything else run like crap.
Guess I shouldn't have bothered, since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
sorry dude, i think your the one refusing to see. you seem to understand your way around, you sure your not doing something goofy on the install ?
dwolfman said:
since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
maybe you can code in a "battery fix" and share it with all of us.
Just use a different ROM. Jesus Christ!
teerout said:
sorry dude, i think your the one refusing to see. you seem to understand your way around, you sure your not doing something goofy on the install ?
Click to expand...
Click to collapse
It didn't matter what I installed or didn't install. Once I got the phone at work with AOIP on it, it ate the battery three times faster than any other 4.2 ROM. One time, to rule out anything I was setting or loading, I loaded AOIP, gapps, then put in my account info and disabled auto updates with nothing else changed. It still did it.
As QA software tester, I know how to identify software issues and bugs. The only explanation for what I have happening is there is something going on with AOIP itself to cause this. Like I've already demonstrated other 4.2 ROMs only use the battery a little faster than RootBox 4.1 (RB about 0.6%/hr vs slimbean 4.2 using 1.1 to 1.5 %/hr) with that screenshot in my OP. AOIP uses about 2.5 %/hr at home but over 10%/hr at work.
In any case, it's quite apparent now that this little group of ostriches with their heads still stuck in the sand isn't interested in hearing the truth, so consider this a closed thread.
Sent from my SGH-T679 using xda app-developers app

Categories

Resources