The inevitable has finally happened, and an important part of the Windows Phone homebrew scene, has gone the way of the dodo. It’s not that we didn’t know it was coming, but the date when the Chevron Unlock expired, August 11, came and went without any heraldry. What does this mean? If you are still rocking a chevron unlocked device, it will relock the next time you sync with the Zune Client on your PC.
If you have moved to an app hub account, you may have to unlock your device again using the Microsoft service after chevron expires. The Chevron team negotiated a deal with Microsoft. All users that purchased an unlock token became eligible for a free registration at Microsoft’s developer app hub. For many reasons a lot of the people who had chevron, signed up for, and paid for app hub registration, and this has been an ongoing saga for the team, Microsoft and those un-lockers.
As the process started, moving close to 10,000 users, and gaining them refunds for app hub registration proved to be a mammoth task.
- 9551 ChevronWP7 Labs customers were submitted to Microsoft for refund processing.
- Only 702 of those customers came back as having a matching App Hub and ChevronWP7 Labs account.
- Of those accounts, 36 did not exist in a supported App Hub country and therefore were denied a refund.
- And of those accounts, 385 were found to have App Hub accounts opened before the January 1, 2012 date and were also denied a refund.
- As a result of this processing, 281 customers are in refund batch #1 and should be receiving their refunds by the end of July, if they haven’t received them already.
The major problem became customers live ID’s,
Specifically, we told our customers to ensure their Live ID matched what was in our ChevronWP7 Labs database. We discovered, however, Microsoft does not have access to App Hub Live ID information and therefore can only match based on App Hub profile information. So long story short, we screwed up.
The Chevron team have been open and communicative about why the process has not been smooth, and are doing as much as they can to rectify the problem, but bureaucracy and privacy procedures have greatly slowed the refund process. If you are waiting on a refund, or have been knocked back initially for a couple of the reasons listed above read this post here for instructions on what to do to help the team rectify the problem.
Things are obviously never as simple as they seem, and coming up against a corporation like MS, trying to get them to shell out money that they already have in their coffers is probably not the most straight forward thing for a few programmers to grasp.
Microsoft and our group have identified an issue where refunds were marked as invalid for customers that opened App Hub accounts way in the past (e.g. for forum use) but onlyrecently purchased a subscription.
Don’t worry, we will be resubmitting everyone for the next refund round. We’ll update you when that happens and when to expect your money back.
Obviously the work will continue till a satisfactory result is reached for all, and hopefully the team are still planning on something new for the future, with all of this experience under their belts. I’m still hopeful that ChevronWP7 has something up it;s sleeve for Windows Phone 8.
Again, all of us involved – Rafael Rivera, Chris Walsh, Long Zheng and the Windows Phone team at Microsoft — are very proud to have been able to bring the ChevronWP7 Labs experiment to fruition and are excited for what the future holds.