Speed up your Google Chrome Browser - Optimus L3, L5, L7 General

The workaround works very easy, even less technology-savvy people can easily perform this. To do this simply open the Chrome browser . In the address field, type :
Chrome://flags/#max.-tiles-for-interest-area
An Android system menu pops up, where you can now make settings. Once there, you choose the highest possible value (512 instead of 128 set for example). This value represents the total memory that the Android system is available for the Chrome browser. After changing this value, choose "Relaunch Now" (restarting) and the phone reboots. As of now, the Chrome browser you can enjoy again in old freshness. In older models, it may be that the adjustable memory size only goes up to 256 and not to 512 .Here you have to test what is possible.
GREEEEEETZ!!!!!!!

Great finding bro ! Thanks for the tutorial !

Thank ! our friend -caliban666-

-CALIBAN666- said:
The workaround works very easy, even less technology-savvy people can easily perform this. To do this simply open the Chrome browser . In the address field, type :
Chrome://flags/#max.-tiles-for-interest-area
An Android system menu pops up, where you can now make settings. Once there, you choose the highest possible value (512 instead of 128 set for example). This value represents the total memory that the Android system is available for the Chrome browser. After changing this value, choose "Relaunch Now" (restarting) and the phone reboots. As of now, the Chrome browser you can enjoy again in old freshness. In older models, it may be that the adjustable memory size only goes up to 256 and not to 512 .Here you have to test what is possible.
GREEEEEETZ!!!!!!!
Click to expand...
Click to collapse
Sent from my Nexus 4 using XDA Free mobile app

I'm doing it here. Thanks!

I'cant find the field where I have to change the value

maybe its changed in newer versions,i take a look at this.

Thanks
Sent from my LG-E610 using XDA Free mobile app

I tryed to use chrome on my l3 e400 but it's so slow....
I'm gonna try to do this.
Thanks so much!!!

<3 i like this so much

Related

Opera mobile 11 /w flash

Anyone try the new opera mobile 11. it now supports flash.
If so does it work on stock rooted?
Sent from my GT-I9000M using XDA App
Stock rom doesn't support flash so no. It will now show you the preview image, and if you click through to youtube and press play there it'll play the video in your youtube app.
It also recognizes it's on a tablet, and shows a different interface than the one for the phone.
Personally I love the new opera, I'm using it as my daily web browser. That's saying alot considering how good dolphin HD is.
I've tried Opera Mobile 11, Firefox 4 RC, and various reskinnings of the default browser (Miren, Dolphin, and stock). Opera Mobile 11 seems by far the smoothest, apparently due to hardware acceleration. Scrolling/panning, pinch zooming, etc., are smooth as silk, similar to what you'd see on an iPad. None of the WebKit-based browsers are that smooth, presumably because they don't yet feature hardware acceleration (at least on the NC?). Firefox 4 RC looks okay but doesn't yet have Flash. I think I may make Opera may daily driver for a bit and see how it does with the various sites I visit.
UPDATE: After playing with Opera 11 for a while, I'll go so far as to say that everyone should try the New York Times Web site with Opera 11 in landscape orientation. That, to me, is what tablet browsing is all about! VERY impressive!
Sorry for asking this. Which fingerprint do you use? I can only find Opera mini, but not opera mobile in the market. any pointers would be great.
cheezer38 said:
Sorry for asking this. Which fingerprint do you use? I can only find Opera mini, but not opera mobile in the market. any pointers would be great.
Click to expand...
Click to collapse
Even I didn't find opera mobile in market....So i went to opera website thru nook browser (I am using cm7 sd card bootable), went to download page, selected android devices. Here you get option to download opera mini or mobile....
Download mobile and enjoy
I am loving it......
Opera = no Javascript = pass!
akarol said:
Opera = no Javascript = pass!
Click to expand...
Click to collapse
Where did you hear that? Opera Mobile has a very good JavaScript engine.
I've been testing Opera and a few things bug me:
A) Panning up and down the page doesn't "lock" the motion to that axis so that it only moves up/down like every other Android browser does. So the page moves around on BOTH axes (up/down/left/right) and even looks weird as it jitters (or "vibrates") left/right when you only mean to move up/down. In every other browser, when you start panning in one motion, it locks the movement to that axis, which makes for a smoother motion (and rarely do you need to move on both axes, which is why this is implemented).
B) Long pressing on a link doesn't show the URL. Sometimes I'm reading an article and want to see what a link goes to without opening a page. In Opera Mobile, there's no way to do that.
C) I find tab switching to be slower and more tedious than in Dolphin, where the only action needed is a single tap on a tab. Whereas in Opera, you need to tap the (frustratingly small) tabs button, tap the tab you want, and then tap out of it to get rid of the pop-out.
That being said, the re-flow option is much better in Opera than Dolphin. It re-flows the text immediately after zooming, every time. Very helpful.
opera:config, uncheck "Scoll is Pan" in User Prefs, helps a little bit with the vertical scroll lock problem.
The only real issue I've found so far is that it's kind of hard to close a tab. I tap the "X" on the tab but most of the time nothing happens, or if something does happen, there's a LONG delay. Any idea if I'm doing something wrong? I have my LCD density set to 200 so perhaps the UI isn't properly adjusting for that (even though everything looks right cosmetically)?
SCWells72 said:
The only real issue I've found so far is that it's kind of hard to close a tab. I tap the "X" on the tab but most of the time nothing happens, or if something does happen, there's a LONG delay. Any idea if I'm doing something wrong? I have my LCD density set to 200 so perhaps the UI isn't properly adjusting for that (even though everything looks right cosmetically)?
Click to expand...
Click to collapse
I had the same issue. Found out tapping the X button twice did the trick. Best browser I've tried.
victle said:
I had the same issue. Found out tapping the X button twice did the trick. Best browser I've tried.
Click to expand...
Click to collapse
Just tried that and it works perfectly! Thanks!
Thanks for the tip. This is the best browser yet for the Nook in my view. Quick, accurate (pinching, dragging) and no fuss. I'm running it on a CM7 SD card build and it's fast. Flash works. A question, however: I know Flash works because I use Flash for our site and checked it there. However, going to HBO.com (wanted to grab some Flash video to see what happened) it tells me that my device is not Flash enabled -- so won't let me connect with Flash. ????????????????????
Regarding panning, zooming, etc., I found version 11 to be far worse than 10.1 Beta. Whereas it was iPhone/iPad-like buttery smooth with 10.1 Beta, it's now become choppy with 11 like every other Android browser. I can really tell the difference on graphics-heavy pages like espn or engadget. With 10.1 Beta, panning/zooming on images was silk smooth even while the cpu was busy loading the rest of the page; now with 11, that's not the case.
Ironically though, Web pages load much, much faster (in their entirety) with 11 compared to 10.1 Beta.
OMG, I just installed this a few moments ago... can't believe how fast this thing is! It's as fast as the iPad browser on a rooted. stock Nook. running stock clock speed. Gentlemen, I have found my new browser. End of story.
I don't find it to be as tablet-friendly as the stock HC browser, but it does seem to be very good in terms of performance
Most importantly I can now watch youtube videos on my nook even with HC. Wowza thanks for the tip!
rabid_droid said:
Regarding panning, zooming, etc., I found version 11 to be far worse than 10.1 Beta. Whereas it was iPhone/iPad-like buttery smooth with 10.1 Beta, it's now become choppy with 11 like every other Android browser. I can really tell the difference on graphics-heavy pages like espn or engadget. With 10.1 Beta, panning/zooming on images was silk smooth even while the cpu was busy loading the rest of the page; now with 11, that's not the case.
Ironically though, Web pages load much, much faster (in their entirety) with 11 compared to 10.1 Beta.
Click to expand...
Click to collapse
Funny, i am the opposite. For me, this is the first browser in CM7 that lets me view pages like Engadget with good fluidity....
It's also the first I've found that handles xda with any level of fluidity
Animec said:
It's also the first I've found that handles xda with any level of fluidity
Click to expand...
Click to collapse
Same here, I thought I was the only one that noticed. Switched to Opera Mini 10, then back to Dolphin Mini 2 because page rendering more livable, now back to Opera Mobile 11 because of speed, although I still hate how vertical scrolling a pain on long pages.

Stagefright, VM Heap, SYSCTL and other performance related options

With the recent release of Spz0s rom and Adrynalyne getting this beat over clocked these settings are becoming obsolete. Use at your own discretion.
I recently restored my phone to stock, with basic settings, meaning I did not use any of the settings listed here. I scored a 1013 on a bench with stock everything. Now that I have VTL Launcher as stock again and have everything set back up for me, I'm scoring 1000s and 990s regularly. Again without any of these settings enabled. Which is leading me to believe that a stable system is the fastest thing when it comes to performance and benchmark scores. The settings listed below did help me out, with an unstable system. Now that I am running on a stable system, none of the settings below helped my performance or bench scores, they only hurt them. So these settings below will help anyone with an unstable system to not feel the lag of said unstability. If you try these settings and they don't do anything, or hurt your performance or score, turn them back to stock and revel at how much you rock for having a super stable system! I have also noticed that the app AUTO KILLER MEMORY OPTIMIZER virtually replaces sysctl. If you run AUTO KILLER I would suggest setting sysctl back to stock! I would recommend AUTO KILLER MEMORY OPTIMIZER from the Market to EVERYONE with a Zio. Nice app, set it to Aggressive!
FIRST OFF, THESE SETTINGS ARE ONLY CHANGEABLE IF YOU ARE ROOTED!! If you are not I cannot help you!!
I am making this thread to address performance issues with the Zio. If you have done a benchmark score with just basic settings, it's already apparent to you the Zio is not the best phone. I have found some tweaks to make the phone run faster and score better on benches.
USE THESE SETTINGS AT YOUR OWN RISK. IF YOU SCREW SOMETHING UP, DON'T CRY TO ME.
Stagefright: Stagefright is part of the stock media player that comes disabled on the Zio. Turning on stagefright will increase your benchmark score by a lot, and has also been reported to make Video Playback much better, getting rid of jumpy lagging videos.
You need to make sure you have r/w(read/write) access in your file manager. Root Explorer has r/o(read/only) and r/w. You cannot change any files without r/w access in your file manager.
To Enable Stagefright you open your file explorer(i.e. root explorer, astro, etc.) and navigate to the system folder. Open build.prop in your text editor. Scroll down to where you find stagefright. There are four settings for it grouped together near the bottom of the script. Next to each setting it says =false. You need to edit the false to say true. Once that is done, go up just slightly from that spot, there is also another spot to enable stagefright. Change that to true as well. Also notice that just above this last stagefright script, there is something about the vm.heap and dalvik cache. This is where you change your VM Heap size.
(NOTE: ENABLING THE HTTP SETTING IN STAGEFRIGHT ALLOWS FOR A RICHER HTTP BROWSING EXPERIENCE BUT WILL ALSO PUT A GREEN BAR ON YOUTUBE VIDEOS. KEEPING IT SET TO FALSE WILL AVOID THIS GREEN BAR AND SHOULD NOT AFFECT OVERALL PERFORMANCE!)
VM Heap-Not exactly sure what the technical aspect of it is, but increasing the vm.heap gives the dalvik cache more room to work with, thus making your memory faster. THIS NUMBER SHOULD NOT BE SET BELOW ANDROID DEFAULT WHICH IS 24. And should also not be set above 44. If you want to change this number, add or subtract 4 within the above values, 24-44. This can go down to 16 but you'll see the results and why I said to leave it up pretty fast.
SYSCTL- To edit these settings, open your file explorer, hit the ETC folder. Scroll to bottom and find sysctl.conf, long press and open in text editor. So far I can only say there are three settings here you need to adjust.
To edit SYSCTL settings you must first download and install the app sysctl config from the Market. After you set it up initially it can be uninstalled and leave behind the settings folder for further settings changes by manually editing or you can keep it and just use it to make the changes.
First is MIN FREE KB. This number will not be the same for everyone, although I can tell you setting this number above 4096 seems to slow the system way down. Although you may try any of the following numbers..
1536, 2048, 4096, 5120, 5632, or 6144.
These are the only numbers I would suggest using as they are parameters that came out of the phone itself.
sys/module/lowmemorykiller/parameters. <----DO NOT CHANGE the numbers in this location, they are system defined parameters and are NOT to be changed!
The second setting is vfs.cachepressure. I have this set to 10. Default is 50. Basically what I've read about this, it opens more room by setting it lower, leaving more memory free from constantly checking and clearing the cache. Read more here http://forum.xda-developers.com/showthread.php?t=523707&page=12
The Third setting is oom. It's the last value in sysctl.conf and needs to be set to 1 or 0. Instead of your phone starting to kill apps when it's out of memory, it does something else that I didn't quite understand, which is supposed to boost memory performance. Some people are seeing great results with this setting. Some people say it doesn't do anything. Seems to be specific to the user, and I have yet to find anything in common between two users who say this helps. Although bench scores are higher with it set to 1.
For these settings to take effect you must reboot your phone. Changes to these settings are only applied by a reboot, so any time you change anything, REBOOT!
If you do not know how to change settings manually, there are two apps in the market to help. VM Heap Tool will change your VM Heap for you, no need to manually edit if you don't want to. sysctl config is an app that will allow you to easily change the sysctl settings.
There is an App that will change your stagefright settings for you called Blade Buddy. I did not have a good expeience with this program and would suggest that you edit stagefright manually since it's pretty easy with a superuser file manager.
I can say with certainty that turning on stagefright and adjusting and playing with the rest of the settings that your phone will turn in to a beast compared to how it came out of the box.
As far as battery performance goes, I've noticed a 10-15 percent increase(estimated) over the life of a charge(depending on amount of usage and type). I have noticed more battery use. But not so much that these settings wouldn't be worth using. I gave numerous variations of these settings tries over 2 very long months of restarts and three different benchmark programs. Any additional information or discoveries are welcome.
If this helped, please hit Thanks!!
Muchos Gracias to everyone in #openzio as always. Spz0 n Mattix are always a big part of anything I do. They are always nice enough to save me from myself. And much thanks to anyone that helps out with the Zio at all. Lets own this phone!
Nice write-up bro.
Well, good guide. Hopefully Kyocera calls me back in regards to the kernel source code so we can really overclock this thing.
Sent from my Zio using XDA Premium App
Their lawyer in San Diego got a hold of me on Facebook. Asked me to call her back. Three calls and no dice. Waiting on her response now. Hopefully soon. She said they are "working the bugs out". Which is a load of BS since we have phones in our hands, the source is done. They just have to give it to us and I told her bluntly just that.
Tell them to call me lol, I want the source. Give us the source!
Sent from my Zio using XDA Premium App
So what happened to getting it? Teacher not know the right trick? Have you heard about using git to get the source? I dunno what git is but it may help? Ever heard of it?
Sent from my Zio using XDA Premium App
http://en.wikipedia.org/wiki/Git_(software).
Google is your friend???
Also, I don't have a sysctl.conf file. At least not where you said it is or one that root explorer can find...
Yeah if I actually understood any of that I wouldn't be asking.
Ok here is the best benchmark average I have gotten so far. These are the settings I used to achieve it.
Avg Benchmark - 795
High - 900 (omitted from average)
Low - 710 (omitted from average)
Avg with high and low only changed by 6 points.
Sysctl Support - Enabled ( I am using the Sysctl app form the market.)
Min free Kbytes - 4096
Dirty Ratio - 80
Dirty BG Ratio - 40
Oom Allocating Tasks - Enabled
VM Heap Tool - VM Heap set to 36m
Stagefright settings are all set to "True"
What we need to know now is what setting are going to speed up the UI. Like cutting load times on FB and other apps, what is making the phone just lightning fast? Doesn't seem to matter too much as long as you don't go above 4096. Finally started to see some system lag with 8192. We need to figure out what makes the phone the most responsive, fastest, beast of a phone.
Messing with the radio numbers only seems to slow me down. And still can't really find anything on what vm.swapiness does either.
sinisin said:
What we need to know now is what setting are going to speed up the UI. Like cutting load times on FB and other apps, what is making the phone just lightning fast? Doesn't seem to matter too much as long as you don't go above 4096. Finally started to see some system lag with 8192. We need to figure out what makes the phone the most responsive, fastest, beast of a phone.
Messing with the radio numbers only seems to slow me down. And still can't really find anything on what vm.swapiness does either.
Click to expand...
Click to collapse
Well, I have also downloaded Link2SD from the market and put every app (except system apps) on the SD card and That has given me a little over 100MB free on phone storage and I am using Memory booster lite to free up memory on the phone. All of these things have made a huge difference in the speed and performance of the phone including page load times. (facebook opens and loads almost instantly).
Be careful. Don't move things like Widgets that need to refresh or themes for your launcher or the launcher itself. Seems fine at first until you run for a while and Widgets stop and launcher always reloads.
Sent from my Zio using XDA Premium App
Are you on Wi-Fi while opening apps or 3G and if 3G how many bars?
Sent from my Zio using XDA Premium App
Using Root Explorer /ect/sysctl.conf I'm not seeing this file...
sinisin said:
Serious changes coming soon. New numbers up for min free KB below already.
Stagefright: Stagefright is part of the stock media player that comes disabled on the Zio. Turning on stagefright will increase your benchmark score by a lot, and has also been reported to make Video Playback much better, getting rid of jumpy lagging videos.
To Enable Stagefright you open your file explorer(i.e. root explorer, astro, etc.) and navigate to the system folder. Open build.prop in your text editor. Scroll down to where you find stagefright. There are four settings for it grouped together near the bottom of the script. Next to each setting it says =false. You need to edit the false to say true. Once that is done, go up just slightly from that spot, there is also another spot to enable stagefright. Change that to true as well. Also notice that just above this last stagefright script, there is something about the vm.heap and dalvik cache. This is where you change your VM Heap size. (NOTE: ENABLING THE HTTP SETTING IN STAGEFRIGHT ALLOWS FOR A RICHER HTTP BROWSING EXPERIENCE BUT WILL ALSO PUT A GREEN BAR ON YOUTUBE VIDEOS. KEEPING IT SET TO FALSE WILL AVOID THIS GREEN BAR AND SHOULD NOT AFFECT OVERALL PERFORMANCE!)
VM Heap-Not exactly sure what the technical aspect of it is, but increasing the vm.heap gives the dalvik cache more room to work with, thus making your memory faster. THIS NUMBER SHOULD NOT BE SET BELOW ANDROID DEFAULT WHICH IS 24. And should also not be set above 44. If you want to change this number, add or subtract 4 within the above values, 24-44.
Phone Edit- Found numbers for min free KB. sys/module/lowmemorykiller/parameters. 1536, 2048, 4096, 5120, 5632, 6144. Assuming these are new guidelines. Will edit fully tomorrow. Don't change these settings. They are system parameters and should NOT be changed.
SYSCTL- To edit these settings, open your file explorer, hit the ETC folder. Scroll to bottom and find sysctl.conf, long press and open in text editor. So far I can only say there are three settings here you need to adjust. First is MIN FREE KB. This number will not be the same for everyone, although I can tell you setting this number above 8192 will slow the phone down, most people report anything over 4096 slowing the phone down. The default is 2048, I would suggest going up to 4096 or 8192.
The second setting is vfs.cachepressure. I have this set to 10. Default is 50. Basically what I've read about this, it opens more room by setting it lower, leaving more memory free from constantly checking and clearing the cache. Read more here http://forum.xda-developers.com/showthread.php?t=523707&page=12
The Third setting is oom. It's the last value in sysctl.conf and needs to be set to 1 for everyone. Instead of your phone starting to kill apps when it's out of memory, it does something else that I didn't quite understand, and this should add speed to everything you do, like surfing or Facebook. Everything should load faster and smoother with this setting enabled. Remember stock value is Zero and may only be set to 1 or 0.
If this helped, please hit Thanks!!
Click to expand...
Click to collapse
Try /system/etc micro. Same thing.
Sent from my Zio using XDA Premium App
Current settings.
4096
95
60
50
Oom
VM heap 30
Stqgefright all but http
Running fast and stable. Launcher pro Orientation from portrait to landscape is faster. Home loads instantly even though I am not using a launcher from /system/app
I will be doing some more tweaks to speed this up but maintain some battery life.
Sent from my Zio using XDA Premium App
I have Stagefright fully enabled. Running 2048 Free KB. Stock radio and background. Turned oom to 0. Zoomin right along.
Sin. How did you edit sysctl.conf I can't find it in ETC
Sent from my Zio using XDA Premium App
Thanks! /system/etc still nothing. I have rtecdc_apsta.bin and void.fstab no luck still.
sinisin said:
Try /system/etc micro. Same thing.
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
Looks like we need to include sysctl.conf in the next theme update.
Sent from my Zio using XDA Premium App

[Q] is there any know way to remove 1gb ram limit?

I understand that if an app have a 1gb ram requirement there must be a reason behind it, but i just discovered that Microsoft Research's Face Swap needs 1gb too.
I have a Lumia 720 and i'm used to have face swap app even with my old win 7.8 phone, it looks like a stupid and non-sense limit.
I tried to download the .xap from web store but it's encrypted so i can't do much. Someone have already lost some time on this?
You would have to edit the WMAppManifest File inside the XAP to remove the Limit so unless you can decrypt it you can't remove the Setting. Best idea might be to contact the devlopers though. I don't believe they would set the Limit unless they have reason to do so. It definitely is not set by Default.
How can we see 1GB ram requirement on the application page? I have lumia 620 and I cant install it too.
http://www.windowsphone.com/en-us/store/app/face-swap/0f55f905-77d3-4e09-8f2a-d8a41c77a02b
SerhatSoylemez said:
How can we see 1GB ram requirement on the application page? I have lumia 620 and I cant install it too.
http://www.windowsphone.com/en-us/store/app/face-swap/0f55f905-77d3-4e09-8f2a-d8a41c77a02b
Click to expand...
Click to collapse
Information such as region restriction or memory requirements seems to be hidden from user. Your will be warned on install attempt with "can't buy app" error and description.
eyeofhell said:
Information such as region restriction or memory requirements seems to be hidden from user.
Click to expand...
Click to collapse
Interesting. I think it wont be hidden, thanks.
SerhatSoylemez said:
Interesting. I think it wont be hidden, thanks.
Click to expand...
Click to collapse
the only way i found to read the "1gb ram needed" error is open windows store application's link from a qr code and then tap on the error message on the phone.
looks like we totally need 1gb for this :\
thanks StevieBallz for the explanation.. i hope someday wp8 will just optimize ram management and remove this limit! I suppose is possible, iphone 3gs with 256mb of ram can run heavy games like real racing 2, why a 512mb ram phone can't run a face swap application?
512 MB devices offer up to 180 MB of Memory for App usage. 1 GB devices offer up to 380 MB of Memory for App usage. The rest of the Memory is reserved for the System, Background Tasks like playing Music, Voice over IP calls like Skype or Background Navigation.
Basically if the Devs put the effort in to get their App running with a Maximum of 180 MB it can run on 512 MB devices. If they Need more Memory than that they'll have to Limit the App to 1 GB devices. There is nothing Microsoft can do to Change that, given that it's down to the Apps Memory footprint. I can't imagine that an App can use > 180 MB on a 256 MB iPhone so it's most definitely down to the Developer to Change this.
This is an very interesting theme!
I think windows phone hast problems work with pictures and the memory limit.
Yesterday I have upload an app to store names Picture Ripper Project.
This is an mass picture downloader, that downloads pictures from Internet websites to phone.
The user can create his own lockscreen and tile images cycler.
In the first version of this app I have so many problems with the SYSTEM OUT OF MEMORY!
When the Engine downloads 15 Pictures with an size from 300 KB, the app has shut down.
I don't know why the Memory of this pictures expands over the Limit!
Now I have write down two new download engines. The Image Downloader and the Image Links Downloader.
I have create an way to download up 100 pictures at once and its working if the size of the pictures not so big.
I need some tester for this app. I only have an Lumia 920 and a Lumia 820 to testing it.
If your interest, send me an PN and get the App for free when it is online!
Thank you!
xtrose.
This happens because you keep the pictures in memory, and do not free/close/dispose the file streams after download. The actual size of an image in memory is bigger than its size on disk. There is no problem with the system. Just your app is doing it wrong.
The basic problem is that a JPEG compressed Image when being opened is decoded to a bitmap array that takes quite a lot more space given that it isn't compressed. 10 1280x720 images can easily take up up to 10 MB even when compressed and can get as big as 50 MB when uncompressed.
That aside your problem most certainly has to do with references to those images being retained in your App (as mentioned by Mcosmin), so the memory is not freed up. You can debug that using the Profiler included with the Windows Phone SDK. There are WebCasts and articles by Microsoft that explain the usage of the tools.
In the Downloadengines I am do it this way!
Downloading the images to an temp file, create an Thumbnail of it, delete the file and download the next!
It works fine.
With the Thumbnails i can open Folders with more then 200 Pictures!
The app is online at the marketplace now!
http://www.windowsphone.com/s?appid=1034eecd-381c-41dc-9386-86498d0ffd17
You can do this a lot faster by using memory streams instead of file streams for temp file to avoid the slower isolated storage.
I am try this in the next version!
Thanks all

[Reference] Firefox Hacks

Firefox Hacks
Desktop UA:
To set Firefox to use a Desktop UA by default, type in about:config in the address bar and then click on Add a New Setting, select String, and enter general.useragent.override, click ok and enter:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20130406 Firefox/23.0 for a Firefox User Agent.​
Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1468.0 Safari/537.36 for a Chrome User Agent.
Mozilla/5.0 (compatible; MSIE 10.6; Windows NT 6.1; Trident/5.0; InfoPath.2; SLCC1; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 2.0.50727) 3gpp-gba UNTRUSTED/1.0 for a Internet Explorer User Agent.
Finally type in agent in the search box and find general.useragent.enable_overrides and toggle it to true
Make Firefox Faster​Enable Pipelining:
Browsers are normally very polite, sending a request to a server then waiting for a response before continuing. Pipelining is a more aggressive technique that lets them send multiple requests before any responses are received, often reducing page download times. To enable it, type about:config in the address bar, type in pipelining in the search box and hit enter. Find network.http.pipelining.agressive and toggle it to true and network.http.pipelining.maxrequests and click on modify and change it to 50(use a lower number if you have a low speed connection)
Render quickly:
Large, complex web pages can take a while to download. Firefox doesn't want to keep you waiting, so by default will display what it's received so far every 0.12 seconds (the "content notify interval"). While this helps the browser feel snappy, frequent redraws increase the total page load time, so a longer content notify interval will improve performance. To enable it type about:config in the address bar and click on Add a New Setting select Integer Type content.notify.interval as your preference name, click OK, enter 500000 and then click on Add a New Setting and select Boolean create a value called content.notify.ontimer and set it to True
Faster loading:
If you haven't touched your screen for .75 second, then Firefox enters a low frequency interrupt mode, which means its interface becomes less responsive but your page loads more quickly. Reducing the content switch threshold can improve performance, then, and it only takes a moment. To enable it type about:config,in the address bar and click on Add a New Setting select Integer Type content.switch.threshold, as your preference name, click OK, enter 250000 (quarter of a second)
Increase the cache size:
As you browse the web so Firefox stores site images and scripts in a local memory cache, where they can be speedily retrieved if you revisit the same page. If you have plenty of RAM, leave Firefox running all the time and regularly return to pages then you can improve performance by increasing this cache size. To enable it type about:config,in the address bar and click on Add a New Setting select Integer Type browser.cache.memory.capacity as your preference name, click OK, enter 18432
Enable TraceMonkey:
TraceMonkey is a new Firefox feature that converts slow JavaScript into super-speedy x86 code, and so lets it run some functions up to 20 times faster than the current version. To enable it type about:config, in the address bar and then type jit in the search box and hit enter. Find javascript.options.methodjit.chrome and toggle it to true and javascript.options.methodjit_alwaysand toggle it to true.
Cache:
Unfortunately Firefox collects copious amounts of data and there is no way to prevent it.
This was adapted from: http://www.techradar.com/us/news/software/applications/8-hacks-to-make-firefox-ridiculously-fast-468317 and http://useragentstring.com/pages/useragentstring.php​
This makes Firefox blazingly fast on my tablet and so far every website works perfectly.
To save settings for easy restoring navigate to data/data/org.mozilla.firefox/files/mozilla/widlm1lw.default/ and make a copy of prefs.js
Some more possibly useful settings:
[FONT=&quot]
Type about:config in the address bar, type in browser in the search box and hit enter[/FONT]
browser.download.manager.displayedHistoryDays set to 1 (set to whatever you like)
browser.enable_automatic_image_resizing set to true
browser.enable_click_image_resizing set to true
browser.helperApps.deleteTempFileOnExit set to true
browser.history_expire_days set to 1 (set to whatever you like)
browser.history_expire_days_min set to 1 (set to whatever you like)
browser.zoom.full set to true
browser.zoom.reflowOnZoom set to true
browser.cache.disk_cache_ssl set to false
If anyone finds any more useful settings that can be changed or settings that work best, post them here.
ABSOLUTE BEAUTY.
I knew about 90% of these on the Desktop version, don't know why it didn't click it may be the same on Tablet, BOOKMARKED for Later, THANKS!!
Wilks3y said:
ABSOLUTE BEAUTY.
I knew about 90% of these on the Desktop version, don't know why it didn't click it may be the same on Tablet, BOOKMARKED for Later, THANKS!!
Click to expand...
Click to collapse
It's rather ironic, that this is the only real desktop browser on android, yet most of the desktop settings aren't enabled or set by default. This is only browser that I have ever used that I can use all day on flash heavy sites and never crash. I've only had one FC in the past month.
prestige777 said:
It's rather ironic, that this is the only real desktop browser on android, yet most of the desktop settings aren't enabled or set by default. This is only browser that I have ever used that I can use all day on flash heavy sites and never crash. I've only had one FC in the past month.
Click to expand...
Click to collapse
Yeah FF is hands down a quality browser, I'd be using it on Desktop if it wasn't so weird about my Cookies (never keeps me signed in on Forums[XDA] etc)
But I can't believe these options are just as usable on desktop, and yeah, even without these settings enabled I must say FF has never crashed on me on my tablet (even with flash heavy sites as you say).
Whereas Chrome just stutters, cries and gives up.
Boat just freaks out and FC's
Dolphin just isn't my pick.
Opera I don't like at all.
SO WEEEE Thanks for these tips my friend !
Wilks3y said:
Yeah FF is hands down a quality browser, I'd be using it on Desktop if it wasn't so weird about my Cookies (never keeps me signed in on Forums[XDA] etc)
But I can't believe these options are just as usable on desktop, and yeah, even without these settings enabled I must say FF has never crashed on me on my tablet (even with flash heavy sites as you say).
Whereas Chrome just stutters, cries and gives up.
Boat just freaks out and FC's
Dolphin just isn't my pick.
Opera I don't like at all.
SO WEEEE Thanks for these tips my friend !
Click to expand...
Click to collapse
No problem, if you have any good tips or variations please feel free to post them here.
Thanks for the post, very interesting.
I applied your tips to firefox running on my Nexus 4, but I did not see much of an improvement. Just doing some casual/typical browsing that I would normally do it felt almost the same as before without the tweaks, although I wasn`t doing any timing with a stopwatch or anything of that matter so I can`t say for sure that there wasn`t an improvement. Maybe these tweaks would benefit lower/older end devices more than the newer high speed quadcores.
SkyandDirt said:
Thanks for the post, very interesting.
I applied your tips to firefox running on my Nexus 4, but I did not see much of an improvement. Just doing some casual/typical browsing that I would normally do it felt almost the same as before without the tweaks, although I wasn`t doing any timing with a stopwatch or anything of that matter so I can`t say for sure that there wasn`t an improvement. Maybe these tweaks would benefit lower/older end devices more than the newer high speed quadcores.
Click to expand...
Click to collapse
Its really noticeable when you start with a fresh install of Firefox with no data, once Firefox starts collecting data it starts really slowing down. Firefox really needs to deal with this data collection issue. For me it collects over 100mb of data in just a couple of weeks despite clearing everything from within the app. I don't think most of settings affect Firefox's performance if its not being used with a desktop user agent since that is handled completely different than if you're using the default android user agent.
prestige777 said:
Finally type in agent in the search box and find general.useragent.enable_overrides and toggle it to true
Click to expand...
Click to collapse
This is not true, general.useragent.enable_overrides has no effect on general.useragent.override (which is always enabled) and instead affects overriding the User Agent on a per-domain basis as described here.
prestige777 said:
Increase the cache size:
As you browse the web so Firefox stores site images and scripts in a local memory cache, where they can be speedily retrieved if you revisit the same page. If you have plenty of RAM, leave Firefox running all the time and regularly return to pages then you can improve performance by increasing this cache size. To enable it type about:config,in the address bar and click on Add a New Setting select Integer Type browser.cache.memory.capacity as your preference name, click OK, enter 18432
Click to expand...
Click to collapse
You should tell people the integer is the cache size in KB. My config already had this setting and it was set to 1024. According to mozillaZine, the default is set according to RAM size but as mine defaulted to 1024, perhaps this is different for mobiles. Setting it to your apparently random value of 18432 could work, but after reading the tweaks page you referenced and mozillaZine, I opted to set it to -1 which should let Firefox decide according to how much RAM I have and if it follows the table in mozillaZine, will make a substantially bigger cache than you suggested.
Thanks for bringing my attention to these useful features.
Sent from my GT-N7100 using Tapatalk 4

How To Guide S21 Force 120Hz!

So this is a huge discovery I made! Myself and many others are annoyed at the fact that Snapchat drops to 60Hz whenever the camera is activated. I found a workaround that allows it and other applications to remain at 120Hz even when the camera is in use! (One UI 3 only)
** BYPASS ADAPTIVE REFRESH RATE WITH CAMERA / GAMES **
(Guide 1 of 2)
For my friends over at Samsung Members looking to fix 120Hz, scroll down until you see Guide 2 of 2!!
What you'll need:
* Set Edit (free on the playstore)
Make sure you are not using power saving mode, and you have your refresh rate set to adaptive. Now launch Set Edit and enter the system table in the selector at the top right of your screen.
Look for the first line: "min_refresh_rate"
Tap that line and hit "Edit Value". Enter very specifically: 24.0
Hit "Save Changes"
Do the same exact thing for the next line: "peak_refresh_rate"
If for whatever reason these lines are missing, you can add them by scrolling all the way up and hitting "Add new setting". I'm not sure why it varies for some users..
And we're done! If you open Snapchat, Instagram, or an app that uses the camera, the refresh rate will stick to 120Hz.
I hope these instructions were clear enough!
The way I believe this works, is the adaptive refresh rate breaking because the minimum and maximum values are set to an unsupported value, thus causing the system not to be able to adjust the refresh rate.
Samsung made some changes on One UI 4, and it still does drop to 60Hz when you don't use the screen, or use Google Maps / Stock Camera. This does not occur on One UI 3.
** FIX 120HZ BUG ON ONE UI 4 **
(Guide 2 of 2)
What you'll need:
* Set Edit (free on the playstore)
Make sure you are not using power saving mode, and you have your refresh rate set to adaptive. Now launch Set Edit and enter the system table in the selector at the top right of your screen.
Look for the first line: "min_refresh_rate"
Tap that line and hit "Edit Value". Enter very specifically: 120
Hit "Save Changes"
Do the same exact thing for the next line: "peak_refresh_rate"
Set the value to: 120
If for whatever reason these lines are missing, you can add them by scrolling all the way up and hitting "Add new setting".
After you get an update that fixes the bug, it's important you change min_refresh_rate back to 48 , and peak_refresh_rate to 120 !
I created an account just to express my gratitude miss / mister !!
One known issue: Screen Brightness set to low causes it to be stuck at 60Hz regardless of the setting. Minor tradeoff at low brightness
You can use galaxy Max hz app for this too.
P-KAY 2323 said:
You can use galaxy Max hz app for this too.
Click to expand...
Click to collapse
I've used this, but it's not able to override the 60Hz cap when launching an app that uses the camera.
MochaVex said:
I've used this, but it's not able to override the 60Hz cap when launching an app that uses the camera.
Click to expand...
Click to collapse
Oh. Ok, gottha check it out then. Thanks for the guide
P-KAY 2323 said:
Oh. Ok, gottha check it out then. Thanks for the guide
Click to expand...
Click to collapse
Of course! Glad to help
MochaVex said:
So this is a huge discovery I made! Myself and many others are annoyed at the fact that Snapchat drops to 60Hz whenever the camera is activated. I found a workaround that allows it and other applications to remain at 120Hz even when the camera is in use! (excluding the stock Camera app)
What you'll need:
* Set Edit (free on the playstore)
* A computer that has ADB installed
* A charging cable.
I'll leave out the details on how to set up adb, we should know how to do this is 2021.. There are also plenty of detailed guides out there!
Make sure you are not using power saving mode, and you have your refresh rate set to adaptive. Now launch Set Edit, and grant the permission it tells you to with the adb shell command (it'll show you what to enter if you tap a line, and hit Edit Value).
After the secure settings permission is granted, enter the system table in the selector at the top right of your screen.
Look for the first line: "min_refresh_rate"
Tap that line and hit "Edit Value". Enter very specifically: 24.0
Hit "Save Changes"
Do the same exact thing for the next line: "peak_refresh_rate"
And we're done! If you open Snapchat, Instagram, or any third party app, the refresh rate will stick to 120Hz. It's unknown as to why the stock Camera still switches to 60Hz, but I don't care about that too greatly..
I hope these instructions were clear enough!
The way I believe this works, is the adaptive refresh rate breaking because the minimum and maximum values are set to an unsupported value, thus causing the system not to be able to adjust the refresh rate.
It still does drop to 60Hz when you aren't using the screen, so don't worry about that.
It's worth noting that this works on both One UI 3.0 and One UI 4 beta 2!
Works with most games and apps I've tested that previously reduce the refresh rate.
Google Maps is still stuck to 60Hz for example.
Click to expand...
Click to collapse
Not able to find min refresh rate and peak refresh rate in the system table ...
I so want to fix the 60hz lag in snapchat
aj7400 said:
Not able to find min refresh rate and peak refresh rate in the system table ...
I so want to fix the 60hz lag in snapchat
Click to expand...
Click to collapse
Try adding them as new lines. You'll see that option at the very top. Reboot after you finish. For whatever reason, not everyone has these..
MochaVex said:
Try adding them as new lines. You'll see that option at the very top. Reboot after you finish. For whatever reason, not everyone has these..
Click to expand...
Click to collapse
I dont know how to do abd .. can help?
No problem! If you go into your phone settings, scroll down and tap About Phone > Software Information > Tap the Build Number until it says Developer Options turned on.
Now go back to your settings and look for Developer Options at the bottom. Carefully scroll down and look for USB Debugging. Turn it on.
Now you'll need a laptop or computer for this next part! Go on XDA and look for a decent ADB tutorial. After adb is installed, you can plug your phone in. Open adb on the computer, and type adb devices.
You're phone should prompt you to allow that computer's signature, just tap allow.
Then you can type adb shell, and then input what the app tells you to.. If you encounter any more issues, don't hesitate to message me!
Hey ! I just found your post today... and tried it immediately on my Galaxy S21+. I searched something like that for so long!
You're an absolute genius! It's working perfectly for now, yet I'm a little surprised : it seems to work even in Google Maps and the stock camera. I didn't reboot the phone though, maybe it won't work after a reboot. It seems to work in low brightness too for the moment! By the way, SetEdit didn't ask me to do anything with adb. I just added the two lines you mentioned. Is that normal?
Thank you so much for that! I hope it'll stay like that even after a system update... we'll see!
brhb said:
Hey ! I just found your post today... and tried it immediately on my Galaxy S21+. I searched something like that for so long!
You're an absolute genius! It's working perfectly for now, yet I'm a little surprised : it seems to work even in Google Maps and the stock camera. I didn't reboot the phone though, maybe it won't work after a reboot. It seems to work in low brightness too for the moment! By the way, SetEdit didn't ask me to do anything with adb. I just added the two lines you mentioned. Is that normal?
Thank you so much for that! I hope it'll stay like that even after a system update... we'll see!
Click to expand...
Click to collapse
SetEdit (usually) asks me. Maybe it's able to edit that line without the adb permission (all I know is it asked me lol).
Glad it's working for you!!
And it should work after updating. I've updated twice in the One UI 4 beta and it still works
Yes it works even without adb ...
Wow thanks .. now i can use snapchat without a problem
aj7400 said:
Yes it works even without adb ...
Wow thanks .. now i can use snapchat without a problem
Click to expand...
Click to collapse
Ok cool! It seems to be hit or miss with needing adb so I'll leave it in the instructions. Have fun!
MochaVex said:
Ok cool! It seems to be hit or miss with needing adb so I'll leave it in the instructions. Have fun!
Click to expand...
Click to collapse
Working even after a restart.
I was wondering what would happen if min refrest rate is set to 1 and max refresh rate is set to 120 .. ( thats what the screen is capable of )
The system won't lower it any lower than 48. If you're using my custom values, it'll vary from 60 to 120 until you restore stock values.
Not sure what anyone would want to force to 120 when the smart refresh rate LTPO works very well. There's also noticeable battery savings.
You will see slightly better smoothness at the cost of battery life.... but LTPO is more than adequate where it stands now, IMHO.
Edit: I didn't see some users were having problems with apps like Snapchat. I see this might be the only temporary solution until that's fixed.
Burt Squirtz said:
Not sure what anyone would want to force to 120 when the smart refresh rate LTPO works very well. There's also noticeable battery savings.
You will see slightly better smoothness at the cost of battery life.... but LTPO is more than adequate where it stands now, IMHO.
Edit: I didn't see some users were having problems with apps like Snapchat. I see this might be the only temporary solution until that's fixed.
Click to expand...
Click to collapse
Yea I intended this fix for that very issue with Snapchat / any app that accesses the camera. Interestingly enough, it still uses adaptive refresh rate, my guide just breaks the 60Hz with camera applications restriction somehow.
Burt Squirtz said:
Not sure what anyone would want to force to 120 when the smart refresh rate LTPO works very well. There's also noticeable battery savings.
You will see slightly better smoothness at the cost of battery life.... but LTPO is more than adequate where it stands now, IMHO.
Edit: I didn't see some users were having problems with apps like Snapchat. I see this might be the only temporary solution until that's fixed.
Click to expand...
Click to collapse
For me, it didn't even impact battery life. But my S21+ (Exynos) wasn't really good to begin with, so I didn't notice any major battery drain with that "fix". And yes, it was mainly because of apps that used the camera (like Snap or even Google Messages) that I applied this workaround.
By the way, it's still working after the November security patch. Still amazed by this device after many iPhones!

Categories

Resources