Works perfectly for me. How were you going about changing it?
Sent from my YP-G70 using xda app-developers app
Sent from my YP-G70 using xda app-developers app
Changing the DPI prevents the device from booting. I get stuck before the bootscreen.
I Can Confirm Zip For Back Camera Recording Fix Works But Camera Is Not Themed
Sent from my YP-G70 using xda app-developers app
What did you set it to? I've managed to set the DPI as low as 120 and it boots fine. Anything below 120 caused a bootloop on ICS, so I assume the minimum DPI the device supports is 120.
persist.sys.vold.switchexternal=0
persist.sys.vold.switchexternal=1
I Can Confirm Zip For Back Camera Recording Fix Works But Camera Is Not Themed
Sent from my YP-G70 using xda app-developers app
Recording meaning take a picture or video?
Sent from my YP-G70 using xda app-developers app
What did you set it to? I've managed to set the DPI as low as 120 and it boots fine. Anything below 120 caused a bootloop on ICS, so I assume the minimum DPI the device supports is 120
The camera recording fix will be built into the next version so the camera remains themed.
It was 4.1 where the 3-parts didn't work. Mine are functioning perfectly with this.
I got a theory on the camera but I don't know much about ROMs so I don't think I can fix it. I believe the reason why the rear camera won't take any pictures is because all the rear camera resolutions available are for the Galaxy S' camera, which makes sense because CM10.1 was ported from the Galaxy S. The resolutions for the rear camera now go up to 5MP and the Galaxy Player 5 has a 3.2MP camera, so it makes sense that the rear camera can't take any photos. If the proper camera resolutions were defined in the ROM then I think the rear camera will work. I would try doing this myself but I have no idea where to find the file to modify (maybe media profiles?)
Yes I know it was with 4.1 but mine don't seem to work but I went back to CM 10.1 so now they work
Sent from my YP-G70 using xda premium
If this is the case, modifying media profiles might not be enough. The i9000 and variants use a different camera sensor so some libraries would probably need to be modified to match our hardware. The sensor used in the 5.0 is not very widely used so this may be fairly difficult to do. I started a thread a while back to collect all the work on a camera fix in one place, but it seems to have gotten buried under everything else. A lot of the stuff there is ICS related and there's a bunch of unnecessary bluetooth stuff, but if we can collect all the development work into one thread, it might speed things up as its easier to find any required info
http://xdaforums.com/showthread.php?t=1847045
Just tested it now and it works fine for me. Doing a clean install might fix it. You might not even have to wipe data. Wiping cache and dalvik cache might fix it.
Well this explains why the available resolutions are up to 5MP: https://github.com/JackpotClavin/an...mmit/68543fc28b889f9a379cf9c49c1fd470f50e29f9
I'm sure it isn't hard to make the changes to the Crespo's camera HAL to get the supported resolutions of the 5.0's camera. The rear camera is already initializing fine so maybe just those resolution changes will fix it. In that commit, look at the changes to libcamera/SecCameraHWInterface.cpp
But then again I'd be amazed if the solution is this simple (it never is and I know almost nothing about ROM development )
I don't think changing the resolution will fix it. I just tried taking a photo with the resolution set to 1.3 MP, but it didn't work. I think the issue is when the image is being saved as the width and height both come up as 0 and even when the flash is forced on, the image details say no flash. If we look at how the front facing camera saves the image, we could compare it with how the rear facing camera is set to save the image and modify it to match. I'm not entirely sure that this would work, but it might be worth a try
Yeah I just looked at the resolutions and some of them are the same as before. I also noticed that some ISOs that aren't supported by our sensor were added in, so I put my hand in front of the camera to lower the ISO and lo and behold it actually took a picture and made the capture sound instead of hang on taking the picture like it usually does. But after that it just hung and didn't save the picture, so you're right that the camera isn't saving the image correctly.
At least we're making some progress. I think we have the same camera hardware as the Galaxy Tab and I believe it has CM10.1 so it might be worth having a look at their source or just trying to use their drivers as I think they also have the Exynos 3 single SoC
Good idea. We were using the Galaxy Tab camera HAL before so looking at their source could help. Hopefully we won't have to mess with the kernel to fix this; camera drivers have always been a pain for me
[COLOR="Navy"]Fire Eel Mk 2 - v5.0.2 - BUILD JB5FE2R - md5: 3c1c7c4b9f889edea372dab63ab64737[/COLOR]
[LIST]
[*]Updated CM10.1 code
[*]Added the Samsung style notification drawer by Team Droid Invaders
[*]Removed the Accuweather widget
[/LIST]
[COLOR="Navy"]Fire Eel Mk 1 - v5.0.1 - BUILD JB5FE1R - md5: 25cf64206185b36a5ea77e9d971ea95b[/COLOR]
[LIST]
[*]Added AROMA installer
[*]Choice of kernels - USA/INTL
[*]Choice of bootanimations
[*]Included the latest version of our custom notification drawer. This is nowhere near finished yet, but we're making progress
[*]Implemented rear facing camera recording fix
[*]Reverted messy vold hack
[*]Updated alarm tones, notification tones, ringtones and UI sounds from SIII to S4 version
[/LIST]
[COLOR="Navy"]Fire Eel Mk 0 - v5.0.0 - BUILD JB5FE0R - md5: 61da9bb0d32de648ed13721ec36ce376[/COLOR]
[LIST]
[*]Initial release
[/LIST]
Superb rom, but there is no FM Radio app
Spirit FM is not working.
persist.sys.vold.switchexternal=0
persist.sys.vold.switchexternal=1