Issues with Latest Chrome Beta - Samsung Galaxy Nexus

Hi All,
I received the latest update for the Chrome Beta on my GNexus, and it now seems to have a big issue with the wikipedia mobile site.
If you got to a page that has a table at the top, for instance:
http://en.m.wikipedia.org/Helium
If you then try to scroll the page, it refuses to move the page unless you touch the screen outside of the top table.
I have submitted a bug report to Google, but I was wondering if anyone else had found the same issue?

yup I see what you mean, it's happening on mine too....I needed to touch on the tables edge or outside it that is in order to scroll the page
Sent from my Galaxy Nexus using Tapatalk

Same here. It has happened to me only with wikipedia mobile site. Everything's going great with other sites until now...

Same for me, only on facebook though
Sent from my GT-I9100 using XDA

How did you get the latest update? I don't think I got mine, and it's not showing up as needing to update on the Play Market.
I have version 18.01025.133

onthecouchagain said:
How did you get the latest update? I don't think I got mine, and it's not showing up as needing to update on the Play Market.
I have version 18.01025.133
Click to expand...
Click to collapse
You probably got auto-updated. 18.0.1025.133 is the latest when looking in the "about Chrome" tab in the settings menu.

Ah, thanks.
And I too notice this issue with Wiki. The heck...

Mine as well. Much slower load times as well. Very disappointing update.

I have an issue more with the loading of pages. Before, if I scrolled down, it would already have the entire page loaded. Now, if I scroll down, I tend to get a teal colored bottom half covering whatever parts of the page weren't visible, as if it's loading the page as I scroll.

i cant even get my latest google chrome to load, i keep getting force closes right as i open it.

Not work with low dpi, you need to set 240 dpi. Hope an update coming soon for low dpi :-(

i thought i was the only on with this problem

Google chrome .16. It works fine. There is a kink in the latest chrome and aokp and cm9 roms
http://www.mediafire.com/?uyjta1swtp0w459
Yw.
Thanks if I helped
Sent from my Galaxy Nexus using Tapatalk 2

Its disappointing chrome takes a good 5 seconds or so to load when you first start it up.

this is fixed now (by wikipedia).
edit: but the redirection to wikipedia's mobile site (en.m.wikipedial) is buggy now ...
edit2: cleared my cache (for the first time) and the problem is gone.

Related

Browser crashes on some pages with Froyo

Hi,
Noticed the default browser seems a little less stable after upgrading to Froyo.
On some pages it just dies. Can open the page fine in Opera Mini.
Emailed HTC support and they suggest a hard reset.
Didn't expect that to work and I was right.
Anyone else seen this?
Here is a page which causes a crash for me. Please try it and see if it does the
same on your Desire.
http://www.bbc.co.uk/news/entertainment-arts-11079055
Thanks
Peter
I've seen it crash out on some pages. Sometimes just the scroll is completely disabled and unable to be used. A bit annoying to say the least and I've found no fix to it yet.
I have noticed it too, it seems it happens when on a bbc (could be others too) site with more than one flash video content window on the same page.
Yes crashes for me too... seems to be related to Javascript - the page will load if you disable it...
Only seems to happen on BBC pages... only half joking when I say its a deliberate anti-Android measure from the Apple-loving BBC...
Sent from my HTC Desire using XDA App
Same here. Especially when being brought to the browser via HTC Peep or Seismic.
Same here, have had lots of crashes to desktop with stock froyo when loading www.bbc.co.uk/football
Thanks all. HTC's response of send your Desire back for a repair now seems like a poor answer from them. Did anyone notice this happening before the 2.2 Froyo update?
Or perhaps someone on 2.1 can see if that link crashes now.
This has been happening ever since the 2.2 upgrade.
Wonder if HTC will acknowledge its the firmware, not the hardware. Was fine before. Also, if you disable javascript, load the page, then re-enable it and refresh it'll often play the video without crashing, but as soon as you navigate to another page and try to play another video, it's back to the homescreen!
Odd that they would prefer to get me to send a handset back rather than say... sorry.. it's a bug. S/W bugs happen. As long as they get fixed not a big deal (well no in the mobile phone sector). Planes
I have responded say that I don't believe it's a hardware problem. Opera loads the page fine. See what they come back with.
www.bbc.co.uk/f1 was causing the default browser to quit, but today it is working fine.
copex said:
www.bbc.co.uk/f1 was causing the default browser to quit, but today it is working fine.
Click to expand...
Click to collapse
I've only seen this on BBC pages so far - there were a couple of threads in the Q&A section about this a few days back (here), but to date I know of no solution other than disabling the plugins.
I've just come back from a month travelling the states and since the official froyo release hadn't come out when I left I have been using Android 2.1 daily whilst in the USA to keep up with the football news at bbc.co.uk/football and never had a problem. Since I got back to the UK and upgraded to 2.2 I have problems accessing this page without getting a crash back to the homepage.
Therefore, I am certain that this is a problem caused by the official 2.2 rom
it's good to know I'm not the only one having these problems on the BBC site. I've been running 2.2 since the OTA launch and have been having no problems until now.
The problem seems to have started (at least for me) some time this week, as I was able to stream some of the BBC F1 content on Wednesday(25/08). It was only when I was trying to access content yesterday (27/08) that this problem started.
Is this happening just with the BBC, or are there other sites that have this issue?
I first noticed this problem on Monday 23rd August (when i updated to Froyo) and haven't encountered it on any other sites yet.
I have also tried the stock OTA 2.2 and a rooted custom 2.2 rom (leedroid) and both of them would crash on the bbc site
I seem to have fixed it for now. I just cleared data from the internet application and no more crashes on BBC pages. You will lose bookmarks so make sure these are syncd with HTC sync 3 first. This may be a temp fix, so let's see how long it lasts.
Sent from my HTC Desire using XDA App
It's caused by flash overload as was mentioned above.
With the stock browser open go to Menu / More / Settings / Enable Plugins and use the arrow to select 'on demand' from the list.
Flash objects on the page will be replaced by a green arrow and will only load when clicked.
The pages should load ok now. If you have several windows open and try to load a heavy flash object the browser will force close.
It's not a perma fix but plugins 'On Demand' allows you to browse at least.
That's not necessarily always the case here. I only use on-demand and many BBC and such sites are crashing the browser in 2.2 whereas they aren't in 2.1. Now all those pages have embedded Flash content and there is never a crash on a Flash-less page so it might well be an Adobe Flash issue. I had no crashes before the last Adobe update.
-----------------------------------
- Sent via my HTC Desire -
elbowz said:
Yes crashes for me too... seems to be related to Javascript - the page will load if you disable it...
Only seems to happen on BBC pages... only half joking when I say its a deliberate anti-Android measure from the Apple-loving BBC...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
How do you disable Javascript?
In the browser Settings there's an option to enable/disable it from there...
Sent from my HTC Desire using XDA App
squared1200 said:
it's good to know I'm not the only one having these problems on the BBC site. I've been running 2.2 since the OTA launch and have been having no problems until now.
The problem seems to have started (at least for me) some time this week, as I was able to stream some of the BBC F1 content on Wednesday(25/08). It was only when I was trying to access content yesterday (27/08) that this problem started.
Is this happening just with the BBC, or are there other sites that have this issue?
Click to expand...
Click to collapse
It's not just the bbc site,I've got this website where I watch live football online via my desire.it was fine before yesterday,but now when trying to view some of the matches it just crashes and returns me to my homescreen.it was a good thing I didn't do a factory reset,it would've been a waste time.
Sent from my Archos5 using XDA App

Browser issue please help

Hello, got a new nexus today and so far love it, but have found one major issue and hoping its just a bug or something i can fix, when using my net browser either my stock one or Dolphion and i google something and select images i see the images tiled like normal but cannot click on one and go to the larger image and scroll through and also i cannot go past page 1, if i select page 2 or whatever it does nothing...please help...
Nexus nub said:
Hello, got a new nexus today and so far love it, but have found one major issue and hoping its just a bug or something i can fix, when using my net browser either my stock one or Dolphion and i google something and select images i see the images tiled like normal but cannot click on one and go to the larger image and scroll through and also i cannot go past page 1, if i select page 2 or whatever it does nothing...please help...
Click to expand...
Click to collapse
Ya that's happened to me once or twice, try force close browser or even rebooting the phone and it should be back to normal. I don't know why that happens.
im not the developer of it, but try the maxthon browser... its not the "simpleest" or the tinyiest, but the main reason for me to use it, that its the ONLY browser that works with the java based groupwise web overlay.
all other browsers slides all graphics to a non visible area or something... kinda weird.
YOUR problem should be gone with that browser too ... dont ask me why
Nexus nub said:
...when using my net browser either my stock one or Dolphion...
Click to expand...
Click to collapse
Try Google Chrome for Android. Once you'll go Chrome, won't come back.
It's much better and faster. The only thing it's missing is Flash support.

[Q] Problem while using Chrome on Note 8

I am using my Note 8 N5100 since last two months. I mostly use Chrome as my default Internet Browser.
Recently I have updated the chrome app (The update brings a nice feature: full screen navigation). Since then I am having this peculiar problem.
1. A part of the web-page usually getting hidden under the navigation bar. If there is any link in that area, it is nearly impossible to click on that as it is hidden.
2. Tapping exactly on the link is not working always. I have to tap a little lower to select the exact target link. Surprisingly this problem does not exist if I zoom the page and tap on the desired link.
This problem is only with chrome browser. The stock android browser/dolphin/UC works fine.
This is my first week with my new brown note 8.0 and I noticed the same issue. In just went back to stock browser and will wait for next up date for chrome and hope it fixes it.
Same issue as well.
Sent from my GT-N5120 using xda app-developers app
Seems to be fixed in the latest Chrome Beta.
Sent from my GT-N5120 using xda premium
I have the same issue.
I think your problems 1 and 2 are the same problem.
The link you touched is in the correct place, but the page displays a little bit higher.
Search is your friend:
http://forum.xda-developers.com/showthread.php?t=2343712
This is a known issue and they are working on it.
I'm also having this issue, hopefully it'll get fixed soon
Here's a workaround using Xposed Framework:
http://forum.xda-developers.com/showpost.php?p=43569866&postcount=17
Actually, just download the Chrome BETA which was refreshed this past Thursday. It fixes the issues you describe and works extremely well on my Note 8..

Chrome is not full screen

When I open chrome beta it is not full screen. How do it get it to its usual full size?
Use chrome.
#stayparanoid
Yea I switched to chrome. I guess not using beta isn't that big of a deal. Thanks for the response
Sent from my XT1096 using Tapatalk
I'm going to jump on this thread while it's still fresh, if nobody minds.
I just switched my Nexus 5 from CM11 to PA4.6b6 two days ago, and this is the only remaining issue. I launched Chrome Beta the first time, and it showed up as a small, greyed window in the middle of my screen. Eff that, I said, and looked for advice on the internet. I found this thread, installed Chrome itself, launched that and was pleased to see it occupy the full screen (not immersively, mind you).
I just tapped my Chrome shortcut again moments ago to find that it was now opening in that little, greyed out window. Wtf, I wondered. I tried Beta. Same thing. I closed both windows by tapping the home nav, and then i opened Chrome again from the recent apps list. Et voila, it's back to full size.
My questions are "wtf?", "how do I make it just use the available real estate and not open in that terrible tiny dark window?", and "should I file a JIRA issue for this? Is this srsly expected behavior?"
I love the ROM, I love the work you guys do, and I wanna be helpful, so let me know if there's anything else I can provide or tell you about my experience.
Thank you!
Well, Google pushed their beta changes to stable. The problem is a flag that Google set that launches chrome in windowed mode...
We are trying to figure out a way around it but with work heavy on lollipop right now, kitkat may fall by the wayside.
The temporary solution is to go back to an older version of chrome.
#stayparanoid
I can get behind the idea of work being heavy on Lollipop, so no worries there. I'll be seriously excited to see new builds based on 5.0, so work away! I presume there's no ETA on that as of yet, right? :angel:
No EtA
#stayparanoid
Workaround:
Open Chrome
Hit Home
Relaunch chrome from recent apps
As long as Chrome isn't killed, it will remain full screen.
I also got a backup from Chrome v38.
Will share on request.
Ratmak said:
My questions are "wtf?", "how do I make it just use the available real estate and not open in that terrible tiny dark window?", and "should I file a JIRA issue for this? Is this srsly expected behavior?"
Click to expand...
Click to collapse
No, it's not expected behavior
https://code.google.com/p/chromium/issues/detail?id=423685
franatic08 said:
Workaround:
Open Chrome
Hit Home
Relaunch chrome from recent apps
As long as Chrome isn't killed, it will remain full screen.
Click to expand...
Click to collapse
Nicely found, confirmed on a n7
For anyone running Xposed. Download Xhalofloatingwindow module and blacklist Chrome. That worked for me
Sent from my SGH-T999 using XDA Free mobile app
stastnysnipes26 said:
When I open chrome beta it is not full screen. How do it get it to its usual full size?
Click to expand...
Click to collapse
I'm sorry, but do you mean Chrome beta on Paranoid Android, or just Chrome Beta in general? I have used Chrome Beta before, but this has never happened to me.
cyanogen_patrick said:
I'm sorry, but do you mean Chrome beta on Paranoid Android, or just Chrome Beta in general? I have used Chrome Beta before, but this has never happened to me.
Click to expand...
Click to collapse
Any ROM that has floating mode.....
ANY ROM.
Google has fixed it in their latest beta though.
#stayparanoid
Pirateghost said:
Any ROM that has floating mode.....
ANY ROM.
Google has fixed it in their latest beta though.
#stayparanoid
Click to expand...
Click to collapse
Oh, okay.

Weird behaviour scrolling lists like amazon or aliexpress.

Hello there,
I recently purchased a used HTC 10 (original purchase date ~5.2016)...
Every time I am searching the flash deals in the Amazon App (I think I have similar problems with AliExpress too, but I am not able to reproduce this on poruse. Amazon is every time making these problems.), I have this weird scrolling behavior.
Procedure:
1. Open App - enter flash deals
2. scroll list, click on entry, go back
3. scroll further
---> Screen will return to the position, where you last checked one entry by clicking on it.
It looks like the "keyboard-choosing-cursor" is stuck there. (Yellow frame around the entry), and I can't go much further down, until it will scoll up again.
Fixing is going back to previous page, going back again, scrolling down to the last items I was.
This is not the workaround I could live with, since I am very limited on using these apps.
Already shoot some google searches, but only got things like "not responsive touch" etc...
Other apps seems normal, eBay has no such problem since now...
Amazon seems to have this problems only within the flash-sales, not the normal.
For AliExpress I wasn't able to reproduce this on purpose.
Is this a app specific fault? Or is it my device?
I am coming from a M7 with CyangenMod 13 (6.0.1) and I am running on the 10 6.0.1 Stock...
Someone else experiencing this? Or heard about it?
I am very clueless..
Thanks
houston
I've noticed this behaviour too with Swipe for Facebook and Chrome Browser. I could reproduce with Swipe by opening an external link with, for example, a floating browser like Flynx, returning to Swipe app i can't scroll well, same behaviour as your. I noticed that to the dev and it comes with a fix, but in the same time i had an update from Google Webview (Beta) in the Play Store, so i can't say who was the guilty one., but I don't have this problem now.
I make these statements because both Swipe for Facebook, Chrome Brtowser and Amazon use html wrapper/webview, but i can be wrong.
I just received the instruction to update webview from the amazon support.
Well ... I oped out the beta program, reinstalled webview and now I am fine
I have read your post to late. But you are mentioning webview too, so I think it is all about webview. Do you use the beta too?
Conclusion for me:
WebView Beta was the culprit. Reinstalling the stable fixed it for me.
houston_ said:
I just received the instruction to update webview from the amazon support.
Well ... I oped out the beta program, reinstalled webview and now I am fine
I have read your post to late. But you are mentioning webview too, so I think it is all about webview. Do you use the beta too?
Conclusion for me:
WebView Beta was the culprit. Reinstalling the stable fixed it for me.
Click to expand...
Click to collapse
Today another update from WebView BETA
benzo said:
Today another update from WebView BETA
Click to expand...
Click to collapse
Fixing it again?
I think I will stay with stable
It happens with beta chrome and webview. If an item is selected it will scroll back to that item. It has to stay in the viewport. Just deselect the item to fix it.

Categories

Resources