yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] Ahmazin:
The number 1 rule is to be civil and courteous to one another

There are probably 1000s of people new to XDA daily, inform them of the "number 1" rule and leave it at that. Don't scold them like children. He may be a senior member, but I've been here longer... and it's easy enough to be nice about explaining how things works.

No disrespect to anyone, but I just don't condone or excuse, bad behavior.
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
I feel bad about hijacking this thread but please tell us! I think a pm might be a bit better though
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
There's generally the rules for this(like the rules after you register) but I don't think people would read them. But I agree that he should have go in a way that would be more gentle. Also klin where have you been? (working at your kernel I presume:p) and supermaster I will send you PM later today because it's sleep time (it's 2am here so...)
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Yeah but at least I knew the rules when I started visiting the forums. I was in no way trying to be rude or such. And I never said I was his Dad, and I never said I owned XDA. But I apologize for any misunderstandings.
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
You guys need to chill. This is development, so only post if you have contributions to make. I'm going to start porting the PVR drivers from the nexus s 3.0 kernel to the SGP. I know JackpotClavin was doing so before he stopped so I'll see if I can get hw acceleration working. Also thanks to zaclimon for the tip
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
It's in the past now. Let's move on and try to adhere to the spirit of XDA and never cease to learn something new, realize that all will need educating along the way, and be supportive of each other.

I'd venture a guess that the SGP 5/4 forum is one of the smallest on XDA, which is even more reason that we should try to get along. We need all the devs, testers, and themers that we can get for our device's community.
[Samsung Galaxy Player 4.0, 5.0] apapousek:
Damn, I leave for a while and the whole Dev forum went to crap. Awesome.

UPDATE:

New computer came in. Beautiful. I'm now on the University's Internet connection. Downloading / Uploading will be easier for me. I'll be taking a crack at compiling/improving CM9 for our Galaxy.
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
I'm sorry and I'm seriously not trying to be rude, but I think we have enough CM9 ROMs lying around. Gmillz says he could use help in porting over CM10 though.
[Samsung Galaxy Player 4.0, 5.0] gmillz:
If you know anything about boot.imgs it would be great of you could take the one from cm9 and edit the ramdisk for cm10

Sent from my SGH-I897 using Xparent Red Tapatalk 2

---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------

If he has experience, then he can contribute to cm9 just let's not male another thread and work alone

Let's team up and maybe we could conquer it.

Sent from my SGH-I897 using Xparent Red Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] apapousek:
What we have is a pile of crappy CM9 Roms lying around. I still have permission from the Zeam Team, and I'll be including the Zeam launcher (maybe) into my Rom. It'll be pretty.
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Supermasters cm9 is amazing, thanks very much and so is gmillz cm9. Still the same
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Howdy guys. Really long time, no talk. The USB port on my old Galaxy Player broke so I couldn't ROM anymore on it. However, I got my hands on a new one so I will be taking another shot at this 3.0 kernel for the Galaxy Player. What I'm doing in using the stock source and doing a cherry pick on every commit up to the latest ICS source (I'll move onto JB when we get there). It will take a very long time to get to 3.0 (we're starting at 2.6.35 so we have to manually fix conflicts from cherry picks from commits from around 5/30/2010 and on and place them on top of the source of the Galaxy Player's source. It will be a long time till I'm upstream but the 5.0 should be able to perform along side the Nexus S running ICS and JB in terms of performance :)
[Samsung Galaxy Player 4.0, 5.0] omaroe666:
good to hear that you got another player : ) i spoke to you 1 week ago then you said you broke your usb so i was afraid that you din't should comeback to the forum of galaxy player but im happy you're back : ) *sorry for my english* happy that you're back jackpot welcome back : )
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Yes! Thank you so much for never leaving this community forever! We need skilled people such as yourself to help us with everything possible. I would reccomend talking to gmillz and supermaster34 about getting 3.0 kernel
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Well it seems that something happened to my /dev/block/mmcblk tables so my galaxy player seems to be screwed. I can't do anything besides boot into recovery and use some adb commands, but since I have no /system /data or /cache block to mount, I can no longer do anything making my 5.0 slightly more effective than a paperweight. I'm open to any suggestions from anybody who has had this issue before me and I'm curious as to what you did to rectify the issue. Thanks for your time
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
If you want, I can make a backup of those blocks if it's possible so you can flash them with Heimdall? Would it work?
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
I actually just got it working from a guide here: http://xdaforums.com/showthread.php?t=1468213

I'd be totally screwed without that :) back to kernel work
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
Glad to see that you're still with us. :)
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Good news everybody. I abandoned the cherry-pick method for git and went straight to the ICS kernel source and backported US 5.0 files. This method is a lot better because there's no bloat or anything, just the files necessary to get the device to boot. I did this about 10 previous other times (and probably wasted like a combined 200+ hours) throughout the months and never got anywhere, but now, I'm able to boot my galaxy player into recovery (the screen still isn't working so it's just black) but I can debug via adb which makes us like 90% of the way there since we can get debug messages now and see what's failing and adjust accordingly based on those messages. It's gonna be sweet once the screen is working :)

~ # cat /proc/version

Linux version 3.0.8-G70UEKI8-CL566269 (JPC@JPC-ThinkPad-X220) (gcc version 4.4.3 (GCC) ) #18 PREEMPT Tue Sep 18 16:47:57 EDT 2012
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
What would we do without you? (And the other amazing devs, of course.) Thank you for your continual investment of time and effort in our humble Galaxy Player Community.
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
I really appreciate your work being done. I am extremely grateful for your presence in this world. Thanks you for your time and effort.
[Samsung Galaxy Player 4.0, 5.0] heat361:
Is any of this on your github?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Awesome job! Can't wait to build it myself! :D
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Howdy fellas, been a few days since I got the 3.0 kernel working on the Galaxy Player 5.0, since then, I've been working almost constantly to get this ready for primetime. There's still a lot of stuff that needs work, so for the sake of brevity, I'll say that does work. The screen display and the touch screen work perfectly, just got wifi running a second ago and that's about all I have of the bare essentials right now. My list goes:

1. Sound

2. A battery driver (it currently says 0%, I've added the necessary source to get it to work, but then I lost the ability to USB debug, so I disabled it for now since I don't need it)

3. The ability to power off the device (I'll push kernel source out and upload a super-alpha ROM once I get this working) I think I know what's causing this so it will be next on my to-do list

Right now I'm running a Samsung Vibrant CM10 4.1.1 ROM nightly from yesterday or the day before and it's really smooth. I don't have a hwcomposer right now because the aries one doesn't work for some strange reason, but once this is working, it should be a lot smoother. I'm running a 3.0.31 kernel with the latest Jellybean sources from Google
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
It might be worth trying the hwcomposer from the Nexus S. Also this is amazing news! Great work!!
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
I had just thought of that a second ago. If not I will try to write one based on it to make it even smoother
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
That's nice!!! From which sources are you based on? Stock, teamhacksung? Also does it needs special work like writing some c codes?
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
It's the bare essentials from Entropy512's overclock kernel (it's pretty close to stock Samsung sources because I haven't taken many files that he modified) but I'm using his defconfig for his overclock branch (with necessary 3.0 kernel changes) which is pretty different from the one that Samsung gave us (his was closer to what we need). This battery driver is gonna have to be reworked to see exactly what's the reason behind the USB not being recognized and no debugging when we have a working battery driver. For now, the battery driver is disabled so it shows 0%, but can be easily added into the kernel by adding CONFIG_BATTERY_ADC=y into our defconfig; but you'll lose the ability to debug via the USB. As for the USB driver, those USB files in drivers/usb/ are taken straight from the 2.6.35.7 kernel sources so the USB OTG probably won't work until the necessary files to get our USB working are properly merged in to the 3.0.31 kernel.

I just got the poweroff function working in the 3.0.31 kernel, but for some reason, lost the ability to reboot. This shouldn't be too much of an issue, for now so I'm gonna push the kernel sources either today or tomorrow when I find some free time, and I'll make a clockwork backup of my current system and boot.img and upload for you to flash. In order to use it, you'll have to push backup folder into your /sdcard/clockworkmod/backup/ directory, and you'll have to do a clockwork restore of that folder, then wipe your /data and /cache and reboot and it should boot into the backed up image of my device's current setup (new kernel and Vibrant CM10 build slightly modified to boot on our device)

Sound is probably gonna be a pain in the arss to get working, I need to see how close the Vibrant aries device was to our device sound-wise (hopefully close to it) and merge accordingly. Worst comes to worst, we will have to use the 2.6.35.7 sound files from the kernel source and use our old Gingerbread libraries.

After the sound is done, that should be it for major features missing from the device with the 3.0.31 kernel and CM10 builds :)
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
I love you
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
I love you
[Samsung Galaxy Player 4.0, 5.0] heat361:
Is it possible to add the FM radio drivers?
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Probably, it's not very high on the to-do list, however. I tried to add the vibrator sources, but for some reason, the module failed to build right at the absolute end of the build.
[Samsung Galaxy Player 4.0, 5.0] heat361:
OK well I hope you add it to the kernel since this is a music player. Were the vibrator sources from 2.6 kernel?
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
I'm sorry, but when did you say you were gonna upload the cwm backup?
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
READ DIRECTIONS. I TAKE NO RESPONSIBILITY FOR YOUR MESS UP IF YOU CHOOSE TO NOT FOLLOW DIRECTIONS. I JUST DID THIS ON MY DEVICE SO IT WORKS FINE.

I'd only recommend using this if you are an experienced developer and familiar with clockworkmod and flashing images. MAKE A BACKUP OF YOUR CURRENT SETUP. My 3.0.31 kernel does not have a recovery in it, so after you flash this, you will lose clockwork recovery unless you put it back in yourself manually. I don't know how to do this with odin, but in heimdall, you can just flash Entropy512's overclock + clockwork recovery all-in-one package which is available on these very XDA developer forums. After reflashing Entropy512's kernel that has clockwork recovery, you can boot into recovery by pressing the up + power and then restore a backup.

Now that you've made you backup, let's get down to business. In order to flash this, you will have to extract the .zip file which will yield a folder called jb.preview that is just a nandroid backup of my 3.0.31 kernel and the CM10 vibrant rom that I modified to boot on the GP USA. You add this jb.preview folder into your /sdcard/clockworkmod/backup/ folder so its new location will be under /sdcard/clockworkmod/backup/jb.preview.

After you copy this folder to the sdcard, reboot into recovery and then select the option where you restore and then restore the folder called jb.preview. Once that rewrites the /system and boot image to the new 3.0.31 kernel, you have to DO A FACTORY RESET IN THE RECOVERY but do not wipe your system; just a simply "wipe data/factory reset" will do. After that's all wiped, select reboot in clockwork and it should reboot into CM10 after staying at the bootanimation for a few mins as it builds the /cache you just wiped. After it boots, let the device be for a few minutes until everything is all done initializing. Then, have a little fun playing around with it :)

What this CM10 super alpha preview has: a working display, and touchscreen, also wifi.

It should be noted that the reboot function does not work currently, but selecting power off works fine.

These instructions are simple:

1. Backup your stuff

2. Extract the jb.preview zip to yield the jb.preview folder and push the jb.preview folder to /sdcard/clockworkmod/backup/ so its location on your sdcard is /sdcard/clockworkmod/backup/jb.preview

3. Reboot into Clockwork and select the option to restore

4. Choose jb.preview

5. Wipe do a factory reset, do not wipe system

6. Choose reboot and it will reboot into CM10

Download from here: http://www.mediafire.com/?rb758g873z6omwd

07b54c851d0582ad1471293a1dfcfdbf jb.preview.zip

One thing to note is that for some reason, the /sdcard shows up as corrupt, but it's not, so don't reformat it thinking that reformatting it will fix it
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
When this uploads, let the dev work of others begin!!! >:D
[Samsung Galaxy Player 4.0, 5.0] heat361:
You will try add cwm6 into your next build right? I could see some inexperienced people bricking their device or unable to use heimdall,fast boot or adb.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
That's why I want to keep it as experienced people with this super-alpha. I'd shy away for a few weeks if you're inexperienced until this is *actually worth* trying out. This is more-or-less a proof of concept to give people a taste of what's to come and to give some kernel developers a place to start :)
[Samsung Galaxy Player 4.0, 5.0] heat361:
Its no problem for me to get this up and running but I just hope just experienced users test this out.:)
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Haha I understand. Were you able to get this up and running? I wanna know if anybody got this working yet to make sure I didn't jump a step to confuse some people
[Samsung Galaxy Player 4.0, 5.0] rafa6571:
Can we flash gapps with this?
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
I may be way out in front of you guys with this question, but I am so stoked for this and can't help myself.

Would it be possible to extract properties from a kernel with support for a physical home button (such as Noisyfox's), and patch them to the 3.x kernel in order to have a working kernel for international and Korean devices?

Sorry if I am getting in the way. I just wanted to get that out there now. :)
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
It'll probably have to be added into the source code. I'm pushing my kernel sources now, but the upload to github has failed twice now and I'm trying for a third time to see if I can get it uploaded. If this fails, I'll give up for the day and try again tomorrow (just hit midnight here on the east coast)

Edit: it failed again, I'll try tomorrow morning
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Initially I got a md5 mismatch, but after recreating tje nandroid.md5 file, it restored fine. It boots fast (a lot better than I thought, even the first time), and the issues you describe are accurate. One thing I did notice was root was not really root... I think. That is, superuser didn't remember anything, and even as 'root' I still couldn't mount system rw. But awesome work nonetheless. Maybe next week I can help work on some stuff, we'll see. Until then, I'll definitely keep watching this thread.

Edit: you probably already know this, but just in case, not only is the internal sd not getting mounted, but the external sd isn't even getting detected at the kernel level - no device node.
[Samsung Galaxy Player 4.0, 5.0] heat361:
I downloaded it but have yet to install it since I gave the SGP to my mom but I'll see if I can pry it from her to test it out lol :)

edit: is sound working?
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Tried it. When you say super-alpha, it really is super alpha... Browsing is very buggy for me and I tried camera but it doesn't work. And sound doesn't work either, can't download apps either cause of SD card
[Samsung Galaxy Player 4.0, 5.0] heat361:
Oooh I think I'll hold off until the a beta is release and a cwm6 for the kernel is added
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Yeah, I really just made this for some devs to give me a hand with the device and the kernel. Having a booting CM10 build and a 3.0.31 kernel has given us a place to start and unify our build environments to build up on. I had said that the only things that work are the display, wifi, and touchscreen a while back
[Samsung Galaxy Player 4.0, 5.0] Cm9aphla:
so your saying you got a booting 3.x kernel
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Yeah I know I've read literally every post here on this thread haha.. I just didn't think browsing wouldn't work so right now it sucks. But I sure as hell do appreciate your work! No doubt about it!

And yes he did get a working 3.x kernal working.
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
Awesome news..i new from the start that you probable only one who can do it.
[Samsung Galaxy Player 4.0, 5.0] heat361:
Did you upload your source maybe I will try to build cwm into your kernel.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
His source is here:

https://github.com/JackpotClavin/3.0-Kernel-Galaxy-Player-US
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
To update: root seems to kinda work. I can remount / but not /system, so I can't really test other apps... do you have an idea why? It fails saying it's read only, even as root, and after doing blockdev --setrw.

From looking at logcat, the internal sd fails to mount because checking fails, because fsck_msdos thinks the vold device it has a sector size of 0, and gets killed because of divide-by-0 in libc. However, a fsck_msdos on the actual mmcblk works fine. I hope that helps fix it.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
I'm sure the internal SD isn't that far away. I can't for the life of me figure out where the external SD code is and change it. I tried to get the sound working but the device still isn't identifying our sound card. I'm using the exact same files as the 2.6.35.7 kernel and it builds fine with a few minor changes but the device still won't list the sound card as an available device for some odd reason

Edit: Just got it so the sound card is recognized, but I'm getting a boot loop due to the audio policy error

> getDeviceForStrategy() speaker device not found for STRATEGY_SONIFICATION
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
I ported over a CM9 build for the Vibrant to the GP 5.0 and to my amazement, the sound worked sporadically even though I hadn't done anything in terms of using our audio wrapper from our Gingerbread libraries, meaning that theoretically, this audio library from the Nexus One/Samsung Aries board could be reworked to use for Jellybean even though we have two different sound chips (they use a WM8998 chip while we use a MC1N2 chip, I completely ruled out the possibility that our audio libraries could be somewhat compatible, but it turns out they are.

Does anybody wanna lend me a hand with the kernel porting to our board? The main issues left are:

1. The battery driver does not currently work with the USB, so we either have no battery driver meaning it shows 0%, or we have a working battery driver, but we lose the ability to debug via USB; so that needs some fixing

2. We lost a ton of RAM somehow in the process of this kernel port (something like going from 324 MB to like 194 and I need to figure out what happened)

3. After that, other tweaks and minor peripheral devices (like the accelerometer and FM radio)
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
You should ask gmillz, he would be a good person to go to in terms of fixing all the misc. issues.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
I had a productive day in that I fixed those two annoying issues mentioned above. I commented out some battery code that created some conflicts with the USB so that issue is gone. Also, I had some completely obsolete and useless code from the 2.6.35.7 kernel that reserved almost half our available RAM for pretty much nothing, so once I removed that, we went from 192MB of RAM free to now around 385MB free.

For anybody who tested out the CM10 super alpha from before, the fact that our available RAM was so low caused background programs to constantly be killed and restarted as they became the foreground application, which made the device perform super sluggish and crappy at multitasking; but has been rectified so background processes are no longer killed due to the lack of RAM. Sound is kind of iffy but needs to be reworked so 100% (it only works around 30% of the time right now).

I just pushed that source to the repository, but we are in need of a functioning external sdcard (the node is missing) and the reboot function does not currently work, only the poweroff works. I'm not gonna be around for the next couple days so if anybody wants to take a shot at it and gets it working, shoot me a pull request and I'll happily add it to the repository
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
Can you compile it? I don't even have an external SD card so I could benefit from the fixes a lot. Also, thanks for your work :)
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Compile what?
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
Da kernel, oh wait but nevermind.