Develop Bugs

Unfortunately messaging has stopped

So I flashed a custom theme here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1803273 and I flashed it over wicked r5.
I also also installed another zip from there to change the jellybean messaging app to the stock touchwiz.
It worked but randomly I get a Unfortunately messaging has stopped error.

Try clearing your cache or fixing permissions. Also, it might just be a bit too much tweaking.. Hopefully you can get it to work.
Sent from my SGH-T999 using xda premium

Every time ive seen that doing a factory reset has fixed it.
BACK UP YOUR INTERNAL SD FIRST!!!
Good luck!
Edit: try daves suggestion first though!
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Every time ive seen that doing a factory reset has fixed it.
BACK UP YOUR INTERNAL SD FIRST!!!
Good luck!
Edit: try daves suggestion first though!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I spent a whole day trying to fix this, in the end had to do a factory wipe.

Corrupt sms / mms database
This has to do with a corrupt db file. It can either happen if something goes wrong with titanium backup/restore process. Or also if you manually copy these files from another older backup (when an older android was installed).
First backup the existing sms/mms with smsbackup from appstore. It is free.
With an explorer app like ESFile explorer, go to "/data/data/com.android.providers.telephony/databases" (or something similar in your phone where the sms / mss .db files are located).
Make a backup of the files here and then Delete all the files.
Then restore the sms from smsbackup app. Voila ! No crash anymore
No need to do a factory wipe.
If everything works fine, you can delete the backup folder containing the old db files.

FYI: After upgrading to Wicked's v.7 I stopped getting these errors. Been a week so far with no probs.

genardas said:
So I flashed a custom theme here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1803273 and I flashed it over wicked r5.
I also also installed another zip from there to change the jellybean messaging app to the stock touchwiz.
It worked but randomly I get a Unfortunately messaging has stopped error.
Click to expand...
Click to collapse
Hi please see http://forum.xda-developers.com/showthread.php?p=27695693 ..... it may be related to your CSC. Or alternatively (in my case) I had mistakenly frozen the system app "BadgeProvider" using Titanium Backup. Constant "Messaging has stopped" kept coming up until I unfroze BadgeProvider.

shriramrs31 said:
This has to do with a corrupt db file. It can either happen if something goes wrong with titanium backup/restore process. Or also if you manually copy these files from another older backup (when an older android was installed).
First backup the existing sms/mms with smsbackup from appstore. It is free.
With an explorer app like ESFile explorer, go to "/data/data/com.android.providers.telephony/databases" (or something similar in your phone where the sms / mss .db files are located).
Make a backup of the files here and then Delete all the files.
Then restore the sms from smsbackup app. Voila ! No crash anymore
No need to do a factory wipe.
If everything works fine, you can delete the backup folder containing the old db files.
Click to expand...
Click to collapse
Thanks I tried restoring one too many things related to SMS with titanium backup which screwed up the messaging app, I wasn't able to receive or read msgs. Your solution worked, I just had to reboot after deleting.

If you rooted your phone, anyone, and you deleted or renamed some system apps to stop them loading then you could face problems with the SMS Messaging app.
Just make sure the system app "WebViewGoogle" is left intact (in the folder data/system/app)
If you deleted it then put it back in, if you renamed it (e.g. from "WebViewGoogle.apk" to "WebViewGoogle.apk.old") then name it back to "WebViewGoogle.apk"
This app must be intact for the Messaging app to work. properly.

[Issue] Most of my apps can't have access to Internal Storage

Hi everyone, three days ago i updated my Galaxy Nexus to the latest 4.2 version, from the stock 4.2 (the one without december in the people app).
Yesterday i started to realize some weird behaviors with overall apps, and here are some of them:
. Câmera app : Photo is taken, but can't visualize it
. Galery app : Shows ammount of photos in each album, but all the thumbnails are solid gray, and no photo can be selected for visualization
. Swiftkey Keyboard : Keeps raising error related to "Dynamic Language Packs" (since swiftkey stores the dynamic packs in the sdcard/internal storage, this might be another access issue)
. All apps that use camera activity : Camera is loaded but once i took the photo, it does not return to the app, and the camera app keeps open. No photo is returned to the app that invoked the camera aswell
. Dropbox : Can't export to internal storage any file, sometimes it manages to finally "read" the internal storage and show me directories structure, and sometimes it doesn't. In both situations, file "fails to export".
This seems a really weird behavior to me, and i thought that it might be a "Permission" issue, so i got in recovery mode and fixed permissions, but nothing got solved.
Is there any other step i might take before having to actually try a full wipe / factory reset ?
Having to reinstall / reconfigure all the apps is a pain in the butt, and since i can't backup them with titanium because of the internal storage issue, i would have to do it "manually".
By the way : Play store can update and download apps with no problem at all, so this is not a hardware issue for sure.

Try this wipe cache via recovery and dalvik cache and then flash latest root.
This should work.

manumanfred said:
Try this wipe cache via recovery and dalvik cache and then flash latest root.
This should work.
Click to expand...
Click to collapse
Wiping cache and Dalvik Cache will not erase all my internal storage right ?
EDIT: Wiping Cache and Dalvik have not worked

Weird Issue:
After booting up into recovery mode, and try to Install .ZIP from sdcard, the CMW does not actually find any other folder in my sdcard than some weird ones like "0", "odb" and "legacy".
What are those folders ?
Why it does not sees the other folders ?

marcelloLins said:
Weird Issue:
After booting up into recovery mode, and try to Install .ZIP from sdcard, the CMW does not actually find any other folder in my sdcard than some weird ones like "0", "odb" and "legacy".
What are those folders ?
Why it does not sees the other folders ?
Click to expand...
Click to collapse
Nevermind, i just reinstalled the Factory Stock 4.2 Android and updated to 4.2.1 OTA
Then i rooted it and everything is ok now.

[Q] Gallery not working on nandroid restored S3

Here is an issue:
I got an insurance replacement for broken screen phone. I am trying to backup and restore rooted Sprint S3. I did a nandroid backup to external card in Clockwork recovery on old phone. On rooted new phone with Clockwork recovery I did a full wipe and restored from external card. Everything is fine except I couldn't take picture or start Gallery. Gallery would give "Not enough space. Remove.. bla-bla" message. Camera would appear to take picture but didn't save it. I tried to fix permissions with Clockworks-didn't work. I used x-plorer in root mode to rename DCIM folder. Camera started saving pictures to a new DCIM folder but Gallery still wouldn't work. I used quickpic to check photos. It could delete photos in new DCIM folder but not old, renamed DCIMbackup folder. I guess it is some issue with permissions but don't know what to do at this point. Could someone advise?

nadegda said:
Here is an issue:
I got an insurance replacement for broken screen phone. I am trying to backup and restore rooted Sprint S3. I did a nandroid backup to external card in Clockwork recovery on old phone. On rooted new phone with Clockwork recovery I did a full wipe and restored from external card. Everything is fine except I couldn't take picture or start Gallery. Gallery would give "Not enough space. Remove.. bla-bla" message. Camera would appear to take picture but didn't save it. I tried to fix permissions with Clockworks-didn't work. I used x-plorer in root mode to rename DCIM folder. Camera started saving pictures to a new DCIM folder but Gallery still wouldn't work. I used quickpic to check photos. It could delete photos in new DCIM folder but not old, renamed DCIMbackup folder. I guess it is some issue with permissions but don't know what to do at this point. Could someone advise?
Click to expand...
Click to collapse
Any ideas?

Anyone?

Try clearing the gallery app's cache (Settings > Applications > Gallery > Clear cache)

[Q] Problems when updating to AOKP 4.3

Hi.
I hope, i'm in the right section here...
I wanted to Change from AOKP 4.2.2 to AOKP 4.3 nightly, did a backup with Titanium, flashed the new rom and restored contacts, sms and user-apps. After reboot the screen got spammed with 2 error messages:
android.process.acore must be closed
android.process.phone must be closed
With this, it's not usable an i had to restore a nandroid backup.
Any help there?
ps: sorry for my english >> GER

Phantom272 said:
Hi.
I hope, i'm in the right section here...
I wanted to Change from AOKP 4.2.2 to AOKP 4.3 nightly, did a backup with Titanium, flashed the new rom and restored contacts, sms and user-apps. After reboot the screen got spammed with 2 error messages:
android.process.acore must be closed
android.process.phone must be closed
With this, it's not usable an i had to restore a nandroid backup.
Any help there?
ps: sorry for my english >> GER
Click to expand...
Click to collapse
Did you flash the 4.3 bootloader and change the backup directory for tbckup ?
Sent from my Galaxy Nexus using Tapatalk 4

Hi. Thx for answering.
Flashing a new bootloader? I never had to do this for the last releases since i bought the phone with 4.0.1 stock.
Please tell me what do you mean. I don't find some hints about this in the release notes.
Yes, i changed the backup directory to "legacy", because restore would not start without that.
After that Titanium asked me to copy the backup files to the new directory, but it doesn't anything if i answer with "yes". And it does the restore, so i didn't care about that.
Edit:
Here are some additional information:
Baseband: XXLA2
Bootloader: PRIMELA03
Should these be updated?

After a couple of tests and searching forums of the world for hours, i have found a solution
solution for having fc with android.process.acore:
- restore a backup (nandroid) of your rom
- go into the settings of the contacts
- chose: export to sd
- flash new rom
- import contacts from vcf file on sdcard
- restore apps and settings with Titanium WITHOUT(!) contacts (contact memory, contacts/calls)
solution for having fc with com.android.phone:
(don't know if this is the best order, but it was the order i did when testing and helped for me. it could be that only copying the dialer app to /system/apps was the final solution. before, it connected to gsm and i could do calls and sending sms, but nothing else.)
- open settings/apps/all
- erase cache/data of Dialer, Telephone and Tel/SMS-Memory (don't know how its exaktly named when set to english)
- deinstall dialer app with Tiitanium
- erase dalvik and cache partition in cwm recovery
- reboot
- search and copy the dialer.apk from the extracted rom file to sd and install it
- copy dialer.apk to /system/apps
- search, download and copy "fix_permissions:emulator" to sd (i'm not allowed to post links at this time)
- restore Tel/SMS-memory (sms/mms/apn) from Titanium
- reboot to cwm recovery
- flash fix_permissions_emulator.zip to do a fix permissions action (cwm has it anymore and fix permissions in rom manager didn't help)
- reboot
- now, dialer app should open without fc and connect to 3G

How to restore contacts, etc.

Hello everyone,
I have been running the 4.3 stock ATT ROM, rooted, for the last few years, and I recently decided to try out a custom ROM. I ran CyanogenMod on my last Android phone (Aria) and as pretty happy with it, so I decided to try it first. I synced everything with Kies, backed up my OS with CM, and used the CyanogenMod installer to install CyanogenMod 11.0. Everything went well, but when I tried to connect to Kies to restore my contacts, I discovered that it's not compatible with CyanogenMod. Not too surprising, but annoying nonetheless. I also discovered that my backup disappeared; apparently CM was set to backup to internal memory and I failed to move the backup off before installing CyanogenMod. I'm wondering if anyone knows any way to get my data, especially my contacts, back. I'm sure I could flash back to a stock ROM and sync with Kies, but then I'm unsure how to best export the data and import it into CyanogenMod. What I'd really prefer is some way to extract the data from Kies and import it to CyanogenMod without having to go back to stock ROM. Any suggestions or solutions?
Thanks

I've never tried this tool (or kies at all for that matter), but it sounds promising for your situation. http://www.mobile-phone-transfer.com/extract-data-from-kies-backup-sbu-file.html

Thanks for the suggestion. I downloaded the program and tried the free trial version. It found multiple backup files with text messages and call logs in them, but said there were no contacts in any of them. I guess I'm going to flash stock rom to see if the contacts are really in the backups or not. Any suggestions for how to export and transfer them if I get everything restored to the stock rom?

falec_illmore said:
Thanks for the suggestion. I downloaded the program and tried the free trial version. It found multiple backup files with text messages and call logs in them, but said there were no contacts in any of them. I guess I'm going to flash stock rom to see if the contacts are really in the backups or not. Any suggestions for how to export and transfer them if I get everything restored to the stock rom?
Click to expand...
Click to collapse
The contacts app on the phone should be able to export them to a .vcf file. You can keep the file as a backup and use it for import/export from contacts on other ROMs. I don't remember exactly how to get there on touchwiz, but if you poke around contacts settings a little bit I don't think it will be too hard to find.

jason2678 said:
The contacts app on the phone should be able to export them to a .vcf file. You can keep the file as a backup and use it for import/export from contacts on other ROMs. I don't remember exactly how to get there on touchwiz, but if you poke around contacts settings a little bit I don't think it will be too hard to find.
Click to expand...
Click to collapse
Thanks again. For anyone who finds themselves in a similar situation, here's what happened. I did find how to export contacts to vcf file; it's pretty easy to find in the menu of the contacts app. I wanted to take my text messages and other settings, so I looked into programs to do that. I tried GO backup, but the upgrade process to the pro version is broken and support not responding, so I went with Titanium Backup. I flashed back to the stock 4.3 rom as described in a thread here (sorry I can't post links yet), restored all my data with Samsung Kies, but made the mistake of letting the phone install a software update. This put me at 4.4.2 with Knox active, and Titanium Backup needs root access. I regained root access by installing CWM using Odin 3.07 in dl mode as described elsewhere, pulling the battery after install to prevent stock recovery from reinstalling, booting to CWM recovery, and installing supersu binary. Then I installed supersu from the store and allowed it to update itself and block Knox, and disabled Knox as follows: (this is quoted from elsewhere, I can't post links yet)
"I installed Android Terminal Emulator from the Play store - granted it SuperSU access - and proceeded to type the following command(s):
su [enter]
pm disable com.sec.knox.seandroid
*NOTE - the above to lines require you to go to a new line after typing "su", the [enter] is only a reminder, DO NOT type [enter] after su"
At this point, I had stable root access, so I installed Titanium Backup Pro to backup by data. Unfortunately, I discovered that 4.4.2 has problems with permissions; Titanium Backup couldn't write to any location on my phone. After some more research, I installed SDCard Fix from the store and let it fix my permissions. This let me access my SD card with Titanium Backup, and I backed up everything I wanted. Then I installed my backup zip of CyanogenMod that I made before returning to 4.3 stock from CWM recovery and was back to CM and able to restore my data and apps from Titanium Backup.
Hope this helps someone else, but I would strongly suggest that before trying out a new ROM you use Titanium Backup or similar, and save a nandroid backup off the phone. That would have saved me a lot of trouble, but things have changed a lot since I last played with custom ROMs about 5 years ago, and I didn't do enough research first.

Or you could just use a google account and have all your contacts sync with no hassle.

elatllat said:
Or you could just use a google account and have all your contacts sync with no hassle.
Click to expand...
Click to collapse
I do have a Google account, but when I switched to CM Rom and told it to sync with Google, I got a lot of my apps re-installed (not all of them), but no contacts, SMS or MMS, etc. Not sure why I didn't get any contacts, possibly the old OS wasn't set to sync contacts to Google. Just reinforces being thorough in research and preparation before trying to change ROMs.