yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Yep by checking from the logcat, I think that something hasn't been merged correctly.

Envoyé depuis mon Nexus 7 avec Tapatalk
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
So I merged your FIMC changes, and kernel crashes on opening the camera app. Do you have any suggestions?
[Samsung Galaxy Player 4.0, 5.0] txordi:
Any improvements guys?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
We've generally located the problem, but haven't gotten anywhere toward fixing it.
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Well, wanna share the problem?:p
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
See logcats above. The HAL is not compatible with the FIMC drivers, which aren't compatible with the camera driver, so it's failing at multiple steps. It worked on CM10 becaused we used a stock-based kernel.
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
Is there any foreseeable hope for a fix? If not, I'm passing this thing off to my wife.

Sent from my XT862
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Well we all missing an important thing which is time. As of myself I can't really do anything until the beginning of August, I don't know for mevordel and jackpot.

Envoyé depuis mon Nexus 7 avec Tapatalk
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I have the week after next, and then school starts up again, FWIW.

Edit: and none of us have the Korean version, either.

Sent from my Galaxy Nexus
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
Actually what are you guys looking at if I wanted to help?

I only have limited knowledge in programming though.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
We need to graft the stock fimc drivers into the 3.0 kernel.

Sent from my Galaxy Nexus
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
If I ask how, would you answer that's what you guys are figuring out?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Pretty much...

Sent from my Galaxy Nexus
[Samsung Galaxy Player 4.0, 5.0] halomademeapc:
I'm retiring my Galaxy Player 5.0 and Sprint Evo 4G and succeeding them with a T-Mobile Optimus L9 and a Motorola Xoom. I'd just like to take one last time to thank all of the developers here for their work on the galaxy player. It was my first foray into the world of android, and getting to follow development for an obscure device with poor manufacturer support has been an awesome experience for me. Thanks for keeping my device exciting.

Adieu.
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
So, it seems as if we need to pick one part and focus on making the other two work with it. Which piece would be the hardest for us to change?

Also, do we have the source code for the drivers or is it compiled? What does FIMC stand for (trying to look it up, but not finding anything)?

I want to help with this project, but really have no idea where to start. The closest I've seen is to PM my home computer's SSH Key, but are all the original files on the build server as well, or will I need to snag those from the web?
[Samsung Galaxy Player 4.0, 5.0] txordi:
Oh... A bad lose...
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
By far, the most difficult part to change is the s5k5ccgx driver (https://github.com/Mevordel/android...lob/3.0Venturi/drivers/media/video/s5k5ccgx.c and https://github.com/Mevordel/android...lob/3.0Venturi/drivers/media/video/s5k5ccgx.h), as it's quite obfuscated. Therefore, it's taken directly from the 2.6 kernel. Since the camera worked in 4.1 jellybean, we know that the HAL works with the 2.6 kernel. That leaves the only changed/incompatible part the Samsung FIMC drivers (https://github.com/Mevordel/android...e/3.0Venturi/drivers/media/video/samsung/fimc), which are currently from the Aries 3.0 kernel. In general what we need to do is forward-port the 2.6 FIMC drivers to the 3.0 kernel. Probably the easiest way to do that is to diff the 2.6 Aries and Venturi drivers and manually apply those changes to the 3.0 Aries one.

We have source to the drivers (at the links above); the HAL source is in the device tree in the libcamera directory. To explain the acronym, fimc.h describes itself as a "Header file for Samsung Camera Interface (FIMC) driver."

If you install an SSH client on your computer and PM me the public key you generate, I will give you an account on my box with the full CM source where you can experiment with the kernel or HAL or whatever. Everything would be pre-downloaded.
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
OK, sent the PM with the key. I flashed CM10.1 for the first time to look at the camera situation (it's been a sticking point for me), and I'm surprised that the preview is working but that it won't take the actual photo. I did a diff on the s5k5ccgx.c files between 2.6 and 3.0, and one thing that stood out to me was that almost every difference was the removal of a line from the 2.6 file. One thing that I'd probably try to add back in is the "Padding Buffer"'s from lines 1091 and 1100. There are a few memset's that are missing as well, which could be causing issues.

About the server, is it just a git version control system or is it something different? Either way I might need a refresher course and a lesson on good manners...

EDIT: My line numbers might be off. I was using Notepad++'s comparison feature, and it looks like it may add line numbers when comparing side by side.
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
Quick question. Do we know of any other devices that have the same back camera that have managed to get it working on the 3.0 Kernel, or is the Galaxy Player a one-of-a-kind?
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
Sorry if I'm posting too much, I'm treating this thread like a brainstorming session.

The back camera crashes when trying to use it for video recording. It shows preview for normal photos and panoramic photos. It actually saves the panoramas (see the attached photo, which is a panorama where I stopped it without moving it).

What I'm thinking is that we've got an issue with the camera drivers trying to save the content directly. I'm guessing that the panorama streams it's content to the app, which then does the computations to stitch the photo together before saving it. Because the app is saving it, there's no issue. I'm guessing the video crashes because it gets ready to write as soon as that mode is selected, since the video doesn't need to be progressed, just stored. The photo preview works because there is nothing to save until you click the button. It then hangs while it tries to save the photo (memory issue? Not enough space allocated for the photo?), which saves as a blank file.

I think if we look at places in the code where memory is assigned for writing the photo/video, we'll find the issue.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The only others are Tegra devices with special proprietary blobs, so basically unique.

That's what this thread is for :)

Those sound like decent reasons for it not working, but I'm not sure how they relate to FIMC; I guess the HAL could have issues, but you could isolate those by using camera.s5pc110.so from cm10.0.
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
I saw in the log cat that is the bitmap encoder of that sort crashes once you save the picture.
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
OK, reading through the camera API as well as the fimc_capture.c and I noticed some things that might be related to this. Whenever you use the API to take a picture, you can ask for four notifications back. One is letting the app know to make the shutter sound, another let's the app know the raw camera data is available, another is the postview of the photo, and the last I'd the days for the photo in a JPEG format. If we are getting errors for an encoder, it might be that last part.
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
I could be the byte array from the camera having issue that leads to the encoding problem.

---------- Post added at 10:51 PM ---------- Previous post was at 10:50 PM ----------

Using the api you should have on autofocus capture picture and play sound. Autofocus and sound works.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
But autofocus takes like fifteen seconds, so something's wrong there too.

Sent from my Galaxy Nexus
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
mCamera.autoFocus(new Camera.AutoFocusCallback(){
public void onAutoFocus(boolean success, Camera camera){
Log.d(TAG, "onAutoFocus " + camera);
camera.takePicture(
null,
null,
new PictureCallback(){
public void onPictureTaken(byte[] _data, Camera camera){
data = _data;
}
}
);
Log.d(TAG, "end of capture()");
}
});

autofocus took around 5 sec for my case, but it's still abnormal.

both logs were printed but not inside onPictureTaken

07-28 02:23:48.347: E/SecCamera(6785): ERR(int android::fimc_v4l2_dqbuf(int)):VIDIOC_DQBUF failed, dropped frame
07-28 02:23:48.347: E/SecCamera(6785): ERR(unsigned char* android::SecCamera::getJpeg(int*, unsigned int*)):wrong index = -1
07-28 02:23:48.347: E/CameraHardwareSec(6785): ERR(int android::CameraHardwareSec::pictureThread()):Fail on SecCamera->getSnapshot()

Some googling return this, http://xdaforums.com/showpost.php?p=26193900&postcount=295

Any idea:confused:
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I guess I was referring to touch-to-focus.

Maybe we need to allocate more memory to the hardware jpeg encoder or the camera device.

Sent from my Galaxy Nexus
[Samsung Galaxy Player 4.0, 5.0] KOala888:
doing that in kernel at mach_venturi.c doesn't help :)

if that is what you ment

Wysłane z mojego Nexus S za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
The log printing could be due to the camera running asynchronously. I'd be willing to bet it shows up at a slightly different spot in the log each time.
[Samsung Galaxy Player 4.0, 5.0] joemhewitt:
Seeing as the changes for 4.3 seem very minor and probably don't affect camera I think we could use this thread for 4.3 camera talk.

Sent from my zx spectrum
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
You are right about the camera talk. But 4.3 has a LOT of changes under the hood. It's just the surface that's the same.
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
I was looking through some of the code, its actually the biggest update since 4.0
[Samsung Galaxy Player 4.0, 5.0] :
Here is an interesting factoid which may or may not be relevant. The stock Gingerbread 2.3.5 doesn't come with a torch app. The one that I use is the nexus torch which, when used, specifically states that the ypg70 is not supported; yet it works. Is it possible that there is a nexus out there with the same rear camera as ours and would that help? Also, am I a fool to hold out hope that the rear camera will ever work properly on jelly bean?
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
I don't think it's foolish. I think that we are on the right track and have some good ideas for what is wrong, but many of us are either busy or unfamiliar with the dozen or so files that make up the camera drivers. I think if we could get a few people working together for a week we could get it working.
[Samsung Galaxy Player 4.0, 5.0] mrshane88:
Hey just wonding if anyone has worked on this recenlty. I'd offer my help but it seems like not many people are here anymore. :confused:
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I was wondering guys, are you able to take a picture with the front cam using the stock camera app?
[Samsung Galaxy Player 4.0, 5.0] mrshane88:
I can, but I don't really use the front cam since its low quality. Theres a Silent camera app that kinda works with flash. But its like the flash comes on too late after it already took the picture, then it stays on and the only way to turn it off is force closing the app. But thats not the stock camera app. Stock camera app can take front pictures and record video front and rear. What we don't have is rear camera for pictures and flash.
[Samsung Galaxy Player 4.0, 5.0] aznflawless:
I use Snapchat to take photos from the front and back camera, and save the photo to my gallery. Works fine as long as you don't auto focus or turn on the flash. Not the best quality, but it works.
[Samsung Galaxy Player 4.0, 5.0] mrshane88:
Yeah that looks like a good app. I think the only thing I miss about Gingerbread was its working camera, it had nice quality and I really liked the flash. But Gingerbread was clunky, it ran slow and lagged even when I shutdown apps and disabled them. It acted like how ever much free ram I got back it used for something else. Jelly bean dosen't do this, it has much better ram management better hardware acceleration, and cpu governors not to mention better wifi, sound, and power saving features. All of this I really like and its a real shame we don't have the support to troubleshoot getting a fully working camera. Its seemed to plague this development even since ICS. But no one is being paid to develop this and people get busy with life so its understandable. If I knew enough about coding I'd help, I do have some knowledge however and If asked to help in any way I would.
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
Shortly after I posted that, the machine that was being used by most of the devs to code on was shut down/repurposed for school stuff. I never made a code change, just looked through the code and pointed out what I thought errors were related to. As I recall, the issue seemed to be related to actually saving the content. The back photo would crash in the saving part of the operation, and trying to switch to video would crash as well, presumably because the video would prepare to write straight away. Panoramic mode worked because it wasn't the camera api doing the saving, it was an app. At least, that was my theory.

Someone mentioned rear video is working? Is that a 4.3 change or did you miss type?
[Samsung Galaxy Player 4.0, 5.0] mrshane88:
That makes sence since the camera does open and work, then when try and take a snapshot it freezes for awhile and does not save the picture. No flash either, I wonder why, I can get a flashlight app to and use my LED flash for light. So we know flash works just not with the camera. I think theres some errors in the code as well, another delevolper told me most of its code is still for gingerbread.

You asked about rear recording, well I did some searching and did find a fix. I've only tested it on 4.2 so I have no idea on 4.3

download link is here --- http://xdaforums.com/atta...3&d=1369421491, and you flash it through CWM. You'll have two camera app so disabling the old one is recommended. The gallery app diables the camera.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Is it possible to have a logcat and a dmesg while taking a picture using it? I would like to see what's wrong with the front cam on the 4.0.

Thanks.
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
https://github.com/xplodwild/android_packages_apps_Focal

That's the focal app by CM.

Would it be beneficial if we could trace which line of code throws an exception?

If so I could try to do it when I got some time.

I'm glad this device is not yet abandoned.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
http://xdaforums.com/showpost.php?p=42706208&postcount=44

This should be CM10.1, and I don't think anything has changed since.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
It doesn't contain any info about the S5KA3DFX which is the front cam, only the back cam.
[Samsung Galaxy Player 4.0, 5.0] JohnBergago:
Well I made some logs. Hope I did it right. I know it's very late but better late than never ;)

Hope it helps a little bit. Would be really nice to see the rear camera working :fingers-crossed:
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I get a 404 error upon opening them. Would it be possible to put it on pastebin or a simillar website?

Thanks. :D
[Samsung Galaxy Player 4.0, 5.0] JohnBergago:
LogCat:

http://pastebin.com/sDBzcpBt

dmesg:

http://pastebin.com/8wZEtU9e

Should work now ;) although I don't know what went wrong, maybe I've been a little bit impatient :D
[Samsung Galaxy Player 4.0, 5.0] NullUser:
Thank you guys for all your effort.

Much appreciated kingz!!!
[Samsung Galaxy Player 4.0, 5.0] speculatrix:
Hi,

is anyone able to give a brief summary of whether this has been fully resolved and the camera is fully working, and in which kernel?

I am happy to run 4.1, 4.2, 4.3 or 4.4 on my Wifi5, just want to be sure all the hardware is fully working; I'd stick with gingerbread but that's really holding me back now.

thanks

Paul
[Samsung Galaxy Player 4.0, 5.0] heet1:
Check out the thread for CM11 or Slimkat by Iurnait and Meticulous, respectively. Meticulous

Found a as he put it a compromise so the camera could work albeit at a bit lower resolution as well as getting the torch to work along with the radio. If I am wrong about this someone correct me. XD
[Nexus 7 Q&A, Help & Troubleshooting] Idkwts:
I downloaded fieldrunners 2 earlier and played it for around an hour until I had to charge my n7. After charging it, I tried opening it again and it won't open. I tried rebooting and still the same thing happens. Any fix?

PS I'm running PA on the N7.

This is what happens:
[Vibrant Q&A, Help & Troubleshooting] Mentalmama:
I'm pretty sure I bricked my phone. I tried to flash to stock using ODIN, but then it wouldn't turn on. Now I can get it to sort of turn on, but all I get is some orange letters. I'm pretty sure that means it's totally gone, but since I really don't know anything I could be wrong. Does anyone know if I could get it to work with a jig??

RST_STAT = 0x1

PWIC_IRQ1 = 0x3C

PWIC_IRQ2 = 0x0

PWIC_IRQ3 = 0x0

PWIC_IRQ4 = 0x0

PWIC_STATUS1 = 0xc0

PWIC_STATUS2 = 0x2c

Thanks
[Vibrant Q&A, Help & Troubleshooting] mikka06:
Not sure if I'm right cause I'm on a party and I'm drunk like a mofo but you could be ok if you're flashing a bootloader ( froyo ) and than you flash back to stock.
[Vibrant Q&A, Help & Troubleshooting] iTz KeeFy:
Your phone can still be saved, you just have to get it back into download mode and flash to stock again. A usb jig should solve your problem but first read this http://xdaforums.com/showthread.php?t=773006 and see if you can get into dl mode without the jig.
[T-Mobile Samsung Galaxy Note II] beryenbeh:
I'm currently on Carbon and I want to flash Frosty. My question is, let's say I make two backups of Carbon and Frosty. Later on if I decide to go back to Carbon, am I gonna need to full wipe and all that stuff before I install my backup Carbon? Or can i just go to TWRP and install the backup right away?
[T-Mobile Samsung Galaxy Note II] RonnieRuff:
Never a need to wipe when restoring a backup. Just remember you are going back to a place in time. So any new apps or app updates will need to be downloaded or updated

CARBON NIGHTLIES | KROZ THEMES | CABIN FEVER MAPLE WHISKY
[T-Mobile Samsung Galaxy Note II] beryenbeh:
Yes, I'm not worried about apps and contacts or any other info I have. So for example right now I'm on Frosty, can I just straight go back to my Carbon backup without having to full wipe? And that's not going to cause any problems?

Then the next day I wanna go back to Frosty, can I go ahead and just install the backup?
[T-Mobile Samsung Galaxy Note II] RonnieRuff:
When you restore you already are wiping. The whole phone is reimaged just the way it was when you created the backup

CARBON NIGHTLIES | KROZ THEMES | CABIN FEVER MAPLE WHISKY
[T-Mobile Samsung Galaxy Note II] beryenbeh:
That's what I needed to know!!! Thank you! I'll go ahead and flash Frosty and make a backup right away so I can just switch back and forth lol
[T-Mobile Samsung Galaxy Note II] beryenbeh:
Hey dude, before going to frosty, I backed up nfs most wanted using titanium backup. When I switched to frosty, there was no backup at all. Now I have to start from the beginning lol
[T-Mobile Samsung Galaxy Note II] RonnieRuff:
Titanium does only so well with system settings especially when switching between TW and AOSP

CARBON NIGHTLIES | KROZ THEMES | CABIN FEVER MAPLE WHISKY
[T-Mobile Samsung Galaxy Note II] beryenbeh:
Is there another option? I love that game haha
[T-Mobile Samsung Galaxy Note II] kozmo21:
You can try Helium backup app (used to be called carbon backup) from CWM.
[Android Apps and Games] mcluvin1065:
I just want a simple widget or app that will let me click to record video quickly since opening the app is to time consuming??

Sent from my rooted, suited, and booted s3, living the dual core life, know dat.
[General Topics] Dominar:
Hey guys.

Just bought XDA II 2 days ago and cant figure out one thing here. Is there a way to have PDA connected to internet via this USB connection (while its in cradel hooked up to pc which is on internet)?

Thanx.
[General Topics] jfran:
cant quite remember how to activate passthrough on the XDA however in active sync on the PC, in options via the rules option select the appropriate connection you want to use for passthrough and have that connection active under the connection settings in the pocket internet explorer (PIE)

PC

active sync | tools-> options -> rules (passthrough - this pc connects to xyz)

XDA

PIE - connection settings (same setting as selected above)

rgds

Jim
[LG Optimus Black] nunoleite46:
1. Go into the LG hidden menu 3845#*970#

2. Go into GPS Test

3. Go to Protocol Setting

4. User Plane Setting

5. Enable SLP Auto Provision

5. SLP Setting -> SLP Server Setting, I created a new one from the nokia servers (address: supl.nokia.com, port: 7275, no cert and no TLS setting)

Certificates of google expired in April, the nokia not :)

Now get 6 satellites in 20 seconds

ENJOY..

<---- ..and click the thanks button :)
[LG Optimus Black] OptimusDan:
Interesting I'll have to give it a try. Thank you.
[LG Optimus Black] Alucard:
It didnt work for me.Then i tried to remove it and i made a mistake and deleted open option and then everything went to crup,it forse closes when i ry to acces the same settings,can u help me fix this?
[LG Optimus Black] nunoleite46:
If you want to apply OPEN again create a new profile:

Slp name: OPEN (Google)

Adress: supl.google.com

Port: 7276

Save!
[LG Optimus Black] Alucard:
When i try to get to the menu with the optins lie open it force closes,factory rest is a must hah?
[LG Optimus Black] Alucard:
Re flashed rom and did not work.Force close still here,what do i do?Factory rest will help?
[LG Optimus Black] N00BY0815:
What ROM are you using?
[LG Optimus Black] Stark_Mark72:
HoW??

How do I go into LG hidden Menu?? Plz help..

This GPS really bugs me!! >_<

---------- Post added at 02:51 PM ---------- Previous post was at 02:10 PM ----------

I am using stable CM 10. I tried your first step. Does'nt work at all. I can't access th LG hidden Menu at all. Plz help. I really need GPS. Thnx in advance.
[Verizon Samsung Galaxy Note II] spoiler1041:
Does anyone have any idea why my keyboard keeps switching from the standard keyboard to the swype? It may be something i'm doing by accident, just not sure how it keeps happening.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] douggiephresh:
Is the bootloader unlock released yet?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] WoodburyMan:
No.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] StolenVW:
Nope but Loki is
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AxAtAx:
You been doing time, or have you been freeze dried..NO
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] goababa:
why o Devs's WHy??? AMF3 suxxxxxxxxxxxxxxxx........so this is my issue...i used goo manager and did something stupid...i can never get into recovery.....same error message...same sense of doom and despair....somebody please help a brother out!!! :cyclops:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] scott14719:
Why did you bump a 3 month old post for THIS?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] toxicpaulution:
Cuz' "YOLO"? XD jkjk idk.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] deron37129:
YOLO YOLO
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] goababa:
coz i'm in pain man....and when you're in pain...you'd do a bump or two...:rolleyes:

#YOLO
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Take it to best buy and ease your pain. http://xdaforums.com/showthread.php?p=45359306