Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #1662: [GSM] not working properly after x
hours of usage (Openmoko Public Trac)
2. Re: Openmoko Bug #2029: Class 0 SMS wrongly decoded (no
UTF-8?) (Openmoko Public Trac)
3. Re: Openmoko Bug #1950: [Installer] system update packages
(Openmoko Public Trac)
4. Re: Openmoko Bug #2029: Class 0 SMS wrongly decoded (no
UTF-8?) (Openmoko Public Trac)
5. Re: Openmoko Bug #666: 3G SIM capability (Openmoko Public Trac)
6. Re: Openmoko Bug #1381: clicking at touchscreen borders
confuses libSDL's mouse cursor (Openmoko Public Trac)
7. Openmoko Bug #2033: FTBFS opkg on gcc-4.3.2 (patch
available) (Openmoko Public Trac)
8. Re: Openmoko Bug #80: wakeup reason not in /proc/cmdline
(Openmoko Public Trac)
--- Begin Message ---
#1662: [GSM] not working properly after x hours of usage
--------------------------------+-------------------------------------------
Reporter: will | Owner: zecke
Type: defect | Status: new
Priority: highest | Milestone: Om2008.10
Component: System Software | Version:
Severity: blocker | Resolution:
Keywords: must have | Blockedby:
Reproducible: | Blocking:
--------------------------------+-------------------------------------------
Comment(by erin_yueh):
Replying to [comment:13 dolfje]:
> You had my word for getting a logread asap, well here it comes.
>
> My distro is now Om2008.9 (updated).
>
> '''My fairy? tale:'''
> After 7 hours that my gsm was up and running, it cannot get phone calls
reliable. I phoned it (After I had put my phone out of suspend, 15 minutes
before) 9 times. 7 times I get immediately the voice mail. 1 time I get
the normal tone but my phone doesn't ring. 1 time it rings as it should
be. This all when I look at the status icon and see a network connectivity
of 4 blocks.
>
> ps: I haven't had any problems with getting sms' and sending sms'.
thanks for providing your log! From this log, it can tell you were
connected with your network 'BEL PROXIMUS', received 2 phone calls,
received 1 SMS, have 26 SIM SMS messages, and delete one SMS message. I
cannot know why you got the voice mail from this log. It would depends on
the local network traffic and need trace protocol layer. If your network
never reached you on those 7 calls, we cannot see from the log. This log
is stored the information between GSM modem and your application.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1662#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2029: Class 0 SMS wrongly decoded (no UTF-8?)
------------------------+---------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by erin_yueh):
Replying to [comment:4 vnevoa]:
> Ok, I've added the logread.
> My reproduction of the problem starts at line 566.
> Steps taken:
> 1 - compose and send an SMS message to myself (body has "test");
> 2 - receive the class 0 SMS with the pre-paid account's current sale;
> 3 - receive the normal SMS I wrote to myself (say NO to qtopia's
question).
> Anything else?
from this log:
you receive a SMS and stored it to SIM card index 16.
Sep 23 23:30:22 om-gta02 user.notice root: AtChat : N : "+CMTI: "SM",16"
what is this SMS?
Sep 23 23:30:24 om-gta02 user.notice root: AtChat : F : "+CMGL: 16,0,,24"
621 Sep 23 23:30:24 om-gta02 user.notice root: AtChat : F :
"07915391131213F4040C9153914352823500008090323223154005F4F29C0E02"
07 91 5391131213F4 04 0C 91 539143528235 0000 80903232231540 05 F4F29C0E02
'0000' those numbers means TP-PID and TP-DCS. The special case of bits
7..0 being 0000 0000 indicates the Default Alphabet as in Phase 2.
the message text are encoded by GSM Alphabet, not UCS2.
you can read SMS format by this site:
http://www.dreamfabric.com/sms/
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2029#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1950: [Installer] system update packages
----------------------------------+-----------------------------------------
Reporter: wendy_hung | Owner: tick
Type: enhancement | Status: closed
Priority: normal | Milestone: Om2008.10
Component: Distro | Version:
Severity: major | Resolution: fixed
Keywords: Updating Packages | Blockedby:
Reproducible: | Blocking:
----------------------------------+-----------------------------------------
Changes (by tick):
* status: in_testing => closed
* resolution: => fixed
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1950#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2029: Class 0 SMS wrongly decoded (no UTF-8?)
------------------------+---------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by vnevoa):
Erin, I have no idea if you are making a statement or asking a question...
I also don't know how to interpret the log file. If I knew, I would have
debugged the problem myself and provided better info.
If you need more info or clarifications, please ask in a clearer way.
Thanks!
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2029#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#666: 3G SIM capability
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: michael
Type: defect | Status: new
Priority: highest | Milestone:
Component: GSM Modem | Version: unspecified
Severity: critical | Resolution:
Keywords: SIM att 7300g 71234 4022 | Blockedby:
Blocking: |
----------------------------------------+-----------------------------------
Comment(by jwo):
Same Problem with my new 3G SIM from O2. My old T-Online SIM works fine.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/666#comment:74>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1381: clicking at touchscreen borders confuses libSDL's mouse cursor
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: sean_chiang
Type: defect | Status: assigned
Priority: high | Milestone:
Component: Screen | Version: unspecified
Severity: normal | Resolution:
Keywords: | Blockedby:
Blocking: |
---------------------------------+------------------------------------------
Comment(by thebohemian):
I just found out that this problem is most likey *not* OpenMoko specific.
I assume it is not a hardware or touchscreen driver issue.
The reason for my assumption is that I installed the OpenEmbeded-based
Mamona distribution on my N770. Apart from a patched xorg-kdrive (omap
support) it uses the same version libsdl as OpenMoko and (surprise!) shows
the same issue.
Perhaps things will be better if we could get libsdl 1.2.13 with all the
patches Debian applies. Who knows. :)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1381#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2033: FTBFS opkg on gcc-4.3.2 (patch available)
--------------------+-------------------------------------------------------
Reporter: rzr | Owner: tick
Type: defect | Status: new
Priority: lowest | Milestone:
Component: opkg | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible: always
Blocking: |
--------------------+-------------------------------------------------------
While building a debian package of opkg
I had to change a few lines in the source code, see patch attached :
http://rzr.online.fr/docs/contribs/patches/opkg-0.0.20080924rzr1.diff
I also fixed some typos and added a basic CONTROL/control in tree
opkg-0.0.20080924/CONTROL/control | 10 ++++++++++
opkg-0.0.20080924/TODO | 3 +++
opkg-0.0.20080924/libopkg/libopkg.c | 4 ++--
opkg-0.0.20080924/libopkg/opkg.c | 2 +-
opkg-0.0.20080924/libopkg/opkg_cmd.c | 4 ++--
opkg-0.0.20080924/libopkg/pkg.c | 3 ++-
6 files changed, 20 insertions(+), 6 deletions(-)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2033>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#80: wakeup reason not in /proc/cmdline
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: reopened
Priority: high | Milestone:
Component: System Software | Version: current svn head
Severity: major | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
-------------------------------------+--------------------------------------
Changes (by mickey):
* status: closed => reopened
* resolution: fixed =>
Comment:
The subreason for * EINT09_PMU is no longer starred. Tried with waking up
by button press as well as waking up by RTC. Tested kernel was
http://downloads.openmoko.org/framework/milestone3/uImage-2.6.24+r5+gitr1+ca19d156400f817960efe0d14680324b2ea34171-r5
-om-gta02.bin, U-Boot is fairly recent.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/80#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
