Database Info

[Q] Cyanogenmod 6.1.1 mms doesn't work

So I finally decided it was time for a new ROM after living with a Rooted stock for so long.I'm loving Cyanogenmod but with one issue. I cannot receive pictures from other Aria's... I got a picture from an iPhone but two other users that have Aria's sent me pictures and they simply says download of message was unsuccessful... I read about some setting changes with APN but that didn't seem to work with any of the changes I tried. Is this a known issue I somehow missed, a bug I should report somewhere, or am I just doing something wrong?

I personally don't know anyone else with an Aria...but I receive MMS messages all the time with no problem from many different phone...including other Androids. Don't know. I would try clearing data, both caches and try flashing again.

Yeah I have thought about reflashing since it was my first run at it with this phone but I didn't notice until a couple of days into having it, just got moved in! Oh well, that's the price for doing this kind of stuff. I was just curious to see if anyone else was having issues like I mine.

My opinion would be to wipe cache, wipe dalvik cache (advanced > wipe dalvik) and then reflash the rom. No need to WIPE data.

Well do u have mobile connection turned on? if I have it off I won't receive any mms
Sent from my Liberty using XDA App

I didn't turn it off... but I have received pictures from an iphone so I would assume that means its turned on. Getting ready to brswattt's recommendation to see if it fixes it.

Ok so I tried wiping the cache's and reflashing, still no dice... I even tried going in a resetting cache and data for the messaging apps. Its doing it both in the messaging app and hancent... any thoughts? Maybe a complete wipe?

I have the same problem. I can receive from iPhones and other phones, but not my wife's Aria. I had this problem since September, with every RC of CM6. I assumed it was a ID10T error, but now that I see otehrs with the same prob, maybe not!

Both myself and the wife have arias...both running cm 6.1.1 able to send and receive mms to each other
Sent from my Aria cm 6.1.1 using XDA App

I have the same. Prob but dun mind since..I using whatsapp
Sent from my Liberty using Tapatalk

Milx said:
I have the same. Prob but dun mind since..I using whatsapp
Sent from my Liberty using Tapatalk
Click to expand...
Click to collapse
Can you speak in English?
Anyway, have you guys tried changing the "Customer User-Agent" setting under the settings menu inside the SMS app? It spoofs the phone in to something else.

Tried the user agent, great idea, but it didn't work. I tried several different user agents...
@seanfinn - I think the issue might be Cyanogenmod receiving from stock Aria, since the two people that I'm having problems with are on stock ROMs but they can receive them from me with no problem.
I have noticed that even other Androids are working fine so its just Aria's... I would normally say forget about it and move on but the two people that I message the most are these two Arias - seems like that is how it always happens.

mattlezeay said:
I have noticed that even other Androids are working fine so its just Aria's... I would normally say forget about it and move on but the two people that I message the most are these two Arias - seems like that is how it always happens.
Click to expand...
Click to collapse
I think you are correct. My wife has a stock Aria, and that is the only phone I have trouble receiving from.

Issue with MikShifted-G v1.6?

I can't post to the ROM in the developers forum so I posting here. I just downgraded from GB last night and installed this ROM. I went today to update my PRL and it gets hung up after the update. When I click the OK box when done it goes to a black screen with the four bottom buttons lit. I can back out of it, but it will keep popping up telling me it is updated. Rebooted to get it to clear.

There really shouldnt be any issues with updating profile and prl, did you do a full wipe of system data and cache and also the dalvik cache?
Sent from my Supreme Shift using XDA Premium

Yes, wiped everything before installing ROM. Also having MMS issues, but that may be Sprint. SMS is fine though.

lancer1991 said:
Yes, wiped everything before installing ROM. Also having MMS issues, but that may be Sprint. SMS is fine though.
Click to expand...
Click to collapse
eh the mms issues come and go like usual i would tell you to update profile and prl but it seems sprint is doings some wonky things in your area give it a day or so and try it again just to make sure sprint isnt playing with the towers, i have been getting mms fine on Supreme and its a MikShifted-G base

Rather than starting a new thread, I'll add on here. The lockscreen icons have disappeared. I'm sure a restore has messed it up. It shows as 0 bytes under the installed apps. Before restoring the data they were there. Any ideas short of full wipe and re-install. David wipe and install didn't fix it.
Still no SMS.

Sounds to me like you've got either a bad flash, or the device wasn't wiped proberly. Try wiping and flashing the device according to THIS guide. See if it helps your issues.

lancer1991 said:
Rather than starting a new thread, I'll add on here. The lockscreen icons have disappeared. I'm sure a restore has messed it up. It shows as 0 bytes under the installed apps. Before restoring the data they were there. Any ideas short of full wipe and re-install. David wipe and install didn't fix it.
Still no SMS.
Click to expand...
Click to collapse
Restoring data is never a good thing and this is exactly why we try to push the issue so much with people that are new to rooting and flashing ROMS. Yes it saves you time in the short run so you don't have to re apply settings and login information and have to get to level 80 on all your games etc. Long run this is what happens system/apps start to go insane and the phone just will not act right, in this case a complete wipe and reflash is not only recommended, but needed in this case, and I hope I don't sound like a **** just wanted to be to the point you know
Sent from my Supreme Shift using XDA Premium

[Q] Trying everything to get group messaging

Hi guys--
My main goal is to achieve group MMS messaging within the native MMS app. I have a Razr HD Maxx currently on 4.1.2 (9.16 vzw update). My main goal is to get group texting to work correctly, however that might occur. I've essentially been attempting two different paths to get to that point.
My first idea was to use the CM10.1 mms.apk file and manually change the other framework files that needed to be changed in order to enable the group texting so it doesn't freeze up every time anything to do with MMS happens. I found details about how to do this on Touchwiz but not Blur. I tried the TW instructions anyway but nothing happened. Neither good nor bad, it just still didn't work.
My next thought was to install a 4.2 ROM that supports group texting. I spent a few hours with Safestrap, but basically I couldn't get the damn thing to boot any safe ROMS....it would just go to a black screen. I could always reset it and boot back to stock fine, but never could boot into any ROM slots.
Here's what I tried: Initial run-through: Downloaded, installed app, rebooted, created slot, installed, and attempted. No dice. Rebooted to stock, undid recovery, installed BusyBox (I was certain my lack of BB would solve the problem), unplugged the phone from charger (at the suggestion of another forum), confirmed root was working, reinstalled recovery, downloaded alternate ROM file. Back in SS, I more thoroughly created the ROM slot, then wiped data, cache, dalvik, and system, then installed, then tried again. Same issue still. I tried the same procedure in slot 4 for $#!+s. I tried wiping, I tried deleting and recreating slots, I tried re-downloading ROMS, etc. I couldn't get the thing to do anything other than show me a black screen after hitting continue when booting from a safe slot.
A few things I noticed that I'm not sure are relevant or not. The ROM's I attempted to flash were CM10.1, Vanquish Pacman, and Vitreous. Vitreous failed the MD5 check even after 2 downloads. On stock, my baseband version is reported as VANQUISH_BP_100730.081.64.09P. I'm not sure what it was before but I feel like it wasn't Vanquish and I'm wondering if something was actually done to the real file system? It still works fine, so I'm not sure if any harm is being caused. When I try to wipe the data partition, SS says it actually failed. At first I just tried it again but I didn't worry much about it because I figured it was empty anyway (trying this between creating the slot and installing the ROM.) But when I browse although I can find the system partition in safestrap\rom-slot1 I have no idea where the data partition even goes...I can't find it anywhere to wipe manually.
So SS is baffling to me. I'm sure a few files could be modified relatively easily to bring group texting to 4.1 but I'm not sure how to do it. Both my solutions are giant fails right now. Anyone have any ideas to help me?
Thank you!!

empoweredh22 said:
Hi guys--
My main goal is to achieve group MMS messaging within the native MMS app. I have a Razr HD Maxx currently on 4.1.2 (9.16 vzw update).
Click to expand...
Click to collapse
I'm pretty sure that the HD has group messaging. In fact, when i send a SMS or MMS to a group, I get a little blue bar that tells me it's a "Group Message." Am I seeing something that you're not, or am I totally wrong?

Have group messaging and it works just fine. Stock firmware.
Sent from my DROID RAZR MAXX HD

Thanks guys. I was hoping to accomplish that with AOSP messaging as opposed to blur messaging. Not possible then?
I like AOSP messaging better because it's ugly and more importantly because it supports emoji, extended notifications, and quick reply as well as long messages and the emoticon key on the keyboard.

[Q] android.process.acore has stopped, on ALL lollipop roms, after complete wipe!

Okay, guys, here's the problem. I have been pulling my hair out for days over this. On any Lollipop ROM I install, no matter what combination of gapps and AOSP ROM I install on my OPO, after completely and totally formatting caches, system, data, and /data/media, the problem persists:
Always after logging into an account, but not always the same one, I start to get an error "android.process.acore has stopped." It happens every few seconds and renders the device unusable. I have tried every fix I could find online, including wiping contacts storage data, contacts data, etc. I have formatted my phone several times, and each time the problem comes back. It only stops when I disable Contacts Storage in settings, which then in turn disables all contacts functionality.
This is getting totally ridiculous, and the only thing I can think of is that the AOSP version of contactsprovider.apk is totally corrupt. Any ideas?

I have the same problem... Did you succeed in resolving it?

flolep said:
I have the same problem... Did you succeed in resolving it?
Click to expand...
Click to collapse
Somewhat. The issue manifests itself when Facebook is synced with your contacts, and you use Facebook OAuth to sign into another app. For whatever reason, this causes the contacts app to go nuts, and the only way to fix it once it happens is to get rid of the Facebook app. It's a bug that is quite beyond me to fix. There is a modded Facebook apk floating around somewhere, that has had permissions modded so it's not allowed to use your contacts or register as an account in your phone. That works. It also works if when you install a new ROM, you sign into any apps that use your Facebook login before you install the Facebook app, that way you log into them with the browser and they never talk to the contacts app. Once you have installed the Facebook app, DO NOT EVER click "Sign in with Facebook" in any app on your phone, or you're screwed again.
That's pretty much what I've come up with thus far. Hope that helps.
EDIT: Here's the link to the thread with the modded Facebook apk: http://forum.xda-developers.com/showthread.php?t=2333637

I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.

prometheus1010 said:
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
Click to expand...
Click to collapse
It happens for other phones users... See here : https://productforums.google.com/forum/m/#!msg/nexus/Ip-hdFEQccY/OSFCz4Qj59oJ
Thanks for your partial solution @jkotzker... For me it's a no go because I am a big facebook user and I can install app with Facebook account linked at anytime... It's really really annoying to not log with Facebook account if the Facebook app is installed I don't know what to do... I tried everything like you.

I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help

marcviado said:
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
Click to expand...
Click to collapse
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app

pablo1215 said:
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I didn't find one...
I talked about this problem in xda temasek rom thread and ak kernel thread without success. I even sent a message on official cyanogenmod website, with last crash and logcat attached. No success. The problem happened in 2012 too... And since then, Google didn't have a solution for it.
It seems that Google is finally aware about this problem and the correction could arrive in "a future version"... Well. I want it now... Indeed, there seems to be only to increase the buffer transaction between applications and contact storage from 1MB to 2MB for example, to have it corrected. But no dev wants to do it because the problem cannot be reproduced! And it's rare! But we have it! It's incredible to have it back after a full wipe... And happening randomly, just after a random sync between application and Android system...

Any more updates on this issue/ anything else we can do to get this resolved? Even my partial, temporary solutions have stopped working, and I am getting really frustrated.

Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.

t3chn0s1s said:
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
Click to expand...
Click to collapse
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.

Aditya Srinidhi said:
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Click to expand...
Click to collapse
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.

t3chn0s1s said:
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
Click to expand...
Click to collapse
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you

Aditya Srinidhi said:
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Click to expand...
Click to collapse
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.

t3chn0s1s said:
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
Click to expand...
Click to collapse
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.

flolep said:
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
Click to expand...
Click to collapse
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?

Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.

t3chn0s1s said:
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Click to expand...
Click to collapse
No. Not yet. But. Well. CM12 is already good functionality wise. And with this bug disappeared it's really a happiness.
---------- Post added at 12:42 AM ---------- Previous post was at 12:39 AM ----------
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Yeah, yeah. Already tried... Lol. I think I tried every single advice given in all the Android forums of the world on this bug lol. Well. Google finally heard us. +++

tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Neither worked but thanks for the suggestion. I did find a Facebook work around. Found the Lite Version via a Google search (since its technically not available in the US) , installed it and it works fine. No android.process.acore FC's or repeated pop ups.

Update: This problem reared its ugly head again on CM12 and I ended up having to uninstall Twitter this time. So, now I'm on CM12s and as soon as I logged into my other Google account user Boxers email app I got the android.process.acore crash again. Uninstalling that app immediately stopped it. God I can't wait for 12.1 for our OPOs. This problem is absolutely ridiculous. I can't take this anymore. I really can't use ANY social media apps unless its like Tinfoil for FB or Twitter. I don't have any connected accounts except Google & Cyanogen.. Which I truly can live without but... Just for the hell of it.... Knowing I have a backup and I'm about to clean flash the latest stock build I tried to add Waze and it caused the crash all over again. Uninstalling Waze didn't help. I shouldn't have to deal with this. Only way to stop it is to disable contacts storage. Once it begins it doesn't stop. Effing Google with their half baked crap.

Help! Apps constantly crashing. have to reboot phone multiple times a day

Hello all,
Having a problem with my unmodded XT926. Apps are crashing frequently during the day. Phone is usable but I get messages saying that Google Play has stopped working or Fleksy has stopped working. Keyboard app stops working multiple times a day. At first I was using the native keyboard app, but for the last three days I switched to Fleksy to see if that worked better but no dice. When the keyboard app crashes, I have to force reboot the phone. Do I need to reload firmware or something to get my phone stable again?
Phone has never been rooted (company phone). All I've ever done was disable some apps listed on the Xt926 Bloatware post on this forum and played around with Nova Launcher and Tasker.
XT926
KK4.4.2
182.46.15
kernel 3.4.42-gbd361ac
kernel date Jul 29, 2014
Any help/guidance is appreciated. Thanks in Advance

Boot into recovery and wipe cache. That has helped me in the past

Guapo613 said:
Boot into recovery and wipe cache. That has helped me in the past
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately, it has not resolved my problem.

You can always try to enable certain things that you have previously disabled to see if that helps. I'm not sure what you have disabled but what works for some, may not work for you.
Since your rooted, you can also use Titanium Backup to freeze apps.
Are you familiar with RSD Lite?

Guapo613 said:
You can always try to enable certain things that you have previously disabled to see if that helps. I'm not sure what you have disabled but what works for some, may not work for you.
Since your rooted, you can also use Titanium Backup to freeze apps.
Are you familiar with RSD Lite?
Click to expand...
Click to collapse
The app crashes were happening prior to me disabling programs. I have tried enabling everything again and the results are the same. Most of what I disabled are the bloatware apps (Amazon, MC3, Real Racing, Spotify, etc.)
I am not rooted.
Have never used RSD Lite but will look into it.

You can try going into the "Apps" menu in settings and clearing the caches for individual apps. Some of them get quite large, and the cache only stores temporary data for reasons of convenience.
You can uninstall apps you don't really need (some of them run in the background and use up memory, look in "Running" apps in the system-apps listing).
Tasker is always running in the background; do you really need it?
You can try going into developer options (go into "About phone" in settings, then tap the build number many times) and reducing the background process limit.
If all else fails, you can do a factory data reset, or even more drastic, you can reflash the stock firmware.
Also bear in mind that this is an old device, and current apps expect devices with more memory and faster processors. Every time an app is updated with more features, it uses more memory on your phone and makes it run slower.

CryptZero said:
The app crashes were happening prior to me disabling programs. I have tried enabling everything again and the results are the same. Most of what I disabled are the bloatware apps (Amazon, MC3, Real Racing, Spotify, etc.)
I am not rooted.
Have never used RSD Lite but will look into it.
Click to expand...
Click to collapse
Backup important data (pics, music etc.) and try a factory reset. This should cure all you problems.
If this process cures your phones problems, you can root your phone if you like. Look at this thread: http://forum.xda-developers.com/droid-razr-hd/general/index-motorola-droid-razr-hd-2015-t3167557

Factory reset was done prior to my post on this board.
Don't think tasker is the problem. After the reset, I manually added apps one or two at a time... Tasker was the last one added, but crashes were happening before that.
Previously, I had been using tasker for about 6 months with no crashes at all.
Right now, I'm leaning toward flashing the firmware. My company has put a temporary ban on issuing droid phones due to that big exploit that was discovered a few weeks ago. I hate iPhones and am trying to keep this one running until they lift the ban.
Thanks for all the help so far. I'm open to trying anything to just get this phone back to a stable condition.
Sent from my DROID RAZR HD using Tapatalk

so here is the latest.
Phone rebooted itself, after an app crash and is now stuck on the Droid Eye bootup screen thingy...
Force reboot doesn't fix it. Took it to Verizon store downstairs for sh*ts and giggles and they were no help. No surprise there!
Does this sound like a hardware issues to you guys?
Guess I'm going to have to bite the bullet and get an iPhone from my company as a replacement.. unless someone on here has some miracle suggestion.

It sounds more like a software issue to me.
I would see if you can get into fastboot or ADB and flash a fresh copy of the firmware before giving up entirely.

A full flashing of the firmware via RSD Lite will probably fix your issues

So I was able to Flash firmware to 183.46.15 and I also rooted the phone using sd_shadow instructions. Took me quite a while to actually download a working firmware file. The only working link I found was here: http://download1520.mediafire.com/rnbmstjwc1wg/du1p88ti1esd5fk/VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml.zip
I guess I'll see if the phone is any more stable over the next few days.
Thank you all for the suggestions. Much appreciated!

Was this ever resolved?