Remote Debug sometimes working, sometimes don't

Hi,
I tried last Friday and it worked. Today it won't. I got the error when I run
exec DBMS_DEBUG_JDWP.CONNECT_TCP( '34.64.120.183', 1522); from SQL*Plus:
ORA-30683: failure establishing connection to debugger
ORA-12535: TNS:operation timed out
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
I am using the current version 1.1.2.25
The IP address is my PC's.
Thanks,
Shirley

Still having the issue?
Timed out... Are you sure sqldev was listening? At the same port?
K.

Similar Messages

  • Remote debugging not working in intex cloud fx

    I followed the steps given in mozilla support to connect for remote debugging.
    but the app manager is unable to detect the phone.
    I tried for 'lsusb' to detect check usb connection and found the following as it detects the device:
    Bus 001 Device 006: ID 1782:5d04 Spreadtrum Communications Inc.
    only app manager is unable to detect the device.
    please help me !

    http://kaustavdm.in/2014/08/connect-firefox-os-spreadtrum-device-adb.html
    check this out, it should fix all your problems !

  • Break Points while remote debugging  not working in Eclipse

    I have set up my tomcat to listen for debugger connections on the default pot 8000. Now when I set break points in the code, it does not show the execution stop at that particular line.
    Now why would that be? Am I missing somethiing?
    I have built the files with debugging on.
    thanks
    M

    http://kaustavdm.in/2014/08/connect-firefox-os-spreadtrum-device-adb.html
    check this out, it should fix all your problems !

  • Mark debug 'sometimes' not working

    I find mark debug sometimes not working.In my new project ,I add mark debug = true, then set up the debug nets.I can't find them in the assigned nets ,but from the netlists I find some of them.The missing nets are wire type,notregister type.Does the command not work on wire type nets?
    Because my project is very large, searching for the nets requires a very long time.So I hope Xilinx can fix this bug.

    Rather than open another thread, I'll extend this one since I'm having what I think is the same problem.
    I'm using Vivado 2014.4.  "Flatten" is set to "None".  The nets are set in the elaborated design with MARK_DEBUG and DONT_TOUCH.  But when synthesis gets done with them, the names are completely different.
    I don't care if the "equivalent" nets are still there.  I need the names.  Every time synthesis runs, it's a crapshoot whether the names will change.  Particularly bad are 500+ bit buses that get exploded into individual signals.  I don't have the time to regather them into the proper buses every time.
    In general, I've been pleased with the changes in Viviado.  But I can't believe how badly a wonderful tool like ChipScope has been screwed up.
     

  • Step Over not working with Remote Debugging of Servlets with JRUN

    Platform: JRun 4, JDK 1.4.1, JDev 9.0.3
    using JPDA and copied jpda.jar to JDEV_HOME/java1.2/jre/lib/ext and set path to jar in app server path.
    using debug args: java.args=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5000
    ok, I'm able to attach JDeveloper to JRun and remotely debug by jumping from breakpoint to breakpoint but stepover causes JDeveloper to continue execution to completion or to next breakpoint. Any idea why step over does not work? The only way to halt execution during remote debugging is by using breakpoints.
    Thanks in advance for any insight to this issue.

    Hi Bob,
    I think OTN ate the other thread. It says there are 4 replies, but it won't display them. Here's my latest reply.
    I just noticed something interesting from your original message. You say you are using JDK 1.4.1 for the app server (that's good) and you are using JDev 903. But you say you have copied jpda.jar to JDEV_HOME\java1.2. That doesn't make sense because JDev 903 didn't have a java1.2 directory; I think JDev 903 has a jdk directory which contains JDK 1.3 (actually 1.3.1_03 or something like that).
    Also, jpda.jar is really old and the directions for using jpda.jar and for putting jpda\bin on the app server path is really old. Those directions were needed for JDK 1.2 because JPDA was released AFTER the JDK 1.2 was released. Starting with JDK 1.3, jpda is built in and you don't need the jdpa.jar or the jpda\bin, etc.
    All this reminds me that in JDK 1.2, HotSpot had bugs where stepping didn't work!!! I'm almost positive that this is what you are experiencing. Here is my advice:
    1. Make absolutely sure that you are using JDK 1.4.1 (or at least JDK 1.3 or later) for running your app server. Make sure that you are not using JDK 1.2 - you may have modified your app server so that it uses JDEV_HOME\java1.2\bin\java.exe[i]Long postings are being truncated to ~1 kB at this time.

  • Remote Debugging w/9iAS  not working !

    I tried posting this in the app server area but apparently, it's too difficult for anyone to answer. No replies.
    We need to debug a deployed jsp that uses java beans.
    The jsp/java beans app is in jdevleoper 9.0.3.1 (windows 2000).
    I have deployed the application to Oracle 9ias java edition (9.0.3) on Red Hat Linux.
    I know how to modify the project settings in jdeveloper for remote debugging.
    when I start debug mode in jdeveloper I am prompted for the host name and port number for the remote debug session. What port do I use ?
    Do I need to do something to start 9ias at a certain port ? If so, how do I do this ?
    I have seen conflicting information on this that mainly refers to a standalone oc4j, not the oc4j in 9ias.
    Frank

    Hi,
    We have gotten many requests for collateral that details these steps. We are currently working on such a document. Keep posted to the JDeveloper OTN website http://otn.oracle.com/products/jdev for updates on this.
    -Stuart

  • Just bought a pair of earpods for the shuffle 3rd gen the first the remote doesn't work so i exchanged them and these don't work either! I already checked that they are compatible and should work! Any ideas or advice?

    Hi I recently bought a pair of earpods for my 3rd Gen ipod shuffle only the remote does not work, so i exchanged them from an unhelpful member of staff from Currys who said the problem could be my device. So i just tested the new ones and the same problem again! I already checked that they are compatible so i don't understand why the remote doesn't work. Will be greatful with any advice or answers on this one. Thanks!

    Actually they are not compatible: http://store.apple.com/us/product/MD827LL/A/apple-earpods-with-remote-and-mic

  • Apex 4.1 remote debugging with dbms_debug_jdwp - breakpoints not working

    Hi all,
    I'm using remote debugging with sqldeveloper like described here:
    http://www.oracle.com/webfolder/technetwork/de/community/apex/tipps/remote-debug/index.html
    http://sueharper.blogspot.com/2006/07/remote-debugging-with-sql-developer_13.html
    It works great with my sqldeveloper 3.0 and Apex 4.0.2
    Now i tried the same on two other servers with Apex 4.1
    The debugger is connecting. I can see the connect and diconnect message in the debug windows in the sqldeveloper.
    But the breakpoints are not working.
    Is the debugging working in Apex 4.1 for anyone here?
    Any ideas why the breakpoints are not working?
    BR,
    Björn

    Hi Björn,
    In your APEX application, have you tried updating the URL to include the parameter REMOTE, in order to initiate the remote debug connection? e.g.
    f?p=100:1:&SESSION.::REMOTE::Using the REMOTE parameter cuts out the need to specify debug code surrounding statements in the APEX PL/SQL.
    The steps are as follows:
    1) In SQL Developer, set break points in the the PL/SQL code, and compile using the "Compile for debug" option
    2) Execute the following two grants
    grant DEBUG CONNECT SESSION to <PARSE USER>;
    grant debug on <PROC> to public;  <-- might not need public but just whoever the DAD is running as.5) In SQL Developer, right-click on your connection and select the "Remote Debug..." context menu item. This will launch the "Listen for JPDA" dialog.
    5) Run the APEX Application page containing/activating the code you wish to debug, and update its URL with REMOTE in the debug parameter of the URL, and then hit Enter.
    6) Carry out the action on the page to trigger the breakpoint in your code e.g. submit the page, or click a button on the page, and you should be redirected to the breakpoint in the code in SQL Developer.
    Although I'm running with the latest release of SQL Developer, version 3.2.2 (http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html), and APEX 4.2, the 'REMOTE' parameter was introduced with our 3.1 release so will also be available for you to use in 4.1.
    Regards,
    Hilary

  • After years without a problem, I am suddenly unable to remote share my work computer at home.  I haven't done any updates recently and did not make any changes.  Anyone have any thoughts?

    After years without a problem, I am suddenly unable to remote share my work computer at home.  I haven't done any updates recently and did not make any changes to the setup.  It was working Monday night and stopped working Tuesday morning.  I am at a loss for what could have happened.   Anyone have any thoughts?

    it sounds like your work changed something on their network.  Try asking your IT people if they recently blocked any ports related to remote management or changed their firewall settings to block incoming connections.

  • Remote debugging from Windows to Linux

    Is there a full description of every step needed to do remote cross-platform C++ debugging? I'm using the Indigo version of Eclipse CDT on Windows and would like to debug an application on a remote Linux machine.
    On Windows, I do not have the ability to install a compiler or cygwin, but I do have plink and ssh on Windows. I am able to access the remote machine via RSE SFTP (a la stackoverflow.com/questions/4216822/work-on-a-remote-project-with-eclipse-via-ssh). I do have VNC but I find that the Eclipse IDE is very unresponsive under that setup, hence the desire to develop and debug from a native Windows app.
    This FAQ is the most complete (wiki.eclipse.org/CDT/User/FAQ#How_do_I_debug_a_remote_application.3F), but doesn't discuss how to deal with Windows using backslash paths and having a different filesystem root compared to Linux and its forward slashes.
    I am able to get a remote connection by playing around with the suggestions here (www.eclipse.org/forums/index.php?S=5e54b35462bb80f79ebb9fbbaf93a288&t=msg&th=173880), resulting in console output that looks like:
    Last login: Fri Apr 6 20:19:09 2012 from foo.bar.com
    echo $PWD'>'
    /usr/bin/gdbserver :12345 /linux/path/to/my/binary args_to_my_binary;exit
    but it fails with "Error while launching command: gdb --version"
    The old FAQ is very incomplete and seems out of date: wiki.eclipse.org/TM_and_RSE_FAQ#How_can_I_do_Remote_Debugging_with_CDT.3F
    This suggests it's possible but does not have sufficient details on how to set the myriad configuration options in Eclipse: stackoverflow.com/questions/6044138/remote-debugging-in-eclipse-cdt
    I suspect many people would benefit if there was a clear set of instructions in one place on how to make this happen.
    --Gerald Dalley

    OK. I just spent the last two days figuring this out, so here are step-by-step instructions that hopefully will help others (This list is unusually anal by the standards of this group, but really simple concrete instructions would have helped me).
    on the target linux box, make sure you have gdbserver. If you don't, get the gdb sources. Note: Making gdb does not build gdbserver. Instead, you have to go into the gdbserver directory and configure/make there.
    Run gdb on the linux box. In the startup banner, it will say what its target is. This will be something like x86_64-unknown-linux-gnu or i686-pc-linux-gnu. Remember this for later.
    Install MinGW on your Windows box (I had trouble building gdb on cygwin, so I recommend MinGW).
    Download expat from http://sourceforge.net/projects/expat/files/expat/2.1.0/.Note: Do not download the Windows expat installer. Download the sources instead.
    In the expat directory. "./configure --enable-shared", make, make install.
    Download the gdb sources
    ../gdb-7.4/configure --with-expat --target=x86_64-unknown-linux-gnu --host=i686-pc-mingw32
    make, make install
    Time to test. On your linux box, create and compile hello.cpp to hello.
    On your linux box, gdbserver :4444 hello
    Note:If you are on a corporate network, non-standard ports may be blocked. Set up an ssh tunnel if necessary.
    Copy hello.cpp and hello to your Windows machine
    From the MinGW prompt, run "x86_64-unknown-linux-gnu-gdb ./Hello" Note: Substitute the name of the gdb you built as appropriate based on the target platform you got in step 2.
    In gdb, load the executable with "file hello"
    target remote localhost:4444 Note: This assumes that you have an ssh tunnel on localhost. Modify appropriately.
    Verify that gdb commands like break, cont, and run work here.
    Now we want to run it from outside of MinGW. In Control Panel/System/Advanced/Environment Variables add something like E:\MinGW\bin to the path. This is necessary for the loader to find libiconv_2.dll, etc. Now verify that you can do the preceding step from an ordinary Windows command prompt.
    Launch Eclipse (finally!). New debug configuration C/C++ attach to process.
    In Main, give path to the copy of the Linux executable on the Windows system.
    In Debugger tab, set Debugger dropdown to gdbserver. Set "GDB debugger" to something like "E:\MinGW\msys\1.0\local\bin\x86_64-unknown-linux-gnu-gdb.exe" based on where your gdb is. For Connection, choose TCP and fill in the hostname and port number you've been using from gdb in the previous steps.
    Make sure gdbserver is running (it often quits when the program ends) and launch the debug configuration
    In the gdb console, enter "file hello," "break main," and cont or run (sometimes it wants one. Sometimes the other) and voila, you should be there.
    Let me know if this works, and I'll post it somewhere better.
    Good luck,
    Mike

  • Remote debugging hang

    Have anyone enconter the remote debugging hang when debug using Jdeveloper with UCM? I got this happen sometimes in some enviroment. any solutions?
    Thanks

    Hi,
    Thanks for reminding me to check on this.
    Currently you can get to it in the data pane, but it isn't pretty.
    Expand "out: oracle.jsp.runtime.OracleJspWriter".
    The "buffer" field is what you are looking for. Unfortunately, you only see the first 100 characters as the value shown for a character array or String (it's prohibitively expensive to show more). To see more, you have to expand the array. However, when it is expanded, you only see one character per line, which is awful.
    Right click on "buffer: char[8192]..."
    Choose Adjust Range...
    Make the range as big as you think you've written but be careful as it will be slow if the range is really big. 0 to 1000 seems to work okay for me. You can also make the range start in the middle, like 1000 to 2000.
    The default range is 0 to 100.
    Expand "buffer: char[8192]..."
    You can also add a watch (main menu -> Run -> Add Watch... or Ctrl+F5)
    "out.buffer" so you don't have to find the "out" and "buffer" items. You still have to do the Adjust Range part.
    I'll work on making this easier in JDev 5.0.
    Thanks,
    Liz
    null

  • OIM 11.1.1.5.0 - Remote Manager not working

    Hi everyone,
    I am working with an AD which I installed on a different machine than my OIM and I would like to install Remote Manager with my AD. I followed all the steps which are described in the documentation but when I launch RemoteManager.bat, I have the following in the console :
    D:\Oracle\Middleware\Oracle_IDM1\remote_manager>"D:\Oracle\Middleware\jdk160_24\jre/bin/java" -cp .;.\lib\xlAPI.jar;.\lib\xlVO.jar;.\lib\xlScheduler.jar;.\lib\xlRemoteManager.jar;.\lib\xerces.jar;.\lib\xlDataObjects.jar;.\lib\log4j-1.2.8.jar;.\lib\xlUtils.jar;.\lib\xlLogger.jar;.\lib\xlCrypto.jar;.\lib\iam-platform-utils.jar;.lib\oimclient.jar;.\ext\spring.jar -Dlog4j.configuration=config\log.properties -DXL.HomeDir=D:/Oracle/Middleware/Oracle_IDM1/remote_manager com.thortech.xl.remotemanager.RemoteManager
    19 mars 2012 14:31:02 com.thortech.util.logging.Logger info
    INFO: Class/Method: RMIClientSocketFactory/static: sslEnabled : trueSSLContextAlgorithm : TLSKeyManagerFactory : SunX509KeyStore : D:\Oracle\Middleware\Oracle_IDM1\remote_manager\config\default-keystore.jksKeyStoreType : JKSTrustStore : default-keystore.jks
    19 mars 2012 14:31:02 com.thortech.util.logging.Logger info
    INFO: Class/Method: RMISSLServerSocketFactory/createServerSocket Remote Managerserver socket port is 12346
    19 mars 2012 14:31:02 com.thortech.util.logging.Logger info
    INFO: Class/Method: RMISSLClientSocketFactory/createSocket Remote Manager client socket Host is (+my ip address+) and port is 12346
    I'm not sure this means Remote Manager is working cause I have a problem when I am creating the IT Ressource on OIM : connection refused to host : (+my ip address+). And when I use nmap, I can notice that port 12346 is not open.
    Thanks for your help !
    Thibault

    Hi Thibault,
    Your problem looks like a firewall problem between these servers, because you should be able to do telnet once it is up into both(SSL and NONSSL) ports, default 12346 and 12345.
    What I normally do is:
    DEBUG,20 Mar 2012 09:17:10,170,[XELLERATE.REMOTEMANAGER],Class/Method: RemoteMan
    ager/RemoteManager: Binding Remote Manager to: rmi://TLEONCIO:12346/RManager
    ...DONE
    Allow unsafe renegotiation: false
    Allow legacy hello messages: true
    Is initial handshake: true
    Is secure renegotiation: false
    RMI TCP Connection(3)-OIM-IP, setSoTimeout(7200000) called
    RMI Scheduler(0), called close()
    RMI Scheduler(0), called closeInternal(true)
    RMI Scheduler(0), SEND TLSv1 ALERT: warning, description = close_notify
    Padded plaintext before ENCRYPTION: len = 18
    0000: 01 00 CF D4 CD 02 55 6E CA 00 E5 08 E8 EC 5C 19 ......Un......\.
    0010: 81 4E .N
    RMI Scheduler(0), WRITE: TLSv1 Alert, length = 18
    [Raw read]: length = 5
    [Raw write]: length = 23
    0000: 00001: 5 1035 01 00 120 3 .....
    [Raw read]: length = 18
    0000: EA 35 E7 8F 7F DB C0 01 000C 1 68 2A 24D EA 35 E 71C 8 F0B 7F 8DB0 C
    0 DF 5 A0C 68 2A .54..D. ...h*M....Z
    0010: F4 29 ......5 .)
    RMI TCP Connection(2)-THIAGO_REMOTEMANAGER_IP, READ: TLSv1 Alert, length = 18
    Padded plaintext after DECRYPTION: len = 18
    ....0..h*M0
    000010: 01 : 10C0 0 BCF D 840 DF CD 02 5 A55 6 EF4 29 C
    ..A 00 E5. 08 E8 EC.Z 5C .)1
    9 ......Un......\.
    0010: 81 4E .N
    RMI TCP Connection(2)-THIAGO_REMOTEMANAGER_IP, RECV TLSv1 ALERT: warning, close_notify
    RMI TCP Connection(2)-THIAGO_REMOTEMANAGER_IP, called closeInternal(false)
    RMI TCP Connection(2)-THIAGO_REMOTEMANAGER_IP, SEND TLSv1 ALERT: warning, description = c
    lose_notify
    Padded plaintext before ENCRYPTION: len = 18
    0000: 01 00 E1 43 9E 6C 4E BF 97 10 03 BA 29 1A 01 EA ...C.lN.....)...
    0010: 08 30 .0
    RMI TCP Connection(2)-THIAGO_REMOTEMANAGER_IP, WRITE: TLSv1 Alert, length = 18
    [Raw write]: length = 23
    0000: 15 03 01 00 12 0A F7 B7 14 70 18 A0 2C 05 E3 21 .........p..,..!
    0010: 4E D0 27 26 FE 6E F3 N.'&.n.
    RMI TCP Connection(2)-THIAGO_REMOTEMANAGER_IP, called close()
    RMI TCP Connection(2)-THIAGO_REMOTEMANAGER_IP, called closeInternal(true)
    RMI TCP Connection(2)-THIAGO_REMOTEMANAGER_IP, called close()
    RMI TCP Connection(2)-THIAGO_REMOTEMANAGER_IP, called closeInternal(true)
    I write into Telnet command and into telnet connection I write one command called +'EHLO something'+ to write and check a message from OIM-Server to RM-Server using SSL_port
    -->telnet THIAGO_REMOTEMANAGER_IP 12345
    [oracle@xxxxx~]$ telnet THIAGO_REMOTEMANAGER_IP 12345
    Trying THIAGO_REMOTEMANAGER_IP...
    Connected to THIAGO_REMOTEMANAGER_IP (192.xxx.xxx.xxx).
    Escape character is '^]'.
    EHLO THIAGO
    then you will see something like this:
    [Raw read]: length = 5
    0000: 45 48 4C 4F 20 EHLO ****
    RMI TCP Connection(3)-OIM-IP, receive SSL message
    RMI TCP Connection(3)-OIM-IP, WRITE: TLSv1 true, length = 2
    [Raw write]: length = 7
    0000: 15 03 01 00 02 02 0A .......
    RMI TCP Connection(3)-OIM-IP, called closeSocket()
    RMI TCP Connection(3)-OIM-IP, called close()
    RMI TCP Connection(3)-OIM-IP, called closeInternal(true)
    but as I said, first the telnet should be ok. If not, take a look into your firewall rules and let us know.
    I hope this helps,
    Thiago Leoncio

  • Cannot remote debug from JDev 10.1.3 on AS 10.1.2 running hotspot

    Hi,
    I've set up an embedded OC4J instance in an application server as described in the help topic, "Remote Debugging in OC4J" (with a few changes, such as the fact that I added startup options using the OC4J instance Admin page of EM, rather than at the command line (since the instance is embedded in a full AS). I followed the directions specifically for HotSpot, because that's the JVM the instance was set up to use, and I can't change it (I know OJVM enables lots more features, but that's the situation I'm in).
    I've also configured my project for remote debugging, ensuring the host name and port matches, and trying both "Attach to JDPA" and "Attach to OJVM" (these being the only two options, except for starting a listener, which I don't think will help with a web application).
    When I try to debug, though, I get:
    Debugger unable to connect to remote process.
    Should I be doing something differently?
    Thanks much,
    Avrom

    I had the delete key quit working after accidentally pressing a key sequent that included the delete key. I don't know what keys were involved, but the delete key from that point on did nothing.
    I am running JDeveloper 10.1.3.0.4 on Window XP.
    To resolve the problem, I set the keyboard Accelerators back to 'Default' in JDeveloper.
    I selected... Tools->Preferences->Accelerators
    then click on 'Load preset' then I chose 'Default'
    You may need to select something other than default for your platform, but that did the trick for me.

  • How to start listener in sql developer for remote debug

    how to start listener in sql developer for remote debug ? Since the new version 1.1.0.23 is different with the old version for remote debug, I don't know how to start the listener on the new version for remote debug.
    even follow the user guide below and not work . Experts on sql developer please help me with this.
    Remote Debugging
    To debug a procedure or function for a connection where the database is on a different host than the one on which you are
    running SQL Developer, you can perform remote debugging.
    Remote debugging involves many of the steps as for local debugging; however, do the
    following before you start the remote debugging: Use an Oracle client such as SQL*Plus to issue the debugger connection command. Whatever
    client you use, make sure that the session which issues the debugger connection commands is the same session which executes your PL/SQL
    program containing the breakpoints.
    For example, if the name of the remote system is remote1, use the following SQL*Plus command to open a
    TCP/IP connection to that system and the port for the JDWP session:
    EXEC DBMS_DEBUG_JDWP.CONNECT_TCP('remote1', '4000'); The first parameter
    is the IP address or host name of the remote system, and the second parameter is the port number on that remote system on which the debugger
    is listening.
    Right-click the connection for the remote database, select Remote Debug, and complete the information in the Debugger - Attach
    to JPDA dialog box. Then, follow the steps that you would for local debugging (for example, see Debugging a PL/SQL Procedure).
    Debugger - Attach to JPDA This dialog box is displayed when you right-click a database connection name and select Remote Debug.
    Use this
    dialog box if you are using the Sun Microsystem's Java Platform Debugger Architecture (JPDA) and you would like the debugger to listen so
    that a debuggee can attach to the debugger.
    For more information about remote debugging, see Remote Debugging.
    Host: Name or IP address of
    the remote host on which SQL Developer should listen for the database to connect.
    Port: Listening port number on the remote host. You can
    choose any valid port number that is not in use by another process.
    Timeout: The number of seconds that SQL Developer will wait for the
    remote database to make a debugging connection. Don't Show Dialog Box Before Connecting: If this option is checked, this dialog box will not
    be displayed before future connections for remote debugging

    You're not the only one:
    Not able to start remote debug listener
    Re: remote debug question at version 1.1.0.23 64

  • Remote does not work correctly after update

    Hello,
    the subject explain it already:
    After upgrading to 2.3 the apple remote does not work correctly anymore:
    I need to push the buttons twice, and than atv is only reacting sometimes.
    Any ideas?
    BR
    Frank

    Same problem here. First, I thought it was the Apple remote's battery. I replaced that and the problem persisted. I then used my digital video camera to verify that the remote was actually transmitting infrared, it was. In frustration, I tapped the buttons rapidly while pointing at the Apple TV. The Apple TV responded. The next button press it failed to respond. I tapped rapidly again and it finally responded. After many many rapid presses, while pointing directly at the Apple TV, it finally began responding to all presses. Once I'd regained control (I thought) I unpaired and re-paired the remote. Everything continued to work. At that time I also saw that I could "learn" another remote. So, I set up my Samsung TV remote. Sweet. Until the Apple TV went into screensaver mode again and I had to go through the same rapid button press sequence... with either the Apple remote or my learned Samsung remote. Conclusion, since the Apple TV will become fully responsive after the rapid button press sequence, it is certainly a software related problem.

Maybe you are looking for