yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] noobnl:
[ 1.104804] Samsung OneNAND Driver (AUDI).

[ 1.108303] OneNAND: Clock gating is enabled.

[ 1.112638] OneNAND Manufacturer: Samsung (0xec)

[ 1.117146] Muxed OneNAND 1024MB 1.8V 16-bit (0x60)

[ 1.122070] OneNAND version = 0x0031

[ 1.125537] Chip support all block unlock

[ 1.129522] Chip has single dataram

[ 1.133078] OneNAND Sync. Burst Read support

[ 1.137236] OneNAND Sync. Burst Write support

[ 1.146889] Scanning device for bad blocks

[ 1.149697] onenand_bbt_read_oob: from = 0x00000000, len = 2

[ 1.155322] onenand_dma_wait: DMA error! [S: 0x10020, D: 0x34c16000, L: 0x2]

[ 1.162352] Bad eraseblock 0 at 0x00000000

full log: http://pastebin.com/raw.php?i=JBnvx6b1

MTD is almost here, thanks to nubecoder for helping out!

High speed bus(DMA) errors preventing the OneNAND controller to read the NAND.

Fixes MTD to kernel: https://github.com/EpicCM/android_k...mmit/f152283b0425e8270aa526bb5ec71509a9eb42ab
[Epic 4G Android Development] dangambino:
Cool, very cool
[Epic 4G Android Development] || Acer ||:
Of course it will be. :), that's really why their even switching to the Yaffs2 filesystem in the first place. Other Galaxy S variants such as the Captivate and Vibrant run Yaffs2, and by having the same filesystem, it only makes it easier for us to become official.
[Epic 4G Android Development] steveo314:
What do you mean based on the same hardware?? It is the same hardware. Its what the captivate should have been + tw.
[Epic 4G Android Development] ugothakd:
Can we please NOT discuss 4g solutions...not only will the cm7 team ingore you, they've probably already thought it themselves.

sent from my always aosp epic
[Epic 4G Android Development] steveo314:
4G for cm7 for the epic and ns4g is probably months away...
[Epic 4G Android Development] Animas1020:
Sorry for trying to offer a temporary solution. Use it or don't use it, I don't care. Plus, any station you call HAS the capability to transfer to the appropriate department/agency (ambulance and fire department included) in a matter of seconds. I've done it before. I am in no shape or way dissing this build or have the slightest issue with the 911 bug. Just was sharing an alternate (temporary) solution to those who do care till it gets fixed, which I have faith that it will.
[Epic 4G Android Development] :
More wifi fixes

Not sure if this was already discussed, but wifi would never enable when I flashed directly from the 1124 build. I had to first flash the 1022 build, enable wifi, then flash the 1124 build (plus that wpa_supplicant fix posted somewhere around page 318).
[Epic 4G Android Development] getut:
All the way back on page 21 of this thread I reported the following bug:

And Decadence responded:

This is still happening the same way in this newest build... although I can see why you devs made the choice for it to be on the "safe" setting directly after a flash, I don't understand why you are overriding it on every boot once the user has chosen the setting that allows it roam.

Can a dev post why that was done or does this setting not do what I think it does? Just an explanation for the mindset behind forcing this off at every boot would help me understand and not be so darn *aggravated* by it if its done a for good reason.

I live in rural NC and staying on Sprint network only make the phone nearly unusable. I also regularly forget to charge the phone so it dies and resets the setting almost nightly.
[Epic 4G Android Development] zanderman112:
Are you porting it yourself? I and others that you're arguing with talk to the devs every day. We know what's going on.
[Epic 4G Android Development] steveo314:
then why don't you speak up when us idiots are in here making dumb guesses on when the cyanogen team is going to have a fully built cm7 rom for us epic users??

and didnt they just get the source code to develop it??? and they still havent figured out wimax for the ns4g which theyve have a build for for a while??
[Epic 4G Android Development] sureshot007:
I actually have to agree with you on this one. I will reboot my phone for various reasons, and I always forget to change that setting. It takes trying to get on the internet for something to realize that I can't get a connection to anything.

How about a way for us to change the default ourselves?

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

The answer is probably never. It will be pretty close to done, but lacking 4g. By the time they get around to actually doing anything with 4g, new phones will be out and no one will care about the Epic anymore...
[Epic 4G Android Development] steveo314:
exactly. deca's rom is going to probably be what cm is going to be or am i wrong on that too??
[Epic 4G Android Development] zanderman112:
The wimax drivers are not in the source code. They have to be reverse engineered, or written from scratch. And it is not worth it. Wimax is dying. By the time they finished, most people would have a new phone. If you want 4G go to a EI22 based rom. None of this is new information, its been stated in this thread multiple times.
[Epic 4G Android Development] AproSamurai:
To back what Zanderman is saying. WiMax drivers are proprietary, closed source if you will. Regardless of how another phone works with it's OWN WiMax drivers it is in turn another phone. Similarities yes, completely the same no. It isn't priority for the same reason trying to run WP7 on an Android device isn't as a vague comparison. The documentation of the work for the EVO is there yes, it'll give developers an idea yes, will the implementation be the same, probably not. Which is why when all else is working and fixed WiMax may be worth looking into, even though it's a dying standard of 4G data transferrence.

Cyanogenmod has no eta's for a reason honestly, you're not supposed to get a guaranteed release because issues arise, priorities arise, no matter what precedent you throw forward it is not meant to be a fast process development, it can be yes. But if it isn't no entitlement, no posting to clarify, none of that is needed. This discussion on 4G should have died out by now, honestly there is always something to complain about. First no CM7, now we've one in the works and the new complaint is 4G. Has to stop.

Sent from my Epic 4G
[Epic 4G Android Development] jocala:
build environment

I'd like to learn how to build this release. Is the build environment for

Galaxy S where I need to start out?
[Epic 4G Android Development] akenis:
I ued ROM Manager to flash cwr ver 5. Is that different than flashing/odin'ing the recovery? I remember this weird situation from a long time ago... now I have two different recoveries and some weird boot loops.

I thought recovery was a separate partition... how can there be 2?
[Epic 4G Android Development] vista178:
There are two. Odin back to stock (reverting both recoveries) then apply the latest CWM (5.0.2.7, found here) or root your stock rom and install from the market.

The kernel of your rom has to support this new recovery to fully function. (I'm not too keen on those details maybe someone else can fill-in the gap.)

There's mention of having to apply an alternate kernel to prevent the stock kernel from overwriting the alternate recovery. I used the one found here with the stock EI22 rom.
[Epic 4G Android Development] xboxfanj:
Honestly, idk, but ask in #epic at webchat.irondust.net
[Epic 4G Android Development] FrankyFiggz27:
? you do not have to do all that. just flash the 5.0.2.7 "zip flash for cwm" in that link and reboot. doesn't matter what kernel you're on.
[Epic 4G Android Development] shaunfrazier:
so i tryed again today still unable to use on a flashed phone
[Epic 4G Android Development] nubecoder:
Yes, the stock EI22 kernel will overwrite bml8 with the stock recovery, but that discussion should not be had in this thread...

OK, I need someone who wants 911 dialing working to do something for me.

Capture a logcat while attempting to dial 911.

Check the logcat for this "Emergency dial: ".

Is it in the log?

If so, then 911 is being detected as an Emergency number (which is good) and we can go from there.

(I have an Idea that may or may not work.)

If not, then we need to fix up the "isEmergencyNumber" method to detect the number correctly.

=]
[Epic 4G Android Development] jocala:
I did adb logcat -f /mnt/sdcard/logcat.txt

Call a known cell number.

Call 911. Dial screen comes up.

After 30 sec, end call.

ctrl-c the adb logcat

pull logcat.txt
[Epic 4G Android Development] noobnl:
http://pastebin.com/raw.php?i=DHiRkKXB

mtd is online!
[Epic 4G Android Development] MДЯCЦSДИT:
:) you are such a tease...
[Epic 4G Android Development] ThrIsNoSpork:
Hell yeah!

You guys are awesome :)
[Epic 4G Android Development] christophocles:
I guess nobody else uses OpenVPN?
[Epic 4G Android Development] tonyp23:
There is still a bug with bluetooth where it disconnects when the screen turns off while running on battery. Has existed since the beginning of CM7 builds. Doesn't happen with TW based ROMs.
[Epic 4G Android Development] JohnCorleone:
Wow! Congrats to the devs working on this project! Keep up the great work.
[Epic 4G Android Development] nubecoder:
I'm not seeing the log entry, but after a brief discussion with Decad3nce, it seems there is more to it than what I had thought.

=[
[Epic 4G Android Development] jocala:
Sorry guy :(

It'll happen when it happens!
[Epic 4G Android Development] steveo314:
I was going through the build.prop for cm7 build for the ns4g....there was an entry for 3 different instances of how 911 is entered. Could this entry be tried or has it been tried or is there a epic version been tried?????????
[Epic 4G Android Development] AmericanJedi001:
I just want to state what should be obvious (but isn't to a few :( )...

You guys are coding Jedis!

I love coming in this thread, wading through all the extraneous BS (not my favorite part), and reading little nuggets of progress info! I continue to be amazed at what you guys are accomplishing.

CM7 ported to the Epic would be badass enough if you guys had full documentation on hardware and source code for stock software, but you guys really take the cake by having to reverse engineer stuff too! Bravo, and thanks for what you're doing--I hang on your every post!

I think that needed to be said, it's been a while since anyone publicly, shamelessly laid it on thick. :p;):D
[Epic 4G Android Development] getut:
I've tried many times. I use pfsense and have created openvpn vpn's but have never gotten connected from an android phone... but I've always tried it with the built in client in one phone or another, but all running cyanogenmod and all using the built in openvpn client.

I would be interested in the steps you take, including spitting out your certs in a format that moves over to android well.
[Epic 4G Android Development] jbadboy2007:
I believe the easiest way to vpn would be if you have a cisco router (like me) you set up an ssl vpn then you use the cisco anyconnect app from the market. No certs just your creditentials then your good to go.
[Epic 4G Android Development] getut:
We're a big company, but we try to avoid Cisco and other companies that sell equipment but then expect you to pay for it as if it is a service... with ongoing fees that AREN'T purely maintenance contracts. I don't mind paying for maintenance contracts but refuse to pay for THINGS as if they are a service. As a result I use lots of open source solutions.
[Epic 4G Android Development] counterfeit187:
so does this mean that the few "Bad eraseblock" and "controller error" entries in pastebin aren't very important and you are nearing a bootable MTD CM7?

You guys are amazical.
[Epic 4G Android Development] AproSamurai:
Ideally yes as an end user, errors and Android are best friends.:) lol.

But Captain MTD(noob) is excited lol.

Sent from my Epic 4G
[Epic 4G Android Development] christophocles:
If you use the OpenVPN client from the Android Market, then you don't need to do anything special with your certs. Just generate them using a windows or linux box (per this guide) and plop them in /sdcard/openvpn along with the .ovpn file containing your server connection info. I run my server on a TomatoVPN router, which is super-easy to configure through the Tomato web interface. But you could also use a plain old linux box and configure it by hand.

The problem with the OpenVPN client from the market is that it can be a pain to install sometimes. You need to download the "openvpn installer" app and run it with root access, and it copies over the openvpn binary to your /system partition somewhere. It also asks you where busybox is installed on your phone, because it needs to use the busybox ifconfig/route commands to set up the TAP network device and tunnel everything through it. If you don't have busybox set up properly or you tell it the wrong location, then your openvpn connections will fail to assign you an IP address. Busybox on this CM7 rom works fine and I believe it's in /system/bin. After you get openvpn set up using the installer, then you use the "openvpn settings" app to actually connect. It uses all of the certs and ovpn files in /sdcard/openvpn. It can be a bit finicky to set up but it definitely works.

The CyanogenMod built-in OpenVPN client requires you to convert the certs to .p12 format (this guide explains how to do so), and then you load them into the phone's secure certificate storage. This keeps your private key encrypted and password-protected, so it's certainly more secure than just keeping the file on the sdcard unencrypted. I would much rather use the more secure method, if I could get it to work. I guess I will have to connect to adb to debug the connection to figure out why it keeps failing to connect....
[Epic 4G Android Development] bickman2k:
Sound issues

I'm on the 1124 build and have been having issues with calls to other cell phones. My dad asked me if I had a new app that caused my phone to sound like it had a ton of reverb.

Also, just now, I missed a call while I was in the bathroom and came back to my phone faintly ringing. Not my ringtone, like a regular ringing sound. Not in a call or anything. Didn't stop until I rebooted the phone.
[Epic 4G Android Development] justlovejoy:
Idk why that happens but it happened to me as well but, alpha build, is what this is. Not even beta, so regardless of the few updated .zips peeps been flashing, we are still alpha so these flaws should be expected and any specific fixes flaws should not be expected to be rapid upon request, til after beta. Once again, this is an alpha build. Be happy that its even being worked on by a small group of devs with day jobs and real life situations that have nothing to do any fan of the epic 4g with or without 4g or/and a keyboard. Be patient kids, nap time is almost over and recess will be next after lunch.

Edit: this ain't totally geared to the quoted but to all who just got to this page that might not have read the first 300+ pages.

Read More/ Talk Less!

Nice work MTDfreak=]
[Epic 4G Android Development] JudasD:
I gotta say a few words here about how kick-ass this rom is. I am one of the flash-happy types that cannot stay with a single rom for very long. I flashed cm7 a few builds back, ran it for a while and then moved to EI22 when it was released. Felling how slow the rom was i had to come back to cm7. Then after a while i got tired of the few issues on cm7 and went to one of the modded flavors of EI22. Again, i got tired of how sluggish the rom was and just had to com back to cm7. The moral here is that even for a rom in this unfinished condition it still steamrolls over everything else currently available. I am not trying to bash the other roms, they are great when compared to the stock EI22 base. But compared to cm7, there is just no chance for anything else. I bow to everyone working on this. much, much love.

JD
[Epic 4G Android Development] bickman2k:
I wasn't complaining. I haven't had these audio issues for a long time with CM7 on the Epic. Just mentioning that they are still here, as rare as they might be. Trying to submit a little information on my experience.

Keep up the good work everyone!
[Epic 4G Android Development] Looneyrat:
Why does this rom have the best sound? I plug it in my car stereo and the bass is supper deep and clean. Is it audio manager? Cuz I tried installing that and it doesn't look like the one on this rom. And out doesn't sound like it either. Wtf. Tell me the secret!
[Epic 4G Android Development] worldwidepmp:
Bless your heart, you think you're driving the car? Huh lil guy?
[Epic 4G Android Development] xopher.hunter:
gonna put this right here ;)

Edit: sorry its sideways but its straight from cyanogen

www.cyanogenmod.com/blog/cm9-progress-update?utm_source=dlvr.it&utm_medium=twitter
[Epic 4G Android Development] zanderman112:
sweet.

Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
[Epic 4G Android Development] AmericanJedi001:
Yes, yes, yes... Yesss... ;)

Thanks for the info!
[Epic 4G Android Development] sgtkwol:
This has made me laugh more than once.
[Epic 4G Android Development] BigOnes69:
Yes and all before his balls drop.
[Epic 4G Android Development] secorrales:
I tried it this ROM last night...I'm really looking forward to it being more stable.

I had to go back to what I had because the WiFi wouldn't work.

Thanks to Decad3nce and everyone else who's put work into this.
[Epic 4G Android Development] Looneyrat:
Lol! What a jerk! Just so you know, I rock out ever minute of the day! Metes my video, some noon wanted to see who I was. Plus u stole my bike... Remember?

http://www.liveleak.com/view?i=c87_1322688505
[Epic 4G Android Development] worldwidepmp:
Yeah, Crack Rock out...
[Epic 4G Android Development] Phasma343:
Guess you should try reading the thread as the fix was posted for wifi.
[Epic 4G Android Development] ugothakd:
So should you. Its not official

sent from my always aosp epic
[Epic 4G Android Development] Phasma343:
The repacked zip file is not, however the workaround that deca posted is still viable and easy to do.
[Epic 4G Android Development] rundmcarlson:
Hey deca, what gives? Those fools over at CM need to give you a section on their forums as well, you do some great work, keep it up :)
[Epic 4G Android Development] Marlinsfan88:
ahhh wrong forum sorry
[Epic 4G Android Development] tdwp16:
Any word on when we will get official cm7
[Epic 4G Android Development] stir fry a lot:
First rule of rom club is that there are no eta's.
[Epic 4G Android Development] sgtkwol:
Great, someone had to ask. Now it's another day tacked on to the next release. Don't ask for updates or ETAs, but I can guarantee that they are working hard on it, and it will be great.
[Epic 4G Android Development] mattykinsx:
So when is this getting TouchWiz? :confused:

:p
[Epic 4G Android Development] ehurt152:
Those are fighting words around here. Deca will smash you himself.
[Epic 4G Android Development] tdwp16:
I don't want an eta I was just confused as far as if we were getting official or if it was just gonna stay in alpha/beta state...
[Epic 4G Android Development] tdwp16:
Lol thank you
[Epic 4G Android Development] StoneRyno:
It would seem that with two calls I've gotten so far, since a week ago today, there was no ringtone even though it wasn't in silent/vibrate mode. I didn't have time to have test calls to see if calls after them resulted the same or not. I do know that I had no other incoming calls the nights it happened and had other calls earlier in those days that the ringtone played. I charge up at night while I sleep and in the morning when I get up reboot after unplugging from the charger. I can only assume at this point the ringtone not playing is an infrequent fluke/bug or the reboots corrected what would have been any calls after also not playing the ringtone. Won't have more details than that until it happens again. But I wanted to post about it in case there is anything specific I should do or whatnot for ya'll to fix.
[Epic 4G Android Development] justlovejoy:
did you do a thread search?

That's how you'll know if you got new news or outdated info.
[Epic 4G Android Development] stir fry a lot:
I found a pretty cool workaround for not being able to place the Torch widget into my notification bar. If you go to the Lockscreen option under Cyanogenmod settings you can create a gesture to activate the led. I set it so that by drawing a circle on the lockscreen the light comes on. Best part about this is that it won't deactivate once the screen turns off.
[Epic 4G Android Development] Alkah0liK:
No experience with CM, but must say this is pretty sweet. Big thanks to those who have made it possible!

Anyone willing to confirm governers need to be set with setCPU or the like? And bluetooth is / is not supposed to be functional?
[Epic 4G Android Development] StoneRyno:
I did a search to find out when the post was made for reference purposes for this reply. The post I referred to was made Nov 11 (quoted below). In my case it was just two calls on different days and normal the rest of the time. A reply suggested it was data use at the time of the call that caused it though in my case data wasn't being used as far as I can recall. Considering that it's only 2 out of over 20 incoming calls and unknown if it will happen again it's of no concern. I simply wished to provide the info in case there was anything they needed me to do to troubleshoot for a fix if it happened to be a bug.
[Epic 4G Android Development] noobnl:
http://pastebin.com/raw.php?i=gTvsad35

I ran stock under MTD/yaffs2
[Epic 4G Android Development] noobnl:
I fixed the remaining bugs in the device_samsung_EpicMTD branch. MTD builds are coming soon and I expect it to be here within this week
[Epic 4G Android Development] dangambino:
Yay. Many thanks to you guys for taking the initiative to get this going on ur own. There s no reason why this shouldn't be a supported device now and we already have the device maintainers. :)
[Epic 4G Android Development] ugothakd:
To the irc cave. Na na na na na!

sent from my always aosp epic
[Epic 4G Android Development] jbadboy2007:
Lol

10 char
[Epic 4G Android Development] omair2005:
an exciting week ahead! Hopefully the new filesystem can be implemented into miui..
[Epic 4G Android Development] Ceelos09:
It will (I think). Bxfxf mentioned it in his MIUI porting guide :)
[Epic 4G Android Development] AproSamurai:
Partition Map LOL. And it can be if someone makes the proper init.rc changes for MIUI as well as it having the proper init for MTD.
[Epic 4G Android Development] counterfeit187:
If I'm reading this correctly wow! Did I really not plug my phone in for a whole day? According to the time at the top it's true. Of course this was with wifi on the whole time, but I wasn't always in a place that had wifi. This keeps getting better and better.
[Epic 4G Android Development] xboxfanj:
It will. Just fyi though, mtd is not the fs. Yaffs2 is.
[Epic 4G Android Development] FrankyFiggz27:
is mtd/yaffs2 being implemented purely for the greater potential for official cm support? it's not going to be faster or more efficient than ext4, right? cuz it seems that most new phones are moving away from yaffs2 for ext4..
[Epic 4G Android Development] AproSamurai:
Okey doke, my rant of explanation. :)

It's being implemented so that our developers can have control over our partitions and how much space we have in /data and /system /cache. We're on BML, which is restricted and proprietary, being on EXT4 means you're still restricted to the size constraints within those partitions. Once MTD is fully implemented we'll hopefully be able to start ICS source ports because we can now fit ICS in it's fullness within our partitions without the lack of space in some instances. Yaffs2 is a fast filesystem(for those concerned about speed) but newer phones moving to EXT4 are still restricted to the size constraints in some way or another even if they don't need to switch to MTD overall.

This isn't about the future of CM being official it's about the future of the Epic and keeping it in the game.
[Epic 4G Android Development] FrankyFiggz27:
dayammm that sounds awesome. NOW i'm excited. thanks for the explanation. keeping the epic in the game is big for me..got this baby til September 2012.