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. Openmoko Bug #1803: Installer reports all package Download
      size as   0 bytes (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 #1804: Menu items falsely activated during
      scrolling (Openmoko Public Trac)
   4. Re: Openmoko Bug #1803: Installer reports all package
      Download size     as 0 bytes (Openmoko Public Trac)
   5. Re: Openmoko Bug #1804: Menu items falsely activated during
      scrolling (Openmoko Public Trac)
   6. Re: Openmoko Bug #1670: Battery life too short; phone should
      sleep (Openmoko Public Trac)
   7. Re: Openmoko Bug #1722: [GSM] taking signal is too slow
      (Openmoko Public Trac)
   8. Re: Openmoko Bug #1754: screen locker killed forever by aux
      button (Openmoko Public Trac)
--- Begin Message ---
#1803: Installer reports all package Download size as 0 bytes
-----------------------+----------------------------------------------------
 Reporter:  peepsalot  |       Owner:  tick                     
     Type:  defect     |      Status:  new                      
 Priority:  normal     |   Milestone:  Om2008.8                 
Component:  Assassin   |     Version:  OM-2008.08               
 Severity:  blocker    |    Keywords:  installer, assassin, size
 Blocking:             |   Blockedby:                           
-----------------------+----------------------------------------------------
 When viewing packages in the installer, they all appear to show a Download
 size of 0 Bytes.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1803>
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:  closed        
 Priority:  highest    |    Milestone:  Om2008.8      
Component:  Qtopia     |      Version:  GTA02v5       
 Severity:  critical   |   Resolution:  worksforme    
 Keywords:             |     Blocking:                
Blockedby:             |  
-----------------------+----------------------------------------------------

Comment(by apm):

 Replying to [comment:34 zecke]:
 > Okay. This is getting way too chaotic and not manageable at all. I have
 no other option than to close the bug, as we at least have two different
 issues.
 >
 > @Peetrus and others: You run gsmd and qpe. This is not going to work.
 Deinstall gsmd or qtopia...

 This has got to be a joke, right?
 I mean... here we are, trying to help you debug a real problem and you
 just plainly states that you don't care because we're running unsupported
 software (gsmd), WHICH WE ARE NOT!

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1765#comment:35>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1804: Menu items falsely activated during scrolling
------------------------+---------------------------------------------------
 Reporter:  peepsalot   |       Owner:  raster    
     Type:  defect      |      Status:  new       
 Priority:  normal      |   Milestone:            
Component:  E - Illume  |     Version:  OM-2008.08
 Severity:  normal      |    Keywords:            
 Blocking:              |   Blockedby:            
------------------------+---------------------------------------------------
 If you tap and drag a menu item, the menu scrolls as expected, but when
 released the menu item is sometimes activated.  If the user is moving the
 menu significantly during a stroke, it should be assumed they are not
 trying to activate a menu item.

 Note, this seems to only happen if you do not scroll past either end of
 the menu.(causing the stylus to move away from the initial menu item that
 the drag began on).
 I noticed this mostly in the Settings menu, since it seems to currently be
 the longest menu(good for ample scrolling testing space).

 I think the absolute value of the each menu movement should be
 accumulated, and if the total is past some small threshold(5px maybe?).

 Examples test cases that should *not* activate menu item:
 User scrolls 50 pixels down, not reaching the bottom
 User scrolls 50 pixels up and 50 pixels down during a single drag.  (net
 movement 0, but accumulated absolute value of movement = 100)

 Example cases that *should* activate menu item:
 User taps and does not scroll at all before releasing
 User "scrolls" 1-5 pixels up or down (accidental slide during menu
 selection)

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1804>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1803: Installer reports all package Download size as 0 bytes
---------------------------------------+------------------------------------
 Reporter:  peepsalot                  |        Owner:  tick      
     Type:  defect                     |       Status:  new       
 Priority:  normal                     |    Milestone:  Om2008.8  
Component:  Assassin                   |      Version:  OM-2008.08
 Severity:  blocker                    |   Resolution:            
 Keywords:  installer, assassin, size  |     Blocking:            
Blockedby:                             |  
---------------------------------------+------------------------------------
Changes (by tick):

 * cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
 (added)


Comment:

 Hi Greame,
   Since we switch to opkg-util, it's seem the size tag disappear again.
 Would you please patch that again on the SVN.

 http://svn.openmoko.org/trunk/src/host/opkg-utils/

 Thanks,
 Tick

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1803#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1804: Menu items falsely activated during scrolling
-------------------------+--------------------------------------------------
 Reporter:  peepsalot    |        Owner:  raster    
     Type:  enhancement  |       Status:  closed    
 Priority:  lowest       |    Milestone:            
Component:  E - Illume   |      Version:  OM-2008.08
 Severity:  trivial      |   Resolution:  invalid   
 Keywords:               |     Blocking:            
Blockedby:               |  
-------------------------+--------------------------------------------------
Changes (by raster):

  * priority:  normal => lowest
  * status:  new => closed
  * resolution:  => invalid
  * severity:  normal => trivial
  * type:  defect => enhancement


Comment:

 the code HAS got code to detect "drag vs click". there is a simple
 threshold value - it just happens to be too low for your comfort. for mine
 i can say it is just fine. this code does exist - otherwise it would
 ALWAYS activate. it is ONLY a user preference. there is in fact a settings
 dialog for swizzling just that under finger scrolling. unfortunately for
 you it's at the maximum setting the gui allows, it's a simple matter of
 adding even more levels, but really - this isn't a defect or a bug. it is
 simply user preference. i think the default right now 24 pixels. there is
 a dialog in e to change this - but that dialog is disabled.

 so as such - this isn't a matter for enhancement, any code changes or a
 bug.. it's simply user preference, and design decisions not to expose such
 config to the user (at which point i can't own such a bug as i don't make
 design decisions). if you wish to refile this as something else... go
 ahead. :) (just need to clarify what this is, and that it's not really a
 bug or an enhancement requirement as it's all already there - it's a
 config preference by design in ASU not exported to the user).

 hope this helps. :)

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1804#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1670: Battery life too short; phone should sleep
-----------------------------+----------------------------------------------
 Reporter:  kenrestivo       |        Owner:  openmoko-kernel
     Type:  enhancement      |       Status:  new            
 Priority:  normal           |    Milestone:                 
Component:  System Software  |      Version:                 
 Severity:  normal           |   Resolution:                 
 Keywords:                   |     Blocking:                 
Blockedby:                   |  
-----------------------------+----------------------------------------------
Changes (by RuiSeabra):

  * owner:  openmoko-devel => openmoko-kernel
  * component:  unknown => System Software


Comment:

 '''Unmeasured improvement: dim back-light to zero a little sooner than
 600s'''

 Add to {{{/etc/matchbox/session}}}, somewhere in the beginning:

 {{{
 # dim back-light sooner than default, 15s instead of 600s of idle
 xset s 15 &
 }}}

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1670#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1722: [GSM] taking signal is too slow
-----------------------------+----------------------------------------------
 Reporter:  wendy_hung       |        Owner:  zecke   
     Type:  defect           |       Status:  new     
 Priority:  highest          |    Milestone:  Om2008.8
Component:  System Software  |      Version:          
 Severity:  blocker          |   Resolution:          
 Keywords:                   |     Blocking:          
Blockedby:                   |  
-----------------------------+----------------------------------------------

Comment(by apm):

 This seems to be related to #1765.
 Symptoms and delays might vary and the PIN-dialog may not come up.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1722#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1754: screen locker killed forever by aux button
----------------------+-----------------------------------------------------
 Reporter:  olberger  |        Owner:  openmoko-devel
     Type:  defect    |       Status:  new           
 Priority:  normal    |    Milestone:  Om2007.2      
Component:  unknown   |      Version:  GTA02v5       
 Severity:  normal    |   Resolution:                
 Keywords:            |     Blocking:                
Blockedby:            |  
----------------------+-----------------------------------------------------

Comment(by RuiSeabra):

 The Aux button may not be the culprit, since I have triggered this problem
 more than one without pressing it.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1754#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to