• 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.
Matt's 175 said:
+1
Click to expand...
I dont use Clock work for my main recovery and Velocity.4 is still Glitchy for me. :confused:
All I know is that Velocity .3 works Flawless
and Punisher .1 works Flawless
Velocity .4 Not so much.

Ive been around the Block a few times with this phone.
Its nothing that I am doing. I know how to use Both Recoveries inside and out. I tutor people on how to use them Properly.

I am not trying to Rom Blame I am simply relaying my happenings.
I truly believe that each phone is different and handles differently.
I have 6 ally's at my disposal and different ally's do different things and have different quirks.
I know that may sound strange but it is the case.
 
Zoandroid said:
I hadn't noticed this, so I just tested it. Both with powering down and booting up, as well as powering down, booting to Amon RA Recovery, and then rebooting back to Velocity. In both cases I can unlock the screen as soon as it becomes possible. However, I never see the "Preparing SD card" when booting simply from the power switch. When booting from RA, at first the unlock 'buttons' are unresponsive (while it says "no service") and tapping them doesn't work, but as soon as they became responsive I was able to unlock the ally before the "Preparing SD card" showed at the top, and it didn't reboot or give me any problems.

I wonder if it also has to do with what apps a person has put on the SD card with A2SD, or if someone moves their swap file to the SD card ( I did not do that)?
Click to expand...

Question, do you have any widgets on the initial home screen? I noticed that if I remove all the widgets (Or move them to screen 2 or something), no more issue.

I think it boils down to me RTFM'ing. I do recall reading something about putting widgets back onto the system storage, or you could run into issues.
 
PSkeptic said:
Question, do you have any widgets on the initial home screen? I noticed that if I remove all the widgets (Or move them to screen 2 or something), no more issue.

I think it boils down to me RTFM'ing. I do recall reading something about putting widgets back onto the system storage, or you could run into issues.
Click to expand...

Yes, I have some widgets on the 5 pages of Home screen I am using with Launcher Pro. I also have some "Action" shortcuts provided by Launcher Pro as well.

Really the only issue I see currently is when I play Angry Birds continuously for about half an hour clocked to 748. The battery gets up near 110F and *sometimes* (no where near every time) it will spontaneously reboot after I stop playing. But I chalk that up to an overclocking issue. I don't get kernel panics though unless I bump it up to 768. And if I run it at 725 this never seems to happen. But Birds runs more smoothly at 748. :)
 
swc2001 said:
I truly believe that each phone is different and handles differently.
I have 6 ally's at my disposal and different ally's do different things and have different quirks.
I know that may sound strange but it is the case.
Click to expand...

Sounds perfectly logical to me, given how they market CPUs in different 'bins' as an example. No two of them are completely identical in their stability or performance. As an added uncertainty factor, I have seen many times how a tough problem comes down to what software you have installed as well as the order in which you installed it (especially in a Windows OS, where installing a given app will overwrite some DLL files a previous app had installed, and needs to have, even if the later app's DLL files are generations older).
 
Zoandroid said:
I just flashed Velocity 0.4. after using GParted to wipe the SD/EXT partition, and then ClockworkMod Recovery to install Velocity. So far it seems to be working OK, but I have noticed the following issues:

Lookout Mobile Security keeps FCing - uninstalled. I had minor issues with this ever since rooting anyway.

Angry Birds didn't run until I rebooted and reinstalled it.
Opera Mini browser wouldn't run until re-installed.
You Tube videos which should be in color are in B&W.

I may be able to shed some light on the B&W YouTube issue. I just tested the camera, and it, too, displays only B&W images on the viewer, but it does take color photos when it is doing that. So I think there must be an issue with the video driver in this build not displaying color video for some reason when using the camera or watching YouTube. I shot some video with the camera and it, too plays back in B&W. So apparently only motion video or "live video" is in B&W. I can view color still shots in color.

I had used the BackupTool before I flashed the ROM, and although it seems to have put my apps back, it did NOT restore "all my settings automatically". I had to reset all the things like volume controls, which ringtones to use for what (many new ones are offered, but for now I am still using what I had been using in stock VZC, so they are still there and could be restored if the program wanted to do it). If I am wrong in assuming this backup gets automatically applied, someone let me know. I thought it did.

I lost my Launcher Pro screen setup. I 'thought' I had made a backup of the 5 screens and settings I was using before, but I can't find it on the SD card so I guess I had forgotten to do it. Would be nice if those would get restored too.

Are there any known apps which simply will not run from the Velocity ROM?
Click to expand...

You should really consider using Amon-RA Recovery.

EDIT: Read some more post and it looks like you are using Amon-RA now, which is necessary for Apps2SD to work properly among other things.
 
- swc2001....ditto.....I dont use rom manager or clockwork, and neither do several other posters that appear to be experiencing some issues, I am inclined to agree with you that some some ally's are more twitchy than others, I don't believe its a rom issue as much as a level of compatibility issue especially with the ap2sd integration...but then who knows!

- grzla.....can't speak for others but I was not flaming anyone or their work/efforts in building and sharing a rom....I am experiencing an issue that I would like to resolve if at all possible....this is a community heavily trafficked by developers that are extremely knowledgeable and informative and I was looking for a potential clue as to what might be causing the problem, not a flame.
 
scotttkd said:
- swc2001....ditto.....I dont use rom manager or clockwork, and neither do several other posters that appear to be experiencing some issues, I am inclined to agree with you that some some ally's are more twitchy than others, I don't believe its a rom issue as much as a level of compatibility issue especially with the ap2sd integration...but then who knows!

- grzla.....can't speak for others but I was not flaming anyone or their work/efforts in building and sharing a rom....I am experiencing an issue that I would like to resolve if at all possible....this is a community heavily trafficked by developers that are extremely knowledgeable and informative and I was looking for a potential clue as to what might be causing the problem, not a flame.
Click to expand...

From my experiences, I don't think it's a ROM+AP2SD issue, and more a RTFM (Read the fine manual) issue with the end-user.

My case of finding a "quirk" is a perfect example. AP2SD says not to load widgets onto the SD card. I did it, ran into an issue, thought it was a "quirk" that was unknown, and found it to be well known.
 
You should really consider using Amon-RA Recovery.

EDIT: Read some more post and it looks like you are using Amon-RA now, which is necessary for Apps2SD to work properly among other things.
Click to expand...


Thanks for the info. However I had to quit using Lookout Mobile Security and then ended up switching to Amon-RA as suggested by several members on the Ally-IRC one night when I was trying to figure out what was going wrong with ROM Mgr. after I had flashed Velocity 0.4. Changing to RA was no picnic, but thanks to a full hour of IRC with Dots guiding me through terminal commands we prevailed. I won't be using ClockworkMod Recovery or ROM Mgr. again.

Nailing down a few PC issues tonight, and then I'll prepare to try out that "going back to stock for OTA Updates" procedure on the other thread.
 
So I'm gonna root my buddies replacement ALLY tomorrow... I'm guessing its got the 2.2 OTA... so I'm gonna root it using z4 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.

Thanks for the help,
John
 
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.
 
I can use universal androot as well... also, is Velocity .4 compatible with Froyo? Might be a dumb question, just wondering...
 
jonathanmsims said:
I can use universal androot as well... also, is Velocity .4 compatible with Froyo? Might be a dumb question, just wondering...
Click to expand...

No and no. If it already has the 2.2.1 update on it, you are pretty much completely stuck until one of these guys figures something out.
 
Or unless the phone still has a custom recovery on it, then I assume you will still be able to flash a different rom or restore a nandroid.
 
Matt's 175 said:
He said his friend is getting a replacement phone tomorrow, so I really doubt it has a custom recovery on it.
Click to expand...

From what he said I thought that it meant that he was just looking at it tomorrow. Didn't think that meant that hes getting a new replacement phone tomorrow
 
The replacement phone is here already... he is on it right now... I don't know yet whether or not its got the new OTA on it...
 
I have been experiencing some problems with calendar reminder alarms not sounding when they should. Since I am still running Velocity 0.4 I wanted to report this as a potential bug. I use Jorte and have also tried other calendar apps but it doesn't affect the problem of alarms not sounding.

The next problem appearing is that I can't reboot into Amon-RA Recovery. When I try I get a kernel panic. I 'did' have the Ally overclocked to 748, but never used the "overclocked at boot" option, and now I am leaving it at 600 Mhz until I get this issue under control. I could use some help trying to figure out how to boot into recovery mode. I thought maybe clearing caches might help. I also have some Nandroids and a Titanium backup I can use but I have to boot to Recovery to use the nandroid, right?

I just pulled the battery after the 2nd kernel panic attempting to get into Amon RA. This third attempt it booted into Velocity instead.
 
Finally got booted into Amon_RA. :) I'll wipe the caches and see if that helps. - Rebooting now (taking LOOOONG time on the 'eye', but it finally brought up Velocity home screen).

Now to see if the 4:00 alarm sounds.
 
jonathanmsims said:
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.
Click to expand...

If you're still wondering about this, there's a cpu script built into this ROM. In terminal, type 'su' and then 'cpu' and go from there. It explains it in the ROM release thread as well.
 
Alarms have resumed sounding as scheduled. Not sure what the problem had been, but clearing the caches may have solved it.
 
Status
Not open for further replies.
Back
Top Bottom