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.
Related
I have an app that uses Chrome custom tabs for third party auth sign in. The problems is is that when the custom tab is asked to open the url, the tab closes as soon as it's opened on an emulator, and only stays visible for a "split second". On a real physical device, it works fine and the custom tab stays open. I have had this working on emulators previously, but as a newbie Android developer, I do not know what can be done to try and pinpoint the problem.
Is there any configuration or setup needed to make custom tabs fully functional on emulators?
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 have a Jquery mobile app that loads one view on a changePage event inside of a webview and then loads another view when input is received from the user and a button is clicked. The first changePage event loads fine. However, the second changePage event does not show any content. The screen changes only to a blank, white screen.
This issue only appears on Android 2.3 +. I have enabled hardware acceleration. The weird thing is that the first view (a login view) works fine. It only occurs when I do a second change page event. This app works great in a standard browser and also works good on the iPhone. I get the same issue when using an Android emulator.
My Worklight version is: 6.1.0.00.20131219-1900. I am able to port this app to iOS 7 and below. It just is not working completely on any Android device that I test with.
Anybody have any idea on what needs to be tweaked to get this web app to continually load in a web view? Any help is appreciated.
After receiving your project and doing some investigation I believe I have found the cause of this issue. Inside of your application you make a call to a load a specific view (normal view in your case) in a changePage event after an event is triggered (a button click). The problem is that when you referenced the view in your code it did not match the correct name of the view you were attempting to load. Please make sure when referencing these files you have the correct spelling and correct case structure.
I have an app in development that runs fine in the emulator but wont run on any android device, when the application icon is clicked the screen goes blank for a second then returns back to the device apps page, i have experimented with setting different permissions but it does not seem to solve the issue. Any ideas?
Using Android 2.3.5 Gingerbread built in browser. Created an offline cached app using html5.
When I turn the network off, the pages seem to cache ok but moving from page to page I get a message warning me there is No Network Connection (with settings / OK buttons). If I press OK you can move to the next page (also cached) but my users are not happy having to press the OK button every time they go from one cached page to the next.
On a an Android 4.0.4 tablet, the internal browser does not generate the message when network is off.
Can anyone confirm that this is standard Gingerbread behavior for a cached HTML5 app or did I do something wrong? Is there any low level setting to suppress that message?
My only other thought is to cram all the pages into a single page and show/hide them rather than navigate from page to page. Or just build a native app.
I'd switch to Chrome but it won't run on Gingerbread.