Issue with Proximity Sensor during calls - Continued.

This thread is a continuation of Issue with Proximity Sensor during calls which was getting too long and causing some browsers to time out. The old thread has been locked and the last post links to this thread.
Thank you.
Apple Discussions Hosts

I find it completely ludicrous that Apple can interject on this thread and say it's received too many posts and has to be shut down and a "new" thread started. Really now? Seriously? Couldn't they also simply pop in and post 'hi guys, we hear you and are working on it' ...or something to that effect? That's my main complaint really is the deafening silence. What they're basically telling us is to complain all we want, if we don't like the phone then return it for a refund ...that is if you still have your original defective phone, for all you that already swapped phones, you're beat and are stuck with our mistake for the next 2 years when you'll be upgrade eligible again. ...WOW, thanks for the statement without technically releasing one. ...I think we're all left in the dark because Apple really doesn't know what is going on with the sensor, they can't and or won't release a statement without getting the facts straight. ...but we all know one fact is straight...the sensor is dysfunctional and that alone deserves an acknowledgement. How are we to have faith in Apple to fix the issue when we're left to believe they don't think there is one.
...btw update on "my fix" ...deleting all your photos and putting the phone in your arm pit and then under your pillow is only a temporary solution, for mine sensor is on the fritz again. ...shaking my head, if only this were
funny.

Similar Messages

Issue with Proximity Sensor during calls - Continued v2

This thread is a continuation of Issue with Proximity Sensor during calls - Continued. which was getting too long and causing some browsers to time out. That thread has been locked and the last post links to this thread.
See also the initial thread Issue with Proximity Sensor during calls
Thank you.
Apple Discussions Hosts

rbrylawski wrote:
Goflying wrote:
mbassoc2003 wrote:
I wish that were so. Then they would probably be taking prompter action. But the return rate three weeks in was substantially lower than most handsets at launch and only a quarter that of the 3GS. I suspect the return rate has remained incredibly low and the figures are further slewed down the way by the worldwide distribution that is now in the tens of millions.
At 5% return rate on a product I understand that becomes a 'significant event' that becomes declarable to shareholders, so we know they haven't reached that milestone yet.
a disclosable event is not triggered by a specific stock return level unless apple has entered into covenants re same. Suggest you take a look at sec rules for more info
Still, unless you have insider knowledge, you don't know Apple's buying them back at record numbers. You may be guessing, but you likely don't have proof....
agree. I don't have any proof whatsoever, just a strong gut feeling that all is very much not as rosy in cupertino as it might seem.
For a company whose culture is steeped in phreakery, apple is showing an amazing inability to exert control.
too many screw ups, too many loose ends, too many whacky hires, too many media backlashes - maybe the senior staff went into dumb-mode while steve was away for so long
null

Issue with Proximity Sensor during calls

I'm having an issue with the Proximity Sensor not properly detecting when i'm holding my phone to my ear. I can confirm that the iPhone sensor is working by covering it with my finger, but when held to my face, the screen blinks as if it cannot decide to disable the screen or enable it. It results on me hanging up, putting calls on mute, and dialing numbers accidentally while i'm on the phone. This occurs on 90% of my calls. Is anyone else experiencing this issue. I would like to confirm whether this is a software issue (Proximity Sensor sensitivity too low) or a design issue (sensor now placed towards the end of the phone).
Macbook Pro, Mac OS X (10.6.4)

Hi there bobby adapa,
You may find the troubleshooting steps in the article below helpful.
iPhone: Hardware troubleshooting
http://support.apple.com/kb/ts2802
Screen won't lock or go black when answering calls
Verify mute or speaker have not been activated, just prior to placing your ear over the receiver.
While on a call hold your hand over the top third of the display, and verify that the screen is locked or goes to sleep.
Try turning iPhone off and then on again.
Issue not resolved
My issue is still not resolved. What do I do next?
Contact Apple Support.
-Griff W.

Re: Issue with Proximity Sensor during calls

Im sure if it is a hardware issue, all Apple would have to do is change the software. Im sure they can add something to the software that allows you to lock the buttons when on a call, or make the sleep button on top of the phone disable the proximity sensor if you hit it. Granted, it would be lame if they had to do this, but we all know they aren't going to recall the phone, so hopefully they can 100% fix it, but if not, there are other options, even if we may not like them.

Dear Gentlemen:
You should join the many people posting about this very issue. Below is the link:
http://discussions.apple.com/thread.jspa?threadID=2475509&tstart=0&start=1680

IPhone having issues with Proximity sensors

I just got my new 5S with iOS 7.1.1 and occasionally when i answer a call and put the phone close to my ear the screen lags. It turns off and then back on and will do it a couple times before either staying off or sometimes on during a call. Not sure if this is an issue with the sensor on my phone specifically or if it's a software issue. I haven't yet taken it to apple as it isn't an emergency and I have no time to go to an Apple store. Is anyone else having this problem?

Screen won't lock or go black when answering calls
Verify mute or speaker have not been activated, just prior to placing your ear over the receiver.
While on a call hold your hand over the top third of the display, and verify that the screen is locked or goes to sleep.
Try turning iPhone off and then on again.

C4 - Issue With Proximity Sensor

Got my xperia c4(E5363) this afternoon and noticed an issue with the proximity sensor. When I make a call and bring the phone near my ear, the screen becomes black BUT it does not recover even when I take the phone away from my ear. It remains black only. Even pressing the power button does not help.The only workaround is that I have to remove the sim, which causes the phone to reboot. Once its up, I need to shut it down again, re-insert the sim and restart. pls help !!!

just back from service centre. you were right. it was the screen protector !!!!It has been removed and the phone works like a charm now.Many thanks for your help !!!!!!!

N8 - Proximity Sensor During Calls is Killing me, ...

Hi guys
again and again .. the proximity sensor is driving me crazy almost 90% of my calls faces End mute hold and bla bla bla ... the cheek keeps touching the screen and hillarious clicks are made during calls ... i swear every single call faces end mute hold .. am too disappinted am avoiding calls now !!! Nokia were is the solution ?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!??????????????!!!!!!!!!!!!!!!!! and where the hell is the red button for quick ending calls or quick quitting menus !!!!!!!!!

Thank goodness I'm not the only one....my N8 keeps putting people on "hold"!!!
I keep talking and they hang up on me! Nokia, seriously, this should not happen. My sister calls me Brittney Spears... since she wears a headset a lot...LOL.
Grrr...it's so annoying....!!!
UHHHH!!!!
Attachments:
britney-spears-big.jpg ‏15 KB

Problem with Proximity Sensor

When I decide to make a call the Proximity Sensor turns off the screen, but when I go to hang up the call I can't because the screen is still turned off. This means I can't hangup on any call!
Using iPhone 4 (1 Day Old)

I don't believe this is fixed and have rised the issue with Apple. I did what was asked on the link provided and still the problem persisted.
Could I ask if the problem came about via upgrading the iOS from 3.1.x to 4?
I've done a clean install of the iOS...meaning I wipe everything.... and it looks like it might have worked.

I can live with iphone 4 antenna problem but not with proximity sensor...

I did not face much trouble with antenna issue.. may be I am having good signal.. but certainly I am facing proximity sensor issue.. out of every 5 calls I have problem with at least 2 to 3 calls going to mute or starting facetime or opening address book etc...

I feel 100% the same. I am wondering if all these people complaint of the signal strength issue are really actually experiencing the proximity problem and just don't know it. This is beyond annoying.

Issue with Session ID during POST

Hi All,
I am using Weblogic server version weblogic 9.2 and facing an issue with the session ID.
I have a client side script with numerous GET calls and one POST call that it makes in a single session. Frequently I come across with issue that the session ID that I send in POST request is not the same as received and this affects my subsequent GET calls not to be in the same session. The call order is like this
GETij/POSTij where i is the sent and j is the recieved session IDs.
[GET11, GET11, GET11, POST12, GET11, GET11, <after few secs interval> GET22, GET22]
I store the session id in a cookie. And I always create a session using the HttpServletRequest.getSession();
Can some one advice on this.
Thanks
Shankar

Hi,
Again as a follow-up, I am using net scape ns plugin for load balancing (iPlanet/Weblogic). The issue happens when the primary server id and the secondary server id are same in the session id (set in the cookie) when the cookie is sent and received, where session id is of the default format <session id>!<primary server id>!<secondary server id>
Any clue?

SUM issue with XSS components during maintenance on NDWI controlled landscape

Hello,
This is our first time using SUM/MOpz for a release upgrade procedure as the last JSPM update disabled the launch program.
During our test upgrade of our Enterprise Portal HUB landscape (source NW 7.02 -> target NW 7.4) with EHP5 for ERP 6.0 - XSS Self Services for backend ERP system installed. I've encountered an issue with SUM in the Configuration stage - Target Release Components screen. the only 5 objects SUM cannot handle automatically are the XSS Self Services target release components:
SAPPCUI_GP         633
SAP_ESS               633
SAP_ESS_LGP     633
SAP_MSS               630
UTXSSLGP             633
The only option I have is to scan inbox to rebuild the component list. I'm assuming, since these components are being modified by us and delivered/deployed thru NWDI track, their source location on the system is now the track name instead of the SAP delivered MAIN_ERP53VAL_C. Which means that SUM is expecting updated modified SCAs from NWDI for new 633 versions in the download directory before proceeding to next phase. However, in NWDI landscape configurator for this track, I have checked the option to mark system in NWDI control and verified SUM recognizes the system as NWDI controlled.
I'm struggling to understand the where the disconnect is between SUM and NWDI for theses components as I thought that SUM is supposed to ignore the DEV NWDI developed and wait for updates modified SCAs only in QA and PROD. Does anyone else have experience with this process to help me?
Regards,
Paul

Hi Paul,
We are facing the same issue although we can see in the process Overview of SUM that the system is not ticked as under NWDI Control.
But we are facing problem only for SAP ESS and SAP MSS not other components. Other three components are coming up fine and ready for deployment. This is due to the issue that only these components are identified in the BUILD COMPONENT LIST UPGRADE step as modified.
Detailed checking of the logs led us to errors identical to the KBA 2034886 - Error: Dialog eliminator ConfirmComponentsDialogEliminator does not allow to omit dialog ConfirmComponents
The system should get picked as under NWDI control and following all steps of the upgrade for NWDI driven system landscapes
Thanks and Regards,
Karan Shah
Message was edited by: Karan Shah

Issues with only one group call.

I am having an issue joining one call group. I did not have this issue until a day or so ago. I multiple people in the group on my friends list. The people that usually lead the calls are all on my friends list. When I try to join it goes through the steps then drops me. A voice comes up telling me that the person I am trying to reach is not available and it has me leave them a message. This is the only group I have issues with. We tried making another group, it worked fine. I can call people and people can call me. I am not sure what the issue is with the lone group. Anyone have any ideas about this?

First... You are not making your boot drive the share point are you????? Only share an entire drive if the drive is ONLY used for data (not OS).
You need to make mroe than one share point.
You can have one share point which is the Data drive and another share point which is the customer folder within.
You can have share points which exist within share points.
Jeff

Issue with Foreighn trade during billing

Hi All,
We have an issue related to Foreign trade during billing.
The system is not throwing any error message even though the foreign trade data is not filled.
We have maintained the incompleteness schemas and incompleteness procedures and other relevant settings for foreign trade but the system is not stopping the user from saving the billing document.
Please let us know what needs to be done so that filling the Foreign trade becomes mandatory.
Regards,
Teja

Dear Teja
Go to OVE6, select the origin country and there you can see various "Procedures" listed out with two boxes "Export" and "Import". Maintain "E" under the tab Export against any Procedure and save.
Now go to OVE7, select the origin country and there assign the above procedure to the combination of sales area, Exp/Imp Group and item category.
thanks
G. Lakshmipathi

TS3367 Since updating to the new operating system I have had some issues with FaceTime. When calling my Dad through FaceTime I have gotten someone else using my Dad's email. This has happened on at least 4 occasions. Has anybody else had this problem?

Has anyone had an issue contacting someone through FaceTime? Sometimes when I try to call my Dad I get a different party ( someone I don' t know). This has happened when calling fro IPad (3) And IPhone 5s.

In the terminal I go to /volumes/some_folder/test and I type "chmod 4711 test" so that the C++ program will be run as the admin account I'm logged in with. This admin account has privileges to create folders in /volumes/some_folder/test.
I vaguely recall something about this - isn't it related to the execution of setuid scripts?
There's a whole discussion on the security implications of doing this. It's generally not considered safe.
It might be worth reading http://httpd.apache.org/docs/2.0/suexec.html for details of how to implement setuid within Apache.

Issues with table filter during navigation between task-flows

Hello everyone,
I'm looking for a workaround to resolve two issues about the table filter. They are:
1) If I type something in a filter and I change tha page (in a different task flow) when I return on the first page there is the previous search plus the string "%*". Here the video example: http://screencast.com/t/FbVenZGm
2) In the same scenario, if I click enter on this filter the system returns this message error: "Attempt to set a parameter name that does not occur in the SQL: vc_temp_1 ". Here the video example: http://screencast.com/t/yMs6rNDF
I have found something interesting in this thread: task-flow table filtering behaviour related to bug 8602867
Anyway, I have implemented the solution reported in this document: http://www.oracle.com/technetwork/developer-tools/adf/learnmore/april2012-otn-harvest-1609383.pdf (pp. 8-11). This solution works fine with my master table, but it doesn't with the detail table.
Have you any idea for this kind of behavior?
Thanks in advance,
Baduel

Sudipto,
each table has a binding on a page fragment in this way:
<af:table [...] binding="#{backingBeanScope.MyBackingBean.masterTable}">
<af:table [...] binding="#{backingBeanScope.MyBackingBean.detailTable}">
In the pageDef I have two methods, each one of the VOImpl class related to the table:
<methodAction IterBinding="MasterTableVO1Iterator"
id="clearOutstandingImplicitViewCriteriaMaster"
RequiresUpdateModel="true" Action="invokeMethod"
MethodName="clearOutstandingImplicitViewCriteria"
IsViewObjectMethod="true" DataControl="MyDataControl"
InstanceName="MyDataControl.MasterTableVO1"/>
<methodAction IterBinding="DetailTableVO2Iterator"
id="clearOutstandingImplicitViewCriteriaDetail"
RequiresUpdateModel="true" Action="invokeMethod"
MethodName="clearOutstandingImplicitViewCriteria"
IsViewObjectMethod="true" DataControl="MyDataControl"
InstanceName="MyDataControl.DetailTableVO1"/>
MyBackingBean class:
public class MyBackingBean {
private RichTable masterTable;
private RichTable detailTable;
/*getter methods here*/
public void setMasterTable(RichTable masterTable) {
this.masterTable = masterTable;
resetTableFilter(1);
public void setDetailTable(RichTable detailTable) {
this.detailTable = detailTable;
resetTableFilter(2);
/*This method returns the phase id */
private String printCurrenPhaseID() {
FacesContext fctx = FacesContext.getCurrentInstance();
Map requestMap = fctx.getExternalContext().getRequestMap();
PhaseId currentPhase=(PhaseId)requestMap.get("oracle.adfinternal.view.faces.lifecycle.CURRENT_PHASE_ID");
// System.out.println("currentPhase = "+currentPhase);
return currentPhase.toString();
public void resetTableFilter(int tab) {
String phase = printCurrenPhaseID();
FilterableQueryDescriptor queryDescriptor;
if(phase.startsWith("RENDER_RESPONSE")) { // Only in this phase the binding is ready
switch(tab) {
case 1:
queryDescriptor = (FilterableQueryDescriptor) getMasterTable().getFilterModel();
if (queryDescriptor != null && queryDescriptor.getFilterCriteria() != null) {
queryDescriptor.getFilterCriteria().clear();
// PPR refresh a jsf component
AdfFacesContext.getCurrentInstance().addPartialTarget(getMasterTable());
break;
case 2:
queryDescriptor = (FilterableQueryDescriptor) getDetailTable().getFilterModel();
if (queryDescriptor != null && queryDescriptor.getFilterCriteria() != null) {
queryDescriptor.getFilterCriteria().clear();
// PPR refresh a jsf component
AdfFacesContext.getCurrentInstance().addPartialTarget(getDetailTable());
break;
default: return;
invokeClearViewCriteria(tab);
public BindingContainer getBindings() {
return BindingContext.getCurrent().getCurrentBindingsEntry();
/* This method invokes the exposed method in my fragment */
public void invokeClearViewCriteria(int tab) {
BindingContainer bindings = getBindings();
OperationBinding operationBinding;
if(tab == 1)
operationBinding = bindings.getOperationBinding("clearOutstandingImplicitViewCriteriaMaster");
else if(tab == 2)
operationBinding = bindings.getOperationBinding("clearOutstandingImplicitViewCriteriaDetail");
else
return;
if(operationBinding != null) {
operationBinding.execute();
Finally I have two identical exposed methods in the VOImpl classes of the tables:
public void clearOutstandingImplicitViewCriteria() {
// we only want to remove the stuff that was added though the table
//filter (or a default search form)
// "__ImplicitViewCriteria__" is the magic name for this VC
ViewCriteria vcDefault = this.getViewCriteria(ViewCriteriaManager.IMPLICIT_VIEW_CRITERIA_NAME);
if (vcDefault != null) {
//Clear the stored values
vcDefault.clear();
//And refresh the collection
this.executeQuery();
Please note that this workaround works fine with my master table, but i does not with the detail table.
Thanks again.
Baduel

Issue with Proximity Sensor during calls - Continued.

Similar Messages

Maybe you are looking for