yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] oisis:
I'm working on it now. Have to fix convert_to_mtd.sh script. Almost done, now you will not lose /efs partition. I need more time, testing is taking a lot of time, have to flash stock ROM then try to install CWM installable pkg with ICS. I tested this steps:

1. Kernel installation - OK

2. Backup partitions - OK

3. Reboot to recovery - OK

4. Convert to mtd - OK

5. System installation - have to check

6. BT MAC address conversion - TODO but should be easy

7. Reboot to ICS - not working - TODO
[Samsung Galaxy Player 4.0, 5.0] terrence1019:
Awesome! You're making good progress :good:
[Samsung Galaxy Player 4.0, 5.0] S_m_O_k:
oisis

You ported CWM6 kernel 3.x?
[Samsung Galaxy Player 4.0, 5.0] oisis:
No, CWM6 will try, can start it up but i have still some errors. Will not port kernel 3 for now, maybe later.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Well since it's been awhile (since i'm waiting on Oisis to help me fix HW acceleration by patching up the kernel), I though I would give you a status update. Oisis has been working on fixing the /efs folder so that you don't lose it, and I am happily running a gl-enabled build. It crashes on some UI actions, and browser doesn't work, but it's a LOT more usable than the last time we tried, but I think we need newer drivers before it will work 100%. JB has also been a topic of discussion, and we have partially decided to focus on getting JB booting on the side, and then working on it full-time when it boots. Oisis and zaclimon, please add anything that I forgot to add, as it has been a LONG time since I have looked at this (unfortunately, with oisis waiting for a player and school, this has taken a back seat).
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Also once we get a 3.0 kernel, we should be able to start implementing more things

Sent From My YP-G1 running ICS build 3.5
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
I'm assuming correct?

Sent From My YP-G1 running ICS build 3.5
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
http://www.verizonwireless.com/b2c/...t&action=viewPhoneDetail&selectedPhoneId=5949

this is a smasung android 4.0 phone with a 3.2 megapixel auto focus camera. if the camera is the same one that is in the galaxy player 4.0 couldn't we just use its camera driver?
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
We may be able to use it, but the chance that it has the same camera is not very high, if I had to guess, depending on when the phone was released.

I will look at the source this weekend and see if I can patch anything more for you guys, as oisis and zaclimon have gone completely quiet the last few days. Hopefully though, Oisis is working on fixing the mtd conversion script, and/or hw acceleration, although I believe he wants to iron out all the small, annoying bugs first before focusing on the larger ones,which may be the way to do it to avoid really odd errors later on.
[Samsung Galaxy Player 4.0, 5.0] oisis:
Yes, i'm still alive and still working. Was ill this week and didn't work was going slower. With camera we can have problem because sensors, even if you see camera 3,2mp this camera can have different sensors. So we will take care about it later. I want to finish installation process. Want to have zip pkg and install it without any strange steps.

EDIT:

Funny thing :) i brick my player hahah. I'm waiting for ordered JIG and i hope it will help if not will have to order JTAG. Will fix device in next week so few days brake :(. Check JTAG is really interesting tool you can unbrick even after hard brick.
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
or you can try the inbrickable ressurector
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
How did you do that. I thought these devices were practically unbrickable

Sent From My YP-G1 running ICS build 3.5
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
The only way to fully brick it, is to completly change the bootloader which is maybe what he did. (wrong partition flash)
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Yeah, well if you truly bricked it, a jig probably won't work, as if the bootloader's borked it's borked, as far as I know (at least I don't see how a jig would help in that condition). I suppose it could help though, depending on your type of brick.

Well if that's what happened he would need the JTAG, right? I'm pretty sure that DL mode is built into the bootloader...
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
it's built into the 2nd bootloader I think. Maybe he wrecked his first stage bootloader.
[Samsung Galaxy Player 4.0, 5.0] the playa!:
What will be in the next release of the ROM?

The next release is much slower then I expected.
[Samsung Galaxy Player 4.0, 5.0] soulshinobu:
The sooner oisis gets his device unbricked, the sooner they can finish the next update.

Sent from my SPH-D710
[Samsung Galaxy Player 4.0, 5.0] the playa!:
i see....
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
So an update on Bluetooth (which is the only issue we have left outside of h/w acceleration): I was fiddling around with it, trying to fix it the other night, and from what I saw in the log cat, the framework works just fine, but the BT address wasn't converted properly when flashing to mtd, and as such the device using that Mac is not found. Should t be too hard to fix, especially since Oisis is in the process of fixing the mtd script, so I guess we just...wait (?) until he finishes. As for the camera, I firmly believe after looking at log cat and the source that the PREVIEW is crashing, not the actual camera itself, due to all the GL oddness and lack of how acceleration we have. This should be fixed as soon as we get the newer drivers working, and iron out the last few graphical issues.
[Samsung Galaxy Player 4.0, 5.0] oisis:
Could you post logcat and dmesg from bluetooth test? Thanks.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Well, I am attampting to finally boot with the newer drivers, and this is the dmesg I get when it attempts to initialize the graphic H/W:

[drm:drm_mode_getfb] *ERROR* invalid framebuffer id

This is the logcat:

E/IMGSRV ( 2448): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).

E/IMGSRV ( 2448): :0: PVRSRVEnumerateDevices: BridgeCall failed

E/IMGSRV ( 2448): :0: PVRSRVConnect: Unable to enumerate devices.

E/FramebufferNativeWindow( 2448): couldn't open framebuffer HAL (Not a typewriter)

E/FramebufferNativeWindow( 2448): couldn't open gralloc HAL (Not a typewriter)

E/SurfaceFlinger( 2448): Display subsystem failed to initialize. check logs. exiting...
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Hey I know the work is going slowly these days but oisis and I were trying to get CWM6 running on our devices, and also we're changing the way the ramdisk is made to the device tree made (like it should be) so all these things are a bit long to do. The great news though is that we can run CWM6 (compiling from CM source) :D. We have to change some usb drivers and I think we should be able to get native USB mounting soon. :) Don't forget, next step after getting CWM6 done, it's HW acceleration so stay tuned!!
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Fantastic. Glad to hear that. Keep up the good work

Sent From My YP-G1 running ICS build 3.5
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Hey guys, glad to see progress being made! I was just wondering if oasis ever got his device unbricked? Also, I have been holding back from flashing just because I like my gb setup and stability, but if you ever need another tester, just pm me, and I'll be glad to help!

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] oisis:
Not yet, still waiting for ordered jig, polish mail is so god damn slow.

EDIT:

oisis not oasis, do not like oasis and do not like britpop :).
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Actually, good news on the H/W front. me and zaclimon worked for white awhile this weekend on updating to the newer drivers (oisis, ask zsclimon for dmesg if you're curious), and we only have one issue left before it *should* boot, but that's not a certainty by far. We're closer than you think! Once we get he acceleration working, I think the next focus should be getting a 3.x kernel booting, I can handle maintaining/fixing the ROM once we get hw (which I have to have a kernel dev to help me on) working. Only thing that will be broken for a long time will probably be the camera, everything else I can fix, time permitting.
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
I've been lurking like crazy to see how this plays out. I love my jig so much because of all the times I've been able to recover my device with it. I hope you have the same luck.

lol, good developer and good humor.
[Samsung Galaxy Player 4.0, 5.0] oisis:
JIG didn't help me, it is time for JTAG, will have to pay for that around 25$ :( but have to do it. Next time will be more careful with kernel.
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Just how bad are you bricked? Can you even power on the device? Hope that you can get the thing working again!

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] oisis:
No, cannot power it on, is totally dead. Black screen, no reaction.
[Samsung Galaxy Player 4.0, 5.0] the playa!:
TRY the heimdall "detect device and then close pc screen" thing... worked for my player when it was bricked.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Well, this is completely random, but I just applied for RD status. Hopefully they consider my work to be adequate, and accept, even though I have only been active since may/june.

Oisis, assuming you tried all the button combos, have you tried plugging it into the computer, making your own jig, etc.? I made my own out of a bad USB cable and some spare resistors I had lying around, and it still services as my only way to access download mode to this day!
[Samsung Galaxy Player 4.0, 5.0] Ben456:
The unbrickable resurector worked for me when I had flashed a wrong bootloaders. The result of the flash was the same: The screen didn't even turn on. The resurector put it into download mode (but nothing appeared on the screen of the player) & I was able to flash with heimdall. I don't know how you can mess up this device so much for it to need JTAG (Everything on mine was screwed up, including boot, param & sbl) I remember it not working on the first try tho.

Since I have a US (don't know if it is your case) player and nobody has its bootloaders, the international one works fine (exept for the button combo to boot into recovery/download)

Good luck!
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Well I have anb update for you guys, so you don't think that we're completely dead.

First off, the next version will have a LOT fixed, including GL, so stay tuned, as far in the future as that may be.

GL/HW: We are *this* close to finishing it. Expect a working version soon, if all goes well.

Bluetooth: Fixing this, and it should be in the next version. To fix it though, you will need to go back to stock, restore /EFS from backup, and run through the MTD conversion process all over again.

Other than that (camera will either take an ETERNITY to fix, or will work as soon as we fix gl, just a tossup), we really don't have any noticeable USER issues (still some behind-the-scenes junk we need to patch up), so next version should be completely flash-ready!
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
First off sounds good can't wait

With gl, if seems to be a reoccurring theme. Hoping all does go well.

Bluetooth presents another nightmare for giving instructions on how to do that. Can't wait!!! :)

Sent From My YP-G1 running ICS build 3.5
[Samsung Galaxy Player 4.0, 5.0] error01671:
Is the market issue will be fixed in next version?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Camera will be nearly impossible if we don't have the source of it, (the libcamera) we would need to ask either samsung the libcamera or, cook one up ourselves. :confused: We can try to take a device with the same camera but even then, I don't know if it would work.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
That's what I meant, but there's a possibility that our camera is soft-restricted, and is able to use the aries files, however unlikely it is.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Nope it's not even soft-restricted. The camera module on the YP-G1 is different from all the aries series. We would need to take a device with the same module which is the sony isx005.

EDIT: Alleluia!! the galaxy tab have the same sensors as us. I think it may be our camera savior! :D
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
Sorry to intrude in your thread, but do the Player 4.0 and 5.0 share the same camera? They both appear to be the same, but the 5.0 has a flash. I've tried using some camera libs from the galaxy tab on my 5.0, but the camera still didn't work. If you do manage to get some parts of the camera to work, please could you let me know?

Thanks
[Samsung Galaxy Player 4.0, 5.0] oisis:
If you needs help just send me dmesg and logcat from camera test.

We will need to do in this way, copy blobs from stock ROM, add HAL wrapper maybe from i9000, take and rebuild media_profiles.xml from stock ROM and build all together. We did it like that in i9001 and camera started to work somehow but we needs coder to finish job. Now is working.

My device is dead for now. JIG didn't help me so need JTAG. Found some places and will go there to fix device. Probably in this week. So now work is going slower but I'm trying to do my best. Will try to help hanthsolo with new version of ICS for YP-G1.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I would need to check into the 5.0's kernel source. Maybe. :) I'll tell you if it's possible.

EDIT: it's seems that it don't uses the same. The 5.0 uses the samsung's S5K5CCGX.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Did you try the unbrickable resurrecter.

Sent From My YP-G1 running ICS build 3.5
[Samsung Galaxy Player 4.0, 5.0] oisis:
It is jig, right? Didn't help.
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
Ah that sucks. I'll have a look around for devices with the same camera.

I can't get a logcat or dmesg at the moment, but I remember gmillz and I got the camera to open, but then the device would reboot. I remember the logcat said something like "Failed to dequeue gralloc buffer"

Are you sure the 5.0 uses a S5K5CCGX? I just had a look at the kernel source and there seems to be a lot of references to a S5PC11X camera driver
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
I thought it is a program but I could be wrong

Sent From My YP-G1 running ICS build 3.5
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Like this, maybe it would need for the preview to have HW activated. (Gralloc is related to GPU)

---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------

The unbrickable resurrector is a program indeed but his computer couldn't recognize his device so it was useless.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Teaser for you guys (since I like keeping users updated :))

All 3 of us are currently in a Gtalk chat, and...let's just say that we're getting a lot done. Expect at least SOME news by tomorrow!
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
sweet can't wait to hear what's planned. Keep up the good work. Let me know what I can do to help.

Ah OK I don't know that. Makes more sense now.

Sent From My YP-G1 running ICS build 3.5
[Samsung Galaxy Player 4.0, 5.0] the playa!:
TEASERS!

I like teasers! :D
[Samsung Galaxy Player 4.0, 5.0] oisis:
What does it means? My dict do not know this world :).

My YP-G1 is totaly bricked, i have tried JIG, resurector and nothing helped. I'm going today to Samsung service to unbrick device. Wondering how much $$ they will want for that :). If it is possible to unbrick it then should have back device tomorrow or day after tomorrow if not will have to buy another one :(. But i'm going to still work on this device.
[Samsung Galaxy Player 4.0, 5.0] crancpiti:
while you're at samsung tell them to give you the source if they don't support our device anymore :D
[Samsung Galaxy Player 4.0, 5.0] theraf:
we already have the source it's on the samsung opensource website
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
The sources are already on the samsung's opensource website (Well we would need some sources like libcamera). If you want our kernel source for whatever reasons, you can find it here:

https://github.com/teamsupernovaSGP

The device tree isn't quite updated yet because we're modifying it for the big release. :D
[Samsung Galaxy Player 4.0, 5.0] the playa!:
handthesolo said that he will give us some news on the progress, but unfortunately he didn't. :(
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Here's what about for now. CWM6 is *finished* (we need to resolve 1 more error and we're done I hope) then we will attack directly the HW accel. When these are finished we will go through beta testing. (one for CWM6 soon and one for HW later). When we will judge that all is stable for a daily use, then we will release it.
[Samsung Galaxy Player 4.0, 5.0] oisis:
Good news, i will have back my device in next week. I will have to pay a lot but device should works.
[Samsung Galaxy Player 4.0, 5.0] the playa!:
nice nice....
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Dang people these days... never happy about anything. Don't worry though, we will release a version with openGL acc activated for those who can't fight with the massive lags in the animations. (like me :p)
[Samsung Galaxy Player 4.0, 5.0] werfu:
Hey guys, I just wanted to say that I still want to help, I simply had a lot on my hand lately. I took time to reinstall my computer and clean with Windows 8 and I left enough space to install Ubuntu this time, so I should be able to have a working dev environment and finally start working on that kernel!

I'll install Ubuntu 12.10 tonight and I'll let you know how the build is going. Hope this time it works first time!

I'm also running the build 3.5 and having small issues like anyone. I installed the gapps from cyanogend and Google Play is broken. Also I'd trying to get back both SD to work as it was before (/sdcard and /sdcard/external_sd) so the music player would work. EDIT: I managed to fix the Google Play by extracting the system directory in the zip directly. I have yet to test application installation though. I also fixed the SDs. The external is mount on /mnt/emmc (reversed), but appolo seems to be able to find my music there. and I also don't know why ES Explorer can't show /mnt/emmc. Speaking of Appolo, it keeps crashing. About the capacitive Home button on the US version, does it require change to the kernel or a simple config edit would work?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Yeah well we're updating the sources right now, as for the kernel, I commited the latest changes 2 days ago concerning the newest usb gadget drivers for the use of usb.rc scripts. Right now I didin't have much time this week to finish CWM6 but I will work on it this weekend.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Well, to state what I planned to say a few days ago, we've been reworking the kernel to get rid of a LOT of behind the scenes bugs, and to get GL working. At the moment, I would say that we're 80-95% of the way there, as we just discovered that we were using some incorrect paths. No promises, but expect big things over fall break folks!
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Here's some news guys, (sorry to announce it before you han XD) the GL issue is now fixed :D and I can say, it's blazing fast...

EDIT: Suprising thing, I got the camera working (even though it's far from being perfect lool).
[Samsung Galaxy Player 4.0, 5.0] soulshinobu:
That's great news! Sounds like this is going by sooner than I thought it would.

Sent from my SPH-D710
[Samsung Galaxy Player 4.0, 5.0] daniel644:
So FC's a bunch or something on the camera?

Keep this up and I may just make this my daily driver on the next build.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Well first, there's a grey bar on the middle and a black bar on the low side, (this is when in landscape) however there's a side with 5 little squares where I can see actually something but it's in black and white.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
This is probably due to the fact that we're using the aries driver (I believe). Our camera is similar enough to use it, but we need to find the correct drivers first (like you said). I may just be barking up the wrong tree, but that's what I think is the issue.

Zaclimon has his build up and working, but isn't going to release it (to anyone) until he irons out the last few bugs (wifi, /efs, etc.), so I would expect it in a few hours (maybe from me, because he said he'll push his changes first).

I would like to say that this project isn't my main focus anymore, hence my greatly lowered amount of participation the last few weeks. I've moved on to other things, and with school, I don't really have time for it anymore. I will still be helping as much as I possibly can, but I think we need to institue a bug tracker, to help all of us sort out the issues we have. As of right now, we have a few major issues documented, but there are countless smaller ones that we still need to sort out (mostly in the kernel, as I have been trying to keep the rom as bug-free as possible), and without a central area to keep them documented in, our progress has been greatly hindered. We don't have the resources for gerrit (my understanding is that it needs it's own server), so what do you suggest?

Looking ahead, what would you guys like to see first: ICS completely smoothed out and bug-free for a smooth transition to JB (will take longer, but will make things easier in the long-run), or would you like us to get JB booting as fast as possible, but with far more bugs, and have both ICS and JB in semi-complete forms? The second option would probably split our team, so that some of us maintain ICS, while the others work on JB.
[Samsung Galaxy Player 4.0, 5.0] crancpiti:
Definitely the first option ^^
[Samsung Galaxy Player 4.0, 5.0] zamuz27:
Yes, definitely smooth ICS first.
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
I concur, ICS.

Also, in as much as I will enjoy ICS on my device I'd like to say that watching this process has been even better. So many people have contributed to this community and Team SuperNova has obviously taken things to the next level. My absolute dream would be for Samsung to release a 2nd iteration of the 4.0 so that the hardware...can keep up with the community. ;)
[Samsung Galaxy Player 4.0, 5.0] the playa!:
Smooth ICS first, and so that means the next build will be released today?
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Possibly, zaclimon still is cleaning stuff up, and i'm trying a new kernel now. At the latest tomorrow, and it WILL have GL 100% fixed and enabled, along with a TON of behind the scenes mods and fixes to improve usability, so this will be the first release that will show you what ICS is capable of on our device.
[Samsung Galaxy Player 4.0, 5.0] the playa!:
what is GL though? :rolleyes:

but it wont have hw acceleration though right?
[Samsung Galaxy Player 4.0, 5.0] oisis:
HW acceleration should works now because we have new drivers in kernel and new drivers in ICS. Zaclimon tested and it works ok. So next release will be almost full working. Bigest bugs gone but still we have to fix some small issues like SDcard usb mounting, camera etc.
[Samsung Galaxy Player 4.0, 5.0] the playa!:
ok. this is it. the perfect ROM for me to download. Chrome works now right?

And is there an easier way to install the kernel/ROM? Like do you still need the computer to flash the CM9 kernel/ROM?
[Samsung Galaxy Player 4.0, 5.0] oisis:
Chrome should works ok. I will keep working on install process when will get back my device, a lot is done but need some time to resolve last issues.
[Samsung Galaxy Player 4.0, 5.0] daniel644:
So are we good on the main issues with this new build?

1. Market Fix, so we don't have to do the terminal thing after every boot

2. External SD not mounting without modified vold.fstab

3. Deep Sleep?

4. Root, or will we still need to re-root after installing?

5. Install process?