Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Not being technical minded, I have to wonder if your NFL Mobile problem is due to either Velocity using Google DNS instead of whatever DNS a stock ROM uses or maybe something to do with the Droid X video player that was included. Again, not saying either one of these is the reason (cause I know nothing about the technical side of a ROM), but looking through the release notes, it's the only things that pop out as possible causes.
No, having a custom recovery causes OTAs to fail.
I don't have any issue with B/W videos from Youtube, and my camera works fine. Wonder why only some people are experiencing this problem?
I just 'fixed' the black and white youtube and camera issue by booting into ClockworkMod Recovery and clearing the cache and Dalvik cache again. I had done that before flashing Velocity, but for some reason doing it again after Velocity is running has corrected the issue for me. You-tube and the camera are color again.
But I have another issue going on. ROM Manager, when it opens, shows the little spinning circle indicating it is busy doing something, but it never stops, even after ROM Manager has been left running on the screen for 20 minutes. I tried reinstalling ROM Manager, rebooting, the above cache wiping, but it still reacts the same way. Has anyone else had this issue? Is ROM Manager incompatible with Velocity? If so, is there an alternative to ROM Manager I can try?
did you get the Amon-Ra recovery to flash? what was causing the problem?
I am sure I speak for many when I say your tireless efforts have helped us all countless times. I would also like to thank all the other members who pitched in and helped me along this path but there are just too many to name. You guys have a great forum here, and it makes owning and using the Ally so much better. Thanks!!
well the good thing is that you now have a good recovery, the best rom released to date, and shouldn't have any more trouble with flashing roms. the hard part is over!

My YouTube eventually started playing in color again, didn't have to do anything.
Loving this ROM, it resurrected my battery. I was ready to buy a replacement because I was having to charge more and more often but the battery is back to lasting like it used to with this new ROM.
I am loving this ROM! It's fast, responsive, and great looking! I only have one problem; Youtube FCs every time I try to open it. Anybody else having/had this problem?
i to got a kernal panic once Zoandroid. i OCed it past 750+ cant remember and it started getting clunky. left it at 726 and all is well now
My Ally seems to run very well with Velocity 0.4 clocked at 748. But as i understand it, no two phone CPUs are 'exactly' the same. So one might clock at a higher frequency and be just fine, whereas another might not. I expect the same sort of "bin" system is used for these processors as is used when fabricating them for PCs.
You may be familiar with how that works, allowing some CPUs to be marketed at a specific clock rating when they can actually run a little faster and "usually" pass the tests, but when stressed they fail to certify at the higher clock speed. So they get sold as a lesser speed part because they can still pass the lower clock speed part's tests.
I have read on the Ally IRC chat room that 'the lucky ones' can clock to 825. But mine gets wonky at 768, so I have decided to just keep it at 748. It does smooth out playing Angry Birds quite well, which gave me problems with the stock ROM at stock 600 clock.
true but i did put artic silver5 on my ally's cpu and went from 768 max stable to 806 max stable... so cooling does help it run better... people in colder areas with less humidity usually can oc higher.