Re: Fwd: No more optimization team
100% ACK Am Di 16. Dezember 2008 schrieb Werner Almesberger: > Joerg Reisenweber wrote: > > Are you living in an area where many people use their cellphone, but only few > > BS around? We have some cloudy theory this might be a trigger for #1024. > > Perhaps it would be good to collect some more specific reports of the > kind of settings ? > > This seems to be a bit similar to the WLAN problems that eventually > turned out to be linked to having multiple access points, but the > picture remained vague until we had a large enough number of fairly > detailed usage stories. > > With GSM, things are more complex, because it's harder to know what > the network is like. But getting a first overview may help to find the > next, more specific questions to ask, etc. > > - Werner > signature.asc Description: This is a digitally signed message part. ___ hardware mailing list hardware@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/hardware
Re: Fwd: No more optimization team
Thanks for the report! Helps a lot. reselecting cells isn't an error or unusual behaviour. In fact that's what the phone is supposed to do, as long as it's two BTS with same signal-level, and the phone doesn't *transmit* every time to re-associate to the network Please see Wolfgang's mail about NDA. Cable probably needs another pinout for the 2.5mm jack, if anything. cheers jOERG Am Di 16. Dezember 2008 schrieb Al Johnson: > On Monday 15 December 2008, Joerg Reisenweber wrote: > > Are you living in an area where many people use their cellphone, but only > > few BS around? We have some cloudy theory this might be a trigger for > > #1024. A very good indication would be #1024 showing up on certain daytime > > while never seen at deep in the night. Another indicator for a situation > > matching our "crowded-BS"-theory is an occasional failure of non-FR > > cellphones to connect an outbound call (unusual "busy" on dialing out, or > > just nothing happens when you push green button), so you would have to > > retry until a resource (channel) is free at BS. > > That doesn't fit my experience of #1024. I get intermittent reregistration > problems with Orange, t-mobile and O2 in the UK, although it has the t-mobile > SIM in most of the time. The O2 SIM has only been working since moko10 was > released, and I haven't done much with it. There is no pattern to the day, or > the time of day, that I have spotted. I have never had the trouble you > describe when making calls. The reregistrations can be regular every ~20 > seconds, or irregularly at larger intervals. The regular reregistrations > trigger the detection in ogsmd, but the irregular ones do not occur > frequently enough to trigger it. > > IIRC I have good signal strength from at least 3 cells, of which the stronger > two have similar signal strength. The phone often moves seamlessly between > these two, occasionally switching to the third. I have only looked at this in > detail once and I don't remember if it was Orange or t-mobile. > > I am happy to record some logs if you can make PCO2 available to me, and could > solder up the required cable if given the pinouts. If I'm lucky it'll be the > same as for the Neuros OSD cable that's around here somewhere. > > ___ > hardware mailing list > hardware@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/hardware > signature.asc Description: This is a digitally signed message part. ___ hardware mailing list hardware@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/hardware
Re: Fwd: No more optimization team
Joerg Reisenweber wrote: > Are you living in an area where many people use their cellphone, but only few > BS around? We have some cloudy theory this might be a trigger for #1024. Perhaps it would be good to collect some more specific reports of the kind of settings ? This seems to be a bit similar to the WLAN problems that eventually turned out to be linked to having multiple access points, but the picture remained vague until we had a large enough number of fairly detailed usage stories. With GSM, things are more complex, because it's harder to know what the network is like. But getting a first overview may help to find the next, more specific questions to ask, etc. - Werner ___ hardware mailing list hardware@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/hardware
Re: Fwd: No more optimization team
On Monday 15 December 2008, Joerg Reisenweber wrote: > Are you living in an area where many people use their cellphone, but only > few BS around? We have some cloudy theory this might be a trigger for > #1024. A very good indication would be #1024 showing up on certain daytime > while never seen at deep in the night. Another indicator for a situation > matching our "crowded-BS"-theory is an occasional failure of non-FR > cellphones to connect an outbound call (unusual "busy" on dialing out, or > just nothing happens when you push green button), so you would have to > retry until a resource (channel) is free at BS. That doesn't fit my experience of #1024. I get intermittent reregistration problems with Orange, t-mobile and O2 in the UK, although it has the t-mobile SIM in most of the time. The O2 SIM has only been working since moko10 was released, and I haven't done much with it. There is no pattern to the day, or the time of day, that I have spotted. I have never had the trouble you describe when making calls. The reregistrations can be regular every ~20 seconds, or irregularly at larger intervals. The regular reregistrations trigger the detection in ogsmd, but the irregular ones do not occur frequently enough to trigger it. IIRC I have good signal strength from at least 3 cells, of which the stronger two have similar signal strength. The phone often moves seamlessly between these two, occasionally switching to the third. I have only looked at this in detail once and I don't remember if it was Orange or t-mobile. I am happy to record some logs if you can make PCO2 available to me, and could solder up the required cable if given the pinouts. If I'm lucky it'll be the same as for the Neuros OSD cable that's around here somewhere. ___ hardware mailing list hardware@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/hardware
Re: Fwd: No more optimization team
[ added [hw], TO->BCC'd Clare to protect email address] Hi Clare thanks for your kind offer to help. Am Mo 15. Dezember 2008 schrieb clare johnstone: > Hi Dieter, > > Sorry, I cannot read the link, it requires a username and password. > AND I have no cable, AND the only cables I have so far found for sale are > Bluetooth headsets with USB charge cables and would cost me as much > as the freight (postage) on my phone to Dieter and back, and that would > probably get a result MUCH quicker. Unfortunately once again CanNotDup here isn't a matter of not having a device with this issue (all FR are same FW), but CND is caused by the fact we see a different GSM-provider/network situation here than you do in your place. So either you should send your GSM-basestation you are registering with ;-D, or Dieter had to come to visit you and your GSM-BS. Are you living in an area where many people use their cellphone, but only few BS around? We have some cloudy theory this might be a trigger for #1024. A very good indication would be #1024 showing up on certain daytime while never seen at deep in the night. Another indicator for a situation matching our "crowded-BS"-theory is an occasional failure of non-FR cellphones to connect an outbound call (unusual "busy" on dialing out, or just nothing happens when you push green button), so you would have to retry until a resource (channel) is free at BS. cheers jOERG > The phone still shows the behaviour, > the version of QTOPIA with workaound is quite different from the > version without. > regards, > clare > > On Mon, Dec 15, 2008 at 1:14 PM, Dieter Spaar wrote: > > Hello Wolfgang, > > > >> can you reply to clare and see whether he can help you? > >i > > The only thing which would currently give some more insight regarding > > bug #1024 is a PCO2 trace of this bug, with and without the AT%SLEEP > > workaround. > > > > PCO2 is a non-public TI tool and I don't know if Clare can receive it. The > > tool and the instructions are in the internal SVN, the instructions are > > here: > > > > https://svn.internal.openmoko.org/trunk/calypso/pco2/PCO2-on-Wine > > > > Additional a headset to RS232 or Headset to USB cable is required. > > > > Unfortunately the PCO2 traces from Stefan don't show bug #1024 but > > most certainly are normal cell re-selection behavior. The other one from > > OM who can reproduce #1024 is Mickey, however he has no cable yet. > > > > Best regards, > > Dieter > > > > > > > signature.asc Description: This is a digitally signed message part. ___ hardware mailing list hardware@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/hardware
