MMS Fix for CM9 Marvelc - HTC Wildfire S

MMS Fix for CM9 Marvelc - HTC Wildfire S

So I found this mms fix for another type of phone and tested it on my Wildfire S marvelc (VM USA). The solution has fixed the mms problem that I have found on CM9 ROMs. I have only tried this on CM9 Alpha 8 but it should work on ParanoidAndroid and other CM ROMs. If developers could incorporate this into the build.prop files, it would be great and save noobs like me some time =P.
Instructions:
- Using a file explorer such as Root Explorer, go to /system/build.prop
- Make sure the system is mounted as writable.
- Open build.prop with the built-in text editor.
- Add the 4 lines listed below that correspond with your provider. I don't think it matters where you add the 4 lines so you could add it at the end of the file. I could be wrong about this so I hope someone more knowledgeable can verify this. I added the lines right under the APN/MMS section of the build.prop file.
VM USA:
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
gsm.operator.alpha=Virgin Mobile US
gsm.operator.numeric=311490
Click to expand...
Click to collapse
Metro PCS:
ro.cdma.home.operator.numeric=310027
ro.cdma.home.operator.alpha=Cricket
gsm.operator.alpha=Cricket
gsm.operator.numeric=310027
Click to expand...
Click to collapse
*I only listed two providers but if you have another one, visit the link below in the credits to get your information.
- Save the file and then reboot the phone.
- Enjoy MMS!
*I did not make this fix and am just posting it in this section.
Credits:
mucus_android
http://forum.xda-developers.com/showthread.php?t=1622055

When I use this on my Marvelc (Virgin Mobile USA) on CM9, I get an error code 34. Before this patch, the phone reported that the MMS was sent, but it never was.

kalaker said:
When I use this on my Marvelc (Virgin Mobile USA) on CM9, I get an error code 34. Before this patch, the phone reported that the MMS was sent, but it never was.
Click to expand...
Click to collapse
When did you get the error code? From trying to send a MMS? I'm using CM9 Alpha 8 by dudeman1996. I only added the lines and then saved the file then restarted my phone. When I saved the file, Root Explorer automatically made a back up file (.bak). That's all you have to do, nothing else. I never used the MMSfix.zip file in the link I left in the credits section.
I added the 4 lines after the MMS APN section so it looks like this:
# Modify MMS APN retry timer from 5s to 2s.
ro.gsm.2nd_data_retry_config = max_retries=3, 2000, 2000, 2000
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
gsm.operator.alpha=Virgin Mobile US
gsm.operator.numeric=311490
Click to expand...
Click to collapse
I have sent picture messages to myself as well as to friends and I have received my messages as well as those from my friends too. My phone was just flashed before doing this too so that may be a reason?
Here's a link to build.prop for dudeman1996's Alpha8: https://dl.dropbox.com/u/56758730/build.prop

Silent7x said:
When did you get the error code? From trying to send a MMS? I'm using CM9 Alpha 8 by dudeman1996. I only added the lines and then saved the file then restarted my phone. When I saved the file, Root Explorer automatically made a back up file (.bak). That's all you have to do, nothing else. I never used the MMSfix.zip file in the link I left in the credits section.
I added the 4 lines after the MMS APN section so it looks like this:
I have sent picture messages to myself as well as to friends and I have received my messages as well as those from my friends too. My phone was just flashed before doing this too so that may be a reason?
Here's a link to build.prop for dudeman1996's Alpha8: https://dl.dropbox.com/u/56758730/build.prop
Click to expand...
Click to collapse
I'm on a recent build I compiled myself (slightly newer than Alpha 8). I just added the 4 lines. It should have worked just as well as Alpha 8, as I compiled this just the other day.
I didn't flash any zip. Just added the four lines. I'll try again.

Related

(req)epic 4g touch metro mms and wed settings

okay so i flashed my epic 4g touch to metro pcs with talk and txt and need some guidance to add web and picture msgs does some on have instructions or a link?

lexo1a said:
okay so i flashed my epic 4g touch to metro pcs with talk and txt and need some guidance to add web and picture msgs does some on have instructions or a link?
Click to expand...
Click to collapse
Bump! Would like to get some guidance on the "MMS (Picture Messages)"
Thanks in advance!

lexo1a said:
okay so i flashed my epic 4g touch to metro pcs with talk and txt and need some guidance to add web and picture msgs does some on have instructions or a link?
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=1303507

Been trying that with no luck! ;(
The EVO 3D was my last device and I did all the settings myself... But, the Epic Touch S2 seems a little trickier but, I think i'm just missing something simple!
All help is appreciated
Sent from my dociousaliexpilisticfragicalirepus SPH-D710 using XDA Premium!

i currently have an epic touch and also can not get mms to work. i believe a modded mms.apk is needed.

livnda209 said:
i currently have an epic touch and also can not get mms to work. i believe a modded mms.apk is needed.
Click to expand...
Click to collapse
Try this
MMS
MAKE SURE YOUR WEB IS WORKING PROPERLY (ABOVE INSTRUCTIONS) AS YOU CAN'T HAVE MMS WITHOUT WORKING INTERNET!!!!!
Remove/Uninstall any existing MMS composer you have attempted to setup. Also a good idea to remove any registry keys it may have created that are left behind after the uninstall.
1: Install Arcsoft MMS version 5.0.70.24 from Verzion.
2: Open your Messaging and click on the SMS/MMS option.
3: Click on "Menu" and select "MMS Options" then select the "Servers" tab.
4: Add a new server with the following settings:
Server Name: metropcs
Gateway: wap.metropcs.net
Port number: 3128
Server address: http://mms.metropcs.net:3128/mmsc
Connect via: SELECT EITHER THE CONNECTION YOU SETUP ABOVE OR "The internet"
Send limit: 399K
5: Click "Done" and then set the new server as default.
6: Using a Registry Editor edit the following values:
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader]
DELETE KEY -> "X-VzW-MDN"
ADD STRING -> "X-metropcs-MDN"="XXXXXXXXXX" ( Insert your 10 digit phone Number )
ADD STRING -> "X-DEVICE-MIN"="1XXXXXXXXXX" ( Insert your 10 digit phone Number WITH the 1 in front of it )
Code:
http://rapidshare.com/files/166154036/HTC_VOGUE_METRO_WEB_MMS_SETTINGS.rar.html
pulled from
http://forum.xda-developers.com/showthread.php?t=448955
---------- Post added at 12:16 PM ---------- Previous post was at 12:10 PM ----------
livnda209 said:
i currently have an epic touch and also can not get mms to work. i believe a modded mms.apk is needed.
Click to expand...
Click to collapse
Try this as well
Use this guide to get MMS for Metro. Replace the mms.apk as directed. Do Not remove the telephony.db file(dont replace or delete). Go to voice Dialer, say open APN. Create MetroPcs apn with these [URL="http://forum.xda-developers.com/show....php?t=1288216"][URL="http://forum.xda-developers.com/showthread.php?t=1288216"]settings[/URL][/URL](. For the record I used CleanGB Rom 1.0 - EI22 Modem.
If you should encounter any difficulty after rom flashes, make sure your prl is current. I ran across a problem earlier that stumped me for a bit, airplane mode would toggle on/off and became frustrated to no end.
MetroPCS APN Settings Guide:
These are settings provided to help users with MMS, and 3G.
It works with Most roms. Tested and Confirmed on Swagged Out Stock.
1.Flash an MMS script compatible with your rom. (Scripts created By Bloodykiller86)
MetroPCS Evo Sense 4.53 Based MMS Script v1.5
MetroPCS Sense 2.1/3.0 Hybrids MMS & Web Script v2
MetroPCS Evo AOSP Script v5
MetroPCS Evo MIUI MMS Script v1
2.Download APN Manager from the Android Market.
3.Create a new APN and enter these settings:
APN: internet
Proxy: wap.metropcs.net:3128
Port: 3128
UserName: Phone#@mymetropcs.com
Password: MSL code*
Server: wap.metropcs.net
MMSC: http://mms.metropcs.net:3128/mmsc
MMS Proxy: wap.metropcs.net
MMS Port: 3128
MCC: 310
MNC: 004
APN Type: MMS
4. Download Any Cut from the Android Market, then create an activity, apns on your homescreen.
Open apns choose MetroPCS and edit then authentication type to pap or chap. If no APN exists create a new one and fill it in with the info above.
-Make sure to enable created APN in APN Manager.
-Also if your MMS still isn't working make sure the metropcs.sh file from the script is in the correct place, if it is execute it. If It's not etract it from the script, and place it in the root of the internal memory, set permissions, and then execute it.
*If you want to figure of your MetroPCS MSL code check out whiterabbit.org
pulled from
http://forum.xda-developers.com/showthread.php?t=1288216

Thanks for the suggestions brianhot1 but the first suggestion is for window's mobile phones. I use to use that method back in the day and it does work but not for android's. Second method has correct apn settings but the modded mms.apk is for htc evo. It would not be compatible with a samsung epic touch as android version and and rom play a factor into making a modded mms.apk. Hopefully i will find a way to get it working soon tho.

Just get ur mms apk. Get apktool decompile nd edit mms.config
livnda209 said:
Thanks for the suggestions brianhot1 but the first suggestion is for window's mobile phones. I use to use that method back in the day and it does work but not for android's. Second method has correct apn settings but the modded mms.apk is for htc evo. It would not be compatible with a samsung epic touch as android version and and rom play a factor into making a modded mms.apk. Hopefully i will find a way to get it working soon tho.
Click to expand...
Click to collapse
Sent from my SPH-D710 using XDA App

thanks for pointing me in the right direction! I got apktool now and i go to decompile the original mms.apk and it gives me an error message at the end that i need to install the specific framework for my phone. I used root explorer to get them onto my laptop. Just stuck on installing them now.

Flashed tablets before, but never a phone to switch carriers. I have my eyes on the same solution being discussed here - Samsung Epic Touch 4G on MetroPCS. Is the solution Brian provided the standard steps needed to flash any android device or does it differ between specific models?
try this
http://forum.xda-developers.com/show....php?t=1303507
Click to expand...
Click to collapse
Thanks!

livnda209 said:
thanks for pointing me in the right direction! I got apktool now and i go to decompile the original mms.apk and it gives me an error message at the end that i need to install the specific framework for my phone. I used root explorer to get them onto my laptop. Just stuck on installing them now.
Click to expand...
Click to collapse
install framework is
Code:
apktool if framework-res.apk

[Wondering]
Hey can't I just make an app for it?
You using Eclipse you can just make a messaging app.
Wouldn't I just be able to add the MetroPCS APN settings to it?

http://metropcsflash.blogspot.com/p/samsun-galaxy-s2-metropcs-full-flash.html

lexo1a said:
okay so i flashed my epic 4g touch to metro pcs with talk and txt and need some guidance to add web and picture msgs does some on have instructions or a link?
Click to expand...
Click to collapse
This is the simplest and most effective method I've found, try this first:
http://forum.xda-developers.com/showthread.php?t=1912451

[ROM UPDATE 01/19/12][Deodexed][1.12.23-2.1.13 Framework][ICS] Nexus S 4G 4.0.3

In the interest of time I will make this quick. I ported this from MIUIScotland's 4.0.3 rom. Everything works if you flash the matrix kernel 13 or 14.5 (see below) Feedback is good.
Proceedure:
*v.1.12.23*
1. Full Wipe (format data, system, boot, cache if boot loops)
2. Flash rom (link below)
3. Flash either of the Matrix Kernels below.
4. Reboot and enjoy
*Update v.1.12.23-2.1.6*
Notes: ROM can be flashed over 1.12.23. Researching standalone flash results. For now install 1.12.36 (the original) then the update to be safe.
Full wipe if coming from anyother rom besides 1.12.23
*memory offset notice during flash is not an error notice, so disregard as normal.*
Working:
WiFi, bluetooth, voice, data, GPS, market, launcher, camera, DHCP, SU, Exchange (ActiveSync), Flash Player*
*Download the BrowserGoogle.apk>place in /system/app directory>fix permissions>enjoy
Not Working:
WiMax
Download Links:
http://hotfile.com/dl/138804622/cc66084/miuiscotland_ICS-NS4G-LamontClan-signed.zip.html
Mirror: http://www.mediafire.com/?crpan11q1dxqyz6
Oh yeah, I am not liable for anything that happens due to this rom.
**No worries though this ROM is stable and crisp.
Includes bash-4.0.0 binary that I added as a supplement. type "bash" using any terminal emulator apk and then type help to view command and version info.
01/16/2012
Update: Below is the ROM Update I promised to deliver.
Version: 1.12.23-2.1.6----->>>>> I have merged my orginal base rom with the 2.1.6 MIUI framework. This merge results with all features functioning as in the orginal rom, but with the added system ui color scheme of 2.1.6. Also, I have added about a dozen new binary files in the /system/bin directory that I have aquaired and or patched from the basic ARMel Linux architecture. In addition to these binary files, I included about 12 new apk in the rom to minimize my own post flash configuration process. I hope that this can save someone else a little time and frusteration too. Bonus features of the new framework are the Supermarket, Notes, YouTube, Google+, DSPManager, the original SprintTV app, the orginal Nexus 3D Gallery, and all Supermarket downloads are now fully functioning. The build number is the same to prevent the mobile data from crashing. So with out further adoo, Here tis'...
Download Link: http://www.mediafire.com/?3c4rbocb90nne49
ATTENTION- Force Closes on inital boot can accure, but should not persistantly inhibit system function. Solution below...
REPLACE GOOGLELOGINSERVICE.APK AND GOOGLESERVICESFRAMEWORK.APK WITH THE RESPECTIVELY NAMED APKS BELOW IN /SYSTEM/APP/. MANUALLY FIX THE PERMISSIONS TO MATCH AL THE OTHER APKS IN /SYSTEM/APP/>REBOOT. [1.17.12]Upgrade (pronounced Oop-grad in German*) Build v4 1.12.23 R2: China 2.1.6 framework resources included
This refined version is fully flashable after a complete wipe/total device reformat (I tested it on my crespo4g this time). I has a tone of features and I received only one force close on boot, Updater App, which after closing only once did not come back to stain me like mustard on a new pair of pants or pantaloons depending on your local vernacular.
What works[Everything from previous builds +]: USB Mounting, Facelock, Language Dictionaries, Theme Manager's online library, over 2000kb/sec downstream on 3g (basically 4g is working after you create a new APN named sprint[pm me of look it up on the net if you need help.
Not Working: MMS..probably..I am sure someone will let me know about their precious mms
*Quote form the timeless Cinemagraphic classic entitle "Idiocracy"
Download Link (Large File Dawg)
http://hotfile.com/dl/142398573/d1fa5c8/miui-1.12.23-2.1.6-framework-refined.zip.html
Download Link (Fully Deodexed Version) *NFC does not function and must be disabled before flashing update*
http://hotfile.com/dl/142706214/e5f4304/miui-1.12.23-2.1.6-framework-refined-fully-deodexed.zip.html
*UPDATE Version 1.12.23-2.1.13 Deodexed*
http://hotfile.com/dl/142724529/69c...3-framework-refined-fully-deodexedv2.zip.html
Includes MIUI framework from ICS 2.1.13. Again NFC does not work, under review. Solution=disable in setting or if flashing update than disable NFC in the setting menu before flashing this update.
Much Obliged,
B-Dawg
Many Thanks the developers below:
Brainmaster: update-script and overall inspiration
MathKid: Use of Matix Kernels on this thread.
All Linux users everywhere for their continued interest and providing a demand for us poster dudes and dudettes.
Remember to click "Thank You" if you download my work.

bdawg31 said:
In the interest of time I will make this quick. I ported this from MIUIScotland's 4.0.3 rom. Everything works if you flash the matrix kernel 13 (see below). Browser is kinda buggy but just use the "request desktop site " and select google as your default search provider. Feedback is good.
http://hotfile.com/dl/138804622/cc66084/miuiscotland_ICS-NS4G-LamontClan-signed.zip.html
Click to expand...
Click to collapse
I guess I am the first to download. Thanks...downloading now

bdawg31 said:
In the interest of time I will make this quick. I ported this from MIUIScotland's 4.0.3 rom. Everything works if you flash the matrix kernel 13 (see below). Browser is kinda buggy but just use the "request desktop site " and select google as your default search provider. Feedback is good.
http://hotfile.com/dl/138804622/cc66084/miuiscotland_ICS-NS4G-LamontClan-signed.zip.html
Click to expand...
Click to collapse
What do you mean everything works "if you flash matrix kernel 13"?? I am about to flash, dont want to jack my phone up!!
Thanks for the port.....
Edit: what does roam indicator off mean? Is it supposed to be in roam mode?

Yeess!! Thank you!

My pleasure.

I haven't tried miui ics yet. This might be my first flash.
Sent from my CM9 alpha-19 Linux S 4G using xda premium

going to give it a spin

Thanks for the port downloading now I already got the matrix 13 so no need to download it!! ; )
Sent from my Nexus S 4G using xda premium

I had constant reboots... Did a full wipe and fixed permissions and installed it again and still rebooting constantly.... Thanks for your hard work nonetheless
Sent from my Nexus S 4G using Tapatalk

craigbailey1986 said:
What do you mean everything works "if you flash matrix kernel 13"?? I am about to flash, dont want to jack my phone up!!
Thanks for the port.....
Edit: what does roam indicator off mean? Is it supposed to be in roam mode?
Click to expand...
Click to collapse
It is a aethetic error. Usually roms say "Sprint," but I did not edit the xml, so it reads that the phone is not roaming, which is the next line item in the array string.

It says everything works but does mms work??
Sent from my Nexus S 4G using xda premium

Esteway.619 said:
It says everything works but does mms work??
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
have not tested mms.

Links broken...
Sent from my Nexus S 4G using xda premium

solesonfire said:
I had constant reboots... Did a full wipe and fixed permissions and installed it again and still rebooting constantly.... Thanks for your hard work nonetheless
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I did not edit the boot.img or the framework, so you shouldn't have boot loop problems. Formate system, data, cache, and boot. Reflash rom and please let me kow the result for troubleshooting purposes. Thank you.

Nope, just tested all three. Check browser settings ie pop-up blocker or safe-screening type filter settings.

bdawg31 said:
Nope, just tested all three. Check browser settings ie pop-up blocker or safe-screening type filter settings.
Click to expand...
Click to collapse
I'm on phone?
Sent from my Nexus S 4G using xda premium

What is the status of those who have flashed?

BLEEDCOLORYOU said:
I'm on phone?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Ok, wait a big and try again. I will post a mirror soon. It appears it is a access limit issue. Sorry for the inconvienence.

downloading now will let you know how it goes.

Mirror Up
I just added a mirror for the rom download. I hope this will solve download demand issues.

[MOD][App][TouchWiz][secMms.apk] Samsung sms JB v2 (Enhanced Spam list+Other mods)

I was facing a problem. I received several unwanted messages from my carrier docomo, ads etc. So I went to register the number as spam in stock messaging app but I couldn't saying invalid number. The numbers contained alphabets. I tried replacement apps like GOsms and handcent . They did the job but returned to stock as it was simple and linked to lock screen and all.
Being a xda member i modded the secMms.apk to even block numbers containing alphabets
v2 :Now you can type in the alpha numeric contacts
Tested on BUG ROM v5.1 NOTE 2 MINI I9100 (deodexed)
But will work on any jb rom (deodexed/odexed)
Other features in v2 (all thanks to jovy23 for his awesome guide )
1. ENABLE THE SCREEN ON/OFF TOGGLE for notification
2.ADDED THE VIBRATION
3.SIGNATURE OPTIONS
4.GROUP MESSAGING
5.SAVE/RESTORE
6.SCHEDULED MESSAGING
7.SMS 1000/UNLIMITED RECIPIENT LIMIT(haven't tested )
8. Exact sent time of received messages, not the moment when you actually received it on your phone
9. DISABLE THE SMS TO MMS AUTO-CONVERSION(not tested please report back)
10. SPLIT-VIEW MODE ON/OFF TOGGLE
INSTRUCTIONS
1.download and extract secMms.apk
2.Rename system/app/secMms.apk to like secMms.apkold(backup)
2.1 Also rename system/app/secMms.odex to like secMms.odexold (only for stock roms/odexed )
4. Place extracted secMms.apk to system/app (check permissions for executable )
3.reboot phone and enjoy 
Dont forget to hit thanks

Great keep up the good work :thumbup:
Sent from my GT-I9100 using xda premium

rickslick said:
Hey guys this is my first thread
I was facing a problem. I received several unwanted messages from my carrier docomo, ads etc. So I went to register the number as spam in stock messaging app but I couldn't saying invalid number. The numbers contained alphabets. I tried replacement apps like GOsms and handcent . They did the job but returned to stock as it was simple and linked to lock screen and all.
Being a xda member i modded the secMms.apk to even block numbers containing aphabets
Tested on BUG ROM v5.1 NOTE 2 MINI I9100 (deodexed)
instructions
1.download and extract secMms.apk
2.replace /preload/symlink/system/app/secMms.apk with the extracted one using any root file manager like es explorer etc
3.reboot phone and enjoy
Note :To register a number as spam long press the thread or go to specific thread and press menu key and register
Next update soon
extending the ability to type in the alpha numeric number as spam
Click to expand...
Click to collapse
Thats a great idea!Wonderful:good:
And what about unlimited recipients and no auto convert sms-mms?

WarcoLLapsE said:
Thats a great idea!Wonderful:good:
And what about unlimited recipients and no auto convert sms-mms?
Click to expand...
Click to collapse
Sure in next version it's easy as it is already done
Anyways next version will contain better tweaks in spam list like ability to block numbers starting/containing/ending with alphanumeric

rickslick said:
Sure in next version it's easy as it is already done
Anyways next version will contain better tweaks in spam list like ability to block numbers starting/containing/ending with alphanumeric
Click to expand...
Click to collapse
Will w8 for update:victory:
Thats exactly that i was looking for - stock extended sms app with true spam ability:laugh:
If it will be possible to add custom vibration then u r my new hero

Do you know if this would be compatible with CyangoenMod, or does it still need TouchWiz as a base?
Thanks!

Zero4 said:
Do you know if this would be compatible with CyangoenMod, or does it still need TouchWiz as a base?
Thanks!
Click to expand...
Click to collapse
stock apks uses some pngs in framework.apk, so this will not be compatible with cm

Zero4 said:
Do you know if this would be compatible with CyangoenMod, or does it still need TouchWiz as a base?
Thanks!
Click to expand...
Click to collapse
Sorry it works only on touchwiz framework

pankaj_GB said:
stock apks uses some pngs in framework.apk, so this will not be compatible with cm
Click to expand...
Click to collapse
rickslick said:
Sorry it works only on touchwiz framework
Click to expand...
Click to collapse
Thanks Guys. That's what I thought but wasn't 100%.
I really like the look of the TouchWiz Messaging & Dialer apps, but I don't want TouchWiz taking up resources in the background on my GS3 if I switch to Cyanogen.

Ohhh maaaan.....i will test it later and report...seems to me its a stock sms bomb app

WarcoLLapsE said:
Ohhh maaaan.....i will test it later and report...seems to me its a stock sms bomb app
Click to expand...
Click to collapse
Yes please test it :good:

Hi ! Thanks for the work !
Tested on a Galaxy S2 4.1.2 (stock ROM XXMS2) FRENCH, and after reboot only "9. DISABLE THE SMS TO MMS AUTO-CONVERSION" works.
No new menu (scheduled messages, About...), no "8. Exact sent time of received messages, not the moment when you actually received it on your phone"...
Maybe 'cause I'm using a french stock ROM ?
I'm going back to the original SecMms.apk
EDIT : Actually, JB doesn' t convert SMS to MMS after 3 SMS ! So, unfortunately, your mod doesn't work at all with my phone :crying:

dixours said:
Hi ! Thanks for the work !
Tested on a Galaxy S2 4.1.2 (stock ROM XXMS2) FRENCH, and after reboot only "9. DISABLE THE SMS TO MMS AUTO-CONVERSION" works.
No new menu (scheduled messages, About...), no "8. Exact sent time of received messages, not the moment when you actually received it on your phone"...
Maybe 'cause I'm using a french stock ROM ?
I'm going back to the original SecMms.apk
Click to expand...
Click to collapse
Let me just verify

Thank you so much !!
I've just edited my post above
EDIT : Actually, JB doesn' t convert SMS to MMS after 3 SMS ! So, unfortunately, your mod doesn't work at all with my phone
Click to expand...
Click to collapse
Hope you'll find a fix !
Thank you again

dixours said:
Thank you so much !!
I've just edited my post above
Hope you'll find a fix !
Thank you again
Click to expand...
Click to collapse
One thing is your rom is stock and i have been testing on deodexed .
I think u r still using your stock sms app
Did u notice "android is upgrading "after reboot after installing at preload/symlink/system/app (just before loading all apps)

rickslick said:
Did u notice android is" upgrading after reboot " after installing at preload/symlink/system/app (just before loading all apps)
Click to expand...
Click to collapse
Yes, I get a message like "upgrading apps..." after reboot
I'm root thanks to PhilZ, but it's a stock ROM. This is the point ?
---------- Post added at 05:37 PM ---------- Previous post was at 05:20 PM ----------
OK, it's working ! Here is what I've done :
I use a root file explorer, browse to /system/app and rename:
- SecMms.apk ---> SecMms.apkold
- SecMms.odex ---> SecMms.odexold
Open a root file manager, set permissions to RW-R-R and move SecMms.apk to /system/app
Reboot... and it works !!!
Thanks you very much !!
I'm testing now

dixours said:
Yes, I get a message like "upgrading apps..." after reboot
I'm root thanks to PhilZ, but it's a stock ROM. This is the point ?
---------- Post added at 05:37 PM ---------- Previous post was at 05:20 PM ----------
OK, it's working ! Here is what I've done :
I use a root file explorer, browse to /system/app and rename:
- SecMms.apk ---> SecMms.apkold
- SecMms.odex ---> SecMms.odexold
Open a root file manager, set permissions to RW-R-R and move SecMms.apk to /system/app
Reboot... and it works !!!
Thanks you very much !!
I'm testing now
Click to expand...
Click to collapse
Great to hear and thanks for the info

Thank YOU to notice the probably Odexed issue !
All work great !
Thanks a lot !

dixours said:
Thank YOU to notice the probably Odexed issue !
All work great !
Thanks a lot !
Click to expand...
Click to collapse
Dont forget to hit thanks if u havent

rickslick said:
Dont forget to hit thanks if u havent
Click to expand...
Click to collapse
Done !

[How To]Group Messaging AND MMS over WiFi calling for T989

Hello! This is my first write up. I'm sorry if it's in the wrong place so Moderators please move to the appropriate place.
I've done a lot of searching for group messaging for our phones (T989) and have done a lot of experimenting myself to get this to work right. I wanted to wait to create this write up until I had it working perfectly but since I'm helping a friend with an i727 Skyrocket (att GS2) I thought I'd just make the write up now. For those who have the necessary tools I've included links to decompile the files and mod them yourselves (which I've done) and those without the necessary tools I've included the working files from my stock deodexed UVMC6 ROM.
First of all threaded group messaging works on the T989 (Also working via WiFi-Calling) May even work (group messaging that is) on other Devices running stock 4.1.2.
The bugs that I haven't been able to/had the time to work out yet are as follows:
1. I can't seem to figure out...yet*...how to filter your own phone number out of incoming MMS messages the results of this are any incoming MMS will default to group messages showing you and the other person in the group. Any incoming group messages will show you in the group so any reply you make will come back to yourself unless you add your own number to the spam list.
All these issues come from the same issue, I haven't had the time to figure out where the framework2.jar file is looking to identify your phone number to filter it out of the conversation thread.
Other than that, if you can live with this issue, or want to help me identify what it is and how to fix it I would love the help.
Now for the instructions:
.5. Read all the instructions ALL THE WAY THROUGH BEFORE YOU START
1. MAKE A NANDROID BACKUP NOW also backup your messages
2. If you haven't made a backup I'm not responsible for your stupidity. Actually, even if you did make a backup I'm still not responsible for your stupidity. Only for mine...and the untold number of times I've soft-bricked my phone working on this.
3. Backup your messages
4. Reboot into recovery and install the attached zip
5. Reboot into normal and wait for Android to upgrade
6. Using your favorite root browser go to /data/data/com.android.providers.telephony/databases and delete the following files: (will delete your messages)
smsmms.db
smsmms.db-shm
smsmms.db-wal
7. IF NOT using an odexed ROM then skip to #11. IF you ARE using an odexed ROM:
a. Use your favorite root browser and go to /system/app and delete:
SecMMS.odex
SecTelephonyProvider.odex
b. Go to /system/framework and delete:
framework2.odex
8. Reboot to recovery
9. Clear cache
10. Reboot into normal
11. Enjoy group texting with iPhones and other group texting devices!
All credit and thanks go to the following developers and their threads from which I have learned so much!
jovy23 - for providing the info to edit a decompiled SecMMS.apk to enable group messaging via WiFi-Calling and other mods Info in his thread
regulusv7 - for proving group messaging in TW could be done Info here
loserskater - for the framework2.jar edits and the smsmms.db His thread here
And anyone else who I may have forgotten who helped along the way.
The info in the threads provided from those I learn from should be sufficient if you want to make changes for other ROMS or other devices.
I still want to figure out the threading issue with the sending messages back to myself by not during the holidays. I hope you guys find this information useful!

Thanks for posting this. I've been needing something like this. Will give it a try later.
Sent from my SGH-T989 using xda premium

Didn't work for me. Do u know if someone with an iOS device have to start the thread first? I created a group message and when they replied it was on separate threads.
Sent from my iPad using Tapatalk

Thanks for the great work! What I've done is just use hangouts which seems to group message fine
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

koudies said:
Didn't work for me. Do u know if someone with an iOS device have to start the thread first? I created a group message and when they replied it was on separate threads.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I doesn't matter who starts the message. I've started group messages, my friends with other Androids, and my friends with iphones - they all work fine aside from the issues I outlined in the OP. Are you running stock or close to stock UVMC6 for the T-Mobile T989? Are you odexed or deodexed? Can't help you without more info....

reverse
hello, is there something i can flash to reverse the process? im having issues sending pictures via mms now and mms period actually and im not sure if its related to this flashing or not.

stevens4life2 said:
hello, is there something i can flash to reverse the process? im having issues sending pictures via mms now and mms period actually and im not sure if its related to this flashing or not.
Click to expand...
Click to collapse
Nandroid backup. Just restore the one you made prior and you're good.
Sent from my SGH-T989

I know this is only for UVMC6, but will this work on ICS 4.0.4? (That's the only ROM I like.....The Sith)
Cuz I really want MMS over Wifi........so is the framework different for ICS? (For MMS)

stevens4life2 said:
hello, is there something i can flash to reverse the process? im having issues sending pictures via mms now and mms period actually and im not sure if its related to this flashing or not.
Click to expand...
Click to collapse
Just restore the files you backed up. replace your original SecMms.apk and SecTelephonyProvider.apk to /system/app and your original framework2.jar to /system/framework

kickcheese said:
I know this is only for UVMC6, but will this work on ICS 4.0.4? (That's the only ROM I like.....The Sith)
Cuz I really want MMS over Wifi........so is the framework different for ICS? (For MMS)
Click to expand...
Click to collapse
I don't know if it will work for 4.0.4...I guess you could make a nandroid and try it! If you don't want the group messaging I guess you can just do the SecMms.apk...thats the file that allows you to send MMS over wifi-calling. At least in my testing when I tried the same file from a Verizon S3 or an ATT Note 2, or even any Mms.apk from AOSP it wouldn't send mms over wifi unless I was using SecMms.apk from a T-Mobile ROM.
Good luck!

how to change hardware device name

hey guys,
this might be a more broader android question, but either way: is there a way to change the hardware device name of a device?
i.e. my issue is the following - i use the "good for work" application for my work emails. My company basically has every manufacturer added to their approved list (HTC, Samsung, even Nexus devices work no problem). Now that I have my sweet OP3, I get the below error message (pic attached)
"the device hardware version is 'oneplus a3000 android 6.0.1' and is not permitted. Install the application on a permitted device."
now - before you tell me to go to my network admins and have the device added - I can't do that for reasons I won't go into here. Basically i want to understand if there's a way to change certain files on the phone that will make this application think it's a nexus device and clear it.
I tried editing the build.prop file (using twrp and adb - since I don't have root) to remove all mention of oneplus, etc. and replacing with "nexus" or something else (used the build.prop file from my 5x for reference). But the app still does not work and the OP3 still shows the model as One Plus 3 in the "about phone" section. This is really fascinating to me. What is driving this device's identity?
Appreciate any thoughts/suggestions you might have.

Try xposed mods... I think it is possible

Wrong forum.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

wrong section.
post this in Q&A

@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading

Go to your Bluetooth settings, select the menu, and Rename this device.

JumboMan said:
@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading
Click to expand...
Click to collapse
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...

piotrus22 said:
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...
Click to expand...
Click to collapse
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name

JumboMan said:
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name
Click to expand...
Click to collapse
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?

piotrus22 said:
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?
Click to expand...
Click to collapse
now I think I'm going out of ideas.
I think you have to ask some experienced dev

JumboMan said:
now I think I'm going out of ideas.
I think you have to ask some experienced dev
Click to expand...
Click to collapse
how do I do that? just hope one of them sees this post? LOL

piotrus22 said:
how do I do that? just hope one of them sees this post? LOL
Click to expand...
Click to collapse
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.

JumboMan said:
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.
Click to expand...
Click to collapse
you sir are amazing. just tried it and it worked. will test it out to see if it causes other issues. may I buy you a beer?

piotrus22 said:
may I buy you a beer?
Click to expand...
Click to collapse
For me Thanks=Beer, so thanks are sufficient

JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?

The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium

piotrus22 said:
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?
Click to expand...
Click to collapse
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.

JumboMan said:
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.
Click to expand...
Click to collapse
Third party camera app has the same problem. Will revert to original build prop and see if that fixes the issue. Will report back.

JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Dethfull said:
The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium
Click to expand...
Click to collapse
@Dethfull do you know which items in the build prop coordinate to the drivers for the camera?

ok so I think I fixed it. I played around with the build.prop file and it appears changing the ro.product.manufacturer =OnePlus back from Nexus5 did the trick. Camera seems to be much faster than before and videos can save now, and the Good app still works.
Will update if things change but hopefully not!

Develop Bugs

welcome