Develop Bugs

Slow typing keyboard Black 2.5

Does anyone have a problem with a slow lagging keyboard while typing text messages. I noticed it after I installed the Black 2.5 rom. I have installed the keyboard mapping fix but that did not help the lagging issue.

I been typing like crazy today on my 8525/2.5 with MSN Live Messenger. Seems very fast to me..

I had the same delay...Can't remember if disabling the word completion took care of it or installing the memory performance cab from JJ that took care of it. I'm banking on the memory performance cab though.

I have noticed this issue a little bit, but if I remember correctly Ive had the problem even before isntalling any of the roms, and it only happened for the first set of characters that I types (usually the first word).
Has anyone else noticed this with the standard wm5 roms?

I've experienced the same issue.

I wonder if it was one of the patch cabs that I installed cause I have not seen a lag at all [yet]. Perhaps it is just waiting to pop up on me.

odie3 said:
I wonder if it was one of the patch cabs that I installed cause I have not seen a lag at all [yet]. Perhaps it is just waiting to pop up on me.
Click to expand...
Click to collapse
Are you talking about the pop up keyboard?
I think what the OP was taliking about is that when you first start typing with the pull out keyboard there is a slight lag, like with me, I'll start typing - it hesitates - and then it like catches up. Not only that but the screen even goes dim for a moment .
I don't remember if I had this issue before or not.

Nope, I was talking about the pull out keyboard. Seems to work very well so far. I just retested it in Work and in MSN IM.

odie3;1250895 said:
Nope, I was talking about the pull out keyboard. Seems to work very well so far. I just retested it in Work and in MSN IM.
Click to expand...
Click to collapse
Oh well.
I'm not going to concern myself too much with it, because I'm hoping by tomorrow I'll be running 3.0

Similiar typing issue here on 8525
I've noticed the same typing issue using both Black 1.2 and Black 2.5 were it often lags or simply skips a letter (usually "h" after "t" leaving "te" instead of "the" or "s" after "i" leaving "I" instead of "is")
I tried uninstalling and reinstalling the 8525 keyboard fix cab, but it does not help.
Two things I have noticed:
1.) The typing problem does not seem to appear until several days after I flash the ROM.
2.) It really only seems to affect the Messaging app. (When I type into PIE forms or Notes, the problem does not seem to exist)
Definitely did not have this problem in WM5, so I am hoping that the problem will be gone in Black 3.0

this is a real problem. I have experienced it with all wm6 roms I have installed. I have a strong feeling its related to the suggested word list that comes up....but this is a rediculous problem for us to have to deal with and should be fixed. I also agree that its limited to the messaging app.
Ezra

yes the problem i was originally talking about is with the messaging app only. i have no problems in word, or IE. I have the memory performance cab installed but noticed it before that as well. does anyone see a difference with the suggestive words disabled?

Put 3.0 on Hold
njmarchetti said:
...clip...I am hoping that the problem will be gone in Black 3.0
Click to expand...
Click to collapse
I'll PM JJ and ask him to hold off on the release of 3.0 until he's sure we won't have this issue.
Just Kidding. .

I actually started a thread about this a while ago but titled it in reference to skipping keys because I type so fast with the thumb keyboard that the device cannot keep up and omits some of my key-presses. However, someone suggested something that I had tried with WM5 (but it didn't work then) but hadn't thought to do with WM6.
Go to Settings>Input>Word Completion(tab) and change the "Suggest after entering" setting to something such as 3 or more letters. I have mine set to 4 letters and have zero problems with skipping or slow typing unless in a third party program such a TomTom.

a little out of topic...
but after changing to black 2.5 my time zone seems to be weird....i had tried to set it to GMT+8 Singapore time....but after a while it will change to another country thats GMT+8 but when i change it back to GMT+8 Singapore time.....it will be one hour early.....

I have the slow keyboard problem too.. Its making me mad.. And the black2.5 rom seems to slow down a heck of allot after a week or so use.. Any ideas why would this be aswell?? I only have 4apps installed.. One on today screen and rest only when i use it..

a slow keyboard is one thing, but skipping letters is another. (This issue pertains to not only Black, but also Custel, LVSW, and Dutty)
The thing is, when i text message, i start typing immediately after the window pops up. But for some reason, it lags, and then when it catches up i notice that my first 3 words are so are all butchered cuz letters were dropped. I didn't experience this issue with my MDA Vario / 8125. The worst that would happen is the text would lag, but would eventually catch up to my typing. And it WOULD NOT drop any letters. With the new wm6 roms for hermes, im noticing lag and letter dropping. I've tried the suggestion of even turning off autocomplete, and setting 1 word, 2 words, 3 words, and 4 words. Still having the same issue. I opened a thread about it long ago, but it just got closed because they "supposedly" deemed it a fixe issue. Well its not!
To clarify: I'm not trying to bash any of the rom chefs' work, as i am very thankful for what they do. But it would be very nice to have this issue addressed and fixed.

Has anyone tried changing the Up/Down Control repeats....
Settings/Buttons/Up Down Control?
I put mine up to max, and seems to have fixed my problem....

@ **Milo**
Hi and thanks for the sugestion , i tried it and my slow typing issue has gone. As an experiment i switched the rate back to where it was (about one third of the way up the slider) and its still gone. It seems switching the slider up to max cleared whatever setting was causing the slow down.
Im going to leave the phone on standby for a while then try it again to see if this has any effect on it.

*MILO* said:
Has anyone tried changing the Up/Down Control repeats....
Settings/Buttons/Up Down Control?
I put mine up to max, and seems to have fixed my problem....
Click to expand...
Click to collapse
And it seems to have cured mine too. Thanks mate.

4 Hard Button Go Crazy on Android

I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?

Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.

I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.

What device do you have? RAPH100?

Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.

Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.

dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...

Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.

also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.

@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.

twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.

+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.

spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.

Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)

devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times

While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.

I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.

I don't think it has anything to do with WM. For me, it only happens in Android.

firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...

But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App

the features that make me want to keep wp7 never work...

Am I the only person who thinks that if wp7 just worked (as is), you would be 100% satisfied?
My live tiles have never worked properly and using more than 4 drains battery. The web browser is very fast when it works but more than a few times it has locked up and randomly rebooted the phone. The GPS never gives me the correct location, showing me as being more than a mile away from where I really am. When I see something I really want to take a picture of I try to go straight to the camera app by holding the camera button, nothing happens and I have to let go and hold it again.
I am not saying that I don't love wp7, because to me it is better than both iPhone or Android. I just wish it would work the way i expect it to.

The camera button wont work if the proximity sensor is being covered. and i'm satisfied! apart from bluetooth which to me is completely useless as it seems to never work but i've found the gps on my omnia 7 to be awesome, never yet had a lock up or automatic reboot! Mango is going to fix many problems anyway so it'll work out for you

Thanks, I hope so because it is a great os just been very buggy for me.

Which device do you have, OP?
A lot of those issues you're describing sound like a problem with the internal memory or a memory card..
I've never had my phone randomly reboot

I've had quite a few random reboots but none of the other problems mentioned in the OP.

You are just *****ing !!!!!!!!!
ryude said:
Am I the only person who thinks that if wp7 just worked (as is), you would be 100% satisfied?
......
I am not saying that I don't love wp7, because to me it is better than both iPhone or Android. I just wish it would work the way i expect it to.
Click to expand...
Click to collapse
Another one with a bold statment in the title so ppl read it ..... what is all about ???? its just ....*****ing
Realy tired of those kind of post arround here...

Andrmgic said:
Which device do you have, OP?
A lot of those issues you're describing sound like a problem with the internal memory or a memory card..
I've never had my phone randomly reboot
Click to expand...
Click to collapse
Yes. Which device do you have. I've had none of the above issues and my phone just works AND it's a Dell Venue Pro.
There are live tiles that can become stuck at times like Alphajax and Weatherbug. They eventually release. But, Mango seems to have fixed those issues.

I have the 1.3 Samsung focus using 7390 nodo. This is my third focus and they all had the same problems.

colossus_r said:
Another one with a bold statment in the title so ppl read it ..... what is all about ???? its just ....*****ing
Realy tired of those kind of post arround here...
Click to expand...
Click to collapse
Yeah right.

Might be a Samsung issue then.

ryude said:
Am I the only person who thinks that if wp7 just worked (as is), you would be 100% satisfied?
My live tiles have never worked properly and using more than 4 drains battery. The web browser is very fast when it works but more than a few times it has locked up and randomly rebooted the phone. The GPS never gives me the correct location, showing me as being more than a mile away from where I really am. When I see something I really want to take a picture of I try to go straight to the camera app by holding the camera button, nothing happens and I have to let go and hold it again.
I am not saying that I don't love wp7, because to me it is better than both iPhone or Android. I just wish it would work the way i expect it to.
Click to expand...
Click to collapse
The only - well known for others too - issue I had on NoDo is the tiles not updating, Marketplace not showing updates - all this push stuff.
However browser and GPS are fine, and the phone rebooted itself maybe once - rock solid performance actually (LG Optimus 7).

ryude said:
I have the 1.3 Samsung focus using 7390 nodo. This is my third focus and they all had the same problems.
Click to expand...
Click to collapse
Do you have a memory card in the phone? if so I am sure you know not all memory cards work...

Well, I have the Samsung Focus 1.3 running 7390 and I've never had those issues.
BTW, the Samsung Focus is notorious for battery drain because of the AMOLED screen.
Anyhow, I've had a few times were the browser shut on me. I just have to launch IE again; I've experienced no reboot issue.
The GPS also gives me accurate location.
As for the camera app, you have to NOT block the proximity sensor when launching from the camera key.
Anyhow, seeing that you constantly have issues with the Samsung Focus model, I suggest you trade in for the HTC Surround or the LG Quantum and see if you have issues there.

I am holding out for a mango device, I am thinking of buying the nokia sea ray or whatever they release. Glad to know that it's not a widespread problem guys, thanks.

About the GPS, you must allow the GPS device to re-locate your location, depend how strong your network are.
This forum have several articles like this when people can't believe themselves when the device show they are LA instead of San Francisco.
I know my HD7 never goes away that far, but it does show the wrong location of mine for a least a mile away several times in a few minutes/

None of those problems on my HD7 ... I'm trying to hold out for Mango. Sounds like they are hardware related though. I'm sticking with what I've got. No sense in buying a new device that is going to have its own bugs.
My problems with the my device are entirely software related ... Cept for the lack of a keyboard and possibly the pink camera hue.
Sent from my HD7 using XDA Windows Phone 7 App

ryude said:
Am I the only person who thinks that if wp7 just worked (as is), you would be 100% satisfied?
My live tiles have never worked properly and using more than 4 drains battery. The web browser is very fast when it works but more than a few times it has locked up and randomly rebooted the phone. The GPS never gives me the correct location, showing me as being more than a mile away from where I really am. When I see something I really want to take a picture of I try to go straight to the camera app by holding the camera button, nothing happens and I have to let go and hold it again.
I am not saying that I don't love wp7, because to me it is better than both iPhone or Android. I just wish it would work the way i expect it to.
Click to expand...
Click to collapse
Aint going to comment or fuel any more whinning or *****ing in this post (yours and from others replying here), but I will comment on the issues you've had compared to mine.
Live tiles are working just fine atm... I've had some issues in the past, but they all seem to have vanished. Weather, Facebook, Foursquare, Twitter and a few others and they all work fine now. As for them draining my battery, I do give the Trophy a good run for its money during the day and it still gets home late at nite with enough battery.
Never had any issues with the browser... fast, has NEVER crashed or locked the phone. Don't know what else to tell ya.
GPS also works great... very fast in Foursquare, and I've compared it to at least 2 Android devices and it just flat out won. Map wise, finds my location just fine, doesnt take the 5 minutes to find my location that I've seen some devices take.
Ain't it time you got something non-Samsung ?

Samsung on android sure does suck buggy as hell and GPS never worked on the moment intercept and it buggy on epic
Sent from my arrive using XDA Windows Phone 7 App

I should look into pointing this forum post out to some people in some company that might find it interesting.
Sent from the miui matrix SGH-i897

about the live tiles and push... this will be fixed in Mango. Live tiles and push before Mango are hit or miss, badly implemented and poorly tested. If your carrier does not support it propperly it will not work on NoDo... Mango fixed almost every issue regarding push (as far as I noticed, am testing it for a few weeks now).
It sucks they did not implemented it properly at first, since a lot of the people have not been able to use apps with live tiles AT ALL. Mango fortunately corrects this, better late then never.

Sticky/Unresponsive Buttons - Are you affected?

I personally have the very annoying issue with my L900 where the buttons sometimes "push themselves" then become unresponsive. Does anybody else have this issue? Can it be fixed?

I've never had them push themselves, but they are definitely less responsive than my HD7... At least that's what it seems like until I actually see precisely where my finger/thumb is pressing.. If it's not dead on the center of the "button" then it won't recognize it as a press.. So I don't think it's that they're unresponsive, I just think that on the Lumia 900 they made the area around the buttons less sensitive to prevent accidental key pressing that tons of WP7 users have complained about. Accidentally hitting search when handing your phone to somebody to look at a picture or whatever...
But like I said, mine don't press themselves --- I'd arrange to have your phone serviced...

Have you tried going into Diagnostics and testing your buttons functionality repeatedly to test responsiveness and see where they like to be pressed.
Sent from my Lumia 900 using Board Express Pro

I frequently have the problem where the buttons become unresponsive. Then when you press the back button, it 'sticks' and brings up the multitask screen. I've seen this reported elsewhere on the forum.

I was also having trouble with this. After searching the WPCentral and Nokia Support forums I found that it has to do with the speaker. I didn't believe it at first but you can replicate the problems 90% of the time.
Do this:
Play a game on max volume for about 5 minutes.
Try exiting using the back button or the Windows button. 90% of the time it will "stick."
Now play a game again on max volume, but with headphones.
When you try and exit, it will work 100% of the time.
Also if the buttons are sticking you can plug something (anything) into the headphone jack and they will work again. The rumor is that the speaker interferes with the buttons. Sometimes I have them activate all by themselves, which can be annoying when streaming video. Some people have reported the only option is to take your phone back to the store and get a new one. But the odds of getting a good one are slim.

I almost never play games, and don't listen to music often. And my Back button does occasionally bring up the multi-task view. Probably about 1 in 10 presses. Rather than sticking I attribute it to a timing issue, where the device has a problem discerning between a long/short press. Might have to do with how much work the processor is doing at the time or how much memory is being accessed. Not sure.
Sent from my Lumia 900 using Board Express Pro

Actually, a lot of people have this problem with unresponsive buttons. Nokia is ignoring everyone with this issue.
http://discussions.nokia.com/t5/Nok...mia-900-touch-capacitive-buttons/td-p/1375977

Never had this, even though I play games (but with sound turned off) and listen to music a lot...

nraudigy2 said:
Actually, a lot of people have this problem with unresponsive buttons. Nokia is ignoring everyone with this issue.
http://discussions.nokia.com/t5/Nok...mia-900-touch-capacitive-buttons/td-p/1375977
Click to expand...
Click to collapse
Actually, I don't think Nokia is ignoring anything. They can't afford to. What I do think is this is an intermittent problem, possibly associated with certain 3rd party apps or settings. Once they can pinpoint the issue it will be corrected.
I lived through a disappearing keyboard that Microsoft took more than 3 months to correct and AT&T still has not had the decency to push out the appropriate update (I did a forced update on my Surround in March). That issue drove me nuts, and kept me from typing replies like this one. On a bug scale of 1-10, that was an 8. The occasional Back button glitch, is more like a 2-3. I can live with it till Nokia pins it down.
Sent from my Lumia 900 using Board Express Pro

jimski said:
Actually, I don't think Nokia is ignoring anything. They can't afford to. What I do think is this is an intermittent problem, possibly associated with certain 3rd party apps or settings. Once they can pinpoint the issue it will be corrected.
I lived through a disappearing keyboard that Microsoft took more than 3 months to correct and AT&T still has not had the decency to push out the appropriate update (I did a forced update on my Surround in March). That issue drove me nuts, and kept me from typing replies like this one. On a bug scale of 1-10, that was an 8. The occasional Back button glitch, is more like a 2-3. I can live with it till Nokia pins it down.
Sent from my Lumia 900 using Board Express Pro
Click to expand...
Click to collapse
The Back button "sticking" happens to me every time I send a text message. So for me that is about 15-20 times a day. I don't play many games anymore because the buttons activate themselves too often to enjoy it.
I think Nokia is trying to ignore this problem. If you look on their forums you'll see someone was told, "Our engineers can't replicate the problem." It's something that I can replicate 99% of the time. You hear a lot about the Blue screen at low light but I haven't read one news story about this. Maybe it's time we put pressure on Nokia.

The_Vermonster said:
The Back button "sticking" happens to me every time I send a text message. So for me that is about 15-20 times a day. I don't play many games anymore because the buttons activate themselves too often to enjoy it.
I think Nokia is trying to ignore this problem. If you look on their forums you'll see someone was told, "Our engineers can't replicate the problem." It's something that I can replicate 99% of the time. You hear a lot about the Blue screen at low light but I haven't read one news story about this. Maybe it's time we put pressure on Nokia.
Click to expand...
Click to collapse
It's probably a hardware issue and they don't want to replace those with new phones. Not good for Nokia.

nraudigy2 said:
It's probably a hardware issue and they don't want to replace those with new phones. Not good for Nokia.
Click to expand...
Click to collapse
If you go into the Diagnostics menu, you can test those capacitive buttons 100 times, like I did, and they will perform perfectly. Got the same results when I tested the camera button (yes, another 100 times). Despite that, the capacitive buttons do occasionally register a long press. That's a software glitch.
Sent from my Lumia 900 using Board Express Pro

The_Vermonster said:
The Back button "sticking" happens to me every time I send a text message. So for me that is about 15-20 times a day. I don't play many games anymore because the buttons activate themselves too often to enjoy it.
I think Nokia is trying to ignore this problem. If you look on their forums you'll see someone was told, "Our engineers can't replicate the problem." It's something that I can replicate 99% of the time. You hear a lot about the Blue screen at low light but I haven't read one news story about this. Maybe it's time we put pressure on Nokia.
Click to expand...
Click to collapse
Ok, whatever. So I guess it's a Nokia conspiracy to cover up a bug so they don't have to send out another $100 to everyone. Btw, I do write 10-12 texts per day and have a terrible (WindowsMobile) habit of always backing out of everything, even though in testing I found it has zero effect on battery life. I do not recall ever having the multi-view screen popup or the Back button being unresponsive when exiting the Messaging app. So maybe its a software glitch (capacitive button are software controlled-hence capacitive) on your phone. Have you tried a hard reset? It can work wonders.
Sent from my Lumia 900 using Board Express Pro

same issue here. But it feels like a software issue. i did some experiment and come into conclusion that this wont happen when you playing video on 3rd party apps e.g., Metrotube, Netflix.
Did anyone try this way?
hopfully, Nokia can address the issue soon.
Sent from my Sony Tablet S using xda app-developers app

I went to AT&T to get a replacement because the capacitive buttons don't respond that good during an audio playing through the speaker. I showed the AT&T rep the issue and he called to get me a replacement device. He was using a black Lumia 900. The brand new phone came in. The capacitive buttons always work now. Definitely a hardware issue. Volume buttons work when locked. Camera button works 50% of the time. The Tango update should fix the camera button as it is confirmed by couple people.

What do you mean by "camera button works 50% of the time"? Works where? Do you mean launching the camera when the phone is locked by a long press on the camera button?

efektos said:
What do you mean by "camera button works 50% of the time"? Works where? Do you mean launching the camera when the phone is locked by a long press on the camera button?
Click to expand...
Click to collapse
I have that problem too, but it will only work if I have no apps running and I have the pin disabled.
As far as the "sticking" buttons, I can't say that 3rd party apps are any better. IE and Surfcube 3d were both having the same problem watching videos. Youtube videos seem to play fine but Nokia Trailers never work. All games fail miserably, even simple ones like Minesweeper.

nraudigy2 said:
I went to AT&T to get a replacement because the capacitive buttons don't respond that good during an audio playing through the speaker. I showed the AT&T rep the issue and he called to get me a replacement device. He was using a black Lumia 900. The brand new phone came in. The capacitive buttons always work now. Definitely a hardware issue. Volume buttons work when locked. Camera button works 50% of the time. The Tango update should fix the camera button as it is confirmed by couple people.
Click to expand...
Click to collapse
Ok, so is the new phone running the exact same firmware as the old phone? Did you ever try a hard reset on the old phone, and then not load any apps during the test period?
And the Tango update won't fix anything. The Nokia firmware update, that is supposed to to be attached to the AT&T Mango update, with though.
Sent from my Lumia 900 using Board Express Pro

jimski said:
Ok, so is the new phone running the exact same firmware as the old phone? Did you ever try a hard reset on the old phone, and then not load any apps during the test period?
And the Tango update won't fix anything. The Nokia firmware update, that is supposed to to be attached to the AT&T Mango update, with though.
Sent from my Lumia 900 using Board Express Pro
Click to expand...
Click to collapse
_______________________________________
I meant the Tango update that comes with the firmware update if you flash it using Nokia Care suite. New phone is running the latest firmware from Zune with Mango. Not the latest Tango update yet. I don't really want to wipe my device again. Nokia is ignoring this issue maybe because there is no fix for it.

nraudigy2 said:
_______________________________________
I meant the Tango update that comes with the firmware update if you flash it using Nokia Care suite. New phone is running the latest firmware from Zune with Mango. Not the latest Tango update yet. I don't really want to wipe my device again. Nokia is ignoring this issue maybe because there is no fix for it.
Click to expand...
Click to collapse
Sorry if I wasn't clear.
Is your new phone running the same firmware as your old phone, or a newer version?
Did you ever try a hard reset on your "old phone", without loading any third party apps during a 24-48hour test period to see if the capacitive button issue went away?
I am always puzzled by users who are reluctant to hard reset their phones, but have no problems exchanging their phone, which is in effect a hard reset. If it's not, it should be a requirement 24 hours prior to any exchange.
Sent from my Lumia 900 using Board Express Pro

Touch screen issues?

Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...

RealEvil_UK said:
Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...
Click to expand...
Click to collapse
I have same issues with my g4 here in the US.

Unfortunately same here, on a G4, korean model F500S.

I have the same issues on my G4. So probably returning it won't solve it. I notice it the most when I am scrolling in Facebook or web pages I will open a link accidently.

I have the same, occasionally it just won't respond to some taps, i find just pressing the standby on/off button quickly sorts it but it is very annoying.

same here in israel, sometimes do not respond to double tap on lock screen to wake the G4 up
im sure its a software issue, prolly the LP 5.1

Are so you guys using screen protectors? That was the issue for me with g3 and g2.

20degrees said:
Are so you guys using screen protectors? That was the issue for me with g3 and g2.
Click to expand...
Click to collapse
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?

Try...SGS Touchscreen Booster - Google Play Store
I have run into this same problem with my Verizon G4 (VS986). Many of my taps have gone unrecognized.
I did find this.... http://forum.xda-developers.com/g4/help/fix-touch-screen-registering-touches-t3128518
I tested the software that was recommended...and IT WORKED!
Give it a try...can't hurt!

nipun1110 said:
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?
Click to expand...
Click to collapse
After market but plastic.

Just started to get issues where taps on the far left-hand side of the screen don't work.

blackknightavalon said:
Just started to get issues where taps on the far left-hand side of the screen don't work.
Click to expand...
Click to collapse
Okay, I was able to replicate my bug. It happens after playing a game and stops after some time. Turning autorotate back on and switching back and forth from landscape view fixed it.

Hey guys.
I was searching the forums for a fix that solves the phantom/ghost touches I'm getting frequently on my LG G4, H815 model.
Sorry for the long post but my case looks a little more complex than the ones I've been seen in here.
In my case, that's how it happens:
I receive several multi-touches at the same time, usually when Data is enabled. Sometimes it starts right when I switch from Wi-Fi.
It happens often when I'm driving and using Location+Data as well, which drives me crazy. I does also happens (like another user mentioned in this thread) when scrolling down a feed (such as on Facebook) and it suddenly likes/shares a photo/post. It also drives me crazy! And there is also the case where it taps the keyboard and send crazy typos on chat apps when you are real-time texting someone! Another hassle is right after using the camera and opening the gallery to show someone the taken photo...it suddenly scrolls the gallery and open another photo. I just can't make it to see the taken pic. Therefore, I really wanna fix this so bad since it happens every time I need something right away.
A workaround that's been helping, though it's a pain:
I found that pressing the On/Off button and giving it a few seconds will return it to a normal state. The problem is when it happens while I'm driving and are supposed to take an exit/make a turn at the moment. There are some other cases where I'm into something and giving this few seconds is not an option.
Trying right now:
Someone suggested in this thread to use the SGS Touchscreen Booster. I'm giving it a try right now.
Important notes:
This issue has been happening since I got this phone on November, 2015. We got this 6.0 update recently and I was hoping that it would fix it. It didn't.
I have an after market screen protector that I applied in order to see if the issue would go away. It also didn't.
I have been searching about a digitizer replacement but I don't think is a hardware issue, since it just doesn't happens when I'm only on Wifi at home with Data disabled. I believe that the problem is the Data connection that triggers smth.
Any thoughts?
Does anyone have any idea or have experienced the same scenario before? Any thoughts on my guess of data enabling triggering the ghost touches?
Sorry for the long post and thank you so much for reading it.

I think it's both, its hardware and software, LG tried to fixed it but it makes it worst. You can solve the problem for few seconds putting your five fingers at the home menu, It goes crazy and after it stopped making ****. Anyway this phone is great but all the problems make it ****.

I am going to use this thread even though I think my problem is not as serious as yours are.
My problem is that touches are registered, but no action is taken.
For example. Quickly tapping on an icon on the home screen will highlight it, but it will not open the application. I enabled the option in Developer mode to display the touches and the touch is registered. It's just that the app will not load. If I click for a tad longer - it loads. Happens on both stock Launcher and Action Launcher. I have not noticed it happening outside the launcher.
I read something about a keyboard update, but in the Update Center I don't have anything related to the keyboard.
The icons I see it happening with are located in the lower part of the screen.
I am almost sure that this is a software problem, but several updates have not fixed it. Currently on v20d.
Any suggestions or ideas?

After a few more testing and monitoring, I found out that the ghost touches only take place when I'm on LTE.
And even more weird, while driving through some specific areas when I'm commuting.
It's just so weird to think that some towers may send a LTE signal that may cause the ghost touches.
At home, at work, wifi or data, it doesn't happen.