Hi guys--
My main goal is to achieve group MMS messaging within the native MMS app. I have a Razr HD Maxx currently on 4.1.2 (9.16 vzw update). My main goal is to get group texting to work correctly, however that might occur. I've essentially been attempting two different paths to get to that point.
My first idea was to use the CM10.1 mms.apk file and manually change the other framework files that needed to be changed in order to enable the group texting so it doesn't freeze up every time anything to do with MMS happens. I found details about how to do this on Touchwiz but not Blur. I tried the TW instructions anyway but nothing happened. Neither good nor bad, it just still didn't work.
My next thought was to install a 4.2 ROM that supports group texting. I spent a few hours with Safestrap, but basically I couldn't get the damn thing to boot any safe ROMS....it would just go to a black screen. I could always reset it and boot back to stock fine, but never could boot into any ROM slots.
Here's what I tried: Initial run-through: Downloaded, installed app, rebooted, created slot, installed, and attempted. No dice. Rebooted to stock, undid recovery, installed BusyBox (I was certain my lack of BB would solve the problem), unplugged the phone from charger (at the suggestion of another forum), confirmed root was working, reinstalled recovery, downloaded alternate ROM file. Back in SS, I more thoroughly created the ROM slot, then wiped data, cache, dalvik, and system, then installed, then tried again. Same issue still. I tried the same procedure in slot 4 for $#!+s. I tried wiping, I tried deleting and recreating slots, I tried re-downloading ROMS, etc. I couldn't get the thing to do anything other than show me a black screen after hitting continue when booting from a safe slot.
A few things I noticed that I'm not sure are relevant or not. The ROM's I attempted to flash were CM10.1, Vanquish Pacman, and Vitreous. Vitreous failed the MD5 check even after 2 downloads. On stock, my baseband version is reported as VANQUISH_BP_100730.081.64.09P. I'm not sure what it was before but I feel like it wasn't Vanquish and I'm wondering if something was actually done to the real file system? It still works fine, so I'm not sure if any harm is being caused. When I try to wipe the data partition, SS says it actually failed. At first I just tried it again but I didn't worry much about it because I figured it was empty anyway (trying this between creating the slot and installing the ROM.) But when I browse although I can find the system partition in safestrap\rom-slot1 I have no idea where the data partition even goes...I can't find it anywhere to wipe manually.
So SS is baffling to me. I'm sure a few files could be modified relatively easily to bring group texting to 4.1 but I'm not sure how to do it. Both my solutions are giant fails right now. Anyone have any ideas to help me?
Thank you!!
empoweredh22 said:
Hi guys--
My main goal is to achieve group MMS messaging within the native MMS app. I have a Razr HD Maxx currently on 4.1.2 (9.16 vzw update).
Click to expand...
Click to collapse
I'm pretty sure that the HD has group messaging. In fact, when i send a SMS or MMS to a group, I get a little blue bar that tells me it's a "Group Message." Am I seeing something that you're not, or am I totally wrong?
Have group messaging and it works just fine. Stock firmware.
Sent from my DROID RAZR MAXX HD
Thanks guys. I was hoping to accomplish that with AOSP messaging as opposed to blur messaging. Not possible then?
I like AOSP messaging better because it's ugly and more importantly because it supports emoji, extended notifications, and quick reply as well as long messages and the emoticon key on the keyboard.
Related
So I'm having a really strange issue. I got my Atrix 2 a few weeks ago after owning the OG since it launched. I'm currently running 2.3.6 Stock Deodexed installed via CWM restore in bootstrap. Everything is working fine, except this: the Voice Search app, which I use a lot, continually reverts itself to default settings. As long as the app is running, it behaves normally, but when I kill the process, reboot the phone, or too much time passes, it seems to wipe out its own data. As a result, nearly every time I use it, I get this first run dialog asking me if I want to enable personalized recognition and a tutorial overlay. I've selected both options multiple times and the issue persists. A few things:
1) I'm not sure if this has been happening since the beginning, because I've been rooted and deodexed in some form or fashion since the 2nd day I had it. I don't remember initially having a problem, though. Maybe someone running straight stock with no mods could test this?
2) I use local data encryption for both the SD Card and the app storage, as required by my corporate exchange server. That's the only thing I can think of that might be causing this.
3) I've reinstalled the app multiple times.
4) It seems like Voice Search can't be moved to the SD card.
Anyone else having this problem?
KinglyCitrus said:
So I'm having a really strange issue. I got my Atrix 2 a few weeks ago after owning the OG since it launched. I'm currently running 2.3.6 Stock Deodexed installed via CWM restore in bootstrap. Everything is working fine, except this: the Voice Search app, which I use a lot, continually reverts itself to default settings. As long as the app is running, it behaves normally, but when I kill the process, reboot the phone, or too much time passes, it seems to wipe out its own data. As a result, nearly every time I use it, I get this first run dialog asking me if I want to enable personalized recognition and a tutorial overlay. I've selected both options multiple times and the issue persists. A few things:
1) I'm not sure if this has been happening since the beginning, because I've been rooted and deodexed in some form or fashion since the 2nd day I had it. I don't remember initially having a problem, though. Maybe someone running straight stock with no mods could test this?
2) I use local data encryption for both the SD Card and the app storage, as required by my corporate exchange server. That's the only thing I can think of that might be causing this.
3) I've reinstalled the app multiple times.
4) It seems like Voice Search can't be moved to the SD card.
Anyone else having this problem?
Click to expand...
Click to collapse
s a matter of fact, I have had it happen to me a couple of times too. I'm running lfabor's SC_V5 Update 2 though.
Now I shall reply to you statements / questions:
When I was running stock 2.3.5 or 2.3.6 I didn't have this issue.
I do not use encryption as its not required for my corporate sync (nor is my phone a company phone)
I have not tried to reinstall it, as I dont use very often, and only had to he issue happen a couple of times. This is also because lfabor placed it in the
system directory, and I've been to lazy to move it out.
The reason it can't be moved to SD is because the SD storage has to be enabled by the developer of the app.
Also note I am using swiftkey X for my keyboard, but if you are having issues with stock I don't think swiftkey is to blame.
I have not
I have had this issue TONS of times on a 100% stock not even rooted phone. I think there is just something screwed up, I dont think it's because of anything you did. My SD card is not encrypted, and I am also using Swiftkey X (but I doubt its swiftkey X). Infact I think it even used to happen before I started using swiftkey x.
I have the same issue, and I'm also using Swiftkey X. I'm sensing a pattern...
While I haven't empirically tested enough, I think the voice search might be resetting every time that Swiftkey gets updated (like with new language files, since that seems to happen quite often).
I'll try to keep track to see if there's a link there.
quasihellfish said:
I have the same issue, and I'm also using Swiftkey X. I'm sensing a pattern...
While I haven't empirically tested enough, I think the voice search might be resetting every time that Swiftkey gets updated (like with new language files, since that seems to happen quite often).
I'll try to keep track to see if there's a link there.
Click to expand...
Click to collapse
I'm not using SwiftKey, but I do use the ICS keyboard, so I tried uninstalling it and freezing Swype for good measure. It didn't seem to affect things, at least on my end.
I'm having the same problem. I installed the swiftkey x keyboard to give it a try but uninstalled it when I didn't like it. Have had the problems even since the uninstall. Currently using the stock keyboard with stock rom rooted.
Sent from my MB865 using XDA App
Just did a complete wipe and installed the latest Emancipation release this morning.
When my text messages are a certain length, the sms message fails to send.
When I try to download dialers or themes using the OTA, the downloads are unsuccessful.
Did the lock screen option menu get moved somewhere else from the first release because I dont see it.
Im just wondering if I need to add another APN?
Thanks for the input!
eezeekial said:
Just did a complete wipe and installed the latest Emancipation release this morning.
When my text messages are a certain length, the sms message fails to send.
When I try to download dialers or themes using the OTA, the downloads are unsuccessful.
Did the lock screen option menu get moved somewhere else from the first release because I dont see it.
Im just wondering if I need to add another APN?
Thanks for the input!
Click to expand...
Click to collapse
hmmm... i've been cruising the Eman thread all day and no one else seems to have these issues. My first guess would be possible bad download and/or flash. Did u try to flash again?
eezeekial said:
Just did a complete wipe and installed the latest Emancipation release this morning.
When my text messages are a certain length, the sms message fails to send.
When I try to download dialers or themes using the OTA, the downloads are unsuccessful.
Did the lock screen option menu get moved somewhere else from the first release because I dont see it.
Im just wondering if I need to add another APN?
Thanks for the input!
Click to expand...
Click to collapse
What length SMS seems to cause an issue? I have not seen any issues with SMS so far, but granted my messages are generally pretty short anyway.
When you try and download the dialers or themes are you using the stock browser? I think there is a known issue with that. Nun had said "Q. I try to download from the ota and I always get "download unsucessful. How do I fix this?
A. Many have stated that trying a browser other than stock will help...Opera, Dolphin, etc should work. If you prefer to use stock...try this: Download Astro File Explorer, open preferences, and scroll to the bottom and select "enable browser downloads"...then ownload like a good boy should!"
I followed his suggestion and had no more troubles trying to download the OTA stuff.
Lock screen stuff is in display settings. Don't remember where it was on the previous build.
Thank you for the info, you pretty much answered all my questions. I had a brain fart on the lock screen- it was under display. I thought it was in the Emancipation OTA previously.
As far as the text messaging, I cant put a finger on the length because sometimes it works... Not sure whats up with that. But I do know that usually long texts do fail and they will go through if i try to resend them a few times...
What browser do you recommend? Is there an agreed upon one that everyone uses?
when I download i use dolphin mini browser...-
i like opera but it doesnt let me download...
about your sms, you check the messages/setting /message center... sometimes its reset when changing roms..
I just use the stock browser. I loaded the Astro File Explorer and everything worked fine.
I know there are better browsers out there but the audio book service I use only works the stock browser and Firefox. I have tried it with Firefox, but it just works better with the stock browser. My commute is about 80 minutes each way; so I would go crazy without my audio books.
I have always used the app "Download All Files" its a super light app that works with all files in any app or browser and then I can just use the stock browser
Sent from my Emancipated Infuse w/ Eternis Veris
I'm having a problem sending and recieving MMS, which I had once before ever flashing my infuse. APN settings got changed somehow (probably me). Reset the APN and it was fixed. Problem crept again after flashing Emancipation. Under the available APN types the list I'm given only has:
Internet+MMS
Internet
MMS
I think I'm needing an "supl" option. Am I missing that due to a bad flash and need to redo it. Or is it simply not available o Emanc and need to try a ROM i can edit the APN by typing like CM7?
Thanks
ntorresla said:
when I download i use dolphin mini browser...-
i like opera but it doesnt let me download...
about your sms, you check the messages/setting /message center... sometimes its reset when changing roms..
Click to expand...
Click to collapse
What is suppose to be in the message center?
BigAtrain said:
What is suppose to be in the message center?
Click to expand...
Click to collapse
I believe the number in your Message Center should be:
+13123149810
Its official, both my Infuse and my wifes cannot send long text messages. We have to cut them in half for whatever reason. Any ideas?
Also my data is ridiculously slow. Youtube videos are taking upwards of an hour to load on both phones too. This wasnt a problem on Zeus and I was wondering if there are something I should look into? Thanks!
I have the same issue also can't send/receive pics to my ended phone started when I flashed this ROM. Worked great in last.
Sent from my SAMSUNG-SGH-I997 using xda premium
Whats the issue? I sends texts and pics NP.
Sent from an Emancipated Infuse bleeding Orange
I can't seem to send long texts or send or receive pix with my wife. she's the only person I send pix to. And she never gets them. And when I get one from her I can see the message info but never get the picture.
Sent from my SAMSUNG-SGH-I997 using xda premium
eezeekial said:
Its official, both my Infuse and my wifes cannot send long text messages. We have to cut them in half for whatever reason. Any ideas?
Also my data is ridiculously slow. Youtube videos are taking upwards of an hour to load on both phones too. This wasnt a problem on Zeus and I was wondering if there are something I should look into? Thanks!
Click to expand...
Click to collapse
What modem are you using? I had a similar issue running another ROM. I flashed UCLB3 and it resolved the issue.
http://forum.xda-developers.com/showthread.php?t=1342978
Emancipation OTA Problem
Firstly I'd like to thank everyone for the awesome community and work that goes on here at XDA. I've been reading through all the forums the last several weeks and learned so much about my new phone (Samsung Infuse 4G). Through all the tutorials, Q&As etc. I have successfully flashed my firmware three different times. Started out with Zeus v6, Aeon and now I'm finally settled on Emancipation1 with the Dark Blue theme. I really like this ROM.
Now my problem/question. For the ROM flash and Dark Blue theme flash I just downloaded the files to my PC and moved them over to the phone. Everything at that point was fine. Everything on my phone works great except for the Emancipation OTA. It worked the first time immediately after the flash (just checking it out), however now whenever I try to use the Emanicaption OTA I get an error on my phone screen that says "Sorry - The application Settings (process.com.android.settings) has stopped unexpectedly. Please try again. - Force close)
I've tried with wi-fi enabled and disabled. My stock browser works fine and I went ahead and installed Astro File Manager Explorer. I also booted the phone into Recovery Mode and wiped the cache and Davlik cache.
Any ideas on what might be wrong or causing my inability to use the Emancipation OTA? Any suggestions would be greatly appreciated.
Thank you.
wevsspot said:
Firstly I'd like to thank everyone for the awesome community and work that goes on here at XDA. I've been reading through all the forums the last several weeks and learned so much about my new phone (Samsung Infuse 4G). Through all the tutorials, Q&As etc. I have successfully flashed my firmware three different times. Started out with Zeus v6, Aeon and now I'm finally settled on Emancipation1 with the Dark Blue theme. I really like this ROM.
Now my problem/question. For the ROM flash and Dark Blue theme flash I just downloaded the files to my PC and moved them over to the phone. Everything at that point was fine. Everything on my phone works great except for the Emancipation OTA. It worked the first time immediately after the flash (just checking it out), however now whenever I try to use the Emanicaption OTA I get an error on my phone screen that says "Sorry - The application Settings (process.com.android.settings) has stopped unexpectedly. Please try again. - Force close)
I've tried with wi-fi enabled and disabled. My stock browser works fine and I went ahead and installed Astro File Manager Explorer. I also booted the phone into Recovery Mode and wiped the cache and Davlik cache.
Any ideas on what might be wrong or causing my inability to use the Emancipation OTA? Any suggestions would be greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Sorry, the only known solutions when that consistently pops up is a reflash. Something did not take right or is interferring with that working properly. Back it up and reflash.
Thanks. Was hoping you weren't going to say that though
One more simple ?
Does anyone know if the themes and other content available through the EmancipationOTA is available for direct download (say from the server to a PC so it can then be moved to the phone the old fashioned way?)
Nope. All themes go though the OTA.
I'd been running rooted (Revolutionary) with the Verizon/HTC stock ROM (605.9) for awhile and fairly happy. Then I received the OTA push attempt about 2 weeks ago for 605.19... so I opted to defer the push for 2 weeks (June 1) so I could do some research and decide what best to do.
That's when the following problems began... I noticed right after the OTA request... that anytime I restart or reboot the Tbolt many of my core app defaults now go away:
GO Launcher... requires to re selected
Power widget... will not reload (but GO Calender widget is fine?)
Facebook... contacts sync have to be reset (but Google syncs are fine?)
Swype keyboard... must be re selected
Even though I could/can manually fix these disconnects, I decided to take the opportunity to try some other ROMS to see if that would correct the problem. Long story short... I have basically tried 4 different ROMS including 2 different stock ROM (650.19) variants. I am now currently running iKReaM.605.19.NOSeNSe.ROM.v1.0.RLS-R3Ds
which is a nice running ROM.
BBUTTT... with every clean and wipe and reflash, the above "default" disconnects occur? I have tried to search several sites for anyone experiencing similar problems with no success... I know this can't be a ROM issue because it occurs no matter what ROM I use.
Misc info: Several ($paid$) rooted apps that I use are... TiBackup, ADfree, Root Explorer, Superuser (DDChain), No Frills CPU, ROM Mgr... all of which seem to be working together just fine.
Thanks for reading and any thoughts would be appreciated.
I'm beginning to narrow this down to self-affliction... perhaps via something I've done in ROM manager and I keep restoring the problem (???). I deleted all backup data and have reflashed iKReam. One by one I'm adding apps back and have had no app "default" disconnects as of yet. Also I'm not going to reload GO launcher... since the default iKReam launcher (LauncherPro +) is working/reloading just fine and I don't want to chance it.
App Defaults
Sometimes weird things happen like this for the oddest of reasons.
Try running fix permissions in ROM manager.
If it doesn't work...
Did you also clear the dalvik cache when you flashed over to your new ROM?
Did you restore data only from your pervious ROM onto your new one?
Always make a backup before doing anything different, just in case.
If none of this works, I really don't know what to tell you man.
Hopefully this will bump your thread and someone will be able to help you out a little bit more.
So, I'm running the latest CM10 nightlies on my One X.. otherwise everything else is normal I think.
My problem is that I can't send MMS messages. When I try and send a picture, it just says sending and never sends. I'm not sure if I can recieve, I haven't had the chance to ask someone to send me something. Anyway, I haven't done any heavy modding to my phone besides trying out the new camera app from 4.2. Since I couldn't view my photospheres, I flashed my rom again to get rid of the new gallery/camera apps. And some time after that, I noticed the mms problem..
I tried editing the build.prop in /system when the 4.2 camera came out, but if I'm not correct, doesn't it get overwritten when I flash again? It seems like the build.prop is back to normal.. The only thing I changed was the model name and brand to galaxy nexus/google but it changed back when I flashed.
Anybody having any MMS problems? Or does anyone know of a possible fix? I've tried earlier nightlies, but to no avail.. This sucks
APN
itsjaylin said:
So, I'm running the latest CM10 nightlies on my One X.. otherwise everything else is normal I think.
My problem is that I can't send MMS messages. When I try and send a picture, it just says sending and never sends. I'm not sure if I can recieve, I haven't had the chance to ask someone to send me something. Anyway, I haven't done any heavy modding to my phone besides trying out the new camera app from 4.2. Since I couldn't view my photospheres, I flashed my rom again to get rid of the new gallery/camera apps. And some time after that, I noticed the mms problem..
I tried editing the build.prop in /system when the 4.2 camera came out, but if I'm not correct, doesn't it get overwritten when I flash again? It seems like the build.prop is back to normal.. The only thing I changed was the model name and brand to galaxy nexus/google but it changed back when I flashed.
Anybody having any MMS problems? Or does anyone know of a possible fix? I've tried earlier nightlies, but to no avail.. This sucks
Click to expand...
Click to collapse
are you sure you have the right APN for your telco? some have some funny settings for MMS. There are a few lists kicking around for all the major telco's, you might want to check the settings you have against those. These can be entered via
settings -> [wireless & networks] -> more -> mobile networks -> Access Point Names -> [there should be at least one configured here for mms]
Yup, incorrect APN settings is the most common reason for MMS failing.
The notification badge on my stock Messaging app icon is incorrectly showing 1 unread message.
I have a totally stock Droid RAZR MAXX HD running 4.4.2. My stock messaging app is version 4.4.2-10. SMS is set to "Messaging" (not "Hangouts"). All settings are default. Verizon Wireless is my service provider.
From my own troubleshooting, I have concluded that the problem is probably KitKat-related since stopping, disabling, and clearing (data, cache, and defaults) the stock messaging app has no effect. Also, this problem started after my OTA upgrade to KitKat (never had it before). Further, after completely disabling the stock messaging app, I alternatively installed GO SMS Pro, chomp SMS, and Verizon Messages and experienced the exact same problem with each.
Any ideas about how to fix this problem, without FDR'ing or rooting the phone, would be greatly appreciated.
clear dalvik?
you try clearing dalvik cache?
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
PW_Irvine said:
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
Click to expand...
Click to collapse
i never have stock recovery on, so i could be wrong, but i dont think you can do that in stock recovery.
which means you would have to put on a custom one and root, which i think you said you didnt want to do.
it is somewhat common to have random issues like this on a major software upgrade, especially one that jumped so many other builds.
i know you really dont want to do it, but clearing the corrupted data is really the best course of action, and it may be the only one honestly.
and if you are going to go that far, it is really best to just re-flash the phone encase something in the system is corrupt. just no point in going 1/2 way just to find out you still have the issue later.
sorry thats not the answer you were looking for, but sometimes it is not avoidable.
bweN diorD said:
i never have stock recovery on, so i could be wrong, but i dont think you can do that in stock recovery.
which means you would have to put on a custom one and root, which i think you said you didnt want to do.
it is somewhat common to have random issues like this on a major software upgrade, especially one that jumped so many other builds.
i know you really dont want to do it, but clearing the corrupted data is really the best course of action, and it may be the only one honestly.
and if you are going to go that far, it is really best to just re-flash the phone encase something in the system is corrupt. just no point in going 1/2 way just to find out you still have the issue later.
sorry thats not the answer you were looking for, but sometimes it is not avoidable.
Click to expand...
Click to collapse
Have the same problem - I find that if I delete a recent MMS message sent from me, then it goes back to normal.
PW_Irvine said:
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
Click to expand...
Click to collapse
baldbob said:
Have the same problem - I find that if I delete a recent MMS message sent from me, then it goes back to normal.
Click to expand...
Click to collapse
nice suggestion :good: i have never heard of that.
thanks
yeah dont think its possible on a phone that isnt rooted or has a custom recovery, whats the reason you dont want to to root?
Unfortunately, deleting all SMS and MMS messages did not solve the problem either, so I just FDR'ed the phone. Problem is gone on reboot of course, but so is 13 months worth of app configuration. I would root the phone this time except that the screen is also acting up on me and the phone still has 4 months left on the Costco warranty that I got (for free) with the phone. Wouldn't it be great if Android "L" allowed you to back up app settings along with apps without the need to root the phone first! Thx to all.
PW_Irvine said:
Unfortunately, deleting all SMS and MMS messages did not solve the problem either, so I just FDR'ed the phone. Problem is gone on reboot of course, but so is 13 months worth of app configuration. I would root the phone this time except that the screen is also acting up on me and the phone still has 4 months left on the Costco warranty that I got (for free) with the phone. Wouldn't it be great if Android "L" allowed you to back up app settings along with apps without the need to root the phone first! Thx to all.
Click to expand...
Click to collapse
Follow-up: same problem occurred following FDR. It is related to MMS messaging and it is solved by removing all MMS messages from phone. I did not have this problem with JB. It showed up after OTA upgrade to KK. Too bad for those who like to keep their MMS messages.