yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] nathan951:
I am also looking for a fix to keep the menu keys on longer.. Either add a setting feature, or hard code them to stay on with the display (which is my preferred setting).

Thanks Nathan
[Epic 4G Android Development] bender beerman:
sorry bird, i was misleading. i thought the option was in gosms, but it was in the stock messenger right under "split large texts" option... guess i just never use that
[Epic 4G Android Development] crcsboy:
Thanks for the ROM works perfectly for me on nightly 13. Also noticed when playing games it's smoother and phone doesn't get nearly as hot...awesome work!!!
[Epic 4G Android Development] AproSamurai:
I've been quiet for a few days reading this thread(has happened in all CM7 threads), but all I have to put out truly is that you all(majority but not everyone) always have a complaint every day of every week there is something, and it overwhelms the comments of those who are looking for a means to correct this complaint, or rather don't see it as an issue. Let it be official CM7, Let it be Wimax, let it be wifi, let it be audio routing or feedback whistle which are related to eachother depending on your perception of it, or bluetooth disconnecting at sleep. The complaint is/was commented 4 billion times in a row some ways proper, some ways *****ing about it to be honest and you wonder why no one is replying. Jnadke commented on camera wake so people could understand why it happens, never said it was a bug but it was and has been assumed as much(meaning his post was overlooked to an extent), he then cleared that up because camera wake "bug" isn't and never has truly been a bug, it's an alternative way to unlock. Suggestions as always are appreciated but unless you've some legitimate suggestion which actually benefits the overall on a logical level or in some way can be helpful please don't just post what it is that you want because you want it. It helps no one.

Sent from my Epic 4G
[Epic 4G Android Development] inameiname:
Ah ok. It does seem pretty cool, and handy. I will have to look into it. Shame there isn't a trial/free version of it to check out. Anyway, I'll look into it in a bit. I'm still having the issue of the Wifi randomly not turning on, saying I am out of range of it (even after following the method mention in this thread to 'fix' it), so I have more pressing things.

Regardless, thanks a lot. I look forward to seeing what tasks I can automate. ;)
[Epic 4G Android Development] jnadke:
Well:

1. It's difficult to change the keys file, because actually it's somewhat tied to the keyboard driver. The implementation would be different for each Cyanogen device. Anyhow, there is an APK that lets you modify it how you like:

http://xdaforums.com/showthread.php?p=9399440#post9399440

Adding such a setting to a configuration menu would be _a lot_ of work for something mostly meaningless.

2. My post was partially directed as an explanation as to why it can be advantageous for the camera to be able to wake the device. You can divide Android into two pieces: Linux (the kernel), and Android (essentially a glorified desktop environment like KDE/Gnome). The Camera button only interacts with Android, but the Power button interacts with both (loosely speaking).

When the processor sleeps, all the camera button can do is shout at it. But the power button has a bucket of water it throws on it as well as shouting. When debugging sleep problems, seeing if the processor is responding to shouts is an easy test, and you don't want buckets of water being thrown it.

3. Decad3nce: You forgot to remove WAKE_DROPPED from the FOCUS in our keylayout :p

Personally, remove WAKE_DROPPED from FOCUS and add it to CAMERA. This pretty much solves vita10gy's problem.
[Epic 4G Android Development] Decad3nce:
Completely forgot the button was 2 stage, thanks.
[Epic 4G Android Development] jnadke:
I'd fix it myself, but I'm having issues syncing CM at the moment.

repo sync keeps failing out, I'm not sure if it's my router being janky, as usual. Been about a year and half since I touched repo.
[Epic 4G Android Development] algorhythm:
So, what you're saying is... don't bother to report bugs?
[Epic 4G Android Development] cornaljoe:
I finally figured out what was graining my battery. Samsung did a good job optimizing GB because on TW roms I could leave wifi on all day and it won't effect my battery. If I leave it on in CMOD it eats the battery pretty fast. Now that I turned it off I'm getting great battery life.
[Epic 4G Android Development] Decad3nce:
Steve already filed a complaint with github about it.

For now though, you can edit the manifest.xml in .repo to point the fetch to either git:// or https://

<remote name="github"
fetch="https://github.com/"
review="review.cyanogenmod.com" />

It seems to error out on each one every once in a while so I just point it to a different one.
[Epic 4G Android Development] AproSamurai:
What I'm saying is be more insightful of the things you report, honestly it may be a hassle for some people but I read back a few pages when I look into this thread or any thread for that matter because something important or clever can be missed, otherwise all you will see is the same set of issues being cited 10 posts a page as if the person who just posted didn't catch the 40 posts before them, but then again we all are unique people, we handle things differently , a lot of this, is already being discussed between our developers, the ideals of what is important now and what may be important down the road, or what really isn't important are for them already set out, they're getting to fix that(those things THEY find important) now.

It just gets aggravating that there is a large group of people who won't look for their own answer when it could have been two posts above theirs had others bothered to acknowledge it but the process continues.
[Epic 4G Android Development] jnadke:
I don't think it was directed at bugs, but mostly people that ask the same thing over and over. Volume buttons, audio issues, bad battery life, Titanium Backup not working, "I can't use this ROM because...... <insert reason I don't care about>"

That's more of an organizational thing. I made the Wiki, but people need to add to it. I added a Q&A section where people can put these types of "lessons learned".

http://xdaforums.com/wiki/Samsung_Epic_4G_CyanogenMod

I asked UberPinguin to add it to the first post, but he hasn't quite responded.

Perhaps a separate development [DEV] thread needs to be started, where people who care can talk about bugs. This being the [ROM] thread, people can talk about issues. The difference being that issues may be PEBKAC errors. Bugs are confirmed ;)

Now, don't go off doing it. It'd be better for someone who is doing coding work to do it, so it can be kept up to date.
[Epic 4G Android Development] MeetFace:
thanks jnadke, +1 for the Wiki.

Apro, the problem with your legitimate gripe post, is that people who don't log in this evening will be none the wiser, haha, which, like you said, perpetuates the problem.

Wiki is the first step, the next step is to train people to read the Wiki first. It's an on-going battle, but it does help. Cleaned up the Viper threads pretty well doing this at one point.

Final step is making sure we the people keep the wiki updated, although I recommend that bugs are not removed unless there is official word from the OP that the bug has been squashed (even then, you might notate the bug to say "fixed as of nightly 13", etc.)
[Epic 4G Android Development] zanderman112:
This is how xda is supposed to work. A Rom thread in development, and an accompanying thread for discussion/bug reports/thanks/etc in the General section. The Epic section has never followed this though, so most people dont know this.

Sent from something with a Ｋモ尺れモㄥ.
[Epic 4G Android Development] murso74:
someone could always be made a mod that wants to move said questions to the general forum until people get the picture. or just lock the dev thread so no one can post bugs
[Epic 4G Android Development] Sherrillface:
I took sprint vmail from a back up and it works fine for me
[Epic 4G Android Development] zanderman112:
It sinks that way. Not a good method

Sent from something with a Ｋモ尺れモㄥ.
[Epic 4G Android Development] vita10gy:
To be fair, it's not "my problem". I guess if I had my druthers it would be removed (and now evidently is) just because the 2 stage button specific to our phone makes the slightest brush wake the phone. To be perfectly honest until I saw someone bring it up as a potential issue I didn't even notice, and the post you replied to is, I think, my only mention of it.

Really I was just commenting on the fact that people can, politely of course, voice their opinion, and offer suggestions, on things they'd like to see different to make this ROM even better. If the answer is "that would be really hard to do and probably won't ever be done", then so be it.

It "not being a bug" isn't really the crux of the matter, IMO, and "that's the intended functionality" isn't the be all end all response, if the real point the person is attempting to make is that they think it's a misguided feature. That's all I meant.
[Epic 4G Android Development] projectm3tal:
How come mms over wifi works on ERA's legendary rom but not on cm7? not really a complaint or anything, would be nice to have but im more so genuinely curious.
[Epic 4G Android Development] algorhythm:
I've posted my BT issue a few times in this thread, but for different builds. I think we need an official bug tracker for the epicmtd build, since we can't post issues on the official CM issue tracker. Actually issues get lost between stupid posts like the buttery smooth crap and stupid off topic posts that really are wastes of space.
[Epic 4G Android Development] zanderman112:
Cause Legendary is a TouchWiz Rom and this in an AOSP based Rom.

Sent from something with a Ｋモ尺れモㄥ.
[Epic 4G Android Development] jnadke:
I don't know, I haven't looked at this.

I will say this: Do you mean "MMS over WiFi" or "MMS while WiFi is active".

The former isn't how MMS works. What you mean is the 2nd one.

MMS is basically SMS with a HTML link for a picture/media file. The media file is uploaded to a special Sprint server. This Sprint server can only be accessed via 3G data connection. Your phone then sends a special text message with the link, and the receiving phone decodes and downloads the picture.

MMS can't be done over WiFi. There must be a bug in our code that isn't turning on the 3G radio when you try to send a MMS.

Suggestion: See if this is a general bug, or WiFi driver bug (not turning off). Do me a favor and go back to nightly-2 and see if this problem exists there. This will help give me an understanding where the bug might lie, since the new WiFi driver seems to have broken other things.

Edit: This may have worked older builds (regression). I sent a MMS on Dec 29th at home, which would've been on WiFi, that seemed to have gone through fine.
[Epic 4G Android Development] vita10gy:
I've seen a few forums where an automated 2nd post is automatically a WIKI type deal. I think that would be great for XDA to implement. (Even if we don't use it as THE wiki, we can maintain links and whatnot.) A guy can dream. :)
[Epic 4G Android Development] nathan951:
On nightly 13 I do NOT have any vibration at all, can someone confirm this is/isnot an issue.

GOT IT FIXED (Quite Hours enabled)

Thanks!
[Epic 4G Android Development] MeetFace:
This is not an issue, I'm on the same nightly. I just had my vibration go out 2mos ago, had to send it back to Sammy (was w/in 12 mo). The vibrator is in the same component as the external speaker, and eventually the external speaker went out a month after the vibrator stopped working.

I would do everything possible to test it, including the different settings, as well as flashing another ROM and testing it out.
[Epic 4G Android Development] pvtjoker42:
been running 13 all day.. and i ONLY use vibrate, and it has been working fine for me. if you did a clean flash and are using the stock mms app, you have to enable vibration for sms/mms. but otherwise haven't had any issues..
[Epic 4G Android Development] RyleyinSTL:
I did some research and may have this one licked.... http://xdaforums.com/showthread.php?t=1442666

-----

On topic - loving the bat life! Sleeping very well.
[Epic 4G Android Development] Xinlitik:
I have the same problem and think I know why. For some reason, wifi leaves prevents your phone from entering deep sleep. 3g does not have this problem. I don't think this was the case for tw.
[Epic 4G Android Development] Zeinzu:
The mention of a seperate thread/section is one place SDX (a site I've worked with a lot when I had/dev'd for the Samsung Moment) has always had XDA beat. Much smaller volume site for low/mid range Android devices, but what we did was

Had an entirey seperate section for development. The only people who could post there were developers of that device and "registered" testers that were chosen based on having enough knowledge to help the developers debug who didn't have quite the knowledge to develop themselves, and who displayed themselves in a manner that showed they would be benificial and reliable as a tester.
[Epic 4G Android Development] jnadke:
I just tested this. The new wifi driver broke this. I see the 3g connection engage but wifi doesn't disable itself. It must be ignoring the command to disable. Probably broken.

I also noticed wifi won't connect when phone is asleep. It should.
[Epic 4G Android Development] stir fry a lot:
The dev for the OG Nebula rom had it right.

http://code.google.com/p/nebularom/issues/list
[Epic 4G Android Development] jbadboy2007:
Totally agree as the first site I started with and rooted this phone with was sdx. (Cough, cough, joey krim root) yeah no one even knows that's how this phone even got root in the first place. But sdx was so easy to find what you were looking for. The problem is when someone asks a question then someone answers either positively then they are buddies and posts exchange back and forth amongst them in dev threads and the person who asked question has no more reason to search for answers and not only that but the thread is so littered with post it kind makes it worthless or someone responds negatively to ones question then posts are exchanged in pissing match also cluttering up a dev thread. Everyone here wants to talk but are to lazy to go and chat in general.

/end rant
[Epic 4G Android Development] bender beerman:
Settings> wireless networks> Menu button> advanced> wifi sleep policy: set this option to "never"

BEER!
[Epic 4G Android Development] Beezer80:
jnadke,

If you want to help you need to get in touch with the Devs working on this. Your best bet is via IRC.
[Epic 4G Android Development] bender beerman:
So why is it ok to have completely off topic posts complaining about people posting off topic? Does that really help, or maybe should we all just relax a bit about it? This is an internet forum, it's not Microsoft. People aren't going to learn the things you want them to learn mostly because there are so many different people that would need to be taught. My impression is that the devs are already aware of this and that's why they use irc for active development. I'm not condoning trolling by any means, but let's all get a bit more realistic in our expectations of the general public and turn it down a notch in here. There is no need for so many cool and good ppl to get so upset about something so insignificant.

BEER!
[Epic 4G Android Development] rangermateo:
Does it help at all if you flash back to another mtd tw rom and update your profile? Seems like there are some settings in ##DATA# that could be what tells MMS where to upload the media too. If your data profile is wrong (and no way to update from an AOSP ROM) then you could be screwed even if the 3G connection comes up. Tries to contact 0.0.0.0 and times out.
[Epic 4G Android Development] steveo314:
Finally figuring out the battery....
[Epic 4G Android Development] bender beerman:
Correct me if I'm wrong, but you can't update because you're on an mtd partition, not because you're on an aosp rom.

Edit: so no, I don't believe it would help.

re-edit: i have been corrected in a subsequent post

BEER!
[Epic 4G Android Development] TrentB:
You guys are my heroes.
[Epic 4G Android Development] murso74:
thank you, i know
[Epic 4G Android Development] styles420:
A YAFFS2 partition can store all of the same data that a EXT4 or RFS partition can, so how does your assertion make any sense? The kernel handles the file system details, making them transparent to the higher level software - all the profile updater cares about is that it instructed the system to write new data to the profile, it doesn't have the burden of telling the system how to format the partition or the data.

Think about it - do you have to explicitly tell the system what file system is in place when you mount your phone as usb storage to transfer files? No. If this abstraction were absent (in other words, if you did have to be explicit), then windows users wouldn't be able to mount their phones because they don't use FAT/FAT32 or NTFS... (okay, there are ways to access some linux partitions from windows, but they're third party and not common knowledge)

However, AOSP roms don't have carrier-specific data profiles because they weren't built by the carrier, and each carrier tends to have their own proprietary variations, so the profile updater would most likely need to be customized to the correct carrier. In other words, it has everything to do with the rom, and little or (more likely) nothing to do with the underlying file system

Sorry if I sound slightly irritated, it's not you - I've dropped from a pack a day to 5 smokes a day and counting in the past two weeks, and the toughest part is yet to come... (maybe I should put this disclaimer in my sig for a few weeks, lol)
[Epic 4G Android Development] bender beerman:
congrats, quitting smoking is no easy feat sometimes! keep it up!!! (i'm not easily offended, btw) as far as the aosp/mtd profile update: i haven't actually tried it, i was fully updated to ei22 before flashing to avoid having to unnecessarily odin. but i was basing my assertion on the fact that we had been told multiple times that the only way to update our modems was to actually odin back to a bml partition. not to mention that we on mtd are on a completely different file system (yaffs2) from the stock (rfs).

thanks for the correction!
[Epic 4G Android Development] Speedin07si:
Running Nightly-14 with no big issue's.... btw thanks for fixing the camera button waking the phone.
[Epic 4G Android Development] zanderman112:
Wasn't a "bug" but....oh, I give up.

Sent from something with a Ｋモ尺れモㄥ.
[Epic 4G Android Development] Speedin07si:
First thankyou for providing the useless posting that has been talked about all day.

And your right it wasn't a bug. From what I gathered by reading (interesting idea this reading thing) but it was designed to wake the phone up.

But still it was annoying pulling my phone out of pocket and the screen be on. I'm simply saying Thankyou dev's for fixing or rather adjusting a annoying pesky part of this rom for our phones.
[Epic 4G Android Development] Effsi:
No no but you don't understand! It wasn't a bug! Gosh man! Even tho I don't believe your post mentioned it being a bug but still...
[Epic 4G Android Development] stilesja:
Same here. 14 flashed fine and running well for waiting to see if it's safe you are good to go.
[Epic 4G Android Development] Speedin07si:
Ok maybe I'm missing some kinda humor idk... If so i apologize I have been up since 5AM.

Nightly-14 seems a bit more snappy.

Wifi-check

4G- check

3G-check

GPS-check

Bluetooth-check

Never had the video studdering problem so no comment on that.

Happy Flashing.

Sent from my 4G Cyanogen Epic.
[Epic 4G Android Development] RyleyinSTL:
If you start tapping the screen all random like while in the "about phone" menu it seems that an array of selected art will pop up. There was an accompanying message with the duck painting from Team Douche.

Is this old news?

Also...flashed 14. No issues.
[Epic 4G Android Development] Nashdogg:
In settings>about phone? I can't get it to do that. Huh? *shrug*

Sent from my cyan seppuku samurai epic
[Epic 4G Android Development] RyleyinSTL:
^^ it happened completely randomly and quite by accident so far as I could tell
[Epic 4G Android Development] bbelos:
The zombie pic appears if you repeatedly trap the firmware version. Not sure how you got that second pic.
[Epic 4G Android Development] ac16313:
By tapping on the "mod version 7.xxx" in the same menu.
[Epic 4G Android Development] saramon:
I have a check mark instead of zombies, I wonder if it is the same type of issue that shows the weird numbers at the top of the dialer...
[Epic 4G Android Development] ksmullins88:
That issue is from using the samurai kernel
[Epic 4G Android Development] mrcollpepper:
that also worked my at&t skyrocket... it must be with all cm7 roms lol way cool
[Epic 4G Android Development] Qwallace70129:
Well....I recorded a minute long HD video and didn't get a single stutter ....our devs are the ****....straight up

Oh yea....I just flashed nightly 14
[Epic 4G Android Development] styles420:
The modem does have a road block - both methods would need modifications to accommodate the changes to the partitions. I'm not sure how hard it would be to modify the CWM zip, but as far as I'm aware, no one has done it yet. But I can see where it might lead to confusion about other things being able to cross over

And this withdrawal thing sucks - I've never experienced it this bad on my previous attempts. But those were failures, so maybe this is a good sign? Thanks for the understanding and support :)
[Epic 4G Android Development] tbob18:
Does automatic exposure work for anyone while shooting video with the rear camera?

It works fine when shooting video on the front facing camera but not on the rear one. :confused:
[Epic 4G Android Development] bender beerman:
it's all good dude; with cm7 there was no contract, no promises, no wedding bands, no kids. u don't like it, just change it. no need to explain yoself :)
[Epic 4G Android Development] Decad3nce:
Scrolling is too laggy?

Does anyone ever look in settings -> CyanogenMod Settings -> performance before posting that "nothing worked"

Enable 16bit transparency, you can read what it does right underneath the title.

Otherwise, try interactive cpu governor as it ramps up the cpu when coming out of idle a bit quicker than any other governor and is noticeable on interaction with UI.
[Epic 4G Android Development] Ceelos09:
/Drama queen exits....

Deca only made a suggestion, ur harsh response was uncalled for. Although you "dislike" this ROM, please dnt be a **** to one of the Devs that gave us this ROM. There are many of us who are enjoying this ROM and we'd hate for someone like u to kill it for the rest of us.
[Epic 4G Android Development] Decad3nce:
thnx dis p0st if u cry evry tim.
[Epic 4G Android Development] Silpher:
Have you tried a different launcher? I bother with the stock launchers (whatever is supplied with the ROM, I think ADW?) about as long as it takes to restore Go Launcher, but have seen little to zero lag since RC0... Definitely could be something else, but I thought I'd throw that out there.