Related
I got this app and the paid version, I'm currently at x1.30 useage. How do y'all configure it? I read post from other android users getting way way higher numbers. I just really don't how to configure it(total noob). I have root and got rid of the bloated sprintware. If anyone could post a guide or steer me in the right direction....I would ove you lots!!!
Sent from my SPH-D700 using XDA App
I am fairly new to android and I heard a lot about this app as well. I just let it configure my settings for me. I'm getting around 1.70x right now and its probably my 3rd charge cycle since I got it. It was around 1.30x at first. I got the ultimatedefender exension so it could prefer wifi before using 3g, I think that helps save on battery.
I hope there's other settings to tweak to get the most battery. I would love to go a entire day on this thing.
Sent from my SPH-D700 using XDA App
A good overview of the settings and features http://latedroid.com/juicedefender
Sent from my SPH-D700 using XDA App
I tried it a few times on the evo and felt it was not helping me. I didn't believe the numbers it said it was saving me.
on my hero it was incredible with collins battery tweak, as for the epic i dont think its fully compatible as my settings were to turn 3g off with the screen and to turn data on 5m every 2 hours to sync, 12am to 7 am airplane mode. and i didnt notice much on the epic, but then again it didnt shut my 3g off...
Mine currently says 1.74x. I don't think it's really helping though and it's kind of annoying having to pull the wait after I pull out the phone to get on the internetz
im not sure if it is helping either and it gets annoying when i am having a convo with someone on say gtalk and it disables data when my screen turns off.
I used to use it. My favorite thing about it was being able to turn off data while using certain apps/games. Also set it to check for emails every 15 minutes.
JD
I'm getting 2.25x. Install JuicePlotter and run without JD... and you can see your battery drain without JuiceDefender. I've used it for quite some time, and the graph matches my real time use (I've also used other battery monitoring apps and seen the same kind of results, JP just shows it in a nice graph). Then install JuiceDefender (I'm running the beta channel) and watch how much more slowly your battery drains.
When ACS released the latest SyndicateROM with Froyo I jumped on it and disabled JD because my girlfriend saw her battery lasting a LOT longer once TMobile (she has a Galaxy S with them) released Froyo. While it was better, it's ridiculously better with JD.
It will auto configure itself... but I customize it and have it disable during the night, 30 minute data off during the day, configured the apps I want (and yes, disabling data when using a game is a great way to save if you dont need data during the game).
Im at x2.14 now, self customized using JD Plus. 3G/Wifi turns off during certain apps running in the foreground, 3G/Wifi is off when the screen is off, Wifi automatically turns on/off depending if Im home or not. Best $1 ever spent.
I'm using super power, and JD and will be testing out, I'll let you guys know!
On custom. Data turns on every hour and during the night, data is off from 1:30AM to 8:30AM. Data is only activated after unlocking and ignores on low battery below 15%.
Everytime i use this app it starts ****ing with my permisiions and ****s up the phone i finally just said screw it. Its horrible.
I own Juice Defender Ultimate. I use the beta and It says I get around x2.35 on average. I use Advance settings and set them to my liking. I spent a week where i tried one day JD and next day no JD, same process the whole week. ended up as 30-40% more battery with JD.
I now have 100% wake time again. My ROM is Fesh 3.2 and Kernel is Netarchy 4.1.9. Is 100% wake time even an issue anymore? I remember it being an issue with the Hero, but I just started looking at it with my Evo. Using spare parts the highest on the partial wake usage is UID10018, but its a very small bar, the second is android system. Under battery usage it says running 100%, screen on 7.5% and phone on 13.8%. I have setcpu and juice defender, but I had 100% even with those uninstall ed. Any ideas would be great appreciated!
Also under running services, I have easy tether and juice defender on that list, could that be the problem?
bigupurself7 said:
I now have 100% wake time again. My ROM is Fesh 3.2 and Kernel is Netarchy 4.1.9. Is 100% wake time even an issue anymore? I remember it being an issue with the Hero, but I just started looking at it with my Evo. Using spare parts the highest on the partial wake usage is UID10018, but its a very small bar, the second is android system. Under battery usage it says running 100%, screen on 7.5% and phone on 13.8%. I have setcpu and juice defender, but I had 100% even with those uninstall ed. Any ideas would be great appreciated!
Also under running services, I have easy tether and juice defender on that list, could that be the problem?
Click to expand...
Click to collapse
Are you using BT?
I know there are some ROMs/Kernels that have an issue where they will not sleep if bluetooth is active... I'm running CM6 with King's kernel and I have to remember to manually turn off BT when I'm done so the phone will sleep.
sohr said:
Are you using BT?
I know there are some ROMs/Kernels that have an issue where they will not sleep if bluetooth is active... I'm running CM6 with King's kernel and I have to remember to manually turn off BT when I'm done so the phone will sleep.
Click to expand...
Click to collapse
Nope, not using bluetooth. I just reinstalled my rom and started fresh, im going to re-install each app, one at a time to see where the problem is. I wish there was an easier way
I have been reading A LOT about this lately, and I am also affected by this problem. No matter what you do, the problem comes back after a day or two.
I have tried uninstalling ALL my apps and still have 100% uptime. I'm starting to think this has to do with Sprint's Voicemail App that recently got updated. That's the only thing I can think of.
I have to say though, i have NOT noticed a hit on battery life. Still, this bothers me.
Ive had to deal with this a few times and it was almost always an app or a widget that was causing it. Sometimes its swype and people dont realize it.
Old thread but I just had this problem with 100% wake time and finally figured out that is was a process called com.android.providers.stocks, I just force stopped it in the "running apps" list and the little animated sync icon went off and I'm no longer at 100% wake time.... hope this helps
Hello!
I don't know it is only me or not but after my Epic 4G with the Froyo running for a day or two without reboot, If I'm trying to turn on Wi-Fi, after half minute or longer I'm getting the message 'Error" and can't run Wi-Fi. It is working only after I'm turning my phone off and then turning it on again.
Can somebody help me with it? Maybe you have some recommendation what to do?
Thank you!
midNIGHT Rom 2.6 with RFS.
Are you using juice defender? I noticed that problem a lot when I have juice defender running.
Sent from my Epic4g using the Inernet
antila said:
Hello!
I don't know it is only me or not but after my Epic 4G with the Froyo running for a day or two without reboot, If I'm trying to turn on Wi-Fi, after half minute or longer I'm getting the message 'Error" and can't run Wi-Fi. It is working only after I'm turning my phone off and then turning it on again.
Can somebody help me with it? Maybe you have some recommendation what to do?
Thank you!
midNIGHT Rom 2.6 with RFS.
Click to expand...
Click to collapse
I get this but not always. Wifi always works the first time after the phone is turned on, but after that it's about 50-50 for me whether it will come on again the next time I try vs. if I'll have to reboot the phone. I'm on Quantum 2.7 with EXT4, no juice defender/app killer/anything like that.
Unfortunately, I have no solution for you (or me), but I have found that I have a slightly better chance of getting wifi to actually turn on if I do it from the "settings" menu, rather than the status bar button.
Yes. I have a juicedfender. You think it might be the problem?
It's the DK28 rom that is the problem. The one you are running is based on the leak. I had the same problem when I installed the leaked update. Wifi would cut off sometimes and when I turn it on from the notification area it would try for a bit then say error. Going through settings to turn it on would work.
Didn't have juice defender so I'm pretty sure that isn't the prob. Soon as I switched back to DI18 never any problems.
Sent from my SPH-D700 using XDA App
For me with juice defender it happened very often. Without it not as much.
Sent from my Epic4g using the Inernet
In no way is it Juicedefender that is causing this issue. Juicedefender simply causes the wifi to be turned on more often so you notice it more, IF you have it set that way.
This is a DK28 issue. It happened to me every day when I was running the stock DK28. It has happened to me a lot less often, actually not at all, from running custom roms based on DK28, but I have only been running those for a few days. I have not intalled juicedefender on any DK28 rom I have run, so that is why I am sure it is unrelated to that program. My only theory is that juicedefender is just making the issue more apparent by constantly toggling the wifi.
I have the same issue and I dont have juice defender. I always thought it was after I had been using 4g but I do randomly get it and have to reboot. I'm on dk28 also
On any dk28 wifi only freezes itself.never ever works. ever. No JD or anything like that installed.
Sent from my SPH-D700 using Tapatalk
If I remember correctly instead of rebooting my phone when I would get that error on dk28 I would just go into the built in task manager, go to ram management and clear out both level 1 and 2. Then if I try to turn wifi on it usually works for me.
pyroswithoutfire said:
If I remember correctly instead of rebooting my phone when I would get that error on dk28 I would just go into the built in task manager, go to ram management and clear out both level 1 and 2. Then if I try to turn wifi on it usually works for me.
Click to expand...
Click to collapse
That worked for me as well. Also if you go into settings to the Wifi settings and disable it and re-enable it in there is usually worked for me.
pyroswithoutfire said:
If I remember correctly instead of rebooting my phone when I would get that error on dk28 I would just go into the built in task manager, go to ram management and clear out both level 1 and 2. Then if I try to turn wifi on it usually works for me.
Click to expand...
Click to collapse
That fixed it for me! Will I receive the official release if I installed the leaked 2.2 a few months ago?
Anyone has found a fix for this issue? I'm still getting it on EB13. Is there any utility included in Busybox (or custom) that we can reset the device manually?
megabiteg said:
Anyone has found a fix for this issue? I'm still getting it on EB13. Is there any utility included in Busybox (or custom) that we can reset the device manually?
Click to expand...
Click to collapse
I'm on EC05 and still have this problem. It seems that after several on/off cycles of the wifi it starts to do this. Rebooting solves it. Haven't tried the level 2 memory clearing. I'm running juice defender and a location-based app that toggles wifi on and off for me. Between the two, wifi gets toggles a lot.
I'm running EC05 stock, rooted.
Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.
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