[5-10] nueDynamicClock 1.3 - more bug fixes

[mcw]

Originally Posted by twe90kid

1.2 doesn't have slowdown.

The dynamic speed may be delayed in responsiveness, so it does seem slower than before. I would have to agree with the other posts - when you wake the phone up from standby, it seems to take quite a bit more work to get the speed back up to the active speed. I have been unable to answer calls if the phone was in standby and wakes up as any presses (button) or slides (s2a) won't work.

[no2chem]

I'll take a look at this tommorow; I think I've been banging my head on this for too long... I know there is a issue, and I'll get it fixed as soon as I figure it out.

[worldwolf]

Bug report:

i've used both 1.0 and 1.2 version

on JuicyROM Apr 24th, Bell Touch Pro.

When using wisbar advance 3.4.3.1 (which startup automatically), i won't be able to launch the installer and the nueDynamicClock application. when i close wisbar advance, i have no problem running them. and when i start wisbar again, i can open up the installer/app without problem.

so it appears that the app need the be ran before the wisbar loaded into the memory. i wonder if there is a glitch and conflict between them?

[Calkulin]

Don't know if this is happening to anyone else or just to me but if I go to file and exit, my start menu is not working anymore using QuickMenu(haven't tried without) but if I use the x button, it continues to work fine

[Compusmurf]

1.0 was working fine for me. (I guess) I didn't really notice any battery savings.

So I upgraded to 1.2, set to 256 or 254, whatever the 2xx one was.

I locked up overnight. First time I've had that happen with my phone. I'm going to step back from this app and let it "mature" a bit more, but I believe you are definitely on the right track!!!

My fault tho, I shouldn't have done it on the phone I use for work. hahahaha. Glad I wasn't on call!

[shaggylive]

Originally Posted by Calkulin

Don't know if this is happening to anyone else or just to me but if I go to file and exit, my start menu is not working anymore using QuickMenu(haven't tried without) but if I use the x button, it continues to work fine

what ver of quickmenu? it was updated to 2.8 in Jan.

update: I now experience the same issue. i'm using quickmenu 2.8 on stock sprint rom. (dynamiclock v.1.2)

[06gmc]

Originally Posted by Compusmurf

1.0 was working fine for me. (I guess) I didn't really notice any battery savings.

So I upgraded to 1.2, set to 256 or 254, whatever the 2xx one was.

I locked up overnight. First time I've had that happen with my phone. I'm going to step back from this app and let it "mature" a bit more, but I believe you are definitely on the right track!!!

My fault tho, I shouldn't have done it on the phone I use for work. hahahaha. Glad I wasn't on call!

I had the same thing happen to me last night. Locked up had to reset. I rolled back to 1.0 and will see what happens tonight.

[entwined82]

So over the past 5-6 days I've had noticeable keyboard lag, my LCD screen image has been reversed/mirrored, sometimes the screen would not turn back on, turning back on from suspend was slow as hell answering calls was lagged and several other issues with the initial version of Dynamicclock came up too. I wasn't sure if it was my phone or what.

I switched back to the original app which just allows one constant speed, set it to 256 and things are running smooth. I guess its a sacrifice. Good battery life with weird screen/phone issues or no issues and not so good battery life.

Hopefully my radio upgrade will improve things to a tolerable level while this app matures and the kinks are worked out.

[twe90kid]

i've been experiencing the lag. when you power on from suspend mode, it takes 2/3 secs to get it to speed up again. also when phone calls come in, it takes a long time for the s2a to respond to your finger gesture. another thing that i notice was the bluetooth problem. bluetooth responds slower than normal

[djsonar]

Ok. i upgraded to juicy 7
power savings 528.384.256.122
so far no problems at all.
i will test for the next few days to see what are the best setting base on my usage.