Done a bit of research now and all the keywords I have searched through haven't returned any results of this particular issue.
I have flashed CM10 (Stable) to the XL, has installed and boots fine, however there is 0 feedback from the touchscreen so i can't use it at all.
I couldn't really find anyone else with a similar issue. Has anyone run into this, or know what may be causing it?
Have downloaded numerous times, different versions of twrp, everything's been cleared out/wiped (both before and after flash).
I'll add that I have not had this issue at all elsewhere, EXCEPT where yesterday I updated stock to the latest version to give it a go (was hoping for more of a JB experience...). In this case there is / was a bug with TWRP where if you installed Android 4.1 (Latest stock), the touch would no longer work in TWRP. Luckily the TWRP dev updated to 2.3.3.1 today, fixing the touch again (which some themes such as viper require). But I have no idea if any of this is related, shouldn't be though,given the rom should work standalone...
Any ideas would be great. I battled to overcome that damn TWRP mess (seen above) that I got myself into, then I got past a boot issue and now that I'm booted the damn touch doesn't work lol.
Hope to hear some good news,
regards.
Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.
twistedddx said:
Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.
Click to expand...
Click to collapse
Thanks for your reply. I just tried installing JellyBam now and alas the same issue, checking here confirms things
Can you recommend a Kernel that will work for the mean time? I was actually looking at some of the kernels, but didn't really go anywhere with it.
You can only use roms and kernels made from 3.17 for the time being.
twistedddx said:
You can only use roms and kernels made from 3.17 for the time being.
Click to expand...
Click to collapse
This sucks. I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
My restores also don't work. Only JB roms actually boot now and all of them don't have any touch screen support. I AM able to get touch support if i install the ElementX JB kernel, however that then throws infinite "nfc and android.phone process-stop" messages (just after applications are being upgraded w/ the first boot of a JB rom).
Just looking to make the phone work
Playing around with Joker and have got the phone back into a working state. *phew*
xlmama said:
I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
Click to expand...
Click to collapse
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Thanks for your help. I'm now not clueless about my phones fate. :victory:
I have the same issue - updated to Andriod 3.17 about a week ago, and decided to flash CM10 afterwards. As a result, I am stuck with no touchscreen functionality.
Have there been any updates the past few days in terms of ROM's being released that will work on 3.17? How far into the future are we talking about before a release of CM10 will become available?
Is there no way to revert back to ICS and thus have a fully functioning version of CM10?
Is there any news on this issue ?
It's not possible until HTC releases kernel source. There's nothing the devs can do. You can only run sense roms
Sent from my VENOMized HoxL
twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.
I think I may be having the same problem, though I don't remember ever upgrading to 3.17. Is what you all are seeing like the screen doesn't even turn on? It just stays black, but the power button and volume button seem to be responsive? I can't even seem to get into recovery or bootloader, and this all started when I flashed the latest CM10 nightly.
Never mind.
Magickalhack said:
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.
Click to expand...
Click to collapse
You do realized you flashed a sense kernel for an aosp Rom?... And you're wondering why it gave you FC's?
I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?
slash178 said:
I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?
Click to expand...
Click to collapse
Do you use s2w? That causes that issue
Sent from my VENOMized HoxL
Quick question:
I've been having wifi issues which I've searched for the solution, but haven't found it. I don't want to downgrade hboot because I see my limitations laying in there somewhere and don't want to mess everything up. Wifi is the the only issue I'm having.
I flashed the Fusion Ultimate v.4 kernel hoping it would help, but it hasn't, although my phone seems to run faster and smoother.
So I'm wondering... will a kernel even really help a wifi issue and, if so, is there one better suited than the Fusion Ultimate?
My phone:
HTC One S (S4) S-On
hboot: 1.14
kernel flashed via Flash Image GIU
It seems many have wifi issues with custom roms and hboot 1.14. Kernels doesnt help.
The only solution Ive seen around the forum is, downgrading the hboot.
In terms of kernel, you are one of the lucky ones who managed to get v4 to boot, welcome to the club Theres a giant bug somewhere in it which causes it to not boot for the majority of the users.
You could try Fusion v3.1 instead - but I doubt that will help your issue.
Surprisingly, it seems to have worked. At least, I assume it did since I made no other changes tonight and Wi-Fi is working. Even when I leave the house, it connects when I get back. Whatever happened, I hope it keeps up.
Thanks for the reply.
Sent from my HTC One S using Tapatalk 2
Hey all,
I picked up a cracked screen Sensation for my son and discovered it also had funky wifi/BT. It was bone stock running 4.0.3.
I unlocked the boot loaded, S-OFF'd, rooted and updated firmware to 3.33.
Did my research here and determined my issue was HDW related. So I order a new digitizer and LCD flex (the later includes the wifi chip).
While I waited for my kit to arrive I flashed CM10, 8/4 build I think.
Well yesterday I did my repairs and fired up the phone only to see wifi stuck at turning on - and the phone rebooting every so often. BT, however was now working fine.
So here is the twist.
I restored my stk 4.0.3 rooted nandroid and wifi works fine!:good:
But if I do a clean install of CM10 - again wifi does not work
I have read about the issues with wifi and being S-ON, but I am S-OFF.
Any thought s on how to get CM working?
micl9 said:
Hey all,
I picked up a cracked screen Sensation for my son and discovered it also had funky wifi/BT. It was bone stock running 4.0.3.
I unlocked the boot loaded, S-OFF'd, rooted and updated firmware to 3.33.
Did my research here and determined my issue was HDW related. So I order a new digitizer and LCD flex (the later includes the wifi chip).
While I waited for my kit to arrive I flashed CM10, 8/4 build I think.
Well yesterday I did my repairs and fired up the phone only to see wifi stuck at turning on - and the phone rebooting every so often. BT, however was now working fine.
So here is the twist.
I restored my stk 4.0.3 rooted nandroid and wifi works fine!:good:
But if I do a clean install of CM10 - again wifi does not work
I have read about the issues with wifi and being S-ON, but I am S-OFF.
Any thought s on how to get CM working?
Click to expand...
Click to collapse
Sometimes ROMs have problems with wifi, I had similliar problem with another ROM.
Some users with HTC Amaze report builds prior to April 5 had Wifi problems. Did you try CM10.1/2? For me there is no problem with wifi at all, worth a shot.
Maybe try a different ROM?
I have also experienced some wi fi issues with some of the CM 10.1/10.2 ROMS. Since there is not really an "official" CM 10.1 ROM for the sensation, you sort of have to accept that there may be some bugs. I would suggest trying CM 9.1 and see if that works for you. Since you seem to be doing a complete wipe and format before the upgrades, the only other problem could possibly be some sort of hardware issue. However, I suspect that since it worked well on a previous ROM that the problem is ROM related. I would suggest you try all the various ROMs to see if the problem goes (mostly) away on one of them. I'm current running a 10.2 ROM and have noticed intermittent problems with connecting to Wi fi, but, on the most part, things work fine.
Good luck!
hello.
I had a HTC One S, T-Online Germany branded, with s-on and the Viper rom(-> unlocked and rooted).
Then it ran out of batterie, (not the first time that happend after a long day) and when i plugged it in and turned it on again, the x-axis of the touchscreen was mirrored: The Display is normal but when I touch anywhere on the left side it acts like I touched at this spot on the right side.
I was hoping that it was some bug in the rom, and flashed it again.. while flashing I discovered that the same bug is in the recovery (twrp).
I reflashed the recovery and rom a cupple of times untill I lost hope.
Then I s-off'ed it and changed the cid (I wanted to do this since a while) and flashed some custom kernels to see if this would bring any change..
I have no idea what else I could try to solve this.. has anyone a good idea or do you believe it is an hardware bug?
sincerly, menessim
well I guess, no one can help here..
Hi Guys
Seems like this would be one of those things that's been answered before but couldn't find anything
I'm trying to flash AOSP ROM's from Viper, I have tried several ROM's
I haven't got any problems with flashing but when I get into the ROM I have no touch screen, it's completely unresponsive. Volume rocker works so I know the phone is responding, just wont take any inputs from the touchscreen
The screen is fine, it works in Aroma and I went back to Viper and that was fine too.
I have upgraded firmware and HBOOT
I also tried manually flashing the boot.img from the AOSP ROM's but no luck
I'm sure it's something small I'm missing, anyone know what it is?
HBoot 1.27.1100
Firmware 3.32
Radio 11.22.3504.07_M
S-OFF
Bump
Can anyone help me?
One more time
Piemole said:
Hi Guys
Seems like this would be one of those things that's been answered before but couldn't find anything
I'm trying to flash AOSP ROM's from Viper, I have tried several ROM's
I haven't got any problems with flashing but when I get into the ROM I have no touch screen, it's completely unresponsive. Volume rocker works so I know the phone is responding, just wont take any inputs from the touchscreen
The screen is fine, it works in Aroma and I went back to Viper and that was fine too.
I have upgraded firmware and HBOOT
I also tried manually flashing the boot.img from the AOSP ROM's but no luck
I'm sure it's something small I'm missing, anyone know what it is?
HBoot 1.27.1100
Firmware 3.32
Radio 11.22.3504.07_M
S-OFF
Click to expand...
Click to collapse
Which ROMs did you try? Also, did you try upgrading the firmware to 3.33?
Can you try CM10 and see what happens? From a quick google search, I found a case where the problem was driver related, and flashing newer drivers for the touchscreen worked. Also, does the problem happen n ICS sense ROMs?