Hey guys,
I've recently swapped my Z2, from a carrier locked; to one that's unlocked from Sony. Trouble is, the unlocked Z2 seems to be defective. The haptic feedback is super weak, to a point I can't tell if the motor is working. The thing is, if I perform a repeated action, such as tapping the back button (furiously), the vibration motor will then pick up momentum and start to vibrate properly. I've compared the two Z2, and the other Z2 (locked one) is performing as "expected".
So far, I've two areas/actions that are lacking in haptic feedback; typing on the stock keyboard (even though I've set the vibration duration to the default level), and the navbar buttons (back/home/recent) give a very very faint feedback.
I've ran several tests, including the ones from the service menu; and those worked wonderfully; the device would just vibrate right away. The device also has no problem vibrating when receiving phone calls or texts.
Just how many different vibration motors are in the phone? What could be causing weak haptic feedback?
in the Z2 there is 1 viabrate motor to my knowlage,
it seems your device is defective and id recomend you try to get a replacement
the exact problem seems like the motor is stiff, or over magnitised of sorts
Sent from my D6503 using XDA Premium 4 mobile app
hidea said:
Hey guys,
I've recently swapped my Z2, from a carrier locked; to one that's unlocked from Sony. Trouble is, the unlocked Z2 seems to be defective. The haptic feedback is super weak, to a point I can't tell if the motor is working. The thing is, if I perform a repeated action, such as tapping the back button (furiously), the vibration motor will then pick up momentum and start to vibrate properly. I've compared the two Z2, and the other Z2 (locked one) is performing as "expected".
So far, I've two areas/actions that are lacking in haptic feedback; typing on the stock keyboard (even though I've set the vibration duration to the default level), and the navbar buttons (back/home/recent) give a very very faint feedback.
I've ran several tests, including the ones from the service menu; and those worked wonderfully; the device would just vibrate right away. The device also has no problem vibrating when receiving phone calls or texts.
Just how many different vibration motors are in the phone? What could be causing weak haptic feedback?
Click to expand...
Click to collapse
I have exactly the same problem with my UK unbranded Z2..Haptic feedback works perfectly on all diagnostic tests, phone ringer, notifications and alarms, but only intermittently with stock keyboard, Swiftkey and home buttons.
I think its a software problem, I'm going to flash the .402 German firmware later today to see if that cures the problem...If not it's going back to Amazon.
hidea said:
Hey guys,
I've recently swapped my Z2, from a carrier locked; to one that's unlocked from Sony. Trouble is, the unlocked Z2 seems to be defective. The haptic feedback is super weak, to a point I can't tell if the motor is working. The thing is, if I perform a repeated action, such as tapping the back button (furiously), the vibration motor will then pick up momentum and start to vibrate properly. I've compared the two Z2, and the other Z2 (locked one) is performing as "expected".
So far, I've two areas/actions that are lacking in haptic feedback; typing on the stock keyboard (even though I've set the vibration duration to the default level), and the navbar buttons (back/home/recent) give a very very faint feedback.
I've ran several tests, including the ones from the service menu; and those worked wonderfully; the device would just vibrate right away. The device also has no problem vibrating when receiving phone calls or texts.
Just how many different vibration motors are in the phone? What could be causing weak haptic feedback?
Click to expand...
Click to collapse
I just flashed the .402 German firmware and also did a 'repair my device' in PC Companion before flashing, and the haptic feedback is still weak, not functioning properly and erratic. Must be a hardware issue.
I'm returning the phone for a replacement.
Related
I have got the problem that sensors turn out my screen after calls start (incoming/outgoing) and it does not activate again when I want to end the call.
I have realized that after a call is started and the phone is moved (e.g. after typing a number, dialling and then move the phone to your ear) that this (or actually any movement) locks the screen.
I have realized that the movement actually activates the 'dial pad' (just as you would press the icon on the screen during a call) but somehow also fully de-activates the screen. You can get the screen activated again only by sliding the hardware keypad out. Then you can press 'x' on the screen to get back to the normal call screen (and then end the call normally).
I have got the 2nd SK17 now and it has got the same issue regardless which firmware I use (branded 4.0.A.2.335 from vodafone, 4.0.A.2.335 Generic or 4.0.2.A.0.58 Generic).
Anyone else got this issue and has got a solution.
Same here. its because of the light sensors.
http://forum.xda-developers.com/showpost.php?p=18404603&postcount=6
heres a guide to turn it off
Thanks for the quick response. Much appreciated.
However, I am afraid this does not resolve the issue. When applying as described in the guide the screen is de-activated straight after answering a call (without moving the device) and even when sliding the hardware keyboard out and pressing 'x' on the screen (to return to normal call screen) and then close the hardware keyboard again the screen is de-activated straight.
Ending calls now is only possible when the hardware keyboard is slided out.
Before applying as described in the guide at least the screen returned to be active after sliding keypad out, pressing 'x' and sliding keypad back in (and then not moving the device).
Therefore I have reverted back to what is was before for the time being.
Any other thoughts, hints, help.
----------
UPDATE 2011/11/27:
I have got my SK17 exchanged again (got the 3rd one now) and on this one it does not occur respectively call screen and sensors work perfect. Finally SE or vodafone seem to fix it on newly produced devices.
Hi, I got my phone this morning and no doubt its a very good phone, but...
Is anyone else having trouble with the speech recognition. When I speak into it the mic graphic seems to indicate it's getting good pickup, but then the waveform it displays after is very flat and the recognition accuracy is very poor indeed.
Also I'm finding the capacitive buttons very unresponsive.
Any hints or tips?
I don't use speech recognition so can't help you there but I agree the capacitive buttons are a pain. I find a firmer press or a slight slide upwards works best. You do get more used to them the longer you use the phone but for me they are the biggest niggles on an otherwise fantastic device.
Remove the screen protector that came with the phone from the capacitive keys.
They should get way responsiver after that.
I was wondering as well if removing screen potector would increase capacitive buttons responsiveness. Anybody tested it already, or is changing screen protector in near future?
I use the voice recognition all the time. Do you have a weird accent?
For the buttons:
Have you tried just swiping them from the transparent bar up?
After I started doing that I had no issues, and they respond just fine. If you want to just do the touch method, aim for between the screen and the silver dots, but I find the swiping method easier and it's a no-fail way
The voice recognition:
Only used it a few times, and only on my X10, haven't tested it on the S yet.
I have 2 problems also with the xperia s, the battery life and the unresponsive capacitive buttons. Its really a hassle always thinking if it would register after hitting with your thumbs. Is there really a solution to this? Would the ICS upgrade be of help when it comes out?
Rashkae said:
I use the voice recognition all the time. Do you have a weird accent?
Click to expand...
Click to collapse
No I used to use voice on both my samsung and my htc all the time with no problems.
Actually, this is the first phone that allows me to use speech recognition to call my wife, all other phones failed to do it, so I rated the mic as very good but didn'tell it to the wife...
I don't have any of the niggles with voice recognition or the capacitive button sensitivity (to me they are the same sensitivity as the one's on the galaxy s2 which I got used to). The problems I've experienced so far are -
- Video focus problems
- Audio playback clipping when using google navigation.
Hopefully these are bugs that will be ironed out soon via firmware.
Problem with network and sms tone
the sms tone dosent ring as an sms arrives and frequent loss in network signal, PLZ HELP
Thread closed please don't bump old threads which have no relevance to your problem. You can start a new one in the Q & A section but not in the General section.
I just installed AOKP Unofficial 4.2.2 from this thread.
If I simply make a call, the proximity sensor functions as expected and near perfectly (I think there's slightly too much lag between removing the phone from one's ear and the screen coming back on... but not unbearable). With the keypad shown, I've found the behavior to be quite unpredictable. On my first call with the new ROM, I called my company voicemail and between inputting my password and cradling the phone, I could hear a bunch of key presses occurring. It ended up disconnecting the call. This is quite reproducible for me.
I'd like to know if this is a reproducible issue, intended function, and/or bug (which I will report if others can verify).
Method:
- Dial a number
- Set phone on table
- Put hand in viscinity of top of the phone
- Observe screen turning off and on as you move your hand over the sensor and then away
- Pull up keypad
- Repeat hand test and observe that the screen is not predictable
In trying this several ways, there's either a lag in detecting proximity, or it's just flaky. I actually find it really hard to reproduce consistently. Sometimes it actually will turn off (I can see peripherally that if I put it to my ear), however if cradling (with phone still well within what I could call "proximity" to my face/ear), it will dial numbers. In putting my hand in various positions over the phone, sometimes it turns off, sometimes not. With the keypad hidden, it turns off reliably 100% of the time.
The biggest difference I can reproduce is that if you put a single finger over the full width of the top of the phone (over the HTC logo -- the sensor is just to the left of the logo), it will reliably turn off the screen without the number pad, but not with it. I get that the sensor probably needs to account that one's fingers will be pushing on the screen to enter numbers, but something directly over the sensor (simulating an ear pressed to it) should turn it off even with the number pad shown, I would think.
Thanks for any suggestions of if you'd like any further information.
----------
ETA: S-off, unlocked bootloader, AOKP: aokp_jewel_unofficial_Mar-12-13, baseband 1.12.11.1210, Android 4.2.2.
Yesterday I rooted my UK SGP612 without unlocking the bootloader. It took a while to get done, but eventually got there and I now have a rooted 4.4.4. The only problem is that haptic feedback seems to have mostly disappeared in the process.
What doesn't work:
Vibrate on touch doesn't work
Sony keyboard vibration doesn't work
What does work:
Google keyboard vibration works
Soft nav buttons vibration works
Test vibration in diagnostics works
Swiftkey vibration works, but only if I increase the duration from the default 10ms to 50ms
I'm fairly certain it all worked prior to rooting, but even a factory reset and a reflash of the kernel has failed to fix it. One thing that did catch my eye is that in the settings for the google keyboard the intensity can be set and this defaults to the system setting, which seems to be 0.
UPDATE: I just found that the Sony keyboard also works, but only if I crank up the intensity to almost max.
So does anyone have any idea what might be causing this issue and how to resolve it?
Hi guys, I just got the N7.1 last week, with Android 10 already on it (December update). Both are new for me, so I have no idea if these are Nokia or Android issues, but hopefully you can help me:
1) Ring volume is very loud! Even the lowest setting is still way louder than I've ever had before. Is this normal?
2) On Mario Kart Tour the sound is awful. Even on low volumes the game produces a loud crackling sound. Might be very game specific, but it's the only one I play atm
3) On the lock screen the upperleft corner of the statusbar shows the carrier. When you go to home screen this changes to clock. Quite often the carrier 'sticks' and also shows on home screen. I then have to go back and forth a bit to get the clock back.
4) Not always, but like 80% of the time, when I unlock the phone directly with my fingerprint, the home screen will show. This sounds quite normal, but I mean that it minimizes any app I was working with / had open while the lock went on. I've never had this behaviour before: it used to just go back to the app I was using.
5) Sometimes I get some serious lag while typing, until now I only notice this in message boxes on forums, like the one I'm typing in right now. During typing the letters stop appearing and everything seems to freeze. Then when I hide/lower the keyboard on my phone, the typed letters appear instantly and I can continue.
Cheers!
There are many bugs in the Android 10 update Nokia released. There are multiple topics about them in the Nokia 7.1 subforums. I know audio issues with games and other apps is one of them. As far as I can tell, Nokia has not acknowledged these bugs (even on their own forums) and there is no ETA on fixes.
I now see some reports of crackling sound, but do you guys have the other issues as well? There are a lot of annoying bugs!!
Yes!
All the other issues you face are common. The loud ring volume you acknowledged is common too and i too, face it and get disturbed by it too
The crackling sound you get in games is common too.