My code right now downloads an animated gif from a website, and since, as far as I know, webview and imageview doesn't support animated gifs and using BufferedInputStream and Movie.decodeStream along with a custom View to render it (this code runs in a seperate thread)
I have tested the code on the android emulator (1.6, 2.1, 2.2, 2.3.3), Xperia X8 with 2.1, ViewSonic viewpad with 2.2 and Galaxy S with 2.3.3 and the activity only crashes on the Galaxy S (after like 1 minute). On the other devices it's working just fine.
I've tried debugging the app on the Galaxy S and I get this message just before it crashes:
11-17 13:37:18.152: ERROR/(1161): Wink AGIF pDecInfo is Null or not avail
That's all I get when debugging :(
I've tried changing my code back and forth but I can't get it working. Anyone have any idea what's wrong?
We also have some problems with Samsung devices. I was told that Samsung heavily modifies original Android source code so they seem to introduce many bugs.
Related
I'm writing an app that I've been testing on my Nexus 5 with Android 5 and in the emulator on different DPI and API levels. While some UI magic is missing on pre-L Android, everything worked just fine and I know how to work around these missing parts (e. g. implement touch feedback etc.)
I've implemented RecyclerView and CardView from the support library which worked just fine on my device and the emulators. There is data being fetched from the web so the "list" is being filled upon launch.
Now, I've tested the app on a LG G2 mini running Android 4.4.2. The UI is not being updated. The items are added, but I have to leave the Activity and come back again before I can see them.
This sounds like I've been missing runOnUiThread, but I didn't! Furthermore, why is this working on stock Android but not on an OEMs mod?
I working on my first Android app (published on iOS and Windows Phone before). When testing the app on a Nexu 5 eveything works fine but on a Kindle Fire the app crashes:
java.lang.IllegalStateException: Cannot add header view to list -- setAdapter has already been called.
This is NOT about the exception itself. I could easily solve the problem by simple using listView.addHeaderView(...) before using listView.setAdapter(...). Not a big deal, but why does the same code runs without any problem on one device but crashes on the other?
I would understand the problem if the devices would use different Android/SDK versions but this is not the case. Both devices run Android 4.2.2 with SDK Level 17...
I would understand the problem if it would be related to something close to the hardware or some vendor specific system calls, but this not the case. It is just about setting up a ListView...
So, what is the difference?
Of course I have only a limited set of test devices. How can I be sure that the app will work on all devices that are running a supported SDK Level?
EDIT:
Of course one device is a phone and the other a tablet. To app uses different layouts for large screens at some places but problem also shows up in Activities/Fragments that have the same layout on both devices. Additionally no separated code for large devices is used. Using the same code and the same layout on both devices leads to a crash on the Kindle but runs on the Nexus...
The Camera on my galaxy s2(Android 4.4.2) looks like this when i run the color blob sample code. The same code works on my galaxy tab 2 (also Android 4.4.2).
Tried with writing the code from scratch and other sample codes. There are no errors on both devices, but the image looks like this on the S2
Does anybody know how to fix this?
I have the exact same result running OpenCV Samples on my S2 i9100 with Neatrom 3.6 (4.4.2) and ART enabled. Changing ART back to Dalvik does not change anything (for what it`s worth).
Using Stock Samsung Rom fixes the problem. Seems to be something in the Custom Rom which causes the problem.
After some testing this seems to be the only working Rom for me.
I checked without success the following Roms:
CyanogenMod 10.1
CyanogenMod 10.2
CyanogenMod 11
SlimSaber 4.4.2
Biftor™SlimKat-Rom-V6.0-i9100-4.4.2
I9100_4.4.2_AOSP_NeatROM_v3.6
SlimBean 4.2.2
I currently work on an Android application with two developpement phones :
1 SGS GT I-9000 with Android 2.3 at first, then Cyanogen 10.1.3 with Android 4.2
1 SGS III GT I-9300 with Android 4.0.4
My problem is that when my application triggers an unhandled exception while testing my code, the behavior is radically different on the two handsets : The old Galaxy S displays a force close popup (either on Android 2.3 or 4.2), but the Galaxy S III completly crashes and I have to reboot it each time.
Is there a parameter that i have missed ?
Edit : I also tried to run the app on AVD with a deliberate NullPointerException. It is correctly trapped.
I finally managed to get rid of this problem : I downloaded a new ROM for SGS III and flashed the phone with ODIN 3.09. Exceptions don't crash the handset anymore and the force close popup is correctly displayed.
(For those who wonder why i didn't simply update the current ROM, the response is : I tried, but it changed nothing)
I've developed an android application using opencv and I used back camera in my app. I can use my app in Galaxy S1 but surprisingly when I want to test it on Galaxy s4, after some seconds my phone restarts!
How can I fix this problem?
you can look at this question that I post:
http://answers.opencv.org/question/20054/video-get-stuck-on-galaxy-s4/
I have also the same problem, till now I didn't solve this problem.
you can see here the status of the bug: http://code.opencv.org/issues/3113 .
I use MediaMetadataRetriever that is much slower and you have to save the video first.