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 #1765: No pin-dialog appears after boot, so
no gsm is working in 2008.8 (Openmoko Public Trac)
2. Re: Openmoko Bug #1765: No pin-dialog appears after boot, so
no gsm is working in 2008.8 (Openmoko Public Trac)
3. Openmoko Bug #1788: Maps - Please do not store offline data
in /tmp (Openmoko Public Trac)
4. Openmoko Bug #1789: 2008.8 screen blanks and refuses to
wakeup (Openmoko Public Trac)
5. Openmoko Bug #1790: Om2008.8 Cannot make or receive calls
(Openmoko Public Trac)
6. Openmoko Bug #1791: Exit application - suggestion
(Openmoko Public Trac)
7. Re: Openmoko Bug #1790: Om2008.8 Cannot make or receive calls
(Openmoko Public Trac)
8. Openmoko Bug #1792: SMS not received properly during suspend
(Openmoko Public Trac)
--- Begin Message ---
#1765: No pin-dialog appears after boot, so no gsm is working in 2008.8
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone: OM-2008.8
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------+----------------------------------------------------
Comment(by Rorschach):
No, removing the SD-Card changes nothing for me. I tested again FSO2 and
2007 and with both images I can give in my pin and use GSM but with 2008.8
I can't.
So as already pointed out this bug is not related to the 3G bug. Any help
on figuring this bug out would be nice.
I'm still waiting for any information about what the binary which asks for
the pin is called and which process starts the dialog.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1765#comment:25>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1765: No pin-dialog appears after boot, so no gsm is working in 2008.8
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone: OM-2008.8
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------+----------------------------------------------------
Comment(by thepizzaking):
I couldn't manage to get the PIN input dialog up at all (not even by
restarting the XServer), but I removed the SD Card and then the PIN came
up about 30 seconds after booting, though, after I entered my PIN I
couldn't receive or make any calls.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1765#comment:24>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1788: Maps - Please do not store offline data in /tmp
-------------------------+--------------------------------------------------
Reporter: Sjors | Owner: marek
Type: enhancement | Status: new
Priority: normal | Milestone: OM-2008.8
Component: Diversity | Version: OM-2008.08
Severity: normal | Keywords: maps offline
Blocking: | Blockedby:
-------------------------+--------------------------------------------------
I have scrolled around the map in Locations [0] to download some map data
of places I plan to go to. That way I can use the map when I am offline.
However, the data is stored in /tmp/diversity-maps/osm which gets deleted
upon reboot.
Temporary workaround: tar all tiles and move them to a save place, copy
them back after reboot.
Proposed solution: store files in a permanent location.
If the tiles are stored in a permanent location, then the Locations
application should probably have a preference menu where you can allocate
a maximum number of megabytes.
[0]http://wiki.openmoko.org/wiki/Om2008.8_Locations
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1788>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1789: 2008.8 screen blanks and refuses to wakeup
---------------------+------------------------------------------------------
Reporter: billk | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone: OM-2008.8
Component: unknown | Version: OM-2008.08
Severity: major | Keywords: wakeup screen display sleep suspend
Blocking: | Blockedby:
---------------------+------------------------------------------------------
I have had the FR go into blank screen a number of times and refuse to
wakeup. Its not suspended as usb networking still works. Trying to
restart the xserver hangs. If I press the power button briefly, nothing
happens. Same if I hold it for a second or two. At ~ 10 seconds it will
shutdown - sometimes.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1789>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1790: Om2008.8 Cannot make or receive calls
-----------------------+----------------------------------------------------
Reporter: sonicated | Owner: tick
Type: defect | Status: new
Priority: highest | Milestone:
Component: Assassin | Version:
Severity: blocker | Keywords:
Blocking: | Blockedby:
-----------------------+----------------------------------------------------
rootfs: Om2008.8-gta02-20080808.rootfs.jffs2
kernel: Om2008.8-gta02-20080808.uImage.bin
Using the released Om-2008.8 image I cannot make or receive phone
calls. When the phone boots I am asked to enter a PIN. This appears
to be accepted and I can send and receive SMS messages.
However when I try and make a call it fails with the message "No
phone call is possible. Reason GSM Phone is not registered. No
network". No connection information is displayed on the bar at the
top. I could make and receive calls with 2007.2 and I am in an area
with a full GSM signal.
This has been verified on the mailing list
(http://lists.openmoko.org/pipermail/support/2008-August/001455.html).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1790>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1791: Exit application - suggestion
-------------------------+--------------------------------------------------
Reporter: mattt | Owner: marek
Type: enhancement | Status: new
Priority: normal | Milestone: OM-2008.8
Component: Exposure | Version: OM-2008.08
Severity: normal | Keywords: gui menu
Blocking: | Blockedby:
-------------------------+--------------------------------------------------
I'd like to suggest a more intuitive method of exiting an application.
Current method:
- The application needs to be active.
- Activate the main drop down menu.
- Wait for 'REMOVE' to appear (replacing 'qwerty')
- Click 'REMOVE'
- the menu will roll up.
Here's what I don't like about this:
- I have to activate an application to close it
- unnecessary delay
- 'qwerty' changes to 'REMOVE'
- It's confusing, does it relate to the keyboard in any way? no.
- the change to uppercase is overly dramatic
- The word 'remove'
- This is not a normal synonym for terminating an application
Here are my suggestions for improvement
- Change the verb to 'quit' or 'exit' or 'close'
- This is line with normal computer use - more intuitive
- Uppercase letters are not required
- Move the verb label to be horizontally aligned with the application
name
- give clear indication of what is going to happen and what it will
affect
- Move label/icon tot he right hand side of application name
- this is more intuitive
- reduces chances of accidental clicking
- Provide theme capacity for label/icon
- items should be able to be either an icon or label
- Don't close the menu after exiting application
- we do not know what the user wants to do
- user may want to close another
- user may want to choose an open application
I hope accept these the suggestion in the spirit that I give them.
It's an honest and genuine attempt to improve the gui, to create some
consistency, and to encourage intuitive design.
thank you
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1791>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1790: Om2008.8 Cannot make or receive calls
-----------------------+----------------------------------------------------
Reporter: sonicated | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone: OM-2008.8
Component: unknown | Version:
Severity: blocker | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------+----------------------------------------------------
Changes (by sonicated):
* owner: tick => openmoko-devel
* component: Assassin => unknown
* milestone: => OM-2008.8
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1790#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1792: SMS not received properly during suspend
---------------------+------------------------------------------------------
Reporter: thomasb | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Blocking: | Blockedby:
---------------------+------------------------------------------------------
I'm running Om2008.8 on my Freerunner and have problems receiving SMS
messages during suspend. I can reproduce this by suspending my Neo and
sending a test message from another phone. I immediately get a receipt
confirmation on the other phone.
Expected result: Neo should wake up on receiving SMS (or at least show me
the SMS immediately when I wake it up manually)
Actual result: Neo keeps sleeping. After I wake it up manually, no sign of
incoming SMS. Some minutes later, I manually start up the Messages
application, and only now the Neo starts vibrating and the received SMS
shows up.
I'll attach a log file.
To me it looks like the Neo's GSM subsystem receives the message, but
doesn't wake up the phone and instead saves the message into the SIM
card's internal memory. The SMS then only shows up when Qtopia feels like
asking the SIM card for messages the next time (e.g., when starting up the
Messages application).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1792>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
