Re: GTA03 Touchscreen Capacitive (was Re: OT: iPhone howto)
Matthias Apitz wrote: El día Friday, February 27, 2009 a las 02:43:30PM +0100, Simon Kagstrom escribió: On 2/27/09, Matthias Apitz g...@unixarea.de wrote: Ok, as I think that we have now exchanged enough good arguments to stay with resistive in GTA03 and I have not seen any strong argument to move to capacitive screen, I don't think we can draw this conclusion, it's your opinion. What we can say is this: - Capacitive touch screens have some advantages - Resistive touch screens have some advantages - They *both* have disadvantages ... That's to simple saying some/other advantages; the key point is that with a capacitive touch screens we will loose the possibility to control this as any other X11 server, i.e. being able to point and click nearly to a single pixel, or at least select a very small square of 2x2 pixels; This has nothing to do with Capacitive vs. Resistive. It has to do with resolution of the touchpad and size of area that touches the screen. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Android] muxgsm-ril code submitted
We have submitted the RIL to Google now and it is available for inspection at: https://review.source.android.com/9013 Sean ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GTA03 Touchscreen Capacitive (was Re: OT: iPhone howto)
Matthias Apitz wrote: El día Wednesday, February 25, 2009 a las 06:36:31PM +0100, Yorick Moko escribió: http://en.wikipedia.org/wiki/Touchscreen#Resistive vs http://en.wikipedia.org/wiki/Touchscreen#Capacitive Thanks; But: Do we really want a GTA03 which can't be managed with a stylus pen? I can't imagine a 'Terminal' like keyboard (i.e. one having all keys like the actual Om2008.9 'Terminal', including Shift, SHift-Lock, ...) and using it with my finger tips; how should this work? Where this idea, GTA03 with Capacitive, comes from? :-(( matthias What do you mean? You can get a stylus that works with capacitive touch screens: http://songtak.manufacturer.globalsources.com/si/6008826112271/pdtl/PDA-styli/1006246576/Touch-Pen.htm Just about all phone manufacturers are going to capacitive screens as they virtually eliminate accidental touches in something like a purse or pocket. Calibration used to be an issue, but resistive screens are made with pretty good tolerances now and don't often need recalibration once manufacturing goes into mass production. How a keyboard works with the iPhone is it expands a key on touch, lets you slide your finger if you missed the right one, then types in when you release. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: which file system for sd card?
thewire wrote: The Digital Pioneer пишет: The only reason they come with FAT is so windoze can use it. That said, I don't know much about filesystems, but I would generally go with EXT2/3 over FAT. I'm no fs expert either, but i would generally advise to use jffs2 or ubifs, as they are specially designed for use in flash memory devices. Note that ubifs requires kernel = 2.6.27. Neither of those filesystems are appropriate for sd cards. They have wear leveling logic that is not necessary or a good thing as it is already done in firmware for sd. An efficient journaled filesystem not designed for memory devices (like ext3) would be best. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Yaouh! out (update for tangogps maps)
arne anka wrote: ext2/3 is not really suited to storing such a large number of small files. afaik ext3 can be configured to use small files. (I don't understand why ext2/3 is used at all these days, as it has been obsolete for years. that's nonsense. Except for one bug 8 years ago[1], ReiserFS has worked flawlessly for me on my desktop systems.) i use ext2/3 for over ten years now and never had any problems. if you like reiser better, it's ok, but please don't tell such nonsense only to justify your likings. it's purely a matter of personal preferences, nothing more -- and least of all extX is bad, reiser is good. There is also a lot of community support for ext[234] with noticeable active development. I'm not so certain what the condition of ReiserFS is these days, but I don't think there have been any enhancements or improvements to match ext4. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Re: disable power-button
Actually, the kernel will call shutdown if the power is held for 8 seconds. To disable that, you'd need to recompile the kernel. There is no proc interface to enable/disable its behavior. Sean arne anka wrote: ok, excuse me: we are using the official debian installed by the official script in the flash! that's the important part, since every distribution handles it differently. debian uses fso and fso in turn handles the pwr -- i think, you can hanlde your task by creating a rule in rules.yaml or so. but you better ask on the fso-lists, see http://www.freesmartphone.org/index.php/Infrastructure#Mailing_Lists ___ 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, 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: [android] Unable to read long SMS messages
Thanks for the info. I think I have all of these SMS issues fixed. Testing now. Andy Kilner wrote: Ok, I've run a number of tests listening to the output of logcat. 1) Unsuccessfully sending an SMS message 2) Successfully receiving a short SMS message containing Short message 3) Unsuccessfully receiving a full SMS message (160 chars) I'm not sure what the cutoff point is here for the length that can be successfully received, I could try a few more and narrow it down. 4) And just incase I haven't pissed anyone off enough attaching large files I've included the logcat output (not just for radio) when attempting to power down the device (which doesn't work and just sits there with the spinner until I take the battery out). Thanks for your help with this, if you can point me in the right direction I'll help out as much as I can. Cheers, Andy 2008/12/8 Sean McNeil [EMAIL PROTECTED] Hi Andy, What would be really helpful is to have it plugged into a linux host and run the command ADBHOST=neo ./adb logcat -b radio This assumes you have your host setup to connect usb over ethernet and have neo set to the proper IP. Andy Kilner wrote: Hi, I've been using android on my freerunner for a few days now, the original image and the latest image and both seem to have a problem displaying SMS messages that go over a few words. Has anyone else experienced this problem, or do most of you just avoid txting? I'm afraid it's an essential requirement of my phone almost more so than being able to place and receive calls. I've had a quick poke about on the adb shell but data/data/com.google.android.providers.telephony/databases/sms.db appears to be empty. Can anyone point me in the direction of where SMS's are stored, unfortunately it doesn't look like it's going to be all that simple. The phone also refuses to send SMS messages, if I attempt to do so the gsm connection is dropped and sometimes it can be a pain in the arse getting it back. All in all though, (IMHO) Android is looking the more promising and I'd like to stick with it. Cheers ___ 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 ___ 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: [android] Unable to read long SMS messages
Hi Andy, What would be really helpful is to have it plugged into a linux host and run the command ADBHOST=neo ./adb logcat -b radio This assumes you have your host setup to connect usb over ethernet and have neo set to the proper IP. Andy Kilner wrote: Hi, I've been using android on my freerunner for a few days now, the original image and the latest image and both seem to have a problem displaying SMS messages that go over a few words. Has anyone else experienced this problem, or do most of you just avoid txting? I'm afraid it's an essential requirement of my phone almost more so than being able to place and receive calls. I've had a quick poke about on the adb shell but data/data/com.google.android.providers.telephony/databases/sms.db appears to be empty. Can anyone point me in the direction of where SMS's are stored, unfortunately it doesn't look like it's going to be all that simple. The phone also refuses to send SMS messages, if I attempt to do so the gsm connection is dropped and sometimes it can be a pain in the arse getting it back. All in all though, (IMHO) Android is looking the more promising and I'd like to stick with it. Cheers ___ 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
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
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
Re: [android] Building Android from the Koolu Source
Marcelo wrote: Hi, On Thu, Dec 4, 2008 at 8:43 PM, Jim Ancona [EMAIL PROTECTED] wrote: I've documented how I did it on the wiki at: http://wiki.openmoko.org/wiki/Android#Building_the_Koolu_Android_Source we would like this to be as straightforward as possible, so a few hours ago I added the required toolchain to the git repo and patched the necessary build files to use that toolchain by default. If you go to http://git.koolu.org/ and follow the instructions form there (basically download repo, do a repo init and repo sync) you should be able to build everything from source with just: $ make TARGET_PRODUCT=freerunner I find it easier to just do this $ echo TARGET_PRODUCT:=freerunner buildspec.mk You can also do a $ . build/envsetup.sh $ choosecombo and then select defaults for first 2 questions and freerunner for last. and then afterwards: $ make Hopefully this allows everyone interested to work on the code — as opposed to working on build system around the code. Thanks! Marcelo ___ 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
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
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
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
Re: [OT]Software patents end? ??:) light at the end of tunnel
Dale Maggee wrote: Denis Johnson wrote: On Fri, Nov 28, 2008 at 6:59 PM, Dale Maggee [EMAIL PROTECTED] wrote: * It's my Hard drive that doesn't support FLAC! If I used flac, my music library (I guess mp3 collection will soon become a misnomer!) would be *enormous*! Yes, I realise it's lossless etc etc, but 320kpbs mp3s are close enough for me. I understand and agree that from a quality pov MP3 @ 320kpbs is sufficient for most, and the amount of space required for your library matters, but I was under the impression that FLAC is also a compressed format. However I must admit I'm not sure how it compares to MP3 @ 320kpbs cheers Denis FLAC *is* compressed, but it's lossless compression, meaning that there is no change to the sound when you encode it to FLAC, Whereas when you encode to MP3 or ogg, you're losing audio information. I'd like to point out also that the CD source is already lossy in that it is a digital representation of analog signals. Recording companies, however, compensate for this and work to make the sound output from a CD player as ideal as possible, Usually it's not noticable, and the higher bitrate you choose the less you lose, but there is a difference. Personally, I can't hear the difference between an audio CD and a 320kbps mp3 on my equipment, but ymmv. In terms of file size, FLAC is bigger than 320kbps (not sure exactly how much bigger, as I don't have much experience with flac, but It's substantially bigger). If you have unlimited HDD space and really care about audio quality, FLAC is the way to go. If you want some free HDD space and decent sounding stuff, 320kbps mp3s (or, more precisely, since abandoning mp3 is the whole point of the discussion, the ogg equivalent of a 320kbps mp3 - I haven't figured out how ogg's quality scale thing works yet) are a very reasonable compromise, and if you can hear the difference it pretty much means you're a) using expensive equipment and b) a freak of nature. ;) But really it all comes down to personal taste. If you have a nice big HDD, you might even want to encode everything in FLAC and then re-encode it at 256kb for burning CDs for use in your car / mp3 player / clock radio / fridge / whatever... -Dale ___ 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: [OT]Software patents end? ??:) light at the end of tunnel
Stroller wrote: On 28 Nov 2008, at 11:06, Sean McNeil wrote: ... I'd like to point out also that the CD source is already lossy in that it is a digital representation of analog signals. Recording companies, however, compensate for this and work to make the sound output from a CD player as ideal as possible, I understood otherwise: http://en.wikipedia.org/wiki/Loudness_war Google loudness war for many other posts on the subject - many of these posts are very readable and are complaints from genuine music- lovers disappointed with deteriorating audio quality on new releases. I don't listen to music so much these days - I've just gotten out of the habit of it, I guess. But I have fond memories of the very early 1990s, when CD was still the medium of audiophile choice, and the argument against vinyl still raged. I would kick back with a Jimi Hendrix remaster and pick out individual instruments to appreciate as part of the whole. Each was pure and remarkable - or perhaps that was just the spliff - but when I read about how the record companies are reducing the dynamic range of the albums they now publish I wonder if the same experience would be possible. Ah, now we are talking about opinion of ideal ;) Yes, I agree with all you have said, but the interpretation of ideal for record companies is to appeal to the largest body of consumers and they are marketing it that way. Kids want it loud. Back on topic, my point is you are starting with a lossy format to begin with even if you use FLAC. What really matters is how it sounds to an individual and the type of device you are using, quality of headset, etc. With choices, a user can see what he/she can tolerate and determine a reasonable compression to get the most music on a device. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] OnScreen Keyboard
Excellent. Then we can just include it within the image as it won't affect operations otherwise. Rui Castro wrote: Hi, The keyboard is launched from the menu. Press Menu, all the the menus appear with a Keyboard item (except if the activity/application overrides all the menu methods), click the keyboard menu and the keyboard appears on screen; the bottom/left key changes the position of the keyboard (bottom/top); the bottom/right key hides the keyboard (clicking the keyboard menu when the keyboard is on screen also hides it). I will be happy to, when the image is ready (with suspend working)! Rui On Thu, Nov 27, 2008 at 4:08 AM, Sean McNeil [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Rui, Your images look really nice. Thanks for all that work! I have planned to release a new image by Monday and will incorporate your changes. One thing: is the keyboard always there or can it be turned on/off? If always present, then perhaps we should make it a package that can be optionally installed? This will make a lot of people happy. Cheers, Sean Rui Castro wrote: Hi, I implemented an OnScreen Keyboard in the Android framework. It works with all applications and it's possible to answer calls :) I already uploaded the changes to Android repository, here (http://review.source.android.com/4801) and here (http://review.source.android.com/3087). I've tried to upload all the changes at the same time, but something went wrong :) I don't expect the changes to be merged in the android official code because they are developing their own IMF and also because my implementation is very simplistic, it's just to be able to use Android until the IMF is ready. I've attached some screenshots of the keyboard in several applications running on the emulator. Now, I just need someone (Sean/Brian) to create an image for Neo :) Please hurry!!! :D Rui Castro ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
