I would make sure that my application for devices Android Wear the first element of my WearableListView is selected by default when i start the application. I tried everything but without success and the many guides that I find on the web dealing with this subject for a normal ListView NOT for devices WearableListView primed for Android Wear, thanks in advance.
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 am creating my first Adobe Air application from a Flash animation file via Flash Builder (I am an Android developer by trade.) One of the last updates I had to make was updating some of the text fields within the app to be dynamic so their text can be set at runtime via ActionScript.
When I view the app via the Adobe Air Simulator or push to an iOS device the buttons work fine, but when I push to an Android device some Buttons and Movie Clips are invisible. I can still click on the buttons if I touch where they should be on the screen but I cannot see them. In my testing of a fix I set the alpha of a button which is affected by this issue to 100 but it still shows as invisible.
Is this a known issue? How would I go about ensuring that all Buttons and Movie Clips are visible to the user?
Thanks,
Adam
Edit:
The only change to my code in order to set the text is running the following AS:
play_play.text = TranslationUtils.getTranslationText(TranslationUtils.PLAY_PLAY);
The AS for the TranslationUtils class is an external AS file which switchs through constants to return the correct text, based on the device's Capabilities.language
I was able to inspect and interact with (update css) on my android devices using chrome's device inspector then a week or so ago it stopped working. I can still see and interact with devices somewhat, but the styles pane never changes to reflect the element I have selected, and selecting elements is more difficult. Use to be a single click, now its a double click and even that doesn't always work - and when it does finally work, the styles pane still doesn't display the attributes of the element I've just selected, just stays at the root of the document from when page initially loaded - so I can't edit DOM properties as I was able to do.
I've deleted Canary and re-installed, but still have this issue. Has anyone seen this before and found a solution?
I implemented a TextView with a custom ActionMode.Callback, where I add an item to the menu if certain criteria is met. This works like a charm on most devices (N4, N7, GS4) but now I noticed that it doesn't work on The LG G2. I don't have other devices to test it on, but LG has implemented the default TextView- ActionMode in a way that the menu is not shown in the actionbar, but on top of the selected text (much like it happens on iOS afaik) and I'm wondering whether somebody else had this experience and how I could solve it?
(Maybe it would also help to let me know of other apps that use a custom TextView action mode, so I can check, whether they work properly on this device, I couldn't think of one yet...)
Thanks,
j
I found several other posts about the same behavior on HTC (sense) devices, and there was not a solution which somehow forces those stupid custom android versions to behave the way it's supposed to...
So I ended up adding the functionality in another way :(
We have a Web application that dynamically builds elements via JS. We are testing for mobile usability and are finding that on devices that run 2.3.x versions of Android, our select element behavior is a little strange. A touch on the select element will bring up the usual radio button list of the options and touching an option will select it and return to the page view. However, the option shown in the select box does not update. It still shows the top element in the option list. When the page is reloaded, the behavior is normal. I have tried adding an additional empty element at the top of the list and setting it as selected when the element is built, which seems to clear up the issue on some devices, but our QA tester is saying that behavior remains on others.
Any ideas?
If you're fishing for areas to look into, I had a similar issue for select elements when using the fastclick library in any Android 2.3.x browser. The issue was caused by a hack in fastclick for it to work better under Android Chrome. The fix for native browsers hasn't been merged to this day (https://github.com/ftlabs/fastclick/pull/190).
On another note Android 2.x can be a nightmare in unexpected places once you start adding an assortment of everyday things - CSS animations, opacity, negative margins outside the screen etc