Related
This is (or will be come June) my first experience with an android set. Now I've read that the codec support in Sensation is quite poor but I'm wondering if that support could be extended to include e.g. .mkv playback now that Sensation will (hopefully) be unlocked.
first: welcome to the android world
second: http://forum.xda-developers.com/showthread.php?t=1097503
Thanks! So the codec support depends on the media player like in PC OSs.
I'm also wondering if there's any possible "fix" for the quality of the photos taken with Sensation's camera. The photos I've seen aren't too bad but someone mentioned too high level of compression of the file which creates artifacts. Are there apps for the camera that will lower the compression level? The ones I've looked at on Android Market don't mention anything about compression. Or maybe it's a hardware limitation.
Welcome to android as well.
To be honest I am pretty new myself. The sensation when purchased, will be my first android smartphone. Had an Archos tablet for a few weeks before lending it to my sister 6 months ago lol...
Regarding the camera, I am not certain if we are talking about the same thing but they do seem similar. In the engadget review, they mentioned 'artifacts' where isolated areas of a picture were randomly soften or blurred. This is most likely due to software/settings that are processing the raw image before saving as pictures/files. With the recent HTC bootloader unlocking announcement, we should be able to see custom ROMs or even just single solution, fixes, tweaks, updates or whatever you want to call them to address issues like this. Or of course HTC can also fix the issue themselves.
Here is a link to the review if you need it
http://www.engadget.com/2011/05/27/htc-sensation-review/
if you are looking for the camera portion scroll down until you see the picture of the daisy? (sorry know very little about flowers)
apex84 said:
Thanks! So the codec support depends on the media player like in PC OSs.
I'm also wondering if there's any possible "fix" for the quality of the photos taken with Sensation's camera. The photos I've seen aren't too bad but someone mentioned too high level of compression of the file which creates artifacts. Are there apps for the camera that will lower the compression level? The ones I've looked at on Android Market don't mention anything about compression. Or maybe it's a hardware limitation.
Click to expand...
Click to collapse
I was testing out the HDR options for this and they do not seem to do much at all. There is a difference, but it is VERY minor. I took a shot without HDR, one with HDR, and then one using the free HDR app, and the HDR app simply blew the HTC HDR mode completely out of the water...
Has anyone else had any experience with this? Is there something I may be missing?
HDR always seemed like something better left to photo editing software to me (like photoshop). Phone camera filters always seem kind of lackluster, but then again, none of us are taking professional shots with a cell camera I assume
On topic though, I wouldn't doubt it being better. Sense stuff isn't exactly always perfection as far as software quality and HDR was probably just an afterthought tied into the camera so they could tick off a notch somewhere on some sheet for features.
Absolutely the same as my experience. I used HDR Camera from the market before this (free), and I really loved its results. When I installed the 3.0 Sense camera and saw the HDR setting, I was happy until I tried it. My theory is that it is NOT taking multiple pictures, but only doing an image adjustment --->> NOT the same thing. HDR Camera doesn't have the issues that some of you described. You do not have to be rock steady and my phone is plenty fast enough to take the three photos within about a second. The image settings are also adjustable (color, etc.).
On the other hand, the panorama mode in the Sense camera is Awesome!
yareally said:
HDR always seemed like something better left to photo editing software to me (like photoshop). Phone camera filters always seem kind of lackluster, but then again, none of us are taking professional shots with a cell camera I assume
On topic though, I wouldn't doubt it being better. Sense stuff isn't exactly always perfection as far as software quality and HDR was probably just an afterthought tied into the camera so they could tick off a notch somewhere on some sheet for features.
Click to expand...
Click to collapse
Software cannot do what HDR does. HDR takes 2 pictures, adjusting the gain on the sensor between low and high. It combines the best of both images to gain detail in low light areas and avoid over exposure in high light areas. Software will not work after the fact because the extra information gained from low/high gain is not present. Unfortunately the HDR option is poorly implemented by HTC. If you try HDR on the Iphone, you can see a drastic difference.
Actually, I use Pro HDR on my Evo, and it takes fantastic pictures in true HDR. It is a touch slower than a pro camera, but it does actually meter the scene and adjust the camera's aperture accordingly. It then allows for adjustments between the composite image and allows for saving the final as well as the source images, meaning you can do further editing elsewhere. Outside of some cropping, I haven't had problems.
With that said, I would be curious to know what the deal is with Sense. What's interesting is if you put it in HDR mode, it shows the little icon in the top right with multiple images...like whoever designed it at least understood how true HDR *should* operate. Then, if you push and release it instead of the regular shutter button, it beeps and you hear the lens go, and the image focuses itself. So...idk. I don't see a noticeable effect in the regular images at all...
Hello.
First of all, my compliments to everone that makes great things like custom roms, mods, and so.
I'd like to know if is there a way to mod/improve/change the camera app, so the shutter speed can be set.
Thanks.
Hello again. It seems this thread gained some interest, but no one could give an answer. What I asked was if is there any way to hack, develop, activate improved settings for htc chacha camera.
Videos are saved in 3gp format. Is there any way to make camera app to save them as mp4?
Pictures get blurry if the subject moves quickly, or you are not steady when shooting. Is there any way to set the shutter speed?
I don't know if the camera app can be disassembled or something, and hacked into make that things.
Maybe the camera app can be ported from another model that uses the same camera model, and can do that.
I asked HTC about this, and they answered "latest 2.3.5 version has many improvements", but none about the camera...
The camera is way better than Wildfire, which my wife owns, but I think it can be even better if the camera app is up to it.
Thanks for reading.
The big question revolving around this issue is if the cameras themselves are the same between the phones. It's not only the camera.apk that's connecting them, it's the hardware as well. Yes, there could be a possibility that the cameras are the same, between ChaCha and Wildfire (for example), but at the same time the proc or image sensor might be of a newer generation. Unfortunately I have no hardware specs on this, if anyone knows it would be nice to know.
Question: Do you know of any phone that has advanced settings inside the Camera.apk that allows you to set shutter speed? Would be interesting to compare them a bit.
In the camera.parameters public class there is a setting called scene_mode_sports that seems to be the only way to set a faster shutter speed.
I can't see it in my HTC Chacha/Status, and even lgcamera hasn't that option in the menu.
There is a profile.xml file that sets the limitations of the camera, but it seems people hack it to allow the camera to record movies in higher resolutions, because many times the limitations are imposed by the manufacturer and not the hardware.
Also, hacking the firmware and/or the drivers of a camera would allow to gain the full features of it.
This reminds me of people that upgraded the Nokia N900 to allow it to record movies in 720p, just by replacing binary files in the phone.
Is there an app that tells you what exactly hardware your phone has, and such drivers or modules it uses?
Thanks all.
Hello all.
I'm reviving this with some news. The camera module the ChaCha uses is a Samsung s5k4e1gx (http://www.samsung.com/global/busin...t/cmos-imaging/detail?productId=5622&iaId=220), the same found in several other HTC models: HTC Desire Z, HTC Mini and others.
It seems that in the Desire Z this camera is able to record 720p video.
I think this is determined by the firmware loaded for the camera, and the app itself.
I'd like to know if it's possible to port change the original ChaCha camera related modules and firmware from the Desire Z ones, so the camera can get taht 720p video shooting.
Also, I'm searching for a way to disable the auto light metering so a manual can be set. There are many 'better camera' apps in the market but they all seem to improve the original camera app itself, instead of getting the most of the actual camera sensor.
Thanks all.
This first post from me is going to be short. I welcome additional thoughts, of course. Sorry if this isn't the best place to drop this, but it's not a question and it's not anything in development!
First, an observation: the problem with 720p in CM10 is not bright light, it's the camera's ability to adapt to bright light from low light. In other words, the problem seems to be related to the light sensor. Although this is not completely new, what I noticed from playing around with LGCamera is that if I turn UP the video bitrate, the flickering is not as sever. The flickering will stop and stabilize when filming in consistent light. Any change in light quality will produce more sticking. This makes sense since 720p requires finer adjustments to light and dark than 420p. The other part of the equation is the h264 encoder. I'm guessing that certain values in the light sensor need to match up with the h264 encoder...
Second, I was playing around with these settings today: http://forum.xda-developers.com/showpost.php?p=17791551&postcount=20 I haven't had enough time to verify what makes a difference and what doesn't. I believe that some settings have helped a bit. Also, I felt that changing the ISO to 800 in camera and then switching to video improved the video, but that could be totally imagined! Essentially, what we need is ISO800 for the vidcam... I think!
Suggested fix that was here didn't work. I'm editing to see if I can correct the "Invalid User ID" error I keep getting on my XDA app. Started right after I went to correct this message.
if you think you have found a fix i'd suggest bringing it to the developer's attention, such as indeed posting this in the official thread.
Also your second post got chopped off lol
threi_ said:
if you think you have found a fix i'd suggest bringing it to the developer's attention, such as indeed posting this in the official thread.
Also your second post got chopped off lol
Click to expand...
Click to collapse
I'm just messing around right now. I don't think I've found a fix. A few things I've found: I can't find a way, using the included camera, to film above 25 fps. It doesn't matter what the settings are in media_profiles.xml, 25 is the cap. The cap should be a little above 30. I also can't force the camera to film above a bit rate of 6 Mbits/sec. I averaged around 8 Mbits on the stock camera and 10 in LG camera on GB. These settings will affect light responsiveness! Perhaps the oddest thing I've noticed is that the recording streams are inverted in JB. Everything I've filmed in GB has audio in stream 1 and video in stream 2. JB's streams are the other way around. EDIT: In fact, in GB 480p recordings use Stream 1 (or 0, depending on your player) for video and stream 2 for audio, but 720p recordings use Stream 1 for audio and Stream 2 for video. So, perhaps it's worth looking into the ways in which 720p recording is being "sent" to the codec.
In the process of sorting these things out, it would help if we could find out what the AVC h263 and MPEG4 profiles and levels were in GB. I'm not completely convinced that they are configured optimally for our phone.
[To Forum Mod: Is it possible to move this thread elsewhere? Possibly the Q&A section?]
I've spent more time on this than I intended today, so this will be brief(ish). I don't know if I've found a fix, but I may have discovered a good lead. This is definitely for people who can put together and test out kernel changes faster and more accurately than I can! The other day I thought I'd found something of use, a v4l2 driver modification for Crespo. I sent my findings over to Scotthartbti. The modification may still be of use, but there was an unanswered question: why is vidioc_dqbuf unable to to clear the buffer queue? If it's the preview screen size, the fix I discovered wouldn't repair everything. SO, when I read this morning that the kernel is actually based on a Rogers ROM with limited capabilities, I decided to run another diff on the JB kernel and the GB kernel from Samsung. What I discovered was that certain drivers s3c_bc.c and s3c_bc.h are absent from the JB kernel. These two files (?) contain information that sets screen and buffer size that I couldn't find replicated anywhere in the JB kernel. I don't think it's not there... so, in the process of trying to find out why these files might not be in the JB kernel, I discovered something better: the android exynos 3.4 Git. And surprise surprise! What is it that devs are fixing over there? Quite a few issues to do with s3c buffer size, particularly in s3c-fb, and the problem of the system ignoring preview frame size!
I suspect that some lingering bugs are being addressed here: https://android.googlesource.com/kernel/exynos.git/+/android-exynos-3.4
keep it up.
Thanks for working at this. I just learned how to pull a logcat and I nabbed one while barcode scanner was on. I'm running CM10 now and I ran CM9 until July. I wish I could help, but alas I am merely a padawan.
Thanks, reynaim. Yours looks pretty much like mine. It's useful to have that confirmation!
So, I've been working on this for awhile now, spending much more time than I ever thought I would. I'm not a developer. I taught myself html, css, and php and it looks to be following a similar route with c++ and python! I've learned a fair bit about how our phone works and I have some ideas about the problems with our camera. I'll list what I can here:
1. Google updated their camera code several revisions ago, but it appears Samsung either relied on aging code or has not released the actual code for the camera hal. Several commands that bind the driver layer to software are not up to date in our camera hal and may be part of the cause of the flickering. The way the camera works is that it calls up a preview, then dumps that information before it starts recording. I suspect that the camera is not clearing the buffer queue at that moment as it should. I am attempting to rewrite this portion of the driver, but it's laborious.
2. Let's be clear about what the problems actually are: Flicker in any transition of light conditions. I can get 720p to work in bright light if there are no shadows. The light sensor is not working with the camera correctly. Actually, the problem is the framerate. At the moment, the 720p stream is going through the wrong channel, as if it is running on a PAL device. Hence, not only is the datastream throttled, but the framerate is wrong. I tinkered a bit with the light sensor drivers - changed a few values here and there - but I haven't noticed a difference.
To note here: PAL = 25 fps, NTSC =30fps. Also, PAL = 50Hz, NTSC = 60 Hz. The Infuse may use a mixed mode that runs 30fps and 50Hz.
What you will notice as a user in addition to the flicker and stuck frames is that:
The video stream is stream 1. It should be #2 (you can check this most reliably in VLC on your computer or MX Player on your phone - VLC refers to the streams as 0 and 1).
FPS, despite media_profiles.xml demanding otherwise, will not rise above 25 and may drop to around 15.
Bitrate won't rise above 6Mbits/sec (interestingly, Android sdk has the bitrate capped at 8Mbits/sec). GB would ordinarily record at 10 - 11 Mbits/sec (there is a way to up the bitrate in JB, but it doesn't improve vid quality).
3. Some minor irritations can be corrected by adding the firmware packages back into the system folder. Add a directory called "firmware" to your system folder (so it should look like /system/firmware/), give it the permissions 754 (RWX,R-X,R-X), and add RS_M5LS_OI.bin, RS_M5LS_SI.bin, RS_M5LS_TB.bin (which you may find in an old GB backup). Give those the permissions RWX, R,R (or R-X, R-X for the last two - I'm not sure which is better!). Reboot. This gets rid of that odd lag you've probably noticed when you open up 3rd party cameras and they search for storage and sometimes crash as a result.
4. I don't think - I could be wrong! - that the problem is actually in fimc. Fimc is behaving normally. There are some curiosities in the current camera hal that fimc doesn't like.
5. In fact, it seems the camera hal was not written for an 8MP camera. Why doesn't Samsung release the camera hal? Does anyone know this? My best lead came when I bricked my phone and decided to take a couple of video logcats so I could at least pinch a few values and processes.
Its seems very long since update on this thread
Whizzpopper said:
Thanks, reynaim. Yours looks pretty much like mine. It's useful to have that confirmation!
So, I've been working on this for awhile now, spending much more time than I ever thought I would. I'm not a developer. I taught myself html, css, and php and it looks to be following a similar route with c++ and python! I've learned a fair bit about how our phone works and I have some ideas about the problems with our camera. I'll list what I can here:
1. Google updated their camera code several revisions ago, but it appears Samsung either relied on aging code or has not released the actual code for the camera hal. Several commands that bind the driver layer to software are not up to date in our camera hal and may be part of the cause of the flickering. The way the camera works is that it calls up a preview, then dumps that information before it starts recording. I suspect that the camera is not clearing the buffer queue at that moment as it should. I am attempting to rewrite this portion of the driver, but it's laborious.
2. Let's be clear about what the problems actually are: Flicker in any transition of light conditions. I can get 720p to work in bright light if there are no shadows. The light sensor is not working with the camera correctly. Actually, the problem is the framerate. At the moment, the 720p stream is going through the wrong channel, as if it is running on a PAL device. Hence, not only is the datastream throttled, but the framerate is wrong. I tinkered a bit with the light sensor drivers - changed a few values here and there - but I haven't noticed a difference.
To note here: PAL = 25 fps, NTSC =30fps. Also, PAL = 50Hz, NTSC = 60 Hz. The Infuse may use a mixed mode that runs 30fps and 50Hz.
What you will notice as a user in addition to the flicker and stuck frames is that:
The video stream is stream 1. It should be #2 (you can check this most reliably in VLC on your computer or MX Player on your phone - VLC refers to the streams as 0 and 1).
FPS, despite media_profiles.xml demanding otherwise, will not rise above 25 and may drop to around 15.
Bitrate won't rise above 6Mbits/sec (interestingly, Android sdk has the bitrate capped at 8Mbits/sec). GB would ordinarily record at 10 - 11 Mbits/sec (there is a way to up the bitrate in JB, but it doesn't improve vid quality).
3. Some minor irritations can be corrected by adding the firmware packages back into the system folder. Add a directory called "firmware" to your system folder (so it should look like /system/firmware/), give it the permissions 754 (RWX,R-X,R-X), and add RS_M5LS_OI.bin, RS_M5LS_SI.bin, RS_M5LS_TB.bin (which you may find in an old GB backup). Give those the permissions RWX, R,R (or R-X, R-X for the last two - I'm not sure which is better!). Reboot. This gets rid of that odd lag you've probably noticed when you open up 3rd party cameras and they search for storage and sometimes crash as a result.
4. I don't think - I could be wrong! - that the problem is actually in fimc. Fimc is behaving normally. There are some curiosities in the current camera hal that fimc doesn't like.
5. In fact, it seems the camera hal was not written for an 8MP camera. Why doesn't Samsung release the camera hal? Does anyone know this? My best lead came when I bricked my phone and decided to take a couple of video logcats so I could at least pinch a few values and processes.
Click to expand...
Click to collapse
Hi @Whizzpopper,
I was searching on Google for infuse 4g 720p recording on JB custom ROMs and found your thread,
it seems you had been gone throught very deep on this.
Have you found anything that help us on resolving this issue afterwards ?
yogi.306 said:
Hi @Whizzpopper,
I was searching on Google for infuse 4g 720p recording on JB custom ROMs and found your thread,
it seems you had been gone throught very deep on this.
Have you found anything that help us on resolving this issue afterwards ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=38355903
Sent from my Galaxy Nexus using xda premium
yogi.306 said:
Hi @Whizzpopper,
I was searching on Google for infuse 4g 720p recording on JB custom ROMs and found your thread,
it seems you had been gone throught very deep on this.
Have you found anything that help us on resolving this issue afterwards ?
Click to expand...
Click to collapse
Indeed, I did leave the Infuse. There are so many variables, it's hard to say. The problem could be in the codec or in the settings used to interact with the codec (the media_profiles.xml or media_codecs.xml) or it could be in the kernel as Scott Hart used to suspect (don't know what he thinks now!). As you know, Samsung did not provide an honest release of the source for the Infuse.
Sorry I couldn't be of more help!
Thanks
Whizzpopper said:
Indeed, I did leave the Infuse. There are so many variables, it's hard to say. The problem could be in the codec or in the settings used to interact with the codec (the media_profiles.xml or media_codecs.xml) or it could be in the kernel as Scott Hart used to suspect (don't know what he thinks now!). As you know, Samsung did not provide an honest release of the source for the Infuse.
Sorry I couldn't be of more help!
Click to expand...
Click to collapse
Thank you for your updates,
Now Scott made a lot of improvement and fixed all most all the bugs for the kernel we are using in infuse 4g,
the only 720p recording and HDMi are not resolved yet, and i guess its not possible due to samasung not provided the source.
Thanks for your efforts on infuse.
The LG 360 Cam is now available to buy. I got this from Clove Technology at the same time as the VR headset.
I spent a lot of time playing and using this, my detailed review is below. Includes sample media, screen shots and more.
https://gavinsgadgets.com/2016/05/04/lg-g5-friends-lg-360-cam-review/
Any questions, please ask. Also if anyone else has one, then add your views.
gavinfabl said:
The LG 360 Cam is now available to buy. I got this from Clove Technology at the same time as the VR headset.
I spent a lot of time playing and using this, my detailed review is below. Includes sample media, screen shots and more.
Any questions, please ask. Also if anyone else has one, then add your views.
Click to expand...
Click to collapse
It looks really cool man. Will consider to buy one.
How well do you think the 360 cam would work as a dash cam?
Probably overkill
I'm also considering it for a possible dashcam, but what are the practicalities like? Can you just plug it into a USB charger and have it record continuously (1 hr+) to a sd card, or are there some limits?
From memory it's 4gb video size max.
New beta software has arrived play store after some time they take back 5.2.2 to 5.1.1
software says for new features (3d audio for example) need to update firmware but when checks no new firmware found(also check with bridge
). Do u know anything about that?
Old thread, but i dig him out...
Got the camera yesterday for small money. Less money = less risk i thought.
The first impression: Video & photo quality are lower than expected.:crying:
Tried some apps from play store to handle the camera. THan i had made a firmware update because the camera doesn’t support life monitoring with the old firmware. (LGbridge) Now it seems to work alright.
The camera uses BT connection to control the hardware and uses the w-lan to transfer picture data to smartphone.
You can change between full automatic and manual mode. I tried the auto mode at first.
After a few experiences, the results are a little bit disappointing. Under low light, the results are noisy and a little bit unsharp.
The visible quality is lower than expected.:crying: BTW: Between the front and rear pictures, there is a small visible cutting edge.
I hope, this will be fixed in next release!
I think, i will give the project a last chance with daylight now. Thinking about to return the camera to dealer....
more about the camera:
-> http://www.trustedreviews.com/lg-360-cam-review
-> https://www.youtube.com/watch?v=qe6B4sgtLiQ
Edit:
ok, got better results using "daylight" ! Of curse not the same quality as the LG5 camera will do, but acceptable for me.
tried to make some records like GOOGLE does. Driving along the street with G360 on top of the car. That was amazing!
tried to edit 360 video with AndroVid and it worked for me! (cutting and adding sound, no color effects or titles!) Hope i will find more apps to handle my videos.
tried to edit a 360° picture with "snapseed" and "photo editor" and it work!
see my pic in attachment. I have cut me out!
BTW: after uploading my pic, it is only 5% of size as the original one. (4,5MB>245kb)
The quality is very reduced now compared to the original!
There is a new firmware available for 360 cam. Version "L"! Can’t see any differences until now. Was described as a camera optimization only. No new features.
max. record time ~20min / ~2.3Gb. - nothing changed!
no new fw until now.
juli.2017