Xperia V (LT25i ) SoD research - Sony Xperia T, TL, TX, V

Hi!
Several days ago I bought aftermarket Xperia V for experiments and got this infamous SoD bug. This bug is really disturbing and nobody on the web was able to explain it's cause, so I decided to research this strange issue. After several days of testing I found that the root cause of this bug is touchscreen controller, probably due to problems handling deep sleep mode and I2C bus communication. I bought another two LT25i devices with broken screens (whithout SoD), interchanged main boards and voila! - main board from device with bug with other touchscreen/display module works like a charm. It's highly unlikely, that screen controller can lead to such effect, it's a passive LVDS device, but I tried to exclude this possible cause, so I disconnect buggy touchscreen controller flex cable, leaving display connected, and phone works for two days and wakes up many times without problems, no SoD at all.
One more interesting thing: LT25i uses Synaptics S3200 touch screen controller, there are two chip revisions ("A" and "B") and both can be found in this phone, but it seems, that most of stock screen modules using "A" revision and now chinese copies are mostly with "B" revision. Docs about these chips are NDA of course, but I think that both revisions are identical in terms of programming and differs only in some electrical parameters (e.g. voltage range, maximum I2C speed, ADC noise floor etc). In my case SoD was generated only with "B" revision chips, but I have not enough devices for getting reliable stats.
Now I try to find, what kind of electrical modifications will lead to SoD elimination (or worsening), I hope I will post new findings later (experiments with SoD takes days, you know, so this cannot be fast enough).

No significant success so far. I have tried undervolting and overvolting touchscreen controller (2.8 volts and 3.3 volts respectively), make additional I2C pull-up to positive voltage, add capacitors to power rail - nothing works, device gets SoD in 3-30 hours of battery operation. Now I do another kind of test: I have desoldered S3200A controller from the broken touchscreen flex and replaced S3200B on working module with A version (this is a really complex task and cannot be done without experience, proper tools, air soldering station and epoxy resin removing fluid, so it cannot be classified as user-level patch) and now I will wait day or two for SoD again. Stay tuned.

Glad to report, that phone works fine for three days now, - no SoD at all. Seems that S3200 touch controller with "B" revision is the root cause of this kind of problem, so If you order a replacement display module it will be a good idea to ask seller about chip revision and buy only ones with "A" mark. I hope my research will help someone, cheers.

Related

Xperia Bluetooth and Wifi cannot be switched

I am facing several problems with my xperia x1 that a purchased a couple of months back, it has no warranty
1. Bluetooth
the bluetooth of the deice is not functioning and cannot be switched on, i have tried hard reset and several roms but it has not worked. when i switch on the cell and go to comm. manager it shows that bluetooth is working but when i search for devices it gives error after some time and switches off
2. Wifi
the problem is same as that of bluetooth, it is off and remains off...
3. Overheating
the device overheats during charging, takes a long time to charge.... the battery only lasts few hours... the device remain slightly heated even when it is switched off... i believe that the problem is linked to the above two problems, but once i have searched other threads, i believe others are also facing this problem but they do not seem to have problem with wifi or bluetooth
4. Cracks
the body is cracked at three places, near the camera, and the inside battery cover
used, t300, k500, k750, w880, w960 (still using) and now this one, but this seems to have a lot of problems for no reason... i have never had any problem with any of the sets that i have used before
please if anyone can help and atleast resolve the heating problem, cause the set is unusable if it has battery time of arount 6 to 7 hours.... if theres any hardware issue, can it be repaired? if not, im afraid i ve made a dead investment,
ooook NOW its X2
now i got x2, its brand new
but the video playback (youtube) isnt sharp nor smooth
what do i do/nstall to make things better
rest is great
i wish it had a more powerful processor
but HELP

Has anyone tried Samsung warranty repair for GPS issues?

Has anyone tried getting their Captivate repaired under warranty for GPS issues? I've tried every fix out there except prying the connectors up (at least until I get outside the 30 day exchange window) and have spent too many hours on the phone with Amazon, AT$T, and Samsung tech support. I've tried all 3 of da_g's GPS fix updates, the factory "GPS Restore" crapware fix, LBtestmode, and a handful of ROMs. The problem persists that when driving and using Google Navigator it will snap to the wrong roads, think I've kept going after making a turn etc. and just generally annoy me.
I'm now on my 3rd Captivate (only 2nd for GPS issues though) and none of the parties involved are willing to exchange for a new one again. I have a return label in hand already to return to Samsung for warranty repair but I would be without my phone for 6 business days. I would have an easier time living with this if I had some reasonable expectation that it might actually work, but somehow I expect that they would either
Pronounce it problem-free and return it right back to me still broken, or
Just replace it with another Captivate with an equally wonky GPS
So... has anyone tried sending their Captivate in to Samsung for repair with any degree of success? Is it worth bothering with?
It's a 1010 build now running Cognition for what it's worth. Best performance so far was with Cognition 3.04 and da_g's "control plane" GPS fix, with which I can get a 5m accuracy fix with 5 sec. TTFF (indoors!) but it's still all over the place on the road. Plugging in to the car adapter as suggested elsewhere seems to help slightly.
I sent mine in for repair. Here's the TD;DR story.
I'm running Andromeda 1.0 with the KP1 modem, build 1008. I've done a lot of testing since that post and GPS has remained great. It locks fast outdoors, indoors and while moving; it tracks turns, stops and starts perfectly and it doesn't get confused in areas with tightly packed parallel streets (using CoPilot--I haven't tested other nav apps). Tonight I ran GPS Test Plus with the speed display on and the phone mirrored exactly what was on the speedo through starts stops and turns for an 8 mile trip.
Edit: just wanted to add that I never mentioned GPS problems when I called Samsung to get repair setup.
opcow said:
I sent mine in for repair. Here's the TD;DR story.
I'm running Andromeda 1.0 with the KP1 modem, build 1008. I've done a lot of testing since that post and GPS has remained great. It locks fast outdoors, indoors and while moving; it tracks turns, stops and starts perfectly and it doesn't get confused in areas with tightly packed parallel streets (using CoPilot--I haven't tested other nav apps). Tonight I ran GPS Test Plus with the speed display on and the phone mirrored exactly what was on the speedo through starts stops and turns for an 8 mile trip.
Edit: just wanted to add that I never mentioned GPS problems when I called Samsung to get repair setup.
Click to expand...
Click to collapse
Good to know that there's at least a little bit of potential that it might come back fixed, thanks. For all the bellyaching about the GPS issues all I had ever seen were homebrew fixes and reports of one-for-one exchanges, but little to no mention of actually giving it to Samsung to fix.
well i got gps problem with my captivate also and worst im outside u.s. using att captivate
for waranty its be months..... i want to flash new rom but scare brick my phone.
i brick it onces cause install wronp app but thanks to [mcord11758] i able 2 restore
it back. by the way my build no is 1007 on its battery hear they say very hard 2 brick???
Case White said:
Good to know that there's at least a little bit of potential that it might come back fixed, thanks. For all the bellyaching about the GPS issues all I had ever seen were homebrew fixes and reports of one-for-one exchanges, but little to no mention of actually giving it to Samsung to fix.
Click to expand...
Click to collapse
I have seen a couple of others mention that they had working GPS after repair and I've seen quite a few report that refurbished phones they received from AT&T warranty service had good GPS. The software fixes do help, but it seems pretty clear that the real fix requires a hardware change.
Here's the repair log (dates and times removed to protect the paranoid):
Code:
*##/##/#### //##:##:## //RSI_SHIP2 //
*##/##/#### //##:##:## //RSI_TECH18 //
PASSED FINAL QC
*##/##/#### //##:##:## //RSI_TECH15 //
F72-REPLACED PBA, SENT TO SW---LSC---
*##/##/#### //##:##:## //RSI_TECH15 //
F18-REPLACED INTERFACE CONNECTOR (IFC300), RAN EDL, SENT TO SW---LSC---
*##/##/#### //##:##:## //RSI_TECH3 //
REPLACED TIB
*##/##/#### //##:##:## //RSI_TECH2 //
SW
Original Problem
Technical Inquiry
Power
Intermitted Power Down
Problem Found
BAD BGA COMPONENT
WARRANTY, REPLACE PART
Solution
Replaced PBA
Passed All Functional Testing
*##/##/#### //##:##:## //RSI_TECH18 //
PASSED FINAL QC
*##/##/#### //##:##:## //RSI_TECH15 //
F72-REPLACED PBA, SENT TO SW---LSC---
*##/##/#### //##:##:## //RSI_TECH15 //
F18-REPLACED INTERFACE CONNECTOR (IFC300), RAN EDL, SENT TO SW---LSC---
*##/##/#### //##:##:## //RSI_TECH3 //
REPLACED TIB
*##/##/#### //##:##:## //RSI_TECH2 //
SW
Mine is currently being fixed by Samsung for the following:
- random shut down issue
- random crazy home button acting like its getting pressed multiple times without being pressed
- horrible GPS
Build #1008, phone was shipped out Wed and arrived there Friday afternoon.
I'll update as soon as I get it back.
Got my Cappy back from Samsung yesterday, they replaced the "TIB", whatever that is.
So far today I haven't had a single random shutdown or crazy home button. I also tested out the GPS breifly earlier and I seem to get a better lock and it actually stays on course for the most part.

GPS remarkable observation

Guys,
I spent 2 weeks of holidays (my wife almost left me for that) mostly trying to find out why GPS performance on my P970 is so poor, losing satellites fixes every so often and sometimes no fix at all although 'seeing' satellites. I did not find a 'real' solution, even after tests on both mostly Huexxx 7 and lately boype's 0909, too.
Best results now on boype's 0909 CM7 but with adapted gps.conf and gps_brcm_conf.xml. Nevertheless, the result is still disappointing, far away from satisfying.
However, during all these checks, I found that satellite's receiption is depending on the way I hold the device in my hands, at least on MY device. Whenever I hold a finger on the top left of the chassis (just above the location where the GPS chip is located, see pictures), then receiption improves by 0 up to 14 db (!!!).
Also the number of 'seen' and 'used' birds increases from 6 to 10 easily!!! However, the fix did not become more stable through that.
Pls check on your devices if you can verify the same behaviour.
If so, what could be the reason (i do not put any pressure on the device)? And is there anything that we can do to make this improvement permanent, i.e. put a piece of 'aluminium foil' between the back lid and the device or something similiar?
Let me know your remarks, guys.
No problem at all. Riding on the tram right now. Fix on 12 in few seconds. Sure it's not because of your position? And 6 is enough to fix the position.
@eighty-four
I appreciate your info, and you are surely right it is depending on my position. My question was a different one though: Do you observe the same reaction as soon as you put the finger on top of the device; i.e. increase of signal strength?
BTW You attached an impressive picture, would like to aks you are you still on AOKP beta 1.1 ICS 4.0.4 and how do your files gps.conf and gps_brcm_conf.xml look like? Can you share them?
AOKP 1.1, no any GPS fixes
Hard to say about reaction while on move. But didn't noticed any noticeable changes.
Can't check now - I'm in home.
I've been using Marvel v9 since released, with the GPS "Tweaks" installed too.
I'm getting GPS signal, sometimes really fast, some others i need to wait for a couple of minutes (maximum 3 minutes).
There are certain times though, that it doesnt lock no matter what, just like in your situation. It manages to find many sattelites (7+) with an average decent signal strength but it refuses to get a gps fix location.
I believe it has to do with the temperature of the chip (i couldnt get easy GPS fix at winter) because now that summer passed by and used my GPS a lot, i had no issues... might be the clouds, might be the stars alignment and zodiacs ... i really dont know.
It's not that accurate and fast though for city driving. Some turns are being announced way too late (Sygic Aura) and the error treshold is about 10meters mostly, rarely goes down at 5meters.
I guess it's a chip manufacturing bull**** rather than a "case construction" or antenna problem.
@morx
I just wanted to check if others can verify better receiption when holding finger on top.
I agree it seems a hw or engineering defect, nevertheless I am trying to optimize the settings in order to compaensate at least partially.
Interesting you mention the temperature: In my research I came across a relationship between temperature and gps accuracy. Our (and any other gps chip) uses a oscillator hw module for precision timing. These oscillators' accuracies depend on the temperature and are measuered in PPM. There is also a setting in the gps_brcm_conf.xml that refers to this, it is "FrqPlan". The usual value in CM7 is "FRQ_PLAN_26MHZ_2PPM_26MHZ_300PPB". However, other values do also work, like "FRQ_PLAN_26MHZ_2PPM_26MHZ_100PPB".
You can check details in THIS post.
Would be interesting to determine if different values lead to better results.
I had no clue that chip temperature had a side effect on GPS fix !!
When i was writing my concern about that, i was feeling stupid until i saw your redirection to that post...
hmmm there are many factors which can be put on the table about optimization and troubleshooting.
Later on, i'll give a try keeping the cellphone with both hands, different angles, one handed on top/bottom etc...
Interesting thoughts.
I'm on CM10 nightly and always had blazing fast fixes until yesterday. I activated GPS in my car and after 3 minutes it fixed (in Osmand), after some more minutes the fix got currently lost.
Due to my big custom 3500 mAh battery I couldn't place my phone in the cradle therefore I simply laid it onto my dashboard. Maybe because of this the signals were harder to receive.
I will switch back to the normal battery today and try to test your variant.
Sent from my LG-P970 using xda app-developers app

[Q] Issue with Navigation apps and power fluctuations

Hi, I'm pretty sure this is a unique or rare situation I've experienced, so I'm starting a new thread, but will endeavour to find similar issue threads.
On my motorcycle I have mounted a Brodit powered cradle for my Xperia Z. I figured it would be the ideal way of providing power to the phone while I travelled, and would allow me to use the phone as a Sat-Nav, utilising one of the many sat-nav apps (Google's offering, mapquest, copilot etc etc). Using the Brodit allows full use of the waterproof attribute of the phone - no socket ports need to be opened, and the phone doesn't need to be in a transparent case in inclement weather to prevent damage. I chose the Xperia Z (over other phones eg HTC) with this usage in mind.
It's worth nothing that I had a previous similar setup for my HTC Desire HD: without the powered mount, but using the charging socket and a transparent case over the phone for rainy days. It worked perfectly.
However - I currently am experiencing the following issues with the Xperia Z setup:
Firstly - The Brodit mount is 'not' weatherproof. (this is not Brodit's fault - it's not marketed as weatherproof) It provides power to the phone perfectly, until the first bit of rain, and then it starts to fail - either cutting out completely, or not providing enough current to keep the phone charged while the GPS / Mobile Data / Sat-Nav-App systems are turned on. (Previously it would provide enough power to increase the battery charge even while all the navigation systems were active). This is something I shall look into but I'm not really aggrieved about it - the cradle is NOT sold as an outdoor item so I'm not going to blame Brodit for this. I suspect that the issue is water getting into the 'spring-stud' connections and reducing the current flow. I'm going to see if I can adapt these connectors. If anyone has any further ideas or suggestions for better powered cradles too - I'd greatly appreciate it!
Secondly - and this is the main issue - when the power supply fluctuates (see above) the Sat-Nav Apps behave in a highly irritating manner : They instantly kill the viewport (it goes black), and also forget the current GPS location coordinates, and forget the viewport display setting: ie - show my current location in top down or perspective viewpoint and viewpoint relative to 'North'. When the power returns, the viewport, depending on how the app is being used, either returns to the start of the journey, or to a point in the journey where it remembers, but always loses the current location viewpoint settings.
This is obviously highly distracting, firstly you instantly lose your whereabouts which is dis-orienting, and secondly you then have to stop and reset all the settings so that the sat-nav display is back to doing what you want it to do. On a motorcycle this is further aggravated with the need to remove a glove in order to control the phone. On a recent trip to France I had this happen no less than 5 times in as many minutes right at the start of the journey.
It should be noted that I wasn't using the GoogleNav system in full directions mode. I find this mode misbehaves terribly if you're trying to use a customised route (see below for more info), and so I tend to load up my customised route so that it displays over the maptiles, and then I either just center my viewpoint on my location, or utilise the 'Preview' mode and again, center the viewpoint on my location (this mode displays a useful 'current direction of travel' arrow on your location).
Has anyone experienced issues like this, and if so - did you solve them? Or does anyone have any ideas for how to get into the configuration settings so that I can turn off the screen blanking and signal losses when the power fluctuates?
Thanks
Notes on Customised routes in Google Nav:
As I noted in this Google Product forums thread (just in case anyone else is involved) : https://productforums.google.com/d/msg/maps/DwPoT0pklas/sG0-sFYozT4J :
When in full 'Directions' mode, Google Maps a) doesn't poll your location accurately or often enough when slip-roads (off-ramps) are involved, and re-calculates the route to the next/final destination every time this happens - thus abandoning your carefully planned route.
So - I take it no-one has seen a similar issue or knows of a way to stop Google Maps losing all it's signals when the power is cut off?

Calibrate accelerometer and/or gyroscope

Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Info
vetko said:
Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Click to expand...
Click to collapse
factory Reset ur phone and then use PC companion app to Repair Firmware...
this can wipe current data and install fresh firmware on ur device
:good:
Hi,
I have the same problem. Only the x axis of the accelerometer seems to be affected : it show a value around 1 instead of 0 while the phone is sitting flat. Y and Z display normal values.
All the software solutions I have tried have had no effect at all... It seems the built-in test reads raw data from the accelerometer. It is hard to imagine how this can be a hardware problem though...
Anyway, in my case I believe a software fix (x=x-1) would do the trick but I have no idea how to do such a thing ! Any help ?
@vekto : Have you solved the issue by any chance ?
Would anyone care to try the accelerometer tests and post their results ?
Typing *#*#7378423#*#* will get you on the service menu. The two significant tests are "accelerometer" and "gyroscope".
I'd post some screenshots myself but I'm not allowed yet...
I'm having the same problem now. It seems one axis is affected. Haven't found a way around so far. This is sad because it affects the images taken with Google Camera Sphere mode. The images are badly aligned together with glitches in between. My phone wasn't like this before.
Either a SW fault - might be able to calibrate with GPS Status & Toolbox app, for example - or a FW fault - and reflashing ROM might help (highly unlikely) - or HW fault - the sensor has moved on the board (which is a bad sign anyway, might be on the way to disconnecting itself).
I sent mine to Xperia Care and got it back with the accelerator fixed. Still unclear if it's a HW problem...
It came back with a white spot on the screen (near the power button) though... so I sent it back again
I'm also having issues with the gyroscope. Installed Bubble app to calibrate the gyro. It showed the gyro was of a couple of degrees. Unfortunately the bubble app calibration doesn't work in a game like Need for Speed. It's very difiicult to achieve good times in the game right now since I have to hold it tilted to the left to go straight ahead.
So if anyone has a fix or workaround... Please do post.
Same problem, Seems after factory reset whith wipe dalvik cache.
any solution?
02nd March 2017, my autorotate has completely stopped working, restart, safe-deposit and reset do not fix. Diagnostics show Gyroscope Light Sensor and accelerometer failed testing, 3 years of same issue, surely there must be a fix that works by now?? ( please note, " turning it off and on again " does not fix it )
Helps Please
I have the same issue. Since last week, gyro, accelerometer, light and proximity sensors stop working. I've tried reflashing stock ROM without success. I have not warranty (almost 3 years old), so I even try to disassemble , disconnect an reconnect every flex (I don't know exactly were the sensors are located on the board). After that I get almost 8 hours of fully functionally sensors and then, they stop working again, so I'm almost sure it's a hardware issue.
Same problem for 3 years
I'm just now getting around to doing something about this. As my power button stopped working I can't post requested screenshot without going to the pc. I have been shopping new (fall 2018) phones after having the Z3+ since release. In my research I'm finding the phone still is better than Samsung, LG, and the pixel3 for me because the 3.5mm phone jack is mandatory for me using my device with an i-rig midi requiring both that port and the USB at the same time. I'm going to do everything I can to keep using this phone till it falls to dust. It's one of 4 Sony I've bought since the day Z1 came out of t-mo. I look forward to testing solutions. :good:
Some time after my post, I bought a new jack/proximity sensor flex and replace it. This solved the issue, but weeks later, the bottom portion of the touch screen becomes unresponsive. May be I have done something wrong... may be programmed obsolescence...
Hi I'm facing a problem of my gyroscope I don't know which one is not working a gyroscope or accelerometer. My gyroscope is so delay when I play pubg mobile and I can't also calibrate my Gsensor it always says FAIL but I put in a perfect flat surface please please please help me with this problems

Categories

Resources