Mozilla has been testing Firefox for Android on ARMv6 devices. We have had builds available for some time now, but we know that Firefox does not run optimally on all devices. Initially, we are limiting Firefox for Android to devices with 800MHz CPUs and 512MB of RAM. See this post for more info:
blog.mozilla.org/futurereleases/2012/09/07/firefox-for-android-beta-is-expanding-support-to-new-devices-help-us-test/
Many ARMv6 devices fall outside of these requirements, so we are looking for feedback on stability and performance for devices with lower specifications and we need your help. There are a lot of potential devices out there and we are not able to test Firefox on all of them. If you can't install the latest Firefox Beta for Android from the Google Play Store, it might be because your device falls outside the 800MHz/512MB requirement and we block it. You can install the Beta directly from the Mozilla FTP server: ftp.mozilla.org/pub/mozilla.org/mobile/releases/16.0b4/android-armv6/multi/
If you take the time to test Firefox on your ARMv6 device and want to post some feedback, please include your device model so we can get the CPU speed and amount of RAM. We'd like you to think about how Firefox compares to the stock browser (or other browser) on your device. Things to try:
Load some web pages. Compare how long they take to load.
Scroll up and down longer pages. It should be smooth.
Open multiple tabs. Switch back and forth between them. It should be responsive.
Use the 'Reader' icon in the URL bar to view an easy-to-read version of articles and posts.
Accessing Bookmarks and History should be fast and scroll smoothly.
Does Firefox crash while loading pages or any other times?
Does Firefox seem to restart a lot when switching between applications?
Does Firefox feel slow and laggy? If so, when is it happening.
Thanks for your help. In addition, the Mozilla QA team is running a testday on September 28th for people to try out various new features and look for bugs. See:
quality.mozilla.org/?p=42896
If you have questions or comments, the Mobile team hangs out on Mozilla's IRC (irc.mozilla.org) in the #mobile channel.
Feel free to also subscribe to our mailing list: https://mail.mozilla.org/listinfo/mobiletestdrivers-armv6 for news
Its woking
Fire fox is working very well with no lags..
More over it supports the flash plugin of adobe flash 11.0.152 ; YouTube videos work; farmville opens [dont like to play as on pc, but it works]
Related
Does Fennec works?
Its very unstable on hd2,lags all the time and many times crash on most of devices because is alpha realese
And as far as I know they have stopped development of Fennec for Windows Mobile and they also wont develop for WP7 because it offers no NDK I think.
Yeah, the above posts are both right. I gave it a try for a while and couldn't even access a web page - it's nowhere near usable, although there was a nice sliding menu system.
You'd be better sticking with Opera or Skyfire.
I have a theory that Android uses the CPU exclusively to display a webpage, while iOS loads the rendered result of the current window into the graphics buffer. This would explain the checkerboarding that you get on iOS that you don't on Android, why zooming on Android doesn't blur like iOS does, and why slow scrolling on iOS is so smooth.
Does anyone know if I'm right about this?
iOS display every Website in the same way. Visit a website that is not mobile and u see Android is faster!
iOS display not the whole website so its get good performance.
Edit me if i am wrong
It's actually the other way around. Visit a website that is not mobile and you'll see the Android default browser crawl. The checkerboard pattern on iOS is precisely as you described it: the CPU is not keeping up with page rendering, and it hasn't loaded that part of the web page into the GPU buffer yet. But it only happens to really large web pages with a lot of contents (a tech blog).
The Android UI lacks any sort of GPU acceleration possible, and it's been an ongoing issue for a while. The Android team responded that it wasn't done earlier on because earlier hardware just wasn't enough for it. All current Android devices are effected...
On the bright side, if you want smooth browsing on your Android phone, you can use Opera Mini. I'm using it myself.
What browsers are u guys using ?
THUNDERBOLT
dolphin mini for regular browsing...dolphin HD for when i wanna watch HULU..
Default
-Monky_1
I like the default browser. Haven't had any problems yet.
Sent from my ADR6400L using XDA App
Using regular browser here, but I have Opera Mobile installed, gonna be giving that a try.
I think the regular browser is great but I just started using Miren and like it a lot so far.
I am using firefox 4, and it is pretty nice. I wish it were snappier, but it's feature set is so nice and the fact you can swipe right to see open tabs and swipe left for back/forward/bookmark, it's super convenient.
Xscope
Sent from my ADR6400L using XDA App
Been on dolphin hd for a few months now. I would use firefox more if pictures didn't look so bad.
Sent from my ADR6400L using XDA App
Xscope here
Sent from my ADR6400L
I use stock for most normal browsing. Have Dolphin hd setup as a desktop profile for hulu and the like.
Sent from my Thunderbolt using Perfect Storm xda app.
Miren Browser, for sure.
Sent from my ADR6400L using XDA App
Normal browser. I really like the pinch-zoom-out gesture used for opening new windows. Really spiffy and easy.
So, rally any of them then.. LOL No real distinct one is better than another..
Everyone has their own choice of browser as you can see. However, that doesn't mean a particular browser wont have features or semantics that wont appeal to you more than others, so try them all and see.
For the record though, I prefer Opera Mobile, but I also use Opera on my desktop as the main browser as well. However, some browsers do certain things better than others. I prefer firefox (for firebug and dynatrace http://www.dynatrace.com/en/) when I develop and SrwIron (chrome) is my fallback browser on the desktop if Opera wont work on a site.
Opera probably has the longest development track record (starting years ago with windows phones and symbian) for a mobile browser (and one of the longest for support on ARM processors in general). All but a wrapper that calls the code libraries (.so files or for those that stick with windows, .dll files) in Android's dalvik vm are compiled natively for ARM in c++ (since they use these libraries on windows phones and symbian as well), so they have the ability to run faster than the code that must be interpreted through the dalvik virtual machine. See http://my.opera.com/operamobile/blog/the-components-of-opera-mobile-11-on-android for more details on that.
Opera will also allow you to sync your browsing history, bookmarks, search history, favorite pages (the speed dial), etc to the desktop version if you use it. http://my.opera.com/desktopteam/blog/my-opera-synchronization-explained
Opera also has a pretty good track record for security and patching exploits. I'm leary of trusting any browser other than Opera or the native one built into Android, which has similar libraries as chrome (firefox mobile is probably okay as well, but it's still in the development phase so there could be bugs or things not patched quite yet). The rest of the mobile browsers other than firefox mobile (built on gecko) and opera (built on presto) are all mostly close to vanilla webkit clones (excluding the built in android browser similar to chrome) that aren't overly proven to be secure or have a long history of development. Since they're webkit clones (since webkit is currently the only stable open source platform choice for phones until the release of a stable firefox mobile), they're all going to tend to look somewhat alike and have similar speeds. That's not to say they are not secure, but they're mostly rookies to the game compared to Chrome/FireFox/Opera. Webkit rendering engine itself is well designed (with a history of being used on mobile phones long before android via nokia's built in symbian os browser), but how companies take that code and implement is is the problem. In the pwn2own hacking competition, chrome (the desktop version) was the only webkit based browser not to be susceptible to a major exploit.
Opera has its little annoyances like any browser. Mostly things like being ignored by bad web developers in the past that only cared about IE. However since firefox and chrome follow web standards like opera now and have a significant market share, this rarely happens nowadays. Though, sometimes I will stumble on a site using the desktop version that forgets Opera is also a desktop browser and gives me the mobile page, haha. For quite a while, McDonalds.com would do this.
Any of the more popular browsers should be good enough if you use good judgment, but if you're ever leary of a site, at least pick a browser you can disable plugins (flash and pdf readers) and javascript if needed, since those are the 2 main ways you might get hacked via a web browser. In opera mobile, you can type "opera : plugins" (without quotes and the spaces) in the url and you can disable any plugins you do not want to use. With that it's generally harder to monitor the system internals and connections on your phone versus a desktop pc (and the wonky permission control system [or lack thereof] in the graphical interface of android), it's better to be a bit more cautious.
I like dolphin HD
I use Firefox and the default one. For some reason Firefox has problems for me on facebook when i try to send a message
Sent from my ADR6400L using XDA Premium App
Opera Mobile is currently my browser of choice.
@yareally: a simple "I prefer Opera Mobile" would've sufficed. We get it, you like it.
I'm using a WP7 NoDo ROM on an HTC HD2 that I was previously running Android on. I really like WP7 (the music player especially) and am looking forward to getting more apps in the Marketplace.
BUT, I've been disappointed with the web browser. I visit a number of technology blogs, most of which use the Disqus system for posting comments. When using the WP7 browser, I regularly see messages saying "you are using an older browser, please upgrade your Flash version or upgrade to Internet Explorer 8 in order to comment". This is on Boy Genius Report (mobile version).
I get that WP7 doesn't have Flash, so it must be the IE version that's not letting me comment. On some sites, I can't even view the comments when accessing the mobile version of the site like Engadget. I can view it when accessing the desktop version of the site, though like before, I can't post comments. I never had these problems on the Dolphin Browser Mini on Android.
Also, I've set the user agent on the WP7 browser to "desktop" a number of times, but it keeps defaulting to the mobile website on sites like Gawker (and its associated sites like Gizmodo,etc), Boy Genius Report and Ars Technica. Any way to solve this?
Last problem: on the Gawker network sites, when accessing the mobile site, I can't expand replies. I click the link that says "Show 2 replies" or something, nothing happens. The link gets highlighted once i touch it, but it doesn't expand. The fonts in the comment section look jagged and pixelated as well, which doesn't happen on other sites.
Try a Mango beta ROM for the HD2 as mango have IE which might fix some of your problems. As for the desktop/mobile view, some site supersede what ever setting you have set in your browser. I know, it's annoying, but it's the site, not IE. Facebook, Youtube, Google, & a few other sites do this. Some have a link to click to change that setting via a cookie, others, you have to manually type in the "www.".
I tried a Mango ROM but it's a laggy right now (not much, but the NoDo has zero lag, so it's noticeable). any way, the problems were there as well. You're right, some sites do force a redirect to the mobile site. It just sucks that the WP7 browser is still primitive compared to those available on Android or iOS.
some people who post here are misinformed, I don't get redirected on any sites I goto except for google and their sister sites. the fact that the wp7 browser is primitive compared to android and iOS is also wrong because I've gotten redirected to mobile sites much more on those browsers than on wp7 NoDo and mango beta. those browsers don't even have an option to toggle between mobile and desktop.the wp7 mango browser which is based off IE9 scores 97/100 on the acid3 test while the android and iOS browsers are in the low 90s. the IE in mango also renders html5 at a higher framerate than the competition.this has been proven as well. and as for the fact of the disqus comment system not working in NoDo this is because the IE in NoDo is based off IE7 and those sites require IE8 to comment. it could also be due to the fact that like IE7 the IE in nodo only clocks a score of 15 on the acid3 test. the disqus comment system is also known for having issues as well.
Disqus i have problems on. But i can read comments and switch between mobile or desktop without problems on the sites i wisit. I even save bookmarks in various formats since some places is better in mobile view. I can however on sites as pocketnow not read comments in mobile view, i cant do that on my currently borrowed Android phone ether.
Heard users having no problems on Mango thou.
eric12341 said:
some people who post here are misinformed, I don't get redirected on any sites I goto except for google and their sister sites. the fact that the wp7 browser is primitive compared to android and iOS is also wrong because I've gotten redirected to mobile sites much more on those browsers than on wp7 NoDo and mango beta. those browsers don't even have an option to toggle between mobile and desktop.the wp7 mango browser which is based off IE9 scores 97/100 on the acid3 test while the android and iOS browsers are in the low 90s. the IE in mango also renders html5 at a higher framerate than the competition.this has been proven as well. and as for the fact of the disqus comment system not working in NoDo this is because the IE in NoDo is based off IE7 and those sites require IE8 to comment. it could also be due to the fact that like IE7 the IE in nodo only clocks a score of 15 on the acid3 test. the disqus comment system is also known for having issues as well.
Click to expand...
Click to collapse
I am just speaking from day-to-day usage experience. I mentioned that I was using Dolphin Browser Mini on Android, which certainly does have a user agent option, so you are mistaken.
On Mango Beta I was having the same browser problems as I did in my OP (NoDo). Disqus would display OK on desktop sites (and on some mobile sites) but wouldn't let me log in or post. On Gawker Media sites, I couldn't expand replies on their proprietary comment system, which displays fine on DBMini. THe fonts are also messed up on WP7. You can see for yourself by checking the fonts on comments on your computer and then looking at them again through WP7.
Scrolling through forums like Crackberry or NotebookReview is also a little sluggish, whereas there isn't any lag on DBMini. The desktop version of the Staples site also lagged, and showed typing delays in the search bar. I don't get what those benchmarks are supposed to mean, by the way. I don't go to graphics intensive websites on my phone or anything, just simple news and shopping websites.
Nakazul said:
Disqus i have problems on. But i can read comments and switch between mobile or desktop without problems on the sites i wisit. I even save bookmarks in various formats since some places is better in mobile view. I can however on sites as pocketnow not read comments in mobile view, i cant do that on my currently borrowed Android phone ether.
Heard users having no problems on Mango thou.
Click to expand...
Click to collapse
So maybe this is a case of web designers optimizing site display for iOS and Android browsers, but not WP7? I thought there were standards in place so that they'd all display the same in all browsers.
aniym said:
I am just speaking from day-to-day usage experience. I mentioned that I was using Dolphin Browser Mini on Android, which certainly does have a user agent option, so you are mistaken.
On Mango Beta I was having the same browser problems as I did in my OP (NoDo). Disqus would display OK on desktop sites (and on some mobile sites) but wouldn't let me log in or post. On Gawker Media sites, I couldn't expand replies on their proprietary comment system, which displays fine on DBMini. THe fonts are also messed up on WP7. You can see for yourself by checking the fonts on comments on your computer and then looking at them again through WP7.
Scrolling through forums like Crackberry or NotebookReview is also a little sluggish, whereas there isn't any lag on DBMini. The desktop version of the Staples site also lagged, and showed typing delays in the search bar. I don't get what those benchmarks are supposed to mean, by the way. I don't go to graphics intensive websites on my phone or anything, just simple news and shopping websites.
So maybe this is a case of web designers optimizing site display for iOS and Android browsers, but not WP7? I thought there were standards in place so that they'd all display the same in all browsers.
Click to expand...
Click to collapse
yea I didn't experience issues with commenting in NoDo before they made the IE8 requirement,haven't tried in mango yet. it may all he due to the fact that disqus uses popups and IEM9 doesn't support pop UPS. I don't know about the 3rd party browsers because I dont use them. provide links to the sites ur experiencingthese "problems" on so we can test.
All of us surely remember the time when we had to deal with the agonizingly slow Mircosoft Internet Explorer browser. Most of us had alternates like Google Chrome, downloaded just so they would not have to go through the torture and delay that the Internet Explorer put us through. But, those days are definitely over and, Mircosoft’s Edge browser is going strong, so far. And, now, Microsoft’s star browser would not be limited to only your PC; it is coming to iOS and Android (the beta version is already here!)
Making their browser available on Android and iOS was the next step we expected Microsoft to take, in order to work better with smartphones. Mircosoft’s Edge browser has a unique feature that makes it stand out among all the other browsers you can use on your smartphone. It has a ‘continue on PC’ feature, which lets you continue your browsing where you left it off on your smartphone. Cool, right?
The Edge browser has a lot more to offer than just the ‘continue on PC’ feature. Having the iOS and Android app, allows you to access your history, favorites, reading list and ebooks. Joe Belfiore, fro Microsoft, says that they still have to work on the desktop version of Edge to support the smartphone app. Below is link
xdevhost.com/files/4e28341c2dab83c6f15a974ed432ca54.apk