Hi I am developing an app in which on long press I will be able to move the icon and on single tap I perform some activities.
The app works fine in mobile phones but does not work completely in tablets.
In tablet it does not detect onLongPess just the single tap.
I actually need to press very lightly on the icon for the tablet to detect onLongPess if I try it roughly as I would in my mobile phone it does not detect at all.
Why is it?. Do we need to handle differently for tablets?
Can anyone please help me? I am pretty sure my code is fine since it runs perfectly in all mobile phones.
Related
I recently bought Galaxy Tab S8 and noticed that it's builtin gesture controls are pretty terrible.
I'd like to build my own system to react to two and three finger swipes to do things such as going back in the app and switch between apps no matter what app is in the foreground.
Is such thing possible? If it is, how to get started?
I have the same website for mobile and desktop devices. One weird behavior I discovered is on mobile devices - Android and Chrome browser.
I didnt have the opportunity to discover exact trigger of the behavior but I think it has something to do with screen turning off.
I have this code before unload. On desktop it works fine.
$(document).on('beforeunload',function(){
$('.loading').show();
})
On phone it works also good but when I minimize Chrome or screen turns off and I wake up the phone. It triggers beforeunload event. Because of that I need to reload the page. I tried also small workaround that clicking on the .loading class will hide it, but with this behavior it doesnt work.
Any ideas ?
I've got a sticky situation. I'm developing a kiosk-style tablet application on JellyBean, and we're stuck with JellyBean.
We don't install a standard launcher on our Android tablets, and instead supply our own Home Screen/Launcher app, so that our application starts on system startup.
We were using a WebView for our GUI app. The WebView that comes with JellyBean is buggy and deficient in many ways, so our app doesn't work correctly in the WebView.
However, Chrome runs our app perfectly, so we want to switch to using Chrome, which we would launch from our own Home Screen application on startup.
We need to start it in full-screen mode, just like Launchers do when they launch any app/URL via a link that was placed on the Desktop.
I can't for the life of me find out how launchers pull this off.
I've tried adding --app="xxx", and/or --start-fullscreen to the /data/local/chrome-command-line file, but all to no avail. The additions options show up on the "chrome://version" screen in Chrome, but they have no effect.
Does anyone have any clue how they manage to launch Chrome in full-screen mode?
These tablets are all rooted tablets, completely under our own control, so no solution is out of bounds.
Thanks for any help!
I'm new to Android development and my first application is looking good.
Curious if anyone has ran into problems with admob:
I have a ListFragment that displays a list with ads at the top and bottom of the list. The display is fine and everything runs ok except -
when I click on the ads and after the browser loads up, clicking back does nothing except for "going" back on the browser and it doesn't go back to the app.
Strangely enough this is happening on my Samsung s3 device but not on my HTC device.
This is because Samsung uses their own custom browser (not stock), and its deciding what to do with the back button. I don't think there's anything you can do- their browser has the focus, it gets to decide what to do with all IO. Your app is in the background and doesn't have any say over IO response.
I'm building an AIR Application for Android devices and I'm using the Camera.
I found a really strange behaviour. When I first start the app and the camera initializes, I get around 1fps(!).
If I then press the home Button and klick on the app icon again, it's all good and I get the full framerate.
This same behaviour also occurs within the Tour de Mobile Flex app when I start the Raw Camera part.
As soon as I press home and then return to the app, everythings fine...
Anybody out there having the same issues and maybe a soulution?
Help is highly apreciated.
This is a bug in Adobe AIR that is fixed and soon to be released.
http://forums.adobe.com/message/3357078#3357078
Set <renderMode>direct</renderMode> in your app.xml. This configuration solve my problem