Related
So, I have read that it's an issue with all Froyo ROM's on the EVO... You can't see paid/protected apps in the Marketplace; supposedly, the apps not showing are not verified to work on Froyo.
Could someone just patch the build_prop like they did on the Nexus One before Google released the official fix?
N1 Fix Thread for Reference: http://forum.xda-developers.com/showthread.php?t=693102
If anyone wants to tackle it, the dev of the N1 fix explained what needs to be done here: http://forum.xda-developers.com/showthread.php?t=693102
I don't have an EVO, nor am I much of a developer; but I just rooted my friend's EVO and was looking for a fix for him when I realized that the N1 had a very similar issue when it was running leaked versions of Froyo.
Just throwing it out there... I could be way off.
I think this should be easy to do. Theoretically you should be able to take buildprop swticher v0.3.1.zip and replace /buildprop/build.2.1 with the build.prop from stock and /buildprop/build.2.2 with the build.prop from CM6 and then follow the directions from that post.
I'm about to test it out myself and see if it works...
Let me know... If it does, could you post the build.prop files that you used?
EDIT: Awesome to see another SC member!
Okay, first attempt boot looped. I think build.2.1 needs to be a 2.2 build.prop modified to look like 2.1 because the stock 2.1 build.prop won't work with 2.2. Should've looked at that more instead of rushing Going to see if I can find the lines to change real quick, gotta go back to work in a few minutes...
It also cleared my Google Account settings haha... trying a new modification but may not be able to upload anything until tonight!
Thanks for your help... Can you post your build.props before going back to work? If so, I will try to work on this more if you aren't able to get it before going back.
Thanks
Just printed and compared the build.props for the N1 fix and see that there are only 2 lines that were changed. If someone wants to provide me with a 2.1 build.prop and the CM6 build.prop, I might be able to get this working.
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
I was just about to post saying what I tried didn't work and I was hoping you'd pop in here. I was thinking about digging into it more this weekend but if you haven't been able to get anywhere I doubt I could either.
Well... that blows... Sorry guys
Wish I could've been of more help!
Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data
Geniusdog... what all does the ro.build.fingerprint line do?
spiicytuna said:
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data
Click to expand...
Click to collapse
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
We need a setting like most of the android browsers to allow us to spoof ourselves as stock 2.1 EVO.
Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet
ok this is what we did on the Hero when we was with 1.5 and got the leak of 2.1 the market didnt show all the apps so we just change it with the nexus one, so i am guessing maybe we can get a 2.2nexus one build.prop and push it to the Evo, make sure to clear the market chache though , it took like 5-6hours for the apps to start showing up on the Hero!! just an Idea
jabbawalkee said:
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet
Click to expand...
Click to collapse
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.
datajosh said:
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.
Click to expand...
Click to collapse
bootlooops
Edit: nvm, was incomplete.
Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
It takes some changes to get the phone to boot with them, or to get radio access with them.
I've already tried a stock Nexus fingerprint, but it still doesn't give access. Like I said, I even pushed the file before even booting the phone (I.E, wipe, flash CM6, push file in recovery, then reboot) and it still didn't work.
Ava's build prop comes up, but no Market. Something else is going on.
Geniusdog254 said:
Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
Click to expand...
Click to collapse
Duh, forgot it was Sense for a minute there. I feel like looking into it more but I'm not sure if anyone's going to find a solution.
I am currently running CM6 RC1 with LauncherPro Plus. Everything works fantastically well. I have applied the market fix and I love AOSP Android.
Pursuant to instructions in the CM6 nightly build thread, I installed sprintvm.apk and sprintupdater.apk. The latter force closes after the phone boots up.
Please advise if Sprint Voicemail will work properly without sprintupdater.apk installed.
Thanks in advance.
It FC's for everyone on boot. That's well known. And why not try it first? Really? Just take a Nandroid backup, then remove the updater, and see what happens.
drmacinyasha said:
It FC's for everyone on boot. That's well known. And why not try it first? Really? Just take a Nandroid backup, then remove the updater, and see what happens.
Click to expand...
Click to collapse
I did try. I was getting mixed results and was looking for some additional insight on the matter.
Also, it's the Q&A section. I can ask if I please. No need to be rude.
Install Sprint Updater. Install Sprint VVM. Once things are squared away and the VVM is working properly, uninstall Sprint Updater.
Problem solved!
trobb09 said:
Install Sprint Updater. Install Sprint VVM. Once things are squared away and the VVM is working properly, uninstall Sprint Updater.
Problem solved!
Click to expand...
Click to collapse
Problem solved, indeed. Thanks!
It says Package file was not signed correctly when I try to install it. Could this have something to do with the ROM I'm using?
I'm running skyraider 2.2 and it installed perfectly for me; straight from the market. The alarm clock function doesn't work but I think that's an issue with sense rather than the rom.
Sent from my ADR6300
hazard666 said:
I'm running skyraider 2.2 and it installed perfectly for me; straight from the market. The alarm clock function doesn't work but I think that's an issue with sense rather than the rom.
Sent from my ADR6300
Click to expand...
Click to collapse
Which Skyraider? I'm using the aiccucus rom which is a non sense rom so maybe that's the problem?
I'm on CM 6 nightly, didn't install for me either.
Yeah, I am using the sense rom but if anything I'd figured that it'd play nicer with vanilla.
E: here's my apk if it helps any.
http://www.mediafire.com/?vrqxf1youubvlah
i installed the voicesearch.apk from the link above however i dont notice anything different happen when i execute a voice search
blakestiffler said:
i installed the voicesearch.apk from the link above however i dont notice anything different happen when i execute a voice search
Click to expand...
Click to collapse
there are a bunch of new features that you can do with voice search.
blakestiffler said:
i installed the voicesearch.apk from the link above however i dont notice anything different happen when i execute a voice search
Click to expand...
Click to collapse
Do you mean that the update didn't go through or it doesn't look any different? Like the337 said, there's a bunch of new features.
If the video upon first start works, watch that. Neat stuff.
hazard666 said:
Yeah, I am using the sense rom but if anything I'd figured that it'd play nicer with vanilla.
E: here's my apk if it helps any.
http://www.mediafire.com/?vrqxf1youubvlah
Click to expand...
Click to collapse
Wouldn't install for me when I downloaded it.
Bobb_o said:
Wouldn't install for me when I downloaded it.
Click to expand...
Click to collapse
Sorry guys, I just deleted the VoiceSearch.apk from my phone and voice search still works which means this file isn't the one you're looking for.
From Twitter:
cyanogen: Yes I know the new Voice Search won't install on CM because of different signatures. Should be fixable.
Sent from my Incredible using Tapatalk
Is anyone else using the new voice search getting a Force Close every time you try any of the new functions which depend on (afaik) gmail -- such as "note to self" "send email to..." and so on? Other functions work fine such as "call such and such" or "listen to whatever", but anything message-like causes a FC when I press 'send' from the text-confirmation window.
I am running on the 8/1 leak, and have tried various things all to no avail including clearing application data, uninstalling old versions first (by different methods), not uninstalling old versions first, and all with nandroid restores in-between. Any more ideas?
EDIT: OK, some progress. It seems that there is an issue with the Gmail.apk that I was using (version 2.2.1). If I removed or renamed it, then the messaging functions of the new voice search would not force close, but would instead look for another mail handler (such as htc). I then tried pushing via adb the Gmail.apk that was originally in the 8/1 leak (version 2.2) and to my surprise everything works now. I will mess around a bit more to see if I can get a 2.2.1 working again without it causing a FC, but it seems that is where my issue was.
Voice search installed fine on jager rom v3.2 no force closes yet. I've tried to use the note to self voice action, but after I say the command it asks to send an email with an empty subject and body message.
hey everyone, if you're having trouble getting the voice search to work. Vlingo just made their android app free on the market so i downloaded it and it works fairly well. it was previously 10 dollars. i know it's not the new google voice search but i'm going to try and use that until this gets working or we get an official OTA 2.2.
my incredible is unable to find it on the market so i used my girlfriends droid. I had to first delete voicesearch.apk to get it to install. I got it installed and working. So now i want to make a copy to send to my incredible but the problem is i dont see it anywhere on my phone. Not under /system/app or /data/app. Not a single app is showing as even being written on the current date, yet the voice search works.
UPDATE:
I didn't see a com.google.android.voicesearch or com.google.android.googlequicksearchbox, so I just removed the 2 apk's, and voice search installed just fine.
Saw a force quit during note to self.
I found this article on CM forums, but do these instructions apply to the Incredible running CM?
I'm running CM test 8, but the pm uninstall commands don't seem to want to work - I'm getting this error:
pm: exec: line 7: app_process: not found
Does anyone know how we can uninstall VoiceSearch.apk as well as the widget?
http://forum.cyanogenmod.com/topic/4231-installing-updated-voice-search/
adb pull /system/app/ ~/Desktop/app/
adb remount
adb shell rm -f /system/app/VoiceSearch.apk
adb shell pm uninstall com.google.android.voicesearch
adb shell rm -f /system/app/GoogleQuickSearchBox.apk
adb shell pm uninstall com.google.android.googlequicksearchbox
askwhy said:
Is anyone else using the new voice search getting a Force Close every time you try any of the new functions which depend on (afaik) gmail -- such as "note to self" "send email to..." and so on? Other functions work fine such as "call such and such" or "listen to whatever", but anything message-like causes a FC when I press 'send' from the text-confirmation window.
I am running on the 8/1 leak, and have tried various things all to no avail including clearing application data, uninstalling old versions first (by different methods), not uninstalling old versions first, and all with nandroid restores in-between. Any more ideas?
EDIT: OK, some progress. It seems that there is an issue with the Gmail.apk that I was using (version 2.2.1). If I removed or renamed it, then the messaging functions of the new voice search would not force close, but would instead look for another mail handler (such as htc). I then tried pushing via adb the Gmail.apk that was originally in the 8/1 leak (version 2.2) and to my surprise everything works now. I will mess around a bit more to see if I can get a 2.2.1 working again without it causing a FC, but it seems that is where my issue was.
Click to expand...
Click to collapse
I just tried using the "note to self" and it did FC on me when I hit send. So you aren't the only one. I'm using Skyraider Vanilla 2.5 for reference.
J913B said:
I just tried using the "note to self" and it did FC on me when I hit send. So you aren't the only one. I'm using Skyraider Vanilla 2.5 for reference.
Click to expand...
Click to collapse
Running the 8/1 leak, 2.2.1 GMail. "note to self" with the updated voice search works fine for me.
I have it running in a CM6 Nightly. I removed it with titanium backup. Rebooted and it installed. I may of wiped cache too.
I was able to install it using Skyraider Vanilla with no problems.
Now the Chrome to phone app wouldn't install, I think it was because I already had that app installed which it was an older version of that app.
Went to Market this Morning Bright and Early Like I usually do before Work. And it Gave Me Error....Sorry forgot Exactly what is said, but at end gave me a code....*#9900#
What is that? And Why Would it Be doing that?
Info to maybe help....EG22 with EH17 modem
rootxda said:
Went to Market this Morning Bright and Early Like I usually do before Work. And it Gave Me Error....Sorry forgot Exactly what is said, but at end gave me a code....*#9900#
What is that? And Why Would it Be doing that?
Info to maybe help....EG22 with EH17 modem
Click to expand...
Click to collapse
this is happening on mine and wife's phone too we are both running bonsia b14
Seems to be happening on a few GB leaks. The only way I found to fix it is to delete the market and market updater, flash in an old market 2.3.6 and freeze Market Updater. I will be experimenting with 3.0.2.7 tomorrow but in the meantime here is 2.3.6 for you to try:
kennyglass123 said:
Seems to be happening on a few GB leaks. The only way I found to fix it is to delete the market and market updater, flash in an old market 2.3.6 and freeze Market Updater. I will be experimenting with 3.0.2.7 tomorrow but in the meantime here is 2.3.6 for you to try:
Click to expand...
Click to collapse
i have a version that works but can't seem to freeze it before it breaks again
tazfanatic said:
i have a version that works but can't seem to freeze it before it breaks again
Click to expand...
Click to collapse
Yeah, I believe that any 3.x version will still update automatically no matter what you freeze. I will see if I can find 3.026 somewhere today and try that. But you have to clear data in Titanium and Force Stop in settings, then remove it completely from your system, flash the file above and immediately freeze market updater and market feedback upon boot. The older version of the market is much faster anyway.
kennyglass123 said:
Yeah, I believe that any 3.x version will still update automatically no matter what you freeze. I will see if I can find 3.026 somewhere today and try that. But you have to clear data in Titanium and Force Stop in settings, then remove it completely from your system, flash the file above and immediately freeze market updater and market feedback upon boot. The older version of the market is much faster anyway.
Click to expand...
Click to collapse
Oh ok thanks I d/l yours. Will follow this when I get home tonight. This started last Wednesday or Thursday for me sucked I was a way on vacation rebuilding my phone on my anniversary at dinner LOL. No matter what I did I thought there was a issue with permissions or something tried everything except flashing back to stock. Is it only on certain versions of the leak? I can go back to ec05 but really don't want to.
Yes it is only on certain leaks and I am guessing it is caused by the same thing that causes the new Google Voice to FC. Anyone running Market 3.1.5 on a Gingerbread leak let me know which ROM so I can see if we are missing a file removed as bloat.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Yes it is only on certain leaks and I am guessing it is caused by the same thing that causes the new Google Voice to FC. Anyone running Market 3.1.5 on a Gingerbread leak let me know which ROM so I can see if we are missing a file removed as bloat.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
bonsia b14
tazfanatic said:
bonsia b14
Click to expand...
Click to collapse
That does not run either the new Market or Google Voice updates. Is there a GB leak ROM that does not FC with either of these updates? I guess I can compare files in the stock deodexed EH17.
I flashed Cyanogenmod 7.1.0 on an Evo 4G on Sprint service and now I get text messages that say I need to call 408.970.0000 to get my VM. When I called it I got a recording about having a smart phone with SMS or something or another and I wasn't sure what it asked me but I pressed option '2' and it said something to the effect that it would continue sending me SMS voice mails but that's not what I want. I don't like getting the cryptic text messages and would much rather have the previous VM solution I had. I think it's called visual voice mail or something to that effect.
If I want that back and to do away with the SMS notifications what are my steps?
Can anyone help me out or link me to a how to and how to resolve my voice mail issue?
I found something about a Spring VM apk so do I just need to install this app and if so where can I find the latest one compatible with CM7?
Thanks for the help.
OstrichSak said:
I flashed Cyanogenmod 7.1.0 on an Evo 4G on Sprint service and now I get text messages that say I need to call 408.970.0000 to get my VM. When I called it I got a recording about having a smart phone with SMS or something or another and I wasn't sure what it asked me but I pressed option '2' and it said something to the effect that it would continue sending me SMS voice mails but that's not what I want. I don't like getting the cryptic text messages and would much rather have the previous VM solution I had. I think it's called visual voice mail or something to that effect.
If I want that back and to do away with the SMS notifications what are my steps?
Can anyone help me out or link me to a how to and how to resolve my voice mail issue?
I found something about a Spring VM apk so do I just need to install this app and if so where can I find the latest one compatible with CM7?
Thanks for the help.
Click to expand...
Click to collapse
Should be able to get everything you need here, I followed the steps when i first started and it worked great for me. Hopefully it works for you.
http://forum.xda-developers.com/forumdisplay.php?f=652
lithid-cm said:
Should be able to get everything you need here, I followed the steps when i first started and it worked great for me. Hopefully it works for you.
http://forum.xda-developers.com/forumdisplay.php?f=652
Click to expand...
Click to collapse
Which topic specifically?
Since posting this thread I kept searching and I've found some threads talking about a Spring VVM apk and I've downloaded what I think is the right file that I may try. Now I'm just trying to make sure this is my solution.
Try the themes and apps subforum. Your answer is there.
Sent from my PC36100 using xda premium
We are in the middle of this same discussion on another thread so im guna hook ya up. First, download the two apps i linked below. Then using root explorer or a file manager that has root privileges mount system as r/w and delete the stock CM7 MMS app in system/app folder. Than move the MMS app i linked to system/app. Long click the MMS app and make sure permissions are set exactly like the other system apps, click ok. Now do the same with the VVM app below, move it to system apps and set permissions as well. Mount the system as r/o again and reboot your phone. Go into the VVM app and set up VVM and thats it. You will now have visual voice mail again and no annoying 9016 texts. BTW, the MMS app i posted is from Decks AOSP 1.3d rom(that has the fix for the 9016 texts) and the VVM app is from the 8/22 GAPPS, Enjoy.......
luist4498 said:
We are in the middle of this same discussion on another thread so im guna hook ya up. First, download the two apps i linked below. Then using root explorer or a file manager that has root privileges mount system as r/w and delete the stock CM7 MMS app in system/app folder. Than move the MMS app i linked to system/app. Long click the MMS app and make sure permissions are set exactly like the other system apps, click ok. Now do the same with the VVM app below, move it to system apps and set permissions as well. Mount the system as r/o again and reboot your phone. Go into the VVM app and set up VVM and thats it. You will now have visual voice mail again and no annoying 9016 texts. Enjoy.......
Click to expand...
Click to collapse
Thanks, I'll try it out soon as I get a chance. I installed an apk based on something I found and it kind of worked but I was getting those annoying 9016 texts like you mentioned. I'll give this a go when I get some more time.
OstrichSak said:
Thanks, I'll try it out soon as I get a chance. I installed an apk based on something I found and it kind of worked but I was getting those annoying 9016 texts like you mentioned. I'll give this a go when I get some more time.
Click to expand...
Click to collapse
Cool man, if all the steps are done right there will be no annoying 9016 texts.
luist4498 said:
We are in the middle of this same discussion on another thread so im guna hook ya up. First, download the two apps i linked below. Then using root explorer or a file manager that has root privileges mount system as r/w and delete the stock CM7 MMS app in system/app folder. Than move the MMS app i linked to system/app. Long click the MMS app and make sure permissions are set exactly like the other system apps, click ok. Now do the same with the VVM app below, move it to system apps and set permissions as well. Mount the system as r/o again and reboot your phone. Go into the VVM app and set up VVM and thats it. You will now have visual voice mail again and no annoying 9016 texts. Enjoy.......
Click to expand...
Click to collapse
is this strictly for cyn 7?
im using OMFGB and im having problems with voicemails after i flashed the rom, it keeps saying unable to play message
Toney Starks said:
is this strictly for cyn 7?
im using OMFGB and im having problems with voicemails after i flashed the rom, it keeps saying unable to play message
Click to expand...
Click to collapse
I have not tried that rom but the issue we are trying to fix is the annoying texts you get with every vm from 9016. I know this works with the salvaged rom too. The vm come through on your vm app though? Also, some have had success with the following if the VVM app is not verifying there account automatically. Press menu in VVM and compose a message over 25 seconds long. Send the message to [email protected] and make sure you have either wifi or 3g enabled so it will send. This should kick start it.
Use super private conversation app to block 9016 txt. Spc is a free app.
Rafael Garces
Apple and PC Certified Technician
luist4498 said:
We are in the middle of this same discussion on another thread so im guna hook ya up. First, download the two apps i linked below. Then using root explorer or a file manager that has root privileges mount system as r/w and delete the stock CM7 MMS app in system/app folder. Than move the MMS app i linked to system/app. Long click the MMS app and make sure permissions are set exactly like the other system apps, click ok. Now do the same with the VVM app below, move it to system apps and set permissions as well. Mount the system as r/o again and reboot your phone. Go into the VVM app and set up VVM and thats it. You will now have visual voice mail again and no annoying 9016 texts. BTW, the MMS app i posted is from Decks AOSP 1.3d rom(that has the fix for the 9016 texts) and the VVM app is from the 8/22 GAPPS, Enjoy.......
Click to expand...
Click to collapse
The part in bold above; is it just called MMS.apk or should I be looking for a file called CM7 MMS? Just want to make sure I delete the right one before I get started here. Also, is this process going to be changed any because I installed the VVM apk before you posted this or will following your steps still yield the same results?
OstrichSak said:
The part in bold above; is it just called MMS.apk or should I be looking for a file called CM7 MMS? Just want to make sure I delete the right one before I get started here. Also, is this process going to be changed any because I installed the VVM apk before you posted this or will following your steps still yield the same results?
Click to expand...
Click to collapse
Yes the app you are looking for is in system/app and is called Mms.apk. The icon looks just like the messaging app in your app drawer. If you already have VVM set up and working than just delete stock Mms app and replace with new Mms app and reboot, thats all.
luist4498 said:
We are in the middle of this same discussion on another thread so im guna hook ya up. First, download the two apps i linked below. Then using root explorer or a file manager that has root privileges mount system as r/w and delete the stock CM7 MMS app in system/app folder. Than move the MMS app i linked to system/app. Long click the MMS app and make sure permissions are set exactly like the other system apps, click ok. Now do the same with the VVM app below, move it to system apps and set permissions as well. Mount the system as r/o again and reboot your phone. Go into the VVM app and set up VVM and thats it. You will now have visual voice mail again and no annoying 9016 texts. BTW, the MMS app i posted is from Decks AOSP 1.3d rom(that has the fix for the 9016 texts) and the VVM app is from the 8/22 GAPPS, Enjoy.......
Click to expand...
Click to collapse
Flawless Victory!
I just wanted to quote this post again for anyone who may be searching for a solution to the same problem. Since I had already installed the VVM I simply deleted the MMS apk and replaced as instructed and it worked perfectly. Thanks again for taking the time to post up the fix and link the files needed.
For the record, I searched and while I found ZERO answers to my problem there were sure a lot of people suggesting to search as the answer was as easy as falling off a log and that wasn't the case. I get SO frustrated when people offer zero help and instead ridicule any and every post looking for help to somehow make themselves feel better. No, the answer isn't always that simple and no you're not helping anyone. If you don't have the answer, a link to the answer or at least first hand knowledge that the answer for sure exists someplace recent then do everyone a favor and move along w/o posting. This forum is made better from people like luist4498 who actually contribute and not people like you who appear only to be around to pad their post count.
OstrichSak said:
Flawless Victory!
I just wanted to quote this post again for anyone who may be searching for a solution to the same problem. Since I had already installed the VVM I simply deleted the MMS apk and replaced as instructed and it worked perfectly. Thanks again for taking the time to post up the fix and link the files needed.
For the record, I searched and while I found ZERO answers to my problem there were sure a lot of people suggesting to search as the answer was as easy as falling off a log and that wasn't the case. I get SO frustrated when people offer zero help and instead ridicule any and every post looking for help to somehow make themselves feel better. No, the answer isn't always that simple and no you're not helping anyone. If you don't have the answer, a link to the answer or at least first hand knowledge that the answer for sure exists someplace recent then do everyone a favor and move along w/o posting. This forum is made better from people like luist4498 who actually contribute and not people like you who appear only to be around to pad their post count.
Click to expand...
Click to collapse
No problem man! I dont understand why certain people are so nasty about another asking for help when it took me only a couple minutes to upload and post the files and fix. Go figure, btw, if u flash CM nightlies or re-flash CM for any reason u will have to do this fix again since they install the stock MMS again when u flash nightlies or re-flash rom.
luist4498 said:
No problem man! I dont understand why certain people are so nasty about another asking for help when it took me only a couple minutes to upload and post the files and fix. Go figure, btw, if u flash CM nightlies or re-flash CM for any reason u will have to do this fix again since they install the stock MMS again when u flash nightlies or re-flash rom.
Click to expand...
Click to collapse
Thanks for the heads up but I'm not one to flash ROMs on a regular basis. I was running MikG v2.3 for months before a got caught in a boot loop which forced me to reflash a new ROM. At this time I looked at what was available and decided I liked CM7 the best and flashed that. Unless something else catastrophically fails or I find a feature I can't live w/o I will likely rock this ROM for some time to come. If I do change it though I will be sure to do the fix and refer back to this thread for a refresher. Thanks!
OstrichSak said:
Thanks for the heads up but I'm not one to flash ROMs on a regular basis. I was running MikG v2.3 for months before a got caught in a boot loop which forced me to reflash a new ROM. At this time I looked at what was available and decided I liked CM7 the best and flashed that. Unless something else catastrophically fails or I find a feature I can't live w/o I will likely rock this ROM for some time to come. If I do change it though I will be sure to do the fix and refer back to this thread for a refresher. Thanks!
Click to expand...
Click to collapse
Me too man,,,,,im lovin this CM7.
luist4498 said:
Me too man,,,,,im lovin this CM7.
Click to expand...
Click to collapse
I thought I was going to miss Sense more than I do.
Good post, alerted of this thread & more need to be alerted of this thread & external links in here. Thanks
---------- Post added at 12:09 AM ---------- Previous post was at 12:06 AM ----------
luist4498 said:
We are in the middle of this same discussion on another thread so im guna hook ya up. First, download the two apps i linked below. Then using root explorer or a file manager that has root privileges mount system as r/w and delete the stock CM7 MMS app in system/app folder. Than move the MMS app i linked to system/app. Long click the MMS app and make sure permissions are set exactly like the other system apps, click ok. Now do the same with the VVM app below, move it to system apps and set permissions as well. Mount the system as r/o again and reboot your phone. Go into the VVM app and set up VVM and thats it. You will now have visual voice mail again and no annoying 9016 texts. BTW, the MMS app i posted is from Decks AOSP 1.3d rom(that has the fix for the 9016 texts) and the VVM app is from the 8/22 GAPPS, Enjoy.......
Click to expand...
Click to collapse
Thanks for not being a prick. Dude comes for help & maybe he didn't post in the right section. Some people act like they always knew it all.
luist4498 said:
We are in the middle of this same discussion on another thread so im guna hook ya up. First, download the two apps i linked below. Then using root explorer or a file manager that has root privileges mount system as r/w and delete the stock CM7 MMS app in system/app folder. Than move the MMS app i linked to system/app. Long click the MMS app and make sure permissions are set exactly like the other system apps, click ok. Now do the same with the VVM app below, move it to system apps and set permissions as well. Mount the system as r/o again and reboot your phone. Go into the VVM app and set up VVM and thats it. You will now have visual voice mail again and no annoying 9016 texts. BTW, the MMS app i posted is from Decks AOSP 1.3d rom(that has the fix for the 9016 texts) and the VVM app is from the 8/22 GAPPS, Enjoy.......
Click to expand...
Click to collapse
I tried this for the virtual voice mail and it works perfectly. But...now when I hit settings while on the sms screen I get the following message: "Sorry! The application Messaging (processing com.android.mms) has stopped working unexpectedly. Please try again." Any ideas or advice?
Thanks
luist4498 said:
We are in the middle of this same discussion on another thread so im guna hook ya up. First, download the two apps i linked below. Then using root explorer or a file manager that has root privileges mount system as r/w and delete the stock CM7 MMS app in system/app folder. Than move the MMS app i linked to system/app. Long click the MMS app and make sure permissions are set exactly like the other system apps, click ok. Now do the same with the VVM app below, move it to system apps and set permissions as well. Mount the system as r/o again and reboot your phone. Go into the VVM app and set up VVM and thats it. You will now have visual voice mail again and no annoying 9016 texts. BTW, the MMS app i posted is from Decks AOSP 1.3d rom(that has the fix for the 9016 texts) and the VVM app is from the 8/22 GAPPS, Enjoy.......
Click to expand...
Click to collapse
Worked great on my evo 4g and CM7.1
Thanks