OK some one please shed some light. I enter the about:debug mode and have a bunch of new options but I still cannot find the Uastring setting. does anyone know why this would happen?
Im running cog 5.5 and I can't seem to find it either? Does anyone know where to find the uastring setting?
It is there at the bottom - but it causes the browser to crash. Confirmed on JF6 and JH7.
search works very well:
http://forum.xda-developers.com/showthread.php?t=730542&highlight=browser+user+agent
Related
How do I enable plug-ins to "always on?" There's no actual "plug-ins" vebage anywhere on this g tablet settings. I can't find it in system settings or browser settings. Where could it be? I'm running stock TNT with enhanced package.
Use the "about:debug" page from the browser. Just type it into the address field and then go.
Then hit the menu button, choose More, Settings
Scroll down to "Enable Plugins" and select "Always On"
Note: If you scroll all the way to the bottom of the Settings page, you can also set the User Agent -- I personally set mine to "Desktop" instead of Android (so I get the full site rather than a mobile site)
I typed about:debug and hit Go, but just a blank page popped up. I went under settings but no change available for what you said. What's happening?
I am getting nothing with this too. any other ideas. I would love to be able to use my usb port.
shuratilt said:
I am getting nothing with this too. any other ideas. I would love to be able to use my usb port.
Click to expand...
Click to collapse
This is for enabling plug ins in the browser....flash....not for the usb port. What do do want to use the usb port for?
shuratilt said:
I am getting nothing with this too. any other ideas. I would love to be able to use my usb port.
Click to expand...
Click to collapse
???
Not sure what you are trying to do...I was trying to answer the initial question about enabling plug-ins for the stock browser...
Maybe restate the question as I may have mis-understood what is being attempted...
SirDroidAlot said:
I typed about:debug and hit Go, but just a blank page popped up. I went under settings but no change available for what you said. What's happening?
Click to expand...
Click to collapse
Once you type about:debug, nothing will open so you did it right. Now you need to open your browser settings to see the additional setting that you can change.
So has anyone else experience this? It just started out of nowhere. When I use the search or voice search in the top left. The display goes dim but the browser does not open with results.
Any light on this would be helpful.
Thanks in advance...
easygoing20016 said:
So has anyone else experience this? It just started out of nowhere. When I use the search or voice search in the top left. The display goes dim but the browser does not open with results.
Any light on this would be helpful.
Thanks in advance...
Click to expand...
Click to collapse
Make sure auto-rotate is enabled in settings, and just rotate the Xoom...a window will then pop-up with a choice of actions to take. Do this if the screen dims and it doesn't let you do anything. It's just a bug in HC3.2.
I use the Hidden Menu to adjust the LED brightness, but I don't really know anything else about the many things in it. I was looking at the various tests and checking them out today and noticed something weird. When I did the Gyro Cal Test (in Device Test just above the LED brightness one), I got "Functional Test Result: FAIL" as the result. That doesn't sound good.
Can anyone try that test and see if something is wrong with my phone or if the G2x is supposed to fail that test.
I don't know if my device has always failed that test or, if not, when it started. The only thing that is wrong with my phone is that the screen doesn't come back on after the proximity sensor turns it off during a call. Either the other person ends the call or I have to pull the battery. If you know how to fix that, I'm all ears! [I'm running Tsugi with stock kernel.]
And speaking of the Hidden Menu, does anybody know anything else useful in it other than the LED brightness adjustment?
lobsterhead said:
I use the Hidden Menu to adjust the LED brightness, but I don't really know anything else about the many things in it. I was looking at the various tests and checking them out today and noticed something weird. When I did the Gyro Cal Test (in Device Test just above the LED brightness one), I got "Functional Test Result: FAIL" as the result. That doesn't sound good.
Can anyone try that test and see if something is wrong with my phone or if the G2x is supposed to fail that test.
I don't know if my device has always failed that test or, if not, when it started. The only thing that is wrong with my phone is that the screen doesn't come back on after the proximity sensor turns it off during a call. Either the other person ends the call or I have to pull the battery. If you know how to fix that, I'm all ears! [I'm running Tsugi with stock kernel.]
And speaking of the Hidden Menu, does anybody know anything else useful in it other than the LED brightness adjustment?
Click to expand...
Click to collapse
Not all items in the Hidden Menu have to do with the G2x, example FM Radio Test. I get the same results with the Gyro Cal Test.
GTWalling said:
Not all items in the Hidden Menu have to do with the G2x, example FM Radio Test. I get the same results with the Gyro Cal Test.
Click to expand...
Click to collapse
Do you know of anything that is useful in the Hidden Menu or is it all just tests to make sure something is on or not?
Call me crazy, but what it's this hidden menu and how do I access it?
Sent from my LG-P999 using xda premium
F0rgiven said:
Call me crazy, but what it's this hidden menu and how do I access it?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Here are two ways of getting to it here.
It's got a bunch of tests for your phone. I've never heard of any major uses for it other than what I do with it, which is adjust the "Touch LED Brightness." I like to turn them down.
You can also set some parameters that are used for GPS; in particular, some people have reported significant speedups by using the Google SUPL server instead of one of the three that are available in the stock ROM.
wmm said:
You can also set some parameters that are used for GPS; in particular, some people have reported significant speedups by using the Google SUPL server instead of one of the three that are available in the stock ROM.
Click to expand...
Click to collapse
Where can I choose to use Google SUPL? It's not listed on mine. Only T-Mobile, Spirent, and LGE SUPL. The T-Mobile one was chosen by default on mine. Do you know what is meant by "Use XTRAS" in the same sub-menu?
Yes, those are the three I mentioned that are available in the stock ROM. You have to add the Google SUPL server before you can select it. If you go to the SLP Server Setting screen and hit the menu button, you'll get the choices Add, Edit, and Delete. Hit Add and set "name" to Google, "slp address" to supl.google.com, "port" to 7276, and "certification file" to /etc/SuplRootCert. Leave "TLS Setting" unchecked. Hit the menu button and then Save. You should then have a Google entry you can select. I'm not sure about "Use XTRAS", but mine is checked.
wmm said:
Yes, those are the three I mentioned that are available in the stock ROM. You have to add the Google SUPL server before you can select it. If you go to the SLP Server Setting screen and hit the menu button, you'll get the choices Add, Edit, and Delete. Hit Add and set "name" to Google, "slp address" to supl.google.com, "port" to 7276, and "certification file" to /etc/SuplRootCert. Leave "TLS Setting" unchecked. Hit the menu button and then Save. You should then have a Google entry you can select. I'm not sure about "Use XTRAS", but mine is checked.
Click to expand...
Click to collapse
Awesome! And you say this will help with GPS? Do you know what it does/how it works differently? Do you use the Google one? Maybe that makes XTRAS become checked because currently mine is unchecked. It is listed as "Disabled."
I do use the Google server, but it's not clear to me whether it helps or not because my TTFF is not great (but not terrible) and varies a lot. Some people have reported that it gives a big improvement. I don't know what the difference might be other than possibly increased bandwidth or decreased latency when downloading the AGPS data. I don't know what the story is with XTRAS. Sorry I can't help more; you can find several threads here referring to the Google SUPL server.
Two things:
Firstly, when I type in the browser the screen moves up on every key press...weird.
Secondly, the top of the screen (in expanded desktop mode, with full screen lab running) gets corrupted - legacy downloading blue lines and tabs - which should disappear. Weird.
Any ideas from the brains trust out there? It's been happening sporadically for a couple of weeks - I'm on CM10.1 Nightlies - been the same with various versions of CM10.1.
dgjl said:
can anybody explain and /or solve the following two things:
Firstly, when I type the screen moves up on every key press...weird and annoying.
Secondly, the top of the screen (in expanded desktop mode, with full screen lab running) gets corrupted - legacy page downloading blue lines and tabs - which should disappear remain in the top part of the screen.
Any ideas from the brains trust out there? It's been happening sporadically for several weeks - I'm on CM10.1 Nightlies - been the same with various versions of CM10.1.
Click to expand...
Click to collapse
Bump - any ideas? Has this really never been seen before (did a clean install yesrerday and it still happpens).
Over 100 views and no ideas? Someone must know something. Surely it's not a unique set of problems .
It's definitey an issue with the 'labs' setting - turn that off and it goes away. Any reason why this should happen? can anyone replicate this?
dgjl said:
It's definitey an issue with the 'labs' setting - turn that off and it goes away. Any reason why this should happen? can anyone replicate this?
Click to expand...
Click to collapse
Hi dgjl-
I'm replying to this post with your same settings and having none of the same problems. No scrolling when I typing, no ghosted tabs or lines above? I do have some wierdness with the cursor positioning though and positioning the cursor with the arrow keys does not work in desktop mode but does in mobile mode (user agent). Also the page seems to have a white hue like its been whitewashed.
Labs, Developer Settings, and Experimental all mean about the same thing. It means its a new feature that hasn't been fully tested so use it at your own risk. I tend to avoid these settings unless you want to be a beta test site for Asus. You may then have to disable other settings that previously worked fine to run your new setting as they may conflict. You may have to "experiment" to find the combination of settings that work together.
If you type "about:debug" into the address line, then go back into settings there is a new menu item "debug" and in there are a slew of new settings to check out. Enabling "enable cpu upload path" speeds things up, and there is also controls for OpenGL and WebGL that you might experiment with. Also try disabling "fast scroller" under the advanced settings as it may conflict with the labs flyouts. I am also running my Multi browser2RAM startup script which is the same as browser2RAM.
elfaure said:
Hi dgjl-
I'm replying to this post with your same settings and having none of the same problems. No scrolling when I typing, no ghosted tabs or lines above? I do have some wierdness with the cursor positioning though and positioning the cursor with the arrow keys does not work in desktop mode but does in mobile mode (user agent). Also the page seems to have a white hue like its been whitewashed.
Labs, Developer Settings, and Experimental all mean about the same thing. It means its a new feature that hasn't been fully tested so use it at your own risk. I tend to avoid these settings unless you want to be a beta test site for Asus. You may then have to disable other settings that previously worked fine to run your new setting as they may conflict. You may have to "experiment" to find the combination of settings that work together.
If you type "about:debug" into the address line, then go back into settings there is a new menu item "debug" and in there are a slew of new settings to check out. Enabling "enable cpu upload path" speeds things up, and there is also controls for OpenGL and WebGL that you might experiment with. Also try disabling "fast scroller" under the advanced settings as it may conflict with the labs flyouts. I am also running my Multi browser2RAM startup script which is the same as browser2RAM.
Click to expand...
Click to collapse
Thanks. I've been through the various debug settings already - what's strange is that when debug is operating (i.e., in the same browsing session as 'about:debug' is launched) the problems don't seem to occur. Is there anyway to make debug permanent - as it is on Cromi, for example?
dgjl said:
Thanks. I've been through the various debug settings already - what's strange is that when debug is operating (i.e., in the same browsing session as 'about:debug' is launched) the problems don't seem to occur. Is there anyway to make debug permanent - as it is on Cromi, for example?
Click to expand...
Click to collapse
This is the first I'm hearing about the "about:debug" settings you change not being "permanent". I don't follow you. When I change a debug menu setting in a browser session, then launch a new tab and url "about:debug" in that session, all the settings I changed in the previous session are applied to all new tabs I create. Same is true if I shut it down and relaunch the browser. The settings persist. Yours don't?
Are you running the old browser2RAM that loads the actual browser app as well as its cache into RAM ["mount | grep tmpfs" to check all mounts from the terminal] so the session data doesn't persist? If so, use my startup script 3 in my signature instead - data persists. Its a more versatile replacement for browser2RAM that works on 4.2 as well. For 4.1 and below you can run it from the terminal as su after boot. For 4.2 you need to run it as su *at boot* using either an init.d method or the Script Manager (Devwom) app.
I'm kinda liking this lab flyout! Makes for quick navigation. But this cursor thing is starting to P me O. I use Chrome instead.
@sbdags do you have any suggestions?
elfaure said:
This is the first I'm hearing about the "about:debug" settings you change not being "permanent". I don't follow you. When I change a debug menu setting in a browser session, then launch a new tab and url "about:debug" in that session, all the settings I changed in the previous session are applied to all new tabs I create. Same is true if I shut it down and relaunch the browser. The settings persist. Yours don't?
Are you running the old browser2RAM that loads the actual browser app as well as its cache into RAM ["mount | grep tmpfs" to check all mounts from the terminal] so the session data doesn't persist? If so, use my startup script 3 in my signature instead - data persists. Its a more versatile replacement for browser2RAM that works on 4.2 as well. For 4.1 and below you can run it from the terminal as su after boot. For 4.2 you need to run it as su *at boot* using either an init.d method or the Script Manager (Devwom) app.
I'm kinda liking this lab flyout! Makes for quick navigation. But this cursor thing is starting to P me O. I use Chrome instead.
@sbdags do you have any suggestions?
Click to expand...
Click to collapse
Actually I'm running your script for b2r… As for 'permanent' I just meant the menu for debug being always available, not the settings. When it's there as an option the typing doesn't move the screen up - though screen corruption still happens as described.
Using Dolphin currently as I'm a full screen addict and Chrome doesn't offer that - or flash.
dgjl said:
Actually I'm running your script for b2r… As for 'permanent' I just meant the menu for debug being always available, not the settings. When it's there as an option the typing doesn't move the screen up - though screen corruption still happens as described.
Using Dolphin currently as I'm a full screen addict and Chrome doesn't offer that - or flash.
Click to expand...
Click to collapse
Ah, gotcha. About:debug>enable cpu load path fixed some of the corruption I was having with my cursor. Its not just for speed. Developer Options>Force GPU rendering fixes random reboots and other things if you haven't tried that. Make sure you have my script version 3 for Dolphin support. That's about all I've got for you @dgjl.
elfaure said:
Ah, gotcha. About:debug>enable cpu load path fixed some of the corruption I was having with my cursor. Its not just for speed. Developer Options>Force GPU rendering fixes random reboots and other things if you haven't tried that. Make sure you have my script version 3 for Dolphin support. That's about all I've got for you @dgjl.
Click to expand...
Click to collapse
Thanks for taking an interest, Elfaure. Looking around the 'web' I don't think I'm the only one with ths issue, but there's no one out there with the solution yet. It's just strange that it started without an obvious cause...
SORTED:
I found this thread http://code.google.com/p/android/issues/detail?id=39811
I had downloaded a notifiation app which ran under Settings>Accessibility. The moment I disabled it the probem went away!
Marvellous!
dgjl said:
Thanks for taking an interest, Elfaure. Looking around the 'web' I don't think I'm the only one with ths issue, but there's no one out there with the solution yet. It's just strange that it started without an obvious cause...
Click to expand...
Click to collapse
You might want to unload my script and see if the problem persists. If it does then ? If not, then maybe some switches could be added to your mount line (nodev, nosuid, gid=...etc.)
elfaure said:
You might want to unload my script and see if the problem persists. If it does then ? If not, then maybe some switches could be added to your mount line (nodev, nosuid, gid=...etc.)
Click to expand...
Click to collapse
The solution is in my previous post - anything running in Settings>Accessibility with conflict with the stock browser/lab and cause this to happen. trouble is now I don't know what to do for a notification widget as they all use 'accessibility' and I don't want the notification bar to be visible. Good old Android - there's always something!
dgjl said:
The solution is in my previous post - anything running in Settings>Accessibility with conflict with the stock browser/lab and cause this to happen. trouble is now I don't know what to do for a notification widget as they all use 'accessibility' and I don't want the notification bar to be visible. Good old Android - there's always something!
Click to expand...
Click to collapse
So its either accessibility notifications and a different browser or labs flyouts with the stock brower - your choice. Good you got the bottom of it. That's always the first step in fixing a problem. Looks like you can't have your cake and eat it too on this firmware.
It seems to be a pop up in the Samsung Browser that randomly happens. Ive made it a point to try and take a screenshot if it comes up before it dissappears to post on here.
Its completely random and doesnt happen all the time. It changes its subject also not always being the same thing. It slides in for a few seconds from the mid left side then slides back out to the same mid side. Ive been searching for hours to try and figure what it is amd how to disable it… .but i dont know what im exactly looking for on what its called and whats causing it. Any help would be greatly appreciated. Thank you in advance.
UPDATE UPDATE… IT WAS NOT THE BROWSER. THE KEYBOARD THAT I USE HAS A NEW FEATURE OF SENTANCE PRODICTION. I TURNED IT OFF.
MODS PLEASE DELETE THREAD.
Why not delete the browser entirely? There are a number of better browser options.
Actually the Samsung browser is pretty good now as it has improved a lot over time. One nice thing about it is if you use DEX, it will automatically detect you are in desktop mode and adjust the browser to full desktop mode. On you phones screen it defaults to mobile mode.
varcor said:
Why not delete the browser entirely? There are a number of better browser options.
Click to expand...
Click to collapse
It was not the browser… .i like samsung browser the best put of the ones i tried. And im familiar with it.