yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] celsius0010:
Appreciate the attempt but if you're not going to help you don't have to reply.. You didn't answer any of my questions.. I specifically said I dont like the 3D fly out on the lock screen which is an animation that is not ICS.. Perhaps I need to flash some new system animations but my lockscreen on my ICS theme didn't do that last week when I was on Marcusant...
[Epic 4G Android Development] the_dark_knighton:
I read this while listening to music on a bose bluetooth speaker and it sounds great!

Sent from my Cyanogenmodded Epic4g! Wanna fight about it?
[Epic 4G Android Development] adamdelozier:
I have searched and found nothing. I just flashed the latest nightly and now my cm settings is force closing. All other settings are working ok. I have wiped caches and reflashed. I also tried fix permissions. Only thing left I can think of is wiping data. Just some background...I was on the nightlys before then went to EL30 ROM sleeperrom. Then I flashed the sd bootable so I can upgrade the modem (which worked well). Now flashed back to the latest nightly. Any other options, than wiping data?
[Epic 4G Android Development] styles420:
Not exactly - he meant radios as in the GPS radio, wifi radio, etc. - actual hardware that sends and receives radio wave transmissions :)

What do you mean? You said you didn't have the ICS style lockscreen, so I pointed that that the Holo style is the ICS style lockscreen. I also clarified that you don't need to mount anything because the script contained in the flashable zip does that for you when necessary. I didn't respond to one out of your three questions, about the volume bar color - I haven't seen that change with any theme I've applied (now I've answered that one, too). :)
[Epic 4G Android Development] Zeinzu:
He means the unlock animation. The ring expands outward, unlike a "true" ICS lockscreen. That's just cm7 bud. It's not an ICS lockscreen it's just giving you the option for that style ring. I use widgetlocker to have the more legit ICS style lockscreen.
[Epic 4G Android Development] nastypup:
I assume they're on or the Wifi and GPS wouldn't work at all.
[Epic 4G Android Development] Cash Machine:
In CM settings/Display/Automatic backlight, check "Use custom," then "Edit other levels..." Set everything in the "Buttons" column to 255. Save & apply.
[Epic 4G Android Development] mcluvin1065:
Im not sure if anyone has mentioned this yet.....my apologiez if this has been asked....but i was wondering if anyone has encountered the youtube bug where if you rotate the screen while the video is playing ypu get a black screen???? If there are have there been any fixes???.....currently running nightly 31
[Epic 4G Android Development] justppc:
Toggle HQ is the workaround, and yes it has been answered in this thread previously
[Epic 4G Android Development] Zeinzu:
Turn animations off so you don't have to toggle anything when rotating. You can't toggle an HQ mode in other video playing situations and you will still get the black screen.
[Epic 4G Android Development] sensor32:
OK, first time I had encountered a problem.

I downloaded n31 via 4g and powered down then rebooted into CWM by the 3 finger method, and installed the nightly as normal.

When it rebooted the phone stuck at the samsung logo and will not reboot in either normal mode or CWM.

Second problem- I do not have a PC,,,I have a Mac.

What are my options to get back to CM7?
[Epic 4G Android Development] styles420:
Heimdall is probably the only way...

Do you have adb set up on your Mac? (I can't confirm, but I think the software exists) If so, does 'adb devices' show your phone while it is bootlooping? If so, it might be possible to use adb to fix this - let me know if you can at least detect the device, and we can go from there
[Epic 4G Android Development] sensor32:
Currently,

Heimdall doesn't detect the device, nor is it showing up as an external drive while stuck at the samsung display screen.

I dont have adb on my mac
[Epic 4G Android Development] bender beerman:
and you can't boot cwm even after a battery pull?
[Epic 4G Android Development] sensor32:
That is Correct
[Epic 4G Android Development] bender beerman:
well, your only other option is heimdall... or borrow your neighbor's pc for about 45 minutes ;)
[Epic 4G Android Development] DrKaotica:
the MTD CWM we use right now does look like it bootloops as you hold down the 3 finger salute.. if you hold down your 3 buttons, let it go through 2-3 samsung logos, then let it go, does it let you get into CWM then?
[Epic 4G Android Development] sensor32:
No, it just sticks at the Samsung screen once I let go. It does go through the loops while holding down the buttons.
[Epic 4G Android Development] DrKaotica:
Oh ok, sorry for a noob assumption there but I wanted to be sure. I also have a mac and couldn't get heimdall to work with it, but I would definately explore that option as I gave up relatively quickly.. if you can bootcamp into windows, you should be able to odin. I ended up restoring a laptop from 05 just so I have odin capabilities in case, and yes I've used it

Short of that I would say ask someone with a pc laptop to stop over with it so u can use it for 5 minutes, have everything ready on a flash drive that u will need (odin, the tarball, and samsung drivers install file). Give them a dark beer and have your gf rub their feet while u odin ec05, etc etc. I've found this to be the easiest way.
[Epic 4G Android Development] thabest85:
Cyanogen mod 9 is out for the epic 4g yayyyy
[Epic 4G Android Development] styles420:
I would suggest setting up adb (you can find it in one of the old one-click roots that was multiplatform, I think). On the off chance that you can access the phone through adb while it is stuck on the Samsung screen, you can try two things: first, adb logcat might reveal what isn't loading correctly, and second, you *might* be able to use adb to push the correct files...

By the way, I ran into the same problem when I got a bad download on a nightly - you can use terminal emulator to run 'md5sum [path/filename]' to make sure the file isn't corrupted (compare the output to the md5sum listed on the download page)

If the adb idea doesn't work for any reason, then Odin would be the only recourse... as for heimdall, has it ever detected your phone before? (Silly question, maybe - but just to be sure, if you've never gotten a connection then you should look for the drivers, I think)
[Epic 4G Android Development] SamsungSucks:
Poor call quality issue.

I'm currently on the latest nightly and have been using CM7 on and off since RC0. Whenever I use CM7 people I call say it sounds like I'm in a wind tunnel or have a lot of echo. If I change to another ROM such as stockish the problem goes away.

Is there anything I can provide to help trouble shoot this?

Great work btw.
[Epic 4G Android Development] sensor32:
This is the first time I have encountered anything of this kind. I just downloaded Heimdall, so it never has had the opportunity to detect my phone before. In times past I used my wifes old laptop to Odin, but the power source on it is broken, so no PC access right now.
[Epic 4G Android Development] KennyG123:
Post 2 in this thread is about using Heimdall:

http://xdaforums.com/showthread.php?t=1052813
[Epic 4G Android Development] sensor32:
I was able with the help of my wife holding the power cord in the most wretched of positions for 10 minutes to get it to Odin, using EL30. Last time I did that was back on something like eb13.

Looks like I lost root in the process.

Thanks for all the help.
[Epic 4G Android Development] styles420:
Glad you got it to boot again, at least :)

The only way to get root on GB that I'm aware of is to use Odin to, at the very least, install CWM (if that is all you Odin, you must not let the phone boot up afterwards - you need to quickly remove the battery once it resets, then put it back in and three finger (wow, that sounds wrong) in order to install a custom kernel so it won't overwrite CWM with the stock recovery.

You might try Heimdall again, now that the phone boots - ToadLife has a thread of heimdall packages, I'm sure one of them will have what you need to get back to root.

Or, maybe another user is aware of another method to obtain root? Anyone?
[Epic 4G Android Development] adj998:
Awesome rom works great and everything but i only have one problem. Since im on cricket i only get 1x and it keeps turning on and off over and over again. Is there any way i can fix this, or is there a certain modem i can use to fic this? thanks
[Epic 4G Android Development] Beezer80:
I think if you copy SU to your SD card then flash CWM with reboot checked and leave the cable plugged into the PC it will boot straight into CWM. Then you can flash super user for root. It will reboot and overwrite your recovery with the factory one but you'll retain root. At which point you grab a file explorer and delete the script that reflashes the stock recovery. Then again flash CWM which will stick this time. You might have to use an old version of CWM I can't remember.

EDIT: If you flash the ACS recovery with Odin and leave the cable plugged into the phone and PC while you reboot the phone it'll start in ACS recovery.
[Epic 4G Android Development] veris:
I'm also having this problem, not only on this rom, but MIUI and CM9.

I know a few other people are too.

Hope it gets figured out.
[Epic 4G Android Development] hayzooos:
Just to let everyone know, I flashed n32 earlier today and for the first time, I had someone say it sounded like I was in a tunnel when I was talking. It's never happened before, so when I got back home a few minutes ago, I reflashed n31 and talked to the same guy, said I sounded fine.

Not sure what was all changed, but something did, at least I'm assuming so. Just be wary of it when flashing some of the next nightlies as well.
[Epic 4G Android Development] Devtodi:
So, is this thread dead? I am hoping that development will continue on CM7. I think that it is near perfect and there are many that will stay with it at least until CM9 is a bit more polished. Thanks to everyone for the amazing work. My contract is up in August but I have no desire to replace our two Epics. They are once again awesome.

From my CM7 Epic!
[Epic 4G Android Development] MeetFace:
Don't think it's dead, perhaps if it hadn't received a response in a couple days =] The Nightlies sure aren't.

Still stuff coming down the pipeline:

http://cm-nightlies.appspot.com/?device=epicmtd
[Epic 4G Android Development] hayzooos:
I certainly hope this isn't dead. I think there are still a few things that could be improved on CM7 before jumping ship to CM9. I would agree that I would like to stay on something a bit more stable and functional until CM9 gets a bit better, which I know it will.

What I don't know is how much comes from our devs and how much comes from upstream in terms of changes. It's possible our devs haven't made many changes lately, and the few changes in the nightlies have come from upstream. I don't quite understand how all that works, but just guessing.
[Epic 4G Android Development] RyleyinSTL:
I should hope it's not dead. CM7 is rather polished and the batt life I'm getting is impressive to say the least (admittedly the attached example is light usage). It will be awhile until CM9 is at this level and given CM9's RAM issues...might it be possible that some of us will want/need to stick with CM7?
[Epic 4G Android Development] StoneRyno:
I think the remaining few bugs are common ground bugs between CM7 and CM9 so I'm assuming when it is solved for one it will be for both. Which means while it seems like nothing is happening I'm sure they are working on things they have ideas of how to solve. My opinion as CM7 stands it is more or less a finished product. The only bug I can think of offhand is kernel or driver related I believe.
[Epic 4G Android Development] zman519:
How could it be dead before its even to RC1 ?

Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
[Epic 4G Android Development] zanderman112:
Just cause a project starts doesn't mean it will be finished necessarily. Just speaking in general.

Besides, other people *could* take it over if they knew what they were doing. Not saying the Devs are stopping, its just a scenario type thing.

Sent from something with a Ｋモ尺れモㄥ.
[Epic 4G Android Development] worldwidepmp:
Well, I know everybody's excited for CM9 but even if CM7 never gets updated again I'm sticking with it until I see an RC for CM9.
[Epic 4G Android Development] zanderman112:
CM9 is already RC ready. But, CM9 as a whole is in alpha stage. So, no matter how stable, EVERY CM9 build for every phone is alpha right now. Don't look too much into the name. Its amazing.

Sent from something with a Ｋモ尺れモㄥ.
[Epic 4G Android Development] worldwidepmp:
Maybe the bug list has me a little leery, but I'll give it a shot tonight.
[Epic 4G Android Development] ac16313:
Maybe someone can help convince you? What bugs exactly have you on the fence? Actually take this to general and ill answer some question if you'd like. I'm running it right now
[Epic 4G Android Development] Epicnole:
I am currently running CM7 nightly 33 and today I noticed that when a call that lasted more than 3 min ended I was back on the lock screen. I had to unlock my phone to go back to call log or anything else. This was never an issue in other nighties. I also he a short "ring" when a call comes in before my set ring starts and my phone vibrates. The same "ring" happens when I am on a call and another call comes in. If I don't answer it never goes away and the party on the other end can hear the ringing.

I want to try CM9 but I am concerned about:

Manual dialing causes Contacts to get stuck.

Default ring tone volume is WAY TOO QUIET.

Battery drain issues I keep reading about.

Voice to text issues I read about. I use swype voice to text a lot.

I know CM7 and 9 have the same "Call volume always starts at 100% causing distortion" bug and I am hoping there is a fix soon. I have also used CleanGB-MTD and I really liked it. I switched back to CM7 because the batter life was so much better.

Any suggestions on my CM7 problems would be helpful and I appreciate feed back on CM9.

Thanks

[/LIST]
[Epic 4G Android Development] troyolson92:
My call has always started at 10% which is more annoying as you can not hear anything...
[Epic 4G Android Development] Beezer80:
I got boot loops on Nightly 34.
[Epic 4G Android Development] n0g0:
On nightly 30, in dmesg seeing a lot of the following:

<6>[13372.373553] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>[13372.373578] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>[13372.373599] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>[13372.373621] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling

Also:

<4>[13372.732925] s5pv210_setup_sdhci_cfg_card MMC_SD card inderted
<4>[13372.732998] s5pv210_setup_sdhci_cfg_card MMC_SD card inderted

Is this related to high MMC_delayed_work?

Anyone else experiencing this?

Obviously "card inderted" is a spelling error... is there some issue with the SD drivers causing the high MMC situation?

Thanks again to the devs for all the hard work...
[Epic 4G Android Development] omair2005:
wipe and install n34 and see if you get the same issues..
[Epic 4G Android Development] rsage:
Installed n34, no boot loops here. Bad flash? Maybe re-download and try flashing from 3-finger-salute CWM instead of ROM Manager (assuming you flashed from ROM Manager the first time)...
[Epic 4G Android Development] ac16313:
1)I have no idea what that means I don't see it when dialing manually maybe I'm missing it?

2)you can just switch to another ringtone

3)battery drain, hm that's a difficult one, for me batery life is meh not bad not good.

4)I'm not sure how to test that for you

And for the distortion I guess I never notice it I always use my volume at max in-call
[Epic 4G Android Development] anfrany:
Any chance you could post a screenie of the new lock screen?
[Epic 4G Android Development] Beezer80:
Looks like it was a bad download.
[Epic 4G Android Development] rsage:
Yep 10 char
[Epic 4G Android Development] xopher.hunter:
Day old bump.

I have an issue with this rom. I personally love it to death and would be running it now if it weren't for my refurb arriving soon but after I will surely be flashing onto it.

I have 2 other epics on my plan (my gf and my cousin) and they treat their phones as phones first and everything else is extra. My issue is I have noticed poor call quality throughout and randomly when placing a call all you will hear is yourself. This is a big deal breaker for them and I know they will love the stability of CM7. I use the nightlys however I can reproduce it on wimax rc0 as well.

Will this be addressed in future nightly's or in the official CM release?
[Epic 4G Android Development] RyleyinSTL:
^^my understanding is that this is due to the use of generic audio drivers. Latest official release of firmware from Samsung contains an update which the CM7 folks are investigating to see if they can use it to fix the issue.

I'm sure I read that, or something like it, in this thread some place.
[Epic 4G Android Development] ac16313:
It still gives feedback issues so they're, not going to use it I think.
[Epic 4G Android Development] xopher.hunter:
10charrrrr
[Epic 4G Android Development] nastypup:
It's a common problem and has carried over to CM9. Darn shame. People are getting angry with me when they hear themselves echo. I've had to call several back on a land line.

---------- Post added at 02:52 AM ---------- Previous post was at 02:47 AM ----------

Unfortunately, the problem has carried over to CM9 and appears to be even be worse. Lots of people are getting angry with me so I have to call them back from a landline.
[Epic 4G Android Development] Devtodi:
Bump!

Anyone else still on CM7? Is development finished?

From my CM7 Epic!
[Epic 4G Android Development] XxLostSoulxX:
This is why you use custom kernels. im on N28 with samurai no issues with feedback, plus OC ability as well as GPU OC, and some other features as well.
[Epic 4G Android Development] Zeinzu:
The feedback isn't caused by the kernel.
[Epic 4G Android Development] adamdelozier:
Looks like the nightlies link is currently down, but I assure you, development marches on. While CM9 is running great, it is still an alpha build, and CM7 has not released a final version yet. Don't worry, PLENTY of people are still using CM7 as their daily driver.
[Epic 4G Android Development] nastypup:
So what is causing the feedback and how do I get rid of it?
[Epic 4G Android Development] troyolson92:
I'm using nightly 35 and it rocks.

Turn your volume down to reduce feedback. Use voodoo, search the market and google.....
[Epic 4G Android Development] XxLostSoulxX:
Yes it was EB fixed it way back in the bushido kernels because if you used stock kernel you had feedback, EB used differen audio drivers hence no more feedback. Trust me its kernel related if I'm 100% wrong then sorry but you can ask EB yourself
[Epic 4G Android Development] StoneRyno:
I haven't had anyone tell me they are echoing back while I'm using CM7 and now CM9. I have used all modes speakerphone, BT headset, and normal phone to ear. All with call volume at max.
[Epic 4G Android Development] dzl:
Nightly 32 with shadow kernel. No issues with calls other than the volume issue. Haven't messed with Bluetooth much but the sixaxis app works great. Overall a very pleasant experience...rom is very smooth and snappy, snappier than SRF 1.2, and that **** was fast.

I loved SRF but I don't know if I will go back to another TW rom after CM7.... :)
[Epic 4G Android Development] RyleyinSTL:
Still using CM7 here. Check Git for development progress...it has slowed, sure, but it isn't dead. CM9 is amazing but not anywhere near daily driver for me.
[Epic 4G Android Development] nastypup:
What kernel are you using?
[Epic 4G Android Development] ac16313:
You corrected yourself? Its the audio drivers not the kernel... they switched to using generic audio drivers iirc that's what stopped the feedback, and that's why we have some audio issues.
[Epic 4G Android Development] XxLostSoulxX:
Yes but its in the kernel itslef not the rom audio drivers are used in the kernel.
[Epic 4G Android Development] Zeinzu:
You go on a lot about things you don't know just cause you think you read something somewhere. Your talking about tweaks to his kernel to get rid of squealing when using voodoo sound. He didn't "change the sound drivers" or "fix the feedback" inherit in cm7 and cm9. If he did it would have been incorporated in both builds by now.
[Epic 4G Android Development] n756gkj:
fail to restore from backup after switch to CM7; other ROMs ok

hi,

i've been running a rooted Samsung Epic4G with Marcusant ROM v3/mtd + SAMURAI.SEPPUKU.MTD.01.19.13.12 kernel.

i've formatted my /sdcard as two partitions: FAT32 (~28GB) & ext4 (~2GB) for Link2SD use.

my backup/restore regimen across TW MTD ROMs has been based on TitatniumBackupPro. it's all worked great -- backup & restore have been reliable reliable.

wanting to make the move to CM7 for Epic4g, I DL'd the current RC02, wiped & factory/reset my device, and installed. no issues with install.

i re-installed the Google apps .apk, market-installed Link2SD & Titanium Backup, setup & verified my sd-ext partition mounts, fixed permissions, and rebooted.

now for restore.

opening TB, if i try to restore any or all apps, user or system, the "Restoring" dialog pops up as always -- but then just sit there. No 'progress' is indicated, and the only option is to kill TB.

installing apps from Market still works, as expected. apps are correclty linked to Link2SD-managed /sdcard partitions.

if I switch back to a non-CyanogenMod Touchwiz-based mtd ROM, all's well again -- I can restore from existing TB backups.

is this a known issue ? are there suggestions or workarounds to get my restore to work on CM7 ?

thanks.

p.s. just chatted with a friend trying the same restore from TB on CM7 on an Epic4G. he's seeing the same problem -- no restore progress.
[Epic 4G Android Development] wscott9903:
SUSH...

I'm still stuck on nightly 31 (technically nightly 30 b/c 31 kept me in a boot loop). Been using CM9 for the past few days, then i remembered, wait CM7 is official, and there are NIGHTLIES!!!

aaaaaaand, the website is down. #FML
[Epic 4G Android Development] Ragnar:
Yes that is an issue with the RC02 that issue is corrected when you flash the nightlies, just download the latest one and flash right over, reflash gapps and download a fresh version of titbu and everything should work perfect.

EDIT: if your flashing cm7 why not jump straight to çm9 and just start with that?
[Epic 4G Android Development] iil:
I've had something similar and I followed the following options under the 'Problems' button in the program. Under preferences, change 'app processing' to 'AUTO, Indirect' and then try again. i'm not sure if we have the same issue but this worked for me. So...YMMV, and might want to do some research to make sure this will work or not break anything b4 trying.
[Epic 4G Android Development] n756gkj:
Noted, thanks. I'll do a bit of reading on the nightlies, and perhaps give the latest a try.

I'm looking for a daily-driver for this phone. Iiuc, CM7 is in release-candidate stauts, whereas as CM9 is in alpha. Without have tried either yet successfully, the alpha sounds a bit too risky for me, atm.

---------- Post added at 05:25 PM ---------- Previous post was at 05:23 PM ----------

Yep, found that advice too. I'd already done that, even going so far as to switch to Interactive/Classic app processing.

No dice.

Going to give the nightlies a try, I think.
[Epic 4G Android Development] Ragnar:
The cm9 while in its infancy is labeled alpha, and has some minor bugs but is just as good as the rc02 cm7. I have been using cm7 since back in October and can tell you cm9 is just labeled alpha because of the whole cm community and other devises but our epic 4g version is a good daily driver already.
[Epic 4G Android Development] n756gkj:
Sound like it's at least worth a look, then. Now, if the CM/CloudFlare website would start behaving ... :-/

thx.