Related
Hello,
apart from several software issues i have following hardware issues:
- vibration stops working from time to time, especially when not having used the device for a day or long. If you shaked the phone it would start working again.
- rotation sucks, as the proximity/acceleration sensor seems to be calibrated wrongly, as apps which need the sensor do not work properly (such as car racing --> car goes for one side though the phone is hold horizontally exactly) or display switches orientation too early/late
- If I used Google maps the blue thing points in a wrong direction (maybe 45°)!
Anyone same there?
stephan902 said:
Hello,
apart from several software issues i have following hardware issues:
- vibration stops working from time to time, especially when not having used the device for a day or long. If you shaked the phone it would start working again.
- rotation sucks, as the proximity/acceleration sensor seems to be calibrated wrongly, as apps which need the sensor do not work properly (such as car racing --> car goes for one side though the phone is hold horizontally exactly) or display switches orientation too early/late
- If I used Google maps the blue thing points in a wrong direction (maybe 45°)!
Anyone same there?
Click to expand...
Click to collapse
Do you still have the stock rom on it if so have you tried a restore to factory after its a call to dell
lufc said:
Do you still have the stock rom on it if so have you tried a restore to factory after its a call to dell
Click to expand...
Click to collapse
Yes and yes. Still the same. So i really got a lemon and the Streak usually is a good device?
The vibration issue certainly is a hardware issue that I would replace my phone over, it sounds like a physical problem with the motor, and bad motors only get worse with age.
Sent from my Dell Streak using XDA App
I have felt my vibration button fade or lag at times. Not sure if that was normal. I had it sometimes where it wouldn't work at all. I did a factory reset and all seems to work ok. I still get the laggy vibration when to many processes going on at the same time.
Sent from my Dell Streak using XDA App
When I turn off the A7 I feel/hear a low sound/feeling like a hard drive starting/stopping. Is that supposed to happen or is there something wrong with my A7?
I really don't know how to describe the sound. It is more like something 'moving' inside the A7.
Thank you.
Alice
BTW: How do I register my unit?
I'm guessing what you are feeling and hearing is the haptic feedback vibrate mode...it's normal
durango99 said:
I'm guessing what you are feeling and hearing is the haptic feedback vibrate mode...it's normal
Click to expand...
Click to collapse
I turned off the Haptic and I still 'feel' slight vibration when I turn ON/OFF the Elocity A7. (Feels like something 'moving' inside the A7.)
I don't think you can turn off the haptic feedback that occurs during bootup. It's more or less a system check. I have tried already, but can live with that one instance.
rapcon said:
I don't think you can turn off the haptic feedback that occurs during bootup. It's more or less a system check. I have tried already, but can live with that one instance.
Click to expand...
Click to collapse
So, the "vibration" I feel when I turn ON/OFF the A7 is 'normal," and nothing to worry about?
As I said, it feels like something 'moving' inside the A7.
I just want to make sure there is nothing wrong with my A7 because my 30 day return policy is running out, in case I have to return it.
P.S. In the Settings, there is a (green) check mark next to the Haptic. I unchecked that and still feel the 'vibration' (moving inside the A7), when turning ON/OFF the A7.
alicez said:
So, the "vibration" I feel when I turn ON/OFF the A7 is 'normal," and nothing to worry about?.
Click to expand...
Click to collapse
Yes, perfectly normal and nothing to worry about.
alicez said:
As I said, it feels like something 'moving' inside the A7.
Click to expand...
Click to collapse
That's because there is something moving, that how the vibration is done, it vibrates. Perfectly normal.
alicez said:
P.S. In the Settings, there is a (green) check mark next to the Haptic. I unchecked that and still feel the 'vibration' (moving inside the A7), when turning ON/OFF the A7.
Click to expand...
Click to collapse
As mentioned above. The vibrations on shot down can't be turned off. Heptic feed back can only be turned off for screen presses and the keyboard.
RojasTKD said:
Yes, perfectly normal and nothing to worry about.
That's because there is something moving, that how the vibration is done, it vibrates. Perfectly normal.
.
Click to expand...
Click to collapse
Thanks so much for your time and patience. You say "That's because there IS something moving."
What is moving?
Funny thing is that it baffles my grandson because he has used the Edge and Pandigial tablets and he said when he turned them on or off, there was never that feeling of vibration when they were shutting down. He just wondered why this A7 would vibrate (feeling of something 'moving' inside the case) after he has turned it ON or OFF. Shuffle - would that be a better word?
Just can't describe the exact feeling we get when we turn it on and off. Guess best word would be = short 'vibration.'
He says he thinks something is loose inside the A7 and we might have to send it back as being defective. I told him that everyone here says it is NORMAL, for it to vibrate when after turning ON/OFF. A little more vibration when it has been turned OFF.
I don't think this has anything to do with "Haptic" which is in the Settings (turn On/Off)? Do you?
Does yours do the same - the vibration when turned ON and OFF?
It's just a little motor wizzing inside the unit. It runs when the device is turned on because the system is probably just doing some basic function checks and it's also to let you know the device is on/off. Mine does the same...they all do. All tablets are different so this may not have been the case when using other models
esemelis said:
It's just a little motor wizzing inside the unit. It runs when the device is turned on because the system is probably just doing some basic function checks and it's also to let you know the device is on/off. Mine does the same...they all do. All tablets are different so this may not have been the case when using other models
Click to expand...
Click to collapse
Thank you.
Same sound when A7 is turned off. Correct?
alicez said:
Thank you.
Same sound when A7 is turned off. Correct?
Click to expand...
Click to collapse
That is correct.
This has been happening pre and post Nodo on my focus. If i'm on a phone call for at least a few minutes, then pull the phone away from my head, the phone's display should become active, but it isn't.
Anyone else having this issue or is it time to exchange the phone?
I have the same issue also it seems like I have to press the power button a couple of times to get it back.
Sent from my SGH-i917 using XDA Windows Phone 7 App
I'm also having this issue. Anyone remember if ther were having it pre-Nodo? Just wondering if the update changed something.
Regardless, it's a bit of a PITA.
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
ArcWhistler said:
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
Click to expand...
Click to collapse
How did you do that?
Yeah, ditto that - how do recalibrate the sensor?
Samsung Diagnostic App.
http://forum.xda-developers.com/showthread.php?t=839154
I was pecking around the screens months ago, and there was one bank of tests (multi-touch, red, green, blue, white, battery, etc, etc) that allowed setting and viewing the proximity sensor.
I remember playing with moving my hand closer, and further and watching it change from sensed to clear.
Sorry, can't remember which codes now.
I used the Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
LCD Test - *#0*#
Ok, mine says No Detection. Is there anyway to set the value?
One other thing to note, about the samsung focus specific update regarding disabling the touch sensitive buttons while in a program, that also isn't working for me either. Not sure if they are related, but thought I'd throw it out there.
And as far as calibrating goes, not sure it would help since the problem only occurs while I'm on a longer phone call. On short ones the proximity sensor works just fine.
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
ArcWhistler said:
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
Click to expand...
Click to collapse
Mine says No Dectection. It has Prox Sensor: XXX I've taken my entire hand and covered my phone. NOTHING. When I push SET, It says ProxThreshold :0. Is there anyway to set it manually?
samsung focus post nodo
I believe the prox sensor issue is happening post nodo, I have never had this problem prior to the update... I have been able to fix it temporarily by pulling the battery and starting it up... don't know how long the fix works... got to do some testing... I am wondering if its a power thing as the screen wouldnt work when you plugged it in to power and had on a soft surface....
Still nothing. I didn't want to hard reset since I have Chevron installed. For some reason I did four updates on my phone and don't have a single backup. If I hard reset I'm S.O.L. with Twin Blades and other homebrew apps
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
BooR4dley said:
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
Click to expand...
Click to collapse
It has a big red box. It says No Detection. Prox Sensor:XXX Do I press Set or Reg?
another thing is wrong
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
rockclimbaudiextreme said:
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
Click to expand...
Click to collapse
same problem here. seems like those two sensors are burned
I have two SGS4's. On one, when I place a call, the call screen stays on and it turns off when I raise it to my ear. It then turns on when I pull it away.
On the other, as soon as I place I call the screen goes dark. The only way to get it back is to push the power button and unlock the phone.
The "Turn screen off during a call" setting is set on both phones.
Anyone have any idea what is causing this? Next step is to do a wipe, but that just sucks.
I'm on stock and not rooted.
Thanks!
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Sirchuk said:
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Click to expand...
Click to collapse
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
jprocket45 said:
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Nope, mine is naked for now. I'll have to do a reset today/tomorrow and see if that solves my issue. If not, I'm taking back to the store for an exchange. It's only been a couple of weeks.
To late for me to take it back but suppose to be a update coming soon that does alot of fixes so we will see Good luck like I said reset I did notice fixed it a bit let me know how it goes I'm threw sprint just curious if you have them only reason I ask if it's just a carrier issue with software or something I doubt it but just figured to see who you had lol
Sent from my SPH-L720 using xda app-developers app
Dial *#7353# and make a test
sent from my Galaxy
samersh72 said:
Dial *#7353# and make a test
sent from my Galaxy
Click to expand...
Click to collapse
That's what I was looking for!
Sure enough,the proximity sensor was always on and wouldn't go off.
I'm with T-Mobile and they have a 30 return/exchange policy if you buy it outright, which I had, so it only took about 10 minutes for them to exchange it!
Thanks for the testing code! XDA comes through once again!
Same problem when I'm making a call, the screen goes blank when I put it to my head and when I remove it nothing happens.
I tried *#7353# and the proximity sensor goes of but will not stop..
I'm currently rooted, could it solve the problem to go back to stock?
Possible Fix
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
I have had the same problem over the last 3 weeks and decided to take a gamble. I tightened up all the screws on the device and squeezed real hard on the area where the prox sensor is and poof... it works. I have no idea what was up but I feel like the sensor is loose and the pressure resolved the issue. Many other post have talked about cleaning the area over the prox real good and it works but I think its the pressure that is actually fixing the issue. Anyone else have any ideas? Sorry if this was posted incorrectly, I have never posted before but I felt this issue is a PITA.
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
My proximity sensor works - when I go into diagnostic, it goes green when I bring a hand near the sensor - my issue is that it doesn't seem to notice when I remove my hand and there no longer is anything proximal - until I hit the back button to exit the test. Other than blowing out the earphone jack, does anyone have a suggestion?
Thx.
divche said:
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
Click to expand...
Click to collapse
Proximity sensor
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
I guess what it comes down to is.....for some you can reset the sensor, for some they can blow it out with compressed air, but others actually have to take apart their phone to fix this issue.
marduj5 said:
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
Click to expand...
Click to collapse
hi
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Shohat said:
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
Click to expand...
Click to collapse
Hubris2 said:
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Click to expand...
Click to collapse
i'm sorry. i already tried your first solution and it worked like charm ! thank you ! :good:
HOw to solve, none of this works. How cann i clean proximity?
Hello all!
Anyone else notice that the keypress vibration is insane when typing? I tried SwiftKey and lowered the vibration to its lowest setting and it stays the same. Also tried G Board and it's still the same. I switched the vibration under setting for touch to light but same issue..
Same for me. After rooting and installing a custom kernel...it's possible to adjust vibration via a kernel manager.
Same here. I just put in for an RMA thinking my vibrator is defective because the vibrator is way too strong to be good haptic feedback for the keyboard. Every other OP has very fine tunability for key pressing. The OP5 is over the top! Not sure now if I should proceed with the RMA or not....
JonDeutsch said:
Same here. I just put in for an RMA thinking my vibrator is defective because the vibrator is way too strong to be good haptic feedback for the keyboard. Every other OP has very fine tunability for key pressing. The OP5 is over the top! Not sure now if I should proceed with the RMA or not....
Click to expand...
Click to collapse
Bro that is such a software fix, don't trip, mine vibration is strong on swiftkey too.
Rebel7022 said:
Bro that is such a software fix, don't trip, mine vibration is strong on swiftkey too.
Click to expand...
Click to collapse
Does your vibrator also have a "long decay" whenever its activated? Like when I get a call or press a key, the vibrator almost feels like a spring and it doesn't stop as quickly as it starts.
This is why I felt the my unit may be defective. But it could just be the nature of this new more powerful vibrator. I was just surprised that nobody else (and our reviews) mentioned it until this lone thread.