yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] styles420:
That's kinda weird - usb usually gives me much better speed than wifi. But I have also noticed problems with my 4G in general lately. Speed tests might read high speeds (4-5 mbs), but downloads still crawl and fail (even on my phone).

I think it could have something to do with Virgin rolling out 4G support - the rumors I have seen indicate that Virgin will be getting Sprint's WiMax network as Sprint switches to LTE. Maybe the rumors are true, and the WiMax network is becoming too taxed... I'll have to experiment with an older nightly or something to see whether this was introduced with a build or with Virgin's 4G support, lol
[Epic 4G Android Development] gundamfan:
just updated from CM9 and..WOW! what a difference!!! It's crazy fast and smooth! Definitely a daily driver, thank you devs!!!

But now a couple of issues I noticed running 10/18 nightly +FC09 modem:

1. As in CM9 and looks like CM10. Still having issues with bluetooth and my car. Constantly connects/disconnects when in sleep, or even during phone calls. Solved the issue by keeping the power plugged in. I know there was a few people who had this issue on CM9 as well. Something to do that the phone shuts off bluetooth when in deep sleep, but when power is plugged the phone never really gets to deep sleep?

2. Once I'm out of range of a 4g signal, the phone doesn't reconnect to data (3g). I tried turning on airplane mode on/off, only way to reconnect is by restarting phone.

am i the only one experiencing this?

Minor annoyances, but was just wondering.

thanks!
[Epic 4G Android Development] neuton:
A quick question has anyone gotten flash to work properly on cm10 on the epic 4g phone?

I looked at a guide on xda but it didn't work even with browsers they suggested
[Epic 4G Android Development] TracerBullitt:
Here's what I've used. Can't really say all its done for me, I've never reached the two day battery phenomenon others seem to enjoy.

http://androidforums.com/triumph-al...cts-scaling-other-battery-related-issues.html

I might try this...
[Epic 4G Android Development] BoominSVX:
There's always better ways to calibrate the battery for your phone, but I've always noticed the first time I use Nav with the phone plugged in, the battery gets hot as heck and it falls out of whack. Other ways do sound better, but this only takes a minute or two and gets it a little more accurate than it was prior.
[Epic 4G Android Development] pablomentabo:
Running stock here & the Car Dock but since this update I do not get any audio out of the phone speaker when plugged into the dock. I searched this thread but didn't see anyone mention this. If there is anyway I can help then PM me or post here & I'll try my best to get back to whoever looks into this. It would be nice to get my spoken directions back when I am using Maps in the car. Thanks & and always CM rocks!
[Epic 4G Android Development] chrishighs:
It works for me. I just restored an old version of flash with Titanium and I have no issues with it.
[Epic 4G Android Development] slybarman:
Did you go into settings, advanced, dock and check the box?
[Epic 4G Android Development] I Brick Phones:
I've noticed this as well. Up until the last couple builds, reboots were almost non-existent. But when I went from 10/10 to the 10/17 build, i'm getting at least several (if not more) reboots per day.
[Epic 4G Android Development] styles420:
The phone automatically wipes the battery stat file when it reaches a full charge... so the summary of your method is:

1. Charge to full

2. The phone wipes the stats without your interaction

3. Kill the battery entirely

3. Reboot into recovery to wipe the stats file (again)

4. Charge to full again (which could wipe the stats a third time - go redundancy!)

If any part of your process actually does improve battery life (and I'm not saying that it doesn't), then it is not because of wiping a file that already gets wiped every time the phone is fully charged. But rebooting the phone gives a fresh start, which can flush out any apps that were supposed to close but stayed present in the background, etc. Also, giving a full charge in one session may give a more consistent discharge than the usual rollercoaster of charging it a bit, discharging for a while, charging a bit more, etc without reaching 100% each time.

My point is that your method might work wonderfully, but not for the reason so many people still like to believe :)
[Epic 4G Android Development] beltsnspoons:
You should also check out jelly x, especially if you're getting a little tired of all the blue. I believe the authors name is vicinio, either way it can be found on the cm10 themes stickie on the android themes thread. All this guys themes are worth checking out. Nice break from the same old holo themes.
[Epic 4G Android Development] davidh59:
Odd, I've not had a reboot since putting on 10/17. I'm at a little over 53hrs and listening to music and texting now. Maybe there needs to be a bounty on finding the cause of the reboots. LOL!

oops just looked I lied I'm on 1018
[Epic 4G Android Development] Bloodwar1988:
My CM10 updater now says:

Samsung SPH-D700 Installed: No CyanogenMod

CM10 is not provided for this device

Retry in the future

It really does not matter since I can still just download via PC, but my CM10 installer did work up until I updated to the Oct 18th nightly.
[Epic 4G Android Development] pablomentabo:
Yes. I've tried it with it checked, without it checked. With and without resetting the phone after checking or unchecking the box and same issue. It only started after that option was added and the way I updated was thru the CM Updater method. If there are any suggestions for what I can do then I'm game... I just figured someone else would have this issue by now so I put it off and have been using CM Updater to go to each nightly after the one that added this option hoping it'd be corrected already.
[Epic 4G Android Development] AuGmENTor:
The one variable I see is the CM updating method you're using. Seems to be the common denominator with little annoying problems like that. I use bt, but a while ago when I didn't I had to use a audio bypass app, available in the play store (or Android Market as I'll always know it as...) so perhaps, either a fresh wipe, reflash of an honest zip, or the bypass app are probably your best bets. I know with the newest dock integration, you're not supposed to need the bypass, but it may save you a wipe.
[Epic 4G Android Development] Bloodwar1988:
Since my PC does not play well with Odin, Is there any other way to go from CM10 to another rom without having to use it?

I can get my phone to be recognized by Odin, but every time I go to flash via the program, my PC will instantly reboot.I really dig CM10 and everything, but think I am going to find something else until the few bugs that are actually bothering me are all worked out.
[Epic 4G Android Development] BloatedDuck404:
Just flash CM9 or something then reboot recovery flash it again. I mean I tried CM10 alot and I never used odin. Im on a sense rom currently last time i used odin is when i was on miui and i bricked.

Sent from..........iOS
[Epic 4G Android Development] pablomentabo:
Well I used the CM updater prior to the nightly that added the dock integration and didn't loose sound then. I think it's the new integration but I'll look into it more when I have the time. For now I've just been using Maps w/o any voice assistance. I never had to use that bypass app so I'm not sure of the apps name to test it out
[Epic 4G Android Development] Nashdogg:
What version of Odin are you using?

Sent from my SPH-D700 using Xparent SkyBlue Tapatalk 2
[Epic 4G Android Development] rundmcarlson:
I am only posting what I had learned way back when we were trying to get the hero running for more than 8 hours. It worked great back then, and it still works now. I don't see why the battery stats would clear every reboot. It was my understanding that the battery stats were simply the full charge and no charge voltages put out by the battery, since batteries put out less voltage when they are running out of juice. The % you see is just based on an extrapolation based on those 2 data points. Thats why people who use 2 batteries never get the same performance out of both of them, because no 2 will have the exact same voltage at a given charge level.

---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------

Although I can't seem to figure out why that would work, it is interesting that it does, because the internal resistance of your battery and the resistance of all the components increases when they get hot. The hotter the device is, the more power it should consume, so its odd that you are getting more accurate numbers and not just more rapid battery drain.

---------- Post added at 07:45 PM ---------- Previous post was at 07:45 PM ----------

Looks good, but I love blue lol. Thats one of the reasons I use mattedblues.
[Epic 4G Android Development] AuGmENTor:
Oh its something simple just search USB audio bypass or something like that. I think it was a work around for the CM7 days.The only curiosity to me is why no one else is in here noting similar problems, as so many use docks in the same way you are. 9 times out of 10, when I have a problem that no one else has my first guess is a glitch in the flash. Typically, a wipe and reflash fixes it. I also usually redownload the zip just to be sure it's not the file itself. I don't do OTA updates, so I don't know the protocol for MD5 checksums, but receiving a file over network of that size opens up way more potential points of failure, which is why logic would dictate looking there first.
[Epic 4G Android Development] styles420:
It's cool, man, I'm not attacking you. I believe you when you say it works (hell, I've done it myself). I think the full discharge followed by the full charge cycle has more to do with it - the stats file is used in some way to determine the current charge, or it probably wouldn't exist. I base my opinion on information from various developers, including information released by a google developer a while back that stated that the stats file is wiped at full charge in order to collect fresh data (among other details that I can't properly remember).

I think what happens is that, since most of us probably don't always fully charge the phone due to busy lives and such, the data can become stale and inaccurate, containing data from multiple charge cycles instead of just one at a time. Fully charging should be enough to fix that, but I agree that it doesn't seem to be as effective as one would imagine. What I don't know is whether the stats file is deleted at full charge if you charge with the phone off - maybe that's what makes the wipe necessary, unless you power on and let it hit 100% again (since it will probably be at 99% or lower by the time boot completes). To be honest, I think we're all still missing a variable or three that are key to a proper understanding of the process. But on the other hand, I was the kid that took apart all of his toys (and rebuilt them to still work), so my idea of a full understanding might be above and beyond what is normally good enough, lol
[Epic 4G Android Development] AuGmENTor:
I thought with the invention of lithium ion batteries, there was no longer a memory loss a a result of short cycle charging?
[Epic 4G Android Development] slybarman:
Correct. Lithium batteries degrade based on how long they are kept above or below their nominal voltage of 3.86v/cell - roughly 50% charged. They do not like to be above or below that voltage. But, they do not develop "memory" like the old Nicad or Nimh batteries did. over time as they spend their lives above and below nominal voltage the internal resistance of the cells will start to go up and they will not hold voltage under load as well as they once did. You will notice they get a lot warmer during charge or discharge than they used to.
[Epic 4G Android Development] styles420:
You are correct, but this is a different issue (although there are apparent similarities, their causes and solutions are completely different).

The memory issue with NiCad batteries was a limitation of the hardware. With the lithium ion batteries, the symptoms appear the same on the surface, but it isn't the battery itself that has the problem. I guess we could possibly describe it as an artificially imposed reproduction of the symptoms, if that makes sense...

The stats file has to exist for some purpose. Since it does get wiped, it can't be simply a long-term history for record-keeping purposes, so it makes sense that it has a more short-term purpose. For those reasons, I believe that the stored data is used to make a more accurate determination of the current battery status based on the most recent behavior. If the system was designed to calculate based on a single discharge cycle, then partially charging would leave old, now irrelevant data in the file. Depending on what is calculated from the stats, and how it is calculated, that irrelevant data could throw off the calculations in ways that could result in a less efficient charge. There are several ways that this could affect battery life, too many to speculate on without more information to narrow down the possibilities... but regardless of the details, we have more than enough first-hand reports from other users to assert that it does have an impact.

My original point is more on the path of properly acknowledging what we do and don't know, and to keep an open mind about the unknowns rather than taking a religious blind-faith assumption and claiming to know things that we're only guessing about. I've seen plenty of cases where people forget that a detail was only assumed, making it more difficult later for them to accept the newly discovered facts when they don't match the old assumption. Hell, that's the basis of organized religion, the crusades of the past and the modern-day jihad ;)
[Epic 4G Android Development] pablomentabo:
Thanks, next time I update I'll go through the normal process I was doing to see if it could be how it was flashed or wipe and start again. Thanks for the insight though.
[Epic 4G Android Development] neuton:
Is it possible for you to upload it. Also what browser are u using that it works with no problem?
[Epic 4G Android Development] TracerBullitt:
Yea so ...what battery are you using again?
[Epic 4G Android Development] Dropple:
3 days no update from CM :(

Failed on building on jenkins

This day will be not any update too :(
[Epic 4G Android Development] davidh59:
I'm using the Epic Touch battery, I usually get about 18hr of normal use. Some of the nighltlys seem more stable on my phone than others.I had my first reboot on this one last night before I put it on the charger.
[Epic 4G Android Development] shiloah:
Just google flash and apk download the newest one
[Epic 4G Android Development] AproSamurai:
Lol oh yes, we've abandoned you.
[Epic 4G Android Development] jctello1:
Call me crazy.......but I feel an awesome update coming very, very soon...........

Undefeated CyanogenMod10-B10/17
[Epic 4G Android Development] weldsmoke:
This guy figured out the usb issue worked for me no proplems .
[Epic 4G Android Development] bbelos:
This is a fresh build for testing, so it's as good as a nightly except better. :)

**As usual, these changes require kernel modifications, so please don't tell me it's broken if you're not running the stock kernel.**

Bonus test features:

- For the 4g users: This has a patch to keep 4g on during sleep. Let me know how it goes.

- Preliminary Touchkey Brightness control: Accessed through System->Advanced. Options for 100%, 75%, 50%, 25% & Off. I am still tweaking the actual brightness values (just realized that the Off option is still barely visible under very low light conditions.) Also, occassionally when changing the value, the touchscreen will become unresponsive for a few seconds while the controller is being reset. But no need to worry, just bear with it if it happens.

- Preliminary Vibration intensity controls: Also accessed through System->Advanced. Use the slider to control the haptic feedback. There is also a test button. **Word of warning** Try not to adjust the slider while the test is active. It seems to have the possibility for the intensity level to become out of sync with the slider value, although I was able to resync it after a few tries.

Download: cm-10-20121021-UNOFFICIAL-epicmtd.zip

md5sum: ce332fc4e447da35edefa0eb00ecd3b2
[Epic 4G Android Development] socos25:
Awesome I hope I get to try this soon. I had to take my phone in to a Sprint store after flashing a sound app. The thing won't even go into download mode anymore, even with the battery out. My first true brick since I've had my Epic. I'm missing it greatly.
[Epic 4G Android Development] AproSamurai:
I'd like to say, "how?" To try and figure this all out, but O___o lol.
[Epic 4G Android Development] Kkthnxbye:
Not sure if it is me or not but Wifi does not connect it is stuck on "Authenticating" yes im using the stock kernel

Nvm I rebooted and it worked, weird.. -.-
[Epic 4G Android Development] AproSamurai:
It had to do with an overall wifi sleep policy fix which was pushed, nothing to worry about. :)
[Epic 4G Android Development] socos25:
I would like to know how myself. I've flashed a lot of stuff on my phone and never experienced anything like it.

At first it would just get stuck at the Samsung screen. I couldn't go into CWM or anything else. So I tried Odin and it failed. Bought a new cable and it failed. Then my computer couldn't recognize the phone so I went through the entire restore a brick thread and went through all those steps... Eventually I couldn't even get the phone in download mode... Shortly before all this happened I dropped it and the battery shot out of it. That was a day or two ago, but I'm wondering if a cable isn't borked inside or something. Hopefully the Sprint store fixes it up.

Edit: Called Sprint this morning, they've ordered me a new phone, they couldn't get it to work either.
[Epic 4G Android Development] Bloodwar1988:
I have got it to work now. I simply reinstalled windows and the USB drivers and the PC now recognizes and flashes with no problems.
[Epic 4G Android Development] 1999TL:
Switched from CM9 to CM10. what a difference in speed. Even upon initial flash CM9 seemed to lag. CM10 flies compares to CM9. Thanks fellas. keep up the good work fellas.
[Epic 4G Android Development] Dougrun:
1018 build battery life is definitely worse that previous builds. the only app i added was gosmspro so maybe thats it.
[Epic 4G Android Development] styles420:
"Simply" reinstalled windows...? Ouch. That's dedication ;)

But on a serious note, I'm glad to hear that you got it working :)
[Epic 4G Android Development] omair2005:
chances of this being included? looks VERY promising

http://xdaforums.com/showthread.php?t=1774503
[Epic 4G Android Development] AproSamurai:
Read the last couple of posts, it's currently device specific as that developer owns just that device. It's promising yes, it's probability to come to us, is beyond me.

Though you're welcome to see if he'd be willing to work on it for the Epic and help him do so if he has the time, if not it's perfectly understandable just the same. :)
[Epic 4G Android Development] galahadUSA:
This morning I downloaded my nightly, reinstalled gapps and remembered to re flash the new touch cwm. What I forgot was to boot into recovery first and then boot system.

Had this beast of a phone back up and running in less than 5 minutes!

Odin is our friend even at 5 in the morning...anyway, Apro and all the other cm team members Thanks for bringing JB to our Epics.

And thanks a million learning me a thing or two!

You guys f'ing ROCK!!!
[Epic 4G Android Development] shiloah:
After flashing 10/22 nightly I can't seem to get mms messages to download just a gray box appears. And says downloading and never completes, I've tried on 3g 4g and wifi. Anyone else having this issue?
[Epic 4G Android Development] rando991:
It was fun while it lasted. Switched back to FC09MTD to enjoy better battery and cooler phone (for me). CM10 was the first non stockish ROM I've ever flashed other than the MTD FC09. I kind of got addicted to flashing nightlies for a while. Battery life on CM was ok until I started using it, then it sucked power dry. The CPU area would get really warm too, but I went back to GB and all is well now. Probably a little too much ROM for too little RAM on the phone...definitely not the fault of the CM Team. Thanks for all the work though!
[Epic 4G Android Development] nickknaack:
Is the nightlies link down for anyone else? I get an "oops" from google and no website when I click on the link for the OP.
[Epic 4G Android Development] Nashdogg:
Worked for me just now. Click on " get.cm" in the OP and Try the short link.

Sent from my SPH-D700 using Xparent SkyBlue Tapatalk 2
[Epic 4G Android Development] nickknaack:
Indeed, it is now. I tried the same thing earlier... maybe the server was buggy.
[Epic 4G Android Development] AuGmENTor:
Always happens when I new nightly posts. People are downloading it like crazy. Is there a way to see the stats of just how many times these are downloaded?
[Epic 4G Android Development] I Brick Phones:
Not sure what you might have running on your phone, but for me the battery life has been as good as it has ever been with any rom, and my phone only gets hot when using navigation
[Epic 4G Android Development] AuGmENTor:
Agreed.
[Epic 4G Android Development] DurhamHusker:
During preliminary testing, 4G during sleep is staying active. I'll test more tomorrow with the hotspot and let you know how that goes.

Thanks!
[Epic 4G Android Development] WoodmanMN:
I agree as well.

When I first put CM10 nightlys on my Epic4g, I left Google Now on all the time. That was a huge battery drain for me. I always have constant drain because I only get one bar of signal in my office, and average 3 bars out and about, but as of 10/07 or thereabouts, battery drain has been as good or better than running stock gingerbread. Add in the much faster speed of the phone (even only clocked at 1ghz vs my 1.2 on CM9) and it's full of win.

I do run an Epic4G touch 1800mAh battery (with a stock 1500 as spare for heavy use days) which buys me extra time, but I find that overall the phone is much better and more efficient on CM10.

Your mileage may vary, but I can't imagine going back to stock.
[Epic 4G Android Development] bbelos:
Only saw one comment on 4g so far. Any comments on the touchkey & vibration contol features, good, bad, or indifferent? Maybe too soon to tell? Just want to get a feel for things in case there is anything major to fix that I overlooked.
[Epic 4G Android Development] I Brick Phones:
I am currently on the 10/22 nightly but am downloading your unofficial and will report back tomorrow on my results. I work in an area with really good 4g so should be able to give that a good testing...
[Epic 4G Android Development] DurhamHusker:
I noticed the 'unresponsive' attribute at work while changing the cap-key-brightness setting. Just waited a couple seconds and was OK. No issues there. I'm likely to leave it at stock, but it appears to work as advertised.

The slider for vibration intensity is nice. Thanks for that. I'll heed your warning about adjusting during the test. So far so good.

I'll try more 4G tomorrow.
[Epic 4G Android Development] ZenInsight:
I'm on EI22. Someone recomended I go to FC09 to stop random reboots. I then saw someone else mention the NS4G radio being much better. What should I do? Does it matter...and does anyone have actual experience with the different variations?

Thanks.
[Epic 4G Android Development] I Brick Phones:
I tested the vibration settings and noticed that if you move the slider to a different setting, test it, and then click the default button and then test again, the vibration intensity doesn't actually reset to the default. But other than that it appears to work as advertised.

I also tested the touchkey brightness and it works perfect. Nice to be able to adjust that.

Will report tomorrow on 4G staying active when screen is off. Any special tests or tools to use for that?