yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] Sesquipedalian:
You likely have some errors in your mmssms database. This has happened to be before. You have a few options, and they all involve losing your texts, but c'est la vie. I've have reasonable success using text backup software then restoring them after this procedure, but this has never "fixed" the MMS messages so I could download them. I would advise you to backup your SMS and MMS messages, and only restore the SMS messages if you need to.

The database in question is /data/data/com.android.providers.telephony/databases/mmssms.db. You need to delete it (along with the db-journal if there is one), then restart your phone.

A couple methods:

1) Use a file manager and (backup and then) delete the file.

2) Clear data for "Phone/Messaging Storage". This will also clear call logs. Use you preferred app manager, or System Settings > Apps > All. (You can back this up using something like Titanium, but I'm not sure the backup will be useful. I tried backing up and restoring Phone/Messaging Storage once, and it ended up having to do a full wipe to stop Phone from constantly crashing.)

3) If you're clever with databases, you can go in and manually delete (or even try to repair) the offending rows, but it's messy. I've actually salvaged a few bugged MMS messages this way, but my overall success rate is low.

After either of the above, I would clear data on Messaging or whatever texting app you use, then reboot the phone. If you want to be especially sure not to reintroduce the data errors, I advise you not to try and restore your messages. If you really need to, restore only the SMS. I would not suggest restoring the MMS messages. You can try, but you will probably end up having to wipe the database again. (If the lost messages are important to you, it might be worth the loooong shot, though.)

I also recommend you get GoSMS and stop using Messaging. I've even went to far as to disable Messaging, just to be sure it can't foul up my data. GoSMS can be a little annoying. I recommend you put it in "Lite" mode. It turns off most of the obnoxious stuff. Others have had success with ChompSMS, which is a bit less annoying but aesthetically challenged, IMO.

If you don't have a preferred SMS backup software, I recommend SMS Backup +. It will sync them to your gmail and restore SMS (but not MMS). I've also used Go Backup, and it seems to work well without a lot of fuss.
[Epic 4G Android Development] bpsears90:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

Ehhhh I didn't say that lol im just losing patience with some of the bugs. 4.2.2 is something we have to work hard for to have on our phones instead of it coming naturally. I want to get an up to date phone and put customized roms on it. Ya know? The phone is 2 and a half years old. The s4 is coming out at the end of april so this phone's days are numbered. If they would just come out with another samsung phone that's android based with a keyboard with bells and whistles and blah blah blah we wouldn't have this phone lol
[Epic 4G Android Development] bakerja:
I'm probably right with you for the S4. Me and my wifes epic's are showing their age. Her screen has been broken for almost 2 years, my vibrator broke a long time ago but I did fix that recently. Also, LTE is coming to my area "within months". The processor of the S4 is significant enough to warrant a new one. Will most likely root the S4 too.
[Epic 4G Android Development] DynamicN:
Another option to get the best signal is turning on airplane for a few secs then turning it off, the radio will reconnect and find the best tower after doing so.
[Epic 4G Android Development] Sesquipedalian:
I feel just the opposite. I think the hardware specs on the Epic are actually still pretty reasonable. I am totally amazed at just how smooth Jellybean is on here. I never find myself wishing too much I had a faster processor. Multicore and more RAM would be some improvement, but I really have no complaints! I've actually been MORE satisfied with my phone than ever before. I even bought a Note 2 and ended up returning it. It was faster, but it didn't really present me with any practical functionality I didn't already have on my Epic.

The main things I wish I had is a better camera and LTE. Even battery life on the recent CM 10.1 builds have been superb. (Don't hesitate to get the 1800 mAh Samsung battery. It's amazing how much more time you can get when you combine the extra capacity with a fresh battery. +20% from extra capacity base, and +20% more from what your old 1500 mAh has lost over time is a lot of extra juice!)

That said, even if they did debut an S4 with a keyboard, I would hesitate to get it until the developer community matured a bit. It's amazing how much better a community project like CM is than the stock ROMs being produced by paid engineers. The Note 2 dev community wasn't nearly as mature and robust as the Epic's. It was more active, so I'm sure it will get there, but it will take time. You can't overlook the software as a feature of the Epic. Sometimes good software on middling hardware is better than iffy software on a high-end hardware.

These days, it's almost like having a totally different phone than the Epic I bought 2+ years ago. Back then they hardware keyboard didn't even work right. Anyone remember that? (I still say a little blessing to mkasick every now and then where I am furiously hammering out text on the QWERTY). We've come an impossibly long way from the erstwhile custom repackaging of Sprint stock ROMs. Some of that credit goes to Android in general and the AOSP, but a lot of it's brilliant dev work right here on this forum.
[Epic 4G Android Development] Counterfeit7485:
Flickering screen

I've seen a few other comments about issues with a flickering screen but they don't seem to be similar to my issue. I currently have CM10.1 nightly 20130315 and nitest kernel build 0315 with fc09 modem. I'm having my screen flicker really bad when using the stock browser and in facebook most often. Sometimes the flicker is so bad the screen gets stuck in, almost an inverted colors look with a mostly greenish tint. The only way to get the screen back to normal is to restart the phone. Not sure whether this issue is kernel or ROM based, but I've had the issue on several cm10.1 builds and other nitest kernels. Thanks in advance for any help!
[Epic 4G Android Development] bpsears90:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

Good points. All true. I just feel at this point the only thing I'm holding onto is the QWERTY keyboard. Its what makes the phone. Its something no other one has. But like I said all this work we have to do to keep it "up to date" is exhausting for me. Like the MMS issue for example, it doesn't work via wifi. Only data network. And it takes forever to send or receive and u just have to fight with it. I wanna send it fast with wifi. Or beam it with everyone else I know that has it. And then there's the current bluetooth. Y should I have to wait 20 seconds before it switches to my headset? Especially since some of my work related calls don't last long or I have my hands full and don't wanna grab my phone.

.........as a spoiled american I want these easy things to come easy lol!
[Epic 4G Android Development] UPdownLoAD:
Sounds like you have a small tear in your flex cable (was just discussed a page or 2 back)
[Epic 4G Android Development] Counterfeit7485:
I've read several pages back and don't see any discussions about this and even searched for flex or cable and found nothing in this thread about it either. The main reason I don't think this is hardware related is it only seems to happen when using certain apps.
[Epic 4G Android Development] tbob18:
Has anyone gotten Dock Audio to work?
[Epic 4G Android Development] cybershawngates:
yeah- it's still glitchy but for the first time I can actually send pics with the steps. THe only thing different I'm doing is have auto-download the pics ON in teh MMS settings of the messaging app - that seems to work better with the steps I gave. I don't know what it has to do with anything, but leaving auto-download ON seems to help. But if you are on a different provider (i.e. virgin and not sprint) I don't know how much of this will help or apply.

It terms of usability of the epic 4g - cm10.1 has been the best one so far, but admittedly it's an old phone with old specs. One thing I've found that makes a diffference is to have as much filespace open 110+ MB open in the "data" file system space at least (NOT the Sd card). So this requires periodic flushing of caches, etc. I've found an app called systemcleanup (clean all items) that I run every few days since I've packed as many apps as I possibly can on this old phone (I use app2sd to move to SD card and then force other apps such as FB to the SD card using Link2sd). Though annoying is waiting for the sdcard to scan on bootup (approx 5 mins till all apps available). I have 132 MB open and it's running great.

I also have 13MB of system space open (which can be easily seen with the systemcleanup app). I freed up system space by using file manager root permissions to go to /system/media/video (delete all) and /system/media/audio (remove any files > 100 kb or 1MB esp). It does suck having to remove audio ringtones, but i'd rather have a faster phone than so many choices for sounds. The 4 video files are demo files can be safely deleted.

I'm quite happy with these tweaks for now....S4 for the future though. (Though I hate touchwiz and will def want 10.1cm on it as long as MMS etc works).
[Epic 4G Android Development] labumm:
Although it would be nice to have more memory, dual band wifi n (+ac), GPS+GLONASS, etc, etc. --that I could have with the S3 or the S4--I would also loose the QWERTY. Not sure if that is a good trade for me.

My main gripe is with Android's lack of BLE support on JB 4.2. If I moved to an S3 or S4, that problem would follow me. So the Epic is still a winner for me and I am stuck at CM10.

If I got an S3 or an S4 today, the first thing I'd do is root it and install CM10.1
[Epic 4G Android Development] bpsears90:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

I too would root it to 10.1 BUT if the bugs and glitches are the same, what would be the point? Id have a phone that has a bigger screen with no keyboard lol
[Epic 4G Android Development] UPdownLoAD:
I didn't post in this thread actually (http://xdaforums.com/showthread.php?p=39248961#post39248961), and what was discussed was replacing the flex cable, not the symptoms. You are describing a small tear in the flex cable. Another symptom (I've seen) is the screen going back a screen or 2 when you slide out the keyboard. It may seem sporadic, but it usually rears it's ugly head depending on how you're holding your phone and especially when you slide out the keyboard.

If you really want to diagnose it, flash stock software and see if you're having the same problem. I bet you will.

I also would suggest your Epic may be liquid damage. Regardless, I believe your problem is hardware related.
[Epic 4G Android Development] Senater_Cache:
I have the exact same issue (though not quite as severe as you describe) It seems that the color white is the problem. White Apps are very banded and flicker. The browser looks like a TV set from 1949 with bad reception. getting into a black screen app fixes the problem. It may be related to the radios, because it happens much less frequently if 3G/4G is off.

P.S. never had this problem before M2 build. Been on CM since CM9 alpha
[Epic 4G Android Development] labumm:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

Is the flex cable failure due to a normal life cycle of flexing the cable by sliding out the keyboard, abuse/damage, or something else?

I imagine more mechanical problems will appear as our phones age and the hours of use increase.
[Epic 4G Android Development] didhiy:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

this maybe came with auto brightness on, try to turn it off or try this adjustment works on mine
[Epic 4G Android Development] counterfeit187:
Well, it was even worse this morning. Left the phone off and let it charge to 100%. Turned it on and tried to browse the forum with the tapatalk app. I went to scroll to see if anyone else had the same problems or a solution for me and it flickered some thick black lines while scrolling and shut itself down. Flashed back to M2 and still have the problem. I guess maybe my battery is done for. Trying to decide if I should just go get the S3. Please let me know of anything pertaining to this issue, I saw some other people commenting on similar problems in the past few days, but not to the degree I'm having them. I don't really want to drop $200 on a new phone today if I don't have to, but also don't want to spend money on a new battery for a device that is probably in its last days.
[Epic 4G Android Development] labumm:
A new 1800 mAh battery is pretty inexpensive. A new flex cable is $6. If you have the "insurance" plan Sprint will probably fix it for "free", after they try to sell you an S3....
[Epic 4G Android Development] counterfeit187:
It's been a good ride. Tried wiping everything to see if it was data corruption giving me problems, but the shutdowns are getting worse. It isn't the flex cable, could be the battery, but I'm switching to the GS3. <3 everyone here and the developers that let me keep this phone for so long.
[Epic 4G Android Development] bpsears90:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

Might be joining ya. Restarting my phone and losing 40% for no reason is getting ridiculous. I rebooted my phone because my phone had been "sending" a mms file for 10 minutes. I had great connection. I'm just losing patience.
[Epic 4G Android Development] UPdownLoAD:
Yes, it is a very thin cable prone to wear by sliding. I've gone through 2 of them in about 1 1/2 years (and think I may have a 3rd one starting to go now) and 1 hinge break (springs flew out lol). I send @ 2000 txts a month + e-mails etc, and most are sent by the physical keyboard.

Years ago, I worked for a major cell phone carrier and was told that the phone manufactures intentionally build the phones to last about 18 months, 6 months before most contracts expire. I'm not sure if that holds true today, but I would say it's accurate for batteries.

I refuse to go to the GS3 because of NFC and it's too big for my pockets. If I ever upgraded, I might consider the GS2, but I really really really like a physical keyboard. I do not live where either WiMax or LTE are available, but I can use WiMax in Columbus, OH when I'm nearby; GS3 would not have any 4G available to me at this time.
[Epic 4G Android Development] robrob:
I'm getting a spare Epic in a few days. My brother-in-law's Epic refuses to wake from sleep. If unplugged and it goes into sleep mode or if you hit the power button to induce sleep it will not wake up, even after removing the battery--at least not the first few times. If he keeps messing with the battery he can eventually get it to wake up and he plugs it in to keep it alive. He's running the latest Sprint OTA update and is not rooted. Does this sound like a hardware issue or could I possibly fix it with a new rom flash?
[Epic 4G Android Development] DynamicN:
Just a question out of pure curiosity, how long have you had that battery that's in the Epic?

Stock oem battery?
[Epic 4G Android Development] bpsears90:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

Yes stock battery. I don't understand how the battery could lose 40% off of a reboot tho?
[Epic 4G Android Development] counterfeit187:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

I had the gs2 battery 1800 mhz or whatever. Probably close to 2 years. It was obviously not a problem with the ROM because flashing back to the factory ROM still had the battery life problem. I got the new phone though and I'm pretty happy with it so far.
[Epic 4G Android Development] codest3r:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

ot. My gs2 battery went sour after a year. swolled up and got unpredictable. Back on my og epic 1500mah for now untilsz orderz a new gs2 batter.
[Epic 4G Android Development] Shinydude100:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

I would like to remind everyone that when an issue arises, just confirming it and reporting it if new, would suffice. If you aren't satisfied with Cyanogenmod, you aren't obliged to use it. Go back to stock or just don't mess with your phone. Not all of you are grown ups and that's ok. Just please try to keep things on the brighter side. Its the praise and gratefulness alongside the donations received that keep the devs going.

I speak out because our lovely devs may not do so, and i'd be more than happy to take that bullet of hate (if any) for our devs.
[Epic 4G Android Development] UPdownLoAD:
I had the EXACT same problem with an Epic TOUCH (D710 GS2). It had a bad eMMC chip, and Sprint ended up swapping it.

On a side note, I was reading through the change logs and it looks like ClockworkMod was updated in the 0320 build, which could effect/fix/worsen the battery life and how the device charges (http://changelog.bbqdroid.org/#epicmtd/cm10.1/1363763679). So if you've been having a charging problem, you might want to update to a newer build and see if it fixes anything for those effected.
[Epic 4G Android Development] bpsears90:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

I flashed from 0319 to 0321. Right away I was getting unfortunately android keyboard has stopped working. Half the time it popped up it went away before I could press ok. Sometimes it was a split second like u could just see the box flash. The keyboard indeed did not work. Also, some apps weren't "installed" when I tried using them. And apollo didn't load any of my music. I did however lose maybe just 2% if that when flashing to 0321.

Needless to say I flashed back to 0319 because of the mentioned issues. When I flashed back, I went from 26% to 3%.

---------- Post added at 10:16 PM ---------- Previous post was at 10:10 PM ----------

And I lost gapps flashing back to 0319 so now I have to get that working
[Epic 4G Android Development] DynamicN:
All of this sounds like batteries that are at the end of their life cycle, a battery will produce optimal results between 300 and 500 charges.

100% agree

---------- Post added at 08:39 AM ---------- Previous post was at 08:38 AM ----------

Battery level also goes off voltage so let the phone sit for 30 mins or so and it should come back to around 26% Did you dirty flash?
[Epic 4G Android Development] bpsears90:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

Yes I dirty flashed. I clean flashed and now I'm on 0321 and its working fine.
[Epic 4G Android Development] copticwalad:
I've done nightly builds every so often since CM9 over a year ago and these past few weeks the dirty flashes are just terrible at working. Anyone else having so many issues after a dirty flash that they have to constantly wipe and do clean flash? I backup everything every few flashes but I'm surprised that I haven't had a good dirty flash in a few weeks. I just tried to jump from CM 10.1 nightly 21 to 23 and it couldn't boot right. Had issues with nightly 19 to 21 as well and had to do clean flash. I'm just curious if it's just me or if others have same issue?

Also, I noticed the stock touchwiz Task Manager (yes I know I'm lame but I actually like it) stopped working on nightly 19 when installed in recovery. Also, bluetooth seems to be getting a little better but I'm curious when we'll see that really good bluetooth support in latest jelly bean build. My bluetooth headset just can't hold a connection after the initial one and needs manual connect every call.

Keep up the good work everyone :)

UPDATE! When my dirty flash from nightly 21 to nightly 23 didn't work, I decided to try dirty flashing back nightly 21 and boot (without wipe dalvik/cache just in case cause I notice I might have full wipe at times). Didn't boot, then went into recovery and Only wiped cache and dalvik, then rebooted and it actually worked great. So I'm happy a downgrade dirty flash works at least to save time on all of our customizations on a clean wipe. Don't forget to reinstall gapps again, I dont understand what use is Android without gapps (needed for Google Play)..
[Epic 4G Android Development] DynamicN:
From personal experience I can't say i've had those issues but I never dirty flash. For best results it is always recommended that one clean flash but sometimes it is not necessary. I think people have become use to taking the easy way by dirty flashing and now some expect it to work all the time but it's always best to clean flash for best results. As for the bluetooth not being 100% there were changes in 4.2.2 so it made it hard on devs. I'm sure our awesome devs will get it working 100 percent, it's only a matter of time.
[Epic 4G Android Development] propjockey:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

I'm a little confused as to what you are or are not wiping when you "dirty flash". Nothing personal is lost when you wipe cache and dalvik (dalvik rebuilds itself on the first boot, that's the "android is upgrading" thing). You should always wipe those, it's easy and will fix silly little issues. CM updater does this for you as well when you use it to update.

I consider not wiping data, a dirty flash. But really, like any OTA update, data doesn't need to be wiped. Unless you think there is a problem you want to report with the ROM, in which case, you should perform a

completely clean install to verify the potential issue. Or when you are switching to a dramatically different ROM.

Wiping system isn't bad to do either, it guarantees a clean system update. The only downside is you will have to reflash gapps. But let's be honest, that takes a whopping 45 seconds.

I haven't wiped data since I switched from CM10 to CM10.1 (when the first preview build came out). I haven't had any boot loops or other weird issues. That said, I always wipe cache and dalvik, and I usually wipe system. Flash latest nightly, flash gapps, reboot, ???, profit!
[Epic 4G Android Development] DynamicN:
I've always considered a dirty flash not wiping anything at all such as cache, dalvik, data etc. If data is not wiped wouldn't there be a chance of data becoming corrupt?

Edit: Not trying to come off in a negative way, just trying to learn more:)
[Epic 4G Android Development] flastnoles11:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

Dirty flash is not wiping data, ha nothing to do with the others and most of the time you can get away with it... chance is the keyword in your statement. ;)
[Epic 4G Android Development] DynamicN:
My apologies, I've been wrong this whole time:confused: Thank you for the clarification Flast.

Edit: I'd hit the thanks button but I've used all 8 thanks today, get ya tomorrow.
[Epic 4G Android Development] flastnoles11:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

No need to apologize, we've all been misinformed before. Knowledge is power and I'd like everyone to be a body builder! :D