Nokia c3-01 calibration!

I have a big problem with mi device (Nokia c3-01)! I make a software update to the last 07.32 and and now my touch is doesn't work good! When i try to go in the menu it enters in search of wireless! I think if I could get in the menu to the calibration settings it will work again good! But the question is how to get there what i supposed to do?
Solved!
Go to Solution.

Hi,
I have the same problem - caused by using Nokia's Software update. I've reported it here: http://discussions.nokia.com/t5/Cseries/C3-01-5-Software-Update-7-32-renders-the-touchscreen-unusabl...
Have yet to take it to a Nokia care point, I was hoping they might release a fix via Software Update (where the problem was caused), but doesn't seem so.

Similar Messages

Screen calibration nokia n8-00

how do i calibrate the screen of my nokia n8-00?i've tried menu<settings<phone<touch input but screen calibracion does not apear.how should i do it?somebody can help me please?

Hi lqdtd,
Thanks for your post and welcome to the Nokia discussion forums.
Have you had this problem with touch screen ever since you had your phone?
What you could try is to do a soft reset on the phone by typing *#7870#. If the phone asks you for security code this is defaulted at 12345. This will not erase any of your data.
Give this a try and if the problem exists then I would visit a Nokia care point. Where are you based?
Regards
Raoul_Duke
If you find this post helpful, a click upon the white star at bottom would always be appreciated.
If it also solves your problem, clicking ACCEPT AS SOLUTION below it will benefit other users!

Calibrating the magnetic Compass in the Nokia 5230...

I have read somewhere that there is a proceeding to calibrate the magnetic compass on the 5230, and my questions are:
1) The 5230 has a magnetic compass built in it? Where it is documented?
2) It is used in navigation using Ovi Maps? How and when?
3) How I can calibrate it, making the 360 turn, as suggested elsewhere? On what screen/menu is the function selected?
Thanks
Pascal
Solved!
Go to Solution.

Dear,
FIrst of all update your nokia and ovi maps on Nokia Suite
To know about compass keep your cell in open i.e. under open sky with no roofing or building obstacles
Press menu
Icon with "Location" will appear or otherwise go to applications there you find "Location"
Press Location
Go to "GPS Data"
You will find compass on Navigation icon
Regards

[SOLVED] Gnome 3.8: Unable to use Nokia N9 as a Bluetooth modem

Hi,
I'm unable to use my Nokia Any ideas on how to fix this?
Here are some log files:
Bluetooth startup from everything.log:
/> bluetoothd[382]: Bluetooth daemon 4.101
bluetoothd[382]: Starting SDP server
bluetoothd[382]: DIS cannot start: GATT is disabled
bluetoothd[382]: Failed to init deviceinfo plugin
bluetoothd[382]: Failed to init gatt_example plugin
bluetoothd[382]: Bluetooth Management interface initialized
bluetoothd[382]: bluetoothd[382]: Bluetooth Management interface initialized
bluetoothd[382]: bluetoothd[382]: Unknown command complete for opcode 1J
bluetoothd[382]: Unknown command complete for opcode 19
bluetoothd[382]: bluetoothd[382]: Adapter /org/bluez/382/hci0 has been enabled
bluetoothd[382]: Adapter /org/bluez/382/hci0 has been enabled
entries from everything.log:
/etc/gdm/Xsession[612]: Ikkunointiohjelman varoitus:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800003 (Uuden Blue)
/etc/gdm/Xsession[612]: Ikkunointiohjelman varoitus:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
bluetoothd[382]: bluetoothd[382]: Discovery session 0x7f5d47491d10 with :1.58 activated
bluetoothd[382]: Discovery session 0x7f5d47491d10 with :1.58 activated
bluetoothd[382]: bluetoothd[382]: Stopping discovery
bluetoothd[382]: Stopping discovery
kernel: [ 1179.820342] usb 2-1: reset high-speed USB device number 2 using ehci-pci
dbus-daemon[396]: dbus[396]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.58" (uid=1000 pid=1082 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.4" (uid=0 pid=382 comm="/usr/lib/bluetooth/bluetoothd -n ")
bluetoothd[382]: bluetoothd[382]: input-headset driver probe failed for device 40:98:4E:65:A1:00
bluetoothd[382]: input-headset driver probe failed for device 40:98:4E:65:A1:00
pulseaudio[678]: [pulseaudio] bluetooth-util.c: org.bluez.AudioSource.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.AudioSource" doesn't exist
pulseaudio[678]: [pulseaudio] bluetooth-util.c: org.bluez.HandsfreeGateway.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.HandsfreeGateway" doesn't exist
pulseaudio[678]: [pulseaudio] bluetooth-util.c: org.bluez.HandsfreeGateway.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.HandsfreeGateway" doesn't exist
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 SyncMLClient
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 DialupNetworking
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 OBEXObjectPush
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 OBEXFileTransfer
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 AudioSource
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 A/V_RemoteControlTarget
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 A/V_RemoteControl
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 Headset_-_AG
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 HandsfreeAudioGateway
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 Phonebook_Access_-_PSE
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 SyncMLClient
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 DialupNetworking
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 OBEXObjectPush
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 OBEXFileTransfer
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 AudioSource
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 A/V_RemoteControlTarget
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 A/V_RemoteControl
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 Headset_-_AG
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 HandsfreeAudioGateway
/etc/gdm/Xsession[612]: ** Message: has_config_widget 40:98:4E:65:A1:00 Phonebook_Access_-_PSE
/etc/gdm/Xsession[612]: ** Message: Default Bluetooth adapter is powered
/etc/gdm/Xsession[612]: ** Message: dun_start: starting DUN device discovery...
/etc/gdm/Xsession[612]: ** Message: Tutkitaan puhelimen asetuksia…
/etc/gdm/Xsession[612]: ** Message: dun_start: calling Connect...
/etc/gdm/Xsession[612]: ** Message: dun_start: waiting for Connect success...
/etc/gdm/Xsession[612]: ** Message: dun_connect_cb: processing Connect reply
/etc/gdm/Xsession[612]: ** Message: dun_connect_cb: new rfcomm interface '/dev/rfcomm0'
/etc/gdm/Xsession[612]: ** Message: dun_connect_cb: finished
upowerd[506]: (upowerd:506): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/pci0000:00/0000:00:13.1/usb6/6-3/6-3:1.0/bluetooth/hci0/hci0:21/rfcomm0
kernel: [ 1212.925984] Bluetooth: TIOCGSERIAL is not supported
kernel: [ 1214.790844] Bluetooth: TIOCGSERIAL is not supported
kernel: [ 1214.791357] Bluetooth: TIOCGSERIAL is not supported
ModemManager[457]: <info> Creating modem with plugin 'Nokia' and '1' ports
kernel: [ 1215.816882] Bluetooth: TIOCGSERIAL is not supported
ModemManager[457]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:13.1/usb6/6-3' successfully created
kernel: [ 1215.820679] Bluetooth: TIOCGSERIAL is not supported
ModemManager[457]: <info> Modem: state changed (unknown -> disabled)
kernel: [ 1216.873341] Bluetooth: TIOCGSERIAL is not supported
/etc/gdm/Xsession[612]: ** Message: modem_object_added: (/org/freedesktop/ModemManager1/Modem/0) modem found
/etc/gdm/Xsession[612]: ** Message: start_wizard: (/org/freedesktop/ModemManager1/Modem/0) starting the mobile wizard
NetworkManager[387]: <info> ignoring modem 'rfcomm0' (no associated Bluetooth device)
/etc/gdm/Xsession[612]: ** Message: wizard_done_cb: mobile wizard done
/etc/gdm/Xsession[612]: ** Message: wizard_done_cb: adding new setting
/etc/gdm/Xsession[612]: ** Message: wizard_done_cb: waiting for add connection result...
NetworkManager[387]: <info> BT device Nokia N9 (40:98:4E:65:A1:00) added (DUN)
NetworkManager[387]: <info> (40:98:4E:65:A1:00): new Bluetooth device (driver: 'bluez' ifindex: 0)
NetworkManager[387]: <info> (40:98:4E:65:A1:00): exported as /org/freedesktop/NetworkManager/Devices/1
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
NetworkManager[387]: <info> (40:98:4E:65:A1:00): deactivating device (reason 'managed') [2]
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
/etc/gdm/Xsession[612]: ** Message: Puhelimesi on nyt valmis käyttöön.
upowerd[506]: (upowerd:506): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/virtual/tty/rfcomm0
dbus-daemon[396]: dbus[396]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.4" (uid=0 pid=382 comm="/usr/lib/bluetooth/bluetoothd -n ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.59" (uid=1000 pid=1082 comm="bluetooth-wizard ")
NetworkManager[387]: <info> (eth0): device state change: activated -> disconnected (reason 'user-requested') [100 30 39]
NetworkManager[387]: <info> (eth0): deactivating device (reason 'user-requested') [39]
avahi-daemon[392]: Withdrawing address record for 192.168.0.222 on eth0.
avahi-daemon[392]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.222.
avahi-daemon[392]: Interface eth0.IPv4 no longer relevant for mDNS.
dbus-daemon[396]: dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
systemd[1]: Starting Network Manager Script Dispatcher Service...
dbus-daemon[396]: dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
systemd[1]: Started Network Manager Script Dispatcher Service.
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) starting connection 'Dna connection'
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) started...
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) starting...
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) complete.
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00 40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN.
NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear.
upowerd[506]: (upowerd:506): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/pci0000:00/0000:00:13.1/usb6/6-3/6-3:1.0/bluetooth/hci0/hci0:21/rfcomm0
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: config -> failed (reason 'modem-not-found') [50 120 43]
NetworkManager[387]: <warn> Activation (40:98:4E:65:A1:00) failed for connection 'Dna connection'
NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: failed -> disconnected (reason 'none') [120 30 0]
NetworkManager[387]: <info> (40:98:4E:65:A1:00): deactivating device (reason 'none') [0]
upowerd[506]: (upowerd:506): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/virtual/tty/rfcomm0
dbus-daemon[396]: dbus[396]: [system] Rejected send message, 7 matched rules; type="method_return", sender=":1.4" (uid=0 pid=382 comm="/usr/lib/bluetooth/bluetoothd -n ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=387 comm="/usr/bin/NetworkManager --no-daemon ")
/> systemd[1]: Mounting Arbitrary Executable File Formats File System...
systemd-sysctl[132]: Duplicate assignment of kernel/sysrq in file '/usr/lib/sysctl.d/50-default.conf', ignoring.
systemd[1]: Started Apply Kernel Variables.
systemd[1]: Started udev Coldplug all Devices.
systemd-modules-load[138]: Inserted module 'fuse'
systemd[1]: Started Create static device nodes in /dev.
systemd[1]: Starting udev Kernel Device Manager...
systemd[1]: Started udev Kernel Device Manager.
systemd[1]: Mounted Arbitrary Executable File Formats File System.
systemd[1]: Mounted Debug File System.
0.000000] Initializing cgroup subsys cpuset
0.000000] Initializing cgroup subsys cpu
0.000000] Linux version 3.9.5-1-ARCH (tobias@T-POWA-LX) (gcc version 4.8.1 (GCC) ) #1 SMP PREEMPT Sat Jun 8 09:22:45 CEST 2013
0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=90b0c2df-9b19-4c19-91ce-5479b086da4d ro quiet
0.000000] e820: BIOS-provided physical RAM map:
0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff] usable
0.000000] BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000cfdeffff] usable
0.000000] BIOS-e820: [mem 0x00000000cfdf0000-0x00000000cfdf2fff] ACPI NVS
syslog-ng[390]: syslog-ng starting up; version='3.4.1'
systemd[1]: Mounted Huge Pages File System.
0.000000] BIOS-e820: [mem 0x00000000cfdf3000-0x00000000cfdfffff] ACPI data
0.000000] BIOS-e820: [mem 0x00000000cfe00000-0x00000000cfefffff] reserved
0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000032fffffff] usable
0.000000] NX (Execute Disable) protection: active
0.000000] SMBIOS 2.4 present.
0.000000] DMI: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P/GA-MA790XT-UD4P, BIOS F8g 07/12/2010
0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
0.000000] No AGP bridge found
0.000000] e820: last_pfn = 0x330000 max_arch_pfn = 0x400000000
0.000000] MTRR default type: uncachable
0.000000] MTRR fixed ranges enabled:
0.000000] 00000-9FFFF write-back
0.000000] A0000-BFFFF uncachable
0.000000] C0000-C7FFF write-protect
0.000000] C8000-FFFFF uncachable
0.000000] MTRR variable ranges enabled:
0.000000] 0 base 000000000000 mask FFFF80000000 write-back
0.000000] 1 base 000080000000 mask FFFFC0000000 write-back
0.000000] 2 base 0000C0000000 mask FFFFF0000000 write-back
0.000000] 3 base 0000CFE00000 mask FFFFFFE00000 uncachable
0.000000] 4 base 000100000000 mask FFFF00000000 write-back
0.000000] 5 base 000200000000 mask FFFF00000000 write-back
0.000000] 6 base 000300000000 mask FFFFE0000000 write-back
0.000000] 7 base 000320000000 mask FFFFF0000000 write-back
0.000000] TOM2: 0000000330000000 aka 13056M
0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
0.000000] e820: update [mem 0xcfe00000-0xffffffff] usable ==> reserved
0.000000] e820: last_pfn = 0xcfdf0 max_arch_pfn = 0x400000000
0.000000] found SMP MP-table at [mem 0x000f5440-0x000f544f] mapped at [ffff8800000f5440]
0.000000] Scanning 1 areas for low memory corruption
0.000000] Base memory trampoline at [ffff880000099000] 99000 size 24576
0.000000] Using GB pages for direct mapping
0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
0.000000] [mem 0x00000000-0x000fffff] page 4k
0.000000] BRK [0x01b30000, 0x01b30fff] PGTABLE
0.000000] BRK [0x01b31000, 0x01b31fff] PGTABLE
0.000000] BRK [0x01b32000, 0x01b32fff] PGTABLE
0.000000] init_memory_mapping: [mem 0x32fe00000-0x32fffffff]
0.000000] [mem 0x32fe00000-0x32fffffff] page 2M
0.000000] BRK [0x01b33000, 0x01b33fff] PGTABLE
0.000000] init_memory_mapping: [mem 0x32c000000-0x32fdfffff]
0.000000] [mem 0x32c000000-0x32fdfffff] page 2M
0.000000] init_memory_mapping: [mem 0x300000000-0x32bffffff]
0.000000] [mem 0x300000000-0x32bffffff] page 2M
0.000000] init_memory_mapping: [mem 0x00100000-0xcfdeffff]
0.000000] [mem 0x00100000-0x001fffff] page 4k
0.000000] [mem 0x00200000-0x3fffffff] page 2M
0.000000] [mem 0x40000000-0xbfffffff] page 1G
0.000000] [mem 0xc0000000-0xcfbfffff] page 2M
0.000000] [mem 0xcfc00000-0xcfdeffff] page 4k
0.000000] init_memory_mapping: [mem 0x100000000-0x2ffffffff]
0.000000] [mem 0x100000000-0x2ffffffff] page 1G
0.000000] RAMDISK: [mem 0x378a4000-0x37c49fff]
0.000000] ACPI: RSDP 00000000000f6e70 00014 (v00 GBT )
0.000000] ACPI: RSDT 00000000cfdf3000 00038 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
0.000000] ACPI: FACP 00000000cfdf3040 00074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
0.000000] ACPI: DSDT 00000000cfdf30c0 0725F (v01 GBT GBTUACPI 00001000 MSFT 03000000)
0.000000] ACPI: FACS 00000000cfdf0000 00040
0.000000] ACPI: SSDT 00000000cfdfa400 008F5 (v01 PTLTD POWERNOW 00000001 LTP 00000001)
0.000000] ACPI: HPET 00000000cfdfad00 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
0.000000] ACPI: MCFG 00000000cfdfad40 0003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
0.000000] ACPI: APIC 00000000cfdfa340 000BC (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
0.000000] ACPI: Local APIC address 0xfee00000
0.000000] Scanning NUMA topology in Northbridge 24
0.000000] No NUMA configuration found
0.000000] Faking a node at [mem 0x0000000000000000-0x000000032fffffff]
0.000000] Initmem setup node 0 [mem 0x00000000-0x32fffffff]
0.000000] NODE_DATA [mem 0x32fff9000-0x32fffdfff]
0.000000] [ffffea0000000000-ffffea000cbfffff] PMD -> [ffff880323600000-ffff88032f5fffff] on node 0
0.000000] Zone ranges:
0.000000] DMA [mem 0x00001000-0x00ffffff]
0.000000] DMA32 [mem 0x01000000-0xffffffff]
0.000000] Normal [mem 0x100000000-0x32fffffff]
0.000000] Movable zone start for each node
0.000000] Early memory node ranges
0.000000] node 0: [mem 0x00001000-0x0009efff]
0.000000] node 0: [mem 0x00100000-0xcfdeffff]
0.000000] node 0: [mem 0x100000000-0x32fffffff]
0.000000] On node 0 totalpages: 3145102
0.000000] DMA zone: 64 pages used for memmap
0.000000] DMA zone: 21 pages reserved
0.000000] DMA zone: 3998 pages, LIFO batch:0
0.000000] DMA32 zone: 13240 pages used for memmap
0.000000] DMA32 zone: 847344 pages, LIFO batch:31
0.000000] Normal zone: 35840 pages used for memmap
0.000000] Normal zone: 2293760 pages, LIFO batch:31
0.000000] ACPI: PM-Timer IO Port: 0x4008
0.000000] ACPI: Local APIC address 0xfee00000
0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled)
0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
0.000000] IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
0.000000] ACPI: IRQ0 used by override.
0.000000] ACPI: IRQ2 used by override.
0.000000] ACPI: IRQ9 used by override.
0.000000] Using ACPI (MADT) for SMP configuration information
0.000000] ACPI: HPET id: 0x10b9a201 base: 0xfed00000
0.000000] smpboot: Allowing 8 CPUs, 5 hotplug CPUs
0.000000] nr_irqs_gsi: 40
0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
0.000000] PM: Registered nosave memory: 00000000cfdf0000 - 00000000cfdf3000
0.000000] PM: Registered nosave memory: 00000000cfdf3000 - 00000000cfe00000
0.000000] PM: Registered nosave memory: 00000000cfe00000 - 00000000cff00000
0.000000] PM: Registered nosave memory: 00000000cff00000 - 00000000e0000000
0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000
0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fec00000
0.000000] PM: Registered nosave memory: 00000000fec00000 - 0000000100000000
0.000000] e820: [mem 0xcff00000-0xdfffffff] available for PCI devices
0.000000] Booting paravirtualized kernel on bare hardware
0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1
0.000000] PERCPU: Embedded 28 pages/cpu @ffff88032fc00000 s85824 r8192 d20672 u262144
0.000000] pcpu-alloc: s85824 r8192 d20672 u262144 alloc=1*2097152
0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3095937
0.000000] Policy zone: Normal
0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=90b0c2df-9b19-4c19-91ce-5479b086da4d ro quiet
0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
0.000000] __ex_table already sorted, skipping sort
0.000000] Checking aperture...
0.000000] No AGP bridge found
0.000000] Node 0: aperture @ c4000000 size 32 MB
0.000000] Aperture pointing to e820 RAM. Ignoring.
0.000000] Your BIOS doesn't leave a aperture memory hole
0.000000] Please enable the IOMMU option in the BIOS setup
0.000000] This costs you 64 MB of RAM
0.000000] Mapping aperture over 65536 KB of RAM @ c4000000
0.000000] PM: Registered nosave memory: 00000000c4000000 - 00000000c8000000
0.000000] Memory: 12235744k/13369344k available (4984k kernel code, 788936k absent, 344664k reserved, 3966k data, 1092k init)
0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
0.000000] Preemptible hierarchical RCU implementation.
0.000000] RCU dyntick-idle grace-period acceleration is enabled.
0.000000] Dump stacks of tasks blocking RCU-preempt GP.
0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=8.
0.000000] NR_IRQS:4352 nr_irqs:744 16
0.000000] spurious 8259A interrupt: IRQ7.
0.000000] Console: colour dummy device 80x25
0.000000] console [tty0] enabled
0.000000] allocated 50331648 bytes of page_cgroup
0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
0.000000] hpet clockevent registered
0.003333] tsc: Fast TSC calibration using PIT
0.006666] tsc: Detected 2812.672 MHz processor
0.000003] Calibrating delay loop (skipped), value calculated using timer frequency.. 5627.73 BogoMIPS (lpj=9375573)
0.000006] pid_max: default: 32768 minimum: 301
0.000035] Security Framework initialized
0.000041] AppArmor: AppArmor disabled by boot time parameter
0.000892] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
0.005505] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
0.007582] Mount-cache hash table entries: 256
0.007774] Initializing cgroup subsys cpuacct
0.007776] Initializing cgroup subsys memory
0.007786] Initializing cgroup subsys devices
0.007787] Initializing cgroup subsys freezer
0.007789] Initializing cgroup subsys net_cls
0.007790] Initializing cgroup subsys blkio
0.007813] tseg: 00cff00000
0.007816] CPU: Physical Processor ID: 0
0.007817] CPU: Processor Core ID: 0
0.007818] mce: CPU supports 6 MCE banks
0.007823] LVT offset 0 assigned for vector 0xf9
0.007828] Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8
0.007828] Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64
0.007828] tlb_flushall_shift: 4
0.007908] Freeing SMP alternatives: 20k freed
0.008523] ACPI: Core revision 20130117
0.010353] ACPI: All ACPI Tables successfully acquired
0.042664] ftrace: allocating 19546 entries in 77 pages
0.399338] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
0.432338] smpboot: CPU0: AMD Phenom(tm) II X3 720 Processor (fam: 10, model: 04, stepping: 02)
0.535738] Performance Events: AMD PMU driver.
0.535742] ... version: 0
0.535743] ... bit width: 48
0.535744] ... generic registers: 4
0.535745] ... value mask: 0000ffffffffffff
0.535746] ... max period: 00007fffffffffff
0.535746] ... fixed-purpose events: 0
0.535747] ... event mask: 000000000000000f
0.565797] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
0.572465] smpboot: Booting Node 0, Processors #1 #2
0.602275] Brought up 3 CPUs
0.602279] smpboot: Total of 3 processors activated (16882.19 BogoMIPS)
0.605948] devtmpfs: initialized
0.608503] PM: Registering ACPI NVS region [mem 0xcfdf0000-0xcfdf2fff] (12288 bytes)
0.609303] RTC time: 21:44:15, date: 06/16/13
0.609349] NET: Registered protocol family 16
0.609448] node 0 link 0: io port [b000, ffff]
0.609451] TOM: 00000000d0000000 aka 3328M
0.609453] Fam 10h mmconf [mem 0xe0000000-0xe00fffff]
0.609455] node 0 link 0: mmio [a0000, bffff]
0.609457] node 0 link 0: mmio [d0000000, dfffffff]
0.609459] node 0 link 0: mmio [f0000000, fe02ffff]
0.609460] node 0 link 0: mmio [e0000000, e04fffff] ==> [e0100000, e04fffff]
0.609462] TOM2: 0000000330000000 aka 13056M
0.609464] bus: [bus 00-04] on node 0 link 0
0.609466] bus: 00 [io 0x0000-0xffff]
0.609467] bus: 00 [mem 0x000a0000-0x000bffff]
0.609468] bus: 00 [mem 0xd0000000-0xdfffffff]
0.609469] bus: 00 [mem 0xe0500000-0xffffffff]
0.609470] bus: 00 [mem 0xe0100000-0xe04fffff]
0.609471] bus: 00 [mem 0x330000000-0xfcffffffff]
0.609498] ACPI: bus type PCI registered
0.609552] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
0.609554] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
0.617921] PCI: Using configuration type 1 for base access
0.618123] mtrr: your CPUs had inconsistent variable MTRR settings
0.618124] mtrr: probably your BIOS does not setup all CPUs.
0.618125] mtrr: corrected configuration.
0.618516] bio: create slab <bio-0> at 0
0.618576] ACPI: Added _OSI(Module Device)
0.618577] ACPI: Added _OSI(Processor Device)
0.618578] ACPI: Added _OSI(3.0 _SCP Extensions)
0.618580] ACPI: Added _OSI(Processor Aggregator Device)
0.619096] ACPI: EC: Look up EC in DSDT
0.623380] ACPI: Interpreter enabled
0.623389] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130117/hwxface-568)
0.623394] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130117/hwxface-568)
0.623403] ACPI: (supports S0 S3 S4 S5)
0.623405] ACPI: Using IOAPIC for interrupt routing
0.623473] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
0.637118] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
0.637201] PCI host bridge to bus 0000:00
0.637204] pci_bus 0000:00: root bus resource [bus 00-ff]
0.637207] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
0.637209] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
0.637210] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
0.637212] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
0.637214] pci_bus 0000:00: root bus resource [mem 0xd0000000-0xfebfffff]
0.637223] pci 0000:00:00.0: [1002:5958] type 00 class 0x060000
0.637234] pci 0000:00:00.0: reg 1c: [mem 0xe0000000-0xffffffff 64bit]
0.637312] pci 0000:00:02.0: [1002:5978] type 01 class 0x060400
0.637342] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
0.637366] pci 0000:00:02.0: System wakeup disabled by ACPI
0.637399] pci 0000:00:04.0: [1002:597a] type 01 class 0x060400
0.637428] pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
0.637453] pci 0000:00:04.0: System wakeup disabled by ACPI
0.637485] pci 0000:00:0a.0: [1002:597f] type 01 class 0x060400
0.637514] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
0.637542] pci 0000:00:0a.0: System wakeup disabled by ACPI
0.637581] pci 0000:00:11.0: [1002:4390] type 00 class 0x01018f
0.637600] pci 0000:00:11.0: reg 10: [io 0xff00-0xff07]
0.637609] pci 0000:00:11.0: reg 14: [io 0xfe00-0xfe03]
0.637618] pci 0000:00:11.0: reg 18: [io 0xfd00-0xfd07]
0.637627] pci 0000:00:11.0: reg 1c: [io 0xfc00-0xfc03]
0.637636] pci 0000:00:11.0: reg 20: [io 0xfb00-0xfb0f]
0.637645] pci 0000:00:11.0: reg 24: [mem 0xfe02f000-0xfe02f3ff]
0.637664] pci 0000:00:11.0: set SATA to AHCI mode
0.637736] pci 0000:00:12.0: [1002:4397] type 00 class 0x0c0310
0.637749] pci 0000:00:12.0: reg 10: [mem 0xfe02e000-0xfe02efff]
0.637811] pci 0000:00:12.0: System wakeup disabled by ACPI
0.637840] pci 0000:00:12.1: [1002:4398] type 00 class 0x0c0310
0.637853] pci 0000:00:12.1: reg 10: [mem 0xfe02d000-0xfe02dfff]
0.637916] pci 0000:00:12.1: System wakeup disabled by ACPI
0.637948] pci 0000:00:12.2: [1002:4396] type 00 class 0x0c0320
0.637966] pci 0000:00:12.2: reg 10: [mem 0xfe02c000-0xfe02c0ff]
0.638046] pci 0000:00:12.2: supports D1 D2
0.638047] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
0.638065] pci 0000:00:12.2: System wakeup disabled by ACPI
0.638099] pci 0000:00:13.0: [1002:4397] type 00 class 0x0c0310
0.638112] pci 0000:00:13.0: reg 10: [mem 0xfe02b000-0xfe02bfff]
0.638178] pci 0000:00:13.0: System wakeup disabled by ACPI
0.638205] pci 0000:00:13.1: [1002:4398] type 00 class 0x0c0310
0.638217] pci 0000:00:13.1: reg 10: [mem 0xfe02a000-0xfe02afff]
0.638282] pci 0000:00:13.1: System wakeup disabled by ACPI
0.638316] pci 0000:00:13.2: [1002:4396] type 00 class 0x0c0320
0.638334] pci 0000:00:13.2: reg 10: [mem 0xfe029000-0xfe0290ff]
0.638414] pci 0000:00:13.2: supports D1 D2
0.638415] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
0.638436] pci 0000:00:13.2: System wakeup disabled by ACPI
0.638472] pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500
0.638587] pci 0000:00:14.1: [1002:439c] type 00 class 0x01018a
0.638602] pci 0000:00:14.1: reg 10: [io 0x0000-0x0007]
0.638611] pci 0000:00:14.1: reg 14: [io 0x0000-0x0003]
0.638620] pci 0000:00:14.1: reg 18: [io 0x0000-0x0007]
0.638629] pci 0000:00:14.1: reg 1c: [io 0x0000-0x0003]
0.638638] pci 0000:00:14.1: reg 20: [io 0xfa00-0xfa0f]
0.638722] pci 0000:00:14.2: [1002:4383] type 00 class 0x040300
0.638743] pci 0000:00:14.2: reg 10: [mem 0xfe024000-0xfe027fff 64bit]
0.638806] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
0.638830] pci 0000:00:14.2: System wakeup disabled by ACPI
0.638857] pci 0000:00:14.3: [1002:439d] type 00 class 0x060100
0.638963] pci 0000:00:14.4: [1002:4384] type 01 class 0x060401
0.639012] pci 0000:00:14.4: System wakeup disabled by ACPI
0.639040] pci 0000:00:14.5: [1002:4399] type 00 class 0x0c0310
0.639053] pci 0000:00:14.5: reg 10: [mem 0xfe028000-0xfe028fff]
0.639119] pci 0000:00:14.5: System wakeup disabled by ACPI
0.639151] pci 0000:00:18.0: [1022:1200] type 00 class 0x060000
0.639203] pci 0000:00:18.1: [1022:1201] type 00 class 0x060000
0.639254] pci 0000:00:18.2: [1022:1202] type 00 class 0x060000
0.639305] pci 0000:00:18.3: [1022:1203] type 00 class 0x060000
0.639358] pci 0000:00:18.4: [1022:1204] type 00 class 0x060000
0.639454] pci 0000:01:00.0: [1002:94b3] type 00 class 0x030000
0.639466] pci 0000:01:00.0: reg 10: [mem 0xd0000000-0xdfffffff 64bit pref]
0.639475] pci 0000:01:00.0: reg 18: [mem 0xfdee0000-0xfdeeffff 64bit]
0.639482] pci 0000:01:00.0: reg 20: [io 0xee00-0xeeff]
0.639493] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
0.639520] pci 0000:01:00.0: supports D1 D2
0.639554] pci 0000:01:00.1: [1002:aa38] type 00 class 0x040300
0.639566] pci 0000:01:00.1: reg 10: [mem 0xfdefc000-0xfdefffff 64bit]
0.639616] pci 0000:01:00.1: supports D1 D2
0.648955] pci 0000:00:02.0: PCI bridge to [bus 01]
0.648960] pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
0.648963] pci 0000:00:02.0: bridge window [mem 0xfde00000-0xfdefffff]
0.648966] pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
0.649016] pci 0000:02:00.0: [197b:2363] type 00 class 0x010185
0.649081] pci 0000:02:00.0: reg 24: [mem 0xfddfe000-0xfddfffff]
0.649130] pci 0000:02:00.0: PME# supported from D3hot
0.649179] pci 0000:02:00.1: [197b:2363] type 00 class 0x010185
0.649197] pci 0000:02:00.1: reg 10: [io 0xdf00-0xdf07]
0.649207] pci 0000:02:00.1: reg 14: [io 0xde00-0xde03]
0.649217] pci 0000:02:00.1: reg 18: [io 0xdd00-0xdd07]
0.649227] pci 0000:02:00.1: reg 1c: [io 0xdc00-0xdc03]
0.649237] pci 0000:02:00.1: reg 20: [io 0xdb00-0xdb0f]
0.649319] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
0.649326] pci 0000:00:04.0: PCI bridge to [bus 02]
0.649329] pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
0.649331] pci 0000:00:04.0: bridge window [mem 0xfdd00000-0xfddfffff]
0.649334] pci 0000:00:04.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
0.649377] pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
0.649389] pci 0000:03:00.0: reg 10: [io 0xce00-0xceff]
0.649408] pci 0000:03:00.0: reg 18: [mem 0xfdfff000-0xfdffffff 64bit pref]
0.649421] pci 0000:03:00.0: reg 20: [mem 0xfdfe0000-0xfdfeffff 64bit pref]
0.649430] pci 0000:03:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
0.649474] pci 0000:03:00.0: supports D1 D2
0.649475] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
0.658954] pci 0000:00:0a.0: PCI bridge to [bus 03]
0.658959] pci 0000:00:0a.0: bridge window [io 0xc000-0xcfff]
0.658961] pci 0000:00:0a.0: bridge window [mem 0xfd900000-0xfd9fffff]
0.658964] pci 0000:00:0a.0: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
0.659008] pci 0000:04:06.0: [1131:7146] type 00 class 0x048000
0.659025] pci 0000:04:06.0: reg 10: [mem 0xfdbff000-0xfdbff1ff]
0.659127] pci 0000:04:07.0: [9710:9805] type 00 class 0x078000
0.659143] pci 0000:04:07.0: reg 10: [io 0xbf00-0xbf07]
0.659155] pci 0000:04:07.0: reg 14: [io 0xbe00-0xbe07]
0.659167] pci 0000:04:07.0: reg 18: [io 0xbd00-0xbd07]
0.659179] pci 0000:04:07.0: reg 1c: [io 0xbc00-0xbc07]
0.659190] pci 0000:04:07.0: reg 20: [io 0xbb00-0xbb07]
0.659202] pci 0000:04:07.0: reg 24: [io 0xba00-0xba0f]
0.659264] pci 0000:04:0e.0: [104c:8024] type 00 class 0x0c0010
0.659286] pci 0000:04:0e.0: reg 10: [mem 0xfdbfe000-0xfdbfe7ff]
0.659298] pci 0000:04:0e.0: reg 14: [mem 0xfdbf8000-0xfdbfbfff]
0.659387] pci 0000:04:0e.0: supports D1 D2
0.659389] pci 0000:04:0e.0: PME# supported from D0 D1 D2 D3hot
0.659445] pci 0000:00:14.4: PCI bridge to [bus 04] (subtractive decode)
0.659449] pci 0000:00:14.4: bridge window [io 0xb000-0xbfff]
0.659453] pci 0000:00:14.4: bridge window [mem 0xfdb00000-0xfdbfffff]
0.659457] pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff pref]
0.659458] pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7] (subtractive decode)
0.659460] pci 0000:00:14.4: bridge window [io 0x0d00-0xffff] (subtractive decode)
0.659462] pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
0.659463] pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
0.659465] pci 0000:00:14.4: bridge window [mem 0xd0000000-0xfebfffff] (subtractive decode)
0.659479] acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
0.659481] acpi PNP0A03:00: Unable to request _OSC control (_OSC support mask: 0x08)
0.659908] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.659945] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.659979] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660012] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660045] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660078] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660111] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660144] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.
0.660468] acpi root: \_SB_.PCI0 notify handler is installed
0.660494] Found 1 acpi root devices
0.660564] ACPI: No dock devices found.
0.660640] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
0.660643] vgaarb: loaded
0.660644] vgaarb: bridge control possible 0000:01:00.0
0.660676] PCI: Using ACPI for IRQ routing
0.668997] PCI: pci_cache_line_size set to 64 bytes
0.669004] pci 0000:00:00.0: no compatible bridge window for [mem 0xe0000000-0xffffffff 64bit]
0.669070] e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
0.669071] e820: reserve RAM buffer [mem 0xcfdf0000-0xcfffffff]
0.669150] NetLabel: Initializing
0.669151] NetLabel: domain hash size = 128
0.669152] NetLabel: protocols = UNLABELED CIPSOv4
0.669161] NetLabel: unlabeled traffic allowed by default
0.669177] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
0.669180] hpet0: 4 comparators, 32-bit 14.318180 MHz counter
0.671205] Switching to clocksource hpet
0.674983] pnp: PnP ACPI init
0.674994] ACPI: bus type PNP registered
0.675058] system 00:00: [io 0x04d0-0x04d1] has been reserved
0.675060] system 00:00: [io 0x0220-0x0225] has been reserved
0.675062] system 00:00: [io 0x0290-0x0294] has been reserved
0.675065] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
0.675512] pnp 00:01: disabling [mem 0x00000000-0x00000fff window] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.675535] pnp 00:01: disabling [mem 0x00000000-0x00000fff window disabled] because it overlaps 0000:01:00.0 BAR 6 [mem 0x00000000-0x0001ffff pref]
0.675543] pnp 00:01: disabling [mem 0x00000000-0x00000fff window disabled] because it overlaps 0000:03:00.0 BAR 6 [mem 0x00000000-0x0000ffff pref]
0.675575] system 00:01: [io 0x4100-0x411f] has been reserved
0.675578] system 00:01: [io 0x0228-0x022f] has been reserved
0.675580] system 00:01: [io 0x040b] has been reserved
0.675581] system 00:01: [io 0x04d6] has been reserved
0.675583] system 00:01: [io 0x0c00-0x0c01] has been reserved
0.675585] system 00:01: [io 0x0c14] has been reserved
0.675586] system 00:01: [io 0x0c50-0x0c52] has been reserved
0.675588] system 00:01: [io 0x0c6c-0x0c6d] has been reserved
0.675589] system 00:01: [io 0x0c6f] has been reserved
0.675591] system 00:01: [io 0x0cd0-0x0cd1] has been reserved
0.675593] system 00:01: [io 0x0cd2-0x0cd3] has been reserved
0.675594] system 00:01: [io 0x0cd4-0x0cdf] has been reserved
0.675596] system 00:01: [io 0x4000-0x40fe] has been reserved
0.675597] system 00:01: [io 0x4210-0x4217] has been reserved
0.675599] system 00:01: [io 0x0b00-0x0b0f] has been reserved
0.675601] system 00:01: [io 0x0b10-0x0b1f] has been reserved
0.675602] system 00:01: [io 0x0b20-0x0b3f] has been reserved
0.675604] system 00:01: [mem 0xfee00400-0xfee00fff window] has been reserved
0.675608] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
0.675676] pnp 00:02: [dma 4]
0.675693] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
0.675740] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
0.675772] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
0.675791] pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
0.675815] pnp 00:06: Plug and Play ACPI device, IDs PNP0c04 (active)
0.676004] system 00:07: [mem 0xe0000000-0xefffffff] has been reserved
0.676006] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
0.676106] pnp 00:08: disabling [mem 0x000cfe00-0x000cffff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676108] pnp 00:08: disabling [mem 0x000f0000-0x000f7fff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676110] pnp 00:08: disabling [mem 0x000f8000-0x000fbfff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676112] pnp 00:08: disabling [mem 0x000fc000-0x000fffff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676114] pnp 00:08: disabling [mem 0x00000000-0x0009ffff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676117] pnp 00:08: disabling [mem 0x00100000-0xcfdeffff] because it overlaps 0000:00:00.0 BAR 3 [mem 0x00000000-0x1fffffff 64bit]
0.676153] system 00:08: [mem 0xcfdf0000-0xcfdfffff] could not be reserved
0.676155] system 00:08: [mem 0xffff0000-0xffffffff] has been reserved
0.676157] system 00:08: [mem 0xcfe00000-0xcfefffff] has been reserved
0.676159] system 00:08: [mem 0xcff00000-0xcfffffff] could not be reserved
0.676161] system 00:08: [mem 0xfec00000-0xfec00fff] could not be reserved
0.676162] system 00:08: [mem 0xfee00000-0xfee00fff] could not be reserved
0.676164] system 00:08: [mem 0xfff80000-0xfffeffff] has been reserved
0.676166] system 00:08: Plug and Play ACPI device, IDs PNP0c01 (active)
0.676180] pnp: PnP ACPI: found 9 devices
0.676182] ACPI: bus type PNP unregistered
0.682550] pci 0000:01:00.0: BAR 6: assigned [mem 0xfde00000-0xfde1ffff pref]
0.682553] pci 0000:00:02.0: PCI bridge to [bus 01]
0.682556] pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
0.682558] pci 0000:00:02.0: bridge window [mem 0xfde00000-0xfdefffff]
0.682561] pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
0.682564] pci 0000:00:04.0: PCI bridge to [bus 02]
0.682566] pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
0.682568] pci 0000:00:04.0: bridge window [mem 0xfdd00000-0xfddfffff]
0.682570] pci 0000:00:04.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
0.682574] pci 0000:03:00.0: BAR 6: assigned [mem 0xfdf00000-0xfdf0ffff pref]
0.682575] pci 0000:00:0a.0: PCI bridge to [bus 03]
0.682577] pci 0000:00:0a.0: bridge window [io 0xc000-0xcfff]
0.682579] pci 0000:00:0a.0: bridge window [mem 0xfd900000-0xfd9fffff]
0.682582] pci 0000:00:0a.0: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
0.682585] pci 0000:00:14.4: PCI bridge to [bus 04]
0.682587] pci 0000:00:14.4: bridge window [io 0xb000-0xbfff]
0.682592] pci 0000:00:14.4: bridge window [mem 0xfdb00000-0xfdbfffff]
0.682595] pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff pref]
0.682771] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
0.682772] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
0.682774] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
0.682775] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff]
0.682777] pci_bus 0000:00: resource 8 [mem 0xd0000000-0xfebfffff]
0.682779] pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
0.682780] pci_bus 0000:01: resource 1 [mem 0xfde00000-0xfdefffff]
0.682782] pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
0.682784] pci_bus 0000:02: resource 0 [io 0xd000-0xdfff]
0.682785] pci_bus 0000:02: resource 1 [mem 0xfdd00000-0xfddfffff]
0.682787] pci_bus 0000:02: resource 2 [mem 0xfdc00000-0xfdcfffff 64bit pref]
0.682788] pci_bus 0000:03: resource 0 [io 0xc000-0xcfff]
0.682790] pci_bus 0000:03: resource 1 [mem 0xfd900000-0xfd9fffff]
0.682791] pci_bus 0000:03: resource 2 [mem 0xfdf00000-0xfdffffff 64bit pref]
0.682793] pci_bus 0000:04: resource 0 [io 0xb000-0xbfff]
0.682795] pci_bus 0000:04: resource 1 [mem 0xfdb00000-0xfdbfffff]
0.682796] pci_bus 0000:04: resource 2 [mem 0xfda00000-0xfdafffff pref]
0.682798] pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
0.682799] pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]

I managed to get my wired connection back and updated my system. After that (and a reboot), NetworkManager started to mysteriously work.
Here are the relevant parts from journald's log:
kesä 17 17:47:40 sunnydale dbus-daemon[396]: dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
kesä 17 17:47:40 sunnydale dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
kesä 17 17:47:40 sunnydale systemd[1]: Starting Network Manager Script Dispatcher Service...
kesä 17 17:47:40 sunnydale dbus-daemon[396]: dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
kesä 17 17:47:40 sunnydale dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
kesä 17 17:47:40 sunnydale systemd[1]: Started Network Manager Script Dispatcher Service.
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) starting connection 'dna internet connection'
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: disconnected -> prepare (reason 'none') [30 40 0]
kesä 17 17:47:49 sunnydale NetworkManager[387]: <debug> [1371480469.388835] [nm-manager.c:596] manager_device_state_changed(): stopping connectivity checks
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) scheduled...
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) started...
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) scheduled...
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 1 of 5 (Device Prepare) complete.
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) starting...
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: prepare -> config (reason 'none') [40 50 0]
kesä 17 17:47:49 sunnydale NetworkManager[387]: <debug> [1371480469.390823] [nm-manager.c:596] manager_device_state_changed(): stopping connectivity checks
kesä 17 17:47:49 sunnydale NetworkManager[387]: <debug> [1371480469.398034] [nm-device-bt.c:947] act_stage2_config(): (40:98:4E:65:A1:00): requesting connection to the device
kesä 17 17:47:49 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 2 of 5 (Device Configure) complete.
kesä 17 17:47:52 sunnydale NetworkManager[387]: <debug> [1371480472.813677] [nm-device-bt.c:836] bluez_property_changed(): (40:98:4E:65:A1:00): bluez property 'Connected' changed to 'true'
kesä 17 17:47:52 sunnydale NetworkManager[387]: <debug> [1371480472.813775] [nm-device-bt.c:846] bluez_property_changed(): (40:98:4E:65:A1:00): connected to the device
kesä 17 17:47:53 sunnydale NetworkManager[387]: <debug> [1371480473.67585] [nm-device-bt.c:808] bluez_connect_cb(): (40:98:4E:65:A1:00): connect request successful
kesä 17 17:47:53 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00 40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN.
kesä 17 17:47:53 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear.
kesä 17 17:47:53 sunnydale upowerd[518]: (upowerd:518): UPower-Linux-WARNING **: unhandled action 'move' on /sys/devices/pci0000:00/0000:00:13.1/usb4/4-3/4-3:1.0/bluetooth/hci0/hci0:21/rfcomm0
kesä 17 17:47:53 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:54 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:54 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:56 sunnydale ModemManager[390]: <info> Creating modem with plugin 'Nokia' and '1' ports
kesä 17 17:47:56 sunnydale ModemManager[390]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:13.1/usb4/4-3' successfully created
kesä 17 17:47:56 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:56 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem: state changed (unknown -> disabled)
kesä 17 17:47:57 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00/bluetooth) Stage 2 of 5 (Device Configure) modem found.
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect started...
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (3/8): Enable
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (rfcomm0) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
kesä 17 17:47:57 sunnydale kernel: Bluetooth: TIOCGSERIAL is not supported
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> enabled)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (4/8): Wait to get fully enabled
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (5/8): Register
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (6/8): Bearer
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (rfcomm0) modem state changed, 'enabling' --> 'enabled' (reason: user-requested)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (7/8): Connect
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabled -> connecting)
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (rfcomm0) modem state changed, 'enabled' --> 'connecting' (reason: user-requested)
kesä 17 17:47:57 sunnydale ModemManager[390]: <warn> Couldn't load Operator Name: 'Unknown error'
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '0', MNC: '0', Location area code: 'A1', Cell ID: '10C654')
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
kesä 17 17:47:57 sunnydale ModemManager[390]: <info> Simple connect state (8/8): All done
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (rfcomm0) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
kesä 17 17:47:57 sunnydale NetworkManager[387]: <warn> (rfcomm0): failed to look up interface index
kesä 17 17:47:57 sunnydale NetworkManager[387]: <debug> [1371480477.987235] [nm-device.c:3066] nm_device_activate_schedule_stage3_ip_config_start(): Activation (40:98:4E:65:A1:00) setting firewall zone 'default'
kesä 17 17:47:57 sunnydale NetworkManager[387]: <debug> [1371480477.987260] [nm-firewall-manager.c:107] nm_firewall_manager_add_or_change_zone(): (rfcomm0) firewall zone add/change skipped (not running)
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 3 of 5 (IP Configure Start) scheduled.
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 3 of 5 (IP Configure Start) started...
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: config -> ip-config (reason 'none') [50 70 0]
kesä 17 17:47:57 sunnydale NetworkManager[387]: <debug> [1371480477.987628] [nm-manager.c:596] manager_device_state_changed(): stopping connectivity checks
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> using modem-specified IP timeout: 20 seconds
kesä 17 17:47:57 sunnydale NetworkManager[387]: <info> starting PPP connection
kesä 17 17:47:57 sunnydale NetworkManager[387]: <debug> [1371480477.988323] [nm-ppp-manager.c:1068] nm_ppp_manager_start(): command line: /usr/sbin/pppd nodetach lock nodefaultroute ipv6 , debug rfcomm0 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> pppd started with pid 914
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 3 of 5 (IP Configure Start) complete.
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 4 of 5 (IPv6 Configure Timeout) started...
kesä 17 17:47:58 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 4 of 5 (IPv6 Configure Timeout) complete.
kesä 17 17:47:58 sunnydale pppd[914]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
kesä 17 17:47:58 sunnydale NetworkManager[387]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
kesä 17 17:47:58 sunnydale kernel: PPP generic driver version 2.4.2
kesä 17 17:47:58 sunnydale pppd[914]: pppd 2.4.5 started by root, uid 0
kesä 17 17:47:58 sunnydale pppd[914]: using channel 1
kesä 17 17:47:58 sunnydale pppd[914]: Using interface ppp0
kesä 17 17:47:58 sunnydale pppd[914]: Connect: ppp0 <--> /dev/rfcomm0
kesä 17 17:47:58 sunnydale pppd[914]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x2ae21925> <pcomp> <accomp>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: <debug> [1371480478.113258] [nm-netlink-monitor.c:164] link_msg_handler(): netlink link message: iface idx 3 flags 0x1090
kesä 17 17:47:58 sunnydale NetworkManager[387]: using channel 1
kesä 17 17:47:58 sunnydale NetworkManager[387]: Using interface ppp0
kesä 17 17:47:58 sunnydale NetworkManager[387]: Connect: ppp0 <--> /dev/rfcomm0
kesä 17 17:47:58 sunnydale NetworkManager[387]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x2ae21925> <pcomp> <accomp>]
kesä 17 17:47:58 sunnydale systemd-sysctl[922]: Duplicate assignment of kernel/sysrq in file '/usr/lib/sysctl.d/50-default.conf', ignoring.
kesä 17 17:47:58 sunnydale NetworkManager[387]: <debug> [1371480478.116359] [nm-udev-manager.c:568] handle_uevent(): UDEV event: action 'add' subsys 'net' device 'ppp0'
kesä 17 17:47:58 sunnydale NetworkManager[387]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
kesä 17 17:47:58 sunnydale pppd[914]: rcvd [LCP ConfRej id=0x1 <magic 0x2ae21925> <pcomp> <accomp>]
kesä 17 17:47:58 sunnydale pppd[914]: sent [LCP ConfReq id=0x2 <asyncmap 0x0>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: rcvd [LCP ConfRej id=0x1 <magic 0x2ae21925> <pcomp> <accomp>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: sent [LCP ConfReq id=0x2 <asyncmap 0x0>]
kesä 17 17:47:58 sunnydale pppd[914]: rcvd [LCP ConfAck id=0x2 <asyncmap 0x0>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: rcvd [LCP ConfAck id=0x2 <asyncmap 0x0>]
kesä 17 17:47:58 sunnydale pppd[914]: rcvd [LCP ConfReq id=0x0 <auth pap> <mru 1500> <asyncmap 0xa0000>]
kesä 17 17:47:58 sunnydale pppd[914]: sent [LCP ConfAck id=0x0 <auth pap> <mru 1500> <asyncmap 0xa0000>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: rcvd [LCP ConfReq id=0x0 <auth pap> <mru 1500> <asyncmap 0xa0000>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: sent [LCP ConfAck id=0x0 <auth pap> <mru 1500> <asyncmap 0xa0000>]
kesä 17 17:47:58 sunnydale pppd[914]: sent [PAP AuthReq id=0x1 user="" password=<hidden>]
kesä 17 17:47:58 sunnydale NetworkManager[387]: sent [PAP AuthReq id=0x1 user="" password=<hidden>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [PAP AuthReq id=0x2 user="" password=<hidden>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [PAP AuthReq id=0x2 user="" password=<hidden>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [PAP AuthAck id=0x2 ""]
kesä 17 17:48:01 sunnydale pppd[914]: PAP authentication succeeded
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [PAP AuthAck id=0x2 ""]
kesä 17 17:48:01 sunnydale NetworkManager[387]: PAP authentication succeeded
kesä 17 17:48:01 sunnydale kernel: PPP BSD Compression module registered
kesä 17 17:48:01 sunnydale pppd[914]: sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPCP ConfReq id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPCP ConfAck id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPCP ConfReq id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPCP ConfAck id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:01 sunnydale kernel: PPP Deflate Compression module registered
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [LCP ProtRej id=0x0 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
kesä 17 17:48:01 sunnydale pppd[914]: Protocol-Reject for 'Compression Control Protocol' (0x80fd) received
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [LCP ProtRej id=0x0 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
kesä 17 17:48:01 sunnydale NetworkManager[387]: Protocol-Reject for 'Compression Control Protocol' (0x80fd) received
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x0 <addr fe80::0000:0000:0000:0000>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfNak id=0x0 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x0 <addr fe80::0000:0000:0000:0000>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfNak id=0x0 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale pppd[914]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:01 sunnydale NetworkManager[387]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:02 sunnydale pppd[914]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:02 sunnydale pppd[914]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:02 sunnydale NetworkManager[387]: rcvd [IPV6CP ConfReq id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:02 sunnydale NetworkManager[387]: sent [IPV6CP ConfAck id=0x1 <addr fe80::f042:f734:907e:22b9>]
kesä 17 17:48:03 sunnydale pppd[914]: rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
kesä 17 17:48:03 sunnydale pppd[914]: sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
kesä 17 17:48:03 sunnydale pppd[914]: rcvd [IPCP ConfNak id=0x2 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale pppd[914]: sent [IPCP ConfReq id=0x3 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: rcvd [IPCP ConfNak id=0x2 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: sent [IPCP ConfReq id=0x3 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale pppd[914]: rcvd [IPCP ConfReq id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:03 sunnydale pppd[914]: sent [IPCP ConfAck id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: rcvd [IPCP ConfReq id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: sent [IPCP ConfAck id=0x0 <addr 10.6.6.6>]
kesä 17 17:48:03 sunnydale pppd[914]: rcvd [IPCP ConfAck id=0x3 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale pppd[914]: Cannot determine ethernet address for proxy ARP
kesä 17 17:48:03 sunnydale pppd[914]: local IP address 10.241.96.30
kesä 17 17:48:03 sunnydale pppd[914]: remote IP address 10.6.6.6
kesä 17 17:48:03 sunnydale pppd[914]: primary DNS address 62.241.198.245
kesä 17 17:48:03 sunnydale pppd[914]: secondary DNS address 62.241.198.246
kesä 17 17:48:03 sunnydale pppd[914]: Script /etc/ppp/ip-up started (pid 928)
kesä 17 17:48:03 sunnydale NetworkManager[387]: <debug> [1371480483.851617] [nm-netlink-monitor.c:164] link_msg_handler(): netlink link message: iface idx 3 flags 0x110D1
kesä 17 17:48:03 sunnydale NetworkManager[387]: <info> PPP manager(IP Config Get) reply received.
kesä 17 17:48:03 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
kesä 17 17:48:03 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 5 of 5 (IPv4 Commit) started...
kesä 17 17:48:03 sunnydale NetworkManager[387]: <debug> [1371480483.852986] [nm-system.c:194] sync_addresses(): (ppp0): syncing addresses (family 2)
kesä 17 17:48:03 sunnydale NetworkManager[387]: <debug> [1371480483.853021] [nm-system.c:247] sync_addresses(): (ppp0): removing address '10.241.96.30/32'
kesä 17 17:48:03 sunnydale NetworkManager[387]: rcvd [IPCP ConfAck id=0x3 <addr 10.241.96.30> <ms-dns1 62.241.198.245> <ms-dns2 62.241.198.246>]
kesä 17 17:48:03 sunnydale NetworkManager[387]: Cannot determine ethernet address for proxy ARP
kesä 17 17:48:03 sunnydale NetworkManager[387]: local IP address 10.241.96.30
kesä 17 17:48:03 sunnydale NetworkManager[387]: remote IP address 10.6.6.6
kesä 17 17:48:03 sunnydale NetworkManager[387]: primary DNS address 62.241.198.245
kesä 17 17:48:03 sunnydale NetworkManager[387]: secondary DNS address 62.241.198.246
kesä 17 17:48:03 sunnydale NetworkManager[387]: Script /etc/ppp/ip-up started (pid 928)
kesä 17 17:48:03 sunnydale NetworkManager[387]: <debug> [1371480483.853775] [nm-system.c:280] sync_addresses(): (ppp0): adding address '10.241.96.30/0'
kesä 17 17:48:03 sunnydale pppd[914]: Script /etc/ppp/ip-up finished (pid 928), status = 0x2
kesä 17 17:48:03 sunnydale NetworkManager[387]: Script /etc/ppp/ip-up finished (pid 928), status = 0x2
kesä 17 17:48:04 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:04 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855173] [nm-netlink-utils.c:356] dump_route(): route idx 3 family INET (2) addr 10.6.6.6/32
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855250] [nm-netlink-utils.c:356] dump_route(): route idx 3 family INET (2) addr 10.241.96.30/32
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855608] [nm-dns-manager.c:995] nm_dns_manager_begin_updates(): (device_ip4_config_changed): queueing DNS updates (1)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855649] [nm-dns-manager.c:1013] nm_dns_manager_end_updates(): (nm_dns_manager_end_updates): DNS configuration did not change
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855666] [nm-dns-manager.c:1017] nm_dns_manager_end_updates(): (device_ip4_config_changed): no DNS changes to commit (0)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.855795] [nm-manager.c:596] manager_device_state_changed(): stopping connectivity checks
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.858147] [nm-device.c:5244] nm_device_queue_state(): (40:98:4E:65:A1:00): queued state change to activated (id 252)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.858200] [nm-device.c:5174] nm_device_state_changed(): (40:98:4E:65:A1:00): device entered SECONDARIES state
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) Stage 5 of 5 (IPv4 Commit) complete.
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.870449] [nm-device.c:5202] queued_set_state(): (40:98:4E:65:A1:00): running queued state change to activated (id 252)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> (40:98:4E:65:A1:00): device state change: secondaries -> activated (reason 'none') [90 100 0]
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.872130] [nm-manager.c:591] manager_device_state_changed(): (40:98:4E:65:A1:00): triggered connectivity check due to state change
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.873625] [nm-dns-manager.c:995] nm_dns_manager_begin_updates(): (device_state_changed): queueing DNS updates (1)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.873683] [nm-dns-manager.c:995] nm_dns_manager_begin_updates(): (update_routing_and_dns): queueing DNS updates (2)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> Policy set 'dna internet connection' (ppp0) as default for IPv4 routing and DNS.
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874320] [nm-dns-manager.c:1013] nm_dns_manager_end_updates(): (nm_dns_manager_end_updates): DNS configuration changed
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874341] [nm-dns-manager.c:1017] nm_dns_manager_end_updates(): (update_routing_and_dns): no DNS changes to commit (1)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874368] [nm-dns-manager.c:1013] nm_dns_manager_end_updates(): (nm_dns_manager_end_updates): DNS configuration changed
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874383] [nm-dns-manager.c:1022] nm_dns_manager_end_updates(): (device_state_changed): committing DNS changes (0)
kesä 17 17:48:04 sunnydale NetworkManager[387]: <debug> [1371480484.874399] [nm-dns-manager.c:591] update_dns(): updating resolv.conf
kesä 17 17:48:04 sunnydale NetworkManager[387]: <info> Activation (40:98:4E:65:A1:00) successful, device activated.
kesä 17 17:48:04 sunnydale dbus-daemon[396]: dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
kesä 17 17:48:04 sunnydale dbus[396]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
kesä 17 17:48:04 sunnydale systemd[1]: Starting Network Manager Script Dispatcher Service...
kesä 17 17:48:04 sunnydale dbus-daemon[396]: dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
kesä 17 17:48:04 sunnydale dbus[396]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
kesä 17 17:48:04 sunnydale systemd[1]: Started Network Manager Script Dispatcher Service.
kesä 17 17:48:07 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:07 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:10 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:10 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:13 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:13 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:16 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:16 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:19 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:19 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:21 sunnydale /etc/gdm/Xsession[622]: (process:953): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
kesä 17 17:48:22 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:22 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:25 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:CurrentTime used to choose focus window; focus window may not be correct.
kesä 17 17:48:25 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:Got a request to focus 0x2200006 (jussi@sunn) with a timestamp of 0. This shouldn't happen!
kesä 17 17:48:25 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:CurrentTime used to choose focus window; focus window may not be correct.
kesä 17 17:48:25 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
kesä 17 17:48:25 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:25 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:28 sunnydale pppd[914]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:28 sunnydale NetworkManager[387]: sent [IPV6CP ConfReq id=0x1 <addr fe80::e85e:dbed:209d:cf47>]
kesä 17 17:48:31 sunnydale pppd[914]: IPV6CP: timeout sending Config-Requests
kesä 17 17:48:31 sunnydale NetworkManager[387]: IPV6CP: timeout sending Config-Requests
kesä 17 17:49:41 sunnydale dbus-daemon[396]: dbus[396]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
kesä 17 17:49:41 sunnydale dbus[396]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
kesä 17 17:49:41 sunnydale systemd[1]: Starting Hostname Service...
kesä 17 17:49:41 sunnydale dbus-daemon[396]: dbus[396]: [system] Successfully activated service 'org.freedesktop.hostname1'
kesä 17 17:49:41 sunnydale dbus[396]: [system] Successfully activated service 'org.freedesktop.hostname1'
kesä 17 17:49:41 sunnydale systemd[1]: Started Hostname Service.
kesä 17 17:49:43 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:Log level 8: meta_window_raise: assertion `!window->override_redirect' failed
kesä 17 17:49:44 sunnydale /etc/gdm/Xsession[622]: Ikkunointiohjelman varoitus:Log level 8: meta_window_lower: assertion `!window->override_redirect' failed
And here is log about the updates I made:
[2013-06-17 17:01] [PACMAN] Running 'pacman -Syu'
[2013-06-17 17:01] [PACMAN] synchronizing package lists
[2013-06-17 17:01] [PACMAN] starting full system upgrade
[2013-06-17 17:04] [PACMAN] Running 'pacman -S --asdeps polkit'
[2013-06-17 17:04] [PACMAN] upgraded polkit (0.110-2 -> 0.111-1)
[2013-06-17 17:24] [PACMAN] Running 'pacman -U --asdeps lib32-polkit-0.111-1-x86_64.pkg.tar.xz'
[2013-06-17 17:24] [PACMAN] upgraded lib32-polkit (0.110-2 -> 0.111-1)
[2013-06-17 17:27] [PACMAN] Running 'pacman -S --asdeps libxkbcommon'
[2013-06-17 17:27] [PACMAN] upgraded libxkbcommon (0.3.0-1 -> 0.3.1-1)
[2013-06-17 17:28] [PACMAN] Running 'pacman -U --asdeps lib32-libxkbcommon-0.3.1-1-x86_64.pkg.tar.xz'
[2013-06-17 17:28] [PACMAN] upgraded lib32-libxkbcommon (0.3.0-1 -> 0.3.1-1)
[2013-06-17 17:28] [PACMAN] Running 'pacman -Syu'
[2013-06-17 17:28] [PACMAN] synchronizing package lists
[2013-06-17 17:28] [PACMAN] starting full system upgrade
[2013-06-17 17:33] [PACMAN] removed lib32-dbus-core (1.6.10-1)
[2013-06-17 17:33] [PACMAN] upgraded attr (2.4.46-2 -> 2.4.47-1)
[2013-06-17 17:33] [PACMAN] upgraded acl (2.2.51-3 -> 2.2.52-1)
[2013-06-17 17:33] [PACMAN] upgraded attica (0.4.1-2 -> 0.4.2-1)
[2013-06-17 17:33] [PACMAN] upgraded cups-pk-helper (0.2.4-1 -> 0.2.5-1)
[2013-06-17 17:33] [PACMAN] upgraded dbus (1.6.10-1 -> 1.6.12-1)
[2013-06-17 17:33] [PACMAN] upgraded dosfstools (3.0.17-1 -> 3.0.20-1)
[2013-06-17 17:33] [PACMAN] upgraded gtk-update-icon-cache (2.24.18-1 -> 2.24.19-1)
[2013-06-17 17:33] [PACMAN] upgraded gtk2 (2.24.18-1 -> 2.24.19-1)
[2013-06-17 17:33] [PACMAN] upgraded flashplugin (11.2.202.285-1 -> 11.2.202.291-1)
[2013-06-17 17:33] [PACMAN] upgraded libgdm (3.8.1.1-2 -> 3.8.3-1)
[2013-06-17 17:33] [ALPM] warning: directory permissions differ on /var/log/gdm/
filesystem: 711 package: 1770
[2013-06-17 17:33] [PACMAN] upgraded gdm (3.8.1.1-2 -> 3.8.3-1)
[2013-06-17 17:33] [PACMAN] upgraded geoip-database (20130514-1 -> 20130607-1)
[2013-06-17 17:33] [PACMAN] upgraded git (1.8.3-1 -> 1.8.3.1-1)
[2013-06-17 17:33] [PACMAN] upgraded glib2 (2.36.2-1 -> 2.36.3-2)
[2013-06-17 17:33] [PACMAN] upgraded xkeyboard-config (2.9-1 -> 2.9-2)
[2013-06-17 17:33] [PACMAN] upgraded iso-codes (3.41-1 -> 3.43-1)
[2013-06-17 17:33] [PACMAN] upgraded gnome-desktop (1:3.8.3-1 -> 1:3.8.3-2)
[2013-06-17 17:33] [PACMAN] upgraded gnome-user-docs (3.8.1-1 -> 3.8.2-1)
[2013-06-17 17:33] [PACMAN] upgraded graphite (1:1.2.2-1 -> 1:1.2.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-afc (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-goa (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [ALPM-SCRIPTLET] Users no longer need to be in the 'camera' group to use camera devices
[2013-06-17 17:33] [PACMAN] upgraded libgphoto2 (2.5.1-1 -> 2.5.2-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-gphoto2 (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-mtp (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-obexftp (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded gvfs-smb (1.16.2-2 -> 1.16.3-1)
[2013-06-17 17:33] [PACMAN] upgraded hwids (20130512-1 -> 20130607-1)
[2013-06-17 17:33] [PACMAN] upgraded jre7-openjdk-headless (7.u21_2.3.9-4 -> 7.u40_2.4.0-1)
[2013-06-17 17:33] [PACMAN] upgraded jre7-openjdk (7.u21_2.3.9-4 -> 7.u40_2.4.0-1)
[2013-06-17 17:33] [PACMAN] upgraded jdk7-openjdk (7.u21_2.3.9-4 -> 7.u40_2.4.0-1)
[2013-06-17 17:33] [PACMAN] upgraded json-c (0.10-2 -> 0.11-1)
[2013-06-17 17:33] [PACMAN] upgraded krb5 (1.11.2-4 -> 1.11.3-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-attr (2.4.46-2 -> 2.4.47-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-acl (2.2.51-2 -> 2.2.52-1)
[2013-06-17 17:33] [PACMAN] installed lib32-dbus (1.6.12-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-gtk2 (2.24.18-1 -> 2.24.19-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-json-c (0.10-2 -> 0.11-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-krb5 (1.11.2-1 -> 1.11.3-1)
[2013-06-17 17:33] [PACMAN] upgraded libpulse (4.0-1 -> 4.0-2)
[2013-06-17 17:33] [PACMAN] upgraded lib32-libpulse (4.0-1 -> 4.0-2)
[2013-06-17 17:33] [PACMAN] upgraded libxrender (0.9.7-1 -> 0.9.8-1)
[2013-06-17 17:33] [PACMAN] upgraded lib32-libxrender (0.9.7-1 -> 0.9.8-1)
[2013-06-17 17:33] [PACMAN] upgraded libbsd (0.4.2-1 -> 0.5.2-1)
[2013-06-17 17:33] [PACMAN] upgraded libmbim (1.0.0-1 -> 1.2.0-1)
[2013-06-17 17:33] [PACMAN] upgraded libnautilus-extension (3.8.1-1 -> 3.8.2-1)
[2013-06-17 17:33] [PACMAN] upgraded libpipeline (1.2.3-1 -> 1.2.4-1)
[2013-06-17 17:33] [PACMAN] upgraded libquvi-scripts (0.4.14-1 -> 0.4.15-1)
[2013-06-17 17:33] [PACMAN] upgraded libusb-compat (0.1.4-2 -> 0.1.5-1)
[2013-06-17 17:33] [PACMAN] upgraded libxvmc (1.0.7-1 -> 1.0.8-1)
[2013-06-17 17:33] [PACMAN] upgraded link-grammar (4.7.11-1 -> 4.7.12-1)
[2013-06-17 17:33] [PACMAN] upgraded linux-firmware (20130528-1 -> 20130610-1)
[2013-06-17 17:33] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-06-17 17:33] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Starting build: 3.9.6-1-ARCH
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Starting build: 3.9.6-1-ARCH
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-06-17 17:33] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-06-17 17:33] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-06-17 17:33] [PACMAN] upgraded linux (3.9.5-1 -> 3.9.6-1)
[2013-06-17 17:33] [PACMAN] upgraded linux-headers (3.9.5-1 -> 3.9.6-1)
[2013-06-17 17:33] [PACMAN] upgraded lirc-utils (1:0.9.0-46 -> 1:0.9.0-47)
[2013-06-17 17:33] [PACMAN] upgraded mime-types (8-1 -> 9-1)
[2013-06-17 17:33] [ALPM] warning: extracting /usr/share/applications/nautilus.desktop as /usr/share/applications/nautilus.desktop.pacnew
[2013-06-17 17:33] [ALPM] warning: extracting /usr/share/applications/nautilus-autorun-software.desktop as /usr/share/applications/nautilus-autorun-software.desktop.pacnew
[2013-06-17 17:34] [PACMAN] upgraded nautilus (3.8.1-1 -> 3.8.2-1)
[2013-06-17 17:34] [PACMAN] upgraded p7zip (9.20.1-6 -> 9.20.1-7)
[2013-06-17 17:34] [ALPM] warning: /etc/ppp/ip-down.d/00-dns.sh installed as /etc/ppp/ip-down.d/00-dns.sh.pacnew
[2013-06-17 17:34] [ALPM] warning: /etc/ppp/ip-up.d/00-dns.sh installed as /etc/ppp/ip-up.d/00-dns.sh.pacnew
[2013-06-17 17:34] [PACMAN] upgraded ppp (2.4.5-6 -> 2.4.5-7)
[2013-06-17 17:34] [ALPM-SCRIPTLET] >>> If you have per-user copies of configuration files (such as client.conf,
[2013-06-17 17:34] [ALPM-SCRIPTLET] daemon.conf or default.pa) in ~/.pulse/, make sure you keep them in sync
[2013-06-17 17:34] [ALPM-SCRIPTLET] with changes to the packaged files in /etc/pulse/. Otherwise, PulseAudio
[2013-06-17 17:34] [ALPM-SCRIPTLET] may refuse to start due to configuration errors.
[2013-06-17 17:34] [PACMAN] upgraded pulseaudio (4.0-1 -> 4.0-2)
[2013-06-17 17:34] [PACMAN] upgraded python-dbus-common (1.1.1-2 -> 1.2.0-1)
[2013-06-17 17:34] [PACMAN] upgraded python-dbus (1.1.1-2 -> 1.2.0-1)
[2013-06-17 17:34] [PACMAN] upgraded python2-dbus (1.1.1-2 -> 1.2.0-1)
[2013-06-17 17:34] [PACMAN] upgraded sdparm (1.07-1 -> 1.08-1)
[2013-06-17 17:34] [PACMAN] upgraded sg3_utils (1.35-1 -> 1.36-1)
[2013-06-17 17:34] [PACMAN] upgraded shared-desktop-ontologies (0.10.0-1 -> 0.11.0-1)
[2013-06-17 17:34] [PACMAN] upgraded subversion (1.7.9-6 -> 1.7.10-1)
[2013-06-17 17:34] [PACMAN] upgraded sudo (1.8.6.p8-2 -> 1.8.7-1)
[2013-06-17 17:34] [PACMAN] upgraded syslog-ng (3.4.1-3 -> 3.4.2-1)
[2013-06-17 17:34] [PACMAN] upgraded usbutils (006-1 -> 007-1)
[2013-06-17 17:34] [PACMAN] upgraded webkitgtk (2.0.2-3 -> 2.0.3-1)
[2013-06-17 17:34] [PACMAN] upgraded wine (1.6rc1-1 -> 1.6rc2-1)
I'm marking this thread solved for now. If the problem arises again, I'll reopen it.

My Own Concept Idea - Nokia Gorilla Phone.

I figure a range rather than just limiting myself such as the Navigator Series, the E series, the N series, but this could be the G range or Gorilla Range. anyway i'd like to see this based on Symbian 60
OK might as well warn you,i'm drunk now, i was drunk when i wrote it too, so i've not spell checked it or anything and to be honest not going to either until i wake up so here goes, if nokia can't take on iphone because they don't understand what 'bling' is yet. so anyway check out my concept phone idea.
Nokia's Gorrila Phone
Specs for: Nokia Survival Range - The Gorrila Phone
This is all new, This is for the mountain climber, the skier the extreme sports, the swimming
coach, anyone who works in a dusty or dirty enviorment, this is for the construction worker, the
security gaurd, the police, this is for everyone who likes to venture out past their back doors
and into the wild extreme world we live in, scared of going into a pub in the fear of dropping it or
falling out, the Gorilla Phone can handle it.
We first have to do a special technique to this phone to get it to be what people will need
and want.
*Waterproof
*Sturdy Gel / rubber type case to protect it from drops
*GPS
*WIFI
*Accelerometer
*Compass
*Barometer*
*Signal Amplifier*/Better internal antenna design
*All the frequencies we can fit on
*Small Camera, nothing fancy
*8/16 Gig of Memory for user content files and games images / videos
*100+ meg of ram
*OLED 320*200, enough to see a map on would be ok, a little larger than the Nokia 6110
*Bluetooth *heart rate device
*Docking Station (maybe compatable for future releases?)
Able to squeeze as much power out of it as possible with say a 1amp/h battery
All radio devices off mode except anything you select on the list to help conserver
battery life or survival mode.
AND
Docking Station which connects at the bottom of the phone and then clips onto the phone, there
will be 5 (or more) little metal pins that protrude out of the plastic phone which is slightly hidden out
of the view due to the gel like case..
[Nokia's]
[Gorilla]
[_Phone_]
{ I I I }
[ ] (this is the docking station which just clips in and accesses the ports from the PC)
DPV
So basically once you cliped it on the 5 little pins (as soldered blobs protude gold coated
to prevent wearing away
(Sea water might be an issue, might stick a warning in saying not suitable for sea water due to errorison
which will be down to you other than that the phone should work fine.... maybe a cost underwarrents to
just replace those pins meaning a component could be designed to simply pull out with realitive ease making
it cost efficient to both the user and nokia...)
Other than being able to make actual phone calls maybe if that went under a thin peace of plastic that can be
easily heard so that the case does not get in front of sound quality. and likewise near the bottom or some sort
of attachment for a waterproof speaker. The electronics with the exception of the connectivity modual to make it
easy to exchange the rusted component pop it out and replace)
Battery / Sim Card.
Pull off the battery case, some kind of switch to lock the battery cover into place to prevent it coming out
even if you try yourself, the inner side of the phone should have a waterproof gasket to prevent any kind
of water coming through under the battery.
Outside of the phone we appear to have 0 inputs but infact we actually have it with this simple docking
station, the docking station is connected to the PC via usb so this way your phone simply clips on
no fuss no looking around for a spare usb port, or plugging in the cable, the docking station makes it much
more easier.
---- +
---- Data
---- Data
---- Whatever.
The data can then be grabbed off the phone on the computer, the docking station, while docked it will charge
the phone, it will supply USB 2.0 and transfer files between phone and computer, optional for later advances
could be given on the docking station also USB/WIFI file transfer if not using the docking station
Gorrila Phone Charge In(0) Such as, External Chager
USB Out (which connects to PC)
TV out (TV OUT)
Headphone out (unplug the computer's USB)
- etc
Virtual Drive or Real Drive via Micro SD.
Virtual would be for example this gorilla phone were the 8 gig internal is the memory card on E:\
once connected to the docking station, you then have the unquie ability to put in an 8 gig memory
SD card into the dockingstation and backup or use (from windows explorer) and be able to
copy either from internal memory or external memory of a memory card you've inserterd, in terms
this is a way of cloning your memory card as a backup, this could all be done with the docking station
and a simple button of "Backup Memory Content" simply have a little Green LED and Red Led come up when
you press copy, Green for writing/Reading, Red for Error, or maybe Orange for finished succesfully...
you could then back up your phone to another memory card anywhere anytime... how useful's that! or even
have the ability to use that dockingstation's memory with the mobile device itself and as long as it's connected
you can even install programs on it.... 2 Drives, the posibilites are endless.
So all the outputs we're all so a custom all now live on the docking station, so now what, the protection
of the phone comes first, all the circuits have to be covered in a gel/rubber/glue expoy type substance
and injected protecting the delecate components, it has to be essential to protect ribbin cables
and other little pins and cables that have to stay firmly in place, also doing this will increase
the circuity's protection against g-force and shock.. once all the gaps have been filled and all made
sure to be very very watertight against dust and all else that is thrown at it...
Now then the Gorrila Phone's key aspects
*Survival of any keen trecker or explorer will need and want.
*Tough for the toughest jobs, Construction Worker, Police, Law Enforcement, Road Workers.
*can be dropped from X amount of feet (based on calculations done)
*Survies water and dirt
*Can be submerged underwater up to 30 Feet for 30 minutes or so? etc, give it an IP rating of IP-6
Now then why does an explorer or hiker need this?..
*Electronic compass will always point you north, combine this with GPS and you'll have
yourself a way of locating your position and which direction you're pointing.
*Barometer, small symbian application to interpret the pressure in milli bars, you could
then have your phone warn you if the pressure's increase (high pressure, good conditions) or
if the pressure starts to drop rapidly which could indicate bad weather (storms etc)
*Altimeter could be used, however the GPS is far more precise, maybe something in the future could be done, this would
be uptodate information, other phones could even send into a server, how much processing power and number crunching would
take place if every mobile phone could send a FREE SMS to a server every few hours with your GPS location
and altitude, world wide, i'm sure we'd be able to improve weather predicting with so much data coming in
from the people who say yes to submitting data to a weather server, providing the altmeter is calibrated.
GPS data, this phone will go all out to get a signal, then you have a series of options like sms my current
location to another phone or a request for help including how high up (altimeter/gps) his/hers cords from
the GPS
with the OPTIONAL bluetooth heartrate monitor.
*the phone could connect to a bluetooth heartrate monitor and then it displays the BPS of the indvididual
and a small sensor to measure temprature from the person as well.
*Maybe a Resuce Mode
*Safety mode / tacker
If the person who's in danger is able to get a signal even from 2g or the phone
will automatically try if it's in rescue mode, in rescue mode it could get your body
temprature, BPS, get your GPS location and direction heading from compass, even the barometer
so it could report things like weather info to help, for example is it safe to use a helicopter?
Why yes, the last 8 sms text messages the barometer has been increasing, but could easily be looked
up anyway.
If the person collapses, the SMS messages until someone arrives will be the only info, since we
are able to monitor heart rate and location, the emergency services will arrive.
Now if the heart beat drops below X BPS, it could automatically SMS the wife, brother, girlfriend
or even multiple people, reporting back the person could be in a lot of danger, there would be nothing
like this on the planet.
If not in danger, there will be software to monitor vital conditions, tempraterue of you, it can
also see where you've been by tracking your data and storing it automatically on memory, all data
stored could be used as a 'black box' once recovered, in other uses..
In other uses, it could detect that your heart beat has just shot up from 80 up to 120 and higher
it was an instant change, this could then SMS the parent, or the phone could make a high pitched alarm
sound either as to prevent an attacker and drawing attention to you or the high pitched alarm could be
an alert to others to say something is wrong with you and seek help, it could even detect low heart beats
and also do a similar warning of sms or both.
the Gorrila Nokia Phone can survive up to say -30c because it's well insulated and well protected
from the outside elements if there's a way of making a watertight seal with a slide, use that
if not the keypad can be put below as traditional phones go for example the new nokia 2960 style.
internally protected by epxoy too, So for a good rough phone that withstands abuse and yet be
absolutely packed tight of features nobody could say no.....
With the broadsprectrum of frequencies the phone has to offer, 2G, 3G 3.5G etc etc you stand more
chance of getting a signal with the better antenna or included signal amplifier/booster to pickup
that signal that might just save your life and then your phone becomes your only chance of hope....
Without the gorrila docking station, you wont be able to charge the phone without one although
you could use bluetooth/wifi in the short term for data transfer...
*Accelerometer / Barometer/ GPS...
Each one could be used for this but if all 3 were combined an accurate result would be optained
and better to accurately determine to warn or not, for example if the heart beat drops or increases
significantly an automatic SMS text message can be delivered to friends and family instantly before
the person even realizes themselves...
The person might be climbing the side of a hill and all of a sudden he trips and ends up sliding down
the hill, the Gorilla Phone might be a few feet away now even outside the range of the bluetooth heart
/temp monitor, ok, the phone is montioring the altitude via either altimeter or GPS or both, the acceleromter
detected the sudden movement and jerk and strong G-Force at the very millisecond he falls.
the alitmeter suddenly declines in only a couple of seconds, and now the heart rate monitor is out of range
based on that data.....
The person has just fell 3ft from X,Y GPS cords, and the phone landed X,Y GPS cords, it then gets as much
data as possible such as altitude, temprature from phone (or heart rate monitor) and if the phone is not picked
up within 10 seconds, the Nokia Gorilla Phone kicks into action sending out an SMS with your location on it can send up
to 10 people or so of importance along with contact info directly to you when it happens.
by now, the SMS message will provide emergency services precisely to the location of
where the person has fallen or rough position, as the person may lay 3 or more meter away from where
the phone had landed, this could very easily save a persons life, imagine if this happening at night
in a wooded area, if the phone is simply dropped most people would pick it up within 10 seconds, even then
a drop from roughly were you're holding the phone to where your feet are would indicate a dropped phone......
The heart rate monitor could sit on you as every day normal life and if you have a heart attack, your
phone will know (providing you're linked via bluetooth 10/100m range?) there's a serious medical problem
and again could easily get the message out to save your life, even possibly having an option where the phone
smses AND turns on the loud speaker so you can talk to emergency services, maybe a simple voice to speech or
if you can't speech and can't move, there's not going to be that much of conversation but could be added.
SMS Return: Location: GPS Cords X,Y; Altitude: 844m; HeartRate: 50; Pressure: ?milibars
time spent getting to you to save your life,
rather than time spent trying to find out where you are.
Another option would be to text the phone and then get a text message back automatically
providing access was granted on the phone.
The Ultimate Survival Tool... Nokia's Gorrial Range of phones.
They can save your life, they're tough take them anywhere you want, show it smashed down
hard onto the table with an iphone (lookalike) that just smashes into pieces with the phone
saying pick me up (since it will detect the smash as a drop of phone onto say concrete)
if it detects a fall, if it does not get pickedup within 10 seconds, people are alterted
to this fall or collapse,
Difference in this case between fall and collapse is simple, what's your heart rate at if
there's a problem there, it does not presume it was dropped and that you're in serious medical trouble
take it swimming with you in the swimming pool, get your GPS cords and display them on a map
geotag photos, get info about the weather, using the barometer high and low bands if a low pressure
wave comes in and the barometer is dropping 998, 983 over a period of time will indicate what's likely
to happen, if it increases better weather, if it decreases the weather coming in is bad, the phone
will then direct you to start looking for shelter or find a nice lookout sunshine on the way...
So all is well? the bluetooth monitor could even be attached to you sleeping so if your body
temp and heart rate drop badly, it looks like you're freezing to death, the phone will then alarm
a danger sound to try and wake the person sleeping up as well as contacting friends and family
who will ring you, or give the message out with the GPS info out to the emergency services.
The nokia gorilla's not just another phone, it's your buddy who looks out for you and will follow you
into any conditions you go into, you work on the construction site, you wear a hard hat for protection
when you see a nice new iphone (lookalike) all pretty has to wear a yellow hat, what a disgrace... while
the Gorllia slilently laughs...
The toughman phone with the ultimate survival tools, the Nokia Gorilla Phone, kicked, sat on, used
to prop up your monitor, very tough and very strong handles whatever is thrown at it... but with GPS
Barometer, WIFI, Compass you'll have everything you'll ever need handle what mother nature can throw
at you..
Maybe a couple of LED's to make the casing light up at night incase you drop it, which a sensor can detect
if it's dark or not after it's been dropped (fed by data by the accelerometer, drop found, any light? no switch on lights)
Oh yes and relax by playing with the internet browser over wifi, enjoy the better reception you get from better
antenna or boosed up (amplified) radio signal.. enjoy the fact you can depend on this phone, it's your buddy
not just a phone.
So anyway guys what you think?

The Nokia 3720 classic is a IP54 level water,
Not even close to good enough, LCD screen will crack, water will go in through the jack/charger ports..
The phone i describe has no external ports just 4-5 little pins which can't let water in or out of the device, the docking station will connect via these 4 - 5 pins for data transfer and recharging...., IPX8 standard, all the electronics are epxoyed with a glue to stop real bad shocks from drops and bangs, along with a silicon case and all the other preventative meausres means this little phone is going to outlive you.
in combination with heart rate external bluetooth connection, really what more could you want... only the Sonim comes close in terms of perfection but if it managed to pack all of above, then it would be simply wow... I don't think there's enough people who work for nokia who actually go camping, backpacking, hiking, i'm pretty sure that if i told them one day
on a holiday you might drop your phone into the swimming pool, ok fine it's a mistake but damn, there goes your $$$$ N7 or N900 or even a HTC or Iphone.... not this, you'd yell to the first person you see in the pool, hey mate can i have my phone back, don't worry about the water damage, i'll get it back on insurance after a small lie stopping the person from running off with it (in fear of the now useless mobile phoned killed by water, making an attempt to steal be useless)
The person gets their phone back and carries on about his day, it drops out of your pocket, how many times you ran over it because you happened to leave it behind the back tire. oh no i ran over my phone, the tough casing and the epoxy keeping it nice and safe, except for superficial damage cosmetic, the screen and phone should be working still able to make that call or send out GPS info....
Sorry nothing comes close by any company (except Sonim) in terms of what they can do... maybe even a portable charger turn it to recharge like on LED dynamos. nah maybe not.

My experience with the N97 - "my last Nokia"

Hi everyone,
I know this is a user-to-user support forum but I believe a complaint to be some sort helps users to decide whether the N97 is for them or not. Before you read on, this post will contain comparisons to competitors, so if you hate apples, feel free to ignore me! (Also I don't think users should stop harassing Nokia for what they have done to us - the more complaints the better. Igoring customers is not a very good corporate strategy. Eventually it will take them down - people buy Nokia for quality, otherwise they could buy a rip-off from ebay).
Just skimming over the posts shows me that I am not alone. So let me share my experience with Nokia and the N97. I am too tired complaining about this phone, at least I think my experience has made sure that no-one of my friends and relatives is ever going to buy a Nokia again.
When I bought the phone for then 500 pounds at the Nokia flagship store in London it seemed nice enough. Good camera, decent keyboard and features competitors could only dream of. Unfortunately, that's paperwork. For a start, the much advertised facebook application was completely disfunctional and taking into account that Nokia clearly tried to compete with the iphone (my apologies again for mentioning a competitor) frankly a lame joke. I know a firmware update has somewhat relieved the situation now, but I will come to that later.
Okay, so I have disabled the facebook application. Not a drama, surely the rest will work okay. But then after a week some of the pictures I took with the built-in camera weren't accessible anymore (broken image displayed). Again, I have another camera and I was hoping for a firmware update so I ignored it. I had now started using the joikuspot app to browse the internet on my linux box. Very nice. I started using email a lot on my phone but again was disappointed. I have a £165 ipod touch here. Without kinetic scrolling and an extremely bad UI design, by which I mean the icons and menus (ignoring the graphics flaws all the time) it is no match for the ipod, so what i did was to use joiku spot with my ipod touch. Before that firmware update the N97s browser was also still buggy so I used joikuspot for that too. I was now down to using my £500 smartphone as a wireless modem. What a shame. But I was still hoping for some kind of magic update.
Then finally, I found out about the firmware update. I had to open my phone, check the serial and visit the Nokia website. Unfortunately, the Ovi software and drivers supplied with the phone did not recognize my N97 properly. Something which I think was fixed with the firmware update (anyone seeing a circular dependency here? ) Furthermore, the built-in firmware update over 3G seemed to be disabled. So I made the journey back to the flagship store in London, explaining the problem. I was greeted by an extremly rude employee. Well, I think that's not really his fault, I guess he was just sick of all the complaints. Anyways, I told him that the 3G update was not working and he started to be really patronizing telling me that I wouldn't listen to him (he said it was "working" but "disabled"). Maybe I should have told him that I am a software engineer and that in 99.9% of the cases in which we disable a feature, the reason is that it is "not working". Anyways, he kindly allowed me to use one of their machines to update the firmware "at my own risk", which worked. At no point I have received an apology for the fact that I have paid Nokia £500 to beta-test their products.
Now of course, the firmware update has succeeded, but is all fine? Far from it.... As many report on this forum the N97s battery meter is faulty. Countless times, my phone has just literally died overnight. It even forgets time and date! This is more than bad - every phone I have had so far complained about a draining battery well in advance. I had to dig out my old phone to serve as an alarm clock again - the fact that the alarm clock itself is unreliable is a alltogether different matter... One time the battery died during the day - after doing nothing for 4 hours in my sports bag (started with 1 bar down). When I had to make a call that day, for the first time in I don't know how many years I had to use a telephone box. Progress?!
The firmware update has also barely improved the email client - just a few ui glitches solved. However, the biggest issue at the moment seems to be the weird memory organization. When I buy a phone I don't want to deal with something like the c drive problem. Reinstalling applications on the 32gb partition helps somewhat but why didn't Nokia do that in the first place? Has this phone never been tested?The phone is still way too slow.
I can't comment on the iplayer app - says it needs wlan to work. But the youtube player has crashed every time i used it. And by crashing I mean it took down the whole phone with it. I admit that my ipod crashed a few times too - in just under a year (~3 times). But the reset was straightforward every time. With the N97, the only thing that seems to help is to take the battery out!
Before I forget, the N97 doesn't even work as a phone. In a 30 minute conversation, the call got dropped 4 times. I don't know whether it was because of a calibration issue with the proximity sensor or a more serious problem, all I know is that this is unacceptable!
I am sick of the phone and Nokia's service. The joikuspot app ran out and asks me to pay... I have paid £500 pounds for the bloody phone already. The adobe reader asks me to pay... (somehow it ran out without me even using it). Maybe you see why I am getting angry now - the only use case that actually put the N97 on top of my old phone was gone. What infuriated me even more, is that Nokia bundles this software with the phone. It cannot actually be deinstalled! It just sits there merrily and takes up my hard drive space.
Last but not least, I have written to Nokia already, but not received a response! This is a Nokia forum with Nokia employees following the posts. I would be very, very, very grateful if Nokia could give me a refund. However, with them not even acknowledging the various problems I somehow don't see that coming. I'll probably have to sell it with a massive loss on ebay.
Cheers,
Will
P.s.: I have all the same small issues as the other guys here - slider lock at the side not working etc. You are not alone... Has anyone complained about the music player? I have 16gb of music on the phone and scrolling is impossible! The Symbian OS is so obviously not built for a touch screen that it hurts. Of course they don't put much music on the phones in the Nokia store so people only find out when they get home...
Message Edited by alcroth on 12-Sep-2009 11:32 AM
Solved!
Go to Solution.

hi ! the nokia n97 is a really an amazing device. It keeps up to the promise of live online 24 x 7. I discovered it and wanted to share. Still there are some unanswered questions and if any vetran could help would really appreciate.
i am an user from India. and have the n97 for about 3-4 weeks now. Practically I have been living online 24 x 7 as The list of unexpected issues that a nokia n97 offers seems unending, some of which i am narrating have made me scout on the web to try n search answers.Not that i will be able to action information you provide instantly. My new phone has gone for reparis(sic), so once its back can do that & will acknowledge your replies.
My Quests:
1. First things first! How to request for & get refunds for a Nokia Phone in India.
2. Is there a touch querty as an input method? like windows mobile ? Request Know How. I now seem to agree to the feedback on one of the blogs.. that nokia designers feel that the average size of user hands would be that of big people & fingers like a japaneese teen. The physical keyboard does not seem to offer any additional functions other than text input !
3. Predictive text where in the touch screen menu, the words dont get auto completed. This increases the number of taps/input strokes. Is the n97 intelligent & learn words from sms, contacts, emails. my blackberry does so. Request Know How & any options to edit custom dictionary. Auto Punctuation ? Am i expecting too much already ?
4. Single hand use of phone impractical using touch pad t9. Entering alphanumerics on the physical querty is a nightmare... Request Know how on tips & tricks.
5. Green tick yes or v button on top left of the text input screen. friendly again only for big handed people. Could this have been at bottom right. Is alternate screen for text input touch t9 available? Requested Know how.
6. Unnecessary taps additional taps alomost in all menus...for eg.. sending a biz card from n97 requires 5 taps... in the other mobile phone systems it can be done in 3 taps. Requested Knowhow for shortcuts.
7. Can In a nokia we get a view of the entire events as single thread.... No Provision for search display against keywords upon I can get call logs, messages - Here in Nokia, no search filters / advanced search and all searches results plotted to applications vs person/events. Requested Know How if it can be done like blackberry / windows mobile.
8. Copy & Paste across applications. eg. Select text from web page copy n paste on message application.... possible on Nokia...? Requested Know How
9. Call& Event Logs e.g Missed calls. If there are 5 missed calls the log will show the last called time only. In most other mobile systems Blackberry, windows each event is logged against a user. Requested know how on how this is handled in Nokia.
10. Lag in picture display upon call. Number displays first and after few seconds lag the pic pops up. Is this normal & acceptable ? Other windows / rim devices show it instantly.
11. When will Nokia enable usage of Native clients like google talk, yahoo like blackberry, iphone ? Any know how on possibility of release. Any equal alternatives suggested for n97. Tried Nimbuzz, Fring, Ebuddy. Miss the chat message notification icon on home screen, notification on the chat messaging icon, sound, breathing lights.
12. Is there any planning for better email client? Likely Release dates?
13. The Java App for GMAIL on blackberry shows an indicator on icon in addition to customised alert setting tone & breathing light for new messages. Retreiving Emails is consistent & auto on other devices. The Nokia Does not seem to auto refresh + No Notification. How is it handled on Nokia ?
14. Can user friendliness be something where we can do actions with a contact or on contacts screen single view... e.g see contact on google map, Help on contacts screen/n97 help, lookup contact on server, filter by category. new address, new group, view, edit, delete, activity log (incl sms, mms, email, calls), call, sms, mms, email, send as attachment, send as im, add a custom ring tone, add picture, options - sort by, separators, sync settings, actions, switch
applications, exit. We have seen it on inexpensive phones. is it possible to be done on Nokia?
SOME OF MY STILL UNRESOLVED PROBLEMS Post upgrade to ver 12. Did you also face similar bugs/issues?
15. Contacts inaccessible – “Memory Full Error”. No other applications were active at the time of the error. Just unable to reach any of my 3500 contacts through the contacts options & do anything.
16. Pbk2 error upon selecting contacts in the messaging application.
17. Audio Delay upon receiving a call. No Sound upon connection of incoming call. Especially if picked up too fast.
18. Shows as searching for network constantly many times a day. We have 2 n97s & observed that both n97 almost have similar timing of network loss. Whereas, our other devices like blackberry do not show any weak signal signs.
19. GPS Lock. Keeps searching for GPS locks constantly i.e Drops connection to GPS network frequently.
20. Unpredictive battery talk time, standby & required Charge time.
21. Voice inaudible at other end, when using loudspeaker & especially during calls from moving vehicle.
22. Camera:
a. Picture clarity issues. Secondary camera highly pixelated. Primary camera shows light flooding on pictures. Clarity Missing.
b. Erroneous Time stamp on images.
c.Lens Cover Started to show minor scratch pressure.
23. Ovi Suite recommends erroneous updates for E.g Maps 3
24. Text Input touch t9 screen freezes / Hangs, especially when entering special characters like period(.), comma(,), exclamation (!) etc
25. Selectively & at random contact Name not displayed on Caller ID (sometimes)
26. Selectively Message & Message delivery display number, instead of stored contact names.
27. Sync Issue, All contacts not synced always.
How to sync "categories" field as stored in outlook or how to map custom fields to Nokia.
28. Format Mass Memory error, Unable to format. Unable to delete specific files.
29. The auto lock... When attempted to unlock with querty out .. it still opens in portrait mode ?
30. SMS Logs Not updated. e.g any sms sent before storing a contact.... after storing or adding
contact the number does not get automatically updated to the name. It reflects the number still in the logs.
31. Picture caller... The face is half cut ..Looks weird on most images... as the number is not transparent. In landscape mode there is enough space on the screen to put up the answer or reject buttons and displaying the numbers.
32. Browser will close on its own & return to menu or home screen.
thanks in advance for your time to stop & read. Pls do send any information that you think will be useful to me for making the n97 do some work.
NEW additions:
(tested on another n97)
33. Predictive Text :
Usage for auto word completion only on physical keyboard, when the Dpad down key is used it throws up options but the way the scroll is designed you can see the full word and one makes mistakes.
34. another strange behaviour is on the text input... this was on an email i was trying to reply. the stylus touch will paste the last keyed in word !! we wonder why.
35. and while showing off the second n97 we have (again 3-4 weeks old) - we were asked how much did we pay for this second hand unit - 50% off .. apparently the comment as the surface has got scratched very badly.
i hope the info is good use to others who want to take the risk of buying this device

Are we Beta testing the N97 for Nokia?

Because if i was given this as a beta release i would have told them what i thought, the current launch version on the N97 with V10 firmware is barely an Alpha release, this phone was a rush job thrown out on the market to coincide with the launch of the iphone 3Gs.
This is my fourth N series, N80, N95, N95 8gb (the best N series yet), and now this N97 what should be Nokia's flagship, but being stripped of apps and filled with Trial versions to please the accountants at Nokia.
Day one and it locked up twice, corrupted my contacts when synced with OVI, and ran down to less than 4mb on the C drive, day 2 i found the GPS was not working, it was a joke, walking down the road under a clear sky and it could not hold a signal lock, driving was worse barely holding a signal for a few seconds and as for sitting spinning it round for an age to get the compass to work........forget it id rather be lost than look like a **bleep**.
Deleting apps and reinstalling them on the mass memory frees up some space, but why should we have to do this, the whole phone is badly thought out and configured.
Soon after the stylus supplied with the phone and attached to the phones only tie point scratched my screen, what was wrong with a rear cover with a bump and a thin PDA style stylus, no not good enough for Nokia, a fat thing on a string will do for them.
New Firmware release 4 days after UK launch and still not available to most users as it has not been network approved yet, 3 network say its Nokia's job and they are delaying things, Nokia say its the networks delay. Come on if it was needed that quickly why leave most of your customers waiting, or just get to work on a layered OS with a standardised core with a network layer, so everyone can have the updated without waiting.
4 weeks in on this phone, i too have the scratched camera lens, still No working GPS, and having some good negotiations with Three to try to reverse the contact upgrade, as i don't think another N97 will last any longer than this one.
I see Nokia spending Millions on punting the N97, TV, Billboards, Net adds, why push so hard on what is a sub standard product, could you imagine Joe public trying to free off some memory by moving apps, tell the care centres to brace themselves the N97 flood will be coming their way.
What next, well if 3 don't cancel the upgrade, then Nokia will have to fix my phone again and again and again untill it works as advertised, in the mean time i am off to get in touch with watchdog so they can let Joe Public know what to expect from an N97.
Rob
Solved!
Go to Solution.

I don't believe we're beta testing the N97 for Nokia. Beta testing suggests it is in a state prior to production. Nokia's track record (at least to me) seems that leading edge phones never reach a stable plateau.
What I believe happens is the phone is released and remains unstable until they sort of perfect the platform, then a new handset is released bringing a whole new world of bugs and problems and so the cycle continues.
By the time the phone is suitable for every day use it is, by today's technological stance, ancient and the damage has already been done to the reputation.
S40 phones seem to fare much better, mainly because it is much more widely used within Nokia. S60 is up against some fine competition from vendors who will rush fixes out.. Nokia only ever seems to rush phones out. It isn't the same and it shows (see their forcast for the next 6 months)
I honestly would not be surprised if this flagship phone limps on in a partially functional state until it is superceeded by a budget blackberry clone.
Sad? Very! Am I being cynical, or telling it like it is.
I'd be real interested to know if any exec at Nokia used the N97 in the weeks before it was released.. Not that I'm a fan, but we all know Stevie J used an iphone long before it was released.. I kind of get the impression they must all use very basic "corporate" s40 handsets and assume their flagship product must be of the same calibre.
Next release, why not give 100 people N97 for testing, real testing. It seems Nokias quality assurance team is out of touch with what a $700 handset demands.. ooooh, I gasp in awe at your 30 MB of free capactity when you remove ALL the applications you can. (It's like having a 2TB hard drive in a computer and continuing to boot from a floppy)
I appreciate there are product time lines to meet, but if Nokia were aiming to compete with the likes of the pre, iphone and the various android handsets (not even mentioning windows mobile) rushing out a phone like this was very wide of the mark. Concept wise, the N97 is a great design.. the implementation of both the hardware and software just isn't going to cut it in todays market..
(but this is what they want? you'll get bored with the handset and buy a replacement! yeay!)

Nokia c503 touchpad is slow and it freezes..

Hi since one month the touchpad of my nokia C503 is slow and it freezes.. it works for a while only if i hit a little bit the back of the mobile..! any of you have this kind of problem? is there a simple way to solve it? because i lost my warranty.. and if i keep it off the whole night and i turn it on, the mobile works fine but after some hours it becomes slow again..! if i may decide to send it to a nokia center it could even happen that an operator tries the mobile and sees that there are no problems..but it's nout true! you have to wait different hours to view the real problem..! T_T
i already tried soft reset, hard reset and calibration..!

Hi,
My position is almost same with some more or less problems.
I have my warranty upto 1st April,2012.
I had problems like
-Sudden switch off with red and green lines on screen
-Touch totally stops responding
-Sometimes when hanged not even able to switch it off using the button,forcing to open the battery and turn it on back
-recorded video play back stucks with boxes while playing
I complained regarding this several times to my nearest Nokia care centre.They made me run many times finally they sent to head office and said it is replaced.
BUT THE STORY STARTS NOW. EVEN NOW WHEN I GOT THE PIECE WITHIN 2-3DAYS, I AM FACING TOUCH RELATED PROBLEMS AND PHONE HANGS.
AS YOU SAID I EVEN CANT SHOW THEM ,BECAUSE IT JUST HAPPENS WHICH CANT BE OBSERVED AT A TIME BUT CAN BEEN EXPERIENCED ONLY WHILE CONTINUOUS USAGE.
AS ONE OF MY FRIEND HAS THE SAME PIECE WITH SAME PROBLEMS.
SO MY SINCERE REQUEST TO THE AUTHORITIES OF NOKIA,IF THEY CAN SEE THIS POST , PLEASE PLEASE RECTIFY THE PROBLEM,
AS IT MAY BE A BAD NAME TO THE COMPANY BECAUSE OF THIS ISSUE AND I DONT WANT IT TO BE.
HOPING YOU WILL DO THE NEED FUL.

NEW FW for Nokia 5800XM V51.0.006 (12/08/2010)

What are your experience from new FW?
Is our phones look better?
Have the last problems finished?
Are any bugs again?
Anything new and improved from the last better FW from the previous???
Don't forget:
Before put new update you have to make a hard format to your mobile and to your memory card!!!

First... i did not hard reseted ... not even soft reset it... however i can tell this:
Interface looks a bit more snappy...
RDS on radio seems to work.... BUT takes a lot of time (like 2~3mins - and don't touch the phone during that time) to catch station name (and before someone asks, i'm in a place where reception is quite good)... with version v21 was almost instantaneous (it took a bit of time but was like 10~20 seconds) ... also ... i managed to almost lockup/crash the phone with radio application... after around 1min it closed and went back to homescreen ... and i had to reboot the phone to make radio to work again ...
RDS seems to work .... but just sometimes
Another point on RDS is that bluetooth needs to be active for it to work.... i find it quite amusing *sarcasm* .... i don't know if this is really true.... but when it worked i had it on....
Radio is filled with bugs... i wonder if a hardreset will correct them, aside from what i've said, i also get the radio widget on homescreen even when radio was shutdown ...
The rotation of screen is now being detected correctly ... you now don't have to tilt the phone down to make it work... (the guy that changed calibration config for this on v50 should have been killed)
About free memory.... running Nokia's Energy Profile, after reboot,, it shows around 59Mb free of RAM ... a hard reset would be better to test this... :/ ... with old versions i got around 60Mb right after reboot so no huge improvement here
Camera quality is identical, no extra manual control over it either, it's not that bad as some people say, the 1/6" sensor does a great job for its size...
Please remember i did not hard reset (mainly because it is a pain to put everything there again), however some of the stuff doesn't require hard reset to be tested... i would love to hear about how radio is working from someone who had hard reset and waits a bit (5 mins?) with an RDS enabled station to see if it's working (also try with and without the bluetooth on, and with listed and non-listed station - listed has in saved)
Hope this helps someone
5800xm on a blender ... will happen sooner than expected.... v51 is a failure as an update .... v52 just postponed its fate....

Nokia C6- Touch Screen is not responding

Hi
I have bought a nokia c6-00 few month back.. from last two-three day, the touch screen of this cell is not working properlly..Even i have restarred mobile many time..some time is working..but within the second again faceing the same problem...
Is any one faceed this type of problem. is this a software or hardware proble..
it is very disappointng me..
Please have any solution for same..
Regards
shtru

Hi Shtru,
I will suggest you try and calibrate the device first by using the keypad, the steps to do this are as follows:
Menu > Settings > Phone > Touch input > Touch screen calibration. Follow the instructions on the screen.
This should address your issue.
If this post answers your question, you can help others by clicking the green accepted solution' button.
Please ask your questions to the main board and not to my mailbox. Thank you.

Replacement of 3 days old Nokia Lumia 720 manufact...

Nokia dealer sold me damaged mobile. I submitted my new device on 28th august for replacement to nokia care center but after 14 days they call me saying that my mobile is repaired. But i specifically said in complaint that i don't wan't my new device to be repaired, i need is replacement. I purchased it on 20th august & since 2nd day it started hanging that too continously & was unable to use it. On 23 i Visited nokia care center for replacement but they sais that it is just software problem. But they didn't got updated software so, they told me visit another nokia care center because we have two nokia care center in our city. but the working hours were about to finish. I visited them on monday i.e. on 25th august & they did software update. On the same day i found that problem was still there so i visited them back on next day but they didn't logged my complaint & kept my mobile without providing any job. They said to me that they want's to use my mobile so that they can see problem on their own. On next 27th they provide me new job sheet no. & took my mobile. & on 28 i logged another complaint on live chat for replacement & told them the whole story. & after that what happened i told you above. Please help me i this regards as soon as possible because i am using borrowed mobile which i have to give back soon or else i don't have any mobile to contact with. please help me...

Im sorry I dont know how to start a topic, hope you all dont mind but really need advice.
My boyfriend bought me a Nokia Lumia 720 for my birthday 6th of Sept this year. I had it only a week and when I dropped it and I smashed the screen. Instead of sending it nokia, I completely did the wrong thing and brought it to the local repair shop as I thought it would be done there and then and so the story begins.
The technician had a look at it and quoted 50 to 60 euro for a new screen as the LCD was still working, I said fine so he ordered the part in and let me use my phone till it came. Week or two later brought it up and he said it would be fixed within the hour. I came back only to be told he had trouble getting it apart and it would not be ready till the next day.
My boyfriend went up to get it the next day and he was told there was another problem, the screen and LCD were fused together so the technician said the part he got was no good that I need the two of them together and would be bout 90 euro. As the phone was in a million pieces I kinda didn't have a choice so told him that was fine and go ahead to order it.
Another week or two went and I got a phone call to say he could not get the part he wanted so he had to order the hole front of the phone and it would be now 150 for parts and labour. I gave the extra money as I was really fed up and just wanted my phone back that I barely used. I waited and waited and the part finally arrived around the 24 of Oct, I know because I was fuming it wouldn't be ready as I was going to England on the 27th Oct.
My boyfriend was in touch with them while i was away and it was suppose to be collected on the Saturday the 1st of November.I was really excited as I was coming home that night to my fixed phone but again it didn't happen.
The technician told my boyfriend (after staying an hour or so and been back and forth to the shop) that it was still calibrating and wouldn't be ready till Monday. Monday came and as I was working my boyfriend collected it, I finally had my phone but alas it was too good to be true. The camera was not working and when I got my boyfriend too ring me (when he was beside me) I could not hear a thing. On the Tuesday morning he brought it back and told him the issues, the technician was full of apologies and said he would have another look, he updated or restored the phone and told him to bring it home and when it finished what it was doing everything would be okay.
After the clogs on the screen went off I tried to switch it back on like the technition said but it never did, I even tried charging it but it was like it was dead nothing happened. I went straight back to the shop put it on the counter and told him to fix my phone that what ever he did its not working at all now. Again he was full of apologies and said he would take it home and see what he can do. My boyfriend rang a couple of days later and the technician said he is going to order a camera piece for it, I said I was not paying for it as the camera was working when we brought it up, he said he would "take the hit for it" and it will be 10 to 24 days delivery.
I rang and talked to the manager saying I wasnt happy, he was also full of appoligies and said he would have a look at it for me also. Never heard anything more from him like I was supposed to.
I got a phone call yesterday 2nd of January and the technician said the camera part was put in but it is still not working, he said there is nothing really more he can do. Im so upset because it was just a cracked screen everything else was working.
Long story short nearly 3 months and 150 euros later my phone is worse off than I left it in.
I need a little advise in what to do if he tries handing me back a broken phone. I am going to go to citizens information for legal advise but I also need some technical advise on this issue. Could it have been a faulty phone? Is everything that he has said about the parts true? Could he have broken the speaker and camera when he was trying to get the phone apart etc.
Sorry for the length of this, and if you could get back to me with some advise I would really appreciate it, thanks

Nokia 500 Problem with Tracking mode and touch sc...

Hi,
I just bought Nokia 500 and I am having lot of problem
1. When I use navigator..it should be in tracking mode not in browing mode so I can see where i am going on where is the turn. But as soon as it calculate the route, withing few second it automatically comes in browsing mode. Even if I press back arrow on left bottom corner it again shows browsing mode. However, sometime it's working fine and always display tracking mode. I am not sure how to switch between the mode. As per manual, I need to hit the back arrow left bottom corner but that does not work for me.
2. The second problem is really bad. The touchscreen response is slow. It looks like the processor is slow. Particularly if I go to Setup menu..it automatically goes to system. I just touch Setup on main menu and sometimes it automatically goes into system. If I manually go to system..it automatically goes to About ..menu. It just behaves randomly..I have done screen calibration many times. but still issue is there. Also, when I got to keyboard to enter address..it automatially press Q key. Not sure what's wrong here
Anybody please suggest me what's wrong. Do I need to replace it with nokia?

Hi
Night mode is designed to work without flash. So either use flash or night mode, but not both.
Cheers
Gryff
------ N78 -------

Nokia N8 reduce lower SAR value

Hi, I have noticed that nokia N8 has high SAR value of 1.02 W/kg when Samsung Galaxy 2 has SAR of 0.35 !
I did have not found any posts about bad reception quality on samsung, so why nokia choose so high SAR value??? My old N6680 has SAR of 0.64 and thats a phone I can use anywhere, elevators, bad receptions areas you name it.
So my quations is this:
How can I reduce - lower the SAR value of nokia N8 with service application or plugin whatever.
The Service manual for N8 uses software to test the transmitter with various levels of power settigns, so there should be a way to set lower power, that will increase battery life and you probably know WHO anounced that microwaves are cancerogenic don't you?
Attachments:
Nokia N8 reduce lower SAR.gif ‏53 KB

It is not quite as simple as that.
Phones always have to be below a particular SAR value, and depending on which part of the world you are in it is typically 2. That is already a very low level, so when you are comparing figures like 0.35 and 1.02 you are comparing two very small numbers below another small number that is already a threshold many times below which any harm would be caused.
You also should know that the figure quoted is the maximum for a range of different tests and conditions including against the head, body and hand and different channels and voice and data modes, also combined with WiFi etc..
All this means that in a typical situation when you are just making a phone call the SAR value in most phones is below than the figure quoted - although again you are still only comparing two very small numbers....
and the reason why Nokia doesn't allow you to change the power levels is that those are very carefully calibrated to meet the GSM and WCDMA standards otherwise the device would not be certified and allowed for sale, and would most likely not work....

Nokia drive 3.0 unable to sync favorites

Is there a way to sync Drive3.0 Favorites to Nokia account? If not how can I transfer favourites from Nokia Maps ?

It might be me, but if Nokia maps is installed on my Lumia 800 and the favourites are synced and stored on my phone, I would have thought Nokia Maps & Nokia Drive (both by Nokia) apps could access these synced favourites, after all what is the point on having to enter every destination for 'drive' when it's already stored by you in the 'maps' app. This does to things: 1. Annoys people having to enter things twice. 2. Wastes storage space on the phone (even though it might only be a small ammount). Also Nokia maps on my C6 seems more accurate, as I live at number 9 and my C6 says either 11 or 13, but Nokia Drive says number 24. Which is on the other side of the street and 5 houses away. Even my Garmin says number 11. It's. A pitty that all Satnav units and apps could not allow the user to calibrate then to there exact position. E.G. while outside our home, use a calibration option and press cursors until it shows the exact location. From then on everything should be correctly displayed.
Ish68
UK Vodafone - E72 - Code: 0590128 - FW (022.007)

Nokia 300 touch screen problems

hi , i have bought this nokia 300 recently and after just three months its touch screen is malfunctioning, the proble is that if u touch the left side if the screen the effect is visiblle on a little right side, not that exact point which i want to click. e.g if i touch alarm , it open calender, need help

uvijay wrote:
Nokia 300 touch is not working.I understand Nokia touch is not working properly for many people . But unfortunately we bought two touch models of Nokia both not working.
Hi uvijay,
Welcome to the forum.
Have you done calibrating the touchscreens of the two devices? Also, check if soft reset will fix your problem. You can do a soft reset by dialing *#7780#. After that you'll be asked to enter a lock code. Just enter 12345 if have not changed it. You can also do the steps advised by @ng85 (message no. 4) above.

Nokia c3-01 calibration!

Similar Messages

Maybe you are looking for