Develop Bugs

After Installing Android CAB and download apps Screen Stop Working

My Screen has totally stop touching and Ive searched and searched for a solution.... and yet havent found any. I deleted the ts-calibration file and yet still screen no work

BUMP Help!

You mean that the screen is not working within android of with windows mobile?
If you mean windows mobile then your screen is broken or if you think it is because of the cab, you can try a hard reset.
If it is only in android then uninstall this version of android and download the .rar and extract it to your SDcard.

I have sort of the same issue. My screen doesn't work (most of the time). For some reason it is responsive sometime (not clear how to recreate that). I can see the screen is responding, although if I go to the menu and try to select a icon with my finger it holds the icon and drags it (and I cannot let it go)
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Deleting the calibration file doesn't work for me. Also I have tried hard resets and rom upgrades several times, with no succes. It looks like installing android changed something, but doesn't set it to his old state after removal.
Anybody?

This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.

yea i was having the same problem and couldnt figure out a solution, i deleted the ts-calibration, i've tried deleting all android files and starting over but the problem still exists. I think it might have something to do with the little bit of moisture i see under the screen because before i started seeing that, it used to work. But the screen works just fine when WinMobile is running so i dont know

If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?

arrrghhh said:
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
Click to expand...
Click to collapse
No, in both. This problem originated from the fact I was never able to start up a blazin android. It started booting, but for some reason never finished it. With the previous editions I never had any problems.
arrrghhh said:
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
Click to expand...
Click to collapse
I know you are replying on another user, but I still want to respond
Yesterday my screen was responding for a short moment. I have replaced the WinMo rom after that several times, no success. Also deleted android and reinstalled it again. (I've been trying trial and error for a while now, without any success.)
My WinMo rom btw was an energy build. Any similarities with other users experiencing this issue?
Is there some internal memory where these type of settings (keyboard layout and such) are stored and what not always change if you upgrade roms?
Perhaps I should go back to the original T-mobile rom.

Just upgraded to the original tmobile rom, but I'm stuck at the WinMo startscreen (tap the screen to start using it for the first time) I noticed that if you slide the phone open (keyboard visible) the display of the screen is correct. If I flip it back I'm missing parts of the screen.

dwaaz said:
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Click to expand...
Click to collapse
I'm sorry for spamming this topic, but isn't it really weird that only for entering your pincode the numbers are correct, but afterwards the layout is all messed up?
6_7_8 = 123
Y_U_I = 456
H_J_K = 789
N=0
I have the feeling my phone is using system files (after login) of a completely different phone (and no.. I did use the right rom's ) This goes for the keyboard as well as the screen issue.

any bright ideas?
Just to bring it under the attention again, because I'm on the edge of sending it back to t-mobile. (I hope they are not going to charge me because I have a diamond 2 that also needs repairing, touchscreen doesn't work as well, and I'm seeing some costs coming up there. For some reason I always manage to wreck my phones in the first 2 years. )
Any bright ideas?

I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slighty and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App

It worked!
trotmanc said:
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slightly and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
Click to expand...
Click to collapse
I was kind of skeptic here of this solution, because my phone looked quit clean. But there I was, on visit with my parents, fiddling with my phone, thought; let's put my nails between the lines next to the touchscreen..... and wtf.. it worked My screen is back up. Very surprising but good.
No I only have my keyboard to worry about. Any thoughts on that?

[Q] ts_calibration HTC Touch pro Xandroid

Hi everyone.
First time on a forum for years. This one is pretty daunting though. Not even sure if Im in the correct thread
Just recently got myself an HTC Touch Pro. Yeah! it's old but I guess its better that the Ericsson w350 I had.
I was not happy with the 6.1 Win Mobile OS on the HTC and I heard that Android can be loaded up instead. So I started doing some research.
To cut a long story short, I managed to load XDAndroid onto the microSD card. all is working fine except I messed up on the touch screen calibration. or at least it was not made clear to me that what I was indeed doing was a screen calibration.
After some reading on the wiki files, I removed the ts_calibration as instructed and rebooted the system. The graphic for the calibration test does not seem to display correctly. Hence the readon for the initial stuff-up so I simply had to guess where the pointer were using the win6.1 OS calibration(Don't ask - it involved a non-permanent marker). Even that does not seem to work.
It would seem that the co-ords where transposed after some fiddling around. Left was right, up was down etc. So I got to thinking to open that ts_calibration file and started playing around with the numbers. Even the screen functionality was reversed when the I slid the screen open. Navigation via the Keyboard is no hassle though. The touch button navigation seems to work fine except the selection key does not actually select anything, I have to use the enter key on the keyboard. Not sure if this is normal. So if anything, navigation involves the keyboard to be open thus the screen orientation is always landscape as opposed to portrait view which sucks! esp if I'm texting or making a call. What the work around for this is general?
So I thought of opening the ts file in a txt editor and I transposed the numbers. I seem to be getting somewhere as the up and down seem to be working correctly now but the left and right are not, center screen is still out though. I'm not sure what sets of number represent which co-ord. I know that the calibration requires 5 co-ords, but I dont know in which order they should be. Is middle, top-right, top-left, bottom left, bottom right?
It would be easier to just have the correct co-ords for this phone. instead of playing around with some random numbers. IOW would the ts file co-ords be the same for all HTC Touch Pros? if so where can I get the correct co-ord numbers for that file? then I wont have to use the calibration function. easier still, is there a free app that will do this from within the XDAndroid os?
The start up txt I chose was Raph100 for the root folder. This is correct for my phone according to the wiki help files. I've not updated the files and used them as is. Would the incremental updates fix this?

I'm having the same issue for my TP. After some discussion, I downloaded the ts file from the FRX07 fixed discussion and it's pretty darned close to accurate. MAYBE just a little off center to the lower left of icons.
Here's a utube vid that shows clearly the touch pattern for calibration.
http://www.youtube.com/watch?v=FB6MVFH4Jv4
Hope it helps.

[Q] 4.2 Issue with proximity sensor/dialpad?

I'm not sure if I am the only one but searching hasn't really helped me find any answers. Basically, since updating (rather, doing a clean install of 4.2 tajku) to 4.2 Jellybean, I often have an issue where despite the fact that the proximity sensor blacks out the screen, the dial pad when pulled up still detects key hits. Hence, my cheek is randomly pressing buttons. Happens during voicemail since the dial pad is needed to get through menus and/or during calls which have a menu system.
Any else have this problem or have any ideas how I can resolve it?

Same here

Glad I'm not going crazy. Seems to also be happening without the dial pad, per say. I say that because it appears during a call, I was pressing something so I removed from proximity to be greeted by the lock screen (number pad). So I wonder if it has something to do with that. I am going to disable pin lock for awhile to see if that alleviates the problem.

Do you have something similar with SKype?
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.

MenaMAKS said:
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.
Click to expand...
Click to collapse
No Skype. And the screen goes off due to the proximity sensor - but the buttons and/or dial pad are still active. I'll try changing my power button back from "end call" to just screen off and see if that helps.

Anyway, a quick update. Seems like a couple of factory resets did the job. So something with Titanium Backup did not translate over well to 4.2 (from 4.1.2). On top of that, I can no longer seem to do a full restore, causes my device to go into boot loop. Don't know why it worked the first time. At any rate, just re-downloaded all my apps and so far so good. Just have to try and restore individual app data one by one and see if I can get it to stick without fudging up the dial pad again.
EDIT: Scratch that, it's going it again. What the hell... 4.2 is such a @#@#@ in the ass.

Still having same issue. Glad you came back with an update, bc I was about to re-flash and re-download all of my apps. I know you say that you experience it even without the keypad pulled up, but I have not. Usually happens when I call an automated system, and my call gets sent to every extension possible!
Sent from my Galaxy Nexus using xda app-developers app

Alright, I think I have it working. I did factory reset... made sure any phantom directories (i.e. storage(sdcard)/0/0/0/0 etc) were deleted.
1) By default, I tested by calling voice mail then rolling my cheek against the screen. So far so good.
2) I downloaded StickMount, Titanium Backup Pro, NTFS mounter (for ntfs driver) and ES File Explorer. Tested again as per above. OK.
3) Used Titanium Backup to restore missing apps + data. Did a test, still good.
4) Used Titanium Backup to restore only select system data (i.e. call logs, SMS log, alarm, etc). Still tests fine.
5) Enabled PGM free. Did test and BOOM, problem.
So it seems like with 4.2 there is something screwy with PGM which is essentially keeping the screen "awake" even though it's off due to sensor. Don't know why I didn't think of it earlier.
EDIT: Checked the PGM thread and it appears the author has already fixed it though only the paid version is updated atm. Says will update the free version soon if the paid version doesn't have any new bugs.

Awesome, nice work! Will see of it works for me too and report back.
Sent from my Galaxy Nexus using xda app-developers app
Edit Uninstalled PGM, reboot and its solved! Thanks for your hard work!

I was going crazy with this issue too .. it's good that it's not only me .. i will disable PGM and try

My brother's nexus has this issue without pgm installed on full stock 4.2.1 rom.
I have watched the serial code and production date is c9,or rather september 2012.
What I have to do to fix this very annoying issue?
edit: no one has this issue?It's a common problem of latest batch sold in Italy.

[Q] Default Messenger App Randomly Opens

Hi,
So I got an HTC One M8 when it first came out, loved it right from the start. However, since the start, I've been having various software issues. The gesture controls never really worked for me, the on board music player app never really worked for me either (to be fair, I think that's because my SD card is dying)...however, the biggest annoyance I've been having is that the default text messenger app randomly opens.
By that I mean, I can be doing something on my home screen, tapping away in an area that has nothing to do with where my messenger app is, and all of a sudden I'll be in my last text conversation.
I have sent my phone out for repair once and they re-flashed it. The problem persists after that.
Any suggestions?

Majestic8705 said:
Hi,
So I got an HTC One M8 when it first came out, loved it right from the start. However, since the start, I've been having various software issues. The gesture controls never really worked for me, the on board music player app never really worked for me either (to be fair, I think that's because my SD card is dying)...however, the biggest annoyance I've been having is that the default text messenger app randomly opens.
By that I mean, I can be doing something on my home screen, tapping away in an area that has nothing to do with where my messenger app is, and all of a sudden I'll be in my last text conversation.
I have sent my phone out for repair once and they re-flashed it. The problem persists after that.
Any suggestions?
Click to expand...
Click to collapse
Does it do that with just the messenger? I mean... The area on the phone where the messenger app is, have you noticed at all while in another program or something that that area gets "tapped". If not then we can probably exclude a hardware related issue kinda like a "stuck button" on the touch pad.

BerndM14 said:
Does it do that with just the messenger? I mean... The area on the phone where the messenger app is, have you noticed at all while in another program or something that that area gets "tapped". If not then we can probably exclude a hardware related issue kinda like a "stuck button" on the touch pad.
Click to expand...
Click to collapse
Tried that, just a moment ago. Moved my messenger app over along the bottom and put a browser in the spot the messenger app was. However, now my phone is randomly launching the Car app.

Majestic8705 said:
Tried that, just a moment ago. Moved my messenger app over along the bottom and put a browser in the spot the messenger app was. However, now my phone is randomly launching the Car app.
Click to expand...
Click to collapse
better yet check to see if it "draws" on the line test.
*#*#3424#*#* It should give you a screen with "HTC Function Test" at the top, press accept, select Line Drawing test and press on Run. Touch the screen once and wait for it to tell you to start drawing, just leave it then and see if it makes marks on the screen or not.
Just to check if maybe it's an issue with touch pad.

BerndM14 said:
better yet check to see if it "draws" on the line test.
*#*#3424#*#* It should give you a screen with "HTC Function Test" at the top, press accept, select Line Drawing test and press on Run. Touch the screen once and wait for it to tell you to start drawing, just leave it then and see if it makes marks on the screen or not.
Just to check if maybe it's an issue with touch pad.
Click to expand...
Click to collapse
Did that, the line appeared on the screen as I drew.
I feel I should mention that the car app is now randomly launching even when I press the home button.

Majestic8705 said:
Did that, the line appeared on the screen as I drew.
I feel I should mention that the car app is now randomly launching even when I press the home button.
Click to expand...
Click to collapse
Yeah but I didn't want you to draw anything, I wanted you to check if it draws on its own.
Touch the screen once and wait for it to tell you to start drawing, just leave it then and see if it makes marks on the screen or not
Click to expand...
Click to collapse
It might be a hardware problem then I don't think there's much that we can do on this side. I find it funny and odd that the service center you took it too didn't run these kinds of tests themselves and just instead decided to "reflash" (If they even did that).
Hopefully though the problem is software related somehow and perhaps a complete restore would fix it, but we'll see.

BerndM14 said:
Yeah but I didn't want you to draw anything, I wanted you to check if it draws on its own.
It might be a hardware problem then I don't think there's much that we can do on this side. I find it funny and odd that the service center you took it too didn't run these kinds of tests themselves and just instead decided to "reflash" (If they even did that).
Hopefully though the problem is software related somehow and perhaps a complete restore would fix it, but we'll see.
Click to expand...
Click to collapse
Sorry, just skipped the last part of that sentence. Bad habit of mine.
No lines appeared when I just waited.

Majestic8705 said:
Hi,
So I got an HTC One M8 when it first came out, loved it right from the start. However, since the start, I've been having various software issues. The gesture controls never really worked for me, the on board music player app never really worked for me either (to be fair, I think that's because my SD card is dying)...however, the biggest annoyance I've been having is that the default text messenger app randomly opens.
By that I mean, I can be doing something on my home screen, tapping away in an area that has nothing to do with where my messenger app is, and all of a sudden I'll be in my last text conversation.
I have sent my phone out for repair once and they re-flashed it. The problem persists after that.
Any suggestions?
Click to expand...
Click to collapse
Have you got any mods going? Xposed for example? Something might be on like swipe up/down/left/right to launch an app etc. Must be something like that or it wouldn't only do it on the home screen.

backfromthestorm said:
Have you got any mods going? Xposed for example? Something might be on like swipe up/down/left/right to launch an app etc. Must be something like that or it wouldn't only do it on the home screen.
Click to expand...
Click to collapse
No mods, Only thing in terms of swipe commands I have running are the default HTC Gesture commands which launch things like the camera. They don't open any of the apps that have been acting up.

Random top row of the screen not working! Grrr

Okay this has bugged the heck out of me for ages, maybe someone knows the answer to it.
The top notification bar (and sometimes the row underneath in certain apps) sometimes is completely unpressable, as if it's being blocked. I should note this happens on my Note 7, but has also occurred on my Note 3, my old S2 and even the S7. Which makes me think it must be a setting I choose, or an app I install.
Sometimes, I'll turn on my phone, go past the lock screen and I won't be able to drag the notification bar down. I found a workaround (which has worked on all my old phones).
- Turn the phone off
- Turn it back on
- On the lock screen try to drag the notification bar down (which doesn't do anything)
- Unlock the phone
- Then it works again!!
My mrs had this too, and my workaround fixed it.
This issue has spanned over multiple versions of Android and is now doing my head in.
Any ideas?

Some app overlay is on top of it such as: Flux, blue light filter, and things like that. Once disable the issue is gone. That might be your issue.

jonboyuk said:
Okay this has bugged the heck out of me for ages, maybe someone knows the answer to it.
The top notification bar (and sometimes the row underneath in certain apps) sometimes is completely unpressable, as if it's being blocked. I should note this happens on my Note 7, but has also occurred on my Note 3, my old S2 and even the S7. Which makes me think it must be a setting I choose, or an app I install.
Sometimes, I'll turn on my phone, go past the lock screen and I won't be able to drag the notification bar down. I found a workaround (which has worked on all my old phones).
- Turn the phone off
- Turn it back on
- On the lock screen try to drag the notification bar down (which doesn't do anything)
- Unlock the phone
- Then it works again!!
My mrs had this too, and my workaround fixed it.
This issue has spanned over multiple versions of Android and is now doing my head in.
Any ideas?
Click to expand...
Click to collapse
I would place a 90% bet on this being a carried over app problem. Have you tried a fresh reset and reproduced the problem?
Have you also tried the service test for Touch ans S Pen? *#0*#

Kansatsusha said:
Some app overlay is on top of it such as: Flux, blue light filter, and things like that. Once disable the issue is gone. That might be your issue.
Click to expand...
Click to collapse
I thought as much. I used to have Twilight installed but I deleted it and it hasn't solved my issue!
alltaken123 said:
I would place a 90% bet on this being a carried over app problem. Have you tried a fresh reset and reproduced the problem?
Have you also tried the service test for Touch ans S Pen? *#0*#
Click to expand...
Click to collapse
I think so too. One example I have an issue with is the offscreen memo function. I pull the stylus out and can write on the screen off, but the row of buttons along the top NEVER work! But, I should say on a hard reset it was fine until all the apps were installed and logged into, or a setting was put in place. The service test for S Pen and Touch works perfectly. All I can think is trying to install 1 app at a time, and seeing what happens as a result. Will be painful with 100+ apps though. I'm about to replace my N7 on the recall too so I want to hold off on a hard reset too.

I feel your pain, if it were me I would rather discover the erroneous app now than later. Perhaps a backup via smartswitch on PC (very fast over USB 3) and when you know which app restore the backup and delete the app accordingly?

alltaken123 said:
I feel your pain, if it were me I would rather discover the erroneous app now than later. Perhaps a backup via smartswitch on PC (very fast over USB 3) and when you know which app restore the backup and delete the app accordingly?
Click to expand...
Click to collapse
By pure luck. I found it. 3 years of pain and I nailed the bugger! Something you said triggered a thought process.
It was....
Cerberus security! An app that automatically hides itself from the draw once it's installed so usually never crossed my mind.
Disabling the "Block Status bar" feature in Cerberus fixed it.
PHEW!!!!!!!!!!! Thanks for this (both of you).

good for you!