Re: Bounties?
I'd pay ~50 for a thing like Agendus on Palm OS. http://www.iambic.com/agendus/palmos/ That can sync to Evolution (at least Calendar and Contacts) and has good mail app. QT mail is not usable, clawsmail is a lot better but not optimized for a small screen. Michael Sargun Dhillon schrieb: Just out of curiosity, how many OpenMoko users out there would be willing to pay for bounties? Additionally, how many developers would work for bounties? What sort of bounties would you guys request? How much would you pay? ___ 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
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: Funding Global Domination
Arigead ha scritto: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Minh Ha Duong wrote: Le mercredi 03 décembre 2008, arne anka a écrit : The second option is more like it. It takes a few hours to design a T-Shirt and upload it to an online store where everybody else can go and buy it. So just do it: the entry costs are so low that there is no real need for a formal market study ! Rui: There are lots of cool artwork under a Cc: license on the wiki including the hardware schematics and What about making a T-shirt with the hardware schematics? ;) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: U-boot flashing failed?
EH a écrit : I have tried to flash the u-boot from the daily release. After booting up in NOR, I have used the file gta02v5_and_up-u-boot.bin, I am unable to boot up in NAND? When I press power and then aux, the AUX start blinking in Red.. Have I done anything wrong? It boot in NOR ? Low battery ? Wait a little, a few times after it boot normaly, if it was the low battery case. Maelvon ___ 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: andy-tracking kernel?
Hi Andy, On Wed, 2008-12-03 at 16:36 +, Andy Green wrote: ~ - WLAN driver now uses mainline SDIO stack (should fix some probs) Does that mean WiFi is working now ? Thanks, Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi Andy, | | On Wed, 2008-12-03 at 16:36 +, Andy Green wrote: | ~ - WLAN driver now uses mainline SDIO stack (should fix some probs) | | Does that mean WiFi is working now ? Wifi has been working (for some values of working) for a long while... what bad behaviour does not working look like for you? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3qRIACgkQOjLpvpq7dMqofwCgiF7V+PzyU8gggDNphszuwUyT 02QAoI7n1sGzzWGrCL8smhyPg9G4KU9A =9gnV -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Gsm problem
Ok yesterday after some test (for understand if the update of the gsm is ok!) and the gsm start ! After the reboot I see it dosen't work again.. :( I saw 3 strange events: At the boot before the boots I see 2 error: The message of setting time stop the boot for some time (4-5 seconds) after this message I recive some error: crcfail=0x1a33 (I thinks is too fast!) and other message that I can't read.. At the finish of the booting the gsm dosen't work and the time is wrong!!! Why?? Some help? Thanks!! Yes I finish it.. But now I can't use my old 64 k sim.. :( 2008/12/2 Cédric DUFOUIL [EMAIL PROTECTED]: Hi, Did you get this when you complete the flash ? (fluid, version 3) ok Checksumming (269 * 8kB = 2152kB): ok Flash Detect: (0xEC, 0x22A0) Samsung K5A3240CT ok Program: (34 sectors, 267*8k=2136k) (***) ok If yes, it mens that the flash is OK. Maybe the new firmware doesn't solve the compatibility with your SIM On Tue, Dec 2, 2008 at 4:12 PM, Martino [EMAIL PROTECTED] wrote: Hi, I have a om freerunner with om 2008.9 and a sim 128k (vodafone it) and it doesn't work.. I tried to flash the gsm firmware and I finished the procedure like the wiki says but it don't work.. Could I have make a mistake? Where? How to check the gsm? Thanks and sorry for my bad english.. Martino ___ 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 -- Martino -- Martino ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems
any help would be greatly appreciated. well, it would be _really_ helpful, if you could specify what your problem is and how it manifests itself. ___ 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: Funding Global Domination
as Arne correctly spotted I was only interested in helping fund global domination, which does not come for free. I can design my own T Shirt and have it made but benefit to OM = Zero. Not interested in this at all. If OM have made it clear they are not into derived products then that answers the question I asked and the subject is closed. Still, if someone makes fan-art T-shirts design and post it at lafraise.com or elsewhere, I am interested. Minh ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
On Thu, 2008-12-04 at 09:55 +, Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi Andy, | | On Wed, 2008-12-03 at 16:36 +, Andy Green wrote: | ~ - WLAN driver now uses mainline SDIO stack (should fix some probs) | | Does that mean WiFi is working now ? Wifi has been working (for some values of working) for a long while... what bad behaviour does not working look like for you? Well, if you ask for it: - can only connect through command-line (not that important) - weak signal - connexion lasts only for a few minutes - after connexion is lost, reconnecting nearly always involves rebooting I think I already sent the kernel messages that appear in that case somewhere. I must confess that, as I wanted to use my Neo as a sort of internet tablet, it now just gathers dust somewhere, waiting for a WiFi fix. HTH, Xav ___ 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: andy-tracking kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Wifi has been working (for some values of working) for a long while... | what bad behaviour does not working look like for you? | | Well, if you ask for it: | - can only connect through command-line (not that important) Sean McNeil is targeting getting the Android UI for that working at any rate. | - weak signal Weak transmission or RX or both? | - connexion lasts only for a few minutes Hum. | - after connexion is lost, reconnecting nearly always involves rebooting Well, if this is due to SDIO side errors, this situation can have been improved in andy-tracking. If it's due to firmware trouble, probably this will never be fixed due to Atheros closed firmware policies. | I think I already sent the kernel messages that appear in that case | somewhere. I must confess that, as I wanted to use my Neo as a sort of | internet tablet, it now just gathers dust somewhere, waiting for a WiFi | fix. Changing the SDIO stack is enough of a jolt it's probably worth blowing the dust off and having another go according to your optimism / schedule :-) At any rate if you do this please post on kernel list about your experiences. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3wUQACgkQOjLpvpq7dMq3vACfe0uMjBCMueWANbTmtOuPTpvR VPcAn10hXLCc0XNUhX7wF5FacR4OPNRW =V0aw -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
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: working SIM install, network problems
On Thu, Dec 4, 2008 at 7:24 AM, Rodney Myers [EMAIL PROTECTED] wrote: Debian stable, and neorunner I have a semi-functioning Neo right now, thanks to the Hackable:1 folkes (http://www.hackable1.org/) I have changed all instances, that I find, from 192.168.0.* to 192.168.1.*, for my lan. I've followed this wiki page for networking debian; http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others also changing the 192.168.0.* address'. Hello Rodney, I really hesitate to say anything, being overcome with admiration of anyone who can follow that wiki page that you quote. It looks far too complex for normal humans and far too automated for someone who is just starting. If you dont agree with that then best to ignore what I have to say. I have tried many images. One of the first things that becomes obvious is that attempts to change the mind of the Neo to use other than the network 192.168.0 will lead to serious frustration. So I accept that. My home network is equally determined to be 192.168.2 When I want to comunicate from my PC to the Neo via the USB, I join them with the USB cable and on the PC run this little script ( as root) #!/bin/sh /sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0 /sbin/route add -host 192.168.0.202/32 dev usb0 Then I run this one #!/bin/sh /bin/echo 1 /proc/sys/net/ipv4/ip_forward iptables -F iptables -A INPUT -s 192.168.0.202 -i usb0 -d 192.168.0.200 -j ACCEPT iptables -A INPUT -s 192.168.0.200 -i eth+ -d 192.168.0.202 -j ACCEPT iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -j ACCEPT iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.2.0/24 -j ACCEPT iptables -A FORWARD -s 192.168.0.202 -i usb0 -d 192.168.2.0/24 -o eth+ -j ACCEPT iptables -A FORWARD -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -o usb0 -j ACCEPT iptables -A OUTPUT -d 192.168.2.0/24 -o eth+ -j ACCEPT iptables -A OUTPUT -d 192.168.0.202 -o usb0 -j ACCEPT iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 At this stage I can do ssh [EMAIL PROTECTED] Normally it will argue and I have to edit the file ~/.ssh/known hosts by removing the line it is objecting to. It will then agree to the ssh. Most people automate that process to avoid the editing etc but that is a matter of taste only. Once you have things going without trouble you can automate a lot of things. good luck, clare ___ 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: Bounties?
Do you think it is a good idea to start a bounties page on the wiki? People can post their detailed bounties on the page with details of how to contact them. The developers can claim the bounties once they feel they have fulfilled the task. Rakshat On Thu, Dec 4, 2008 at 1:40 PM, Michael Kluge [EMAIL PROTECTED] wrote: I'd pay ~50 for a thing like Agendus on Palm OS. http://www.iambic.com/agendus/palmos/ That can sync to Evolution (at least Calendar and Contacts) and has good mail app. QT mail is not usable, clawsmail is a lot better but not optimized for a small screen. Michael Sargun Dhillon schrieb: Just out of curiosity, how many OpenMoko users out there would be willing to pay for bounties? Additionally, how many developers would work for bounties? What sort of bounties would you guys request? How much would you pay? ___ 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 -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Funding Global Domination
all you have to do is ask me. I like saying yes. Rui Miguel Silva Seabra wrote: On Wed, Dec 03, 2008 at 09:51:44AM +0100, Minh Ha Duong wrote: Could somebody official in OpenMoko respond to this email and perhaps indicate whether the company would be interested in this idea and perhaps some way of gauging if the community is interested? Perhaps somebody in the Community could design a cool subtle OpenMoko garment? The second option is more like it. It takes a few hours to design a T-Shirt and upload it to an online store where everybody else can go and buy it. So just do it: the entry costs are so low that there is no real need for a formal market study ! There may be trademark issues, better clear that with OpenMoko first! Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Funding Global Domination
what about combining the T-shirt bounty ideas ? Use the money from the T-Shirts to have some extra bounty budget. F. On Thu, 04 Dec 2008 13:31:27 +0100, Steve Mosher [EMAIL PROTECTED] wrote: all you have to do is ask me. I like saying yes. Rui Miguel Silva Seabra wrote: On Wed, Dec 03, 2008 at 09:51:44AM +0100, Minh Ha Duong wrote: Could somebody official in OpenMoko respond to this email and perhaps indicate whether the company would be interested in this idea and perhaps some way of gauging if the community is interested? Perhaps somebody in the Community could design a cool subtle OpenMoko garment? The second option is more like it. It takes a few hours to design a T-Shirt and upload it to an online store where everybody else can go and buy it. So just do it: the entry costs are so low that there is no real need for a formal market study ! There may be trademark issues, better clear that with OpenMoko first! Rui ___ 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: Optimization team update (11/23 ~ 11/29)
Hi, Joerg went over the change for a5/a6 with me the other night. Over the next few days I'll drive to get an SOP published for the change. But for now I'll just explain it in words. The modification should work for both a5a6. It consists of: 1. Removing the front cover. 2. Changing a resistor ( in some cases this is not necessary) 3. Adding a Cap. Steve Jakob wrote: On Tue, Dec 2, 2008 at 9:42 PM, Andy Green [EMAIL PROTECTED] wrote: buzz / echo / hiss... no software change can fix buzz. It's baked into the hardware and you will have to do fairly extreme meddling with your soldering iron to impact it. Would it be better to wait until A7 is out and then buy a Freerunner? How hard is it to do the component change on a A6? Jake ___ 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: andy-tracking kernel?
On Thu, 2008-12-04 at 11:38 +, Andy Green wrote: I must confess that, as I wanted to use my Neo as a sort of | internet tablet, it now just gathers dust somewhere, waiting for a WiFi | fix. Changing the SDIO stack is enough of a jolt it's probably worth blowing the dust off and having another go according to your optimism / schedule :-) At any rate if you do this please post on kernel list about your experiences. Right, I'll try in my copious spare time. Would it be possible for you to put a small README in your directory, to explain how to use these files ? Even if it's just a pointer to somewhere on the wiki, it'd be great. Thanks, Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
improved in andy-tracking. If it's due to firmware trouble, probably this will never be fixed due to Atheros closed firmware policies. wasn't there recently a release of an completely open atheros driver? http://www.heise-online.co.uk/news/MadWifi-HAL-now-open-source--/112113 or did that not apply to the chip used in the fr? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Thu, 2008-12-04 at 13:54 +0100, arne anka wrote: | improved in andy-tracking. If it's due to firmware trouble, probably | this will never be fixed due to Atheros closed firmware policies. | wasn't there recently a release of an completely open atheros driver? | http://www.heise-online.co.uk/news/MadWifi-HAL-now-open-source--/112113 | or did that not apply to the chip used in the fr? | | There are working drivers for ath5k and ath9k, but the Neo has an | ath6k ... Yes the main difference is that the AR6001 in GTA02 is what's called a fullmac device, it means that it has an 80211 stack in the firmware of the device that can run autonomously. That's in contrast to the other devices which use a softmac 80211 stack in Linux. The advantage is that it can run autonomously somewhat even with Linux down, the disadvantage is we are entirely at the mercy of the not-really-updateable closed firmware for a very wide range of operations. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3164ACgkQOjLpvpq7dMpeMQCaAqluqq4S+c4xiveBgVVMTfvt 5AUAn2cBOrC3CGtoxYsEFU9kPZsJpUPK =VO5V -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Funding Global Domination
please do. DJDAS wrote: Arigead ha scritto: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Minh Ha Duong wrote: Le mercredi 03 décembre 2008, arne anka a écrit : The second option is more like it. It takes a few hours to design a T-Shirt and upload it to an online store where everybody else can go and buy it. So just do it: the entry costs are so low that there is no real need for a formal market study ! Rui: There are lots of cool artwork under a Cc: license on the wiki including the hardware schematics and What about making a T-shirt with the hardware schematics? ;) ___ 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: Funding Global Domination
Awesome :) On Thu, Dec 04, 2008 at 04:31:27AM -0800, Steve Mosher wrote: all you have to do is ask me. I like saying yes. Rui Miguel Silva Seabra wrote: On Wed, Dec 03, 2008 at 09:51:44AM +0100, Minh Ha Duong wrote: Could somebody official in OpenMoko respond to this email and perhaps indicate whether the company would be interested in this idea and perhaps some way of gauging if the community is interested? Perhaps somebody in the Community could design a cool subtle OpenMoko garment? The second option is more like it. It takes a few hours to design a T-Shirt and upload it to an online store where everybody else can go and buy it. So just do it: the entry costs are so low that there is no real need for a formal market study ! There may be trademark issues, better clear that with OpenMoko first! -- All Hail Discordia! Today is Pungenday, the 46th day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Funding Global Domination
That would be soo geeky, great idea! :D -- Marcel Am Thursday 04 December 2008 14:23:40 schrieb Steve Mosher: please do. DJDAS wrote: Arigead ha scritto: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Minh Ha Duong wrote: Le mercredi 03 décembre 2008, arne anka a écrit : The second option is more like it. It takes a few hours to design a T-Shirt and upload it to an online store where everybody else can go and buy it. So just do it: the entry costs are so low that there is no real need for a formal market study ! Rui: There are lots of cool artwork under a Cc: license on the wiki including the hardware schematics and What about making a T-shirt with the hardware schematics? ;) ___ 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: Funding Global Domination
Steve Mosher ha scritto: please do. DJDAS wrote: What about making a T-shirt with the hardware schematics? ;) Well :) I'm a bit practical with The Gimp, I'll try to do something in the weekend, in the meantime I accept suggestions for the file format, size, color numbers and so on so I'll have some guides before doing any work...Never made a T-shirt before :P Bye! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Funding Global Domination
I've good experiences with http://cafepress.com for t-shirts. Send me an email and I will reply with some URLs with some nice examples. On Thu, December 4, 2008 14:28, Rui Miguel Silva Seabra wrote: Awesome :) On Thu, Dec 04, 2008 at 04:31:27AM -0800, Steve Mosher wrote: all you have to do is ask me. I like saying yes. Rui Miguel Silva Seabra wrote: On Wed, Dec 03, 2008 at 09:51:44AM +0100, Minh Ha Duong wrote: Could somebody official in OpenMoko respond to this email and perhaps indicate whether the company would be interested in this idea and perhaps some way of gauging if the community is interested? Perhaps somebody in the Community could design a cool subtle OpenMoko garment? The second option is more like it. It takes a few hours to design a T-Shirt and upload it to an online store where everybody else can go and buy it. So just do it: the entry costs are so low that there is no real need for a formal market study ! There may be trademark issues, better clear that with OpenMoko first! -- All Hail Discordia! Today is Pungenday, the 46th day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ 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: Funding Global Domination
Pander ha scritto: I've good experiences with http://cafepress.com for t-shirts. Send me an email and I will reply with some URLs with some nice examples. i think http://www.spreadshirt.net/ is better ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems
On Dec 4, 2008, at 2:04 AM, arne anka wrote: any help would be greatly appreciated. well, it would be _really_ helpful, if you could specify what your problem is and how it manifests itself. When I plug the OM into the debian machine, i know it gets connected. the output of dmesg says so. From both the Neo or the debian machine, pinging the other does not work, no packets returned. I can take SD card, mount it to the debian machine and edit all necessary files, then reinsert into the OM to get it to boot. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: TwitterMoko 0.4 out
Joachim Breitner ha scritto: (sorry for my bad ensligh) * Please use a proper setup.py (using the python distutils) to install your files into the proper locations. See http://git.debian.org/?p=pkg-fso/openmoko-panel-plugin.git;a=blob;f=setup.py;h=d6056f95561b9a8f4f602fc968e0bc8e6ca7a18b;hb=HEAD as an example. * Using this setup.py, you can create proper and consistent tar-balls using ./setup.py sdist. Make sure that you set the version number corresponding, and check that all required files are included. ok... i'm looking it tomorrow Additionally, while reading through your code, I’m wondering (please don’t take this personally): Does TwitterMoko have any advantages over existing projects such as twitux? What are it’s distinct features? Is there is not a package of twitux for openmoko, and i'm not know how to recompile. i talk about om2008 and SHR there a good reason to fork and launch curl for each access, passing all parameters via the commandline and possibly not fully escaped, and blocking on the output of curl, instead of using some asynchronous http library directly? yes... when i code i have use libcurl in my computer but after i have see there is not the package python-pycurl for om2008 Also, the config should be saved in, say ~/.twittermoko.cfg, instead of a global place, and probably created with mode 660 (who knows, someone might actually have a guest ssh login to his FreeRunner :-) this is a very good idea! in the next release... I hope this does not discourage you from working on TwitterMoko, but give you some hints on how to improve it – but I think befor inclusion in Debian, things have to evolve a litte bit. mhh... i don't know... :) i have start to code twittermoko because i have not found a client for om2008 :) only this see you ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems
On Dec 4, 2008, at 3:57 AM, clare johnstone wrote: On Thu, Dec 4, 2008 at 7:24 AM, Rodney Myers [EMAIL PROTECTED] wrote: Debian stable, and neorunner I have a semi-functioning Neo right now, thanks to the Hackable:1 folkes (http://www.hackable1.org/) I have changed all instances, that I find, from 192.168.0.* to 192.168.1.*, for my lan. I've followed this wiki page for networking debian; http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others also changing the 192.168.0.* address'. Hello Rodney, I really hesitate to say anything, being overcome with admiration of anyone who can follow that wiki page that you quote. It looks far too complex for normal humans and far too automated for someone who is just starting. If you dont agree with that then best to ignore what I have to say. I have tried many images. One of the first things that becomes obvious is that attempts to change the mind of the Neo to use other than the network 192.168.0 will lead to serious frustration. So I accept that. My home network is equally determined to be 192.168.2 When I want to comunicate from my PC to the Neo via the USB, I join them with the USB cable and on the PC run this little script ( as root) #!/bin/sh /sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0 /sbin/route add -host 192.168.0.202/32 dev usb0 Then I run this one #!/bin/sh /bin/echo 1 /proc/sys/net/ipv4/ip_forward iptables -F iptables -A INPUT -s 192.168.0.202 -i usb0 -d 192.168.0.200 -j ACCEPT iptables -A INPUT -s 192.168.0.200 -i eth+ -d 192.168.0.202 -j ACCEPT iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -j ACCEPT iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.2.0/24 -j ACCEPT iptables -A FORWARD -s 192.168.0.202 -i usb0 -d 192.168.2.0/24 -o eth+ -j ACCEPT iptables -A FORWARD -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -o usb0 -j ACCEPT iptables -A OUTPUT -d 192.168.2.0/24 -o eth+ -j ACCEPT iptables -A OUTPUT -d 192.168.0.202 -o usb0 -j ACCEPT iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 At this stage I can do ssh [EMAIL PROTECTED] Normally it will argue and I have to edit the file ~/.ssh/known hosts by removing the line it is objecting to. It will then agree to the ssh. Most people automate that process to avoid the editing etc but that is a matter of taste only. Once you have things going without trouble you can automate a lot of things. good luck, clare Thanks for the tip(s). The wiki is ponderous, but gleaned what i hoped was a working set of instructions. I have the above printed out, and may re-install the image(s) to get a default install and try again. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems
On Thu, 2008-12-04 at 07:17 -0800, Rodney Myers wrote: On Dec 4, 2008, at 2:04 AM, arne anka wrote: any help would be greatly appreciated. well, it would be _really_ helpful, if you could specify what your problem is and how it manifests itself. When I plug the OM into the debian machine, i know it gets connected. the output of dmesg says so. On your PC, what do you get from: $ ifconfig usb0 And on your FR, what do you get from: $ ifconfig usb0 ...cj ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems
On Thu, 2008-12-04 at 07:19 -0800, Rodney Myers wrote: On Dec 4, 2008, at 3:57 AM, clare johnstone wrote: When I want to comunicate from my PC to the Neo via the USB, I join them with the USB cable and on the PC run this little script ( as root) #!/bin/sh /sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0 /sbin/route add -host 192.168.0.202/32 dev usb0 Then I run this one #!/bin/sh /bin/echo 1 /proc/sys/net/ipv4/ip_forward iptables -F iptables -A INPUT -s 192.168.0.202 -i usb0 -d 192.168.0.200 -j ACCEPT iptables -A INPUT -s 192.168.0.200 -i eth+ -d 192.168.0.202 -j ACCEPT iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -j ACCEPT iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.2.0/24 -j ACCEPT iptables -A FORWARD -s 192.168.0.202 -i usb0 -d 192.168.2.0/24 -o eth+ -j ACCEPT iptables -A FORWARD -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -o usb0 -j ACCEPT iptables -A OUTPUT -d 192.168.2.0/24 -o eth+ -j ACCEPT iptables -A OUTPUT -d 192.168.0.202 -o usb0 -j ACCEPT iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 I few comments from my own experience. I used to be able to configure usb0 on the PC manually like above, but after either a FR software change or possibly my upgrade on PC to Fedora 9, that no longer worked. Instead, I followed the wiki directions to set it up via the UI and I can now do ifup usb0 after connecting the FR to PC. Also, note that all the iptables commands are necessary only to communicate to the internet from FR via the PC. I'd skip those steps until you can successfully ping from PC to FR. ...cj ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: working SIM install, network problems
When I plug the OM into the debian machine, i know it gets connected. the output of dmesg says so. and according to the snippet from log, usb0 is up at your side with ip 192.168.1.200. From both the Neo or the debian machine, pinging the other does not work, no packets returned. probably no route set route add 192.168.1.202 usb0 ? please post the output of of netstat -rn from your side (ie not freerunner). and the output of ifconfig on both your side and the fr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: TwitterMoko 0.4 out
Hi, Am Donnerstag, den 04.12.2008, 16:18 +0100 schrieb Carlo Minucci: there is not a package of twitux for openmoko, and i'm not know how to recompile. i talk about om2008 and SHR i have start to code twittermoko because i have not found a client for om2008 :) only this All very valid, and of course it it more fun and gives you more power over your program. But generally, it’s advisable to re-use existing code – in this case, instead of re-coding the applications, it would have been more beneficial to the general community to make sure that twitux and it’s dependencies are built in openembedded. But that’s just my opinion, and again, don’t be discouraged by this. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ 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: [OM2008.x] praise for the new testing image
Yes, that's how I get my ballance... it's the operator that automatically sends it at hangup. I confirm that the dialer exits when we try to do it upon request... Citando Marco Trevisan (Treviño) [EMAIL PROTECTED]: Vadim, Efimov wrote: Another 2 positive points I forgot to mention: - the UCSD messages are now correctly displayed (yay, I can see my account balance!!) how? i call *102# and dialer just disappear... I figure that actually only the ones sent by operator (with no an explicit request, i.e. after a call) are working. There's an issue while placing an USSD request... -- 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
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: [OM2008.x] praise for the new testing image
I also went that way and hacked the qwerty button in again (but not
the wrench - didn't know how).
However, the button is there and it reacts, but the keyboard does not appear.
Instead, it controls the appearance of the qtopia keyboard...
How do we reach the illume keyboard from this button?
Citando John Lee [EMAIL PROTECTED]:
On Wed, Dec 03, 2008 at 08:36:53AM -0800, Martin Benz wrote:
Read the bugreport:
https://docs.openmoko.org/trac/ticket/1767
So we have a slow illume-theme with rasters keyboard or a fast asu-theme
without an usable keyboard (especially for non-engish users)...
Maybe i'll try to hack the edj-file, did manage to get the qwerty-menu back
in the wrench, but messing around with the keyboard only gave me errors when
running build.sh...
(See Method 2 from http://wiki.openmoko.org/wiki/Keyboard_Toggle)
cheers
Martin
actually it's quite easy to bring back the wrench and the qwerty
buttons in asu theme. it's not the real issue though.
wrench: it's a gadget to put on the illume 'shelf'. so just add it
back into the config then it will show up. something like this
(haven't tested):
Index: illume-theme-asu/config/e.src
===
--- illume-theme-asu/config/e.src (revision 4796)
+++ illume-theme-asu/config/e.src (working copy)
@@ -428,6 +428,24 @@
value resizable uchar: 0;
}
}
+ group clients list {
+group E_Config_Gadcon_Client struct {
+ value name string: configuration;
+ value id string: configuration;
+ value geom.pos int: 0;
+ value geom.size int: 32;
+ value geom.res int: 472;
+ value geom.pos_x double: 0.0;
+ value geom.pos_y double: 0.0;
+ value geom.size_w double: 0.0;
+ value geom.size_h double: 0.0;
+ value state_info.seq int: 1;
+ value state_info.flags int: 1;
+ value style string: plain;
+ value autoscroll uchar: 0;
+ value resizable uchar: 0;
+}
+ }
}
}
value font_hinting int: 0;
qwerty: enable it in the theme.
Index: illume-theme-asu/misc-data/asu/freerunner.edc
===
--- illume-theme-asu/misc-data/asu/freerunner.edc (revision 4796)
+++ illume-theme-asu/misc-data/asu/freerunner.edc (working copy)
@@ -1575,8 +1575,8 @@
type: RECT;
mouse_events: 1;
description { state: default 0.0;
-// visible: 1;
-visible: 0; // sean wants it gone. don't look at me.
+visible: 1;
+// visible: 0; // sean wants it gone. don't look at me.
color: 0 0 0 0;
rel1 {
to_y: e.swallow.content;
@@ -1585,8 +1585,8 @@
rel2 {
to_x: kbdtext;
to_y: e.swallow.content;
-// relative: 1.0 1.0;
- relative: 0.0 1.0; // sean wants it gone. don't look at me.
+ relative: 1.0 1.0;
+// relative: 0.0 1.0; // sean wants it gone. don't look at me.
offset: -1 -1;
}
}
@@ -1595,8 +1595,8 @@
type: TEXT;
mouse_events: 0;
description { state: default 0.0;
-// visible: 1;
-visible: 0; // sean wants it gone. don't look at me.
+visible: 1;
+// visible: 0; // sean wants it gone. don't look at me.
align: 0.0 1.0;
fixed: 1 1;
rel1 {
the real problem is, after you click on the wrench, it will show the
config menu, but click on any one of them will give you black screen.
probably black fonts on black background. I hope someone can find out
what went wrong because I don't have time to work on it.
- John
Vasco Névoa wrote:
I've been trying the illume (gray) theme with the testing image, and
it is badly broken - Enlightenment keeps crashing at random moments
for reasons unknown.
I gave up on trying to have illume's keyboard, and reverted to the
original asu (black) theme. The qtopian keyboard sucks, but at least
everything else rocks.
I find it very strange that the whole image works so solidly with the
asu theme and is so flakey with the illume theme...
Citando Vasco Névoa [EMAIL PROTECTED]:
Citando William Kenworthy [EMAIL PROTECTED]:
And also yes, I have modified 89qtopia - but it doesn't seem to have
much of an effect :(
I found out how my illume keyboard went missing. From the wiki:
edit '/etc/enlightenment/default_profile' to use illume theme
instead of 'asu'
So, if you just want to get rid of it, replace illume with asu inside
/etc/enlightenment/default_profile ...
But if you want to keep it
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: OMoney? :O
Hi OMoney is a little application by me. It is far from being finished but the main features work and it is under steady development (if everything goes well the first release might be this weekend) code can be found at omoney.googlecode.com DJDAS wrote: Hi all, I was thinking about an expense handling program (like HandyExpenses on Symbian phones), I have many ideas in mind but didn't write anything yet, but looking at some screenshots at linuxtogo I saw these: http://scap.linuxtogo.org/index.php?page=6 I didn't find such an application (tried googling and at opkg.org)...Does anybody knows where to find and try it? Thank you in advance, bye! ___ 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: Optimization team update (11/23 ~ 11/29)
Thanks Steve for this little insight. As the mod doesn't seem that hard to do, I'm looking forward to my Freerunner for christmas (regardless if its A7 or a not yet reworked A6 :) ). Jake On Thu, Dec 4, 2008 at 1:46 PM, Steve Mosher [EMAIL PROTECTED] wrote: Hi, Joerg went over the change for a5/a6 with me the other night. Over the next few days I'll drive to get an SOP published for the change. But for now I'll just explain it in words. The modification should work for both a5a6. It consists of: 1. Removing the front cover. 2. Changing a resistor ( in some cases this is not necessary) 3. Adding a Cap. Steve ___ 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: TwitterMoko 0.4 out
TwitterMoko is very cool and I always use it ;) However, are you interested to make a client for Facebook? I really appreciate it too :) I've started something using the nice Elementary library by Raster friends :P. It looks nice on my PC [1], but I've not tested it on the phone yet :| Bye! [1] http://3v1n0.net/openmoko/Facebook-FacElementaryBook-wip1.png -- 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
Where can I find this game?
Oh, I've found one of the games I've played more when I was young :P screenshotted on scap [1]. Now I forgot its name, where can I find it? :) Maybe I've some saves around too...! ;) [1] http://img407.imageshack.us/my.php?image=a2cb0faac134c6ba717ab4bhc6.png -- 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
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: U-boot flashing failed?
It is indeed low in battery...Didn't know the battery got drained out that fast... Thanks for the help :) 2008/12/4 Maelvon HAWK [EMAIL PROTECTED]: EH a écrit : I have tried to flash the u-boot from the daily release. After booting up in NOR, I have used the file gta02v5_and_up-u-boot.bin, I am unable to boot up in NAND? When I press power and then aux, the AUX start blinking in Red.. Have I done anything wrong? It boot in NOR ? Low battery ? Wait a little, a few times after it boot normaly, if it was the low battery case. Maelvon ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Edward Hsiao ___ 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
[android] Building Android from the Koolu Source
I've been able to successfully build an Android rootfs from the Koolu repository. When flashed to my phone with the kernel that Sean provided, it runs with just about the same set of issues as the images that Sean has put up. I've documented how I did it on the wiki at: http://wiki.openmoko.org/wiki/Android#Building_the_Koolu_Android_Source Thanks to the folks at Koolu for hosting the repository, and to Sean McNeil, Brian Code and others who have contributed to the port! Now that it's available and buildable, I hope we in the community can start contributing to their excellent work! While I'm sending this message to both the Community and Development lists, please send follow-ups to the development list ([EMAIL PROTECTED]) only! I'll be happy to answer questions or clarify anything I can. Jim ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
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: [android] Building Android from the Koolu Source
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 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
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: [android] Building Android from the Koolu Source
Hi, In order to make the compile process straightforward as Marcelo said, I've made these 2 scripts compile.sh and build-jffs2.sh (a combination of Sean scripts cp_android_OS and mkjffs2). Place them in the root of Koolu source tree and then to compile and produce de jffs2 image, do: $ ./compile.sh $./build-jffs2.sh release androidfs.jffs2 On Fri, Dec 5, 2008 at 4:14 AM, Marcelo [EMAIL PROTECTED] 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 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 compile.sh Description: Bourne shell script build-jffs2.sh Description: Bourne shell script ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OM2008.x] praise for the new testing image
On Thu, Dec 04, 2008 at 06:07:38PM +, Vasco Névoa wrote:
I also went that way and hacked the qwerty button in again (but not
the wrench - didn't know how).
However, the button is there and it reacts, but the keyboard does not appear.
Instead, it controls the appearance of the qtopia keyboard...
How do we reach the illume keyboard from this button?
* disable the qtopia keyboard
* enable the illume one if it still doesn't show up. you need to hack
eet file because wrench doesn't work.
Once wrench works this will be pretty easy though.
- John
Citando John Lee [EMAIL PROTECTED]:
On Wed, Dec 03, 2008 at 08:36:53AM -0800, Martin Benz wrote:
Read the bugreport:
https://docs.openmoko.org/trac/ticket/1767
So we have a slow illume-theme with rasters keyboard or a fast asu-theme
without an usable keyboard (especially for non-engish users)...
Maybe i'll try to hack the edj-file, did manage to get the qwerty-menu back
in the wrench, but messing around with the keyboard only gave me errors
when
running build.sh...
(See Method 2 from http://wiki.openmoko.org/wiki/Keyboard_Toggle)
cheers
Martin
actually it's quite easy to bring back the wrench and the qwerty
buttons in asu theme. it's not the real issue though.
wrench: it's a gadget to put on the illume 'shelf'. so just add it
back into the config then it will show up. something like this
(haven't tested):
Index: illume-theme-asu/config/e.src
===
--- illume-theme-asu/config/e.src (revision 4796)
+++ illume-theme-asu/config/e.src (working copy)
@@ -428,6 +428,24 @@
value resizable uchar: 0;
}
}
+ group clients list {
+group E_Config_Gadcon_Client struct {
+ value name string: configuration;
+ value id string: configuration;
+ value geom.pos int: 0;
+ value geom.size int: 32;
+ value geom.res int: 472;
+ value geom.pos_x double: 0.0;
+ value geom.pos_y double: 0.0;
+ value geom.size_w double: 0.0;
+ value geom.size_h double: 0.0;
+ value state_info.seq int: 1;
+ value state_info.flags int: 1;
+ value style string: plain;
+ value autoscroll uchar: 0;
+ value resizable uchar: 0;
+}
+ }
}
}
value font_hinting int: 0;
qwerty: enable it in the theme.
Index: illume-theme-asu/misc-data/asu/freerunner.edc
===
--- illume-theme-asu/misc-data/asu/freerunner.edc (revision 4796)
+++ illume-theme-asu/misc-data/asu/freerunner.edc (working copy)
@@ -1575,8 +1575,8 @@
type: RECT;
mouse_events: 1;
description { state: default 0.0;
-//visible: 1;
- visible: 0; // sean wants it gone. don't look at me.
+ visible: 1;
+//visible: 0; // sean wants it gone. don't look at me.
color: 0 0 0 0;
rel1 {
to_y: e.swallow.content;
@@ -1585,8 +1585,8 @@
rel2 {
to_x: kbdtext;
to_y: e.swallow.content;
-// relative: 1.0 1.0;
- relative: 0.0 1.0; // sean wants it gone. don't look at me.
+ relative: 1.0 1.0;
+// relative: 0.0 1.0; // sean wants it gone. don't look at me.
offset: -1 -1;
}
}
@@ -1595,8 +1595,8 @@
type: TEXT;
mouse_events: 0;
description { state: default 0.0;
-//visible: 1;
- visible: 0; // sean wants it gone. don't look at me.
+ visible: 1;
+//visible: 0; // sean wants it gone. don't look at me.
align: 0.0 1.0;
fixed: 1 1;
rel1 {
the real problem is, after you click on the wrench, it will show the
config menu, but click on any one of them will give you black screen.
probably black fonts on black background. I hope someone can find out
what went wrong because I don't have time to work on it.
- John
Vasco Névoa wrote:
I've been trying the illume (gray) theme with the testing image, and
it is badly broken - Enlightenment keeps crashing at random moments
for reasons unknown.
I gave up on trying to have illume's keyboard, and reverted to the
original asu (black) theme. The qtopian keyboard sucks, but at least
everything else rocks.
I find it very strange that the whole image works so solidly with the
asu theme and is so flakey with the illume theme...
Citando Vasco Névoa [EMAIL PROTECTED]:
Citando William Kenworthy [EMAIL PROTECTED]:
And also yes, I have modified 89qtopia - but it doesn't
Re: Funding Global Domination
Let me look into doing this on cafepress. Marcel wrote: That would be soo geeky, great idea! :D -- Marcel Am Thursday 04 December 2008 14:23:40 schrieb Steve Mosher: please do. DJDAS wrote: Arigead ha scritto: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Minh Ha Duong wrote: Le mercredi 03 décembre 2008, arne anka a écrit : The second option is more like it. It takes a few hours to design a T-Shirt and upload it to an online store where everybody else can go and buy it. So just do it: the entry costs are so low that there is no real need for a formal market study ! Rui: There are lots of cool artwork under a Cc: license on the wiki including the hardware schematics and What about making a T-shirt with the hardware schematics? ;) ___ 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: [OM2008.x] praise for the new testing image
On Thu, Dec 04, 2008 at 06:05:04PM +, Vasco Névoa wrote: Yes, that's how I get my ballance... it's the operator that automatically sends it at hangup. I confirm that the dialer exits when we try to do it upon request... I would like to know how many people need this. My resource for qtopia is very limited and I need to decide what to fix first. - John Citando Marco Trevisan (Treviño) [EMAIL PROTECTED]: Vadim, Efimov wrote: Another 2 positive points I forgot to mention: - the UCSD messages are now correctly displayed (yay, I can see my account balance!!) how? i call *102# and dialer just disappear... I figure that actually only the ones sent by operator (with no an explicit request, i.e. after a call) are working. There's an issue while placing an USSD request... -- 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Funding Global Domination
use cafepress, when I tried to get this going internally that was my choice. DJDAS wrote: Steve Mosher ha scritto: please do. DJDAS wrote: What about making a T-shirt with the hardware schematics? ;) Well :) I'm a bit practical with The Gimp, I'll try to do something in the weekend, in the meantime I accept suggestions for the file format, size, color numbers and so on so I'll have some guides before doing any work...Never made a T-shirt before :P Bye! ___ 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: [OM2008.x] praise for the new testing image
On Fri, 05 Dec 2008 08:05:19 +0300, John Lee [EMAIL PROTECTED] wrote: On Thu, Dec 04, 2008 at 06:05:04PM +, Vasco Névoa wrote: Yes, that's how I get my ballance... it's the operator that automatically sends it at hangup. I confirm that the dialer exits when we try to do it upon request... I would like to know how many people need this. My resource for qtopia is very limited and I need to decide what to fix first. - John mmm... how many people need USSD ? In Russia it is difficult get balance other way, and the USSD-message comes in cyrillic letters. also, we have many services via USSD... but, i'm not know how many freerunners sold in Russia. at least 20-30. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Where can I find this game?
http://www.openttd.org/ I'm just not sure how playable this one will be on such a small display :( Marco Trevisan (Treviño) wrote: Oh, I've found one of the games I've played more when I was young :P screenshotted on scap [1]. Now I forgot its name, where can I find it? :) Maybe I've some saves around too...! ;) [1] http://img407.imageshack.us/my.php?image=a2cb0faac134c6ba717ab4bhc6.png ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Where can I find this game?
Yeah played that too a long time ago... :) That's Transport Tycoon - or the opensource clone Simutrans. http://www.simutrans.com/ It would be awesome if there was a package or source for our neo... cheers Martin Marco Trevisan (Treviño) wrote: Oh, I've found one of the games I've played more when I was young :P screenshotted on scap [1]. Now I forgot its name, where can I find it? :) Maybe I've some saves around too...! ;) [1] http://img407.imageshack.us/my.php?image=a2cb0faac134c6ba717ab4bhc6.png -- 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 -- View this message in context: http://n2.nabble.com/Where-can-I-find-this-game--tp1616362p1617217.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: Where can I find this game?
There is definatly an ipk, if after intense googling you cannot find it, post again and i'll possibly (if i can find it) upload it somewhere. Once you install you also need openttd data to have a playable game, there are places that host a .zip (if I'm remembering things right). It is a touch hard to play with things so small, but very playable with a stylus. On Thu, 2008-12-04 at 22:36 -0800, Martin Benz wrote: Yeah played that too a long time ago... :) That's Transport Tycoon - or the opensource clone Simutrans. http://www.simutrans.com/ It would be awesome if there was a package or source for our neo... cheers Martin Marco Trevisan (Treviño) wrote: Oh, I've found one of the games I've played more when I was young :P screenshotted on scap [1]. Now I forgot its name, where can I find it? :) Maybe I've some saves around too...! ;) [1] http://img407.imageshack.us/my.php?image=a2cb0faac134c6ba717ab4bhc6.png -- 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
5 Freerunners for a discounted price (India)
In India we had sent out a few Freerunners as review samples to a number of magazines and websites and have received 5 of these back now. We plan to make these available at a 25% discounted price to students/ hobby linux developers in India. The Freerunners have been checked and refurbished and come a 30 day return policy against Hardware defects. We will also send a note stating which magazine your Freerunner was sent for review to along with the shipment The Price is Rs 16500 inclusive of CST and Blue Dart insured shipping in India. ( $325 Approx) The special price is only for these 5 Freerunners and our normal price remains at Rs 22000. Contact me directly if you are interested. Also check out the December issue of Linux for You. Edgar has done the cover story on the Freerunner based on a phone he bought (not a review sample). Rakshat rakshat at idasystems dot net -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
ntpd status?
How can I find the status for a running ntpd? On desktops, I use ntpq, but this doesnt seem available on the FR - I have ntp, ntpdate and ntp-utils installed so far. grepping the logread for ntp messages isnt enough to see whats going on :( BillK -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
