Hi guys I updated my rom the other day to a touchflo rom but then whent back to touch 4.02 but when I pressed on to my contacts the blue selection bar comes up and just goes mad on the screen. Its almost as if I'm messing with the track ball but I'm no where near it, it started doing it all the time but since Ive flashed to another rom it seems to have settled and only does it every once in awhile can anyone think of what it might be.
Thanks for your time.
Sorry if I'veput this in wrong section
Hi gys just a quick update I think that the problem is due to dials mechanism messing up so I was wondering if anyone know of a way to disable the ball and dial either by removing a driver or If I'd have to damage them
Thanks for your time
Related
i have herems 100 and last rom i had was tnt 2 it was untill two days ago the screen somtimes doesnt close sometime open only white and when it works fine the screen view is shifted down i see parts of the soft keys at the top of the screen
i also have another problem s that the bottons at the buttom doesnt work sometimes.
the phone didn't fell down from me or hit
please if any one can help
MMM
Same problem....
I'm experiencing the same problem on my herm100. It has been like this for a few weeks now. I'm running the latest T-mobile test rom. I have problems with the buttons and also the screen both going white sometimes and shifted down a little. So I also see some little part of the softkeys at the top of the screen.
Anyone know what is causing this, and how to get it solved???
Originally Posted by nosgergj
I have this same issue, but i also have a white-out problem which I am trying to fix first. Like you the problem is intermittant at best - whilst it happens all the time, I cannot put my finger on a sequence that actually causes it. I am trying to fix this other problem that is more annoying at the moment, but if I stumble across a solution, i'll be sure to put it on here.
regards,
i found this on http://www.4winmobile.com/forums/he...llment-black-5atin-normal-medium-light-7.html
i'll keep looking there hoping to find a solution
MMM
http://forum.xda-developers.com/showthread.php?t=297994&highlight=buttons+Hermes+solved
MMM
after flashing three different roms then coming back tnt beta the problem went now am very happy
hope this could be the solution for you too
MMM
problem came back and it's worse now
Hi All, I was wondering if anyone has run into these issues, I mentioned them in a thread but decided to make a new post. this happens in both roms
1) Is anyone having issues that some contacts in the messaging client (HTC) lose their pix and you see a sim card instead of their photo? If so anyone know how to stop this?
2) Sometimes when hitting send after writing a txt msg, the screen right away goes black where you have to hit the power button to bring the screen back on.
3) Anyone notice that with this rom, the home weather screen is slower then the stock eu 6.5 with 2.1 manila? Seems it has something to do with the clock, because if you slide the clock up and show only the clock in the bar the weather animation plays just as the demo does (Especially the rain and wiper blade). Can someone check to see if the home page possibly has a memory leak or bad coding? And is there a way to change the flip clock easily to not flip or to a different clock on these roms?
4) Anyone notice during a call there is no way to get to the call history from the dial pad or anywhere? if you know please enlighten me.
5)Anyone figure out how to make the htc sms program bump up the writing section instead of it taking its time?
6) I tried using the SDKCert cab, and it seems to me that it messed up my Sea rom install. Anyone know of another way to re-map the keyboard for an ATT Tilt 2?
Any help or guidenance would be greatly appreciated. And any help I can give I will, I have a spare HTC tilt 2 phone and can test anything out. right now trying to figure out why MSVC doesnt read back txt msgs with another senior member. Hopefully we can get this to work I need that!
No one else has these problems?
Okay here is another one, anyone figure out how when you get a txt msg and hit the msg tab it goes to the first msg and not be stuck on the last msg you read on the msg tab?
AngelDeath said:
Hi All, I was wondering if anyone has run into these issues, I mentioned them in a thread but decided to make a new post. this happens in both roms
1) Is anyone having issues that some contacts in the messaging client (HTC) lose their pix and you see a sim card instead of their photo? If so anyone know how to stop this?
2) Sometimes when hitting send after writing a txt msg, the screen right away goes black where you have to hit the power button to bring the screen back on.
3) Anyone notice that with this rom, the home weather screen is slower then the stock eu 6.5 with 2.1 manila? Seems it has something to do with the clock, because if you slide the clock up and show only the clock in the bar the weather animation plays just as the demo does (Especially the rain and wiper blade). Can someone check to see if the home page possibly has a memory leak or bad coding? And is there a way to change the flip clock easily to not flip or to a different clock on these roms?
4) Anyone notice during a call there is no way to get to the call history from the dial pad or anywhere? if you know please enlighten me.
5)Anyone figure out how to make the htc sms program bump up the writing section instead of it taking its time?
6) I tried using the SDKCert cab, and it seems to me that it messed up my Sea rom install. Anyone know of another way to re-map the keyboard for an ATT Tilt 2?
Any help or guidenance would be greatly appreciated. And any help I can give I will, I have a spare HTC tilt 2 phone and can test anything out. right now trying to figure out why MSVC doesnt read back txt msgs with another senior member. Hopefully we can get this to work I need that!
Click to expand...
Click to collapse
I am having issues with mine also.....
i am actually having a bit of a hard time with the new HTC 2.5 ROM.
I have read through the threads and it seems other people are having the same problems.
i.e.- sms very slow-
speakerphone bug- once activated the other person cannot hear you, you have to turn off speakerph and turn on again for them to hear you.
I hard reset but still get the same problems.
I think after I try a few more tweaks I will be able to post a good assessment so others will "hopefully" not have to deal with the same problems.
I hard reset to clear everything and then flashed the ROM again. Took care of some problems.
I installed your Volume Settings cab from another post to take care of the low vol prob.
After flashing the ROM the speakerphone is working. ..
1) I have not had a problem with the contacts
2) I am still having this problem with the text msg
3)To fix the Home screen issues- I installed Cookies Home Tab and his editor
4) Haven't noticed the during call problem but will check it out
5) I installed SMS chat cab to help with the text problems and also disabled the HTC msgng. it is still slow but not as slow
6)I used the Tilt 2 Keyboard fix....
Hey there.. I just installed the Energy ROM after having received this phone as a gift from a friend (with an unknown other ROM installed). I haven't had any problems with it for several weeks until just earlier today when the Quick List has decided to randomly start appearing on my screen. I don't even know how to trigger that screen to appear myself, but I can leave my phone unlocked on my desk and it'll randomly show the Quick List for a little while, then it'll vanish, sometimes extremely quickly. But I can't do anything on the phone anymore since it's constantly appearing and interrupting whatever I'm trying to do.
Like I said, I attempted to install an Energy ROM (Energy.RHODIUM.21916.Sense2.5.Cookie.2.0.Mar.08.7z, according to the file I downloaded from the Energy website) and it just finished no more than 30 minutes ago. As soon as I turned the phone back on from a reboot, that dang Quick List screen appeared.
Does anyone know why it keeps popping up and how I can get it to quit? Or is there some way I can just disable the Quick List altogether (as the options on it aren't really useful anyway..)? Thanks for any help ya'll can provide!
Started having this problem a few weeks ago. Did some hardresets, some task29 and tried different roms. But this quick list keeps appearing outof nowhere. Starts to get frustrating.
It's happening again...
So, for no reason that I could tell, it magically started working again (same rom as listed above) and I never saw the Quick List window again until today.
Today, I was using that same ROM as before, but the Quick List window started appearing. I thought that perhaps it was just something to do with that build, so I upgraded to the English build available at (well, tried giving the link but apparently I haven't posted enough, so never mind). It's at "http : // Energy Roms dot com forward slash www forward slash flavors forward slash sencity.html" for the HTC Touch Pro 2 Cookie (April 8, 2011 version). The ROM installs without a problem (absent the annoying attempts to get the phone to not constantly display the Quick List) but as soon as I power the phone on, the Quick List starts blinking on again.
I searched around as before for a solution and thought I could just disable the setting so that when I hold the end call button, it displays the Quick List, but after 10+ attempts to get to the settings window without the Quick List appearing and interrupting me (then closing itself automatically and displaying the Home screen), I finally got the setting saved and it didn't change anything.
Is it possible to just turn the Quick List feature off? Is there some known reason why it has possessed my phone? Thanks for any help ya'll can give.
Is there still no solution for self appearing Quick List? because I have the same problem :/
EDIT:
I've solved it The front keys flex need to be reconnected to main flex because "endkey" was self pushed what in energy rom is configured to turn on Quick List.
Hello xda-developers,
as I searched for a long time and didn't find anything useful, i decided to post here on xda for the first time.
My problem is the same as mentioned in this post or in the youtube video:
Post
[YOUTUBE]https://www.youtube.com/watch?v=0SLA0WctmuU
[/YOUTUBE]
It is not possible to pull the notification bar down in horizontal mode. In landscape mode, there is no problem. The screen is not reacting in this area, even in ladscape mode -> the navbar is not working in landscape mode.
This problem started a few days ago on Resurrection Remix (Marshmallow 6). After it did start, i flashed back to Stock G3 Rom and it still consisted.
Then the screen worked for a few hours again, thus it thought "Fine, it's working, you can flash back". I flashed to CM13 and it worked fine.
After a half day, it didn't work again. So, thats the normal case: It is working for a few hours and then it is not, for 4 days now.
I don't know what this could be and I wanted to ask you guys, if you have any idea, what to do...
So, I would be very happy, if you could answer my following questions:
1. Is it possible, that it is something with the software? I though, that every time I flash a new ROM the whole software is new and bugs are "away"... If this is true, than my problem can't be a software problem. Especially that I've flashed back to Stock, which does install everything new...
2. If it is not software, could it be hardware? But that's not really logical because it works sometimes. Only thing is a loose connection. But can there be a loose connection, which makes the screen not working only on this smart area of the screen?
3. As I flashed Stock ROM, there was the area thicker, because the notification bar was thicker. This absolutely makes no sense, does it? It seems, that the system says "Oh, thats the area which the notification bar covers, let's deactivate it"
4. Do you have any other ideas what to do?
I'm afraid of sending it in because I think, that it will work, when LG is testing the phone.
Excuse my english, i know that it is not the best:angel:
I hope, you can help me because this is a very ****ty problem...
Thank you in advance and lets discuss about it
Arkas96
Same here
**BUMP**
I can sometimes get it down from the upper left, but not always. For me it sometimes shows a persistent touch and the top center of the bar until I lock and unlock it again. Its definitely a software issue. Wish somebody would look into this!
Awkward Problem
Hello,
Nice to have an answer even in it is not a good one
I "fixed" the Problem by sending it to LG service. THREE TIMES. It really took 3 times that they found the Problem. Changing the touch panel solved it for me.
Hope everybody with this Problem finds a solution. Good luck
Hi guys
I bought a cheap OnePlus 5t. It's had a hard life, but everything seems to be working ok.
Except- 3 or 4 times a day it starts having phantom/ghost touches. Usually at the edge of the screen (I put touch tracking on) -I've rebooted, factory reset, but no improvement.
Anyone know the best way forward? Don't think I'll get warranty, so is it likely to be hardware or software? Unlock it and put a new Rom/kernal on? Or try fitting a new screen?
Is there any way to know whether it's software or hardware?
Any experience or suggestions gratefully received
Thanks
What rom are you on? I used to be on custom roms and I noticed phantom touches. It wasn't till I went back to oxygenOS and disabled nav bar completely did I fix this. I found that having a nav bar greatly worsens phantom touches because when you type on the keyboard you tend to touch one of the nav bar buttons.
Also maybe check to make sure you are on the right firmware
Thanks for the reply.
I was on stock, I'm now on lineage. It hasn't fixed it.
The touches are always up the left of the screen... When they happen theyre happening hundreds of times a second, as in its not one touch... The screen becomes in unusable because there's so many touches on the top left of the screen -
It lasts for about a minute, or untill I force restart it...
It's driving me nuts to be honest. I've even taken out apart to see if re-seating the screen would help but it didn't.
Would a custom kernal help?
I don't have any experience with custom kernals. And this problem seems a little different than the one I had which was more a single phantom touch.