yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] Ohmster:
I haven't switched to the new gapps yet and am trying to get Dwillian on firm ground with a stable, working, upgradeable rom so that he can play with everybody else. What I am showing him is a method that is tried and true. Once mastered, it is a logical jump to bigger and better things. As of yet, our poor friend is deeply troubled with just getting *any* install of CM11 to be stable, responsive, and upgradeable.
[Motorola Droid RAZR] stargo:
I'm pretty sure this bug got introduced on 2014-11-11 into CM. I'm on it.

Just to make sure, your crash looks like this?

com.android.phone threw java.lang.NullPointerException
java.lang.NullPointerException
at android.telephony.SmsMessage.getOriginatingAddress(SmsMessage.java:553)
at android.provider.Telephony$Sms$Intents.getNormalizedAddressesFromPdus(Telephony.java:1167)
at com.android.internal.telephony.InboundSmsHandler.processMessagePart(InboundSmsHandler.java:742)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:371)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.os.HandlerThread.run(HandlerThread.java:61)

This affects all CM devices on CDMA-networks as far as i can see.

Cheers,

Michael
[Motorola Droid RAZR] morr22066:
That looks like it. Last night I had deleted my as slots, uninstalled recovery, uninstalled safestrap and created new slots and started over with a fresh install on the 11-23-14 nightly. It seemed to be running well but by this morning I got the same force close that I have been getting since 11-11-14. It is nice to hear that it is a known cm11 bug and that it is not my phone.
[Motorola Droid RAZR] Dwillian:
Thanks for the advice.

I deleted and recreated rom slot 1 (using partition sizes of 700/2000/300 Mb as recommended). Then I installed the 11/22 nightly and the 11/21 mini-modular PA-GAPPS (current release). The latest PA-GAPPS does use the 2.0 installer, so I did create a .gapps-config file that contained just the debug keyword, but no other options (the 2.0 installer now includes the Play Services update module and AFIK there's no way to turn that off). I then wiped cache/dalvik and rebooted. Unfortunately, I immediately got the com.android.phone process force close before I could even select English on the Welcome to CyanogenMod screen. So, no joy :crying:

Curiously, I am not having force close problems with the CM12 alpha release using PA-GAPPS micro package (5.0 version) in slot 2. I will try using the micro package with CM11and see if that works any better.
[Motorola Droid RAZR] Dwillian:
Deleted.

---------- Post added at 12:01 PM ---------- Previous post was at 11:56 AM ----------

It looks like the bug has been identified and a fix is in progress. Thanks everyone for the help on this issue.
[Motorola Droid RAZR] Ohmster:
Michael please patch/fix the current CM11 NIGHTLIES

[MENTION=3457922]stargo[/MENTION]

Michael,

It seems that almost all of the current CM11 NIGHTLY Builds are either crashing or introducing other nasty bugs like severe lag, black screens, App FC issues, and very low signal blocks. I did see your post on this issue, Post #6858 and you seem to be on top of this. Since I am not getting outright crashes of the OS but am getting the other issues mentioned, are there logs I can collect to assist in the debugging process that you might find useful.?

E.G.: You posted some "code" to illustrate the issue as such:

Where are you seeing, getting, or us the user supposed to see this "code"? Is this a dmesg or CatLog with filter? Any particular filter keyword one would use to extract useful build issues from the raw log that you can suggest?

After your post you did mention patching the issue and that you would get on it. Is this the patch to fix the poor rom issues as posted in the 11/23 Changelog?

ril: implement a new motoOmap4 RIL which unsupports CB/CellInfo (android_device_motorola_omap4-common)

I will update over 11/07 to 11/24 to see if you commit made any difference. Is there anything else to look out for or any type of log you would want or could use?

Thank you. I know you are busy with Android L and we all support you 100% in your amazing efforts and accomplishments. But, *somebody* has to "mind the store" for CM11 users that depend on their phone for daily use and cannot afford risky builds resulting in missed appointments, lost phone calls, loss of navigation, or a phone that just does not work. Thank you, thank you. ...THANK YOU MICHAEL! :highfive:

...we're not worthy, we're not worthy!

[IMG="Wayne's Word, Wayne's Word. Party time, excellent!"]http://i.kinja-img.com/gawker-media/image/upload/s--5GuBJgZd--/fdlqovpvmwwt7kymipts.gif[/IMG]
[Motorola Droid RAZR] kennethbass:
Anyone experiencing total mobile network loss? Does anyone know how to fix this issue?

My baseband and imei are showing up as unknown and apn settings will not save.

Someone please help me resolve this.
[Motorola Droid RAZR] sharptv:
i don't you your lte chip is broken, you've probably flashed mentor's gsm patch or it wasnt probably cleaned up. Try replacing moto-ril-multimode.so in /system/lib with the one you extract from any of the later cm11 nightlies, and check your baseband version again. Make sure you set the correct permission
[Motorola Droid RAZR] Ohmster:
Um, [MENTION=3423220]sharptv[/MENTION] gave you good advice. Whether or not you understand it may be a different issue. :p

[MENTION=6143712]kennethbass[/MENTION] you are a new member and need a quick "Heads Up" on XDA Forums to get what you need...

When asking questions like this, please provide "basic" information about your device. Such as:

Manufacturer: Motorola, Model: XT912 -XT910, Location: Budapest Hungary or Hartford Connecticut, Radio: CDMA or GSM, Carrier: Verizon, US or what you have. Without telling us this stuff, the help you get may be totally incorrect or you get little to none because we don't know what you have. To avoid having to put this stuff in every post, go to your XDA Control Panel, then Signature, and write this information in your signature that will show on every post, like mine below. While you are at the Control Panel you can also edit your Profile so that others can see your location (Need not put that in signature, it should go in your Profile.), name, interests, and what devices you have. It makes it *much* easier to help you this way. :)

Next, the Thanks Button. If someone helps you, be a good member and tap the word "Thanks" next to the post you found helpful. It is a small reward system that XDA has to encourage others to help you and give you a meaningful way to say thanks to the member. You will also make friends fast this way when you express your gratitude for the help given. ;)

And last, there are a LOT of people flashing the new Alpha CM12 rom in this CM11 thread, although there is a thread just for the new CM12 for our phones. Be sure to tell us if you are using CM11 or the new CM12 Alpha. CM12 questions go to the link above in orange. XDA class is over. :D

I don't use GSM in the US so that kind of information others could help you with such as [MENTION=3423220]sharptv[/MENTION], [MENTION=5057697]welder73[/MENTION], or maybe [MENTION=3313632]ChungHung.Chen[/MENTION]. These members have XT910 phones if that is what you have, I don't know because you did not say.

One way to fix a rom gone bad is to reboot to Safe Strap, go to Wipe, Advanced, and check

ONLY cache, dalvik, and system

. Slide finger to wipe these partitions. Then tap HOME and INSTALL, go find your cm11 zip file, then "Add another zip" and find your pa-gapps file. Swipe to flash them and reboot to System. You will not lose your stuff this way and it will fix any problems created in the system. Make SURE you have the CM11 install zip file AND your pa-gapps file on the phone before wiping and doing this!!!

If you fill in some of your information, it will be a LOT easier to help you in the future. Good luck buddy! :good:
[Motorola Droid RAZR] kennethbass:
My apologies. I have been working on said phone for 3 weeks and I am frustrated.

I have the HTC one m7 bought from Verizon. I have a ST SIM card. I'm in the US.

I can not get ViperOne, InsertCoin, and Android Revolution HD to get out of bootloop. LiquidSmooth and Cyanogenmod are the only ROMs that will install but both turn up network issues.
[Motorola Droid RAZR] Ohmster:
Alright Kenneth, that makes a little more sense. But, your issue is that you are now in a Motorola Droid Razr thread where we all own such devices and all of us use CM11, other roms like LS, and are experimenting with CM12 for our devices. It makes sense that "If you are a zebra, go where zebras go to get food, shelter, and the best hunting grounds". In other words, you are in the wrong place, my friend. To get the answers you seek for your particular device, go and subscribe to the Verizon HTC One Android Development thread.

Click the orange link above to take you there. Not that anyone here does not want to help you, but we do not own such a device and therefore, would be of little help in getting you what you need.

And the three things I mentioned before are very important if you plan to stick with XDA Forums. Put something in your profile. Put your device specifics in your signature so you do not have to list them in every post or wait for someone to "ask what you have" in order to help you. And, to officially Thank people that help you and click that Thanks button on the BOTTOM LEFT of the post they have made for you.

The link I gave you above is the right place to get the help you need. Good luck, Kenneth. :cowboy:

TIP:

The best thing you can do when you get to the new thread is explain your device and issue, then ask if this is the correct forum for these questions and if not, could someone please direct you to the proper thread. I sent you to the closest thread I can find for you, but sometimes there are sub-threads that can be of more help. It does not hurt to ask. ;)
[Motorola Droid RAZR] d.casper.b:
Now this is how we help people here in this thread!

:thumbup:

Generated on a RAZR Maxx (XT910) using XDA's free mobile app.
[Motorola Droid RAZR] farangcm:
Strange, I don't have these problems on my XT910, in any of the recent CM11 nightlies. No black screens or severe lag, even the next day. My experience is the same as your initial reports, all smooth and stable. I know there have been others with these same problems, even on an XT910 RAZR MAXX, as I recall. Am I just lucky?

My only problem with recent builds is still battery life. Even running Greenify free and DS Battery Saver, the battery goes down 2%+ per hour in standby. When I test the build, the battery drops 10-20% per hour. CM12 pre-Alpha seems to have better battery life than CM11.

Allen
[Motorola Droid RAZR] d.casper.b:
OK, I had to bring up this old post because, like GTiceman, I could also (at this stage) get the phone to rotate when in dock (while the display's auto-rotate was disabled).

The good news was that, although CM11 doesn't include the dock-app, it actually knew the phone was docked. The display rotated because it knew it was docked. How do I know? Because I tested by enabling "Daydream" to activate only when docked - and it began to daydream as soon as it was docked - not while charging nor while screen-off.

This suddenly stopped working and I've never seen it again. I don't understand why. I have bothered this thread before about this, but no one really took much note. It's not vital, but it's just something small that I'd like to see again.

(And that's April 2014, not November 2014)

Generated on a RAZR Maxx (XT910) using XDA's free mobile app.
[Motorola Droid RAZR] Ohmster:
Could be Allen. Everyone seems to have different issues or some, none at all. I have been lucky being in the "not at all camp" for a long time. Maybe my luck just ran out? :p

Michael did find a bug in the builds that would cause crashing and other issues in 11/14 and up, IIRC. He posted about it so I got my 11/07 build all freshened up and am now trying out 11/23 which should include Michael's patch. :fingers-crossed:

Thanks for the report. That gives others a better perspective on the build status. When they conflict like this, it means the build may be good for some, maybe not for others. I was "pushing it a little bit" with navigation, Bluetooth, and streaming audio. Usually that does not cause the severe lag unless I try to use the phone at the same time. Perhaps that could be it, but I am still puzzled by the numerous low signal pockets in my area where none have been before. Oh well, keep on Truckin' (Testing!)! :D

---------- Post added at 04:42 AM ---------- Previous post was at 04:41 AM ----------

Thank you for the kind words, Danial. That is exactly right, this is how we do it and we, are darned good at it! :D

BTW, I do not have a dock. Cannot help you with that one my friend. But [MENTION=838017]sherri[/MENTION] does use a dock. Perhaps if you can attract her attention, she might shed some light on the subject. :)

...I try to attract her attention all the time, but she is clearly out of my league. LOL! :laugh:

I do, however, respect the heck out of her and pay rapt attention when she does share with us. ;)
[Motorola Droid RAZR] stargo:
Nope, that patch is for a different issue, mostly for GSM-users where the modem sometimes just crash when configuring CellBroadcasts. The former solution was to manually delete CellBroadcastReceiver.apk after each flash...

The fix for com.android.phone should be: http://review.cyanogenmod.org/79233

Cheers,

Michael
[Motorola Droid RAZR] sherri:
I am not out of anyone's league, [MENTION=4245858]Ohmster[/MENTION]. I appreciate the flattery though! And since this is a public forum, I'll keep my private thoughts private. ?
[Motorola Droid RAZR] Ohmster:
That was a term of admiration for the treasures of experience you have, help that you give, and that fact that you are "Super Mom", amazingly active to the likes of which I could only imagine. I never in my life meant to make you uncomfortable, Sherri.

Public Forum, Private Thoughts. Got it. Truck on girl and thanks you for everything! :good:

---------- Post added at 07:44 PM ---------- Previous post was at 07:14 PM ----------

Thanks for clearing that up, Michael. I guess we will just have to work out ways to lighten the load on our aging devices to maintain performance and prevent lockups and crashes. So far, I am "getting there", but the new series of roms seems to present a new challenge. Some times the roms are "a bit off". Maybe this is one such period. Thanks for your efforts, buddy! :good:
[Motorola Droid RAZR] ChungHung.Chen:
Test report of CM11-20141123-umts_spyder

<< Basic Info >>

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

Note: PA-GApps was flashed manually because it may corrupt my stock slot from CyanDelta, still checking.

<< Report >>

Tested Period : 2 days

Tested Item : Phone call / SMS / Mobile data / WiFi / GPS / HDMI / MX Player / YouTube / etc.

Tested Result : Good, I will keep this version for recovery use.
[Motorola Droid RAZR] Ohmster:
Thank you Mr. Chen. That was an excellent report. If you do not mind, I will follow up with my own report so far. Nice format by the way! :D

<< Basic Info >>

XT912 (spyder) / CM11-20141124 / pa-gapps-modular-mini-4.4.4-20141121-signed.zip / From CM11-11/07->11/24 by manual wipe of /system, /dalvik, /cache. Installed CM11 & pa-gapps in Safe Strap. Rebooted to system. Set BetterBatteryStats to system app, updated AdAway, tapped installl/update in Xposed Framework and rebooted to system.

<< Report >>

Tested Period : 1 day

Tested Item : Phone call / SMS / Mobile data / WiFi / GPS / MX Player / YouTube / CM11 File Manager / Bluetooth Audio / Streaming Audio / Navigation / etc.

Tested Result : Good, I will keep this version in use for continued testing and report any anomalies or sustained good performance.
[Motorola Droid RAZR] farangcm:
XT910 (umts_spyder)/gapps-kk-20140924-minimal/Nightly 141125->141126/CM Updater

I just noticed a small problem with the 11/26 nightly. When I changed the grid size of the home screen from 5x5 to 6x6, there was no change in the displayed home screen until I rebooted. On earlier builds the change was immediate.

Allen
[Motorola Droid RAZR] Dwillian:
I'm still getting the com.android.phone java.lang.NullPointerException following OTA update from 11/07 nightly (which was working reasonably well) to 11/27 nightly. Just wondering if this is still a known issue or if something else is wrong on my phone.

Thanks
[Motorola Droid RAZR] Ohmster:
[MENTION=5362796]Dwillian[/MENTION] what does that mean? Like, I see that window of code that Michael posted. Is that what you are seeing, if so, where are you seeing it. Or are you getting toasts or FC popups telling you this? It looks like Michael is pulling stuff out of the dmesg or system log and using a filter word to get the results he wants. But it is not explained where this information is being viewed. What do you see and how do you see it my friend?

I am on 11/26 right now and it seems reasonably okay for a day. I get the feeling that these roms might be "creepers" where they seem alright on day one and as days go by, they begin to lag a little bit. Not terribly bad like some past roms, but at least somewhat. No doubt that 11/07 is/was such a fantastic rom that you could install that one and leave it alone, like, "forever" until CM11 becomes final. I think it really is *that* good and always have that backup ready to restore. I do restore and use it once in a while so I can update my apps and then save it again and delete older backups. But not the original, pure backup. That one you should always save.

I am going to jump to 11/27, let's look at Changelog. Oooooh! Michael *did* put an omap4 commit in this build, check out his comment:

Revert "omap4-common: enable swapping to zram"

Seems to induce lag for many people.

Anything that might reduce lag in the current rom set is for sure my friend. I am on it! Let me know how it is going dude! :good:
[Motorola Droid RAZR] ChungHung.Chen:
I've seen this changelog too. Updating now and will report back after few days.
[Motorola Droid RAZR] Ohmster:
Awesome Mr. Chen. You and I are applying the same update at the same time, Thursday, November 27, 2014 @ 3:37 AM. You have the umts_spyder and I have spyder. So this will be an interesting comparison. Let's do it and see what happens. I hope not to see another "creeper rom" this time. (When a rom starts out well and degrades as days pass.)

Check back with published results in a day or two. Thank you Mr. Chen. :good:
[Motorola Droid RAZR] Dwillian:
When I get the android.phone.com process force close window I click on report and the code that Michael posted appears.

The phone is unusable when this happens since the force close window reappears nearly every time I touch the screen.

The OMAP4 update in the 11/27 nightly does not fix the problem.
[Motorola Droid RAZR] Dwillian:
The problem is that every time I touch the screen I get the FC. So, it's impossible to try any of the fixes suggested.

A clean install of just 11/27 nightly and PA GApps still has continuous FC of phone process. So, completely unusable. No joy with OTA update from working 11/07 to 11/27 either.

At present I'm stuck with my 11/07 backup with no path forward.
[Motorola Droid RAZR] ChungHung.Chen:
According to this stargo's post, this bug is only in XT912(sypder) since 11/11, so 11/07 should be ok. And from another's stargo's post, the fix of this bug is not in nightly build yet.

Return to 11/27 build, the changelog of ZRAM is for performance and it's worked as I expect. No random lag ( no response for 1~2 seconds ) last night, including some light games (Paper Toss, etc.) and HDMI for video over two hours. Will test more and report back in few days.
[Motorola Droid RAZR] Ohmster:
Alright man, I get it. I am really trying hard for you, Dwillian. I want you to "come and play" with the rest of us, and boost my own helper status at the same time. You have 11/07 and can use that. We really need BIG GUNS for help. Let me try a "Hail Mary" pass to see if it works.

[MENTION=5362796]Dwillian[/MENTION] Try to grab a dmesg if you can off that phone! In Terminal Window enter command:

dmesg > /sdcard/dmesg.txt

This will put the dmesg output in a text file called "dmesg.txt" on your internal sdcard. Save that text mesage to PC or have it ready to send, post, or give to Michael if we can get his attention.

[MENTION=3457922]stargo[/MENTION] Michael, please take a minute, review Dwillian's last post here, see how hopeless it is. Dwillian will try to get a dmesg for you. Is there anything at all that you can suggest to get him out of this endless "com.android.phone process stopped unexpectedly" crash message loop? He can restore backup or install cm11 Nightly Build 11/07 only but cannot update or install a later version. His reply to your question can be found here in Post #6879. Thank You Michael. :fingers-crossed:
[Motorola Droid RAZR] Dwillian:
I recreated rom slot 2, installed CM11 11/27 nightly and stock PA GApps, wiped cache and dalvik cache, rebooted. Then I worked through hundreds of com.android.phone process force close until I could get to the terminal window and type the dmesg > /sdcard/dmesg.txt command. When I entered the command I got a permission denied error (unfortunately the window went away before I could copy down the exact message).
[Motorola Droid RAZR] ChungHung.Chen:
Hi [MENTION=4245858]Ohmster[/MENTION] and [MENTION=5362796]Dwillian[/MENTION],

We already have got response from [MENTION=3457922]stargo[/MENTION] in his post at #6858 and post at #6873. And I've re-posted it just above Ohmster's post #6887. You may take it a look. Currently the FC issue in XT912(spyder) has not fixed yet. The fix from stargo's post should be http://review.cyanogenmod.org/#/c/79233/.
[Motorola Droid RAZR] Ohmster:
Thank you Mr. Chen. I knew about this for a couple of days, I thought the patch was committed and merged already. I can see now that it isn't. I really feel bad for Dwillian, he just cannot get a break like my2cents with his phone. Except either Dwillian has been quite about this for a very long time, or something has changed for him. I am still on 11/27 and this rom is so far, absolutely "dreamy" nice. I cannot understand why Dwillian cannot get a stable install by flashing totally clean like he says he did. This just does not make sense!

Are you still testing 11/27? How is it so far for you my friend?
[Motorola Droid RAZR] stargo:
Hi,

I've built an image for you with the patch applied: http://droid.cs.fau.de/cm-11.0/test/

Please test it and tell me if it works, so I can +1 the patch in gerrit so it gets merged :)

Regards,

Michael