Wie kann ich die Benutzung der Kamera durch Programme erlauben

    Peter
    Sorry, of course you are right.
    I didn't know, that there should be 2 views.


    I also only have got one.:(


    My fault:(

    Dear JoTo,


    Thank you for your kind words. Your description is most clarifying, and
    matches my expectations about the artefacts caused by the firmware bugs.
    The switching back and forth between the different views is a consequence
    of the video capturing and display painting running asynchronously under
    firmware control, which becomes noticeable now that the two are misaligned.
    Your observation that the small high contrast view shows approximately
    the top left part of the full camera view is also consistent with what
    I'd expect. Actually my tunnel vision analogy was not entirely correct:
    it is more like an unintended zoom effect as with a telescope, where you
    get a higher acuity for distant items at the expense of the peripheral
    view. The small view is by default a high contrast greyscale view. It is
    positive (default) or negative depending on whether or not the negative
    video mode was toggled by key "1".


    A German or international version will probably come someday, but not
    anytime soon, because of the maintenance drag of ensuring consistency
    across languages while developing. For that reason I also do not offer
    a Dutch version (my own native language).


    I much appreciate your offer to help, and I will definitely remember.
    Your current clarification was already most helpful in confirming the
    expected side effects of the series 60 third edition firmware issues
    that I was only recently made aware of.


    Also thanks to hecke. I will update my documentation a bit, because
    indeed one could not readily know the intended behaviour in advance.
    For now we can only hope that Nokia fixes the series 60 third edition
    problems for their various phones through some firmware upgrade, but
    they rarely announce what they fix with what upgrades. For reasons
    like these, and because it is not feasible to test each and every phone,
    quality user feedback such as provided through this forum is extremely
    valuable for developers. It is really appreciated.


    Ich sollte mal besser Deutsch lernen, aber die Zeit fehlt mir leider...


    Vielen dank!


    Peter Meijer

    Hello Peter!


    Soweit ich das hier lese, ist Dein Deutsch doch recht gut! Weiter so - trau Dich! :D


    Concerning the topic, I only want to confirm JoTo's experience, just on my N95 with FW 20.0.015. V1.24 works with one big image flickering/switching to a smaller image and back.


    Sorry for not having a better reply! :rolleyes:


    Kind regards

    N95-1 @ 20.0.015 // 16GB µSDHC // Power.Guy D.2200

    It wooooorks!!!


    Dear Peter,


    now it's my turn to confirm Heckes finding.


    On my N95-1 FW 21.0.0.16 the V 1.25 of The voICe works when it comes to the graphics now. Thank you very much.


    Only thing i discovered is, that an old error is back now. When i start the app with the camera shutter already open, the new version again falls back in this, from you so called "compatibility mode", and asks for permission to use the camera. Then it demands a setting change to allow it, even if this setting is already set correctly, and shuts down the app.


    This problem can be circumvented, when you start the app with the shutter closed. Then, after the app initialized and shows the first (of course black) images, you can safely open the shutter and close the then opened camera app again. Then you are back in The voICe and it works like charm.


    Maybe you can have a look for this compatibility mode problem once again and make it work with the already opened camera shutter as well. But thats not a vital problem, as there is the a.m. workaround.


    Thank you again for your good work. Now i must learn to "understand" the "language" of the app. :-))


    Bye
    JoTo

    Thank you for checking, JoTo, and of course also hecke!


    The "old error" has to do with trying to support a few Nokia series 40 phones that cannot handle the new tricks of series 60 phones. Unfortunately, Nokia does not offer any methods to directly determine from software whether a phone is series 40 or series 60, so I check for a black view instead to judge which mode should be used. However, this workaround can lead to the wrong conclusion when the lens cover of a series 60 phone is closed, since that also gives a black view (short of some image sensor noise).


    Intended usage was that you open the lens cover, next quit any built-in camera app that comes up automatically, and then start The vOICe. That should prevent that it lands in its compatibility mode. Therefore I do not quite understand how for you it seems to work just the other way around, requiring you to start with the shutter closed. Maybe the interaction with the built-in camera app is different on N95 such that The vOICe reads a black view and falls back into compatibility mode when the built-in camera app is active, I just don't know. These things are difficult to test and figure out without access to the physical device, and my old Nokia 6682 stubbornly refuses to fail on this issue. :-)


    Danke!


    Peter Meijer

    Compatibility mode and N95


    Dear Peter,


    yes, it sounds strange, but you understood exactly perfect. For me it works just the opposite way as you expected.


    Shutter open and camera app exited before The voICe -> Ask for permission and exit immediately


    Shutter closed before The voICe -> works and shows a black image -> open shutter -> close camera app -> the voICe works fine


    After your explanations i did one more test and that confirms your sayings. I can also open the shutter and close the camera app before starting the voICe without problems when i cover the lens with my fingertip to simulate the closed cover. So it hast definitely nothing to do with the N95 camera or camera app initializes sth. that the voICe needs or disturbs the voICe's initialization or sth. like that. Its only your "black image detection" that makes the difference.


    Thanks again, as this way (covering the lens) is a bit more convinient for me.


    But the strange thing keeps alive...why is my finding exactly the opposite of what you expected? *Shrug*


    But as i said, as i know whats going on under the hood, i know this trapdoor and can circumvent to fall in it with ease and still use the app now.


    You're great!


    CU
    JoTo

    Thanks JoTo. I'm checking the code, thinking of ways to explain your observed behaviour. Another way in which The vOICe can currently switch to the unwanted compatibility mode is when the initial view is totally overexposed, meaning perfectly white, before the automatic white balance of the camera kicks in. Any sighted N95 user who can tell what the very first preview image of for instance the built-in camera app tends to look like? If it is perfectly white then I understand the problem and can fix it. Otherwise I am still baffled. Initial overexposure could explain why you get The vOICe to run properly by covering the lens with your finger: that would prevent the initial overexposure, but it is also nearly impossible to create a perfectly black view by covering the lens with your finger, which is exactly what is needed to keep The vOICe from switching to the unwanted compatibility mode. If nothing else works then I will probably remove the automatic switch, but preferably I create something that works on as many phones as possible without user intervention, so I am eager to understand how the N95 falls into this "compatibility trap".


    Vielen Dank!


    Peter

    Just in case the overexposure "theory" would indeed hold up, I have temporarily added a test version 1.25.1 at the direct JAR file URL


    http://www.seeingwithsound.com/The_vOICe.jar


    that will only check if the initial view is perfectly black (and then fall into compatibility mode), and it will no longer be thrown off track by any overexposure.

    Peter

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden