Hi all -
I'm running Winner's pre-CM9 ROM (now on latest build) with Franco's milestone 2 kernel. The latest builds of the ROM are 4.0.4-based.
I had no problems on the previous versions, which were 4.0.3-based. A few days after upgrading to the 4.0.4-based versions (yes, I did do a full data/cache wipe first) and the 4.0.4 versions of the Google apps, someone tried to send me an MMS message. I have it set to auto-retrieve, but in this case it didn't. Tried to manually download it, and it failed. This has happened since with messages from other people from different carriers. If I try to SEND a pic via MMS, the app (stock Messaging app) just crashes. I can still receive regular text messages, but trying to delete some message threads causes the app to crash; some delete OK.
I'm assuming that I'm having problems with the database (/data/data/com.android.providers.telephony/databases/mmssms.db). I tried flipping the permission bits with Root Explorer, but that didn't change anything. Short of deleting and somehow recreating it (don't know if just "touching" the file will work) and losing all the data - is there anything else I can do to solve this?
Thanks!
Everything else is working fine.
Finally just deleted the database file (actually, just renamed and moved it) and it's working again, though I "lost" about 400K of data...the database file was somehow corrupted.
Related
I have wiped everything twice and am not getting any of the contact pictures to appear with my text messages. It happened when I first flashed Fresh .3 but I figured that something didn't wipe correctly. Anyone else see this? The contact pics show up normally under favorites and when scrolling through contacts.
Thanks
Everything shows up fine here. Idk what could cause that. Are you using the stock messaging app?
Yep, I haven't changed anything from the Fresh release with the exception of adding the voicesearch back in.
mine all show up fine too.
do this. delete the contacts.
then resync with google.
I finally fixed it! I opened an adb shell and used the find command to locate all files with mms in the name(find / -name *mms*) and purged them all. Then I reflashed Fresh 0.53 over my current install without doing any wipes and tada, it worked. Thanks for the suggestions.
I am unable to install apps from the market. I can access the market and select the apps but all I get is starting downloads which doesn't change even if I leave for hours. I have WI-FI enabled and can access the web with no problems. Here is what I have tried already.
Clear Data in Downloader,
Clear Data and Cache in market
Factory reset
Flashed to CyanogenMod 7
and I still cannot download any apps.
If you have s-off you could try deleting the market.apk file and then reinstalling from a non market source? If you search xda I'm sure I remember several threads about this.
I had this problem a few times. Have you recently changed your Gmail (If you use Gmail) address from @googlemail to @gmail? This is what caused the problem for me and many others...
Sent from my HTC Desire using XDA App
I never did work out what was causing the problem. I installed CyanogenMod 7 and all is work again.
Yea, sometimes just a reflash fixes the problem. I also found that, sometimes, the download would just finish but never actually install - almost as if the .apk downloaded but the Market Process just never actioned the new .apk to open, so it just sat in /cache until the next reboot, doing nothing.
log in to google talk...i think that should solve the issue.
I notice that lately I can't install some apps...AT ALL.
I can copy them to the sysem/apps folder. It's strange that Rom Toolkit can't restore them, but even redownloading them gives an error. I've had this with a few ROMs, including Stock 4.1.1, the multiwindow release.
I'm just seeing if anyone else has this issue, and if anyone has solved it without having to copy to the system/apps folder.
So far the list is:
Amazon Appstore
Yahoo Mail
I've been having a very odd bug that started to occur today.
Whenever I restart my phone, battery pull, or turn it off and on it resets to Jan 1st at 7:00pm. Some apps are not working, including BBM (msgs don't attempt to send), Snapchat (gives me a "Google Play not supported by device" notification), and Google Play (no connection error).
Because my phone is "in the past", whenever I send or receive texts they do not appear on the message log due to their time stamps being in the future (I assume so).
What should I do? Should I wipe and re-root. I'm running Liquid Smooth JB 4.2 ROM and have been for nearly 6 months for no issues. I wouldn't expect it to be the ROM.
Another thing, If I do wipe and re-root, how would I completely wipe everything minus the core things? Let me elaborate: I've been having a problem caused by CWM where it is creating multiple "0" folders (which are created to store all the files every time I install a new ROM). I think it's at about 7 files deep now due to switching ROMs daily about 6 months ago. This leads to a very messy internal SD with files all over the place. How would I fix this so it goes back to the normal file structure, pre-root? Do I have to go delete the files by hand on via my PC?
Another thing, what method is recommended to save my People contacts, messages, app data, etc (preferably on an external back up: PC or external SD)?
Thanks in advance!
I'm having trouble restoring some backed-up SMS and MMS on my new LG G3. I have tried several methods with varying results and I'm starting to think it's an issue with the G3 because I have not had these problems with the myriad of other devices I have been doing this on.
Titanium backup pro: restore messages from snapshot causes messaging to force close (not surprising). restoring from XML works fine with SMS, but the MMS are all timestamped with the date/time they were restored (today).
Mybackup pro: restoring SMS causes them to have a timestamp of today but it fixes itself when you open the thread (not a big deal, have had this happen in the past). restoring MMS causes only the MMS that were sent by me to be timestamped with today.
now I've just started testing any app that let you restore MMS to see if there'll be any luck. just finished trying Easy Backup and it has the same results as Titanium.
any ideas?? anyone have any luck restoring MMS? what app did you use?
Sorry to resurrect a dead thread, but I'm running into this issue now and can't find another thread discussing a solution.
It seems to occur with two different G3 stock-based ROMs when I tried to restore MMS messages that were backed up on a CM-based ROM. Titanium Backup and SMS Backup & Restore both have the same issue: a bunch of MMS messages get the current timestamp (time of restore). Doesn't seem to be a problem restoring to AOSP ROMS, just LG-based ones.
Any ideas? Anyone else see this?
Same problem here on LG-based roms running on my G2. This seems to be the problem of some manufacturer-based ROMs, not just LG but at least also Motorola.
Preparing the mmssms.db file using https://github.com/t413/SMS-Tools on your Linux desktop rather than directly on the phone (using restore programs) seems to be the working workaround. But I do not envy those who still use Windows as their main system.
For anyone having the same problem, i finally found the solution...
the lg g3 has a custom com.android.provider.telephony service : when the restore app send the mms to restore, the "date" field is not read properly, and the current timestamp is store in the "date" field of the "pdu" table in the database "mmssms.db"
But... there is another field in that table, "insert_time" which contains the good timestamp... almost cause it's a microtimestamp.
So, for the solution :
1/ you need to download and open your "mmssms.db" file using you're favorite sqlite editor
2/ apply that sql query to set a good content for the "date" field based on the "insert_time" field :
Code:
update pdu set date = substr(insert_time, 0, 11);
3/ you send the mmssms.db back to your phone and reboot
That's it !
You're welcome
A finally happy LG G3 owner
patoulich said:
For anyone having the same problem, i finally found the solution...
the lg g3 has a custom com.android.provider.telephony service : when the restore app send the mms to restore, the "date" field is not read properly, and the current timestamp is store in the "date" field of the "pdu" table in the database "mmssms.db"
But... there is another field in that table, "insert_time" which contains the good timestamp... almost cause it's a microtimestamp.
So, for the solution :
1/ you need to download and open your "mmssms.db" file using you're favorite sqlite editor
2/ apply that sql query to set a good content for the "date" field based on the "insert_time" field :
Code:
update pdu set date = substr(insert_time, 0, 11);
3/ you send the mmssms.db back to your phone and reboot
That's it !
You're welcome
A finally happy LG G3 owner
Click to expand...
Click to collapse
Thank you for the explanation!
Although your solution didn't work for me (no insert_time column on my new Axon 7) I ended up joining my old table with my new table and fixing the date, date_sent (and creator...) columns. That worked, and helped me not looking for another 20 apps on playstore that wouldn't work anyway.
Now one major hassle I didn't realized for long hours, google messenger had some sort of cache issues and was not showing me my new data.. so I kept trying stuff with no result... till I tried the stock messaging app and realized it worked.
Anyway, I've been looking at this for 2 days now, so thank you so much, I can finally move on