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 #2019: Headphone Jack Event
(Openmoko Public Trac)
2. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
3. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
4. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
5. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
6. Re: Openmoko Bug #1966: The qtopia addressbook does not
provide a search bar (Openmoko Public Trac)
7. Re: Openmoko Bug #2021: /etc/init.d/dropbear restart doesn't
work (Openmoko Public Trac)
8. Re: Openmoko Bug #2021: /etc/init.d/dropbear restart doesn't
work (Openmoko Public Trac)
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | 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 Zoup):
ok , heres the result :
since im noob , i did tested all Restiance levels of my multimeter , first
row is resistance level , second row is resistance with headphone , third
row is resistance without headphone
Any idea ? :)
200m 00.9 00.9
20m 00.9 00.9
2m 098 097
200k 73.2 74.5
20k,2k,200 0 0
ps :
200m 0.25 ( my right to left hand resistance! )
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:21>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | 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 werner):
The 2M and 200k range look about right. Unfortunately, what it says is bad
news: the switch in your jack never closes :-(
I don't know if there's anything you can do to fix it, and much less if
you
should try any desperate measures, because they may cause other damage.
This
looks like a warranty case, sorry.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:22>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | 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 Zoup):
well , isn't it as simple as simple connection that need to be de-
connected ? :) two surfaces that have been forced into each other or
something like this ? maybe i can reform them ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:23>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | 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 Zoup):
i mean , is this mechanical or electronical issue ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:24>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | 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 werner):
Electromechanical :-) And the problem is that the connection is always
open, though the switch should connect when there is no plug.
Things I could think of:
- a foreign object stuck between the contacts (seems unlikely, since the
device is new and the contacts normally touch, i.e., things can only
creep in while the plug is inserted)
How to fix it: insert a jack and blow compressed air into all openings,
in the hope to dislodge the object.
- contacts oxydated or contaminated with something acting as an insulator.
Again, seems unlikely.
How to fix it: as above, but use contact cleaner.
- some fault in the plastic, causing a protrusion that blocks the contact
How to fix it: dunno. X-ray it, then apply a strong laser pulse to
evaporate the offending plastic ? :-)
- one of the metal parts is not at its correct position and is thus
blocked
by the plastic
How to fix it: try to bend it into its correct position by applying
pressure with a suitable object, e.g., tweezers or a small screwdriver
inserted into the jack's hole.
Or it could be something else. Since most of this involves the application
of force without really knowing what or where the problem is, I would
discourage such attempts, unless you consider the device expendable.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:25>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1966: The qtopia addressbook does not provide a search bar
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: zecke
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Qtopia | Version: Om2008.8
Severity: blocker | Resolution:
Keywords: PM | Blockedby:
Reproducible: | Blocking:
-----------------------------------------+----------------------------------
Comment(by Treviño):
Replying to [comment:13 zecke]:
> Do you know git-add -i? This allows you stage single hunks from a file.
Also it would be cool if you could make a git-commit (with author, email
address) so I can easily apply it with git-am. Currently this involves
using whois to get a name and mail address :)
Ah... I never used commands like git-add in projects where I can't commit
directly with git-push, that's why I didn't used here (I also didn't know
that I could have post here just )
BTW a lot of time ago, I've set my GIT_AUTHOR_* variables (to be used with
git-commit), but the patches I've sent here are stored in a different
PC...
However maybe I'd need to read something more about using git just for
sending patches... :P
Replying to [comment:14 zecke]:
> Clearing HasPatch. I landed patches for the above mentioned issues.
Thanks.
Nice!
BTW, the same feature could be re-enabled also in the CallHistory. I
didn't patch it since I didn't find that so useful, but today (while using
my phone) I missed that feature q bit...
So what about enabling there too? Maybe adding a different configuration
flag, so people could chose.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1966#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2021: /etc/init.d/dropbear restart doesn't work
-------------------------------------------+--------------------------------
Reporter: alih | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version: Om2008.9-dev
Severity: blocker | Resolution:
Keywords: dropbear restart, HasPatch | Blockedby:
Reproducible: | Blocking:
-------------------------------------------+--------------------------------
Comment(by Treviño):
Replying to [comment:2 zecke]:
> Plese see http://wiki.openmoko.org/wiki/Bug_Filing_Policy. Specially
when you have a patch please add HasPatch to the keywords otherwise we
will not see your patch. Trac does not send mails when something is
attached, and there is no way to query for attachments.
Sorry if I'm completely OT with the bug reporting, but I'm replying to the
HasPatch thing: how can we set these tags when putting in a patch after
that a bug has already been reported? I don't see any editable field here
to modify the tags!
I figure it should be added; we, users, have too few permissions in trac!
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2021#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2021: /etc/init.d/dropbear restart doesn't work
-------------------------------------------+--------------------------------
Reporter: alih | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version: Om2008.9-dev
Severity: blocker | Resolution:
Keywords: dropbear restart, HasPatch | Blockedby:
Reproducible: | Blocking:
-------------------------------------------+--------------------------------
Comment(by zecke):
Replying to [comment:4 Treviño]:
> Sorry if I'm completely OT with the bug reporting, but I'm replying to
the HasPatch thing: how can we set these tags when putting in a patch
after that a bug has already been reported? I don't see any editable field
here to modify the tags!
> I figure it should be added; we, users, have too few permissions in
trac!
Hehe. For many being able to set a component is... We have different
groups and there is no reason to not give externals the same rights as
internals. Talking about HasPatch and keywords you should be able to add
it. In regard to your question there will be a custom boolean field
HasPatch soon(tm) you could check if there is a ticket at the admin trac
and if not file one. :)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2021#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
