Random 'Unknown' call screen on 4S

Hello - I'm getting a completely random 'Unknown' call screen on my phone. The End Call soft key shows up but it does nothing when I press it. Pressing either of the hard keys also does nothing. The phone did not ring when this screen popped up. Never seen anything like this on my phone before. Thoughts?

Looks like the Assistive Touch feature is enabled. To switch it off tripple click the home button
Accessibility Shortcut
Use the Accessibility Shortcut. Press the Home button quickly three times to turn any of these features on or off:
VoiceOver
Invert Colors
Grayscale
Zoom
Switch Control
AssistiveTouch
Guided Access (The shortcut starts Guided Access if it’s already turned on. See Guided Access on page 156.)
Hearing Aid Control (if you have paired Made for iPhone hearing aids)
Choose the features you want to control. Go to Settings > General > Accessibility > Accessibility Shortcut, then select the accessibility features you use.
copied from page 139 of the user guide iOS8

Similar Messages

Using *77 to set 'anonymous' or 'unknown' call blocking is not working

Per instructions from Verizon, I used *77 to turn on anonymous call blocking last night. I dialed *77, and got a voice telling me that I have enabled anonymous call blocking.
However, it's NOT working. When I call home from my office, it shows up in caller ID as "unavailable"; shouldn't a call that is identified as 'unavailable' be blocked with this service? Does anyone understand why this would be the case? Are all 'unavailable calls' the same?

Unavavailable/unknown calls and anonymous/private calls are two different things. Anonymous calls are calls from someone who has chosen to block their telephone number from being displayed on your caller ID screen. This means the caller has dialed *67 before dialing your phone number (or they have what is called line blocking where all their outgoing caller id info is automatically blocked without them having to dial *67 before every call). *77 is used to block anonymous/private calls and force the caller to allow their caller id info to come through to your phone in order for the call to complete.
Unavailable/unknown calls are calls in which no caller id information has been sent. These are generally from collection agencies or telemarketers. *77 will not block these calls in any way. The only services which will block or screen these calls are Call Intercept or Do Not Disturb.

Unknown caller, no ID

On my new Verizon iPhone, if I miss a call from a caller who is not in my contacts, there is no caller ID number displayed in the log; "Unknown Caller" is all that is displayed. My previous Verizon phones showed the originating number, so I expect the iPhone should also. Is there a setting that I can make?
Thanks for any advice.

sn4p2k wrote:
to be honest these are the solutions that may or may not work..
first thing I would try is rebooting the phone by holding the sleep/wake button and home button for 15 seconds until you see the white apple logo
if that doesn't work I would restore from backup and if that doesn't work I would restore as new if all else fails take it to your closest apple store they may replace the phone for a working one..
Did you even read the OP's question? Its probably just a random carrier issue, these things happen once in awhile. If it continues to happen and it bothers you that much call Verizon.

Call screening too limited

As in the case of the Anonymous Call Rejection function that won't reject Unknown Name calls, I believe the Call Screening function is too limited. As a matter of fact, why don't we just reduce the confusion and put that function into the Call Screening function. We should be able to screen by the entry we see on the Caller ID display. (If we want to take the chance that we will block occasional valid calls for which the information just does not come through, that should be our choice.) Also, most people will need more than 12 screened number calls. We should also be able to manage any digital voice functions throught the Digital Voice Center website, including the lists of screened entries. Having the statistics on how many calls a particular screened entry is attempting would be useful, so that we can reuse that slot when an entry stops trying to call us. The main reason I converted to Comcast Digital Voice was that Qwest's call screening function wouldn't allow us to screen the calls that really mattered. I hope Comcast will learn from this example. I am sure many functions will be improved over time. I just hope we don't have to wait too long!

I don't know about anyone else, but I'm not interested in the Call Trace feature, or the Call Screening feature (at least as JimWe indicated that Comcast defines Call Screening -- which is different than the definition of Call Screening that many remember). I simply would like the ability to not allow any calls through that are blocking their Caller ID from me. The features mentioned above are designed for extreme cases of phone abuse, not "screening" calls as you desire.
I currently use Grand Central, which offers traditional Call Screening (you can have calls go through to Voice Mail and then listen as the messsage is being left - then pick up if it turns out to be someone with whom you do wish to speak), call filtering, and selective call ringing. You can also have Grand Central automatically send an SMS (text message) to certain callers, depending on the filters you set up. That way I don't have to worry about the features offered (or not, as the case may be) by whatever phone service I use.

No Service then Emergency Call screen?

This all started back about a month ago, my iPhone 4 ended up having No Service. I was connected to a WIFI connection at the time so I checked on the Internet on the phone to see if there was any method to resolving the No Service issue, people said to use the Airplane Mode, did that didn't work. Then I tried turning it off and turning it back on. Didn't work there was 3G for like 10 seconds then it went to two bars than it went to one bar than No Service again. I turned it off again and turned it back on, this time it sent me to an Emergency Call screen which it then said No Service and slide to Emergency Call. I clicked on the little I in the corner and it said UNKNOWN and UNKNOWN under IMEI. So I turned the phone off then tried a different area, finally it sent me back to the Home screen and I was able to received 3G service for a while until like an hour later than my phone was sitting on my desk out of no where my iPhone pops up and says "You have No Service Please restore from iTunes" or something between those words.
So I hooked it up to my computer and restored my phone from a previous backup, it semed to work perfectly fine but that was just the beginning of my problems. Around recently about Friday the 13th, I got the No Service issue again, I did the turning the phone off and turned it back on. This really annoyed me since I was beginning to get very upset that this No Service issue was happening to me, I was near someone who had an iPhone 4 as well I asked them if they were having issues they said they weren't. I'm using AT&T BTW, so I did the turning on and off again. I ended up getting the Emergency Call screen again and it said No Service. So I kept turning it back on and off 70% of the time it was the Emergency Call screen and the other 30% was the Home screen but then within seconds it would go to No Service again.
So I moved to a different location (another part of town) and I got the 3G signal but then soon after I recieved No Service again. This issue went on and off and it was getting worse and worse by the day. Saturday the 14th, that morning I was using the phone to call someone half way through it cut out, No Service this was the day when it just stopped working for me. I ignored it and woke up 7 hours later I then used Skype on the phone WIFI connection worked but then saw I had No Service I turned it off and turned it back on. Emergency Call again, so it brought me back to the Home screen, this was the last time I would be seeing my Home screen. No Service again, turned it off and it brought me to the Emergency Call screen again, turned it off and turned it back on, EC screen again. It turned it off and turned it back on.
At this point I'm thinking to myself my iPhone is dead, so someone tells me to try to restore it. I hooked my iPhone to my Mac, it said "Waiting for iPhone" to sync I suppose. Then it says unable to sync Brandon's iPhone please restore, so I restored it, then it seemed the restore process went fine, but when the phone restarted it took me back to the Emergency Call screen. So is my phone pretty much dead? I hope this long descriptive discussion post is some help so if anyone else has gone into this problem or knows if a solution. Do I need to take my phone back and it get replaced?

I had the same problem. After the firmware update, iTunes claimed that it couldn't complete the phone registration. I traced it to an SSL web proxy, which confused iTunes (it couldn't handle the SSL man-in-the middle). A normal web browser will show a dialog stating that the SSL cert is invalid, and will give you an opportunity to accept it. iTunes doesn't gracefully handle this situation. Once I bypassed the SSL web proxy, iTunes synced up successfully.

What is the diffrence of 'call screen 100' and 'leave to screen 100'

Thank u

hi,
You can insert a screen sequence. This adds another layer to a stack.
You insert a screen sequence using the CALL SCREEN <nnnn> statement.
Note: Layers created in this way must be removed afterwards. You can do this by setting the next screen
statically or dynamically to the initial value (0) an the end of the inserted screen sequence.
To interrupt processing of the current screen and branch to a new screen (or sequence of screens), use
the CALL SCREEN <nnnn> statement. The screen <nnnn> must belong to the same program.
In the program, the system constructs a stack. The stack has to be destroyed before the end of the
program.
To return to the statement following the CALL SCREEN statement, you can use either SET SCREEN 0.
LEAVE SCREEN. or LEAVE TO SCREEN 0. The screen that called the other screen is then processed
further.
If you use the above statements outside a call chain, the program terminates, and control returns to the
point from which it was called. You can also terminate a program using the ABAP statement LEAVE
PROGRAM.
To interrupt processing of the current screen and branch to a new screen (or sequence of screens), use
the CALL SCREEN <nnnn> statement. The screen <nnnn> must belong to the same program.
In the program, the system constructs a stack. The stack has to be destroyed before the end of the program.
To return to the statement following the CALL SCREEN statement, you can use either SET SCREEN 0.
LEAVE SCREEN. or LEAVE TO SCREEN 0. The screen that called the other screen is then processed
further.
To specify the next screen and leave the current screen in a single step, use the LEAVE TO SCREEN <nnnn> statement.
Hope this helps, DO reward.
Edited by: Runal Singh on Apr 3, 2008 3:11 PM

ALV not getting refreshed when call screen is executed second time

I have 2 screens 9001 and 9002. In 9001 , I am displaying the fields of a database table in a Table Control. The user has to select some of those fields and click on a button 'Generate ALV'. After clicking , the control navigates to 9002 where I am displaying ALV with data in the selected fields(the other fields remain empty). (using custom container)
Now there is BACK button in 9002 where i have written LEAVE TO SCREEN 9001. After this if the user again make changes in column selection and click on 'Generate ALV' , then still the old alv data is displayed. (Mind you the structure of alv is same , only the selected fields should show data).
I am using REFRESH_ALV_DISPLAY also and when i tested this function independently , its working fine (although for interactive alv in the same screen).
I am making use of <fs> for dynamic internal table and i checked it using breakpoints , during the 2nd time , it contains the correctly updated data so i think the problem lies with alv
Kindly check this code
MODULE STATUS_9002 OUTPUT.
SET PF-STATUS 'ZALV'.
* SET TITLEBAR 'xxx'.
CREATE OBJECT C_CONT
    EXPORTING
      CONTAINER_NAME               = 'CUST_CONT'
IF SY-SUBRC <> 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF OBJ_ALV IS INITIAL.
CREATE OBJECT OBJ_ALV
    EXPORTING
      I_PARENT           = C_CONT
CALL METHOD OBJ_ALV->SET_TABLE_FOR_FIRST_DISPLAY
     EXPORTING
       I_STRUCTURE_NAME              = INP_TABLE
     CHANGING
      IT_OUTTAB                      = <itab>
ELSE.
   CALL METHOD OBJ_ALV->REFRESH_TABLE_DISPLAY
ENDIF.
ENDMODULE.                 " STATUS_9002 OUTPUT
Edited by: amber22 on Sep 16, 2011 6:45 PM

Amber,
Something like:
*&      Module STATUS_9001 OUTPUT
MODULE status_9001 OUTPUT.
SET PF-STATUS 'ST9001'.
ENDMODULE.                 " STATUS_9001 OUTPUT
*&      Module USER_COMMAND_9001 INPUT
MODULE user_command_9001 INPUT.
CASE sy-ucomm.
    WHEN 'GEN'.
      SELECT * FROM spfli INTO TABLE gt_outtab.
      CALL SCREEN 9002.
    WHEN 'BACK'.
      LEAVE.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_9001 INPUT
*&      Module STATUS_9002 OUTPUT
MODULE status_9002 OUTPUT.
SET PF-STATUS 'ST9002'.
IF obj_alv IS INITIAL.
    CREATE OBJECT c_cont
      EXPORTING
        container_name = 'CUST_CONT'.
    CREATE OBJECT obj_alv
      EXPORTING
        i_parent = c_cont.
    CALL METHOD obj_alv->set_table_for_first_display
      EXPORTING
        i_structure_name = 'SPFLI'
      CHANGING
        it_outtab        = gt_outtab.
ELSE.
    CALL METHOD obj_alv->refresh_table_display.
ENDIF.
ENDMODULE.                 " STATUS_9002 OUTPUT
*&      Module USER_COMMAND_9002 INPUT
MODULE user_command_9002 INPUT.
CASE sy-ucomm.
    WHEN 'BACK'.
      CALL METHOD: obj_alv->free, c_cont->free.
      CLEAR: obj_alv, c_cont.
      CALL METHOD cl_gui_cfw=>flush.
      LEAVE TO SCREEN 9001.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_9002 INPUT
Altough it's not a really nice solution... Why using 2 screens for example? you could use two containers instead...
Also I would recommand playing with the new salv class for your grids.
Anyway don't hesitate to give feed-back.
Kr,
m.

In CL_GUI_SPLITTER_CONTAINER ALV list is not show in called screen

Hello experts,
i come across a problem while using the class:CL_GUI_SPLITTER_CONTAINER ,
my codes is as follows:
data:declarations is as follows:
             data:gr_spliter     TYPE REF TO cl_gui_splitter_container,
                     gr_container1 TYPE REF TO cl_gui_container,
                     gr_container2 TYPE REF TO cl_gui_container,
                     gr_grid1       TYPE REF TO cl_gui_alv_grid,
                     gr_grid2       TYPE REF TO cl_gui_alv_grid,
step 0 Fit table contents:gt_out1 and gt_out2
step 1:   CREATE OBJECT gr_spliter
               EXPORTING
               parent            = cl_gui_container=>screen0
               ows               = 1
               columns         = 2
step 2: CALL METHOD gr_spliter->get_container
             EXPORTING
             row       = 1
            column    = 1
            RECEIVING
            container = gr_container1.
            CALL METHOD gr_spliter->get_container
             EXPORTING
             row       = 1
            column    = 2
            RECEIVING
            container = gr_container2.
step 3 :call screen 100 to show ALV.
in the screen's PBO ,i show ALV using CL_GUI_ALV_GRID,the codes is:
   CREATE OBJECT gr_grid1
    EXPORTING
      i_parent          = gr_container1
   CREATE OBJECT gr_grid2
    EXPORTING
      i_parent          = gr_container2
CALL METHOD gr_grid1->set_table_for_first_display
    EXPORTING
      i_structure_name              = Structure of table Gt_OUT1
    CHANGING
      it_outtab                     = gt_out1
CALL METHOD gr_grid2>set_table_for_first_display
    EXPORTING
      i_structure_name              = Structure of table Gt_OUT2
    CHANGING
      it_outtab                     = gt_out2
But after activing the program ,there is no ALV show in screen 100,I debug the program and find that
all the above object have been created corredtly.
if i create a custom contol named 'CONTAINER',and at Step 1 change the parent's value to 'CONTAINER',
then i could see the ALV　whick i hope in screen 100.
If i create a custom control in screen 100, the size of the alv will be different across different computer,
is it possible to use CL_GUI_CONTAINER=>screen0 as cl_gui_splitter_container's attribute parent value???
and i find that there are 10 attributes named screen0 to screen9 in class CL_GUI_CONTAINER,will you tell me the usage of
these attributes?
now i only konw that ,you could set a containers parent value to be CL_GUI_CONTAINER=>screen0,which you do't have to create
a custom control in your screen ,and the alv will be shown in full screen.and what the other attributes use (screen1,screen2,screen3,screen4 and so on)
now i am confused with the problem,i am sure any words from you will give me help to this question!
Hope to receive your advice!
Best regards!
yours Carl
Edited by: lakeandmoon on Aug 27, 2010 11:24 AM

Dear Carl,
I mean go to screen painter and place there CUSTOM_AREA (the icon with C letter). In program's PBO create CUSTOM_CONTAINER
module pbo output.
if custom_container is initial.
CREATE OBJECT custom_container
   EXPORTING container_name = 'CUSTOM_AREA'.\
endif.
endmodule.
Then you work only with CUSTOM_CONTAINER (i.e. as parent to SPLITTER_CONTAINER). Using subscreens here doens't really add the value, so you don't need any.
But how could i stretch the screen and this area to full screen?is it just gragging the screen to full screen and drag the subscreen or the custom control to full screen in screen painter?
Yes, this is what I mean
Regards
Marcin

Starting random apps and screen flicker when scrolling

My Touch 2G suddenly started to launch random apps without me touching the screen. Besides starting random apps the screen flickers when scrolling. Any body have experienced the same? It started about 1 month ago and I have always taken good care of it. I have tried every possible thing I can think of when it comes to software. Full restore, jailbreak, full restore, back to factory, back to earlier versions of IOS, but no luck. It is pretty persistent. I am sure it is hardware related and don't mind paying to have it fixed. I tried two repairshops already and they were not able to recover the reason for the malfunction. I wonder whether there is anybody who has experienced the same or even knows what is wrong?

Hey Kimwaldal,
Thanks for using Apple Support Communities.
Sounds like the devices are opening things on their own. You may want to follow this article to make sure the screens are working correctly.
iPhone, iPad, iPod touch: Troubleshooting touchscreen response
http://support.apple.com/kb/ts1827
Have a nice day,
Mario

Statement "CALL SCREEN" is not allowed in this form.

Hi,
Could anyone identify the short dump.
Statement "CALL SCREEN" is not allowed in this form.
There is probably an error in the program
"SAPLKKBL".
This program is triggered in the update task. There, the
following ABAP/4 statements are not allowed:
- CALL SCREEN
- CALL DIALOG
- CALL TRANSACTION
- SUBMIT
Error in
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLKKBL" or "LKKBLU01"
"K_KKB_LIST_DISPLAY"
Regards
Manohar S

Short text
Statement "CALL SCREEN" is not allowed in this form.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKKBL" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
There is probably an error in the program
"SAPLKKBL".
This program is triggered in the update task. There, the
following ABAP/4 statements are not allowed:
- CALL SCREEN
- CALL DIALOG
- CALL TRANSACTION
| - SUBMIT
Information on where terminated
Termination occurred in the ABAP program "SAPLKKBL" - in "K_KKB_LIST_DISPLAY".
The main program was "RSM13000 ".
In the source code you have the termination point in line 441
of the (Include) program "LKKBLU01".
| The program "SAPLKKBL" was started in the update system.
This is the dump

Is there a way to find out the number of an "unknown caller" somehow?

Recieved call from unknown caller and want to know their number...is there a way? i.e. an app or anything?

If the number is not available from your phone, no. Forget it and carry on.

Problem with Call Screen and Leave Screen !

Hi,
I am calling Modal screen (Dialog Pop up screen) from my first screen by 'Leave to Screen 'nbr' ' then once user enter the value in the pop up screen then I haveto display value with TABLE in Final screen as 'Normal screen' here I am using LEAVE to SCREEN, but after this call - my new final screen is not displaying as noraml screen it also displaying like 'Modal Screen' Like big pop scrren.!!
When I tried final CALL by using CALL SCREEN instead of LEAVE screen the final screen with table is dispalying fine as Normal screen but its returning control to pop-up screen which I dont want.
I like Screen flow as 1>2>3--->1
Help me to solve this Problem.
Regards
James

Hi,
Check the below thread,
Unable to close Modal dialog box
1) 1st screen--> 2nd screen --> Use CALL SCREEN.(This is Modal Screen)
2) 2nd Screen-->(ModalScreen so you need come back) use the above thread
3) Still on 1st screen--> Use CALL SCREEN --> To 3rd Screen
4) 3rd Screen back to First Screen -> use LEAVE TO SCREEN First_Screen_NO.
Cheerz
Ram

Problem with call screen

Hi everybody, I did work a program with Tx SE38, in the program I call a screen.
START-OF-SELECTION.
PERFORM completa_lista.
CALL SCREEN 0100.
END-OF-SELECTION.
The program run very well, but. When the program is in screen 0100 and push the button BACK or button EXIT. Don't return to program that called to screen 0100, always return to the program SAPMSSY0 and then push again the button BACK or EXIT to return the program that called to screen 0100.
This is my code in the PAI:
MODULE user_command_0100 INPUT.
CASE sy-ucomm.
WHEN 'EXIT' OR 'BACK'.
LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE.
I try with SET SCREEN 0. or LEAVE TO SCREEN 0. But always return to the program SAPMSSY0
Is there a way to skip the program SAPMSSY0?

Hi ,
LEAVE TO SCREEN 0 will work in your case.
it comes back to the point from where it triggered screen 0100.
If you want to leave the program and come back to the easy access screen then you have to use LEAVE PROGRAM.
hope this helps!!
Regards,
Soumya Ranjan
Edited by: Soumya Ranjan on Dec 15, 2010 5:59 AM

My friend has a macbook and is having problems controlling he mouse/trackppad. The problem started with snow leopard and continues with Lion. The mouse moves at random across the screen and is difficult to control. Adding a separate mouse cures the proble

My friend has a Macbook running Lion. She uses the trackpad for her mouse. The mouse can't be controlled, except with great difficulty. It hops all around the screen at randon. The problem can be mitigated to some extent by using an external USB mouse; however, when this mouse is not is use, it keeps jumping at random around the screen.

My friend has a Macbook running Lion. She uses the trackpad for her mouse. The mouse can't be controlled, except with great difficulty. It hops all around the screen at randon. The problem can be mitigated to some extent by using an external USB mouse; however, when this mouse is not is use, it keeps jumping at random around the screen.

How to go back to calling screen???

Hi experts,
I had modified the Exit MV45AFZZ to display pop up message when we save a sales order.
Now user after giving all the input in VA01 will go for SAVE button and after which pop up will occur.
Now my problem is after displaying message it should come to same screen of sales order and with all the input data as user had mentioned.
Please help as its very urgent for me.
All the answers will be appreciated.
Thanks.
Saurabh.

hi,
You insert a screen sequence using the CALL SCREEN <nnnn> statement.
Note: Layers created in this way must be removed afterwards. You can do this by setting the next screen
statically or dynamically to the initial value (0) an the end of the inserted screen sequence.
To interrupt processing of the current screen and branch to a new screen (or sequence of screens), use
the CALL SCREEN <nnnn> statement. The screen <nnnn> must belong to the same program.
In the program, the system constructs a stack. The stack has to be destroyed before the end of the
program.
To return to the statement following the CALL SCREEN statement, you can use either SET SCREEN 0.
LEAVE SCREEN. or LEAVE TO SCREEN 0. The screen that called the other screen is then processed
further.
If you use the above statements outside a call chain, the program terminates, and control returns to the
point from which it was called. You can also terminate a program using the ABAP statement LEAVE
PROGRAM.
Hope this helps, Do reward.

Random 'Unknown' call screen on 4S

Similar Messages

Maybe you are looking for