Active Topics

 


Reply
Thread Tools
Posts: 42 | Thanked: 27 times | Joined on Dec 2009 @ Espoo, Finland
#461
Originally Posted by vitaly_repin View Post
Confirming the bug. Completely forgot that this crap is included into the sales box distribution. Sorry for not informing you, guys, here. Will include the link to this post in the very first post of this thread.

After sw. update, this bug will not happen anymore and no additional steps (symbolic linking) will be needed to import certificate.
When can we wait this software update? In near future?
 
vitaly_repin's Avatar
Posts: 320 | Thanked: 763 times | Joined on Oct 2009 @ Espoo, FInland
#462
Originally Posted by labra View Post
When can we wait this software update? In near future?
I can not communicate the marketing plans, sorry. My personal hope - yes, in near future.
 

The Following User Says Thank You to vitaly_repin For This Useful Post:
vitaly_repin's Avatar
Posts: 320 | Thanked: 763 times | Joined on Oct 2009 @ Espoo, FInland
#463
Originally Posted by labra View Post
vitaly_repin: is this a known bug and will this be fixed?
In the first sw. update which contains MfE update.

Shortly speaking - in the first MfE update.
 

The Following User Says Thank You to vitaly_repin For This Useful Post:
Posts: 547 | Thanked: 1,383 times | Joined on Sep 2009 @ Stockholm, Sweden
#464
Originally Posted by vitaly_repin View Post
12.1 protocol (Exchange update is needed). Or wait for N900 MfE client update. I am really sorry about this bug.

The keywords to detect it:

MS-ASProtocolVersions: 1.0,2.0,2.1,2.5,12.0
AS-LIB: Created factory for version 2.5

After client update (w/o server update) you will see:

MS-ASProtocolVersions: 1.0,2.0,2.1,2.5,12.0
AS-LIB: Created factory for version 12.0

After Exchange update you will see:

MS-ASProtocolVersions: 1.0,2.0,2.1,2.5,12.0,12.1
AS-LIB: Created factory for version 12.1
Thanks, forgot to apply SP1 & SP2 to the server in question, I'll do that now.

Thanks again

Edit: SP1 installed, syncs just fine, thanks
__________________

Problem with fMMS? Run in x-terminal: cp /tmp/fmms.log /home/user/MyDocs/
After that you'll see fmms.log in filemanager or when you connect the device to your desktop as a mass storage device.
E-mail the log to me, if you don't have the email address, drop me a PM. Thanks!

fMMS - MMS for your N900
fAPN - GUI for adding a new GPRS APN
If you like this post, don't be shy to thank me -->

Last edited by frals; 2009-12-14 at 12:47.
 
Posts: 221 | Thanked: 51 times | Joined on Nov 2009 @ Germany
#465
Originally Posted by HugoSon View Post
Actually - can someone confirm this problem? Or am I the only idiot synchronizing manually trying to get out eMails written on the N900?
Hi Vitaly - can you confirm this one? Will this be fixed also in the next sw. update?
 
Posts: 23 | Thanked: 5 times | Joined on Dec 2009
#466
Originally Posted by vitaly_repin View Post
Agree with small remark - full provisioning support requires quite huge reworking of the whole system.
And what about a partial provisioning support? My company requires the device lock code to be inserted in the phone.
 
rjzak's Avatar
Posts: 170 | Thanked: 23 times | Joined on Oct 2008 @ Annapolis, MD, USA
#467
Originally Posted by karmax View Post
And what about a partial provisioning support? My company requires the device lock code to be inserted in the phone.
That might actually do it for me, too.
__________________
Professional Genius
N810 WiMax Edition
Nexus One
 
Posts: 48 | Thanked: 128 times | Joined on Dec 2009
#468
Originally Posted by vitaly_repin View Post
First. Log is needed. https://bugs.maemo.org/show_bug.cgi?id=5597#c26
I try to record a log according to these instructions (I bypassed sudo -gainroot and cat commands, as they were optional).

However, only lines that are printed to syslog are like this (when device is booted):

Dec 14 19:59:51 Nokia-N900-42-11 cellmo-watch[739]: LINK UP: MCU-SW Ver: V ICPR82_09w34.3, 16-10-09, RX-51, (c) Nokia

Can anyone say what is the problem with my syslog?
 
Posts: 486 | Thanked: 154 times | Joined on Sep 2009 @ New York City
#469
Hi Vitaly,

I have a weird quirk I'd like to report with MfE.
Connected to Exchange 2007:

When I click into my MS Exchange account in Email on the N900, I end up seeing this screen, anywhere between 15-30 seconds (in rate cases up to a minute):



I don't have an Inbox, and then it will reappear.

The Inbox has about 970 items in it.

Are you aware of this bug?
I also have an Google Imap account configured with about 1400 messages in the Inbox, but the Inbox displays immediately.

Thanks for your help.
If there is an open bug in the tracker, let me know and I will vote on it.
 
Posts: 2 | Thanked: 3 times | Joined on Dec 2009
#470
Can someone please inform me whom to direct feedback from a large group of individuals that have a n900 and no email access anymore due to the provisioning support..And i do not believe it can be a choice due to personal thoughts by dev team..There should be a statement in the description where it says Mail for Exchange that it does not support the standard features which are part of ther revisions of the same software. Most large global companies require support for provisioned devices. If you do not believe me then ask Microsoft..


And yes I understand the difference between E and N series but dont believe that to be a valid reason..

Last edited by jase; 2009-12-14 at 20:24. Reason: added comment on E series
 

The Following 3 Users Say Thank You to jase For This Useful Post:
Reply

Tags
activesync, certificate, email, exchange, fremantle, ignore tex14, maemo 5, mail for exchange, mfe, n900, provisioning, sync, thanks vitaly!


 
Forum Jump


All times are GMT. The time now is 07:17.