yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] Ohmster:
What about it, Brian? Naifaharsy has a Droid phone and wants to install and play his high quality video games. I have done this myself, Dead Space downloaded several hundred megabytes of game data just to run. Same thing for GLES Doom. A couple of games like that and your partition will fill up quick. The game does not use ext-sdcard for game data, it is an app like anything else. I have a class 10 SDCard and I cannot use it for application data either. But if he uses the huge stock partition or enlarges his CM11 partition, he will have enough room to run a couple of really good graphic games. The Droid Razr is not really a good gaming phone. Dead Space played well on it, but most good graphic games would not. It depends on what kind of video is used in the game. Software rendering works, hardware rendering is pretty spotty.

I do not know of any way he can run the game off an ext-sdcard, do you? Bear in mind the language barrier makes very complicated instructions and communications quite difficult. Happy New Year my friend! :)

Edit:

You know, Google really messed us up by cutting the ext-sdcard out of the application loop. I could make a very educated guess as to why, now that I know about Android 5. Google is now a public company and they have to make money. All the time, LOTS of it, every quarter for the shareholders. I do believe they are planning to get into the online banking/credit market as it is quite lucrative. Right now you have Apple Pay and Google Wallet. But if they could tighten up security on Android devices, like we see coming in Android L, encryption, Selinux, locked boot-loader, and, restricted media access, then the phone could become "like a credit card". Wave the phone w/Bluetooth over a scanner at the cash register and your purchase is paid. Just like that. Then Google would become like Visa and make like, "Billions" of dollars on it. To make that a reality, the phones must be so secure as to win consumer confidence in it. And that means locking it down, piece by piece, little by little to make it secure. I do not like it at all. But when not only millions are at stake, but "billions", all bets are off.

I could be wrong, this is only speculation, but as we all know, a year ago we could save anything, from any app, to our ext-sdcards. These are removable devices. And as such, they are not secure. What I know for sure is that Google intentionally locked us out of our ext-sdcards and it is not coming back. All the "apps2sd" apps do not work anymore, or are extremely limited on what they can do. The ext-sdcard is becoming little more than just personal storage and backup space. And that really sucks. But the reason is always the same, companies just cannot seem to get enough money to be happy with. Google changed a LOT from when they won the confidence of the entire world decades ago. Once BIG money came into the game, they never really were the same. Even on censorship, something they vowed NEVER to do. But money changed all that. Now they say "Some Google is better than no Google at all" an in came censorship to places like China and other dictator countries. :(
[Motorola Droid RAZR] morr22066:
12-25-14 nightly build (modified)

I got bored and decided to try installing it again. But, after reading through the thread and seeing that whisper push may be the reason for the android phone process crash i thought i would try something different.

I used x-plore file manager, opened the 12-25-14 zip file and deleted the whisper push apk and the whisper bin file (also deleted voice plus just because i never use it). Then i dirty flashed the 12-25-14 nightly over 11-7-14.

It booted up fine, sent some texts, made some calls and rebooted several times and after several hours i have still not had a phone process crash. I'm going to play with it more and see if it stands up to normal use without crashes.
[Motorola Droid RAZR] brkahughes:
Just tossing my input in regarding a stable "daily driver"... For the last two months, I have been running the same ROM on my stock slot! LS 9/29/14 build. I installed it, flashed the APN fix (required), and have had no lag problems or other serious issues. The only thing I have seen, and that has only happened a total of three times, is the complete disappearance of the status bar (I assume a system_ui crash), solved simply by a reboot. I have not yet tried the LS milestone build from December, because everything just works! No lag, gobs of features, stability... I've been happy, and I still have slot one if I "need" to play.

- Brian

"Whatever happens... happens." -Spike Spiegel

AIO XT912 Stock Utility:

Reflash/Root/SafeStrap​
[Motorola Droid RAZR] Ohmster:
Hey, nice work, Morr! Scraping the seeds out of the potentially harmful zip file prior to flashing was a very good idea to try. This might help [MENTION=5362796]Dwillian[/MENTION] a whold bunch if he were to try it. I do not subscribe to WhisperPush and don't get the FC issue after 11/07. But I *do* get horrible lag developing on any later roms after they are installed for a day or more. December roms install fine, nice and easy, and then next day on some, 2-3 days later on others, and Whammo! "Tap N Wait","Tap for Black App", "So and so has stopped responding, close or wait", and all that stuff starts in.

You have an interesting "Test Bench" going on over there, Morr. It will probably help Dwillian. And it might be helpful to everyone. If the WhisperPush apk and binary file or files are "bad", that could impact the entire build, especially as time goes by and WhisperPush messages "pile up" or do whatever it is that they do. This is quite fresh, new, and interesting and we *are* the developer thread for OMAP4 so this kind of experimentation is not only welcome, it is what we are "supposed to do". Nice fresh look at the issue, it could pan out to be valuable and if so, perhaps Michael can debug and fix them, or we just remove them ourselves. I really have to Google just what the heck WhisperPush really does in CM11.

Oh, this does explain a LOT about what WhisperPush does, in particular how it is implemented by CyanogenMod.

WhisperPush: Secure Messaging Integration

Hey Morr, is your Google Voice integration into any messaging application working? Can you test it for me please? They mention it in the article link and I use Google Voice with text and SMS/MMS all the time. Who can bother pecking that tiny virtual keyboard when I can just "talk" my messages and articulate my speech well. You taking out the WhisperPush binary and apk probably does not affect Google Voice typing or Artificial Speech, but now you cannot send encrypted text messages to other cm11 users or other platform device users. If it turns out you need WhisperPush because you want encrypted text messages or something breaks, maybe you can take it from the 11/07 binary and put it back into the Christmas build before flashing or upgrading to it. :confused:

I want to get some version of cm11 FINAL on my stock slot. So far only 11/07 fills the bill. But with all this digging, investigation, and testing going on for cm11 FINAL, I am holding back to see how it all pans out. :)

Neat stuff, thanks for sharing buddy. Keep us updated, will yah? :good:
[Motorola Droid RAZR] morr22066:
So far so good. Been using the modified 12-25-14 build all day, calls, texts, maps, browsing, etc. No force closes, no black screens, no major lag.

So far Google voice has been working fine, I use Google voice all the time for my voice mail and selected texts but I never really make any calls with it.

I never use whisper push our encrypted texting, I have never really needed to. It was my understanding that the receiving party also has to be using the service or it was useless and since I don't text anyone else that uses it I simply don't need it.

I have not tried this as a fresh install, like I said, I did this as a dirty flash over my 11-7-14 backup.

Hopefully things continue to run smoothly.
[Motorola Droid RAZR] Ohmster:
Yep, that is pretty much exactly what I do and I have good results. But the real acid test will be for you to have the December builds installed, put the phone on charge at night, and see how the rom works the next day and subsequent days after that. This is when the terrible lag sets in for me on these roms, let's see if it happens to you.

It would help if you could "give the phone a little bit of a workout" both now and after a night on charge. Make it do some multitasking. Stream music, use Bluetooth, use Maps and Navigation, use the phone, all at the same time. I can do all this, any time, on 11/07 and although the phone is not "instant response", it does multitask well and there is no unreasonable wait when doing this sort of multitasking.

Put phone on charge tonight. Give it a workout tomorrow. Let's see what happens. Thanks bro! :o

I do not want to see your phone fail this test but so far, none of the December builds have passed. 12/06 installed and ran great, or so I though for 3 days. Then I did the little multitasking trick I mention above because this is how I use the phone in the car. I could not even get Pandora up and running and the phone went down in flames. :(
[Motorola Droid RAZR] crackerjack1957:
I was so impressed with LS 3.2 milestone build I have flashed to the stock side on all 3 razrs at home!!!
[Motorola Droid RAZR] morr22066:
12-25-14 nightly build (modified)

*Well i spoke too soon... After about 12 hours i suddenly began to get the phone process force close again... Oh well, it was worth a shot. I may give it another try but I'm out of ideas.
[Motorola Droid RAZR] Ohmster:
Psssssssssst! "Hey Morr, over here! Ssssssssssh, be quite! It's a secret."

Tell you what, you can use "my idea" or "secret" about CM11, FINAL. Your intention is to install, run, and use CyanogenMod ROM #11 on your Droid phone as your daily rom. Yes? Those are my intentions anyway. CM11 officially went "FINAL" on or about November 1st, 2014. That means any and all roms released on or about 11/1/2014 are all "Final" and all contain the exact same number of features and they all identical in the way they work and in what they do. Yes, there are quite a few Nightly Build Releases past November 1st. The M12 SNAPSHOT was pulled from the 11/03 Nightly and worked on for what, 7-10 days and released as "M12 SNAPSHOT FINAL". From what I now understand and from what Michael told me about M snapshots and the current state of CM11 rom in Post #7063:

Notice that Michael did mention yours and Dwillian's current issue with the new roms, the dreaded SMS "FC from HELL".

So, from what Micheal tells me and what I interpret from the Changelog tells me that any cm11 build from November to present are ALL cm11 FINAL release builds. The only difference is that latter releases have some code updated, bugs fixed for certain individuals, a repository change, and several other small system improvements. But no one build in particular is really any "better" than any other one. Micheal and CM11 state that we should use the M12 SNAPSHOT as the cm11 FINAL rom. But if the M12 is not better or is worse for me than, say, my beloved 11/07 Nightly, then I can use and enjoy the 11/07 Nightly as my final rom.

Same goes for you, Morr. If 11/07 works great, 11/19 works great, or 12/06 is your best running CM11 rom, them make it your Final rom and be done with it and "don't look back", as if you were "missing something". You really are not.

Yes I want to install and use cm-11-20141225-NIGHTLY-spyder.zip and call it a done deal. But if it hangs, crashes, lags, or is in any way inferior to the 11/07 build that I love and that never lets me down, crashes, or lags, I should ditch it and use the November rom that works best for me. Does that make sense? :confused:

Yes it is fine to try out the newer roms and see if they work satisfactory, and use them if they do. But it is not really "fine" to get hung up on it and allow it to ruin our day. What do you think about that, my friend? :)

...BTW, thank you for performing and reporting the WhisperPush zip file removal experiment with the 12/15 rom. Even though it did not end successively, it did educate the rest of us about this idea and what the results would be. Information is always good. :D
[Motorola Droid RAZR] Crumplet:
So I want to give cm 11 a try. I am using XT910. What release date should I use? Gapps as well? Including any patches? Also the download link on the front page is not working for me. Any recommendations?And can anyone confirm this rom can be considered as a daily driver on XT910?
[Motorola Droid RAZR] morr22066:
Hi Ohmster. Yeah, I have been following the thread and the cm11 change log and I know that the M12 snapshot was the final significant release and that nothing after that really changed.

But I do enjoy flashing new builds and checking them out. So I have enjoyed trying to get the later builds to work mainly because I am bored right now waiting for the next semester of classes to start. Right now there is not a whole lot going on other than the experimental lollipop builds.

I still have quite a few ROMs backed up on my SD card that I go back to including cm11 M12 and 11-7-14. Plus I have been checking out the lollipop builds and they have been getting better. So I am still able to satisfy my itch to flash new ROM's ;)
[Motorola Droid RAZR] farangcm:
The final Snapshot for the XT910 is here: http://download.cyanogenmod.org/?device=umts_spyder&type=snapshot

The Gapps you use depends on which Google apps you use. Here are the Paranoid gapps that many people use: http://xdaforums.com/showthread.php?t=2397942

No patches required for the XT910, as far as I know.

The M12 Snapshot is supposed to be the most stable, but you could also try any of the nightlies after 11/3, the M12 cutoff date., but they are "hit and miss."

I put the M12 Snapshot in the Safestrap Stock Slot, so I am using it as a Daily Driver, but it depends on the functions you require. It's always possible to run into a bug. It seems CM has stopped working on CM11 so they can work on CM12 Lollipop. See [MENTION=3457922]stargo[/MENTION]'s last post for the official word. Hope this helps.

Allen
[Motorola Droid RAZR] Crumplet:
Thank you both for the great information. I will download it definitely. Agian thank for your hospitality. Happy new years.
[Motorola Droid RAZR] Ohmster:
You are very welcome and polite, Crumplet. Working the Help Desk is not a bad job when it really makes a difference to someone that really needs the help, is nice about it, and appreciates it. The only other thing we ask if for you to post your results and if you are pleased. Who knows, perhaps you will not be or you might try a few different builds to find one you like. Feedback is important because it lets us know what works and what to tell fellow members with questions. And yes, it "feels good" when we really do help someone and it really made a difference. Happy New Year my friend. :D
[Motorola Droid RAZR] Ohmster:
Ahhh! So you play with and update cm11 for "the twitch to fix that itch". Got it. So it is voluntary, not in response to some compulsion to always correct the rom and constantly update it. You are just doing this to play, and learn, got time, and are bored. Good! Not the bored part, but that you know what you are doing and you are comfortable now. A lot of people, and I have gone through this myself, feel like, if they do not update to the latest build, the rom will never be complete. Which is a lot of bull. I don't like "feeling like I am missing out" and it drove me compulsively to try and fix things I could not fix. It drove me nuts, man. Now that I found the build that works best for me, I can relax and put it on my stock rom when I feel like it. For now, I can "play rom" too. Who knows, might learn more neat stuff.

Okay dude, you are all good and that is what matters. Take it easy, bra! :D
[Motorola Droid RAZR] farangcm:
New Nightlies!

I don't believe it. CM says M12 is the final, but they forgot to tell the developers :D. Now we have a new 12/30 Spyder nightly and new 12/31 umts_spyder nightly build. Maybe this is just a one-time, end of year special? Enjoy while you can.

Allen
[Motorola Droid RAZR] Dwillian:
I doesn't look like the patch to fix the dreaded com.android.phone force close has made it into the most recent nightlies for the XT912/Spyder yet. It's been about a week and a half since [MENTION=3457922]stargo[/MENTION] said that patch was in the works. [MENTION=3457922]stargo[/MENTION] provided an unofficial CM11 release about two weeks ago that included the patch and I confirmed that it fixes the force close problem on my phone. I'm not sure when the patch is going to make it into the CM11 builds for the XT912, but I don't expect any of the recent nightlies to work very well until that patch makes it into the nightly releases.

I just checked on the status of the patch and it is still under review (see http://review.cyanogenmod.org/#/c/81835/). Note that the com.android.phone force close problem is also affecting the HTC M8 and at least a couple other XT912/Spyder users.

See post #7040 (at http://xdaforums.com/showpost.php?p=57674828&postcount=7040) for more information and link to unofficial CM11 release.
[Motorola Droid RAZR] Bobcus Leper:
M12 was the final Snapshot of 2014, It was not the end of CM11. That is why we still have nightlies.
[Motorola Droid RAZR] farangcm:
Maybe we have Weeklies ;).

Allen
[Motorola Droid RAZR] Bobcus Leper:
Happy New Year everyone!
[Motorola Droid RAZR] Ohmster:
Seems like an awful long time for such a critical patch to make it to the cm11 build tree. Here is some good news for you [MENTION=5362796]Dwillian[/MENTION] read this:

Telephony: If no wrapped message, originating address is null

Adnan Begovic	Dec 31 7:25 PM

Change has been successfully merged into the git repository.

More Good News, check the Changelog. Specifically this part:

to be included in next nightly:

Telephony: If no wrapped message, originating address is null (android_frameworks_opt_telephony)

So the next nightly release and every nightly thereafter should really contain your dreaded com.android.phone FC fix. It does not seem to be Michael who is working on this though, Michael does do the OMAP4 phones, but this is the patch URL that you gave me. It could be for HTC or all phones. HTH

Hope this is the news we have been waiting for to help you and [MENTION=3687628]morr22066[/MENTION]. Happy New Year fellows and gals! :D
[Motorola Droid RAZR] Dwillian:
That is the patch that [MENTION=3457922]stargo[/MENTION] said would fix the com.android.phone force close on our phones. It looks like the latest nightly (2015/01/01) is available and has the patch. I'm going to load it now.

Thanks for the update and Happy New Year [emoji4]
[Motorola Droid RAZR] Dwillian:
I did an OTA update from my fully configured M12 Snapshot (running in stock ROM slot) to the 01/01/2015 nightly. Everything has been working fine for about 6 hours now (and may be a bit snappier and smoother).
[Motorola Droid RAZR] Ohmster:
Yah, I did the update to 01/01 OTA too, directly from 11/07 and backed it up again first. Did this very early afternoon. I did check it out, seemed very good. Since I like to multitask a bit when driving, I decided to check that right away. If a rom is not equal to or better than the one it replaces, I nix the update. So I got into the car, turned on Bluetooth and Car Connect to car stereo, turned on Pandora and streamed some hits of the 80's, opened contacts and tapped a close by address to start Maps then tap Navigation from Maps to get it all running. If I can do all that in 2 minutes, this is good. I just made it. While driving to store, I tapped Home to clear screen, Contacts, myself to call home. Phone muted and dialer commenced, the call went right through without incident. :good:

This evening I am making stuffed red peppers for dinner and had more stuffing than I had peppers. Off to the grocery store for a couple of red peppers and repeated the mini-multitask procedure. Again, all went well, except I used Google Play Music this time and the Eagles album I was streaming was stuttering pretty bad, like it did not buffer properly. But fast forward a song or two then back winding to the song again restored normal play. The call home went very smooth. It is noteworthy to mention that many roms could not get through this "mini multitask run" at all but Nightly 11/07 would breeze right through it, any time, any place. :)

This is all really good news. Now I am biting my nails because this is almost too good to be true! And "lag creep" is a fairly regular "rom killer" that sinks into the rom anywhere from overnight to just a few days. The rom becomes so lagged and unresponsive that it is not even usable, much less an improvement. That is what happened with update build 12/06. But this 01/01 update did seem pretty snappy for me too. So, the nail biting continues for me. :eek:

But you stand a pretty good chance of getting a good rom out of this, Dwillian. I think your main or only complaint was "The FC from Hell" and I saw the youtube video on it, man, you cannot use the phone at all for anything! Okay, so we wait. It would be good if we could get a couple of others to check in with their results too. I did ask Mr. Chen if he would mind trying it on his XT910 for us. ( Ugh, Sonia Kitty is up on the back of my chair, nuzzling my hair and wanting attention again. Gotta go. :o ) Thanks for the report, buddy! :highfive:
[Motorola Droid RAZR] farangcm:
This explains why we only see CM11 nightlies and snapshots: http://wiki.cyanogenmod.org/w/Release_Versioning

"CyanogenMod 9 - 10.2 build tags

CyanogenMod 9 through 10.2 were qualified with tags: Experimental, Nightly, Release Candidate, and Stable. The Snapshot tag was added with the introduction of M builds in CyanogenMod 10.2. These tags were meant to indicate a build's suitability for general use.

Nightly: usually generated every 24 hours, experimental, newest features, unstable

Experimental: testing version requested by device maintainers to evaluate specific changes

M Snapshot: milestone snapshot, more stable than a nightly but potentially some issues

Release Candidate: last builds before stable release, few minor issues, mostly stable, and safe for daily use

Stable: most stable version available, all or nearly all issues resolved

The Release Candidate and Stable tags bring with them considerably high expectations from users. For this reason, device maintainers and developers involved with CyanogenMod had one simple rule: No ETAs.

Stable build tags carry additional minor version numbers. Consider CyanogenMod A.B.c.d, where A.B is as described in the What's in a number? section. Then,

c signifies a large number of bugs were fixed for a new stable release. For example, CM 10.2 had two major Stable releases: CM 10.2.0.0 and CM 10.2.1.0.

d signifies a bugfix or hotfix version. This number is less often seen, but signals a critical bug fix that was identified as required after a stable release has been issued. Example: CM 10.2.1.1. This version can vary between devices.

CyanogenMod 11 Community build tags

CyanogenMod 11 Community releases reduce the number of build tags to just two: Nightly and M Snapshots.

(emphasis mine)The tag names have been retained for historical reasons, but this is really just a basic two channel release system:

Development channel: (a.k.a. Nightlies) usually generated every 24 hours, experimental, newest features, unstable

Release channel: (a.k.a. M Snapshots) generated once a month, suitable for daily use, lags behind nightlies by roughly 2 weeks

The simpler tagging system has had a number of positive outcomes. Perhaps, most importantly, there is now a predictable release schedule for builds that should behave well on your device. More information on the rationality behind this change in build tagging can be found in the CyanogenMod 11.0 M6 Release blog post."

There is so much information on CyanogenMod on the internet, that it is easy to not see some very basic information. I have been using CyanogenMod 11 for over three months and I just now saw this explanation.