yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] xboxfanj:
http://www.4shared.com/zip/Eng4D-gy/xboxfanjicsv2.html
[Epic 4G Android Development] iatedeadpeople:
Does this only have the lib/egl folder from the OP?
[Epic 4G Android Development] xboxfanj:
Yes and a couple other changes
[Epic 4G Android Development] iatedeadpeople:
ill give this one a shot, changed the egl folder to the op, i get a bootloop of the android startup logo, but it gets passed sammy screen.

edit: just a black screen with soft keys lit.
[Epic 4G Android Development] xboxfanj:
Could u logcat both?
[Epic 4G Android Development] iatedeadpeople:
yes, sorry, i was busy un semi bricking my phone from a bad backup, and now im setting up my system
[Epic 4G Android Development] iatedeadpeople:
http://db.tt/LAHxKlaX

This is the logcat to your first build with egl folder of OP

http://db.tt/hsxbVbqB

And this one is a logcat of your v2
[Epic 4G Android Development] xBTx:
xbox and I have made some progress.

I'm still testing some things, but keep watching this post, and I should have a new build up in a couple of hours.
[Epic 4G Android Development] iatedeadpeople:
Meaning you'll be up til 3 am?! :D lol
[Epic 4G Android Development] xBTx:
lol it's already 2:30 here, so yes I will be.
[Epic 4G Android Development] iatedeadpeople:
Lol, yea, its 12 here sooo... anyways, progress meaning it boots?
[Epic 4G Android Development] xBTx:
It boots, touch is working half assed, and haptic feedback works.

That's pretty much all that does work.

Oh, and speaking of, here's the new build:

http://www.mediafire.com/?91abmfl4kbmpl35
[Epic 4G Android Development] Timothy08:
will it change the filesystem?
[Epic 4G Android Development] b16flybye:
Well xBTx, this thing started with no bootup and zero touch screen capabilities, so you, xbox, and others I forgot to mention are pushing this thing along nicely. By god, if samsung doesn't give us ICS, you geniuses will find a way.
[Epic 4G Android Development] iatedeadpeople:
Touch doesnt work?
[Epic 4G Android Development] b16flybye:
Touch didn't work when the first build was posted last month. It does now, sort of. ICS is coming along.
[Epic 4G Android Development] flastnoles11:
I love it... progress!!!! You guys are amazing!!!
[Epic 4G Android Development] xboxfanj:
Huge thanks to Rodderik, the epic kernel god. He made the kernel and without him, thered be no progress.
[Epic 4G Android Development] Timothy08:
any luck??? im trying some stuff to try gettin the touch screen to work
[Epic 4G Android Development] xboxfanj:
It is inconsistent, but as long as you use two fingers, it works a little.
[Epic 4G Android Development] Timothy08:
i got it to work so what too i have to use two fingers to scroll it works for me i think want to see i can send you the zip??

Edit: cuz i got the little dot on my phone to see where is pressed at.... and my version number say 2.3.5 ???? but its ics

Edit 2: i got the keyboard mapping down but the power and camera button dont work
[Epic 4G Android Development] ddrbeastappv1:
Good job so far guys! look forward to more updates on this.
[Epic 4G Android Development] xboxfanj:
Just a gb buildprop. Doesn't mean anything
[Epic 4G Android Development] ugothakd:
Maybe an ics build.prop would fix something.

sent from my always aosp epic
[Epic 4G Android Development] AproSamurai:
Two touch has been working for a long time... Just not shared because it's finicky. Take my word for it.

Sent from my Epic 4G
[Epic 4G Android Development] iatedeadpeople:
Yea, i know, let a man dream. Lol
[Epic 4G Android Development] xboxfanj:
Ya I know. I just gave it to xbtx so we can try to fix it and he posted so people can have a taste. Its not usable for over 5 minutes, but its better than the op build. I still feel like there's libs to fix it.
[Epic 4G Android Development] xboxfanj:
I feel like this thread below may help. Some ICS Touch info for a completely different device, but still may help

http://android.modaco.com/topic/348898-dev-aosp-dev-for-zte-blade/page__st__80
[Epic 4G Android Development] ac16313:
you think this one? seems he fixed the two finger issue

http://xdaforums.com/showthread.php?t=1328515
[Epic 4G Android Development] iatedeadpeople:
Wow, this looks promising. Wish I knew watit meant tho.. lol
[Epic 4G Android Development] AproSamurai:
Actually, I'm not meaning to be a buzzkill lol. But this is exactly the same place we were at a month ago. Nothing has changed haha, just now people are going to begin to want an update more and more.:|
[Epic 4G Android Development] iatedeadpeople:
Yea, but it can also be a tactic, trying to give people the low down of wats going on.
[Epic 4G Android Development] AproSamurai:
I do that for CM and people rant about what they pay for, with this they're going to lose the same amount plus some. But you're right.
[Epic 4G Android Development] xboxfanj:
I diffmerged the file that was in the link that someone posted a page back on what worked on ics vs what didnt. It only took 9 changes.

input_report_abs(ts->touch_input, ABS_PRESSURE, 255);

input_report_key(ts->touch_input, BTN_TOUCH, 1);

Most of the changes were the additions of lines like that.

Some had different numbers
[Epic 4G Android Development] xboxfanj:
Here's an interesting post too:

http://xdaforums.com/showpost.php?p=19658625&postcount=1017
[Epic 4G Android Development] iatedeadpeople:
How do I get ahold of our touch driver?
[Epic 4G Android Development] xboxfanj:
The idc is in usr/idc and the others are in kernel
[Epic 4G Android Development] iatedeadpeople:
I don't want the idc one in usr. I want to look at the code for the driver. How do I get that?
[Epic 4G Android Development] xboxfanj:
The gb ones are at github.com/epiccm in the android_kernel_epic4gofficial repo in kernel/input/drivers/touchscreen/qt602240.c and qt602240.h
[Epic 4G Android Development] xboxfanj:
Did rodderik ever give you his sources/modified file? Everything in that thread a page back seemed implementable in our kernel. Just diffmerge the original and the ics one in the thread and add the stuff and compile and we may have touch working as long as you get rodderiks modded files.
[Epic 4G Android Development] AproSamurai:
The driver you're looking for is called qt602240. Quantum TSP Driver. It's a secondary for the MXT224 touch panel which practically the Captivate Fascinate Vibrant use, but custom to us in specific. It looks nothing like the MXT224 driver that they all use, so you can't benefit from it's changes. The Galaxy 3 uses a form of qt602240 which is larger than ours, however they only have froyo if I am correct and I conferred with their developers on how to fix touch. They themselves at the time could not fix their own CM9 compile due to the many natural complications in the build process. The Galaxy Tab 7 being the original uses qt602240, which in itself is different in lines and it's variance. Our touchscreen driver is rooted into cypress just as much as cypress is rooted into it. They're connected and according to other developers controls our hw keyboard as well.

It's not that it hasn't been looked into, I'm a novice at these types of things so someone better or perhaps someone who looks where I overlooked will figure it out as Rodderik had(Don't bother him on this at all) the thing is when looking at our kernel the Epic 4G isn't like the others, we've many differences which don't make sense whatsoever, how touch is governed is likely one of them.

Either way I wish you luck. It'll be in android_kernel_epic4g_gb_official/drivers/input/touchscreen/qt602240.c and or o iirc.
[Epic 4G Android Development] iatedeadpeople:
Actually, I think if you diffmerge, it will change the name of the drivers, and idk if that will do anything. But I think it'll be easier to manually add those lines
[Epic 4G Android Development] AproSamurai:
No, he only gave me the zImage, he did what he could. I thought he told you how he went about doing it. Otherwise I've no clue and I'm not going to bug him on it.
[Epic 4G Android Development] iatedeadpeople:
Do you atleast know how to decompile it?
[Epic 4G Android Development] xboxfanj:
Nah. I'll ask. Last time I talked to him, he was busy and told me to ask later. Do you think those lines I posted earlier could help? They seem to have helped other devices. We may have to sub out some stuff to say qt602240 or something like that
[Epic 4G Android Development] iatedeadpeople:
Its worth a try.
[Epic 4G Android Development] iatedeadpeople:
Hey @xboxfanj can't we just get gb kernel source from epiccm, port it to ics like that one tutorial says to, and while we port, fix touch drivers? I mean, in the process we would be learning.
[Epic 4G Android Development] xboxfanj:
Show me the tutorial. Also, we did use epiccm source, but added a couple init.rc lines and recovery.rc and uevent.rc lines to get it working.
[Epic 4G Android Development] iatedeadpeople:
Finally found it, lol

http://xdaforums.com/showthread.php?t=1312595&ved=0CBcQFjAA&usg=AFQjCNGPlSZastMd8ZDBhYkfvjNl0kXkSA

Edit: just noticed its the same used for the op, that you probably knew about :/
[Epic 4G Android Development] xboxfanj:
Yep. That's exactly what we did.
[Epic 4G Android Development] iatedeadpeople:
What did rodderik do different?
[Epic 4G Android Development] ugothakd:
Nothing. He commented out a few lines in the qt driver

sent from my always aosp epic
[Epic 4G Android Development] xboxfanj:
OK. Thanks. All we did was modify the kernel to support ics (bxfxf did that), then added system folder from ns4g ics to cm7, then some egl files from cm7 to ics hybrid.
[Epic 4G Android Development] qbking77:
Video is up!

Android 4.0 ICS SDK Port on the Samsung Epic 4G!

http://www.youtube.com/watch?v=KKvHl4S1PN0
[Epic 4G Android Development] xizzmatt:
Thank you so much! You're Epic! (Pun intended)
[Epic 4G Android Development] ugothakd:
So this is based on cm7 kernel?
[Epic 4G Android Development] allmasteraa:
No this is based on the kernel that bxfxf worked on with xboxfanj
[Epic 4G Android Development] ugothakd:
Isn't that the cm7 kernel with some edits though?..
[Epic 4G Android Development] :
Do3z 5Gz w0rk?
[Epic 4G Android Development] zanderman112:
^^^ what the .....?

Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"
[Epic 4G Android Development] xboxfanj:
Yes. It is. I used the guide here. http://www.google.com/m/url?ei=hQmy...cQFjAA&usg=AFQjCNGPlSZastMd8ZDBhYkfvjNl0kXkSA
[Epic 4G Android Development] zanderman112:
I'm just glad to see people trying. Nothing ever works without some trial and error. We need more people trying to do this.

Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"
[Epic 4G Android Development] ksweat2292:
wooooo!

Sent from my legacy Epic 4g
[Epic 4G Android Development] Fatonuseni:
Lol, I guess we are not waiting for.Samsung on this one!
[Epic 4G Android Development] ksmullins88:
Count me in on this.
[Epic 4G Android Development] kladd:
This "epic" community will not quit i love it. Thanks guys.
[Epic 4G Android Development] ksmullins88:
idc how old this phone is.. its still one of the best imo
[Epic 4G Android Development] jbadboy2007:
I couldn't agree more
[Epic 4G Android Development] ksmullins88:
downloaded.. ready to try and do some edits tomorrow to get this thing working right,
[Epic 4G Android Development] MikeyLee:
Rock n roll! Hope you can get this stable and working :)

Sent from my CM7 powered Epic Beast...
[Epic 4G Android Development] smartboy36:
This the beginning. Good work guys. Looking forward to the future of this port.
[Epic 4G Android Development] xboxfanj:
New Build. I don't know what works or not. Not even if it boots.

http://www.mediafire.com/?6of2a1rw76exk0c
[Epic 4G Android Development] iatedeadpeople:
Thanks for your intel.
[Epic 4G Android Development] xboxfanj:
Ok. I didn't know what he did. Do you think that the stuff referenced in this thread can help?

http://xdaforums.com/showthread.php?t=1328515

I did a diffcompare and the files that touch worked on and didn't work on weren't very different. I think we may be able to add them (or something similar but with qt602240 subbed in or however our formatting is in comparison to thers, we'd have to mirror).
[Epic 4G Android Development] iatedeadpeople:
I just compared the 2 he did, then I looked at our driver for touch, and it already has those lines, just, not the same language or format or watever.
[Epic 4G Android Development] xboxfanj:
Can you elaborate? And are they the same amount of times as they are in the version I posted? And we may need to add to usr/idc to get this working.
[Epic 4G Android Development] iatedeadpeople:
If you look at his driver and our driver, it completely different.
[Epic 4G Android Development] xboxfanj:
Ugothakd and/or aprosamurai, do you think that adding the idc that should help us into android_device_epic in the prebuilt folder in usr/idc would help? And obviously we'd have to reference it in epicmtd.mk. but do you think that we need to do that or will it not help at all?
[Epic 4G Android Development] AproSamurai:
android_device_epic is a part of actually building CM7(or 9) So perhaps it could if we weren't using an SDK port. The thing is regardless of popular belief, an SDK port is more computer based than Android, so it's not going to be a positive type thing. It'd help with CM9 development but someone would have to build CM9 and we'd use that as a base, which I'm sure if the EpicCM7 team does not jnadke will once he has time and everything slows down in life.

In a little bit, depending on the timing of things I'm sure a lot of people will be happy.
[Epic 4G Android Development] xboxfanj:
Yea I know its for building, but we do have our other usr files there. And also, I've seen other android_devices have usr/idc. Do you think that if someone made an mtd version of this kernel that we'd be able to boot later versions of ics and maybe even a source port, or will mtd not change much?
[Epic 4G Android Development] Shinydude100:
I know it's easier said than done, but honestly if an SDK port is much more complicated than a source port, we might as well have better luck with source. Perhaps more devs would assist once CM7 for the Epic became official. If this cannot progress due to issues such as what we're having, then perhaps (for now) once CM7 goes official, we could focus all of these thinking trains in building CM9. ;)

P. S. I know CM7 is still a KANG, but has anyone tried copying the Epic's CM7, merging it with team hacksung, and getting and early taste of CM9? Perhaps that'd actually work, either that or I've just lost my mind. But anyway. Say we did build ICS from source, we wouldn't want to try to bake Samsung's version with Touchwiz baked in it. So might as well go the CM9 route, or use what you can from CM9.
[Epic 4G Android Development] xboxfanj:
That's past my skills.
[Epic 4G Android Development] b16flybye:
By the time we could officially port ICS, or CM9, we'll all be on LTE dual cores, so may as well forget about it. I'm happy with cm7 for now. Thank you devs for working with what you have.
[Epic 4G Android Development] xboxfanj:
I agree, but for the EpicCM team (deca, noobnl, uberpinguin, etc) it'll probably only take a couple months to be official. They haven't taken long on CM7 since their second restart.
[Epic 4G Android Development] Shinydude100:
That's a load of horse piss. As long as my Epic works, I'm not changing it for another. I've been off contract since I purchased my Epic so I could of changed at any given moment. This is also not true for the many of people who just recently purchased the Epic, and for all of those who are *still* purchasing them. They're still being sold.
[Epic 4G Android Development] SNYPE2K9:
According to the most recent news on the subject it seems they are planning to port a stripped down version of ICS. Would this do anything to speed up development (with official source code and such) or would we just have to extend the official rom?

EDIT: Oh and I just got my Epic before Christmas. I am out of my contract and they go for about $150 on ebay now. So it was a lot of phone for $150. +1 for people that just received and Epic. My brother just got a Fascinate as well.
[Epic 4G Android Development] xboxfanj:
We'll be getting CM9 soon from Decad3nce and noobnl and Rodderik and UberPinguin (Our CM7 Devs), so the Samsung release wont really affect us. This ROM is pretty much dead as the CM9 will replace it.
[Epic 4G Android Development] xplus93:
all this talk about MTD and CM9 is making me consider the nexus s less. i might stick with my Epic. Keyboard FTW
[Epic 4G Android Development] dev997:
ICS 4.0.3 available on GalaxyS I9000 now

I saw a youtube vedio last week of some guy reviewing the official 4.0.3 ICS port on Galaxy S and it was ported pretty amazingly with very minor bugs (messaging was not working, i think).

I was wondering getting a good port on one of the galaxy s series phone might speed up the process of getting iCS ports on Epic4g too.

Epic Timezzzzz !!!!
[Epic 4G Android Development] MДЯCЦSДИT:
No. The other galaxies had cm7 for a long while.
[Epic 4G Android Development] xboxfanj:
It may help the epic cm team. They just finalized cm7 and are starting cm9. I'm sure some of the galaxy s code can be applied to epic, but it'll take more than that.
[Epic 4G Android Development] diptenkrom:
i for one would love to see ICS on the epic. i recently got my wife a nexus s with ICS and it is the most awesome software i have seen on a phone ever. since the hardware is almost the same, the performance should be very similar, and that would make me very happy!

Is this dead? doesn't seem to be much going on...
[Epic 4G Android Development] allmasteraa:
It's not dead. We are still working on it and trying to get a new build. Currently we don't have much progress and are kind of waiting for other developers results
[Epic 4G Android Development] diptenkrom:
cool, thanks allmasteraa!

have you gotten anything else working, or close to working?

after playing with my wife's phone, it is like going back to winxp from win7 to use mine! GB and ICS are night and day!
[Epic 4G Android Development] Timothy08:
hahahaha so ture its like going back to xp from 7 hahaha i had it on my hero and i loved it i wanted to change phones but i forgot that my touch screen is broken:(
[Epic 4G Android Development] xboxfanj:
Once I learn to compile kernels (should be soon, I just installed Xubuntu), I'll try to make a kernel with the ICS required changes for touchscreen. Until then, no progress will be made unless a kernel dev happens to see this (or someone sends this post to a kernel dev).

If someone does happen to see this, there's kernel sources at github.com/sg3

Those have some commits that were needed to get touchscreen to work. We and the Samsung Galaxy 3 (Not galaxy s 3), use the same touchscreen driver, so we should ideally be able to use their commits to add touchscreen functionality.

After that, making a new ROM that is much improved should be easy now that we have MTD to support the larger /data and /system partitions.

The touchscreen driver is in the kernel repository in drivers/input/qt602240.c
[Epic 4G Android Development] Qwallace70129:
I have been holding off on CM7 for a while. I use my 4g daily here in Jacksonville and I just don't see the benefits of CM7 and in turn capping my data( I use about 11gb of 4g a month)......BUT IF SOMEONE GETS THIS WORKING..... THEN F**K 4g!!! I'm already running ICS on my A500 and I can't wait to get it on my Epic!!
[Epic 4G Android Development] AproSamurai:
I'm going to jump on here because I have another thread I need to divulge my attention to.

The Galaxy 3 is using a froyo kernel, all of the fixes in which they're using are to make their kernel have GB/ICS functions, which we in essence already contain. So therefore the changes don't make in our qt602240.c's layout. I've talked to their developers a month ago on it. I wish you luck but either way CM9 is on it's way is all I can. Our main issue is in true honesty, is that the people(myself included) don't understand the way in which touch input is governed in ICS or how to patch it so that two touch would work the way in which Rodderik managed to, I've only given up on ICS to spend my time understanding touch input. So I'd suggest laying off of it for a bit to get a larger more valid understanding of the inner workings of the kernel.
[Epic 4G Android Development] xboxfanj:
OK thanks. I guess I'll wait for the Epic cm team to do their thing.
[Epic 4G Android Development] Timothy08:
How is it comen along?
[Epic 4G Android Development] xboxfanj:
The EpicCM team is working on CM9.
[Epic 4G Android Development] ÜBER™:
OoOOOoOhhhHH :)

http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png

Sent From My Cyan Samurai
[Epic 4G Android Development] m5james:
What does "comen" mean?
[Epic 4G Android Development] :
It's dutch and means " to come"
[Epic 4G Android Development] m5james:
So a Dutch speaking person from Fargo, ND asked the question "How is it to come along?" That sentence makes complete sense now :/ For a second there I just thought it was an ignorant spelling error of an elementary school word, but apparently it's just him being witty and bringing some culture into the forums...I understand now.

Moving on...
[Epic 4G Android Development] fami:
What does "wity" mean?

Edit: Also: "it's" with an apostrophe is the contraction for "it is". It's okay, sometimes people make elementary level grammar mistakes.
[Epic 4G Android Development] xboxfanj:
C'mon guys dont be ross

http://www.youtube.com/watch?v=sLhCzSas07c&feature=related
[Epic 4G Android Development] m5james:
It means using Swype isn't always reading my fingers right and/or I wasn't paying attention vs him meaning to write "comin'" or "coming"...I had no expectation that I have to look up a word in a different language. Some people do intentional misspellings like that on purpose, at least mine was a simple accident. Thanks for pointing that out though, fami.

---------- Post added at 07:18 PM ---------- Previous post was at 07:05 PM ----------

I got the explanation and said moving on already, but cute video.
[Epic 4G Android Development] diptenkrom:
i want to preface this with a sincere "thanks for all the hard work you devs have done and continue to do for the epic/android community!"

sorry to be asking the same question again... but is this being dropped and are all hopes of ICS on the Epic resting on the shoulders of CyanogenMod? is the touchscreen still being a roadblock?

not to take away anything from the efforts of the Epic CM Team, but it is nice to have choices. i, and i hope others as well, am really hoping for a "vanilla" ICS port for the epic. i like my keyboard, and don't want to have to give that up for a nexus just to get ICS.

just looks like there is nothing happening. maybe that is just my misconception, but the first post has not been updated in a long time. wish i had the programming know-how to help out with this endeavor, but i don't, more of a hardware man myself.
[Epic 4G Android Development] xboxfanj:
There are some things id personally rather not say yet until later because I don't want to release a bad build, but I also dont want people hounding me to release a build, so I'm not gonna say exactly. Just know this, there is still progress made and just recently a pretty huge advancement made recently.

I'm letting you guys know that and that only.

Sorry for the huge tease, but I don't want to deliver empty promises and I know that xda users can get angry (and when dr evil gets angry, mr bigglesworth gets upset and when mr bigglesworth gets upset, people die). Whoa there. Sorry for the lame austin powers reference. Not a death threat.

I'm posting this so you don't think we forgot about you.

When/if i/we get a few more things working, I'll let you know and may show you instead of only telling.
[Epic 4G Android Development] :
I understand what you just said, but can you at least tell us what should be expected in future releases?