[QtMoko] SMS Service Center number
Hi, So it seems my problem with sending SMS messages has to do with using an incorrect SMS service number. I guess it is using one that is preset in the SIM? But it is incorrect. I've changed the number in Settings -> Call Options -> Service Numbers -> SMS Service Center, but it still doesn't work. It also resets whenever I restart QtMoko. So perhaps the Settings app is not setting the service center number properly. Can I set the number in a configuration file somewhere? Thanks, Bernie ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: [QtMoko] Error sending SMS (GTA02])
On 01/-9/-28163 05:59 AM, Radek Polak wrote: On Saturday 17 December 2011 22:44:36 Bernie Schelberg wrote: Hi, About two weeks ago, my GTA02 stopped sending SMS messages. I was running QtMoko v35 at the time, on a Kingston uSD card. Running dmesg while trying to send messages revealed this error: [ 4171.93] mmc0:0001: error -110 reading SDIO_CCCR_INTx Hi, have you tried running QtMoko from NAND? You can try various Settings- Logging->Categories and check /var/log/messages if something interesting shows up. Regards Radek Hmm... good suggestion about NAND. I have SHR installed in NAND and want to leave it there as a just-in-case alternative to QtMoko. Anyway, I booted it up, and tried to send a message from there, but it didn't work. I didn't get any error message, and I'm not so familiar with where the logs are on SHR, but the message wasn't received by the contact I sent it to. I didn't really know what Logging categories in QtMoko would be relevant, but I enabled all of them, and tried to send another message while tailing /var/log/messages. Here's a part that seems relevant: Dec 19 20:34:27 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 20:34:27 neo Qtopia: AtChat : T : "AT+CMGS=51" Dec 19 20:34:27 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 20:34:27 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 20:34:27 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 20:34:27 neo Qtopia: AtChat : T : "0011000B911664863221F3A82AE8340B747ED341ED3C088E7EBBCB20731A5F26BB5C20F4FB0EBA87E7203ABA0C9297CBE61F^Z" Dec 19 20:34:29 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 20:34:29 neo Qtopia: AtChat : F : "+CMS ERROR: 1" Dec 19 20:34:29 neo Qtopia: Messaging : transferFailure: "Send Failure" - "Error sending message: " Actually, I turned off logging categories except for those related to Modem usage, and tried again... the log segment is attached. I'm assuming that the line saying +CMS ERROR: 1 is the problem... it says that the number I'm trying to send to is unassigned, is that correct? I know that the numbers I'm trying to send to are valid - they're contacts I've messaged many times before. But there's something else not quite right - if I understand correctly, the AT+CMGS should specify the number to send to, but it has just 2 digits. It should have at least 10 for an Australian number, and that's not what I entered in the box in the SMS app. Although I've never looked at these logs when my phone was working correctly, so I'm not sure if the full number should appear there or not. Any more ideas? Bernie Dec 19 21:00:31 neo Qtopia: QTimeLine::start: already running Dec 19 21:00:34 neo last message repeated 2 times Dec 19 21:00:35 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 21:00:35 neo Qtopia: AtChat : T : "^Z" Dec 19 21:00:35 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 21:00:35 neo Qtopia: AtChat : W : "" Dec 19 21:00:35 neo Qtopia: AtChat : W : "OK" Dec 19 21:00:36 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 21:00:36 neo Qtopia: AtChat : T : "AT+CMGF=0" Dec 19 21:00:36 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 21:00:37 neo Qtopia: AtChat : F : "OK" Dec 19 21:00:37 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 21:00:37 neo Qtopia: AtChat : T : "AT+CMGS=17" Dec 19 21:00:37 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 21:00:37 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 21:00:37 neo Qtopia: AtChat : T : "0011000A81400111A804F4F29C0E^Z" Dec 19 21:00:37 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 21:00:37 neo Qtopia: AtChat : t : "AT+CSCB=0,"50"" Dec 19 21:00:37 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 21:00:37 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 21:00:37 neo Qtopia: AtChat : f : "AT+CSCB=0,"50"" Dec 19 21:00:37 neo Qtopia: AtChat : f : "OK" Dec 19 21:00:38 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 21:00:38 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 21:00:38 neo Qtopia: AtChat : F : "+CMS ERROR: 1" Dec 19 21:00:39 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 21:00:39 neo Qtopia: AtChat : T : "AT+CMGS=17" Dec 19 21:00:39 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 21:00:39 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::write() Dec 19 21:00:39 neo Qtopia: AtChat : T : "0011000A81400111A804F4F29C0E^Z" Dec 19 21:00:41 neo Qtopia: Mux : QGsm0710MultiplexerPrivate::read() Dec 19 21:00:41 neo Qtopia: AtChat : F :
[QtMoko] Error sending SMS (GTA02])
Hi, About two weeks ago, my GTA02 stopped sending SMS messages. I was running QtMoko v35 at the time, on a Kingston uSD card. Running dmesg while trying to send messages revealed this error: [ 4171.93] mmc0:0001: error -110 reading SDIO_CCCR_INTx Thinking that my uSD card had failed (I'd had it for just over a year), I bought another one (A-Ram), set up a fresh install of QtMoko, upgraded to v37, tried to send another message, and see the same error in dmesg. At this point I'm assuming it's not a fault of the uSD card. Is it hardware? There doesn't seem to be any problem writing to the uSD card... On fail of sending message, the message is moved into Drafts, which works nicely. Is it a problem with my SIM card? It's only about 5 months old. Are there any other logs I can look at to find out what's happening? Is this something I can fix in the software, or should I just get another phone for use until the GTA04 is released? Thanks, Bernie ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner doesn't boot properly after upgrading to QtMoko v31
Thanks Vincent, I had wondered if that was wrong when I checked with uname. Anyway, I just did another apt-get dist-upgrade, and it upgraded 3 more packages - qtmoko-kernel-images, qtmoko-kernel and qtmoko. This time it requested confirmation to change /boot/append-GTA02 which I'm sure it didn't do when I did the dist-upgrade yesterday. And my phone now boots properly!! Thanks, Bernie ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Freerunner doesn't boot properly after upgrading to QtMoko v31
Hi, I've been running QtMoko v26 from my uSD card (Kingston) more or less successfully. I wanted to upgrade to v31, so I added the qtmoko repository as per the instructions on the wiki, did an apt-get update and apt-get dist-upgrade. When I rebooted the phone, I get only a terminal login prompt. My dmesg log is attached. I noticed some glamo errors: [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x8120 [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x120 [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x8120 [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x120 So I tried changing the settings in the max_sd_clk file, and also tried the qi-31.udfu bootloader from the QtMoko Downloads, but neither seemed to make any difference. I found one message suggesting that the errors indicate the SD card is not inserted properly, so I removed and reinstalled it a number of times. It seems to me that if it's not installed properly, I get a kernel panic almost immediately, with an error message about not being able to sync the rootfs or something. What else can I try to get QtMoko up and running again without doing a fresh install? Thanks, Bernie [0.00] Linux version 2.6.29-rc3-v26 (ra...@rp-skunk) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 Sat Aug 28 13:11:14 CEST 2010 [0.00] CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177 [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine: GTA02 [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] On node 0 totalpages: 32768 [0.00] free_area_init_node: node 0, pgdat c03b3dc4, node_mem_map c0413000 [0.00] Normal zone: 256 pages used for memmap [0.00] Normal zone: 0 pages reserved [0.00] Normal zone: 32512 pages, LIFO batch:7 [0.00] CPU S3C2442B (id 0x32440aab) [0.00] S3C24XX Clocks, (c) 2004 Simtec Electronics [0.00] S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz [0.00] CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [0.00] Kernel command line: loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(qi),0x0004(depr-ub-env),0x0080(kernel),0x000a(depr),0x0004(identity-ext2),0x0f6a(rootfs) g_ether.host_addr=00:1F:11:01:A1:E3 g_ether.dev_addr=00:1F:11:01:A1:E3 root=/dev/mmcblk0p1 rootdelay=1 console=tty0 loglevel=3 rootdelay=1 [0.00] Unknown boot option `g_ether.host_addr=00:1F:11:01:A1:E3': ignoring [0.00] Unknown boot option `g_ether.dev_addr=00:1F:11:01:A1:E3': ignoring [0.00] RCU-based detection of stalled CPUs is enabled. [0.00] irq: clearing pending ext status 000b12f0 [0.00] irq: clearing pending ext status 000902d0 [0.00] irq: clearing subpending status 0180 [0.00] irq: clearing subpending status 0080 [0.00] PID hash table entries: 512 (order: 9, 2048 bytes) [0.00] timer tcon=, tcnt a2c1, tcfg 0200,, usec 1eb8 [21474536.48] Console: colour dummy device 80x30 [21474536.48] console [tty0] enabled [21474536.48] console [ttySAC2] enabled [21474536.48] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [21474536.48] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [21474536.495000] Memory: 128MB = 128MB total [21474536.495000] Memory: 125624KB available (3456K code, 533K data, 140K init) [21474536.495000] Calibrating delay loop... 199.47 BogoMIPS (lpj=498688) [21474536.595000] Mount-cache hash table entries: 512 [21474536.595000] CPU: Testing write buffer coherency: ok [21474536.60] net_namespace: 936 bytes [21474536.605000] regulator: core version 0.5 [21474536.605000] NET: Registered protocol family 16 [21474536.63] S3C Power Management, Copyright 2004 Simtec Electronics [21474536.63] modem wakeup interrupt [21474536.63] wake enabled for irq 17 [21474536.63] wake enabled for irq 49 [21474536.64] s3c24xx-adc s3c24xx-adc: attached adc driver [21474536.645000] S3C2442: Initialising architecture [21474536.645000] S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics [21474536.645000] DMA channel 0 at c8808000, irq 33 [21474536.645000] DMA channel 1 at c8808040, irq 34 [21474536.645000] DMA channel 2 at c8808080, irq 35 [21474536.645000] DMA channel 3 at c88080c0, irq 36 [21474536.645000] S3C244X: Clock Support, DVS off [21474536.72] bio: create slab at 0 [21474536.73] usbcore: registered new interface driver usbfs [21474536.73] usbcore: registered new interface driver hub [21474536.73] usbcore: registered new device driver usb [21474536.78] NET: Registered protocol family 2 [21474536.835000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [21474536.835000] TCP esta
