Database Develop

Tilt Touch Screen failing after loading Dutts latest ROM

Hey there,
A bit new, just finished loading Duttys WM6.1.5.2.1972_Hybrid_V2_1_65.14.06[CubeV2] Rom. Seems great at first. Had to download Goodlink for the corporate stuff. It works fine for a bit, but as soon as an Outlook reminder pops up, suddenly the touch screen is completely dead. Tried all buttons etc on the front. The keyboard works and the buttons can be used as the menu choices, but it took a hard reset to fix it. Which then I had to reload Goodlink and it happened again.
Any patches or settings anyone can think of? Goodllink is the only add in I put in. Any other ROM's recommended perhaps? Thanks all!

Borg7of9 said:
Hey there,
A bit new, just finished loading Duttys WM6.1.5.2.1972_Hybrid_V2_1_65.14.06[CubeV2] Rom. Seems great at first. Had to download Goodlink for the corporate stuff. It works fine for a bit, but as soon as an Outlook reminder pops up, suddenly the touch screen is completely dead. Tried all buttons etc on the front. The keyboard works and the buttons can be used as the menu choices, but it took a hard reset to fix it. Which then I had to reload Goodlink and it happened again.
Any patches or settings anyone can think of? Goodllink is the only add in I put in. Any other ROM's recommended perhaps? Thanks all!
Click to expand...
Click to collapse
I notice this is your fisrt post so welcome. There is a great deal of helpful experience here to help but it does certainly pay to pose questions in the correct place. If you ever have a question about a ROM then post your question in that area and you will be far more likely to get the helpful anser that you want. People are also sometimes too quick to 'Flame' people making such errors - but not me so hopefully this will help:
I am on that same ROM and have noticed that after initial ROM installation that the touch screen is initially 'prone' to what appear to be freezes. In fact I noticed on my device that I had to press quite hard to get any interaction with the screen and sometimes it did not respond.
Cannot say why but this has now completely gone and did so with each ROM install. It took a few soft resets to see the screen working correctly but it is great now! So it may not be your additional software. Just try sticking with it for longer and some soft resets. You might also try tweaking the sensitivity of the screen.
Suggest you search within the correct area and you'll see few comments about this kind of thing (but not many).
Regards

Thanks Tony. My first time posting so wasnt sure where to put it. Have done all you suggested. Worse case, back to the ATT rom, oh well. Will search also and try posting in the right location. Thanks!

Borg7of9 said:
Thanks Tony. My first time posting so wasnt sure where to put it. Have done all you suggested. Worse case, back to the ATT rom, oh well. Will search also and try posting in the right location. Thanks!
Click to expand...
Click to collapse
i just reviewed the software online and i can make several predictions why this is conflicting with the rom. 1) htc home
go to settings>personal>today>items>and uncheck htc home.
let me know if goodlink works thereafter if not I have a few more predictions to why it doesn't operate correctly.
Oh, and i just noticed you had a cube version, which could also be conflicting.

Thanks for the input Red. Tried that to no avail. Even tried soft reset afterwards. It is dead before goodlink even starts. BTW, this will be worth a Pint or two if you get me working.
I thought it might be the Cube version so after several hard resets(storage clearing), I went ahead and flashed it with Dutty's Non Cube version just to see if that was it and it wasn't. I tried tuning the touch screen too, bumping sensitivity up to 200, didnt help either. Tried loading the tweaks program, but nothing there either helped(actually cant even use it when frozen). The keypad, buttons all work, but the touch screen is dead. Hard reset fixes it, loading Goodlink, which I have to have for its a corp phone, kills the touch screen. I believe it worked for a few minutes, then locked up. I need to reverify that just to make sure it didnt happen immediately with Goodlink install. Very strange.

AT&T Tilt 6.1 Lags

Since upgrading to the AT&T 6.1 ROM I have 2 recurring issues. First, the device seems to have "busy" times when it will not respond to screen taps. If I turn off the phone radio the problem goes away. Second, the on/off/sleep button on the side will occasionaly turn on the phone from sleep for less than the second. The screen flashes and then back off. The next press of the button will turn the phone on.
I have seen these problems posted on other forums but not here and have not seen any solutions posted. Has anyone else seen these problems and are there any fixes?

Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.

The power button issue seems to be related to WM 6.1 (it's been present in every 6.1 ROM I've used). I've read several comments about it in several different threads. NotATreoFan (NATF) posted a 'workaround' in his ROM thread which has worked perfectly for me. Simply hold the power button for a very short time instead of just pushing it - .5 second works fine.

The power button issue has been revealed as a "feature" AT&T added to their 6.1 ROM. It is intended to prevent accidental powering on when the phone is in your pocket.

NotATreoFan said:
The power button issue has been revealed as a "feature" AT&T added to their 6.1 ROM. It is intended to prevent accidental powering on when the phone is in your pocket.
Click to expand...
Click to collapse
Some "Feature"

Kuschelweich said:
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
Click to expand...
Click to collapse
I had the previous stock ROM installed and whatever SPL version that was. The power switch is an interesting feature, I guess now that I know it, it makes sense. The Tilt power switch is so hard to press that it seems unnecessary.
Has anyone else experienced the lag. It is very noticable when I am playing a game like solitaire. The phone will work fine for 2 or 3 minutes then be unresponsive for 10 or 15 seconds and then be good again. I haven't installed any 3rd party apps yet, just run them from my SD card.

I gave up on the official ROM, and had to be selective on which ones to load up. My favorites were the basic naked ROMs (NATF-it will be missed, yes yes, go Phillies-That old dude sounded like a rock star, and AthineOS). Added applications (not all at once) to be able to see what programs would mess up the speed or even the sound (found out that a certain version of SRSWOW would render the volume control and anything having to do with sound as useless). Ended up with what I think is a completely functioning, lag free WinMo phone. Yes, it took a little while, but worth the effort. So far have over 35 different programs/customizations along with Igo8 and Manilla 2D (w/o Youtube or GoogleMaps) working together beautifully. To save me the trouble of having to load cabs one by one I installed SASHIMI to my storage card and, voila! Almost automated reloading of all cabs...

I've experienced the lag across some new cooked roms I've been trying. I'll have to go back and figure out the SPL situation to see if that fixes it. The lag is super annoying though.

Kuschelweich said:
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
Click to expand...
Click to collapse
Yup that was exactly my problem. I still had V1, what a huge difference, no more lag. Thank you!
TracyD follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=433835

Lev00 said:
Yup that was exactly my problem. I still had V1, what a huge difference, no more lag. Thank you!
TracyD follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=433835
Click to expand...
Click to collapse
I ran through the tutorial and updated the SPL but that did not fix the lag. I ran the unlocker and that seemed to do the trick. No more lag. I had already determined that I could stop the lag by putting the phone in flight mode. There must be a problem with the stock ATT Radio.

Small problem

Hi,
I have tried several ROMs, all of them work just fine until (after a period of time that may range from hours to days) and when I soft-reset my device, it acts like if I hard-reset it; goes through the setup, contacts gone.. etc. Anybody?
I do flash ROMs following the the steps in the related threads.
I've tried to search threads for anything like this, but I couldn't find any. (I hope I didn't miss any post, I know how annoying it would be for more to ask for something that was asked before).
Ah, and this is my first post! I'd like to thank all the devs for their outstanding work.
Thanks.

How do you reset the device from the back of the phone or from the software.
If you do it from the back of the phone, it should only do a saft reset not eraase anything.
If you do it using software on the phone, It maybe written to do a hard reset, I advise to check with the maker of the software or ROM what type of reset it is suppose to do.

[Q] Touch issue

At a certain point on my screen, the phone thinks I am touching it.
I dont know how else to explain it but a 'phantom touch'.
Its repetitive and very annoying.
It seemed to start after I flashed some custom ROMS.
I flashed back to stock (2.3.5) in the hopes of it being fixed but it seemed to follow me.
Has anyone had this issue/knows how to fix it?
Thanks

It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle

dr. xp55 said:
It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle
Click to expand...
Click to collapse
It seems to have just gone away on its own. Cheers for the help anyway, would have done this if I still had the problem.

It seems to come back when I flash a ROM.
I flashed the German ICS official ROM (which is great btw), and it seems to have come back.
Hopefully, someone can provide me with a solution, perhaps its a corrupt system file?
Still, it goes away when the phone is charging.
Any ideas at all?

I'm not sure if this is helpful, but I faced the same issue when I flashed ParanoidAndroid yesterday. In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive). It was then that these phantom touches started. I set it to 100(max, least sensitive) and I couldn't get the touchscreen to register any touches at all. The Spen worked in both cases, so I just used that to reset it.
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.

Hi, I think this seems to be the trick.
I was unable to find the code to access the settings menu you described.
However, I installed TouchScreenTune, and that seems to be working for the moment.
Will post my results in a few hours or so.
Thanks

bloodyhippo said:
In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive)....
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.
Click to expand...
Click to collapse
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again

novastorm17 said:
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again
Click to expand...
Click to collapse
You're right, I couldn't find one that'd help either. Hmm.
Do you still have the problem?

It hasn't gone away, but I think the frequency at which it occurs has reduced
Any other ideas/any other way to do your previous method?
Cheers

Okay so here is all the information I have.
No matter which ROM I flash, the issue of the random touching continues.
Ive tried without root, and tried a complete reinstall (by formatting all data and storage)
I found a CWM restore I made 6 months ago (long before the issue started). That didnt work either.
Things that DO work:
TouchScreenTune seems to greatly reduce the frequency at which at occurs by decreasing the sensitivity of the screen, however, it makes it harder to use the phone.
Plugging in USB stops it completely, but when its removed, the issue comes back.
I thought since it is following me through different ROMs it is a hardware issue.
Does ANYONE know a fix/heard of this before?
At the moment Ive resorted to using my old IDEOS (oh god) and have begun working towards a warranty rectification.
Thanks anyone who can help

Update from Samsung:
Issue due to motherboard/touchscreen
Cheers for your help

[Q] HTC One Screen Problem

Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!

anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?

Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.

LibertyMarine said:
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Click to expand...
Click to collapse
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.

anibjoshi said:
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
Click to expand...
Click to collapse
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!

anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
Try flashing a Sense ROM, like ARHD or MaximusHD?
Enviado de meu HTC One usando Tapatalk

LibertyMarine said:
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
Click to expand...
Click to collapse
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.

well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?

IINexusII said:
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
Click to expand...
Click to collapse
No I rooted the device but did not install any root apps...i unrooted the device to install the GPE Rom(not necessary i know, but it seemed like a proper way) and found that it started giving problems immediately. Can non-root regular apps also cause such problems? I had installed only a limited number of apps anyway, updated the pre installed apps, facebook, twitter, whatsapp, some games..thats it..nothing wierd..

Might be a Screen-Off max. frequency issue. Like the phone gets only 500Mhz in sleep mode at maximum. Which is to low for an incoming call. Could you install a app like Android Tuner or Trickster Mod to check your Screen-Off Max frequency. If it`s that low, set it to ~1000Mhz.

anibjoshi said:
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
Click to expand...
Click to collapse
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.

LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One

LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again

Yup try installing kernel and custom rom.
Remove the case and try ( i know this is stupid thing but can give it a try)

Jvov said:
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
Click to expand...
Click to collapse
Thanks for your help buddy! I really appreciate it!

anibjoshi said:
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Click to expand...
Click to collapse
Thanks ! That's awesome and gives so much motivation! If you find out that you have a hardware defect and that you have to send it to HTC, I'll give you some information how to deal with those guys that you get your warranty.