7 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHremote key getting weaker
Reported or suspected cause
key head
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report identifying a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Leading evidence: 'key head' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'key head' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Replace battery and it didnt make a difference' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
I thought it was the remote battery but i changed the battery and it didnt make a difference.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
Mine was doing a similar thing with the range getting weaker, but when I replaced the battery it got much better for a few days, then began getting weak again.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
i havent yet, i ran across that tsb as well and bookmarked it.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause · Original poster
I thought it was the remote battery but i changed the battery and it didnt make a difference.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
Mine was doing a similar thing with the range getting weaker, but when I replaced the battery it got much better for a few days, then began getting weak again.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
7 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T053112Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi all, Ive searched the forums and google for answers but the threads that i find never actually pin point the problem and solution for this issue. So Im just gonna ask.
I have a 996 1999
My remote key has been getting weaker and weaker (range wise).
I thought it was the remote battery but i changed the battery and it didnt make a difference.
From what Ive read it could be a number of things:
the battery, fuse, alarm module, head unit installation, etc.
Some info:
The range has always been pretty bad, like 6 feet from the car max. But from what I've read this is normal. Then I installed an aftermarket head unit, and I didn't ground the brown (i think) wire and left it on purpose because I kinda liked having the car honk when I lock it with the remote.
My battery is ok, not great, around 13 when started then goes up to just under 14.
So the question is, what is causing my remote getting weaker? And what can I do to find out and fix it?
Thanks.
Have you fixed your remote antenna length? This is a well know fault documented in Porsche TSB #9662 "Insufficient Range of Remote Control"
Google it. There are documented procedures on sites such as Renntech with pictures that will get you through this. this will greatly improve your range.
I believe the antenna is inside the drivers side A pillar. I remember removing the outside cover of this and tweeking it to get better range on our Boxster years ago. Search and you may find the details.
i havent yet, i ran across that tsb as well and bookmarked it. I am planning on doing that too, but the fact that my remote actually got weaker tells that i need to fix something else first.
I also have a '99. Mine was doing a similar thing with the range getting weaker, but when I replaced the battery it got much better for a few days, then began getting weak again. After two batteries, it wouldn't even last a day. My problem turned out to be the key head. I replaced it and have had no problems since.
