Related
well hello there xda community and others,
I've recently obtained knowledge of the "PreRelease" of WM6 Crossbow. Therefore I went in search of it and installed on my i-mate Jasjar and briefly used every version. During my experience of using it...I concluded to say how it seemed pretty speedy, except one minor issue (but not minor for normal use) The issue is the two soft keys...generally named Calendar & Contacts. The issue is...when pressing either one, hardware button or through screen 'n' stylus, there was a whole second delay. I know that this isn't a final version, but in the videos I've seen of the OS, the soft key action is executed immediately with no waiting period. I haven't read of this issue anywhere else...Might someone enlighten me of whether this is an isolated issue on my individual Jasjar or if this is common amongst others.
Thanks - any comments are of use to me
Ho all,
I am having a serious problem with touch display alligning. It happened two times, on resuming it from stand by, touch screen lost its configuration. So that display becomes unusable becouse finger touch doesn't have a correct corrispondance. I had to restart device to have it working again.
Have you installed any custom ROMs? If not...
You'll want to contact HTC as this sounds like it may be a hardware issue. http://www.htc.com/www/support/nexusone/
kozm0naut said:
Have you installed any custom ROMs? If not...
You'll want to contact HTC as this sounds like it may be a hardware issue. http://www.htc.com/www/support/nexusone/
Click to expand...
Click to collapse
No, I still haven't rooted it. It's with stock rom. HW problem? I wish in a SW issue..
I've seen this issue crop up on my rooted N1 as well. A reboot fixes it, as does waiting it out. For some reason I seem to notice it happening when I'm in the browser. There's a thread here about it (which evidently I can't link to since I'm new). Check the second page of the general section, the subject is "touch screen issues".
Seems like a software issue to me, but who knows.
The first thing to do if you have these types of obvious software issues is a hard reset (Settings>Privacy>Factory Reset). If that doesn't work, then it's time to call HTC.
uansari1 said:
The first thing to do if you have these types of obvious software issues is a hard reset (Settings>Privacy>Factory Reset). If that doesn't work, then it's time to call HTC.
Click to expand...
Click to collapse
Thank you all! I found the post where this is being discussed.
This is an issue many people are experiencing on google support forums, in fact it is the second longest thread after the 3g issues. It has also finally been pinned. Here is the link: http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en#all
Anyone experiencing the same problem please post in that thread, the more people that post the more chance for google to acknowledge this and remedy.
BTW I also experince issues with the touch screen which happen quite randomly and can normally be cleared with a power on/off. When the screen goes bad the touch is no longer registered in the correct spot on the screen.
So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?
Hello' this is my first post in this forum. I'm posting from Italy and I'm just a new Android user. Hopefully I can give my little contribution to the forum.
For the moment I have to report two issues on my new HTC Legend: suddenly the keyboard randomly stop to work and the writing field become "grey" so even if I press any letter nothing appears.
It happen also that headphone control (used to listen music) does not respond sometimes.
It seems that these problems are occuring after some stand and the only way to temporarily solve it is to re-boot the device.
I guess there is some software issue or some application crash on the device.
Last week I have already tried to hard reset the phone but the problems appeared again after a couple of days.
Please, do you have any suggestion or experience?
Thank you
Then if no reply I can suspect that nobody has observed the problem that I have reported....
For a long time now my Nexus 7 2013 (flo) 32gb has had this annoying touchscreen glitch where it will get false readings causing it to push buttons I didn't want to press, zoom when I wanted to scroll, and generally make it unusable unless I rebooted (which on some occasions didn't fix the problem). After doing some research, I found that it seems to be a common enough problem, but there was only one thread that claims to have fixed it. Now, to be honest I didn't try his method, as frankly it looked long, complicated, and I never found the time. Yesterday the thought occurred to me that the screen may actually be picking up real interference, and that it may just simply be to sensitive, so I set about to decrease the sensitivity on the device. To decrease the sensitivity ( THIS REQUIRES ROOT) I used root explorer (you may use any file explorer that can access root files) and went to the folder "/system/usr/idc" and opened the file "touch_dev.idc" in a text editor. In this file I found the line "touch.pressure.scale = 0.0125" and changed the value from 0.0125 to 2.5. I then saved the file and rebooted. Since doing this I have not had the touchscreen glitch, and I have been using the device for a little over 24 hours now. I used to get the glitch about 3 times a day. I will continue to test this config, to see if it actually does fix the problem, but due to the nature of the problem, the only way to know if this fix works, is to use it over a long period of time. I will remove this post if the issue ever returns and I am not able to fix it using a similar method.
Notes:
* the directory is "/system/usr/idc/touch_dev.idc"
* increase the value of "touch.pressure.scale" to decrease the screen sensitivity
* make sure you have write privileges (in root explorer, don't forget to hit the R/W button before opening the .idc file in a text editor)
* don't forget to save the file
* after saving the file, reopen it to make sure the change took place, if it didn't make sure you have write privileges and actually saved it
* don't forget to reboot for the changes to apply (I'm not sure if its necessary, but am willing to bet that it is)
* this should work with other versions of the nexus 7 flo, not just the 32gb
* I am not liable for any damages caused to your device (you should know this by now)
*I have only tested this on one device, as it is the only one I have access to with this problem
* If this fix works for you, please let me know below, feedback is appreciated
* I didn't return the device, simply because I lost the receipt, and don't know if the warranty is still in place
Edit:
This does not work, after more testing issues returned. But I will continue to try different values to see if this can fix the problem.
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Ok, yeah I'll have to do that. I posted this a bit early, as I was seeing positive results at first and got excited. Thanks.
yes, there are 3 different fixes posted, ts10, ts20 and ts30.....and there are a couple of others in that thread too. I found the experiment ts18 worked best for me. ts10 was an improvement, ts20 better, and and ts30 too sensitive. after sticking with ts20 I decided to try the additional ones and so far 18 is best for me.
try the 3 main ones....and use the one that works best......if you still see little bugs in it, then try the experimental ones closest the 10 or 20 or 30 that worked best for you. I feel like I have a brand new device since running this fix on mine. You don't have to be rooted, but you do have to be unlocked.
I have a wifi 32 gb model manufactured Sept 2013
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
pre4speed said:
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
Click to expand...
Click to collapse
Well that's really up to you. If it works fine then you don't need a fix.... But if there are glitches.... Well you know where to get a fix.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Okay, but you do know there are SEVERAL different issues with the touchscreen & that thread only will fix (partially fix as everyone I know that has tried it, still has occasional issues) one of three or more issues. There is also a grounding issue, that your reference WILL NOT FIX. There are also issues with the ribbon cable placement, which was my issue & several others, which requires opening the case & either reattaching the cable or reinforcing the connection at the terminal, which fixed mine & a few others. Just saying, I wouldn't blindly state that "this fix" will solve all your issues.
can anyone provide a flashable patch to try? Thanks
This problem is starting to annoy me really badly D:
I have seen different types of issues on my N7 2013 - 32gb. I tested using YAMTT app.
1. touch will not be registered at certain areas or ghost touches - this is worse with stock rom the tablet came with. the best solution for stock rom is to either try ts10, ts09 etc. or try different roms. I finally settled with AOSB rom with Glitch kernel, working fine.
2. touch will work fine if you hold the tablet in your hand or have it connected to usb or headphones. but wont register or see ghost touches if you keep it in a flat place and use it - (grounding issue) - there are various fixes i have seen. (a) remove the tablet and do fix (b) try different magnetic cases if you use one (c) some report that ts file fixes fix these too.
Mine still have this issue. I use it by holding it. Have to try the fixes above sometime.
3. Touch is too sensitive - I believe that is what OP suggests a fix. Sometime when i was scrolling through emails, suddenly a click registers and it goes inside an email. I will try this and report.
Even if one of the above fixes work, after some time if you see problems again, do a reboot and it will be back working normal again. I am still not convinced if it is just a software issue or a hardware issue or both.
This seems to have helped with the 'jumpy' touch issues I've been having. It could also be because I just rebooted for the first time in over a month.
I set mine to 3.0, for me its a lot better than 2.5
Can you (or someone) please post a direct link to the main thread (or others) - I am having a little trouble locating. Thanks. By that I mean main thread mentioned in 2nd post regarding T10 etc
This seems to be it:
http://forum.xda-developers.com/showthread.php?t=2428133
Nexus 7 unresponsive screen or reaction without touching
Started having trouble with my Nexus 7 2013 not responding to touches or sometimes just entering characters not touched when doing keyboard entry. Thought it might be sensitivity issue, but checked one of the posts on line here and found that mine was actually set more sensitive than the suggested amount. Thought it might be a software issue as it really started getting bad after update to Version 5.0.2. I found that it seemed to be worse after notices that some of the apps had updated. My solution albeit imperfect was to start deleting apps until I found the problem. Not sure which it is, but it appears to be some of the in built apps that come from Google. I forced stop on several of these like play movies and books and did the uninstall procedure. Like magic, my Nexus started responding like if was just out of the box. Unfortunately, Google has these set so that they evidently run automatically when the tablet is turned on and update by themselves (which seems to have the effect of turning them back on as well). In any case, when I start getting sensitivity issues like it not responding to areas of the screen or not swiping, I go to apps and go through the list forcing a stop on all I don't use (especially You Tube) then uninstalling (only option seems to be going back to factory versions). Nexus then works OK until the next "automatic" update, I actually use (i.e. enable) one of the apps or turn the Nexux completely off and reboot. At least it is less frustrating doing this every week or so than having a non-responsive tablet. If anyone knows how to "permanently" kill these Google apps or at least turn off the auto-start and auto-update functions, I would be pleased to hear it. By the way, the best I can tell, stopping these does not seem prevent You Tube videos playing or any of the other tablet functions from working, but maybe utilizing them from a browser or whatever is what triggers them coming to life again. I'm a novice so I don't know.