I'd like to know if the camera app has changed in PR2.0.. all anyone talks about is the dam browser and Querty keyboard..
PR2.0 browser - Any facts?
jake20 wrote:I'd like to know if the camera app has changed in PR2.0.. all anyone talks about is the dam browser and Querty keyboard..
No change in camera app.
What device has a querty keyboard?
Dr Tran wrote:What device has a querty keyboard?
They all have an on-screen QWERTY keyboard but the Nokia E7 has a hardware one as well. See here:-
Even with a tidy-up, the Symbian 2.0 browser is only be so fast. At which point server compression speeds up page loading more. Assuming Symbian PR 2.0 browser be as fast as Opera mobile 11, which is probably not likely - Opera mini would still loads site noticeably faster.
So not sure about you guys - might just keep on using Opera mini 6 regardless.
err.. the complaint about the Symbian browser was never with the downloading but more on the Java Scripting engine being slower than the competition. Users complain that the page doesnt finish loading until the JScript is actually finished parsing (which can be up to a minute or more).
In fact, the funny thing is, most of the competition are all spawned from the Webkit family (KDE web browser) including the Safari / IOS browser. But its mainly the implementation of it that needs optimisation.
People also have to realise is - the N8 is still has an "underpowered" CPU at the end of the day compared to an iphone 4 for example - 680Mhz of core processing using an ARMv6 processor versus the iPhone4 of 1Ghz with ARMv7 processor (A4). Realistically, this gives a much better advantage to the iphone (around 50% faster). IF the N8 came with a Cortex A8 (ARMv7) running at 1Ghz for example, the gap would close up substantially.
BTW.. Opera Mini 6 CAN be slow as well - because it has to go through another source (Opera's proxy servers), re-render and reformat it all before resending it down to your phone. Yes, the transmission size is small with the compression, but you waste time waiting for them to render the page in the first place. It gets worse when there are congestions in the traffic and proxy servers waiting longer in effect. Also, Opera Mini 6 typically cannot render webpages on the Local Area Network - so that can be pretty much ruled out for Intranet type access.
Not impressed either by this, according to Rafe a full rewrite wont happen till PR3 so why has it took them this long grrr
bchliu wrote:err.. the complaint about the Symbian browser was never with the downloading but more on the Java Scripting engine being slower than the competition. Users complain that the page doesnt finish loading until the JScript is actually finished parsing (which can be up to a minute or more).In fact, the funny thing is, most of the competition are all spawned from the Webkit family (KDE web browser) including the Safari / IOS browser. But its mainly the implementation of it that needs optimisation.
People also have to realise is - the N8 is still has an "underpowered" CPU at the end of the day compared to an iphone 4 for example - 680Mhz of core processing using an ARMv6 processor versus the iPhone4 of 1Ghz with ARMv7 processor (A4). Realistically, this gives a much better advantage to the iphone (around 50% faster). IF the N8 came with a Cortex A8 (ARMv7) running at 1Ghz for example, the gap would close up substantially.
BTW.. Opera Mini 6 CAN be slow as well - because it has to go through another source (Opera's proxy servers), re-render and reformat it all before resending it down to your phone. Yes, the transmission size is small with the compression, but you waste time waiting for them to render the page in the first place. It gets worse when there are congestions in the traffic and proxy servers waiting longer in effect. Also, Opera Mini 6 typically cannot render webpages on the Local Area Network - so that can be pretty much ruled out for Intranet type access.
If competitors could get more out of Webkit, then why couldn't Nokia? they were amongst the frontier to implement it, by a long shot. You're right about the downloading speed - though the rendering speed determines our perception of speed directly. Symbian browser in terms of speed has not improved dramatically, since N95; this PR2.0 serves to become the first major update to user experience in 4 years, and I frankly do not understand why it took so long..
N8 has 680Mhz core, we just got to make do, and get most from. I prefer Opera mini - it's not perfect but does what I want without becoming an liability. Would even go as far, as saying it's the only decent browsing experience I've had on Symbian.
bchliu wrote:People also have to realise is - the N8 is still has an "underpowered" CPU at the end of the day compared to an iphone 4 for example - 680Mhz of core processing using an ARMv6 processor versus the iPhone4 of 1Ghz with ARMv7 processor (A4). Realistically, this gives a much better advantage to the iphone (around 50% faster). IF the N8 came with a Cortex A8 (ARMv7) running at 1Ghz for example, the gap would close up substantially.
Couldn't agree with you more bchliu.
After the fiasco of the N97 you'd have thought they would have learned their lesson about under powering their flagship smartphones, the N8 and E7.
In my review of the N8, 6 months ago, I remarked that I had feelings of deja vue after the N97 and those feelings grow daily. 😡
vdhan22 wrote:
Firmware PR 2.0 which has got portrait qwerty and tabbed browsing is postponed to May-June.
What was the original release date for PR 2.0 given by Nokia and where was that published (link please)?
vdhan22 wrote:
Nokia should apologise to it's symbian 3 users for this inconvenience!
If they have never officially given a release date for PR 2.0... why should they apologise?
vdhan22 wrote:
http://pctipsntutorials.blogspot.com/2011/03/release-of-pr-12-delays-upgradation-of.html
I'm guessing that this is your blog as you copy/paste its contents and url in every posting you make on this forum. 😃
I think there is no reason to postpone the PR2.0 that much. Anyway, I hope Nokia is only waiting till April 12th because it is the date of C7 Astound's launch in USA.
It would make more sense, after all this way Nokia would allow a standard Symbian version on all smartphones.
Here is the thing: @Blog_Jack, a chinese blogger posted: "Have further information to determine next Tuesday (12 / 4), Nokia will release new Symbian phone / PR2.0"
His blog seems to be very up-to-dated so I don't disconsider this information.
bazao wrote:Here is the thing: @Blog_Jack, a chinese blogger posted: "Have further information to determine next Tuesday (12 / 4), Nokia will release new Symbian phone / PR2.0"His blog seems to be very up-to-dated so I don't disconsider this information.
Brings a whole new meaning to the phrase, "Chinese whispers". 😃
Just to let you know.. Upgraded to the latest QT (4.7.3) which updates the Webkit libraries that the S^3 web browser uses as the main core engine. Its a very visible increase in performance from the regular pages I go to and is a lot snappier in response. Also less prone to "hanging" when a bad JS waits for an object. Very impressed with this..
Nice to know that!
And BTW, the chinese source was right, eh?
I just went back to page 1 of this thread to read ironass's comments about the PR2.0 browser video. I wanted to see which web pages he noted as particularly bad (saves me having to cringe through the video again).
Earlier this week I installed PR1.2 and today I applied Qt & QtWebKit 4.7.3 and QtMobility 1.1.2. See April 12th thread.
I've just loaded dailymobile and the NYT website and...well what a difference!
I'm not saying that the browser now performs as well as the best of the browsers on other high-end phones, but the render times and responsiveness are now well within my own frustration tolerances.
I'm a happy upgrader 😃
Here is a "leaked" Three video with the new X7 and the new OS/ functionality / browser
http://www.gsmarena.com/nokia_x7_shows_up_on_video_sporting_symbians_latest_ui-news-2503.php
Pretty impressive to me.. cant wait..
In case you missed this on the AAS News page, here is a "hands on" review of the new, final version, "Anna" (a.k.a. PR2.0) browser:-
"Well… honestly, I was expecting more. The browser is much faster than before, but it still feels old compared to other smartphone’s browsers."
"We know that HTML5 is not a simple concept. It’s an umbrella for many, many different things. However, every browser shipped in 2011 needs to be HTML5-some-kind-compatible.
I can’t believe that a mobile browser released this year can be shipped without W3C Geolocation API support. It’s a basic API, a more mature standard than HTML5 and very simple to implement. So: Symbian Anna Browser does not support Geolocation
In fact, it doesn’t support any HTML5 API apart from Canvas (2D drawing). Other great missing is video & audio support. You can still use Flash for video playing on Symbian browser, but video tag was a feature I was expecting for this release.
What is missing from the main HTML5 features available on other platforms:
* No Viewport support
* No Audio & Video tag support (the multimedia events seems to be there, but I couldn’t see a <video> tag working)
* No Application Cache / Offline storage mechanisms
* No Geolocation API
* No Accelerometer / Motion API
* No HTML5 new input types"
Full review here:-
http://www.mobilexweb.com/blog/symbian-anna-browser-html5
The reviewers credentials are contained in this article over on Symbian Freak...
http://www.symbian-freak.com/news/011/04/html5_support_on_the_new_symbian_anna_browser.htm
Very bad news.... 😞 I'm still waiting to see its result on Acid3 Test and the upcoming Acid4!
hmm.. HTML5 capability is kinda bit overrated - given IE9 scores even worse for HTML5 compliance, it will be quite some time before the advanced functionality will get used. Whats more important is probably the overall interface and usability over the old version.
Its never about technology - just about how applicable it is to the users.