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.
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.
We have just managed to replicate an issue that a customer is reporting with our Android Tablet (4.4.2) and a Bluetooth device. They have reported that they are unable to pair our supplied bluetooth device with the our supplied tablet. To fix it they just rebooted the tablet.
In the office we have replicated this. Going to Settings->Bluetooth and clicking on the device in Available Devices doesnt do anything. If I power up another one of our devices, then I can pair with it without an issue.
Its only this one particular device thats causing the issue....which got me to thinking Android was caching this devices info somewhere and that cache was now out of date/corrupt somehow.
After a lot of googling I came across the tip of clearing the "Bluetooth Share" application data cache and this fixes this issue. However I need to do this automatically from code.
Has anyone come across this issue? And if so how have you managed to call this Clear Cache function from code?
Thanks!
I'm having trouble with an app I published that sends user notifications.
The notifications are called from a background service that checks for a boolean that gets saved to SharedPreferences when the user selects to enable notifications or not.
However, I've had some users on the Galaxy S5s say that they can't turn them off (I test with nexus devs and have beta testers on m8, etc). How do I address this issue?
What is the strategy for solving problems that arise only for specific devices?
IMO, Android kinda sucks in that regard. There is absolutely no way to guarantee that if one piece of code that works on one device works on another one. Since Android is open source, manufacturers usually modify the firmware to make it kinda customized. However, they sometimes change things that will affect performance of a single function.
It is even worse! Your code might work on S4 with Android JellyBean, but not work with the same device Android Kitkat. Anyways, no - there is no way to debug without the actual device. However, you can log different events in your code and use an analytic service (like Google Analytics) and send the data to your database to study and figure out the problem. This is the method that I typically use in such cases.
If the problem is that the app crashes on some device. It is even easier. Users need to press on the "send crash data" button - so you can study the log on your developer account.
Client came to me needing me to create a cash back calculator on their WordPress site http://onetouchrelo.com/
Did it with Caldera forms and seems to work on every device and browser I've tested it on, but the client and one other person at their office say's the calculator doesn't work on their Galaxy S4's. There are other people there with S4's (and any other device for that matter) that it's working fine for. The problem is that whatever the first number is he types, for the incentive it just repeats that number over and over instead of calculating. eg. 3333333, or 5555555.
I've tried removing all of the CSS from the form and just stripping it down to basics, deactivating plugins, all the normal stuff. Nothing seems to fix it for these two guys' phones. They say they're on kit kat and everything else works fine on the site for them. I am at a loss O_o
Generally, if you have multiple test cases that work with a piece of software and one device that does not work, your troubleshooting should begin with the device itself.
You mentioned that other devices of type Galaxy S4 are able to use the app. In that case check to see if the OS versions match on the ones that do and don't work. Check that there are no updates needed for the device. Recommend using another mobile browser to use the app like Chrome or Firefox and see if that alleviates the issue.
Lastly, Power off the device and try accessing the web app again.
If it still does not work, then the last resort is to try a factory reset to see if that clears the issue - after backing up their data. But, this seems to be device specific based on what you have mentioned.
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 :(