Active Topics

 


Reply
Thread Tools
vitaly_repin's Avatar
Posts: 320 | Thanked: 763 times | Joined on Oct 2009 @ Espoo, FInland
#471
Originally Posted by jase View Post
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.
Good question. Nokia Care?

.And i do not believe it can be a choice due to personal thoughts by dev team.
And it is not. Nothing personal can be involved in such decisions and decisions of such kind are always business decisions. Engineers execute business decisions.
 

The Following User Says Thank You to vitaly_repin For This Useful Post:
Posts: 48 | Thanked: 128 times | Joined on Dec 2009
#472
Originally Posted by IlkkaP View Post
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?
Here is output of the gconftool-2 -R /apps/activesync

setup = false
/apps/activesync/AsBackup:
/apps/activesync/AsBackup/Syslog:
MinLogLevel = 0
/apps/activesync/ActiveSyncAccount1:
file_storage_path =
modest_account_name = Mail for ExchangeID
account_name = Mail for Exchange
storage_account_id = 2
db_path =
modest_account_key = /apps/modest/accounts/Mail@32@for@32@ExchangeID
autodiscover_https_port = 443
use_version =
/apps/activesync/ActiveSyncAccount1/sync:
conflict_policy = 1
calendar = true
contacts = true
tasks = true
mail = true
/apps/activesync/ActiveSyncAccount1/connection:
roaming_sync = 0
port = 443
exchange_server = webmail.hpuss.de
device_id = 356938030317607
secure_connection = true
/apps/activesync/ActiveSyncAccount1/calendar:
past_time = 4
id = 1
first_sync = 1
/apps/activesync/ActiveSyncAccount1/credentials:
username = ilkka.pirskanen@REMOVED.com
encrypted_password = REMOVED
domain =
/apps/activesync/ActiveSyncAccount1/email:
past_time = 3
send_policy = 0
copy_outgoing = true
sig = Lähetetty Nokia N900 -matkatietokoneesta
email_addr = ilkka.pirskanen@REMOVED.com
use_sig = false
notify_enabled = true
/apps/activesync/ActiveSyncAccount1/schedule:
peak_schedule = -1
peak_end_tm = 1140
peak_days = 31
peak_start_tm = 420
off_peak_schedule = -1
/apps/activesync/ActiveSyncAccount1/results:
check_info = 2
autodiscovery = 4
/apps/activesync/ActiveSyncAccount1/tasks:
first_sync = 1
sync_completed = false
/apps/activesync/ActiveSyncAccount1/events:
connection_status = 4
sync_in_progress = false
/apps/activesync/ActiveSyncAccount1/statistics:
last_sync_result = 14
contacts_first_sync_done = true
last_sync_date = 1260807832
contacts_updated = 0
emails_deleted = 0
calendar_updated = 0
full_contacts_done = 465
contacts_deleted = 0
calendar_added = 0
full_calendar_total = 148
full_email_done = 656
emails_added = 0
full_email_total = 128
calendar_deleted = 0
full_sync_action = 0
emails_updated = 0
full_contacts_total = 462
init_progress = 100
full_calendar_done = 250
contacts_added = 0
/apps/activesync/ActiveSyncAccount1/contacts:
store_vcard = false
first_sync = 1
/apps/activesync/AsStatusApplet:
/apps/activesync/AsStatusApplet/Syslog:
MinLogLevel = 0
/apps/activesync/asapplet:
/apps/activesync/asapplet/SysLog:
MinLogLevel = 0
/apps/activesync/AsProvider:
/apps/activesync/AsProvider/Syslog:
MinLogLevel = 0
/apps/activesync/modest:
/apps/activesync/modest/Syslog:
MinLogLevel = 0
/apps/activesync/AsDaemon:
/apps/activesync/AsDaemon/Syslog:
MinLogLevel = 0


Is there something wrong with MinLogLevels here in order to get a log?
 

The Following User Says Thank You to IlkkaP For This Useful Post:
Posts: 51 | Thanked: 8 times | Joined on Nov 2009
#473
Originally Posted by vitaly_repin View Post
Good question. Nokia Care?



And it is not. Nothing personal can be involved in such decisions and decisions of such kind are always business decisions. Engineers execute business decisions.
Why in earth MfE work well in N97 etc, simply this must just temporary problem with N900?
 

The Following User Says Thank You to Random For This Useful Post:
rjzak's Avatar
Posts: 170 | Thanked: 23 times | Joined on Oct 2008 @ Annapolis, MD, USA
#474
Originally Posted by Random View Post
Why in earth MfE work well in N97 etc, simply this must just temporary problem with N900?
Ya know, I wonder how much thought Nokia put into the decision to scrap support for provisioning. Nevermind the babble about how much extra work is needed in the OS to support provisioning- I'm a programmer, I understand.

But, from a consumer's point of view, they see the N900 as a device which is advertised to support Microsoft Exchange 2007. However, when they get the device, whooolla! it doesn't work. I bet they feel cheated. I know I'd be pretty upset. And I bet only in the little fine print is provisioning mentioned (if at all). I bet this little surprise to Random and the others must feel as a real slap in the face. It certainly does to me, and I haven't even purchased one. Besides, who even thinks to check for support for something so inconspicuous and ridiculous as provisioning before buying a device? I mean, Exchange support means it supports Exchange, right? NOPE! Not on the N900, at least.

So, is there anyone who is a programmer who has some free time who'd like to help code up a simple GUI for Maemo that checks Exchange for new messages, regardless of Provisioning or any other crap? Then other features could be added later. I'm started on a Python-based solution, starting with weboutlook and my N810. Any takers? It'll be a hackjob, but for some of us, it'll be far better than what Nokia has offered.
__________________
Professional Genius
N810 WiMax Edition
Nexus One

Last edited by rjzak; 2009-12-14 at 22:54.
 

The Following User Says Thank You to rjzak For This Useful Post:
vitaly_repin's Avatar
Posts: 320 | Thanked: 763 times | Joined on Oct 2009 @ Espoo, FInland
#475
Originally Posted by rjzak View Post
So, is there anyone who is a programmer who has some free time who'd like to help code up a simple GUI for Maemo that checks Exchange for new messages, regardless of Provisioning or any other crap? Then other features could be added later. I'm started on a Python-based solution, starting with weboutlook and my N810. Any takers? It'll be a hackjob, but for some of us, it'll be far better than what Nokia has offered.
If you want to implement something "far better" you need to implement EAS protocol: http://msdn.microsoft.com/en-us/libr...CHG.80%29.aspx

EAS 12.0, 12.1 specs are publicly available and you can start the development right now. You can (technically, not sure about legal consequences) ignore provisioning requests in your code and tell to the server "everything is OK" (something Nokia engineers are not allowed to do).


The current approach if weboutlook module sounds crazy to me:

> weboutlook is a Python module that retrieves full, raw e-mails from Microsoft Outlook Web Access by screen scraping

You have EAS 12.0 and 12.1 specs published. Just take them into use!

The only documentation which community does not have is EAS 2.5 (provided by MS Exchange 2003).
 

The Following 4 Users Say Thank You to vitaly_repin For This Useful Post:
vitaly_repin's Avatar
Posts: 320 | Thanked: 763 times | Joined on Oct 2009 @ Espoo, FInland
#476
Originally Posted by Random View Post
Why in earth MfE work well in N97 etc, simply this must just temporary problem with N900?
I see no relation between S60 and Maemo in this respect. Maemo MfE and S60 MfE are different MfE implementations.
 
Posts: 221 | Thanked: 51 times | Joined on Nov 2009 @ Germany
#477
Hi Vitaly - one more try; can you confirm that emails will be send out with mfe on manual sync with the next sw update?
 
vitaly_repin's Avatar
Posts: 320 | Thanked: 763 times | Joined on Oct 2009 @ Espoo, FInland
#478
Originally Posted by HugoSon View Post
Hi Vitaly - one more try; can you confirm that emails will be send out with mfe on manual sync with the next sw update?
Sorry, missed the problem description. Manual update works now. What issues do you have?
 

The Following User Says Thank You to vitaly_repin For This Useful Post:
Posts: 221 | Thanked: 51 times | Joined on Nov 2009 @ Germany
#479
Originally Posted by HugoSon View Post
MfE does not send out my eMails
I hope this is already known (somewhere) - ....
I sync MfE manually – and my send eMails should be “synct” (send out) on “next synchronization” – but they don’t. They remain in the outgoing folder forever (found 4 eMails I wanted to send yesterday in this folder just this morning). Once you change the MfE setting to “send immediately” – no problem. The eMail goes out. Change back to “send out on next synchronization” they get stucked in the outgoing folder and are never send out (status on the eMail says “on hold”.
...here you go Vitaly. I hope this is fixed....
 
vitaly_repin's Avatar
Posts: 320 | Thanked: 763 times | Joined on Oct 2009 @ Espoo, FInland
#480
Originally Posted by HugoSon
I sync MfE manually – and my send eMails should be “synct” (send out) on “next synchronization” – but they don’t.
Do you sync it manually or periodically (using automatic scheduler)? "Send on next sync" means the following:

1) Wait for the next sync session (any session - either initiated by the user or by scheduler according to the MfE settings)
2) During this sync send outgoing mails which are in outbox

They remain in the outgoing folder forever (found 4 eMails I wanted to send yesterday in this folder just this morning).
Hm. What happens if you press "Send and Receive" from e-mail client? Any error message? Could you initiate send/receive being in the outgoing folder? You will be able to see the statuses of the message sending while sending attempt is performed. What are the statuses?
 

The Following User Says Thank You to vitaly_repin 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 09:07.