Hi guys.
Just curious: what is the state of WP7 self portrait camera? I believe my developer's Samsung Taylor have one. Not 100% sure but it looks like a small camera, not just a light detector.
Tried to use it via Microsoft.Phone.Media.Extended:
videoCamera = new VideoCamera(CameraSource.SelfPortraitCamera);
videoCamera.Initialized += new EventHandler(videoCamera_Initialized);
cameraVisualizer.SetSource(videoCamera);
but getting exception:
System.Runtime.InteropServices.COMException was unhandled
Message=There are no more files.
ErrorCode=-2147024878
StackTrace:
at Microsoft.Phone.Camera.<>c__DisplayClass1.<SetVideoSessionHandle>b__0()
Seems like lack of driver support (I think exception trying to tell us about lack of handles, not a files).
Anybody have any info?
this thread should be in the windows phone development section, not general.
as for front facing camera support, no final phones have it. there was rumour that the taylor did have it (which is what you could be noticing) but my guess is that interop exception means that the drivers haven't been written in, and therefore the API hasn't either. so what you're trying isn't really worth it.
from what i've read, the API for "video" isn't operational yet, only still images.
The Gate Keeper said:
as for front facing camera support, no final phones have it. there was rumour that the taylor did have it (which is what you could be noticing)
Click to expand...
Click to collapse
Agree with you about lack of driver/API support but that stuff (on the left) really looks like camera (sorry, macro from not too good):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yep, that would be a camera. but as i said, because all the final devices (taylor is a developer phone) don't have cameras, you can assume the APIs don't work at present (at the API level or the driver level). But aye, keep what you had in mind (perhaps sudo code it in the app in comments), and then when it does become available it will only take you a few hours or dev and testing, and done.
Related
Inspired by the zoombar projects (link below), I thought that it could be possible to convert the hard button area of the touch HD to a more useful thing: a touch pad.
I think we have enough room for left-right and also up-down movement. Also a double click could be considered as pressing the Enter button.
I believe we have skilled enough developers who can make this dream a reality (like XaKing and namuk).
-------------------------------------------------------------------------
Links to the zoombar projects mentioned above:
XaKing's (works flawlessly on many ROMs): http://forum.xda-developers.com/showthread.php?t=518367&highlight=zoombar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
namuk's (on-going project): http://forum.xda-developers.com/showthread.php?t=515701
Although im no developer, i'd love to see this!
Although, would it only enable in certain applications? Because i want to answer a call when one comes in and not be zooming! lol
Also, if i get a call in camera mode, will it detect this and revert the buttons?
It all comes down to the limits of our imagination. Maybe we could have a blacklist/whitelist approach, where we could define the applications for which this touch pad should be enabled. This could be in some conf file or registry.
But we need the real thing first, these nice little touches could come later.
vizier said:
It all comes down to the limits of our imagination. Maybe we could have a blacklist/whitelist approach, where we could define the applications for which this touch pad should be enabled. This could be in some conf file or registry.
But we need the real thing first, these nice little touches could come later.
Click to expand...
Click to collapse
you are a wise person
Blogging site Xanga just released an app and it's not accessible for anything running 3.0+. As soon as I open the app, I get this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any way of "tricking" the app into thinking I'm running 2.3 or something? I've spoken to the developer and he said they only had 2.3 devices to test with so until they get something newer, they aren't looking into it. Any thoughts?
Sent from the third terrestrial planet in the system Solar from an electronic communications device.
Tell them to download 4.0 simulator... crazy replied from the developer
I told them to root their phones and install an ICS rom.
Sent from the third terrestrial planet in the system Solar from an electronic communications device.
I've found that most developers are pretty good with updating their apps for new versions. Right before the Galaxy Nexus came out I remember my phone/tablet grabbing tons of updates, and usually the update notes would say "Android 4.0 compatibility added".
But there are some developers who have either abandoned their apps completely, or just don't see the need to invest in keeping their apps updated and in tip-top shape. It's a shame, because I feel a lot of them are primarily interested in iOS, and ported their stuff over because of the demand for Android versions, but then don't really think investing their time into the Android version is worth their while.
All a part of the ecosystem I guess. Good thing about Android is that if an app isn't coded to work properly or gets abandoned, there are usually quite a few alternatives.
What do you guys think of this Camera Concept for Windows Phone ? click for more screens via 1800PocketPC
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is out yet on xap
Nice,
when it's ready ?
Did anybody care to read the article or is at least capable of understanding the meaning of "concept"? These are just pictures. The designer is currently looking for developers for this concept.
I don't like it - I think it doesn't fit into WP7.
I was at a conference at Microsoft's HQ where they talked about Windows 8 and Metro.
They took an old fashioned RSS reader and slowly 'converted' it to Metro, as they explain every step. From what I understand, In WP7:
You display on the main area only whats needed - otherwise there's the [...] area for settings and configurations (called the App Bar).
Element design is kept to a minimum - jagged edges are too much, also, the borders around the icons are too much.
The circular elements don't fit well into a squared environment.
It's really nice designed. Shame I can't help, need to learn new technologies I am at .net aspx jquery ajax
This will depend on the OEM pretty much and what the Radio version / Firmware allow the camera to do.
for me its to much on the screen, if the first picture should represent it in use??? the screws are to much and to big. i know it should be like on an DSLR but its to much, it has nothing with metro to do.
I see RETRO here
BTW I could buy as appears in the Market
Mortscript
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment MortScript.zip
IreView attachment IRE.zip
Why not? Whenever app doesn't use HWND APIs, it will run. If it does, it just won't show HWND.
Absent functions is still a problem for some (if not most) of apps.
Please more information
About how to use and benefit from the advantages
AhmedElsharkawy said:
Please more information
About how to use and benefit from the advantages
Click to expand...
Click to collapse
There is explorer.exe (started usually by HKLM/Init/Launch50, it is replaced by simply TellShell.exe TaskBar started by HKLM/Init/Launch40) and some shell missing on WP7 relative to full WEC7, especially screen UI functions and parameters. There are possibilities to include missing APIs by using Platform Builder sources, but it is too much work for deprecated system, because all necessary changes will related to big amout of dependent places. The same answer is to USB Host/OTG/HID support etc. All is possible, but too few experienced native coders is available. May be simple debugging API using application can start most of WCE/WEC applications with simplified UI. There is security hole posssible due to different data and shared code segments between kernel and user mode (callbacks are valid with marshalled parameters), which offers to us all processes memory and code controlling access too. The most simpliest way is to add visual page creating and registering to original WM/WCE/WEC source code, which cause application main window visibility, but it could not solve problem of any missing needed API functions and parameters (scrollbars, start menu, low level support etc.).
I made a module to enable lens from the assistant screen instead of having to take a picture and hit the button in photos. Seems to work fine and I still pass safetynet, it changes the fingerprint to that of a Pixel 2.
I modified it from the Pixel Experience Module, which I tried first, but unfortunately it caused instability and a lot of crashes. I decided to start by removing the overlay and that helped some but it seems that the stock ROM launcher interfered with the scripts even with no launcher selected.
I removed everything but stuff to enable lens, but it has one unfortunate side effect. I'm sure if you have tried any of the non-stock ROMs you seen the camera lose vibrancy with colors. It causes that but to a lesser extent than what I've seen in the past. It's perfectly usable to me, just wanted to let you know.
I haven't tried this on anything but the stock 8.0 ROM with magisk 16.4, but you're welcome to give it a shot.
MD5: 3f90eff0aef1070a4363a380452a86b7
... Please don't tell that lens needs Camera2 API to work. And I'm surprised why it just won't arrive for me in Assistant. Hopefully someone finds a way to make camera usable with Camera2 API. At least on Alberto's ROM it only looks good inside lens. In Moto camera is just jumping around between normal and pretty much b/w
PS: why are you including all those system sounds? They shouldn't be necessary at all and I actually made a module to rename the camera sounds to mute them, that could conflict with your module
No, it doesn't. On latest ROM by Alberto it finally popped up for me.
Working
Thanks, it's working on AospExtented for addison.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}