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

[ROM] Velocity V0.4 | LG Ally | Super Fast | VZC | Android 2.1 | Stable

Status
Not open for further replies.
Is it just me or is this extremely buggy? I followed the instructions perfectly, but it's so laggy, slow, tons of force closes and restarts itself like 2-3 times a day. I don't know if I should go back to the stock ROM (because it worked better) or try to reflash it with this again. Anyone else run into problems like this?
 
Is it just me or is this extremely buggy? I followed the instructions perfectly, but it's so laggy, slow, tons of force closes and restarts itself like 2-3 times a day. I don't know if I should go back to the stock ROM (because it worked better) or try to reflash it with this again. Anyone else run into problems like this?

Working 100% fine for me now. I had to buy a class 6 card because when I tried it with a class 4 card it was buggy for me as well. Also, use the Amon-Ra recovery to flash. That seems to work better.
 
Why is youtube force closing on me. I have velocity .4 and I'm confused. HELP!!!
I was having a boatload of trouble with the youtube app as well. I found a way (using root explorer) to copy the .apk to my sd card, then uninstall the app from the system directory, and reinstall it off the sd card. Low and behold, it worked again. Not soon after that however, I got another FC and it wouldn't let me open it anymore. This kept happening so I did some digging and, on the XDA Developers forum, I found an entire thread devoted to just this particular port of this new youtube app. A lot of people were having the same issue. It doesn't matter what ROM you have, it would force close and would never open again. I tore through the whole thread (about 9 pages deep) and came up with this: It's the app, not your phone, not your ROM, not your SD card, but the app itself. The way that this app was ported (for Eclair - Android 2.1), if you sign in to your youtube account, all you'll get is one, maybe two uses before it force closes and starts the problem. Whatever you do, don't try and put the widget up on your home screen if you've already gotten a FC, that's a whole nightmare you just don't want!!! The fix seems to be to: 1). to never sign into your youtube account through this app. If you don't sign in it will work just fine (it's what I decided to do) or 2). Remeber to sign out of your account everytime you use it and sign in (I actually only read that on the XDA site I have not tried it for myself, but I figured I'd pass along what I learned). I hope this helps and if you need a hand uninstalling the app so you can reinstall and use again, let me know, I'll walk you through what I did.
 
I'm having trouble getting Velocity 0.4 to pair with my laptop over bluetooth. This was working in the stock rom, and it would be nice, as I am currently data cableless. Every time I try to pair, Settings FCs and then tells me that it failed to pair because the pass key didn't match.
 
I was having a boatload of trouble with the youtube app as well. I found a way (using root explorer) to copy the .apk to my sd card, then uninstall the app from the system directory, and reinstall it off the sd card. Low and behold, it worked again. Not soon after that however, I got another FC and it wouldn't let me open it anymore. This kept happening so I did some digging and, on the XDA Developers forum, I found an entire thread devoted to just this particular port of this new youtube app. A lot of people were having the same issue. It doesn't matter what ROM you have, it would force close and would never open again. I tore through the whole thread (about 9 pages deep) and came up with this: It's the app, not your phone, not your ROM, not your SD card, but the app itself. The way that this app was ported (for Eclair - Android 2.1), if you sign in to your youtube account, all you'll get is one, maybe two uses before it force closes and starts the problem. Whatever you do, don't try and put the widget up on your home screen if you've already gotten a FC, that's a whole nightmare you just don't want!!! The fix seems to be to: 1). to never sign into your youtube account through this app. If you don't sign in it will work just fine (it's what I decided to do) or 2). Remeber to sign out of your account everytime you use it and sign in (I actually only read that on the XDA site I have not tried it for myself, but I figured I'd pass along what I learned). I hope this helps and if you need a hand uninstalling the app so you can reinstall and use again, let me know, I'll walk you through what I did.

Yeah, mine doesn't work anymore either. How about just installing the old youtube app? Would that be alright?
 
I had this same problem and it turned out to be a very easy fix. Just get some headphones, plug them in, unplug them, plug them back in and then take them back out. Now reboot your phone.

wasnt so easy for me... didnt work... im sending this back and probably wont root again, if i restore the OS to unrooted but cant get the recovery back to original... wat are the chances verizon will notice? any input?
 
Yeah, mine doesn't work anymore either. How about just installing the old youtube app? Would that be alright?
I tried that as well and that does work but I really like the way the new one works, what with the whole orientation changing views. But yeah, if you uninstall the new version you should be able to load the old one again with no problems.
 
You have to format, clear cache(s), then install the zip file for the rom, then reboot. But before you do all that you need to flash your rom in rom manager. If you are stuck at a boot screen you need to reboot into recovery, then clear data/cach again and use a recovery backup file if you have one made. If one is not made there are ways to fix it but I don't know them.

I've tried all of the above, and i am still stuck in the eye boot.!!! i'm not able to format the sd card ext.. i am using clockworks mod w/rom mgr.
i have tried to flash ramona recovery but it does not seem to replace the existing clockworks recovery. can you help??? any suggestions are appreciated..!!! thanks
ez
 
Anybody having this problem? I flashed Velocity 0.4 onto my Ally. Love it, lightning fast, works great. Only issue I'm having is with Live Wallpapers. I'll set one, and then I'll open an app (usually a game like Angry Birds), and then when I go back to the homescreen, my live wallpaper is gone and it defaults back to the default wallpaper.

I was originally also having the SEND/HOME button problem. Then rebooted into recover, wiped the cache, dalvik cache, and user data, and reflashed Velocity. It worked fine after that. All I got left is this wallpaper issue. Anything I can try? Thanks so much
 
I tried that as well and that does work but I really like the way the new one works, what with the whole orientation changing views. But yeah, if you uninstall the new version you should be able to load the old one again with no problems.

I couldn't uninstall for some reason. But I did go into the application setting and clear the cache and it seems to be working again :confused:
 
I couldn't uninstall for some reason. But I did go into the application setting and clear the cache and it seems to be working again :confused:
You know it's funny, I didn't even think to try that! If it's working after that then I would say that's the new fix! I had a terrible time uninstalling it, if I'd known about that I wouldn't have bothered. Thanks for the tip!
 
anyone else having this problem:
only about half of my facebook contacts pictures show up under contacts. when i go into facebook the pictures all show now problem but at the contacts screen half only show the little android pic and the other half show their facebook pic. any help would be greatly appreciated.
 
I figured out how to use the "cpu" overclocking script, and it leaves me with a couple of questions:

(1) The script offers a choice between governors called "ondemand" and "interactive". What's the difference?

(2) Is there some way to test the performance of a certain clock setting definitively when I'm ready to test it, rather than just setting it and waiting indefinitely for it to possibly crash at an inopportune moment?

Thanks,
~ Justin


I have the same question.

Also in cpuinfo it says "Scaling Governors Available: interactive conservative ondemand userspace powersave performance"

anyone know the deal these things? and what they are?
 
Kinda curious to c what he's got in store since 0.5 was tossed aside when froyo was released. All I gotta say is awsome
 
That refers to turbo feature that was incorporated in to this build. You can toggle it on or off using Scripts.

-TURBO4 enabled by default for a faster and more optimized experience (credit to Getitnowmarketing)
-turbo enable or disable GNM's Turbo performance pack


I go into Terminal Emulator, type in "turbo", it gives me the dialogue about what it does, then I type "e", press enter, and it says "permission denied". Do I have to enable something?

EDIT: I realized that I have to type "turbo -e" instead, but it still says I don't have permission.
 
So I'm gonna root my buddies replacement ALLY tomorrow... I'm guessing its got the OTA... so I'm gonna root it using universal androot and then install clockwork recovery, make a backup... then I'm gonna install this ROM... now before I I had .3 with the GIT kernel and new radio on it... I'm guessing now I can just flash this ROM and then the new radio... I need to know if that is the right order? And when I flash each thing, what do I need to wipe? Guessing the ROM needs Cache, Data and Delvik-Cache? Just need a little guidance...

I"m not a noob either, I'm on a Rooted, overclock Droid X (hardest phone in the world to work with considering a locked bootloader) and have bricked my device and come back from the brink. I know the ins and outs of flashing, just unfamiliar (not totally, but I can't remember what all I did last time I flashed his phone before he broke it) with the Ally.

Also, since this ROM has a built in custom Kernel, how do I overclock it? Do I just use SetCPU? On the DX we have to Setscaling for it to work, just wondering.

Last question... am I screwed if he took the OTA... or will it work on the current OTA for the ALLY?
 
Also, since this ROM has a built in custom Kernel, how do I overclock it? Do I just use SetCPU? On the DX we have to Setscaling for it to work, just wondering.

Last question... am I screwed if he took the OTA... or will it work on the current OTA for the ALLY?
I don't see why it wouldn't work. The OTA hasn't caused problems with rooting, as far as I know. Once you get velocity installed just go to terminal emulator, type su, then type cpu and it will give you a list of available frequencies. You can work your way up to whatever frequency the phone will run fastest with.
 
This rom is amazing! I had v3 and tried raptor and punisher but velocity just seemed much smoother and raptor couldnt even boot (maybe my ally doesnt like it) When i first switched from v3 it did just a few small funny thing, notifications and sounds for apps switched up and the color script wasnt working until i flashed savoxis' update and the first day or so there were a few fcs and reboots but its been smooth sailing since then. Im oc'd at 825, only gotten a kernel panic a few times when the phone was doing all sorts of things at once. It runs so fast i wouldnt believe it was the cheapest android phone i could get. And i love the wallpaper where the droid had the lightsaber too funny. Great work to all you who made this happen and thank all of you so much. Id die if i had to go stock again.
 
So when I flash I just wipe, cache, data and delvik-cache? I know with our ROMs on the DX we don't wipe Delvik-cache... do I need a different kernel with this like I had the turbo on when I loaded .3 for him? And do I flash the radio before or after the ROM?
 
So when I flash I just wipe, cache, data and delvik-cache? I know with our ROMs on the DX we don't wipe Delvik-cache... do I need a different kernel with this like I had the turbo on when I loaded .3 for him? And do I flash the radio before or after the ROM?

Yes.
No, it is built right in and it is "on" by default.
After. And clear cache and delvik AGAIN.
 
Status
Not open for further replies.
Back
Top Bottom