I tried to find a answer but have been unsuccessful.
Since upgrading to JB whenever I reboot, my keyboard reverts to the stock keyboard and I have to go into settings to turn back on SwiftKey and then re select it.
Also on reboot, switch pro widget will not be loaded nor will audio manager profile switcher.
Any advice?
Sent from my HTC One X using Tapatalk 2
DucRider749S said:
I tried to find a answer but have been unsuccessful.
Since upgrading to JB whenever I reboot, my keyboard reverts to the stock keyboard and I have to go into settings to turn back on SwiftKey and then re select it.
Also on reboot, switch pro widget will not be loaded nor will audio manager profile switcher.
Any advice?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I recall having the same issue with JB at one point but I think after I RUU'd it stopped. I could be wrong, ofcourse. I know there's a bug with some settings switching back after reboot and I remember thinking this was part of that bug. But I was on Viper for a couple days a few days ago and don't remember it happening during that time.
I have the same issue. SwiftKey almost always is disabled on reboot and frequently overnight. Not sure if this is a glitch or some new memory management thing with the AT&T JB based ROM. Doesn't happen with my N7.
Running CR6.X - also happened with a ported ROM I flashed over the holidays.
Pretty annoying. Not really into RUUing at this time, since that has always been painful for me on other HTC phones. I have attempted clean flashes in an attempt to fix, with no luck.
Sent from my HTC One X using Tapatalk 2
So a ruu might fox the problem?
Sent from my HTC One X using Tapatalk 2
DucRider749S said:
So a ruu might fox the problem?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Might, RUU up to 3.18/3.17, make sure your S-OFF and don't relock your bootloader. Report your findings.
exad said:
Might, RUU up to 3.18/3.17, make sure your S-OFF and don't relock your bootloader. Report your findings.
Click to expand...
Click to collapse
Shoot, now I just need to figure out how to do that
DucRider749S said:
Shoot, now I just need to figure out how to do that
Click to expand...
Click to collapse
There's a thread about S-OFF in the original android development section.
Ruu, is simple, download the exe and run it with your phone plugged in. Don't relock the bootloader.
An update,
I didnt RUU but I found out that if I power off and then powerback on it keeps the keyboard and widgets
I also had At&t send me a new device, but it had the same problem
the rep called HTC and they have never heard of this problem, but have no fixes, so that sucks
the end response was just dont restart the phone, power it off then back on
Related
Hi there guys!
i just bought a htc sensation a month ago and make its s-off an flashed also a custom rom (senseless rom 1.2)
now my problem its, that the phone is rebooting sometimes, when i try to unlock the device from sleeping.
i push the power button, the phone doesn't react, so i push a second time. after pushing 2nd time, the display splash on and at the next moment off.
2 seconds later, i got the boot-splash of the device.
anyone had this problem already?
EDIT: this problem was coursed also before s-off, therefore i choose this section to disks about! =)
I'm having this problem as well. I have not rooted or s-off'd or anything else. Stock rom, most apps from the market. This started happening the other day when I installed an update to version 2.3.4. This is happening several times a day and is getting extremely annoying!!
hi,
i just followed this problem again.
i am using now the Beast Rom, and the phone has still this problem.
any ideas?
yasinis said:
hi,
i just followed this problem again.
i am using now the Beast Rom, and the phone has still this problem.
any ideas?
Click to expand...
Click to collapse
Try flashing ARHD 3.6.1 from Mike1986 very stable, good support and fully operational. way better than stock.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Defrag your micro sd card and fix file system errors. Uncheck enable fastboot and turn off your phone then turn it back on again. Lastly, try not to use "kill all" in task manager. Hope it help you guys.
Crashing as well
Same here with crashing.
During unlock, when using GPS. It's now several times a day. The device has become unfit for purpose. Will try the SD card trick.
I just bought this phone and since day one it keeps rebooting randomely. This happens multiple times a day and I am not sure what causes this.
replace it with new one
ts3010 said:
replace it with new one
Click to expand...
Click to collapse
If the problem persists till monday I will, but I'd like to find a solution other than replacing it as it usually is such a hassle.
realy dont waste your time finding solutions
you may find a temp solution but you will never know it you complete solve the problem or not
Yeah but it just might be a software problem..
Sent from my GT-I9100 using xda premium
that's easy if you didn't unlock the bootloader try factory reset
so if it's software problem it will gone otherwise it's a hardware problem
NTP
Found out in the logcat, that when you've selected automatic time/date settings. The htc Cha Cha couldn't pull a correct time/date from the NTP server. Maybe this is the cause of the random reboot. Ive changed my settings and i've for a 2 hours no reboots...
Hmmm, it's weird though.. I've been using auto time/date without any issues for the past 9 months. On stock ROM, SuperOSR, CM7 and CM9. You could try a factory reset (erasing all data) and check if that clears it out. Other than that, it might be radio related.
810215118 said:
Found out in the logcat, that when you've selected automatic time/date settings. The htc Cha Cha couldn't pull a correct time/date from the NTP server. Maybe this is the cause of the random reboot. Ive changed my settings and i've for a 2 hours no reboots...
Click to expand...
Click to collapse
This is fix the issue? I have been having abnormal restarts with my ChaCha right after I bough it.
It was not the ntp, but the launcher with the sense engine.... I have replaced them with go laucher and removed the stock launcher and the sense engine with root uninstaller.
Sent from my HTC ChaCha A810e using xda app-developers app
810215118 said:
It was not the ntp, but the launcher with the sense engine.... I have replaced them with go laucher and removed the stock launcher and the sense engine with root uninstaller.
Sent from my HTC ChaCha A810e using xda app-developers app
Click to expand...
Click to collapse
So removing sense and replacing it with go launcher fixed it for you? I had the same issue with my HTC chacha the very next day I bough it, did factory reset a couple of times and even flashed a new stock ROM through RUU but nothing helped, I feared it could be a hardware problem but since installing cyanogenmod 7 my phone has worked flawlessly. Every time I go back to stock I get abnormal restarts. I have written HTC about this, the only help they offered was to "factory reset" the device. The logs show kernel panic before every random restart.
Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.
Unrelashade said:
Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.
Click to expand...
Click to collapse
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2
mattlowry said:
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own
demkantor said:
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own
Click to expand...
Click to collapse
Thanks guys! Fastboot says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
Click to expand...
Click to collapse
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha
Unrelashade said:
Thanks guys! Fastboot says:
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha
Click to expand...
Click to collapse
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2
Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium
You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?
mattlowry said:
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
demkantor said:
Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
WeekendsR2Short said:
You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?
Click to expand...
Click to collapse
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.44.1107
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
Jun 27 2011, 14:08:29
Click to expand...
Click to collapse
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha
If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Sent from my HTC MyTouch 4G Slide using xda premium
Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2
A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Sent from my myTouch_4G_Slide using xda app-developers app
Unrelashade said:
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha
Click to expand...
Click to collapse
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.
WeekendsR2Short said:
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.
Click to expand...
Click to collapse
Thanks for the info.
demkantor said:
If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Click to expand...
Click to collapse
Ok, right now I'll not try flashing bootloader since everything seems to be normal.
What I did to get last_kmsg:
Code:
Open terminal app
Enter "su" to get root privileges
Enter "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" to save current log.
Close terminal app.
I attached the last_kmsg.txt. What do I do with it now? I don't have knowledge to understand it.
mattlowry said:
Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
I can't remember using a ROM that never crashed, but I'll try a stock ROM if nothing else works. However an old kernel of scverhagens CM 9.1 seems to work flawlessly if battery is not about < 15%. The newest r10 kernel on the other hand always immediately crashes when the phone is not charging. When charging I haven't experienced a crash yet. That's strange and makes me suspect my battery is the problem.
mojoffdawal said:
A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Click to expand...
Click to collapse
Thanks! I guess I'll try an Anker since I have seen so much users here using it.
virtuous rom works great! when i had mine, i was running 4.0.3 overclocked to 1.5ghz. super stable too! daily driver for sure.
Sent from my SGH-T999 using xda app-developers app
Thanks, but the problem is I'm pretty sure that something's wrong with my phone...
I'll try virtuous ROM and a new battery though.
hope it works
Sent from my SGH-T999 using Tapatalk 2
So, I'm reviving this thread, because I stopped writing only because my phone was broken. Now it's back and I'm facing this problem again.
I've tried a lot of the 4.x ROMs here from the forums, but all of them rebooted or shut down after 5 - 10 minutes after flashing. I also tried some without flashing gapps even, but still the same symptoms. Also tested it with my new battery, nothing changed. Even the scverhagen CM 9.1 ROM rebootet shortly after flashing that worked longer previously (guess that was just by chance)
Now I've tried the original image and it works! Ugh. So what can be wrong, any ideas?
I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app
bit1 said:
I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
It happened with both stock and new battery (Anker).
Thanks, update to latest TWRP had been my next try, if it didn't work now. But it does! Yeaaah so happy Thanks to everyone again. Almost three hours uptime and not a single issue so far!
To conclude: What I did:
Revert completely back to stock with BlueIX6's stock image (except that phone was still s-off and sdcard not wiped).
Then followed instructions to unlock bootloader, flash CWM recovery and finally flashed ROM (see sticky thread). Works like a charm!
In hindsight maybe radio made my phone unstable... I think it's the only thing that's different from now.
Hey guys, there's something wrong with my phone and I'm stumped on what the problem is. I am currently running Team Venom ViperXL 3.2.6 with the Bulletproof kernel, wifi partition, and newest ATT radio. After roughly three days of using the rom, my homescreen just completely crashed and I could not load my applications through the app drawer or recent menus page. I basically couldn't use my phone to access anything, but I could still receive and pick up calls. I reset the phone the same issue would occur where I unlock the phone and all I get is a white screen with the status menu on top.
I did a factory reset on the phone and it works fine now, but this isn't the first time I have experienced this issue. In one of the previous roms I was using, my phone completely froze on me on two separate occasions. My phone would hang on the boot animation for hours at a time each time I reset the phone. I had to reflash the rom in order to get around this.
I don't know what's causing these deathfreezes and I doubt its the problem with bad flashing or individual rom concerns. Any opinions and advice is greatly appreciated. Maybe I didnt unroot my phone properly? Is there a difference between S-On and S-Off?
Heres my phone info:
tampered/unlocked
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Apr 2 2012, 21:08:24
I flash all my roms via TWRP
Well for you, s off would not matter. Don't get me wrong, its simple, but one flaw could f you up. As for the home screen, could be the launcher. Haven't worked with viper, so I don't know if holo or another launcher is used. I use nova and haven't had any issues. For the hanging on the boot screen, could be a bad download. Do you use goo or ROM manager? I tend to stay away from those and get the complete download using a PC and match it up with md5.
Other than that. I couldn't tell you what is wrong.
Sent from my Carbon-ize Evita using xda-developers app
Herc08 said:
Well for you, s off would not matter. Don't get me wrong, its simple, but one flaw could f you up. As for the home screen, could be the launcher. Haven't worked with viper, so I don't know if holo or another launcher is used. I use nova and haven't had any issues. For the hanging on the boot screen, could be a bad download. Do you use goo or ROM manager? I tend to stay away from those and get the complete download using a PC and match it up with md5.
Other than that. I couldn't tell you what is wrong.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
I used apex and this was the first time it happened. I dont think it was a launcher issue because I did a force close on it in settings and I still got blank screens. Didnt revert to default launcher or restart apex.
As for the boot screen, it only happens after I have been using the rom for some time. I download the roms from my mac and flash it via twrp. At first I thought it was an inherent issue with scratch build jb roms so I grabbed viper only to get the same problem much quicker.
joshuaadude said:
I used apex and this was the first time it happened. I dont think it was a launcher issue because I did a force close on it in settings and I still got blank screens. Didnt revert to default launcher or restart apex.
As for the boot screen, it only happens after I have been using the rom for some time. I download the roms from my mac and flash it via twrp. At first I thought it was an inherent issue with scratch build jb roms so I grabbed viper only to get the same problem much quicker.
Click to expand...
Click to collapse
Hmm haven't got the slightest clue. My suggestion would be to do a for factory reset again clear evert cache and reflash. If that doesn't work, then could be hardware issue
Sent from my Carbon-ize Evita using xda-developers app
Wich version of twrp are you using?
Sent from my HTC One X using xda premium
Venomtester said:
Wich version of twrp are you using?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Keep forgetting 2.3.x.x is the best to use...
Sent from my Carbon-ize Evita using xda-developers app
I am using version 2.3.1.0.
Part of my touch screen does not work so when I go to install a custom rom with twrp I cannot factory reset delvik cache and all the other stuff. What can I do? I would use clock work mod but the roms I want to install need twrp. For example the ViperXL Rom says to install with twrp? Is there anyway to get viper installed on my phone? Is there something else I can use to clear the cache?
You should be able to use CWM to flash Viper, I think it's just a recommendation to use TWRP. I'd say give it a try.
Sent from my HTC One XL using XDA Premium 4 mobile app
jluca98 said:
Part of my touch screen does not work so when I go to install a custom rom with twrp I cannot factory reset delvik cache and all the other stuff. What can I do? I would use clock work mod but the roms I want to install need twrp. For example the ViperXL Rom says to install with twrp? Is there anyway to get viper installed on my phone? Is there something else I can use to clear the cache?
Click to expand...
Click to collapse
What version of TWRP are you using? Some of the older versions of TWRP won't work with the updated touch screen firmware, which you would have if you ran the 3.18 RUU or took the OTA JB update.
timmaaa said:
You should be able to use CWM to flash Viper, I think it's just a recommendation to use TWRP. I'd say give it a try.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unless it's been changed, Viper won't install on anything other than TWRP. I tried to install it using Philz AdvancedCWM and it stops the install and prompts you to install TWRP instead.
Oh, I stand corrected then. Thanks for clarifying that.
It sounds like a hardware fault to me though, only part of the screen isn't working.
Sent from my HTC One XL using XDA Premium 4 mobile app
pside15 said:
What version of TWRP are you using? Some of the older versions of TWRP won't work with the updated touch screen firmware, which you would have if you ran the 3.18 RUU or took the OTA JB update.
Click to expand...
Click to collapse
This is mostly likely the issue. It's a rather old version of TWRP that has this touch screen issue, so update to the latest (2.6) posted in Development.
I do have twrp 2.6 installed. The thing is that the touch screen under my status bar does not work in most apps but in some of them it does. This problem is occurring in twrp but when I play games that part of the touch works so I do not understand what is going on.
Sent from my One X using XDA Premium 4 mobile app
This is pretty confusing, since you haven't given a lot of vital info, and didn't completely describe (as far as I can tell) the issue in your original post. First it sounded like touchscreen wasn't working in recovery only, now it sounds like its not working when the OS is booted also.
What ROM are you running?
What hboot?
Ok, so like I said, it's a hardware issue, it has nothing to do with touchscreen drivers. I think at the moment you only have two options:
1) Have your touchscreen repaired.
2) Use CWM (non touch) and flash something other than Viper. There are plenty of great ROMs available, now the official Sense 5 update has been released you'll see even more pop up. There's already a stock Sense 5 ROM by Turge, and MagioRom will have our own modded version released in the next day or so.
Sent from my HTC One XL using XDA Premium 4 mobile app
timmaaa said:
Ok, so like I said, it's a hardware issue, it has nothing to do with touchscreen drivers. I think at the moment you only have two options:
1) Have your touchscreen repaired.
2) Use CWM (non touch) and flash something other than Viper. There are plenty of great ROMs available, now the official Sense 5 update has been released you'll see even more pop up. There's already a stock Sense 5 ROM by Turge, and MagioRom will have our own modded version released in the next day or so.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
'
Problem Solved. The Viper aroma installer actually has a feature that automatically clears the delvik cache. I flashed the ROM and all is working. Thanks for the help guys.
Also, to clarify my problem, my touchscreen has a spot on it that does not work in some apps and works in some apps. For example, I cannot click the install button in the Google Play Store (I rotate the screen to install apps.) but I can click in that same area in the lockscreen and get a touch reaction. This seems to me like a hardware issue because the affected area does not work in TWRP either, but then why does it work in some apps and in some locations of the ui?
jluca98 said:
'
Problem Solved. The Viper aroma installer actually has a feature that automatically clears the delvik cache. I flashed the ROM and all is working. Thanks for the help guys.
Also, to clarify my problem, my touchscreen has a spot on it that does not work in some apps and works in some apps. For example, I cannot click the install button in the Google Play Store (I rotate the screen to install apps.) but I can click in that same area in the lockscreen and get a touch reaction. This seems to me like a hardware issue because the affected area does not work in TWRP either, but then why does it work in some apps and in some locations of the ui?
Click to expand...
Click to collapse
because of the response area specified within the app. Chances are the ones that are working just have a larger area of response and therefore it recognizes within those confines. there are apps that test the touch screen try one to find out where you lose responsiveness
You are correct. I used the touch screen test app and that strip is completely unresponsive.
Sent from my One X using XDA Premium 4 mobile app
jluca98 said:
You are correct. I used the touch screen test app and that strip is completely unresponsive.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi I have the same issue with you, a segment of my touch screen is not responding but it's pixel is alright.. No dead pixels, only segment of screen not responding. The affected segment is in line with the send key in text message so I have to rotate everytime i need to send a text message in order to change the location of send key. What did you do in order to solve this problem? Did you bring it to HTC Service Center? Thanks!
mabrinez said:
Hi I have the same issue with you, a segment of my touch screen is not responding but it's pixel is alright.. No dead pixels, only segment of screen not responding. The affected segment is in line with the send key in text message so I have to rotate everytime i need to send a text message in order to change the location of send key. What did you do in order to solve this problem? Did you bring it to HTC Service Center? Thanks!
Click to expand...
Click to collapse
If what you're experiencing is a hardware issue, which it probably is, you need to replace the digitizer. Whether you attempt it yourself or get an experienced repairer to do it is up to you.
Sent from my Evita
Got the same issue as posted above but my touchscreen works perfectly in landscape mode (touchscreen test apps don't work here either but other apps do) while that silly strip still doesn't work in both recovery and booted OS, whichever recovery/OS installed, in portrait. Tried to find different touchscreen drivers but that thread seems to be deleted. I'll try an older firmware (2.14 seems to be the last one to have tp drivers inside).
=edit=
Firmware flash didn't help.
=edit2=
Ordered new digitizer, I'll see when it arrives.
also ordered screen
PlayPetepp said:
Got the same issue as posted above but my touchscreen works perfectly in landscape mode (touchscreen test apps don't work here either but other apps do) while that silly strip still doesn't work in both recovery and booted OS, whichever recovery/OS installed, in portrait. Tried to find different touchscreen drivers but that thread seems to be deleted. I'll try an older firmware (2.14 seems to be the last one to have tp drivers inside).
=edit=
Firmware flash didn't help.
=edit2=
Ordered new digitizer, I'll see when it arrives.
Click to expand...
Click to collapse
new screen did not help for me. how did the new screen work for you?
Moto Mouth said:
new screen did not help for me. how did the new screen work for you?
Click to expand...
Click to collapse
Did you change just the screen, or the screen + digitizer?
Sent from my Evita
changed the lcd and the digitizer but in two parts so not to run into broken digitizer issues in the future and need an assembly.
Moto Mouth said:
changed the lcd and the digitizer but in two parts so not to run into broken digitizer issues in the future and need an assembly.
Click to expand...
Click to collapse
Mine didn't arrive yet. Will probably tomorrow or early next week. Also ordered an lcd screen + digitizer combo just to be sure. Funny how stuff is cheap on ebay.
Moto Mouth said:
changed the lcd and the digitizer but in two parts so not to run into broken digitizer issues in the future and need an assembly.
Click to expand...
Click to collapse
Ok, was thinking you had only changed the screen.
Sent from my Evita
I can not format your partitions in, because I do not work in the sensor recovery menu, I tried to reinstall all else fails Please provide help