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 #2211: Windows instant reboot while
      connecting        Freerunner on USB (Openmoko Public Trac)
   2. Re: Openmoko Bug #2235: Monochrome display on resume
      (Openmoko Public Trac)
   3. Re: Openmoko Bug #2049: Illume dynamic dictionary has some
      problems... (Openmoko Public Trac)
   4. Openmoko Bug #2241: GSM "deregistring" after registring
      (Openmoko Public Trac)
   5. Re: Openmoko Bug #2241: GSM "deregistring" after registring
      (Openmoko Public Trac)
--- Begin Message ---
#2211: Windows instant reboot while connecting Freerunner on USB
-----------------------------+----------------------------------------------
 Reporter:  psonek           |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                 
Component:  System Software  |        Version:  unspecified    
 Severity:  normal           |       Keywords:                 
 Haspatch:  0                |      Blockedby:                 
Estimated:                   |    Patchreview:                 
 Blocking:                   |   Reproducible:                 
-----------------------------+----------------------------------------------

Comment(by vnevoa):

 I think this is probably a duplicate of #1279, which has a patch and was
 closed successfuly.

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

--- End Message ---
--- Begin Message ---
#2235: Monochrome display on resume
-----------------------------+----------------------------------------------
 Reporter:  zeroedout        |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                 
Component:  System Software  |        Version:                 
 Severity:  normal           |       Keywords:  display, resume
 Haspatch:  0                |      Blockedby:                 
Estimated:                   |    Patchreview:                 
 Blocking:                   |   Reproducible:                 
-----------------------------+----------------------------------------------

Comment(by nicolas.dufresne):

 It's going to look like I only know one single driver in the Kernel, but I
 think jbt driver is again to blaim.

 In 2.6.24 we've have worked around a sticky WSOD by not bringing the LCM
 into deep standby (only bring it to sleep). This work around has worked
 nicely so far, but in 2.6.29 it's different. We do have the workaround,
 meaning that on suspend we go to sleep (and not deep standby), but on
 resume we hard reset the line (the new) and travel through every
 initialisation.

 With locking still terribly weak in this driver, I'm not really surprise
 resume works only once on two tries (that's what I'm getting).

 I'm doing some testing with better locking. I'll try both using deap
 standby and sleep (removing the reset when only going to sleep state). I
 should have more input this weekend. Also, it would be nice to review the
 locking in other graphic components.

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

--- End Message ---
--- Begin Message ---
#2049: Illume dynamic dictionary has some problems...
----------------------------+-----------------------------------------------
    Reporter:  Treviño      |       Owner:  raster
        Type:  enhancement  |      Status:  new   
    Priority:  normal       |   Milestone:        
   Component:  E - Illume   |     Version:        
    Severity:  normal       |    Keywords:        
   Blockedby:               |    Blocking:        
Reproducible:               |  
----------------------------+-----------------------------------------------

Comment(by lysgaard):

 Another problem: If your dictionary have a word with capital letter, let's
 say "Hello", it won't add the lower case version to the dictionary when
 you enter it "hello"
 This is really irritating because if you're unlucky, like me, some of your
 most used words are only in the dictionary with capital letter, so you
 have to type them perfectrly, press the "up-arrow" and select the word.
 This is because it's not in the dictionary, even though I've typed it a
 thousand times.
 NOTE: If you enter the lover case version of the word first: "hello", then
 the capital one "Hello" is added to the dictionary.

 I've looked at the source, but it was a bit to complex for me beginning to
 mess with it, but i think the problem lies in the word normalization,
 before dictionary lookup.

 One fix would be to just fix this, but i suppose that the dictionary
 should be case-agnostic.
 So when you want to enter a word with a capital letter, you have to
 explicitly press te shift button.

 I would also propose that you can touch a word in the buffer area, and do
 an upstroke gesture to make the firs letter in the word upper case.
 Example: you write "david" all in lower case, then instead of just tapping
 it, you press it and do an up-stroke, just like when changing keyboard.
 This would be intepreted as "I want the first letter capital" and the
 input would be "David"

 If you want to write a word with abnormal chasing, like "aBnOrMaL" you
 would have to use the "shift" button to specify the capital letters, but
 not when you just want the first letter capital, then you could use the
 up-stroke gesture.

 *Firstly this greatly reduces the entries in the dictionary, which again
 leads to better performance.
 *It removes duplicate words like "Hello" and "hello" in the buffer.
 *I believe it would add even more usability to FSO/openmoko's absolutly
 best application.

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

--- End Message ---
--- Begin Message ---
#2241: GSM "deregistring" after registring
---------------------+------------------------------------------------------
 Reporter:  keroami  |          Owner:  openmoko-devel
     Type:  defect   |         Status:  new           
 Priority:  normal   |      Milestone:  FSO           
Component:  unknown  |        Version:  unspecified   
 Severity:  normal   |       Keywords:                
 Haspatch:  0        |      Blockedby:                
Estimated:           |    Patchreview:                
 Blocking:           |   Reproducible:                
---------------------+------------------------------------------------------
 gta01
 UMTS capable SIM, Dutch KPN, got it last autumn.
 upgraded firmware to moko11
 FSO milestone 5.1

 Zhone, starts fine, detects SIM, asks for PIN, delivers it, gets
 registered and then after a varying amount of time, claims to be
 deregistered. The Neo can still receive calls. The bottom-left
 icon/program still lists an active cell and show changing activity for all
 cells it can detect. I can even make a call from the command line.

 switched on logging, found the following:
 2009.02.24 19:50:15 ogsmd.channel DEBUG    <MiscChannel via /dev/pts/0>:
 COMPLETED 'AT+COPS=3,0;+COPS?;+COPS=3,2;+COPS?' => ['+COPS: 0,0,"NL KPN
 "', '+COPS: 0,2,"20408"', 'OK']
 2009.02.24 19:50:15 ogsmd.channel DEBUG    <MiscChannel via /dev/pts/0>:
 COMPLETED 'AT+COPS=3,0;+COPS?;+COPS=3,2;+COPS?' => ['+COPS: 0', '+COPS:
 0,2,"20408"', 'OK']

 and as otimed says, there's no network code in there. As a consequence,
 Zhone claims the SIM deregistered and disables the phone icon.

 This can happen (as in the example) virtually immediately, or any amount
 of actions later. call, answer, look at cell(s), do another call and oops-
 there's the COPS result. Whenever the phone icon gets disabled, there is
 the COPS result without provider; and there's no other COPS result without
 it earlier in the logfile. Later results of the COPS command do not have
 the provider, either. Restarting X+Zhone seems no different from rebooting
 the Neo.

 firmware bug or zhone bug?

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

--- End Message ---
--- Begin Message ---
#2241: GSM "deregistring" after registring
---------------------+------------------------------------------------------
 Reporter:  keroami  |          Owner:  mickey     
     Type:  defect   |         Status:  assigned   
 Priority:  normal   |      Milestone:  FSO        
Component:  unknown  |        Version:  unspecified
 Severity:  normal   |       Keywords:             
 Haspatch:  0        |      Blockedby:             
Estimated:           |    Patchreview:             
 Blocking:           |   Reproducible:             
---------------------+------------------------------------------------------
Changes (by Nytowl):

 * cc: wer...@… (added)
  * owner:  openmoko-devel => mickey
  * status:  new => assigned


-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2241#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