You are not logged in.
Pages: 1
I installed the latest firefox and there is no Hello/Chat (firefox webrtc based skype thing) button in my customize menu -where it is supposed to be according to google.
http://i.imgur.com/lNqslQP.jpg
Am i missing a library or i have to mess with something in about:config ![]()
Offline
Yes, you do need to modify about:config. In there, find "loop.throttle" and set it to false (by double-clicking on it). Once you restart your browser you should find the button in menu>customize.
Source: OMG!Ubuntu, and more specifically Joey's comment
Offline
I got "Firefox hello" button using above method.
But nothing happens when I click "sign in or sign up"
Offline
This thing is a mess. All my calls are failing. Did anyone get it working?
Offline
It does not work behind proxy (just incase you are using one).
You need to bypass proxy for .firefox.com, .tokbox.com and .opentok.com
Then I called myself using the URL given.
And then it rang and I accepted.
Video and audio worked for a while but after that I got message saying - "something went wrong"
And call got disconnected.
May be call fails because I called myself.
Could not test anything further as I dont have anyone else to call.
Also I tried lot of things - still clicking on "sign in or sign up" does nothing.
Last edited by amish (2014-12-02 03:44:39)
Offline
But nothing happens when I click "sign in or sign up"
I'm not sure why that is - that worked perfect for me (I had to sign up since I had never made a Firefox account before).
I will be testing calling on Wednesday; I will post my results following that.
Last edited by DaimyoKirby (2014-12-02 04:01:15)
Offline
Ok, so I got around to testing it and it all seems to work fine for me. The video and audio quality are comparable to Skype's. It doesn't have a chat, which would be nice to have since I sometimes like to send links to the other person, but who knows if that's in the works or not.
Since I don't really know anything about debugging Firefox, I can't really help you guys if you have issues, but I'm guessing it's something with your configurations since it works fine on mine; it's also technically Beta software, so that might be part of your issues. Googling your symptoms would probably reveal more.
tl;dr It seems to work great, especially for beta software. Sorry I can't really help you with your issues ![]()
Offline
I forgot tell that I had solved my issue by resetting the following to default values in about:config
loop.fxa_oauth.profile
loop.fxa_oauth.tokendata
loop.hawk-session-token
loop.hawk-session-token.fxa
loop.ot.guid
loop.seenToS
loop.urlsExpiryTimeSeconds
Basicallly everything that starts from loop.
Except loop.throttled and loop.soft_start_ticket_number
Offline
Interesting, I had the same issue as amish: the call would work for about 30 seconds, and then suddendly fail with the message "Something went wrong." I tried connecting from Chromium, but it wouldn't let me activate the audio to begin with, it would always insist on blocking it.
In the end I found out a way to work around the issue. It turns out that both browsers get utterly confused if you have a microphone, but no webcam. So the workaround is to install v4l2loopback, then send something through it, for instance with ffmpeg:
ffmpeg -f x11grab -r 15 -s 1280x720 -i :0.0+0,0 -vcodec rawvideo -pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0Doing that makes both work fine (and as an added bonus you can show other people your screen; if you don't want to, you can turn off broadcasting it, "mute webcam", from Firefox Hello itself).
Offline
Ok above issue still exists for me.
Issue I had solved was - "nothing happens when i click sign-in or signup". Clearing the configs (as above) solved it.
But random disconnection with "something went wrong" still happens.
Offline
But random disconnection with "something went wrong" still happens.
Did you try my sugestions with v4l2loopback?
Offline
I have a webcam so I dont need v4l2loopback. It displays webcam correctly for few seconds and then reports "something went wrong"
I tried with above command (via v4l2loopback) but it shows blank video. (in my case loopback device would be /dev/video1)
Anyway I am done with R&D, will wait for it to come out from beta and then test again.
Last edited by amish (2014-12-08 11:18:31)
Offline
Huh, interesting. So maybe there are several issues at play here.
Offline
Pages: 1