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

Velocity Script

Status
Not open for further replies.
Umm, yeah, I didn't realize just how large the scripts file was until I saw your link to it. DAMN! That's a lot of code! Arguably however, scripts are the one thing that makes this one of the best custom roms out there, and not even just for the Ally, but out of all the roms I've read about. I like to do these periodic updates from time to time, just to give my updated 2 cents on this rom and functionality with the phone. So far I have only come across two issues since the last one of these I wrote. 1, the Pandora not working thing, which I'm not convinced is an Ally or a Velocity problem, I saw that to get it working again you have to install an older version, 1.5.6 I believe. Since doing that, it's not even an issue, so I mean whatever. 2, has anyone tried Plug In Launcher? I have and it's very hit or miss. I don't know if this is an Ally thing, a Velocity thing or simply an issue with the app but it's annoying as hell. I had it set to do one thing and one thing only. When I plug into my headphone jack, Pandora is supposed to open and begin playing automagically, this happens maybe one in four tries. Oh well, I mean it's not a killer but I feel it's my duty to report things that aren't working properly. Given that these are the only issues I've found, and they are incredibly trivial, I must say that it's a close to perfect ROM. I can't even remember how many months I've been running Velocity in some version or another and I have to say, it is great! So Savoxis I suppose no news is good news, at least on this topic!
 
Don't know whatever would possess someone to downgrade to Velocity 1, but I have to presume the older files used at that time are probably no longer available.
 
I can make another one, I had to pull that server. ( It was getting DDOSed ) And. as I am sure most of you realized the force close problems on that handful of apps is a build.prop discrepancy.

I can have the script auto patch it..... Tomorrow.... I will make a new flashable, and have the script auto fix the build.prop.

I would say I am sorry for being so inactive.....
 
Androidians​

I have solved all your problems.
I have made an update to the script. Version 39. After updating when you launch it the first time, it will patch your build.prop (if it needs it) to allow you to use the new market, age of zombies, pandora and all the rest.

I have made a NEW flashable script package, for those of you who have an olde variant that has the old hardcoded IPs. You can download this and flash it in recovery.

I have also updated the guide to use the new OTA server, which is velocity.awesomazing.com (actually this isn't too new, the guide was just old) so now the FAQ is accurate.
 
Zoandroid said:
When I searched this thread and the Velocity ROM thread using overclock and/or boot as key words I couldn't find anything. I didn't know that the way Velocity Tools sets the overclock was different from doing it by using the script accessed 'the old way' before we had Tools. That's nice to know. I'll use Tools to set it at boot and then hopefully it won't ever be an issue.

So when entering Recovery (to restore a Nandroid) the overclock has never yet occured?

Thanks!
Click to expand...

If you have been overclocking with the script, and you set it to OC at boot too high, please boot into recovery and open adb:
Code: 
mount system
cd /system/etc/init.d/
rm 01gov
rm 02freqmin
rm 03freqmax
 
savoxis said:
Androidians​

I have solved all your problems.
I have made an update to the script. Version 39. After updating when you launch it the first time, it will patch your build.prop (if it needs it) to allow you to use the new market, age of zombies, pandora and all the rest.

I have made a NEW flashable script package, for those of you who have an olde variant that has the old hardcoded IPs. You can download this and flash it in recovery.

I have also updated the guide to use the new OTA server, which is velocity.awesomazing.com (actually this isn't too new, the guide was just old) so now the FAQ is accurate.
Click to expand...

I just tried updating from version 38 and nothing happened. Please let us know when 39 is available. Thanks! (I did not think I had an old version of the script - how can I tell?)
 
eitucatsuj said:
How were you able to get netflix working on the ally? That would be really awesome... :cool:
Click to expand...

there's an .apk floating around out there. unfortunately, it runs like junk on the ally. the audio is always a few seconds behind and buffers a lot over both 3g and wifi. i had my ally overclocked to 806mhz and it didn't help at all.
 
I just flashed the VelocityScript-39-signed.zip and now every time I start the script I get:


Connecting to 50.56.77.160 (50.56.77.160:80)
wget.tar 100% |*******************************| 590k 00:00:00 ETA
MD5 Failed for Download, restarting....
Press enter to continue...

Every time I hit enter, it just repeats.

velocity fu gives:

Mirror savoxis.awesomazing.com selected...
cp: target '/system/bin/velocity' is not a directory

which makes me think something is out of whack somewhere.


EDIT: issue resolved. I had actually installed Velocity 1.0, not 1.1. Updated to 1.1 and all is well
 
eitucatsuj said:
How were you able to get netflix working on the ally? That would be really awesome... :cool:
Click to expand...

I've been trying to find ways to make it work smoother but no luck yet.
I've been also getting bored with the allys UI so ive been working on trying to port launchers i have dug out of Chinese android phones, since I support Chinese tablets and such over at android tablet forum
I've been working on my own launcher as well. The ally is slowly dieing and we have to spice up the ally.
 
I am running v 39 of the scripts (I upgraded as soon as I flashed the ROM) and I'm still getting the OTA notification. If I attempt to install the OTA (and let the recovery deal with it), it downloads but never auto reboots. Rebooting manually just reboots the phone and the OTA notification comes right back.

Do I need to force update or re-flash the v39 scripts?
 
I updated to version 39 of the scripts, but the market still closes. If I delete cache and updates, i can get into the market. But once I close and try to go back in, it crashes. The first time, it says the app is no longer installed. Any further attempts result in a error, but it dissapears before I read it.
 
NM, I guess you have to run the velocity script twice, once to download it, and once to run it. Once the update applied, everything works.
 
Status
Not open for further replies.
Back
Top Bottom