The Nokia N86 wins the race to v20 firmware

slitchfield wrote:Did you wipe the mass memory as well though? If you'd installed apps on that (or on memory card) then there could still be something auto-loading and auto-running.

Of course, it maybe that you haven't installed any low level third party apps, in which case the phone could simply be faulty?....

rafii wrote:Try to use Energy profiler (available on OVI Store) to see if there is not a process running in the background.

On idle the phone consumes:
Screen ON + T9 lights ON = ~0.34 watts
Screen ON + T9 lights OFF = ~0.13 watts
Screen OFF + T9 lights OFF = ~0.04 watts

Press 0 to change the data displayed, and 8 to change between average and discrete measure.

Help me guys, there is something wrong with my phone. I reinstalled firmware v20 using the REFURBISH use case in Phoenix yesterday.

@rafiii
My results

Screen ON + T9 lights ON = ~0.39 watts
Screen ON + T9 lights OFF = ~0.24 watts
Screen OFF + T9 lights OFF = ~0.09 watts

I have formatted the mass memory. Does anyone here know how to open Phoenix Phone crash files cause I have them preserved (they are in .bin format)

Yes, my phone still powered Off in the night. When I powered it on again in the morning, the battery still had 4 bars

Your numbers don't seem particulary wrong even if they are higher than mine.

If I understand well your problem, when you go to sleep you have the full battery and then the next morning when you power the phone on you have 4 bars, that's it? And when you have 3 bars or something like that the battery dies rather quickly, even if the phone stays idle.

If that's the case I think that the behavior of your phone is normal. Symbian monitors the battery according to the voltage and not the capacity. In other words, it is not linear, it might takes 10 hours to lose the first bar and then 2 hours to lose the 3 next bars on the indicator.
Also, do not forget that powering up the phone use a lot of energy since there is no power management mechanisms started until you get to the home screen.

Maybe I will do a schema to make myself clear.

rafiii wrote:Your numbers don't seem particulary wrong even if they are higher than mine.

If I understand well your problem, when you go to sleep you have the full battery and then the next morning when you power the phone on you have 4 bars, that's it? And when you have 3 bars or something like that the battery dies rather quickly, even if the phone stays idle.

If that's the case I think that the behavior of your phone is normal. Symbian monitors the battery according to the voltage and not the capacity. In other words, it is not linear, it might takes 10 hours to lose the first bar and then 2 hours to lose the 3 next bars on the indicator.
Also, do not forget that powering up the phone use a lot of energy since there is no power management mechanisms started until you get to the home screen.

Maybe I will do a schema to make myself clear.

Yes, you have described my problem accurately. I find this pretty annoying and even if it IS something normal, the battery indicator should be fixed.

some night shots for you 😃:

Cheers,
Miki

DamianDinning wrote:1st the bad:

I don't think you'll see an update for Christmas 😞

Now the good:

Yes it is intended that there will be further update/s. 😊

The first is planned for early in the new year. Any further update/s are currently unconfirmed schedule wise.

These will be more about improving the product performance rather than new features if you know what I mean 😉

On the topic of v20 not being available for some variants. Please PM me with your product code and I will try and take a look for you - no promises! These may not be available due to operator approvals which in some cases can take longer. I did hear that there could be another small wave of variants released in the next 4 weeks or so.

atb

Where is this bloody update??!!!

Not agree

I have made many pair of comparison using my own n86 v20 & n82 v30 fo night shot with flash on.

I prefer use back n82 to take photo when no dc on hand.
Almost all photo taken with my n86 is out...especially slower shutter speed & bad white balance for flash photo & incorrect white balance for indoor. But for photo taken with my n82 was good because n82 can use faster shutter speed & bright & white flash light which give better photo. n86 doesnt take advantage on its bigger aperture & led light for photography at all. The bigger aperture just allow it to take photo using much lower ISO & led light does give vry slow shutter speed==> 1/8s? this was to slow to get better picture + stiff camera button.

if n86 can have higher ISO (but not ISO800 = too much noise) in order to reduce the shutter speed & exposure time like 1/20s i think it is quite enough to eliminate hand shake problem + its bigger aperture which will take more advantages.

Here is comparison:

n86 1/20s ISO348 (greenish colour due to led flash on skin)

1/9s ISO428 (the longer exposure time just give only brighter background)

n82 1/30s ISO800

1/30s ISO800

..not only this pair of photo.. but all n86 get loss as compare to n82 faster shutter speed & bright xenon light

another:

blue colour white balance when back light or on shadow place

Unregistered wrote:Where is this bloody update??!!!

I did say 'early' in the new year.

It's only 6 days in to the year, give us a chance! 😮

DamianDinning wrote:I did say 'early' in the new year.

It's only 6 days in to the year, give us a chance! 😮

They probably didn't realise that "afer new year" can be any date from january to december 😃

genus86 wrote:Not agree

I have made many pair of comparison using my own n86 v20 & n82 v30 fo night shot with flash on.

I prefer use back n82 to take photo when no dc on hand.
Almost all photo taken with my n86 is out...especially slower shutter speed & bad white balance for flash photo & incorrect white balance for indoor. But for photo taken with my n82 was good because n82 can use faster shutter speed & bright & white flash light which give better photo. n86 doesnt take advantage on its bigger aperture & led light for photography at all. The bigger aperture just allow it to take photo using much lower ISO & led light does give vry slow shutter speed==> 1/8s? this was to slow to get better picture + stiff camera button.

if n86 can have higher ISO (but not ISO800 = too much noise) in order to reduce the shutter speed & exposure time like 1/20s i think it is quite enough to eliminate hand shake problem + its bigger aperture which will take more advantages.

Here is comparison:

n86 1/20s ISO348 (greenish colour due to led flash on skin)

1/9s ISO428 (the longer exposure time just give only brighter background)

n82 1/30s ISO800

1/30s ISO800

..not only this pair of photo.. but all n86 get loss as compare to n82 faster shutter speed & bright xenon light

another:

blue colour white balance when back light or on shadow place

As part of our testing we evaluated the image quality achievable at various light levels comparing different amounts of gain. Our aim was to use as little gain as possible given how much discussion we see from people when either noise is high or noise reduction is high therefore removing detail from the image. On this basis we tried to balance ALL of the elements of noise, shutter speed, gain, exposure, noise reduction, colour and sharpening against each other. This meant many many different combinations before we settled on the one in the product. I think all things considered we have the best balance in the product. I admit not perfect in every situation but the best balance of all these aspects and across thousands of images. Remember what works in one particular scene may not work as well as in another. Also what is good for one person may not be good for another. I think we must have taken well over 20,000 test images and videos now in the tuning of the N86.

DamianDinning wrote:I did say 'early' in the new year.

It's only 6 days in to the year, give us a chance! 😮

Do you have a timescale for this update? Yes it is only 6 days but since it was to be expected for Xmas and has been delayed untill 'after' the New Year i imagine a lot of folk would be thinking it would be ready or due about now.

If it's not going to be released this month (Jan - 'after' New Year) then you should just be honest and tell us we're not getting it. Makes things a lot easier for everyone and your honesty would be appreciated.

Upto you now.

Unregistered wrote:Do you have a timescale for this update? Yes it is only 6 days but since it was to be expected for Xmas and has been delayed untill 'after' the New Year i imagine a lot of folk would be thinking it would be ready or due about now.

If it's not going to be released this month (Jan - 'after' New Year) then you should just be honest and tell us we're not getting it. Makes things a lot easier for everyone and your honesty would be appreciated.

Upto you now.

I think we should appreciate we have such person like Damian here. If we hadn't we would complain that the nokia is blind and deaf and don't answer our questions. When we have the answer we are still unsatisfied. If Damian would say the month than we would ask the day, when he would specify the day, I bet one would ask for time of day! Don't exaggerate, my friends! We'll eventualy get it!

Why has Nokia removed the possibility to mark photos by pressing the #-key in gallery??

At messages it still works. On my old N82 it works also for photos! :con?

RS77 wrote:Why has Nokia removed the possibility to mark photos by pressing the #-key in gallery??

At messages it still works. On my old N82 it works also for photos! :con?

Yes, very strange...it still works by pressing # + OK, but no longer by # + left/right

RS77 wrote:Why has Nokia removed the possibility to mark photos by pressing the #-key in gallery??

At messages it still works. On my old N82 it works also for photos! :con?

N82 was using the old gallery, whereas FP2 products are using the newer gallery which was ground up a new application.

The N82 had a stop gap solution for multiple marking the images after the edit key was removed. The newer gallery had a longer term solution for marking images. Personally I prefer the old method but on the other hand I believe the newer method was found to be more likely to be discovered by more people. A lot of people never get to find these 'hidden' features.

atb

Unregistered wrote:Do you have a timescale for this update? Yes it is only 6 days but since it was to be expected for Xmas and has been delayed untill 'after' the New Year i imagine a lot of folk would be thinking it would be ready or due about now.

If it's not going to be released this month (Jan - 'after' New Year) then you should just be honest and tell us we're not getting it. Makes things a lot easier for everyone and your honesty would be appreciated.

Upto you now.

If I knew the date I'd tell you. I am a firm believer in honesty.

I'm not hiding the date from you for some bizarre personal kicks 😉 It should be available soon but until it's approved I can't guarantee any date. If I did I'd only make things worse. As I post a date on here or even a week (as I have in the past) it then gets posted on some other site/s then if it slips for some completely valid reason there's a whole raft of ranting that then starts. I'd rather not be responsible for that. It's in our interest to get updates to you as quickly as we can.

BTW, to set the expectation this is relatively minor maintenance update, focused on maintenance. We're still planning to deliver another update later this year, but that's not guaranteed.

atb

DamianDinning wrote:N82 was using the old gallery, whereas FP2 products are using the newer gallery which was ground up a new application.

The N82 had a stop gap solution for multiple marking the images after the edit key was removed. The newer gallery had a longer term solution for marking images. Personally I prefer the old method but on the other hand I believe the newer method was found to be more likely to be discovered by more people. A lot of people never get to find these 'hidden' features.

atb

DamianDinning wrote:If I knew the date I'd tell you. I am a firm believer in honesty.

I'm not hiding the date from you for some bizarre personal kicks 😉 It should be available soon but until it's approved I can't guarantee any date. If I did I'd only make things worse. As I post a date on here or even a week (as I have in the past) it then gets posted on some other site/s then if it slips for some completely valid reason there's a whole raft of ranting that then starts. I'd rather not be responsible for that. It's in our interest to get updates to you as quickly as we can.

BTW, to set the expectation this is relatively minor maintenance update, focused on maintenance. We're still planning to deliver another update later this year, but that's not guaranteed.

atb

Thanks for getting back to me and all understood, cheers.

DamianDinning wrote:BTW, to set the expectation this is relatively minor maintenance update, focused on maintenance.
atb

I really hope that's NOT the case. Should be MAJOR maintenance release 😊

I can't get GPS lock with A-GPS disabled, waited over 40 min, several occations. When A-GPS enabled, it's a matter of 10-15 sec. Hope this will be fixed among other issues (like auto-rotation broken, RealPlayer buttons don't work in full screen (D-pad: FF and RW), better memory usage, more responsive....

Cheers,
Miki

miki69 wrote:I really hope that's NOT the case. Should be MAJOR maintenance release 😊

I can't get GPS lock with A-GPS disabled, waited over 40 min, several occations. When A-GPS enabled, it's a matter of 10-15 sec. Hope this will be fixed among other issues (like auto-rotation broken, RealPlayer buttons don't work in full screen (D-pad: FF and RW), better memory usage, more responsive....

Cheers,
Miki

...charging light behavior, missing "show gps information", "already in use" message when deleting picture that was just taken, missing music folder icon, multiple (visible) contacts and ovi chat processes, paused song that starts playing after the call even when it was't playing before the call, kickstand that won't open any program if the keypad is locked, thumbnail generating and picture zooming difficulties, minor full screen clock option inconsistency...
Yup, it must be a maintenance update, but really a major one if all this is going to be fixed 😉

sebarkh wrote:I think we should appreciate we have such person like Damian here. If we hadn't we would complain that the nokia is blind and deaf and don't answer our questions. When we have the answer we are still unsatisfied. If Damian would say the month than we would ask the day, when he would specify the day, I bet one would ask for time of day! Don't exaggerate, my friends! We'll eventualy get it!

I agree with this, it's extraordinary that we actually have someone to complain to 😊

DamianDinning wrote:N82 was using the old gallery, whereas FP2 products are using the newer gallery which was ground up a new application.

The N82 had a stop gap solution for multiple marking the images after the edit key was removed. The newer gallery had a longer term solution for marking images. Personally I prefer the old method but on the other hand I believe the newer method was found to be more likely to be discovered by more people. A lot of people never get to find these 'hidden' features.

atb

I am trying to think of the reason why couldn't both solutions exist. They've removed something that's been there since the beginning of the series 60. It would be great to see it included in next version, but I guess it's just wishful thinking, especially when it's the matter of FP2, not the phone itself.

Oh, and I remembered I spotted two more bugs 😊 One is with before mentioned full screen clock that shows when you press d-pad while the phone is locked. Sometimes it shows landscape-mode-sized clock when the phone is in the portrait mode. The result is that not all numbers fit to the screen, you don't see the whole time and date. I couldn't find any pattern for this.

The other bug was posted before somewhere, I think, but maybe not in this forum. Closing the slider locks the keypad. But while the message "keypad is locked" is shown screen can still be rotated. The common scenario is this: I walk, type something into my phone, I finish that, close the phone (all of this was in the portrait mode) and put it in the pocket. When I get it out of the pocket, it is in the landscape mode and I didn't want it that way. It changed orientation while I was putting it in my pocket, it was in position that would turn it to landscape mode, but it shouldn't because I previously closed the slider and therefore locked the keypad. I hope this is not so confusing, if it is I have video to explain it 😃 Could it be made that accelerometer is disabled the moment the "keypad locked" message appears, and not only after it disappears?

The v20.115 finally available for my N86 🙄 Sorry I'll stay cool this time 😃 Why didn't nokia bring out the new v21? Has the v20 to be installed before upgrading to v21 or can I skip this buggy v20?

djmuzi wrote:The v20.115 finally available for my N86 🙄 Sorry I'll stay cool this time 😃 Why didn't nokia bring out the new v21? Has the v20 to be installed before upgrading to v21 or can I skip this buggy v20?

You can skip it, but don't expect the new update too soon 😊

Hi Mate,
I read your entire post it is really nice job I understand well your problem, when you go to sleep you have the full battery and then the next morning when you power the phone on you have 4 bars, that's it? And when you have 3 bars or something like that the battery dies rather quickly, even if the phone stays idle.

If that's the case I think that the behavior of your phone is normal. Symbian monitors the battery according to the voltage and not the capacity. In other words, it is not linear, it might takes 10 hours to lose the first bar and then 2 hours to lose the 3 next bars on the indicator.
Also, do not forget that powering up the phone use a lot of energy since there is no power management mechanisms started until you get to the home screen.

DamianDinning wrote:
BTW, to set the expectation this is relatively minor maintenance update, focused on maintenance. We're still planning to deliver another update later this year, but that's not guaranteed.

atb

Could u pls tell me whether this update will fix GPS lock without AGPS. Believe me, unlike many others, my N86 is totally bug free (may be there are some, I don't notice), except that GPS lock. If it is fixed, I am very happy with my N86. Thanks.

Firmware V21.006 is available

RS77 wrote:Firmware V21.006 is available

Just read in Nokia Support Discussions:

"I have just downloaded the firmware 21.006. The keypad tones are back, I can turn on the theme effects now without any problems, but apart from that all my bugs still exist :smileysad: I am currently going through the list of problems and am yet to find any other solutions. My music player has been refreshing now for about ten minutes!"

Only the brave should make the update 😃 My N86 still offers me the v20.115... I think my product code will be able to update in March or April, enough time to read about bugs of the v21 😃

Btw. the v21.006 seems to be a real Christmas gift, see the date 24.12.2009 😃 😃 😃

Assuming all goes as planned, should be available to over 120 variants by early next week, maybe earlier (as above.)

Principle fixes are in these areas:

Browser, camera, email, maps
But there are many others too... e.g. music remains paused after call now, if you had paused it yourself before receiving a call. At least it does on mine 😊

atb.

D

There is a new thread on AAS for the v21 discussion 😊

YUHHHOOOOO!! Finally the most desired update in smartphone history is here!! On my way to update! Thanks for the support, DamianDemming.

It's available OTA to me as well in UAE, but I don't know whether to update it now or wait for more comments on it...

What do you think?

My Googlemail account via Nokia N86 E-mail does not sync after the update :con? Strange, anyone the same problem?

Btw wrong icons in log are still not fixed with V21.