Develop Bugs

[Q] Messaging (and DRM content) processes stopping unexpectedly on boot?

Today I took a picture with my phone and my phone froze up shortly after viewing the picture for some odd reason. So I soft reset it with a battery pull. When I started my phone back up I received a few error messages. The first one was that the DRM Content process had stopped unexpectedly (I think this was happening before my phone froze up). The second one was that the Messaging process had stopped unexpectedly, and the third was Handcent stopping unexpectedly.
After this happened I tried opening up Handcent, to which it displays the same force close error for a split second and then automatically closes. I uninstalled Handcent and tried opening the regular Messaging application, to which it displays some sort of force close error for a split second and then closes.
I was running the SyndicateROM Frozen 1.1.0. I tried updating to the ACS SyndicateROM Frozen 1.1.1 to see if it would fix my problem. It didn't
Does anyone have any suggestions on how to troubleshoot this?

You had journaling off. You can't reboot the phone without powering off or you wind up with data corruption and force closes. You need to reflash your rom and then use the re eable journaling zip in the development section. Also it wouldn't hurt if you researched things before posting, there have to be > 50 posts about this.

NateTheGreatt said:
Today I took a picture with my phone and my phone froze up shortly after viewing the picture for some odd reason. So I soft reset it with a battery pull. When I started my phone back up I received a few error messages. The first one was that the DRM Content process had stopped unexpectedly (I think this was happening before my phone froze up). The second one was that the Messaging process had stopped unexpectedly, and the third was Handcent stopping unexpectedly.
After this happened I tried opening up Handcent, to which it displays the same force close error for a split second and then automatically closes. I uninstalled Handcent and tried opening the regular Messaging application, to which it displays some sort of force close error for a split second and then closes.
I was running the SyndicateROM Frozen 1.1.0. I tried updating to the ACS SyndicateROM Frozen 1.1.1 to see if it would fix my problem. It didn't
Does anyone have any suggestions on how to troubleshoot this?
Click to expand...
Click to collapse
Download enable journaling from here:
http://forum.xda-developers.com/showthread.php?t=1071723
Flash it after you reflash your rom.

I flashed the reenable journaling zip after reflashing my ROM. The DRM Content force close error still pops up when I boot up, and my Messaging is still crashing :/. What am I missing? Or could there be another problem?

NateTheGreatt said:
I flashed the reenable journaling zip after reflashing my ROM. The DRM Content force close error still pops up when I boot up, and my Messaging is still crashing :/. What am I missing? Or could there be another problem?
Click to expand...
Click to collapse
Have you tried a different kernel? Or something you are restoring from Titanium or Mybackup is causing.
I would start from scratch go back to stock, reroot with cwm 3.0.2.5, d/l ext4 conversion here http://forum.xda-developers.com/showthread.php?t=1109362, flash ext4 conversion, flash Frozen 1.1.1, flash journaling enable. Do not restore anything see if you still have the issue. If not then something you are restoring is causing your issue.

I don't have Titanium or Mybackup. The only backups I have are within CWM, made from flashing my ROM. I will try what you suggested, thanks.
Edit:
To go to stock, do I just wipe data/factor reset from CWM? Also is there any way to do what you said while still retaining all of my contacts/texts? I cannot lose my SMS history. There is valuable information within.

NateTheGreatt said:
I don't have Titanium or Mybackup. The only backups I have are within CWM, made from flashing my ROM. I will try what you suggested, thanks.
Edit:
To go to stock, do I just wipe data/factor reset from CWM? Also is there any way to do what you said while still retaining all of my contacts/texts? I cannot lose my SMS history. There is valuable information within.
Click to expand...
Click to collapse
Mybackup does txt and sms backups. Make sure you do a nan backup also just in case. You need to odin back to stock. Go here for step by step
http://forum.xda-developers.com/showthread.php?t=773032&highlight=odin+stock

Okay, I tried a bunch of SMS backup programs to no avail. Every one I tried would either crash or throw an error when it tried to back up my text messages.
I went back to stock, wiped my data/cache/system, and then flashed back Frozen 1.1.1 again. Everything worked fine until I tried recovering my data. The Messages process crashes again after recovering my data
Is my SMS history unrecoverable?

Is sms crashing or just the back up of the sms? What are you using to back up and recover your txt?

tazfanatic said:
Is sms crashing or just the back up of the sms? What are you using to back up and recover your txt?
Click to expand...
Click to collapse
The whole reason this started was because my SMS messages application started crashing. I am trying to recover my texts. I tried using 5 or 6 SMS backup utilities, but to no avail. I didn't try anymore because I figured none of them are going to work. Something in my SMS history is borked :/

Thinking the same thing sorry. Not sure if someone else has any ideas. Do you have a nan backup from before the issue started? Yeah you might lose some txt but not all.

[Q] I fixed permissions in CWM... now my phone is going haywire!

I just updated to ACS SyndicateROM Frozen 1.2 from CWM. It updated successfully. Everything is great... until I had a bright idea to go into CWM and select "Fix Permissions".
Now, the phone successfully boots up and into the ROM. However, all the apps are going haywire! Everything keeps force closing. Nothing will work long enough before it force closes. I can still lock the phone and shut the phone down from the ROM, but I'm stuck. What do I do? HELP!!!

WHEW! Ok, it worked after I went back into CWM and did fix permissions again. BUT, a bunch of apps are still force closing whenever I load them up. Swype and Google Frameworks keep force closing on their own.
How can I fix those issues? Go into CWM and do it again?

Depending on the number of apps you can just goto settings -> manage applications -> wipe data
If its more than a few just reflash the rom or load a recent nandroid backup.
Sent from my frozen Syndicated Beast...

Good news is that I think I got everything back to normal. I went back into CWM and did the Fix Permissions 3 times in a row. Except my contacts are all gone. Luckily, I have them all saved to my Google account. But, for some reason they won't sync. Any ideas?

[Q] MMS not working, closes with "Unfortunately, Messaging has stopped."

Need help with MMS. The app stopped working and I am unable to receive or send MMS. When I try to open the MMS app it opens, but the main body area is black, then it crashes and closes with the "Unfortunately, Messaging has stopped." error.
I'm not sure when this exactly happened. I was on the stock rom, then used the non-flash counter root method and stopped without installing CWM. I thought everything was working properly and I did some data restores of my Titanium back-up. The later might have been the cause of the problems, but I have read that a this issue comes up with not clearing the cache when flashing a new rom (didn't do this, just odin'ed a root injected rom). I'm travelling so I am very hesitant to do a factory reset or new rom flash.
I also had the Unfortunately the Outlook service has stopped problem, but I fixed that by clearing out Cache and Data in the Applications settings menu for the mail client. I tried that with the MMS app and it didn't fix the problem.
I also check the permissions and owner for the secmms.apk and secmms.odex files and the are correct. I tried downloading a secmms.apk, but I am not sure if it is the right file, especially since it didn't have an odex file with it. That didn't fix the problem.
Update: Restoring from TiBack-up didn't help. Also tried restoring mmsprovisioning. I'm overseas so I have mobile data off and using WiFi. Does this impact MMS, e.g. need to have mobile data networks on to get MMS or MMS not working with WiFi?
Can anyone suggest a fix for this, e.g. send me the right secmms files? Does flashing CWM and doing a cache wipe help and will this erase all my files? How about restoring my full MMS back-up from Titanium back-up? Any help is appreciated.

You restored some backups from Titanium? Of /data?
I thought that the no trip root method avoided overwriting /data, meaning there was no need to restore anything? Maybe that's the reason you're seeing your MMS app fail?

gr4p3s said:
You restored some backups from Titanium? Of /data?
I thought that the no trip root method avoided overwriting /data, meaning there was no need to restore anything? Maybe that's the reason you're seeing your MMS app fail?
Click to expand...
Click to collapse
I think the problem was with the titanium backup restores. So avoid restoring data on the mms or email.
I could not find a fix and ended up doing a factory data reset from the settings menu. After reboot everything was working fine.

[Q] TimeTracker app keeps FC'ing when restoring data. Can you confirm?

My rooted HTC EVO 4G which was running Fresh EVO 4.3.3 rebooted with the endless white screen, so I figured it's time to Wipe and Flash.
I wiped it and flashed it with the following:
Kernel: Mason-G-d15rc4-sbc-fso-supersonic-signed*.zip
ROM: MikG-v3.11-signed.zip
Everything works fine, except the one app that I depend on for my consulting business -- TimeTracker by ABS
TimeTracker keeps an autobackup of the database on Dropbox, so when I copied the file to the sdcard\TimeTracker folder to restore it, I got a Force Close error.
I contacted the developer and e-mailed him a copy of my database. He said the restore worked fine on his Samsung Galaxy.
I've tried various ROMs and kernels from stock to custom, all with the same Force Close error.
I tried a newly formatted SDCARD and had the same Force Close error.
Can someone try this test out on their HTC EVO 4G, and let me know if you're able to backup and then restore the data file?
1. Install TimeTracker by ABS from Google App store
2. Launch TimeTracker, and choose database Backup from the menu
3. Next, choose database Restore from the menu
4. Did you get a Force Close error too?
If you don't get a Force Close, I'd really like to know which Android version you're running, which kernel, and which ROM.
Thanks

Just wanted to update everyone.
I've been corresponding with the developer, and he released an update just now which fixes this problem. TimeTracker version 2.2.4 fixes this problem.
Glad it wasn't my phone!

[Q] Problem with default mesaging app in Kitkat

I had a stock 4.3 P601 which I upgraded to stock 4.4.2.then rooted with CF-Autoroot The upgrade was over OTA after removing root and the new firmware is ND6.
Everything works fine except for one weird problem. I cannot send texts through the stock message app. It opens fine, but the compose box is grayed out.
If I go to the settings to set it as the default messaging app, it does not appear in the list at all! The tablet can send and recieve texts just fine through third party apps like Go SMS, but just does not seem to recognise the stock app.
What could be causing this?

Did you try wiping the cache? If that doesn't help you could uninstall and reinstall the SMS app, apk should be located in system folder. Last resort would be wipe data and reflash through Odin.

Tried wiping cache and dalvik. No luck. Will probably just stay with a 3rd party app as re flashing seems too much of a pain.
Thanks for your suggestion.