Develop Bugs

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

Issues with Latest Chrome Beta

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.

Non stock chrome issue/bug on g3?

Anyone else getting the bug on updated/non stock chrome that causing the browser to become blank or just stuck at the background color after it tried to load/reload the page you want to view?
This bug occur when I leave the chrome on for too long in the background with several tabs open or heavy web pages
The only way to fix this is by closing tabs and clearing the app itself from ram
This issue occur on both stable and beta version of chrome, any chrome other than the one provided with stock rom
Anyone else experiencing this? Any fix/solution?[emoji55]

me dude. i just had enough of it and removed the update and now it's all back to normal.

Yeah removing the update can fix it but then it defeat the purpose of having update capability, is there any way to make google aware of this?

nap007 said:
Yeah removing the update can fix it but then it defeat the purpose of having update capability, is there any way to make google aware of this?
Click to expand...
Click to collapse
I am also having this problem. The issue is known to Google, if you research it. We have to wait for an update to see it go away. It's a sad state of affairs. I like Chrome and now I can't use it. And it ruins my exp3ri3nce with my G3, as the problem is practically non-existent on my N7.

F_T_B said:
I am also having this problem. The issue is known to Google, if you research it. We have to wait for an update to see it go away. It's a sad state of affairs. I like Chrome and now I can't use it. And it ruins my exp3ri3nce with my G3, as the problem is practically non-existent on my N7.
Click to expand...
Click to collapse
According to a google community thread, apparently this is not an lg g3 exclusive issue, this happened on other devices as well and look pretty random
Hopefully a fix soon come because I've tried other browsers and while some of them are nice but they tend to eat much more battery compared to chrome

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.

Large image files not appearing. Moderately urgent.

My OnePlus 5T doesn't show large image files on browsers. I checked on a different phone and it all worked fine. I tried Chrome and Firefox Focus and got no luck. I tried reboot, reinstalling the apps, deleting cache but nothing worked. I did some testing and I think an image of some particular number of pixels and above doesn't appear.
The largest image I got that shows up is 3649*4543, 16,577,407. The smallest image that doesn't is 3923*4656, 18,265,448.
(I thought I would add links but since I'm a new user, I am not allowed to include links, I don't think giving partial links to bypass this policy is justifiable, so...)
Edit8: Now I can post with URLs.
For the former: https://upload.wikimedia.org/wikipedia/commons/5/53/Farida_Arriany,_c._1960_(signed).jpg
For the latter: https://upload.wikimedia.org/wikipedia/commons/8/8f/United_States_Declaration_of_Independence.jpg
And when I try the latter, I get this.
http://imgur.com/X2k6doV
The firmware version: OxygenOS 5.1.7
Just to be sure: It is not that loading isn't completed.
Edit6: To be clear, the 3923*4656 file is not corrupted or anything. It works perfectly fine on my previous phones and a friend's phone. Also, Snehasish1994 confirmed me that it works fine. I mainly use the 3923*4656 file because it's public domain.
Edit10: I've been mistaking snehasish1994 for snesish1994. I apologize.
This is really strange. Strongly hope someone can help me out.
Edit1: Maybe this issue is limited to JPEG files. A bigger PNG file of the resolution of 4300*5500 appeared on a different website. It complicates the issue further. I can't even think of any cause.
Edit2: I tried "Download link" on the latter 3923*4656 file. I was able to download and see it on Google Photo. However, I couldn't see it when I tapped "Open" upon the completion of download and opened the file in, I guess, Chrome, all I saw were blackness and a small square at the centre.
Edit3: I found that I cannot upload the bigger 3923*4656 file on Twitter. Twitter responds "Some of your media failed to load" right after I finished selecting it for uploading. I think it meets the file requirements of Twitter. And what's more maddening is that the 4300*5500 PNG file I mentioned earlier could be uploaded despite not meeting the requirements. I think this has confirmed my suspicion that something, be it Chrome or some system service or whatever, is refusing to load or process and render large image files (most likely limited to JPEG files) for apparently no reason. I am inclined to believe that this is purely software related issue.
Edit4: And now on Imgur I was able to upload the 3923*4656 JPEG file. This is insane. I really, really hope someone of knowledge will help me out.
Edit5: I tried uploading the 3923*4656 JPEG file again. On Tumblr it was successful, both from Chrome and the Tumblr app. On Pixiv it was a failure from Chrome. On Imgur, as I tested earlier, it was successful when I chose "Upload from Device" but it seems to have failed when I chose "Paste Web URLs" from Chrome. I didn't try the Imgur app.
Edit7: Since reboot and reinstall don't work, I suspect that it is not easily fixable via usual settings and such. Maybe clean flash?... I don't know.
From the fact that on Tumblr and Imgur I can upload the 3923*4656 JPEG file, I suspect that the process that is required on some sites during attaching large image files is not properly working. And this process may also be related to image rendering.
Edit9: It seems that those images are actually loaded into Chrome, or browsers but they just don't get displayed.
I think this is the case because:
1. I was able to download the image on (https://upload.wikimedia.org/wikipedia/commons/8/8f/United_States_Declaration_of_Independence.jpg) via Option > the download button on Chrome.
2. I downloaded a whole page (https://shakespearedocumented.folger.edu/file/details/151) as an mhtml file, again via Option > the download button on Chrome. When I view it on my OnePlus 5T the image didn't appear expectedly but when I view the same file on a PC offline running Windows 10, the image was displayed. So it is clear that the image is actually contained in that mhtml file, thus I think it is safe to say that the image is actually loaded into Chrome. But it does not show up somehow.

Can you message me the link so I can check that for you?

peisi said:
My OnePlus 5T doesn't show large image files on browsers. I checked on a different phone and it all worked fine. I tried Chrome and Firefox Focus and got no luck. I tried reboot, reinstalling the apps, deleting cache but nothing worked. I did some testing and I think an image of some particular number of pixels and above doesn't appear.
The largest image I got that shows up is 3649*4543, 16,577,407. The smallest image that doesn't is 3923*4656, 18,265,448.
(I thought I would add links but since I'm a new user, I am not allowed to include links, I don't think giving partial links to bypass this policy is justifiable, so...)
The firmware version: OxygenOS 5.1.7
Just to be sure: It is not that loading isn't completed.
This is really strange. Strongly hope someone can help me out.
Click to expand...
Click to collapse
I wonder if data saver is the culprit!

intoxicated.mad said:
I wonder if data saver is the culprit!
Click to expand...
Click to collapse
Yes, I thought that too. But I leave them off for the whole time. I just double checked the setting it was off. Besides I do not have that option on Firefox Focus. Just to make sure, I understand that there is no data saving option on OnePlus 5T itself. Am I right? The battery saving is obviously off.
Snehasish1994, PM'd you. Thanks.

Is it possible that my OnePlus 5T is defective, even though everything else seems to be fine? I got it only few days ago.

peisi said:
Is it possible that my OnePlus 5T is defective, even though everything else seems to be fine? I got it only few days ago.
Click to expand...
Click to collapse
Are you on stable or open beta??
May be you should try by switching channel or just wait until New Android version is released :good:

intoxicated.mad said:
Are you on stable or open beta??
May be you should try by switching channel or just wait until New Android version is released :good:
Click to expand...
Click to collapse
I'm on stable. I don't have a good memory but as far as I can remember, I got mine with Android 7.1.1 installed. Then I got OTA twice, now the OxygenOS version is 5.1.7. Android security patch level says 1 October 2018. When I was downloading the latest OTA update the internet connection went down. I don't remember exactly how it happened though. Could this have caused this weird problem?
What does it mean to switch channel? Does it involve difficult-for-layman operations?

peisi said:
I'm on stable. I don't have a good memory but as far as I can remember, I got mine with Android 7.1.1 installed. Then I got OTA twice, now the OxygenOS version is 5.1.7. Android security patch level says 1 October 2018. When I was downloading the latest OTA update the internet connection went down. I don't remember exactly how it happened though. Could this have caused this weird problem?
What does it mean to switch channel? Does it involve difficult-for-layman operations?
Click to expand...
Click to collapse
In your case I mean trying official open beta you can find how to switch to open beta here if you are interested https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074 do it at your own risk although there's very little chance things going wrong

intoxicated.mad said:
In your case I mean trying official open beta you can find how to switch to open beta here if you are interested https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074 do it at your own risk although there's very little chance things going wrong
Click to expand...
Click to collapse
Ah I see. Thanks for clarifying.
But I'm not really sure if I wanna go beta with this really strange thing going on.

peisi said:
Ah I see. Thanks for clarifying.
But I'm not really sure if I wanna go beta with this really strange thing going on.
Click to expand...
Click to collapse
You can always back up and go back to stable and you don't even void Warrenty :good:

intoxicated.mad said:
You can always back up and go back to stable and you don't even void Warrenty :good:
Click to expand...
Click to collapse
I got this from expansys. So I'm not really sure if I can get warranty from OnePlus itself. Expansys stated that flashing ROM will void their warranty. Having said that, I will ask if I can get warranty from OnePlus.

Follow-up.
I am still trying to solve this issue within the current state. But I am now suspecting the issue could only be solved, if it's even solvable, via likes of complete factory reset, clean flash and such. So I started contacting the shop and OnePlus trying to confirm details about warranty and also asking for tech support, now waiting for their responses.
People are still very cooperative, but as of now no one has figured out what the cause may be.
I will be updating as things progress.

I just found that picture-in-picture doesn't function in addition. My understanding is that if you activate this feature by accepting apps to use it via Settings > Apps > Special access > Picture-in-picture > (any app) > Allow picture-in-picture and no additional tweak required, it will do just that. I know that outside of NA, YouTube doesn't do it unless you are a YouTube premium member. I checked this on Chrome and Tumblr.
At this point I'm almost convinced that there are a few more issues I haven't encountered yet and these issues, though looking like they are unrelated, may have arisen from one cause.
I haven't received any response after the last post so I'm not going rush to clean flash and see if these problems can be fixed but it's so tempting to say the least.
I hope that some people still read this thread.
Edit: Oops. Picture in picture does work. I was too nervous, it seems. But the original problem persists so the situation is no better than before.

After checking details about warranty coverage with OnePlus and Expansys, I tried hard factory reset and ROM flash. And sadly, both didn't work.
Snehasish1994 suggested that I try remote debugging, which seems quite overwhelming for me but I will see what I can do.
But well, I am considering return or replacement at this point really. Because, what else can I do? It may not seem like a deal breaker but I use large JPG files quite often, like really often.
I've been mistaking the guy's name snehasish1994 for snesish1994. I apologize.

Update
Yes, the problem persists, still.
I went to a local repair shop. I told them about the symptom and what I confirmed thus far. They were unable to solve the issue. And they said that it is safe not to open the back and inspect the internal to keep the warranty intact. I got no new information there except that they think the problem is too complex to be hardware related, which is a relief at least.
Snehasish1994 is still helping me solve it. Thank you, snehasish. Now, he inquired me if I tried Firefox and actually I hadn't at that point, except for Firefox Focus. I tried Firefox and to my surprise it works as it should!
But then, I am still unsure as to whether the issue on Chrome and Firefox Focus, which are my go-to browsers, can be fixed. I use Firefox Focus much less than Chrome so I am okay even if the issue on Firefox Focus won't be fixed but I can't accept it on Chrome both because I use it most often and it is now the only proprietary web browsing app provided by Google.
Oh, and in the first post in this thread, I said, at Edit9, that the image seems to be loaded into Chrome. This was confirmed via DevTools. Again, snehasish suggested me that I use it. So if I can tell Chrome (and hopefully Firefox Focus as well) to render large JPG files, I should be good to go.
That's all I got since the last post, I think.

Finally, having tried every possible solution only to find the issue was still there, I went for a replacement. I will be receiving it in the next few days or so. Hopefully there will be no problem.
I think anything beyond this point will all be irrelevant to the topic of this thread so this would be my last post on this thread.
It was really annoying to deal with the issue, but I am grateful to find people on xda are helpful. Snehasish in particular has helped me a lot.

That last post would have been the final post. If the replacement didn't have the same problem...
It got delivered a few hours ago. The first thing I checked was of course that nasty issue. It was depressing to see the same issue but I thought "well, it can't be a faulty device or a one-off bug then".
With the clues I listed on this thread, I was testing again. I was thinking about why on earth Firefox can display those images while Firefox Focus can't. And I discovered that the two browsers use different browser engines: The former uses Mozilla's in-house Gecko engine whereas the latter uses Google's Webview engine, which Chrome uses too. But fortunately, Mozilla is trying to implement Gecko on Firefox Focus lately and there's the Nightly version, which has Gecko. I immediately tried it. Boom, the images in question appeared. I'm just a layman so I know nothing about technical details, but I believe that the problem is somehow related to Google's Webview engine.
It may be beyond my capability to dig any deeper but this had me interested.
Anyway, life is tough.

Another followup.
I updated the firmware to the latest OOS 9.0.1. And the problems I have discussed are gone for good it seems. I can now view large images without any problem. After all it turned out I didn't have to replace the previous device then.
Anyway, I'm pretty happy with my 5t now. I hope no one else is facing this issue but if anyone is, hope this thread helps.