Clean & Simple Vibrate problem
 

I posted this in Kirvin's C&S thread, but I'll post it here as well.

I upgraded one of my phones to this ROM, works great. Zero problems. I then upgraded the other one, and the vibrate function does not work. I have tried:

1. reflashing the OS.

2. Flashing to an old, official OS.

3. Reupgrading to the C&S OS.

4. Taking that re-upgraded OS and doing the LED registry edit (hklm/drivers/builtin/allledmgr/index/d-word=1

I have also soft and hard rebooted every step of the way. At no point has the vibrate feature actually vibrated. And yes, it did work fine just before the upgrade.

Any ideas?

Thanks,

Mike

Can't offer any help... but I've got the same problem. For me it started with the first time I flash my phones' ROM. (It was before C&S was released).

Hmm. So, it is a generalized upgrade problem? Not something specific to the 3.5AKU?

Interesting.

Mike

Coronach, make sure that when you click on the AllLEDMgr key, you see the following underneath:

Dll = AllLEDMgr.dll
Index = 1 (0X00001)
Order = 0 (00000000)
Prefix = LED

All my settings match...except the Dll entry. It's spelled with two lower case L's...

AllLEDMgr.dll

Sorry...typo. There should be 2 lowercase ls. Just be sure to soft reset after applying the reg edit. Other than that, I can't think of what else might be causing it. I suggest you post your questions in the Clean & Simple thread; you may get a better response.

I THINK that's what shows up on the phone (don't have it in front of me). If anything is off, it is the spelling of the AllLEDMgr.dll file. I'll check when I get home.

Thanks guys, but I don't think that's it.

Mike

I know that zizo has this same issue. He has tried many different things, but it does not appear to be related to the AllLED reg. It may just be a hardware issue. The thing to do to test is to flash back to an Official rom and see if it still does not work.

Did that. Doesn't work.

I checked again with the wife. She said that the vibrate was working properly before the upgrade, but she "was not sure" when the last time she knew, for a fact, that it worked. She thinks maybe at some point in the prior week. Hmm.

At this point, I'm leaning towards hardware failure. I dislike coincidences, but they sometimes do happen. Seems shady, but it could have failed prior to the ROM being switched. Unless anyone else has any idea?

Thanks again,

Mike