yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] MrJymm:
Dock Audio

I asked a few pages back about getting Dock Audio to work, but I don't see any replies. Anyone know if this is something that can/will be addressed in an update?
[Epic 4G Android Development] RodimusConvoy:
Worked like a charm. Thanks a bunch. Thanks everyone. Still have battery problems, may go to a nightly...but at least I have data. :laugh:
[Epic 4G Android Development] bpsears90:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

I've noticed some ppl reporting the freezing logo or whatever when they were flashing the 0327 and 0329. Are those issues still occurring? I'm on 0324 and would like to maybe jump to 0401
[Epic 4G Android Development] RodimusConvoy:
Bluetooth works fine for me. Though I was on the stable (10.0) and now the monthly (10.1). Still, bluetooth was never an issue, though I only use it to transfer contacts between phones.
[Epic 4G Android Development] BigOnes69:
I am totally dependent on audio from bluetooth the entire day and drive a lot. Music through bluetooth is a must also. Having a connection drop before after, during a call while driving mucks my day, is dangerous, and will lose me money. 10.0 allows me to navigate, listen to music and recieve call reliably while driving. Not to say its perfect but its consistent.
[Epic 4G Android Development] RodimusConvoy:
I see. Well I hope you find a solution quick, based on what you just described. I've always wanted to use the bluetooth feature that's now standard in car stereo receivers, mostly so I wouldn't have to worry about holding a phone and drive at the same time (I have a standard, non-bluetooth stero receiver at the moment in my car). So I'll keep an eye out of this, too.
[Epic 4G Android Development] nlinux:
Still occuring for me, but if I use this method it works every time:

1. Flash image

2. reboot and get freezing logo

3. Reboot to recovery

4. Wipe Cache

5. Reboot

I've used this method on the last 3 or 4 nightlies with no problems.
[Epic 4G Android Development] bpsears90:
Re: [ROM][OFFICIAL] CyanogenMod 10.1 Preview Builds for Samsung Epic 4G

That's so annoying and not worth it till there's a drastic change in the changelog. If it doesn't make a difference ill wait
[Epic 4G Android Development] TracerBullitt:
Exactly...
[Epic 4G Android Development] RodimusConvoy:
Tried to switch to the nightly (well the one from the 31st) but got stuck on the animation screen so I went back to the monthly.

The only problem (beside the ever-present battery drain issue) is notifications. Some go through, some don't. I get WhatsApp and SMS notifications just fine, but no Facebook Chat and Email notifications.

Seems the other ROMs are built on CM10.1, so maybe they fix some of these issues as well as the battery issue, and hopefully I won't go through the data problem I had. Or, maybe the flash solution works on those ROMs, too, if I can't get data. In the end, though, I need those notifications. Gonna research the heck out of all of them before making a jump.
[Epic 4G Android Development] UPdownLoAD:
I don't do Facebook or any social networking, but I have yet to have Yahoo Mail work pushing notifications since going to CM10/10.1 from CM9. May be related, may not. Now I'm just using the default e-mail app to check my e-mail every 15 min.
[Epic 4G Android Development] RodimusConvoy:
LOL Rare in this day and age. Good for you. :good: I wish I could go back to the days when the only social networking there was were beepers, but...I'm hooked. :crying:

What's weird is I won't get a notification until I open the stock email app. lol Its took late then, I can already see if I have email or not.
[Epic 4G Android Development] Dougrun:
im on 4/1 and the boot logo froze but if i let it work, it reboots again on its own and is fine. I think its actually upgrading fine, just the logo is wanky.
[Epic 4G Android Development] Kitteh298:
Anyone have a fix for bluetooth pairing? I am unable to use my torque app with obd2 bluetooth reader.

It tries connecting but then it reboots bluetooth.
[Epic 4G Android Development] UPdownLoAD:
Yup, your solution is to go back to CM10, prior to when Google made changes in the way Android uses bluetooth.
[Epic 4G Android Development] DynamicN:
Remove boot animation in system/media
[Epic 4G Android Development] VaderSS:
Same probem I am having. I had to go back to CM10. After getting a taste of CM10.1, it was a hard move to make...
[Epic 4G Android Development] AuGmENTor:
Yeah, there's a lot of us in the same sh!tty boat.
[Epic 4G Android Development] TracerBullitt:
AND my headphone mic doesn't work...

...Runs away, chuckling.
[Epic 4G Android Development] RodimusConvoy:
Yeah it was fun while it lasted but I'm getting off the CM10.1 train.

Gonna wait till about Saturday to try Slim and Baked before deciding if I should just go to Legacy. I like the look and feel of CM10.1 (still on that monthly for last month) I just can't deal with that battery life. Plus...seems the voice is Google Navigation is sped up. I don't know if that's a known bug or something that Jelly Bean also has. No biggie, just a head scratcher.

I think the biggest thing I'll miss from CM10.1 is the cube-out transition. Yeah I'm easily pleased. :o But I think the other ROMs has it too, so...no real loss. Not sure about Legacy, though.
[Epic 4G Android Development] robrob:
I flashed the 4/4 nightly and it booted fine. The known Bluetooth instability is my only issue with 10.1 (yes I know it's an upstream Google issue).
[Epic 4G Android Development] DynamicN:
How long have you had your battery?
[Epic 4G Android Development] RodimusConvoy:
The entire life of my Epic 4G. Bought it way back in August 2011. Never had a single problem with battery life until I went to CM10.0. I was hoping the monthly for CM10.1 would fix it, but no.
[Epic 4G Android Development] DynamicN:
Battery life on cm10 was always terrible for me and cm 10.1 was a little better. I had my battery a couple years as well and baught a brand new s2 1800 MaH oem battery (which fits in our phone no problem) and it was a lot better. I can easily get a full day off one charge with over 4 hours screen on time now. Just a suggestion but I'd recommend a new battery because it's probably close to the end of it's life span.
[Epic 4G Android Development] cybershawngates:
10.1 has the best battery life, much better than stock. I'm running 10.1-20130316 build. Tips:

1. Make sure 4g is off

2. Make sure google talk is signed out (default is signed in)

3. Google now can be a battery killer, but you can switch most / all of it off. Click google search bar, configure it initially and choose settings --> google now and either turn it fully off or keep only the features you need. I keep traffic and weather everything else off. My battery can last a whole day even with heavy push email and some light SMS/MMS.
[Epic 4G Android Development] didhiy:
epiccm team has wrote a nice post about battery drain issue on their blog, I think battery usage became a big problem since CM9 ;) it's not our device specific issue

jb has a project butter, but gb was a true power saver :D
[Epic 4G Android Development] RodimusConvoy:
I mean I'd agree if it did this while I was on regular ol' rooted Gingerbread FC09. But it didn't. Before going to CM10.0, I'd go hours before it taking just a little hit. Now that I'm on CM10.1, yeah it shows a little improvement, but not much, not enough that I'll keep the ROM anyway. It may be time to get a battery based on age alone, but the length of charge and this ROM seem to be connected.
[Epic 4G Android Development] cybershawngates:
definitely get a new battery - i have like 4 of them and a spare charger. I can last a whole day and at the end of the day I just swap in a spare, like a cartridge in a game console. Also, running FC19 if that makes a difference http://xdaforums.com/showthread.php?t=1599752
[Epic 4G Android Development] RodimusConvoy:
Well, again, no problem until I switched ROMs, so for now I'm blaming the ROM. I expect my battery will go back to normal on a NON CM10.0/10.1 ROM, though I may try others just to be sure.

Also, that FC19 ROM doesn't look worth it, to be honest with you. If I downgrade, it'll be to the Legacy ROM. It seems like a super-charged version of FC09, which is just fine with me. :)
[Epic 4G Android Development] Sesquipedalian:
I don't have any battery life issues on CM 10.1. It's pretty good, IMO. Though I do have a relatively new 1800 mAh battery. I still carry an extra one around with my just in case, but I rarely need it. I usually make it through a day.

I would recommend a new battery to anyone having issues. It's cheap, and then end up having your old one as a spare. The bluetooth issues on CM 10.1 suck, and there's no real way to sugar coat that. I hope they get them fixed soon.
[Epic 4G Android Development] danipoak:
I find it interesting so many have battery issues on CM10.1. This rom gives me the best battery life hands down. I leave 4G on all the time and I am always signed into gtalk and I get 18ish hours easy. I'm not exactly sure what the bluetooth issues are. Only problem I have is when I get in the car it starts playing a random playlist. Usually I like it's choice though.
[Epic 4G Android Development] RodimusConvoy:
Looking at the battery for my Epic 4G, its a 1500 mAh battery. Aren't the 1800s for the Epic 4G Touch? And they fit in a regular Epic 4G just fine?

Looking at Amazon.com they are pretty cheap, though there seems to be a ton of bad reviews for the 1500 whereas everyone loves the 1800.

---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------

Well I guess I should ask which battery do you have, the 1500 or the 1800?

LOL :D
[Epic 4G Android Development] DynamicN:
Yes, the 1800 mah s2 touch battery fits our Epic's just fine.
[Epic 4G Android Development] bbelos:
EXPERIMENTAL TEST BUILD:

This is aimed at the bootanimation lockups many of you have been experiencing. I would request anyone willing to test it, to please test this build and let me know if anyone still experiences the lockup. No guarantee that it's fixed. Side note: If the lockup still occurs, it appears a reboot will resolve it.

Bonus feature for your trouble: Working car dock audio.

Download: cm-10.1-20130408-EXPERIMENTAL-epicmtd.zip
[Epic 4G Android Development] UPdownLoAD:
I would test it, but that was your 666th post...... :angel:

I'm staying on last month's experimental M2 release for now, though I'm sure several others will jump on this :highfive: Thanks though!
[Epic 4G Android Development] bbelos:
Here you go, try this one. :p

cm-10.1-20130408-EXPERIMENTAL-epicmtd.zip
[Epic 4G Android Development] Jshugzda:
Thanks Bbelos, I will test this build and report back.

EDIT: No boot animation Lockups on this build. Thanks again Bbleos and happy flashing to all!
[Epic 4G Android Development] ecooce:
bbelos, it seems when you clear dalvic cache, boot locks up, this is on a week old nightly though.

And anyone that is having a reboot issue may want to move to the CFQ scheduler, I couldnt get past 16hours without a reboot using SIO. Now back to normal, dosnt reboot during a phone call anymore either...

Follow me on...

Youtube http://bit.ly/To93d6

Google+ http://bit.ly/RqyYPa

Facebook http://on.fb.me/RFIADb

Twitter @Jason_Feriani http://bit.ly/Qa3Yyu
[Epic 4G Android Development] TracerBullitt:
...Not that this was directed at me, I'm interested in the part that keeps my phone from rebooting while talking to my grandparents, but I have no idea what any of this means. :P
[Epic 4G Android Development] ecooce:
Go into system setting/performance, but defaukt id deadline if I remeber right, so switch to CFQ...

Follow me on...

Youtube http://bit.ly/To93d6

Google+ http://bit.ly/RqyYPa

Facebook http://on.fb.me/RFIADb

Twitter @Jason_Feriani http://bit.ly/Qa3Yyu
[Epic 4G Android Development] Shinydude100:
Note only for Virgin Mobile Users in regards to CM 10.1:

As always I stay a few builds back, if not weeks back before moving forward to establish checkpoints of functional MMS. It seems some builds get stubborn and refuse MMS to work (perhaps commit changes, and then reverts, and so forth)

I won't list every single last build that works solid with MMS (should be most of them) however I will establish a few noteable builds for your stability's sake.

Build 03-23-13 -MMS works on dirty flash, (although I recommend a clean install)

And for those of you who like to be a bit more up to date:

Build 04-06-13- MMS works on clean install. Dirty flash will be iffy.

As always, at your own risk. However this is meant to help you not having to risk much. Some people don't have time to read forums because of how busy they get in their lives. This is meant for you.

Edit: for clarification purposes.

What I mean when I say Dirty Install: flashing a newer cm build of the same cm version on top of a newer nightly /stable release.

What I mean when I say clean install: wiping data, system, cache, dalvik, boot (optional)

As for Odin: I'll leave that up to each user's judgement, I odin probably once or twice in 3 months time, if I'm messing with my phone a lot, sometimes 8-10 times a week. I can however, go 6-8 months without using Odin.
[Epic 4G Android Development] dfrhodes:
I've been having this problem on all builds for the past week or so. Only on the first boot though. Battery pull solves it.

I'm using CyanDelta however so I wasn't going to say anything until I had a chance to full wipe.

d
[Epic 4G Android Development] bypod:
Mine froze up. I cleared Cache and Dalvik before updating. Battery pull and reboot worked. Also, DOCK AUDIO. Thanks for the bonus. :D
[Epic 4G Android Development] TracerBullitt:
I'm a little rusty with odin and all that but am currently contemplating making a new theme thru Nova and UCCW. I figured going to a solid build would be best. Would a "clean install" involve odin or should I just wipe data and load a newer build? I remember using odin helped me resolve some memory issues in the past.

I also wanted to add pie navigation but I'm not sure if that's available and know its definitely not included in the last M2. Does anyone know if its included in the latest builds or still not for us.
[Epic 4G Android Development] propjockey:
Regarding the experiential build: after wiping system, cache, and dalvik I installed the build and gapps. Rebooted fine without boot animation issues. Seems to be running quick and clean. No issues noted, but I can't comment on dock audio. I'm sure many users are stoked to have that back :thumbup:

I'll stick with it for a while to really work through everything, but it runs great so far. Thanks bbelos for the great work. It is much appreciated :beer:
[Epic 4G Android Development] ecooce:
edit: sorry everyone, but it may actually be " allow purging of assets " causing reboots, I may have jumped the gun for the solution to the issue, ill keep testing...

It seems I changed more than SIO to CFQ, because when I checked the " allow purging of assests" it rebooted 5min after, and during a phone call. Now before changing that setting I had made over 10 calls lasting more than 10min, so, ill keep testing the rest of the night...

Follow me on...

Youtube http://bit.ly/To93d6

Google+ http://bit.ly/RqyYPa

Facebook http://on.fb.me/RFIADb

Twitter @Jason_Feriani http://bit.ly/Qa3Yyu
[Epic 4G Android Development] Shinydude100:
It was just a stable checkpoint/reference for those on Virgin Mobile, however, if you prefer that to get both Sprint and VM users interested, they make a fine choice (for now) I edited the OP with what I meant in my own terms. You could wipe data, & system, or odin. Either should be fine unless you find unfamiliar or abstract behaviour, then you may benefit from an odin.
[Epic 4G Android Development] bbelos:
TEST BUILD

OK, so it seems that these jpeg optimized bootanimations are causing our lockups. Here is a build that uses the older, non-optimized animations. (It's the same animation, just the file is 100K bigger :rolleyes:) I have cleared my dalvik a couple times and it seems to be back to normal. Unless anyone still experiences and animation lockups, I will merge this fix for the next nightly.

cm-10.1-20130409-EXPERIMENTAL-epicmtd.zip

P.S. This still has the car dock audio for those of you who would like to use it (until I can get the fix merged into the nightlies).
[Epic 4G Android Development] vizionforever:
Awesome cant wait to try this out...Thanks! I'm still on the 130303 nightly With no problems cept the fast talking nav which I like and I dont use bt for anything so dunno if there is an issue there...
[Epic 4G Android Development] wakkigy:
Also got the lockup with 0408, will try 0409 now (finger cross)

Aside from the initial lock up, does anyone experience issue with SD card randomly disconnecting, so any of the app installed there will not work (and cannot read the SD card either)? Going to try the different scheduler to CFQ for test too.
[Epic 4G Android Development] cornaljoe:
Zomg that was the issue! I actually created a new bootanimation for Baked with the optimized jpegs and got it working. I then synced and built a new ROM for release. But when tested it froze again... I was so confused lol. Seems like some bootanimation creators haven't switched over yet. Thanks for the fix bbelos.
[Epic 4G Android Development] wakkigy:
Experimental 0409 worked great. Smooth boot animation w/o any lock up.

Google about the SD card problem and looks like my SanDisk 32GB class 10 might be dying after just 6 months of use :mad:
[Epic 4G Android Development] the john:
I was just thinking about downgrading to a GB ROM. Obviously I'll have to wipe everything, but is there anything else I should know about? Repartitioning, etc.?
[Epic 4G Android Development] vizionforever:
Try a different sd card or take it out and put it back in..When I take my sd out and the system is booting up or the system is running at a certain point restart or reinsert usually cures.. be patient dont be trying to hammer with requests before system auto checks sd
[Epic 4G Android Development] AuGmENTor:
It's more than a wipe you know. You have to ODIN back to stock and go from there.
[Epic 4G Android Development] ProperNoun:
Read this before but is that 'best practices' advice or am I missing something? Flashing the ROM should to be enough, right? For example, I go back to a very well tuned CM7 backup often enough and all I do is flash a CM7 ROM (which I just use to repartition, etc) and then restore my backup. Same with going back to CM9, 10, and more recently 10.1.
[Epic 4G Android Development] AuGmENTor:
My understanding was that if you wanted to revert to any ROM pre CM10, you had to ODIN due to the way it creates and sizes partitions. Keep in mind, my understanding never goes much past "soft focus." Hopefully someone with a brain will show up and let you know. But I do believe it's more than a safe practice thing.
[Epic 4G Android Development] DynamicN:
Augmentor is correct, cm10 changed the partition sizes because our phone was never meant to run anything above 2.3 so you will have to odin back to stock first then flash your rom of choice. Of course you can always try to flash your rom of choice over what you're running now without odin'ing and may get away with it but it will not run right.
[Epic 4G Android Development] mbellot:
My understanding, and experience, is that the new CM10 partitions don't prevent installing older ROMs - it's just not optimal.

I've bounced back and forth several times between TPR2.21 (an MTD TW GB ROM) and CM10/CM10.1 without any issues.

The first time I created a nandroid backup of my TPR system, CM10 repartitioned the phone (larger /system, smaller /data I think) and then installed just fine. When I'm done playing I simply did a nandroid restore of my TPR backup and everything was back to normal.

I've gone back and forth several times since the first (without ever touching ODIN). Right now I'm running TPR and have the following partition sizes according to df.

/data = 676M

/system = 268M

Are those correct for CM10 or earlier?
[Epic 4G Android Development] bbelos:
ODIN back to stock is the easiest method to describe, but it is not the only way. Reverting to any pre-CM10 MTD rom only requires you to be on the appropriate kernel for that rom before you flash it or restore a backup.

You can either advanced restore the boot image, reboot to recovery and then do a full restore Or you can flash the rom, reboot to recovery and flash the rom again.

Even those steps aren't always necessary, depending on the size of your backup, but that's more than we need to talk about right now :p
[Epic 4G Android Development] bbelos:
Those are correct for CM7 & CM9. CM10 required more system space to fit the rom plus gapps, so the partitions were resized to ~601 for /data and ~343 for /system.

Restoring an older rom from CM10 will work in one step as long as the backup has less than 600MB of data.

Restoring CM10 from an older rom requires 2 restores. At minimum, the boot, then reboot to recovery. And then the full restore. Otherwise the CM10 system backup (343megs) wont fit inside the older kernel's 268meg system partition.
[Epic 4G Android Development] mbellot:
Interesting. I assumed that nandroid didn't actually resize the partitions, it would just reformat and use them.

You learn something new every day. Thanks! :good:
[Epic 4G Android Development] bbelos:
No, you're right, nandroid won't resize the partitions. That's why you would need to reboot to recovery, which reloads the new kernel for the proper partition sizes.
[Epic 4G Android Development] bbelos:
Here's a little something I've posted a couple times in the past:

EDIT: TW MTD Rom partition sizes are equal to CM9 in these examples.
[Epic 4G Android Development] AndyYan:
As for the different partition problem related to flashing, here's my experience:

1) You DON'T have to Odin to stock if you're FLASHING a zip with different partition layout (e.g. CM10.1 -> CM7). Just additionally wipe /system and flash the zip.

2) The partition difference comes as a problem ONLY WHEN NANDROID RESTORING. For example if I'm now CM10.1, if I simply wipe everything and restore a CM7 nandroid backup and reboot, it won't boot due to unfit and un-overwritten partition layout. To switch between nandroid backups with different partition, wipe everything and flash a ROM with the same partition as what you intend to nandroid restore. Reboot recovery, wipe everything again and restore the backup.

Sent from HTC Incredible S @ PACman v21
[Epic 4G Android Development] TracerBullitt:
Is anyone still having reboot issues during phone calls and such?
[Epic 4G Android Development] ecooce:
Seems I found my issue with the reboots on call (knocks on wood) for me anyways, was the option "allow purging of assets to free RAM". This option does help to keep the phone snappy, but can cause serious issues aswell.

Follow me on...

Youtube http://bit.ly/To93d6

Google+ http://bit.ly/RqyYPa

Facebook http://on.fb.me/RFIADb

Twitter @Jason_Feriani http://bit.ly/Qa3Yyu
[Epic 4G Android Development] Shinydude100:
I should be most ashamed for this bold confession since it may be interpreted wrongfully as discouraging a CM Dev to drop focus on stock but..

I miss your shadow kernel Bbelos. Deep down inside I bet many others do as well.

*Back on topic* I never did get ahold of Francois Simund to get some newer sound driver module love going by the time 10.1 rolled out.

*really back on topic * Phone works like a charm for me without messing with schedulers and so forth. Then again YMMV in how we each uniquely use it.
[Epic 4G Android Development] kvan1707:
I reverted to GB for Shadow Kernel! Getting 16+ hours on battery!

This is the OG battery from 2 years ago that has gone threw my washing machine 3 times now. :)

Still love CM, still reading and following.
[Epic 4G Android Development] TONYSALEM78:
Hey. I am using a Epic flashed to MetroPCS.. on stock gb fc09 my 3g works perfectly, I also used to use cm10 stable and it worked there also, now with cm10.1 I get no data besides when I run wifi.. any thoughts?
[Epic 4G Android Development] UPdownLoAD:
Please read/search. It's been covered before, even just a few pages back (and separate threads).