maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   N900 Microphone / Mic Issues: Dead on Arrival (DOA), Not Working, Intermittent Failures (https://talk.maemo.org/showthread.php?t=35075)

hypnotik 2009-11-25 15:51

Re: N900 no mic audio
 
I reread your post Venomrush:

I plugged my phone into the mains before turning on for the first time, and then let it charge for an hour and then went out for dinner and came back around 5 hours later and plugged it into mains again. My mic IS working fine.

Venomrush 2009-11-25 16:01

Re: N900 no mic audio
 
Quote:

Originally Posted by kalim13 (Post 391651)
is this confirmed. i still have to get home and open the box, if this is the case i will start my phone, drain the battery and than charge it.

thanks

Never drain the battery, ever.

bbrindle 2009-11-25 16:01

Re: N900 no mic audio
 
Mic still broken on mine after full re-install with Software Updater. Was worth a shot..

Venomrush 2009-11-25 16:02

Re: N900 no mic audio
 
Quote:

Originally Posted by hypnotik (Post 391663)
I reread your post Venomrush:

I plugged my phone into the mains before turning on for the first time, and then let it charge for an hour and then went out for dinner and came back around 5 hours later and plugged it into mains again. My mic IS working fine.

Yours is a US unit using 110v power sockets.

My post was really for EU chaps (UK to be more specific) with 220v power sockets.

Bratag 2009-11-25 16:03

Re: N900 no mic audio
 
Quote:

Originally Posted by bbrindle (Post 391698)
Mic still broken on mine after full re-install with Software Updater. Was worth a shot..

Hardware issue it would seem. Thats a bummer. Sorry.

hypnotik 2009-11-25 16:05

Re: N900 no mic audio
 
Quote:

Originally Posted by Venomrush (Post 391702)
Your is a US unit using 110v power socket.

My post was really for EU chaps with 220v power socket.

Yeah, 110v. Ah well, I'll never let me battery charge down anyway... super paranoid now. I may end up buying a spare battery to have for emergencies.

ninjaboxergirl 2009-11-25 16:07

Re: Microphone not working
 
Quote:

Originally Posted by maemoexperts (Post 391278)
Guys,

Received my N900 this morning (finally) but the microphone is not working ie. The other person on the call can not hear me.

Anyone have a similar problem or heard of this problem before ?? searched, but nothing.

To resolve Ive tried the following without any luck:-

- Flashed standalone
- Flashed NSU
- Call recorder software does not pickup anything up
- Phone works with headphones
- Mute / unmute doesnt do anything

Annoyed or what. Any suggestions ? Thanks

Just to point out- and I know this is VERY tenuous- but I have exactly this problem on my N95 as we speak and it suddenly went down week before last. A firmware update fixed it temporarily but it has gone again- just thought I'd throw that in for no reason.

Edit: and it shold be noted that sometimes its on outgoing calls, sometimes on in- and occasionally it actually works.

NvyUs 2009-11-25 16:07

Re: N900 no mic audio
 
i got mine today no problems did a couple of tests over network then tested with voice recorder app from extras

mikec 2009-11-25 16:14

Re: N900 no mic audio
 
Quote:

Originally Posted by bbrindle (Post 391698)
Mic still broken on mine after full re-install with Software Updater. Was worth a shot..

can you post the output of dmesg in a terminal after a fresh reboot.
It would be interesting to see if the system has some problems loading the driver for the mic.

huntr77 2009-11-25 16:15

Re: N900 no mic audio
 
Quote:

Originally Posted by Venomrush (Post 391696)
Never drain the battery, ever.

Can you qualify that Venonrush? Why would you not ever want to drain the battery? Surely with a battery that only lasts a day will run down completely several times a month by accident.

What good is a phone that you're constantly worried about having its battery drained? I'm confused...

Bratag 2009-11-25 16:15

Re: N900 no mic audio
 
Is there a maemo IRC channel or something - I just think it might be easier than growing threads exponentially.

Venomrush 2009-11-25 16:17

Re: N900 no mic audio
 
Quote:

Originally Posted by Bratag (Post 391732)
Is there a maemo IRC channel or something - I just think it might be easier than growing threads exponentially.

Yes
http://maemo.org/community/irc/

Maemo community on channel: #maemo
Server: irc.freenode.net

Stskeeps 2009-11-25 16:17

Re: N900 no mic audio
 
Quote:

Originally Posted by Bratag (Post 391732)
Is there a maemo IRC channel or something - I just think it might be easier than growing threads exponentially.

Yeah, many of us hang out on #maemo on irc.freenode.net. Keep the tone sober and non-trollish though :)

Bratag 2009-11-25 16:18

Re: N900 no mic audio
 
Danke. As soon as I have anything to contribute I will check it out.

Ulrik 2009-11-25 16:23

Re: N900 no mic audio
 
So the general advice is to charge the N900 to full before turning it on for the first time?

impatient 2009-11-25 16:25

Re: N900 no mic audio
 
Quote:

Originally Posted by Venomrush (Post 391617)
so far from what i can tell
people who are not having the mic issue did not charge their device before turning it on for the first time

I am sorry but I can't imagine there being any link between charging and failure of the mic.
Most people won't wait for the device to be charged before playing with it, nor should they.
If 90% of people don't wait before use and 2% of people have a failed mic there is a pretty good chance that the 2% of people with failures didn't charge their device, it does not prove a link.
I would have thought looking at whether the mic is properly detected with correct drivers loaded would be a good first step.
I would also say that if plugging in an external mic works then you have proved to some extent that the software is fine. I would guess that it might be a hardware problem. It may be a batch of microphone were used that were bad and that final pass out testing did not cover checking the microphone (quite likely I would have thought).

Perhaps if you can post up your serial numbers then someone at the factory can work out what hardware was put in these.

jackabite 2009-11-25 16:26

Re: N900 no mic audio
 
Quote:

Originally Posted by Ulrik (Post 391749)
So the general advice is to charge the N900 to full before turning it on for the first time?

Yup best to turn it upside and spin around three times whilst chanting maemo, maemo, maemo...

If it's a dud then it's a dud best to find out sooner rather than later!

sharper 2009-11-25 16:30

Re: N900 no mic audio
 
Quote:

Originally Posted by impatient (Post 391755)
It may be a batch of microphone were used that were bad and that final pass out testing did not cover checking the microphone (quite likely I would have thought).

If what people are saying about the driver not loading then it's fairly unforgivable for those units to have even made it out of the factory. Failures that can be detected in software are the easiest and most obvious ones, the microphone being a fairly critical component in the case of the N900.

bbin 2009-11-25 16:43

Re: N900 no mic audio
 
Quote:

If what people are saying about the driver not loading then it's fairly unforgivable for those units to have even made it out of the factory. Failures that can be detected in software are the easiest and most obvious ones, the microphone being a fairly critical component in the case of the N900.
damn you taiwanese... and Nokia! :D

sharper 2009-11-25 16:44

Re: N900 no mic audio
 
If only the community knew it could have written a "Check everything on your N900 works" app and had it in extras ready for release :D

mklass 2009-11-25 16:53

Re: N900 no mic audio
 
I have just opended mine an played with it for like 10 mins plugged charger in then made a call to test.... it worked fine :D

Venomrush 2009-11-25 17:00

Re: N900 no mic audio
 
Quote:

Originally Posted by impatient (Post 391755)
Perhaps if you can post up your serial numbers then someone at the factory can work out what hardware was put in these.

:confused:

pwannell 2009-11-25 17:15

Re: N900 no mic audio
 
suck suck sucks, whats the refund policy for a DOA?

MrGrim 2009-11-25 17:17

Re: N900 no mic audio
 
Quote:

Originally Posted by impatient (Post 391755)
Perhaps if you can post up your serial numbers then someone at the factory can work out what hardware was put in these.

That's actually not a bad idea. People with bad mics could post their S/N here to see if they're close => bad batch of phones. Or maybe there's another pattern (multiples of 13?)

bbin 2009-11-25 17:19

Re: N900 no mic audio
 
Quote:

That's actually not a bad idea. People with bad mics could post their S/N here to see if they're close => bad batch of phones. Or maybe there's another batch (multiples of 13?)
Not a bad idea at all. Especially if we could already spot some day of manufacturing.

RevdKathy 2009-11-25 17:21

Re: N900 no mic audio
 
Quote:

Originally Posted by mikec (Post 391727)
can you post the output of dmesg in a terminal after a fresh reboot.
It would be interesting to see if the system has some problems loading the driver for the mic.

Thanks for trying to solve this MikeC - I fear your post got lost in the distress.

Can you explain exactly the steps you are asking people to take to supply that information please: some folks here are new to all this. If you have a solution, you'll be the hero of the hour!

(Mine is ok, BTW)

bbrindle 2009-11-25 17:25

Re: N900 no mic audio
 
Here's my dmesg:

Code:

k quotas dquot_6.5.1
[    2.553924] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    2.555419] msgmni has been set to 479
[    2.555999] lowmem: Module initialized.
[    2.564483] alg: No test for stdrng (krng)
[    2.564636] io scheduler noop registered
[    2.565032] io scheduler cfq registered (default)
[    2.565429] OMAP DSS rev 2.0
[    2.565551] OMAP DISPC rev 3.0
[    2.565643] OMAP VENC rev 2
[    2.573486] OMAP3 ROM RNG: initializing
[    2.575683] Serial: 8250/16550 driver4 ports, IRQ sharing disabled
[    2.582305] brd: module loaded
[    2.584594] loop: module loaded
[    2.584686] i2c /dev entries driver
[    2.585845] input: triton2-pwrbutton as /class/input/input0
[    2.610870] triton2 power button driver initialized
[    2.611450] OneNAND driver initializing
[    2.612670] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base d0880000
[    2.612762] OneNAND Manufacturer: Samsung (0xec)
[    2.612792] Muxed OneNAND 256MB 1.8V 16-bit (0x40)
[    2.612823] OneNAND version = 0x0121
[    2.612854] Chip support all block unlock
[    2.612854] Chip has 2 plane
[    2.614471] Scanning device for bad blocks
[    2.732238] Creating 6 MTD partitions on "omap2-onenand":
[    2.732299] 0x00000000-0x00020000 : "bootloader"
[    2.732666] 0x00020000-0x00080000 : "config"
[    2.732940] 0x00080000-0x000c0000 : "log"
[    2.735443] mtdoops: Attached to MTD device 2
[    2.735504] 0x000c0000-0x002c0000 : "kernel"
[    2.735748] 0x002c0000-0x004c0000 : "initfs"
[    2.736083] 0x004c0000-0x10000000 : "rootfs"
[    2.738250] UBI: attaching mtd5 to ubi0
[    2.738311] UBI: physical eraseblock size:  131072 bytes (128 KiB)
[    2.738342] UBI: logical eraseblock size:    129024 bytes
[    2.738372] UBI: smallest flash I/O unit:    2048
[    2.738403] UBI: sub-page size:              512
[    2.738433] UBI: VID header offset:          512 (aligned 512)
[    2.738494] UBI: data offset:                2048
[    2.874420] UBI: attached mtd5 to ubi0
[    2.874481] UBI: MTD device name:            "rootfs"
[    2.874511] UBI: MTD device size:            251 MiB
[    2.874542] UBI: number of good PEBs:        2010
[    2.874572] UBI: number of bad PEBs:        0
[    2.874603] UBI: max. allowed volumes:      128
[    2.874633] UBI: wear-leveling threshold:    4096
[    2.874664] UBI: number of internal volumes: 1
[    2.874694] UBI: number of user volumes:    1
[    2.874725] UBI: available PEBs:            0
[    2.874755] UBI: total number of reserved PEBs: 2010
[    2.874786] UBI: number of PEBs reserved for bad PEB handling: 20
[    2.874816] UBI: max/mean erase counter: 7/3
[    2.874847] UBI: image sequence number: 2
[    2.875366] usbcore: registered new interface driver libusual
[    2.875488] mtdoops: Ready 0, 1
[    2.875518] UBI: background thread "ubi_bgt0d" started, PID 25
[    2.892669] input: omap_twl4030keypad as /class/input/input1
[    2.941223] cpuidle: using governor ladder
[    2.941284] cpuidle: using governor menu
[    2.941467] Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
[    2.941711] ASoC version 0.13.2
[    2.955322] AIC3X Audio Codec 0.2
[    2.957885] asoc: tlv320aic3x <-> omap-mcbsp-dai-0 mapping ok
[    2.959411] asoc: Bluetooth codec <-> omap-mcbsp-dai-1 mapping ok
[    3.011108] input: RX51 (tlv320aic3x) Jack as /class/input/input2
[    3.035339] ALSA device list:
[    3.035369]  #0: RX51 (tlv320aic3x)
[    3.035888] TCP cubic registered
[    3.035919] NET: Registered protocol family 17
[    3.035980] NET: Registered protocol family 15
[    3.036041] Power Management for TI OMAP3.
[    3.039428] pm_dbg_init()
[    3.040222] SmartReflex driver initialized
[    3.046875] Disabling unused clock "gpt2_ick"
[    3.046966] Disabling unused clock "gpt3_ick"
[    3.046997] Disabling unused clock "gpt4_ick"
[    3.047027] Disabling unused clock "gpt5_ick"
[    3.047088] Disabling unused clock "gpt6_ick"
[    3.047119] Disabling unused clock "gpt7_ick"
[    3.047149] Disabling unused clock "gpt8_ick"
[    3.047180] Disabling unused clock "gpt9_ick"
[    3.047210] Disabling unused clock "uart3_ick"
[    3.047271] Disabling unused clock "gpio2_dbck"
[    3.047302] Disabling unused clock "gpio3_dbck"
[    3.047332] Disabling unused clock "gpio4_dbck"
[    3.047363] Disabling unused clock "gpio5_dbck"
[    3.047393] Disabling unused clock "gpio6_dbck"
[    3.047424] Disabling unused clock "gpt9_fck"
[    3.047485] Disabling unused clock "gpt8_fck"
[    3.047515] Disabling unused clock "gpt7_fck"
[    3.047546] Disabling unused clock "gpt6_fck"
[    3.047576] Disabling unused clock "gpt5_fck"
[    3.047607] Disabling unused clock "gpt4_fck"
[    3.047637] Disabling unused clock "gpt3_fck"
[    3.047668] Disabling unused clock "gpt2_fck"
[    3.047729] Disabling unused clock "uart3_fck"
[    3.047760] Disabling unused clock "wdt2_ick"
[    3.047790] Disabling unused clock "wdt2_fck"
[    3.047821] Disabling unused clock "gpio1_dbck"
[    3.047882] Disabling unused clock "rng_ick"
[    3.047912] Disabling unused clock "ssi_ick"
[    3.047943] Disabling unused clock "gpt10_ick"
[    3.047973] Disabling unused clock "gpt11_ick"
[    3.048034] Disabling unused clock "uart1_ick"
[    3.048065] Disabling unused clock "uart2_ick"
[    3.048095] Disabling unused clock "usbtll_ick"
[    3.048126] Disabling unused clock "ssi_ssr_fck"
[    3.048187] Disabling unused clock "uart1_fck"
[    3.048217] Disabling unused clock "uart2_fck"
[    3.048278] Disabling unused clock "usbtll_fck"
[    3.048400] Disabling unused clock "ts_fck"
[    3.048431] Disabling unused clock "cpefuse_fck"
[    3.048492] Disabling unused clock "gpt11_fck"
[    3.048522] Disabling unused clock "gpt10_fck"
[    3.048553] Disabling unused clock "dpll5_ck"
[    3.048614] Disabling unused clock "dpll4_m6x2_ck"
[    3.048675] Disabling unused clock "dpll4_m5x2_ck"
[    3.048706] Disabling unused clock "dpll3_m3x2_ck"
[    3.048736] Disabling unused clock "sys_clkout1"
[    3.049133] Bootup reason: pwr_key
[    3.049224] OMAP GPIO switch handler initializing
[    3.051727] slide (GPIO 71) is now open
[    3.051788] proximity (GPIO 89) is now open
[    3.051818] kb_lock (GPIO 113) is now open
[    3.051849] headphone (GPIO 177) is now disconnected
[    3.051879] cam_shutter (GPIO 110) is now closed
[    3.051910] cam_launch (GPIO 69) is now inactive
[    3.051940] cam_focus (GPIO 68) is now inactive
[    3.051971] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
[    3.064239] omapfb: acx565akm rev 8b LCD detected
[    3.071472] tpa6130a2 2-0060: Headphone amplifier initialized successfully
[    3.117706] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    3.117767] UBIFS: file system size:  254822400 bytes (248850 KiB, 243 MiB, 1975 LEBs)
[    3.117828] UBIFS: journal size:      9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[    3.117889] UBIFS: media format:      4 (latest is 4)
[    3.117919] UBIFS: default compressor: lzo
[    3.117950] UBIFS: reserved for root:  4384586 bytes (4281 KiB)
[    3.118469] VFS: Mounted root (ubifs filesystem).
[    3.118774] Freeing init memory: 144K
[    4.601104] Registered led device: twl4030:vibrator
[    4.746398] twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
[    4.828094] tsl2563 2-0029: model 7, rev. 0
[    4.887847] lp5523 2-0032: LP5523 Programmable led chip found
[    4.988220] Linux video capture interface: v2.00
[    5.056274] I2C driver for Si4713 FM Radio Transmitter
[    5.833007] Bluetooth: Core ver 2.15
[    5.839660] NET: Registered protocol family 31
[    5.839691] Bluetooth: HCI device and connection manager initialized
[    5.839752] Bluetooth: HCI socket layer initialized
[    5.884399] i2c_omap i2c_omap.2: controller timed out
[    5.903808] hci_h4p hci_h4p: Registering HCI H4P device
[    5.942108] lp5523 2-0032: got interrupt from led chip
[    5.942657] lp5523 2-0032: interrupt from led chip 4f
[    5.942687] lp5523 2-0032: all engines configured
[    5.942718] lp5523 2-0032: disabling engines
[    5.943328] Registered led device: lp5523:kb1
[    5.943481] Registered led device: lp5523:kb2
[    5.943603] Registered led device: lp5523:kb3
[    5.943756] Registered led device: lp5523:kb4
[    5.943908] Registered led device: lp5523:b
[    5.944030] Registered led device: lp5523:g
[    5.944183] Registered led device: lp5523:r
[    5.944305] Registered led device: lp5523:kb5
[    5.944458] Registered led device: lp5523:kb6
[    6.016662] nokia-av nokia-av: accessory detect module initialized
[    6.026336] radio-si4713 2-0063: Detected Si4713 (0x0d) Firmware: 3.0 Patch ID: 00:00 Component: 3.0 Chip Rev.: unknown
[    6.085113] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
[    6.128509] TSC2005 driver initializing
[    6.129211] input: TSC2005 touchscreen as /class/input/input3
[    6.220855] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
[    6.377288] omap_wdt omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec, nowayout is on
[    6.390777] SSI DRIVER Version 1.1-rc2
[    6.391265] omap_ssi omap_ssi: SSI Hardware REVISION 1.0
[    6.487884] phy0: Selected rate control algorithm 'minstrel'
[    6.521759] smc91x: not found (-19).
[    6.533386] wl1251: loaded
[    6.534118] wl1251: initialized
[    6.644256] mmc1: new high speed MMC card at address 0001
[    6.650482] mmcblk0: mmc1:0001 MMC32G 29.8 GiB
[    6.650787]  mmcblk0: p1 p2 p3
[    6.902954] CMT speech driver v0.2.0
[    6.920043] NET: Registered protocol family 35
[    6.952606] SSI McSAAB PROTOCOL Version: 2.0-rc1
[    7.213653] dspbridge_init: 412800 bytes @ 80600000
[    7.301361] omap-iommu omap-iommu.1: isp registered
[    7.472473] omap-iommu omap-iommu.1: isp: version 1.1
[    7.629333] smia-sensor 2-0010: firmware: requesting smia-sensor-01-022b-04.bin
[    7.655975] smia_reglist_import: meta_reglist version 2009-07-27
[    7.656066] smia_reglist_import: type 10        w 648        h 488        fmt 30314142        ival 100/1502        ptr d0c392a0
[    7.656066] smia_reglist_import: type 10        w 648        h 488        fmt 30314142        ival 100/3003        ptr d0c39228
[    7.656097] smia_reglist_import: type 1        w 0        h 0        fmt 30314142        ival 100/0        ptr d0c39090
[    7.656127] smia_reglist_import: type 0        w 0        h 0        fmt 30314142        ival 100/0        ptr d0c39038
[    7.666992] et8ek8 3-003e: firmware: requesting et8ek8-0002.bin
[    7.691497] smia_reglist_import: meta_reglist version V14 03-June-2008
[    7.691558] smia_reglist_import: type 10        w 2592        h 1968        fmt 30314442        ival 100/1292        ptr d0c3c1f4
[    7.691589] smia_reglist_import: type 10        w 2592        h 1968        fmt 30314142        ival 100/399        ptr d0c3c454
[    7.691619] smia_reglist_import: type 10        w 1296        h 984        fmt 30314142        ival 100/501        ptr d0c3c57c
[    7.691619] smia_reglist_import: type 10        w 1296        h 984        fmt 30314442        ival 100/2500        ptr d0c3c614
[    7.691650] smia_reglist_import: type 10        w 1296        h 984        fmt 30314442        ival 100/3000        ptr d0c3c28c
[    7.691680] smia_reglist_import: type 10        w 864        h 656        fmt 30314142        ival 100/2988        ptr d0c3c324
[    7.691680] smia_reglist_import: type 10        w 648        h 492        fmt 30314142        ival 100/499        ptr d0c3c4e4
[    7.691711] smia_reglist_import: type 10        w 648        h 492        fmt 30314142        ival 100/2993        ptr d0c3c3bc
[    7.691711] smia_reglist_import: type 1        w 2592        h 1968        fmt 30314142        ival 100/1207        ptr d0c3c04c
[    8.315582] g_file_storage gadget: File-backed Storage Gadget, version: 7 August 2007
[    8.315643] g_file_storage gadget: Number of LUNs=2 Number of buffers=16
[    8.315704] musb_hdrc musb_hdrc: MUSB HDRC host driver
[    8.316284] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[    8.316741] usb usb1: configuration #1 chosen from 1 choice
[    8.316955] hub 1-0:1.0: USB hub found
[    8.317047] hub 1-0:1.0: 1 port detected
[  14.849426] kjournald starting.  Commit interval 1 seconds
[  14.860595] EXT3 FS on mmcblk0p2, internal journal
[  14.860626] EXT3-fs: mounted filesystem with writeback data mode.
[  15.260711] Adding 786424k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 across:786424k
[  15.486511] McSAAB: ACWAKE DOWN
[  15.486572] McSAAB: ACWAKE UP
[  15.486663] McSAAB: WAKELINES TEST OK
[  15.822204] Bluetooth: L2CAP ver 2.13
[  15.822235] Bluetooth: L2CAP socket layer initialized
[  15.923706] Bluetooth: SCO (Voice Link) ver 0.6
[  15.923736] Bluetooth: SCO socket layer initialized
[  15.927551] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
[  16.461975] Bluetooth: RFCOMM socket layer initialized
[  16.462066] Bluetooth: RFCOMM TTY layer initialized
[  16.462097] Bluetooth: RFCOMM ver 1.11
[  20.272705] misc iphb: Module registered in 2.6.28-omap1, built Oct 28 2009 15:33:55
[  40.269561] warning: `dnsmasq' uses 32-bit capabilities (legacy support in use)
[  45.780883] cfg80211: Regulatory domain changed to country: US
[  45.780944]        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  45.780944]        (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[  45.780975]        (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[  45.780975]        (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[  45.781005]        (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[  45.781005]        (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[  45.781036]        (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[  47.212860] wl12xx spi4.0: firmware: requesting wl1251-fw.bin
[  48.368927] wl1251: 154 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[  48.384552] wl1251: firmware booted (Rev 6.0.4.156)
[  49.153106] SCSI subsystem initialized
[  49.485717] Driver 'sd' needs updating - please use bus_type methods
[  49.979003] wl1251: down
request


MrGrim 2009-11-25 17:26

Re: N900 no mic audio
 
Quote:

Originally Posted by RevdKathy (Post 391856)
Can you explain exactly the steps you are asking people to take to supply that information please: some folks here are new to all this. If you have a solution, you'll be the hero of the hour!

Not wanting to steal MikeC's glory for his contribution, here's how to get dmesg output:
*open terminal (yup, no other option that i know of)
*type "dmesg" (no quotes)
*copy+paste
If the output seems enormous, try "dmesg | tail" to leave just the most recent (that's a straight bar, no quotes)

mikec 2009-11-25 17:31

Re: N900 no mic audio
 
looking at the dmesg seems to imply the driver is loading compared to a known good unit. prob means a duf mic.

The driver is linked to the bluetooth, so maybe something strange there. can you have a play with turning the bluetooth on and off and see if makes a diff.

noobmonkey 2009-11-25 18:02

Re: N900 no mic audio
 
Few intruiging bits, assume they dont mean much?

[ 6.085113] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock

[ 6.220855] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock

[ 6.521759] smc91x: not found (-19).

[ 45.780883] cfg80211: Regulatory domain changed to country: US
(Isn't this a UK device?)

[ 49.485717] Driver 'sd' needs updating - please use bus_type methods
(interesting!)

Just a few lines - anyone in know, know? :)

dnastase 2009-11-25 18:05

Re: N900 no mic audio
 
Quote:

Originally Posted by mikec (Post 391885)
looking at the dmesg seems to imply the driver is loading compared to a known good unit. prob means a duf mic.

The driver is linked to the bluetooth, so maybe something strange there. can you have a play with turning the bluetooth on and off and see if makes a diff.

lsmod would list the loaded drivers, it would confirm the driver is loaded properly.

mikec 2009-11-25 18:08

Re: N900 no mic audio
 
Here is dmesg from good unit from the summit

http://pastebin.ca/1610167

mikec 2009-11-25 18:10

Re: N900 no mic audio
 
Quote:

Originally Posted by dnastase (Post 391956)
lsmod would list the loaded drivers, it would confirm the driver is loaded properly.

do we know the name of the driver?

nuknuk 2009-11-25 18:26

Re: N900 no mic audio
 
Anyone have any clues to this MAJOR problem yet.

Bratag 2009-11-25 18:33

Re: N900 no mic audio
 
The problem is that even if the hardware was faulty - the driver could still load. It really would help to see if the serials on the units were part of a batch.

dnastase 2009-11-25 18:36

Re: N900 no mic audio
 
Nope, sorry, I can't seem to figure out the audio driver name.

.....


Well, if you would see that the driver doesn't load then you would be able to draw a conclusion... if the driver loads then I agree, no conclusion can be drawn.

TA-t3 2009-11-25 18:42

Re: N900 no mic audio
 
Thanks for starting this thread - it's something that DDP orderers will have to remember checking quickly (due to the one-week return policy).

Quote:

Originally Posted by Ulrik (Post 391749)
So the general advice is to charge the N900 to full before turning it on for the first time?

Yes.
It's highly unlikely that charging like described above will have anything to do with the failed mic. But as you won't know the state of the battery when you receive the N900 you should start with charging it. If you're impatient you could power it up after half an hour and continue charging, but you should avoid powering it on first thing. If you're unlucky you may suddenly have a completely empty battery and then you will not be able to charge the device - it needs to be able to boot to its "charge mode" because the charging is managed by software. And it's always powered through the battery, even when plugged in. A dead battery is a catch-22.

And to the other poster: It's very bad for the battery to do a deep discharge. If it needs to be charged often, charge it often. Every accidental discharge-till-it-turns-off will reduce the capacity and lifetime of the battery. This is how it is with lithium-ion and lithium-polymer batteries.

kwotski 2009-11-25 18:44

Re: N900 no mic audio
 
To see the audio driver, couldn't you just do:

lsmod | grep snd

and

cat /proc/asound/cards

?

mikec 2009-11-25 18:53

Re: N900 no mic audio
 
Quote:

Originally Posted by nuknuk (Post 391996)
Anyone have any clues to this MAJOR problem yet.

nuknuk there are two tracks here

1. it would be useful to see your serial numbers
2. we trying to see if your sound driver is loading to isolate if its a hardware or software problem. Would you know how to get into the terminal ? and run some of the proposed commands :-

Cat /proc/asound/devices

MrGrim 2009-11-25 19:02

Re: N900 no mic audio
 
I seriously don't think this is software. We'll need someone from nokia to confirm, but i think the headset mic and the embedded one use the same hardware from some point on, which implies the same software too. Are there separate controls for headset and embedded mic ?
If they do use the same path, it becomes obvious that it's just faulty hardware
EDIT: could people please start posting serial numbers?


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

vBulletin® Version 3.8.8