Does Galaxy Tab 10.1 get keyboard lag with 3.1 update? - Galaxy Tab 10.1 General

When I installed Android 3.1 on my Transformer, I began getting ridiculous keyboard lag when using the stock browser. I tried three different keyboards with different websites, but continued to have a lot of lag. If I used Opera, then no keyboard lag.
I'm curious of the Galaxy Tab 10.1 has experienced this keyboard lag with the stock browser with 3.1 installed?

entering urls seems to be fine for me. typing in a text box on a website(e.g. xda) can be pretty painful though. I mean, you can still do it but it could definitely be much better

I've not noticed any.

I'm thinking it may have something to do with Honeycomb. I experienced lag while trying to type in text boxes on websites with my Acer Iconia before I returned it. I ended up typing what I wanted in notepad, then pasting it into the browser.

I noticed some pretty serious lag on my XOOM device under 3.1.
I found an effective fix: Dsabled the Opengl rendering setting and then enabled the Normal rendering on the browser's Debug setting. Disabling the Opengl prevents the browser from properly playing the flash embedded objects though.
I am not sure this fix would address Samsung devices, but may be worth a try.
Waiting for my pre-ordered unit.

My Samsung had serious keyboard lag until I turned off the haptic feedback. Now it's fine.

So, this issue is related to stock browser only, correct?
Have you tried Dolphin HD and/or Opera Mobile?
I am not saying thise are alternative, but interested to know if those web browsers also suffers the same issue.
Thanks.
Ravynmagi said:
When I installed Android 3.1 on my Transformer, I began getting ridiculous keyboard lag when using the stock browser. I tried three different keyboards with different websites, but continued to have a lot of lag. If I used Opera, then no keyboard lag.
I'm curious of the Galaxy Tab 10.1 has experienced this keyboard lag with the stock browser with 3.1 installed?
Click to expand...
Click to collapse

ssbmg said:
My Samsung had serious keyboard lag until I turned off the haptic feedback. Now it's fine.
Click to expand...
Click to collapse
What is "haptic feedback"
Don't have the tablet yet so getting all the feedback as possible to have a smoother experience when it arrives with you guys as early adaptors

gogol said:
So, this issue is related to stock browser only, correct?
Have you tried Dolphin HD and/or Opera Mobile?
I am not saying thise are alternative, but interested to know if those web browsers also suffers the same issue.
Thanks.
Click to expand...
Click to collapse
On my Xfrmr it happens with any browser. Sometimes it's horrible and sometimes a little bit better. I was hoping the GT 10.1 wouldn't have this issue. Hearing that I might just stay with the Xfrmr. Cheaper price and uSD slot and other than a couple ounces lighter I see no big advantage.

SR45 said:
What is "haptic feedback"
Don't have the tablet yet so getting all the feedback as possible to have a smoother experience when it arrives with you guys as early adaptors
Click to expand...
Click to collapse
When you enter a character on the keyboard it vibrates, beeps or whatever.
http://en.wikipedia.org/wiki/Haptic_technology

ssbmg said:
My Samsung had serious keyboard lag until I turned off the haptic feedback. Now it's fine.
Click to expand...
Click to collapse
Disabling haptic feedback has no effect for me.

I have the same problem with SwiftKey in the browser.

Related

Web browser bug?

I'm having a problem with the web browser.
Basically it keeps closing when I click on a link. Example, right here on the XDA forum when I click on one of the threads the web browser just shuts down & returns to the home screen. I had it just a day & took it back to the shop & they swapped for a brand new one.
Got home tried the web browser & it did exactly the same. I've not loaded any apps its straight out of the box, set up wifi & fire up the web browser.
Also I changed the UA string to desktop but it doesn't work either. Got no problems with my HTC Desire or the Dell Streak.
Any others having the same problem. Looks like I might have to return it again tomorrow.
I have experienced this too a couple of times. I found deleting cache data and cookies then also disabling plugins in browser settings seemed to fix this. Not a major issue.
luigino1 said:
I have experienced this too a couple of times. I found deleting cache data and cookies then also disabling plugins in browser settings seemed to fix this. Not a major issue.
Click to expand...
Click to collapse
Same here.
Strangely enough it only happened here at xda-devs but doing as you say cleared the issue and it's been right as rain ever since.
What does disabling plugins do? Does it stop flash from working? And how about the UA string, why won't it stay in desktop mode?
Thanks
As far as i can tell disabling plugins doesn't appear to do very much. I noticed YouTube videos will stop playing in the web browser (but will play in YouTube app perfectly fine) and that's about all. Flash support in this version of the browser is so minimal that it is barely worth having or switching on.
I have no idea about the UA string.
i had that problem on a nexus turned off my locations by wifi in settings and worked fine.
OK I've returned the phone for full refund at the shop I bought it from. I'm going to give the Galaxy S a final chance though as I will buy another from a different shop. I'm thinking it could be due to fact that the previous shop stock was from a dodgy batch of phones.
I think you'll be disappointed, sounds more like a software issue than a hardware one and I cant believe a batch of phones had a software flash go wrong like that. What id like to know is if this is just a Galaxy S thing or not? As I thought it was the same browser on all eclair phones.
I have a HTC Desire aswell. The web browser on the Desire doesn't have any of the issues I'm seeing with the Galaxy S. The problem I have with the Desire though is the external speaker volume is too low & tinny, but most significant is the pink tint when on the lowest brightness setting (I use the phone a lot in dark conditions). In saying that I noticed that the Galaxy lowest brightness setting is still much brighter than the Desire.
try out Skyfire? other browsers?
J-Hop2o6 said:
try out Skyfire? other browsers?
Click to expand...
Click to collapse
If you want to try out a good browser, then try Dolphin HD.
Very quick, slick and does have some nice features.
Beards said:
If you want to try out a good browser, then try Dolphin HD.
Very quick, slick and does have some nice features.
Click to expand...
Click to collapse
not for me.. i was suggesting them to try out the other browsers and compare.
Beards said:
If you want to try out a good browser, then try Dolphin HD.
Very quick, slick and does have some nice features.
Click to expand...
Click to collapse
Same thing happens to me. Tried to change browser, but it didn't help. Tried Opera mini 5 and Dolphin HD and HD2. Same arse
csolb said:
Same thing happens to me. Tried to change browser, but it didn't help. Tried Opera mini 5 and Dolphin HD and HD2. Same arse
Click to expand...
Click to collapse
In what way?
I'm using it over the default browser and love it.
Ok, my browser (both the default one and Dolphin HD) shuts down randomly back to the main screen. Usually it's preceded by a single vibration, followed by three quick vibrations before it happens. This happens regardless of what website I am on.
I didn't have this issue at all on 2.1, and to be honest I really wish I hadn't bothered updating the phone as sites loaded and ran quicker on 2.1. Wondering if you guys have any ideas.
My baseband is I9000XXJPM
Build is FROYO.XWJP6
Oh and, I'm running RyanZA's OneClickLagFix 2.2+
CaptainLeChuck said:
Ok, my browser (both the default one and Dolphin HD) shuts down randomly back to the main screen. Usually it's preceded by a single vibration, followed by three quick vibrations before it happens. This happens regardless of what website I am on.
I didn't have this issue at all on 2.1, and to be honest I really wish I hadn't bothered updating the phone as sites loaded and ran quicker on 2.1. Wondering if you guys have any ideas.
My baseband is I9000XXJPM
Build is FROYO.XWJP6
Oh and, I'm running RyanZA's OneClickLagFix 2.2+
Click to expand...
Click to collapse
The vibration pattern you mention are indicative to a Force Close procedure.
Clearly something is interfering with the Internet App.
What happens after a reboot?
It's the same after a reboot. I rebooted it this morning before coming into work. Later in the morning I was on the internet on my phone and the same thing happened.
edit: I upgraded via the reg-hack to force Kies to give me the update. The JPM firmware is onlly for nordic regions, I'm wondering if maybe the proper European firmware will solve the problem...
Also: FIVE MINUTES BETWEEN POSTS FOR NEW USERS?? JESUS CHRIST, XDA!!
CaptainLeChuck said:
It's the same after a reboot. I rebooted it this morning before coming into work. Later in the morning I was on the internet on my phone and the same thing happened.
edit: I upgraded via the reg-hack to force Kies to give me the update. The JPM firmware is onlly for nordic regions, I'm wondering if maybe the proper European firmware will solve the problem...
Also: FIVE MINUTES BETWEEN POSTS FOR NEW USERS?? JESUS CHRIST, XDA!!
Click to expand...
Click to collapse
I would say it looks quite good that you have a problem with the ROM.
I would put the correct ROM on your SGS and if Kies is problematic use Odin.
There is a great information link on how to use Odin to upgrade a ROM at How to use Odin to Upgrade the SGS to Froyo.
I used it and it worked a breeze.
Beards said:
If you want to try out a good browser, then try Dolphin HD.
Very quick, slick and does have some nice features.
Click to expand...
Click to collapse
Dolphin, skyfire (i really hate this over hyped crappy product) uses stock browser engine. So, on froyo they perform as the default browser. Browser on froyo sucks badly. I browse quite often and got a few fc (vibrates.. phone unusable for seconds, that happen when an app FC in official froyo) or simply self close. Plus how much resources eats (cpu + mem).. simply pathetic. Eclair browser performance was way better..
DSF said:
Browser on froyo sucks badly. I browse quite often and got a few fc (vibrates.. phone unusable for seconds, that happen when an app FC in official froyo) or simply self close. Plus how much resources eats (cpu + mem).. simply pathetic. Eclair browser performance was way better..
Click to expand...
Click to collapse
That's just your opinion and you are quite entitled to it especially if you are experiencing the problems you mention.
Mine however performs without a hitch. It's quick, reliable and does exactly that as I ask of it.

Is there a patch for the "in browser" typing delay?

3.1 didn't help resolve the annoying typing delay on this pad. I played with a Xoom and the small Samsung and it didn't have this problem.
Have there been any patches or fixes released? I was really hoping 3.1 would do it, but it didn't.
I also would love to get this. It's literally the ONLY issue I have with this device.
Didn't someone say turning off some option will help or switch to generic keyboard? I'm not really sure what the issue is, I don't think I've had it.
I noticed this problem pretty quickly and was very bothered by it. I tried out a couple different browsers and found that Opera was the only one with good keyboard responsiveness. While it may not be the best browser in other respects, it trumps all other browsers for this reason.
Now I wish there were an easy option to turn off tap-to-click. Damn thing throws me off everytime I type.
is this with the dock or the onscreen keyboard as well?
cyberchuck9000 said:
I also would love to get this. It's literally the ONLY issue I have with this device.
Click to expand...
Click to collapse
Yea, me too. It's pushing me to reconsider the Samsung 10.1.
I've only experienced typing lag on vBulletin based forums sites with the stock browser - and for example here on XDA if you choose the classic skin things improve quite a bit.
Its been mentioned many times before, that the "lag" isn't a "Transformer issue" per-se but a stock browser problem on certain sites. I've tried XDA with Firefox and Dolphin Mini and the there's no real lag that i can see, which further points to the stock browser..
Or are you guys experiencing lag on any web page with the stock browser?? (in which case I'll get my coat)
Try switching to the Honeycomb keyboard instead of the Asus keyboard.
jerrykur said:
Try switching to the Honeycomb keyboard instead of the Asus keyboard.
Click to expand...
Click to collapse
That's worse for me.
jms_uk said:
I've only experienced typing lag on vBulletin based forums sites with the stock browser - and for example here on XDA if you choose the classic skin things improve quite a bit.
Its been mentioned many times before, that the "lag" isn't a "Transformer issue" per-se but a stock browser problem on certain sites. I've tried XDA with Firefox and Dolphin Mini and the there's no real lag that i can see, which further points to the stock browser..
Or are you guys experiencing lag on any web page with the stock browser?? (in which case I'll get my coat)
Click to expand...
Click to collapse
Yes. The amount of lag may vary slightly between sites but it is still there and annoying. Dolphin made no difference for me. I've tested both the Xoom, Samsung and Acer in stores and they don't seem to have the problem.
The best test for A/B comparing purposes is to just type the numbers 1 thru 9 quickly and see what's left when you are done. For me when I'm done "7" is usually on the screen.
Try this temp fix
1. go to google.com
2. select settings in the upper right and click on search settings
3. disable google instant
This seems much better for me. Others may vary.
Sent from my Transformer TF101 using Tapatalk
I've figured it out. It's a text box issue. Go into XDA forum settings. Change the text box to "simple "and skin to classic and enjoy lag free typing on this forum.
I'm pretty sure ASUS will post an update for this typing lag... althought typing lag has improved only slightly by changing user agent to Tablet (or to Android on dolphin browser)... will just have to be patient on the update
transceiver said:
I've figured it out. It's a text box issue. Go into XDA forum settings. Change the text box to "simple "and skin to classic and enjoy lag free typing on this forum.
Click to expand...
Click to collapse
Makes no difference here (and of course it wouldn't help when using any other website that requires a typed response).
danielsjam said:
Try this temp fix
1. go to google.com
2. select settings in the upper right and click on search settings
3. disable google instant
This seems much better for me. Others may vary.
Click to expand...
Click to collapse
Been there, done that, no help.
I hate the responsiveness of the Asus keyboard, but the stock keyboard does a nice job. I wish the layout was better, but I will take the responsiveness of the stock keyboard over the layout of the Asus one with crappy responsiveness.
nebrando said:
I hate the responsiveness of the Asus keyboard, but the stock keyboard does a nice job. I wish the layout was better, but I will take the responsiveness of the stock keyboard over the layout of the Asus one with crappy responsiveness.
Click to expand...
Click to collapse
Both keyboards are the same for me. I just came back from the mall where I tested a Xoom, Samsung Galaxy Tab , T-Mobile G-Slate and iPad and none of them had any delay anywhere. I simply go to the forum, log in and type 123456789 in an empty reply to a message and see what's left when I am finished typing. The only problematic one seems to be the Asus.
U know what , out of the typing delay frustration i went on to try my most trusted browser for my froyo phone, miren and walla no lag in typing. But since miren is not build for honeycomb there are some fc here n there as expected. But the feature i love most, the smart full screen still works in honeycomb yay !!!
Part from that, it also doesnt have the image tearing issue when u scroll the browser quickly most probably related to hardware acceleration that is implemented on honeycomb browser.
Conclusion,the typing lag is definitely caused by the browser itself or even the webkit itself :-(
Too bad miren's developement stopped :-(
I think there's more than one "typing delay" issue here.
The one that I'm having 1) does not depend on which keyboard is used, and 2) is just as bad on Xoom. Just go to http://slashdot.org, open any story, and try to post a comment there - and watch characters you type being entered at like 1 per second...
I am typing this on the dolphin browser HD which has just been updated today. I am using Smart keyboard pro and cannot notice any lag. This reply is on the XDA 2010 theme.
HasC said:
I am typing this on the dolphin browser HD which has just been updated today. I am using Smart keyboard pro and cannot notice any lag. This reply is on the XDA 2010 theme.
Click to expand...
Click to collapse
I just tried downloading the free trial of Smart Keyboard Pro and keep getting "Purchase Cancelled, error processing purchase."
Hmmm, seems I can't download anything from the Market ... get the same error with Dolphin.

Typing Lag Fix = opera Browser

I Own an Eee Pad Transformer and That Typing lag is Horrendous. Im going to be getting a Gtab 10.1 In the next few weeks and selling my Tab + Dock but thats beside the point. I Made this Thread just for an FYI. for Those who didnt know and wanted a Fix for Typing Lag, Opera Browser Mobile is Perfect. Using Opera Browser Mobile Feels Soo much smoother when typing with NO LAG what so ever. For those who are on ends, You should Try this out. Also an FYI, for people who Think Opera Mobile Just shows Mobile versions of websites, it doesnt. You can set it to a Full Desktop View Now with New Update.
Hope This Helps People out ~ Cheers ~
Edit: Opera Now Supports Flash. Tested and works! yay for updates. Also it Supports desktop without having to go to hidden menu.
"Only Thing Opera is missing is Flash Support."
LOL! That's a pretty major thing to be missing don't ya think?!
akarol said:
"Only Thing Opera is missing is Flash Support."
LOL! That's a pretty major thing to be missing don't ya think?!
Click to expand...
Click to collapse
LOL Yeah but they cant without Source since Opera is built Differently. Gotta wait for Google to release it, If they do. Theyre being picky with HoneyComb. still the Smoothness is worlds different. you'll notice the typing difference right away.
Look like the new version opera mobile 11.1 has a agent setting, support flash, and has a exit button. So no need to go into about:config to set the agent. Too bad the font is still pretty small compare to default and dolphin HD. I havent tried out 11.1 but with 11 there was still some lag when typing on this forum.
http://my.opera.com/operamobile/blog/2011/06/30/opera-mobile-11-1-has-arrived
dazz87 said:
Look like the new version opera mobile 11.1 has a agent setting, support flash, and has a exit button. So no need to go into about:config to set the agent. Too bad the font is still pretty small compare to default and dolphin HD. I havent tried out 11.1 but with 11 there was still some lag when typing on this forum.
http://my.opera.com/operamobile/blog/2011/06/30/opera-mobile-11-1-has-arrived
Click to expand...
Click to collapse
Strange. I Have no Lag. Maybe its because Im using Thumb Keyboard too. I also turned off all Auto Corrections and grammar corrections.
Been using Opera Mobile for a little while. Love this browser, was bothered by the lack of agent setting, but now that can be turned on. Also was able to watch Flash and that worked good.
Really like the browser alot.
I never had lag on my Opera, what settings did you have?
Sent from my T-Mobile G2 using XDA App
Likes
1) typing is indeed much better. no more blue highlights in text boxes which seems to be the cause.
2) text selection is steadier.. the cursor seems to pick the right position more accurately and without the real annoying cursor jumping.
Dislikes
1) when typing this response.. the typing indicator started right in the middle of the reply text box with no way to put it at the top line.
2) font is smaller than stock browser and dolphin HD
3) scrolling is not as smooth as stock browser and dolphin hd
4) loading pages is slower than stock browser and dolphin hd
5) no full screen viewing
6) bookmarks are not as easy to access like dolphin HD
with all that said.. it is such a relief to be able to type without lag and to be able to set the cursor more accurately. I'll stick to opera for now until dolphin or stock gets rid of the lag.
HorsexD said:
Strange. I Have no Lag. Maybe its because Im using Thumb Keyboard too. I also turned off all Auto Corrections and grammar corrections.
Click to expand...
Click to collapse
I am also using the thumb keyboard and have xda set to classic view. The lag comes and goes. There is major lag if I have music playing in the background with either default music player or player pro. This lag is on both my TF and 10.1. I havent tried out 11.1 yet, hopefully there lag is gone.
I just started using Opera and the typing is indeed much better. I think everything is crisper looking too. Everything in Dolphin HD seems soft and scrolling in both Dolphin and the stock browser is nothing to brag about. They may scroll, but content loads after.
HorsexD said:
Strange. I Have no Lag. Maybe its because Im using Thumb Keyboard too. I also turned off all Auto Corrections and grammar corrections.
Click to expand...
Click to collapse
I have two g tabs, and one is unlocked.
I don't experience any of the keyboard lag that everyone writes about.

keyboard lag in browser fixed in touchwiz - but the fix is not in the browser itself

So anyone that has gone from stock honeycomb to touchwiz knows that the keyboard lag in the browser is fixed. Also text boxes highlighting in blue when you type in them is gone too (the two were believed to be related).
I had assumed that Samsung modified the browser.apk somehow to fix the issue. It turns out that that is not the case. How do I know? Because the lag and blue box are also gone on the dolphin HD and dolphin pad browsers when installed on a touchwiz ROM. The lag and blue box are present in dolphin browsers in stock honeycomb roms, but not in touchwiz roms.
So this tells me that the core issue is a framework or something that the browser accesses. Maybe the webkit engine itself, I don't know. Now the question is, can we extract that fix and apply it to non-touchwiz roms? If it is a Google code fix that samsing implemented, then maybe. If Samsung rewrote their own webkit and tied it into touchwiz, then probably not.
Any developers interested in finding out where the fix is, and try to apply it to non-touchwiz roms? I am going to poke around but I am probably under qualified for this.
cursor problem still
I have a question about this fix, which might be related to what your trying to find out.
I realized the keyboard input lag is fixed, but not the weird cursor movement when you try to edit something you've already typed. It still lags and still doesn't follow touches very well. Most noticable wwhen trying to go back to a mistyped word on this xda post.
I'd guess this is bizarre cursor input is related too?
EvoXOhio said:
Any developers interested in finding out where the fix is, and try to apply it to non-touchwiz roms? I am going to poke around but I am probably under qualified for this.
Click to expand...
Click to collapse
Simple answer: no, not without sources.
DocRambone said:
Simple answer: no, not without sources.
Click to expand...
Click to collapse
Honeycomb being closed source is the greatest source of frustration as a tinkerer and probably one of the many reasons why Android tablets still fail to sell in any appreciable numbers.
sassafras
DocRambone said:
Simple answer: no, not without sources.
Click to expand...
Click to collapse
I'm not sure I agree with this entirely. If we were trying to fix it ourselves, then I agree with this statement. However it's already fixed in Touchwiz. Touchwiz has already been ported to other tablets like the Acer Iconia, so it's hackable. In theory, as long as the fix is not part of the Touchwiz framework, but rather in the google framework, we should be able to extract the relevant files and shove them into stock honeycomb. it may be ugly and it may require source to optimize it, but i think we can do something with it.
I don't often have to type in a text box while in the browser on the GT but when I do I feel like breaking this thing in fnin half...
The swype keyboard inserts spaces in spots that I don't really need it to and trying to backspace is a nightmare.
I am sure there is a setting somewhere in swype to change this but I may be updating the tab today at the NYC event so I will worry about it afterwords. I may try thumb keyboard instead of swype also.
Typing lag is due to the "Instant" feature in Google. It's a javascript issue.
akarol said:
Typing lag is due to the "Instant" feature in Google. It's a javascript issue.
Click to expand...
Click to collapse
Source?
sassafras
akarol said:
Typing lag is due to the "Instant" feature in Google. It's a javascript issue.
Click to expand...
Click to collapse
No it's not. This happens on form boxes everywhere like here at XDA. it's fixed in touchwiz.
Hi,
Can anyone post you s/w version screen after the TW update please ? I have a 3G enabled European 10.1 Tab with TW and still seem to suffer from the keyboard lag issue in the browser. Also the blue highlight is still there. Possibly I still run an older version of TW.
bandit_knight said:
Hi,
Can anyone post you s/w version screen after the TW update please ? I have a 3G enabled European 10.1 Tab with TW and still seem to suffer from the keyboard lag issue in the browser. Also the blue highlight is still there. Possibly I still run an older version of TW.
Click to expand...
Click to collapse
I don't have my tablet with me, but go to the development section and look at the ROMs that DocRambone has posted. It's fixed in those.

Chrome problems with hardware keyboard

Problem #1: lack of hotkeys. Control T, Control F, etc do not work.
Problem #2: "Shift + c" is mapped to "backspace", and "Shift + b" is bound to enter. The only way to type a capital C or B in Chrome is to hit the key twice in rapid succession, which first causes a backspace/enter, then types the letter.
If you all could so kindly go into Chrome, go to settings, click Under The Hood, click Send Feedback, and write off a quick description of the problem to Google, let's try to get them to fix it. Google's support is typically pretty lackluster, and it generally takes many people acknowledging and reporting a problem to get it fixed!
I'm still god damn floored by how awesome Chrome is. JSNES (NES emulator written in JavaScript) runs at 25 FPS in Super Mario Bros. That benchmark alone gets me a little hard, as my old notebook doesn't even handle it that well. But with the above two problems, it's kinda annoying to use it, especially the lack of control T to open new tab as that's just become instinctual over the past 8 years.
Sent from my Transformer TF101 using Tapatalk
Huh...I can't reproduce the issue on mine (Shift-B and Shift-C work fine). No CTRL+T or CTRL+F, but the cut/copy/paste shortcut keys work fine.
Gary13579 said:
I'm still god damn floored by how awesome Chrome is. JSNES (NES emulator written in JavaScript) runs at 25 FPS in Super Mario Bros. That benchmark alone gets me a little hard, as my old notebook doesn't even handle it that well. But with the above two problems, it's kinda annoying to use it, especially the lack of control T to open new tab as that's just become instinctual over the past 8 years.
Click to expand...
Click to collapse
I'm not familiar with JSNES, what's it do in the old browser? I ask because on a completely stock, just-wiped US TF101 running ICS, I get a slightly (but outside margin of error) *worse* Javascript score in the Chrome beta, than I do with the stock browser. I also find the scrolling lag on Chrome beta to be awful -- the stock browser is orders of magnitude better.
I want to like Chome, and I'm sure I will eventually when the bugs are worked out, but so far it isn't usable for my purposes.
Perhaps related to the scrolling thing, I also noticed if I check chrome://gpu-internals/ that I get "WebGL: Unavailable. Hardware acceleration disabled." and "Problems detected. WebGL has been disabled, either via about:flags or command line."
Edit: No, not related. Just googled and now know WebGL's for 3D graphics.
laslow said:
Huh...I can't reproduce the issue on mine (Shift-B and Shift-C work fine). No CTRL+T or CTRL+F, but the cut/copy/paste shortcut keys work fine.
Click to expand...
Click to collapse
Where did you try it? It only occurs in text boxes within the actual page. In the URL bar and other places, Shift C/B work fine, but if you try to respond to this post in Chrome and use shift C, it should backspace. It also makes capital C and B impossible to enter in password fields -- really annoying.
knoxploration said:
I'm not familiar with JSNES, what's it do in the old browser? I ask because on a completely stock, just-wiped US TF101 running ICS, I get a slightly (but outside margin of error) *worse* Javascript score in the Chrome beta, than I do with the stock browser. I also find the scrolling lag on Chrome beta to be awful -- the stock browser is orders of magnitude better.
I want to like Chome, and I'm sure I will eventually when the bugs are worked out, but so far it isn't usable for my purposes.
Perhaps related to the scrolling thing, I also noticed if I check chrome://gpu-internals/ that I get "WebGL: Unavailable. Hardware acceleration disabled." and "Problems detected. WebGL has been disabled, either via about:flags or command line."
Edit: No, not related. Just googled and now know WebGL's for 3D graphics.
Click to expand...
Click to collapse
It ran fine in the HC browser, just slow. To be fair I checked it in ICS browser and it gets the same FPS as Chrome, glad to know stock ICS browser is just as capable, but it doesn't handle the actual page anywhere near as well as Chrome does, for ex it cannot hook the keys to get keyboard input like Chrome does. I suspect Chrome's compatibility far surpasses that of the stock browser, perhaps costing it a bit of performance in benchmarks?
Haven't really had any scrolling issues whatsoever.
Sent from my Transformer TF101 using Tapatalk
Gary13579 said:
It ran fine in the HC browser, just slow. To be fair I checked it in ICS browser and it gets the same FPS as Chrome, glad to know stock ICS browser is just as capable, but it doesn't handle the actual page anywhere near as well as Chrome does, for ex it cannot hook the keys to get keyboard input like Chrome does. I suspect Chrome's compatibility far surpasses that of the stock browser, perhaps costing it a bit of performance in benchmarks?
Click to expand...
Click to collapse
Well, to be equally fair in return, it was only a very slight difference in benchmark, and it was just one benchmark -- Sunspider -- I didn't try any others.
Gary13579 said:
Haven't really had any scrolling issues whatsoever.
Click to expand...
Click to collapse
Interesting. Pretty-much any long web page (say, Engadget or similar), if I load the page, let it finish loading, then swipe my finger across the screen to scroll, I'm instantly into a white page until I stop scrolling, or at the very least I get significant stuttering. With the stock browser, the same trick gives me a perfect preview of the fast scroll, so I can stop it in the right place with a tap of my finger.
Even when scrolling slowly, Chrome is noticeably stuttery for me, nowhere near as smooth as the stock browser's scrolling.
Gary13579 said:
Problem #1: lack of hotkeys. Control T, Control F, etc do not work.
Problem #2: "Shift + c" is mapped to "backspace", and "Shift + b" is bound to enter. The only way to type a capital C or B in Chrome is to hit the key twice in rapid succession, which first causes a backspace/enter, then types the letter.
If you all could so kindly go into Chrome, go to settings, click Under The Hood, click Send Feedback, and write off a quick description of the problem to Google, let's try to get them to fix it. Google's support is typically pretty lackluster, and it generally takes many people acknowledging and reporting a problem to get it fixed!
I'm still god damn floored by how awesome Chrome is. JSNES (NES emulator written in JavaScript) runs at 25 FPS in Super Mario Bros. That benchmark alone gets me a little hard, as my old notebook doesn't even handle it that well. But with the above two problems, it's kinda annoying to use it, especially the lack of control T to open new tab as that's just become instinctual over the past 8 years.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Yep. I concur... The shift c, b is a pain in the ass. Also having the lagging problems.
Anyway, i'm back to stock browser.
control c and control v work fine for me, make sure you have asus keyboard set
wilx said:
control c and control v work fine for me, make sure you have asus keyboard set
Click to expand...
Click to collapse
I never said they didn't. Try reading, this time.
Sent from my Transformer TF101 using Tapatalk
Gary13579 said:
Where did you try it? It only occurs in text boxes within the actual page. In the URL bar and other places, Shift C/B work fine, but if you try to respond to this post in Chrome and use shift C, it should backspace. It also makes capital C and B impossible to enter in password fields -- really annoying.
Click to expand...
Click to collapse
Well, I'm using the hardware keyboard to type this reply -- BBBBCCCCCBCBCBC -- and I used it to login here and a number of other places. I'd say that no, I really can't reproduce it, whether the Asus, Android, or Swype virtual keyboard is enabled along with the hardware keyboard.
laslow said:
Well, I'm using the hardware keyboard to type this reply -- BBBBCCCCCBCBCBC -- and I used it to login here and a number of other places. I'd say that no, I really can't reproduce it, whether the Asus, Android, or Swype virtual keyboard is enabled along with the hardware keyboard.
Click to expand...
Click to collapse
Interesting. Lates t version of chrome from the market? What region ICS version? What version dock? You are doing this in CHROME, right? It's affecting a lot of us, interesting that it works for some. The same problem even occurs on the TF Prime. You spamming the keys doesn't really show that it's working though, as if you hold shift and hit "c" twice, it will backspace once then type out C, but when you press down shift, hit c, then let go of shift, it only does a backspace.
Sent from my Transformer TF101 using Tapatalk
US region ICS, dock version EP101-0213. Yes, this is the latest Chrome Beta from the market. Yes, I'm actually using the hardware keyboard, and yes I'm actually typing this through Chrome. The keyboard spam was for effect - if you read my post you would have noticed I also said that I had used the above to login in to different places (the problem doesn't happen text inputs, text areas, or password inputs). Yes, other people are having the issue, but I'm not.
If you're interested, I did a clean install of the official .21 HC firmware (with a wipe), then did the OTA update and wiped it again before rooting it.
Hadn't actually tried it myself, so here's a fourth (fifth? forget how many replies we've had...) opinion:
* Ctrl-T, Ctrl-F, Ctrl-N: Do not work
* C and B type just fine for me on the first try, by holding down shift and typing the letter on the physical keyboard, in Chrome. That's how I just did it, in this post. No backspace, no enter for either combination.
I have a B60 dock with EP101-0213, a just-wiped, unrooted, stock ICS US build, and although I'm using the physical keyboard to type the whole of this post, I'm set to the stock ICS soft keyboard, not Asus' modified one.
I, too, did a double-wipe, once before updating and once after ICS was installed.
I can only reproduce this when I have the ASUS keyboard selected. Using the normal Android one it's not reproducable.
So, that's a workaround if anything.
Radiofodder said:
I can only reproduce this when I have the ASUS keyboard selected. Using the normal Android one it's not reproducable.
So, that's a workaround if anything.
Click to expand...
Click to collapse
Just tested that myself: yes, Shift-C and Shift-B don't work when the Asus soft keyboard is selected.
This is an Asus problem, not a Google problem.
Radiofodder said:
I can only reproduce this when I have the ASUS keyboard selected. Using the normal Android one it's not reproducable.
So, that's a workaround if anything.
Click to expand...
Click to collapse
Interesting, this does fix it for me now, even though I had tried it previously. It makes me wonder, what "compatibility" does ASUS speak of when you get the warning message using stock ICS keyboard with the dock? Thinking back to when I was using thumb keyboard on HC, I never noticed any issues not having the ASUS keyboard enabled.
Sent from my Transformer TF101 using Tapatalk
Beats me, I've yet to find any slight incompatibility between the physical keyboard and the stock ICS keyboard. I wonder if they're not suggesting an incompatibility with the stock one, but rather practicing CYA with respect to all the other third-party keyboards on the market?
Does the ASUS keyboard need to be used only if you want access to all of the hotkeys on the dock (Transformer Prime)? Or is there any other reason not to switch over to the standard keyboard to avoid the SHIFT-C bug?
There is something specifically related to Chrome here. The standard browser has no problem with SHIFT-C or B using the dock w/ASUS keyboard selected. Chrome is the only application I have found that has this problem.
shuddles said:
Does the ASUS keyboard need to be used only if you want access to all of the hotkeys on the dock (Transformer Prime)? Or is there any other reason not to switch over to the standard keyboard to avoid the SHIFT-C bug?
Click to expand...
Click to collapse
Can't speak to the Prime, but with the TF101, the hotkeys work just fine regardless of which soft keyboard you're using, the Asus one or the stock one. Just tested, I don't use the Asus one, I'm on the stock ICS keyboard but I just tested and absolutely every hotkey works correctly regardless.
The only problem I've encountered is that special characters specific for your language will not work properly. Or in my case, åäö. You can still do capital Bs and Cs - just click B and C again after typing it and it should pop. Fiddly as hell, but I'm sure if enough users report it something will be done.
Bloody' ell, the Asus keyboard isn't exactly a thing of dreams.
Radiofodder said:
The only problem I've encountered is that special characters specific for your language will not work properly. Or in my case, åäö. You can still do capital Bs and Cs - just click B and C again after typing it and it should pop. Fiddly as hell, but I'm sure if enough users report it something will be done.
Bloody' ell, the Asus keyboard isn't exactly a thing of dreams.
Click to expand...
Click to collapse
Interesting, so for native English speakers, there's basically no reason to use the Asus soft keyboard then. Unless for some strange reason you like it, that is.

Categories

Resources