Guest Sh4d0w940 Posted December 27, 2010 Report Posted December 27, 2010 I've been using ADW.Launcher for a while now, but lately I'm having a problem with it after unlocking the phone. It usually happens when I don't use my phone for a hour or so and when I unlock the lockscreen the launcher is unresponsive and sometimes FC's. I've tried installing the market version but that didn't fix the problem. I'm using the CM rom v0.40 with swap and overclock. Has anyone had problems like this before? Sh4d0w940
Guest peelie Posted December 27, 2010 Report Posted December 27, 2010 I've been using ADW.Launcher for a while now, but lately I'm having a problem with it after unlocking the phone. It usually happens when I don't use my phone for a hour or so and when I unlock the lockscreen the launcher is unresponsive and sometimes FC's. I've tried installing the market version but that didn't fix the problem. I'm using the CM rom v0.40 with swap and overclock. Has anyone had problems like this before? Sh4d0w940 have you tried another launcher?
Guest Sh4d0w940 Posted December 27, 2010 Report Posted December 27, 2010 have you tried another launcher? Yes, Zeam and LauncherPro but the problem occurs only with ADW. Sh4d0w940
Guest todd8 Posted January 9, 2011 Report Posted January 9, 2011 hi, I have the same problem here nexus 1 cm 6.1.1 wildmonks kernel Yes, Zeam and LauncherPro but the problem occurs only with ADW. Sh4d0w940
Guest Pulseuser1 Posted January 9, 2011 Report Posted January 9, 2011 Have you gone to the CM settings ---> perfomance settings ---> then lock home in memory....it might solve the problem a little (it solved it for me). It just keeps your default launcher in the memory at all times so it doesnt have to keep n starting up again. You might have done this already but i just thought i'd help :D
Guest Sh4d0w940 Posted January 9, 2011 Report Posted January 9, 2011 Have you gone to the CM settings ---> perfomance settings ---> then lock home in memory....it might solve the problem a little (it solved it for me). It just keeps your default launcher in the memory at all times so it doesnt have to keep n starting up again. You might have done this already but i just thought i'd help :D Yes, I'd already done that but the problem is not that the launcher is being closed. All widgets and icons are visible but more like a screenshot, in example a clock widget is visible but it shows what the time was half an hour ago or so. Sh4d0w940
Guest mrand Posted January 9, 2011 Report Posted January 9, 2011 (edited) I've been using ADW.Launcher for a while now, but lately I'm having a problem with it after unlocking the phone. It usually happens when I don't use my phone for a hour or so and when I unlock the lockscreen the launcher is unresponsive and sometimes FC's. I've tried installing the market version but that didn't fix the problem. I'm using the CM rom v0.40 with swap and overclock. Has anyone had problems like this before? Sh4d0w940 Are you using SetCPU Profiles for example for screen off?? I found my phone (or better: ADW launcher) quite unresponsive when scaling down CPU too much in standby.. Don´t know if it makes sense, but maybe this might help you :D Edited January 9, 2011 by mrand
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now