yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] Zeinzu:
Just had two random reboots back to back on the stock Beta3 Pre3 build at 1.2ghz using the built in performance settings. Both reboots resulted in bootloops that required battery pulls. First time was while watching a youtube video. Second time was scolling through app drawer.

I noticed the 600mhz step is in this kernel. I know "no one" is going to listen to or believe me (as usual) but I've had lag issues and occassional soft reboot issues with any kernel using this mhz step. I've tested a lot with other kernels, and performance and stability were always perfect for me if I manually disabled that step. I honestly believe the 1200mhz step is stable but also believe the kernel would perform better and more stable without the 600mhz step.
[Epic 4G Android Development] propjockey:
Me too. It happens with a bad signal mostly. But strangely it happens when I'm connected to my air rave too.
[Epic 4G Android Development] KennyG123:
Actually I noticed the 600 mhz hangs up on certain governors on my phone refusing to drop any lower. I believe!
[Epic 4G Android Development] Zeinzu:
It's a very buggy step imo. There's probably legitimate reason Samsung didn't use it.
[Epic 4G Android Development] GanBei:
Rooting D700

Would someone direct me how to root my Samsung Epic 4G D700? I tried following the instructions on androidadvices.com but they they only have instructions for the Epic 4G Touch.. Please provide downloads to what i need.. I installed the ClockworkMod ROM Manager but it says I need to root my device first..

I would like to use the CM9 but I understand my devices must be rooted first..

Here's my device info:

Model No: SPH-D700

Firmware Version: 2.3.6

Baseband Version: S:D700.0.5S.FC19

Kernel Version: 2.6.35.7

Build No: GINGERBREAD.FC19

Hardware Version: D700.0.5

Thank you in advance for any help you can provide..
[Epic 4G Android Development] ÜBER™:
... wrong place to post but I offer remote rooting services if you would be interested in that.
[Epic 4G Android Development] pdappcgeek:
Can I get the beta2 gps fix without installing beta3pre? I don't want to have to do everything over if a new release is on the verge.....
[Epic 4G Android Development] MДЯCЦSДИT:
Don't wipe data and you won't have to do anything over.
[Epic 4G Android Development] StoneRyno:
Since I flashed cm9 for the first time I've discovered a way to avoid rooting stock. I have been using Odin to return to stock between cm9 updates. After tw boots I shut down my epic. Go into download mode and Odin cwm but don't check reboot. Once complete I pull the battery for a brief time and put it back in. Then use the 3 finger boot into cwm and flash cm9. No root needed. :-)
[Epic 4G Android Development] amateurhack:
You are probably correct. I tried finding technical data for that, but don't have enough time right now to research it. There probably is something about the step frequencies that don't play nice at 600Mhz.

Anyone know right of hand the recommended step for the 1Ghz ARM A8? It may be that it's 60 or 120Mhz, rather than 100.

Or it may be just that Samsung found their modifications didn't work well at 600Mhz and left it out.
[Epic 4G Android Development] v8bait:
Been having a problem with CM9b2 since this afternoon. I have been on CM9 for a few weeks now, everything was working fine. This past weekend I started having a couple problems downloading an app from the market, was getting "invalid file" or something like that, but it was only for one or two things.

Today is something new... I was using my phone in the morning like usual, and tonight I cannot get 3g data to connect. Wifi works fine, but the signal bars in CM9 are grey when on 3G and they phone says "data network disconnected" in the settings page. Booting to FC09 also has no 3G icon and no data, and will not update profile or PRL. I am able to get data back on temporarily if I turn on google maps in FC09, but it doesn't stick through a restart. I tried clearing my aGPS data in case it thought I was outside the country or something. Anybody have this problem before?
[Epic 4G Android Development] Zeinzu:
Have you at all considered it's service, not rom related?
[Epic 4G Android Development] bighuta:
Yeah i gotta admit this happened to me recently, it turns out a sprint tower broke down for like 4 days. Good thing I didnt odin back to stock.. lol
[Epic 4G Android Development] AproSamurai:
In regards to the 600 MHz step, I'm removing it currently, however if I don't finish I'll get it after I get back from class. :)

Or at least upload the project to Gerrit.
[Epic 4G Android Development] Zeinzu:
I really appreciate you guys considering my suggestion. Makes me want to apoligize for how I've come across before towards you guys.

So... sorry about how I use to come across. And great work as always you guys.
[Epic 4G Android Development] v8bait:
I use an Airrave at my house, and other phones were working so it wasn't network related. But to update, I was able to update the PRL this morning to 60687 and 3G is working normally again. Does sprint try to block data from people who don't update their PRL? Seems like a backhanded way to keep data roaming costs down if that's the case.
[Epic 4G Android Development] Restola:
Maybe unrelated, but for about 24 hours starting some time yesterday I was unable to place a call on my epic via our airave (my fiance's epic worked fine). I called sprint's airave tech support and they said it was a known problem. Data for me was unaffected through, just outgoing phone calls. It's been resolved as of about noon today.
[Epic 4G Android Development] AproSamurai:
Ah, don't worry about it at all man, I've always understood where you were coming from even if we didn't agree, so speaking for myself. We're good. :)

Suggestions are always welcome if they're feasible to attempt, though some(more erratic) aren't.;)
[Epic 4G Android Development] Zeinzu:
Hey Apro. Will you be posting a link to said kernel here in the thread or on the cm blog? Not really in a hurry so much as I just wanna know where to keep an eye out for it.
[Epic 4G Android Development] AproSamurai:
Ah earlier today I was, currently due to circumstance no, there's a a bit of a large revamp being done by mkasick as we speak which addresses which files are to be touched with OC making it more ideal to do so, as well fixing the 100 MHz-200 MHz issue(which he's already done and upped to Gerrit for review), so it may take a bit. But know that it's being worked on if that's any consolation heh.
[Epic 4G Android Development] pvtjoker42:
awesome.. can't wait for new changes in beta 3!
[Epic 4G Android Development] MДЯCЦSДИT:
Yay, time to cherry-pick. Mind linking me to the patch on IRC via PM so I can cherry pick it when I get to a PC?
[Epic 4G Android Development] Zeinzu:
Sounds good to me. I'll be patiently waiting.

On another topic, from a standpoint of someone who knows better than I, do you think the bluetooth address issue being looked into might have any affect on issues like hanging up a call from bluetooth with the screen off, or bluetooth being able to connect with screen off? That and auto flash for camera not working correctly after a reboot till you manually toggle on/auto and flash not working for video recording are the only noticable bugs I seem to be having with cm9 at this point.
[Epic 4G Android Development] AproSamurai:
It's quite possible that it *MAY* have some effect towards that, though when it comes to that area of things I'm not the most aware, I've also been a bit out of touch due to school. What I'm thinking occurs is that our phone stops broadcasting properly on it's side when the screen is off(Probably obvious to everyone by now LOL), so making the address more prevalent at all times seems full of benefit to me as that is definitely tied into the problems it incurs, but that is the best answer I can give towards that. Methods to keep it up are being looked into.

Towards Camera related issues, I'm sure they're being looked into, I think the things which would cause more issues in the long run and in the future if untended are being looked into currently, and the quirky things will follow. If I didn't phrase that horribly.
[Epic 4G Android Development] Mama Luigi:
Just posting this for anyone else who encounters a similar issue - I have recently had a problem where if I plug my headphones in and then unplug them, I won't get any sound through the earpiece. How it typically happens is thus:

1. I turn on a podcast/music/streaming app to listen to something

2. I plug in a pair of headphones or possibly the 3.5mm input on my home stereo. Everything is working fine at this point.

3. I am finished listening so I turn off the app and unplug the headphones.

4. Next time I try to listen to music or make a phone call, I can't hear anything through the earpiece. The only thing that appears to work is if I turn on the speakerphone.

The fix that has worked for me has been to download an app called Wired Headset Routing Toggle. It's actually a widget. It allows you to manually switch between headset routing on and off. Once I turn it off, everything works again as expected.
[Epic 4G Android Development] Zeinzu:
Thanks for the feedback bro.
[Epic 4G Android Development] wtogami:
CM9 beta3-pre7

Epic CM Blog: CM9 beta3-pre7 needs testing

Simpler OC code

100MHz fixed

Capacitive button backlight options
[Epic 4G Android Development] Zeinzu:
On it.
[Epic 4G Android Development] wtogami:
And yes, 600MHz was removed. Thanks for bringing this to our attention.
[Epic 4G Android Development] zanderman112:
Running great, I have 100mhz back(*dance of joy*), and liking the new option for the capacitive keys. Too bad it doesn't have a built in screen filter, or else I could remove the app lol

~ Mr. Z
[Epic 4G Android Development] stevie13.xo:
Use RootDim itll save you battey too..
[Epic 4G Android Development] wtogami:
I just took a look at RootDim. On Epic CM9 it doesn't seem to be able to reduce dimness beyond what manual dimness setting in Settings > Display is capable.
[Epic 4G Android Development] stevie13.xo:
Oh dang that sucks..
[Epic 4G Android Development] Liner81:
Flashed beta3 pre7. (Good md5, wiped dalvic & cache) At first looked good, now stuck hard at 200hz. No other OC methods used, just under settings menu was using 100/1200 smartassv2. Had deleted throttle folder and unchecked the set on boot as directed.

Now got it freed up again with 100/1200 interactivex. I'll mess with it and see if it reoccurs.
[Epic 4G Android Development] zanderman112:
So, i'd be uninstalling Screen Filter...to install another app like it? Uhh....lol

What I'm saying is that screen filter is now half useless.

~ Mr. Z
[Epic 4G Android Development] BeerChameleon:
Hey guys, has anyone tried using the CM9 reloaded addon on this?

I will try later as i need my phone to work right now, but its pretty cool if it will work on ours: http://xdaforums.com/showthread.php?t=1531222
[Epic 4G Android Development] csmasn:
Tried long time ago...a POS mod, had to reflash back.
[Epic 4G Android Development] xopher.hunter:
Ran it forever, until I realized aokp has it built in lol. I personally had 0 issues with it.

Sent from my MIUI V4 Epic 4G
[Epic 4G Android Development] BeerChameleon:
well on aokp where is the setting to change the color of the pulldown? doesn't the reloaded have that? Also some of the status bar settings on aokp didn't work and change to my liking :(

I was just wondering if the reloaded settings had more and worked? :confused:
[Epic 4G Android Development] philowneus:
The back light option is amazing. No issues with pre 7.
[Epic 4G Android Development] wtogami:
Be warned it looks like he's replacing chunks of the operating system, and he seems confused that beta3 isn't released. If this breaks stuff don't complain to CM.
[Epic 4G Android Development] steelers_exe:
Yea, I had the misfortune of trying it out, and it ended up breaking my recovery for some reason, nandroids would restore properly. Ended up having to start over clean.

Sent from my Suped and Nyaned AOKEpic 4G. Swagger Up!
[Epic 4G Android Development] csmasn:
I told you.... :p
[Epic 4G Android Development] CapsLockKey:
Has the music playback issue that appeared in Beta2 get fixed in the Beta3-pre7?
[Epic 4G Android Development] csmasn:
Im having the best battery life than ever (b3- pre7). Thank you Devs.
[Epic 4G Android Development] tonysohn:
Same here. Great battery life!

Sent from my SPH-D700
[Epic 4G Android Development] amateurhack:
I'm having the worst battery-life day ever after flashing pre7...and it has nothing whatsoever to do with the ROM. No worries.
[Epic 4G Android Development] CapsLockKey:
Guess to answer my own question, went ahead and tried out the latest beta3 test and so far I haven't had any problems. Beta 2 I'd get mad electronic skip noises when playing music.
[Epic 4G Android Development] xtrezpasor:
Where do you download beta3-pre7?
[Epic 4G Android Development] Beezer80:
From their blog. Check the OP.
[Epic 4G Android Development] tony_spear:
Beta3- pre7....solid. No issues.

Thanks Devs. Keep 'em coming.
[Epic 4G Android Development] Zeinzu:
Beta3 Pre7 is working well here also. Good battery even at 1.2ghz. The tweaks to overclocking and removal of 600 seems to have smoothed out performance. No reboots, the soft key backlight options works, 100mhz works, and the other tweaks don't seem to have introduced any new issues for me. The mentioned fixes are working as well. No issues with gps or incorrect order in gallery.

The only issues for me that are still present are the before mentioned ones in my previous posts.

Looking good guys.
[Epic 4G Android Development] AndroAsc:
ARGHHH!!! First time cyanogenmod user. After flashing, I am getting no signal whatsoever.

Btw, I am running on Verizon network, not Sprint. My guess is that Cyanogen must have overwritten or messed up my PRL setttings (which was custom to Verizon).

And now when I want to check the PRL settings using QPST, it is not detected! Took me a while to figure out how to use ##8778#, and that still did not work.

Can anyone help? I need my phone to connect to QPST to fix the PRL error!!!
[Epic 4G Android Development] ÜBER™:
GET OFF CYANOGENMOD!!!!!!!!
[Epic 4G Android Development] wtogami:
http://epiccm.blogspot.com/2012/01/boot-el30-stock-from-sdcard.html

Boot that from sdcard and it should theoretically allow you to use the dialer code to get into DIAG and use QPST.
[Epic 4G Android Development] AndroAsc:
Seems that the problem I was having is not related to PRL at all!

The roaming settings do not work on CM9 Beta 3. I flashed to CM7 RC1 and my phone functionality works fine. In CM9 I can't change the roaming settings. It is stuck on "Home", and since I am on Verizon, I have be roaming 100% of the time. I tried changing the roaming settings in CM9, but they won't change from Home.

Has anyone found a fix for the roaming problem? I've seen the CM9 change log, and this was supposedly fixed in the earlier alpha releases, but apparently it's still not fixed.
[Epic 4G Android Development] xtrezpasor:
*deleted*
[Epic 4G Android Development] zanderman112:
Settings>About Phone>Baseband Version

~ Mr. Z
[Epic 4G Android Development] sonarchist:
@wtogami

The cuatro de mayo Kernel = rockin' it on Cinco de Mayo!...........not 1 hiccup, despite the margaritas ;) :) ;)

..........sent from today's android 4.0.4
[Epic 4G Android Development] BigOnes69:
goo manager

Are the files for this being put on GOO servers? I have Cyanogen Mod 9 on the touchpad and this works great with it which teamwin has the automated script down to a science.
[Epic 4G Android Development] AndroAsc:
I've managed to figure out why CM9 doesn't work on my phone... it doesn't roam. It gets stuck on "Home" network, and since I am running my Epic 4G on Pageplus (aka Verizon network), it will never connect to the "roaming" Verizon network. I've installed CM7 and it doesn't have this problem since I roam all the time. All is good, voice works, but data doesn't.

So I checked the PRL settings and other stuff using QPST by flashing into that stock ROM that CM has provided on the main blog for Epic 4G. As far as I can tell, overwriting the PRL and other settings related to data seems to work fine. The CM7 indicator suggests that there is data connection, but I can never get any data... not to mention that the connection is intermittent as well. Now, when I loaded up the stock ROM (without changing anything in QPST), my data connection works fine.

So obviously, Cyanogenmod is modifying some settings relating to data connectivity or has some missing functionality in stock.My guess is that the lack of support for the ##XXXXX## functions like 8778 to change to modem mode and 33284 to lock the phone into CDMA (no EVDO) mode is causing the problem. Can anyone help me with this? It's really upsetting, I've almost an entire day troubleshooting CM ROMs, and I never had this much problem with other ROMs before.
[Epic 4G Android Development] Ceelos09:
Has anyone else's front facing cam borked after flashing a CM9 build? It was working fine on Beta 1, flashed Beta 2 and it no longer works. Didn't care much at first. Just recently, I completely flashed Beta 3 pre-7 CLEAN, and it still doesn't work. All I get is 3 little letters at the top "SCN". Also, I have not used any other kernel but stock. I cleared camera app, and made sure md5 matched.

Anyone else experiencing this?

I'm gna try pulling the camera.apk from Beta 1 and see if that works.
[Epic 4G Android Development] xgerryx:
When I receive a phone call, the ignore, answer buttons that come with CM9 are almost completely OFF of the bottom of the screen, so much so that I can barely tap the slider to select answer or ignore. Any idea why this is happening? Running CM9 beta 2, stock kernel, no theme.
[Epic 4G Android Development] ÜBER™:
I've seen this before, its a bad download... try redownloading the rom and flashing it fresh again wiping data,cache, and dalvik. That should fix things.
[Epic 4G Android Development] tonybeau:
I tested my camera after reading your post. All seems fine with my front facing camera. I can't seem to find any method to make it fail. I do get the "SCN" letters, but my image immediately shows on the screen.

If you have anything else to test, I'll give it a shot... (Running B3pre7, from a clean install.)
[Epic 4G Android Development] Ceelos09:
Hmmm...weird. I might have to ODIN back to complete stock and start completely clean cuz nothings really fixing it for me. What's more odd is that I've been running stock CM since Beta 1, and it worked then. After beta 2 (or sometime around then) is when I noticed my FFC was borked :\
[Epic 4G Android Development] xgerryx:
Thank you, I will try that.
[Epic 4G Android Development] TechnoGeezer:
Also tested mine after reading your post. My FFC works fine; took my picture OK. On beta 2.
[Epic 4G Android Development] TechnoGeezer:
Question for anyone about beta 3 pre7. I flashed it last night over beta 2 (no wipes) & it performed very poorly. Jittery scrolling, some apps wouldn't work correctly, etc. Since that is in stark contrast to what others have reported, I' m wondering if a complete wipe is recommended before flashing pre7? Md5 checked out & flash appeared to go OK. I'm back on beta 2 now but would like to try pre7 again. Thoughts?
[Epic 4G Android Development] davidh59:
I had some initial jittering but switching from SAv2 governor to ondemand seems to have fixed that. I wiped cache but not data. Everything else has been smooth.
[Epic 4G Android Development] Ceelos09:
Thanks for checking guys. I'll ODIN back to stock, didn't want to, but it seems to be my only options :p
[Epic 4G Android Development] Zeinzu:
Performance is fine here. No jittery anything. Tested on both the Beta3 Pre7 and Beta3 Pre8 kernels. I don't change govenors though. I stick with On Demand and just bump up to 1.2ghz.
[Epic 4G Android Development] sonarchist:
@TechnoGeezer

You may want to flash CM9beta3-pre3 first, then go ahead + flash beta3-pre7............(wipe caches ONLY, GApps, test kernel = optional, your comfort level......no need to wipe data, yet. ;) )

..........sent from today's android 4.0.4
[Epic 4G Android Development] TechnoGeezer:
Done! Made another Nandroid of beta 2, wiped cache & Dalvic, flashed pre-3, booted into pre-3, manually rebooted twice, wiped cache & flashed pre-7. Checking it out now. Thanks.
[Epic 4G Android Development] DarkIceCream:
The only problems I've been having lately are:

1.Random reboots the start from the splash screen

2.Car mode activating by itself!!!!!! all the time!! RQ

anyone have any solutions?
[Epic 4G Android Development] wtogami:
What are you running? beta2? beta3-pre7? What kernel are you using?

What you describe is certainly not normal. It is likely either hardware trouble or the ROM is corrupted on your phone.
[Epic 4G Android Development] DurhamHusker:
I flashed Beta3-Pre7 over Beta2 along with the experimental kernel from May 4th. Before doing so, I did uncheck set-on-boot as well as delete the "throttle" folder. It's been running very well for a few days overclocked to 1200 MHz, minimum set to 100 MHz, with the ondemand governor.

This morning I noticed that it was not dropping below 400 MHz, even at zero load on the CPU. A reboot is now allowing the phone to again drop to 100 MHz.

One question: I've seen some suggest to flash Pre3 before Pre7. Does that suggestion come from the CM team or just from user/tester observations?
[Epic 4G Android Development] sonarchist:
NO.......not Officially presented by the Team..............Beta3-pre3 + pre-7 (an update.zip), these are beta test builds for users to explore + hopefully inform the Epic CM Team of their stability, specifically w/ respect to the fixes stated on the Epic CM blog where the DL links are posted......my suggestion to TechnoGeezer came in response to his trouble flashing beta-7 --he managed to flash as posted above you, seems to be working-- so it would be up to you to interpret this however it suits you w/ your specific situation..............beta testing is always at your prerogative.

..........sent from today's android 4.0.4
[Epic 4G Android Development] TechnoGeezer:
I think that suggestion came as a result of my experience, noted a page or so above, where I had significant issues after an apparently good flash of pre-7 over beta 2 without any wipes (but otherwise solid - md5 good, etc) . I repeated the flash but first wiping cache & Dalvic, then pre-3 before pre-7 as suggested by Sonarchist, if I remember correctly. Now running pre-7 apparently without issues although recorded videos may (repeat MAY) have a few stutters. I don't record many videos so that may be normal for this camera. IDK if a "pre-flash" of pre-3 is necessary before pre-7 or if it was a fluke(a one-off so to speak), or if it cured my prob. Statistic with N=1; not very useful.
[Epic 4G Android Development] ProDriver77:
I know this has been posted as an "upstream" issue, but do any of our wonderful devs here have a "timeline" (bad pun, I know) on native FB Sync? Gave AOKP a try yesterday and am currently using it as a daily driver for this reason.

I really like CM9 though, and thanks again for all your hard work; because AOKP wouldn't be possible without your team here first! :)
[Epic 4G Android Development] jdelano:
Pssst .. "ETA" is a 4 letter word ... ;)
[Epic 4G Android Development] murso74:
2 weeks
[Epic 4G Android Development] nastypup:
So far, Beta 3 is nice and smooth. Wifi is a bit better and GPS is stronger. One lockup and one random reboot. Otherwise, good.

Cyanogen Mod Beta 3, EL30. I like my Ice Cream Sandwich!
[Epic 4G Android Development] wtogami:
There are no technical reasons to flash pre3 before pre7.

Did you try the beta3-pre8 kernel? pre7 has known cpufreq problems but pre8 as far as we know is good. We need to know if pre8 kernel is stable in the long-term.
[Epic 4G Android Development] DurhamHusker:
Yes, I have been using the pre8 kernel.
[Epic 4G Android Development] Shinydude100:
Hey Warren, how about those of us that don't even bother with undervolting or overclocking? Do these cpu frequencies affect us as well?
[Epic 4G Android Development] AproSamurai:
Yeah, it's an across the board thing, there isn't any undervolting included within the kernel.