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)
Related
When I try to open Notification Access Settings page on Samsung Galaxy S8 running Android Oreo, I'm getting "Unfortunately settings has stopped"
This is the code I'm using:
public static final String NOTIFICATION_ACCESS_SERVICE_SETTINGS_PAGE = "android.settings.ACTION_NOTIFICATION_LISTENER_SETTINGS";
startActivityForResult(new Intent(AppConstants.NOTIFICATION_ACCESS_SERVICE_SETTINGS_PAGE), 1108);
This is working fine on all other devices except Samsung Galaxy S8.
Note: I'm not getting any Log since the crash is not happening in my app.
Samsung devices have custom TouchWiz interface, created by Samsung Electronics.(TouchWiz is available only on Samsung devices) As many files are customized, it is not possible to find the exact root cause without complete device software information and they even might need sample application code for which issue is seen. I would suggest you to report them the bug: Where to report device-specific bugs to Samsung?
I have a problem running my app on a device.
Not on all devices!
On many devices(Lenovo android 4.2.2, Lenovo 4.4, Nexus 4 android 4.4 and more) it's running perfectly!
Unfortunately on some devices, such Samsung with android 4.4(upgrade to 5.0), Wiko android 4.4.4 app crashes without any message.
When I click on the app icon, the app opens then it shows a white screen for less than 1 second before the app closes.
I've made a apk file like this: In Android Studio I press "run" triangle, after it finished building I copy apk from "appname\app\build\outputs\apk". app-debug.apk
Does anyone have the same problem ?
Thanks for any helpful information !
Important:
The device is for 2,500 kilometers from me
UPD:
I try to launch "empty" app and it works!
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...
I'm developing for android (API 14) deploying for Nexus One on Genymotion simulator and to a Galaxy Note N8000 tablet, but my app it's having a strange behaviour: in one of the activities, when I press the back button, the app shows the right activity but my debugger disconnects.
Using the simulated Nexus One I have a log message related to OpenGL out of memory and I've found out that OpenGL support for simulators it's usually bad, but using physical note n8000 I have nothing in my logs that can help me. The app behaves like it should but I loose debugging.
Does anyone had a problem similar to that? How did you fix it?
I face the same issue sometimes, my guess is that the Exception actually forces application closing (disconnecting it from debugger), but somehow it gets automatically restarted restoring the previous 'state'.
In your case, maybe is just a simulator issue, but you should consider testing in a real Nexus One device, just to make sure.
I have PhoneGap application made for Android. On my device and other users devices it runs just fine. But on some phones ( right now I know about LG Optimus One and HTC Magic ) it doesn't start and / or crashes while starting.
Anybody has some good hints why could this happen ? I tried to run my app on Android emulator in all possible versions of Android and it runs fine. So its more of the hardware/phone problem.
Does an empty PhoneGap app work for you on the crashing devices? If so, I'd recommend binary search adding to the empty app [or reducing your work] until the crash occurs [crash stops].
The only feature (in the same app and Android version) I've seen cause crashes is the Camera. Different devices have different default resolutions and large resolutions can cause memory overflows.