yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] p-y-r-o:
Well after some searching I found 8sms, installed it, disabled stock messaging and I had MMS working with Go Sms Pro. Then for some reason I kept getting an error message saying that I had an invalid recipient, even when sending to myself.:mad: I couldn't figure out how to fix this through Go Sms Pro so I uninstalled it.

8sms is working just fine to send and receive MMS now tho so I'm gonna leave well enough alone and hope 8sms continues to work. :good:

p.s. I am on verizon and searching for the APN settings was a bit of a run around as all the forums I came across were saying to set MMSC to "http://mms.vtext.com/servlets/mms" but mine was already set to that and I couldn't find any saying what ports to set etc. :confused:
[Motorola Droid RAZR] Ohmster:
Wow, you are lucky dude! For one, you got the issue solved for yourself. For two, it is exactly midnight and I just got my Thanks cookies renewed so for this helpful post, I can give you one. :laugh:

You are exactly right, "Leave well enough alone" or, "If it ain't broke, don't fix it". LOL! Nice work Pyro! :highfive:

I want to tag this post with search terms since I cannot tag your post. SMS FIX, MMS FIX, TEXT FIX. APN FIX
[Motorola Droid RAZR] Dwillian:
I'm having the same experience with 11/11 nightly of CM11. I did use the CM Update option under settings to update my phone (so, it was a "dirty" update) . I'm going to try a completely clean install in slot 2 to see if that works any better. If not, I think I need to revert to something earlier. Perhaps 10/07, 10/10, or?
[Motorola Droid RAZR] Ohmster:
Wow, I am surprised. I really "got ready for this awful build" with a fresh backup of a supreme build of 11/07. I did do an OTA update, did AdAway and Xposed Framework install, as usual, and rebooted. No issues. Then another reboot to test it out and the phone did self-reboot at the lock screen. Other than that, no problems, ...yet. The overnight next day is usually the acid test. Haven't gotten that far yet. Only thing I can think of is that the build of 07 underneath it was really running great, OR, I have not had it running overnight or for a few days yet. How long did it take to crash out on you, [MENTION=5362796]Dwillian[/MENTION]? :confused:

BTW: 11/07 is a great build. I had that baby tuned up to the max, ran so great I was afraid to try anything else. So if you need somewhere stable to start, I would say 11/07 is it. Do a "Dwillian Dump" to downgrade. I use it all the time for downgrading now that I know about it and that procedure really works great, dude. :)
[Motorola Droid RAZR] Dwillian:
It crashed immediately on first boot. Some process, com.android.phone (I think), FC and I had to hit OK numerous times before I could finally tell the phone to power down. It didn't actually power down though. It rebooted, so I had to select recovery during the reboot, select reboot from SafeStrap, then select Power Down to get it to actually power down, then disconnect charging cable before it tried to reboot again.

I just completed a clean install into a newly created rom slot 2. It's booting now.

I am wondering if there is any problem doing an OTA update with Greenify installed as a system app? Should I have uninstalled Greenify as a system app before taking the OTA?

Update: The phone seemed stuck on the revolving CM splash screen and it didn't look like it was ever going to finish rebooting. I finally forced it to powerdown and I'm now restoring my 11/10 backup and will then revert to 11/07 using the "Dwillian Dump" process. Thanks for the accolade btw, but I really can't take credit for the idea. The Paranoid Android GApps instructions for changing types of GApps (e.g., from Stock to Full, or from Full to Micro) recommends a similar procedure. I just adapted the process for doing a cleaner install of a new ROM.
[Motorola Droid RAZR] Ohmster:
Yeah, that is pretty much what [MENTION=3687628]morr22066[/MENTION] said in his post: 11-11-14 Nightly Build 'beware' Post #6626

It came up and crashed right away. One way to force a power down on an Android device that always works is to hold the Power button in and at the same time, hold Volume Down, and wait. It takes about 5 seconds, the screen flickers and it is OFF! I use that when I get a "stuck build". Press Power momentarily to turn it back on again and see the Safe Strap screen.

Greenify as a system app? I don't think that is recommended so I checked in Titanium Backup and no, it is not a system app. I did purchase the Donation Pack and that gives me the Xposed Module for it which allows putting system apps and services to sleep. But no, I never installed it as a system app nor is it recommended. I cannot say it caused the crash though. Don't know, maybe. Just don't make it a system app and if you got the 3 bucks one day, instead of two 6 packs of beer, get one and the Greenify Donation pack. It is worth it and you do not need to make it a system app at all. :)

I only got one self-reboot so far, so not sure why it is crashing but I am sure it has some rough spots in it. Only thing I can think of is that 11/07 was running so well that the OTA over it did not cause any issues. But having a system run good is not all in the system partition which gets wiped and fresh at every build update anyway. The details are in the Data partition and this is where your apps and settings lie. You have to make the phone run good by managing your apps and services in the rom while working, so the apps and settings are saved in the data partition. Just wiping /system does not clean this up. :(

This is the part I am learning now, how to keep cm11 running well and for me, Greenify donation pack is like, "mandatory" but if one cannot buy it right now, the free version does work well, just don't make it a system app. The donation pack has nice features like the Xposed module which gives it the ability to Greenify system apps. That permission does not come from a system app, but an Xposed Module. You get some other nice things too like choice of root or boost mode. And you can make all the text, email, and other apps wake at the same time to check their stuff in one group instead of constantly waking the phone for these tasks. I get great battery and wakelock stats because of it. Attached are my Wakelock Detector and BetterBatteryStats screens. They are about as good as it gets. If you can pull stats like this, you should not have these problems, Dwillian. :good:

Don't get the wrong idea. I am no expert on this stuff. But I am learning and so far, it looks really good. :)
[Motorola Droid RAZR] Dwillian:
I think I misspoke about making Greenify a system app. Now that my phone has been reverted to 11/10 nightly it reboots and I now realize it was BetterBatteryStats that had the option of making it a system app. Not sure if that is a good idea, required, or what. I don't think it was the problem with the 11/11 nightly though. The clean install of 11/11 failed on my phone (i.e., before I ever had the chance to reinstall Greenify or BetterBatteryStats).
[Motorola Droid RAZR] Ohmster:
Hmmm. Well, BetterBatteryStats does require it to be a system app. You will get a warning when you open it if you have not made it a system app and it does contain a one button installer to "make it so". I do use this "feature" or mandatory button and not only does it not affect the phone, it is the only way that BetterBatteryStats can work properly.

Personally, I think that 11/09, 11/10, and 11/11 ALL have issues. I had issues with 09 and 10, but I also had issues with my 11/07 system, it was when I got the Superuser issue fixed that the phone really became "nice". Before when I tried 09, it crashed on boot. No good, reverted back to 07 backup. Next I tried the 10 build and it seemed ok, but the app counter when it first starts and says "127/200" Apps Updated" was dead wrong. It showed I had less than 100 apps installed. And the same thing happened in 09. Build 11/10 seemed to run okay, despite the app count error, but by the third day, the lag was SO bad I gave up and restored 07 again. Normally, good builds do not degrade like that over days when I am not changing the system.

So if 09 and 10 were bad, how did I escape the ax on 11/11? Well, I have like 5 different backups for 11/07, each one a little better than the one before it. I finally deleted the first set of backups on the 10 build because they were inferior and I don't need them. My last 11/07 backup was GREAT. Nothing more I could do with it and I loved it.

Since a fresh install is good, have not had time to junk it up yet, it is not "Pristine", either. Because you did not Greenify, Uninstall, and Freeze the junk you don't want/need. I bet NIGHTLY Builds 11/09, 11/10, and 11/11 would all fail on a fresh install. I really don't think they are good builds and there were too many complaints about them to ignore.

...but I have no proof. This is only speculation at this point. Speculation based upon observation and actual hands on cleaning of my device system. So am I right? Who knows. Do I believe this speculation to be accurate? Yes, until I can get something to make me believe otherwise.

I think that NIGHTLY Build 11/07 is really good. Easy to work on, clean up, and Greenify and the results were quite good.

BTW [MENTION=5362796]Dwillian[/MENTION] did you check my stats screenies? I know you cannot compare right now as you have already torn down your system. But when you did look at the battery stats, were you at, near, or above 80% Deep Sleep?
[Motorola Droid RAZR] morr22066:
I initially did it as an ota but when that went bad I tried a clean install and also started to have problem s so I just restored my last back up. I don't remember issues with 11-7 , but with the omap 4 changes and the telephony / sms & mms changes something didn't go well. Like Ohmster says, large change logs are often a recipe for trouble.

Since I had to wipe and restore CM11 in slot 1, and PAC in slot 2, I have been restoring and updating several of the other ROM's that I had backed up. The new 'unofficial' aokp ROM has been running really well for me today in slot 2. But I always like to keep a good version of CM11 in slot 1.
[Motorola Droid RAZR] Ohmster:
Top 4 Apps on XDA

Check this out, man. This is the "Top 4 List" of apps for the XDA Community. I am really surprised that Titanium Backup is not on this list, but not at the #1 app, Greenify. That is one app recommended by ALL the top phone maintainers I have spoken to. And betterBatteryStats is on the list, too. Also very useful for getting that phone to run right, sleep well, and have a good battery life. SuperSU is no surprise either. It is the best superuser app there is. I took mine out just to remain consistent across the cm11 line and retain the built in Superuser on the menu.

If the majority of members at XDA believe that Greenify is the #1 app for Android devices, then I believe it. :D

[IMG="Top 4 Apps at XDA Developers"]http://home.comcast.net/~theohmster/razr-img/Top4AppsXDA.jpg[/IMG]​
[Motorola Droid RAZR] ChungHung.Chen:
XT910 (umts_spyder) / PA-Gapps Micro 20141110 / 141108->141111 by CyanDelta

Updated about 6 hours ago, no self-reboot and FC so far. Will try video play to HDMI output if have time. One suggestion about nightly test report, perhaps we should include some "basic" info in our reports. May help to verify if problem is model related?
[Motorola Droid RAZR] Ohmster:
Hello Mr. Chen,

You want model information included in the build reports? Sure, I think it's a good idea. One thing that makes troubleshooting difficult is lack of details, as in XT910 or XT912. However, both of us have our phone models in our signatures to help avoid that issue. But not everyone does that. Your model in sig is quite clear, since I spend more time here and have almost zero Samsung issues, I could move my Droid model number to top of signature. Okay that is done.

You are right, we need model numbers because issues could be quite different for the two model phones we use. A signature with model is always preferable. Any other standard you can think of? I list method (OTA, clean, or manual) and mention any anomalies I encounter during the install, AND follow up in 24 hours because after a night on charge and the next day is when I see lag and other problems. Other than that, it is really hard to run a mult-ipoint check list like I did when I worked in the Crest amplifier factory. Too many things to test and if something is wrong, the build tester will let us know. I don't want to make it so hard that people just don't bother with it. What do you think, Mr. Chen? :)

Build 11/11 is going dark during phone calls and is difficult to wake up. I think this build may have some "rough edges" for phones that are not really running well. Too many complaints to dismiss on this build. I cannot tolerate black screen phone calls because I cannot hang up. Reverting back to backup of 11/07.
[Motorola Droid RAZR] morr22066:
M12 Snapshot build

It looks like there are a lot of fixes in the next nightly, but for now I am going to try the M12 build. Ohmster, I believe that you had previously said the snapshot builds usually finalize the code several days before release, is that correct?
[Motorola Droid RAZR] Ohmster:
Finalize, you mean like stop coding and get ready for snapshot? I would think so. But SNAPSHOT builds are not anything special. What you get is a typical NIGHTLY build that is set aside and called a snapshot. And CyanogenMod will take official bug reports on these builds only. But they are not better than the NIGHTLIES. Just another nightly that gets "old", really fast. Any issues you have in the snapshot will not be fixed. And while the snapshot gets old, the users with nightly builds get improvements, bugs, new features, etc. That's why we promote Build Reports. Everyone likes them, it gives troubled members a decent build to setup with, and it gives regular members an idea of what NIGHTLY Builds to skip and which ones to update with.

SNAPSHOT Builds are not semi-stable builds that you can install and forget about.

So to me, a SNAPSHOT build is like any other nightly. Usually I skip them and just install good NIGHTLY builds. HTH :)
[Motorola Droid RAZR] Bobcus Leper:
This may be the last Snapshot Build. Look real closely at the build number in this video. It actually says CM BLABLABAL test keys. So, this is probably an early CM12 source built ROM.

CyanogenMod 12 Android 5.0 Lollipop ROM on Samsun…: http://youtu.be/f1GxGb8JPJc
[Motorola Droid RAZR] mihovil13:
Do I need GSM patch for this ROM? BTW how's the battery on stock?

I need something for my mom, a simple, stable ROM without many functions, and since there isn't any stock 4.4.4 I'm considering flashing this since LiquidSmooth didn't really meet my expectations.

Should I flash snapshot/nightly or what?
[Motorola Droid RAZR] Vallerino WR:
m12

snapshoot m12 are out :D:)
[Motorola Droid RAZR] Ohmster:
[MENTION=4074222]mihovil13[/MENTION] You are a Recognized Contributor with over 1.000 posts. Your signature indicates that you have Nexus devices and you are in the Droid Razr thread asking about roms. We need a little information here like what model phone do you have and your location if you have an XT912 phone and need GSM. If you do have an XT912 and live outside the US where GSM is required, then I would say yes, you "might" ned the GSM patch. The NIGHTLY builds are what most all of us in here use. We test them and give Build Reports to weed out bad builds. Last confirmed very good build was the 11/07 NIGHTLY Build. The new M12 SNAPSHOT Build is out but as of yet is untested by us because it was just released.

If you want to use the snapshot, try it out, it should be useable. If you want a confirmed good build, then I would say it is the 11/07 build as of now. If you need GSM on an XT912, then you

*might need* the GSM patch

. I say "Might Need" because

GSM is listed in the XT912 Mobile Network Settings

so try it by flashing the cm11 rom and pa-gapps ONLY first. If you have issues with GSM after that, THEN go back to recovery and flash the GSM patch.

And be a good member, thank the people who help you and let us know if you did or did not need the GSM patch for which model phone in what location. Thnx. :)
[Motorola Droid RAZR] mihovil13:
Hey, outbound SMS doesnt work for me on Verizons XT912

I'm running M12, tried the GSM patch and without it aswell.

Google Voice isnt available in Croatia, and even after I installed that apk and set Voice+ to disabled account I still can't send messages.

I can recieve them though. Anyone else with this prob?

Maybe I should flash a different radio, is there any for XT912?

Edit - sry didnt see QA thread, I'll move my post there
[Motorola Droid RAZR] Ohmster:
A few members are having issues with text messaging and the only thing that seems to work is a third party SMS/MMS App. [MENTION=2148113]p-y-r-o[/MENTION] got his SMS/MMS working with the 8sms (Enhanced Stock Messaging, KitKat) App.

It is interesting to note that almost all of these SMS/MMS issues are due to APN issues. We have worked on this issue for well over 6 months. We have tried editing the APN list, importing better APN lists from other builds, and Brian went so far as to create a flashible zip file to perform this APN update. Nothing seems to be a permanent fix for it. Not all users are affected, only a select few are really troubled with this issue. The 8sms App has a neat way around this issue by using the Internet data connection to send "free" text SMS/MMS messages that works quite well and puts an end to this problem. If you read the news on the 8sms Homepage, you will see that the developer of this app hates advertising and constantly works on bug fixes and to make this the best SMS message system there is. I would like to use it myself but have good luck with Go SMS Pro, free edition. p-y-r-o found Go SMS Pro stopped working after sending 2 pictures but is pleased with his 8sms App. :)

Hope this helps. :good:
[Motorola Droid RAZR] p-y-r-o:
Go SMS Pro was weird for me. It would send MMS after I force closed it with titanium then opened it back up. I send far too many MMS for that.

So far I haven't had any issues with 8sms. It's been working just fine :good:
[Motorola Droid RAZR] Ohmster:
Build Report 11/11 FINAL

Finished testing cm11 NIGHTLY rom Build 11/11/2014 on an XT912 Droid Razr Maxx, LTE/CDMA over Verizon US

OTA Update, pa-gapps Mini-Modular

NIGHTLY Build 11/11 - BAD ROM

Initial install as and OTA update over a "very good" nightly build 11/07 seemed to go well. The only immediate issue apparent was the rom did self-reboot when rebooting at lock screen. Nothing else seemed wrong at the time and anything I tested worked well.

Next day after full night on charger and using phone to make a call, screen went dark while away from my face. Pressed Power and got hard buttons list but not the screen. Repeated pressing of the Power button got the screen lit at the lock screen. Swiping lock screen finally got me back to the phone call. I did not have this issue immediately after installing the rom. This "back screen, won't light" issue I have had before on bad builds and it gets worse. Screen will never light up fast enough to receive an incoming call, nor light up to hangup a call in progress.

"Hard Power down"

by holding Power and Volume Down for 5 seconds to shut off device is only way to regain control of the device. Although the 11/11 rom was not "that bad", performance was degrading and black screen was becoming prominent.

There are too many complaints on the 11/11 NIGHTLY to dismiss.

The previous NIGHTLY Builds, 09 and 10 were not good roms. I have reverted to my stable 11/07 backup.

I will skip the M12 SNAPSHOT because it would have to come from a previous nightly build such as 11/11, 11/10, or even 11/09, ALL of which are poor. This is my report and experience installing and testing the cm-11-20141111-NIGHTLY-spyder.zip update file, your mileage and experience may vary. :)
[Motorola Droid RAZR] farangcm:
Anybody know the nightly cutoff date for M12 Snapshot? This would be the last nightly before the M12 branched off, and the last nightly you should update M12 from.

Allen
[Motorola Droid RAZR] Ohmster:
No, I don't, Allen and sure would like to know. If this M12 SNAPSHOT is simply a frozen NIGHTLY Build 09, 10, or 11, we already know these roms have issues. That snapshot build date is important and I would love to know what it is. The ChangeLog still does not show it and there are quite a few updates planned for the next nightly. There does not seem to be a 11/12 build actually released yet, but for this "SNAPSHOT", which AFAIK is just a frozen nightly build. :confused:

If someone does install it, we may get a clue from the /Settings/About Phone/Build Date/ as indicated in the attached screen shot. I am not sure if it will indicate the true build date or release date, but we can for sure have a look at it. If anyone installs the M12 snapshot, can you please post your /Settings/About Phone/Build Date/ as indicated in the attached screen shot. Thank you.
[Motorola Droid RAZR] farangcm:
I went ahead and installed M12 Snapshot over my current build, 11/11 nightly, even though I know there may be conflicts. The M12 build date in Settings is: Wed Nov 12 09:21:31 PST 2014.

And they fixed the CM File Manager, so the top left menu button is working again.

Allen
[Motorola Droid RAZR] Ohmster:
Wow, awesome! So then the M12 SNAPSHOT really *is* the 11/12 NIGHTLY Build. Excellent. Since this snapshot is a nightly build like any other, I feel confident now to upgrade to it as though it were the next nightly. Hey, be a good chap and let us know of any issues or if it goes South tomorrow after charge and next day use. Thanks buddy! :good:

EDIT:

I wouldn't worry too much about conflicts. These roms are not so very different as to have issue when updating like that. The OTA updates do wipe your dakvik, cache, and /system partitions anyway so the install really is "clean", but for the settings you have in your Data partition.

So was your 11/11 install bad? If I update, I will be going from a good 11/07 build to the M12 11/12 SNAPSHOT. I wonder if updating from a bad rom or a good rom to another build will make much difference. It could, or it might not. Let's see. :)
[Motorola Droid RAZR] ChungHung.Chen:
Good morning in my timezone, Ohmster. Yes I'm suggesting about some standard info we should give when we post our test reports. It may help others to find posts which related with his/her phone because not everyone have their phone information in their signature. Discussions are very welcome.

Here is my suggestion: Model / PA-Gapps / Version (From->To) / Upgrade Method

For Example in my previous post is

"XT910 (umts_spyder) / PA-Gapps Micro 20141110 / 141108->141111 / by CyanDelta"

I agree that nightly-20141111 is not a good one. Having some freeze/lag and some screen wake-up issue. Sometimes key is light up but screen is off. Need to wait for few seconds to bring screen up or have to press power button to sleep/wake again. Will skip M12 snapshot and revert to 20141108 or wait for 20141113 tonight which have some new optimization about our CPU.