Re: First impressions on new Android rootfs

Hi, I just received this message today. I didn't update the GSM firmware. I'm compiling the android root filesystem again from the updated koolu repository and I will compare the radio log with yours. Rui On Fri, Dec 5, 2008 at 3:10 AM, Sean McNeil wrote: > Rui, > > This looks really bazaar. Wh

Re: First impressions on new Android rootfs

Rui, This looks really bazaar. What version of hardware do you have? Have you updated the GSM firmware? The initial chat should look like: D/AT ( 2004): CHAT< AT-Command Interpreter ready D/AT ( 2004): CHAT> ATZ D/AT ( 2004): CHAT< ATZ D/AT ( 2004): CHAT< OK D/AT ( 200

Re: First impressions on new Android rootfs

Gothnet wrote: > > Please forgive me for replying to so many of my own emails... > ... that helps more than is annoing ;) Gothnet wrote: > > Apparently the answer is "setprop net.usb0.dns1 $IP_ADDRESS" > Try "setprop net.dns1 $IP_ADDRESS" (just without the network device) for me then dns

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

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 g

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

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=ne

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. >>

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. Excep

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 remembe

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,

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. ___ Op

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,

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 thin

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 th

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

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

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

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

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

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

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 ... ; sav

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, >> >>

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 commun

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

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 f

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 >

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

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. >

Re: First impressions on new Android rootfs

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 environmen

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 obvio

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

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 >>> >>>

Re: First impressions on new Android rootfs

There is a known issue with Wifi and the wpa_supplicant in Android. I'm trying to track down why it won't scan properly. wp wrote: > Hi > Thanks for providing an image. > Few words from me: > I'm able to make calls, but it's rather hard to hear other person in a > speaker (he does hear me very we

Re: First impressions on new Android rootfs

Can you send me the output of ADBHOST=neo ./adb logcat -b radio ? Riccardo Centra wrote: > Sean with the lastest image the gsm doesn't work :( > > 2008/12/3 Sean McNeil <[EMAIL PROTECTED] > > > Gothnet wrote: > > > > Warren Baird wrote: > > > >> I ag

Re: First impressions on new Android rootfs

Marco Trevisan (Treviño) wrote: Rui Castro wrote: The workaround to boot the uImage-tracking kernel from uBoot (setenv bootcmd setenv ... ; saveenv) works, but when I poweroff neo and try to boot again it doesn't work anymore; I have to do the hack again. Maybe I'm doing something stupid here

Re: First impressions on new Android rootfs

Franky Van Liedekerke wrote: > On Thu, 04 Dec 2008 01:12:59 +0700 > Sean McNeil <[EMAIL PROTECTED]> wrote: > > >> I'm uploading a new image right now that includes Ruis virtual >> keyboard. Please give it 30 minutes or so to complete the upload. >> >> Sean >> >> > > Sean, > > which uImage s

Re: First impressions on new Android rootfs

Rui Castro wrote: > The workaround to boot the uImage-tracking kernel from uBoot (setenv > bootcmd setenv ... ; saveenv) works, but when I poweroff neo and try > to boot again it doesn't work anymore; I have to do the hack again. > Maybe I'm doing something stupid here. It's the first time I mess w

Re: First impressions on new Android rootfs

Hi, My first impressions on this new image is that it isn't usable :) My keyboard has some obvious problems, the letter/number/symbols keys are too small and when dialog windows appear asking for text, like the bluetooth pairing code, the keyboard is bellow the dialog and cannot be clicked. I hav

Re: First impressions on new Android rootfs

Gothnet wrote: > But editing the bootcmd entry to read a larger kernel "nand read.e > 0x3200 kernel 0x30;" then flashing the kernel and rootfs image as > usual. Unfortunately the time I took to do this seems to have run down the > freerunner's battery, and now android boots and immdeiately

Re: First impressions on new Android rootfs

Franky Van Liedekerke wrote: > > which uImage should we take? uImage-android or uImage-tracking? > OK, for the hard of thinking (amongst whom I count myself) I got the tracking kernel booting by following the "what if I borked my bootloader" instructions from here - http://wiki.openmoko.org

Re: First impressions on new Android rootfs

Sean with the lastest image the gsm doesn't work :( 2008/12/3 Sean McNeil <[EMAIL PROTECTED]> > Gothnet wrote: > > > > Warren Baird wrote: > > > >> I agree Android looks like it has a lot of promise - but if you want a > >> functioning phone today - I'd suggest trying out QtExtended 4.4.2 - it >

Re: First impressions on new Android rootfs

Hi Thanks for providing an image. Few words from me: I'm able to make calls, but it's rather hard to hear other person in a speaker (he does hear me very well, no echo issue). After receiving a message (yep, it works) I lost contact with my gsm network, so I can't answer. Reboots did not work, i'm

Re: First impressions on new Android rootfs

Paul wrote: >>> which uImage should we take? uImage-android or uImage-tracking? >>> >>> > > Right.. I stuck the new jffs and uImage-android on the Freerunner. > > I can get to the system even though the SIM card is not recognised > (probably because the SIM's pin is still in place). Pr

Re: First impressions on new Android rootfs

On Thu, Dec 4, 2008 at 6:38 AM, Matthias Camenzind <[EMAIL PROTECTED]> wrote: > I tried this with 512MB SD (it works): > Device Boot Start End Blocks Id System > /dev/mmcblk0p1 17814 250040 6 FAT16 > /dev/mmcblk0p27815 15568

RE: First impressions on new Android rootfs

Sorry not f, use "t,2,6" From: [EMAIL PROTECTED] To: community@lists.openmoko.org Date: Wed, 3 Dec 2008 20:38:29 + Subject: RE: First impressions on new Android rootfs I tried this with 512MB SD (it works): Device Boot Start End Blocks Id S

RE: First impressions on new Android rootfs

PROTECTED] > To: community@lists.openmoko.org > Subject: Re: First impressions on new Android rootfs > > > The image doesn't work for me. > I'm using the daily u-boot build from yesterday, and the latest android > rootfs and kernel. > > I have tried it with 2 different sd

Re: First impressions on new Android rootfs

>> which uImage should we take? uImage-android or uImage-tracking? >> Right.. I stuck the new jffs and uImage-android on the Freerunner. I can get to the system even though the SIM card is not recognised (probably because the SIM's pin is still in place). Pressing menu (power button) take

Re: First impressions on new Android rootfs

The image doesn't work for me. I'm using the daily u-boot build from yesterday, and the latest android rootfs and kernel. I have tried it with 2 different sd cards, a 256, and a 2gb both formatted with a 50mb fat16 and the rest ext2. it just sits at a black screen, I've waited over 20 minutes to

Re: First impressions on new Android rootfs

Franky Van Liedekerke wrote: > > > Sean, > > which uImage should we take? uImage-android or uImage-tracking? > > Franky > > Take a look here - http://n2.nabble.com/andy-tracking-kernel--td1609293.html for details on the kernel difference. and what you'll need to do to u-boot to get the

Re: First impressions on new Android rootfs

On Thu, 04 Dec 2008 01:12:59 +0700 Sean McNeil <[EMAIL PROTECTED]> wrote: > I'm uploading a new image right now that includes Ruis virtual > keyboard. Please give it 30 minutes or so to complete the upload. > > Sean > Sean, which uImage should we take? uImage-android or uImage-tracking? Frank

Re: First impressions on new Android rootfs

> I'm uploading a new image right now that includes Ruis virtual keyboard. > Please give it 30 minutes or so to complete the upload. > Sounds fabulous, Sean. I wonder... will I be able to use the virtual keyboard to enter a PIN for the simcard? I can't remove that from the card (some provid

Re: First impressions on new Android rootfs

Gothnet wrote: > > Warren Baird wrote: > >> I agree Android looks like it has a lot of promise - but if you want a >> functioning phone today - I'd suggest trying out QtExtended 4.4.2 - it >> doesn't give you much more than basic phone functionality, but I've been >> using it as my day-to-day ph

Re: First impressions on new Android rootfs

Warren Baird wrote: > > > I agree Android looks like it has a lot of promise - but if you want a > functioning phone today - I'd suggest trying out QtExtended 4.4.2 - it > doesn't give you much more than basic phone functionality, but I've been > using it as my day-to-day phone for a month now

Re: First impressions on new Android rootfs

On Wed, Dec 3, 2008 at 10:19 AM, Gothnet <[EMAIL PROTECTED]>wrote: > > //just kidding, though am interested because android currently looks like > the best possibility of turning my neo from an interesting looking brick to > an actual phone I agree Android looks like it has a lot of promise - bu

Re: First impressions on new Android rootfs

Sean McNeil wrote: > > > bluetooth is setup to work with the new andy-tracking kernel. They've > switched to using an rfkill switch which I didn't implement in the > 2.6.26 kernel. > > ... > > I forgot there is a permission setting in /init.rc that needs to be > changed as well. Essential

Re: First impressions on new Android rootfs

Jim Ancona wrote: > Cédric Berger wrote: > >> On Tue, Dec 2, 2008 at 14:27, Gothnet <[EMAIL PROTECTED]> wrote: >> >>> Improvements since the first release are evident, the graphics are now >>> pretty >>> glitch free where they used to occasionally flicker. >>> >>> However, since the last i

Re: First impressions on new Android rootfs

On Tue, Dec 2, 2008 at 16:38, Gothnet <[EMAIL PROTECTED]> wrote: > > Please forgive me for replying to so many of my own emails... > > Apparently the answer is "setprop net.usb0.dns1 $IP_ADDRESS" > > Though I haven't made it do anything because the browser won't start, > there's no keypad to enter

Re: First impressions on new Android rootfs

Please forgive me for replying to so many of my own emails... Apparently the answer is "setprop net.usb0.dns1 $IP_ADDRESS" Though I haven't made it do anything because the browser won't start, there's no keypad to enter mail settings and the only command line tool I can find (ping) doesn't seem

Re: First impressions on new Android rootfs

On Tuesday 02 December 2008, Jim Ancona wrote: > Cédric Berger wrote: > > On Tue, Dec 2, 2008 at 14:27, Gothnet <[EMAIL PROTECTED]> wrote: > >> Err... does anyone know if suspend/resume works yet? > > > > - suspend/resume is known not work yet (at least not reliably). > > Using Sean's new rootfs a

Re: First impressions on new Android rootfs

Yup, DNS is the issue now. Attached to another machine I can ping 66.249.91.147 but lookup of www.google.com fails. To create a resolv.conf i had to remount the root filesystem as rw with - mount -o remount,rw -t jffs2 /dev/root / But it didn't help. So, yes, net access over USB but no DNS. --

Re: First impressions on new Android rootfs

Cédric Berger wrote: > On Tue, Dec 2, 2008 at 14:27, Gothnet <[EMAIL PROTECTED]> wrote: >> Improvements since the first release are evident, the graphics are now pretty >> glitch free where they used to occasionally flicker. >> >> However, since the last image I flashed, bluetooth has stopped worki

Re: First impressions on new Android rootfs

Cédric Berger wrote: > > For now, most wanted for me is a keyboard, and internet connectivity > (90% off android applications need internet access !). > Wifi does not work, GPRS either (for me at least), and I did not > manage to have internet access via USB (though I have read this may > work

Re: First impressions on new Android rootfs

On Tue, Dec 2, 2008 at 14:27, Gothnet <[EMAIL PROTECTED]> wrote: > > Improvements since the first release are evident, the graphics are now pretty > glitch free where they used to occasionally flicker. > > However, since the last image I flashed, bluetooth has stopped working, I > now just get a me