yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] Ohmster:
Thank you for the update, Dwillian. I have a lot invested in your case and am trying everything within reason to help you narrow it down and possibly find a solution for your predicament.

Oh that is awesome, dude. At least now we know that you phone "can update", you are having issues with the current set of nightly builds. Yeah, use the 11/09 as a stepping stone to update, save good updates to proceed. I will look for any "in between" updates if you want them. Or anyone else who has roms between 11/09 and 11/30 might offer them up.

I think this update via steps is a good way to troubleshoot, lacking any other choice.

Trying to help you bro. If you think the help is worth it, be a nice guy and tap the Thanks for me. :good:
[Motorola Droid RAZR] Dwillian:
I guess I am going to need some more intermediate nightlies. Even though they are listed on the server I get a server error when I try to download them.
[Motorola Droid RAZR] Ohmster:
Ouch, I only got 11/27, 11/28, & 11/29. Nothing in between that. I think the issues started at the very end of November and the roms got a little rough. Try 11/27 first to see if you can get that far. If not, then we ask some Members to upload anything they have between 11/09 and 11/27 Spyder. Okay?

Here are some download links for you:

cm-11-20141127-NIGHTLY-spyder

cm-11-20141128-NIGHTLY-spyder

cm-11-20141130-NIGHTLY-spyder

M12 SNAPSHOT is still on the server and has the release date as 11/12 cm-11-20141112-SNAPSHOT-M12-spyder.zip It may not help much though, I think the branch date on that snapshot is 11/03.

Yah, file sizes are the same for 11/27 & 11/28, 211.16MB and 11/30 is 212.21MB. I think that is when they got kind of bad. *Something* definitely changed at the end of the month. Right around 11/30 or 12/02 is when I got issues on every one, and you got really bad FC issues. And the file size increased over 1MB from 11/28 to 11/30. That might be the break point. This is only speculation but you can try these. If 11/27 won't go, then we have to scout for something in between because this is all I got. :p

See if this helps you bro and let us know what is going on. Be nice and Thank your helpers. ;)
[Motorola Droid RAZR] clclcl:
I'm not using any custom icon, at some point, a few hours after charging, I saw it staying at 100℅ and was like wow! But then I rebooted and..... It immediately changed to 84℅, after that it became normal though and started to discharge naturally (by 1℅) so I guess this isn't a battery problem. Maybe I'll wait and see if it's normal now.

Also is it just for me but when I type ℅, it looks like a small 'c' character instead of o at the top which is appearing? Like (c/o) instead of (o/o) ??

Sent from my XT910.
[Motorola Droid RAZR] Bobcus Leper:
The % looks exactly like you described it in this thread. It's strange because it looks fine for me on my keyboard (Google Keyboard).
[Motorola Droid RAZR] Ohmster:
Man, I don't usually use tapatalk because the PC is so much easier. But I'll use it now so you can see your percent symbol. Here it is, %. Well it looks normal to me in tapatalk and it also looks like a small letter C when you do it and I view it on a PC. That's kind of nitpicky but I guess if you're bored, it's something to do. LOL! :D

This message was sent by my XT912 in TapaTalk.

Back to PC comment.

Bob is right though. Your Percent symbol does look exactly as you describe it in both Tapatalk and on PC. Why I don't know. I use Google keyboard and Google Voice Typing in Android. You are a pretty gifted guy clclcl. You notice a lot of things and are very capable of working them out. :good:
[Motorola Droid RAZR] Dwillian:
I worked my way from the 11/27 nightly you provided (thanks) all the way up to the latest 12/05 nightly (although I inadvertently skipped 12/04) and they all installed fine (using the OTA process) and I had no problem with force close of any processes. 11/28, 11/30, and 12/05 had a smaller than usual app count during the app optimization phase. These three nightlies showed 50 apps optimizing instead of the usual (for me) of 150 apps.

I am very happy that these nightlies load now without any FC issues, but I have no clue what actually solved the problem. I'm going to try starting with a newly created rom slot, and flash 12/05 nightly and micro PA GApps to see if the force close comes back. If not, then whatever was causing the problem was finally fixed through all the newly created rom slots, wiping, and installs. I will post an update once I've done the clean install.

Which nightly do you recommend as "best" right now?

Thanks for all the suggestions and assistance.

Update: Clean install of 12/05 nightly into a new rom slot resulted in FC of com.android.phone.
[Motorola Droid RAZR] farangcm:
Unfortunately, this won't help you, but for anyone with the XT910, I have saved most of the CM11 downloads from 9/2 to 12/5 on my computer. After downloading each one, I checked the MD5 hash, and they all matched. I didn't keep the MD5 hashes, but I can recreate them with the HashCalc program.

So if any XT910 user wants an older CM11 build, I can upload it to Mediafire, or some other online storage location.

Allen
[Motorola Droid RAZR] welder73:
Why do you keep saying to people to hit that "Thanks" button?Nobody asks that except you...

Like you you'll get some money with that lol :p

"Okay, maybe you just did not know how to do it on a phone. *I* didn't know. :o"

That's a little ironic...

Sent from my Razr XT910
[Motorola Droid RAZR] Dwillian:
I usually do hit the thanks button, but I see that I forgot to hit thanks for providing the files. I must be getting rummy from all the wipes and reinstalls. Sorry about that. I went back and rectified the situation.
[Motorola Droid RAZR] Bobcus Leper:
Not to be rude or bragfull( I know bragfull isn't a word), but some of you members have been on XDA for months maybe years longer that I have, and some of you have give 1/4 the amount of thanks that I have given, in a shorter period of time I might add (less than a year for me). I have received just as many thanks in my short time here on XDA (if not more) than some of the senior members in this thread. All I'm saying is DON'T ASK FOR THANKS! I know I'm committing a fallacy (Hasty Generalization), but you won't receive thanks unless your post is helpful and concise ( I know that some members here don't like to read).

Please for my kurtness and potential hurt feelings of other senior members here.

Sincerely,

Bob.
[Motorola Droid RAZR] Dwillian:
Not a big deal for me. I am wondering how you know how many thanks have been given by someone. I don't see that information listed in user profile statistics. I believe the "thanks" meter measures how many thanks have been received, not given, by someone. The length of time a person has been a member, or the number of thanks they have received is less meaningful to me than what percentage of a users posts receive thanks (i.e., number of thanks received/number of posts; which suggests how many posts were useful to others). Of course, not everyone gives thanks, or always remembers to give thanks (mia culpa), so I don't think it hurts to occasionally remind everyone that thanks can be given. Still, it's not a big deal for me.

As Dennis Miller used to say "That's just my opinion; I could be wrong" ;)

---------- Post added at 01:11 PM ---------- Previous post was at 01:01 PM ----------

I tried to get back to 11/28 by doing a clean install of 11/07 and then OTA to 11/27, then OTA to 11/28. Today, for some inexplicable reason, I am getting the FC of com.android.phone again and it happens as soon as I OTA to 11/27 after the phone reboots. As far as I know I am repeating exactly what worked yesterday. Very perplexing. Since I didn't make a backup of any the succesfull OTAs yeesterday (I know, I know, I didn't follow my Droid Razr Zen Master's advice; [MENTION=4245858]Ohmster[/MENTION] ;)). So, I guess I'm stuck on 11/07 again.

I just got back from Best Buy and confirmed that if I buy a new Verizon phone off contract I can keep my unlimited data plan. Unfortunately my two favorite phones right now (Samsung Galaxy S5, or HTC One M8) are $749 off contract. Ouch!!! :(
[Motorola Droid RAZR] Bobcus Leper:
I can view how many thanks a person has given and received on mobile.:)
[Motorola Droid RAZR] deboyz1014:
Best value right now for an off contract phone is moto x 2013 developers edition 32 gig, 220 on ebay. Got one for the wife and its smoking fast compare to razr. Am still using the razr though, i like to tinker
[Motorola Droid RAZR] Ohmster:
You are a good guy, Dwillian and have been here for a long time. I really can't believe how much frustration you have put up with in the past couple of months with that phone. I really wanted to help you see that this rom can run well, even on old phones like ours. But it takes work. I think if we had new, rooted phones, the rom would work much better. A lot of us tried to get my2cents phone working well again and nothing worked! Made me feel bad for having him wipe his phone so many times. I will hand it to you for determination. You stuck it out and turned small progress into big progress. Good job! :good:

You are running December roms now? Any issues with the faulty app count update roms so far?

---------- Post added at 05:24 PM ---------- Previous post was at 05:19 PM ----------

Thanks Bob. I really never use the phone to post or view web forums because I have a nice PC setup at home and use it every day. Trying the phone is *way* different than using a PC. The toolbar is gone and a lot of things I see on a PC screen are missing or in different places. Plus, it is hard for me to type with the tiny on screen keyboard. I use voice typing for text messages and almost everything.

Thanks for pointing that out. Now I can view Thanks and other things, but I had to work with it for a while last night to find some of the stuff. I still like a PC better. To each his own I guess. :)

---------- Post added at 06:00 PM ---------- Previous post was at 05:24 PM ----------

Hey [MENTION=5362796]Dwillian[/MENTION] we had an intermediate rom for you that I posted a couple of pages back. This one.

Download cm-11-20141109-NIGHTLY-spyder Here.

Maybe you can step from 11/07 to 11/09 if works, backup. Then try update to 11/27. I remember you needed intermediate roms and those are all I have, but it did work.

I love that Galaxy S5 and want it real bad. But I can't spend ½ the monthly household income on it now. That is full retail price, bra. Amazon might have it cheaper and I have gotten customer service from Amazon and even refunds very quickly over the phone. Even if a third party sells you something and does not ship, gives you bad stuff, or won't answer. Amazon will cut you a refund immediately if anything like that happens. I would be a little more nervous on ebay because they will help you, but I don't think they give your cash back if you get burned like Amazon will.

Yeah, Amazon has the Galaxy S5 Verizon at $600 new, $360 and up for used good condition. :good:
[Motorola Droid RAZR] Dwillian:
Hmm... 11/09 may be the secret ingredient. Giving it a try now.
[Motorola Droid RAZR] clclcl:
:silly: Really sorry guys but apparently I hit the wrong key on my keyboard, there is this normal % key in my keyboard AND that "c/o" key, so I was simply hitting the wrong key... :silly:

Also battery indicator problem is OK right now but... Another challenger appears! Sometimes media sound isn't working!

So I flashed the latest 1206 CM11 (umts_spyder) still with 1121 2.0 PAGApps in Safestrap 3.75 again (Well I have a lot of free time) problem still persists for now, will try to find fix....

Thanks for the hard work of all developers!
[Motorola Droid RAZR] Ohmster:
Thanks for the update. I didn't know there was a "c/o key". :laugh:

System sounds failing has been attributed to enabling "OK Google Detection" in /Settings/Language & Input/Voice Search/"OK Google" Detection. Turn it off and system sounds should not stop. Our developer stargo reported this and so far, it has worked for me. Good luck! :good:
[Motorola Droid RAZR] Ohmster:
Another November rom for Dwillian

[MENTION=5362796]Dwillian[/MENTION] I scoured my PC and found one more November cm11 rom. I hope this helps you get back on track and updated to near current build status. Grab it here:

cm-11-20141124-NIGHTLY-spyder

This "Unfortunately com.android.phone has stopped" error message is something totally new and very irritating because one cannot use the phone, the OK acknowledgment popup is relentless and returns with every touch to the screen. Has anyone here had this issue before and had any success of getting rid of the "Unfortunately com.android.phone has stopped" error on a Droid Phone?

Dwillian is a really decent guy and I would like very much to help him. However, all of our efforts have yielded no fruit. What would really help is to know what triggered it and how to rid the device of it. Thanks to anyone who can help with it. :fingers-crossed:
[Motorola Droid RAZR] Bobcus Leper:
On my Droid X Running CM11, I got that error to go away by disabling the radio and enabling airplane mode.
[Motorola Droid RAZR] clclcl:
Oh gosh! been wondering what's wrong... I really didn't remember that I've turned on OK Google on all window! :silly: Thanks for that! So...

1206 CM11 NIGHTLY

1121 4.4.4 PAGApps 2.0

Safestrap 3.75

Recommended! battery life is pretty good me think!
[Motorola Droid RAZR] Dwillian:
As near as I can tell the com.android.phone FC problem first appeared with the 11/11 nightly (see http://xdaforums.com/showpost.php?p=56673210&postcount=6626 and http://xdaforums.com/showpost.php?p=56680161&postcount=6645)

Turning on Airport mode did not stop the FC.
[Motorola Droid RAZR] Ohmster:
The Morr post is great intel. Good looking out for providing it, Dwillian. :good:

I didn't really think that airplane toggle would fix what you have because we did so much already, but we did scratch off another item on the "to do" checklist my friend. Troubleshooting is a total PITA process of elimination. And this one has a LOT to eliminate. :(

Oh wow, so [MENTION=3687628]morr22066[/MENTION] has seen the com.android.phone error too! Maybe we can ask him if he got rid of it and what did he do. He should see the mention and if so, he might respond with what happened to him. It could happen, dude. :) Morr got this error on 11/11 and that is about right. I remember how good 11/07 was and Mr. Chen reported great success with 11/08, I just skipped over it and went directly to 11/10 and quickly to 11/11 and that is when it all went South for me too. That is why I stayed on 11/07 for so long. 12/06 is the very first rom so far that I am really comfortable with since then, I am on day 2 and so far, no issues at all with it. Will wait to give final build report on it. Mr. Chen is doing the same with umts_spyder on 12/06.

You know, we are openly complaining about it now and that is a good thing, generally. [MENTION=3457922]stargo[/MENTION] does monitor this thread and he does address issues here because this is "his baby". Bad thing is he is away for a month vacation. So we push on and if not fixed in a month, we mention it again my friend.

But if this is a rom error and has been here almost 30 days already, it could have been addressed by now. Any luck with 12/06? Either install directly, update to it from 11/07, or "Dwillian Dump" up to it from 11/07? Another idea for sure to try and check off the list. Do a clean install of 12/06 w/out gapps at all. Just get the build up and running quickly to see if the FC issue is in the rom or happens when mixed with gapps and what kind such as pa-gapps, gapps, or pa-gapps 2.0. I know, I know, TOTAL PITA, but both of us work on computers and electronics and you know it is all a process of elimination. Usually it is something you have seen before or can easily figure out. And them come "the problem children" and they do take a toll on anyone. :(

If not, then you get comfortable with 11/07 or update as far as you can and back it up. Then we wait for stargo to get back and ask him. This is his build branch so if anyone can or will fix it, it would be Michael. He is very good at this and will ask for certain logs for debugging that none of us will know about. Once he is committed, he is like a Pit Bull and does not give up until it is done. What do you think, Dwillian? :confused:
[Motorola Droid RAZR] Dwillian:
com.android.phone force close problem - SOLVED!

Ever since I flashed the 11/11 nightly I have been having serious problems with the com.android.phone process force closing. The problem was so severe that I have not been able to upgrade to any of the more recent nightlies (instead I have been relying on a backup I made of the fairly good 11/07 nightly).

I finally solved the problem by formatting my internal sd card. Then I ran Matt Groff's utility to restore my phone back to the stock Verizon rom and to root the phone (note: I used the original version of Matt's utility so I also had to take the OTA update from Verizon to get on the latest stock rom). Then I installed SafeStrap 3.73, created a new rom slot 1 (using default partition sizes), and flashed the 12/07 nightly and Paranoid Android micro GApps (12/07 release). After running through the initial setup, connecting to my Google account, and letting Google restore all my apps and settings everything seems to be working very well. I have been using the phone for several hours now with no force close of any process. The phone also seems to be working far better than it has in a long time. Apparently whatever was corrupted on the internal sd card was causing performance problems even when I flashed nightlies prior to 11/11 (which for some inexplicable reason I could flash and not have com.android.phone force close).

I've only been on the 12/07 nightly for a few hours. I will provide an update once I've run this rom for a day or two.

A few important notes:

You should backup your /pds folder (see post #1 in this thread). This folder contains device specific information. It doesn't appear that this folder is affected by the reformat, but it would be a good idea to save a copy just in case something goes awry. You never know ;)

You should backup any important documents or media files that are on the internal sd card if you want to keep them. The format will completely erase the sd card.

You need to use windows to reformat the internal sd card. Boot into SafeStrap, tap on the Mount button, connect your phone to your PC using a USB cable. Then from your PC format the sd card using FAT32 format and uncheck the Quick Format option. Unchecking Quick Format will force the entire 8GB internal sd card to be checked for bad sectors and they will be fixed if they exist. Quick Format will not do this additional check.

Thanks to everyone ( [MENTION=4245858]Ohmster[/MENTION], [MENTION=3457922]stargo[/MENTION], [MENTION=3313632]ChungHung.Chen[/MENTION], and others) who spent a lot of time offering advice, suggestions, older nightly files, web links etc. during my month long quest to solve this problem.

I would be interested to know if anyone else who has experienced this problem has any luck solving the problem by following this process.
[Motorola Droid RAZR] Ohmster:
Hey Congrats Dwillian! That was a really tough issue to sort out and man, you were "going at it like crazy", man. Good determination, nice!

I lost a ton of Gigs on my Samsung Tablet in the Jellybean days with CM10, I think it was. Seems like a LOT of people saw their internal 16GB sdcard seemed to lose a bunch of Gigs in the sauce, and nobody knew where it went. We struggled with that for like months, man. One dude on XDA figured it out, the new CM10.x installed nicely, but did not overwrite or delete the previous install of CM10 and it just "stayed hidden on the sdcard" with no way to see it or delete it. By formatting the internal sdcard and letting Google repopulate the apps Got back all my lost storage space and put everything back, in like 45 minutes. Sweet!

Formatting the internal sdcard is a good way of getting all the old "crud" off the card and all of your space back, as well as remove corruption. I would for sure backup the /pds folder off device, just in case, like you said before doing it on a phone. Didn't have that issue on the WiFi Tablet.

You did a great job man, thanks for reporting and giving up the method! I hope that this helps [MENTION=3687628]morr22066[/MENTION] come back. He had it BAD and if he could not fix it, he would use another rom and give up on cm11. So sad.

Thanks buddy, goodnight! :good:
[Motorola Droid RAZR] Dwillian:
BAD NEWS!!! The force close of com.android.phone is back. After about 8 hours of moderate use and no force close problems I started having a problem with spontaneous reboots when I was using the Chrome browser. After this happened several times I decided to clear cache, and clear app data for the Chrome browser (Settings, Apps, Chrome, Clear Cache, Clear Data). As soon as I clicked on Clear Data and said OK to the popup informing me that all the app data would be cleared the dreaded com.android.phone FC started with a vengence.

I'm giving up on this until [MENTION=3457922]stargo[/MENTION] is back and can, hopefully, take a look and fix the problem. I provided logcat's earlier, but I will be more than happy to provide additional logcats or any other information required to help diagnose and stomp this bug.
[Motorola Droid RAZR] Ohmster:
Wow, that totally sucks. Uh, you "did" backup that install while it was working so well, ....RIGHT?

So, restore your backup and what in the heck are you doing with Chrome Browser anyway?" Chrome BLOWS, dude! Everybody knows that Dolphin Browser is the best browser there is for Android. Grab that Dolphin Browser, dump Chrome, like totally uninstall it. Freeze it with Titanium Backup you if cannot uninstall it. Grab the Jetpack for Dolphin while you are at it and off you go! Dolphin rocks man. Lots of nice plugins for it, you can tap and tell it where to go, very nice, not so heavy on the system. At Play Store, type in "dolphin" for search to find nice plugins for it. Give it a nice theme. Dolphin is like Firefox for Android. Does not cause issues and is fast.

I am not sure that this will prevent your FC issue, but Chrome is a horrible browser and it might have triggered it. If you got the backup (Dude, if you don't have a backup this time, just like do "hara-kiri" and get it over with! :p), dump Chrome and try it with Dolphin to see if this helps. Just use Dolphin and tread lightly for a bit. :D
[Motorola Droid RAZR] Dwillian:
It's not Chrome it's CM. Restoring good backup of CM 12/07 still has FC problem. A clean install of 12/07 into new rom slot 1 still has FC problem. Restore of good backup of CM 11/07 does not. It is starting to look like the recent versions of CM are fundamentally corrupting my phone somehow. And, apparently, the only way to recover is to do a full reformat of the internal SD card or stay stuck on CM 11/07. Totally unacceptable IMHO.

BTW Chrome is a fine browser. It's the only browser AFAIK that will keep bookmarks synced across all my devices (e.g. desktop, laptop, tablet, phone). My bookmarks are even available at work or any computer for that matter as long as I'm logged into my Google account.

See http://www.androidpit.com/chrome-vs-dolphin-which-android-browser-is-better for a comparison. Dolphin sounds comparable, perhaps slightly faster, but the synced bookmarks and data compression available in Chrome still make it my browser of choice.
[Motorola Droid RAZR] crackerjack1957:
Why don't you try another rom in the mean time to see if its only cm11 related vrs SS & hardware.

DU & LS are great roms.
[Motorola Droid RAZR] Dwillian:
Good idea. Both DU & LS look promising. Do you have a preference?