I am working on an Android App that implements Flash Peer-assisted networking.
I have normal Android controls and a WebView that includes HTML with an embedded Flash player.
Sometimes the flash player will ask for permission (and everything thereafter works correctly) and sometimes it will not ask and will instead hang. Is there a way I can force the Flash player to ask for permissions? Or a way I can add my App to a list that the Flash player accepts everytime?
As an example, this is the box that I need to pop up regularly.
I found the issue. It was simply due to some HTML markup I had used.
I didn't realise that object tags didn't like being terminated like XHTML designates. Removing /> from the end of the param elements fixed it.
Related
Currently making an app that's made to be used in warehouses, since 60% of warehouse workers there use PDA scanners instead of phone, Expo's Camera scanner isn't good enough, and I am trying to figure out the most optimal way to handle those types of scanners, currently mostly the keyboard type ones
So far I tried react-native-keyevent combined with react-native-keyevent-expo-config-plugin, did not work, was just ignored in development and it crashed the test production...
Tried react-native-keyevent by itself after ejecting expo, was still breaking...
The only thing that worked so far was autofocused input that triggers a function with every onChangeText and that function refocuses on it, the issue: after pressing anywhere else, user would have to manually re press the input, ofc I could make it into an indicator whether the user "paused" the scans and make it into a kind of safety feature (if you can't fix it, it's a feature) but since there sure is a lot of pressing around included due to a lot of functionalities included to ease the work, it seems that having to press a "button" aka the input every time you want to continue the scanning work seems a bit off, especially since the purpose of use of PDA scanners over phone cameras is speed
I want to prevent remote screen recording of my app using third party apps like Anydesk, Quicksuppport, Teamviewer etc.
I have used below flag for activity :
getWindow().setFlags(WindowManager.LayoutParams.FLAG_SECURE, WindowManager.LayoutParams.FLAG_SECURE);
but the above flag doesn't work for all devices.
Any other work around for preventing remote screen recording?
The apps you mentioned are operating with either permission of CAPTURE_VIDEO_OUTPUT or CAPTURE_SECURE_VIDEO_OUTPUT. Unfortunately, if they own CAPTURE_SECURE_VIDEO_OUTPUT, then setting the FLAG_SECURE on your window has no effect from their viewpoint.
Sadly, I don't think there is a better (or more effective) way to achieve the desired behavior.
If you make your app a device administrator, then (on certain api levels) you will have the ability to disable screen capturing on the entire device, but setting this up is a lot of hassle, and it's probably not what you want to do in the first place.
I am developing an app using the TextToSpeech class. I'm getting this pop-up on Galaxy Note 4 (Android 5.0) when calling Android's TextToSpeech.speak(...) that asks if I want to download a better quality voice file:
High quality TTS Popup on Android 5, Galaxy S4
This didn't occur on the other development device, an ASUS tablet. How can I somehow prevent this popup from appearing when I use speech to text?
Searching around hasn't revealed much from a development perspective about this popup, or how to prevent it from appearing. I have checked here but it references recording audio and seems to reference a different issue: Android speech Recognition App Without Pop Up
On this particular device I could prevent it by simply accepting the download. That is evident from this, though I have not tried it: http://androidforums.com/threads/download-high-quality-voice-file.789236/ However, when installed on a new device, by the time the speech feature is enabled, the user may not have access to the device. It is a unique case, I suppose, violating normal guidelines for UI. Once the app starts, the user cannot be expected to interact with the app. It receives messages over the internet and speaks those, and this is when the popup appears.
I'm open to solutions that enable me to check and download the referenced high quality voice file myself (in order to prevent the popup, hopefully) and only start speaking once this is handled.
mTextSpeech.speak(s2, TextToSpeech.QUEUE_FLUSH, null);
EDIT:
Is there an INTENT sent somewhere in the loop that the Samsung package is responding to? My thinking is, I could check to see if the "offending" package causing the pop-up is in the PackageManager list, and then possibly go from there. Or if the package has been somehow registered with the system, maybe I could somehow un-register it? I admit I'm reaching here, but I'm sick of seeing this pop-up!
I am working on a project where I am using a set-top-box (Geniatech ATV1220) to display one website (http://goo.gl/1SckBk) on which there are some webkit transitions and other stuff like a video in a carousel.
The box is running Android 4.2.2 and it will only display the site correctly when I use the Google Chrome Browser (v34). The only problems I have with it, is that the Android Google Chrome doesn't have a kiosk mode and that autoplay of the video tag is not supported by intent, so I have to "click" manually to start it. Once I activated it, it will play without a problem in the next rounds of the carousel.
Is there any way to toggle the fullscreen API or get the video to automatically play without user interaction?
If I use the tag
<meta name="mobile-web-app-capable" content="yes">
and then add a site to homescreen I still have the android status bar with the clock and I don't want that. So that is sadly not an option.
I was also thinking about maybe using Webview, since it gives you the option to remove the need of user interaction to play a video, but after my first tries it also didn't display the site correctly, probably because it is not using the chrome webkit version.
Before I dig deeper into it and maybe try to work with chromeview or something I wanted to ask if anyone had some similar needs and could guide me in the right direction on how to continue.
Thanks in advance,
egon
I ended up building a custom chromium content shell with the needed features.
For the fullscreen I did as explained here:
kiosk mode or fullscreen in chromium on android
For the autoplay you have to set m_userGestureRequiredForPlay in the HTMLMediaElement.cpp to false:
if (document.settings() && document.settings()->mediaPlaybackRequiresUserGesture())
m_userGestureRequiredForPlay = false;
I have a mobile web page which includes an input element of type 'file', to allow users to upload image files to a server. The page works fine on iOS, and on a Nexus 4 (Android 4.2.1) in the Chrome Browser.
When I use a Samsung S3 (Android 4.0.4) with the default browser clicking on the 'Choose file' button opens the image selection dialog as expected, however after I choose an image and close the dialog the web page gets refreshed, so I lose the image that was selected. Has anyone else seen this behaviour? Any suggestions for a workaround?
The input element that I'm using is fairly standard, and looks like this:
<input id="addPhoto" type="file" accept="image/*"/>
Even without the 'accept' attribute I get the same problem.
Have a look a this issue:
https://code.google.com/p/android/issues/detail?id=53088
Basically, what seems to be happening is this:
Android does not have enough memory available for the file-chooser or camera app.
It frees up memory by closing the browser
After the file chooser/camera is closed the browser is opened again, triggering a page refresh, which renders the whole file choosing exercise useless.
It seems to me that this is beyond the control of any browser based solution but I would love to be proven wrong on this assumption.
I'm having the same problem on a phone with Andriod 2.3.6. One of my colleagues does not have the problem on his phone (can't recall what that is running). He suggested it may be a memory issue. If the phone doesn't have enough available memory, the browser might actually be forced to reload the page after selecting the picture, which defeats the purpose. I have not yet been able to confirm that this is the problem, but my phone does have considerably less available memory than his.
You could try this JQuery Method: http://blueimp.github.com/jQuery-File-Upload/
Uploadify also looks promising: http://www.uploadify.com/
Here's a demo of it: http://www.uploadify.com/demos/
I think the problem is not your code, but the default Android browser you are using.