http://www.clickapps.com/moreinfo.htm?pid=18117§ion=PPC
Looking for something like this...This is for diamond...But can it be ported to xperia?
Any cookers help?
Thanks in advance
Fulgore69 said:
http://www.clickapps.com/moreinfo.htm?pid=18117§ion=PPC
Looking for something like this...This is for diamond...But can it be ported to xperia?
Any cookers help?
Thanks in advance
Click to expand...
Click to collapse
It's for PocketPC, so I'd just try. Only the resolution of the Diamond is different (well, maybe also camera drivers). What does it do? show the image recording of the front camera on screen?
In general, when you see a program is for PocketPC, it will work on most HTC and other windows mobile devices. Sometimes there's a restriction because of the resolution used (older programs often use 320x240, which doesn't look too pretty on the 800x480 screen of the X1), but most of the times they will work.
Like in 'normal' Windows there may be a restriction because of the type of program. Maybe you need .Net compact (newest version is often installed in X1 roms) or some program or driver. If that's the case, it should be mentioned at the download or info page of a program imo.
Some programs are written for a certain type of Windows Mobile (2003, 2003 SE, WM5, WM6.1 or WM6.5) and use instructions that aren't available on older WM versions. Usually you'll find such info on the info or download page of the program as well.
If you're not sure whether the program will run or not: just try . The chance it will leave your device broken is very small and again: if the program is that specific and shouldn't be used on another device, it is usually mentioned somewhere (for instance HardSPL and roms are device specific, but then again those aren't really programs).
Let's look at the program info:
Description :
Use this Make Up Mirror to make oneself up and when no real Mirror is available. The program activates the Front Camera and you see yourself. Only for HTC Touch Diamond and HTC Touch Pro.
# Image from the Front Camera, suitable as Mirror
# After closing and on starting the usual camera function the rear camera is active again
# For fast access the program can be laid upon an button
# Daily utilization as Make-up-Mirror
# Only for HTC Touch Diamond and HTC Touch Pro and compatible devices*
This program works only on devices from HTC and identical devices, e.g. HTC Touch Diamond, HTC Touch Pro, O2 XDA Diamond, T-Mobile MDA Compact IV and future devices from HTC.
System requirements:
# System: Windows Mobile for WM6.1
# Screen: 240x320 Pixel or higher
# Processors: Samsung, Intel® PXA XScale, StrongARM, OMAP, Qualcom
# Newest technology: Program developed in Visual Studio.Net.
Compatibility:
Pocket PC Windows Mobile 6.0
Pocket PC VGA resolution (fullscreen 640x480)
Pocket PC Square VGA resolution (480x480)
Pocket PC Square QVGA resolution (240x240)
Pocket PC QVGA resolution (320x240)
Pocket PC QVGA resolution (240x320)
Click to expand...
Click to collapse
The info says you need WM6.1 or above: check
you need resolution 320x240 or above: check
you can use a device with a Qualcomm chip: check
supported resolutions don't include 800x480, but this probably means that 640x480 will be stretched a bit or a black bar will be displayed. I think the program will still work.
why don't you simply use the Camera Application of you X1?
In the Camera Settings you can choose which camera should be used, Front or Rear Camera. Is guess its the same effect an you can save the Price of 2 Euro.
Greetings
LordK
As I am sure many already know, there is a service called QIK which allows you to transmit live audio and video from your phone.
I've been trying it out on my Verizon HTC TouchPro 2, and it's a pretty fun application, but the one thing that is a bit annoying is that the frame rate is low - something like four or five frames per second and therefore very jumpy. It does not seem to matter if it is 3G or Wifi, either way it's just not very fast. Other phones, however, seem to get much better frame rates, Nokia's and the iPhone 3G look like they're doing at least 15fps or better.
As I have come to understand, the reason for this is that HTC has not published their camera system hardware API, thus forcing developers to capture the images directly and encode them in software. While the phone is able to encode pretty good mpeg-4 on the fly, they don't give any kind of SDK to actually use this capability in any third party software.
So...
This leads me to wonder if there are any ways of doing this that have been developed independently. We all know that a vendor's refusal to put out a public API does not stop others from developing one using a combination of reverse-engineering, API sniffing, backdooring etc.
I am aware that developers have managed to get 3D acceleration working on HTC models, despite the lack of openness from HTC.
Alternatively, are there any other services like QIK that might do better when it comes to streaming?
great question. I am looking for the same answer.
The quality of the video is much better if you upload a video taken directly with the HTC camera app.
This would be fine for me, but it always make the upload Private, which is the opposite of what I need.
Have you found any workarounds?
Hi guys, does anybody know if there's any applications available for a camera timer? I'm using an Omnia 7 and it's becoming a bit of a glaring omission, so it'd be great if there was an app for it, and I certainly wouldn't mind paying. Thanks!
don't believe so at present. i haven't fiddled with the camera API, but from what i'm aware it just launches the camera application and requires the end user to capture the image. a homebrew solution might be possible, but nothing has come around as of yet.
Hi,
I didn't find information about this yet. I am new to Android but never intended to use stock, so I bought the Z1c and flashed CM11. The only thing I miss are video recordings with 60 or even 120 FPS, as possible with stock firmware. Now, please correct me, if I am wrong. AFAIU it is not easily possible to port the stock camera because of the dependency of Sony's framework (even if I don't understand the difficulties about this and why nobody did it yet?). If I understood correctly, the drivers extracted blobs from stock-ROM, so it not being able to record videos with high frame rates is not an issue of the camera driver but of the camera app. I also didn't find an alternative camera app providing this functionality.
I read that Android L will bring much more possibilities to the camera API, so apps could be able to 'get the full performance of image sensors', as I read in some news article. It will be possible to take RAW images as well as setting the exposure time, aperture, fps etc manually, even if the device manufacturer wants to limit these functions. Do you see maybe a possibility to get high-speed recording with Android L based CM(12?)?
/e: nevermind, did't read properly.
Dear owners of an OnePlus 5T and maybe 5 too,
please grant me an answer to a really important question: Is the Camera2-API bug fixed for the OP5T or is it still valid and OnePlus didn't do anything against it?
Please do following:
Download Open Camera > Go to settings > Scroll down > Switch on Camera2-API > Cover the rear camera with your hand > Read the values at the very top of your screen:
• If ISO 799 and 1/16,7 is still here: Nothing was fixed. Please leave a reply.
• If values differ from those values (ISO 799 1/16,7) OnePlus finally fixed the Camera2 API. Please also leave a reply.
Thanks in advance.
MickyFoley said:
Dear owners of an OnePlus 5T and maybe 5 too,
please grant me an answer to a really important question: Is the Camera2-API bug fixed for the OP5T or is it still valid and OnePlus didn't do anything against it?
Please do following:
Download Open Camera > Go to settings > Scroll down > Switch on Camera2-API > Cover the rear camera with your hand > Read the values at the very top of your screen:
• If ISO 799 and 1/16,7 is still here: Nothing was fixed. Please leave a reply.
• If values differ from those values (ISO 799 1/16,7) OnePlus finally fixed the Camera2 API. Please also leave a reply.
Thanks in advance.
Click to expand...
Click to collapse
Glad I could help.
ISO 9600 and 1/16,7s
so what does this mean now exactly?!
what are the advantages, what can be accomplished? the Google Cam HDR still doesn't seem to work correctly on the 5t.
@vercetti: The reason why I'm asking it: There are several good, real camera apps out, taking advantage of the Camera2 API. I still have the 3T and OnePlus didn't fix the Camera2 API implementation for us. Neither with Oreo. With the correct implementation (thanks for the confirmation @Wilux), Open Camera, Footej Camera, A Better Camera, etc. will work correctly and a Google Camera port is more likely than with a bugged implementation of the API - like for the 3 and 3T.
OnePlus 5 also shows ISO 9600 and 1/16,7s (latest stock rom)
MickyFoley said:
@vercetti: The reason why I'm asking it: There are several good, real camera apps out, taking advantage of the Camera2 API. I still have the 3T and OnePlus didn't fix the Camera2 API implementation for us. Neither with Oreo. With the correct implementation (thanks for the confirmation @Wilux), Open Camera, Footej Camera, A Better Camera, etc. will work correctly and a Google Camera port is more likely than with a bugged implementation of the API - like for the 3 and 3T.
Click to expand...
Click to collapse
This means pictures will be lot better then on original camera app?
Would like to see some comparison from OP5t camera and OpenCamera. I still thinking to buy this great piece of tech, but its all about camera what I am focused about. Google phones not available in my country (officialy), Im getting sick over Samsungs (got them for 3 years now, too much!) as all what is good on Sammies is camera. Want to move from my s7e as there was no good flagship, but OP5t is perfect, if at least have same quality of pictures/videos as its on s7e, even if that means using 3rd party app.
@droidhd: This means, the device is theoretically able to do better images via the correct working Camera2 API. Mostly, images will be bad because of post-processing. And if you shoot RAW, mostly the hardware and the correct implemented API is significant for good photos. Maybe you'll see more grain. Maybe the colors aren't the same like you do with the standard camera app. But I'd say: Yes, they get better with more advanced camera apps.
My list of professional camera apps (No need for social media crap like filters, effects, etc.):
Open Camera: https://play.google.com/store/apps/details?id=net.sourceforge.opencamera (Simply a great piece of software!)
Snap Camera HDR (Beta): https://play.google.com/store/apps/details?id=com.marginz.snap (Looks like abandoned. Last update 1 year ago)
Manual Camera: https://play.google.com/store/apps/details?id=pl.vipek.camera2
A Better Camera Unlocked: https://play.google.com/store/apps/details?id=com.almalence.opencam_plus (Looks abandoned, but will get updates from time to time. Unsteady, but alive)
Camera FV-5 (Beta): https://play.google.com/store/apps/details?id=com.flavionet.android.camera.pro
ProShot: https://play.google.com/store/apps/details?id=com.riseupgames.proshot2
Footej Camera: https://play.google.com/store/apps/details?id=com.footej.camera
Sadly, only one for video left:
FiLMiC Pro: https://play.google.com/store/apps/developer?id=FiLMiC+Inc. (Please try Evaluator first!)
Cinema FV-5: https://play.google.com/store/apps/details?id=com.flavionet.android.cinema.pro (Seems abandoned. Last update 2 years ago)
The list isn't very long, I know. Feel free to extend it. But please: No filters, no effects, no social media like things. Those are around in thousands and nothing professional in it!
Micky, could you explain to me why it is common knowledge that picture quality is usually best when the stock rom with the stock cam is used compared to any photography app running on custom roms?
I've read in so many threads, posts... that people went back to the stock rom just because pic quality is higher than on custom rom.
is this history when camera2 API works correctly? meaning that images are identical when using open camera on stock vs opencam on custom rom? or would opencam (or any other photo app) still produce images of lesser quality when used on a custom rom?
People went back, because of the abstraction layer and because drivers are still closed source. I'd like to compare it a bit:
If you setup a new computer, you only have standard drivers for each and everything. You can use it, but only if you install the correct drivers, things get to start working like they should. Like your graphics card: Working, but you'll notice some kind of stuttering/tearing when scrolling in your browser on certain websites. If you install the driver for your card: All is smooth, like it should.
So we can say: Drivers in AOSP are more like standard. Not all functions, more workarounds, but working OK. And drivers directly from stock (OEM) will get all functions to work good and smooth (if they're implemented correctly).
But you can see, that it's possible to get great photos out of your device with mods for Google Camera even on AOSP-ROMs. Because this mod brings itself some "magic". So you see: Closed source vs. open source. If we'd have the full code of the drivers: Photos, produced by the standard camera app of every OEM would probably look like crap.
OnePlus once promised to get us at least the camera blobs, but they didn't. They say: "Too hard!". Lie, because they know, that their already scratched images would suffer more than now, because Devs like sultanxda would have kicked their butts out of the universe by producing better photos than the stock camera app.
Thx for the answer Micky, i like the comparison with the computer and missing drivers, you made it much clearer now!
But 2 questions still remain:
1.) Does a 3rd party photo app (like Open Camera or any other one) lead to the exact the same picture quality if installed on a stock rom as compared to being used on a custom rom? Or will a 3rd party app still be better on the stock rom than on a custom rom because of the drivers you explained before?
And 2.) does this whole camera2 API aspect change what you explained about the driver situation? Meaning, that there is no need anymore for the drivers that can only be found in a stock rom because camera2 API gets to use the whole potential of the camera hardware?
Just trying to figure out where the best image quality can be found. The whole thing is too confusing to me, sorry
@vercetti: Sorry for the late reply. Was kinda busy. To answer your questions:
1: Yes and no. Depends. But pictures will probably visualize it a bit better:
HAL1 (LEGACY):
HAL3 (CAMERA2):
A bit more complex explained: https://source.android.com/devices/camera/camera3
2: HAL and driver are bond together. Without a driver, you can't even get HAL1 to work . But yes: A correct working HAL3 implementation will get you to the point of using your full potential of your camera. Again depends on the driver too . Hard to explain, but the more advanced explanation at Google should answer your questions very well.