artcloud

So far this piece of trash MIUI music app does not show previously downloaded album artwork AND has downloaded a Justin Bieber album cover for the following Albums:

In This Moment - Beutiful Tragedy
In Flames - Clayman
In Flames - Colony
In Flames - Come Clarity
In Flames - Jester Race
In Flames - A Sense of Purpose
In Flames - Soundtrack to your excape
In Flames - Tokyo Showdown
In Flames - Whoracle

But it did download the correct artwork for the OLDEST In Flames combined album Lunar Strain / Subterranean. And I didn't mention the other 1/3 of my library that it is downloaded either wrong Album Covers or simply none at all. I am fairly certain iTunes can chose and download artwork better than this app, and it is absolutely terrible.

Oh, and more importantly it FCs almost everytime I am using it.

OMG! it has a visual digital oscilloscope and the buttons look like Apple buttons! Can someone tell me how this is prefered over the Stock or "Music Mod" app that actually worked without FCs and displayed Album Artwork correctly?

Please devs, ditch this in 1.2 and never port the full MIUI rom to Ally, I beg of you! This app is proof enough that we don't need it.

rayZay

Hey I need some help, when I try to boot into recovery I get stuck at the fastboot screen. I tried fixing permissions and didnt work what else can I do? I also tried looking for the install-recovery file and wasnt there in the system/etc/ folder

Last edited by rayZay; May 6th, 2011 at 10:14 AM.

Zoandroid

Your best and quickest bet would probably be going to the Ally IRC for help.

__________________
- Zoandroid -


liberum enim electronic fabrica

Biotic

Yeah i know but i like different. I was thinking of taken the touch panel from the one new samsung android phone that came out and work with it. I like everything to be at my finger tips.
Still trying to figure what you guys did to not allow spb shell 3d launcher to not run.

Last edited by Biotic; May 6th, 2011 at 11:33 AM.

artcloud

Has any dev figured out why certain apps wouldn't be compatible through the market??

The only app I am having an issue with is this:

https://market.android.com/details?id=com.dollarbank.onlinebanking

I never had an issue when I was using Velocity 1.0, the app developer thought that a custom kernel could have been the cause, but in another thread on AndroidForums I noticed that V1.1 has the same kernel and base ROM (ZVD) as V1.0.

ecb562

First really like velocity v1.1. But i have been having problems with the wifi since 1.0. Every time i try to turn on wifi on it just says error. I'm still having this problem with 1.1. I flashed it several times. I dont really know what to do. Help?

Zoandroid

Do you have other wifi devices that do connect OK in the exact same location?

When you try to turn the Ally wifi on, do you get the curved wifi "bars" indicator up in the notification bar to the left of the 3G symbol? When it doesn't work, what exactly does the error message say?

Do you have wifi at home where you could work on troubleshooting the problem, or are you only trying to access wifi spots away from home? If on a home wifi, and you can get the Ally wifi to turn on OK, the first step in diagnosing wifi connection issues is to turn off your router's encryption temporarily and see if you can then connect. If that works it can either be a matter of settings on the Ally or in the router for encryption which prevented connecting before.

Hope this helps.

azuma73

Hey guys, I just found this "Root Tools" app on the market. It looks pretty cool with many many options. I downloaded it and it looks pretty badass! However, I'm afraid to do anything with it?
Is it safe to use with velocity 1.1 without screwin' up any scripts or running processes. I just wanna be safe, since my phone is runnin' pretty sweet right now!
I know, why mess with it if it's running good? Well, this app has a lot of really cool options and tweaks and such. Seems like a lot of things we can now do with Velocity, and more!
Check it out and let me know what ya think .....thanks guys!!

__________________
Samsung Fascinate, TeamHacksung's CM9 ICS, Glitch V14 beta3 kernel
Get your own personal Dropbox now!!!! Sync your files online and across computers with Dropbox. 2GB account is free! And get extra free space from referrals http://db.tt/3IsIYJB

Zoandroid

Looks interesting, but may possibly conflict with Velocity scripts. If you do play with it, could you see, for me, if it can do something? I would like to increase the time the Ally screen stays lit when an alarm sounds from a screen-off state. The alarm sounds, I pick up the Ally. If I want to snooze it, I have to select between several choices of snooze time buttons on the calendar interface I use. And by the time I decide and reach to tap the button, the screen goes back to black until the next ring iteration 15 seconds later. It only stays on for a few seconds when all that is goingh down. I'd like to extend the on time during an alarm for even a few seconds.

mightysween

Just noticed that the phone reboots anytime I use the camera, or any app that uses the camera. This includes the built in camera app, the camcorder app, Google Docs (scanning docs w/camera), Google Shopper...basically any time the camera is used. The system freezes for about 20 seconds before soft resetting itself.

Anyone else experiencing this?

Guess I will wipe/reflash and see if the issue persists.

Zoandroid

I just read this post, grabbed my Ally, pressed the camera button, and......reboot. The screen goes black, then the Verizon logo, and then the vertical VELOCITY screen appears. I'll try it again a second time once the reboot is finished.

After the reboot, the camera worked fine taking pictures, and also as an input device for the 2 'scanning' apps I use, which are CamScanner and Document Scanner. So not sure what to think. Anyone else having this problem?

jeckel

After applying a couple themes I start to get mms force closes when I try to delete a thread or fforward a text. The market seems to crap out too. A nandroid fixes all though

TPR300C

I've searched around to see if i can find a fix to my problem but I haven't so far. My issue is upgrading to Velocity 1.1 I have downloaded Velocity via computer and transferred it to my SD card on my phone and I have also done the OTA update via terminal and i keep having the same problem. I get this error message
Flashing...
assert failed: write_raw_image("/tmp/splash.Ingram","splash") E:Error in /sdcard/download/velocity_1.1_release.zip
(Status 7)
Installation aborted.
Then if i just reboot the phone i get stuck at the new Velocity splash screen and that is it. I have to restore back to a previous points. I have tried this multiple times. I have downloaded Velocity several times just to make sure i didn't have a corrupted file and no matter what it gives me the exact error message. Any ideas?

fuhrl

After upgrading to 1.1 I noticed that the available memory for my apps on my phone nearly tripled. I was sitting at about 30mb and now my phone shows 119mb available. could this be an error?

Also, I used to be able to mount my phone to my car stereo to access the mp3 files on my phone. (I would mount it just like I would with a computer.) For some reason I cannot mount it anymore as the icons that would pop up in my notification bar do not show up anymore. (they still show up when I plug it into a computer.) Any suggestions on a fix or am I just out of luck?

Zoandroid

The memory increase comes from the movement of Dalvik-cache away from its default location over to the phone's cache memory. That's a good thing! I believe this now happens automatically when upgrading to 1.1 However, Savoxis has posted, prior to the release of 1.1, that moving it 'sometimes' conflicts with certain apps (no list of which ones).

If your car mounting is associated with an application not intrinsic to the Ally, this 'might' be the reason. You may need to move the Dalvik-cache back to its default location.

Use the Velocity Toolkit app to open Terminal, type in velocity, then on the Rom Utilities Menu Item 7, Toggle Dalvik is what you could try. Try toggling it back to not being moved, and see if that helps. You would again have less memory free, but it might fix the problem.

Last edited by Zoandroid; May 8th, 2011 at 10:28 AM.

fuhrl

Thanks for the feedback. I'd rather keep that extra space available to me on my phone so I guess it's not a huge deal if I can't mount my phone to my stereo. I have a flash drive with all my music on it anyways but it was nice to be able to charge my phone and play music off it at the same time.

Last edited by fuhrl; May 8th, 2011 at 10:47 AM.

Zoandroid

You're welcome!

Of course I could be wrong in guessing the cause, and it might be something else having to do with 1.1. There have been other issues, such as the problem with MMS messages, so this could be something else which needs to be addressed. But the above would be easy enough to check, and if it doesn't help you can always toggle Dalvik back again to regain the memory. It might be satisfying to learn if that really is the cause of your connection problem. If so, perhaps the developers can find a fix for it, and then you get the best of both worlds.

fuhrl

I'll give it a shot and report back with my results. I've also found a couple of auto mount programs i'm gonna try out as well..

mightysween

it appears to be some kind of overflow issue or CPU incompatibility. My phone was rebooting at the stock cpu settings. After my wipe/reflash i am able to use the camera (so far) at the stock 600MHz, but it becomes unstable with any overclocked frequency. no big deal, as long as it works at 600, i guess!

Zoandroid

FWIW, I haven't had another reboot from using the camera since that first one, even running clocked at 768 MHz.

artcloud

Try switching over to "interactive" governor. I know the dev team prefers "smartass", but in my experience it seems to cause the same camera issues on my phone. Mine will only OC to 729 but is stable with interactive gov. If I go higher camera causes reboot almost every time the camera loads.

Crash89

Anyone else having bluetooth Poblems?

When I try to pair it force closes half the time and the other half of the time it says passcode is incorrect, but it never gives me the option to enter the passcode.

FWIW the headset worked with no problems on Vel 1.0

Zoandroid

Whatever the devs did with the GPS radio software in the 1.1 update, my Ally now immediately locks on my Lat Lon accurately as soon as I open the market app GPS Status. It used to plod along and sometimes NEVER find my location while indoors here. Now it takes less than 3 seconds!

For some reason I have to do this with GPS Status before Latitude will show an accurate location for me. But once I do, Latitude then puts me spot on the part of my house I am sitting in!

Great work devs!

Edit - Turns out Latitude will locate too without having to open GPS Status first, it just takes a little longer. Maybe a minute.

Last edited by Zoandroid; May 9th, 2011 at 09:39 PM. Reason: updated information

c0ldburn3r

Any plans to update velocity to 2.2.2 ?

PantherVT

Yea whatever change they made to the GPS was phenomenal. I love the whole package. Great work guys.

enirgiN

I have trouble with the Widgetsoid BT control. When I try to turn BT on, it sometimes hangs. When I check through the Android Settings menu, I get "Bluetooth is connecting." If I reboot it will turn on fine with the widget. I haven't explored beyond this, though.

KingOfGreen

Oh man. . . . The only thing you want, velocity already has. So no, never. You have nothing to gain from it.

savoxis

Teaser


This is also obviously a ways off, so please dont nag

__________________
Come join us on IRC!
The mAndroid Connection
VZW Galaxy Nexus CM9 Nightly
There Aint No Such Thing As A Free Lunch
Donate

fastyz

A - M - A - Zing. This group never fails to impress me. Great work guys

j0eh4x

apologies if this has been asked, but i have a system update notification in my top bar and it wont go away... on older velocities i could just disable ota updates, how do i do this
?

Zoandroid

Actually, I noticed the tiny "1.2B" in your signature earlier today, but I didn't say anything. So, since we are on the subject, how far is a "ways"?

Zoandroid

There is one thing you can try, but I haven't yet verified it will work. Read this post:

VZE Froyo 2.2.2 Update Discussion Thread

Aside from that, DTA is working on a solution. Until then, the only other thing I know of is to go through the motions and let it 'try' to install. It will fail, and the notification will stop. But some of us have been getting repeat notifications, so that is why we are looking for more answers.

KingOfGreen

i was getting AMAZING battery life on 1.0. since updating to 1.1 it felt much shorter. i noticed i was on it a lot more getting everything back exactly to the settings i wanted and things went crazy on the forums so i was on here a lot. but its been over a week now and im still not getting nearly the same life out of my battery as i was with 1.0

Ive done everything i could on my own and cant find the problem. Ive got all my apps/widgets/services set up EXACTLY the same as with 1.0 and have be running system panel in hopes of catching something. with everything that was going on with the new release i wanted to wait for it to calm down before bringing this up and today saw others have been experiencing the same thing.

im hoping this is something that can be taken care of and if one of the team is going to look into it and there is ANYTHING i can do to help i would be glad to. im not the most experienced but i am comfortable with adb and with a little help could look into it more on my phone if someone could give me a little direction. i want to thank all of the team in advanced as i know you don't get out of this nearly what you put in.



From thread LG Ally Battery Life 100% to 90% Fast

savoxis

Measuring the drain in the battery from 100% is not really the best mo.

When a phone charges it goes up to 100% then it will stop charging to avoid over-charging the battery. The battery will then drain (about 5% iirc) before it starts charging again. So if you leave a phone on a charger all night you will have ~90-100% battery. The Phone however will report that you have 100%, it will just drain quick.

I personally haven't noticed anything out of the ordinary, but I keep my phone on a charger pretty much all the time, and rarely use it.

Since the kernel is the same between 1.0 and 1.1
The only differences that could effect your battery would be:

• 1% battery mod (wich would surly make it SEEM like its going faster)
• Calpad instead of LG Calendar
• MiuiMusic instead of MusicMod
• Velocity Toolkit

So naturally I would start any investigation in these areas, like I said, Ill keep an eye out. Let me know if you find anythjing

KingOfGreen

Thanks for the info savoxis! The big thing i noticed was how much it would drain overnight compltetely idle. After being asleep for 8 hours it dropped almost 40% when with 1.0 i maybe would have lost 10. I wiped battery stats not too long ago so im thinking maybe it wasnt reporting as accurately as before and would drop alot becuase it was previously innaccurate. I used UOT to change my battery so its always been 1% increments. Its seems to have evened out a little bit. It may be that im using it more than i think i am. Figured others saw the same thing so id bring it up. Im gonna keep tabs on it and see if there is something or if im mistaken. Again thanks for the input!

enirgiN

Thinking about the earlier thread re. GPS relative to this... might there be some power setting or parameter somewhere that could be affecing bat life? Not a change to the kernel code itself, but (a) tweak(s) that affect(s) it? I know for sure Velocity handles things like charging status better than stock FroYo - remember how the stock OS just wouldn't turn off the screen sometimes when plugged in? Just a thought from an utter Android non-techie...

icon123

As much as I like Velocity in general and appreciate the devs, I am noticing an obvious decrease in battery life from 1.0 to 1.1 and I can't figure out why either. I also was running uot 1% battery and was very impressed with how well my battery lasted in 1.0. Unfortunately, I will probably have to go back to 1.0. I did notice changing govenors seem to help a little but still no where near 1.0. Any suggestions are welcomed.

Zoandroid

Mentioning governors is a good point. Are those of you with this issue clocked at the same rate as with 1.0? I got brave and bumped mine up from 748 to 768 since I stopped playing Angry Birds, and it runs well at 768 now.

I notice on days when I am using the internet a lot on the Ally that the battery discharges faster, but aside from that I can't really say it is worse, especially since I have it clocked faster now. I do charge it every night though, so I would not be able to comment on "long term" operation without a charge. I have used the Extended Battery since day one, and have rarely ever put the standard battery in the Ally. Most of the time the larger battery takes me through a whole day no matter what I do with the Ally.

KingOfGreen

Im runnin at 748 with smartass. Same as with 1.0 wifi and gps are almost always off all my widgets update at the same intervals. Got all animations turned off. Its the same setup as 1.0 and its not a HUGE drastic difference. i dont know. Im probably just gonna watch how much i use and when and then restore my nandroid of 1.0 to try to see if its 1.1 or maybe a new/updated app. Or if ive just started using my phone more haha

tron101

My ally lasted for two days running v1.1 48 hrs,a few days ago........now if im using it to browse web or teather then it drains faster,obviously!

Zoandroid

I know I use my Ally a lot for some things I would have once done only on a PC. Email, most of these forum posts, reminder alarms, shopping lists, tracking various pieces of information, web browsing for information and sometimes even online shopping. I know many consider the Ally to be 'just a low end Android phone' but it rarely fails to meet whatever task I ask of it, and it is handy and quick, whereas going to a PC isn't always convenient. I would not be surprised to learn that I use it twice as much with Velocity 1.1 as I did before rooting.

Whatever technology replaces it when I'm due for my next upgrade will have to be pretty amazing to be better than this, at least for my purposes. ;-) I doubt I'll ever go the tablet route. I like the compact and light weight footprint in my pocket wherever I go, as well as the qwerty keyboard. That excludes many of the currently available 'high end' phones. And of cxourse the low cost was a plus, too.

artcloud

Google Music in stead of MIUI Music please! You guys will make us never want new phones! 600mhz or not Velocity makes this phone rock.

fuhrl

i've overclocked mine to 806mhz max 600mhz minimum with very minimal issues. it'll reboot itself every four or five days or so but if i go any higher it'll reboot within a half hour or so or just freeze up. i was having issues with the battery draining faster after i switched to 1.1 but i switched the governor from smartass to conservative and it seems to drain much less quickly.

from an earlier post of mine: i tried a few of the auto mount apps with no luck but i haven't tried toggling the dalvik cache yet. even if that solves the issue i probably won't leave it there. if the issue could be fixed i'm not sure if it would be worth the time or effort because there may be too many variables with all the different brands of car stereos out there.

magedassad

Thanks for v1.1, love it and it's so much faster. One thing though. I'm getting force close on the navigation and maps every time I open it. How do you fix it?

Thanks.

Biotic

Honeycomb ui? Exciting

magedassad

I wiped data and cache and reinstalled it. fixed it.

gb4fan

ok I'm lost. I installed 1.1 OTA with no problem.
I need to wipe and reinstall velocity to fix the mms problem
but not sure how to. Can't seem to do it thru terminal. Do I use recovery?
Any step by step instructions would be appreciated.

Zoandroid

Yes, you would use Recovery to do this. I recommend your first step is to create a Nandroid backup, so if you need to get 'back to square one' in your efforts you can easily do that. You might also like to use Titanium Backup to back up all your apps, unless you plan to manually re-install them.

After creating the Nandroid, check the SD Card/Nandroid/mem=223M folder to note the file name of the new backup (if you have multiple Nandroids).

Then go back into the Recovery 'wipe' menus and wipe the cache and Dalvik cache. After that, use the Flash Zip menu to locate the Velocity zip file you placed on the SD card, and flash it again. That should get it reinstalled.

Then you can restore your apps with Titanium Backup, if you backed them up.

Last edited by Zoandroid; May 14th, 2011 at 09:17 PM.

gb4fan

So I checked the SD card and there is only Velocity 1.0 zip on the card. Not the correct one I would imagine.

Zoandroid

OK. Well, you will have to re-download it, and put a copy there.

One thing I should mention, if you are like me and have a lot of folders on your SD card, the Recovery menu for flashing a zip from the SD card cannot "see" more than a single screen length of folders. It won't scroll, and will just give you the (mistaken) impression the rest of your folders are "not there". So you may have to put the zip file you want to flash in a folder which you are sure gets displayed during that step. Even putting it in a newly created folder and naming it with "__" at the beginning, like "__Folder", will STILL not put the folder at the top of the list (like it would in Windows). I don't know why.

Anyway, once you get a newly downloaded copy of Velocity 1.1 zip file, put it on the SD card and then flash it from there with Recovery.