Re: USB networking broken after Android install
I used NeoTool before, and I must have done something weird because it worked fine with dfu-util. I must have forgotten everything from the last time I did this, thanks for your help. 2010/1/1 Werner Almesberger > Tomas Gustavsson wrote: > > I can't get usb networking working in > > the nor boot menu anymore. > > How exactly does dfu-util fail ? (I assume that's what you mean with > "USB networking". The u-boot boot loader doesn't do TCP/IP, SSH, etc., > and never did.) > > - Werner > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB networking broken after Android install
Tomas Gustavsson wrote: > I can't get usb networking working in > the nor boot menu anymore. How exactly does dfu-util fail ? (I assume that's what you mean with "USB networking". The u-boot boot loader doesn't do TCP/IP, SSH, etc., and never did.) - Werner ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB networking broken after Android install
There's no problem with booting to the NOR boot menu, the problem is that can't get usb networking working when in the nor boot menu. It has worked before but after I installed Android I can't get usb networking working in the nor boot menu anymore. If there's no solution to this then I'll have to try to install SHR to the memory stick or something. 2010/1/1 Joachim Ott > 2010/1/1 Tomas Gustavsson : > > Hi! > > > > First I ran SHR on my Neo Freerunner, at some point I got the stupid idea > of > > trying Android on my phone. It works okay but now I want to reinstall SHR > > but the USB networking doesn't seem to work when I'm in the Phone's > > integrated boot loader anymore. So I'm stuck with Android for now and > can't > > use usb networking (though it works fine when I have booted to Android). > > Boot into NOR boot menu (press+hold AUX, then press+hold Power). Then > you can use dfu-util to flash some good distro. More hints are on > http://wiki.openmoko.org/wiki/Flashing > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB networking broken after Android install
2010/1/1 Tomas Gustavsson : > Hi! > > First I ran SHR on my Neo Freerunner, at some point I got the stupid idea of > trying Android on my phone. It works okay but now I want to reinstall SHR > but the USB networking doesn't seem to work when I'm in the Phone's > integrated boot loader anymore. So I'm stuck with Android for now and can't > use usb networking (though it works fine when I have booted to Android). Boot into NOR boot menu (press+hold AUX, then press+hold Power). Then you can use dfu-util to flash some good distro. More hints are on http://wiki.openmoko.org/wiki/Flashing ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
USB networking broken after Android install
Hi! First I ran SHR on my Neo Freerunner, at some point I got the stupid idea of trying Android on my phone. It works okay but now I want to reinstall SHR but the USB networking doesn't seem to work when I'm in the Phone's integrated boot loader anymore. So I'm stuck with Android for now and can't use usb networking (though it works fine when I have booted to Android). Best regards /Tomas Gustavsson ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: cannot connect to freerunner android
I have had similar problem on Gentoo. try this : export ADBHOST=192.168.0.202 adb kill-server adb devices Vimal Joseph a écrit : On Wed, 2009-09-16 at 11:32 +0530, rakshat hooja wrote: # ifconfig usb0 192.168.0.200 netmask 255.255.255.0 # adb kill-server # ADBHOST=192.168.0.202 adb devices If you have installed Qi loader, find on which eth device the FreeRunner is located (for me, it is eth2). # ifconfig -a Then, issue the following (if you have Qi, and whether you found your eth for FreeRunner. For me it is eth2): # ifconfig eth2 192.168.0.200 netmask 255.255.255.0 # adb kill-server # ADBHOST=192.168.0.202 adb devices I tried this, but no results: r...@gnubox:~# ifconfig eth2 192.168.0.200 netmask 255.255.255.0 r...@gnubox:~# adb kill-server r...@gnubox:~# ADBHOST=192.168.0.202 adb devices * daemon not running. starting it now * * daemon started successfully * List of devices attached r...@gnubox:~# ADBHOST=192.168.0.202 adb shell error: device not found regards, ~vimal ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- __ Fabian Rami Département WebMobile Ligne dir : +32 81 71 57 90 http://www.webmobile.be WOW Company Rue Pieds d'Alouette 18 5100 NANINNE (Belgique) Tel : +32 81 40 19 66 Fax : +32 81 40 24 44 http://www.wowcompany.com __ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: cannot connect to freerunner android
On Wed, 2009-09-16 at 11:32 +0530, rakshat hooja wrote: > > > # ifconfig usb0 192.168.0.200 netmask 255.255.255.0 > # adb kill-server > # ADBHOST=192.168.0.202 adb devices > > If you have installed Qi loader, find on which eth device the > FreeRunner is located (for me, it is eth2). > > # ifconfig -a > > Then, issue the following (if you have Qi, and whether you found your > eth for FreeRunner. For me it is eth2): > > # ifconfig eth2 192.168.0.200 netmask 255.255.255.0 > # adb kill-server > # ADBHOST=192.168.0.202 adb devices I tried this, but no results: r...@gnubox:~# ifconfig eth2 192.168.0.200 netmask 255.255.255.0 r...@gnubox:~# adb kill-server r...@gnubox:~# ADBHOST=192.168.0.202 adb devices * daemon not running. starting it now * * daemon started successfully * List of devices attached r...@gnubox:~# ADBHOST=192.168.0.202 adb shell error: device not found regards, ~vimal signature.asc Description: This is a digitally signed message part ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: cannot connect to freerunner android
On Wed, Sep 16, 2009 at 11:17 AM, Vimal Joseph wrote: > On Tue, 2009-09-15 at 13:49 -0400, François-Léonard Gilbert wrote: > > Android has no SSH server. It is possible that you could access your > > phone using adb, wich is part of the Android dev kit. Since it does > > not work well in OS X I couldn't try it, so YMMV. > > Thanks, i tried adb, but i cannot even ping to 192.168.0.202 (which is > suppose to be the phone IP). The Debian detects the phone and load the > usb eth module properly and showed the device eth1. > > Thanks and regards, > > ~vimal > Have you done this - 3 adb connects to Android but you need to set up Android on FreeRunner first, otherwise you may skip this step. This will not work on other distributions. Make sure your FreeRunner was booted while being plugged in to a USB port. If you have flashed a *Uboot*, run the following commands in Terminal: # ifconfig usb0 192.168.0.200 netmask 255.255.255.0 # adb kill-server # ADBHOST=192.168.0.202 adb devices If you have installed Qi loader, find on which eth device the FreeRunner is located (for me, it is eth2). # ifconfig -a Then, issue the following (if you have *Qi*, and whether you found your eth for FreeRunner. For me it is eth2): # ifconfig eth2 192.168.0.200 netmask 255.255.255.0 # adb kill-server # ADBHOST=192.168.0.202 adb devices Note the part about booting with USB plugged in. Last time i tried beta 7 adb worked fine. Rakshat > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: cannot connect to freerunner android
On Tue, 2009-09-15 at 13:49 -0400, François-Léonard Gilbert wrote: > Android has no SSH server. It is possible that you could access your > phone using adb, wich is part of the Android dev kit. Since it does > not work well in OS X I couldn't try it, so YMMV. Thanks, i tried adb, but i cannot even ping to 192.168.0.202 (which is suppose to be the phone IP). The Debian detects the phone and load the usb eth module properly and showed the device eth1. Thanks and regards, ~vimal signature.asc Description: This is a digitally signed message part ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: cannot connect to freerunner android
Android has no SSH server. It is possible that you could access your phone using adb, wich is part of the Android dev kit. Since it does not work well in OS X I couldn't try it, so YMMV. On Tue, Sep 15, 2009 at 12:31 PM, Vimal Joseph wrote: > Hi, > > I installed the beta 7 of koolu android. When connecting to the usb, it > shows as eth1. I set the IP of eth1 as 192.168.0.200 but i cant connect > to 192.168.0.202 as mentioned > http://wiki.openmoko.org/wiki/Android_on_Freerunner > > Is there anything to do on the phone settings? I'm using debian lenny > and neo freerunner. > > thanks and regards, > > ~vimal > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
cannot connect to freerunner android
Hi, I installed the beta 7 of koolu android. When connecting to the usb, it shows as eth1. I set the IP of eth1 as 192.168.0.200 but i cant connect to 192.168.0.202 as mentioned http://wiki.openmoko.org/wiki/Android_on_Freerunner Is there anything to do on the phone settings? I'm using debian lenny and neo freerunner. thanks and regards, ~vimal signature.asc Description: This is a digitally signed message part ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
On Wed, 22 Jul 2009, aw...@sayne.org wrote: > This was my process: http://www.koolu.org/releases/beta7/android-freerunner-koolu1.0-beta-7.tar.gz BUT this is the old android. Either I am a bit dense, or it is very hard to find out from koolu's website, but the latest version is: http://www.koolu.org/releases/cupcake-1.5-alpha1/android-freerunner-koolu1.5-alpha-1.tar.gz in which case > ./adb install AndroidScriptingEnvironment-0.9-alpha.apk does install! -- Ant ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
On ons, 2009-07-22 at 02:47 +0100, Al Johnson wrote: > On Tuesday 21 July 2009, Jette Derriche wrote: > > On tir, 2009-07-21 at 18:55 +0100, Al Johnson wrote: > > > On Tuesday 21 July 2009, Jette Derriche wrote: > > > > On tir, 2009-07-21 at 12:39 -0400, François-Léonard Gilbert wrote: > > > > > If your SIM card does not require PIN entry, Android shoud work; > > > > > that's the only problem I had with the Koolu beta7 distro... so I > > > > > had to go for something else. > > > > > > > > Oh...There must be a way to remove the pin. > > > > > > If you're using something FSO-based see: > > > http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesm > > >artphone.GSM.SIM.html;hb=HEAD#SetAuthCodeRequired > > > > > > I think this is available through the settings gui in recent SHR. > > > > Is QT Extended FSO based?... I am currently running version 4.4.2 > > No, it isn't. It should have an option in its settings to turn off SIM > authentication, but I couldn't tell you exactly where. Yes, Qt Extended has an option to turn off SIM lock... My everyday phone (P900) also has this option. But I was wondering if this feature actually removes the PIN, or just remembers it. So I disabled the SIM lock from my P900 and then moved the SIM card to my FR. The FR did not ask for a PIN, so I guess this means it has been removed. /Jette ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
On Tuesday 21 July 2009, Jette Derriche wrote: > On tir, 2009-07-21 at 18:55 +0100, Al Johnson wrote: > > On Tuesday 21 July 2009, Jette Derriche wrote: > > > On tir, 2009-07-21 at 12:39 -0400, François-Léonard Gilbert wrote: > > > > If your SIM card does not require PIN entry, Android shoud work; > > > > that's the only problem I had with the Koolu beta7 distro... so I > > > > had to go for something else. > > > > > > Oh...There must be a way to remove the pin. > > > > If you're using something FSO-based see: > > http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesm > >artphone.GSM.SIM.html;hb=HEAD#SetAuthCodeRequired > > > > I think this is available through the settings gui in recent SHR. > > Is QT Extended FSO based?... I am currently running version 4.4.2 No, it isn't. It should have an option in its settings to turn off SIM authentication, but I couldn't tell you exactly where. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
On ons, 2009-07-22 at 09:00 +1200, aw...@sayne.org wrote: > On Wed, 22 Jul 2009, Jette Derriche wrote: > > I dusted off my FR today, since I have decided to give Android a try. > > Which is best, Koolus or Michael Thrimarchis' files? > > I tried koolu (android 1.5) and it (mostly) seems to work! > > > The current documentation is about a 1GB sd card, using 768MB for the > > first partition. Does this mean that using Android is a no-go for me? If > > that is not the case, what size can you recommend for my partitions? > > The image is small, so I put it on a 64M card and booted with that. It > appears > to work fine except for wifi with WPA. I am still investigating. > Thanks :-) Are you using Qi or uboot? I was planning on sticking with uboot since the wiki tells me that Qi can give problems.. On the other hand, the uboot modification for kernels > 2MB seems tricky, and the Qi way seems much simpler. Can you recommend Qi? /Jette ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
On Wed, 22 Jul 2009, Jette Derriche wrote: > I dusted off my FR today, since I have decided to give Android a try. > Which is best, Koolus or Michael Thrimarchis' files? I tried koolu (android 1.5) and it (mostly) seems to work! > The current documentation is about a 1GB sd card, using 768MB for the > first partition. Does this mean that using Android is a no-go for me? If > that is not the case, what size can you recommend for my partitions? The image is small, so I put it on a 64M card and booted with that. It appears to work fine except for wifi with WPA. I am still investigating. -- Ant ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
On tir, 2009-07-21 at 16:29 -0400, François-Léonard Gilbert wrote: > I think Qt Extended is working, and I know for sure that Qtmoko (a > fork of QtE) does SIM PIN authentication well. > > As for being based on FSO, I don't know. What do you mean by "Qt Extended is working"? Do you mean that the suggested command for removing the pin will work? I currently have Qt Extended installed, but I want to try Android... Removing the pin is necessary for that... And to get back to my original question: Is my Micro SD (512mb) big enough to install Android? /Jette > > Francois > > On Tue, Jul 21, 2009 at 2:30 PM, Jette Derriche > wrote: > On tir, 2009-07-21 at 18:55 +0100, Al Johnson wrote: > > On Tuesday 21 July 2009, Jette Derriche wrote: > > > > > > > Oh...There must be a way to remove the pin. > > > > If you're using something FSO-based see: > > > > http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.SIM.html;hb=HEAD#SetAuthCodeRequired > > > > I think this is available through the settings gui in recent > SHR. > > > Is QT Extended FSO based?... I am currently running version > 4.4.2 > > /Jette > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
I think Qt Extended is working, and I know for sure that Qtmoko (a fork of QtE) does SIM PIN authentication well. As for being based on FSO, I don't know. Francois On Tue, Jul 21, 2009 at 2:30 PM, Jette Derriche wrote: > On tir, 2009-07-21 at 18:55 +0100, Al Johnson wrote: > > On Tuesday 21 July 2009, Jette Derriche wrote: > > > > > > > Oh...There must be a way to remove the pin. > > > > If you're using something FSO-based see: > > > http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.SIM.html;hb=HEAD#SetAuthCodeRequired > > > > I think this is available through the settings gui in recent SHR. > > Is QT Extended FSO based?... I am currently running version 4.4.2 > > /Jette > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
On tir, 2009-07-21 at 18:55 +0100, Al Johnson wrote: > On Tuesday 21 July 2009, Jette Derriche wrote: > > On tir, 2009-07-21 at 12:39 -0400, François-Léonard Gilbert wrote: > > > If your SIM card does not require PIN entry, Android shoud work; > > > that's the only problem I had with the Koolu beta7 distro... so I > > > had to go for something else. > > > > Oh...There must be a way to remove the pin. > > If you're using something FSO-based see: > http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.SIM.html;hb=HEAD#SetAuthCodeRequired > > I think this is available through the settings gui in recent SHR. Is QT Extended FSO based?... I am currently running version 4.4.2 /Jette ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
On Tuesday 21 July 2009, Jette Derriche wrote: > On tir, 2009-07-21 at 12:39 -0400, François-Léonard Gilbert wrote: > > If your SIM card does not require PIN entry, Android shoud work; > > that's the only problem I had with the Koolu beta7 distro... so I > > had to go for something else. > > Oh...There must be a way to remove the pin. If you're using something FSO-based see: http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.SIM.html;hb=HEAD#SetAuthCodeRequired I think this is available through the settings gui in recent SHR. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
On tir, 2009-07-21 at 12:39 -0400, François-Léonard Gilbert wrote: > If your SIM card does not require PIN entry, Android shoud work; > that's the only problem I had with the Koolu beta7 distro... so I > had to go for something else. Oh...There must be a way to remove the pin. Do you know Androids minimum requirement for SD card size. /Jette > > Francois > > On Tue, Jul 21, 2009 at 11:42 AM, Jette Derriche > wrote: > I dusted off my FR today, since I have decided to give Android > a try. > Which is best, Koolus or Michael Thrimarchis' files? > > My Micro SD card currently looks like this: > > > Disk /dev/mmcblk0: 507 MB, 507379712 bytes > 16 heads, 63 sectors/track, 983 cylinders > Units = cylinders of 1008 * 512 = 516096 bytes > Disk identifier: 0x > >Device Boot Start End Blocks Id > System > /dev/mmcblk0p1 1 983 495313+ 6 > FAT16 > > > The current documentation is about a 1GB sd card, using 768MB > for the > first partition. Does this mean that using Android is a no-go > for me? If > that is not the case, what size can you recommend for my > partitions? > > /Jette > > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Partitioning SD card for Android
If your SIM card does not require PIN entry, Android shoud work; that's the only problem I had with the Koolu beta7 distro... so I had to go for something else. Francois On Tue, Jul 21, 2009 at 11:42 AM, Jette Derriche wrote: > I dusted off my FR today, since I have decided to give Android a try. > Which is best, Koolus or Michael Thrimarchis' files? > > My Micro SD card currently looks like this: > > > Disk /dev/mmcblk0: 507 MB, 507379712 bytes > 16 heads, 63 sectors/track, 983 cylinders > Units = cylinders of 1008 * 512 = 516096 bytes > Disk identifier: 0x > >Device Boot Start End Blocks Id System > /dev/mmcblk0p1 1 983 495313+ 6 FAT16 > > > The current documentation is about a 1GB sd card, using 768MB for the > first partition. Does this mean that using Android is a no-go for me? If > that is not the case, what size can you recommend for my partitions? > > /Jette > > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Partitioning SD card for Android
I dusted off my FR today, since I have decided to give Android a try. Which is best, Koolus or Michael Thrimarchis' files? My Micro SD card currently looks like this: Disk /dev/mmcblk0: 507 MB, 507379712 bytes 16 heads, 63 sectors/track, 983 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/mmcblk0p1 1 983 495313+ 6 FAT16 The current documentation is about a 1GB sd card, using 768MB for the first partition. Does this mean that using Android is a no-go for me? If that is not the case, what size can you recommend for my partitions? /Jette ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [android] strong echo with buzz-fixed A6
Thomas Otterbein wrote (ao): > I installed Koolu's Android Betra 7 on my recently buzz-fixed Freerunner A6. > It > has the well known echo problem now. On the lists and forums I could find > only > solutions (dbus commands) for other distros. However I hope similar settings > may help on Android too, just that I have no idea on how to apply them. :-) > > Can anyone possibly drop me a hint? Can you try lowering the mic gain to see if that helps? With kind regards, Sander -- Humilis IT Services and Solutions http://www.humilis.net ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [android] strong echo with buzz-fixed A6
Thomas Otterbein schrieb: > Hi, > > I installed Koolu's Android Betra 7 on my recently buzz-fixed Freerunner A6. > It > has the well known echo problem now. On the lists and forums I could find > only > solutions (dbus commands) for other distros. However I hope similar settings > may help on Android too, just that I have no idea on how to apply them. :-) > > > maybe: alsactl -f /usr/share/openmoko/scenarios/gsmhandset.state restore does the job. take the gsmhandset.state from shr.jffs2 (mount -oloop jffs2 /mnt) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[android] strong echo with buzz-fixed A6
Hi, I installed Koolu's Android Betra 7 on my recently buzz-fixed Freerunner A6. It has the well known echo problem now. On the lists and forums I could find only solutions (dbus commands) for other distros. However I hope similar settings may help on Android too, just that I have no idea on how to apply them. :-) Can anyone possibly drop me a hint? Thanks in advance thomas ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [Android] SD-card not mounted
Joachim Ott a écrit : > 2009/6/14 Linus Gasser : >> Dear all, >> >> I'm trying out the Android Koolu beta 7 version from >> >> http://freerunner.android.koolu.com/release-files >> >> Unfortunatly it always tells me "SD card not mounted". So I tried the >> following command, as noted on some wikis and mailing-lists: >> >> setprop EXTERNAL_STORAGE_STATE mounted >> >> but it doesn't help at all. Neither with the original 512MB SD-card from >> Openmoko, neither with a SanDisk 8GB card... >> >> any other ideas of what I could try? > > Have you partitioned the SD card as Android wants it? That is, a FAT > and then an ext2 partition. I thought that beta7 does this automatically. According to the link above, it is enough to have one FAT-partition on the SD-card. Or do I still have to do the partitionning? Funny thing is that with the console on Android, I can see the /sdcard partition with files in it. So I think it is OK. Linus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [Android] SD-card not mounted
2009/6/14 Linus Gasser : > Dear all, > > I'm trying out the Android Koolu beta 7 version from > > http://freerunner.android.koolu.com/release-files > > Unfortunatly it always tells me "SD card not mounted". So I tried the > following command, as noted on some wikis and mailing-lists: > > setprop EXTERNAL_STORAGE_STATE mounted > > but it doesn't help at all. Neither with the original 512MB SD-card from > Openmoko, neither with a SanDisk 8GB card... > > any other ideas of what I could try? Have you partitioned the SD card as Android wants it? That is, a FAT and then an ext2 partition. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[Android] SD-card not mounted
Dear all, I'm trying out the Android Koolu beta 7 version from http://freerunner.android.koolu.com/release-files Unfortunatly it always tells me "SD card not mounted". So I tried the following command, as noted on some wikis and mailing-lists: setprop EXTERNAL_STORAGE_STATE mounted but it doesn't help at all. Neither with the original 512MB SD-card from Openmoko, neither with a SanDisk 8GB card... any other ideas of what I could try? Linus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Android Software Development - Failure -12
Hello I write HelloWorld in Android-Java. In SDK it working fine. But when try to install it on my OpenMoko it did not work: $ ./adb install ~/workspace/p/HW/bin/HW.apk 115 KB/s (8870 bytes in 0.074s) pkg: /data/local/tmp/HW.apk Failure [-12] I was trying in v1.1 and v1.5. Can somebody help me? THX Walery ;o) -- Follow me: http://twitter.com/walery ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android not finishing boot
Joachim Ott wrote: > Press and hold the AUX button, then press and hold the power button. > After 2 or 3 seconds the NOR boot menu should appear. Thanks! It was the sequence that mattered. Regards -Lars ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android not finishing boot
2009/6/5 Lars Nooden : > I've just tried putting Qi and androidfs-koolu-beta3.jffs2 onto my > Freerunner. > http://freerunner.android.koolu.com/release-files > > Qi seemed to work fine with Om2009 testing. > > However, Android only partially boots and I'm unable to get the boot > menu again to load a different image. Holding down the AUX button while > starting and holding the power button no longer does the trick. How do > I get the boot menu again? Press and hold the AUX button, then press and hold the power button. After 2 or 3 seconds the NOR boot menu should appear. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Android not finishing boot
I've just tried putting Qi and androidfs-koolu-beta3.jffs2 onto my Freerunner. http://freerunner.android.koolu.com/release-files Qi seemed to work fine with Om2009 testing. However, Android only partially boots and I'm unable to get the boot menu again to load a different image. Holding down the AUX button while starting and holding the power button no longer does the trick. How do I get the boot menu again? -Lars Here is what shows on the screen when booting stops: Freeing init memory: 132K Warning: unable to open an initial console A N D R O I D [21474550.150] modem wakeup interupt init: Unable to open persistent property directory /data/propery errno:2 init: cannot find '/system/bin/playmp3', disabling 'bootsound' init: cannot find '/system/bin/flash_image', disabling 'flash_recovery' warning: `rild' uses 32-bit capabilities (legacy support in use) The unit will respond to pressing the power button with messages like this: pcf50633 0-0073: ONKEY is held pcf50633 0-0073: ONKEY is held for 1 secs etc. so holding it down does not poweroff the unit. Popping the battery does, but when booting, the unit vibrates very briefly then the AUX button blinks red once. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Recommend Openmoko Android course. Europe
Has anyone been on either the BigNerdanch Android course or the RootDSP.eu embedded course? Can they recommend either? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android-Image for Neo 1973 (GTA01Bv4)
Hi Paul! Thanks, but this is all about the Neo Freerunner (GTA02), not about the Neo 1973 (GTA01). At least as far as I can tell. Regards, Torsten Paul schrieb: > Here are some links > > http://wiki.openmoko.org/wiki/Android > > Beta 3 release > http://freerunner.android.koolu.com/release-files > > On Thu, Feb 19, 2009 at 5:29 AM, Torsten Schlabach wrote: > >> Hi all! >> >> I was glad to read this: >> >> http://benno.id.au/blog/2008/11/02/android-on-neo1973 >> >> But I wonder if there would be a downloadable image anywhere? >> >> Regards, >> Torsten >> >> ___ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> > > > > > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android-Image for Neo 1973 (GTA01Bv4)
Here are some links http://wiki.openmoko.org/wiki/Android Beta 3 release http://freerunner.android.koolu.com/release-files On Thu, Feb 19, 2009 at 5:29 AM, Torsten Schlabach wrote: > Hi all! > > I was glad to read this: > > http://benno.id.au/blog/2008/11/02/android-on-neo1973 > > But I wonder if there would be a downloadable image anywhere? > > Regards, > Torsten > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Android-Image for Neo 1973 (GTA01Bv4)
Hi all! I was glad to read this: http://benno.id.au/blog/2008/11/02/android-on-neo1973 But I wonder if there would be a downloadable image anywhere? Regards, Torsten ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qi not working? or is it android?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Yes, I suspect that the first message ("dbugfs dir creation failed") is
| coming from the android kernel and that the power_supply message was
| appearing before qi -- I think I'm just now noticing it because of the
fact
| that I don't see the rest of the scrolling boot . . .
|
| But I'll confirm that I flashed the right qi. Is it a good idea to
just keep
| that as the bootloader?
Yeah, Qi is doing fine loading and booting Linux as it should, there's
nothing to blame it for here.
If you see the backlight come up you're out of Qi and the kernel is
running, unless the issue involves kernel commandline it's most likely a
rootfs or kernel related issue then. Some rootfs cannot cope with
mounting the thing ro which is Qi policy, maybe that's the problem.
I don't think you have the wrong Qi either, I guess it would not start
at all.
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkmN5OQACgkQOjLpvpq7dMpIXwCfeHx3sPRF8Bz9KReMYX3zB2J3
5OcAnjQ73Ae7YE6DDFqkcJgWddqPb4yH
=LA9n
-END PGP SIGNATURE-
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: qi not working? or is it android?
Yes, I suspect that the first message ("dbugfs dir creation failed") is
coming from the android kernel and that the power_supply message was
appearing before qi -- I think I'm just now noticing it because of the fact
that I don't see the rest of the scrolling boot . . .
But I'll confirm that I flashed the right qi. Is it a good idea to just keep
that as the bootloader?
Many thanks,
Sean
Andy Green wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Somebody in the thread at some point said:
> | Hi, all:
> |
> | Just flashed qi (GTA02), and I get the flash, the vibration, and then
> this
> | message:
> |
> | s3c2410_udc: debugfs dir creation failed -19
> | power_supply bat: driver failed to report `status' properly
> |
> | trying to boot android (the second message doesn't seem to stop
> booting the
> | OM, but the first message does)
> |
> | Any idea what's up? Any way to get rid of qi, which gave me the same
> message
> | about the power_supply before booting qtopia . . .
>
> You're mistaken, Qi does not issue these messages but the kernel.
>
> Neither of them represent anything fatal so the problem is somewhere
> completely different.
>
> - -Andy
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkmNrZgACgkQOjLpvpq7dMriYACeJCnS1aR9FmjmApxhLGbrPDbJ
> j1kAnRNvFm6kxMvVRGcjdT+O2f3U48tT
> =+cog
> -END PGP SIGNATURE-
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>
>
--
View this message in context:
http://n2.nabble.com/qi-not-working--or-is-it-android--tp2289288p2289585.html
Sent from the Openmoko Support mailing list archive at Nabble.com.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: qi not working? or is it android?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi, all: | | Just flashed qi (GTA02), and I get the flash, the vibration, and then this | message: | | s3c2410_udc: debugfs dir creation failed -19 | power_supply bat: driver failed to report `status' properly | | trying to boot android (the second message doesn't seem to stop booting the | OM, but the first message does) | | Any idea what's up? Any way to get rid of qi, which gave me the same message | about the power_supply before booting qtopia . . . You're mistaken, Qi does not issue these messages but the kernel. Neither of them represent anything fatal so the problem is somewhere completely different. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmNrZgACgkQOjLpvpq7dMriYACeJCnS1aR9FmjmApxhLGbrPDbJ j1kAnRNvFm6kxMvVRGcjdT+O2f3U48tT =+cog -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qi not working? or is it android?
On Sat, Feb 7, 2009 at 4:33 PM, encinalense wrote: > > Hi, all: > > Just flashed qi (GTA02), and I get the flash, the vibration, and then this > message: > > s3c2410_udc: debugfs dir creation failed -19 > power_supply bat: driver failed to report `status' properly Probably you've flashed the wrong Qi: s3c2410 series is for GTA01, for GTA02 you need s3c2442. Check this out: http://people.openmoko.org/andy/ -- Regards, Alex ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
qi not working? or is it android?
Hi, all: Just flashed qi (GTA02), and I get the flash, the vibration, and then this message: s3c2410_udc: debugfs dir creation failed -19 power_supply bat: driver failed to report `status' properly trying to boot android (the second message doesn't seem to stop booting the OM, but the first message does) Any idea what's up? Any way to get rid of qi, which gave me the same message about the power_supply before booting qtopia . . . Thanks, Sean -- View this message in context: http://n2.nabble.com/qi-not-working--or-is-it-android--tp2289288p2289288.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
On Tue, Dec 23, 2008 at 5:44 AM, xiangfu wrote: > i have format the SD card in two partition VFAT(200M) EXT3(200M) > with Andy's Kernel and Sean's Image: > it's just stop at : > -------- >ANDROID [... ...] init: Unable to open persistent property directory > /data/property errno:2 > [... ...] init: cannot find '/system/bin/playmp3', disabling 'bootsound' > - You may want to try again with the Koolu beta image and kernel. See this announcement: http://forum.koolu.org/viewtopic.php?f=10&t=34&sid=4db9bea769ada58363c03235d8454313 Jim ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
Hi on my FreeRunner
Jim Ancona wrote:
> On Sat, Dec 20, 2008 at 3:35 PM, Andy Green wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Somebody in the thread at some point said:
>> | I also tried installing Qi last night, for qi the red aux light blinks
>> once,
>> | and I get a black screen on the phone but the back light is on.
>> |
>> | with u-boot i just get the same black screen.
>> | This phone worked with the very first port of android but none of the
>> | updates.
>>
>> You're booted into the kernel fine, since with Qi nothing brings up
>> backlight until then.
>>
>> In Sean McNeil's kernel configs he has turned off the framebuffer
>> console completely because it caused flickering apparently.
>>
>> So I guess you're all set but something is blowing chunks once Android
>> starts. Maybe try a different kernel image like the ones in
>> http://people.openmoko.org/andy that does have a framebuffer console.
>>
>
> Depending on how far you're getting, you may also be able to see something
> logged using adb (http://people.openmoko.org/sean_mcneil/adb)
>
i have format the SD card in two partition VFAT(200M) EXT3(200M)
with Andy's Kernel and Sean's Image:
it's just stop at :
ANDROID [... ...] init: Unable to open persistent property directory
/data/property errno:2
[... ...] init: cannot find '/system/bin/playmp3', disabling 'bootsound'
-
> Try
>
> ADBHOST=192.168.0.202 {path-to}/adb logcat
and adb get nothing ,
>
> Jim
>
>
>
>
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
You don't. You use all the tools under Linux. I'm using the Ubuntu distro, some are using the Fedora distro. abatrour wrote: > How do I use ADB under vista? > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
How do I use ADB under vista? -- View this message in context: http://n2.nabble.com/Phone-wont-boot-Android-tp1681265p1684705.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
On Sat, Dec 20, 2008 at 3:35 PM, Andy Green wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Somebody in the thread at some point said:
> | I also tried installing Qi last night, for qi the red aux light blinks
> once,
> | and I get a black screen on the phone but the back light is on.
> |
> | with u-boot i just get the same black screen.
> | This phone worked with the very first port of android but none of the
> | updates.
>
> You're booted into the kernel fine, since with Qi nothing brings up
> backlight until then.
>
> In Sean McNeil's kernel configs he has turned off the framebuffer
> console completely because it caused flickering apparently.
>
> So I guess you're all set but something is blowing chunks once Android
> starts. Maybe try a different kernel image like the ones in
> http://people.openmoko.org/andy that does have a framebuffer console.
>
Depending on how far you're getting, you may also be able to see something
logged using adb (http://people.openmoko.org/sean_mcneil/adb)
Try
ADBHOST=192.168.0.202 {path-to}/adb logcat
Jim
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I also tried installing Qi last night, for qi the red aux light blinks once, | and I get a black screen on the phone but the back light is on. | | with u-boot i just get the same black screen. | This phone worked with the very first port of android but none of the | updates. You're booted into the kernel fine, since with Qi nothing brings up backlight until then. In Sean McNeil's kernel configs he has turned off the framebuffer console completely because it caused flickering apparently. So I guess you're all set but something is blowing chunks once Android starts. Maybe try a different kernel image like the ones in http://people.openmoko.org/andy that does have a framebuffer console. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklNVwEACgkQOjLpvpq7dMq2BACffhqT72EZ2lMyPwEMBgfG1CA5 SL0AnjYtz3AFkBsFCO4I2N1jn3W8vSlq =nZHg -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
2008/12/20 abatrour > > I also tried installing Qi last night, for qi the red aux light blinks > once, > and I get a black screen on the phone but the back light is on. > > with u-boot i just get the same black screen. > This phone worked with the very first port of android but none of the > updates. Can you boot into NAND boot menu and select "Boot" from there? It should give you some information before it tries to start the kernel. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
I also tried installing Qi last night, for qi the red aux light blinks once, and I get a black screen on the phone but the back light is on. with u-boot i just get the same black screen. This phone worked with the very first port of android but none of the updates. -- View this message in context: http://n2.nabble.com/Phone-wont-boot-Android-tp1681265p1682432.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
On Saturday 20 December 2008 17:14:50 abatrour wrote: > Hey everyone. I'm having trouble booting Android. I flashed with the latest > rootfs and uimage as well as the the u-boot from yesterday. > I have a 2gb memory card formatted 1gb fat16 and 1gb ext3. Did you change the uboot settings to accept kernels bigger than 2 MB ? Marek ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Phone wont boot Android
2008/12/20 abatrour > > Hey everyone. I'm having trouble booting Android. I flashed with the latest > rootfs and uimage as well as the the u-boot from yesterday. > I have a 2gb memory card formatted 1gb fat16 and 1gb ext3. > > I cant figure out what I did wrong How far do you get? Is there anything on the screen when you boot? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Phone wont boot Android
Hey everyone. I'm having trouble booting Android. I flashed with the latest rootfs and uimage as well as the the u-boot from yesterday. I have a 2gb memory card formatted 1gb fat16 and 1gb ext3. I cant figure out what I did wrong -- View this message in context: http://n2.nabble.com/Phone-wont-boot-Android-tp1681265p1681265.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO & Android (was: Sad Story)
Please don't mix teams, distributions, and efforts. FSO is an initiative building a dbus-based framework for mobile devices, 100% funded by Openmoko. The FSO team evolved out of Openmoko's Framework Team. FSO provides a dbus API and a reference implementation that is supposed to run on as many devices as we can manage -- including the GTA's, but also a lot of non-Openmoko devices. Openmoko 2008.x is a distribution, which does not include the new framework, since Qtopia is the framework used there. Openmoko 2009.x will be a distribution including the FSO framework. A personal remark: With all these semiopen initiatives going live, I see Openmoko being more and more important for free software, not less. At the end of the day, OM is still only free open mobile communications platform(*) out there -- and I don't see that changing soon. Cheers, -- :M: (*) A platform is a combination of hardware and software, not just one of them. What use is a software that I can not put on my closed device? Likewise what use is hardware that I can't update with my own software. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO & Android (was: Sad Story)
Wolfgang, Thank you for your reply. I now understand the situation better. My previous impression was that FSO and OM had a significantly different code base and not terribly compatible with each other. In any case, I am still hopeful for OM. The usability team, I felt, was exactly what OM needed to bring the phone closer to being a phone. But alas and alack. -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
FSO & Android (was: Sad Story)
Paul, > create a working phone. Passing the buck to FSO is passing the torch > to someone else. This is what OM has done. We are funding FSO. This is called teamwork :-) FSO concentrates on the framework, and standardizing interfaces for mobile phones. FSO = freesmartphone.org Openmoko concentrates engineering on the lower level (kernel & drivers), as well as on the top-most level (UI design). All of this is made possible by our community buying our phones and helping with development everywhere. > I'm sure the majority of hardware owners are awaiting Google Android. The cool thing about Free Software is it's configurability and modularity. Try to build a product with half of Android. Won't work. Half of Debian, let alone any image generated with OpenEmbedded? No problem. Best Regards, Wolfgang On Dec 16, 2008, at 3:47 AM, Paul wrote: > Seeing the responses to criticism, it is clear why OpenMoko is where > it is today. If a significant portion of the community is frustrated > at the status of this project, the best course of action is to address > the concerns of the community. Does telling people to buy an iphone > accomplish anything but lower your social standing on this list? > > The main reason of why Open Source works is because people are able to > criticize. When the criticisms are taken into account, real progress > can be had. > > We as a community were warned of the alpha status of the phone. What > we expected was that the community and company would work hand in hand > to create a viable phone solution. Yet, it is clear that the resolve > of the Company is waning and the rest of the community is left holding > the bag. Now we have people blaming us because we are holding the > bag. > > Just because a project is Open Source, doesn't guarantee its success. > We have a lot of people working hard to resolve issues, yet we haven't > achieved our goal. We need to refocus our goals and objectives to > create a working phone. Passing the buck to FSO is passing the torch > to someone else. This is what OM has done. > > I'm sure the majority of hardware owners are awaiting Google Android. > -- > Paul > Email - pault...@gmail.com > > There were moments when he looked on evil simply as a mode through > which he could realize his conception of the beautiful. > Oscar Wilde - The Picture of Dorian Gray > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android first try - kurz und schmerzlos
Joachim Ott-2 wrote: > > 2008/11/7 Roman Pszonczenko <[EMAIL PROTECTED]> > > On 2nd try, I still couldn't get much farther. What key or button is > supposed to be the Menu key mentioned on the desktop? I tried to unlock > the > sim, it told me twice "invalid PIN" (or such). Before making up my mind to > give it a 3rd try or to cancel it, the screen went black again. > > Take a look in the other android threads and the getting started guides. SIM unlock is not working, to try android you must disable the SIM security. -- View this message in context: http://n2.nabble.com/Android-first-try---kurz-und-schmerzlos-tp1470265p1477564.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android first try - kurz und schmerzlos
2008/11/7 Roman Pszonczenko <[EMAIL PROTECTED]> > Well, it went black because it went to sleep. It is said that kernel > 2.6.26 wil not resume properly, so you have to go to the Settings menu > and disable energy saving. I had the same situation but I just > rebooted... > > Another issue is triangular screen blinking when the background is > shadowed, for example when popup windows appear. But overall > impression is good - works faster then other distros on neo. Of course > it is only a proof of concept at the moment - ex. you cannot enter any > text right now. But it really nice to see it working. On 2nd try, I still couldn't get much farther. What key or button is supposed to be the Menu key mentioned on the desktop? I tried to unlock the sim, it told me twice "invalid PIN" (or such). Before making up my mind to give it a 3rd try or to cancel it, the screen went black again. Much later, when I checked the SD card, I saw the the FAT16 partition had vanished. I couldn't mount it anymore. On the ext3-partition 23 MB are used, the directories created are "anr app app-private dalvik-cache data local misc property system". I wonder why this data must be put onto the SD-card instead of the NAND. Before wasting anymore time, I put FSO into the NAND. It was not much success either. After entering the PIN, enlightenment crashed. This time I could login via usb, but I was not able to restart X. Could it be that yesterday was Friday 13? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android first try - kurz und schmerzlos
On Fri, Nov 7, 2008 at 4:37 PM, Joachim Ott <[EMAIL PROTECTED]> wrote: > Following the instructions on http://wiki.openmoko.org/wiki/User:Seanmcneil3 > I flashed the kernel and rootfs and prepared a SD-card. After booting, it > took like 20 seconds before something appeared on the screen (see > http://img220.imageshack.us/my.php?image=androidtestiy0.png). Later the > desktop screen came up. After I made the picture, the screen went black and > remained black, no matter what I tried (tapping, clicking on buttons). USB > didn't react either. Finally I took out the battery. Anything else I should > try before I overwrite the NAND with something else? > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > Well, it went black because it went to sleep. It is said that kernel 2.6.26 wil not resume properly, so you have to go to the Settings menu and disable energy saving. I had the same situation but I just rebooted... Another issue is triangular screen blinking when the background is shadowed, for example when popup windows appear. But overall impression is good - works faster then other distros on neo. Of course it is only a proof of concept at the moment - ex. you cannot enter any text right now. But it really nice to see it working. Didn't managed to get USB working too... Roman ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android first try - kurz und schmerzlos
from the message displayed i'd infer that the device is sleeping -- and you'd need some hw button to wake it up. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Android first try - kurz und schmerzlos
Following the instructions on http://wiki.openmoko.org/wiki/User:Seanmcneil3I flashed the kernel and rootfs and prepared a SD-card. After booting, it took like 20 seconds before something appeared on the screen (see http://img220.imageshack.us/my.php?image=androidtestiy0.png). Later the desktop screen came up. After I made the picture, the screen went black and remained black, no matter what I tried (tapping, clicking on buttons). USB didn't react either. Finally I took out the battery. Anything else I should try before I overwrite the NAND with something else? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
android
ssh?? Bye Luca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android?
Am Freitag 29 August 2008 21:51:37 schrieb e hanks: > Has anyone successfully installed Android? I wonder how usable it is. >From the imaginary FAQ: At this point of time, Android is not open source. Without interesting low-level hacking (armv5 vs. armv4), there's no way to use it on an Openmoko device. -- :M: ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Android?
Has anyone successfully installed Android? I wonder how usable it is. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Android
please search the community mailing list before posting. http://lists.openmoko.org/pipermail/community/2008-May/018199.html On Wed, Aug 13, 2008 at 8:20 PM, Joseph Curtin <[EMAIL PROTECTED]>wrote: > Hey all, > > Has anyone experimented with Android and the Free Runner? > > -- > -Joe > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Android
Hey all, Has anyone experimented with Android and the Free Runner? -- -Joe ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
