The call is working perfectly fine for the first time.
But after that it freezes just before connecting to WebRTC, this is currently happening only on Samsung Galaxy S5 out of my 5 devices that I test upon.
Other devices are:
Motorola Moto G2
Nexus 5X
Samsung Grand
Samsung S2 (Genymotion emulator)
Please point me to something that can help... Sorry, but I don't have the logs for this error
I am from Crosswalk team. We are maintaining some basic tests for WebRTC on Crosswalk and haven't find similar issues.
If you can share your test page, it could accelerate the problem fixing.
Another way is to file bugs a bug JIRA where we use to track bugs,
https://crosswalk-project.org/jira/secure/Dashboard.jspa
Related
I've developed an Android app for remote controlling some special hardware devices. The communication is done via udp and wifi. The app already runs on ~60k devices without any problems but since the rollout of Android 6 I'm getting more and more reports from users who get some strange errors:
Usually the app searches for the hardware with a broadcast package. The app then requests all data from the hardware to stay in sync (~4000 packages in both directions). This sync process is heavily tested with all wifi conditions possible and does work as intended (also on Android 6).
User with a Samsung device and Android 6 are now having the issue, that the sync is unable to complete (no reply from the hardware within 20 seconds). The odd thing is that the broadcast search does work just fine, as well as the beginning of the sync. Usually the timeout happens when 5-15% of the sync was completed.
As I have no idea what could cause this issue I wanted to ask if there is any known problems with Samsung / Android 6 and udp communication via wifi?
Also were there any other changes on the network stack in Android 6 that could cause this issue? On my test devices (HTC mostly) everything runs fine so I'm currently out of ideas.
Edit:
I narrowed the issue down to the following devices:
Samsung Galaxy 6
Samsung Galaxy 6 Edge
Samsung Galaxy Note 5
Edit 2:
I got a Samsung Galaxy 6 device for testing purposes and of course it does work for me. I also tried all sorts of network setup, power saving, anti virus and general settings combination but it's just working all the time.
Edit 3:
After getting some Galaxy S5 and S6 test devices I was not able to reproduce the problem. Comparing the ROM version I found out that these devices all have a newer rom than the devices which got the issues.
Turns out that Samsung simply broke something in their wifi stack which causes the wifi to stop working properly after some udp packages. So only fix for this issue is to wait and hope they fix it in all countries soon.
How do I replicate Nexus 5 images rotation issue when I don't have a Nexus 5?
I have a bug reported that images taken within my app are turned upside down when using Nexus 5. I have 6 devices at hand but not this one, and all 6 work just fine.
How can I replicate this issue, using a good, reliable online service that provides developers with real devices to test on?
Google has the Cloud Test Lab which allows you to test different orientations on real devices, including the Nexus 5.
An emulator like Genymotion has the device you require and many others too.
I want to check my developing application in android device. But i have (VideoView force close on Micromax Canvas magnus, java.lang.StringIndexOutOfBoundsException while playing video in videoView : Android v 4.2.1) these question which are told some problems are present using Micromax mobiles at development on android apps. So i confused to buy mobile for testing? Please provide the solution...
A Nexus device won't have any vendor-specific issues as you seem to have found. But just because it works on a Nexus, doesn't mean it will work on everything. So, there really is no perfect single device for testing.
I had made an android application using ionic framework. My app works fine on all devices except on a Samsung Galaxy S5. When I try to run my app on a S5 the app hangs a lot and crashes at several points. I did a lot of R&D on Google but didn't find any solution. Can anyone please help me out with this problem?
One of the app I am working on works fine on Samsung Galaxy Ace and Samsung Galaxy Y but a user reported that app crashes on installation in Samsung Galaxy S3.
Now I am wondering how could a app working well one phone crashes on installation on another phone, what could be the reason for such a crash?
Also how could I replicate the behavior of Samsung Galaxy S3 even when I don't have one and I don't intent to buy one (given the cost of the phone)?
As mentioned by AppMobiGurmeet in his comment, you can start by creating an Android emulator with the same characteristics as the Galaxy S3.
This can be enough to solve simple bugs, but there is really nothing like testing on the real device.
As it is impossible for you to test on this phone, I would advise you to implement some crash reporting system in your app, using ACRA for example (a really great library for debugging). This way yuo will see the stack of the crash (which is enough in most cases to understand what is going wrong)
Now I am wondering how could a app working well one phone crashes on
installation on another phone, what could be the reason for such a
crash?
Do you know what is the exception when it crashes? There could be so many reasons.
Different VM max size
Different screen resolution
Permissions - are you using specific hardware features/internet/external storage
It is impossible to tell without knowing the exception. If you cannot get the device, you can try to emulate as close to the device as possible. Android emulator allows you all these settings - screen resolution, max VM heap size, RAM size, external storage etc. So get the technical specs of that device and set up your emulator accordingly. Then try to reproduce the problem