• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Juice Defender Not Working on Velocity 1.1

J

jesimpki

Newbie
Has anyone else had any issues with JD working on Velocity 1.1? It never shows that data has been disabled after the screen has been locked. I check the log and I see several error entries that it cant disable data and the app is "giving up." Anyone know of a fix or alternative? Miss going all day with my battery. Thanks
 
jesimpki said:
Has anyone else had any issues with JD working on Velocity 1.1? It never shows that data has been disabled after the screen has been locked. I check the log and I see several error entries that it cant disable data and the app is "giving up." Anyone know of a fix or alternative? Miss going all day with my battery. Thanks
Click to expand...

I hate to break it to you but juice defender really doesnt do anything to save battery that your phone it can already do
 
No, I honestly can see a difference. Sure, I could probably put it into airplane mode everytime I'm finished but I'd rather still be able to recieve texts. And for whatever reason, the ZDbox 3G toggle widget isn't working either.
 
jesimpki said:
No, I honestly can see a difference. Sure, I could probably put it into airplane mode everytime I'm finished but I'd rather still be able to recieve texts. And for whatever reason, the ZDbox 3G toggle widget isn't working either.
Click to expand...


I have used a bunch of "battery savers" including juicedefender and there really isnt much difference. Think about it it runs in the background all the time which uses memory which uses more battery. This equals less battery not more
 
Come on people stay on topic here. I am NOT trying to open up an argument about wether or not apps like Juice Defender work. I am asking why the app is not working with Velocity 1.1. Thanks!
 
I'm using Juice Defender Ultimate and I guess it's still workin'? I notice a significant difference when using aggressive setting, but hey, maybe it's just a "placebo" effect? I don't know for sure?
 
Make sure its installed in internal memory, not the SD card
you may need to move the Dalvik Cache back to data if your using toggle Dalvik2Cache
 
Dautley, good idea, I'll give that a shot and see if it makes a difference.

Azuma, I can tell a difference in battery life under aggressive as well. Especially when I could go to bed and wake up to a phone that had only lost a perecent or two while I was asleep.
 
Okay, moving the cache didn't work. But I reinstalled JD afterwards and checked its log. Apparently its not compatible with my ROM and I should get Cyanogen, according to JD. So something changed in the update from 1.0 to 1.1.
 
You can go back to velocity 1.0, Frunisher, or stock, maybe even try terminal velocity which is velocity 1.1 with a lot of things striped out.
I've gone back to Velocity 1.0 for now, it just seems to run smoother on my phone.
 
jesimpki said:
Has anyone else had any issues with JD working on Velocity 1.1? It never shows that data has been disabled after the screen has been locked. I check the log and I see several error entries that it cant disable data and the app is "giving up." Anyone know of a fix or alternative? Miss going all day with my battery. Thanks
Click to expand...

I am having that same problem. Juice defender used to save lots of battery life but it kinda sucks now.
 
Has anyone brought this up to the developers? I am getting the error "error disabling data, retrying..... permission denial: writing to secure settings requires android.permissions.WRITE_SECURE_SETTINS" it does that every time it trys to shut off the data. I'm not sure if it is because of velocity or because of the update of Superuser. Any help would be appreciated.
 
tucsontd said:
Has anyone brought this up to the developers? I am getting the error "error disabling data, retrying..... permission denial: writing to secure settings requires android.permissions.WRITE_SECURE_SETTINS" it does that every time it trys to shut off the data. I'm not sure if it is because of velocity or because of the update of Superuser. Any help would be appreciated.
Click to expand...

i said stuff to latedroid but theyve failed to fix it... i suppose i could ask the devs.
 
You must log in or register to reply here.
Back
Top Bottom