Back in December of 2011, the T-Mobile Samsung Vibrant was canned by the CyanogenMod team due to a 911 emergency dialing bug that was considered crucial and unfixable:

We are no longer supporting the Vibrant due to the inability to dial 911. We consider the issues related to this unresolvable without source code from Samsung related to the Radio interface layer and its interactions with the Audio layers and have taken the decision to no longer support this. We apologize for the inconvenience and strongly suggest that Vibrant users use a Samsung ROM due to the 911 issues with any ROMs based on open source code.

-SGS Team/Team Hacksung/Teamdouche

Vibrant support was officially pulled, tears were shed, and Vibrant owners lost all hope of ever seeing new CyanogenMod builds on their devices.

Good news, everyone (yes, use the right voice)! Turns out the unfixable bug was actually quite fixable after all. A change, authored by Pawit Pornkitprasan (pawitp), reverted the ban earlier today and restored the Vibrant's place in the official CM list:

Revert "Removed Vibrant from list of CyanogenMod devices"

Emergency call is fixed and we have a new maintainer now.

This reverts commit a42da130069b656c90942640ad9262217d7f04d8.

Awesome. Welcome back, folks. You know you missed us.

Update: I'm pretty sure this is the change that restored E911 support.

Artem Russakovskii
Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.

  • Aaron Ferguson

    YAY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! My Vibrant thanks you CM.

  • paul

    unbelievably happy!! now i can have ics on sgs2 and sgs vibrant!

  • Paul

    So Samsung never stepped up and helped the community out? Still took a hacker developer to eventually figure it out, figures. Thought maybe cyanogen working there may have helped

  • Irshad Chohan

    thank you.... but I have switched to ICS Passion now....

    • Aaron Ferguson

      Me too.

      (10 char?)

  • Fu4ny

    Fuck, pawtip is a great man

    • Tashlan

      Seconded. Thank you pawitp.

  • Dave

    wait,so the bug was their fault all along!??! WHAT A TWIST!!!

    • Mark

      Imagine your friend Samsung turned the lights out, you ,Cyangogen, walk towards the light switch they turned off and fall over and break your tooth and get really hurt. Hah, was Cyanogen's fault the whole dang time!

      No it wasn't their fault, it is closed source modification to what is supposed to be an open source platform that made any chance of fixing the problem the equivalent of walking in the darkness.

  • madhawa

    Thats great news for all vibrant users..yay

  • Tashlan

    Not me. I believed all along this would work out, stuck with my Vibrant, and with CM. I want to thank the CM hacker community for not letting me down. This is a wonderful gift.

    Maybe we should all send pawitp Valentine ecards? ;)

    • Tashlan

      Opps, meant to quote "Vibrant owners lost all hope" from the article, then comment. Oh well, still a happy day.