Related
dont know if this been posted but Anyone that took part in the Swype open beta back in April can now use the updated version of swype
http://www.androidcentral.com/swype-beta-receives-update
im sure someone going to leak it.
Just downloaded it. I love this keyboard!
Cool can't wait for someone to leak it. Can't wait until i can pay for it in the market actually but the a leak is enough too hold me over.
It really needs directional arrows. The EVO doesn't have a trackball for precise navigating through text fields, or the iPhones magnifying glass.
swype from the bottom left key one key to the right for arrows
Aridon said:
Cool can't wait for someone to leak it. Can't wait until i can pay for it in the market actually but the a leak is enough too hold me over.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=6743678&postcount=118
That link doesn't work I get an error on my phone saying can't parse file. I went into astro and deleted all the types I saw. I installed the program too. Any ideas or another working link?
gqstatus0685 said:
That link doesn't work I get an error on my phone saying can't parse file. I went into astro and deleted all the types I saw. I installed the program too. Any ideas or another working link?
Click to expand...
Click to collapse
try downloading it again, you may have gotten a bad copy
It's zipped.. download to pc, unzip and then push over to sd card.
Thanks that worked. Yes. I was dying without Swype.
BTW is there an app for typing via morse code. I used to have it on my iPhone. I know its off topic but I figured I'd ask real quick.
So my "trial" period is over. I've tried deleting and installing different apk's and it still says I need to upgrade. Does this mean I can't ever use swype again? Really liked it.
Same thing happened to me. I need this!
how do we go about buying it?
Can't post links but check out the thread in this section "SKN] - Droid Does Swype". Works for me. My old one expired today, but that one works.
the one u posted above, doesn't work for me, says trial has expired as well
worked for me when i installed it yesterday, and still working on my phone now. i use shapewriter but i just switched to swype after seeing this thread, and mine works.
Check it the N1 forums, the newest beta is posted there and works fine on my incredible.
http://forum.xda-developers.com/showthread.php?t=644536 here is the link... I just had to uninstall the old... reinstall the new then restart my phone... it forced closed the first time I opened it but works fine now that I did a reboot...
Worked great, thanks! Haven't even had to reboot yet.
So I've uninstalled the old swype, and put in the new version. I went to keyboard settings and changed it from android and back to swype, but for some reason when opening up my handcent sms or the stock message app it still uses the default keyboard. I've messed with the menu and can't find an input method option. Just wondering if there is something I'm forgetting to do to get it to work.
Thanks
did you do a long hold on your message
bjw1979 said:
So I've uninstalled the old swype, and put in the new version. I went to keyboard settings and changed it from android and back to swype, but for some reason when opening up my handcent sms or the stock message app it still uses the default keyboard. I've messed with the menu and can't find an input method option. Just wondering if there is something I'm forgetting to do to get it to work.
Thanks
Click to expand...
Click to collapse
having the same problem, even rebooted. uninstalled, installed new version. checked swype in keyboard settings .. but stock keyboard is coming up
bjw1979 said:
So I've uninstalled the old swype, and put in the new version. I went to keyboard settings and changed it from android and back to swype, but for some reason when opening up my handcent sms or the stock message app it still uses the default keyboard. I've messed with the menu and can't find an input method option. Just wondering if there is something I'm forgetting to do to get it to work.
Thanks
Click to expand...
Click to collapse
start to write a new text message, and where it says "compose" or something, do a long press. then input method > swype
it took me 5 annoyed minutes to find that on my phone, hope that helps
This is a problem we will continue to have with Swype. They have no intent to sell Swype on the market. Instead they are selling it to OEM's so it can be preloaded on new phones. After it stopped functioning when I switched to the Seidio 1750 battery (It said my hardware ID had changed and to contact Swype support), I switched to Shapewriter and never looked back. I actually like it better than Swype after using it for a bit.
Edit: SlideIt is another alternative to Swype.
Why would they have a beta sign up and then not put it on market, that makes no sense to me.
they will do whatever makes them money, if there are phones that cant get swype they will most likely offer an app pretty much like they are doing now. The expired trial was a previous beta. The new swype is out and works fine, and supposedly will have an official release tomorrow. There is already a thread with the link in the first post.
swype...
I can't get any of those links to work to get swype back if i don't my wife will kill me...loves swype and i need her to have it... LINK PLEASE
Mine expired today as well and then I got an invite to the beta about 20 minutes later...
GMK83 said:
Mine expired today as well and then I got an invite to the beta about 20 minutes later...
Click to expand...
Click to collapse
Hope I get that lucky.. I just registered today.
i just got accepted to be swype beta tester.
Are we not even allowed to say the S word anymore around here?
rayden25 said:
Are we not even allowed to say the S word anymore around here?
Click to expand...
Click to collapse
Actually you are I deleted it because after I deleted the app, it turned into a PM me *wink wink* deal. Discussion is fine, just no posting the actual app or a link to get the app
i wasn't invited, i was curious about how i could get swype on my phone too.
Crimton said:
i wasn't invited, i was curious about how i could get swype on my phone too.
Click to expand...
Click to collapse
I know, but per a letter from the developers to us, unless swype is native on a device, it should not be posted
i have the swype apk, i was just hoping there was a mod for the g-tablet that would allow swype to install. that wouldn't involve posting a link.
theimpaler747 said:
I deleted it because after I deleted the app, it turned into a PM me *wink wink* deal.
Click to expand...
Click to collapse
I wouldn't do that *wink wink*
rayden25 said:
I wouldn't do that *wink wink*
Click to expand...
Click to collapse
I'd hope not
I tried the official beta, as I'm a member, and a SGS version both on my G-Tablet and they install but wont open as the resolution is not supported. If there's a apk that does actually work. I'd love to just KNOW that. and I'll find it myself.
Thanks!
I tried using the swype from my epic but when I installed it and enable it it just FCs. I did use slideit but the keyboard took up most of the screen. Anybody else have any luck?
This is also something I am very interested in and have yet to get it to work.
I made the changes that rothnic suggested in the build.prop, loaded the lib, and dropped the ap in system/app and my tab doesn't see it at all. I've loaded a ' few' different versions on it that install but just fc. I've spent hours on it with no luck yet.
I'm not giving up hope for someone to release and update.zip but I'm not going to bother rothnic about it (anymore) as I'm sure he's working on roms and such. Even if he weren't, he's done more than his share here and I'm sure one of us will get it.
I'm still working it myself and if I make any progress I will surely let everyone know.
Just a reminder we can't post the .apk for swype here, as we don't want the thread pulled, again.
Sent from my GT-I9000 using XDA App
it2steve said:
This is also something I am very interested in and have yet to get it to work.
I made the changes that rothnic suggested in the build.prop, loaded the lib, and dropped the ap in system/app and my tab doesn't see it at all. I've loaded a ' few' different versions on it that install but just fc. I've spent hours on it with no luck yet.
I'm not giving up hope for someone to release and update.zip but I'm not going to bother rothnic about it (anymore) as I'm sure he's working on roms and such. Even if he weren't, he's done more than his share here and I'm sure one of us will get it.
I'm still working it myself and if I make any progress I will surely let everyone know.
Just a reminder we can't post the .apk for swype here, as we don't want the thread pulled, again.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
It sounds like you are doing something wrong when copying it over. It should come up under keyboards in settings. You would enable it there, then long press on an input box to switch to it.
I just did this a second time today and can confirm that it works.
rothnic said:
It sounds like you are doing something wrong when copying it over. It should come up under keyboards in settings. You would enable it there, then long press on an input box to switch to it.
I just did this a second time today and can confirm that it works.
Click to expand...
Click to collapse
yea, I was hoping that was the case but there can't be much that can go wrong. Download it or copy over via usb... then use root explorer to put it under system/app
For some reason I cant get ADB to work anymore? It had at one time. Do we know of any known issues with flashing that we loose the ability to ADB?
Oh well... I am a patient person and it's not like its a deal breaker for me. All is working pretty smoothly 3 weeks into the game.
Swype / ADB ... Progress / NO Progress
Ok, this is VERY interesting...
I still cant get swype to work. I FINALLY got to ADB push the .apk and the Lib and triple checked the build.prop (even used a couple different ones).
All I get is an FC over and over and when I got to settings-applications-manage, to clear cache, it's grayed out. I booted into recovery and cleared dalvik cache, wipe cache, and data. I have even gone as far as to re-flash the ZPAD 1.1, load gApps, Market Hack, Open GL Hack, and restart the whole swype process again with the same result.
HERE IS THE INTERESTING PART and we may want it posted elsewhere: I couldn't get my win7 to load the proper ADB driver (even though it had worked before). I found an app call ADBWireless (widget). It allows me to hit the widget and connect through ADB wirelessly (local wifi) and push/pull ect.
This was amazing and easy to use. Of course you have to have the Tab up so it wouldn't help for anyone who's in a loop.
When you hit the widget it shows the local ip address to connect to:
-I go to the command prompt \androidsdk\tools and type:
adb connect 192.xxx.xxx.xxx:5555
-it connects, and I am able to see the device
I have to use adb remount and then I'm good to go.
Hope this helps someone down the road. I'll keep checking back here but feel free to PM me if you have any questions (or find an update.zip for swype to work).
I made a little progress last night, got rid of the FCs but I can't get the keyboard enabled in the Settings. I managed to track down a Swype version from a Samsung Gaxlaxy Tab, at least that is what I think it is from, and then I had to find the necessary Lib file from somewhere else but when I push the .so to the Lib through ADB and install the Apk it seems like I'm closer, I can open the Swype settings screen and change things but I just can't get the keyboard enabled in the settings and then of course I can't pick the Swype keyboard when configuring the input method.
What changes were you making to the build.prop?
bmasephol said:
I made a little progress last night, got rid of the FCs but I can't get the keyboard enabled in the Settings. I managed to track down a Swype version from a Samsung Gaxlaxy Tab, at least that is what I think it is from, and then I had to find the necessary Lib file from somewhere else but when I push the .so to the Lib through ADB and install the Apk it seems like I'm closer, I can open the Swype settings screen and change things but I just can't get the keyboard enabled in the settings and then of course I can't pick the Swype keyboard when configuring the input method.
What changes were you making to the build.prop?
Click to expand...
Click to collapse
there was a 'header' so to speak that Rothnic posted that mad a few changes to the build.prop to make it look like portions of the Galaxy. He has it at the 'other' fourm.
Checked the permissions on the build.prop and they looked different. I couldn't just 'change' them in root explorer so I re-inserted the lines on the original build.prop, also did a fix permissions in CM (not that it helped).
Permissions in the lib file are hard to tell what they are supposed to be because several of the lib files there have different ones set. Swype.apk permissions look the same as the others. Still getting same FC's over and over. I was able to get into manage apps and hit force stop and clear (quickly tho) but goes back to the same after reboot.
Thanks for trying, as I said before, it's not a biggie. I just enjoy swype as being from palm and blackberry phone's if it weren't for swype I dunno that I would have kept an Android phone.
I can wait, I've spent too many hours jackin with it (although I did learn about the adb wireless and I am comfortable in pushing file that way now)
I managed to get it working although it is a little laggy. I followed rothnic's info in the other thread and after playing around with the build.prop file it is now working. Hopefully as the roms get faster this will get faster. Thanks for the help.
bmasephol said:
I managed to get it working although it is a little laggy. I followed rothnic's info in the other thread and after playing around with the build.prop file it is now working. Hopefully as the roms get faster this will get faster. Thanks for the help.
Click to expand...
Click to collapse
How did you do it? Can you be specific? Which version of Swype are you using? Where did you find it? What other thread?
Working on latest zpad rom. Had to set permissions - I think the important ones were r-x for User on both the lib and apk. And of course the build.prop edits.
-=Sent from my ViewSonic G Tablet using Tapatalk=-
I'm pretty sure the swype word is naughty here so I suggest you google for 'rothnic swype' and check the post on the other forum that comes up.
I used adb to push the modified build.prop to the sd card, along with the .so and .apk files. Then I used adb shell to copy the files to the locations rothnic specifies.
Does anyone have issues with it working? Sometimes it works, then other times it completely stops doing anything. It will popup and ill start swyping but it wont register anything.
psufan5 said:
Does anyone have issues with it working? Sometimes it works, then other times it completely stops doing anything. It will popup and ill start swyping but it wont register anything.
Click to expand...
Click to collapse
I've seen other people say that when they have issues with swype, just switch input (long press on a text field and change input to keyboard), then switch back and it should be OK
homeslice976 said:
I've seen other people say that when they have issues with swype, just switch input (long press on a text field and change input to keyboard), then switch back and it should be OK
Click to expand...
Click to collapse
Yeah thats just annoying though... Swiftkey did the same thing.
psufan5 said:
Yeah thats just annoying though... Swiftkey did the same thing.
Click to expand...
Click to collapse
Haha.. I understand. It is just a beta though isn't it? Give it time to grow
psufan5 said:
Does anyone have issues with it working? Sometimes it works, then other times it completely stops doing anything. It will popup and ill start swyping but it wont register anything.
Click to expand...
Click to collapse
I stopped using it for this reason. Having to switch text input was irritating me. I just use the stock keyboard, works fine.
I stopped using it because of this issue until I flashed CM7. Figured i would give it another try. It has not stopped working in the 3 days that I have been using CM7, so maybe it had something to do with AR?
Does it come on all the roms? Can't find swype on mine.
Sent from my Desire HD using XDA App
I have the same issues with Swype on AR 3, and now RCMix HD 4.1... But since there's an easy workaround, I'll keep using it as I like Swyping so much.
It works fine on my stock, un-rooted Inspire. I just simply downloaded the latest Swype apk file, and side loaded it through SWM. Simple, clean and easy. It works flawlessly, and has been for weeks now.
I just started having this problem today actually. I have been using it for a week and a half now. Don't know why it just happened today. I had to reset it twice earlier but fine now.
Sent from my Desire HD using XDA App
colbur87 said:
Does it come on all the roms? Can't find swype on mine.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
you have to sign up for the beta here where they send you a download link. At which point in your browser it may tell you that you are not using an android device. If you encounter this change your settings to show as a mobile and then you should be able to download and load it the way they show there
link as follows
http://beta.swype.com/
happy hunting
After reading the terms of service on XDA regarding swype, I removed this post. The post linked to another member who linked the apk file. In the future, anyone considering posting a swype apk file should read this...
http://www.xda-developers.com/android/official-stance-from-swype-inc-regarding-its-distribution/
Thanks to member phil.W for the heads up!
Cheers.
JDM9499 said:
Screw the beta version. Use the verified Swype. Maybe since it's a beta, that is why folks here are having problems. Just download the apk (non-beta version) and simply sideload the file with 'Sideload Wonder Machine'. Quick and easy.
You can get the real Swype version here in XDA. You could have done the search, or I'll just post the link here because I'm nice!
http://bit.ly/fhfgEa
There, on the last page, member cmeyer3 gives the download link.
Happy Swype(ing)!
Click to expand...
Click to collapse
How do you know this is the "Real" version and not just the apk someone got from the beta? Cause this (http://forum.androidcentral.com/htc-inspire-4g/60295-guide-installing-swype-beta-htc-inspire-4g.html - which is referenced in that thread) shows you how to pull the .apk out of the beta, which is what I believe is being shared
JDM9499 said:
Screw the beta version. Use the verified Swype. Maybe since it's a beta, that is why folks here are having problems. Just download the apk (non-beta version) and simply sideload the file with 'Sideload Wonder Machine'. Quick and easy.
You can get the real Swype version here in XDA. You could have done the search, or I'll just post the link here because I'm nice!
http://bit.ly/fhfgEa
There, on the last page, member cmeyer3 gives the download link.
Happy Swype(ing)!
Click to expand...
Click to collapse
How do you know this is the "Real" version and not just the apk someone got from the beta? Cause this (http://forum.androidcentral.com/htc-inspire-4g/60295-guide-installing-swype-beta-htc-inspire-4g.html) shows you how to pull the .apk out of the beta, which is what I believe is being shared. So although you don't need to sign up for the beta doing it this way, I *think* it's still the beta
not to mention of course that SWYPE does not want its apk being shared as such, and wants all copies to be properly licensed which even XDA is observing and removing links to the downloads when they see them to observe swypes request that they have proper copies and/or have permission to install it in their roms or on their own devices.
with link to corroborate the story from what I read yesterday
http://www.xda-developers.com/android/official-stance-from-swype-inc-regarding-its-distribution/
phil.W said:
not to mention of course that SWYPE does not want its apk being shared as such, and wants all copies to be properly licensed which even XDA is observing and removing links to the downloads when they see them to observe swypes request that they have proper copies and/or have permission to install it in their roms or on their own devices.
with link to corroborate the story from what I read yesterday
http://www.xda-developers.com/android/official-stance-from-swype-inc-regarding-its-distribution/
Click to expand...
Click to collapse
Someone should let cmeyer3 know
phil.W said:
not to mention of course that SWYPE does not want its apk being shared as such, and wants all copies to be properly licensed which even XDA is observing and removing links to the downloads when they see them to observe swypes request that they have proper copies and/or have permission to install it in their roms or on their own devices.
with link to corroborate the story from what I read yesterday
http://www.xda-developers.com/android/official-stance-from-swype-inc-regarding-its-distribution/
Click to expand...
Click to collapse
Thanks phil.W for the the heads up. I removed my post on that matter upon reading those terms of service from the link you provided. And yes, someone should let the other member, who is linking to the apk file, know about that as well. No reason to step on anyone's foot over at Swype and cause any problems for developers here on XDA.
Thanks again.
Ok, I love all of the new roms we've had our great developers dropping on us. But on most of the 3.5 roms sprints visual voicemail doesn't work, due to sprint not having an offical 3.5 rom we have to use other carriers ports.
Anyways I figured out a way to get vvm to work on any 3.5 rom, here you go;
1. Have a titanium backup of a working vvm (with a couple voicemails on it)
2. Restore it to whatever 3.5 sense rom you want.
3. Reboot into recovery wipe cache,dalvik then flash attached .zip file.
4. Once phone is rebooted, install the attached .apk.
Let me know if anyone has issues!, I've tested this on a few different 3.5 roms, works fine on all of them.
Note- I have had a couple of times after flashing different fixes that it breaks vvm, if you get force closes, just reinstall the .apk and it will work again.
*****DO NOT UPGRADE TO NEWER VVM, YOU WILL HAVE TO REDO EVERYTHING OVER AGAIN IF YOU DO!!*****
I don't quite understand the issue here. I'm running PrimeXL 3.5 ROM and my VVM works just fine. Unless you are referring to the text feature that comes along with it?
Is there something else to it?
thebbbrain said:
I don't quite understand the issue here. I'm running PrimeXL 3.5 ROM and my VVM works just fine. Unless you are referring to the text feature that comes along with it?
Is there something else to it?
Click to expand...
Click to collapse
Yeah, it's weird. I think some of the 3.5 roms are based on different baseboards, like I was having issues getting newtoroots/mik's 3.5 roms to playback directv's sunday ticket app, which I paid for so on sundays I'd flash back to mikg so I could use it.
But it seems like some 3.5 rom's have working vvm, and some dont. It will try to provision the app, but it ends up producing a "general failure".
This fixes that on the other 3.5 roms that it won't work on.
I dont use VVM but i know one of my friends that does. I'll pass the info along. Good work!!!
Sounds great man will take this into consideration man thanks.
It was my understanding that all you had to do was flash to a 3.0 ROM, let VVM provision, do a TB of VVM and data, flash the 3.5 ROM, and restore VVM using TB. So what are the 2 attachments for?
I'm not sure this really "fixes" anything, as once it flashes, VVM does a FC and I have to re-install. A simple backup-restore with TB works just fine, IMO.
DavidIQ said:
It was my understanding that all you had to do was flash to a 3.0 ROM, let VVM provision, do a TB of VVM and data, flash the 3.5 ROM, and restore VVM using TB. So what are the 2 attachments for?
Click to expand...
Click to collapse
gyrospazjohn said:
I'm not sure this really "fixes" anything, as once it flashes, VVM does a FC and I have to re-install. A simple backup-restore with TB works just fine, IMO.
Click to expand...
Click to collapse
David- That used to work on many of the 3.5 roms, but as things have changed and gotten upgraded in certain 3.5 roms, it somehow broke that way of restoring vvm services, but if it works for you or anyone else then absolutely stick with doing that, it just didn't work for me.
Gyro- I tried to just install the vvm.apk but for me on any rom I tried to do that on it wouldn't work unless I did it in the way I listed above, trust me I wouldn't of posted all of that stuff if it wasn't necessary.
ronartest2005 said:
David- That used to work on many of the 3.5 roms, but as things have changed and gotten upgraded in certain 3.5 roms, it somehow broke that way of restoring vvm services, but if it works for you or anyone else then absolutely stick with doing that, it just didn't work for me.
Gyro- I tried to just install the vvm.apk but for me on any rom I tried to do that on it wouldn't work unless I did it in the way I listed above, trust me I wouldn't of posted all of that stuff if it wasn't necessary.
Click to expand...
Click to collapse
It worked for me. I already had it working from a backup but I can't stand those 9016 notifications. I tried this hoping they would go away but the still come up after a vm.
Sent from my PC36100 using xda premium
Is anybody still getting 9016 notifications after trying this method?
Sent from my PC36100 using xda premium
ronartest2005 said:
David- That used to work on many of the 3.5 roms, but as things have changed and gotten upgraded in certain 3.5 roms, it somehow broke that way of restoring vvm services, but if it works for you or anyone else then absolutely stick with doing that, it just didn't work for me.
Click to expand...
Click to collapse
The other thing I heard was that the new VVM does not work with the 3.5 ROMs. Is this what the attachments address?
jcalderon576 said:
Is anybody still getting 9016 notifications after trying this method?
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Easy way to change that;
When you get one of those messages open it up and press menu, then click "block messages", then it will ask you for a password. Just enter any password that you want (make sure you remember it)
Then it should start blocking all of the 9016 messages.
DavidIQ said:
The other thing I heard was that the new VVM does not work with the 3.5 ROMs. Is this what the attachments address?
Click to expand...
Click to collapse
No, it does not work with the new vvm app. It will give you the "generic failure" message if you upgrade and it won't provision your vvm.
ronartest2005 said:
Easy way to change that;
When you get one of those messages open it up and press menu, then click "block messages", then it will ask you for a password. Just enter any password that you want (make sure you remember it)
Then it should start blocking all of the 9016 messages.
Click to expand...
Click to collapse
Hey that's great so I tried that and it worked. Just one thing u forgot to mention. Once ur in the blocked messages section hit menu and go to block list, add 9016 and it will start blocking them. Thanks man I appreciate it! I have no idea how I missed that lol
Sent from my PC36100 using xda premium
jcalderon576 said:
Is anybody still getting 9016 notifications after trying this method?
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Save the 9016 as a contact and go into your messages APP, Now set up your block password and add the 9016 to the list of Blocked contacts. Problem solved .
Hit thanks if I've helped
flojo73 said:
Save the 9016 as a contact and go into your messages APP, Now set up your block password and add the 9016 to the list of Blocked contacts. Problem solved .
Hit thanks if I've helped
Click to expand...
Click to collapse
Hey thanks man but I had already blocked them lol btw u don't really need to add it to ur contacts. It'll block them just by puting it on the blocked list. Thanks anyway!!! I still hit that thanks button
Sent from my PC36100 using xda premium
I tried this fix on Radiance RC-2. Radiance came with VVM but wans't sure if it was working and what not. I restored from TB my VVM (the one updated by sprint) and then got a voice mail today, didn't work. So I ran the fix (had it sitting on SDCard) and it reverted it back to old voice mail, then asked me to update, so I went ahead and updated and sent myself a voice mail. No go.
As I can see in this thread that there is an issue with the new VVM and it not working on 3.5 anyhow. So how would I go about fixing this? Should I restore my VVM from TB (even though it's the New one) and then run the fix again and let it revert it back to the old VVM?
Thanks for the help and also the fix.
mackattack23 said:
I tried this fix on Radiance RC-2. Radiance came with VVM but wans't sure if it was working and what not. I restored from TB my VVM (the one updated by sprint) and then got a voice mail today, didn't work. So I ran the fix (had it sitting on SDCard) and it reverted it back to old voice mail, then asked me to update, so I went ahead and updated and sent myself a voice mail. No go.
As I can see in this thread that there is an issue with the new VVM and it not working on 3.5 anyhow. So how would I go about fixing this? Should I restore my VVM from TB (even though it's the New one) and then run the fix again and let it revert it back to the old VVM?
Thanks for the help and also the fix.
Click to expand...
Click to collapse
Yeah, do not upgrade to the newer vvm. And you should do what you said to restore vvm service, restore your titanium backup, flash zip and install apk, do not install update.
I will update OP so this doesn't happen to others in the future.
That worked Ron. Thanks for the help. Silly VVM
Worked perfectly, thanks!!!