My application does not break during Runtime. However, the following error messages always show up
NetlinkListener: ignoring non-kernel netlink multicast message
NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
The app I'm developing uses sockets to receive packages from a specific IP source (with specific enabled port number). I set up a set of Log outputs (I even tried 'System.out.println' calls) to verify the data flow and everything seems to be fine.
Can anyone tell me what those errors messages are exactly related to?
The device I'm using for testing purposes is a Motorola Atrix 4G (MB860) with the latest OTA update (Android 2.3.6). Because of compatibility issues, all the development we do have to be done using API 8 (or earlier).
Having the same issue, it's a bug on 2.3.6, reported on Motorola and Android.
Link to Android bug report.
In the bug report, I added the info for my phone plus the search I did on the forums. If anyone has the same issue please add a star and/or comment to make them know that the issue exists and it's not related to only one country/cell provider.
It seems to be something else on the Atrix. I have an Atrix and looking at LogCat those errors come out a lot, so its not your app.
After I rooted my Atrix phone I noticed this problem. Logcat outputs it constantly :(
Related
I just finished my first Android app. I tested it in the emulator and on my personal device (Nexus 6p). Other folks are installing it and it's working for them. My dad, however, also gave it a try. He has a Samsung Galaxy S6 running 6.0.1, and the app crashes on startup for him.
My guess is it's something touchwiz related. The thing is, he's not the most technical person, as far as getting a logcat would go. So... what are my options to try and investigate this issue?
Crashlytics can help you to retrieve the stack trace and exceptions when your app crashes.
But if you want to test and fix before the deploy, another options is Xamarin Test Cloud, it's a paid solution, but have a free-trial
[EDIT]
Searching in the internet, I found something similar to Xamarin Test Cloud, I personally have not tested this solution, but you can check it out.
TestMunk, they have a free plan.
This is an aspect of the extreme fragmentation of the Android ecosystem. I've seen bugs that manifest only on a specific device from a specific carrier. For example, at one point, Verizon broke ACTION_HEADSET_PLUG on one of their tablets, so that no app would ever receive it. It had worked fine on an earlier firmware version. Naturally, they refused to acknowledge the problem. The same tablet model from T-Mobile never exhibited this issue.
This is why I don't trust the emulator. It's fine for early testing, but you still need to test on the actual hardware that you intend to support. There are online services that test your app on a wide variety of real devices to try to uncover the weird vendor-specific issues. I've never used these services, so I can't recommend one.
I am trying to recreate an issue which is only caused on HTC One XL phone running Android 4.2.2. It is a styling issue which can be fixed with CSS. The problem is that the Chrome Developers Tool does not have a profile for HTC One XL phone running Android 4.2.2.
I do not have a real device! How can I test for an issue that only exists on particular phone running a particular Android version?
FInd someone with the device to test a beta or debug info gathering build. There's three reasons one particular device has issues.
1)Hardware problem. No emulator will solve this as they won't perfectly emulate hardware.
2)Software bug on this device's framework. Since each OEM ships their own set of patches, there's no way to know what is actually running, except for having the device.
3)Something weird in the system of an individual user. Some odd combo of software, hardware, and data. You need that actual phone to fix this, but it generally only effects a handful of users.
But none of these are solvable without access to the device, or a real Eureka moment. More logging helps, but you'd still need to get those logs which requires a device.
As my title, i need to know whether a file contains all the crash report in android. Let me explain in detail. In iphone developer can take all crash reports in iphone application by synchronizing the device into system in the specific directory in Mac.All the crash reports are stored in directory with the individual device name.
Likewise i need to get all the crash report for android device. As i googled, i got some suggestion as using ACRA we can get the crash report in Google Doc or as email.
Is there a single way to get crash report or any other way to get it? If so please guide to get the crash report. i'm in running out of time.
See the rrainn answer here Get crash data (stack traces at least) from my Android application?
You can get the crash report at any particular location you desired on SD card, you can send to server as well if you need
I am encountering the same issue as well on a Galaxy Note S2 running Jellybean 4.1.2. My Gingerbread and ICS test devices work fine. I also saw this post indicating that issue is related to some CSS handling bugs in Webkit in some versions:
http://css-tricks.com/crashing-mobile-webkit/
In my case adding a single input control or button is enough to reliably trigger the issue.
Your post and links have been very helpful. I'm going to see if I can't strip down my CSS to mitigate the bug.
I am developing one SIP based application to make and receive a call.I have used shared preference to store the all the registration related data like user-name,password,context etc.This data are also stored in A2billing.And i have used Asterisk Realtime to register sip user in application.
The main issue is that when i am running my application it works fine in all the other devices except Samsung Galaxy S2. On this device SIP user is not get registered and on asterisk console it gives me a error of Wrong password.
I cant configure what the actually issue is because its runs perfectly on other devices except galaxy SII(4.0.3).currently i have tried with HTC phones and galaxy SII(2.3.6) and it worked fine
If you have any idea and suggestion regarding this please share with me so i can workaround with this.
Thanks in Advance
Solved:
Finally the problem is solved when i uninstalled the Avast Antivirus from the device. i think Avast was causing a problem while accessing the data from sharedPrefrences don't know why. yeah but now i need to searched about that about, how do we avoid this kind of problems.
Are you using the native Android SIP stack or your own, linked in your app? If you are using the native one, might be a bug in the firmware. Debug your app and check if it is reading/writing the proper password. Then capture traffic with Wireshark, etc. and check what exactly is being sent over the wire(less). Then compare with traffic from other devices that work. Rinse and repeat until you pinpoint whose fault the error is.
Can anyone tell me if there have been any changes to the bluetooth functionality in the Android update?
I have an app which uses transmission and reception concurrently with a total of 5 connected devices and this works perfectly on a Motorola Droid2 with 2.2.1 but not on the ATRIX running 2.3
There may of course be a hardware element involved but I wanted to establish this first.
thanks in advance.
John
I had the problem that the bluetooth connection worked only on the second try - the first one almost always fails internally (IOException). And you don't have much time in between trials. This was on my 2.3.3 Sony phone. Logcat showed some messages that might imply an internal problem in bluez or with the bluez/java integration.
This problem did not manifest on a 2.2.x Samsung phone. Note that my program only uses one connection at a time.
Android website says "updated BlueZ stack", but that's all.
Did you check the logs, what are the errors you're getting?
Also, I guess you can try running different emulators with different versions of Android and see how that behaves.