[Q] (solved) Touch screen calibration issue + no sensitive keys (UPDATE: video) - Atrix 4G Q&A, Help & Troubleshooting

Hello
After flashing a .sbf firmware with RSDlite 5.0 (also tried with 5.3.1, win7 64bit), my touchscreen appeared to be not calibrated:
I have to push under the buttons
To push a button which is on the bottom of the screen, I have to push on the sensitive key zone
None of the sensitive keys are working (even if I try on the very bottom)
I did try to re install the firmware, and I tried other ones (both orange france, retail france, and orange UK full), always the same issue
I managed to root and install CWM without the keys (by rebooting again and again...) and installed gingerblur 4.5 and greyblur (and wiped everything just before): same issue...
Can anyone help!?
I don't know what else to do
UPDATE: here is a video to show what's wrong
http://www.youtube.com/watch?v=nN5vCsFpCcc

Also tried with orange uk service, same issue
Maybe there's just a corrupted file somewhere I should replace?

Did any of you back up the pds.img file?
Sent from my MB860 using XDA App

Hum...
http://forum.xda-developers.com/showthread.php?t=1138220
-> "but it can resolve issues with the touchscreen not taking input properly"
Looks like I should have made this backup ... but I didn't
Another topic about pds file:
http://forum.xda-developers.com/showthread.php?t=1131649
Should I use this pdsfix.zip file?

SOLVED!
So I did follow the instructions here:
http://forum.xda-developers.com/show....php?t=1131649
and touchscreen input is fine!
Thanks a lot neer2005 for saving me only with "pds.img" !

Related

[Q] Mini pro crashing with 2.0.2.A.0.24 and changing hard keyboard files.

After updating to 2.0.2.A.0.24 the phone crashes\reboots when i wake up the phone and try to swipe the lock screen. It seems like the screen is frozen when waking it up, and if i dont carefully swipe the keylock it will crash.
Anyone know what the problem can be?
mangoman said:
After updating to 2.0.2.A.0.24 the phone crashes\reboots when i wake up the phone and try to swipe the lock screen. It seems like the screen is frozen when waking it up, and if i dont carefully swipe the keylock it will crash.
Anyone know what the problem can be?
Click to expand...
Click to collapse
Yes, it did that that to me.
Solution :
1. wait for black screen just before next reboot(try and error), long press home key (right buttom key), do not release, phone stop reboot. If you release, it will boot again.
2. at your PC, start Sony update program, wait for it ready prompt you to connect USB cable, then connect USB cable while still press (home key).
3. Sony update program should detect your x10 mini, and check version upgrade, after it report that version already uptodate and prompt you reinstall it again, your answer is YES.
4. until you saw you X10mini green light on, then you can release you hand. Sony update will download again from internet and flash your x10mini.
I did this, sucessfully installed again with 2.1 2.0.2.A.0.24 version. But then you have to reinstall all you apps again from the beginning.
yes, i did reinstall the update from seus 3-4 times. I think it crashed 15 times in some hours.
Finally it also crashed and restarted when switching it off, and the popup screen appears to shut it down. Had to remove battery to turn it off.
i was using titanium backup to restore, so now im restoring applications one by one and testing to see if some of them are causing the crash.
The app2sd crash
Sent from my Pulse using XDA App
im not using app2sd, but today it has crashed 4 times so reinstallling with seus again. im soon giving up..
heres what im doing,- On Norwegian phone
1. install from seus again
2. root phone with this guide http://forum.xda-developers.com/showthread.php?t=906231&page=5
3. since im using build.prop with ro.product.name=U20i_1238-8536 im getting for some strange reason keyprint.xml with Keyprint name: QWERTY Swedish/Finnish and <script name="latin" keylayout="qwerty-se-fi"/> when i want norwegian.
Problem here is with 3. party on screen keyboards installed, the hardware keyboard cant write ø and æ. (It becomes ö and ä)
So with root explorer i replace keyprint.xml and mimmi_keypad.kcm.bin found here http://forum.xda-developers.com/showthread.php?t=828558&page=1
I think that can be the problem, but not sure
Edit again..
im 99% sure changing the keymap.xml and mimmi_keypad.kcm.bin from mentioned thread is the cause of the constant crashes.
with build.prop with ro.product.name=U20i_1238-8536 and updating i get Keyprint name: QWERTY Swedish/Finnish. So hardware keyboard cant type ø and æ with third party keyboard installed.
Any advice?
i have a lika problem but my problem is i can't write åäö but i have it on my keyboard it's become the other symbols .',
its lika i have a english keyboard but i dont shold have it. because instad of your .', i have åäö.

[Q] how to test touchscreen with adb

Hello, all ROM makers, developers, hackers and advanced users.
I have a problem and hope you can give me some good advice.
Here is my sad story
You can read the full description if you want. Or you can skip it - the main question in the end of this post..
I have bought a new Sony ericsson Live! with walkman (wt19i) phone during my newyear holydays in Prague. It seemd to be working fine.
It is from rev.3, manufacture date 11/49 (mounth/week)
When I came back home and started using it, I saw that after some inactivity period (about couple hours or maybe more) the touch screen, back and menu snsor buttons stops any responsing. Hardware buttons (home, volume, camera, walkman and power) are still working. The system also continues to work as usual, so I can turn it on (but can not slide to unlock), I can hear if somebody calls me (but can not answer). Alarms, notifications and all another functions are still working.
Once or twise it started to work again (by itself, without any actions by me) but after few time the problem repeated. I was very unhappy and sure it was a hardware problem (and of course the Czech warranty does not work in Russia), but now i'm not so sure.
The phone had 4.0.2.A.0.58 firmware (android 2.3.4) from the box. First of all I tried to install SE PC Companion software, connect phone with usb and make factory reset... touchscreen started to work! But soon I saw this problem again.
The next day a new update was released and installed it (firmware .62). My phone was working again, but with the same result after some time.
You shoud know, that simple softreset (or ejecting and inserting battery) has absolutesy no effect on problem. After system starts I can not even unlock it. But flashing a new (or even the same) firmware (with flash tool or SE PCC) makes touchscreen and buttons working for some time. Have no idea why, but installing ROM with CWM (even with full wipe) does not make touch working.
Then I tried to use another custom kernels and ROMs. I unlocked the bootloader with fastboot tool, flashed one of custom ROMs from this forum (pre-rooted and with CWM). Then tried to use CM7.2 ROM... then another kernel and another ROM. Official, official-based, totally unofficial. The problem was with me each time after couple hours
I thought it is because some troubles in lock screen. Tried to install "no lock" app, so my phone did not use lock... but after some time touch freezes in home screen.
I disabled screen off while charging in settings and tried to leave the phone "wired" for some time... actually it worked fine all the time, and when I dicsonnected it it was still working... for couple hours.
I tried to install "no sleep" applications that does not allow CPU and screen to suspend. But it have no influense.
I even flashed CM9.0 ICS (very) beta ROM with the same result.
If it is just hardware problem - why it solves (for some time, but solves) with flashing? If it is a software problem - why it doesnt solve with new kernels and ROMs? My brain is ready to explode.
Now I have only one last idea and ask you to help me.
The question is:
How can I use adb or adb shell comands to get more information about the problem with touch?
I saw there is some log (logcat, stderr) tools, debug tools. I saw working lsmod, dmesg and mount commands in shell.
I think I shoud get all this information when all is ok. And then get it again when touch stops working and then compare, is it a good idea?
Where exactly shoud I see? How to test or get some touch input device info with adb? Is there any item in /dev that i can explore? Or something in dmesg? Where are touch driver located and how can I check if it is working?
I have some basic linux and andriond skills, but have not enought expierence.
I very (VERY) hope somebody can give me any useful advice to continue solving the problem. Where to see, what to do?
Thank you
P.S.: and sorry for mistakes, of course. English is not my native language.
P.P.S.: i am not sure where is the best place for this question: here or in xperia subforums. But I decided that this question is not xperia-specific and can be useful for other people in future.
Anybody? I have Lenovo Yoga B6000 with touchscreen problem and will be good if anyone know how can i test TS through ADB or shell.

[Q] Help x10a screen touch not working after flash

Hi,
I flashed my x10a with latest flashtool with 2.3.3 firmware. The flash was successful, but after the flash it's screen touch is no more working. I thought that there might be problem with the firmware that I used, so I again checked with many firmwares, but none of them solved my problem.
Then I tried to repair my phone with Pc Companion, it says that no software is available for my phone. Also I tried with Sony Update Service, this also said no software for my phone.
I am tired now. I tried all the methods that I found on internet. Isn't there any solution for me now? I know that It's not a hardware problem because before flashing its screen was working without any problem. I know you guys here are expert in android problems. So hope you will help me in this problem? I am from Nepal. There isn't sony service in my country. What is the solution for me? I need your help....:crying:
could you tell us exactly what you flashed with flashtool ?
and what i understand is that your phone DOES work it fully loads up but not responding to your touchscreen ?
and any other info on what you might have flashed ?
it could just be freezing (so it seems like its not responding)
Bjornlindekens said:
could you tell us exactly what you flashed with flashtool ?
and what i understand is that your phone DOES work it fully loads up but not responding to your touchscreen ?
and any other info on what you might have flashed ?
it could just be freezing (so it seems like its not responding)
Click to expand...
Click to collapse
Bro thanks for your reply, I flashed X10a_2.1update1_r2.1.A.0.435_Generic.ftf, X10a_3.0.1.G.0.75_AMERICA-US GENERIC 1233-8200.ftf, and few more firmwares like this. I used flashtool-0.8.0.0-windows_2.exe to flash the phone. Ya you are right my phone DOES work it fully loads up but not responding to my touchscreen
Keys are working well, volume keys, back keys all are working. After flashing finished option comes to choose the language and I can't go ahead than that because screen touch will not work.
me.amar said:
Keys are working well, volume keys, back keys all are working. After flashing finished option comes to choose the language and I can't go ahead than that because screen touch will not work.
Click to expand...
Click to collapse
did your touchscreen worked on 2.1 firmware
as im googling for this problem EVRYTHING leads to software problems.
for example this post
"''The touchscreen on my phone stopped working. Everything else is working (buttons), except the touchscreen. It shows everything but I can't do nothing with my finger.. I've had this problem before, but then it could be fixed by simply taking out the battery and rebooting that way. This time that didn't work. First thing that I tried was factory resetting the phone, clearing all caches, etc. Touchscreen still not working after booting. Then I flashed SonyStyle V1.1 touchscreen still not working. Then I 'repaired' it with SEUS, touchscreen was working fine.""
so the best thing you can do right now is use SEUS to get back to original firmware.
http://sony-ericsson-update-service.en.uptodown.com/
and a guide to help
http://www.esato.com/board/viewtopic.php?topic=171599
if it works then you are absolutly sure its not a hardware problem.
techdevilisnowmonster said:
did your touchscreen worked on 2.1 firmware
Click to expand...
Click to collapse
Before flashing it was working.But after flashing it didn't worked on any firmware
Bjornlindekens said:
as im googling for this problem EVRYTHING leads to software problems.
for example this post
"''The touchscreen on my phone stopped working. Everything else is working (buttons), except the touchscreen. It shows everything but I can't do nothing with my finger.. I've had this problem before, but then it could be fixed by simply taking out the battery and rebooting that way. This time that didn't work. First thing that I tried was factory resetting the phone, clearing all caches, etc. Touchscreen still not working after booting. Then I flashed SonyStyle V1.1 touchscreen still not working. Then I 'repaired' it with SEUS, touchscreen was working fine.""
so the best thing you can do right now is use SEUS to get back to original firmware.
http://sony-ericsson-update-service.en.uptodown.com/
and a guide to help
http://www.esato.com/board/viewtopic.php?topic=171599
if it works then you are absolutly sure its not a hardware problem.
Click to expand...
Click to collapse
Does this works for android phones?
yes the tutorial is just wrong i noticed .
you could just use it as a guideline tough my apolegies

[HELP] Several issues with a LG G2 D802

(Feel free to move this thread to anywhere where it belongs, if it's an issue. And sorry for my non-native english).
Good night for everyone,
To make it short:
- I bought an LG G2 D802 from amazon.com (description says it's a factory unlocked phone).
- Tried to install a modified kitkat rom.
- The phone bricked into fastboot mode, but then I could repair the download mode and installed a Hong Kong (without noticing it and messed up the phone, because I'm form Venezuela and it went to a Locked state) stock firmware. But couldn't repair the recovery mode.
- When the phone booted it had an apparent screen calibration problem, where it doesn't respond accurately to touch, but going to the sensor->calibrate sensor option from settings menu didn't fix the problem at all. So I think it's something related to the Android system files (partitions maybe?) and not the settings or S/W at all.
- Installed an Open kitkat firmware hoping that it would fix the issue, but with no result. It correctly changed the S/W, but the screen problem persisted.
Some ideas that I have (but haven't found any propper methot to fix the phone) are:
1. If it applies: repairing the Android system files, to fix the touchscreen problem.
2. Rooting the phone and installing the best Recovery Mode to fix the phone.
3. Wiping the phone to blank.
4. Install a correct S/W from zero.
5. Hoping that it works
If it's possible doing it from a pc software or command line (connected to the phone obviously) I think it would be the easier solution, but don't know how to do it.
I would be really grateful with anyone who reads this and can help me fixing this...
Thanks.

[Q] [HELP] ZTE Kis Pro - RO Orange Zali problem

Hi xda-developers. I'm iDatFuuzy and i have this little (huge) problem. So, I was messing with some ROMs on my phone (Orange Zali RO) when I install an messed up boot animation (the actual messed up part is the resolution i think). Then I was like <OK. Reboot should help.> So I rebooted and I simply booted to android but with one problem: everything is INVISIBLE. I still can push buttons and stuff and I can hear if someone calls me but I can't see a thing ! I then tried to factory reset from the recovery, but that didn't fix, since it only formatted my Data and my cache folders. After that, I tried to re-install the Stock-ROM and I had another problem then: After verifying update package, at the half it says this: Installation Aborted. I have downloaded the OFFICIAL ROM from ztedevices.com and I have not modified it in any sort of way. So, can I fix this somehow ? I tried messing with my updater-script without any help. BTW before this happened (about 5months) I rooted my phone so THAT is not the reason for this.

Categories

Resources