In my app Toasts have worked fine until my RazrM phone was upgraded to 4.4.2. then they stopped. I have tried specifically runInUiThread and moving the call to initiate from different places in the code including in onCreate(). The issue [20373751] (Toast not appearing on Android 4.4 KitKat) proposes rebooting or specifically running on the UI thread. Neither makes a difference.
That issue also questions if there is a bug in Nexus or KitKat. I have the Toasts running fine in 4.0.4 on a Samsung Galaxy Tab. So I am thinking the problem is in 4.4. Has anyone found a workaround? (BTW I am compiling to a target of Version 9, so it is not an issue with the compile level.But I am using the infamous 23.0.2 SDK.) Can anyone prove that Toasts work under 4.4.2 while using SDK 23.0.2?
In [21098062] #marcin_j said:
On Jelly Bean 4.1 or higher,you can disable apps notifications from device settings. Just open notification bar, long tap on any of notifications and click App Info, you should see “Show notifications”. Unchecking this option should disable toasts in your app.
If your app does not show any notifications, then you should be able to reach App Info screen from applications manager.
Maybe this is the cause of you missing toasts
This was absolutely correct. My 4.0.4 device was not affected but my 4.4.2 device had had Show notifications unchecked.
Related
In my app, I'm facing a weird issue I can't explain. I can't even give you a logcat or something as I don't know where it is actually coming from, I can only describe the error:
My app Daily works well on some 5.0 and 5.1 devices, the HTC One Max for example. It does NOT work for Samsung and Sony devices running 5.1 and 5.0, maybe also at a 6.0 Samsung. The app just stays white for a few seconds and nothing happens then.
If you have any further questions about the app itself, you can just ask.
The app is using a MultiDexApplication and MultiDex itself if this might help.
Thanks.
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 main window of my app sets the FLAG_SHOW_WHEN_LOCKED and FLAG_DISMISS_KEYGUARD window flags to bring up the app window in front of the usual Android lock screen. The exact code follows
getWindow().addFlags(WindowManager.LayoutParams.FLAG_SHOW_WHEN_LOCKED | WindowManager.LayoutParams.FLAG_DISMISS_KEYGUARD);
This has worked perfectly ever since ICS on all my devices. But recently I received two reports from end users that the app was no longer coming up on top of the lock screen. We finally established that the first user was running Cyanogenmod and had him open a support issue with them. But the second user is running an absolutely stock OS. To make things even more interested, he reports that it was working properly when he first installed the 4.4 system update. But installing the most recent system update broke things. Since then our app no longer appears on top if the lock screen, but it bumps up immediately as soon as the screen is unlocked.
Technical details...
Mode number: SM-G900P
Android Version:4.4.2
Baseband version: G900PVPU1ANE5
Kernel version: 3.4.0-1750661
dpi#SWDD6020 #1
Fri May 30 21:23:48 KST 2014
Build number: KOT49H.G900PVPU1ANE5
SE for Android status
Enforcing
SEPF_SM-G900P_4.4.2_0016
Fri May 30 21:23:28 2014
Security software version
MDF v1.0 Release 3
VPN v1.4 Release 1
I do not have a phone running 4.4 yet. I run the app on the latest and greatest 4.4 emulator and did not any problem with it popping up over the lock screen.
Anyone else heard any reports of this? Any suggestions on what we can do next?
I found this question when I was looking for an answer why a notification I was creating was not showing up in front of the lock screen. The code worked for an old 2.3 android device, but it was not working for a new 4.4.4 nexus 5.
In my case it was caused by:
<item name="android:windowIsFloating">true</item>
When I changed that to false, it was fixed. Not sure why this requirement is there and if this is not needed on 4.3 and lower (I only have the old 2.3 device and the 4.4.4 nexus 5 to test stuff on).
-- Edit
Also see this issue, seems there is another workaround
Android's floating windows coupled with FLAG_SHOW_WHEN_LOCKED fails
Haven't checked on this for a while. After going round and round about this problem, we eventually concluded that the Android system was doing everything it was supposed to. The real problem was the 4.4 change disabling our ability to block incoming SMS messages from getting to the default message app. Our app picked up the incoming SMS message and popped up on top of the lock screen, as intended. But then the default message app picks up the message and pops up on top of our app window. Since our app is no longer visible, the lock screen is, quite properly, reinstated.
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.
We released a new app which has a widget. This works fine so far on all devices, however on Samsung Galaxy S3 we get reports that it stops working in certain situations.
Unfortunately I do not have such a device to check myself - therefore I would just like to know if anyone had some similar experience.
The widget stops working after the screen redraws itself (which seems to happen on the S3 regularly and randomly). Another user reported that the widget stops working after invoking the Task Manager and "clearing memory". There is no crash - in this case unfortunately.
The app has been tested on many devices with different Android versions - so far we have never seen such a random screen update which caused the widget to stop working.
I am thankfull for any hints.
...in fact it turned out to be a fault in Samsung's Android implemenation - they promised to fix it in the upcoming release. Thanks to Samsung amazing support we finally could confirm this issue !