On 9/1/10, Al Johnson <[email protected]> wrote: > I don't expect the bootloader to make a difference either. I have had > occasions with current shr-u and qi where I have failed to get a fix > quickly, > given up and closed the app, removed the agps data and restarted the app, > and > got a fix quickly. It usually happens when I'm out walking somewhere with a > poorish sky view somewhere unsuitable for debugging... > >> Can someone with Qi show me the >> value of his /proc/cmdline? With my u-boot it is this: >> >> rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 >> console=tty0 loglevel=4 regular_boot >> mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u- >> boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0 >> 000(rootfs) > > r...@om-gta02 ~ # cat /proc/cmdline > loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro > mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(qi),0x00040000(depr-ub- > env),0x00800000(kernel),0x000a0000(depr),0x00040000(identity- > ext2),0x0f6a0000(rootfs) root=/dev/mmcblk0p1 rootdelay=1 loglevel=1 quiet > splash > r...@om-gta02 ~ # cat /boot/append-GTA02 > loglevel=1 quiet splash > _______________________________________________ > Shr-User mailing list > [email protected] > http://lists.shr-project.org/mailman/listinfo/shr-user >
I made a test yesterday. I flashed the current SHR-U image. After booting gps worked fine. After a suspend it didn't work (time stayed at 1970). After a reboot I instantly got a fix. I also have an old SHR-U from 04/2010 which is working fine (both on uSD) a cat of cmdline of a qi would be interesting (there should be enough people out there with it :) _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
