Re: FR: Problems, problems: please help
On Tue, 24 Mar 2009 01:33:10 +0100
Toni Mueller wrote {heavily snipped}:
> about one or two weeks ago, I've purchased a new FR, but haven't
> gotten it to work as much as to be usable as a phone yet. The only
> application that seems to be reliable so far is "sudoku", which I
> don't need.
> After investing some 20 hours or so, I'm now at a loss
> and don't know what else to try.
hmmm. 1-2 weeks, 20 hours. Sounds about right... :) I've figured
that I average about 10 hours a week with my FreeRunner (plus a few on
the mailing lists), down from about 30 a week the first few months.
> > There were a few issues with uboot early on, but if yours shipped
> > with 2008.8 it probably has a fixed version. There may be an
> > argument for updating to Qi, but you are probably better off
> > sticking with uboot for the moment.
>
> I read about Qi, but since it can't do the networking and flashing
> stuff, according to the wiki, I didn't try. Currently, maintenance
> facilities are of utmost importance to me.
I've been using Qi for a few months now - it's a bit faster, and a lot
'quieter' - near-zero console messages during boot, and no bootsplash.
(not as pretty, but saves several seconds) It offers no boot menu,
so left to its own it will look for a kernel in /boot in each of the
first three (ext2/ext3) partitions on uSD, and failing that it will boot
the kernel in NAND. If you want to experiment with two different images
at once, one NAND and one on uSD, uBoot is simpler. (if you want four
you need to log into the uboot boot prompt via USB and edit the boot
parameters to support more than one on uSD)
Qi doesn't set up DFU support on boot, so you can't flash using it, but
you only put Qi in NAND - you can still boot from the uBoot in NOR and
use that to flash. (turn on with power...+aux for NAND, aux+power for
NOR)
> > or the repositories may have moved. The URLs for the repositories
> > can be found in files under /etc/opkg. I can't comment on the
> > specifics for 2008.12 as I haven't used it.
>
> Under /etc/opkg I find only the addresses of the repositories that
> were configured by the system, but not the repositories that I should
> try to access. IOW, I don't know what to write there.
True... :) However, I'm curious as to what IS there.
The new toolchain Angus Ainsley announced a few hours ago contains the
following in opkg.conf (I'm not running 2008.x so have no other
reference, and usually each feed is in a separate file):
arch all 1
src/gz all http://downloads.openmoko.org/repository/unstable/all
arch any 6
src/gz any http://downloads.openmoko.org/repository/unstable/any
arch noarch 11
src/gz noarch http://downloads.openmoko.org/repository/unstable/noarch
arch arm 16
src/gz arm http://downloads.openmoko.org/repository/unstable/arm
arch armv4 21
src/gz armv4 http://downloads.openmoko.org/repository/unstable/armv4
arch armv4t 26
src/gz armv4t http://downloads.openmoko.org/repository/unstable/armv4t
arch om-gta02 31
src/gz om-gta02
http://downloads.openmoko.org/repository/unstable/om-gta02
So it would seem that those are the feeds that an up-to-date toolchain
will build packages against.
The /repository/testing folders are (IIRC, someone may correct me here)
the ones for 2008.12, but were last updated Jan 20.
> > > FWIW, I expect to be able to use the device as a phone, a
> > > navigation system, a music player and voice recorder.
http://www.opkg.org/package_8.html - TangoGPS (tracking/mapping)
http://www.opkg.org/package_5.html - Navit (navigation)
http://www.opkg.org/package_140.html - voicenote recorder
http://www.opkg.org/package_1.html - pythm music player
> > Try some of the other distros. You may find it easier to boot off
> > SD rather than reflash every time, and you could even dual- or
> > multi-boot. See: http://wiki.openmoko.org/wiki/Booting_from_SD
>
> This is also only mentioned, but I could find no mentioning of how to
> _install_ something on the SD card in the first place, or at least, I
> didn't find it yet. Likewise for selecting the right one out of
> umpteen distros that I might have installed (I have an 8GB card in the
> device).
http://wiki.openmoko.org/wiki/Booting_from_SD
Taking the simpler case of a single installation on uSD and one in
NAND, put the uSD into a reader on a desktop/laptop and partition it
and install files as below.
If using uBoot I believe you need separate /boot partition still, which
used to be vfat but now (newer uboot from factory or flashed over NAND
uboot) works with ext2/ext3 /boot - just place the kernel file in the
root of that partition (first on the card), then extract the image
tarball (download the tar.gz instead of the .jffs for an SD install)
into the second partition, ext2/ext3.
If using Qi it expects the kernel in /boot as a folder in the root
partition itself, so extract the image tarball to the first (or only)
partition, ext2/ext3, then put the kernel in /boot. (actually the
rootfs already contains the kernel, IIRC)
Re: FR: Problems, problems: please help
Hi, On Tue, 24.03.2009 at 00:04:26 +, Al Johnson wrote: > On Monday 23 March 2009, Toni Mueller wrote: > > about one or two weeks ago, I've purchased a new FR, but haven't gotten > > it to work as much as to be usable as a phone yet. The only application > > that seems to be reliable so far is "sudoku", which I don't need. > > Few people can agree on what a 'usable phone' is, but some of us have found > combinations that make the Freerunner usable for us. can we perhaps agree on "all hardware usable on a daily basis"? > There are a _lot_ of options though, Yes, but documentation is _poor_. > combination. I hope you find something that works for you. I hope, too, but currently, and although I consider myself a Free Software zealot, I am about to lose hope. > There were a few issues with uboot early on, but if yours shipped with 2008.8 > it probably has a fixed version. There may be an argument for updating to Qi, > but you are probably better off sticking with uboot for the moment. I read about Qi, but since it can't do the networking and flashing stuff, according to the wiki, I didn't try. Currently, maintenance facilities are of utmost importance to me. > GTA02 is the Freerunner. v6 is the board revision, and the 0360 shows that it > is v6 that you have. It includes a couple of relatively minor improvements Thanks for the clarification. > over v5, and is AFAIK still the latest version shipping. It was advertised as having a "GPS fix" over v5, and I'd like to verify that GPS works (ie, as opposed to having a (partially) DOA device). > This may be because of a networking problem, Not on my end, though. I specified a local Squid proxy to go through. > or the repositories may have moved. The URLs for the repositories can > be found in files under /etc/opkg. I can't comment on the specifics > for 2008.12 as I haven't used it. Under /etc/opkg I find only the addresses of the repositories that were configured by the system, but not the repositories that I should try to access. IOW, I don't know what to write there. > > * I can make and receive calls. I sound like I'm in an old oil can, > >however. > More recent distros (should) have fixed the echo problem. That was claimed of the Om2008.12, too. > Low audio volume can be fixed by adjusting the mixer settings. I find > manually > adjusting the config files easiest, but there is also a GUI available. See: > http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem Ok... a shell in the box, w/o the need to SSH into it, would be nice, too. > >Using the phone near a server (no problem for my old standard phone, > >a 6230i) can safely be ruled out that way. It also only works when > >I'm standing near a GSM station. At home, where my standard phone "near" = in sight of > This seems odd. My FR has similar sensitivity to my old k700. It might be > worth checking the label under the battery to see you have the > 900/1800/1900MHz European version not the 850/1800/1900MHz US version. I was once able to make a call, and I just checked the label to confirm that I have the European version. But then I read about a GSM update that is both recommended and highly dangerous - I didn't try that one yet, however, as it's also a bit hazy in the docs... > I assume that's a 2008.12 bug. Umm... It never worked, neither before nor after the flashing, and also even not with the external antenna. > > FWIW, I expect to be able to use the device as a phone, a navigation > > system, a music player and voice recorder. > > That should be possible. tangogps and navit provide mapping with raster and > vector maps respectively. Yes, but it needs GSM and GPS before I can use two of these functions. > Try some of the other distros. You may find it easier to boot off SD rather > than reflash every time, and you could even dual- or multi-boot. See: > http://wiki.openmoko.org/wiki/Booting_from_SD This is also only mentioned, but I could find no mentioning of how to _install_ something on the SD card in the first place, or at least, I didn't find it yet. Likewise for selecting the right one out of umpteen distros that I might have installed (I have an 8GB card in the device). > See http://wiki.openmoko.org/wiki/Distributions for an overview of what's Done that already... the list gave the impression that the Om2008.12 (maybe a more recent edition?) would still be the best bet, though. Thank you! Kind regards, --Toni++ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FR: Problems, problems: please help
On Monday 23 March 2009, Toni Mueller wrote:
> Hi,
>
> about one or two weeks ago, I've purchased a new FR, but haven't gotten
> it to work as much as to be usable as a phone yet. The only application
> that seems to be reliable so far is "sudoku", which I don't need.
Few people can agree on what a 'usable phone' is, but some of us have found
combinations that make the Freerunner usable for us. There are a _lot_ of
options though, so some perseverance may be needed in finding the right
combination. I hope you find something that works for you.
> The gory details:
>
>
> When the phone came, it appeared to be flashed with Om2008.8, from the
> looks of the screen (black background).
>
> Today, I tried to re-flash the device with Om2008.12 using dfu-util,
> and got messages like
Snip reasonable looking dfu-util output
> While flashing, the FR displayed appropriate message like "writing root
> file system" (or so).
>
>
> I didn't flash the u-boot, since it was said that that wasn't needed,
> except in very rare cases. The wiki is a bit unclear about that,
> however.
There were a few issues with uboot early on, but if yours shipped with 2008.8
it probably has a fixed version. There may be an argument for updating to Qi,
but you are probably better off sticking with uboot for the moment.
> After a reboot, nothing seemed to have changed. I still have a black
> background (I don't mind that, however).
>
>
> The next step was to set up the USB networking. After doing so, I
> collected some info from the system:
> Hardware: GTA02
> Revision: 0360
> Serial :
>
> (The device was "advertised" as being a GTA02v6, whatever that may mean.)
GTA02 is the Freerunner. v6 is the board revision, and the 0360 shows that it
is v6 that you have. It includes a couple of relatively minor improvements
over v5, and is AFAIK still the latest version shipping.
> In any case, I thought I'd try with 'opkg', eg. 'opkg update', and
> 'opkg upgrade'. I found no way to download upgrades for the system,
> and no way to upgrade to Om2008.12 this way.
This may be because of a networking problem, or the repositories may have
moved. The URLs for the repositories can be found in files under /etc/opkg. I
can't comment on the specifics for 2008.12 as I haven't used it.
> What's (not) working now:
>
> * I can press buttons. Sometimes, the associated application starts
>("Settings": rarely, "Locations": 2/3 of the time).
>
> * Handling is generally clumsy - the phone is _slow_.
>
> * I can make and receive calls. I sound like I'm in an old oil can,
>however.
More recent distros (should) have fixed the echo problem.
>I get no ring tone, and generally have a very low audio volume.
Low audio volume can be fixed by adjusting the mixer settings. I find manually
adjusting the config files easiest, but there is also a GUI available. See:
http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem
>Using the phone near a server (no problem for my old standard phone,
>a 6230i) can safely be ruled out that way. It also only works when
>I'm standing near a GSM station. At home, where my standard phone
>gives me _all_ bars for GSM field strength, I get "no service"
>instead of the field strength indicator (I'm using T-Mobile/D1,
>in Germany). When I was able to inspect the settings, it said "Ring
>and vibration".
This seems odd. My FR has similar sensitivity to my old k700. It might be
worth checking the label under the battery to see you have the
900/1800/1900MHz European version not the 850/1800/1900MHz US version.
> * GPS does not work. So far, I _never_ got a GPS position, even not
>with an external GPS antenna. The one time I was able to fire up
>"Settings", and on every attempt to use "Locations", I said "yes"
>to enabling GPS, to no avail.
I assume that's a 2008.12 bug.
> * Software upgrade(s) may or may not have succeeded - I can't really
>tell at this point because proper documentation does not appear to
>be available. At least, the image shown for 2008.12 is not what I
>see on my phone, and no version number matches exactly what I have.
>
>
> FWIW, I expect to be able to use the device as a phone, a navigation
> system, a music player and voice recorder.
That should be possible. tangogps and navit provide mapping with raster and
vector maps respectively. There are several music player apps, and 3 or so
voice recorder apps in active development. Most of these will appear in the
list at opkg.org though there have been some problems with packages downloaded
from there recently.
> After investing some 20 hours or so, I'm now at a loss and don't know
> what else to try.
Try some of the other distros. You may find it easier to boot off SD rather
than reflash every time, and you could even dual- or multi-boot. See:
http://wiki.openmoko.org/wiki/Booting_from_SD
See http://wiki.openmoko.org/wiki/D
Re: [OM 2008.12] FR: Problems, problems: please help
On Mon, Mar 23, 2009 at 11:24:49PM +0100, Toni Mueller wrote: > > I didn't flash the u-boot, since it was said that that wasn't needed, > except in very rare cases. The wiki is a bit unclear about that, > however. It depends on how old the u-boot your Freerunner shipped with is. In any case, it will have trouble reading above 4 GB on SDHC-cards since the patch to make it do that was posted just yesterday: https://lists.openmoko.org/pipermail/openmoko-kernel/2009-March/009573.html > r...@om-gta02:/etc/opkg# cat /proc/version > Linux version 2.6.24 (bu...@barbie) (gcc version 4.1.2) #1 PREEMPT Wed Dec 17 > 02:13:29 CST 2008 That kernel is outdated. For starters, the power management has bugs and the hardware clock runs a month behind, which is a problem because the months don't have the same number of days. For the OM 200x distributions to have any sort of future, the kernel bug fixes need to be backported to the old 2.6.24 series or OM 2009.x adapted to work with a 2.6.28 (or later) kernel. > r...@om-gta02:/etc/opkg# cat /etc/om-version > Tag Name: > VERSION: cd512fd1e1aee5f4ba368d8acc1f2fb7a32773d3 > Branch: org.openmoko.stable > Build Host: barbie > Time Stamp: Thu, 18 Dec 2008 00:15:27 +0800 OM 2008.12. > (The device was "advertised" as being a GTA02v6, whatever that may mean.) https://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware#History Significant improvements of v6 compared to v5: It can be turned on without a battery (or with a depleted battery). GPS reception isn't disturbed by the SD-card slot. Turning on the AUX button light draws much less current. > In any case, I thought I'd try with 'opkg', eg. 'opkg update', and > 'opkg upgrade'. I found no way to download upgrades for the system, > and no way to upgrade to Om2008.12 this way. There's a file under /etc/opkg or so that you can modify to select where to get updates from. > * GPS does not work. So far, I _never_ got a GPS position, even not >with an external GPS antenna. The one time I was able to fire up >"Settings", and on every attempt to use "Locations", I said "yes" >to enabling GPS, to no avail. Did you try outdoors? Usually GPS signals can't be received inside a building, but it may work with the receiver pressed up against a window. Outdoors, with most of the sky visible, you should get a fix in 35 - 45 seconds. > FWIW, I expect to be able to use the device as a phone, a navigation > system, a music player and voice recorder. > > After investing some 20 hours or so, I'm now at a loss and don't know > what else to try. https://wiki.openmoko.org/wiki/Distributions Try a few and see what you like. -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SD fails spectacularly and unpredictably when a SIM card is used
2009/3/23 Luca Capello > Hi there! > [...] > FWIW, I had problems with the same model, in 4GB size (SDC4/4GB, with > 311C3-001.A00LF written on it) and a Swisscom SIM. It seems that as > reported at [1] the I/O errors are still present. Hi Luca! May you retry debian installation again booting from a distro with gsm/stuff disabled at boot time repartitioning your sd? I'm quite sure that the problem is caused by GSM interference. Regards Nicola ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
FR: Problems, problems: please help
Hi,
about one or two weeks ago, I've purchased a new FR, but haven't gotten
it to work as much as to be usable as a phone yet. The only application
that seems to be reliable so far is "sudoku", which I don't need.
The gory details:
When the phone came, it appeared to be flashed with Om2008.8, from the
looks of the screen (black background).
Today, I tried to re-flash the device with Om2008.12 using dfu-util,
and got messages like
Found Runtime: [0x1d50:0x5119] devnum=3, cfg=0, intf=0, alt=3,
name="kernel"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
bytes_per_hash=35601
Starting download: [##]
finished
!
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
and
Opening USB Device 0x:0x...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=5, cfg=0, intf=0, alt=6,
name="rootfs"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
bytes_per_hash=1386741
Starting download: [##]
finished!
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
While flashing, the FR displayed appropriate message like "writing root
file system" (or so).
I didn't flash the u-boot, since it was said that that wasn't needed,
except in very rare cases. The wiki is a bit unclear about that,
however.
After a reboot, nothing seemed to have changed. I still have a black
background (I don't mind that, however).
The next step was to set up the USB networking. After doing so, I
collected some info from the system:
r...@om-gta02:/etc/opkg# cat /proc/version
Linux version 2.6.24 (bu...@barbie) (gcc version 4.1.2) #1 PREEMPT Wed Dec 17
02:13:29 CST 2008
r...@om-gta02:/etc/opkg# cat /etc/version
200812180014
r...@om-gta02:/etc/opkg# cat /etc/om-version
Tag Name:
VERSION: cd512fd1e1aee5f4ba368d8acc1f2fb7a32773d3
Branch: org.openmoko.stable
Build Host: barbie
Time Stamp: Thu, 18 Dec 2008 00:15:27 +0800
r...@om-gta02:/etc/opkg# cat /proc/cpuinfo
Processor : ARM920T rev 0 (v4l)
BogoMIPS: 199.47
Features: swp half thumb
CPU implementer : 0x41
CPU architecture: 4T
CPU variant : 0x1
CPU part: 0x920
CPU revision: 0
Cache type : write-back
Cache clean : cp15 c7 ops
Cache lockdown : format A
Cache format: Harvard
I size : 16384
I assoc : 64
I line length : 32
I sets : 8
D size : 16384
D assoc : 64
D line length : 32
D sets : 8
Hardware: GTA02
Revision: 0360
Serial :
(The device was "advertised" as being a GTA02v6, whatever that may mean.)
In any case, I thought I'd try with 'opkg', eg. 'opkg update', and
'opkg upgrade'. I found no way to download upgrades for the system,
and no way to upgrade to Om2008.12 this way.
What's (not) working now:
* I can press buttons. Sometimes, the associated application starts
("Settings": rarely, "Locations": 2/3 of the time).
* Handling is generally clumsy - the phone is _slow_.
* I can make and receive calls. I sound like I'm in an old oil can,
however.
I get no ring tone, and generally have a very low audio volume.
Using the phone near a server (no problem for my old standard phone,
a 6230i) can safely be ruled out that way. It also only works when
I'm standing near a GSM station. At home, where my standard phone
gives me _all_ bars for GSM field strength, I get "no service"
instead of the field strength indicator (I'm using T-Mobile/D1,
in Germany). When I was able to inspect the settings, it said "Ring
and vibration".
* GPS does not work. So far, I _never_ got a GPS position, even not
with an external GPS antenna. The one time I was able to fire up
"Settings", and on every attempt to use "Locations", I said "yes"
to enabling GPS, to no avail.
* Software upgrade(s) may or may not have succeeded - I can't really
tell at this point because proper documentation does not appear to
be available. At least, the image shown for 2008.12 is not what I
see on my phone, and no version number matches exactly what I have.
FWIW, I expect to be able to use the device as a phone, a navigation
system, a music player and voice recorder.
After investing some 20 hours or so, I'm now at a loss and don't know
what else to try.
Kind regards,
--Toni++
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: GSM Power Control
Am Mo 23. März 2009 schrieb Joel B. Land: > > The phone's actual transmitted power level does change - I tested this > > in the past while looking at the "gsm buzz" problem: > > > > http://lists.openmoko.org/pipermail/support/2008-August/001121.html > What about the Freerunner? No difference /j 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: GSM Power Control
Joel B. Land wrote: > > > http://lists.openmoko.org/pipermail/support/2008-August/001121.html > > What about the Freerunner? It has the same GSM chipset as the Neo1973 so there should be no difference. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [QT Extended Improved 20090316 snapbuild] Wake up from suspend on incoming call
Hmm - I haven't tried one of the QT 4.4.3 builds yet, but I've been running a 4.4.2 build for many months and it resumes fine, and (unlike 2008.X) resumes quickly enough that I can actually answer my calls. I did see some discussion on the list about kernel logging levels impacting the speed of resume - I'm not sure that it impacts whether the resume happens at all. Good luck. Warren On Mon, Mar 16, 2009 at 12:53 PM, Ian wrote: > This is the same issue that made me dismiss Qtopia earlier on but > frustrated with every other available distro I decided to see if it > had been solved yet: QT Extended won't resume from suspend on an > incoming call (possibly SMS as well), it will only respond to the > event if it is already on. If it was suspended it believes that it is > receiving the event when it is later turned on, likely well after the > event. > > Is this why the default setting is not to suspend? > > Is there another power saving work around (such as replacing the lock > program with something that forces the display to remain off until a > physical button is pressed, a call received or so forth)? > > I haven't tested it extensively yet (freshly flashed... again), but > how are other users dealing with the lack of decent power management > (carry a second battery, charger or USB cable?), or am I missing > something obvious? > > Cheers, > -I > > -- > http://darkstarshout.blogspot.com/ > -- > On the day *I* go to work for Microsoft, faint oinking sounds will be > heard from far overhead, the moon will not merely turn blue but > develop polkadots, and hell will freeze over so solid the brimstone > will go superconductive. > -- Erik Raymond, 2005 > -- > Please avoid sending me Word or PowerPoint attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > > ___ > 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
[shr-testing] GPRS: opkg update stalls on "armv4t/Packages.gz"
Hi.
Got a weird situation here.
When doing "opkg update" using a GPRS connection, the download of
http://build.shr-project.org/shr-testing/ipk/armv4t/Packages.gz always
gets stalled and eventually fails by timeout.
When I try a "wget" of the same file, I can see it stalling at 45568
bytes. If I relaunch it (with -c to continue the same download), it
resumes ok and then stalls again at 90112 bytes. Same thing at 141 kB,
183 kB, 227 kB, and 273 kB, and finishes correctly at 301 kB.
So, it is stalling consistently at every (approximate) 45 kB interval.
When I try wgetting a different large file, like for example
http://www.raulx64.com/wp-content/uploads/2008/04/i_am_blue_1280x1024_wallpaper.jpg,
it also stalls at approximately every 85 kB {48640, 136 kB, 235 kB, 319 kB,
399 kB}, but only for a few seconds each time, and downloads successfully in a
single run (503
kB).
How can I debug this?
Why is it stalling?
How can I change the default timeout (busybox's wget doesn't allow
timeout or retry parameters...)
Thanks,
Vasco.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: GSM Power Control
> The phone's actual transmitted power level does change - I tested this > in the past while looking at the "gsm buzz" problem: > > http://lists.openmoko.org/pipermail/support/2008-August/001121.html What about the Freerunner? -- > > Message: 1 > Date: Sat, 21 Mar 2009 08:16:56 -0400 > From: "Joel B. Land" > Subject: GSM Power Control > To: support@lists.openmoko.org > Message-ID: ><2f93132e0903210516x301e6c71g9d8ae8deaa818...@mail.gmail.com> > Content-Type: text/plain; charset="windows-1252" > > Hi, > > > > Is the phone?s GSM modem doing power control? > > > > ?.was playing around with the AT commands and wondering why the following > never changes: > > > > Serving Cell Information (2,1) > > Parameter no. Name Meaning > > 8 txlev Transmit Power Level > > > > I can change the received field strength (rxlvl) by moving in and outside, > but not the txlvl. > > > > This because the power is always the same? Anyone know what the values > mean? > > > > Thanks in advance! > > -- > > Message: 2 > Date: Sat, 21 Mar 2009 13:29:35 +0100 > From: "Michael 'Mickey' Lauer" > Subject: Re: GSM Power Control > To: Support for Openmoko Device Owners > Message-ID: <200903211329.36092.mic...@vanille-media.de> > Content-Type: text/plain; charset="utf-8" > > On Saturday 21 March 2009 13:16:56 Joel B. Land wrote: > > Serving Cell Information (2,1) > > > > Parameter no. Name Meaning > > > > 8 txlev Transmit Power Level > > Isn't this referring to the cell's power level rather than to the phone's? > > :M: > > > > -- > > Message: 3 > Date: Sat, 21 Mar 2009 09:11:55 -0700 > From: Mike Montour > Subject: Re: GSM Power Control > To: support@lists.openmoko.org > Message-ID: > Content-Type: text/plain; charset=windows-1252; format=flowed > > Joel B. Land wrote: > > Is the phone?s GSM modem doing power control? > > [...] > > I can change the received field strength (rxlvl) by moving in and > > outside, but not the txlvl. > > This because the power is always the same? > > The phone's actual transmitted power level does change - I tested this > in the past while looking at the "gsm buzz" problem: > > http://lists.openmoko.org/pipermail/support/2008-August/001121.html > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
