yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] sga999:
Sorry to be dense, but I'd like to be sure I'm understanding. You're saying everyone who installs the Nebula or Linaro rom will have the problem that I had, i.e. when they try to select anything on the CWM menu, they will not have the use of the power button, because this is a problem in all of those kernels. So everyone will have to use this "feature" of cursoring up to the top of the menu 3 times so that they'll be able to use the back button for select. If this is true, I would have thought someone would have mentioned it here in this thread (or in the Nebula one). I think you must be saying something else, so I think I'm misunderstanding all of this.
[Samsung Galaxy Player 4.0, 5.0] daniel644:
Oh no, the power button is the select button in CWM in all the kernels, because the home button on US players doesn't currently work, I don't know why your power button as select in CWM isn't working.

I think that kernel theraf posted may be your issue, just use the method I posted because the power menu should be select in CWM.

Edit: I just tested the boot.img from theraf's post and my home button as select worked fine in it (also much easier then the long method), so now I need to ask you the condition of your EFS, if your buyer_code.dat is missing or set to the wrong region (which could happen if you've had to rebuild your efs from scratch because of not backing it up right) can break the home button in some CWM builds.

Han and Zac, could we use the CWM recovery 5.0.x that is in that kernel from theraf (for quick jumps between builds, post #107 on page 11 of this thread) instead of the one we use now since it doesn't loop like our recovery and supports the filesystem we need or is there something else that I don't understand blocking us?
[Samsung Galaxy Player 4.0, 5.0] theraf:
the kernel i posted is and aosp gingerbread kernel for the galaxy player...it's what this new kernel is based on
[Samsung Galaxy Player 4.0, 5.0] sga999:
Daniel644, thanks very much. I confused everything by saying " You're saying everyone who installs the Nebula or Linaro rom will have the problem that I had, i.e. when they try to select anything on the CWM menu, they will not have the use of the power button, because this is a problem in all of those kernels". I meant to say "use of the HOME button". Of course, I have been unable to use either the home or the power button in CWM....and that's why the "cursor up 3 times" method worked for me.

Okay, here goes about my efs! I do have an efs folder in the root, but it's not "good". It has 3 files, imei, lost+found, and keystringlock.dat. The first and last of those have a date of 11/23, so they were there before I flashed this new rom a couple of days ago. The middle one has a date of yesterday.

Now for the part that I may get scolded for! I do have an efs folder on my EXTERNAL sd card. I vaguely remember creating it shortly after getting my player and reading these forums (I was going to put on various other kernels, etc. from zac, han, and others). But I took the easy way out and just copied the efs folder there...I think I read about various methods, and some did say that it could just be copied.

Without a good efs, can you tell me what symptoms I should be seeing? Once I'm out of CWM and up and running, my power button works fine (but not the home button, of course), and I don't seem to have other issues. I guess I thought the results of not having the correct efs were pretty disastrous. Maybe it's much worse for phones than it is for our "tablet".

Okay, now for restoring the efs. Can I just copy that efs folder from the external sd back to the root of the internal sd? Or should I create some other form of backup of the one on the external sd card first, and then restore that?

I would guess that since I just copied it originally, rather than following the more elaborate instructions, the permissions and other stuff may be incorrect. Can you tell me what the permissions should be? Is it the same for all files in the efs folder?

My buyer_code.dat in that copy on the external sd has XAA. I tried looking that up, and it seems that may be correct for the US. But obviously, without any efs folder visible in the root of the sd card, CWM was not seeing that code! I think you're saying that the right efs will allow me to use the home button during CWM (because of running Theraf's kernel).

So...I hope you can let me know about the permissions and whether I can just copy the efs to the root of the sdcard. Next time, I will follow the more explicit instructions on backup/restore of efs rather than just copying.

EDIT: I forgot to ask. What causes the efs to be corrupted or changed? Does it occur any time we put on different kernels or roms on our player? Or is it something unusual that occurs during some installs and not others?

EDIT2: I see mentions of restoring nv_data.bin to the efs folder. I don't see that in my copy of efs on the external sd. Does that mean my copy isn't good?
[Samsung Galaxy Player 4.0, 5.0] daniel644:
Well your not gonna see much if any issues in the CM9 based ROM, but that is because of the device id hack in use, your problems will arise when/if you restore to stock, because with the efs wiped like that in stock ROM your lockscreen and power menu will be missing and other possible unseen issues.

XAA is the code for a US player with the capacitive home button, so if that is what you have then you are good there.

It's not really a copy and paste type deal, I mean for now you could do that as a "dirty" method and it might fix your home button ONLY WHEN IN THERAFS AOSP GB KERNEL, but to fix it right is a long process.

this is what I HAD to do to restore a "rebuilt" EFS (special thanks to user GalaxySWifi4 for the method, and any that helped him figure it out):

To fix it right you need to follow Zaclimons recovery/restore to stock thread and use heimdall to flash the listed file, but you'll need to flash the file buried somewhere in that thread called blank_efs.img (otherwise stock recovery will show a mount error on EFS) to the EFS section in heimdall

Once you reboot into stock GB download and use a file manager with root access to copy (keep a copy where you have it as a backup) the EFS you have as a "backup" back to the right spot in the root of the player.

Now flash a kernel with CWM like Terrasilent

Now using terrasilent flash the ROM Dream Ultra Rls. 2.x, this uses Aroma installer, once it boots see if you have a working lockscreen and power menu (if you do you can move on to the next flash)

If your power menu and lockscreen are still missing reboot into CWM recovery and wipe data/factory reset, wipe cache and wipe dalvick, then reboot into Dream Ultra rom again (will probably be in Russian language) to confirm lockscreen and power menu is there.

With that confirmed you can now flash the stock but rooted rom .tar package from this thread http://xdaforums.com/showthread.php?t=1512331& using Odin.

after flashing to stock confirm working lockscreen and power menu, If they are you are now ready to follow Klin1344's backup method for creating an EFS.rfs backup, that will be used any time you use Heimdall to go back to GB from now on, thereby avoiding the need to jump thru all these flashing hoops to fix it.

I know this sounds like a LOT but let it be a LESSON to you on why to FOLLOW INSTRUCTIONS, I lost mine on CM7 before they told us we needed to back it up specifically or how to do it for that matter.

You WILL need a properly restore EFS in the future for any hope of a working Home button in the ROM when/if the issue is solved.

edit: also the reason you need to back it up for CM based Roms and not all the GB ROM's is because the CM roms repartition the player to MTD and you need the backup to restore it where stock GB based roms never touch it.
[Samsung Galaxy Player 4.0, 5.0] sga999:
Daniel, I'm not ready to go back to stock right now, but I'm saving your info on how you recreated your efs "for the future". Thanks very much.

But I might want to do the "dirty" way and just copy my external copy to the sdcard, just for the home button issue in cwm.

1. Can you tell me what permissions the efs files have? I'm hoping there aren't different permissions for different files. Oh dear, the 3 files in the "bad" efs folder all seem to have different permissions, so it might be difficult for you to tell me about all the file permissions?

2. Does it matter that I don't see nv_data.bin in my efs folder that I copied?

3. If I do the "dirty" way and just copy to internal, can it possibly make things worse for me than they already are? I mean, I'm not really in a terrible situation right now, so I won't try the copy if you think it might make things worse.

4. Do you know why the efs can be lost or corrupted?

My buyer_code.dat does have XAA, but it only exists in the efs that I copied to the external sd. So could that alone be the reason for no home button during cwm with theraf's kernel? Maybe for now, I should just try copying that buyer_code.dat into the "bad" efs folder in the internal sd. But again, I'd need to know the permissions for that file.

Thanks for your help!
[Samsung Galaxy Player 4.0, 5.0] daniel644:
just copy the buyer code for the moment, don't really know on the permissions, after going the long method I described I never set any permissions, I use ES File Explorer to move the folder to root on the player, I also don't have a nv_data.bin in mine so I can't comment there. I have rw-, rw-, rw- as the permissions on my buyer code but like I said I never specifically set them.
[Samsung Galaxy Player 4.0, 5.0] PairOfSocks:
Hey everyone, I've been on the first linaro build han put on the Nebula thread awhile back, and loving it. Yet there are some glitches that I wanted to ask are fixed in the newer version.

I mentioned this on the other thread and dan said he had the same thing, it's where some pictures don't show up, instead they are just a black image. Mainly noticed in poweramp, facebook, etc.

Also, when the battery gets low (red), my softkeys and notifications bar seem to freak out and start to disappear. Sometimes when this happens the volume also gets VERY loud, and will come out the speakers even though I have headphones in. And han, thanks for all the work you've done for us.

EDIT: **wanted to ask IF they were fixed, sorry
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
I will attest to the whole speaker issue but for me it doesn't matter if the battery is low or not. But the weird part is, is that it just started happening. Don't know if there is a way to fix that.

Edit: han, what kernel should I be using for the PA rom. Right now I am using the one from nebula but I have a feeling that I should be using a different one. Also. Was the logcat I gave you of any use as to fixing chrome?

Sent From My YP-G1 running ParanoidAndroid beta 2
[Samsung Galaxy Player 4.0, 5.0] theraf:
you should be using the one in the latest linaro build
[Samsung Galaxy Player 4.0, 5.0] daniel644:
ALWAYS USE THE BOOT.IMG from the ROM you are running, to get a copy of it go on your PC open the ROM zip file and "drag" it to your desktop, and now you have a copy.
[Samsung Galaxy Player 4.0, 5.0] ShawnZ248:
My TOUCH SOUNDS on this rom under settings-sounds are not working for some reason? Is it just my device or is happening with everyone else too?
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
that and my lock sounds
[Samsung Galaxy Player 4.0, 5.0] PairOfSocks:
What build were you running when you had those speaker problems goldflame?
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
I was and still are running the PARANOIDANDROID.

Sent From My YP-G1 running ParanoidAndroid beta 2
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
For the kernel compatibility questions everyone's been asking, you can use ANY kernel released for ICS post-fixing the GL issue, and it will work with any rom. As such, I would recommend using the boot.img in the latest release, as that's the fastest kernel we currently have released at the moment. If you have no idea what i'm talking about, or never used heimdall before, don't worry about this, just stick with your current kernel.

Zaclimon, have you heard back from Oisis? I almost feel like at this point he's ripped us off for a $120 device...

Moving forward, what do you guys want to see most from us? We can probably adapt the 5.0's JB sources pretty quickly and painlessly to work on our devices, although we would need their explicit permission, and it wouldn't be as clean of a port as it would be if we built it ourselves (although a lot faster). Also, this device isn't really a challenge to develop for anymore. We have everything working in CM9 except for the camera and bluetooth, JB probably won't see much of an improvement on our device, and we already have all the major rom ports we need, thanks to theraf. That being said, if I get a smartphone for christmas (which I might be lucky enough to get), I will probably drop DEVELOPMENT support for this device, meaning that I will probably sell it. I'll still maintain my threads, provide support for budding devs and contribute in any technical ways I can. It's been fun supporting this community and i've learned everything I know form this device, but for me it might be time to move on, to newer and more relevant devices.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
First if all, nice to hear from you again.

Second, no one has heard from oisis in a LONG time.

As for JB if you could port it from the 5.0 with permission if course, that would be awesome. If not then don't worry about it.

It you can't get it, do you think it would be possible to try to make the version that we have a little more stable than this.

As for dropping development, I wish you the best of luck with your smartphone, if you get it.

Sent From My YP-G1 running ParanoidAndroid beta 2
[Samsung Galaxy Player 4.0, 5.0] ti-pich:
It could be nice to start the 3.x kernel. We were suppose to start it but I haven't heard back from zaclimon. I'm ready to help with anything I can.

Edit: I'm still working a bit on the camera but it's a real pain in the ass to find anything as there is no doc at all with the libraries. I keep trying but I can't promise anything.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Thanks for trying with the camera at least. As for the 3.x kernel, out if curiosity what would it provide over this kernel that we already have?

Sent From My YP-G1 running ParanoidAndroid beta 2
[Samsung Galaxy Player 4.0, 5.0] ti-pich:
Probably more stability and performance. It would also be more future proof so once it is done right it can be used for a long time without modification.
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Merry Christmas everybody! (okay merry Christmas eve). Han, I completely understand if you drop development when/if you get a smartphone. One small thing I would like to see though is the return of the 1.2ghz cpu clock speed. I felt comfortable using that, but 1.5ghz is surely pushing it to far and is going to degrade the life of our cpu. A way to choose between 1.2 and 1.5ghz would be best yet.

Sent from my YP-G1 running LinromV2
[Samsung Galaxy Player 4.0, 5.0] PairOfSocks:
I may be the only one here, but I think I'd like a very polished ics before you guys move to jelly bean. If you guys do move to jb, I'll still support you 100%.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Alright han let's do it, porting JB to our devices!!!!!!! (I do have a semi-working build tree, I'm stuck at the CM bootlogo.)

Also from a side note, Oisis says that his device is mostly dead...
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Alright, nice! Gtalk me, and we can discuss it from there.

If you have it getting to the CM bootlogo, then we should have it up and running a lot faster than I thought!
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
SWEET!!!!!! I'm already thanking you for trying. If you get it working all be even happier.

Edit: out of curiousity reporting this from the 5 or is this straight from the source?

Sent From My YP-G1 running ParanoidAndroid beta 2
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I don't think we can get it working by tomorrow but I can try by the new year (it would be though because i'm going on vacation wednesday soo it will be here when it will be here loool).

Also it is built straight from the source with some cherry picks from other device tree.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Was not expecting it by tomorrow. And don't worry about time. I would rather it be good vs quick and sloppy

Sent From My YP-G1 running ParanoidAndroid beta 2
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Merry Christmas everyone

Sent From My YP-G1 running ParanoidAndroid beta 2
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Merry Christmas to you too and to everyone! :p
[Samsung Galaxy Player 4.0, 5.0] Sultanxda:
Hey Han, where can I find your kernel source? Your Linaro-optimized kernel isn't on TeamSupernovaSGP's GitHub, nor is it on yours :confused:
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
It's on supernova's source. It's on the linaro branch.
[Samsung Galaxy Player 4.0, 5.0] Sultanxda:
Wow, I completely missed that :silly:. Thanks.
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Hey all, could you guys have a look at the issue I posted about here? http://xdaforums.com/showthread.php?t=2069857

I am not sure if this is only for me, or a bug with this rom. Thanks!

Sent from my YP-G1 running LinromV2
[Samsung Galaxy Player 4.0, 5.0] daniel644:
Why go through ALL that trouble just use Talkatone: https://play.google.com/store/apps/...1bGwsMSwxLDMsImNvbS50YWxrYXRvbmUuYW5kcm9pZCJd virtually zero setup if you already have all the stuff configured for google to direct calls.
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Because; 1. I don't like having to have a third party app constantly running and 2. Talkatone is ugly.

Sent from my YP-G1 running LinromV2
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
just some possible helpful information to help with the cameras.

1. the front camera, while the rendering is worse than the back camera, if you take a picture it saves it the same way you see it. it is not gray just a bad picture.

2. as for the rear camera, if you take a picture with that camera, while it will be grey, if you look at the top left corner, there is a small bar that is actually part of the picture you took. if you are having trouble finding it, take a picture of something dark and something light. then put them side by side and you should see the difference.

if you knew this info already then ok, i thought i would throw that out there anyway
[Samsung Galaxy Player 4.0, 5.0] ti-pich:
Yes I already knew this and also the back camera work but only for panoramic picture. This is really weird...
[Samsung Galaxy Player 4.0, 5.0] alex1301:
guys, i have a problem. when i flash a kernel, my phone reboots into recovery and i can not get out of it. i tried every boot.img, kernel and tutorial, but everytime the same result. can somebody help me please?
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
go into download and flash terra silent and then let it boot into recovery

ignore the errors, go into download again and flash the boot.img

---------- Post added at 02:45 PM ---------- Previous post was at 02:42 PM ----------

i actually cant go into panorama mode without a fc happening to the camera app

im assuming there is also no camera that is close to ours. maybe the galaxy s drivers would work
[Samsung Galaxy Player 4.0, 5.0] alex1301:
thanks man, but when i reboot into recovery it is stuck in the recovery again.
[Samsung Galaxy Player 4.0, 5.0] ti-pich:
This is weird. Also for the driver, I think that we are already using the galaxy s one. I think I found a little thing, when in video recording mode, if you change the 720p to 480p then the image get like the one on the picture instead of like the front camera, so maybe the problem is the camera resolution. Maybe lowering the image size again would help but there would still be the picture taking issue. I don't know why it's taking a grey picture but I've tried to take a picture in 3.0mp instead of 5mp and the upper left corner become even more visible, you can see some of the picture. I keep searching and logging some test.

Edit: I might have reduced the source of problem to 2. With what I have found it could be something linked to v4l2, wich I don't really know what it is or it could be the initialison of the function that initiate the picture taking procedure wich would be used with wrong parameters. If someone know what v4l2 is it would be really nice to explain it to me, I think it is linked to the picture encoding but I'm not sure.
[Samsung Galaxy Player 4.0, 5.0] daniel644:
ANYTIME you boot into recovery you WILL HAVE TO flash terrasilent, reboot download then reflash the proper boot.img for the ROM you are running (basically those last few steps in my video), ONCE YOU GET UP AND RUNNING DO NOT BOOT INTO RECOVERY ANYMORE, anytime you go into recovery you will get stuck in the recovery loop.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Intro to V4L2

this may help you out a bit

when i go into recording mode, i can start recording video but it cant stop/save it. app just freezes but the camera stays live.
[Samsung Galaxy Player 4.0, 5.0] ti-pich:
Thanks, I'll take a look at this tomorow and for the video I've got the same thing, won't stop and then fc. The file get created but the size of it is 0 octet. I try to get a log of this tomorow to see where it stop.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Hey in the next 12 hours, expect logs from my camera.

Edit: attached are the logs

Sent From My YP-G1 running ParanoidAndroid beta 2
[Samsung Galaxy Player 4.0, 5.0] ti-pich:
Thanks for the log, I just took a look at the front camera and there seems to be an error with the v4l2 drivers on this one too, it don't fail like on the back camera but it return -1 (wich is not really better) but as I see it seems to be the only place where it log an error for the camera so maybe the v4l2 drivers are the problem. I keep looking at your log and searching.

Edit: If I want to test some modification do I need to recompile the rom or could I just compile the libraries and then put them on my player, because I don't know how to compile the rom and if I want to test it's going to be very long to compile, flash, test and debug every time I want to test something. Also I found where the back camera bug happen, it try to locate the picture with the gps and fail so it can't finish to take the picture. I would remove this section and test if it could at least finish to take a full picture. So if someone know how I should change those libs could you explain. Sorry for those question I don't really develop for android, I'm more a programmer.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Actually you should just be able to basically click and drag and drop them right to where you need them. If are system files and they belong in system/lib then throw them in there and then after reboot they will take effect

In essence you're basically just manually installing drivers

Sent From My YP-G1 running ParanoidAndroid beta 2
[Samsung Galaxy Player 4.0, 5.0] ti-pich:
Yes that's what I thought, but in the lib folder the file are .so and I have .cpp and .h, the .so are probably the compiled file so I need to compile them then put them in here. Also, I've tested a camera fix zip for the galaxy tab wich had similar issues(grey picture) but I haven't been able to take a picture, the preview was here but still laggy as our and when I took the picture it force closed. The front camera acted like before. But now I've got a force close and I can't open the camera apps anymore, it just stay black. Anyway, if someone could tell me how to compile those libs I would be happy, or if someone could do it for me. I have a linux machine available so there is no problem from this side.
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Hey everybody! This is a stupid question but did anyone try supermaster's bluetooth patch for the 5.0 on our cm9? I really can't remember if anyone mentioned testing it, and also can't remember if we have the same bt chip.

Sent from my YP-G1 running LinromV2