e3-hacking

e3-hacking@earth.li

395 discussions

LCD backlight update
by Piotr Michniewski 17 Sep '06

17 Sep '06

Hi, I've updated the backlight driver, so it compiles (and works !) under 2.6.17. The code is probably ugly, but it's my first approach to hacking a kernel driver... I am unable to make a patch, because I forgot to copy the source file before making changes, so I'm just posting the modified ams_delta_bl.c . -- Piotr Michniewski

2 2

Why won't my E3 boot?
by Matt Callow 04 Sep '06

04 Sep '06

I know the short answer - because my camera driver has broken it! But I was hoping that someone may be able to give me some clues as to why. I'm using nfs root at the moment, and if I build a kernel without the camera driver enabled it works find. If I build the camera driver as a module, it works fine. But if I compile the camera driver as a builtin, it fails to boot because it cannot init the network. I'm using a Linksys USB Ethernet adapter and the Pegasus driver. I've attached a side by side diff of the 2 boot logs. In both cases, the Pegasus driver is started. But in the failing case, the driver init seems to be delayed until after the IP/TCP/NET init, which I guess it too late. Initially, I though that maybe the camera driver has messed up the USB config, but now I'm not sure since in both cases the ethernet adapter is found. But I have a vague memory about someone fixing the USB driver (something to so with the clocks?) and I'm wondering if that may be the issue. Anyone got any ideas/suggestions of things I can try to track this down? Matt Starting kernel ... Starting kernel ... Uncompressing Linux.......................................... | Uncompressing Linux.......................................... Linux version 2.6.16.2-omap2 (matt@fileserver) (gcc version 3 | Linux version 2.6.16.2-omap2 (matt@fileserver) (gcc version 3 CPU: ARM925Tid(wt) [54029252] revision 2 (ARMv4T) CPU: ARM925Tid(wt) [54029252] revision 2 (ARMv4T) Machine: Amstrad E3 (Delta) Machine: Amstrad E3 (Delta) Memory policy: ECC disabled, Data cache writethrough Memory policy: ECC disabled, Data cache writethrough OMAP1510 revision 2 handled as 15xx id: 53058f9ab2160e1e OMAP1510 revision 2 handled as 15xx id: 53058f9ab2160e1e SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x30000 SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x30000 CPU0: D VIVT write-back cache CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 2, 16 byte lines, 5 CPU0: I cache: 16384 bytes, associativity 2, 16 byte lines, 5 CPU0: D cache: 8192 bytes, associativity 2, 16 byte lines, 25 CPU0: D cache: 8192 bytes, associativity 2, 16 byte lines, 25 Built 1 zonelists Built 1 zonelists Kernel command line: mem=32M console=ttyS0,115200n8 nfsroot=1 Kernel command line: mem=32M console=ttyS0,115200n8 nfsroot=1 ams_delta_init_irq ams_delta_init_irq Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x0013 ARM_CKCTL: 0x250e Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x0013 ARM_CKCTL: 0x250e Clocking rate (xtal/DPLL1/MPU): 12.0/150.0/150.0 MHz Clocking rate (xtal/DPLL1/MPU): 12.0/150.0/150.0 MHz Total of 64 interrupts in 2 interrupt banks Total of 64 interrupts in 2 interrupt banks OMAP1510 GPIO hardware OMAP1510 GPIO hardware PID hash table entries: 256 (order: 8, 4096 bytes) PID hash table entries: 256 (order: 8, 4096 bytes) Console: colour dummy device 80x30 Console: colour dummy device 80x30 Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 32MB = 32MB total Memory: 32MB = 32MB total Memory: 30124KB available (1732K code, 413K data, 104K init) | Memory: 30096KB available (1752K code, 418K data, 108K init) Mount-cache hash table entries: 512 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 NET: Registered protocol family 16 ams_delta_init ams_delta_init <4>MUX: initialized UART1_TX <4>MUX: initialized UART1_TX MUX: initialized UART1_RTS MUX: initialized UART1_RTS Installing fiq handler from c002d868, length 0x1ac | Installing fiq handler from c002e868, length 0x1ac request_fiq(): fiq_buffer = c0225610 | request_fiq(): fiq_buffer = c022c6d0 DMA support for OMAP15xx initialized DMA support for OMAP15xx initialized Initializing OMAP McBSP system Initializing OMAP McBSP system omap_dsp_init() done omap_dsp_init() done USB: hmc 16, usb0 2 wires USB: hmc 16, usb0 2 wires i2c_omap i2c_omap.1: bus 0 rev1.0 at 100 kHz i2c_omap i2c_omap.1: bus 0 rev1.0 at 100 kHz usbcore: registered new driver usbfs usbcore: registered new driver usbfs usbcore: registered new driver hub usbcore: registered new driver hub io scheduler noop registered io scheduler noop registered io scheduler anticipatory registered (default) io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler deadline registered io scheduler cfq registered io scheduler cfq registered Amstrad Delta backlight driver initialized. Amstrad Delta backlight driver initialized. omapfb: configured for panel ams-delta omapfb: configured for panel ams-delta omapfb-lcdc: init omapfb-lcdc: init Console: switching to colour frame buffer device 80x29 Console: switching to colour frame buffer device 80x29 omapfb: initialized vram=1048576 pixclock 3750 kHz hfreq 7.9 omapfb: initialized vram=1048576 pixclock 3750 kHz hfreq 7.9 OMAP RTC Driver OMAP RTC Driver omap_rtc: RTC power up reset detected. omap_rtc: RTC power up reset detected. omap_rtc: Enabling RTC. omap_rtc: Enabling RTC. serio: AMS DELTA keyboard adapter serio: AMS DELTA keyboard adapter Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ shar Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ shar serial8250: ttyS1 at MMIO 0x4000000 (irq = 162) is a 16550A serial8250: ttyS1 at MMIO 0x4000000 (irq = 162) is a 16550A serial8250.0: ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST1665 serial8250.0: ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST1665 RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 b RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 b loop: loaded (max 8 devices) loop: loaded (max 8 devices) PPP generic driver version 2.4.2 PPP generic driver version 2.4.2 i2c /dev entries driver i2c /dev entries driver Linux video capture interface: v1.00 Linux video capture interface: v1.00 > OMAP Camera driver initialzing > omap1510_cam_init > OV6650 sensor chip > 6650sensor_try_format sizeimage=202752 > omap-camera: OMAP1510 Camera Parallel interface with OV6650 s > omap-camera: registered device video0 [v4l2] usbmon: debugfs is not available usbmon: debugfs is not available ohci ohci: OMAP OHCI ohci ohci: OMAP OHCI ohci ohci: new USB bus registered, assigned bus number 1 ohci ohci: new USB bus registered, assigned bus number 1 ohci ohci: irq 38, io mem 0xfffba000 ohci ohci: irq 38, io mem 0xfffba000 usb usb1: configuration #1 chosen from 1 choice usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected hub 1-0:1.0: 3 ports detected pegasus: v0.6.13 (2005/11/13), Pegasus/Pegasus II USB Etherne pegasus: v0.6.13 (2005/11/13), Pegasus/Pegasus II USB Etherne usb 1-1: new full speed USB device using ohci and address 2 < usb 1-1: configuration #1 chosen from 1 choice < pegasus 1-1:1.0: setup Pegasus II specific registers < pegasus 1-1:1.0: eth0, Linksys USB USB100TX, 00:04:5a:90:37:7 < usbcore: registered new driver pegasus usbcore: registered new driver pegasus mice: PS/2 mouse device common for all mice mice: PS/2 mouse device common for all mice OMAP Keypad Driver OMAP Keypad Driver input: omap-keypad as /class/input/input0 input: omap-keypad as /class/input/input0 NET: Registered protocol family 2 NET: Registered protocol family 2 input: AT Raw Set 2 keyboard as /class/input/input1 input: AT Raw Set 2 keyboard as /class/input/input1 IP route cache hash table entries: 512 (order: -1, 2048 bytes IP route cache hash table entries: 512 (order: -1, 2048 bytes TCP established hash table entries: 2048 (order: 1, 8192 byte TCP established hash table entries: 2048 (order: 1, 8192 byte TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered TCP reno registered TCP bic registered TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 17 Sending DHCP requests ., OK | usb 1-1: new full speed USB device using ohci and address 2 IP-Config: Got DHCP answer from 192.168.1.94, my address is 1 | usb 1-1: configuration #1 chosen from 1 choice eth0: set allmulti | pegasus 1-1:1.0: setup Pegasus II specific registers IP-Config: Complete: | IP-Config: No network devices available. device=eth0, addr=192.168.1.124, mask=255.255.255.0, gw < host=192.168.1.124, domain=mcallow.homelinux.net, nis-do < bootserver=192.168.1.94, rootserver=192.168.1.94, rootpa < Looking up port of RPC 100003/2 on 192.168.1.94 Looking up port of RPC 100003/2 on 192.168.1.94 > Root-NFS: Unable to get nfsd port number from server, using d Looking up port of RPC 100005/1 on 192.168.1.94 Looking up port of RPC 100005/1 on 192.168.1.94 VFS: Mounted root (nfs filesystem). | Root-NFS: Unable to get mountd port number from server, using Freeing init memory: 104K | Root-NFS: Server returned error -5 while mounting /home/matt/ Initializing random number generator... done. | VFS: Unable to mount root fs via NFS, trying floppy. Starting network... | Kernel panic - not syncing: VFS: Unable to mount root fs on u modprobe: failed to load module wlan0 < Error for wireless request "Set ESSID" (8B1A) : < SET failed on device wlan0 ; Invalid argument. < run-parts: /etc/network/if-pre-up.d/wlan exited with return c < Starting dropbear sshd: OK < Starting telnetd... < /etc/init.d/rcS: 26: /etc/init.d/S60mpd: Permission denied < < < BusyBox v1.01 (2006.03.07-08:46+0000) Built-in shell (ash) < Enter 'help' for a list of built-in commands. < / # <

6 11

Boot from flash
by Antony Stone 03 Sep '06

03 Sep '06

Hi. I've just got my first E3 booting Linux 2.6.17 using the Wiki guidelines. It's great to see a Tux logo on the E3 display with the kernel boot messages going past, and to have a command line at the other end of the serial port. I have two questions: 1. How do I enable the E3's keyboard/s so that I can use the ash shell from there as well as (or instead of) on the end of the serial port? (I've tried changing the kernel boot arguments from "console=tty0 console=ttyS0,115200n8" to "console=ttyS0,115200n8 console=tty0"; I've tried just "console=tty0" and I've tried no console definition at all.) 2. Now that I know I have a 2.6.27 kernel which works on the machine, is there a way to load this into the onboard flash so that the machine boots standalone into real Linux, instead of having to use the serial cable every time? Thanks, Antony. -- Python is executable pseudocode. Perl is executable line noise. Please reply to the list; please don't CC me.

2 2

Electronics in E3
by Bob Duncan 03 Sep '06

03 Sep '06

I have read the digests with interest. However I am an electronics type person rather than a programmer, though I do frequently programme ROMs etc when supplied with an image. I am not familiar as to how to go from source code to ROM image especially in Linux. Can anyone enlighten me as to whether there is an electronic fix for this machine (which I bought for fun at Tescos and have absolutely no intention of paying AMS anything) especially when one uses broadband on a monthly fee basis. Thanks Bob Duncan

2 1

Opie on the E3 woes...
by Brendan Berney 30 Aug '06

30 Aug '06

Hi, Thanks for those tips... Sean, you had it right... It now boots with the delay (although it then runs into other problems further down the line....which I'll have a look at). Cheers! Brendan PS.. And it was /dev/sda1 - typo there....

1 0

Opie on the E3 woes...
by Brendan Berney 29 Aug '06

29 Aug '06

Hi everyone, Firstly, let me just say that I'm V. impressed with the work everyone on this group is putting into this. When I first saw one of these things in Tesco for next to nothing I though - cool, now I can do a yell.co.uk lookup without having to wait for a laptop to boot etc. Anyway, with a view to this I plodded off to OpenEmbedded and started playing. At first I manually patched the OE snapshot using David Ford's patches and managed to build the uImage, bootstrap image and a (massively cut down) Opie image. My first problem at that stage was, and still is, how to get the E3 to 'see' the rootfs. Here is what I did: First I got hold of an old 128MB usb flash card and formatted it as an ext2 fs. Next I 'untared' the rootfs.tar.bz2 file that bitbake and OE had generated onto this with the result that I had a perfectly readable root fs on the USB stick. I then created an 'opie' pbl file thus: write 0x11900000 uImage-amsdelta-20060606090139.bin write 0x11f00000 u-boot-amsdelta-1.1.4-r0.bin exec 0x11f00000 which successfully loads the bootstrap and kernel images into the e3. At the u-boot command line, I issued the following: setenv bootargs mem=32M root=/dev/sda0 rootfstype=ext2 and then... on the bootm command everything appears to work...at first. Ultimately I get stuck with: VFS: No root yet, retrying to mount root on sda0 (unknown block(0,0)) Kernel panic: Unable to mount root fs on etc.etc. Please let me know what I am missing, no doubt I have done something stupid. I seem to remember that maybe I need to pivot the bootup using a ramdisk but don't know how to do this... My second problem is that, having noticed that recent OE snapshots no incorporate the work to date, I set off to try with one of those and rashly deleted my working snapshot... Anyway whilst I can get (with much fiddling) a UImage and bootstrap image built, I cannot get an Opie image anymore :-(. There seem to be many clashes between certain parts (such as bluetooth support) and the newer kernel. Does anyone have a recent OE snapshot that works and is prepared to put it up here? Cheers all, Wiretrip (Brendan Berney)

4 3

Amstrad E3
by wongchin 19 Aug '06

19 Aug '06

Hi Everybody , I bought a Amstrad E3 emailer since a ling time when I was in U.K . I use it in Mauritius for only 15 days as I have registered in U.K. Can somebody tell me how to modify itfor using as normal phone in overseas like Mauritius. Many thanks for your help. Francois Wong

1 0

RE: [E3-hacking] AT commands to make voice calls - need help!
by Martin Whitaker 15 Aug '06

15 Aug '06

Hey again! Just an update incase this information is of use to anyone else. I've managed to make a normal voice telephone call using the E3 through the handset. Here are the commands I used: ATZ AT+FCLASS=8 AT+VIP ATM0 ATX0 AT+VNH=1 AT+VLS=2 ATDT<number>; You can probably get away without some of those - the important ones really are: AT+FCLASS=8 <places the modem into voice mode> ATM0 <turns off the internal speaker> ATX0 <prevents looking for a dialtone before dialing - you may not need this> AT+VLS=2 <selects the handset as the analogue source / destination> ATDT<number>; <note the semicolon at the end - this causes the modem to make a voice call not a data one> Noodles suggested the use of ATM0 - works a treat! Thanks. M. -----Original Message----- From: e3-hacking-bounces(a)earth.li [mailto:e3-hacking-bounces@earth.li]On Behalf Of Martin Whitaker Sent: 09 August 2006 18:42 To: e3-hacking(a)earth.li Cc: Martin Whitaker Subject: [E3-hacking] AT commands to make voice calls - need help! Hey Folks, I've been trying to find the right sequence of AT command to make a normal voice call on the E3 through it's internal modem. I haven't managed it yet, so am looking for suggestions. Apologies for the long mail! So far I've managed to make a phone call through the speaker and mic on the base using: AT+FCLASS=8 AT+VIP AT+VNH=1 AT+VSP=1 AT+VGM=127 ATDT<number> ..all fairly standard stuff. Having done that I then tried messing around with AT+VLS to set the source, only I didn't get very far. All of the options either reported 'ERROR' or resulted in no source connected, with the exception of AT+VLS=2 and AT+VLS=3, both of which seem to connected the handset as well as the speakerphone, mostly causing lots of feedback. AT+VLS=? will report the valid options, here is the output: AT+VLS=? 0," ",0000000000,0000000000,B084008000 1,"T",0B8418E000,0FE418E000,0B8419E000 2,"L",0884008000,0CE4008000,0884018000 3,"LT",0B8418E000,0FE418E000,0B8419E000 4,"S",0084008000,0484008000,3084018000 5,"ST",0B8418E000,0FE418E000,0B8419E000 6,"M",0084008000,04E4008000,3084008000 8,"S1",0084008000,0484008000,3084018000 9,"S1T",0B8418E000,0FE418E000,0B8419E000 11,"M1",0084008000,04E4008000,3084008000 13,"M1S1T",0B8418E000,0FE418E000,0B8419E000 14,"H",0084008000,04E4008000,3084018000 15,"HT",0B8418E000,0FE418E000,0B8419E000 19,"M1S1",0084008000,04E4008000,3084018000 20,"t",0B8418E000,0FE418E000,BB8419E000 According to the Conexant AT command reference the letters in the first column mean: L Local Phone. T Telephone Line. M Internal Microphone. M1 External Microphone. S Internal Speaker. S1 External Speaker. H External Microphone and Speaker combination (handset or headset). ..so it would appear that the handset on the E3 is classed as the 'local phone'. Not that it really helps me much. On a different thread of investigation I can successfully use 'vm' from the mgetty/vgetty package to record and playback sounds from the handset. When I do that the base speaker and microphone are definatly NOT turned on, so all appears well. So... I dumped the list of AT command which 'vm' was sending to the modem... they are as follows: voice command: 'AT+FCLASS=8' -> 'OK' : Place in voice mode voice command: 'AT+VSM=?' -> '' : List compression modes available voice command: 'AT+VSD=40,70' -> 'OK' : Silence detection voice command: 'AT+VGT=127' -> 'OK' : Voice gain transmit (playback volume) voice command: 'AT+VGR=127' -> 'OK' : Voice gain receive (record gain) voice command: 'AT+VRA=70;+VRN=10' -> 'OK' : Ringback goes away timer, Ringback never appeared timer voice command: 'AT+IFC=2,2' -> 'OK' : Setup Flow control voice command: 'AT+VCID=1' -> 'OK' : CallerID enabled with formatted info voice command: 'AT+VNH=0' -> 'OK' : Enable automatic hangups voice command: 'AT+VIT=0' -> 'OK' : Voice inactivity timer voice command: 'AT+VDR=1,15' -> 'OK' : Distinctive ring voice command: 'AT+FCLASS=0' -> 'OK' : Put back into normal mode voice command: 'AT' -> 'OK' voice command: 'AT+FCLASS?' -> '' : Report available modes voice command: '' -> 'OK' voice command: 'AT+FCLASS=8' -> 'OK' : Place in voice mode voice command: 'AT' -> 'OK' voice command: 'AT+VLS=2' -> 'OK' : Select analog source '2' voice command: 'AT+VSM=130,8000' -> 'OK' : Setup compression method voice command: 'AT+VSM=130,8000' -> 'OK' : Setup compression method voice command: 'AT+IFC=2,2' -> 'OK' : Setup Flow control voice command: 'AT+VTX' -> 'CONNECT' : Enter playback mode (plays voice here) So.... does anyone have any suggestions as to what I can try next? (or even better has anyone managed to make a phone call with just the handset enabled and can tell me how?). Regards, Martin. _______________________________________________ e3-hacking mailing list e3-hacking(a)earth.li http://www.earth.li/cgi-bin/mailman/listinfo/e3-hacking

1 0

AT commands to make voice calls - need help!
by Martin Whitaker 09 Aug '06

09 Aug '06

Hey Folks, I've been trying to find the right sequence of AT command to make a normal voice call on the E3 through it's internal modem. I haven't managed it yet, so am looking for suggestions. Apologies for the long mail! So far I've managed to make a phone call through the speaker and mic on the base using: AT+FCLASS=8 AT+VIP AT+VNH=1 AT+VSP=1 AT+VGM=127 ATDT<number> ..all fairly standard stuff. Having done that I then tried messing around with AT+VLS to set the source, only I didn't get very far. All of the options either reported 'ERROR' or resulted in no source connected, with the exception of AT+VLS=2 and AT+VLS=3, both of which seem to connected the handset as well as the speakerphone, mostly causing lots of feedback. AT+VLS=? will report the valid options, here is the output: AT+VLS=? 0," ",0000000000,0000000000,B084008000 1,"T",0B8418E000,0FE418E000,0B8419E000 2,"L",0884008000,0CE4008000,0884018000 3,"LT",0B8418E000,0FE418E000,0B8419E000 4,"S",0084008000,0484008000,3084018000 5,"ST",0B8418E000,0FE418E000,0B8419E000 6,"M",0084008000,04E4008000,3084008000 8,"S1",0084008000,0484008000,3084018000 9,"S1T",0B8418E000,0FE418E000,0B8419E000 11,"M1",0084008000,04E4008000,3084008000 13,"M1S1T",0B8418E000,0FE418E000,0B8419E000 14,"H",0084008000,04E4008000,3084018000 15,"HT",0B8418E000,0FE418E000,0B8419E000 19,"M1S1",0084008000,04E4008000,3084018000 20,"t",0B8418E000,0FE418E000,BB8419E000 According to the Conexant AT command reference the letters in the first column mean: L Local Phone. T Telephone Line. M Internal Microphone. M1 External Microphone. S Internal Speaker. S1 External Speaker. H External Microphone and Speaker combination (handset or headset). ..so it would appear that the handset on the E3 is classed as the 'local phone'. Not that it really helps me much. On a different thread of investigation I can successfully use 'vm' from the mgetty/vgetty package to record and playback sounds from the handset. When I do that the base speaker and microphone are definatly NOT turned on, so all appears well. So... I dumped the list of AT command which 'vm' was sending to the modem... they are as follows: voice command: 'AT+FCLASS=8' -> 'OK' : Place in voice mode voice command: 'AT+VSM=?' -> '' : List compression modes available voice command: 'AT+VSD=40,70' -> 'OK' : Silence detection voice command: 'AT+VGT=127' -> 'OK' : Voice gain transmit (playback volume) voice command: 'AT+VGR=127' -> 'OK' : Voice gain receive (record gain) voice command: 'AT+VRA=70;+VRN=10' -> 'OK' : Ringback goes away timer, Ringback never appeared timer voice command: 'AT+IFC=2,2' -> 'OK' : Setup Flow control voice command: 'AT+VCID=1' -> 'OK' : CallerID enabled with formatted info voice command: 'AT+VNH=0' -> 'OK' : Enable automatic hangups voice command: 'AT+VIT=0' -> 'OK' : Voice inactivity timer voice command: 'AT+VDR=1,15' -> 'OK' : Distinctive ring voice command: 'AT+FCLASS=0' -> 'OK' : Put back into normal mode voice command: 'AT' -> 'OK' voice command: 'AT+FCLASS?' -> '' : Report available modes voice command: '' -> 'OK' voice command: 'AT+FCLASS=8' -> 'OK' : Place in voice mode voice command: 'AT' -> 'OK' voice command: 'AT+VLS=2' -> 'OK' : Select analog source '2' voice command: 'AT+VSM=130,8000' -> 'OK' : Setup compression method voice command: 'AT+VSM=130,8000' -> 'OK' : Setup compression method voice command: 'AT+IFC=2,2' -> 'OK' : Setup Flow control voice command: 'AT+VTX' -> 'CONNECT' : Enter playback mode (plays voice here) So.... does anyone have any suggestions as to what I can try next? (or even better has anyone managed to make a phone call with just the handset enabled and can tell me how?). Regards, Martin.

1 0

E3 E-mailer reportedly down to £14.98 at *some* Tesco stores
by John Osborne 06 Aug '06

06 Aug '06

The Tesco Extra in Kingston Park (Tyne & Wear) do have the E3 for £14.98, I just bought my second one from them today so I can now worry less about breaking at least one of them ;) Also the PBL is the all important 4.9 version too :D

1 0

← Newer
1
...
16
17
18
19
20
21
22
...
40
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

e3-hacking