Hi, kinda new to root and all that goes with it, but I flashed first CM10 stable, and then a few days later AOKP MS2, both on my Nexus 4. I did a full cache wipe before flashing each one. Either way, both were not able to fully receive MMS. In the notification pane up top I'd get a notification I got a text but it'd show blank on the drag down and when in the messaging app nothing shows up. On the other end of multiple phones it'd show it was sent successfully. After flashing back to stock rom 4.3 everything came through a few hours later as well as the MMS I had sent to people. Any idea on what to do to keep CM/AOKP and have MMS? Thanks in advance for any help!
Related
Hi,
i'm posting here cause i've less then 10 messages in the forum, is this the right place?
A couple of days ago i flashed the FroYo AOSP for Tattoo v0.333 by fyodor, and everything works fine except the sms sending.
Did a full wipe/factory reset, wiped cache and formatted system partition before flashing (0.33, then just updated to 0.333).
I've never been able to send an sms since the first day, it keeps saying "Sending..." but never sends it (receving is ok).
I tried to update the SMSC with the *#*#INFO#*#* thing, and googled a lot without success (apparently the problem happened to lots of people with froyo, google forums).
Handcent works fine, but i really don't want another app to send sms, i would prefer using the stock one.
Anyone also had this problem? Any idea about how to solve or debug the issue?
Also, just curiosity, does flashing another Froyo ROM require full wipe? I tried ginger, it's amazing but in my opinion "too heavy" for tattoo.
Thank you all in advance.
up.
any idea? anyone?
thank you.
Hi all. I flashed my stock 2.2 Milestone 2 to the MS2Ginger 3.0 about a month ago. Everything was working just fine. But after one to two weeks of use, some minor bugs started to trouble me. I am a Chinese user and I used Moto Smart HandWriting for Chinese input. Everytime i tap on a message box or anywhere else to input text, the screen goes blank. The machine is still responsive and I am still able to go back by pressing the back button. The only way i can input text now is to use other IMEs.
Another thing is that my physical keyboard started to get double bouncing which was initially alright after flashing the rom.
I figured that it is something related to the data/cache or something else because the phone was okay just after flashing the rom. So i booted into bootmenu and do the double wipe to clear all the setting on the phone. But when i rebooted into the system, everything was still there. Lock screen password, messages, account settings,etc. All of it was still there.
I then tried to flash the MS2Ginger again following walter's post in android development forum. Again, nothing was resetted.
I am very annoyed. Can anyone provide some advice? Thank you.
hi, i think this should fix your physical keyboard problem... worked for me
http://forum.xda-developers.com/showthread.php?t=1058544
Hello all and I hope you all had a fab Christmas!
Yesterday for the first time my Nexus4 told me that my ROM is no longer cool. It also told me there is a new ROM in town, better and slicker. I decided to try it out. Custom ROM downloaded the new ROM for me and then I wiped out my PA 3.99. Did a cache wipe and a factory reset. Installed the new ROM which was downloaded into the PARANOIDOTA folder. Now comes the funny part. I got two messages one that there is a problem with google play and another that there is a problem with services or something like that. All this messages preventing me to use the phone while I could clearly see the massive soft keys in the background. Clicking ok on these messages wouldn't do anything as they will switch from one to the other. I rebooted and cleared again and reinstalled again with the same result. Can anyone share some light why it didn't work?
I mention that I used CMR v6.0.4.3
Thanks!
I think you needed to flash KitKat gapps after flashing the new rom
Sent from my Nexus 4 using Tapatalk
After upgrading to the Note 4 back in March, I recently decided to dabble in the rooting and custom ROM world of Android back in late June - early July.
I've been using CM12.1 nightlies since July 19th and currently have the August 20th nightly. One problem I had is that if I tried to update CM via the CM updater under the "About Phone" section, I end up getting "No Service" for my mobile signal/data which meant reflashing the stock firmware and reflashing TWRP/Cyanogenmod. So if I wanted to update nightlies (no plans to until Android M), I would have to manually get the nightly zip files from my laptop then wipe my previous nightly clean so the mobile signal would still work.
But the biggest problem I (still) have now is that I simply can't send text messages ranging from 10 minutes to several hours (Would just be stuck at "Sending..." and eventually "Not sent. Touch to try again") only after I turn off/restart my phone or turn on airplane mode. It shows that I still have connection to Sprint and I can actually use LTE/3g. Also interestingly enough, I can still call people AND receive their text messages, but I just can't send text messages.
It's not a big enough deal breaker for me where I would have to go back to stock ROM, but I'd like to know why this is the case. Since sending text messages seems to be the only problem, I assume it can't be the mobile signal itself since I'm still able to call, receive text messages, and use LTE/3g.
Things I've done/tried so far with no solutions:
1. Read older OPO/XDA threads about something called Voice+ causing the issue, but no such application exists on my CM.
2. Flashing the 5.1.1 firmware from Sammobile since CM12.1 is based off 5.1.1 Lollipop since I originally rooted and flashed CM12.1 with the 5.0.2 firmware. Problem still persists even on the 5.1.1 firmware
One final thing I will probably try to do is do an advanced wipe via TWRP, flash the stock 5.1.1 firmware and then get TWRP back via Odin and flash one nightly zip only and never attempt to update or flash new nightlies until Android M.
As for now, once I get my ability to text again, I'm not going to turn on airplane mode or turn off/restart my phone and leave it be. I have a fair enough standby time with CM (One night I only had a 2% drain in 7 hours of sleep or so without CM's battery saver mode) which is nice.
Any input would be greatly appreciated!
UPDATE: Apparently location seems to be the problem. I am now realizing that this issue only really occurred when I'm at my house. Even though I live in the city, it seems to prevent me from texting. But, I can text with no problems after turning airplane mode on and off or turning the phone off and on again at work and at certain stores I go to.
Sent from my SM-N910P using Tapatalk
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
SashaNT86 said:
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
Click to expand...
Click to collapse
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
If that fails try returning to stock to see if the problem persists. Occationally mms dysfunction can be upstream and require carrier involvement.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
A dirty flash seems to have done the trick,though I will say I used a different download for the flash. Loving it so far.
Thank you for the help!
Davey216, I will keep that in mind if it comes back. Stock is kinda icky but I need my mms. Thank you for the reply!