Ultimate Launch

[eehrhard]

I'm glad it working for you. The activesync thing is the same thing I had happen when i corrupted my ini at the beginning as activsync would show up on the screen and it would just freeze. I was trying to update SBP PP from within UL and I realized that that caused the corruption. The only other program that did it to me was when I tried to integrate HTC Home which caused the same problem for UL when I tried to do anything to HTC.

I am guessing that the UL ini file was already FUBAR when you removed all of the plugins which is probably why you still go the same result even after you deactivated them in the UL Config.

At any rate make sure and back up!

Enjoy.

[rdavidsmith]

Originally Posted by eehrhard

I'm glad it working for you. The activesync thing is the same thing I had happen when i corrupted my ini at the beginning as activsync would show up on the screen and it would just freeze. I was trying to update SBP PP from within UL and I realized that that caused the corruption. The only other program that did it to me was when I tried to integrate HTC Home which caused the same problem for UL when I tried to do anything to HTC.

I am guessing that the UL ini file was already FUBAR when you removed all of the plugins which is probably why you still go the same result even after you deactivated them in the UL Config.

At any rate make sure and back up!

Enjoy.

Oddly enough I had it lock up on me with a screen saying that Active sync had sync'd. Which it hadn't. It locked up the device even after 4 soft resets. I had to remove the SD card with UL on it before my today screen would come back up.

[eehrhard]

Originally Posted by rdavidsmith

Oddly enough I had it lock up on me with a screen saying that Active sync had sync'd. Which it hadn't. It locked up the device even after 4 soft resets. I had to remove the SD card with UL on it before my today screen would come back up.

Its the ini file. Since you had it on the SD card I guess you have another option. I would suggest you backing up your ini once you get it working how you like so if it happens again you can restore it without having to reconfigure anything.

[clockcycle]

Originally Posted by eehrhard

I am guessing that the UL ini file was already FUBAR when you removed all of the plugins which is probably why you still go the same result even after you deactivated them in the UL Config.

At any rate make sure and back up!

Enjoy.

Did not "remove" any plugins. I flashed a clean empty rom without plugins, no contacts, nothing, new from the factory, and installed UL. On first boot, without even ever getting into the phone, already Today screen locked.

No edits, no settings, no customizations, no nothing, brand spanking new.

Try it, flash to stock 6.0 rom and install UL. Let me know the result.

-CC

[rdavidsmith]

Originally Posted by clockcycle

Did not "remove" any plugins. I flashed a clean empty rom without plugins, no contacts, nothing, new from the factory, and installed UL. On first boot, without even ever getting into the phone, already Today screen locked.

No edits, no settings, no customizations, no nothing, brand spanking new.

Try it, flash to stock 6.0 rom and install UL. Let me know the result.

-CC

That is strange I run different ROMs from time to time but right now i have UL running on stock Mobile 6 from Alltel...its the latest ROM update from this month with the Rev A updates. It also run great on my stock mobile 5 on a IP-830 on sprint. Its never been buggy for me unless i messing with plugins. However i did download a corrupt version when first installing some time ago. I just redownloaded and it worked fine.

[eehrhard]

Originally Posted by clockcycle

Did not "remove" any plugins. I flashed a clean empty rom without plugins, no contacts, nothing, new from the factory, and installed UL. On first boot, without even ever getting into the phone, already Today screen locked.

No edits, no settings, no customizations, no nothing, brand spanking new.

Try it, flash to stock 6.0 rom and install UL. Let me know the result.

-CC

That is odd. I wonder what was conflicting. Well you said its working now so thats what matters right?