That will most likely cause issues with wired tether. Usb product id's are changed when tethering to support the rndis tether and mass storage is disabled while using tether. Might corrupt an sd card if that app is used.
I flashed it using Clockwork to flash RA recovery. Manually cleared data and caches and flashed from recovery mode. My phone works fine.
Same here. Been lurkin but I finally registered to say thanks for the great work and no doubt countless hours put into this trident. This rom is immaculate its blazin fast, incredibly responsive, and rock stable not to mention good looking. Easy overclock. Amazing ota update stuff. This is the only ally rom worth flashing as far as I'm concerened. Many thanks to you and the new team.
On a side note any chance of a more accurate battery statusbar icon? By this I mean updates by percentage instead of incriments of 10. This would help replace my battery widget. Thanks again
Device(s): Rooted Galaxy Nexus | Liquid ICS 1.35
Nook Color | ICS cm9 nightly kang
Carrier: Not Provided
Thanks: 64
Thanked 75 Times in 50 Posts
Quote:
Originally Posted by GRZLA
Doing so replaced the entire framework-res.apk, and in doing so you lost your reboot/recovery option when holding the power button and any other improvments made to the framework.
I figured this out the hard way...and flashed back to stock Velocity theme.lol. Thanks though. I cant wait for a theme to come out for this most awesome of awesome roms.
Trident - Thanks for the amazing ROM. I found your guide for all-things-root and think it would be good to include a link to it in the 1st post. It helped me out a bunch.
Something has to be buggy with my phone. I lost my gpu power after the rom install and the phone for me seems to run a little slower, yet everyone on here is talking about how great it runs afterwards. It takes ages for my sd card gallery to actually load or to even prepare it picture taking and when it did finally load it hadn't loaded all the pictures. Also, video playback AHH!! Not only the wvga vids I made for it, but even the lower quality ones I recorded with the phone are choppy. I even re installed the rom and cleaned up and formatted my sd card. It was running amazing on froyo alone though. Any ideas because this rom obviously brings speed for everyone else, so I'm not saying it sucks. It's gotta be my phone, but what?
Last edited by Darkangels6sic; February 5th, 2011 at 06:25 PM.
Reason: forgetfullness.
great job once again velocity makes having the ally not only bearable but enjoyable .
On a side note i updated to froyo using the non ota method that shall not be mentioned while rooted i still had recovery and was able to backup and flash 1.0 without any issue idk if this has been posted anywhere else or if it will work for everyone just putting it out there
Something has to be buggy with my phone. I lost my gpu power after the rom install and the phone for me seems to run a little slower, yet everyone on here is talking about how great it runs afterwards. It takes ages for my sd card gallery to actually load or to even prepare it picture taking and when it did finally load it hadn't loaded all the pictures. Also, video playback AHH!! Not only the wvga vids I made for it, but even the lower quality ones I recorded with the phone are choppy. I even re installed the rom and cleaned up and formatted my sd card. It was running amazing on froyo alone though. Any ideas because this rom obviously brings speed for everyone else, so I'm not saying it sucks. It's gotta be my phone, but what?
In system/build.prop disable stagefright by making them false. This will force old video codecs. Reboot.
Something has to be buggy with my phone. I lost my gpu power after the rom install and the phone for me seems to run a little slower, yet everyone on here is talking about how great it runs afterwards. It takes ages for my sd card gallery to actually load or to even prepare it picture taking and when it did finally load it hadn't loaded all the pictures. Also, video playback AHH!! Not only the wvga vids I made for it, but even the lower quality ones I recorded with the phone are choppy. I even re installed the rom and cleaned up and formatted my sd card. It was running amazing on froyo alone though. Any ideas because this rom obviously brings speed for everyone else, so I'm not saying it sucks. It's gotta be my phone, but what?
try wiping data again. This happened to me with the stock froyo rom and I laged like crazy. Wiped data and the true speed of froyo was revealed.
Ok. So how would I make them false?? And am I doing this directly in the build.prop file? Stage fright is not in the Build.prop. It is in lib though. So I tried putting media.stagefright.enable-player=false in at the first .media. and I can't save the file as a build.prop. If it helps you help me any this is my first time doing any of this.
Last edited by Darkangels6sic; February 6th, 2011 at 01:53 PM.
Reason: forgetfull
I cant figure out how to OC using scripts? Everytime I OC to 748 or higher it will continuously reboot...any help? Bad download?
unfortunately not all cpu's are able to OC. There are bunches of other threads regarding this. I would try reflashing the ROM, and make sure you wipe everything. Data, cache, and dalvik. Then try again. It may not work. If not i bet you'll be very pleased with the performance of the ROM at 600 or 729, and your battery will last longer. I can get mine to oc up to 787, but i use it at 600, smooth as glass, snappy, and the battery lasts all day.
Wow this ROM is beautiful! Love the scripts, simple enough that even I was able to OC without screwing up. Thanks so much guys... things were looking dark when some guys said they were gonna stop supporting the Ally, but for those of you who stick with this community and deal with the BS of being hounded for updates and everything else, thank you so much. You are the only reason the Ally is still worth having.
The Following User Says Thank You to PowerBomb For This Useful Post:
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Script Update 15
So I got a call from Comcast Securities this morning... Apparently they frown upon uploading more than 500gigs in 7 days. Since my home server (awesomazing) has become compromised I have decided to move the OTA server to 184.106.76.138 which is a RackSpace Hosted Gentoo 10.10 box with a 10MB connection. So it should be allot nicer for you guys.
To switch to the new server all you need to do is Update to v15. I will keep awesomazing up as long as comcast will let me, hopefully there isnt service interruption anytime soon.
Changes:
New Server, Quicker, Safer, More Expensive than the one before.
Been trying to determine my problem with Charging for the past week. Basically phone will not charge while plugged into a USB port. I tinkered through possibly apps that are running and such as well as the CPU governer. Phone seems to not only draw more power when plugged into USB but would actually decharge at a rate faster than normal usage would account for. Even on a freshly installed Velocity laydown.
Solution: Install the LG USB drivers. Why? don't have a clue, but my phone refuses to charge off of ANY USB port on a system without the LG Drivers installed. Wall chargers would charge it, just not USB.
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Quote:
Originally Posted by Morte
Just an FYI
Been trying to determine my problem with Charging for the past week. Basically phone will not charge while plugged into a USB port. I tinkered through possibly apps that are running and such as well as the CPU governer. Phone seems to not only draw more power when plugged into USB but would actually decharge at a rate faster than normal usage would account for. Even on a freshly installed Velocity laydown.
Solution: Install the LG USB drivers. Why? don't have a clue, but my phone refuses to charge off of ANY USB port on a system without the LG Drivers installed. Wall chargers would charge it, just not USB.
Seems like the issue may be related to USB tethering -- on it.
**** I THINK ITS BOOTLOOPED! WHAT DO I DO WHAT DO I DO WHAT DO I DO?!?! It just keeps saying lg then velocity. I wiped when to backup and restore then hit backup then I wiped data and cache. UGH PLEASE PM ME SOON IDK WHAT TO DO.
**** I THINK ITS BOOTLOOPED! WHAT DO I DO WHAT DO I DO WHAT DO I DO?!?! It just keeps saying lg then velocity. I wiped when to backup and restore then hit backup then I wiped data and cache. UGH PLEASE PM ME SOON IDK WHAT TO DO.
First calm down, second go to the ally irc channel and someone can help you there right now.
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Script Update 16
I felt guilty making a release that was just a server change, so I threw in some toys for you guys to play with:
Version 16:
Added Stagefright Toggle
Added LCD Density Changer
Added Used Space Checker
with the density changer: anything over 400 is pretty much unusable, might be good for blind people, I tested and you can still get to terminal to switch back, same goes for low, I whent down to 100, very small. If for some reason you adjust it too much to either way, you can run the script from a adb shell and set it back down, generally you will be ok from 150-300
Last edited by savoxis; February 7th, 2011 at 09:02 PM.
The Following 3 Users Say Thank You to savoxis For This Useful Post:
Device(s): LG Ally 2.2.1 Rooted running Velocity 1.0
Carrier: Not Provided
Thanks: 18
Thanked 3 Times in 3 Posts
Quote:
Originally Posted by savoxis
Script Update 16
I felt guilty making a release that was just a server change, so I threw in some toys for you guys to play with:
Version 16:
Added Stagefright Toggle
Added LCD Density Changer
Added Used Space Checker
with the density changer: anything over 400 is pretty much unusable, might be good for blind people, I tested and you can still get to terminal to switch back, same goes for low, I whent down to 100, very small. If for some reason you adjust it too much to either way, you can run the script from a adb shell and set it back down, generally you will be ok from 150-300
Does the Stagefright Toggle fix the problem some of us are having with choppy out-of-sync camcorder playback?
Last edited by PuNN-; February 7th, 2011 at 10:12 PM.
I felt guilty making a release that was just a server change, so I threw in some toys for you guys to play with:
Version 16:
Added Stagefright Toggle
Added LCD Density Changer
Added Used Space Checker
You guys are epic. The scripts are fun to play with. Ha ha. And that Nexus start up is sweet!
Been trying to determine my problem with Charging for the past week. Basically phone will not charge while plugged into a USB port. I tinkered through possibly apps that are running and such as well as the CPU governer. Phone seems to not only draw more power when plugged into USB but would actually decharge at a rate faster than normal usage would account for. Even on a freshly installed Velocity laydown.
Solution: Install the LG USB drivers. Why? don't have a clue, but my phone refuses to charge off of ANY USB port on a system without the LG Drivers installed. Wall chargers would charge it, just not USB.
Probably due to the usb driver subsystem change I did. On linux this is not an issue but I didnt develop under windows.
Question...what does the odex rom script do? Will it free up more memory?
Yes. Odex is the opposite of deodex. The stock lg rom is odexed and the java classes.dex are contained in an odex file. Deodexing allows theming but the side effect is the classes.dex are placed into the apk. On first boot or wipe of dalvik-cache on a deodexed rom these classes.dex are unpacked and optimized into the dalvik-cache and take up some space there. Using the odex script on velocity will re odex all the apks in system and will give you ~ 33mb more free space on /data partition at the cost of not being able to install any themes that alter the system apps after the point you odexed. Framework is left deodexed on velocity FYI.
Last edited by getitnowmarketing; February 8th, 2011 at 08:19 AM.
The Following 2 Users Say Thank You to getitnowmarketing For This Useful Post:
does anyone have drivers for windows xp for the wired tether app?? i found one on xda but i cant get it to work.
On windows greater than xp or linux no additional drivers are needed for rndis wired tether. Xp users have reported that upgrading to sp3 has the drivers included.
Id like a xp sp2 or less user to try this for me.
Download and install active sync 4.5. Yes this is for windows mobile but contains the driver you need. Download details: ActiveSync 4.5
Plug-in phone and activate the wired tether.
When its asks you for the driver generic RNDIS driver, you can choose the place of this driver (don't choose automatic).
Then point the "Find New Hardware" wizard to the directory location :
C:\Program Files\Microsoft ActiveSync\Drivers
Yes. Odex is the opposite of deodex. The stock lg rom is odexed and the java classes.dex are contained in an odex file. Deodexing allows theming but the side effect is the classes.dex are placed into the apk. On first boot or wipe of dalvik-cache on a deodexed rom these classes.dex are unpacked and optimized into the dalvik-cache and take up some space there. Using the odex script on velocity will re odex all the apks in system and will give you ~ 33mb more free space on /data partition at the cost of not being able to install any themes that alter the system apps after the point you odexed. Framework is left deodexed on velocity FYI.
is there a script to deodex the rom if i decide to theme later? or will i have to reflash to get back to deodexed?
Ok so I was one of those curious people who flashed velc. 1 via ra recovery with eclair. Course it didn't work. Just flashed velocity and lg. So I flashed back to velc 0.4. But now every time I go into ra recovery. The velocity logo appears. That suppose to happen or a side affect of doen somtin u were told not to do? And another question. Why can't the ota command be installed on velc 0.4 to install v1 on a eclair device? Wouldn't that work since verizon can do it. Y can't we? An attempt to install 2.2 on allys via custom command?
Ok so I was one of those curious people who flashed velc. 1 via ra recovery with eclair. Course it didn't work. Just flashed velocity and lg. So I flashed back to velc 0.4. But now every time I go into ra recovery. The velocity logo appears. That suppose to happen or a side affect of doen somtin u were told not to do? And another question. Why can't the ota command be installed on velc 0.4 to install v1 on a eclair device? Wouldn't that work since verizon can do it. Y can't we? An attempt to install 2.2 on allys via custom command?
ok almost evey post you have made on this site is looking for an easy way to stay rooted and move to 2.2.1. The steps are not really that hard. It took me about 1.5 hrs to do. All the time you have wasted with asking how to do this easier and you could have been done by now. You wont brick your phone just do it.
Just curious, this is more a question than a reply. I have the same issue since version.04 that I can only charge when connected at home and not at work on my work pc. When you install drivers, does the drivertell the USB port to "up" the voltage? I was thinking that normal usb ports put out a little over 3 volts but the battery needs more or actually it does discharge? Further note, my co-worker has the same problem... completely different phone all stock. If this theory is correct then people can understand the importance of installing the correct drivers.
Ok so I was one of those curious people who flashed velc. 1 via ra recovery with eclair. Course it didn't work. Just flashed velocity and lg. So I flashed back to velc 0.4. But now every time I go into ra recovery. The velocity logo appears. That suppose to happen or a side affect of doen somtin u were told not to do? And another question. Why can't the ota command be installed on velc 0.4 to install v1 on a eclair device? Wouldn't that work since verizon can do it. Y can't we? An attempt to install 2.2 on allys via custom command?
Quote:
Originally Posted by EpicFailz
ok almost evey post you have made on this site is looking for an easy way to stay rooted and move to 2.2.1. The steps are not really that hard. It took me about 1.5 hrs to do. All the time you have wasted with asking how to do this easier and you could have been done by now. You wont brick your phone just do it.
I have to agree with Epic on this one, there really isn't an "easy way out" of this one. You have to remember, if there was an easier way to get the 2.2.1 update while maintaining Fastboot and Root Access, I'm sure they (Trident, Getitnowmarketing, and Savoxis, the brains behind this Rom) would have revealed that information by now instead of just directing people to the http://androidforums.com/ally-all-things-root/263285-guide-froyo-2-2-1-root-users.html link to get there. There is a "One Click Root Method for Froyo 2.2.1 on the LG Ally" but you won't get the benefits of doing it the long way. These guys have put a lot of effort into coming up with this method and have had much more feedback since the day that post was released, so it's a much better method now. If you still can't seem to get over your fears about updating check this out: My guide to the Froyo\root update.... It's a method that a lot of people who seem to be afraid of Tridents complete method have tried with success and relative ease. Give it a try, if you get stuck or have questions there always the freenode Web IRC (qwebirc) avenue. The people who built this rom along with other Android experts are there chatting in realtime to help with this exact kind of thing. Good luck amigo, I hope all the best for you and your quest for Ally Greatness!
The Following User Says Thank You to fltblkvic For This Useful Post:
is there a script to deodex the rom if i decide to theme later? or will i have to reflash to get back to deodexed?
At this time no. Its a possbility but we will need to change some of the odexing method. Reflash to go back to deodexed.
Quote:
Originally Posted by rgocal
Ok so I was one of those curious people who flashed velc. 1 via ra recovery with eclair. Course it didn't work. Just flashed velocity and lg. So I flashed back to velc 0.4. But now every time I go into ra recovery. The velocity logo appears. That suppose to happen or a side affect of doen somtin u were told not to do? And another question. Why can't the ota command be installed on velc 0.4 to install v1 on a eclair device? Wouldn't that work since verizon can do it. Y can't we? An attempt to install 2.2 on allys via custom command?
Velocity comes with a Velocity splashed ra recovery but is the same as the latest version I have on rom manger in every other way. Only the stock recovery can flash the updated radio needed to run froyo roms. All flashing radios that we did on eclair with a custom recovery (Ra or Clockwork) was just a placebo. That's why you have to follow the upgrade to froyo method. If thats not something you want to do maybe stay on eclair or stay stock.
Quote:
Originally Posted by Fishndad
Just curious, this is more a question than a reply. I have the same issue since version.04 that I can only charge when connected at home and not at work on my work pc. When you install drivers, does the drivertell the USB port to "up" the voltage? I was thinking that normal usb ports put out a little over 3 volts but the battery needs more or actually it does discharge? Further note, my co-worker has the same problem... completely different phone all stock. If this theory is correct then people can understand the importance of installing the correct drivers.
As a whole most phones require usb drivers to be able to usb charge. Usb mass storage should be no drivers needed however. I have it set in kernel on velocity to usb charge at 500mah.
Last edited by getitnowmarketing; February 8th, 2011 at 11:23 AM.
Just wanted to share my experiences, the overclock has yet to cause any CP's on me.
The mAndroid Connection
awsome job
