yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] Ohmster:
Thanks for posting, [MENTION=3457922]stargo[/MENTION]. I would like to upgrade with this image to see if it has any "ill effects" or improvements on a very good working XT912 with Nightly Build 11/27 and post results. Gosh I hope this works, I want to see Dwillian to have a good working phone so he can play CM11 with the rest of us and have a solid, reliable daily driver rom on his phone. As well as the cool Alpha CM12, which I am collecting files and waiting for time to try it myself. (I have to make sure I have card space for the new Android L you made.

Could you post the cm-11-20141128-UNOFFICIAL-spyder.zip.md5sum please if you have one? Thank you.

I will test and report on this build like any other. Will supply a dmesg or filtered CatLog if you have any filter suggestions.

[MENTION=5362796]Dwillian[/MENTION] go man, go! I will watch if you need help. Fingers crossed for you. :fingers-crossed:

UPDATE:

Previous rom CM11 NIGHTLY Build 11/27, working very well and smooth by day 2.The cm-11-20141128-UNOFFICIAL-spyder.zip installed very nicely with a fresh pa_gapps-modular-mini-4.4.4-20141121-signed.zip. This update was done manually by the following method:

Download CM11 & pa-gapps to ext-sdcard

Rebooted to recovery, Safe Strap v3.7.3

Wiped /cache, /dalvik, & /system

Flashed CM11 & pa-gapps

Rebooted to system

Set BetterBattteryStats to system app, updated AdAway hosts, updated Xposed Framwork with update button

Rebooted to system

New CM11 rom 11/28 UNOFFICIAL is fast and stable. Everything tested works very well. Will followup with final build report within 2 days.

Dwillian, get up, come home from work. We are dying to see if this helps you, bra! :D

...hmmm, exactly *when* did society begin addressing men as women's breast support undergarments anyway? :p

UPDATE #2:

Dwillian has confirmed in Post #6895 that the new CM11 UNOFFICIAL NIGHTLY Build, 11/28 has fixed his constantly crashing XT912 device. The patch, great thanks to [MENTION=3457922]stargo[/MENTION] has done it's job and should be merged into the build tree very shortly when he gets notice of it. Thank you Michael. Happy Days are here again! :D
[Motorola Droid RAZR] Bobcus Leper:
Off Topic!

MUST WATCH!!!!!!!!!!:D:D:D:D:D

Star Wars: Episode VII - The Force Awakens Offici…: http://youtu.be/OMOVFvcNfvE
[Motorola Droid RAZR] Dwillian:
I just created a new rom slot 1, flashed cm-11-20141128-UNOFFICIAL-spyder.zip and Paranoid Android stock GApps, wiped cache and dalvik cach, rebooted, and setup the rom. So far I have not experienced any force close of any processes. This suggests to me that the patch does fix the problem since with earlier nightlies I would have received repeated force close of the phone process by now.

Thanks for the patch. I will keep an eye on the new nightlies and try again once the patch has been integrated into the official builds.
[Motorola Droid RAZR] Ohmster:
AWESOME DUDE!!! :highfive:

[MENTION=5362796]Dwillian[/MENTION], Oh man, I have been pulling my hair out trying to figure out how to get you back up and running again. I honestly did not know what else to do, we did indeed "Need Big Guns" and you got them! [MENTION=3457922]stargo[/MENTION], who else? :laugh:

Back this up, bro, NOW! While it is still fresh. Then, you know the drill, kill the Play Store auto-updates and optimize it like we talked about. I am not kidding, this is the happiest post I have seen all week! Now I can get on with CM12 and you finally should have not only a solid & dependable CM11 Daily Driver Phone, but one you can optimize up so it runs fast, slick, with no issues anymore. If you need any help with "tuning it up", just ask. I am not an expert but my track record for the last 2-3 months is very good. I wish I had those instructions a year ago.

Woot! :D
[Motorola Droid RAZR] Ohmster:
ATTN: Stargo, Audio loss on Unofficial Spyder 11/28

[MENTION=3457922]stargo[/MENTION]

Installed your cm-11-20141128-UNOFFICIAL-spyder.zip file with pa_gapps-modular-mini-4.4.4-20141121-signed.zip today. Seems to work well. I have been using a Bluetooth headset for most of the days phone calls. After receiving a few text messages, my system audio just "stopped". No touch sounds, nothing. I immediately saved a couple of CatLogs, one with filter "audio" and the other is unfiltered. I got the system audio back by calling the device and the ringtone restored the system sounds. After restoring system audio, I took a dmesg. All three logs are in the attached Audo-Out_11-28-2014.zip file. Perhaps you can use these logs to check the performance or any issues with the current rom and audio system.

System Information:

Bluetooth was enabled but not in use at the time.

"Okay Google"Detection is NOT enabled at all.

Manually flashed ONLY the two listed files over 11/27 Nightly. Wiped cache, dalvik, & system. Flashed two zip files. Wiped dalvik and cache. Rebooted to system. Enabled BetterBatteryStats as system app, checked AdAway for host update was current, tapped Install/Update on Xposed Framework and rebooted.

This rom is otherwise okay so far.

HTH. Thank you for your continued efforts. :)
[Motorola Droid RAZR] Dwillian:
For some reason the force close of com.android.phone is back.

Not sure if this is related, but I was playing with CM12 in rom slot 2 for much of the day today. That did require upgrading to the beta version of SafeStrap (version 3.75). I decided to go back to rom slot 1 where I have the patched version of CM11 (i.e., cm-11-20141128-UNOFFICIAL-spyder.zip) that seemed to be working fine earlier today. Now on first boot the force close is back.

Very strange and frustrating.
[Motorola Droid RAZR] Ohmster:
* Thanks for the immediate report, Dwillian.

Oh God, not again! I was planning on installing the Safe Strap beta today, but being totally broke and having an office IT job for the weekend, forced me to let it go and make some serious cash! Not sure if that is what caused your issue though, dude.

Anytime something like this happens and you are using a [MENTION=3457922]stargo[/MENTION] test debug or new patch, go get that dmesg.txt file. It could hold the clue as to what caused this. You see my post right above yours? My 11/28 lost system audio and I have had this problem off and on for months. I immediately grabbed logs to submit. You can too, if you are able. ;)

Can offer suggestions if you like before you do anything drastic. :)

Make sure you have the necessary files on your phone before you do this!

Go back to stock and uninstall recovery, uninstall Safe Strap beta, install Safe Strap 3.7.3, install recovery, and reboot to see if it fixed anything.

If not, restore your good CM11 11/28 Unofficial backup if you have one. Please tell me you do. If not, move on to steps below.

Again have the necessary files on phone!

If not fixed, use DD procedure to wipe CM11 cache, dalvik, and system. Flash only these two CM11 files:

cm-11-20141128-UNOFFICIAL-spyder.zip

pa_gapps-modular-mini-4.4.4-20141121-signed.zip

Wipe dalvik & cache, reboot. Update AdAway, tap BetterBatteryStats to enable system app, open Xposed Framework installer, tap install/update, reboot. See if fixed.

This should put you back to where you were before the Safe Strap change and phone crash by keeping your data, apps, configs. If this fails, then you might have to flash the same two files after delte/recreate CM11 rom slot. :(

Wish I had better advice but the above listed procedures are a LOT easier than starting from scratch and are for sure worth trying. Maybe the CM12 with Safe Strap 3.7.5 beta is what is triggering it. Not sure, maybe not. But we are gathering clues my friend. :fingers-crossed:
[Motorola Droid RAZR] morr22066:
phone process force close

I also tried the stargo patch. First i tried it as a dirty flash over the 11-7-14 build and got the force close almost immediately. Then i wiped the system in addition to dalvic, cache and secure and flashed it again with current pa gapps pico and within a few minutes it began to force close again. I am still using safestrap 3.73.
[Motorola Droid RAZR] Ohmster:
Oh wow! Be specific, Morr. Did you have *any* FC issues "before the new stargo 11/28 patch build"? Michael will come here to read what is going on and if we don't put up the information he needs, there is not a lot he can do.

How is your phone in general, okay? Been running right? What roms do you currently have installed and use? CM11 and CM12? Any other roms? What slots are they in?

Thanks for reporting. :good:
[Motorola Droid RAZR] morr22066:
My phone has been running well. I have been getting the phone process force close since the 11-11-14 nightly build. I have tried multiple nightly builds since then with the same results. I also had the problem with the PAC ROM builds after 11-11-14 since they pull from cm11. I have between running AOKP and LiquidSmooth ROMs without any issues. I did try the cm12 pre-alpha build briefly and it does look very nice, but after using it I went back to my cm11 backup of the 11-7-14 nightly and have been using it. The only issue I have had with the 11-7-14 build is that chrome will crash and occasionally reboot my phone but that is most likely an issue with chrome. I always run cm11 in slot 1 and other ROMs go in slot 2 as it has less space and cm11 is usually my daily driver except for this past couple weeks.

---------- Post added at 09:32 PM ---------- Previous post was at 09:27 PM ----------

It looks like the next nightly is supposed to have a fix.
[Motorola Droid RAZR] Dwillian:
I reverted to SafeStrap 3.73, deleted rom slot 1, recreated rom slot 1, installed 11/28 patched and PA GApps (full package), wiped cache and dalvik cache, rebooted. Unfortunately, before I could even select English language (the very first step in the setup phase) I got the force close of com.android.phone process. The incessant force close pop-up windows makes it nearly impossible capture log files, so I didn't attempt to get them.

I then did a "Dwillian Dump" and restored my backup of a functioning 11/07 nightly. I think I'm going to stick with this setup until I hear that some progress has been made on solving this problem, or maybe just wait until CM12 is out of alpha testing.

I have given CM12 alpha a try and I really like the way it looks. A few bugs need to be worked out before I can consider it a daily driver though. Specifically, it usually loses wifi on a reboot (waiting a very long time will sometimes get the wifi to reconnect). It also totally locks up at times. the lockups will sometimes clear eventually, or I'm forced to power down and restart.
[Motorola Droid RAZR] ChungHung.Chen:
Test report of CM11-20141127-umts_spyder

<< Basic Info >>

XT910 (umts_spyder) / CM11-20141127 / PA-GApps Micro 20141121 / From CM11-1123->1127 by CyanDelta

Note: PA-GApps was flashed manually.

<< Report >>

Tested Period : 2 days

Tested Item : Phone call / SMS / Mobile data / WiFi / GPS / HDMI / MX Player / YouTube / Light Games(Paper Toss) / etc.

Tested Result : Better as I expected, smoother than 11/23, no random lag, no FC in XT910. Recommend if you ask for a suggestion.
[Motorola Droid RAZR] stargo:
Hi,

Uh, that's bad :( Are you able to get a logcat? This would include more helpful info right before the crash (what gets uploaded in a crash-report is rather limited). It seems this is caused by an incoming SMS. Do you receive many SMS?

May I ask you to try the "CM" Gapps from here to see if you can reproduce it: http://wiki.cyanogenmod.org/w/Google_Apps (I'm using the "small" package from there)

(Or just try it without any gapps)

The "protected sms" feature was integrated on the 11. and seems to cause this, but Adnan's patch should have fixed it again...

Yeah, it's not ready to be a daily driver and will not be for a long time (maybe sometime around january or so).

No, don't do that. This would include your pds-image which would put some parts of your phones' identity on Diwllian's phone (like MAC-adresses, DRM keys, ...). It should be ok if Dwillian deletes /data/pdsdata.img and reboots after restoring your backup. The phone then should create a new pds-image from his partition.

Regards,

Michael

Semi Off-Topic: I will not be able to work on CM in the next few weeks :( See you all in mid-december again :)
[Motorola Droid RAZR] morr22066:
11-29-14 nightly

Tried the 11-29-14 nightly as a dirty flash and also with a full factory reset and no gapps. Got the phone process force close as i was going through the initial set up of the phone on my cdma spyder on Verizon...
[Motorola Droid RAZR] stargo:
I've updated my test-build, hopefully this fixes the com.android.phone-crash now: http://droid.cs.fau.de/cm-11.0/test/

If I get a positive report soon and no negative report until monday, I'll submit the patch to gerrit.

diff --git a/src/java/android/provider/Telephony.java b/src/java/android/provider/Telephony.java
index 4678015..0951130 100755
--- a/src/java/android/provider/Telephony.java
+++ b/src/java/android/provider/Telephony.java
@@ -1173,7 +1173,7 @@ public final class Telephony {
// we can get a bad format and no valid members.
// Thus we introduce a hack that utilizes the deprecated
// SmsMessage.createFromPdu if we get a null originating address.
- if (msgs[i].getOriginatingAddress() == null) {
+ if (msgs[i] == null || msgs[i].getOriginatingAddress() == null) {
msgs[i] = SmsMessage.createFromPdu(pdu);
}
String originatingAddress = msgs[i].getOriginatingAddress();

Cheers,

Michael
[Motorola Droid RAZR] Ohmster:
Right. Alpha software can never be "A Daily Driver". Although it is *very* cool to get not only a sneek peek, but a chance to play with and use it in real life! :)

Ahhhh yes, the DRM keys, MAC address, and all the other goodies that makes my phone, "my phone". But a possible work around if one were to restore the backup to another device.

Delete /data/pdsdata.img and reboots after restoring the backup.

Neat! :D

There are some good logcats and a dmesg from an audio system lock in CM11 here in Post #6897 if it helps you Micheal.

Oh, you will be gone for a month. It is the holidays and if anybody deserves a break, it would be you, Michael. Happy Holiday and Merry Christmas, Michael! Thanks for jumping in to help. :)
[Motorola Droid RAZR] Bobcus Leper:
Not to be argumentative or anything, but I am running CM12 11-27 build on my stock slot, and it is my daily driver. Everything that I need just works, in one way or another!

:)
[Motorola Droid RAZR] Ohmster:
Uh, I guess Michael was dead wrong and myself, dead wrong as usual. Hmmm, who would've thought. :confused:

Bob, Michael nor I did not say using CM12 as a daily driver "could not be done". What was stated is that it should not be done. In the event you need a dependable, reliable phone that works, any time, any day, every day. Alpha software is in a constant state of flux. It is about as far away from stable and complete as the original concept is. You do not have "An activated Phone" that you are running CM12 on, right? So you really would not know if incoming calls crash the UI, or calls are missed or dropped. If text or SMS does not work. Or, if your life depended on it, you could always call 911 or not.

People can use anything they want as a daily driver. 2 Campbell's soup cans and a long string. Just remember to keep that string very taught between you and the 911 operator when reporting an emergency or the call may be subject to dropouts. :p

No offense Bob, but if you have an extra phone lying around w/out service, you cannot really test a rom on it for reliability because you have no service. That is why I do not have CM12 Alpha installed, because I really need a reliable phone and have to make sure that comes first. Playing around with Android L Alpha comes later.

Don't get pissed Bob. I am only trying to make a point. We need cell service, signal, data, and this must be 100% of the time like when I slip and break my7 ankle in a deep canyon. But, you are free to use anything you want, as an individual. Even a Fisher Price Cellphone like this one, if you like it. :D

[IMG="My Daily Driver Cellphone. Can't call 911 but it sure LOOKS COOL!"]http://trus.imageg.net/graphics/media/trus/Aplusplus/2012/4460033/MATTEL-4460033-01.jpg[/IMG]​

...I am just "kidding"! Don't take it personally! ;)
[Motorola Droid RAZR] Bobcus Leper:
I feel so bad now.:(
[Motorola Droid RAZR] Ohmster:
Don't feel bad my friend. I admire your enthusiasm and went back to explain my reasons for "smarting off at the mouth". Hey, you are in the front lines, compiling code, building roms, experimenting on what works and what does not. But, without service on the phone, your reports are limited on how well the device works as a dependable phone.

Still, I plan to install it when I get a LOT of spare time. You post all the new release downloads, where to get the gapps, what to look out for, and we all appreciate that very much. Thanks for your help with the CM12 thread. Now, we really should move the CM12 talk over to the CM112 forum. This way, those who need dependable CM11 phones can get the help they need.

My UNOFFICIAL spyder 11/28 build is running well. But I cannot test it for crashes. We need [MENTION=5362796]Dwillian[/MENTION] for that. I hope he comes along soon and tries out Michael's new rom! :D
[Motorola Droid RAZR] Dwillian:
Thanks for the suggestions. I downloaded the "CM small" GApps, created rom slot 2, installed patched CM 11/28 nightly and GApps. I got a failed message during the GApps install. I tried again and still got a failed message, so wiped cache and dalvik and rebooted anyway. CM started fine and I successfully completed the initial setup without any force close. It seems that GApps is OK since I'm now restoring all my apps from the play store.

If I get a force close I will try and get a logcat. I've never done that before. It looks like I need to install adb on my PC and then I can capture a logcat following this tutorial: http://xdaforums.com/showthread.php?t=1726238. Is that correct?

Thanks for all the help.

Update: I just learned from [MENTION=4245858]Ohmster[/MENTION] that there's a patched 11/29 nightly ready for download. I'm going to switch to that release and see how it goes. Thanks for the tireless work. Much appreciated
[Motorola Droid RAZR] welder73:
I'm running CM12 4-5 days and everything important is working,Wifi,Bluetooth,Data,never lost a signal,calls and messages comes normally...

Sorry for off topic...

Sent from my Razr XT910
[Motorola Droid RAZR] Dwillian:
Appreciate the update, but probably best to post CM12 comments in the CM12 thread: http://xdaforums.com/droid-razr/development/rom-cyanogenmod-12-0-t2950906
[Motorola Droid RAZR] Ohmster:
No ADB or any of that. That is for developers and serious hobbyists. CatLog makes system log captures easy for anyone. If you use ADB and a USB cable you would not need CatLog at all. I have the Android SDK with ADB installed and have used it on my phone, but I never bother with all that just to get a log file. The dmesg is a capture of the current bootup and system messages, but not the entire system log. CatLog shows the system log in real time, scrolling by, all in nice pretty colors to help identify the various messages. The filter word box in CatLog is especially useful so if your text messages fail, you could filter messages for "sms", "mms", or "text". That would eliminate the bulk of the system log that is not relevant to your issue. This way you can now save the filtered log of what it is that you are looking for and not have to hunt though a 750Kb log file for what you need to know.

Get that new cm-11-20141129-UNOFFICIAL-spyder.zip flashed and give a report tomorrow, be sure to mention stargo in the post with the @ symbol to get his attention. This way, if your report is positive, he can merge it into the Git Repository where it will be merged into the current CM11 build tree. Michael will be gone for a month, starting next week.

Yes, install CatLog - Logcat Reader now. That tutorial is fine if you need "A Harvard Education" but skip all that. Open CatLog and play with it to become familiar with it. Find the save button, see the "Filter word" box.

Run CatLog after the incident. If it is a phone crash put something like "phone" in the filter box to weed out anything that does not contain the word "phone" in some form or another. Save the log file. If an audio or power problem, use filter words like "audio" or "power". Save the log. You can also save one log w/out a filter, just in case you used the wrong filter word. At least the log will be captured. Albeit a bit lengthy, but it will be captured. That is all you need to know.

Dwillian, you are getting a fantastic education and LOTS of terrific experience here. I know "it sucks" but you are getting to know a LOT about CM11 roms, all roms, and you carry this knowledge and experience with you for CM12. Nice! :good:

Play with CatLog for a while to see how it works before you actually need it.

Forget that tutorial unless you are gunning for Michael's job or something. ;)
[Motorola Droid RAZR] Dwillian:
Hi [MENTION=3457922]stargo[/MENTION],

Using SafeStrap 3.73 I created a new rom slot 2, installed patched 11/29 nightly and small CM gapps (I still get a failed message when installing gapps even though they seem to work since I have access to google play store), wiped cache and dalvik cache, and rebooted. I was able to complete the setup without a force close, but as soon as google started restoring my apps I started getting continuous force close of com.android.phone (i.e., the force close appears almost immediately after I click OK on the force close dialog box). Since this makes it essentially impossible to get a logcat on the phone I installed eclipse and platform tools on my PC, then connected phone to PC in mass storage mode with debug enabled. I then rebooted the phone and I started getting com.android.phone force close almost immediately. I again enabled mass storage mode and granted permission for debugging mode, then I ran adb and executed the following command:

adb logcat > logcat.txt

Hope this helps. Please let me know if you need additional information, or if I need to do this a different way.

Thanks again for all your help.

Update1: logcat.zip(containing logcat.txt) attached. I also tried just installing the patched 11/29 nightly (i.e., no gapps) and I still get the force close.

Update2: [MENTION=4245858]Ohmster[/MENTION] suggested I provide a logcat file for the case with just the patched 11/29 nightly. I need to get some sleep right now, but I will do that first thing in the morning.

Update3: Attached logcat for install with just the patched 11/29 nightly.
[Motorola Droid RAZR] Ohmster:
Zip the logcat.txt file to "logcat,zip and attach it to your post since text files cannot be attached.

Although there are many ways to get him the file, if you zip it an attach to the post, he gets the file immediately instead of having to give you instructions and then wait until you post or send it later on. :)

EDIT:

That is, if you actually did get a "logcat.txt" file. Did it make a logcat.txt file for you? When I call the logcat command, either in a Terminal window (As root) or from a PC with USB cable, "logcat" produces a never ending stream of system message output until the logcat program is stopped. So for me, running either just the logcat command produces a never ending stream of text or running adb logcat > logcat.txt does not do anything and hangs on the screen until I use CTL-C to stop the process. Did you actually end up with a logcat.txt file Dwillian? :confused:

If you do not want or need my help, I will stay out of it for you dude. :o
[Motorola Droid RAZR] Dwillian:
I did get a logcat.txt file. My experience is the same as yours in that the cmd prompt does not return until I hit CTL-C, but the logcat.txt file is created. I think it is kept open and the phone keeps logging to the file until the CTL-C. I will zip the file and attach it to my post ASAP.