Related
Just updated to v1.2.0 and re-rooted, but now I have a strange problem. I tried searching these forums, and The Google, but couldn't find anything helpful.
When you click in a text field (e.g., the search box, or the address bar of the browser), the keyboard will pop-up for about 1/2 second, and then minimize again. You can do this repeatedly with the same result - the keyboard just won't stay open.
I've tried rebooting, and even installing a different keyboard (can't get them to appear as an option in NCTools).
Has anyone else run into this? Were you able to fix it?
This used to happen to me when I used a Archos 28 "tablet". It was because there wasn't enough RAM most of the time, so it would close the keyboard to make more.
I doubt that's the case for the Nook Color, though. I've never had a problem with memory on these things.
I've had that happen as well but strangely only when the nook is at an angle like when I'm laying on my back in bed with the screen above me angled downward, tilting the screen so that it is facing up solves it for me, like I said, strange.
Sent from my NookColor using XDA Premium App
ninpo said:
I've had that happen as well but strangely only when the nook is at an angle like when I'm laying on my back in bed with the screen above me angled downward, tilting the screen so that it is facing up solves it for me, like I said, strange.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Did you do anything to resolve it, or just live with it?
I just live with it, simply changing the angle seems to solve it, that's a simple enough fix for me.
Sent from my NookColor using XDA Premium App
FYI for anyone that runs into this thread later:
There must have been some glitch in the rooting process that screwed up the keyboard. I ended up doing the whole process over again by restoring back to stock 1.1, updating to 1.2, and re-rooting. Everything works like a charm now.
Incidentally, the stock/update/root process is a lot easier the second time you do it.
Hi, I have the exact issue, anyone knows where I can download 1.1 rom or 1.01 rom? I tried all 1.2, 1.3, 1.4.1, they all have the same issue. Thanks.
Every time before install new ROM, I formatted system, data, and cache, but seems still not totally formatted, cause 1, the keyboard part still mess up, now even cm7 on emmc has the issue. 2, the wifi connection still saved because it auto connects to my network every time flashed. Any idea? Thanks.
My nook is booting up fine, but once it gets to the android interface after a couple seconds or minutes, it just freezes and I can't do anything until I reboot. Has anyone else had any similar issues like this?
If this is a repost, I'm sorry just point me in the right direction as I could not find anything.
Edit: This may be linked to beautiful widgets? I have reflashed CM7 twice now, seems to be linked to that.
Yep, BW will do exactly that. Fancy Widgets is a decent alternative for a large clock widget
I've been having a similar problem after I rerooted and installed phiremod. I can rarely even boot up and have a functional tablet. It almost instantly freezes and must be reboot only to do it again.
reeeaaally pissing me off.
---------- Post added at 05:24 PM ---------- Previous post was at 05:10 PM ----------
after about 10 reboots I was able get it running long enough to uninstall beautiful widgets and after another reboot it seems to have solved the problem. Its a bummer though cause it a good app.
I had the same problems with Beautiful Widgets and the BeWeather widgets. I've read Fancy Widgets work and I'm currently using HD Widgets since it has a 4x4 widget and hasn't given me any problems.
Sent from my PG86100 using xda premium
I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)
mondegreen said:
I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)
Click to expand...
Click to collapse
Are you overclocked? And I assume since you mention SD card, you normally run from the internal storage? And is this a hard freeze while you're using it, or some time later while the screen is off?
1. Not overclocked. Completely pure, just-installed, CM7 with no changes to default settings. No GApps even.
2. I had the same problem when running from internal. Switched to the SD card to see if that would change anything--it didn't'.
3. Hard freeze occurs while using it.
Thanks!
I also had major freezing w/7.1. I flashed the last nightly (11/16/11) and gaaps.
http://download.cyanogenmod.com/?device=encore
Although freezing might happen once in awhile, it's rare now. I only use one widget (wifi signal). Everything else is pretty much default. No overclocking, live wallpaper, themes, etc.
I've downloaded about 20 apps so far.
Yep, it is caused by beautiful Widgets. I had the same thing happen and I posted on their development forums. I was able to get the startup logs and send them to the developer. Then the response was he could not figure out the bug. The logs clear showed a problem when trying to load the bw, but the bug may have been down deeper the operation system.
Not sure. But bummed none the less.....
Sent from my NookColor using Xparent Green Tapatalk
I was having a similar issue. However I didn't have Beautiful Widgets installed. I solved this by going to the Cyanogen CPU settings. I set minimum to 800mhz, max to 1200mhz and the profile to performance. I also checked the SET ON BOOT (can't recall the exact wording.) After a reboot, I haven't experienced any freezing. Hope this helps you guys.
Thanks.
I will give that a try with a beautiful widget on my home screen. then I will report back on my findings.
Update: nope that did not fix the problem for beautiful Widgets. I made your changes, rebooted, added a super clock widget to my home screen, rebooted, it froze. Thanks for the idea, though.
Sent from my DROID2 using Xparent Green Tapatalk
I've been following this thread as I have been experiencing the same thing, I ridded the nook of BW and it hasn't helped the freezing upon boot issue, even knocked up the min setting to 800. I've reflashed a million times. This came out of no where.
Edit: its getting really annoying. This thing isn't even useful. Never occurs with the ics preview. Only with any cm rom.
Sent from my PG06100 using xda premium
Sorry to hear that. The only time I have really experienced freezing, it was always because of some application. Is there some application that you always install that could be causing the issue. I know at one point it seemed like a certain version of flash would freeze mine, even if it was just installed not being used. Are you using the most recent stable build of cm7?
for now I have switched to ics on my nook, just for fun, I wanted to be able to make my own nightlies so I set that up . Will have to try a beautiful widget on there once I make a backup.
Sent from my DROID2 using Xparent Green Tapatalk
same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
---------- Post added at 04:10 PM ---------- Previous post was at 03:30 PM ----------
carlosraf20 said:
same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
Click to expand...
Click to collapse
reporting back still freezes , i will install cm-7.1.0-encore-signed.zip stable tonight and see what happens, what oc kernel to go with stable cm?
So for what it's worth currently beautiful Widgets seem to work on nook color ICS without freezing it up. But ICS is still in it's infancy.
By the way are you running off an sd card or Emmc? Running off an sd card is not nearly as good and that can cause a lot of freezing. Just throwing that out there.
Sent from my NookColor CM9 pre-alpha using Xparent Green Tapatalk
Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium
peanjr said:
Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
how do u find out it was nook tweaks that was causing this?
Because it always ran just fine, until I installed nook tweaks checked "set on boot" for the cpu settings. I didn't change them, just ticked it. After that, anytime i rebooted, it was a fight to keep it on. So i removed the last thing i put on there, nook tweaks. Its not froze one time and I've rebooted it a whole since then. I reinstalled it but never opened the cpu settings, just edit the audio stuff, no freezes. Kinda wierd.
Sent from my PG06100 using xda premium
I just install cm 7.1 stable and change the kernel to daligrin 603011 and still having freezing issues . I don't want to do it ,but i guess i will have to do a complete wipe and then install cm 7.1 fresh.
Nook Color freezing issues
I too have having freezing issues.
Symptoms: I'll be using my Nook Color with no issues when it suddenly just locks up. No error of any sort on the screen. Screen does not black out. It just locks up. I think everytime it has happened has been after I've transferred several MB (over 5 at least) of data over Wi-Fi.
I'm running CM7.2.0 RC0 KANG build from 11/30/2011 from eMMC.
I'm overclocking to 1200 with the Min CPU set to 800 and the governor set to Performance. I also tried Max CPU at 1100 but that didn't make a difference. I'd had Min CPU at 300 but moved to 800 based on a suggestion found here. Setting the Governor to Ondemand didn't make a difference either.
I do have Nook Tweaks installed but have changed nothing from the defaults and nothing is set to start up at boot time. (I use it to get to USB Host Mode.)
With this build I haven't had any screens of death like I was getting on CM7.1. Just the freeze-ups.
Anyone else seeing a pattern with Wi-Fi?
I've never installed Beautiful Widgets.
I was deleting apps and files, no problem. And I think I was going so fast that maybe I hit delete all be accident when I was trying to delete google talk and EVERYTHING is deleted. My phone when black except for the notification bar, the phone was still charging and my F Secure program was going crazy keeping the memory card and all.
I just stayed like that for about 30 seconds and the screen blank except for the status bar and finally it slowly came back. First my back ground, then the apps. First it was slow and about 2 minutes it is back to normal, EXCEPT...
Now when I go into ES File Explorer, everything is gone, it says that ll my folders are empty. I pulled the battery and restarted and things seem to be extremely slow now. But I do have my list back and everything is fine but very slow.
How do I fix this?
You could have wrong rights on folders. If you have CWM then reboot into it and then go to Advanced and there should be an option to "fix permissions" or something. Use it and it should be fine (at least it should not make things worse ).
Bringing this back to life because I notice there is a big problem. My phone is EXTREMELY slow. It takes about 10 seconds to open every single app. Right when I got Gingerbread it was extremely fast, but after the incident happened above its very slow.
Even scrolling through my list of apps, which is a small list, it is very slow and does not scroll smoothly. Whats going on?
Have you got a Custom Rom or do you use Stock Rom?
Sent from my LG-P990 using xda premium
iExitus said:
Have you got a Custom Rom or do you use Stock Rom?
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
100% stock, besides being rooted.
Funny thing, I started deleting more apps, and I deleted a 3G counter and it seems to have made things faster now. But we'll see how it goes. With this phone, it seems its fast one day but slow another. Presently, it is fast again.
Thanks for the reply though. Avoid the program Onavo, it would take about 10 seconds to type one word in a SMS. Sorry for crying wolf again.
Why not flashing a decent (custom) ROM?
Time for a full flash lol
Sent from my LG-P990 using Tapatalk
Cm7.
Sent from my Optimus 2X using Tapatalk
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far
Hi all
I recieved the Update to ICS on 2. July. I was very happy about it and it is really great. But I recognized 2 problems:
-Preformance is not the best
and
-the touch doesn't always recognize more than 1 finger.
What I did to fix:
I tried a hard reset and it fixed the performance, but not the touch.
When does the bug appear:
Often, but not always. Sometimes it works fine and then it doesn't work properly
When I play games, some games needs to tap at varius points on the touch. When I fast tap then the touch doesn't always recognize any fingers. With 1 finger, the touch works fine, with 2 fingers, it doesn't always work.
I attached a link to show how the touch doesn't always work.
https://dl.dropbox.com/u/4910238/IncSTouchbug.mp4
I started the thread to find other people who have the same problem. At the moment I'm writing with the htc support, and I hope that I find more people who has the same problem, so I can give him the link and they try to fix that annoying bug.
i hope I'm not the only one out there and we and HTC can find a fix.
best regards
MrToastbrot
MrToastbrot said:
Hi all
I recieved the Update to ICS on 2. July. I was very happy about it and it is really great. But I recognized 2 problems:
-Preformance is not the best
and
-the touch doesn't always recognize more than 1 finger....
Click to expand...
Click to collapse
Hi MrToastbrot. I have the same issue, after getting OTA 4.0.4 update, from HTC. I noticed the problem early, so I've been searching all over the web to find some solutions, but couldn't find any.
Please write a message, if HTC Support does give you some useful information about this problem.
Best regards
Luckyone.
My Incredible S acts similar, if it is touched by 4 fingers - then fingers on screen are detected "jumping", like in video. That continues even when only 1 finger is still on screen, but ends when nothing touches the screen.
I would post a link of google ''android issues'' page, but I can't because of ''Spam protection''.
The thing I wanted to say is, that this problem doesn't only concern HTC users, but it appers on, for example, Galaxy Nexus with different android versions too.
One guy wrote : ''I've heard people claim its something to do with the digitizer losing calibration when getting hot and that locking and unlocking the device recalibrates it.''
Still waiting for solution.
Edit : p.s. yeah - factory reset didn't help it.
Edit2: ....or it did? Right after factory reset, i tested the multitouch - it still wasn't working. After I downloaded some apps, I decided to test it again, just in case, and it seems to be working now. .
Edit3: It seems, that the theory about digitizer getting hot is true. A minute after I plugged my phone to charger the multitouch stopped working properly. Sad. Well, I guess we will have to wait some updates from HTC, or put our phones in a fridge or something.
Cheers!
ALMOST Solution found!
All we can blame is HTC Sense. You see - when you unlock the phone, the locker(sense locker) does something to make multitouch not working.
When you go to the ''Apps'' menu in ''Settings'' and Force Kill HTC Sense(the one with green HTC logo), touch screen starts working flawlessly again.
After you lock and unlock screen again - it won't be working.
The thing is - I'm a bit afraid to disable Sense permanently.
Let me know if this work for you guys.
Cheers.
Edit : Force Stop ''HTC Sense'' with launcher logo too. I'm really confused, because I can't understand what Stock Launcher has to do with multi-touch issues...
Nice, so we have only to wait until htc fix this bug. But one question:
Why does HTC Sense affect, that the touch isn't working correct in games?
Sent from my HTC Incredible S using xda app-developers app
MrToastbrot said:
Nice, so we have only to wait until htc fix this bug. But one question:
Why does HTC Sense affect, that the touch isn't working correct in games?
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Solution, I think, is to do HARD reset. Atleast it's working fine now in ''MultiTouch Visualizer 2''. Haven't tried in games.
:good:
Note: This will return your device to its original factory settings(all the data from internal storage will be removed).
- With the phone turned off, press and hold the Volume Down key;
- With the Volume key held down, press and release the Power key;
- Release the Volume down key;
- Press the Volume down key twice to highlight FACTORY RESET/CLEAR STORAGE;
- Press and release the Power key;
- Press the Volume up key to factory reset the handset;
The phone is restored to factory settings.
:good:
EDIT: GOSH, I'm sick of trying every freaking thing. Doesn't work with Hard reset!!!!
---------- Post added at 10:21 PM ---------- Previous post was at 09:47 PM ----------
The problem is inside HTC's kernel, so we can't really do anything about it.
And I think I will go for a custom kernel, because HTC will take it's time to fix this and realese update.
Cheers.
Luckyone199 said:
Solution, I think, is to do HARD reset. Atleast it's working fine now in ''MultiTouch Visualizer 2''. Haven't tried in games.
:good:
Click to expand...
Click to collapse
I tried a hard reset 1000 times and it doesn't work. I just think, the htc developers are noobs lvl infinity and the devs on xda are real pro's
We have to wait until htc releases the kernel source and the xda devs fix this bug
Sent from my HTC Incredible S using xda app-developers app
Any news? I'm getting pretty annoyed with this problem, because i can't write on Smart Keyboard Pro.
Yup. I'm facing this bug too. YOU'RE NOT ALONE.
Sent from my potato chips using xda boost
Any news on the touchbug yet?
I'm experiencing the same problem.
When I type fast (with two fingers) in Wahatsapp or SMS, the keyboard starts acting weird.
On a HTC Rhyme with ICS and Sense 3.6 (frow htcdev.com) everything runs smoothly. (same processor and resolution as htc incredible s).
So it's bug specific on HTC Incredible S ICS/Sense 3.6 software.
Has anyone received news yet or contact with htc about this? It's pretty annoying and I would think that HTC should issue a patch to resolve this.
hotdenio said:
I'm experiencing the same problem.
When I type fast (with two fingers) in Wahatsapp or SMS, the keyboard starts acting weird.
On a HTC Rhyme with ICS and Sense 3.6 (frow htcdev.com) everything runs smoothly. (same processor and resolution as htc incredible s).
So it's bug specific on HTC Incredible S ICS/Sense 3.6 software.
Has anyone received news yet or contact with htc about this? It's pretty annoying and I would think that HTC should issue a patch to resolve this.
Click to expand...
Click to collapse
With arhd, xs-kernel and v6 supercharger, i'm not facing the problem anymore.
MrToastbrot said:
With arhd, xs-kernel and v6 supercharger, i'm not facing the problem anymore.
Click to expand...
Click to collapse
I think so, or maybe it is less apparent
Sent from my Nexus 7
The problem is in kernel, so i guess if you put a custom kernel this bug will disappear.
Edit : nop, that didn't work for me.
Go for gingerbread, ics has to much issues for me, just like jb.
Sent from my HTC Incredible S using xda app-developers app
Silversniper said:
Go for gingerbread, ics has to much issues for me, just like jb.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
False. Just flashed Nik Project X v4.1 with HTC Sense 4.0.
Multi-touch bug is gone, even though they use stock kernel. I guess the problem was in HTC Sense 3.6.
P.s. ROM is working flawlessly. Best rom I've ever had. :laugh:
I'm also facing the multi touch prob using niks project x v4.0, with lost prophets Kernel
Cheers
Sent from my HTC Incredible S using xda app-developers app
I'm getting tired. And anything I could say now is - ''What the f**k?''
Multitouch was working on Nik Project X v4.1 fine until.. I don't know really.
And now, when I want to get it working again, I randomly change some settings or force close some apps(for example ''Media Link HD setup'') it starts working again, but, unfortunately - not forever.
Trying to find solution, but can't find any.
Begging for solution... :laugh:
Peace!
p.s. Multitouch is working in some apps. For example N.O.V.A 3, but not working in other apps, like Jet Car Stunts, Gangstar Rio: City of Saints, MultiTouch Visualizer 2 etc. Zooming in browsers and something like that works fine.
can't type "P" or "0" on keyboard. dead spot on touch screen.
I can't type the alphabet "P" or "0" on sense 3.6 Rom.
and on sesne 4 rom, can't type "0" ( P is working)
With show touches & pointer location from dev option, clearly about 1 cm of touch screen is not working. (no touch show beyond 1 cm of right margin.)
take a look at pic, pls.
Because of dead spot, I can't type alphabet "P" and "0" and can't play some game like https://play.google.com/store/apps/...DEsImNvbS5lY2FweWNzdy5vbmV0b3VjaGRyYXdpbmciXQ..
drcrazy91 said:
I can't type the alphabet "P" or "0" on sense 3.6 Rom.
and on sesne 4 rom, can't type "0" ( P is working)
With show touches & pointer location from dev option, clearly about 1 cm of touch screen is not working. (no touch show beyond 1 cm of right margin.)
take a look at pic, pls.
Because of dead spot, I can't type alphabet "P" and "0" and can't play some game like https://play.google.com/store/apps/...DEsImNvbS5lY2FweWNzdy5vbmV0b3VjaGRyYXdpbmciXQ..
Click to expand...
Click to collapse
Have you tried changing kernels?