Re: First impressions on new Android rootfs
Rui, This looks really bazaar. What version of hardware do you have? Have you updated the GSM firmware? The initial chat should look like: D/AT ( 2004): CHAT AT-Command Interpreter ready D/AT ( 2004): CHAT ATZ D/AT ( 2004): CHAT ATZ D/AT ( 2004): CHAT OK D/AT ( 2004): CHAT ATE0Q0V1 D/AT ( 2004): CHAT ATE0Q0V1 D/AT ( 2004): CHAT OK D/AT ( 2004): CHAT AT+CMUX=1,0,5,128 D/AT ( 2004): CHAT OK D/AT ( 2004): Control channel opened D/AT ( 2004): Logical channel 1 opened D/AT ( 2004): MUX[1] AT D/AT ( 2004): Modem status command on channel 1 D/AT ( 2004): No frames allowed D/AT ( 2004): Command acknowledged by the mobile station D/AT ( 2004): MUX[1] AT-Command Interpreter ready D/AT ( 2004): MUX[1] OK D/AT ( 2004): MUX[2] AT D/AT ( 2004): Logical channel 2 opened D/AT ( 2004): Modem status command on channel 2 D/AT ( 2004): No frames allowed D/AT ( 2004): MUX[2] AT-Command Interpreter ready D/AT ( 2004): Command acknowledged by the mobile station D/AT ( 2004): MUX[2] AT D/AT ( 2004): MUX[2] OK D/RIL ( 2004): Connecting GPRS channel to tty /dev/pts/1 D/AT ( 2004): MUX[1] ATE0Q0V1 Note that yours doesn't go into mux mode and the chat seems out of sync. I've bumped up the timeouts on the chat. Can you place the attached file into /system/lib on your phone? I'm not sure how easy that will be for you as adb lets you remount /system but for us it isn't a filesystem. :( Rui Castro wrote: Hi, great, the kill-server command did the trick. Here's my radio logcat. On Fri, Dec 5, 2008 at 2:37 AM, Sean McNeil s...@mcneil.com wrote: Rui Castro wrote: Hi, With the current kernel and jffs2 image, my GSM network is never available. I can't produce the radio log because I can't get adb to connect to neo! It shows - waiting for device - all the time. Hmm... Can you ping the phone? Sometimes an old server for adb gets left laying around and you need to do a ADBHOST=neo ./adb kill-server to clear it out. On Fri, Dec 5, 2008 at 2:11 AM, Sean McNeil s...@mcneil.com wrote: Looks like no response from the modem. Perhaps there is an issue with turning it on. I've seen this happen here on occasion and a reboot resolves it. Cédric Berger wrote: On Thu, Dec 4, 2008 at 05:35, Sean McNeil s...@mcneil.com wrote: Can you send me the output of ADBHOST=neo ./adb logcat -b radio No GSM for me either. And SIM contacts import fails too (says no contacts on SIM). (I aso tried in settings to register to networks, but it already was failing with previous images) adb logcat -b radio : I/RIL ( 857): Opening tty device /dev/s3c2410_serial0,115200 I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT-Command Interpreter ready D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT AT+CMUX=1,0,5,128 D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT OK D/RIL ( 857): Connecting GPRS channel to tty /dev/pts/0 E/RIL ( 857): Error creating PPP options file: /data/ppp/options.gprs. D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): Re-opening after close I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): CHAT ATZ D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857):
Re: First impressions on new Android rootfs
Hi, I just received this message today. I didn't update the GSM firmware. I'm compiling the android root filesystem again from the updated koolu repository and I will compare the radio log with yours. Rui On Fri, Dec 5, 2008 at 3:10 AM, Sean McNeil s...@mcneil.com wrote: Rui, This looks really bazaar. What version of hardware do you have? Have you updated the GSM firmware? The initial chat should look like: D/AT ( 2004): CHAT AT-Command Interpreter ready D/AT ( 2004): CHAT ATZ D/AT ( 2004): CHAT ATZ D/AT ( 2004): CHAT OK D/AT ( 2004): CHAT ATE0Q0V1 D/AT ( 2004): CHAT ATE0Q0V1 D/AT ( 2004): CHAT OK D/AT ( 2004): CHAT AT+CMUX=1,0,5,128 D/AT ( 2004): CHAT OK D/AT ( 2004): Control channel opened D/AT ( 2004): Logical channel 1 opened D/AT ( 2004): MUX[1] AT D/AT ( 2004): Modem status command on channel 1 D/AT ( 2004): No frames allowed D/AT ( 2004): Command acknowledged by the mobile station D/AT ( 2004): MUX[1] AT-Command Interpreter ready D/AT ( 2004): MUX[1] OK D/AT ( 2004): MUX[2] AT D/AT ( 2004): Logical channel 2 opened D/AT ( 2004): Modem status command on channel 2 D/AT ( 2004): No frames allowed D/AT ( 2004): MUX[2] AT-Command Interpreter ready D/AT ( 2004): Command acknowledged by the mobile station D/AT ( 2004): MUX[2] AT D/AT ( 2004): MUX[2] OK D/RIL ( 2004): Connecting GPRS channel to tty /dev/pts/1 D/AT ( 2004): MUX[1] ATE0Q0V1 Note that yours doesn't go into mux mode and the chat seems out of sync. I've bumped up the timeouts on the chat. Can you place the attached file into /system/lib on your phone? I'm not sure how easy that will be for you as adb lets you remount /system but for us it isn't a filesystem. :( Rui Castro wrote: Hi, great, the kill-server command did the trick. Here's my radio logcat. On Fri, Dec 5, 2008 at 2:37 AM, Sean McNeil s...@mcneil.com wrote: Rui Castro wrote: Hi, With the current kernel and jffs2 image, my GSM network is never available. I can't produce the radio log because I can't get adb to connect to neo! It shows - waiting for device - all the time. Hmm... Can you ping the phone? Sometimes an old server for adb gets left laying around and you need to do a ADBHOST=neo ./adb kill-server to clear it out. On Fri, Dec 5, 2008 at 2:11 AM, Sean McNeil s...@mcneil.com wrote: Looks like no response from the modem. Perhaps there is an issue with turning it on. I've seen this happen here on occasion and a reboot resolves it. Cédric Berger wrote: On Thu, Dec 4, 2008 at 05:35, Sean McNeil s...@mcneil.com wrote: Can you send me the output of ADBHOST=neo ./adb logcat -b radio No GSM for me either. And SIM contacts import fails too (says no contacts on SIM). (I aso tried in settings to register to networks, but it already was failing with previous images) adb logcat -b radio : I/RIL ( 857): Opening tty device /dev/s3c2410_serial0,115200 I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT-Command Interpreter ready D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT AT+CMUX=1,0,5,128 D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT OK D/RIL ( 857): Connecting GPRS channel to tty /dev/pts/0 E/RIL ( 857): Error creating PPP options file: /data/ppp/options.gprs. D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): Re-opening after close I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): CHAT ATZ D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857):
Re: First impressions on new Android rootfs
Gothnet wrote: Please forgive me for replying to so many of my own emails... ... that helps more than is annoing ;) Gothnet wrote: Apparently the answer is setprop net.usb0.dns1 $IP_ADDRESS Try setprop net.dns1 $IP_ADDRESS (just without the network device) for me then dns worked reliably. I did setup an bluetooth connection with bnep to my linux pc. Actually the same way as from every other gta02 distro (http://wiki.openmoko.org/wiki/Manually_using_Bluetooth) . Except I had to do an hciconfig hci0 up on android. To keep the browser from crashing I had not only to remove rm /data/data/com.android.browser/app_plugins/gears.so but as well rm /data/data/com.android.browser/app_plugins/gears-0.4.23.0/* rm /data/data/com.android.browser/app_plugins/gears-0.4.23.0 All this done in adb shell, which I got with: - download the file adb from http://people.openmoko.org/sean_mcneil/ an make it executable - cd into the dir where you have adb downloaded - connect freerunner with usb cable and start android on it - as root: ifconfig usb0 192.168.0.199 up - kill process adb fork-server server if running (find it with: ps aux | grep adb) - then do as root ADBHOST=192.168.0.202 ./adb shell You should then have a console on your freerunner running android: * daemon not running. starting it now * * daemon started successfully * # My current freerunner android setup: Bootloader: http://people.openmoko.org/andy/qi-s3c2442-master_2ad3ce6ff57753e3.udfu (01-Dec-2008 02:23 26K) [s3c2442 is for GTA02] Kernel: http://people.openmoko.org/sean_mcneil/uImage-android (04-Dec-2008 05:28 2.4M) Rootfs: http://people.openmoko.org/sean_mcneil/androidfs.jffs2 (05-Dec-2008 04:18 32M) Thanks for all your contributions, Sean first, of course! Schöngruß Ulle -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1619210.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Sean McNeil wrote: Franky Van Liedekerke wrote: On Thu, 04 Dec 2008 01:12:59 +0700 Sean McNeil [EMAIL PROTECTED] wrote: I'm uploading a new image right now that includes Ruis virtual keyboard. Please give it 30 minutes or so to complete the upload. Sean Sean, which uImage should we take? uImage-android or uImage-tracking? Good point. I've deleted uImage-tracking and made uImage-android the matching kernel based on andy-tracking. Sean Here the kernel you provide doesn't boot at all. In used the uImage-Android kernel, but get the following error on boot: ERROR: Can't get kernel image (when booting from the NAND-menu). Otherwise i just get a screen with 'Openmoko'on it, nothing else. Jeroen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Franky Van Liedekerke wrote: | On Thu, 04 Dec 2008 01:12:59 +0700 | Sean McNeil [EMAIL PROTECTED] wrote: | | | I'm uploading a new image right now that includes Ruis virtual | keyboard. Please give it 30 minutes or so to complete the upload. | | Sean | | | Sean, | | which uImage should we take? uImage-android or uImage-tracking? | | Good point. I've deleted uImage-tracking and made uImage-android the | matching kernel based on andy-tracking. I really hope we can capture the diff between this and andy-tracking into andy-tracking directly. It's fair enough if it contains in-progress patches I guess but we need to keep zero diff as often as possible. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3pWEACgkQOjLpvpq7dMrevgCfbCFiPonwVRqXCKcLHG/p0qDE +jQAniIoNdy6n9sja4R5GoTPPaO7yLIA =euuM -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Got the thing booting, finally, by using my universal charger. I guess the problem now is that when it gets too low it'll just shut itself down, even with the charger attached. I'm running uImage-tracking and the rootfs with the keyboard now. Rui Castro wrote: My keyboard has some obvious problems, the letter/number/symbols keys are too small If you have fingernails the buttons just about work, could definitely be wider though. Rui Castro wrote: I have been able to boot with kernels uImage-android and uImage-tracking, but both are very unstable. The suspend/resume don't work reliably in any of them. With uImage-tracking, the only one I could get to work for some time, bluethooth works, gsm works sometimes, wifi works but it doesn't detect my wireless network (WPA) and it doesn't shutdown. I noticed the same stuff, and in addition to this the UI seems less responsive than it was in previous releases. The smoothness of bringing up the app menu is just not quite as good as before, which is a shame. The suspend/resume is better than last time around, and any keyboard is a good start, but we're not quite there yet. OTOH, it seems to be a matter of glueing the firmware to the hardware successfully, rather than fundamental problems. Rui Castro wrote: The workaround to boot the uImage-tracking kernel from uBoot (setenv bootcmd setenv ... ; saveenv) works, but when I poweroff neo and try to boot again it doesn't work anymore; I have to do the hack again. Maybe I'm doing something stupid here. It's the first time I mess with uBoot shell. I did things the long way round, downloading the uboot env with dfu-util, editing it and then re-uploading (see previous post on what to do with borked uboot env). Mostly did this because neither of my debian systems at home wanted to bring up any /dev/ttyACM or /dev/ttyUSB or whatever interfaces and I couldn't access the shell. Have booted this way several times, so you may want to give it a try. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1613093.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Hire wrote:
Someone can explain me how I can edit the uboot env? Because I did it:
bootcmd=
setenv bootargs ${bootargs_base} ${mtdparts};
nand read.e 0x3200 kernel 0x30;
bootm 0x3200
But it doesn't boot. It does the same issue: can't find an image kernel.
I have edited only the environment.in and not env.in
Oh - that's what I did, in NAND uboot, download the env using dfu-util, grab
the devirginator toolset and environment.in, change that single character
in environment.in from a 2 to a 3 in the bootcmd section, run the
environment generator and then upload the new env.out file.
Then I re-uploaded the kernel and rootfs using dfu-util and it worked
fine. That's all the help I can be.
I've also discovered a new feature in the image since my last post. Plugging
it into my windows box to charge makes the box bluescreen. Not only when
booted, but if it's plugged in then the OS bluescreens differently during
startup. Yay!
--
View this message in context:
http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1613173.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Gothnet wrote: I've also discovered a new feature in the image since my last post. Plugging it into my windows box to charge makes the box bluescreen. Not only when booted, but if it's plugged in then the OS bluescreens differently during startup. Yay! Feature? :) I have the exact same issue. But if i plug it into a collegue's box who hasn't the usb driver, it doesn't crash. The major issue i encounter right now is that the gsm doesn't register.. It worked 12 hours ago with another kernel (i was able to make a call without echo, and acceptable sound quality (level a bit too low)). Right now i'm using uImage-android downloaded one hour ago. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1613220.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
On Thu, Dec 4, 2008 at 12:34, Gothnet [EMAIL PROTECTED] wrote: I've also discovered a new feature in the image since my last post. Plugging it into my windows box to charge makes the box bluescreen. Not only when booted, but if it's plugged in then the OS bluescreens differently during startup. Yay! Same for me, except I do not even have bluescreen: immediate reboot. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
On Thu, Dec 4, 2008 at 05:35, Sean McNeil [EMAIL PROTECTED] wrote: Can you send me the output of ADBHOST=neo ./adb logcat -b radio No GSM for me either. And SIM contacts import fails too (says no contacts on SIM). (I aso tried in settings to register to networks, but it already was failing with previous images) adb logcat -b radio : I/RIL ( 857): Opening tty device /dev/s3c2410_serial0,115200 I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT-Command Interpreter ready D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT AT+CMUX=1,0,5,128 D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT OK D/RIL ( 857): Connecting GPRS channel to tty /dev/pts/0 E/RIL ( 857): Error creating PPP options file: /data/ppp/options.gprs. D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): Re-opening after close I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): CHAT ATZ D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT%CSTAT=1 D/AT ( 857): MUX[1] AT%CSTAT=1 D/AT ( 857): MUX[1] AT%CSTAT=1 D/AT ( 857): MUX[1] AT%CSTAT=1 D/AT ( 857): MUX[1] AT%CSTAT=1 D/AT ( 857): MUX[1] AT+CFUN? D/AT ( 857): MUX[1] AT+CFUN? D/AT ( 857): MUX[1] AT+CFUN? D/AT ( 857): MUX[1] AT+CFUN? D/AT ( 857): MUX[1] AT+CFUN? I/RILC( 857): libril: new connection I/RILC( 857): RIL Daemon version:
Re: First impressions on new Android rootfs
On Thu, Dec 4, 2008 at 17:34, Cédric Berger [EMAIL PROTECTED] wrote: On Thu, Dec 4, 2008 at 05:35, Sean McNeil [EMAIL PROTECTED] wrote: Can you send me the output of ADBHOST=neo ./adb logcat -b radio No GSM for me either. And SIM contacts import fails too (says no contacts on SIM). (I aso tried in settings to register to networks, but it already was failing with previous images) I also get this error on startup : (my data partition -first partition on SD- is 4GB but I think it was ok with your previous image) E/MediaScannerService( 1000): exception in MediaScanner.scan() E/MediaScannerService( 1000): java.lang.RuntimeException: Out of memory E/MediaScannerService( 1000): at android.media.MediaScanner.native_setup(Native Method) E/MediaScannerService( 1000): at android.media.MediaScanner.init(MediaScanner.java:320) E/MediaScannerService( 1000): at com.android.providers.media.MediaScannerService.scan(MediaScannerService.java:88) E/MediaScannerService( 1000): at com.android.providers.media.MediaScannerService.access$200(MediaScannerService.java:43) E/MediaScannerService( 1000): at com.android.providers.media.MediaScannerService$ServiceHandler.handleMessage(MediaScannerService.java:234) E/MediaScannerService( 1000): at android.os.Handler.dispatchMessage(Handler.java:88) E/MediaScannerService( 1000): at android.os.Looper.loop(Looper.java:123) E/MediaScannerService( 1000): at com.android.providers.media.MediaScannerService.run(MediaScannerService.java:155) E/MediaScannerService( 1000): at java.lang.Thread.run(Thread.java:935) D/MediaScannerService( 1000): done scanning volume internal D/MediaScannerService( 1000): start scanning volume external D/dalvikvm( 873): GREF has increased to 201 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
On Thu, Dec 4, 2008 at 01:38, Rui Castro [EMAIL PROTECTED] wrote: Hi, My first impressions on this new image is that it isn't usable :) Hi Rui, Is it able to answer calls now? Thanks (Obrigado), Levy. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Hi, Theoretically, yes. I have done it in the emulator, with a test call made from AnETTe (http://android-telefonie.de/anette/). Rui On Thu, Dec 4, 2008 at 4:40 PM, Levy A. M. Sant'Anna [EMAIL PROTECTED] wrote: On Thu, Dec 4, 2008 at 01:38, Rui Castro [EMAIL PROTECTED] wrote: Hi, My first impressions on this new image is that it isn't usable :) Hi Rui, Is it able to answer calls now? Thanks (Obrigado), Levy. ___ 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: First impressions on new Android rootfs
Hi,
Thanks Sean. I will give it a try when I get home.
Rui
On Thu, Dec 4, 2008 at 4:28 AM, Sean McNeil [EMAIL PROTECTED] wrote:
Marco Trevisan (Treviño) wrote:
Rui Castro wrote:
The workaround to boot the uImage-tracking kernel from uBoot (setenv
bootcmd setenv ... ; saveenv) works, but when I poweroff neo and try
to boot again it doesn't work anymore; I have to do the hack again.
Maybe I'm doing something stupid here. It's the first time I mess with
uBoot shell.
Are you editing NOR or NAND uBoot? You have write access only to NAND...
I tried to make a jffs2 image from koolu source code, but I had no
luck. I compiled the sources successfully with make
PRODUCT_TARGET=freerunner, then I tried to create a jffs2 image
following a very simplistic and probably wrong approach:
1. Created a directory newandroidfs,
2. Extracted the contents of out/target/product/freerunner/ramdisk.img
to that directory, using file-roller,
3. copied the files under out/target/product/freerunner/system to
/system,
4. created a symlink /etc to /system/etc and a directory /sdcard (like
I saw in Sean's image)
5. and created a jffs2 image with the contents of the directory
newandroidfs using the command mkfs.jffs2 --pad=0x70 -o
newandroidfs.jffs2 -e 0x2 -n -dnewandroidfs/
Outcome of all this, red light flashing!!! It's kernel panic, right? :(
It should be...
Btw another way for getting working images, I guess that should be using
the Sean's image as base and then putting there only the files you've
changed with your patches after a recompilation...
Would it work?
If someone (have no ideia who :) ) did a simple tutorial about how to
produce the precious jffs2 image, that would make the testing of new
features a lot simpler.
I'm asking this too :P
I use a script to copy out of the opensource build into my NFS mounted area.
Once there, I use another script to create the jffs2 image. You'll probably
need to modify them to your environment.
Sean
#!/bin/sh
ANDROID_OUT=~/moko/android/opensource/out
ANDROID_DEVICE=freerunner
EXPORT_ROOT=/srv/export
Usage()
{
echo Usage: $0 release|debug
}
CopyAndroid()
{
if [ -d $1 ]
then
echo Copying from... $1
sudo rm -rf $EXPORT_ROOT/root/dev
sudo rm -rf $EXPORT_ROOT/root/system
# Copy the image...
cd $1
tar cf - root | (cd $EXPORT_ROOT; sudo tar xf -)
tar cf - system | (cd $EXPORT_ROOT/root; sudo tar xf -)
# Change owner and permissions...
cd $EXPORT_ROOT
sudo chown -R root:root root
sudo chmod -R 777 root
else
echo $1 does not exist!
fi
}
if [ $# != 1 ]
then
Usage
else
case $1 in
release)
CopyAndroid $ANDROID_OUT/target/product/$ANDROID_DEVICE/
;;
debug)
CopyAndroid
$ANDROID_OUT/debug/target/product/$ANDROID_DEVICE/
;;
*)
Usage
esac
fi
#!/bin/sh
sudo mkfs.jffs2 --pad=0x70 -o androidfs.jffs2 -e 0x2 -n -droot/
___
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: First impressions on new Android rootfs
On Thu, Dec 4, 2008 at 17:34, Cédric Berger [EMAIL PROTECTED] wrote:
On Thu, Dec 4, 2008 at 05:35, Sean McNeil [EMAIL PROTECTED] wrote:
Can you send me the output of
ADBHOST=neo ./adb logcat -b radio
No GSM for me either.
And SIM contacts import fails too (says no contacts on SIM).
(I aso tried in settings to register to networks, but it already was
failing with previous images)
adb logcat -b radio :
Oh in fact after booting under qtopia, and have it register to
network, I came back in android and it correctly re-registered to this
GSM network.
I already had this kind of problems on previous android images.
(note that I am at a location where I have access also to roaming networks)
sorry for big log :-p this is what I had this time :
D/GSM ( 912): [DataConnectionTracker] Radio is off and clean up
all connection
D/GSM ( 912): [DataConnectionTracker] Clean up connection due to
radioTurnedOff
D/GSM ( 912): [DataConnection] Stop poll NetStat
D/GSM ( 912): [DataConnection] Stop poll NetStat
D/GSM ( 912): [DataConnectionTracker] ***trySetupData due to roamingOff
D/GSM ( 912): [DataConnectionTracker] trySetupData: Not ready for
data: dataState=IDLE gprsState=1 sim=false UMTS=false phoneState=IDLE
dataEnabled=true roaming=false dataOnRoamingEnable=false
D/GSM ( 912): [GsmSimCard] Broadcasting intent
SIM_STATE_CHANGED_ACTION NOT_READY reason null
D/RILJ( 912): [0002] BASEBAND_VERSION
D/RILJ( 912): [0003] GET_IMEI
D/RILJ( 912): [0004] GET_IMEISV
D/AT ( 853): MUX[1] AT+CFUN=1
D/AT ( 853): MUX[1] %CSTAT: PHB, 0
D/AT ( 853): MUX[1] AT+CFUN=1
D/AT ( 853): MUX[1] OK
D/AT ( 853): MUX[1] AT+CTZU=1
D/GSM ( 912): Notifying: Radio On
D/RILJ( 912): [0005] OPERATOR
D/RILJ( 912): [0006] GPRS_REGISTRATION_STATE
D/RILJ( 912): [UNSL] RADIO_STATE_CHANGED SIM_NOT_READY
D/AT ( 853): MUX[1] OK
D/AT ( 853): MUX[1] AT+CTZR=1
D/RILJ( 912): [0007] REGISTRATION_STATE
D/AT ( 853): MUX[1] OK
D/AT ( 853): MUX[1] AT+CPIN?
D/AT ( 853): MUX[1] +CPIN: READY
D/AT ( 853): MUX[1] OK
D/AT ( 853): MUX[1] AT+CSMS=0
D/RILJ( 912): [0008] QUERY_NETWORK_SELECTION_MODE
D/AT ( 853): MUX[1] +CMS ERROR: 314
D/RIL ( 853): onRequest: BASEBAND_VERSION
D/AT ( 853): MUX[1] AT%BAND?
D/RILJ( 912): [0001] RADIO_POWER
D/AT ( 853): MUX[1] %BAND: 0
D/AT ( 853): MUX[1] OK
D/RIL ( 853): onRequest: GET_IMEI
D/AT ( 853): MUX[1] AT+CGSN
D/RILJ( 912): [0002] BASEBAND_VERSION 0
D/RILJ( 912): [0009] GET_CURRENT_CALLS
D/AT ( 853): MUX[1] +CGSN: 354651011607019
D/AT ( 853): MUX[1] OK
D/RIL ( 853): onRequest: GET_IMEISV
D/RIL ( 853): onRequest: OPERATOR
D/AT ( 853): MUX[1] AT+COPS=3,0;+COPS?;+COPS=3,1;+COPS?;+COPS=3,2;+COPS?
D/RILJ( 912): [0003] GET_IMEI
D/RILJ( 912): [0004] GET_IMEISV error:
com.android.internal.telephony.gsm.CommandException:
REQUEST_NOT_SUPPORTED
D/AT ( 853): MUX[1] +COPS: 0
D/AT ( 853): MUX[1] +COPS: 0
D/AT ( 853): MUX[1] +COPS: 0
D/AT ( 853): MUX[1] OK
D/RIL ( 853): onRequest: GPRS_REGISTRATION_STATE
D/AT ( 853): MUX[1] AT+CGREG?
D/RILJ( 912): [0005] OPERATOR {null, null, null}
D/AT ( 853): MUX[1] +CGREG: 2,0
D/AT ( 853): MUX[1] OK
D/RIL ( 853): onRequest: REGISTRATION_STATE
D/AT ( 853): MUX[1] AT+CREG?
D/RILJ( 912): [0006] GPRS_REGISTRATION_STATE {0, -1, -1}
D/AT ( 853): MUX[1] +CREG: 2,0
D/AT ( 853): MUX[1] OK
D/RIL ( 853): onRequest: QUERY_NETWORK_SELECTION_MODE
D/AT ( 853): MUX[1] AT+COPS?
D/RILJ( 912): [0007] REGISTRATION_STATE {0, -1, -1}
D/AT ( 853): MUX[1] +COPS: 0
D/AT ( 853): MUX[1] OK
D/RIL ( 853): onRequest: GET_CURRENT_CALLS
D/AT ( 853): MUX[1] AT+CLCC
D/RILJ( 912): [0008] QUERY_NETWORK_SELECTION_MODE {0}
D/AT ( 853): MUX[1] OK
D/RILJ( 912): [0009] GET_CURRENT_CALLS
D/GSM ( 912): Poll ServiceState done: oldSS=[3 home null null
null ] newSS=[1 home null null null ] oldGprs=1 newGprs=1
oldType=unknown newType=unknown
D/AT ( 853): MUX[1] AT+CPIN?
D/AT ( 853): MUX[1] +CPIN: READY
D/AT ( 853): MUX[1] OK
D/AT ( 853): MUX[1] AT+CSMS=0
D/AT ( 853): MUX[1] +CMS ERROR: 314
D/AT ( 853): MUX[1] %CSTAT: PHB, 0
D/AT ( 853): MUX[1] %CSTAT: PHB, 0
D/AT ( 853): MUX[1] %CSTAT: PHB, 0
D/AT ( 853): MUX[1] AT+CPIN?
D/AT ( 853): MUX[1] +CPIN: READY
D/AT ( 853): MUX[1] OK
D/AT ( 853): MUX[1] AT+CSMS=0
D/AT ( 853): MUX[1] +CMS ERROR: 314
D/AT ( 853): MUX[1] AT+CPIN?
D/AT ( 853): MUX[1] +CPIN: READY
D/AT ( 853): MUX[1] OK
D/AT ( 853): MUX[1] AT+CSMS=0
D/AT ( 853): MUX[1] +CMS ERROR: 314
D/AT ( 853): MUX[1] AT+CPIN?
D/AT ( 853): MUX[1] +CPIN: READY
D/AT ( 853): MUX[1] OK
D/AT ( 853): MUX[1] AT+CSMS=0
D/AT ( 853): MUX[1] +CMS ERROR: 314
Re: First impressions on new Android rootfs
On Thu, Dec 4, 2008 at 17:48, Rui Castro [EMAIL PROTECTED] wrote: Hi, Theoretically, yes. I have done it in the emulator, with a test call made from AnETTe (http://android-telefonie.de/anette/). Rui On Thu, Dec 4, 2008 at 4:40 PM, Levy A. M. Sant'Anna [EMAIL PROTECTED] wrote: On Thu, Dec 4, 2008 at 01:38, Rui Castro [EMAIL PROTECTED] wrote: Hi, My first impressions on this new image is that it isn't usable :) Hi Rui, Is it able to answer calls now? No one called me :-p But I made a call and while on call I could not get the keyboard ! Menu button brings special call menu, and there is not the keybord button :-( I am afraid that it could be the same for incoming calls. So you could not answer. So no access to volume buttons. And DTMF with Phone application numerical keyboard does not work... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Cédric Berger wrote: But I made a call and while on call I could not get the keyboard ! Menu button brings special call menu, and there is not the keybord button :-( I am afraid that it could be the same for incoming calls. So you could not answer. So no access to volume buttons. And DTMF with Phone application numerical keyboard does not work... I'll give incoming calls a go with real hardware slightly later, but from what you're saying you wouldn't be able to hang up! Still, progress eh? -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1614482.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
On Thu, Dec 4, 2008 at 18:30, Gothnet [EMAIL PROTECTED] wrote: Cédric Berger wrote: But I made a call and while on call I could not get the keyboard ! Menu button brings special call menu, and there is not the keybord button :-( I am afraid that it could be the same for incoming calls. So you could not answer. So no access to volume buttons. And DTMF with Phone application numerical keyboard does not work... I'll give incoming calls a go with real hardware slightly later, but from what you're saying you wouldn't be able to hang up! Still, progress eh? -- Well hang up is possible since there is an hang up button on the standard phone menu. (press menu button during call to see it) The problem is to respond to a call... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
But I made a call and while on call I could not get the keyboard ! Menu button brings special call menu, and there is not the keybord button :-( I am afraid that it could be the same for incoming calls. So you could not answer. So no access to volume buttons. And DTMF with Phone application numerical keyboard does not work... Hi Cedric, none button to answer a call and for other normal things, was the problem when I tested the last image, we don't have a button to answer the call and it is not possible to do by touchscreen. Thanks all, Levy. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Cédric Berger wrote: Well hang up is possible since there is an hang up button on the standard phone menu. (press menu button during call to see it) The problem is to respond to a call... No problem at all, just made and received calls between my cheapo sony ericcson and the freerunner running the 2.4MB (tracking) kernel and the latest rootfs. Incoming call gets displayed, click power button for menu, click button for keyboard, click button for pick up. Would it be better if the dialer app had on-screen buttons for pick up or reject? Certainly. But Rui's keyboard works fine. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1614648.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Actually, when I say fine, I mean that I could pick up. To hang up at the end of the call I still had to bring up the phone menu. Right, next test - text messages. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1614665.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Gothnet wrote: Actually, when I say fine, I mean that I could pick up. To hang up at the end of the call I still had to bring up the phone menu. Right, next test - text messages. Which I can't do because now it's refusing to register. Except when I call it the Network think's it's registered and I get ringtone. Hmmm. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1614818.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Hi, I didn't modify any application directly, just the super class of all activities (Activity), but it's possible to modify the incoming call screen an place a button there. Personally, I prefer not to modify applications because it's more code to maintain as aplications evolve. As Gothnet said, the End Call button is present in the menu of an ongoing call and that screen completly overrides the menu creation methods, that's why the keyboard button doesn't appear. Rui On Thu, Dec 4, 2008 at 6:07 PM, Gothnet [EMAIL PROTECTED] wrote: Cédric Berger wrote: Well hang up is possible since there is an hang up button on the standard phone menu. (press menu button during call to see it) The problem is to respond to a call... No problem at all, just made and received calls between my cheapo sony ericcson and the freerunner running the 2.4MB (tracking) kernel and the latest rootfs. Incoming call gets displayed, click power button for menu, click button for keyboard, click button for pick up. Would it be better if the dialer app had on-screen buttons for pick up or reject? Certainly. But Rui's keyboard works fine. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1614648.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ 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: First impressions on new Android rootfs
On Thu, Dec 4, 2008 at 16:07, Gothnet [EMAIL PROTECTED] wrote: Incoming call gets displayed, click power button for menu, click button for keyboard, click button for pick up. Nice, I will test this last image this weekend. Thank you, Levy. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Levy Abinajm Melero Sant'Anna wrote: Nice, I will test this last image this weekend. Thank you, Levy. don't get too excited, after registering for the first 24 hours, it now refuses to. I think the unregistered but still ringing thing was a network glitch. Since then, no registration despite several reboots. There's a GSM bug in there somewhere that spoils the call answering feature. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1615941.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Rui Castro a écrit : Hi, Theoretically, yes. I have done it in the emulator, with a test call made from AnETTe (http://android-telefonie.de/anette/). Rui With another kernel, i was able to place a call yesterday (uImage-android or uImage-tracking from 24 hours ago, don't remember which, i tried both and then updated it 12 hours ago) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Gothnet wrote: Gothnet wrote: Actually, when I say fine, I mean that I could pick up. To hang up at the end of the call I still had to bring up the phone menu. Right, next test - text messages. Which I can't do because now it's refusing to register. Except when I call it the Network think's it's registered and I get ringtone. Hmmm. It would be most helpful if you could provide the data from ADBHOST=neo ./adb logcat -b radio ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Cédric Berger wrote: On Thu, Dec 4, 2008 at 17:34, Cédric Berger [EMAIL PROTECTED] wrote: On Thu, Dec 4, 2008 at 05:35, Sean McNeil [EMAIL PROTECTED] wrote: Can you send me the output of ADBHOST=neo ./adb logcat -b radio No GSM for me either. And SIM contacts import fails too (says no contacts on SIM). (I aso tried in settings to register to networks, but it already was failing with previous images) I also get this error on startup : (my data partition -first partition on SD- is 4GB but I think it was ok with your previous image) E/MediaScannerService( 1000): exception in MediaScanner.scan() E/MediaScannerService( 1000): java.lang.RuntimeException: Out of memory E/MediaScannerService( 1000): at android.media.MediaScanner.native_setup(Native Method) E/MediaScannerService( 1000): at android.media.MediaScanner.init(MediaScanner.java:320) E/MediaScannerService( 1000): at com.android.providers.media.MediaScannerService.scan(MediaScannerService.java:88) E/MediaScannerService( 1000): at com.android.providers.media.MediaScannerService.access$200(MediaScannerService.java:43) E/MediaScannerService( 1000): at com.android.providers.media.MediaScannerService$ServiceHandler.handleMessage(MediaScannerService.java:234) E/MediaScannerService( 1000): at android.os.Handler.dispatchMessage(Handler.java:88) E/MediaScannerService( 1000): at android.os.Looper.loop(Looper.java:123) E/MediaScannerService( 1000): at com.android.providers.media.MediaScannerService.run(MediaScannerService.java:155) E/MediaScannerService( 1000): at java.lang.Thread.run(Thread.java:935) D/MediaScannerService( 1000): done scanning volume internal D/MediaScannerService( 1000): start scanning volume external D/dalvikvm( 873): GREF has increased to 201 This error is expected. It was a hack to deal with licensing issues. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Looks like no response from the modem. Perhaps there is an issue with turning it on. I've seen this happen here on occasion and a reboot resolves it. Cédric Berger wrote: On Thu, Dec 4, 2008 at 05:35, Sean McNeil [EMAIL PROTECTED] wrote: Can you send me the output of ADBHOST=neo ./adb logcat -b radio No GSM for me either. And SIM contacts import fails too (says no contacts on SIM). (I aso tried in settings to register to networks, but it already was failing with previous images) adb logcat -b radio : I/RIL ( 857): Opening tty device /dev/s3c2410_serial0,115200 I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT-Command Interpreter ready D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT AT+CMUX=1,0,5,128 D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT OK D/RIL ( 857): Connecting GPRS channel to tty /dev/pts/0 E/RIL ( 857): Error creating PPP options file: /data/ppp/options.gprs. D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): Re-opening after close I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): CHAT ATZ D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT ( 857): MUX[1] AT%CSTAT=1 D/AT ( 857): MUX[1] AT%CSTAT=1 D/AT ( 857): MUX[1] AT%CSTAT=1 D/AT ( 857):
Re: First impressions on new Android rootfs
Hi, With the current kernel and jffs2 image, my GSM network is never available. I can't produce the radio log because I can't get adb to connect to neo! It shows - waiting for device - all the time. On Fri, Dec 5, 2008 at 2:11 AM, Sean McNeil [EMAIL PROTECTED] wrote: Looks like no response from the modem. Perhaps there is an issue with turning it on. I've seen this happen here on occasion and a reboot resolves it. Cédric Berger wrote: On Thu, Dec 4, 2008 at 05:35, Sean McNeil [EMAIL PROTECTED] wrote: Can you send me the output of ADBHOST=neo ./adb logcat -b radio No GSM for me either. And SIM contacts import fails too (says no contacts on SIM). (I aso tried in settings to register to networks, but it already was failing with previous images) adb logcat -b radio : I/RIL ( 857): Opening tty device /dev/s3c2410_serial0,115200 I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT-Command Interpreter ready D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT AT+CMUX=1,0,5,128 D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT OK D/RIL ( 857): Connecting GPRS channel to tty /dev/pts/0 E/RIL ( 857): Error creating PPP options file: /data/ppp/options.gprs. D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): Re-opening after close I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): CHAT ATZ D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT ( 857): MUX[1] AT+CMGF=0 D/AT (
Re: First impressions on new Android rootfs
Rui Castro wrote: Hi, With the current kernel and jffs2 image, my GSM network is never available. I can't produce the radio log because I can't get adb to connect to neo! It shows - waiting for device - all the time. Hmm... Can you ping the phone? Sometimes an old server for adb gets left laying around and you need to do a ADBHOST=neo ./adb kill-server to clear it out. On Fri, Dec 5, 2008 at 2:11 AM, Sean McNeil [EMAIL PROTECTED] wrote: Looks like no response from the modem. Perhaps there is an issue with turning it on. I've seen this happen here on occasion and a reboot resolves it. Cédric Berger wrote: On Thu, Dec 4, 2008 at 05:35, Sean McNeil [EMAIL PROTECTED] wrote: Can you send me the output of ADBHOST=neo ./adb logcat -b radio No GSM for me either. And SIM contacts import fails too (says no contacts on SIM). (I aso tried in settings to register to networks, but it already was failing with previous images) adb logcat -b radio : I/RIL ( 857): Opening tty device /dev/s3c2410_serial0,115200 I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT-Command Interpreter ready D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT AT+CMUX=1,0,5,128 D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT OK D/RIL ( 857): Connecting GPRS channel to tty /dev/pts/0 E/RIL ( 857): Error creating PPP options file: /data/ppp/options.gprs. D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): Re-opening after close I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): CHAT ATZ D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CGEREP=1,0 D/AT
Re: First impressions on new Android rootfs
Hi, great, the kill-server command did the trick. Here's my radio logcat. On Fri, Dec 5, 2008 at 2:37 AM, Sean McNeil [EMAIL PROTECTED] wrote: Rui Castro wrote: Hi, With the current kernel and jffs2 image, my GSM network is never available. I can't produce the radio log because I can't get adb to connect to neo! It shows - waiting for device - all the time. Hmm... Can you ping the phone? Sometimes an old server for adb gets left laying around and you need to do a ADBHOST=neo ./adb kill-server to clear it out. On Fri, Dec 5, 2008 at 2:11 AM, Sean McNeil [EMAIL PROTECTED] wrote: Looks like no response from the modem. Perhaps there is an issue with turning it on. I've seen this happen here on occasion and a reboot resolves it. Cédric Berger wrote: On Thu, Dec 4, 2008 at 05:35, Sean McNeil [EMAIL PROTECTED] wrote: Can you send me the output of ADBHOST=neo ./adb logcat -b radio No GSM for me either. And SIM contacts import fails too (says no contacts on SIM). (I aso tried in settings to register to networks, but it already was failing with previous images) adb logcat -b radio : I/RIL ( 857): Opening tty device /dev/s3c2410_serial0,115200 I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT-Command Interpreter ready D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT ATZ D/AT ( 857): CHAT OK D/AT ( 857): CHAT AT+CMUX=1,0,5,128 D/AT ( 857): CHAT ATE0Q0V1 D/AT ( 857): CHAT OK D/RIL ( 857): Connecting GPRS channel to tty /dev/pts/0 E/RIL ( 857): Error creating PPP options file: /data/ppp/options.gprs. D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 D/AT ( 857): MUX[1] ATE0Q0V1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[2] ATE0Q0V1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] AT+CRC=1 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] ATS0=0 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[1] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): Re-opening after close I/RIL ( 857): Setting tty device parameters D/AT ( 857): CHAT D/AT ( 857): D/AT ( 857): D/AT ( 857): AT D/AT ( 857): CHAT AT D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): CHAT ATZ D/AT ( 857): MUX[2] AT+CMEE=1 D/AT ( 857): MUX[2] AT+CMEE=1 I/RIL ( 857): AT channel timeout; closing D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=2 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CREG=1 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CGREG=2 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CCWA=1 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMOD=2 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CMUT=0 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+CSSN=0,1 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+COLP=0 D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CSCS=HEX D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1] AT+CUSD=1 D/AT ( 857): MUX[1]
Re: First impressions on new Android rootfs
On Wed, Dec 3, 2008 at 10:19 AM, Gothnet [EMAIL PROTECTED]wrote: //just kidding, though am interested because android currently looks like the best possibility of turning my neo from an interesting looking brick to an actual phone I agree Android looks like it has a lot of promise - but if you want a functioning phone today - I'd suggest trying out QtExtended 4.4.2 - it doesn't give you much more than basic phone functionality, but I've been using it as my day-to-day phone for a month now, and am generally pretty happy with it... Warren ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Warren Baird wrote: I agree Android looks like it has a lot of promise - but if you want a functioning phone today - I'd suggest trying out QtExtended 4.4.2 - it doesn't give you much more than basic phone functionality, but I've been using it as my day-to-day phone for a month now, and am generally pretty happy with it... Warren Qtopia is one of the two things I didn't try, SHR being the other. I gave up on the rest because of the unresponsive interfaces, poor battery life, terrible remote echo (tried everything I could find), refusal to wake up in a timely fashion on incoming calls etc. I was also discouraged by the prominence of we should work on stuff for GTA03 comments on the lists. I now have a cheap sony-ericsson for the sake of my sanity, so I'll wait until android or other distro can provide a bit more than basic phone functions, or at least do it better than what I have. Android looks like it could be the quickest route to solving most of the issues and the echo was gone straight away. i know I ought to get off my a*se and help, but after the dayjob I don't have much appetite for coding and debugging right now. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1609901.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Gothnet wrote: Warren Baird wrote: I agree Android looks like it has a lot of promise - but if you want a functioning phone today - I'd suggest trying out QtExtended 4.4.2 - it doesn't give you much more than basic phone functionality, but I've been using it as my day-to-day phone for a month now, and am generally pretty happy with it... Warren Qtopia is one of the two things I didn't try, SHR being the other. I gave up on the rest because of the unresponsive interfaces, poor battery life, terrible remote echo (tried everything I could find), refusal to wake up in a timely fashion on incoming calls etc. I was also discouraged by the prominence of we should work on stuff for GTA03 comments on the lists. I now have a cheap sony-ericsson for the sake of my sanity, so I'll wait until android or other distro can provide a bit more than basic phone functions, or at least do it better than what I have. Android looks like it could be the quickest route to solving most of the issues and the echo was gone straight away. i know I ought to get off my a*se and help, but after the dayjob I don't have much appetite for coding and debugging right now. I'm uploading a new image right now that includes Ruis virtual keyboard. Please give it 30 minutes or so to complete the upload. Sean ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
I'm uploading a new image right now that includes Ruis virtual keyboard. Please give it 30 minutes or so to complete the upload. Sounds fabulous, Sean. I wonder... will I be able to use the virtual keyboard to enter a PIN for the simcard? I can't remove that from the card (some providers think it's fun to make that so). Paul -- Heaven from all creatures hides the book of Fate. -Alexander Pope http://www.nlpagan.net Running on Mandriva Linux 2009 and Ubuntu 8.10 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
On Thu, 04 Dec 2008 01:12:59 +0700 Sean McNeil [EMAIL PROTECTED] wrote: I'm uploading a new image right now that includes Ruis virtual keyboard. Please give it 30 minutes or so to complete the upload. Sean Sean, which uImage should we take? uImage-android or uImage-tracking? Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Franky Van Liedekerke wrote: Sean, which uImage should we take? uImage-android or uImage-tracking? Franky Take a look here - http://n2.nabble.com/andy-tracking-kernel--td1609293.html for details on the kernel difference. and what you'll need to do to u-boot to get the tracking kernel to boot. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1610252.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
The image doesn't work for me. I'm using the daily u-boot build from yesterday, and the latest android rootfs and kernel. I have tried it with 2 different sd cards, a 256, and a 2gb both formatted with a 50mb fat16 and the rest ext2. it just sits at a black screen, I've waited over 20 minutes to see if it does anything. I've also checked out the sd card in my computer to discover that android didn't write anything to the ext2 partition.. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1610406.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
which uImage should we take? uImage-android or uImage-tracking? Right.. I stuck the new jffs and uImage-android on the Freerunner. I can get to the system even though the SIM card is not recognised (probably because the SIM's pin is still in place). Pressing menu (power button) takes me away from the prompt, works well. Looks nice, works well. Good job! Could not get to a shell, but perhaps I should've tried that as root? Paul (Just too bad about the phone bit... ;-) -- Heaven from all creatures hides the book of Fate. -Alexander Pope http://www.nlpagan.net Running on Mandriva Linux 2009 and Ubuntu 8.10 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: First impressions on new Android rootfs
I tried this with 512MB SD (it works): Device Boot Start End Blocks Id System /dev/mmcblk0p1 17814 250040 6 FAT16 /dev/mmcblk0p27815 15568 248128 83 Linux Make sure you do in fdisk f,2,6 as described in http://wiki.openmoko.org/wiki/Booting_from_SD#Prepare_the_SD_card (Preparing and formating). I think f,2,6 or the size of FAT16 partition solves the problem. Both partitions are empty (not sure if necessary). Date: Wed, 3 Dec 2008 11:39:37 -0800 From: [EMAIL PROTECTED] To: community@lists.openmoko.org Subject: Re: First impressions on new Android rootfs The image doesn't work for me. I'm using the daily u-boot build from yesterday, and the latest android rootfs and kernel. I have tried it with 2 different sd cards, a 256, and a 2gb both formatted with a 50mb fat16 and the rest ext2. it just sits at a black screen, I've waited over 20 minutes to see if it does anything. I've also checked out the sd card in my computer to discover that android didn't write anything to the ext2 partition.. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1610406.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community _ Werden Sie Mitglied der neuen Windows Live Messenger Familie! http://get.live.com___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: First impressions on new Android rootfs
Sorry not f, use t,2,6 From: [EMAIL PROTECTED] To: community@lists.openmoko.org Date: Wed, 3 Dec 2008 20:38:29 + Subject: RE: First impressions on new Android rootfs I tried this with 512MB SD (it works): Device Boot Start End Blocks Id System /dev/mmcblk0p1 17814 250040 6 FAT16 /dev/mmcblk0p27815 15568 248128 83 Linux Make sure you do in fdisk f,2,6 as described in http://wiki.openmoko.org/wiki/Booting_from_SD#Prepare_the_SD_card (Preparing and formating). I think f,2,6 or the size of FAT16 partition solves the problem. Both partitions are empty (not sure if necessary). Date: Wed, 3 Dec 2008 11:39:37 -0800 From: [EMAIL PROTECTED] To: community@lists.openmoko.org Subject: Re: First impressions on new Android rootfs The image doesn't work for me. I'm using the daily u-boot build from yesterday, and the latest android rootfs and kernel. I have tried it with 2 different sd cards, a 256, and a 2gb both formatted with a 50mb fat16 and the rest ext2. it just sits at a black screen, I've waited over 20 minutes to see if it does anything. I've also checked out the sd card in my computer to discover that android didn't write anything to the ext2 partition.. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1610406.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Hol dir noch heute die neue Beta des Windows Live Messengers! Hier klicken! _ Werden Sie Mitglied der neuen Windows Live Messenger Familie! http://get.live.com___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
On Thu, Dec 4, 2008 at 6:38 AM, Matthias Camenzind [EMAIL PROTECTED] wrote: I tried this with 512MB SD (it works): Device Boot Start End Blocks Id System /dev/mmcblk0p1 17814 250040 6 FAT16 /dev/mmcblk0p27815 15568 248128 83 Linux Would you please spend 5 minutes and post a short list of what works and what does not. Perhaps worth a spot on the WIKI. I'd like to know what to expect before I embark on re-flashing from current QTExtended 4.4.2 (calls working well with no echo or buzz when on handset, suspend/resume, occasional late or duplicate sms notifications and other minor grizzles ) and also having to prepare an SD card just to find out on Android I still can't do the basics again like make or receive calls, sms or suspend. cheers Denis ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Paul wrote: which uImage should we take? uImage-android or uImage-tracking? Right.. I stuck the new jffs and uImage-android on the Freerunner. I can get to the system even though the SIM card is not recognised (probably because the SIM's pin is still in place). Pressing menu (power button) takes me away from the prompt, works well. Looks nice, works well. Good job! Could not get to a shell, but perhaps I should've tried that as root? Paul (Just too bad about the phone bit... ;-) Hi, do you know whether the wake from suspend issue has been resolved in this image? Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Hi Thanks for providing an image. Few words from me: I'm able to make calls, but it's rather hard to hear other person in a speaker (he does hear me very well, no echo issue). After receiving a message (yep, it works) I lost contact with my gsm network, so I can't answer. Reboots did not work, i'm reflashing right now. Couldn't find my wifi network, but it maybe my router's issue. Resume from a suspend does not work. Browser and few apps too, but it's not high prioritaire right now, I think ;) Everything beside that - is great! Thanks and waiting for more ;) ps. After reflashing, I still don't have a gsm connection. After reinserting sim, I've got a connection and lost it again. Some problems here.. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Sean with the lastest image the gsm doesn't work :( 2008/12/3 Sean McNeil [EMAIL PROTECTED] Gothnet wrote: Warren Baird wrote: I agree Android looks like it has a lot of promise - but if you want a functioning phone today - I'd suggest trying out QtExtended 4.4.2 - it doesn't give you much more than basic phone functionality, but I've been using it as my day-to-day phone for a month now, and am generally pretty happy with it... Warren Qtopia is one of the two things I didn't try, SHR being the other. I gave up on the rest because of the unresponsive interfaces, poor battery life, terrible remote echo (tried everything I could find), refusal to wake up in a timely fashion on incoming calls etc. I was also discouraged by the prominence of we should work on stuff for GTA03 comments on the lists. I now have a cheap sony-ericsson for the sake of my sanity, so I'll wait until android or other distro can provide a bit more than basic phone functions, or at least do it better than what I have. Android looks like it could be the quickest route to solving most of the issues and the echo was gone straight away. i know I ought to get off my a*se and help, but after the dayjob I don't have much appetite for coding and debugging right now. I'm uploading a new image right now that includes Ruis virtual keyboard. Please give it 30 minutes or so to complete the upload. Sean ___ 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: First impressions on new Android rootfs
Franky Van Liedekerke wrote: which uImage should we take? uImage-android or uImage-tracking? OK, for the hard of thinking (amongst whom I count myself) I got the tracking kernel booting by following the what if I borked my bootloader instructions from here - http://wiki.openmoko.org/wiki/Bootloader But editing the bootcmd entry to read a larger kernel nand read.e 0x3200 kernel 0x30; then flashing the kernel and rootfs image as usual. Unfortunately the time I took to do this seems to have run down the freerunner's battery, and now android boots and immdeiately says shutting down because of low power. It doesn't do it though. I also can't seem to find my universal charger any more, dammit, so I'm not quite sure what to do. Does the battery charge whilst in u-boot menu? -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1611381.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Gothnet wrote: But editing the bootcmd entry to read a larger kernel nand read.e 0x3200 kernel 0x30; then flashing the kernel and rootfs image as usual. Unfortunately the time I took to do this seems to have run down the freerunner's battery, and now android boots and immdeiately says shutting down because of low power. It doesn't do it though. If you've used the stable-tracking kernel, maybe this is due to the userspace /sys battery node changes. See on previous mail how to fix this. -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Hi, My first impressions on this new image is that it isn't usable :) My keyboard has some obvious problems, the letter/number/symbols keys are too small and when dialog windows appear asking for text, like the bluetooth pairing code, the keyboard is bellow the dialog and cannot be clicked. I have to work on those issues. I have been able to boot with kernels uImage-android and uImage-tracking, but both are very unstable. The suspend/resume don't work reliably in any of them. With uImage-tracking, the only one I could get to work for some time, bluethooth works, gsm works sometimes, wifi works but it doesn't detect my wireless network (WPA) and it doesn't shutdown. The workaround to boot the uImage-tracking kernel from uBoot (setenv bootcmd setenv ... ; saveenv) works, but when I poweroff neo and try to boot again it doesn't work anymore; I have to do the hack again. Maybe I'm doing something stupid here. It's the first time I mess with uBoot shell. I tried to make a jffs2 image from koolu source code, but I had no luck. I compiled the sources successfully with make PRODUCT_TARGET=freerunner, then I tried to create a jffs2 image following a very simplistic and probably wrong approach: 1. Created a directory newandroidfs, 2. Extracted the contents of out/target/product/freerunner/ramdisk.img to that directory, using file-roller, 3. copied the files under out/target/product/freerunner/system to /system, 4. created a symlink /etc to /system/etc and a directory /sdcard (like I saw in Sean's image) 5. and created a jffs2 image with the contents of the directory newandroidfs using the command mkfs.jffs2 --pad=0x70 -o newandroidfs.jffs2 -e 0x2 -n -dnewandroidfs/ Outcome of all this, red light flashing!!! It's kernel panic, right? :( If someone (have no ideia who :) ) did a simple tutorial about how to produce the precious jffs2 image, that would make the testing of new features a lot simpler. Well, I'm sure we will have a working image to show off the new phone on the weekend ;) Rui On Thu, Dec 4, 2008 at 12:23 AM, Marco Trevisan (Treviño) [EMAIL PROTECTED] wrote: Gothnet wrote: But editing the bootcmd entry to read a larger kernel nand read.e 0x3200 kernel 0x30; then flashing the kernel and rootfs image as usual. Unfortunately the time I took to do this seems to have run down the freerunner's battery, and now android boots and immdeiately says shutting down because of low power. It doesn't do it though. If you've used the stable-tracking kernel, maybe this is due to the userspace /sys battery node changes. See on previous mail how to fix this. -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ 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: First impressions on new Android rootfs
Rui Castro wrote: The workaround to boot the uImage-tracking kernel from uBoot (setenv bootcmd setenv ... ; saveenv) works, but when I poweroff neo and try to boot again it doesn't work anymore; I have to do the hack again. Maybe I'm doing something stupid here. It's the first time I mess with uBoot shell. Are you editing NOR or NAND uBoot? You have write access only to NAND... I tried to make a jffs2 image from koolu source code, but I had no luck. I compiled the sources successfully with make PRODUCT_TARGET=freerunner, then I tried to create a jffs2 image following a very simplistic and probably wrong approach: 1. Created a directory newandroidfs, 2. Extracted the contents of out/target/product/freerunner/ramdisk.img to that directory, using file-roller, 3. copied the files under out/target/product/freerunner/system to /system, 4. created a symlink /etc to /system/etc and a directory /sdcard (like I saw in Sean's image) 5. and created a jffs2 image with the contents of the directory newandroidfs using the command mkfs.jffs2 --pad=0x70 -o newandroidfs.jffs2 -e 0x2 -n -dnewandroidfs/ Outcome of all this, red light flashing!!! It's kernel panic, right? :( It should be... Btw another way for getting working images, I guess that should be using the Sean's image as base and then putting there only the files you've changed with your patches after a recompilation... Would it work? If someone (have no ideia who :) ) did a simple tutorial about how to produce the precious jffs2 image, that would make the testing of new features a lot simpler. I'm asking this too :P Well, I'm sure we will have a working image to show off the new phone on the weekend ;) -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Franky Van Liedekerke wrote: On Thu, 04 Dec 2008 01:12:59 +0700 Sean McNeil [EMAIL PROTECTED] wrote: I'm uploading a new image right now that includes Ruis virtual keyboard. Please give it 30 minutes or so to complete the upload. Sean Sean, which uImage should we take? uImage-android or uImage-tracking? Good point. I've deleted uImage-tracking and made uImage-android the matching kernel based on andy-tracking. Sean ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Marco Trevisan (Treviño) wrote:
Rui Castro wrote:
The workaround to boot the uImage-tracking kernel from uBoot (setenv
bootcmd setenv ... ; saveenv) works, but when I poweroff neo and try
to boot again it doesn't work anymore; I have to do the hack again.
Maybe I'm doing something stupid here. It's the first time I mess with
uBoot shell.
Are you editing NOR or NAND uBoot? You have write access only to NAND...
I tried to make a jffs2 image from koolu source code, but I had no
luck. I compiled the sources successfully with make
PRODUCT_TARGET=freerunner, then I tried to create a jffs2 image
following a very simplistic and probably wrong approach:
1. Created a directory newandroidfs,
2. Extracted the contents of out/target/product/freerunner/ramdisk.img
to that directory, using file-roller,
3. copied the files under out/target/product/freerunner/system to /system,
4. created a symlink /etc to /system/etc and a directory /sdcard (like
I saw in Sean's image)
5. and created a jffs2 image with the contents of the directory
newandroidfs using the command mkfs.jffs2 --pad=0x70 -o
newandroidfs.jffs2 -e 0x2 -n -dnewandroidfs/
Outcome of all this, red light flashing!!! It's kernel panic, right? :(
It should be...
Btw another way for getting working images, I guess that should be using
the Sean's image as base and then putting there only the files you've
changed with your patches after a recompilation...
Would it work?
If someone (have no ideia who :) ) did a simple tutorial about how to
produce the precious jffs2 image, that would make the testing of new
features a lot simpler.
I'm asking this too :P
I use a script to copy out of the opensource build into my NFS mounted
area. Once there, I use another script to create the jffs2 image. You'll
probably need to modify them to your environment.
Sean
#!/bin/sh
ANDROID_OUT=~/moko/android/opensource/out
ANDROID_DEVICE=freerunner
EXPORT_ROOT=/srv/export
Usage()
{
echo Usage: $0 release|debug
}
CopyAndroid()
{
if [ -d $1 ]
then
echo Copying from... $1
sudo rm -rf $EXPORT_ROOT/root/dev
sudo rm -rf $EXPORT_ROOT/root/system
# Copy the image...
cd $1
tar cf - root | (cd $EXPORT_ROOT; sudo tar xf -)
tar cf - system | (cd $EXPORT_ROOT/root; sudo tar xf -)
# Change owner and permissions...
cd $EXPORT_ROOT
sudo chown -R root:root root
sudo chmod -R 777 root
else
echo $1 does not exist!
fi
}
if [ $# != 1 ]
then
Usage
else
case $1 in
release)
CopyAndroid $ANDROID_OUT/target/product/$ANDROID_DEVICE/
;;
debug)
CopyAndroid $ANDROID_OUT/debug/target/product/$ANDROID_DEVICE/
;;
*)
Usage
esac
fi
#!/bin/sh
sudo mkfs.jffs2 --pad=0x70 -o androidfs.jffs2 -e 0x2 -n -droot/
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Can you send me the output of ADBHOST=neo ./adb logcat -b radio ? Riccardo Centra wrote: Sean with the lastest image the gsm doesn't work :( 2008/12/3 Sean McNeil [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Gothnet wrote: Warren Baird wrote: I agree Android looks like it has a lot of promise - but if you want a functioning phone today - I'd suggest trying out QtExtended 4.4.2 - it doesn't give you much more than basic phone functionality, but I've been using it as my day-to-day phone for a month now, and am generally pretty happy with it... Warren Qtopia is one of the two things I didn't try, SHR being the other. I gave up on the rest because of the unresponsive interfaces, poor battery life, terrible remote echo (tried everything I could find), refusal to wake up in a timely fashion on incoming calls etc. I was also discouraged by the prominence of we should work on stuff for GTA03 comments on the lists. I now have a cheap sony-ericsson for the sake of my sanity, so I'll wait until android or other distro can provide a bit more than basic phone functions, or at least do it better than what I have. Android looks like it could be the quickest route to solving most of the issues and the echo was gone straight away. i know I ought to get off my a*se and help, but after the dayjob I don't have much appetite for coding and debugging right now. I'm uploading a new image right now that includes Ruis virtual keyboard. Please give it 30 minutes or so to complete the upload. Sean ___ Openmoko community mailing list community@lists.openmoko.org mailto: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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
There is a known issue with Wifi and the wpa_supplicant in Android. I'm trying to track down why it won't scan properly. wp wrote: Hi Thanks for providing an image. Few words from me: I'm able to make calls, but it's rather hard to hear other person in a speaker (he does hear me very well, no echo issue). After receiving a message (yep, it works) I lost contact with my gsm network, so I can't answer. Reboots did not work, i'm reflashing right now. Couldn't find my wifi network, but it maybe my router's issue. Resume from a suspend does not work. Browser and few apps too, but it's not high prioritaire right now, I think ;) Everything beside that - is great! Thanks and waiting for more ;) ps. After reflashing, I still don't have a gsm connection. After reinserting sim, I've got a connection and lost it again. Some problems here.. ___ 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: First impressions on new Android rootfs
On Tue, Dec 2, 2008 at 14:27, Gothnet [EMAIL PROTECTED] wrote: Improvements since the first release are evident, the graphics are now pretty glitch free where they used to occasionally flicker. However, since the last image I flashed, bluetooth has stopped working, I now just get a message saying Unable to turn on Bluetooth. Wifi claims to turn on but fails to scan. Can't remember if this is better or worse than before. No keyboard, will attempt to find a way to install the one mentioned here: http://lists.openmoko.org/nabble.html#nabble-td1583918 Err... does anyone know if suspend/resume works yet? - suspend/resume is known not work yet (at least not reliably). - indeed bluetooth does not work anymore, but I guess it is because of the newest kernel. I did not try it again with previous kernel though. (anyway before I could scan/pair bluetooth but I could not do anything more with it -file transfer, ...-). - wifi still does not work. It is acknowledged by Sean and he is investigating on this. - with latest kernel, for exemple, backlight brightness is not managed anymore. (because of some kernel changes). I tried Sean's modification : (You'll need to change /system/build.prop: backlight.lcd=/sys/class/backlight/gta02-bl). But I did not manage to get it work yet. - Also Sean is working on integrating the software keyboard from Rui Castro . For now, most wanted for me is a keyboard, and internet connectivity (90% off android applications need internet access !). Wifi does not work, GPRS either (for me at least), and I did not manage to have internet access via USB (though I have read this may work ? Success anyone ?). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Cédric Berger wrote: For now, most wanted for me is a keyboard, and internet connectivity (90% off android applications need internet access !). Wifi does not work, GPRS either (for me at least), and I did not manage to have internet access via USB (though I have read this may work ? Success anyone ?). Can't quite get there, I have a missing link. I can get into a shell on the freerunner and see the ifconfig info for usb0 - usb0: ip 192.168.0.202 mask 255.255.255.0 flags [up broadcast running multicast] And ping the notebook on 192.168.0.200. Adding a route with - route add default gw 192.168.0.200 dev usb0 Once that's done I can ping the public IP address of the notebook as well. I think there's some sort of firewall stuff on this machine (work laptop) that's preventing me from forwarding packets, but the main problem I have is that there's no /etc/resolv.conf so I'm not sure how to add DNS info. I could add the file and try that I s'pose. Also the command line ssh (dropbear client) chokes because it can't get random data. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1604011.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
First impressions on new Android rootfs
Improvements since the first release are evident, the graphics are now pretty glitch free where they used to occasionally flicker. However, since the last image I flashed, bluetooth has stopped working, I now just get a message saying Unable to turn on Bluetooth. Wifi claims to turn on but fails to scan. Can't remember if this is better or worse than before. No keyboard, will attempt to find a way to install the one mentioned here: http://lists.openmoko.org/nabble.html#nabble-td1583918 Err... does anyone know if suspend/resume works yet? So anyway, we're still a little way off a useable phone, IMHO. I'm happy to be contradicted here though. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1603648.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Cédric Berger wrote: On Tue, Dec 2, 2008 at 14:27, Gothnet [EMAIL PROTECTED] wrote: Improvements since the first release are evident, the graphics are now pretty glitch free where they used to occasionally flicker. However, since the last image I flashed, bluetooth has stopped working, I now just get a message saying Unable to turn on Bluetooth. Wifi claims to turn on but fails to scan. Can't remember if this is better or worse than before. No keyboard, will attempt to find a way to install the one mentioned here: http://lists.openmoko.org/nabble.html#nabble-td1583918 Err... does anyone know if suspend/resume works yet? - suspend/resume is known not work yet (at least not reliably). Using Sean's new rootfs and his tracking kernel, suspend/resume does seem to work fairly well for me. I am seeing some spurious resumes, but I think that may be the GSM re-registration issue. I should apply the modem firmware upgrade, I guess. - indeed bluetooth does not work anymore, but I guess it is because of the newest kernel. I did not try it again with previous kernel though. (anyway before I could scan/pair bluetooth but I could not do anything more with it -file transfer, ...-). Haven't tried bluetooth. - wifi still does not work. It is acknowledged by Sean and he is investigating on this. Scan doesn't work. I was able to connect to an open network using the Add a Wi-Fi network option in settings. I was able to check email using Wi-fi. The browser crashes without a message. - with latest kernel, for exemple, backlight brightness is not managed anymore. (because of some kernel changes). I tried Sean's modification : (You'll need to change /system/build.prop: backlight.lcd=/sys/class/backlight/gta02-bl). But I did not manage to get it work yet. - Also Sean is working on integrating the software keyboard from Rui Castro . Until he does, I'm using the QD keyboard app that was mentioned here a while back. It works via cut paste, but gets the job done. For now, most wanted for me is a keyboard, and internet connectivity (90% off android applications need internet access !). Wifi does not work, GPRS either (for me at least), and I did not manage to have internet access via USB (though I have read this may work ? Success anyone ?). Sounds like my wish list. I haven't tried GPRS yet. I'd add that I'd really like to see code access via some sort of public repository plus build instructions so I could experiment and possibly help with fixes etc. Jim ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Yup, DNS is the issue now. Attached to another machine I can ping 66.249.91.147 but lookup of www.google.com fails. To create a resolv.conf i had to remount the root filesystem as rw with - mount -o remount,rw -t jffs2 /dev/root / But it didn't help. So, yes, net access over USB but no DNS. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1604131.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
On Tuesday 02 December 2008, Jim Ancona wrote: Cédric Berger wrote: On Tue, Dec 2, 2008 at 14:27, Gothnet [EMAIL PROTECTED] wrote: Err... does anyone know if suspend/resume works yet? - suspend/resume is known not work yet (at least not reliably). Using Sean's new rootfs and his tracking kernel, suspend/resume does seem to work fairly well for me. I am seeing some spurious resumes, but I think that may be the GSM re-registration issue. I should apply the modem firmware upgrade, I guess. The upgrade to moko10-beta fixes #666 (for me anyway) but doesn't touch #1024 and wasn't expected to. Until there is a gsm firmware fix for #1024 we will need the AT%SLEEP=2 fix as used by recent FSO and 2008.x. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Please forgive me for replying to so many of my own emails... Apparently the answer is setprop net.usb0.dns1 $IP_ADDRESS Though I haven't made it do anything because the browser won't start, there's no keypad to enter mail settings and the only command line tool I can find (ping) doesn't seem to get the setting. Guess I need a keyboard. -- View this message in context: http://n2.nabble.com/First-impressions-on-new-Android-rootfs-tp1603648p1604187.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
On Tue, Dec 2, 2008 at 16:38, Gothnet [EMAIL PROTECTED] wrote: Please forgive me for replying to so many of my own emails... Apparently the answer is setprop net.usb0.dns1 $IP_ADDRESS Though I haven't made it do anything because the browser won't start, there's no keypad to enter mail settings and the only command line tool I can find (ping) doesn't seem to get the setting. Guess I need a keyboard. -- the browser crashes because of Gears (not ported -and not open source-). I had to remove it on the sdcard : /data/data/com.android.browser/app_plugins/gears.so Then the browser can start. Maybe you can type mail settings via the copy/paste keyboard : ( apk on http://code.google.com/p/netgents/downloads/list ) Another way to edit settings without keyboard is to configure apps in emulator, then copy settings files (under /data/data/xx/ ) via adb from emulator to neo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
Jim Ancona wrote: Cédric Berger wrote: On Tue, Dec 2, 2008 at 14:27, Gothnet [EMAIL PROTECTED] wrote: Improvements since the first release are evident, the graphics are now pretty glitch free where they used to occasionally flicker. However, since the last image I flashed, bluetooth has stopped working, I now just get a message saying Unable to turn on Bluetooth. Wifi claims to turn on but fails to scan. Can't remember if this is better or worse than before. No keyboard, will attempt to find a way to install the one mentioned here: http://lists.openmoko.org/nabble.html#nabble-td1583918 Err... does anyone know if suspend/resume works yet? - suspend/resume is known not work yet (at least not reliably). Using Sean's new rootfs and his tracking kernel, suspend/resume does seem to work fairly well for me. I am seeing some spurious resumes, but I think that may be the GSM re-registration issue. I should apply the modem firmware upgrade, I guess. - indeed bluetooth does not work anymore, but I guess it is because of the newest kernel. I did not try it again with previous kernel though. (anyway before I could scan/pair bluetooth but I could not do anything more with it -file transfer, ...-). Haven't tried bluetooth. bluetooth is setup to work with the new andy-tracking kernel. They've switched to using an rfkill switch which I didn't implement in the 2.6.26 kernel. - wifi still does not work. It is acknowledged by Sean and he is investigating on this. Scan doesn't work. I was able to connect to an open network using the Add a Wi-Fi network option in settings. I was able to check email using Wi-fi. The browser crashes without a message. - with latest kernel, for exemple, backlight brightness is not managed anymore. (because of some kernel changes). I tried Sean's modification : (You'll need to change /system/build.prop: backlight.lcd=/sys/class/backlight/gta02-bl). But I did not manage to get it work yet. I forgot there is a permission setting in /init.rc that needs to be changed as well. Essentially change pcf50633-bl to gta02-bl. - Also Sean is working on integrating the software keyboard from Rui Castro . Yep, I'm working with Rui to get this in. Until he does, I'm using the QD keyboard app that was mentioned here a while back. It works via cut paste, but gets the job done. For now, most wanted for me is a keyboard, and internet connectivity (90% off android applications need internet access !). Wifi does not work, GPRS either (for me at least), and I did not manage to have internet access via USB (though I have read this may work ? Success anyone ?). Sounds like my wish list. I haven't tried GPRS yet. I'd add that I'd really like to see code access via some sort of public repository plus build instructions so I could experiment and possibly help with fixes etc. Jim ___ 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
