InfiniteMac OSx86

InfiniteMac OSx86 (http://infinitemac.com/forum.php)
-   10.X (http://infinitemac.com/forumdisplay.php?f=36)
-   -   Facetime works for a brief moment (10.6.8) (http://infinitemac.com/showthread.php?t=7521)

adnbek 11-27-2011 09:54 AM

Facetime works for a brief moment (10.6.8)
 
Hi there,

I'm running 10.6.8 after updating from iAtkos s3 and Facetime will work for a short time after I boot (can receive and make calls without issue). However, a short time later it stops working. If I receive calls, nothing happens and if I make outgoing calls, the phone will ring but when I accept and it says "Connecting", Facetime (on snow) will continue calling forever without establishing a connection.

If I turn off and on Facetime, again it will work for a very short period before the same thing happens again.

Anybody have this issue and what did you do to resolve it?

akimoa 11-27-2011 10:49 AM

Upgrade your Bootloader to 1684 for example

Add EthernetBuiltin=yes to your boot .plist and be sure u have a correct smbios.plist

adnbek 11-27-2011 05:20 PM

Quote:

Originally Posted by akimoa (Post 56109)
Upgrade your Bootloader to 1684 for example

Add EthernetBuiltin=yes to your boot .plist and be sure u have a correct smbios.plist

Did all that already. Still same problem.

In console, I get errors saying:

FTMessageDelivery failed! Error (NSURLErrorDomain:-1206): The server registration.ess.apple.com requires a client certificate. https://registration.ess.apple.com/W.../wa/deregister
imagent ApplePushService: Certificate doesn't match host
imagent Couldn't retrieve identity
FaceTime [Warning] Trying to update button images for unknown segment: -1
imagent [Warning] Missing email, but oh well

Dunno if it's related but it must be something to do with the background processes that monitor Facetime calls in and out.... Because Facetime works fine where it's first turned on but stops working after a bit.

hans88 11-27-2011 06:38 PM

Try adding PciRoot=0 in your boot.plist

adnbek 11-27-2011 06:59 PM

Ok.... Please try to understand the issue I have. I can login to Facetime just fine. No errors about registration or GUIDs or Apple IDs. In fact, Facetime will be perfectally functional for the first, oh... I'd say, minute or two and then ceases to receive and make calls. Turning off and then again on Facetime corrects the problem but again for just a short while before it borks again.

SN is replaced, latest chameleon installed and my ethernet is recognized as built-in.

So the issue has nothing to do with PCI roots or anything like that. I think it's because of a missing cert or backgroung processes (pushservice, imagent, marcoagent and ftmonitor) not working properly.

akimoa 11-27-2011 07:29 PM

so why would it miss something unless u deleted it ? wich i doubt u did

so what if u feel really lucky and install the comboupdate over it again i know its pretty semi prof. but maybe helps

and are we talking about an AMD or Intel Machine ?

adnbek 11-28-2011 01:55 AM

2 Attachment(s)
It's on Intel.

I doubt combo will fix this. Combo update does nothing related to Facetime iirc.

It seems to be a connectivity issue, a certificate issue or a background issue. I wish I tested FT on 10.6.6 or 10.6.7 to see if I had the problem then.

I suspect it has to be because it's from a distro and not a retail install... Maybe something was missing in it?

Do you have Snow Installed? Mind if you print-screened the login and system sections of your keychain? This is mine. Wish to see if there's anything missing there.

(note I edited the screenshot hence the missing email under Facetime)

akimoa 11-28-2011 07:09 AM

Make a proper Retail install !!! last advice i can give I'm not supporting Distris !

adnbek 11-28-2011 01:32 PM

I said that earlier in my first post...

Would it make any difference if I also owned a genuine mac with snow OEM disc AND lion? I don't support piracy either but it was easier using a distro at the time than using a retail disc.

I just wish to compare the certs on your box vs. mine.

adnbek 12-10-2011 06:18 PM

Turns it out it was my router. When I put my desktop in the DMZ, it works flawlessly now.
Weird that on my macbook pro it works all the time regardless but with the desktop it needs to be placed in the DMZ to work or else the router blocks the connection somehow. Both are using the same router to connect to the internet, the macbook wirelessly and the desktop through ethernet.
Prior to placing the desktop in the DMZ, no computer was in it.