We have a Javascript bug that only appears in the stock browser of the Galaxy S4 (GT-I9505) running KitKat (4.4.2) and we're unable to debug it or view the Javascript console. I've tried running about:debug and it does enable the debug menu, but it also redirects me to a 'page not found' and going back/forwards removes the debug menu.
We've also tried using logcat, but no messages are shown (this command works perfectly on a Nexus 4 JellyBean and in an emulated Gingerbread).
adb logcat browser:V WebCore:V Console:V *:S
We've also tried JSConsole and Firebug Lite but nothing useful is shown on their console. We also implemented the 'DIY Console' as suggested by EclipseSource and while it did show an error, it doesn't tell us which file the error comes from or any specific details.
Does anybody have any other suggestions for things to try, or a solution as to why about:debug isn't behaving properly?
I don't know if this will work for you, but I have a Galaxy S4 and I was able to see console messages this way:
Plug in your phone, make sure you're getting all the logcat messages
Add this filter: INFO:CONSOLE
Javascript errors are printed under the chromium tag and the "Info" log level
Related
I have a problem on galaxy s8 and galaxy s9 with dynamic links from firebase. On other android devices it works. A strange loading screen appears, then returns to the application from which there was an attempt to open the application. Anyone had a similar problem or potentially knows a solution? The application is not installed. Certificate SHA-1 is attached. https://drive.google.com/open?id=15BTDWjFgMtijZ7RVILN7DUq-fG0BzlE7
on the next day the links started to work correctly ... it looked like a problem with permissions on devices
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 am wanting to create a simple app which will show some information on the Samsung S6s edge panel, and so I am starting to try to get the samsung exmaple running.
I've developed android application before (some time ago), but looking through the Samsung documentation I am lost, i'm sure i'm not the only one.
What I have tried so far
I have downloaded the samsung look sdk here: http://developer.samsung.com/galaxy#look
I can then import a project into eclipse from the samples called "EdgeScreenSampleApplication", and using android 19 I am able to compile it. However, I cannot run it on any emulator. I assume I need some special emulator to show the 'edge', but I cannot find one. When I run it on a Nexus emulator, I get:
[2015-03-21 21:01:33 - EdgeScreenSampleApplication] Installation error: Unknown failure
[2015-03-21 21:01:33 - EdgeScreenSampleApplication] Please check logcat output for more details.
[2015-03-21 21:01:33 - EdgeScreenSampleApplication] Launch canceled!
Now I am stuck, do I need a particular emulator? How can I get this thing running? I'd like to run it, then I can dig in to look at the code and see how it is working. Of course I do not have a Samsung S6 to test on as they are not yet released.
I am developing an app in Android that I hope to release. I've got most of my GUI done, but it does not look even close to correct on the device when installed and opened. I have a screenshot of how it looks, and a screengrab of how it should look (taken from the Emulator in Eclipse) at the links at the bottom of this post. It's best to take a look at the two images rather than me try to describe how screwed up the app becomes on my device.
I had a friend with the exact same device, including hardware and Android version, and his loads up just fine. Does anyone have any idea what's going on here? Both devices are Galaxy Nexuses, running Android 4.0.2, GSM on AT&T (unlocked).
Installed on my device: http://i.stack.imgur.com/x66Jo.png
In the emulator: http://i.stack.imgur.com/qE0J6.png
I've seen this occur in some Galaxy Nexus' and I put it down to a bug/glitch in the OS on that Galaxy Nexus. Try a Factory Reset of your Galaxy Nexus, if that fails, try reinstalling the current OS version you have (if you can get your hands on it), if that fails, get it fixed under warranty.
Does your app use multiple activities?
Can you compare on your two devices if this setting is the same?
Settings > Developer Options > Don't keep activities checkbox.
I realise this is an old question now but I was having the same problem as you and stumbled across a solution. I didn't particularly want to factory reset my phone as per straya's instructions, so I started playing around options in the Settings > Developer Options menu.
As it turns out, this problem occurs for some applications if you have the Force GPU rendering option checked. Disable this (I'm not sure why it was enabled anyway) and everything displays as it should.
I am using the Facebook API to post messages to Facebook from my Android app. I have tested it out on various different phones, yet on one particular phone the Facebook API just pops up a blank white dialogue window that doesn't load the FB log in page.
I have tested it on the Samsung Galaxy S, the HTC Desire, HTC Sensation and it works fine - but when I try it on the HTC Wildfire S it does not work.
There are no messages popping up in LogCat and stepping through it with the debugger does not reveal any problems.
Looking through the code provided by Facebook I can see it is just a WebView which is being created. There is a function called onPageFinished(..) which gets called but there is nothing in the WebView.
I'm not really sure what to try to fix this. I've tried clearing some settings on the phone but that did not work. Does anybody have any ideas?