Re: [debian] experimentation with ofono, telepathy-ring and empathy...
Hi, On Thu, Dec 16, 2010 at 01:53:59PM +, Neil Jerram wrote: I thought this worth mentioning just in case others are doing similar things: I'm experimenting with the stack mentioned in the Subject, on my debian install, to see what kind of UI it gives, and how stable the telephony is. Can you elaborate on how you approached that issue so that others can reproduce your findings? cheers, josch ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qi: use \r\n in serial console?
Hi,
if I use picocom -b 115200 /dev/ttyUSB0 to see the boot messages of Qi
and kernel I see that the Qi lines are terminated with \n while Linux
uses \r\n [1].
Are you using something else than picocom or avoiding the problem in
some other way? If not, should it be fairly safe to add
diff --git a/src/cpu/s3c2442/gta02.c b/src/cpu/s3c2442/gta02.c
index 13be2ac..6dc1208 100644
--- a/src/cpu/s3c2442/gta02.c
+++ b/src/cpu/s3c2442/gta02.c
@@ -458,6 +458,8 @@ const struct board_variant const *
get_board_variant_gta02(void)
static __attribute__ (( section (.steppingstone) )) void
putc_gta02(char c)
{
+ if (c == '\n')
+ serial_putc_s3c24xx(GTA02_DEBUG_UART, '\r');
serial_putc_s3c24xx(GTA02_DEBUG_UART, c);
}
or is there some trouble to be expected?
best regards,
Timo Lindfors
[1] Example output:
Qi Bootloader s3c2442 wallwart debian_20100105-1~unrelease0
2011-06-06T08:29:17+ Copyright (C) 2008 Openmoko,
Inc.
Detected: Freerunner / GTA02, A6 PCB
Battery condition reasonable
Trying kernel: SD Card EXT2 P1 Kernel
Card Type: SD
2.0 SDHC / Mfr: 0x02, OEM TM / SA08G, rev 0.6 / s/n: 576236754 / date:
12/2010
SDHC size: 7592 MiB
Partition: 1 start +52 512-byte blocks, size 16 MiB
EXT2 open: boot/noboot-GTA02 Open failed
EXT2 open: boot/append-GTA02 OK
EXT2 open: boot/uImage-GTA02.bin OK
Found: 3f4c7e4fa3d937a8
Size: 1726 KiB
EXT2 open: boot/uImage-GTA02.bin
OK
** skipping
Read failed
bad magic 66346537
Trying kernel: SD Card EXT2 P2 Kernel
Partition: 2 start +33072 512-byte blocks,
size 3867 MiB
EXT2 open: boot/noboot-GTA02 Open failed
EXT2 open: boot/append-GTA02 OK
EXT2 open: boot/uImage-GTA02.bin
OK
Found: Debian FreeRunner Kernel
Size: 2148 KiB
EXT2
open: boot/uImage-GTA02.bin OK
Cmdline: 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.dev_addr=00:1F:11:01:62:8A g_ether.host_addr=00:1F:11:01:62:8B
root=/dev/mmcblk0p2 rootdelay=1 rootdelay=1 c8008080, irq 35
[
Re: battery life with QtMoko
I've started to keep NeoControl running all the time. With my deepsleep/fixed phone, on resume I see the current between 12000-24000 (2.6.34/qtmoko). With my old battery showing 857000 for current full, I guess it could sleep between 35 and 72 hours. The problem is that when active, the current is between 25-35, about 2.5-3.5 hours. If I keep the screen on (talking or not) for 20-30 minutes, which is not uncommon, I have no chance to use the phone the next day without charging it. This is with default settings, which are very dangerous: in power management, when not plugged, the policy for 'dim light' is off, for 'display off' is off and for 'suspend' is off. This means that any unnoticed sms or missed call will keep the screen on. I can change these settings, but it bothers me that any event will unlock the screen, the neo can make phone calls in my pocket or the touchscreen will stay active while walking with no chance to autosuspend. On 6/9/11, Christoph Pulster openm...@pulster.de wrote: Does anybody has flashed the latest QtMoko and can report something about battery standby time ? I remember Radek mention a serious improvment. thanks, Chris ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qi: use \r\n in serial console?
Am 23.06.2011 14:15, schrieb Timo Juhani Lindfors: Hi, if I use picocom -b 115200 /dev/ttyUSB0 to see the boot messages of Qi and kernel I see that the Qi lines are terminated with \n while Linux uses \r\n [1]. I don't know picocom but Linux normally uses \n while windows uses \r\n. So if qi only use \n it is corrrect for linux. Ciao, Rainer ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] experimentation with ofono, telepathy-ring and empathy...
Hi Johannes, On 23 June 2011 12:24, Johannes Schauer j.scha...@email.de wrote: Hi, On Thu, Dec 16, 2010 at 01:53:59PM +, Neil Jerram wrote: I thought this worth mentioning just in case others are doing similar things: I'm experimenting with the stack mentioned in the Subject, on my debian install, to see what kind of UI it gives, and how stable the telephony is. Can you elaborate on how you approached that issue so that others can reproduce your findings? Unfortunately I no longer have the details to refer to. But as far as I recall, it was something like... - Install oFono. It was 0.36 at the time, and it looks like that's still the latest in Debian, even though I believe upstream has had several releases since that. - Start ofonod, then play with test scripts like `list-modems' and `enable-modem'. - Discover that nothing happens because calypso hasn't been detected. I wrote a patch to fix that, and sent it to the oFono guys. AFAIK that is in the upstream code now, so a more recent oFono release should detect calypso out of the box. - `list-modems' and `enable-modem' now work. - Install telepathy-ring and empathy, and see what happens - and I wrote about that earlier (but a long time ago) in this same thread. Does that help? Please feel free to ask more detailed questions, and I'll do my best! Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: battery life with QtMoko
On Thursday 23 June 2011 20:46:10 Noel wrote: This is with default settings, which are very dangerous: in power management, when not plugged, the policy for 'dim light' is off, for 'display off' is off and for 'suspend' is off. This means that any unnoticed sms or missed call will keep the screen on. I can change these settings, but it bothers me that any event will unlock the screen, the neo can make phone calls in my pocket or the touchscreen will stay active while walking with no chance to autosuspend. If you lock the screen it should always suspend after 20s. I am using QtMoko with default values and i has worked quite nice so far and on the other hand i am not bothered with screen dimming e.g. when reading or playing chess. It's quite hard/impossible to set defaults so that everyone is happy. But any suggestions are welcome. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
