Related
For some reason the voice recorder app was corrupt, so I and looking for the stock 2.2 apk to use. Thanks
Is this it?
I hope this is the one?!
this should be it
shoman24v said:
Is this it?
Click to expand...
Click to collapse
This is the same one that I had on the phone, but even after re installing it it gives me problems. The app icon is the generic one and when I click it, a different looking program comes up. Is there another program that I need to run? The htc one didn't download an my voice search is working fine.
I just want an an app that I can record with, for done reason switching from inc does mash up rom back to a nandroid with full wipes completely messed with my phone. I had to reinstall m radio because the internet wasn't working, also the stock email kept force closing no matter what I did, so un installing it and putting on a fresh copy seemed to work. Just weird all of this happened
Any info on this?
i don't have the stock one but the htc one above.
i am positive VoiceSearch.apk is NOT it. that is probably googles voice search app.
patchnauty said:
this should be it
Click to expand...
Click to collapse
Which of them can record what the radio with?
I have issues with Kik Messenger's messages not being pushed properly to my phone when on a custom rom.
What I have tried so far:
Axura 2.1 w/JK3 modem
Axura 2.2 w/JK4 modem
Axura 2.2 w/JL3 modem
Cognition v2.3b7 (defaults)
Perception Build 8 (defaults)
Symptoms (the are the same for all of the above):
After first installing the rom and the kik messenger program it appears to work as advertised. After about 5 minutes of use is when the problems start and never fix themselves. Kik Messenger will *only* receive messages when I am typing to someone. If I switch to another application it will *not* receive any new messages until I open the program and start typing to someone. I checked the running services and Kik Push Service is still running in the background. I have not used any task killers either. I have received messages up to a full 24hrs late because of this
Strangely, this issue doesn't exist on the stock rom from Samsung. If anyone has any clue of what I could change, it would be greatly appreciated. I know custom roms have a hosts file that blocks ads etc., I wonder if this could have something to do with it (although I doubt it).
TIA
devz3r0 said:
I have issues with Kik Messenger's messages not being pushed properly to my phone when on a custom rom.
What I have tried so far:
Axura 2.1 w/JK3 modem
Axura 2.2 w/JK4 modem
Axura 2.2 w/JL3 modem
Cognition v2.3b7 (defaults)
Perception Build 8 (defaults)
Symptoms (the are the same for all of the above):
After first installing the rom and the kik messenger program it appears to work as advertised. After about 5 minutes of use is when the problems start and never fix themselves. Kik Messenger will *only* receive messages when I am typing to someone. If I switch to another application it will *not* receive any new messages until I open the program and start typing to someone. I checked the running services and Kik Push Service is still running in the background. I have not used any task killers either. I have received messages up to a full 24hrs late because of this
Strangely, this issue doesn't exist on the stock rom from Samsung. If anyone has any clue of what I could change, it would be greatly appreciated. I know custom roms have a hosts file that blocks ads etc., I wonder if this could have something to do with it (although I doubt it).
TIA
Click to expand...
Click to collapse
Answer bolded above.
I'd love a solution to, other then "go back to stock rom"
Try the developer?
Sent from a phone somewhere in the universe
I deleted the hosts files, does the same thing....
Gentlemen, gentlemen, gentlemen. The answer is quite obvious. It's your Android ID. None of the ROMs that you have been using have a unique Android ID, they are all the same. You need to obtain your original, uniquie Android ID for your phone. You can do this by flashing back to stock JF6 or JH7, copying your settings.db file to your computer, opening it with whatever SQLite editor you fancy, and then updating the settings.db on your custom ROM with your unique ID. And problem solved.
Here is the Get Satisfaction page from KIK where they discuss the issue.
http://getsatisfaction.com/kik/topi...atically_received_when_phone_is_idle_too_long
Oh wow....
Thanks
Does that affect any other app ?
Ok it worked... I used http://www.appbrain.com/search?q=android+id+changer to put the new Android_ID, less of a pain in the ass to do.
If you have an ClockworkMod Backup you can use these the 2 files in the zip attaches, extract them to the folder where you have your img and just type unyaffs datadata.img to exctract the content of the img files and get your android ID. (the settings.db you need is in the datadata.img file, in \databases\com.android.providers.settings\ folder) use SQLite Editor : http://goo.gl/cPv8z to check the Android_ID open the .exe, load the extracted settings.db and go to browse data, choose secure in the drop down and down there you should have your android_id.
Thanks miztaken1312 for the hint.
CasseTrop said:
Oh wow....
Thanks
Does that affect any other app ?
Click to expand...
Click to collapse
Affects all Storm 8 games, (World War and whatever else there is), KIK, other messaging apps, Appbrain, and I'm sure there are more.
CasseTrop said:
Ok it worked... I used http://www.appbrain.com/search?q=android+id+changer to put the new Android_ID, less of a pain in the ass to do.
If you have an ClockworkMod Backup you can use these the 2 files in the zip attaches, extract them to the folder where you have your img and just type unyaffs datadata.img to exctrat the content of the img files and get your android ID. (the settings.db you need is in the datadata.img file, in \databases\com.android.providers.settings\ folder)
Thanks miztaken1312 for the hint.
Click to expand...
Click to collapse
I knew about that app, but I'm one for security. I trust no one and nothing with anything on my phone. So if that app can access my settings.db file, it can access more. Unfortunately, there are some really sneaky little ****s out there.
Thanks a ton guys, this was making me go crazy!
Going to flash back to stock, make the appropriate changes and then give Assonance 5.0 a try with the new settings.
miztaken1312 said:
Affects all Storm 8 games, (World War and whatever else there is), KIK, other messaging apps, Appbrain, and I'm sure there are more.
I knew about that app, but I'm one for security. I trust no one and nothing with anything on my phone. So if that app can access my settings.db file, it can access more. Unfortunately, there are some really sneaky little ****s out there.
Click to expand...
Click to collapse
Good to know, thank you!
CasseTrop said:
Good to know, thank you!
Click to expand...
Click to collapse
Glad to help
Sent from my Captivate
I know some of you have been having problems with a force close message that looks like this: Android.process.media is not responding please force close or retry.
I have done search after search only to find one way that ultimately fixes this annoying every second force close message.
1. Make sure your phone is rooted.
2. Using a file explorer of your choice go into the directories as follows:
/system/app/
3. Delete this file from the menu, mediaprovider.apk
4. Force close messages will now stop. Horray!
If you have questions post them. I will do my best to answer.
StaplesDroid
i tried it on my G2 and it hasn't worked yet. Had to give ES FileExplorer root.
Have a great morning!
..........
media.process force close issue rooted htc desire
I fixed this problem without any further issues by clearing the download cache - I'm just as surprised as you.
staplesdroid said:
Yea like I said you must have a rooted phone!!!. Did it work after you gave es file root?
Another great program in root explorer. You can get it from ww w. 4shared .co m
Go there type in rootexplorer .apk and it will have multiple downloads. Just pick one and run it.
You can get all the paid apps for free like that. Just type in .apk after the app you want is typed in for example: rootexplorer .apk or irunner .apk or androidbanking .apk..... you get the picture?
Click to expand...
Click to collapse
Or you could get it from the market, and pay for it, and support the developers. But if you want to be a thief, that's your decision.
..........
staplesdroid said:
I'm not trying to piss anyone off. Sorry if you don't agree with that. But 3.99 for a file explorer. Come on.
Click to expand...
Click to collapse
It never ceases to amaze me how people can justify being a thief.
If 4 bucks is out of line, how is it you could afford your phone in the first place?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
The purple bear gets the purple worm!
indymx said:
It never ceases to amaze me how people can justify being a thief.
If 4 bucks is out of line, how is it you could afford your phone in the first place?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
+ 1, a one time payment of $4 for something useful is nothing.
Sent from my abucus
why patronize piracy?
I live in Asia, where pirated software/apps are more prevalent than legit ones. That is because software like Microsoft Windows is economically out of reach for the man on the street.
But $3.99? Come on! We shouldn't expect devs to continue churning out useful code without getting paid for it. If the developers of Titanium Backup or Root Toolbox had decided early on that it wasn't worth it to develop apps for Android or WinMo, we'd all still be in the Dark Ages of the cellphone era. Making custom ROMs is not the same. For one, many of them were based on stock firmware--which were made by highly-paid software engineers at phone makers in the first place.
What the Android Market offers for free, I download for free. When it has a price and I need it, I pay for it. Simple as that.
1) the fix listed above worked perfectly for me. (HD2, gingerbread, CM7)
2) paying for an app is the right thing to do. free ones are preferred, of course. you know it, i know it, they know it. support open source, support the community. pay it forward.
staplesdroid said:
I know some of you have been having problems with a force close message that looks like this: Android.process.media is not responding please force close or retry.
I have done search after search only to find one way that ultimately fixes this annoying every second force close message.
1. Make sure your phone is rooted.
2. Using a file explorer of your choice go into the directories as follows:
/system/app/
3. Delete this file from the menu, mediaprovider.apk
4. Force close messages will now stop. Horray!
If you have questions post them. I will do my best to answer.
StaplesDroid
Click to expand...
Click to collapse
Thanks for the tip mate. I got rid of FC's after removing mediaprovider. But after removing it cannot access any sort of media like photos, ringtones etc :-D. Any other work around?
WARNING!
fshami said:
Thanks for the tip mate. I got rid of FC's after removing mediaprovider. But after removing it cannot access any sort of media like photos, ringtones etc :-D. Any other work around?
Click to expand...
Click to collapse
Yep, this is actually a horrible fix. For me, it did nothing except stop me from accessing any of my media. So if you don't care about listening to music, viewing any photos, having ringtones, viewing video you have taken etc, this MIGHT work for you. I had to dig out the mediaprovider.apk from the .zip of my ROM and replace it.
I fixed mine by restoring my last Titanium Backup ("restore all apps with data"). Whatever was corrupted was restored back to working order. I understand that not everyone has Titanium Backup, but it has save my a$$ a couple of times now when an app or system file has started acting weird. Root your phone and get TB, it's so worth it.
EDIT: OK, so the problem came back after I replaced mediaprovider.apk, so apologies for that. I booted into recovery and did a factory/data reset, then restored my Titanium Backup, and all seems to be good now. Again, I understand this may not help everyone, but it worked for me, and it avoids deleting apk files without fully understanding what effect it will have.
Help
I have a droid 2 global. i tried deleting the file and it says i cant. is there anything else i can do? i cant access my pics, music, or market.
la vela said:
I fixed this problem without any further issues by clearing the download cache - I'm just as surprised as you.
Click to expand...
Click to collapse
Did this too, was having FCs after installing a new ROM but just cleared the cache and rebooted. My music player worked again after that.
Nothing works!
I tried deleting it which made things worse! Non stop FCs! Put it back. Cleared data multiple times! Rebooted some times! No luck! What to do! Heeelllppppp!!!!!!!!!
CyberZ-JB said:
I tried deleting it which made things worse! Non stop FCs! Put it back. Cleared data multiple times! Rebooted some times! No luck! What to do! Heeelllppppp!!!!!!!!!
Click to expand...
Click to collapse
Try formatting ur sdcard, for me i had some temp folders with long file names which used to mess around..
Sent from my HTC Desire HD using xda premium
fshami said:
Try formatting ur sdcard, for me i had some temp folders with long file names which used to mess around..
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Tried even that! Someone said it might be a Framewore issue! God knows what Android is made of! HELLLPPPPP!!!!!!!!!!!!
staplesdroid said:
I know some of you have been having problems with a force close message that looks like this: Android.process.media is not responding please force close or retry.
I have done search after search only to find one way that ultimately fixes this annoying every second force close message.
1. Make sure your phone is rooted.
2. Using a file explorer of your choice go into the directories as follows:
/system/app/
3. Delete this file from the menu, mediaprovider.apk
4. Force close messages will now stop. Horray!
If you have questions post them. I will do my best to answer.
StaplesDroid
Click to expand...
Click to collapse
I had the same problem with my Asus transformer. In addition the default Music player did not work anymore as it used to (played the wrong numbers).
The above solution did not work for me (I could get to the files mentioned without rooting).
Sofar I got the problem solved as followed.
1. I found an new version 4 of the Music player (com.google.android.misic.4.0.9.apk) and installed this version
2. This by itself did not solve anything, but now I could reinstall the factory original version and now everything is OK.
No forced closing anymore and the default player works as before
I hope it stays this way.
regards,
alfred
I've just updated to latest Oxygen on my Huawei U8800, and was having that same issue.
After reading this post, I've updated with TB the application "[Playlists] Media Storage 2.3.7 (10)" and it solved it.
It seems that my custom playlists of the music app were causing it...
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!!!
I'm not referring to the groupMe app, because they'd also have to install that.
I've tried Go SMS, pansi SMS, chomp SMS, and they don't seem to do it perfectly.
When I receive a group text from an iphone user, I want it to make a new thread with all members of the group text, where I can seamlessly respond to all users. Moreover, the stock app does this in a way that my response is not received as a group text on their end, but simply a message to them (as well as whoever else was in the group). Thus, the response goes into our 1v1 chat thread.
All I want is a plugin, rom, app, anything that solves this ridiculously frustrating issue.
I'd like to know as well. I have not been able to find an easy way to do it. I'm guessing it's Apple hating on us Android folks.
GoSMS does it very well, subject to a few limitations, not sure why it is not working for you. A couple of things to keep in mind.
1) The proper threading is not native but is run after the fact. This requires that the message be fully downloaded before it is properly threaded. This can take 10-15 seconds, if you open the message during that time it will not thread correctly.
2) Unfortunately the app will notify you twice, once the original message is received, and once it is recategorized. I handle this by shutting of sound and vibration in the app and using Tasker instead. If two notifications arrive within 15 secs Tasker just ignores the second one.
From what I have been told Handcent will do something similar
The GoSMS / Handcent implementations are ****. Sorry, but they are.
I've heard tell that Android finally put native group SMS / MMS into Android 4.2, which will likely never come to our phone officially but hopefully we'll get some of the benefit at least as things trickle down in the development community.
I'm also trying to find a solution to this too and I'm always hoping that every update of Go Sms and Handcent fixes this feature. Like one of the previous replies above stated, GO SMS will give you double notifications. It's annoying because it slows down your phone if you get too many all at once.
I've found that Handcent works better than GO SMS because it only notifies you after the message has been downloaded and you don't get double notifications. However, it's still flawed because sometimes your messages hang and dont download properly unless you physically click download. Also, sometimes when you're sending a text and try to hit send, it looks like it sends but just disappears. If you wrote a long message, you would have to re-type it all over again and hope it sends correctly the second time.
If you install CM 10.1 (android 4.2.2), this group messaging feature is baked into the rom. This is probably the best experience I've had to get the group messaging to work. It works like how an iphone user would see it. However, CM 10.1 still has some minor glitches that made me temporarily go back to sense roms. With every nightly, things seem to be getting better though. I will probably try it again in a couple weeks.
Currently I'm back on Viper using Handcent.
Have you tried side loading the MMS apk from 4.2?
Sent from my HTC One X using xda app-developers app
ChrisPBacon said:
Have you tried side loading the MMS apk from 4.2?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
+1 messaging from 4.2 works great
RollTribe said:
+1 messaging from 4.2 works great
Click to expand...
Click to collapse
Nice. Where did you guys get it from?
RollTribe said:
+1 messaging from 4.2 works great
Click to expand...
Click to collapse
Really? Doesn't seem to be working for me. I'm running aokp 4.2.2. Is there something else I must do? I see group messages are checked in the settings already
Sent from my One X using xda app-developers app
Yeah 4.2.x does this. Try it out
Sent from my One X using xda app-developers app
Guys, where can I find this APK?
can someone dropbox the newest apk?
So i tried installing this:
https://www.dropbox.com/s/oisv83ye8yv75lj/Mms.apk
I'm on ViperXL right now. I downloaded that MMS.apk to my phone and just tried running it, and the install process came up. Clicked yes through it but the app just force closes.
Am I doing something wrong here?
qozon said:
So i tried installing this:
https://www.dropbox.com/s/oisv83ye8yv75lj/Mms.apk
I'm on ViperXL right now. I downloaded that MMS.apk to my phone and just tried running it, and the install process came up. Clicked yes through it but the app just force closes.
Am I doing something wrong here?
Click to expand...
Click to collapse
I've been told before that SMS apps for stock Android won't work on Sense ROMs and vice-versa. No idea why or if that's really true.
qozon said:
So i tried installing this:
https://www.dropbox.com/s/oisv83ye8yv75lj/Mms.apk
I'm on ViperXL right now. I downloaded that MMS.apk to my phone and just tried running it, and the install process came up. Clicked yes through it but the app just force closes.
Am I doing something wrong here?
Click to expand...
Click to collapse
I've successfully run a CM10.1 mms.apk in CM10, but I've never tried this with Sense. Do you know what ROM that mms.apk file you have is actually from? I know CM10.1's mms.apk is compiled to require a minimum of JB 4.1, but versions from other JB 4.2 ROMs might have possibly been compiled to require JB 4.2
FWIW: mms.apk file is normally located in the /system/app folder, which requires root permissions to move a file to. File permissions might also need to be modified. Sense doesn't normally has a mms.apk in there since the stock messaging app is built around Sense and I believe the name starts with "htc", but I would assume a new mms.apk would at least run. I'm not sure whether this file location and permissions are actually part of your problem
update -
I've tried the entire process of putting the app in system, setting permissions, and installing, rebooting etc. No avail. App still force closes as soon as it opens.
I think the problem is in fact something to do with sense. I deleted the old messaging app as well first but that didn't do anything either.
Damn.
4.2.2 MMS force closes on viper 4.1
I uninstalled all the htc language packs, htc messaging. Install mms.apk.
I can get the app open, change settings, type a message... But as soon as I add a recipient it force closes.
Since I can do the things I can with the app open seems as though it should be able to work
If there is anyone that wants to work on this? I don't want to bug Turge with it.
Which mms.apk did you install?
Sent from my Evita
The one you uploaded in viperxl forum.
Sent from my HTC One XL using Tapatalk 4
rogcaw82 said:
The one you uploaded in viperxl forum.
Sent from my HTC One XL using Tapatalk 4
Click to expand...
Click to collapse
That is an mms.apk from an aosp ROM, I didn't mention that when I uploaded it. It won't work properly on a Sense ROM.
Sent from my Evita