I have an app which does some really strange thing on Lollipop (never occured on other versions). Sometimes the screen textures just go crazy. It looks like this. In fact there should be pretty standard toolbar and list with two items in it (rows have Switch on the right side). Instead whole screen looks like a broken analog TV. There is not anything suspicious in the log. It is all OK when I restart the application. This bug occurs "randomly" in approximately 1 in 50 runs of the app.
Have you ever seen anything similar ? Can it be some bug in Android ?
Related
in my current app i have a strange effect. Throughout the whole app the touch feedback is some kind of broken. It seems that at a touch an image of a shadow is rendered onto the elements. This only happends on API 20 and lower.
Any idea what can cause this effect and how to fix this?
Edit
I think i finally solved it. I looks like it somehow depends on Java 8. Since i switched back to Java 7 the problems are gone.
Following up on my previous post on animation trouble (Codename One Animation Trouble (also in Solitaire demo)?) in my app and in the Solitaire demo. The simulator and iOS problems are solved, but there remains the issue on Android devices. (Test: Nexus 7, Android 5.1.1; CN1 3.3.1)
In my checkers app, when the computer makes a move, the checker starts moving but the destination square briefly flashes (while the undo/redo animations work fine). This is similar to what happens in Solitaire: when a card starts auto-moving, but only if it is the second move or higher in a row, the card it will land on top of usually flashes (as if the button is pressed?). This also happens in the deal-from-deck animation (many moves in a row).
In my app it looks like the checker is very briefly (one frame?) shown at the destination location and then it starts moving from the source location to the destination location as it should. The same probably applies to Solitaire.
In issue #1640 you mentioned:
'This is probably related to the Android pipeline work we are doing and has nothing to do with the animation framework. We'll take a look at that and try to figure out what happened there.'
When is the improved Android pipeline scheduled?
Would you like me to submit a new issue for this?
I think this works better with issues ideally with smaller scopes (one issue per post) and ideally with a simple test case the demonstrates the issue.
The issue tracker is probably a better place for bugs than stack overflow.
So, this is an odd one.
I have implemented a custom ScrollView that allows drag and sort operation on a list of items by intercepting touch events. This works well enough on three out of four devices that I have tested on.
On Dell 7 tablet running 4.4.2, the behavior is really strange. The movement while dragging is rough. And in the middle of a drag, the Google Keyboard crashes. This happens irrespective of whether the keyboard is currently open or not. And no exceptions are present in my logs. The app continues to function as before - perhaps a bit more smoother - this happens once after the activity starts - on the first drag operation. After this, the keyboard and the drag-sort work as expected.
There were a few mentions of spell-checker events (not sure if they were indicative of an exception) in the System and event log included in the crash report. These spell-checker log statements were output right before the keyboard crash. So, I checked whether the spell check was turned on. The three devices on which the app functioned fine had the spell-check off. Only the Dell tablet had the spell-check on.
Next, I turned off the spell-check on Dell tab and the keyboard crashes stopped. This is very unusual, and I can't wrap my head around it.
Has someone experienced this behavior? If there exists a bug report detailing the issue, it'll be great if someone could point to it.
Thank you for reading. I did not include any code because I don't know what the relevant part(s) would be.
I know this question was asked about 10 times here but none of them came to a solution. I don't want to use the low light SystemBar Mode I want it completely to fade out. And this is possible! The default launcher that comes with Chinese Rockchip devices does this. (It looks like the systembar just flies away into the middle of the screen). Any (new) ideas?
Since API 17 this is directly possible, just select FullScreen Activity when developing an app with Eclipse.
I have a very simple Android app. It is one Activity with Text and Buttons, and as you click on the buttons (onTouch events), they become invisible and the text changes.
This works fine for Android 3 and Android 2.3.3 simulators, but when I use the BlackBerry nature in Eclipse to send the app to a BlackBerry playbook simulator, funny things happen. As I click on the buttons they go invisible, but other buttons change too.
Buttons that were only ever visible, stay visible. Some Buttons that were invisible, become visible. Some buttons that had become visible earlier, return to being invisible.
It feels like a redraw problem, or some strange caching on the button state.
Anybody got any ideas? Wild guess excepted ...
Get a playbook or wait until RIM updates their broken simulator.
I converted an app for the playbook and the code was running fine on the simulator. It's a very simple app too, like a binary calculator. A couple of toggleButtons, Buttons and a TextView.
The app had visual issues, similar to yours. Buttons disappeared. Buttons were highlighted when I pressed buttons around them. ToggleButtons didn't change state. And much much more.
Since I don't have a playbook I couldn't test it on a real device. I tried layout changes, code changes and tried different settings. But nothing helped, those issues stayed.
After some reading in their forum I came to the conclusion that this might be an issue with the simulator.
So I submitted the app to the AppWorld 5 days ago. It got approved today.
So there is a chance that your app is alright, and the problem is the simulator.