WidgetLocker issue

PheenX

Member
Dec 23, 2010
13
0
0
I've been using WidgetLocker on my Fascinate for a couple months and recently it has started acting differently. I have the custom screen timeout set to 10 seconds and the system screen timeout at 10 minutes. After unlocking WidgetLocker the screen timeout is supposed to change from 10 seconds to the system screen timeout but it doesn't change until I touch the screen again. Sometimes I already have something open and I am not touching the screen again because I'm reading it. So it shuts the screen off in 10 seconds. It didn't use to do this. It seems this started around the time DL09 was released OTA but I could be wrong.

Anyone else having this problem? Did I change a setting somewhere?
 
Prior to getting DL09, what version were you on? DJ05? DI01? It could just be the way it plays with the update. DJ05 and DL09 are pretty much identical. DJ05 is what Samsung was working on first, and we got leaks of it, but they couldn't get it to play nice with the VZ apps. So when they changed the update so it would work, they renamed it DL09. If you had DJ05 first, and it was working fine with that, you could go back to it and not lose any of the fixes of DL09.
 
Yeah, it's rooted. I'm not even sure the update caused it. It just seems it was around that time that I noticed it.
 
I'd assume you've also flashed CWM Recovery then. Try booting into it and clearing your dalvik cache as well as fixing permissions. It's a no harm way to try that is known to fix quirky little issues like that.
 
Actually, no, I haven't flashed anything on it. It's only rooted so that I can have wireless tethering and freeze bloatware.
 
Well if you're freezing bloatware, I'd guess you're using Titanium Backup Pro for that. You can at least clear the Dalvik cache with that by hitting menu and more. CWM would still be a good thing to have. Check the how to sticky in the ROM/Hacks section here.
 
I used Bloat freezer to freeze the apps. It was cheaper than the full version of titanium backup. I found a free app called droid tweaker that was able to clear the Dalvik cache but the problem still exists.