yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Alright, it would be more convenient to do it that way, but since it's 4GB VS. 16MB I digress :D.

Thanks for the link, I will upload once I get everything initiated.

EDIT: i am having issues initiating and syncing the repo (for some reason it keeps rejecting my commit due to unmerged files or something), but I will keep trying.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Which repo you want to sync, and I've made an ics branch for a new repo instead.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
I'm syncing to the CM9 repo I just made, and I think I finally got it to work (either that or it's hanging after asking for my password and username).

EDIT: Phew, that's done. Now I need to go off and read all the git documentation I can find.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I think the only thing you would need to know about git is git add, commit, rm, status, and that's about it.
[Samsung Galaxy Player 4.0, 5.0] Neodymium:
How about uploading only neccesary files? Cm9 source has too much unneccesary giles in it.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
I guess that's a good idea if you want to pare down several GB worth of files to the ones we need, add tdm's source and push it. It would actually work, but be rather time-consuming to do, IMHO.

EDIT can someone PLEASE tell me what I need do in the way of combinign tdm's source+CM9 source, to get a running build. I have to searching for awhile now, and haven't been able to find ANYTHING that explains it.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
This is how everyone does their device tree (Even cyanogenmod because the source is maintained by them, not us) Anyway here's the way to get it to compile:

http://wiki.cyanogenmod.com/wiki/Template:Build_from_source_(CM9)

Also neo, do you want to be in the organization?
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
I'm trying that, but I can't figure out how to point brunch to our repo. If I could do that, I would be fine. Perhaps I can copy the files manually?

EDIT: I suppose I am going to need to edit the manifest, right?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Do you have the vendor files set up? if not execute the extract-files.sh and retry to compile.
[Samsung Galaxy Player 4.0, 5.0] klin1344:
If I'm not mistaken you can't use 'brunch' because ypg1 is not a device that's merged into official CM. You would have to do 'lunch', then 'make' then 'make otapackage'.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Okay, I was informed to brunch (or lunch, this is making me hungry) first before running that.

Klin, I will run lunch as soon as I figure out what the heck it is :).
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
it's not mandatory (and it's long too) to do this because I don't know if it's the case but maybe the device tree isn't a recognized one because it's generally setup by vendorsetup.sh

I can compile just fine by this command:

. build/envsetup.sh && brunch ypg1

Han did you extract the libs from your device?
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Yeah I just did, and I figured out I was doing "YP-G1" instead of ypg1. Man, I feel like an idiot :D. Anyway, I will try again, and hopefully it will wokr this time.

EDIT: I have TDM's folder in devices listed as ypg1, and it isn't building from it (and doesn't see cm.mk). Still erroring out like always.

Output:

build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/ypg1/cm.mk]]: "device/samsung/ypg1/full_ypg1.mk" does not exist. Stop.

The thing is, full_ypg1 DOES exist, and it's right there in the directory it's requesting!

EDIT: NVM apparentlyy full_ypg1 was looking for device/samsung/ypg1, and I had /device/Samsung/ypg1.

EDIT: now it's complaining about my java version. Version 7, Y U NO work with Cyanogenmod!

EDIT: it's building right now, fingers crossed! I'm using -j4 on a dual-core, what do you guys find to be the best variable?

EDIT: as soon as it finishes building, I will start working on fixing boardconfig.mk and OpenGL. Oisis, what do you think is causing the GL crash?

EDIT: it compiles fine for ~1hr, then it halts after being unable to configure some .apk. I'm hoping it was a fluke, and i'll try again.

EDIT: it was stopping because I didn't pull the prebuilts before compiling. Hopefully now everything will work as planned.
[Samsung Galaxy Player 4.0, 5.0] Neodymium:
I thought I really HAD an idea to fix recovery, but now I feel.like I was stupid:(

I found that there was last_log file in /cache/recovery so I was very happy. But after few minutes, I recognized that in order to check the log, I should flash well-booting kernel, and you guys will well know that after accessing to recovery first time, it goes infinitely before clicking reboot system now. So it means the previous recovery log is erased, and pure well-booting recovery's log will be written.

???

So isn't there any way to check the log when recovery error occurs? Can't I backup my partitions when in download mode via heimdall?
[Samsung Galaxy Player 4.0, 5.0] oisis:
Hi guys,

Sorry but today don't have time, moving to new apartment. Do not commit anything today, wait with that. Will be back tomorrow evening and will explain everything.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Why wouldn't you be able to pull the file via adb while in recovery? The ICS kernel DOES have adb recovery, I used it a lot when I was getting it running on my device.

@Oisis, good luck with your new apartment! Don't worry, today we just setup the repos, at most I might push a fixed boardconfig.mk, but nothing else.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
yea we can see the log. If you make report errors in the advanced menu, the log will be saved.
[Samsung Galaxy Player 4.0, 5.0] klin1344:
Guys you can refer to this article if you need some clarificiation for the different build commands: http://blog.cameronpickett.com/2011/09/16/breakfast-brunch-and-lunch/

Anyways good luck. If I still had my Galaxy Player, I would definitely be helping you guys right now..
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Thanks for the link. It's a shame you left the community, we need all the devs we can get, especially since they are all working on ICS right now.

Alright, I took a look at boardconfig.mk from sgs, and there is a LOT there that we can easily implement onto ours (heck, we can even just copy/paste it over no problem), and save us a lot of grief, and get FM working hopefully.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
there's not a lot of lines on the boardconfig.mk from the I9000. There's just actually the FM radio support:confused:.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Well maybe not a lot, but there is certainly a decent amount we can compare and fool around with, to hopefully get a better-working build.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Wow, I am going to need to obtain a better build machine, or tweak the heck out of the build process; i'm over 6 hours now, and not even done compiling! I know that the initial build takes longer than others, but this is a little ridiculous. I suppose that I can start the build process before I leave for school, and i'll have a finished build when I get back, but geez!

I'll be using ccache at least, any other compiling tweaks you know of?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
You sure you're on ICS branch because the default one is GB.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Yeah believe me, I made sure I was looking at a CM9 repo before I started poking around:rolleyes:. It DOES look intriguing though, as there are some variables there that are not in our makefile, and vice-versa, so I am going to poke around there this weekend, and hope that I can come up with a better-working build. I finally finished compiling, so my fingers are crossed that webkit is fixed, as Oisis' build was a little weird. Either way, i'll put it up tomorrow provided that all goes well.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Okk I'll check it again, it can be aries-common too.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Alright, so apparently the GL crash is caused by the lack of necessary libs in place, so I am rebuilding that on my compiled form from Oisis' as we speak. I will upload a folder with all of the needed files later for inspection.

EDIT: now that I have gotten past those errors, I am now getting this when surfaceflinger tried to execute (this is only a small part of the crash report):

/libEGL ( 781): loaded /system/lib/egl/libEGL_POWERVR_SGX540_120.so

D/libEGL ( 781): loaded /system/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so

D/libEGL ( 781): loaded /system/lib/egl/libGLESv2_POWERVR_SGX540_120.so

E/libEGL ( 781): initialize:293 error 3001 (EGL_NOT_INITIALIZED)

E/libEGL ( 781): validate_display:190 error 3001 (EGL_NOT_INITIALIZED)

E/libEGL ( 781): validate_display:190 error 3001 (EGL_NOT_INITIALIZED)

F/libc ( 781): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

This seems to be the pertinent part, and I woudl really like to know why it isn't working! Again, maybe it all relates to boardconfig.mk being messed up...

EDIT: I was poking around in boardconfig.mk, and I found this:

# ICS settings

DISABLE_DEXPREOPT := true

COMMON_GLOBAL_CFLAGS += -DMISSING_EGL_EXTERNAL_IMAGE

COMMON_GLOBAL_CFLAGS += -DMISSING_GRALLOC_BUFFERS

COMMON_GLOBAL_CFLAGS += -DMISSING_EGL_PIXEL_FORMAT_YV12

It looks promising, but can someone please tell me what the variables mean?

EDIT: WOW it's NICE to only have to recompile the essentials! I did only edit the boardconfig.mk, but it compiled in under 5 minutes! This is going to come in handy...
[Samsung Galaxy Player 4.0, 5.0] Neodymium:
But the problem is that The recovery has an error, so I can't get into recovery. Is adb possible when it's in bootlogo state?

---------- Post added at 04:12 AM ---------- Previous post was at 04:09 AM ----------

Ummm... I found that in gingerbread, I have 4 libs in /lib/egl. They are 3things in log, and one is libGLES_android.so
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
We found the E: no misc partition error. it's in the recovery.rc I don't remember which line.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Could you upload them here please? That may be useful for fixing egl.

Stupid question, but do you have to 100% (not the incremental build) rebuild to use new settings in boardconfig.mk?

EDIT: My project for today (or at least until Oisis gets back to me about fixing EGL: cloning aries source(aries-common+galaxysmtd), and trying to use it to patch up ours, or modify it and comile from that.

EDIT: EGL is definately not boardconfig.mk based. I pulled the one from aries, and modded it for the Gplayer, and I am still getting the "EGL_BAD_DISPLAY" and "EGL_BAD_PARAMETER" errors when GL tries to start, so it definately it something wrong in another area. Oisis, we need your fix!

EDIT: Thinking about it, it may not be GL-based at all. I set the config to NOT use GL, and I still got the crash, sao maybe it's something else that's missing/mucked up.

EDIT: I am going to try and set GL to refuse to use HW rendering, hopefully that will be a workaround fix. The Nook Color seemed to have similar issues to what we do, so reading their CM9 threads may be useful.

EDIT: IT worked! The problem is that the colors are completely messed up, the screen had a TON of artifacts, and it's very slow. But it's a workaround until Oisis gets back to us. For the record, I edited EGL.cfg and added 0 1 android to the top, and set sgx540 to 0 0. So I guess the definitively narrows the issue down to something in /egl not being there, or not functioning properly. I will push that and my fixed/improved boardconfig.mk to github unless someone says otherwise, as it's progress over what we have in there now.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Ok I see what you have done. You removed the hardware rendering by the device and replaced it by software rendering like this:

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

However the egl.cfg on ICS is 0 1 for the SGX so.. did oisis made a magical trick or something?
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Yeah, that's exactly what I did. Oisis found whatt he issue was (or a pretty darn good workaround for it) and built using that. The problem? He never shared it with us, and is setting up his new apartment, so we are stuck until he can push it to github. He DID have GL-related files in egl, so maybe sgx540 wants to link to them or something?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I think it's something he change to the makefile because how he can do it and we can't, and he said that the cflags were for something and the only cflags I can see related to the GPU is the ICS setting at the bottom.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
He said that the Cflags may be causing instability, I don't believe he said anything about them being related to the GL crash (although I jumped to that conclusion a few posts later). I commited my workaround and fixed config, so now I guess we wait for OIsis to share his fix.
[Samsung Galaxy Player 4.0, 5.0] oisis:
Will be back tomorrow, didn't make any workaround, I just compiled pure tdm config files. There is nothing to push on github from me now. Build 1 was only try to tdm config files. I happy that you built your first CM9 for UP-G1 I think that is good direction.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
You have a magic computer then :p. But now that I'm thinking of it, all the devices we have tried were US one, however me and fromnowon were Intl devices :confused:. Han can you send your build with the defective egl?
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Okay, i'll look for you tomorrow after I get home. Since you only used vanilla TDM, perhaps your compiler type/version makes a difference. Are you using the compiler built into the CM builds, or are you using a different one? perhaps that is the issue, as I am using the built-in compiler, and I bet TDM was too.

EDIT: zaclimon, i'll upload it as soon as possible. Man, that would stink if only INTL devices could run OpenGL for now, although I doubt it, as Oisis' build worked on my US player just fine (comparatively).
[Samsung Galaxy Player 4.0, 5.0] oisis:
I'm using CM9 compiler.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
But when we compile it, isn't it used by default or we have to path it?

---------- Post added at 12:48 PM ---------- Previous post was at 12:47 PM ----------

That's what I tought too. This is very weird?:confused:
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
This is going out on a long, but sometimes compilers son t work well on certain Linux versions. What are you using? I'm using Ubuntu 12.04, which may have issues. Zaclimon, can you try compiling with your mint 11 build?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
it's linux mint 13 (which is based from ubuntu 12.04). and android can just be compiled with ubuntu (or debian) and mac. (I think). I will retry though.
[Samsung Galaxy Player 4.0, 5.0] oisis:
We have this same compiler if you use CM9 one. You have to set up path to compiler in your ~/.bashrc file and use bash. I think that libs from system are needed to build so maybe that is why? I'm using Kubuntu 12.04 x86_64 it is the same as Ubuntu but with KDE.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Ugh, KDE is so...heavy. Why would you want it as your build enviroment? Maybe i'm just used to fixing up old computers, but that would be my last choice for a build enviroment.

Anyway, I double-checked my bashrc, and I *think* I have it setup correctly-

#Android Toolchain PATH

export ARCH=arm

export CCOMPILE=$CROSS_COMPILE

export CROSS_COMPILE=arm-eabi-

export PATH=$PATH:/home/lee/stuff/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin

What do you mean by libs from system? Do you mean libs from the actual enviroment (ubuntu,mint, etc.) or from the cyanogenmod folder?

EDIT: zaclimon, here's my build. All I did was muck around with BoardConfig with this one (already pushed to github): http://www.mediafire.com/?mc7vct7iycc12b7
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Is it in the prebuilts folder? And han, KDE is maybe the heaviest DE but it is the most beautiful one too :D. I hope when I'll get a new computer (if it's possible) to put linux mint KDE (it looks better than kubuntu). However gnome does a really good job too.
[Samsung Galaxy Player 4.0, 5.0] oisis:
For me kde is some much better than Gnome, and I will not change my mind :). Check my thread about compiling kernel, it is in i9001 section, name is kernel 3.0.8. Yes I'm talking about some libs and headers from Linux system like Ubuntu.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Yeah, well the only computers I have ever been able to playa round with are kinda low-end (either old laptops from other family members or the 2009 one I bought for myself for $500). I think I know what my next purchase will be...
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Yeah, I mean I like it as an enviroment, but it's a little too heavy for the computers I use.

Now if the libs were the issue, wouldn't it not boot at all/other builds fail if that was the case?

Since TDMCode was able to compile CM7 perfectly fine, but not CM9, I don't think (hopefully) that that is the issue. Who knows, it probably isn't even the compiler. Maybe you did something to the folder that we didn't (maybe permission-wise or something).
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
But we do have the same libs as tdm used in oisis build. But let's work on the recovery first. Then this part is finished and then we work on the libs issue.

EDIT: Damn I got an error when I tried to get tdm's libs:

error: do_inode_allocate_extents: Failed to allocate 144 blocks

So it seems I have to compile from the beginning. -.-
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Alright, then it looks like I'm our of the picture for now. I'll keep working on the libs, hut I won't start serious development back up until recovery is fixed.
[Samsung Galaxy Player 4.0, 5.0] Neodymium:
How about using linaro 4.7.x build? I use it when I compile my kernel.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Maybe, but Linaro is designed for speed, and is a lot buggier than GCC. I think that I will just compare the aries and ypg1 sources first before I start working on compilers. If OIsis can successfully compile from our source again with GL working, then perhaps he has something on his computer that we don't have, say maybe the aries source that somehow this is pulling from? It IS possible that since TDMcode (I presume) just modded the aries source that some makefile is still pointing to the aries folder, and isn't redirected to ours. Or perhaps OIsis does have the magic computer and a fluke allowed the compiler to fix EGL (computers are the one time where doing the same thing over and over again and expecting the same result is considered normal and okay), but this is worth some investigating. Maybe i'll rebuild with aries-commom and galaxysmtd on my laptop, and perhaps it will work. :p
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Don't even bother to try aries-common and galaxysmtd, your device will become a brick and you would need to restore it to stock. Also as you said the Linaro toolchain isn't well used for android and can make some bugs. We just have to know what is the narnia trick that oisis made in order to get it to work.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
In my experience (I flashed a few SGS ICS builds), it doesn't brick (at least bootloop) your device, it just differs enough that it fails to boot (I didn't look at the logcats closely enough to determine why). I believe that if we selectively pick what we need from the aries source, it will help us tremendously (heck, I bet that if we played our cards right we could even boot from it), but yeah, using too much will probably break more than it will fix. I for one am mixing and matching configs and a few HW files (in a blind hope that the HW files fix GL).
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Alright but don't forget that I9000 uses newer libs and kernel drivers than us (just a side note):p
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Yeah, thanks for that, i'll keep it in mind. For now, unless it's a config, i'm just throwing it against the wall to see if ti sticks.

On another depressing note, I discovered that if I want my changes to be used, I actually have to run make clean bafore rebuilding (tell me that i'm wrong, please), meaning that any work I have done so far has gone nowhere.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Well you want to use practically all the galaxysmtd and aries-common files, it was inevitable for you to make a new build.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Yeah, but am I correct in saying that if I want to make a new build with edited files, I probably need to make clean?

EDIT: looking at the logcat, it seems like EGL is looking for the display, but can't find it? I tried editing EGL.cfg, but that didn't seem to have an effect, and since 0 0 android works, perhaps it refers to something else?

Anyway, I have to sign off since it's a school night, but I will tets my new build once I get home tomorrow, and hopefully pinpoint what the issue is, if you guys and Oisis don't figure it out first.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Alright good luck at school.:p
[Samsung Galaxy Player 4.0, 5.0] Neodymium:
Ummm... getting harder to translate and understand as the topic gets deeper :)

---------- Post added at 08:45 AM ---------- Previous post was at 08:33 AM ----------

Well it would be a wrong thought but I believe that we can share our roms (at least device tree) with galaxys.

---------- Post added at 08:45 AM ---------- Previous post was at 08:45 AM ----------

Well it would be a wrong thought but I believe that we can share our roms (at least device tree) with galaxys.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Well, google translate is your friend (unless that's what's messing it up ;)).

To answer your question, we baiscally DO share a device tree with the SGS, or at least ours is heavily based off of it (and we can draw on their sources to fix most issues), which fortunately makes developing ICS, while hardly easy, a lot less difficult than if we had to do it all ourself.

EDIT: I tried my new build (I replaced the boardconfig+video files with aries), and: no go. Not even the logcat changed, whcih makes me certain that TDM just used aries sources. My personal theory is that a file is missing, or pointing in the wrong location. Maybe someone with a lot of time on their hands can compare both sources and see what's wrong?
[Samsung Galaxy Player 4.0, 5.0] oisis:
I'm back in business now. I moved to new appartment finally, hard to find some corner for work. So if you have problems with compilation just PM me, i will try to help. First we should take care about recovery and kernel i think and I'm trying to find out what is going wrong with that.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Alright, you guys focus on that, I think I can fix the GL issue on my own, since it seems to just be something pointing to the wrong directory or something. Oisis, I forgot to ask you in your PM, but can you copy/paste your path config for your compiler please? Also, do you use ccache or any other type of compiler optimizations?

Not necessary, but can you compile CM9 again (from tdm's repo, not ours), so we can tell if it is your computer, or just a fluke.

EDIT: I found this group discussing our EXACT issue: https://groups.google.com/forum/?fromgroups=#!topic/android-platform/4fom7CSXR1c

Oisis, how did you get your proprietary files (since I know there was no "working" CM10 build for you to extract from)? I think this is the key!

EDIT: link for more info on our issue, if you were interested: http://www.khronos.org/opengles/sdk/1.1/docs/man/eglMakeCurrent.xml
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Ohh I remember. Oisis did say that he put the proprietary files himself. Maybe it's the way he put them that is the cause of it working.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Yes! MAN, I am really excited to (maybe) have our biggest issue cracked after spending literally my entire weekend compiling and recompiling (turns out I never thought to use google, AND I didn't have a vendor folder. That's what happens when you don't get enough sleep kids :D).