What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

LauncherPro Beta (SUPER FAST & SMOOTH Launcher!)

Okay I've never had an issue with LP, including FCs. However last night and then again today I had an odd issue. It freaked out and kept switching back and forth between screens and bringing up the screen previews. I think the app drawer MAY have popped up at one point also. It's like my poor Droid was having a seizure. :(

Locking and unlocking the phone stops this nonsense.

Edit: During this "seizure", none of the soft buttons will respond (back, menu, home, search) and touching/sliding on the screen doesn't do anything either.
 
I agree

I have never tried ADW until last night and it seems to run fine and I have it set up exactly the way I had Launcher Pro, widgets and all. Is Launcher Pro turning in to bloatware?

I went back to 0.5.4 and it's all sweet for me again. There's nothing in 0.6.0 that I need or want so I may just stay at this version. The more that gets added, the slower and more problematic things become/

I too found 0.6.0 slower on my stock Droid. I reverted back to 054 and it once again does what it does best .... RUN FAST.
 
Lately when I pull my droid out of the dock it goes to camera mode. And I've had to delete some widgets to get some speed back and end the force closes.

Is it possible all the new features are slowing it down? The main advantage of it was speed. I'd much rather have the speed.
 
Is answering a call slow for anyone else? Since I installed LauncherPro, whenever I get a call, dragging the tab over to answer the call is super slow. I'm not sure if Launcher is to blame, but I believe it might be due to LP kicking the phone application out of the memory.
I have had the same problem. Not sure if it is LauncherPro. I was going to go back to stock launcher and see how it works for a couple of days. I have Froyo on it, so I think it could be related to that also.
 
I was having an alarming number of force closes last night also. So I went into Spare Parts, and turned off "Keep Launcher In Memory", I still have that turned on in Launcher Pro. Since doing this, I've had 0 force closes. Could be coincidence, but it seems to be working so far. It may be worth trying if you're running a rom that has this option in spare parts.
 
Hey everyone,

If you're having FC's with 0.6.0 and you didn't have them before, please disable the "Keep in Memory" option, that should do the trick.

Also, to those experiencing new FC's... do you have Amazon MP3 installed? I noticed an alarming number of FC's in the submitted logs caused by Amazon MP3.

As for lag issues, next release will hopefully solve that for good.
 
Hey everyone,

If you're having FC's with 0.6.0 and you didn't have them before, please disable the "Keep in Memory" option, that should do the trick.

Also, to those experiencing new FC's... do you have Amazon MP3 installed? I noticed an alarming number of FC's in the submitted logs caused by Amazon MP3.

As for lag issues, next release will hopefully solve that for good.

Unfortunately, Fede, unless one is rooted, uninstalling Amazon MP3 is not possible.

On the other hand, I suspect the presence of the Amazon MP3 app may be an indicator rather than a cause of the problem. It generally shows up when the Droid is booted and eventually moves from active to inactive and then disappears from memory (presumably as the o/s needs the space.)

I'm guessing (and believe me, it's pure speculation) that the LP FC's may be occurring when numerous apps that fire up at boot time (including the MP3 app) haven't yet been pushed out of active memory.
 
I also reverted back to version 54. 60 was just way too laggy and gave me several random reboots. My phone is back to running the way it was--- FAST. I did like the new icon launcher bar in 60, but it was definately not worth the performance degredation. LauncherPro is a fantastic application, but just like any other development project, more features generally equates to more bugs AND a hit in performance.
 
Hey everyone,

If you're having FC's with 0.6.0 and you didn't have them before, please disable the "Keep in Memory" option, that should do the trick.

Also, to those experiencing new FC's... do you have Amazon MP3 installed? I noticed an alarming number of FC's in the submitted logs caused by Amazon MP3.

As for lag issues, next release will hopefully solve that for good.
Yeah, I tried that last night and so far, its been working.

Actually ran into a problem yesterday where the Beautiful Widgets clock stopped syncing and showed a time that was 15 minutes behind what it really was. I ended up being late to work because of it.

I have yet to see this problem replicated after turning off 'Keep in Memory'. Which in itself isn't a big deal because I wasn't bothered too much by the fact that all the widgets had to be redrawn every time I exited from a program or went from landscape to portrait or vice versa.
 
Hey everyone,

If you're having FC's with 0.6.0 and you didn't have them before, please disable the "Keep in Memory" option, that should do the trick.

Also, to those experiencing new FC's... do you have Amazon MP3 installed? I noticed an alarming number of FC's in the submitted logs caused by Amazon MP3.

As for lag issues, next release will hopefully solve that for good.

Unfortunately, Fede, unless one is rooted, uninstalling Amazon MP3 is not possible.

On the other hand, I suspect the presence of the Amazon MP3 app may be an indicator rather than a cause of the problem. It generally shows up when the Droid is booted and eventually moves from active to inactive and then disappears from memory (presumably as the o/s needs the space.)

I'm guessing (and believe me, it's pure speculation) that the LP FC's may be occurring when numerous apps that fire up at boot time (including the MP3 app) haven't yet been pushed out of active memory.


Actually the logs show that it's FCing when Amazon MP3 changes its package properties, which it shouldn't be doing often.

Either way, next version will have code changes to keep Amazon MP3 from crashing it.
 
Last edited:
Back
Top