Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    N800 turns on by itself

    Reply
    Page 1 of 2 | 1   2   | Next
    zlatoust | # 1 | 2007-01-15, 22:41 | Report

    The subject says it all, I am observing the same behavior from my N800 as reported earlier for some 770 units: I shut it down in the evening and next morning find it turned on and connected to my AP. Pristine OS 2.2006.51-6, no additional software installed, no alarms set up. Anyone else?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    JayMontano | # 2 | 2007-01-16, 01:03 | Report

    Yes. I have noticed a couple of random restarts, but I haven't been able to replicate them to figure out what's causing the 'problem'.

    Other than that, (and frustration with setting up email) I'm pretty happy with it.

    (Hey Reggie, Awesome N800 view review btw! I'm posting this here as I'm still trying to find my way around your forums! It was great meeting you, you've got a lot of insight into the who internet tablet thing )

    Edit | Forward | Quote | Quick Reply | Thanks

     
    aflegg | # 3 | 2007-01-16, 10:59 | Report

    Originally Posted by zlatoust View Post
    I am observing the same behavior from my N800 as reported earlier for some 770 units: I shut it down in the evening and next morning find it turned on and connected to my AP. Pristine OS 2.2006.51-6, no additional software installed, no alarms set up.
    If this is all pristine, open a bug on http://bugs.maemo.org/ with the information requested at http://maemo.org/maemowiki/ReportingRebootIssues

    Cheers,

    Andrew

    Edit | Forward | Quote | Quick Reply | Thanks

     
    zlatoust | # 4 | 2007-01-17, 03:04 | Report

    Well, obviously I can't do this since I no longer have a device, returned it to TigerDirect.com today. Anyway, it would GREATLY simplify troubleshooting if we'd have some standard procedure to rapidly obtain complete device's logs and debug info in some standard user-friendly procedure not involving hacking. Perhaps, a simple http server on the device that a user can connect to from his/her PC? I know it is not ideal (you may not have the ability to connect at all). Maybe a file dump to MMC? I think Nokia developers would benefit from an ordinary non-hacking users being able to provide such info upon request. And from hackers short on time to hack

    Edit | Forward | Quote | Quick Reply | Thanks

     
    NokNok770 | # 5 | 2007-01-17, 08:02 | Report

    Well, looks like some of the same bugs that use to be on the 770 is also on the n800

    Edit | Forward | Quote | Quick Reply | Thanks

     
    N770-Freak | # 6 | 2007-01-17, 15:18 | Report

    Originally Posted by
    The subject says it all, I am observing the same behavior from my N800 as reported earlier for some 770 units: I shut it down in the evening and next morning find it turned on and connected to my AP. Pristine OS 2.2006.51-6, no additional software installed, no alarms set up. Anyone else?
    I had the same problem with my 770 (several times).
    How did you check that no alarm is set? with the clock app?

    I solved this problem by using the console alarm tool "retutime"!
    Code:
    /mnt/initfs/usr/bin/retutime
    ...this tool showed me that there was an activated alarm although the clock app didn't show a alarm!

    There are 2 possibilities to solve this (OS2006):
    1. use retutime tool to deactivate this alarm
    2. add a new alarm in clock tool and delete it afterwards

    HTH N770-Freak

    Edit | Forward | Quote | Quick Reply | Thanks

     
    DryLand404 | # 7 | 2007-02-11, 14:59 | Report

    I'm not sure how to interpret this...

    Nokia-N800-51:/# find -name "retutime" -print
    ./mnt/initfs/usr/bin/retutime
    Nokia-N800-51:/# cd mnt
    Nokia-N800-51:/mnt# cd initfs
    Nokia-N800-51:/mnt/initfs# cd usr
    Nokia-N800-51:/mnt/initfs/usr# cd bin
    Nokia-N800-51:/mnt/initfs/usr/bin# cd retutime
    -sh: cd: can't cd to retutime
    Nokia-N800-51:/mnt/initfs/usr/bin# retutime
    -sh: retutime: not found

    Does this indicate there is no scheduled items?

    some ducumentation is here.
    http://maemo.org/platform/docs/api-b...tutime_8c.html

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by DryLand404; 2007-02-11 at 15:22.

     
    N770-Freak | # 8 | 2007-02-11, 15:39 | Report

    Originally Posted by DryLand404 View Post
    I'm not sure how to interpret this...

    Nokia-N800-51:/# find -name "retutime" -print
    ./mnt/initfs/usr/bin/retutime
    Nokia-N800-51:/# cd mnt
    Nokia-N800-51:/mnt# cd initfs
    Nokia-N800-51:/mnt/initfs# cd usr
    Nokia-N800-51:/mnt/initfs/usr# cd bin
    Nokia-N800-51:/mnt/initfs/usr/bin# cd retutime
    -sh: cd: can't cd to retutime
    Nokia-N800-51:/mnt/initfs/usr/bin# retutime
    -sh: retutime: not found

    Does this indicate there is no scheduled items?

    some ducumentation is here.
    http://maemo.org/platform/docs/api-b...tutime_8c.html
    You are not executing the command! retutime a is binary not a directory.
    And retutime is not listed in the standard bin directories... so you can't execute it with just typing "retutime".
    Like I posted before, execute:
    Code:
    /mnt/initfs/usr/bin/retutime
    OR change root to /mnt/initfs and execute "retutime" OR change directory to /mnt/initfs/usr/bin and execute "./retutime"

    Then read the output of retutime and append the needed parameters!

    HTH N770-Freak

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to N770-Freak For This Useful Post:

     
    DryLand404 | # 9 | 2007-02-11, 16:04 | Report

    okay, that helps.
    Nokia-N800-51:~# /mnt/initfs/usr/bin/retutime
    retutime, Version 1.0.8
    Copyright (C) 2004-2005 Nokia Corporation
    All rights reserved.

    Usage:
    -T, --set-time Set date string (in UTC)
    (Y-m-d/H:M:00 -- ex. 2004-11-12/13:16:11)
    -t, --get-time Get date string
    (Y-m-d/H:M:S -- ex. 2004-11-12/13:16:45)
    -A, --set-alarm Set alarm string (In UTC; seconds don't count
    and date must be within 24 hours from current time)
    (Y-m-d/H:M:00 -- ex. 2004-11-12/13:16:00)
    -a, --get-alarm Get alarm time
    -S, --clear-alarm-status Acknowledge the alarm
    -s, --get-alarm-status Get alarm expiration status
    -R, --clear-reset-status Acknowledge the reset
    -r, --get-reset-status Get reset status
    -C, --set-calibration Set calibration data
    -c, --get-calibration Get calibration data
    -I, --rtc-from-system Set RTC to match system time
    -i, --system-from-rtc Set system time to match RTC
    -h, --help Show usage

    Report bugs to Bugzilla.
    Nokia-N800-51:~# /mnt/initfs/usr/bin/retutime -a
    Alarm off

    This either indicates there are no alarms set or I have to enumerate all possible times using -a to see if an alarm is set for that time.
    I set multiple alarms and retested.
    Only the first alarm seemed to be shown and in GMT.

    Nokia-N800-51:~# /mnt/initfs/usr/bin/retutime -a
    2007-02-11/17:00:00Nokia-N800-51:~#

    Thanks, It appears the "alarms set but don't appear in the clock applet" is not the source of my intermittent reboot issue.
    Do you know how to enable or bring up system logs?

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by DryLand404; 2007-02-11 at 16:10.

     
    Jay | # 10 | 2007-03-28, 14:38 | Report

    I have updated my n800 to the lastest firmware version and started experiencing the 'midnight boot' problem. I ran the 'retutime' and there is no hidden alarm.
    Anything else I can try?
    Thanks!

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Page 1 of 2 | 1   2   | Next
vBulletin® Version 3.8.8
Normal Logout