I noticed something strange after implementing and testing a settings screen for my TV app using the LeanbackSettingsFragmentCompat class, please see attached image:
As you can see, after navigating with the remote to other items, the items no longer in focus still retain their focused background state, I was only able to reproduce this behaviour on one device, and it rarely happens
This problem has left me a bit perplexed,as this is not my implementation but rather Leanback's.. But still, I have never seen a TV app with this problem
Has anyone ever encountered such an issue? Could I have made a mistake to cause something like that?
I would be happy to share code, but at this point I don't know if my code is even relevant to this problem
Thanks in advance
Related
This problem happen after android studio suddenly close itself. I feel relieve when i see the interface output can show it's text but, it annoy me when i try to codes the interface and there is no text shown there. How can i solve this problem and what make this problem occur?
I already solve this problem by use the new render layout. I kind a hesitate to use it at first because i have face this problem before and it is also render problem. No matter how many time i change my codes according to suggestion and change the render layout. Still nothing works. I need start from scratch because i can't find the solution. But this time it's work.
I'm having a weird bug that I'm not sure how to debug. I have have an activity set up to show movie trailers and reviews. Everything looks and works fine when the app is initially started unless I navigate away from the app to another app or youtube to watch the trailer. Then when I come back into my app the trailer names and reviews are all out of the original order and just messed up (some are duplicated). However when I click on the the trailer name (that is now incorrect) it takes me to the correct trailer! Also when I come back to the app if I try rotating the phone sideways it won't rotate. Rotation and everything else works perfectly fine before I navigate away from the app and come back. I'm so confused. I've tried different onSaveInstanceState etc. implementations but nothing is working. I don't even know what code snippet to post since I don't know where the error could possibly be occurring.
Yup as David Wasser wrote above the issue was with my adapter and nothing to do with onSaveInstanceState. I was assigning the textview in the incorrect method of the adapter (I was assigning it where I defined my viewholder and not on the onBind method) so it wasn't being handled properly.
I am building a small site and ran into a small problem. I am using MixItUp to filter and sort blocks. I am also using a search field to search through the titles of each block and display relevant ones. Everything works fine on all devices and browsers except for Android.
On Android when I tap into the search field my keyboard slides up and then slides away again without giving me a chance to type anything. I tried googling the problem and only relevant thing I could find was this post but I am not sure how to proceed because I have no clue what event listeners would be disrupting the android one.
I am not a very experienced developer (self-taught and still learning lots) so I am not sure how I would go about correcting. My plan right now is to just remove pieces of code until keyboard starts working and then go from there once I identify what is causing it.
The Website is teste3.khalidsleiman.com
I figured out it was a jQuery snippet that I was using to relocate the input field to a different spot on my page depending on window size. Now I only have it set to run that snippet on document load instead of window load and resize. Keyboard is showing up now.
I'm devolopping a tablet app. I want it to work full screen. After days of investigeting on google, I achived it using:
.getWindow().getDecorView().setSystemUiVisibility(View.SYSTEM_UI_FLAG_HIDE_NAVIGATION);
.getWindow().getDecorView().setSystemUiVisibility(Window.FEATURE_ACTION_BAR_OVERLAY);
.getWindow().getDecorView().setSystemUiVisibility(Window.FEATURE_ACTION_MODE_OVERLAY);
The Tablet I'm using is 4.1 Android version. That was working perfectly though I had to made some changes like doing my own action bar (because sistem action bar made navigation buttons comes up) and dialogs.
Now the problem is that I've installed my application on 4.2 Android version and it's a disaster. Each time I touch the screen, navigation buttons comes up. It's really annoying. This is driving me mad, I've tried many things but it's still coming up.
Is there a way to solve this problem? I think if I could override the method that makes navigation buttons comes up I could achieve my objective. Anybody know which is this method??
It is not working in 4.0 Android version neither. That doesn't bother me much, but if you know a way to solve it as well, that would help me a lot.
I would appreciate any help. Thanxs a lot.
Each time I touch the screen, navigation buttons comes up.
One of the core Android concepts is that the user is always in control of the UI. If developers were allowed to create fullscreen Apps and override the navigation buttons, it would be trivial for an App (rogue or otherwise) to create a screen which the user could not get out from.
If you really want to remove the system bar, you will system-level access or you need to build your own custom Android.
I feel like an idiot for having to ask this question, but I have no idea what a slider interrupt is on Android, and a search of Google and Stackoverflow turned up nothing. Amazon sent me a rejection notice for my app because all of the activities except the main one (which they call, "pop up windows") do not respond well to a slider interrupt. I have no seekbars anywhere in the app, so that isn't the "slider" that they are referring to.
Also, one of the views in question isn't a new activity at all, but a listview. It disappears on a "slider interrupt." As far as I know, I have no control over what a listview dialog does in this case. Once I figure out what a slider interrupt is, how do I tell the listview not to close when it happens? I suppose I could track whether the listview is open and recall in onResume or whatever function handles slider interrupts. But without knowing what a slider interrupt is, it makes testing difficult.
I had the same problem with Amazon. I filed a ticket and here is the response:
A slider interrupt occurs on devices with a flip-out keyboard. While the app is running the keyboard is flipped out.