[Q] Internal system full message - Epic 4G Q&A, Help & Troubleshooting

I'm running ef02plus. My epic will sometimes go out to lala land and reboot or just become unresponsive. Sometimes the battery will drain within 5-10 minutes. It has always been a little unstable no matter what rom or radio I had installed.
I opened a shell window to find out where the space was being used and found that in /data/data/log (I believe if I remember correctly) there was about 200mb of what appeared to be core dumps from apps and system processes. I removed the files and resolved the problem for now.
Is this common? Think I should go back to stock and do a switch out? It's been annoying but I've put up with it until now.

Why don't u go to a newer gingerbread rom ef02 is way outdated
Sent from my SPH-D700 using XDA Premium App

Hmmm...I'm just one leak away from current. I didn't see much in the way of improvements?

I froze DRM launcher with mytoolbox and turned off auto sync. I've read a few posts that low signal areas can cause the battery to get hot when sync is turned on. Will try that for a few days and see how it performs. Battery life already seems better.

brewdude said:
Hmmm...I'm just one leak away from current. I didn't see much in the way of improvements?
Click to expand...
Click to collapse
EG22 is much more stable than EF02. Those reboots and lockups that you speak of occured constantly for me on EF02. I have been on EG22 since the day it came out and I have not had a single lockup, force close or reboot.

Related

[Q] Battery drain: mystery network usage?

I'm running CM6.1 RC2, and the past couple of days I have experienced excessive drain, mainly in the first 50%. I attached a picture of the issue. I went to spare parts battery history to see the network usage, since in the about phone battery usage cell standby was 84% of the battery usage, and under network usage there was just an entry for 0, using the most network. When I clicked on '0' the settings application crashed. Yesterday it dropped 35% in 2.5 hours, before it slowed down. It was ridiculous, never used to have this problem, and the battery is only a couple of weeks old so it has to be software. Today it is at 53% after 7.5 hours, which is pretty decent, but at around 70% I disabled 3g and background data to save some energy for a few hours. Is there any way of figuring out what is causing this, or should I reflash? Could it be a CM6.1 RC2 bug? Anyone else having this issue? Thanks in advance
BTW I have no idea why the dialer was so high in usage I only had like MAYBE 15 minutes total of voice calls in 2 hours. The 0 is what I'm concerned about.
Anyone? Bump? No one else is having the issue? Still happening to me on RC3.
I've been getting that problem too.
I used to have battery life of up to 4 days (Mostly standby), now I'm lucky if I get 1.5 (Same usage).
I went in to spare parts and it crashed for me too.
Battery drain here too since cm 6.1
Sent from my T-Mobile myTouch 3G Slide using XDA App
Well '0' is he system's ID, 0 is root. In the graph the blue is bytes sent, red is bytes received. Have you checked other usage like CPU usage? That might be a better indicator of what's using your battery. Then from there you can start to narrow it down to a specific process or app. I'm using the latest nightly and don't have that issue, never have. I use a bit more battery than I think I should but nothing crazy.
Do you have wifi or bluetooth on? Those drain your battery like no other.
I havent used wifi at all today, unplugged at around 6:30, it's 3:45 now and I'm at 63%, but from around 9:50 to 11:45 and then from 12:20 to 2:20 I had airplane mode enabled since the time without a signal was at 70%, very low signal area. So it seems like for only 4 hours or maybe 5~ of non airplane mode time I should be at above 63%. I only had wifi on for a half an hour today. I'm considering going back to stock for a few days just to see the battery life comparison, and then nandroiding back to CM6.1. I always end up going back to AOSP-based roms in the end. I don't have a data plan on my phone at the moment, getting it today I'm pretty sure, so could all of the blue be from the phone continuously trying to access a website? But other people said they have the same issue and I'm assuming that they have data plans, so that can't be too much related. Hmm.
I also checked cpu usage and such like you suggested, there were a lot of things listed but all but two of them were too small to even have a bar. The two that did have a bar visible were minuscule to put it lightly, so that can't be an issue. Battery use in the about phone area always has cell standby at the top, normally between 40 and 80%. It would seem like there is way too much cell communication going on, moreso than normal. Cell standby stays at the top in even high signal areas, so it's not the signal levels. Kind of stumped here.
Well if the cell is in standby then it's linked to a tower and awaiting activity. Every now and then it 'checks in'. If it's doing that too often then that could seriously drain the battery. You're right though, I'd just switch back. Trouble shooting the exact issue wouldn't be worth the time. Maybe try flashing it again later, could have just been a corrupt download that didn't flash properly.
After conditioning my battery religiously (full to empty with every charge cycle) I am back up to about 15 to 16 hours from full battery to system shut down which is way better than the 10-12 hours I was getting when I first loaded RC2. CR_OTA ROM gave me up to 24-30 hours off of one charge with the exact CPU/2g/3g/wi-fi "routine" as I am using with RC2. Tracked battery usage with System Panel app and RC2 has a steady and even drain pattern ... an even diagonal line down the graph (100% to 0%). Cell standby uses a ridiculous 40% of the battery from full charge! On the stock ROM System Panel app shows plateaus throughout the day when the phone screen is off/sleeping where battery use is virtually non-existent. I'm going to load RC3 today and track the cell standby and battery usage. This time I am not going to use setCPU and just let the ROM run as the CM team designed it to be used and see if anything has changed. I tried this with RC2 and the battery still trended absolutely evenly from 100% to 0%. I can live with a 16 hour battery cycle for the CM ROM because it is very smooth and never has a glitch. The stock ROM is smooth as well but it has some buggy behaviors that I just cannot stand for and it does not run the latest GAPPS.
I've noticed i have exacly the same problem(was actually gonna post it when i found this thread)
Needless to say that on eclair my battery lasted ~48 hours constantly, not its drained in max 24...
The highest I have EVER gotten was 24 hours, and that was on a cm6.1 nightly build, pre RC2. I loaded cr_mod and experienced a HUGE drain. I had airplane mode on, just to test, and it dropped 7% in an hour, in AIRPLANE mode, with no screen on time. I went into spare parts and looked at the usage, and sure enough, "running" was at the top, with 99% of the time spent without sleeping. This has never happened before though, so I can probably attribute that to my modifications. I deleted a few apk's and de-odexed it before I flashed it, and I have a feeling something I did corrupted something else, so I'll flash plain old cr_mod and see where that leaves me. I should probably get back into the habit of full charge/drain every cycle. I used to do that until my battery started lasting longer than I was awake for, so I always had to plug it in at around 15 to 30%. I'll run some more "trials" and see what's going on.
Also, on an unrelated note, I love the stock rom, I always love the sense UI, but I hate HTC_IME compared to the froyo Latin_IME, is there any way at all I could port the froyo Latin_IME to the eclair stock rom?
Edit: also, I flashed dumfuq's OC kernel over cr_mod, could that have been the culprit to the battery drain?
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
KCRic said:
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
Click to expand...
Click to collapse
Actually, by process of elimination, the kernel was the issue. I remember hearing about there being a bug in the older dumfuq kernels with something idle being null, I really don't remember but it had something to do with sleeping. I flashed pure CR_mod and then 3.5 dumfuq and I experienced the same issue where it wouldn't sleep. I flashed 4.0, but I think it's too soon to determine whether or not the same issue with sleep is occurring.
I tried doing what you said with LatinIME.apk, I even imported the lib file from /system/lib on CM6.1, but the it was nowhere to be found in the system when I booted. It wasn't under keyboard settings, and HTC_IME was gone. I figured it was an incompatibility between froyo and eclair, since the stock sense rom is eclair and the LatinIME.apk is from a froyo ROM. Do I have to something more than just adb push the apk and lib file? I also tried installing it with a file manager, and no surprise, problem parsing the package. It's a system apk so I didnt expect it to be able to install via a file manager. Do I have to use adb install instead of adb push? I'm wondering if htc IME is so wired into the system that it won't work that way. What if I rename LatinIME.apk to htcime.apk or whatever the name of HTCime is and see if that works, because the system may be is treating that as the stock android keyboard, rather than a third party one, because it is labeled touch input in settings, just like LatinIME in aosp roms.
I'll experiment some more I guess
edit: Nevermind, 4.0 is draining as well, albeit less rapidly. Ah well. I guess I'll have to go back to CM6.1 if I want to do overclock. Shame, I love sense so much.
ANOTHER edit: nevermind, you were right, it isn't the kernel at all. It happens when I turn wifi off. I'm assuming that's because I don't have a data plan so it's continually retrying a server that it can't access. I don't know why it didn't do this on the stock HTC kernel, but I'm pretty sure it's the issue. If I turn wifi AND mobile data connection off, it stays at normal drain as well. Well, I'm at 11% and my battery app is estimating roughly 1 hour and 20 minutes remaining, so I don't know if that's GOOD, but I'll give it a good full charge tonight and run it tomorrow. I hopefully will have data activated tomorrow so I can really test it.
Hey guys new to the slide forum but not new to the site. I come from the G1 thread and we had the similar problem. How is your battery life on a 2.1 ROM? I have my phone rooted with a Sense ROM and it has 2.2 and i do see a bad battery drain as well. I remember froyo ROMs battery life may not be the greatest yet. I remember that was always a big problem over there and it looks like it still hurts here. Have you tried setcpu settings?
Maybe this information will help, i forgot to mention last time i posted that i'm not using a HTC device, i'm using Samsung Galaxy S, and there are more ppl with this problem on our forum aswell, so maybe someone can use this information correctly, i mean, it's either a program that's doing this or some strange freaky froyo process that not everybody has? or idk..
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
KCRic said:
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
Click to expand...
Click to collapse
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
MusicMan374 said:
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
Click to expand...
Click to collapse
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
KCRic said:
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
Click to expand...
Click to collapse
Yeah that'd be cool. It must have something to do with that, since it's the cell radio sucking battery.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I flashed 6.1.0 stable, battery drain seems to be slightly less. I'm still at around 5 or 10% below where I was at this time on stock, with 9.5 hours off the charger, current level 57%. Although, I did use airplane mode for almost 2 hours, so really I'm like 10 or 20% below where I should be. I just can't figure it out, cell standby is at like 80% usage in this ROM. It's ridiculous, is it the polling intervals or something? How can it be so much less battery efficient than stock?
I flashed 6.1 RC2 with a low battery and had trouble with battery life. TMO's service was acting very strange for a couple of weeks and my cell standby was consuming a lot of juice. Flashed 6.1 RC3 with a well conditioned full battery. At first I used no setCPU just to see how things would go ... 11 hours from full battery to empty. Added setCPU to RC3 and got 27+ hours out of a full charge. Either TMO fixed it's towers or RC3 was better with cell standby because my network usage was not cranking overtime like it had been. Finally, I flashed 6.1 stable with setCPU and I average around 22 to 24 hours on one charge.
One observsation - when I first flashed RC2 I was really into my phone again. I was constantly tweaking it and flipping through options, testing apps, digging new Gapps, etc. ... bottom line I was just using my device waaaaay more than usual and I think that played a huge role in my (supposed) poor battery performance. All seems to be well with 6.1 stable.

Android system sensor usage

It is using sensor the same amount of time as the phone has been on
Sent from Snarf high on SRF 1.02 till freezes are fixed
Help
Sent from Snarf high on SRF 1.02 till freezes are fixed
Hit thanks on accident. Have a freebie.
It has been reported that our Gallery app is buggy with the sensor usage. My suggestion to see if this is the root of the problem is to uninstall/freeze the Gallery app and try a different one. Some people have mentioned that just installing the 3D Gallery from the market doesn't have the issue like the stock one. Either way let us know if that helps.
churro7 said:
It is using sensor the same amount of time as the phone has been on
Sent from Snarf high on SRF 1.02 till freezes are fixed
Click to expand...
Click to collapse
I removed it and using quick pic
Sent from Snarf high on SRF 1.02 till freezes are fixed
I have the same problem, even after uninstalling the 3d gallery it still occurs. It usally keeps my phone awake 50% of the time. I have tried so many things to fix it, nothing helps.
Sent from my SPH-D700 using XDA App
tatoniss said:
I have the same problem, even after uninstalling the 3d gallery it still occurs. It usally keeps my phone awake 50% of the time. I have tried so many things to fix it, nothing helps.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Format your SD card, Odin, redownload the ROM and modem, install CWM3, reflash modem, reflash ROM.
tatoniss said:
I have the same problem, even after uninstalling the 3d gallery it still occurs. It usally keeps my phone awake 50% of the time. I have tried so many things to fix it, nothing helps.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Gallery sensor usage and System sensor usage are two different issues. I have noticed that "System" sensor usage is always around 50%, but it does not effect partial wake usage and does not cause excessive battery drain (at least on my Epic it doesn't).
I tried wiping and using odin to go back to stock but I will try again. This time im going to keep from putting anything back on my sd card. What I noticed was even when I did this the problem occurred on 2.1 stock as well.
While my sensor usage is up. My partial wake lock is usually 50% as well.
Sent from my SPH-D700 using XDA App
tatoniss said:
I tried wiping and using odin to go back to stock but I will try again. This time im going to keep from putting anything back on my sd card. What I noticed was even when I did this the problem occurred on 2.1 stock as well.
While my sensor usage is up. My partial wake lock is usually 50% as well.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
These are most likely useless metrics.
It is affecting battery though. I usally last 8 or 9 hours which is far less than I used to. My phone also will get very warm even if I'm not using it.
Sent from my SPH-D700 using XDA App
google is of no help in locating the app or service
Well I went back to stock then flashed back up ACS 1.1.0. I flashed genocide kernel as well. the battery isn't as bad and i resorted to using autokiller set to aggressive. Most of the time its fine but it still will go back to a 50% wakelock. when this happens usually under sensor usage android system is 50% or 100%. when its 100% my phone will get warm. The only time i noticed this really happening was sometime after i got a replacement phone. Do you think its hardware related. It doesn't make sense to me. This morning my first 10% of battery lasted about 3 hours then the wake lock kicked in and it started to drop very fast. I used to make 14 hours of heavy use with this phone.
Thank you for those that have been trying to help.

[Q] Normal Stability?

Hello all. Ever since I got my EVO, I've been experiencing random restarts, even before I was rooted. Right now, I am running CM7.1 and Tiamat from kernel manager, and I probably have to do about 8 restarts and 5 battery pulls a day, no matter how often I use the phone. For instance, today I woke up and had to do a battery pull because the screen would not turn on. The light was also still orange despite the battery being fully charged. I unplugged it at about 8 in the morning and by 10 with no use, I had to pull the battery again because the screen was frozen off once again. Once I got it back on, the battery was down to 80%. I tried using it and half the apps would force close immediately, so I restarted... You get the picture. Some roms have been better than others, and kernels don't seem to make any difference, and I figured it was about normal. Then, I installed what is supposed to be a really buggy CM7 on my touchpad, and have only had to restart it once in the past 2 days, which makes me question how stable my phone actually should be. Does it seem like I should take it in to sprint, or is my experience about normal?
I also never overclock because of my already poor battery life and have tried underclocking, but don't see any noticible difference
bump. should I post somewhere else?
Run an RUU but stay s-off for the moment and see if the problem persists. If your phone begins working properly, then you can flash a recovery and flash whatever rom you want - but don't restore your backup. I'd start totally fresh if RUUing fixes your problems, don't restore your apps and data, just download them from the Market as you need them.
If the RUU doesn't help and the problem continues, take it in to Sprint. It's up to you if you want to s-on before taking it in - I've never heard of anyone getting problems from Sprint with s-off but without root, but I think it's a general rule to do so.
I hope everything works out for you!
Sent from my Evo + MIUI using Tapatalk!
I have heard and seen on here many times that random reboots are caused by battery problems, and bad software installs. Try calibrating the battery, also use battery monitor widget to see what ur batt temps are. Then reinstall all your apps, do not restore them then see if that helps.
Sent from my PC36100 using XDA App
I'll try an RUU when I get enough time to do some thorough testing. I have reinstalled everything directly from the market multiple times since I've had the phone, and also have used a total of four batteries with no change in behavior. I Will try the RUU soon though. Thanks for the replies

Sleep Of Death

I don't know if this possible but I really like to find out if there is something causing the SOD that we can actually do something about(as in it isn't hardware causing it). I get SOD's on some repack kernels but not on others. When I get it has quite frequently. I am not running setcpu nor do I have any other software controlling the cpu. I have however been using juice defender. I like the product. I am going to remove it and flash a repack kernel that I know gives me SOD's and see if something in the power saving on the JD might be contributing to it. I would like to hear from others that have this issue and see if you are running anything like setcpu or JD.
I've been thinking of something. I don't have sod at all. For those that do have sod how good is your phone at overclocking? Meaning can it run stable at like 1.6 or where does it freeze at?
I'm wondering if its something to do with the difference of processors.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84
I dont really overclock anymore but when i used to, my phone froze at 1.6. This was back when i was on calk eg30 rom. Idk what would now if i tried again
Sent from my SPH-D710 using xda premium
I haven't oc'd mine so I am not sure what it is capable of. Tomorrow I will disable the JD and flash a repack and see if that has any effect. It is frustrating because I love the repack rom's. For now I use mobile odin to flash a repack and boot to recovery if I want to nandroid then flash the stock kernel back again.
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
badname said:
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I was just curious because on the original epic I had sod on some kernels and that phones processor was terrible. It froze when I tried to overclock it. The next one I got I wad able to overclock and I never had sod. Just seeing if phones with not being able to overclock might have an issue right now.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84
Are you using SetCPU? If so, don't fix screen off at 200-500.
Yeah we really meed to figure out what the heck is going on. For the last few days i've been trying to figure out why i've been having SoD. Im on blazer ROM and ive found out that if I don't flash a new kernel i'm fine. But as soon as I flash rouge 1.4.1 or 1.4.0 I get an onslaught of SoD. Things ive tries to fix it are:
-Installing set CPU and raising the voltage and changing gov. to on demand.
-taking all the init.d scripts out of the blazer ROM zip before flashing.
-I find that when the phone is on the charger it never gets SoD
That last point leads me to believe that it has something to do with deep sleep. Because when the phone Is plugged in it isnt allowed into deep sleep mode and idles at 200Mhz. Ill be looking into this more tonight. If anyone would like to work with me i'm always in the e4gt ics dev channel on freenode.
Sent from my SPH-D710 using XDA
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
ElAguila said:
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
Click to expand...
Click to collapse
you know....oddly enough I did install juice defender a few days ago....then flashed the 1.4.0 kernel and thats when everything started.....BUT ive since reflashed the rom a million times without re installing JD and i still get SoD with the 1.4.0 kernel
If you continue to not get Sleep of deaths...will you try flashing 1.4.1 or 1.4.0?
Just to clarify, does the SOD issue include texts/calls not going thru whatsoever while phone sleeping on or off charger for more than ten minutes? I get this with any ICS up to 06, when people call me it goes to VM directly, texts go to sprint limbo. Or, do these leaks just horribly handle low signal areas? I was on stock 85 prl, and signal was about 0-1 bar sprint and force roamed on 1xrtt for 2-3 bars... since this screwed me on a couple important calls I reverted to EL29 and flashed 111115 PRL... anyone have these issues with ICS, or is it just my **** reception and network issues?
Oh, and I SWEAR... no conspiracy theory... but anyone notice pretty much all samsung leaks have issues that are magically fixed for final release? Epic froyo, GB, now ICS on the Epic Touch... just sayin... its like they dont want us daily driving these... just use em enough to beta test (really this site should be renamed XDA Beta Testers)?
The issue you are talking about sounds more like the loss of service bug that has plagued some of these phones. the sleep of death is when the screen turns off and then you can't get the phone to come back on with out holding the power button for 10 seconds or pulling the battery. I am still doing fine. I enabled juice defender but selected advanced settings and disabled jd from controlling the auto sync. I set the controls options to default. So far I haven't had an sod. I will see if I can flash those repacks but I am not sure if it will work right since I am on an ICS rom.
SoD almost certainly involves the cpu going into deep sleep and not coming out. I have never experienced this issue on the E4gT on any rom/kernel combo, but I dealt with the issue extensively on the nook color it it's early days. I can definitively say that because a large number of users are using the repacked kernels and are not having SoD issues, then it is 100% NOT repacked kernel related. SoD is caused by voltage issues or cpu step switching problems. The repacked kernels are identical in these regards across all users, therefore the repacked kernels are not causing the SoD issues.
I've had the SoD a few times on FC05 and FC06 - I'm in the process of downloading FC07 right now. It doesn't happen often (3, maybe 4 times in a few days) and I cannot pinpoint any actions preceding it. I no longer have Juice Defender installed. It's odd though, I've also had problems receiving Kik messages after a reboot. My girlfriend sent me a few messages 6 hours ago that I didn't get until I opened the app, then it's back to normal. This is a pretty regular problem. It's like I have to kick start the app before it starts. But over that 6 hours I streamed Pandora just fine and Gmail has been syncing as normal.
It is a puzzling issue. I also don't think the repack kernels acutally cause it to happen but there is something about the issue that causes it to happen frequently when using a repack. I can go back to any of the stock kernels and it works fine even with juice defender running. That is why I thought perhaps it was some app like juice defender that was causing it but people still have the issue without juice defender. Fortunately for me it seems the fix was to disable juice defender. Unfortunately for my battery though.
Well so far it seems that ive found my solution. All i did was grab the 1 click Odin to Stock Rooted EL29 and wiped everything. I wiped internal storage and flashed back to rooted stock with odin. Then i Odin'd a kernel and flashed back to blazer rom and then had to re odin the rouge kernel that was originally giving me issues. So far all is well. I suggest giving it a shot

Possible ATT JB update battery drain fix - root only

I had been getting some higher battery drain with JB than I was with ICS, both were on rooted stock ATT roms. Early on I had posted that it was about the same as ICS, but after more and more use, I was starting to find that it really wasn't. I was consuming about 5-8% per hour idle and 10+ while actually using it. The idle bothered me the most because, obviously, using a phone will drain the battery
Two things have stood out as the high consumers: Media Scanner and poor signal.
To address the media scan drain, there have been suggestions to change CWM settings to backup as .tar rather than default .dup. This ONLY works if you re-do each nandroid that was a .dup as a .tar, delete the .dup backups, and clear the unused backup data through CWM. This removes the blobs folder files which will be in the thousands.
To address the poor signal drain, I flashed the UCLH9 modem (see modems thread in the development forum). Better Battery Stats is not showing any drain caused by poor signal, and this is also reflected by actual usage, the signal is simply... better.
Consumption is marginally higher than on ICS but not nearly as high as I was experiencing. If this has already been covered, my apologies for eating up server space...
Could you alternatively put a .nomedia file into the clockworkmod folder on the device? Would that prevent it from scanning that folder?
Well I'm bone stock and not rooted, I have no backups and the media is eating my battery like mad since the update. I've killed the process several times but it starts back up on its own. The only way I know to fix it will require root.
Sent from my SAMSUNG-SGH-I747 using xda premium
There is a rogue app in the stock TW that is doing it. I have seen it in every 4.1.2 port. Run a de-bloat and it will go away.
Do you know what bloat exactly is causing it?
shoestar said:
There is a rogue app in the stock TW that is doing it. I have seen it in every 4.1.2 port. Run a de-bloat and it will go away.
Click to expand...
Click to collapse
I have all the att and Samsung bloat frozen via TiBu.
Trust me, something is there. I never had the chance to figure out exactly which app it was though. I have a feeling that it may have something to do with a Samsung app.
I would suggest using OS Monitor from the Play Store. Make it show all system processes and see if you can dig deeper into it.
Edit: Also, here is my humble opinion too. People keep wanting new and better features. Well, that always comes at a cost. Just remember that. The iPhone boys are learning that the hard way too.
shoestar said:
Trust me, something is there. I never had the chance to figure out exactly which app it was though. I have a feeling that it may have something to do with a Samsung app.
I would suggest using OS Monitor from the Play Store. Make it show all system processes and see if you can dig deeper into it.
Edit: Also, here is my humble opinion too. People keep wanting new and better features. Well, that always comes at a cost. Just remember that. The iPhone boys are learning that the hard way too.
Click to expand...
Click to collapse
I agree with that sentiment... I'm considering reverting back to ICS but the smoothness of jelly beans is too enticing.
after making these changes yesterday I got a 40% battery consumption over 9 hours with average use which IMHO is plenty.
Solution is to reboot the phone OR unmount by going into settings, storage and unmount the USB there instead of from the notification bar. I think this solution works but have not tried it myself.
rebooting whenever the os gets out of hand, or unmounting the SD card, is not a viable option IMHO.
my post was directed toward root users who have cwm installed and are experiencing the media drain because of the blob files. the modem change I tried because all the reliable jelly bean ports seem to use the H9 modem. a weak mobile signal is detrimental to battery life, as is a weak or intermittent WiFi signal.
believe me, on my rooted phone, these two changes made a real and noticeable improvement in battery life in JB. I've gone half the day today on ICS and half the day on JB. battery consumption is now within the range I had on ICS.
one the one hand, I believe that some increase in consumption is due to the "omg I has the jelly beans and I'm going to use the bejeasus out of my phone" factor. I also believe that a good number of fixes and patches are simply a placebo effect. BUT, my phone had been getting hot and tearing up the battery due to signal searching in areas where it had been fine prior to the update. heck, we have an att tower within 100 ft if my office, I typically pull 69-70mbps at work. on the k3 modem I was regularly dropping data or losing LTE. not anymore.
Un mounting then re mounting seems to have worked for me the process can now be killed!
Sent from my SAMSUNG-SGH-I747 using xda premium
1% in the last hour and it wasn't idle the whole time. sent a few texts and spent a few minutes on Facebook. I'll take it...
Check you facebook mine wa at 51% I uninstalled it and re installed fixed battery drain
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Argh. k3 modem has been simply horrible. was constantly losing data though I initially thought it was the rom i was using. Is it safe to back flash from k3 to h9 or is there a certain procedure that needs to be done?
mtl171 said:
Argh. k3 modem has been simply horrible. was constantly losing data though I initially thought it was the rom i was using. Is it safe to back flash from k3 to h9 or is there a certain procedure that needs to be done?
Click to expand...
Click to collapse
I used the CWM flashable zip from the thread in development. I did the typical cache/dalvik cache wipe first.
the last4 hours the phone was on my nightstand unplugged doinga sleep drain test. 0.3% per hour.
Ok I have found something running on my SGS3 that wasn't running all the time before and now its open constantly. I need to know if anyone knows if this one is safe to FC and then disable. Any help would be appreciated. I mean heck I wake up in the morning and this is running and I definitely am not using maps in my sleep.LOL anyways anyone know?
bogdaryl said:
Ok I have found something running on my SGS3 that wasn't running all the time before and now its open constantly. I need to know if anyone knows if this one is safe to FC and then disable. Any help would be appreciated. I mean heck I wake up in the morning and this is running and I definitely am not using maps in my sleep.LOL anyways anyone know?
Click to expand...
Click to collapse
what is it?
OOPS! Sorry about that. MAPSserviceSamsung. I finally found the list of apps safe for disable and it is safe to disable. I'm seeing a bit of improvement in battery life. I also uninstalled facebook and reinstalled it and since doing these 2 things I'm things are getting much better.
I will have to try these. My battery is horrid. My OneX got easy 30+ hours of heavy use to a charge. My SG3 is lucky to get 8 hours. I average 10% an hour on mild use, heavy use and its as high as 15%
Sent from my SGH-I747M using xda premium
bogdaryl said:
OOPS! Sorry about that. MAPSserviceSamsung. I finally found the list of apps safe for disable and it is safe to disable. I'm seeing a bit of improvement in battery life. I also uninstalled facebook and reinstalled it and since doing these 2 things I'm things are getting much better.
Click to expand...
Click to collapse
I'd like to see that list too if you don't mind sharing the info
I think I'm going to do a factory reset soon. Pretty sure that these drains are caused by some leftovers from ICS...

Categories

Resources