Related
Hi All
I have just replaced a faulty microphone in my XDA o2 and when I put it all back together Iand reset the device it is now showing a reversed mirror display What have I done wrong and can it be easily fixed ?
Thanks in advance
waam
if hardreset dont help it sounds like you put the screen upside down
Hmm....
Rudegar said:
if hardreset dont help it sounds like you put the screen upside down
Click to expand...
Click to collapse
I didnt actually remove the screen .. I unfolded the mainboard and inserted the replacement mic and closed it all up and now it is a reversed image it appears as if the I am inside the O2 looking out I had not removed the LCD at all from the board so it is in the correct way just not showing the correct image i will try and post a picture if you want
Cheers
Waam
Mirrored Display
hello XDA community,
I have here an imate Jasjar which after a screen upgrade is displaying the image reversed. It did not begin like this,
Upon first booting up the device after screen upgrade, all was fine, screen displayed normally. About a week after this, the screen began flickering, not on/off, but instead, reversing the image shown on the screen. (a mirror) effect. I did not know what to make of this. I delt with it best I could.
A day or two after this flickering began, the screen began to remain in this reversed image mode, which I did not enjoy. The same day, I had dropped the JJ into a tub ( a pretty hard fall), but somehow, by the grace of god, the water failed to enter the inside of the Jasjar.
After the fall, I had noticed that the screen had stopped its flickring antics and remained normal for about a week and a half. It is now displaying a reversed image only.
I now am unsure of what to do, I searched throughout the XDA forums and discovered that performing a hard reset should repair this.
I suppose my main question is, is there a registry tweak I can perform to revert the displayed image back to its original state
Many thanks to all who respond.
John
EdmundsProductions
DeserteDNJ.com
as far as I know, both of your devices are probably dead. Back in the time I was repairing old Ipaq's the mirrow effect was epically called "The mirrow of death" and meant that the display controller (a chip) has failed.
I'm not 100% sure, but I don't think you have many chances to bring them back. Maybe this is not your case, but anyway chances are slim.
thats actually a very interesting idea. If you can mirror them via software, you can fool the device into working again
solution ?
Any solution to this yet ?
Is anyone working on that brilliant idea of that mirroring software ?
I've been having the same problem for almost 6 months now. But for some reasons I am surviving with my O2 XDA EXEC. Now, I can hand my brick to friends without being concerned about my personal messages being read.
However, I have found something. When I charge my phone with a motorola charger, while on charger, the screen flips back to normal. So, my best bet- it is actually a tweeny weenie IC not doing what it is supposed to do.
mirror solution!
Tape the phone to your car's dash and use it as a H.U.D.!!!
hey.... maybe I am on to something here mmmm.....
Frogger said:
Tape the phone to your car's dash and use it as a H.U.D.!!!
hey.... maybe I am on to something here mmmm.....
Click to expand...
Click to collapse
Does anyone know how to make the PDA do this, I've searched everywhere for a software solution but to no avail.
I want to add a second screen to my PDA (piggybacking on the existing screen) but with an inverted display. This way I will have a normal touchscreen display for entering data and an inverted display for HUD use.
I'm aware that when this happens as a fault it is normally due to a loose display connection causing one of the outer contact to come loose, but I'd need to know which 'wire to cut' to force this fault.
Any help would be greatly appreciated.
I need help please..
after installation of several wm6.1 roms here,
my touchscreen isnt precise already.. it seems to be misaligned?
i always need to aligned the screen, but it dont work anymore..
whats wrong with my fone? is it because of the ROM or hardware error already?
thanks.
rizortiz said:
I need help please..
after installation of several wm6.1 roms here,
my touchscreen isnt precise already.. it seems to be misaligned?
i always need to aligned the screen, but it dont work anymore..
whats wrong with my fone? is it because of the ROM or hardware error already?
thanks.
Click to expand...
Click to collapse
BEFORE YOU RAISE YOU QUESTION,
1. did you make a search for an answer yet?
2. you need to provide details for you problems inorder to let other seniors here to help,
for example... which rom, how is the history....what had you done to it.......
ok ?
[QUOTE=..................
the same problem (i think it is the same) here..
it occurs generally while i am playing games and typing so many letters for sms's.
the problem has been existed since i have bought my prophet. the problem was there on official wm5 rom. using wm6 or 6.1 roms didn't fix it, but decreased a little (or i quit playing games so much).
since i couldn't enter the pin to unlock, two or more times i couldn't make an urgent call, then i soft reset it..
i thought that it is affected by heat changes when the battery consumption is high or when i hold it in my hand very long time. i also thought that it is a hardware problem, but not sure.
recently, i do not use my prophet so much, then it hasn't annoyed me for a long time..
sory,
i should have defined the problem mentioned above:
- when i touch a point on the screen by stylus (or any other way)
it assumes that i touch some pixels left of the point i intend.
- in a few minutes, sometimes this shift increases about one or two centimeters, sometimes it stay one or two letters left of the intended letter on a standard keyboard.
- this shift is much more on the right part of the screen, it gradually decreases towards the left side, and finally it exact macthes that your pressing point.
think of a rubber band, fix one end onto the left edge then stretch it to the right, this is the touch screen you see. release it to shrink it, now this is the way that it assumes you touch on it.
- after soft reset, generally the problem's gone, sometimes not.
- after re-aligning the screen, it's gone, but when somehow the cause gets remedy after a while, it occurs reverse way, then you should correct the screen alignment again (
screen misaligned
I have the exact same problem for years, I would say ever sice I got it. It's happens just like atakatas says.
Just something I noticed, It happens to me when I keep it in my leg pocket, and usually I don't soft reset nor realign the screen. I used to do that, but then I found out that waiting a few seconds it would get back to normal.
So I never asked anything arround here because it really didn't look like a software problem. I would say it is climate sensitive
Cheers
I have a problem with my gtab. the screen is kind of flockering. Not the problem with the screen flicker when the tab is low on ram, which was solved with the latest kernel. It is some kind of ... grainy effect. I notized first when I read a Pdf file where the background was black and the letters white. The letters were a little bit moving, as if the pixel were not constant. then I notized it is the same in the taskbar when on landscape, but not on portrait. the numbers of the time were grainy. furthermore the letters of the Apps in the Appdrawer, grainy but only in landscape, not portrait.
How can I solve this problem?
rom is Infamous AOKP latest kernel 1.9.1
should be p7510 - p4 wifi
lordofazeroth said:
I have a problem with my gtab. the screen is kind of flockering. Not the problem with the screen flicker when the tab is low on ram, which was solved with the latest kernel. It is some kind of ... grainy effect. I notized first when I read a Pdf file where the background was black and the letters white. The letters were a little bit moving, as if the pixel were not constant. then I notized it is the same in the taskbar when on landscape, but not on portrait. the numbers of the time were grainy. furthermore the letters of the Apps in the Appdrawer, grainy but only in landscape, not portrait.
How can I solve this problem?
rom is Infamous AOKP latest kernel 1.9.1
should be p7510 - p4 wifi
Click to expand...
Click to collapse
If with grainy you mean that you can see the pixels, that is normal as or device doesn't come with the highest resolution. If it is really moving, that would be odd and is not something I see. Did you check whether it is also present on stock ROM?
Verstuurd van mijn GT-I9000
I know the screen. I mean not the normal grainy letters coming from low ppi.
The pixels are definitly moving, not all pixel of a letter/number only some of them.
I didnt see something on stock, no.
Uploaded a video:
https://www.dropbox.com/s/7mbucitty7wx6yp/VID_20130902_091430.mp4
Another one, with PDF and clock:
https://www.dropbox.com/s/6oake0kgse3jyyq/VID_20130902_093920.mp4
The flicker is even there in CWM and on the SGT 10.1 Boot text
I'd like to push this, maybe someone could help me, although I got a new tablet a while ago.
Videos here:
https://www.dropbox.com/sh/cixq1secy5u5vxq/Xt9w5uVgqB
lordofazeroth said:
I'd like to push this, maybe someone could help me, although I got a new tablet a while ago.
Videos here:
https://www.dropbox.com/sh/cixq1secy5u5vxq/Xt9w5uVgqB
Click to expand...
Click to collapse
Perhaps, it is repairable, I already opened the GTab.
(Never had warranty)
lordofazeroth said:
Perhaps, it is repairable, I already opened the GTab.
(Never had warranty)
Click to expand...
Click to collapse
Hi,
I am facing the same problem. I watched your videos and its the same.
Did u get it checked. Please let me know if you solve this.
Thanks,
AV
Nothing as of yet.
Tablet can be switched on but lies somewhere around
Now I am on a KK Rom - Omni.
Not suprisingly, the flicker is still there...
push?
Any help?
It looks you have a faulty digitizer and/or screen. Since you tried almost every ROM you can safely rule out a software problem (you did test this with a stock ROM as well, right?). So I'm guessing it's hardware related.
Sent from my Nexus 7 2013
Itsa me again...
My tablet seems to be fine again :good:
What did I do?
Two things:
1)
I left the screen on with power plugged in. Nothing else
I do not know if this did the trick.
2)
I overclocked the tab to 1.4 GHz, activated WiFi Bluetooth, max. brightness and ran a stability test with graphics.
I then wrapped the tablet into a blanket (heat generation).
After 15 minutes I heard the battery (it was charged only to 15 % before)
And it was quite hot.
After cooling the tablet down i read a few PDF and no flicker...
Now I have two tablets, one Asus and one Samsung
Any comment on that procedure?
Unfortunately it is back again.
I burned the tablet again, but nothing. Didnt work this time.
Do you have any suggestions how to fix this?
So some of you with white Z5 compact phones might have had this touch sceen bug with repetitive key presses and unstable touch screen behaviour bug which was previously "fixed" by a software upgrade:
http://www.xperiablog.net/2015/10/21/white-xperia-z5-compact-touch-screen-fix-arriving-next-week/
Lo and behold. This bug is back in MM, and there is another guy in the thread which I can see also have the bug come back
It is not always there, but sometimes its just there. I dont know what triggers it. A restart seems to help until it comes back again.
For those of you not familiar with this bug, it usually shows by repetitive touches, and highly unstable touch screen.
For example when i press the key "s", it usually put in "sssssss" like i have pushed that key 5-6 times.
Also the bugs shows, when for example you are scrolling in facebook/internet, it will not let you scroll. Whenever you touch the screen, it will enter, whereever you lay your finger on screen.
Lastly it also shows by the screen becoming completely unresponsive when you press anywhere.
I have clean installed MM and restored my apps via Sony Backup/restore app.
I am so pissed how a phone color (white) can somehow decide the behavior of the phone touch screen, and I believe sony is hiding something.
In the beginning I was thinking that maybe they made different builds for the different Z5 colors, so they might not have included the "newest" touch screen drivers for at launch time for the white version.
But the same bug appearing AGAIN in MM i have a very hard time understanding that should be the case that it was a software bug. I believe there are some hardware bug, they have somehow omitted by a software circumvention, and they forgot to add it to the white version for the MM launch.
Personally I have always had a problem with the "return" key when the phone is placed. Patch or not, this button works once out of 10.
For information, I just bought this phone. I also think there is a hardware problem. This is average for a manufacturer like Sony. I thought for a moment it back in service but when I see the number of dissatisfied with the service Sony in France, I preferred to keep my phone in the hope that a solution comes a day. We have the right to expect in my opinion ...
I did clean install via flastool also and i have/had this problem. Yesterday i did software repair via pc companion and restores apps after that and so far problem has not occured.
I also made a repair with PC Companion but nothing changed.
So there are other people here with this annoying problem.
You all have a white xperia yes?
This bug is so annoying I feel sometimes like tossing the phone into a wall.
If there was an alternative to this phone in this form factor and specs, I would have bought it yesterday.
But unfortunately there isn't
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
hipsterfont said:
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
Click to expand...
Click to collapse
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
I also have Sony Z5 compact white version which had the touch problem from start. Now after the Marshmallow update its back. As said above, it could happen while browsing (or on home screen) e.g. Entering links instead of scolling i.e. It triggers multi click. In these situations all menu keys will also be none responsive. Its starts acting normal again after a quick push of the power button, i.e. puttning the screen to sleep.
As a former developer for mobile software, both for apps and the android platform, i thinking i would agree with the above conclusion that the problem is hardware based, and not due to a difference in the delivery software version, as i was hopping. So the question is; will this always be a problem for these versions of Z5c white, i.e. they are forgotten in new builds?
Unfortunately I'm having the same problem with my white z5 compact...
mcmanuf said:
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
Click to expand...
Click to collapse
it happens that for different colors are used different materials.. probably white ones have different properties..
i can confirm that using bad cable/chargers this kind of bug happens with every device, with random touches and impossible scrolling.. if you have a well-known bad adapter and you note no differences with your white z5c, that's definitively the answer..
i think sony should recall all white z5cs and replace them with newer or different release
What revision of compact Z5 are you? Personally I have a revision 3 (that is written on the box).
I also had a touch of problem before moving to the latest version of Android (6).
My girlfriend also bought white Z5 Compact and funny thing... I put the Panzer Glass on the screen and guess what? Sometimes she can't turn off the alarm clock in the morning and sometimes navigation buttons are not responding. I tried then without the screen and it works without a problem. I am not sure if this is a problem with Panzer glass or sony's bug.
I have Z5 and have no problems, but mine is black edition
Mine is z5c white version as well. The bug started again on MM
And the bug quite annoying.
I bought it on updated lollipop.
And never had this problem before.
This plus Bluetooth is really making me hold off on not moving up from .200 lol
Argh - just saw the visual representation of this bug:
http://www.xperiablog.net/2015/10/06/xperia-z5-compact-owners-reporting-touch-screen-problems/
and it sounds A LOT like the one from the OnePlus One (driver & firmware issue)
easy blame: Synaptics - fix your ****
Anyway:
try enabling the double-tap-to-wake if it's not already enabled, lock the screen - give it some time to settle (~ 30 seconds),
wake it up (double-tap) - do some stuff - disable the double-tap-to-wake and lock the screen again.
Unlock it via power button and see if that improved the "situation".
Sony recommended a few times to boot into Safe Mode,
does this Mode exist on Android Marshmallow ?
Does it make any change ?
Had this in Nougat is there a fix?
It feels like a software problem! You can try to reinstall the system!
First consider whether it is a system problem. You can refresh the system to see if it is back to normal. If it still does not, then you may need to update a new LCD screen. You can go online to find the repaired video as a reference. The witrigs repair video is doing great, you can check it out!
Hello all!
I have dropped my S3 (by accident, of course) and managed to completely break the touchscreen and display (no image). I ordered a replacement screen for i9300 (marketed as original) and replaced it myself (not the first time I replace screens on embedded devices). At first everything worked fine but with increasing frequency I get flickering and a fade out effect on the screen. A video will illustrate this better:
I've looked into the ribbon connector that connects the screen to the motherboard and cleaned it with alcohol and it made no difference.
The flickering effect appears also in the bootloader or recovery, so it's not android related. I also deactivated GPU rendering in Developer Settings.
My question is - has anyone seen this before? Am I looking at a bad replacement screen? Maybe a bad board (something that might have broken when it fell)? A bad contact?
I'd like to fix it somehow but I don't know where to start.
Thanks
mad_ady said:
Hello all!
I have dropped my S3 (by accident, of course) and managed to completely break the touchscreen and display (no image). I ordered a replacement screen for i9300 (marketed as original) and replaced it myself (not the first time I replace screens on embedded devices). At first everything worked fine but with increasing frequency I get flickering and a fade out effect on the screen. A video will illustrate this better:
I've looked into the ribbon connector that connects the screen to the motherboard and cleaned it with alcohol and it made no difference.
The flickering effect appears also in the bootloader or recovery, so it's not android related. I also deactivated GPU rendering in Developer Settings.
My question is - has anyone seen this before? Am I looking at a bad replacement screen? Maybe a bad board (something that might have broken when it fell)? A bad contact?
I'd like to fix it somehow but I don't know where to start.
Thanks
Click to expand...
Click to collapse
I might be just speculating, but i truly believe that is something wrong with the GPU. The contacts have nothing to do with it, so the only possibility is that the balls have cracked. That is my educated opinion. You could go and get your PCB reballed at any good GSM service.
Alexander_the_B0ss said:
I might be just speculating, but i truly believe that is something wrong with the GPU. The contacts have nothing to do with it, so the only possibility is that the balls have cracked. That is my educated opinion. You could go and get your PCB reballed at any good GSM service.
Click to expand...
Click to collapse
Thank you for your input. Would the effect happen even in bootloader (e.g. is the GPU the only component talking to the display)? Also, if I were to connect a HDMI (through a dock) should I expect to see the same behavior? I guess that if it behaves the same way, then yes, it's certanly something on the motherboard that's broken...
mad_ady said:
Thank you for your input. Would the effect happen even in bootloader (e.g. is the GPU the only component talking to the display)? Also, if I were to connect a HDMI (through a dock) should I expect to see the same behavior? I guess that if it behaves the same way, then yes, it's certanly something on the motherboard that's broken...
Click to expand...
Click to collapse
Yes, because the GPU's only task is to turn on pixels on the display to make Graphics. It will happen even via HDMI (MHL). There is no way to bypass the GPU. Assuming that display is 100% working. Try and see if the display is not defective and get a replacement.