dngames / mobilewebcam-android Goto Github PK

Good morning , with the latest version if i select to save picture to sdcard 
the pictures are saved into the internal sd card and not the external one.
on my samsung young with android 4.1.2 i fill up the internal sdcard quickly.
please let me know

Original issue reported on code.google.com by [email protected] on 18 Nov 2013 at 3:40

I'd be willing to help document some of the features and options if you would 
post them or give me permissions to edit a wiki page here. E.g. the meaning of 
the sensitivity controls in the motion detection options is very confusing and 
your (very good) explanation is buried in the forum.

Original issue reported on code.google.com by [email protected] on 2 Apr 2013 at 10:46

Thus night time is always enabled.

Enhancement request

What version of the product are you using? On what operating system?

- Version 3.06. Android 4.0

Please provide any additional information below.

I am playing with the app and making mistakes in setting up server names, 
logins and so on. Errors show up briefly on the screen in the mobilewebcam app, 
but most of the time I cannot read them because they are already gone. Please 
add an option to save error logs to SD card and an option to display those logs 
from the app. Thanks!

Original issue reported on code.google.com by [email protected] on 11 May 2014 at 11:26

What steps will reproduce the problem?

Configuring the Picture for Image Imprint (Battery/Temperature) an option is 
given to display temperature in degrees fahrenheit by removing "°C".


What is the expected output? What do you see instead?

As an example; before deleting the "°C", the temperature read 19.5°C. After 
deletion, the number displayed was 8.9. It should be 69.8 or warmer because of 
handling the phone between readings. 


What version of the product are you using? On what operating system?

mobilewebcam v3.13 running on LG Motion MS770 android v4.0.4

Please provide any additional information below.

The problem, I believe, is an error in the code, WorkImage.java, r17 on line 
130, which reads:

float fahrenheit = (float)(temp - 32) * (5f / 9.0f) / 10.0f;

The above line converts degrees F to C and it should be the other way around I 
think. Maybe something like this:

float fahrenheit = (float)(temp * (9f / 5.0f)) + 32) / 10.0f;

Original issue reported on code.google.com by [email protected] on 30 Dec 2014 at 8:10

What steps will reproduce the problem?
1. The camera is set to white balance 'auto'
2. The exposure compensation is 50
3. The sun is not directly into the lens

What is the expected output? What do you see instead?
I've put the camera on fixed focus as it used to constantly crash.
Since then, The camera starts and ends the day ok but is often washed out.

What version of the product are you using? On what operating system?
We're using an HTC Desire camera

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 20 Oct 2014 at 7:47

I see this app is not developed any more. Still I want to let you know, that the Autostart Option in the system settings is not working. Rebooting Android 13 / LineageOS 20-20230214 on a LG V30 ThinQ does not start up MobileWebcam.
I installed MobileWebCam via f-droid store. "run at startup" is in the permissions list for the app.

Dear developers,

We have recently developed a state-of-the-art static analysis tool for uncovering API compatibility issues in Android apps. Applying this tool to open source apps on F-droid, we have exposed a few instances of compatibility issues and submitting them to development teams for a fix.

For your app, we have found that this project has accessed the following APIs which are available only on an API level higher than the declared minSdkVersion and which are accessed without proper protection. In other words, if those APIs get called at runtime, it will trigger a NoSuchMethodError and thus result in a crash of the running application.

<android.hardware.Camera: int getNumberOfCameras()>:[9,25]
<android.hardware.Camera.Parameters: void setFlashMode(java.lang.String)>:[5,25]
<android.graphics.Typeface: android.graphics.Typeface createFromFile(java.lang.String)>:[4,25]
<android.hardware.Camera.Parameters: void setColorEffect(java.lang.String)>:[5,25]
<android.hardware.Camera.Parameters: int getMaxExposureCompensation()>:[8,25]
<android.hardware.Camera.Parameters: java.util.List getSupportedColorEffects()>:[5,25]
<android.hardware.Camera.Parameters: void setWhiteBalance(java.lang.String)>:[5,25]
<android.hardware.Camera.Parameters: void setExposureCompensation(int)>:[8,25]
<android.hardware.Camera.Parameters: void setSceneMode(java.lang.String)>:[5,25]
<android.hardware.Camera.Parameters: int getMaxZoom()>:[8,25]
<android.hardware.Camera.Parameters: java.util.List getSupportedFlashModes()>:[5,25]
<android.app.Activity: void invalidateOptionsMenu()>:[11,25]
<android.hardware.Camera.Parameters: java.util.List getSupportedPictureSizes()>:[5,25]
<android.hardware.Camera.Parameters: boolean isZoomSupported()>:[8,25]
<android.hardware.Camera.Parameters: java.util.List getSupportedPreviewSizes()>:[5,25]
<android.hardware.Camera: android.hardware.Camera open(int)>:[9,25]
<android.hardware.Camera.CameraInfo: void ()>:[9,25]
<android.hardware.Camera.Parameters: void setZoom(int)>:[8,25]
<android.hardware.Camera.Parameters: java.util.List getSupportedWhiteBalance()>:[5,25]
<android.media.ExifInterface: void (java.lang.String)>:[5,25]
<android.hardware.Camera: void getCameraInfo(int,android.hardware.Camera.CameraInfo)>:[9,25]
<android.hardware.Camera.Parameters: java.util.List getSupportedSceneModes()>:[5,25]
<android.view.MenuItem: void setShowAsAction(int)>:[11,25]
<android.media.ExifInterface: void saveAttributes()>:[5,25]
<android.media.ExifInterface: void setAttribute(java.lang.String,java.lang.String)>:[5,25]
<android.hardware.Camera.Parameters: int getMinExposureCompensation()>:[8,25]

Note that, because of the nature of the static analysis, we cannot confirm whether the flagged APIs would actually be called at runtime (e.g., unreachable code). However, we still believe that those APIs, which may cause compatibility issues, should not be accessed or at least be accessed with proper protections.

In addition to the aforementioned APIs (i.e., backward-compatibility), which could cause app crashes if accessed, we have also identified that this project has also accessed some APIs that have been removed from the latest public SDK, making the app possibly suffer from forward-compatibility issues.

<java.lang.reflect.Array: java.lang.Object newInstance(java.lang.Class,int[])>:[1,8]
<org.apache.http.HttpResponse: org.apache.http.HttpEntity getEntity()>:[1,22]
<org.apache.http.impl.client.AbstractHttpClient: org.apache.http.HttpResponse execute(org.apache.http.client.methods.HttpUriRequest)>:[1,22]
<org.apache.http.conn.util.InetAddressUtils: boolean isIPv4Address(java.lang.String)>:[1,22]
<org.apache.http.auth.UsernamePasswordCredentials: void (java.lang.String,java.lang.String)>:[1,22]
<org.apache.http.auth.AuthScope: void (java.lang.String,int)>:[1,22]
<org.apache.http.Header: java.lang.String getValue()>:[1,22]
<org.apache.http.entity.BufferedHttpEntity: void (org.apache.http.HttpEntity)>:[1,22]
<org.apache.http.HttpEntity: org.apache.http.Header getContentType()>:[1,22]
<org.apache.http.client.methods.HttpGet: void (java.lang.String)>:[1,22]
<org.apache.http.entity.HttpEntityWrapper: java.io.InputStream getContent()>:[1,22]
<org.apache.http.impl.client.AbstractHttpClient: org.apache.http.client.CredentialsProvider getCredentialsProvider()>:[1,22]
<android.app.Notification: void setLatestEventInfo(android.content.Context,java.lang.CharSequence,java.lang.CharSequence,android.app.PendingIntent)>:[1,22]
<org.apache.http.impl.client.DefaultHttpClient: void ()>:[1,22]
<org.apache.http.client.CredentialsProvider: void setCredentials(org.apache.http.auth.AuthScope,org.apache.http.auth.Credentials)>:[1,22]

We would be very much appreciated if you can acknowledge to us that those reported APIs are indeed problematic for the project’s long-term stability. please let us know if you need any more information relating to this issue report.

What steps will reproduce the problem?
1. Set picture sending mode to HTML
2. Enable sending log file with every picture
3.

What is the expected output? What do you see instead?

- Expected to get the picture and the log file uploaded. Got only the picture.

What version of the product are you using? On what operating system?

- version 3.01-04. On Android 2.3.7.

Please provide any additional information below.

In ftp mode, it is nice to get the log alongside with the picture. The same is 
needed for the HTML mode. Thanks!

Original issue reported on code.google.com by [email protected] on 11 May 2014 at 10:12

What steps will reproduce the problem?
1. I want to know if we want to use Samsung Gear along with Galaxy S5 .
Instead of activating mobile camera ,Can it is possible to activate Gear camera 
so that we take snaps 
of picture where ever we move our hand and focus for given time period.
. 

What is the expected output? What do you see instead?



What version of the product are you using? On what operating system?

Samsung galaxy  S5 and gear 
Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 5 Jun 2014 at 1:38

I have just submitted the app to f-droid.org, a catalog for FOSS. The only 
changes made were to add a dummy Admob library and remove proguard from the 
project.properties. I tidied up the description so please look to see if you 
are happy with it. I wish you would make the server files available from here 
as it is tidier. If you have a donation address you can add that and please add 
an official statement about the license to the source code. Thanks

Original issue reported on code.google.com by [email protected] on 1 Dec 2012 at 2:25

If you choose to remove/clear the "image imprint" which sets Date and Time on 
each photo and then later want to have a Time Stamp, you are not prompted with 
the same text and it is difficult to remember/guess what to put back in. 

Maybe include a small example label with input boxes? 
something like this: 
http://www.thatwebguyblog.com/post/15-steps-towards-better-form-usability/#dont_
force_formatting

Alternatively maybe instead of a text input box you can put some kind of date 
input box, or just accept whatever date format has already been set by the 
Android System Settings - Select Date Format option? 
(I'm not very familiar with Android programming and I know you want to keep the 
app widely compatible with older versions too, so just making suggestions, 
don't know what the best way to implement it would be.)

Original issue reported on code.google.com by [email protected] on 22 Jan 2013 at 10:42