-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Motorola Defy+ #4
Comments
This should fix issue #4. Since the CyanogenMod 7.2 release doesn't support the Defy+, I have to pull in the gingerbread branch of the jordan/jordan_plus repos. Hopefully that will work.
Once I get around to testing, I plan to close this bug once the following two conditions are met:
If I can satisfy both of the above conditions, then I'll be reasonably confident that it will work on a Defy+ (and if that turns out to be wrong once I obtain Defy+ hardware, then I can reopen this issue of course). |
Oops. Now issue #4 should really be fixed, I hope.
The current merge is incomplete; jordan still builds, but jordan_plus does not. I'm working on fixing it... |
OK, both jordan and jordan_plus now build. I intend to try actually running the jordan build later today. |
The jordan build works, so I've satisfied both of my conditions and I'm closing this issue. |
My Motorola Defy phones have been dying like flies lately. They're breaking often enough that I need to move to a different kind of phone for this project.
Eventually, that's going to mean I need to redo my changes on top of Jelly Bean, but I also need to have other hardware for Gingerbread in case my user ends up being unable to adjust to Jelly Bean, or in case her current Defy breaks very soon.
For now, I should at least add support for the Motorola Defy+. It's more recent than the original Defy, and if Amazon reviews are any indication, people are happier with the reliability. It's also similar enough to the original Defy that I don't think adjusting to it should cause any problems for my user.
The text was updated successfully, but these errors were encountered: