Opened 8 years ago

Closed 7 years ago

Last modified 6 years ago

#767 closed defect (fixed)

Micro is turned on before the vibrator is actually stopped (on incoming call)

Reported by: McKael Owned by: mrmoku
Priority: major Milestone:
Component: Frameworkd / FSO Version: all
Keywords: Cc:

Description

On incoming call, the micro is turned on before the vibrator is actually stopped, so the other party hears one or two vibrator buzzes when I pick up the call.

Change History (16)

comment:1 follow-up: Changed 8 years ago by TAsn

Latest unstable?
It's clear you haven't read the guidelines at
http://wiki.shr-project.org/trac (at the top) Please do and add more info.

Anyhow, it shouldn't happen, if that happens it only means fsodeviced does something too slow :| And then it's not our domain, but freesmartphone.org's.

comment:2 in reply to: ↑ 1 Changed 8 years ago by McKael

Replying to TAsn:

Latest unstable?

Actually it is on latest testing, but spaetz said it had to be reported to "the shr-unstable guys":
http://lists.shr-project.org/pipermail/shr-user/2009-December/002615.html

It's clear you haven't read the guidelines at
http://wiki.shr-project.org/trac (at the top) Please do and add more info.

It's not clear what more information you do need. It is default (and fresh) installation, default profile, default... incoming call?
Hopefully probably easily reproducible. I'd be surprised if I was the only one having this problem.

Regarding the component, I wasn't not sure which one is relevant so I left the default one (SHR Image).

comment:3 Changed 8 years ago by TAsn

  • Component changed from SHR Image to frameworkd / FSO
  • Owner changed from ainulindale to daniel
  • Version changed from SHR-unstable to SHR-testing

Now that's a lot of relevant issue. and by reporting to the unstable guys he probably meant talk to us but still report it as testing :P

Anyhow, it seems like you are just a couple of versions behind in testing as it looks ok in unstable. (We had it, and it's now gone.)
Ask spaetz (I'll too if I remember) to upgrade fsodeviced.

comment:4 Changed 8 years ago by spaetz

shr-testing has
fsodeviced - 1:0.9.0+gitr861+1b329ccc044eb087a6f8a7c7c61022c162f51ab2-r1.6.4
which is the latest revision of fsodeviced that exists...
This is not an fsodeviced version issue.

comment:5 Changed 8 years ago by TAsn

Okie :P Weird, this means the bug is still there in fsodeviced :P
spaetz: btw, it could easily be niceness, what's the niceness there? we changed back to 0. (for fsodeviced)

comment:6 Changed 8 years ago by spaetz

Just downloaded the latest shr-testing image and it has no niceness (so it's default). However, the first shr-testing still had NICENESS=10, I think.

comment:7 Changed 8 years ago by McKael

I've upgraded to latest testing and it seems better. Sometimes the other side can still hear the end of the last vibe, though.

comment:8 Changed 8 years ago by TAsn

again, this is an fsodeviced issue. (Or niceness)

This bug you are describing just means fsodeviced doesn't stop vibration fast enough, will fix itself when we'll move to controlling it ourselves from phonefsod.

comment:9 Changed 8 years ago by Heinervdm

  • Milestone set to MS1

comment:10 Changed 8 years ago by mrmoku

I guess the 'bug' is more in oeventsd being too slow to turn vibration off... no matter how fast fsodeviced is.

comment:11 Changed 8 years ago by mrmoku

  • Owner changed from daniel to mrmoku
  • Status changed from new to assigned
  • Version changed from SHR-testing to all

comment:12 Changed 8 years ago by mrmoku

  • Milestone changed from MS1 to MS2
  • Status changed from assigned to accepted

delaying this for MS2. We will obviously fix it by dropping oeventsd and handling ringtone/vibration ourselves. But that won't happen right now...

comment:13 Changed 7 years ago by dos

  • Resolution set to fixed in unstable
  • Status changed from accepted to closed

Now it's already ok, even without getting rid of oeventsd :)

comment:14 Changed 7 years ago by jama

  • Resolution fixed in unstable deleted
  • Status changed from closed to reopened

comment:15 Changed 7 years ago by jama

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:16 Changed 6 years ago by morphis

  • Milestone MS2 deleted

Milestone MS2 deleted

Note: See TracTickets for help on using tickets.