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

[ROM] Velocity V0.1.1 | LG Ally | Android 2.1 | ERE27 | Stable

Status
Not open for further replies.
This is pretty cool! Thought I'd jump in and root my Ally today and flash this ROM. I used Universal Androot to root the phone (worked flawlessly) and installed ROM Manager for this ROM. Has similar issues that others have seen (FC's, etc.), but after rebooting, I was able to perform the necessary functions. Backed up stock ROM, and got this puppy working! Ally is A LOT smoother now without all the VZW crap running on it.

Looking forward to exploring this whole thing more.
 
Trident said:
Pretty sure it doesn't..
In fact, I know it doesn't. I'm testing Bugless Beast 0.5 for Pete right now and the Spare Parts app included does not have that option.
Click to expand...

The spare parts I'm referring to is included in cm6 not bb, but I could be wrong.

Also would be interested to hear how well the ally will do with jit enabled.

Edit: I will be donating once I get a paypal account set up. Can't have you working like a slave for nothing.
 
GRZLA said:
Also would be interested to hear how well the ally will do with jit enabled.
Click to expand...

It runs fine, you should try the edits to the build.prop i posted earlier. this will enable jit and smooth out scrolling issues.

if you dont want to edit the file yourself, ive attached the modified build.prop (in a zip file since you cant attach .prop files to the forum) to this post

simply extract the zip and push the build.prop using adb to /system/build.prop

reboot

cheers :D:D

if you have permission errors pushing the build.prop to /system/ try theses steps:


adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cd sdcard
busybox cp -R build.prop /system
mount -t rfs -o remount,ro /dev/stl5 /system
sync
reboot
 

Attachments

Mitchell4500 said:
So if I install this will I be able to update it later in time (Without wiping all my data)?
Click to expand...

thats entirely up to the what sort of framework or library changes. most of the time wipes are standard practice in the rom flashing business.

i would recommend using adw or launcher pro and back up your desktop configuration so you can restore after wiping and install titanium backup to restore your apps

contacts should be synced up to your gmail.

also remember nandroid backups are your friend!
 
I had to reflash 0.1.1 over 0.1.1 once because I got stupid with CM6 and it worked fine without wiping data, so i guess if its exact same ROM it wont be a problem, but the next build you'll probably have to wipe all data, but like others said backups are your friend =), i have everything backed up so I can restore everything within seconds after a new ROM
 
eklipze said:
It runs fine, you should try the edits to the build.prop i posted earlier. this will enable jit and smooth out scrolling issues.

if you dont want to edit the file yourself, ive attached the modified build.prop (in a zip file since you cant attach .prop files to the forum) to this post

simply extract the zip and push the build.prop using adb to /system/build.prop

reboot

cheers :D:D

if you have permission errors pushing the build.prop to /system/ try theses steps:


adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cd sdcard
busybox cp -R build.prop /system
mount -t rfs -o remount,ro /dev/stl5 /system
sync
reboot
Click to expand...

Im having errors with after the busybox command i get
cp: can't stat 'build.prop': no such file or directory

I have build.prop in the folder where adb is located
 
mattgaitan said:
Im having errors with after the busybox command i get
cp: can't stat 'build.prop': no such file or directory

I have build.prop in the folder where adb is located
Click to expand...

Yeah the same issue here, I have it both on sd card and in Android SDK folder
 
to those having trouble w/ the busybox command, make sure the build.prop is in the sd card, the sd card is not mounted in the computer, and you are in the adb shell of the phone

also, make sure you are cd into /sdcard/ and can see build.prop in the root of your sdcard with ls

then try to

busybox cp -R build.prop /system


alternatively if that doesnt work maybe try adb push build.prop /system/build.prop
 
eklipze said:
to those having trouble w/ the busybox command, make sure the build.prop is in the sd card, the sd card is not mounted in the computer, and you are in the adb shell of the phone

also, make sure you are cd into /sdcard/ and can see build.prop in the root of your sdcard with ls

then try to

busybox cp -R build.prop /system


alternatively if that doesnt work maybe try adb push build.prop /system/build.prop
Click to expand...

got it now! thanks
 
eklipze said:
to those having trouble w/ the busybox command, make sure the build.prop is in the sd card, the sd card is not mounted in the computer, and you are in the adb shell of the phone

also, make sure you are cd into /sdcard/ and can see build.prop in the root of your sdcard with ls

then try to

busybox cp -R build.prop /system


alternatively if that doesnt work maybe try adb push build.prop /system/build.prop
Click to expand...
nope same thing =/ i tried to mount the SD card and do adb push K:/build.prop /system/build.prop but I get a "Permission denied"
 
Vmanisme said:
nope same thing =/ i tried to mount the SD card and do adb push K:/build.prop /system/build.prop but I get a "Permission denied"
Click to expand...

you absolutely do not want the sd card mounted as the phone wont be able to access it....

try this:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push build.prop /system/build.prop (if the build.prop is in the same directory as adb)

alternatively if its on the sdcard maybe try:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
busybox cp -R build.prop /system
 
eklipze said:
you absolutely do not want the sd card mounted as the phone wont be able to access it....

try this:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push build.prop /system/build.prop (if the build.prop is in the same directory as adb)

alternatively if its on the sdcard maybe try:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
busybox cp -R build.prop /system
Click to expand...
I got failed to copy 'build.prop' to '/system/build.prop': permission denied =/
 
I love this rom. I cant decide.... Launcher Pro or standard launcher... I really Like launcher pros dock bar. And the standard launcher docent have any settings (That I can find)
 
eklipze said:
It runs fine, you should try the edits to the build.prop i posted earlier. this will enable jit and smooth out scrolling issues.

if you dont want to edit the file yourself, ive attached the modified build.prop (in a zip file since you cant attach .prop files to the forum) to this post

simply extract the zip and push the build.prop using adb to /system/build.prop

reboot

cheers :D:D

if you have permission errors pushing the build.prop to /system/ try theses steps:


adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cd sdcard
busybox cp -R build.prop /system
mount -t rfs -o remount,ro /dev/stl5 /system
sync
reboot
Click to expand...

Guys.. this does not work. Don't you think if it were that easy, I would have already done it?

Enabling JIT require making a port of the JIT Compiler and including it in the curent Dalvik VM and then editing the build.prop.

Enabling Smooth Scrolling is a very tricky procedure as well and certainly not just a build.prop edit.

Sorry to burst this bubble..
 
Trident said:
Guys.. this does not work. Don't you think if it were that easy, I would have already done it?

Enabling JIT require making a port of the JIT Compiler and including it in the curent Dalvik VM and then editing the build.prop.

Enabling Smooth Scrolling is a very tricky procedure as well and certainly not just a build.prop edit.

Sorry to burst this bubble..
Click to expand...
lol glad i didnt do it, Trident dont mean to push you in any way but is there any work being done on 0.2 or are you taking a break?? Just asking out of curiosity
 
Velocity 0.2 is coming along. Very large update planned, give him time, and just keep watching!

Stuff like this isnt fast, especially when your a lone designer.
 
Just getting rid of all the lg crap made my phone go from hurkey jerky to almost no noticeable hitching while scrolling around and between home screens etc. lol.
 
RedFury said:
Velocity 0.2 is coming along. Very large update planned, give him time, and just keep watching!

Stuff like this isnt fast, especially when your a lone designer.
Click to expand...

Oh no pushing at all and I'll give donations in the future, he made the LG Ally alive, he deserves the credit and a Red Bull that he's been craving.

Also I wanted to ask if I can help test?
 
Vmanisme said:
Oh no pushing at all and I'll give donations in the future, he made the LG Ally alive, he deserves the credit and a Red Bull that he's been craving.

Also I wanted to ask if I can help test?
Click to expand...

PM me with your email address as well as your GTalk.

:)
 
Vmanisme said:
ALSO I GOT ANOTHER SUGGESTION FOR 0.2:::
When we click something on android 2.1 it gets highlighted/turns yellow can you change it to like dark blood red to match the Droid X buttons that are in this ROM, like when you click the app drawer arrow it turns blood red, can you do that for everything =D.
Click to expand...

Use LauncherPro. For over a month now you have been able to change the icon highlight style and color.
 
gndmepyon said:
Use LauncherPro. For over a month now you have been able to change the icon highlight style and color.
Click to expand...

Yeah but you guys are not considering the fact that running an app to theme your system vs theme'd ROM, I like speed > looks, theme'd ROM doesn't use more resources because its how the system is made, running an app is just throwing out ur RAM, no thank you.
 
Status
Not open for further replies.
Back
Top Bottom