• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM RELEASE] Velocity V0.4

Status
Not open for further replies.
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?
 
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.
 
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.

The weird thing is, it worked on V3...Also, my You Tube and camera work fine unlike some of the posts above. I'm not technically minded either (not for my phone, anyway), so I have no idea either. Wish someone could help me figure it out though. I need it for tomorrow! I'm going to be on the road during the football games and listen to them in my car. lol
 
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?
 
I was having problems with the camera and video playback being in black in white also. I noticed a couple days ago that a video i thought i had recorded with color played in B&W. So i went to camera and everything was showing up in B&W. I played around with settings and i lowered everything and then gave up. Not sure what was going on cause now it is in color and working fine. Im not sure if my youtube app was affected but everything is working now with color. I had also installed the VidTrim app when i first noticed this and had not used the camera prior to this.

Other then that I have had nothing but love for this ROM...Thanks Trident and all the testers for the hard work.

EDIT: I just read the post bout clearing the cache and i cleared mine after i noticed the camera issue and it must have been what fixed the problem... i had forgot all about clearing it.
 
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?

When you say little spinning circle im guessing you are referring to the one at the very bottom of screen? If im not mistaken that is where the ads would be but velocity disables them automatically.

I just installed Rom Manager and it is working fine. I do not use the clorkwork recovery. I highly recommend flashing the RA recovery since you are using a2sd and doing away with clockwork and ROM manager. The RA recovery will allow you to backup ext. They are both very good but it is alot easier to just boot into recovery and do everything from there. Hope that helps.
 
Actually I am trying to flash Amon-Ra now, but with ROM Mgr being "screwed up" as it is, it won't correctly flash it, and now I also cannot get it to correctly flash back to Clockwork either. I am on Ally IRC with Dots who is going to try to talk me through a manual recovery installation.
 
did you get the Amon-Ra recovery to flash? what was causing the problem?

I don't have much to go on here, and don't like to point fingers so I'll just say I have to conclude that for unknown reasons, on my ALLY, ROM Mgr will not run properly on the Velocity 0.4 ROM.

In short, the first time I went to use it after Velocity was running, not only was ROM Mgr (RM) missing from my apps drawer, it wasn't even listed in My Apps under the Market, despite that I have been using it for several days since rooting with Z4root.

I reinstalled RM, but then found every time I opened it the spinning circle at the bottom of the window (equivalent to Windows OS hourglass) never stopped spinning, even after running RM for 20 minutes. I had been experimenting with overclocking to 748 MHz, so at that point I clocked it back to 600 MHz and left it there (using Terminal and the Velocity 0.4 "cpu" command).

Recommendations from several people prompted me to try RM's "flash alternate recovery" to Amon-RA from the ClockworkMod Recovery I have been using all along. Trying to do so went through all the usual steps except I never got a "completed" message at the end. When I tried to boot into Amon-RA Recovery at this point I got a blue screen with something about "fast-boot" and "--suspended--" and could not type or tap on anything and get a response. Only pulling the battery and rebooting allowed me to escape that issue, and I was able to boot back into Velocity again on the Ally.

By then I had Dots helping on Ally IRC. He said to try in RM to flash clockworkmod recovery back again. I did, and it even said 'completed' but when I tried to boot to clockwork recovery at that point, I got the same unresponsive "fastboot" blue screen.

So, Dots took me aside in chat and (bless his soul!!) spent an hour talking me through a manual acquisition and installation of Amon-RA Recovery using Terminal Emulator. We had some difficulties even doing it that way but after persistent attempts it eventually worked. So I now have Amon-RA recovery on the Ally. I uninstalled ROM Manager. I have to conclude that for whatever reason I can't use RM anymore.

I would like to know if anyone else encounters this same issue. So please post here if you do.

@Dots -- We lost the chat connection for good before I had the chance to say
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!! :) 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 shouldnt have any more trouble with flashing roms. the hard part is over!
 
I wish I could run V4. I was running it for several days but couldn't get NFL mobile to work (it's a must have on my phone). I flashed back to V3 this morning and NFL mobile works again. Apparently, there's something in the kernel affecting NFL mobile on V4. :(
 
Is the "script" list above...complete? .....as far as V4 goes?
Also, is there a way to check if "turbo" is running?

THX!
 
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.
 
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!

I agree! This was an interesting learning experience, and the rewards are worth the effort. I just played Angry Birds for several screens at 768 MHz. I got one "Kernel Panic" error screen, and rebooted. I set the cpu back up to 768 (using on demand and NOT at boot), and played even longer with no issues at all this time. :)
 
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.

Are you using a standard battery or the extended version? Just curious. I use the extended battery from Verizon. I ordered it with the phone so really have not used the standard battery much at all with the Ally.
 
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 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?

You apparently cannot login with your accuont credentials. The android 2.1 build does not have the libs for the "new" youtube app to work right. You can make it work if you go into your settings>applications>manage, open the youtube app, and clear the data. The app will work after that, but if you login with your creds it will work once or twice then FC again, also if you reboot.

I hope this helps.
 
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
 
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.
 
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.
 
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.

I thought you were Under Clocked?

You know by the Ally Undertaker.
undertaker.jpg
 
Status
Not open for further replies.
Back
Top Bottom