Our android app user reported they had display error situation like the picture below, on some tablets like these 2 :
Sony Xperia Z3 8 inch,
Google nexus 7 2013.
Both are Android 6.0.1, 1200x1920 resolution.
Is there any special setting needed to some tablet, Android 6.0.1 or resolution 1200x1920? Or does anyone has similar desynchronization happened on your app?
This display error is not reported on phones. Most of phones' resolution are 1080x1920 or less.
this is the screen shot
We've found the root cause. It's because we use the solution below to detect soft keyboard appearance and then hide some views. When the views are hidden, the value of "activityRootView.getHeight();" will become bigger. So, the threshold of "dpToPx(this, 200)", to check whether soft keyboard appears, need be carefully choose.
How to check visibility of software keyboard in Android?
Related
I need to develop an app including feature to add widget on lock screen.
I tried that on 3 devices so far -
1) Samsung Galaxy s4 (KitKat 4.4) - It worked well, if the lock is swipe screen lock,
but doesn't work in case of pattern lock. Even in case of swipe lock, I am unable to add it on main lock screen, instead it appears on second or third screen, navigated from the main lock screen to its right.
2) Samsung Galaxy Grand (JB 4.2.2) - same behaviour as above.
3) LG ls970 (JB 4.1) - It doesn't seem to provide lock screen widget feature at all.
So, what must I do in case I need that to be worked in most of the devices.
What may be the issue by the way - Is it version specific issue or the brand specific or both.
Please let me know the solutions.
Thanks
Lock screen Widgets is not provided by "default" in "older" versions of Android.
Speaking of older - ALL DEVICES THAT ARE >= Android 4.2 SUPPORT lock screen widgets.
OLDER devices < Android 4.2 does NOT SUPPORT this feature. That's the problem
You can get more information on this topic here: Lock screen Widgets
And btw, make sure just to read more on the Google's provided information about Android. It supports search too!
Basics of Android by Google
I have two devices in my GenyMotion application. One is nexus 7 4.2.2 API. The other is a saumsung galaxy s4 4.3 API. The nexus emulator starts up fine and works well. However when I tried starting the s4 emulator, the android loading screen doesn't even show up, all i get is a black screen. When I go to DDMS, the devices tab tells me that the samsung galaxy s4 is online and debuggable. Does anyone know how to fix this issue? It make more sense if both show a black screen but why does one show a black screen and the other doesn't. I don't see anything out of the ordinary in the console.
I just tested this, and notice the blank screen is due to Genymotion version mismatch. Once i downloaded the latest genymotion (v2.3.0) , i was able to see Galaxy S4 startup properly.
If you do not see the navigation bar, you can manually enable it in Configure virtual device, see below.
this worked for me : In Configure Virtual Device (as shown in ashoke's answer) I changed Screen size to one of predefineds resolutions.
I am seeing a difference between what TalkBack reads out loud when a screen is displayed on a Nexus 7 (4.4.2) and a Samsung SGH-I317 (4.1.2).
On Samsung SGH-I317 (4.1.2) when a screen is displayed some elements
are read out loud but not all of the elements displaued.
On the Nexus 7 (4.4.2) TalkBack reads only those elements that are specifically
selected/tapped.
Is this a Samsung/Nexus difference or an Android 4.1.2/4.4.2 difference?
What is the expected behaviour when a screen is displayed, should TalkBack read all the elements on the screen or just read what screen is displayed and leave it to users to touch a UI element before it is read out?
Android 4.1.2 (early JellyBean) and 4.4.2 (KitKat) are significantly different versions of the Android OS and you should expect different behavior. Additionally, unless you have manually updated from the Play Store, the devices will be running significantly different versions of TalkBack.
I have upgraded my Motorola Atrix to Gingerbread (2.3.4), so far with no issues. When I go for my old apps and games which I developed previously, those are not displayed fully in the screen, it is only giving a 320x480-pixel display. Do I need to change my code or my phone settings?
Given that you currently use android:minSdkVersion="1", try setting minSdkVersion="4" or setting anyDensity to true.
Both should have the same effect of allowing your app to scale beyond Android 1.0 screen sizes of 240x320; before SDK 4 (Android 1.6 ) the default was not to scale as there was only a single resolution.
How can I build a standard ADV to test my Hello World app. I've just built my Hello World app on Android - using eclipse, and am having real problems getting the AVD to work properly. My setup Android 3.1 level 12, and I set the skin to 800 x 600 as the default WXGA, seem to make a massive screen. When it loads, I get just the Android screen but no side keyboard.
In addition, why do I get completely different looking skins when I play around with the skin size. Sometimes, I get a nice sea scape sometimes, but its portrait not landscape - how do I turn it? One time I get a lock?
Any help would be really appreciated. (I using Java 1.6 64 bit).
Thank you very much.
Ed Ryan
My setup Android 3.1 level 12, and I set the skin to 800 x 600 as the default WXGA, seem to make a massive screen.
Use the scale option when launching the emulator to resize it to something manageable. There are no 800x600 Honeycomb devices, so you are far better served using WXGA.
When it loads, I get just the Android screen but no side keyboard.
Correct. You won't get the side keyboard for WXGA, either. You do not need it, as everything on that side keyboard is available to you from your own physical keyboard on your development machine.
The skins are only available for the out-of-the-box skins or the ones you create manually (see here). However, you can access all of the keys using other keyboard shortcuts, which I personally found way more convenient. Plus, you save space.